On Thu, Oct 02, 2003 at 09:09:48AM +0800, Holden Hao wrote: > > This is a perpetual myth that won't go away. /etc/modules.conf is a > > configuration file for modprobe, and nothing more. It won't tell which > > modules get loaded at startup, but rather what parameters to apply to > > modules when they are loaded by modprobe. Also, it performs aliasing > > (e.g. alias eth0 mynetcard). > > What I have observed is that if I have module entries in modules.conf > for a device then it gets loaded automatically after an application > requests for the device but it does not automatically load modules on > startup.
Okay, but clarify what you mean by "module entries". There are a couple of options: you might have an alias or you might have the default parameters for a module. It's also possible to have pre-install, post-install, and quite a few other possible options in there. The most common usage is to put an alias in there for ethernet devices, such as this: alias eth0 bcm4400 But if you look through your startup scripts, you'll find that the script performs a "modprobe eth0" for you. That's probably what you're talking about above. Michael -- Michael Darrin Chaney [EMAIL PROTECTED] http://www.michaelchaney.com/ -- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
