From: Stefan Agner <stefan@agner.ch>
To: rauc@pengutronix.de
Subject: [RAUC] Bootloader change
Date: Mon, 28 Feb 2022 09:54:49 +0100 [thread overview]
Message-ID: <0ca1f5b159c309fced97a4ff34b371db@agner.ch> (raw)
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?
--
Stefan
_______________________________________________
RAUC mailing list
reply other threads:[~2022-02-28 8:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0ca1f5b159c309fced97a4ff34b371db@agner.ch \
--to=stefan@agner.ch \
--cc=rauc@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox