On Saturday 22 August 2009 05:13:00 pm John5342 wrote: > 2009/8/22 Bruno Wolff III <bruno@xxxxxxxx>: > > On Sat, Aug 22, 2009 at 23:22:19 +0200, > > > > drago01 <drago01@xxxxxxxxx> wrote: > >> On Sat, Aug 22, 2009 at 11:18 PM, Mike Chambers<mike@xxxxxxxxxx> wrote: > >> > On Sat, 2009-08-22 at 16:15 -0500, Bruno Wolff III wrote: > >> >> The initrd-generic file I get when installing new kernels in rawhide > >> >> doesn't work (raid devices don't get named as expected causing the > >> >> boot to fail), but running mkinitrd myself produces initrd files that > >> >> work. What component should I report this against? > >> > > >> > First guess is mkinitrd. They can change it accordingly if it's > >> > wrong. > >> > >> The generic initrd is created by dracut. > > > > Which is weird because the dracut package didn't get installed on the > > system even though I did a fresh install during the alpha freeze. > > If i understand correctly the initrd-generic is precreated by dracut > into another rpm which means dracut is not needed on the system. I > have raised my doubts over this method before on the list for exactly > this kind of reason but my comments were ignored :( dracut is in the kernel buildroot. the initrd is created when the kernel is compiled. Dennis
Attachment:
signature.asc
Description: This is a digitally signed message part.
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
