Now a single unified kernel image is built using a new CoreOS
specific functionality added in the efibootguard UKI stub to
automatically insert root=PARTLABEL=rootfs0 (or rootfs1) in the
kernel command line
BREAKING CHANGE: coreos-image-uki.bbclass now only generate a
single kernel image named kernel-${MACHINE}.efi
Now we use fw0, fw1, efi, ebg0, ebg1, rootfs0 and rootfs1 partition
name.
BREAKING CHANGE: bootX partition are now named ebgX
BREAKING CHANGE: platformX partition are now named rootfsX
sw-description files
The COREOS_SWUPDATE_EXTENDS_FOR and COREOS_IMAGE_SWUPDATE_EXTRACLASSES
variable can now be used to configure the coreos-image-swupdate to
dynamically extends some part of the sw-description by calling some
python function
This also change the beaglebone target to use a GPT
partitioned disk
BREAKING CHANGE: .swu image generated can not be used on old
device, thus the device has to be reflashed.
BREAKING CHANGE: Support for MBR formatted disk is removed, as
it was only used for Beaglebone
COREOS_EFI_SECUREBOOT_KEYDIR_HASH was intended to store a hash
of each file present in build/key in order to discard the sstate
cache on key changes. But this variables was wrongly always empty
due to a wrong check in a loop.
This introduce a new coreos-emmc-flasher-beaglebone
recipe that create a SWU file that can be used to
create the partition in the internal emmc of a beaglebone
and flash both u-boot and efibootguard.
Support for create efibootguard configuration partition
and flashing kernel and rootfs is not included.
Merge in ICO/coreos from chore/efibootguard-handling to master
* commit 'e02d4b95f8e257d55f70b1dfbf6435ddd564b09e':
chore(efibootguard): better handling of efibootguard related variables
Default value related to efibootguard are not set inside the distro
and MACHINE that use coreos-image and doesn't define EFI as a
MACHINE_FEATURE doesn't get the efibootguard-tools package.
We can build container with non-container machine with
coreos-container-image classes so having a MACHINEOVERRIDES
for container machines only is misleading
--fixed-size produce a partition of the right size but doesn't expand
the filesystem. Instead we use --size --extra-space and
--overhead-factor to have a fixed size partition and fixed size
filesystem
Checking for COREOS_EFI_SECUREBOOT_INSTALL_PUBKEY_IN_EFIDIR
was not done properly resulting of the key always being
installed inside the EFI partition.
We are now using efibootguard to provide a A/B boot path for
the kernel and the rootfs.
This commit remove some change for systemd/systemd-boot that are
not needed anymore and rework how we set the command line, as we
will need to have the command line argument of the kernel both
inside do_image_wic and in a future do_image_swu
Samuel Dolt