From: Enrico Joerns <ejo@pengutronix.de>
To: Abhishek Kumar Rai <abhishekr@eximiusdesign.com>
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] Query regarding rauc
Date: Tue, 4 Dec 2018 12:24:18 +0100 [thread overview]
Message-ID: <454fb88a-2909-acfc-5c63-e139d5fccb34@pengutronix.de> (raw)
In-Reply-To: <CALYWmf89_tzz06wj=1GHv5tDU+ojCkn5WmyLYm5oh3BNsCuaVA@mail.gmail.com>
Hi Abhishek,
On 12/4/18 12:12 PM, Abhishek Kumar Rai wrote:
> Hi Team,
>
>
> To achieve a specific requirement for us the "rauc install" command won't work i.e due to a configuration that we have the rauc install would fail. Though we would still like to go ahead and flashload to that partition. We would like to know if the approach below is correct
>
>
> Our understanding of rauc install suggests that it does the following things:
>
> 1. Verify signature of the bundle
> 2. Run partition selection algorithm
> 3. Extract the tar balls from the bundle
> 4. Create new ext4 FS on the selected partition
> 5. Write appropriate tar ball to the partition
>
>
> Since "rauc install" would give us errors due to our configuration we plan to achieve this using the steps below:
>
> 1. Verify signature of the bundle (rauc info ...)
> 2. Partition selection algorithm (we would like to skip this)
> 3. Extract the tar balls from the bundle (rauc extract ..)
> 4. Create new ext4 FS on the selected partition + Write appropriate tar ball to the partition (rauc write-slot ... ....)
how do you trigger the custom installation? Do you use the full-custom RAUC install handler?
Extracting the tar's should not be required in all cases. With the full-custom handler you
will already have it mounted, otherwise you can simply mount the bundle after verification
as it is basically a squashfs.
For rauc write-slot you also rely on parts of the system.conf, but not in the fixed scheme.
If that is where your issue resides, you should be fine with that.
Could you give me a hint what forces you to do this kind of manual handling?
Maybe then we can think about a possible solution more targeted.
But basically it should work as described above, yes.
One thing will miss, depending on what you actually try to do.
The key for atomic updates is to deactivate the bootable slot you
write your image to before writing and set it as primary after successful writing.
You can achieve this behavior with
rauc status mark-bad <slot-to-update>
[ perform update ]
rauc status mark-active <slot-to-update>
Best regards, Enrico
--
Pengutronix e.K. | Enrico Jörns |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
RAUC mailing list
next prev parent reply other threads:[~2018-12-04 11:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 11:12 Abhishek Kumar Rai
2018-12-04 11:24 ` Enrico Joerns [this message]
2018-12-04 12:06 ` Abhishek Kumar Rai
2018-12-04 12:50 ` Enrico Joerns
2018-12-05 6:45 ` Abhishek Kumar Rai
2018-12-06 9:24 ` Abhishek Kumar Rai
2018-12-10 8:17 ` Enrico Joerns
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=454fb88a-2909-acfc-5c63-e139d5fccb34@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=abhishekr@eximiusdesign.com \
--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