> If a kernel code requires an external loadable module then will it get > loaded automatically?
Yes it will be, after you install a module, depmod is run which generates a file called modules.dep . modules.dep lists all dependencies for every module. These dependencies are then automatically loaded by modprobe when you try to load the actual module. > If the code requires the kernel module much earlier > than the filesystem is loaded and the module is made available than I should > provide it earlier. This should require to make the external module be part > of the kernel. So how might I do this? First of all, is the code going to be used again after it is used once? If not, then it is probably a better idea to include the kernel module in an initial ram disk (initrd). This solves both the problems - of loading a kernel module before the FS module on which it resides is loaded, and at the same time not being forced to include the module within the kernel itself. -Joel -- Twitter: http://www.twitter.com/joelagnel Web: http://www.hackerbliss.org/ -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecar...@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ
