Hi shyam,
modules.conf file is actually use by modprobe and depmod while
loading modules.For eg the man page of depmod reads
Depmod creates a "Makefile"-like dependency file, based on
the symbols it finds in the set of modules mentioned on
the command line (or in a default place). This dependency
file can later be used by modprobe to automatically load
the relevant module(s).
Actually depmod creates a file called modules.dep in /lib/modules/<kernel
version>/modules.dep file every time u boot.This file contains the various
object files,and their corresponding dependencies.Like loading msdos file
system requires a fat file system support ,so it will be requiring a fat.o for
it's existence.This is what we call as stacking of modules.I got this extract
from Writing Linux device drivers by Alessandro Rubini .Now u can
change how this depmod and modprobe should work using the
modules.conf file.A very good explanation is given in the man pages
of depmod and modprobe.
HTH,
HariShankkar.S
----------------------------------------------
Find out more about this and other Linux India
mailing lists at http://lists.linux-india.org/
