* Brooklyn Linux Solutions CEO [Mon, 23 Apr 2001 19:23:34 -0400 (EDT)]:
It's functionality depends on it being initated correctly by the kernel.
Nope! modules.conf configures the loading of modules, i.e. which modules have to be loaded for things the kernel is looking for and which parameters the modules get passed.
mkinitrd does this for RH. This file does not exist in SuSe. Instead it is done with /etc/rc.d files.....
mkinitrd creates an initrd, i.e. an initial ram disk. This is something completely different! The initrd is mainly used to load drivers needed by the kernel to boot correctly, most prominently the drivers needed to access the disk. And, BTW, we do have such a tool, it's called mk_initrd in SuSE Linux.
The new kernel doesn't work with the old configuation......
How do you expect a configuration for 2.2 to completely work for a 2.4 kernel, given the differences between those two kernels? Philipp -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390