On Tue, 2002-06-04 at 18:27, Mark Hounschell wrote: > Austin Gonyou wrote: > > > > On Tue, 2002-06-04 at 17:27, Jan Hudec wrote: ........ > > > Kernel does not seek for modules to load in any way. Actually, in usual > > > installation there are tons of modules compiled an mostly unused. You > > > must put the insmod command (or better modprobe command) somewhere in > > > the init scripts. Since I expect your installation is RedHat (the kernel > > > version looks like a RedHat one), there should already be one a it > > > should be loading all modules listed in /etc/modules.conf (not sure abou > > > the exact name - I don't have RedHat). > > > > Isn't that what modules.conf (conf.modules on some) is for though? To > > have lists of available devices and load modules if their services are > > used?(i.e. ifup eth0, but eth0 doesn't exist at boot time, so ifup calls > > a utility that loads the module, then ifup continues to run) > > > The utility is built into the kernel, it's called kmod and uses /etc/modules.conf > as it's config file.... That's all my point was...:) Thanks! > > Mark > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
