> kerneld determines what module should be loaded by scanning the
> configuration file /etc/conf.modules There are two kinds of entries in this
> file: Paths (where the module-files are located), and aliases (what module
> should be loaded). If you don't have this file already, you could create it
> by running
>
> /sbin/modprobe -c | grep -v '^path' >/etc/conf.modules
My word, what a teeming horde of crap that generates, all of which was
either from defaults or already specified in /etc/modules.conf. I
prefer:
/sbin/modprobe -c | grep -v '^path' | awk '{print "# " $0}'>>/etc/modules.conf
as a less destructive form, which also follows the ancient tradition of
commenting out configuration lines which merely echo defaults. Use the
other name for the file in /etc if you prefer.
Keith