Brooklyn Linux Solutions CEO wrote:
wrong, modules.conf is part of the modutils packages and is integral part of suse. /etc/rc.d files are part of the sys V init mechanism and has nothing to do with modules.conf.
Of course they are related. What does mk_intird do but create boot scripts for the kernel dameon.
I think you are confusing the initrd feature with sysv init scripts. /sbin/mk_initrd is a script that will take a bunch of kernel modules and other files and pack them together in a compressed file in the /boot directory, those are the initrd... files you see there. When linux boots that file is uncompressed and the modules in there are loaded, then the boot continues. The variable INITRD_MODULES in /etc/rc.config especifies which modules go in.
Are you saying that I use any init scripts and module.conf will look the same?
I don't understand that question.
The original /rc.d/boot - or some other script in that directory had a case in the shell script looking for kerneld and conf.modules or modules.conf or both or either ;)
The init scripts are a convenient way of booting a unix system, but it is not the only one. The module loading mechanism could be started some other way. Perhaps "not related" is not appropriate, they are part of the same system and each contributes to make your linux expereience what it is. I'll be damned, I just looked for kerneld and there is no such program in my suse 7.1. -- Rafael