for the longest time, when i was teaching students how to rebuild a kernel, i would explain the purpose of the file /boot/initrd.img, but suggest that they could avoid having to deal with one by just compiling the necessary modules into the kernel and be done with it once and for all, and not have to mess with "mkinitrd" or having to mention it in their GRUB configuration file.
as it stands, the only modules supplied by red hat's current initrd.img are for ext3 and jbd, so it's easy enough to build those into a new kernel and not have to mess with initrd any more. is this a fair observation? and (i've mentioned this before) i'm still baffled why red hat doesn't just build ext3 support into the shipped kernel and be done with it. the rationale i've heard is that ext3 is still considered "experimental", but if that's the case, it's inconsistent to have ext3 as the *default* filesystem choice at install time, isn't it? anyway, if not for ext3, is it reasonable to suggest to students that they can skip dealing with initrd just to keep things simple? rday -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
