2009/1/16 Greg KH <greg@xxxxxxxxx>: > On Thu, Jan 15, 2009 at 05:55:08PM +0800, loody wrote: >> Dear all: >> I try to porting linux on a new platform. >> After running vfs_caches_init, it will show >> "Mount-cache hash table entries: 512 >> <7>kobject: 'fs' (80007280): kobject_add_internal: parent: '<NULL>', >> set: '<NULL>'" > > This is with kobject debugging enabled, right? If so, it looks normal, > what is the real problem? > > thanks, > > greg k-h > Hi: thanks for your kind reply. my questions are: 1. from the log file, it seems somewhere in kernel, we go through kobjects one by one. (it is only my assumption) And it will do so if I call some functions in fs, like (sys_open((const char __user *) "/dev/console", O_RDWR, 0) < 0). If my assumptions above are correct, would you please tell me where entry point which check each kobject and what it is used for? 2. My kernel seems ready so far because it can successfully keep running before run_init_process("/sbin/init"), then it tells me "No init found. Try passing init= option to kernel." I know the problem comes from I didn't tell the kernel where the root file system is. I have googled the "root file system", but they only tell me the purpose of it and minimum elements it should have. But I cannot find any information tell me how to let the kernel know where it is. I have made a root file system with busybox in it and I also make it as ext2 format. where I should and what I have to pass this information to kernel? BTW, does root file system have any relationship with initramfs and initrd? appreciate your kind help, miloody -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ