On Mon, 28 Feb 2005 15:49, Jeff Waugh wrote: > <quote who="O Plameras"> > > > 1. In CONFIG_????=y I am telling the kernel load the modules at boot time > > This is the bit you're confused about. When you set a kernel configuration > option to 'y' that means "build it in to the kernel" not "build it as a > module". A "module", in kernel lingo, very clearly means loadable objects, > not a particular configuration option. That's why we distinguish between > "y" (for "yes, build it in") and and "m" (for "build it as a module). When > you build something in to the kernel, the kernel doesn't load it - it's > already part of the kernel. > > - Jeff
And to expand on that, there is no guarantee that a module will get loaded at boot time. Different Linux distributions manage module loading differently but there usually is some sort of module configuration file in the /etc/ folder. There are also hotplug daemons and such that you might want to investigate. A search on Google is highly recommended... -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
