> 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. Holden -- 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
