a few related questions, building up to using LVMs: 1) i'm pretty sure this is true, but just wanted to confirm that part of the install process is to build the initial "initrd" image based on which features you select during the install itself.
for the longest time, i've noticed that my initrd images contained only ext3.o and jbd.o, given that i select ext3 filesystems during install. for the first time recently, i chose to create some logical volumes and, sure enough, my initrd contained ext3.o, jbd.o and lvm_mod.o. so clearly the install process takes care of this, right? 2) to play it safe, i created a non-LVM /boot ext3 partition outside the volume group, and everything else as a logical volume. i'm assuming there's no way to have /boot as a logical volume since i can't imagine any way that the boot process can get to a logical volume to start the boot process. is this a fair statement? 3) after having installed using LVMs, i downloaded and built a new kernel (2.5.59) and built LVM support right into the kernel, but booting this new kernel failed almost immediately with "Uncompressing kernel ..." and that was it. given that /boot was still a non-LVM ext3 partition, is there something else i have to do to build a new kernel that works with LVM? am i forgetting something really trivial to make this work? rday -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
