On Sun, 18 Jul 1999, Sameer D. Sahasrabuddhe wrote:
> 1. Isnt kerneld the process that is responsible for loading all the
> modules? Maybe you should try a 'man kerneld' ...
okay. kerneld manpage says:
Apart from automatically removing unused modules, kerneld
also performs specific kernel tasks in user space by
responding to requests from the kernel via a dedicated IPC
message queue.
duno how that's useful.
> 2. The above script seems to look for the "/lib/modules/preferred" files
> first. So there must be a way to customise the whole process using that file.
the contents of this directory include:
-rw-r--r-- 1 root root 24438 Jul 20 1999 modules.dep
and subdirs which appear to contain actual modules (*.o files)
modules.dep seems to contain lines similar to:
/lib/modules/preferred/fs/vfat.o:
> 3. Theres a system variable $USEMODULES being accessed. Does it indicate
> that the kernel supports modules?
looking in rc.sysinit again, i find the following:
if [ -f /proc/ksyms ]; then
USEMODULES=y
else
USEMODULES=
fi
> Anyway, what happens when the system is "looking for modules"? Doesnt it
> already know where they are? Why do you want to disable this particular
> function, Satya?
"Finding module dependencies..." it waits there upto 30 secs, hdd
grinding. (4mb swap on 16mb main ram)
thanks :)
--
Satya.
Freelance website designer and CGI/Perl programmer.
http://satyaonline.cjb.net/
