Including the kernel in the image
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?
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Op 28 feb. 2012, om 16:48 heeft Paul Eggleton het volgende geschreven:
Quoted 7 lines
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.
As long as the solution doesn't end up with the FILES_kernel = "" crap we had in OE-classic.
Quoted 5 lines
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_RRECOMMENDSfor all machines likely to need it is the right thing to do?
I think so, maybe that will get people motivated to make BAD_RECOMMENDATIONS work with all package formats :)
regards,
Koen
Quoted 8 lines · Paul Eggleton
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.
Quoted 5 lines
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_RRECOMMENDSfor all machines likely to need it is the right thing to do?
kexec and qemu/kvm could use this...
-M
Quoted 10 lines · Matthew McClintock
Quoted 8 lines · Paul Eggleton
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.
Quoted 7 lines
Quoted 5 lines
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_RRECOMMENDSfor 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