On Mon, 14 Feb 2000 Benjamin Scott wrote:
> /boot/module-info is used ... to map module names to the type of
> module (e.g., so that they know "3c501" is an ethernet driver), along with a
> short description and the parameters it needs.
On Mon, 14 Feb 2000 [EMAIL PROTECTED] wrote:
> I thought /etc/modules.conf (or /etc/conf.modules) did that, built when
> you did (i'm not certain which) make modules or make modules_install?
"make modules" builds the module files themselves, in the kernel tree.
"make modules_install" copies the module files from the kernel tree to the
"/lib/modules/$KERNEL_VERSION/" tree.
"/etc/conf.modules" gives default arguments to modules, and aliases specific
modules (e.g., "3c501") to generic names (e.g., "eth0").
However, there is nothing in the base Linux kernel which will automatically
setup "/etc/conf.modules" for you. Red Hat includes such functionality, and
it uses "/boot/modules-info" as a database of what modules do what, so that it
can fill "/etc/conf.modules" appropriately.
Make sense? :-)
--
Ben Scott
[EMAIL PROTECTED]
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
