On Sat, May 03, 2003 at 02:42:08PM -0400, Robert P. J. Day wrote: > (perhaps related to an earlier issue as to why one needs > an initrd when using ext3 ...) > > earlier today, when demonstrating to a class how to rebuild > a kernel, i suggested that one could avoid having to deal with > creating an initrd.img if one built all necessary drivers into > the kernel. I'd much rather see courses that give student information on how to deal with initrds, instead of working around them by recompiling kernels. > as a test, i ran "mkinitrd" against the new kernel, > got my new initrd.img, and opened it up to find ... > no module at all. not surprising since everything was > in the kernel, and "mkinitrd" was smart enough to figure > that out. but using that module-less initrd.img got the > boot to work. You have to have LVM userland utilities to activate the volumes. Cheers, Matt msw@xxxxxxxxxx -- Matt Wilson Manager, Base Operating Systems Red Hat, Inc.
