mail archive of the rauc mailing list
 help / color / mirror / Atom feed
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: Wed, 16 Jun 2021 08:45:36 -0400	[thread overview]
Message-ID: <CAFZh4h9cq39BLYfDhGz3L_ep0MYmoUqx1VcRSkxyE8-sm06JpQ@mail.gmail.com> (raw)
In-Reply-To: <d05ba658a829c9419956d840bb3b7099db1b169d.camel@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 2089 bytes --]

On Wed, Jun 16, 2021 at 1:06 AM Enrico Jörns <ejo@pengutronix.de> wrote:

> Hi Brian,
>
> Am Dienstag, dem 15.06.2021 um 17:32 -0400 schrieb Brian Hutchinson:
> > Ok, I think I figured out my problems.  Appears that I was using busybox
> > version of tar so I switched to the real thing (GNU Tar) and that fixed
> one
> > problem then I ran into a mkfs.vfat problem and I added dosfstools to my
> image
> > and that took care of that so now my bundle is updating correctly now
> ... so
> > sorry for the noise!
>
> glad you solved it!
>
> You could actually use busybox tar, too.  But then you need to make sure
> to have
> enabled format autodetection and the required compression algorithm, see:
>
> https://rauc.readthedocs.io/en/latest/integration.html#required-target-tools
>
> About your original questions:
>
> > So I should use "parent" to tie both kernel and appfs slots to the
> rootfs?
>
> Your system.conf (and parent relations) looked good from what I saw.
>
> > And for now, the rootfs is r/w on a ext4 filesystem, but in the future
> it will
> > be a squashfs.  So once that happens would 'type=ext4' then change to
> > 'type=raw'?
>
> Yes, 'raw' will be fine for squashfs as there is an explicit handler
> available
> for it. The 'raw' type ensures RAUC does not think it could mount the
> bundle for
> writing.
>
> 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.

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?

Thanks again!

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 2890 bytes --]

  reply	other threads:[~2021-06-16 12:45 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 [this message]
2021-06-17 10:20             ` Enrico Jörns
2021-06-17 12:42               ` Brian Hutchinson

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=CAFZh4h9cq39BLYfDhGz3L_ep0MYmoUqx1VcRSkxyE8-sm06JpQ@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