From: Brian Hutchinson via RAUC <rauc@pengutronix.de>
To: "Jan Lübbe" <jlu@pengutronix.de>
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] Is it possible to change the [system]compatible= string after it has already been set/flashed?
Date: Tue, 14 Jan 2025 10:38:19 -0500 [thread overview]
Message-ID: <CAFZh4h-sA4hoPUobFyV3z9+G0JJYLCOQgkCJQpPA0dbRZKVN7A@mail.gmail.com> (raw)
In-Reply-To: <dce5a82b6f1cd9a5b15908c3af216b83f88ca864.camel@pengutronix.de>
On Mon, Dec 9, 2024 at 3:43 AM Jan Lübbe <jlu@pengutronix.de> wrote:
>
> Hi again,
>
> On Thu, 2024-12-05 at 22:38 -0500, Brian Hutchinson via RAUC wrote:
> > This almost feels like the intermediate update that's necessary with
> > changing rauc versions ...
>
> Enrico pointed me to this part.
>
> Updating RAUC versions normally does *not* require an intermediate
> update. An intermediate update is only needed if you explicitly create
> bundles which use new features:
> https://rauc.readthedocs.io/en/latest/basic.html#forward-and-backward-compatibility
Thanks!
I should probably start another thread, but now I'm running into a
chicken & egg problem.
I need to add downgrade protection due to newer hardware and I
discovered pre-install handler doesn't have access to bundle version
(RAUC_MF_VERSION), only a hook has that environment variable. Well,
if I create a hook that can compare bundle version to current version
to do some hardware checks ... that hook won't be in older bundles, so
wondering how pre-install handler (which lives in the current version
file system) can figure out the bundle version attempting to be
installed if it can't see RAUC_MF_VERSION to implement downgrade
protection if that makes any sense.
Regards,
Brian
next prev parent reply other threads:[~2025-01-14 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 3:38 Brian Hutchinson via RAUC
2024-12-06 9:25 ` Jan Lübbe via RAUC
2024-12-09 8:43 ` Jan Lübbe via RAUC
2025-01-14 15:38 ` Brian Hutchinson via RAUC [this message]
2025-01-14 15:52 ` Jan Lübbe via RAUC
2025-01-14 16:04 ` Brian Hutchinson via RAUC
2025-01-14 20:46 ` Brian Hutchinson via RAUC
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=CAFZh4h-sA4hoPUobFyV3z9+G0JJYLCOQgkCJQpPA0dbRZKVN7A@mail.gmail.com \
--to=rauc@pengutronix.de \
--cc=b.hutchman@gmail.com \
--cc=jlu@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