On Sun, 26 May 2002, Joachim Breuer wrote: > For those running custom kernels with ext3 as a module: Also remember > to rebuild the initrd (after editing fstab), otherwise the root root > fs cannot be mounted... Not insurmountable using the install cd/rescue > mode, but unneccesary hassle.
technically speaking, this is not true. even without the ext3 module in the initrd.img, the boot will work just fine. given my curiosity with the different run levels, i've been experimenting with just what i can get away with in terms of booting/troubleshooting, and i tested just that. the boot works fine, and if you check /var/log/dmesg afterwards, you see the line: VFS: Mounted root (ext2 filesystem) readonly. so even though the root filesystem is an ext3 with the associated .journal file, there's nothing wrong with the kernel mounting it as an ext2 to start with, at which point, since the /lib/modules directories are on that filesystem, the ext3.o module can be loaded out of there. and afterwards, "lsmod" confirms that the ext3 module has been loaded. i tested this by just deleting the "initrd" out of grub.conf -- no problem. i suspect, of course, that if you were missing other initrd modules like scsi or raid, you'd have trouble. i'm hoping i tested this the right way -- anyone else want to confirm? rday _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
