[OE-core] Generating UBIs containing multiple volumes
jon.szymaniak at gmail.com
Fri Feb 8 23:24:52 UTC 2013
I see that the image_types.bbclass's IMAGE_CMD_ubi() does the following:
1) Creates a single-volume ubinize.cfg on the fly
2) Runs mkfs.ubifs to create the UBIFS image
3) Run ubinize to create a UBI image
However, I'm currently using a two-volume image: one volume for the
rootfs, and one for "user config" as shown in the below ubinize.cfg.
I'm considering making some changes to image_types.bbclass to support
this and was hoping I could get some feedback and advice.
I'd planned to stage my config.ubifs with some sane default files via
a recipe (e.g., an ubinize invocation in a do_compile). It feels like
it might be "bad practice" to have a recipe install config.ubifs
(perhaps a name with a timestamp and then a shorthand symlink, as done
with existing image files) into $(DEPLOY_DIR_IMAGE}. Any
Where would be an appropriate place to keep a custom ubinize.cfg? In
my case, it should always remain the same for my MACHINE. However, I'm
not certain if this would be always be the case for other folks...
More information about the Openembedded-core