[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [PATCH] initrd-generic.img -> dracut.img
- From: Jon Masters <jcm redhat com>
- To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list redhat com>
- Subject: Re: [PATCH] initrd-generic.img -> dracut.img
- Date: Wed, 09 Sep 2009 13:42:01 -0400
On Wed, 2009-09-09 at 19:38 +0200, Hans de Goede wrote:
> Hi,
>
> On 09/09/2009 05:14 PM, Bill Nottingham wrote:
> > Hans de Goede (hdegoede redhat com) said:
> >> We're moving back to %post generation of dracut initrd's due to
> >> GPL concerns about shipping pre build initrd's. This means the initrd
> >> will no longer be truely generic. To reflect this and make clear it is
> >> not an mkinitrd initrd, the name was changes to simply dracut.img.
> >
> > Even with regeneration in %post, it can still be generic, yes?
> >
>
> Yes and it will be, but dracut was split in dracut and dracut-network,
> and the normal generated initrd will be able to boot anything except
> for things like iscsi FCoE or / on nfs, that requires having dracut-network
> installed when the initrd is generated, so it is less generic then it
> was, but still may more generic then mkinitrd generated initrd's
> (this saves dragging in quite a few deps, as we now need dracut
> runtime, and also is a nice safe on the initrd image size)
We still get two images generated, right? Or is it now just one larger
initrd that is also "generic"?
Jon.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]