SUMMARY: Startup Modules

[email protected]
Newsgroups gmane.linux.admin.managers
Message-ID <OF54DC1037.0A00A9A1-ON80256D4B.00324252-80256D4B.00340ECA@waverider.net.uk>
Hi All,

The consensus is that the answer is very much distribution specific.

However, the answers can be summarised as follows:

Redhat: amend the file /etc/modules.conf to include a line
        "alias scsi_hostadapter driver"
unless the module is required for the root filesystem (which in my case it 
isn't).

SuSE: add 
        "modprobe driver" to the /etc/init.d/boot.local file
unless the module is required for the root filesystem.

Debian: add the module name to /etc/modules

Alternatively, a quick and dirty fix would be to add a modprobe modulename 
to the rc.local.

If the driver is required for the root filesystem, the module has to be 
either compiled into the kernel, or available on the initial ramdisk (see 
initrd).

Many thanks to everyone for your answers (too many to list individually), 
but I must give a special mention to D. Stimits for a great explanation of 
the relationship between the kernel and the /dev filesystem, and then how 
modules fit into the overal picture.

A.

-- 
Andy Cowan
Wave Rider Internet Ltd
W: http://www.waverider.net.uk
T: 0121 603 3888
F: 0121 603 3777
_______________________________________________
LinuxManagers mailing list - http://www.linuxmanagers.org
submissions: LinuxManagers-35TzE1X9F6582KRnZfj+bdi2O/[email protected]
subscribe/unsubscribe: http://www.linuxmanagers.org/mailman/listinfo/linuxmanagers
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.