mail archive of the rauc mailing list
 help / color / mirror / Atom feed
* [RAUC] Bootloader change
@ 2022-02-28  8:54 Stefan Agner
  0 siblings, 0 replies; only message in thread
From: Stefan Agner @ 2022-02-28  8:54 UTC (permalink / raw)
  To: rauc

Hi List,

We are using rauc since several releases successfully in Home Assistant
OS. Thanks for this awesome piece of open source software!

With the upcoming release we plan to switch from Barebox to GRUB2 for
x86-64 platform. The main reason being GRUB2 also supporting aarch64,
and is generally more common in x86-64 world.

This requires a change to system.conf obviously. However, only with the
new upgrade the necessary tools and new system.conf are shipped. From
what I can tell there is no built-in mechanism for such a change in
rauc. Is there a best practice for such a change?

We use a A/B layout with a single boot loader. My current implementation
ships with two GRUB2 environment defaulting ORDER to "A B" and "B A"
respectively. I then use a hook to copy the right environment based on
RAUC_SLOT_BOOTNAME. With that the correct boot slot get booted on
upgrade. However, downgrading won't work as the upgraded rauc uses a
system.conf for grub now.

Instead of using the hook to handle the environment "manually", it would
be nice to have rauc handle it for the (other) boot loader present in
the update bundle. For that to work the update bundle would need some
mechanism to override system.conf. Of course this would need tooling to
be present for both boot loaders. Thoughts?


RAUC mailing list

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-02-28  8:55 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-28  8:54 [RAUC] Bootloader change Stefan Agner

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox