On Thu, Sep 3, 2015 at 3:29 AM, Patrick Ohly <patrick.o...@intel.com> wrote: > On Wed, 2015-09-02 at 13:24 -0300, Otavio Salvador wrote: >> On Wed, Sep 2, 2015 at 1:19 PM, Otavio Salvador <ota...@ossystems.com.br> >> 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).
I see your point and it is a valid one. However in this case, the finish change needs to be reworked to avoid too much indenting change for no reason, the finish_enabled function can be used for this. -- 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 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
