On Fri, Sep 05, 2014 at 08:34:56PM +0200, Tobias Hunger wrote:
> I see that secure boot wants one file and that you will need to merge kernel
> and initrd into one. But you will need the meta data to link the kernel/initrd
> combo to a combination of root-subvolume and usr-subvolume. IIRC chromeos
> also has that and stores that meta-data in non-volatile memory accessible to
> the BIOS.

I've been wanting the ability to take a kernel image and add/replace an
initrd to the end of it after it is built and remain a single "image"
that you can then sign/copy/whatever.  You can't do that today due to
some static variables in the initrd image.  I started to hack it up a
while ago, need to carve up some time to revisit that to fix this issue,
which should make some of this easier.

sorry for the digression,

greg k-h
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to