On Fri, Feb 21, 2003 at 04:33:03AM -0000, Rajaram Suresh Gaunker wrote: > here are two cases when it is loaded as module or fixed in kernel > as permenent resident , then in later case where i need to chnage > , from documents i got that i need to change vfs code but wher are > those files No. That is the whole point of a VFS; one can add a new filesystem _WITHOUT_ changing the VFS code. :) The VFS is there to modularize filesystem support enough that nothing in the kernel needs to change to support your new filesystem. To address your question of how your module code should register with the VFS subsystem even if you compile your module statically into the kernel, this is remarkably easy. You don't have to do anything special. :) When you register your module's init function with the module_init() function (see include/linux/init.h), the build system will automatically Do The Right Thing if the module is compiled into the kernel. When you build your module statically into the kernel, the kernel will call whichever function you specify early in the bootup process. (Before control is handed over to init(8).) It all works magically. :) For more details, check the Linux Device Drivers, 2nd Edition, Chapter 2. http://www.xml.com/ldd/chapter/book/ch02.html -- "Nothing says, 'Superpower' like bombing a country that is poor and hungry." -- Ken Brush
Attachment:
pgp00328.pgp
Description: PGP signature
