[OE-core] [PATCH 00/10] enhancing images, booting and runqemu

[Otavio Salvador]

On Wed, Sep 2, 2015 at 12:48 PM, Patrick Ohly <patrick.ohly at intel.com> wrote:
> I've spent some time lately on building custom full-disk images with a
> custom initramfs based on the initramfs-framework. The ultimate goal
> is to initialize IMA in a initramfs-framework module.
>
> As part of that work, I enhanced runqemu such that it can boot
> full-disk images more easily, made those images more versatile (no
> more hard-coded root=/dev/sda2), and solved a kernel panic that only
> seems to appear under qemu (the /dev/console issue).
>
> Only a few patches are really important (because I'd probably not be
> able to achieve the same effect with setting variables elsewhere):
>    boot loader: support root=UUID
>    initramfs-framework: handle kernel parameters with . inside
>    initramfs-framework: add separate init_verbose log level parameter
>    initramfs-framework: support mounting rootfs in modules
>    runqemu: support full-disk images
>
> But I think the rest might also be relevant for others and thus
> worthwile including.
>
> Note that the mechanism for root=UUID is separated from actually
> making that default. Changing the default this late in the development
> cycle might be a bit risky, so I'd be fine with leaving out the last
> patch which changes the default. On the other hand, it solves one
> potential snag for users of these images, so it might be better to
> include it - your choice.

I would like to thank you to work on this. This extends the use of the
initramfs-framework as we wished since we designed it and it allows
for the removal of the live specific recipes for more metadata
polishment.

This is indeed a step on the right direction.

I provided some feedback; hope it helps.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750