On Wed, 2015-09-02 at 13:24 -0300, Otavio Salvador wrote: > On Wed, Sep 2, 2015 at 1:19 PM, Otavio Salvador <[email protected]> > wrote: > > If there is any limitation please share the use case so we can > > understand the need for it. > > I found the live module and understood why you want to do this. > Instead you could use: > > - live as 99-live > - move finish for 99-rootfs-mount and split as a package > - put RCONFLICTS and RPROVIDES initramfs-module-rootfs-mount.
So you are suggesting that either "live" or "finish" do the final step of mounting the rootfs and switching to the rootfs? I actually wanted to have an initramfs which can be used in the live image *and* on a real disk and thus would need both, with the "live" module doing nothing unless booting from the live image. That's because the initramfs would also contain IMA initialization, and that is needed in both cases. Maintaining two different initramfs versions would be an alternative, but then the user and/or script which does the installation must be aware of the difference. It would also prevent embedding the initramfs inside the kernel (INITRAMFS_IMAGE_BUNDLE). But I'm fine with dropping these two patches for now and revisit the topic at a later time. I'll remove them from V2 of the patch series. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
