From: Brian Hutchinson <b.hutchman@gmail.com>
To: "Enrico Jörns" <ejo@pengutronix.de>
Cc: rauc@pengutronix.de, "Jan Lübbe" <jlu@pengutronix.de>
Subject: Re: [RAUC] Create bundles from command line outside of yocto?
Date: Thu, 17 Jun 2021 08:42:09 -0400 [thread overview]
Message-ID: <CAFZh4h8T8kt1JsQ=nRRMsR-aBrS-qzdUpeB3MMJSc8h_tBsQqA@mail.gmail.com> (raw)
In-Reply-To: <15aea096a6b8e1a533d9d8069118889fb2dd5d81.camel@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]
Hi Enrico,
On Thu, Jun 17, 2021 at 6:20 AM Enrico Jörns <ejo@pengutronix.de> wrote:
> Hi Brian,
>
> Am Mittwoch, dem 16.06.2021 um 08:45 -0400 schrieb Brian Hutchinson:
> > > If you have a separate shared data partition, then I would recommend to
> > > configure RAUC to use this for its status file (which cannot be located
> > > inside
> > > the slot anymore when having "ro by design"):
> > >
> > > [system]
> > > ...
> > > statusfile=/path/to/datapart/rauc.status
> > >
> > > See https://rauc.readthedocs.io/en/latest/reference.html#statusfile
> > >
> >
> >
> > I'll check that out. I'm using u-boot so I "thought" all the status
> stuff was
> > being done with u-boot environment variables via fw_setenv/fw_printenv.
>
> u-boot is used for the partition/slot switching only.
> This is sufficient for basic functionality of of RAUC.
>
> In the status file we store some additional information, like when and how
> often
> a slot was updated, or which bundle version it is running.
> You get this for example when running "rauc status --detailed".
>
> > Was it my imagination or did RAUC populate my rootfs during the update
> faster
> > than when I just mount and manually untar my rootfs? How is it you guys
> are
> > faster?
>
> Sounds interesting, but I cannot tell because I don't know what you did to
> untar
> ;)
> But actually there is no magic. We simply call 'tar' to unpack. Maybe
> you've
> used a slower (de)compression algorithm when testing manually?
>
I bet it's because I'm in the habit of using xvf ... the 'v' is slowing it
down.
B
[-- Attachment #2: Type: text/html, Size: 2328 bytes --]
prev parent reply other threads:[~2021-06-17 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 2:54 Brian Hutchinson
2021-05-25 6:56 ` Jan Lübbe
2021-06-15 4:17 ` Brian Hutchinson
2021-06-15 19:07 ` Brian Hutchinson
2021-06-15 21:32 ` Brian Hutchinson
2021-06-16 5:06 ` Enrico Jörns
2021-06-16 12:45 ` Brian Hutchinson
2021-06-17 10:20 ` Enrico Jörns
2021-06-17 12:42 ` Brian Hutchinson [this message]
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='CAFZh4h8T8kt1JsQ=nRRMsR-aBrS-qzdUpeB3MMJSc8h_tBsQqA@mail.gmail.com' \
--to=b.hutchman@gmail.com \
--cc=ejo@pengutronix.de \
--cc=jlu@pengutronix.de \
--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