On Tue, Feb 28, 2012 at 5:16 PM, Matthew McClintock <m...@freescale.com> wrote: > On Tue, Feb 28, 2012 at 9:48 AM, Paul Eggleton > <paul.eggle...@linux.intel.com> wrote: >> Hi all, >> >> For some boot configurations (e.g. kexecboot) having the kernel binary in the >> image is required. In OE Classic, task-boot used to always include the kernel >> binary in the image (via RRECOMMENDS, so it could be uninstalled). We don't >> currently have this in OE-Core and I was wondering what the new preferred way >> to have this done would be. >> >> Obviously we could go and add it to various images or even to task-core-boot >> again but I'm not sure that's ideal. Wanting the kernel in the image is >> really >> machine-specific (or to be precise, boot method specific); so I'm wondering >> if >> adding it to MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS for all machines likely to >> need it is the right thing to do? > > kexec and qemu/kvm could use this...
And I meant to finish by saying qemu/kvm can also use a rootfs in a rootfs... -M _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
