Bug 8728 - wic: Allow to use custom bootloader configuration
Summary: wic: Allow to use custom bootloader configuration
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: deployment (show other bugs)
Version: 2.0
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.1 M1
Assignee: Mariano Lopez
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-11-26 00:52 UTC by Mariano Lopez
Modified: 2015-12-11 18:15 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mariano Lopez 2015-11-26 00:52:51 UTC
When wic creates an image the bootloader configuration is created based on options in the .wks file. If there is need for a very specific configuration, these options are not enough and the configuration file needs to be modified/replaced after the image is created. Examples of these specific needs would be multi-boot system or scripting.
Comment 1 Ed Bartosh 2015-11-26 16:10:44 UTC
I'd like to propose alternative solution for this problem - to prepare boot rootfs by bitbake and use wic source plugin to convert it into the partition.

you can see similar example in meta-selftest/recipes-test/images/wic-image-minimal.wks

This way bootloader configuration of any complexity could be handled easily.
There is one limitation of this approach - it works only with EFI booting. I hope it's not your case though.
Comment 2 Mariano Lopez 2015-12-01 18:02:18 UTC
For EFI is a good option to use a recipe to create the boot partition, however the requirements here is to have something that can also work with MBR. Hence the bug. I sent the patches to the ML.

http://lists.openembedded.org/pipermail/openembedded-core/2015-December/113581.html