Re: {BIG MISTAKE} - what is modules.conf
In article <Pine.LNX.4.21.0010201239020.880-100000@satan>,
Peter Jay Salzman wrote:
>ok, so modules.conf is created by a call to update-modules.
>suppose i compile a new kernel. where along the process is conf.modules
>updated? all i ever see 'make modules' do is compile, and 'make
>modules_install' simply moves stuff around. surely, this file has to be
>modified when you compile a new kernel?
No, not really. /etc/modules.conf is the configuration file for modprobe(8)
and depmod(8). It specifies such things as what parameters are to be passed
to certain kernel modules, what modules to load for certain devices (for
example, load the 3c509.o module for the eth0 device), what modules to not
auto-load, etc.. You would need to modify the file if, for example,
parameters for a kernel module were changed (which usually doesn't happen
but its been known to). For more info, read modules.conf's man page.
>also, why only one file? most people have 2 or 3 kernels laying around, and
>sometimes very different ones (i have 2.2.17, 2.2.17-nosound, 2.4.0 and
>2.2.16). wouldn't it make more sense to have one for each kernel?
The 'path' setting you use in modules.conf can let you specify the location
of modules for different kernels. This setting can be dynamically set based
on the kernel version. So multiple modules.conf files aren't needed.
Again, for more info on this read modules.conf's man page.
---
===============================================================================
Arcadio A. Sincero Jr.
Computer Science Major at the University of Maryland Baltimore County,
Linux systems administrator, wanna-be Windows and Linux software developer,
amateur competitive bodybuilder and all-around nice guy.
WWW: http://www.arcadio.net/~asincero (COMING REAL SOON NOW(tm)!)
E-mail: mailto:asincero@arcadio.net
"Only *I* can prevent narcissism!"
Reply to: