Timothée Ravier

Proposed flow (generic image for all devices). Slightly updated example for Raspberry Pi 4 (from https://github.com/coreos/bootupd/pull/935#issue-3093610029): ``` RUN dnf install -y uboot-images-armv8 # rpm -ql uboot-images-armv8 | grep rpi #...

Alternative using https://github.com/coreos/bootupd/pull/938 to specialize an image right now. - "Undo" `the generate-update-metadata` command - Place the `uboot-images-armv8` in `/usr/lib/efi/uboot-images-armv8/` - Re-run `bootupctl backend generate-update-metadata` Containerfile example: ``` FROM bootc-arm64-image...

Hum, this is indeed a case I don't remember thinking about (updating files at the root of the ESP) so I don't remember if the current code handles that properly....

I remember that we chose to do updates as the "directory under /EFI (i.e. /EFI/foobar)" level a while back as there could be other things at the root that we...

Answering questions from https://github.com/coreos/bootupd/pull/935#issuecomment-2991545407: > * Are those firmware files versioned? > * Are they always installed under the same name? > * Are it tied to a kernel version?...

From a side chat, adding a distinct option to be able to create generic images for all devices (option described in https://github.com/coreos/bootupd/issues/959#issuecomment-3151413045) is not currently desirable as it's unlikely we'll...

New suggested update logic: - Update each subfolder in `/EFI` atomically in a sequence (i.e. `/EFI/BOOT`, `/EFI/fedora`, etc.) - This is what we do right now - Then update other...

A lot of questions are unanswered here: - Is those firmware files versioned? - Is it always installed under the same name? - Is it tied to a kernel version?...

From what I understand, this re-implements #938 but on the side, differently, and does direct copies, etc. We need to have this integrated, not a duplicate of an existing path.

We had a chat a while back and this should now be possible with what we have in https://github.com/coreos/bootupd/pull/938.