From: Brian Hutchinson <b.hutchman@gmail.com>
To: "Jan Lübbe" <jlu@pengutronix.de>
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] Create bundles from command line outside of yocto?
Date: Tue, 15 Jun 2021 00:17:37 -0400 [thread overview]
Message-ID: <CAFZh4h8STJMD+KkzOXKMddrq_sZ9hq6QH7CFcOm+VZio+gJ5GA@mail.gmail.com> (raw)
In-Reply-To: <592943eab0a32f9e1b892960e84e0524a6f56c14.camel@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1663 bytes --]
Hi Jan,
So using your manifest example and my partition scheme from earlier ...
RAUC A slots:
/dev/mmcblk2gp0p1 (kernel/dtb)
/dev/mmcblk2gp0p2 (rootfs)
/dev/mmcblk2p1 (appfs)
RAUC B slots:
/dev/mmcblk2gp1p1 (kernel/dtb)
/dev/mmcblk2gp1p2 (rootfs)
/dev/mmcblk2p2 (appfs)
On Tue, May 25, 2021 at 2:56 AM Jan Lübbe <jlu@pengutronix.de> wrote:
>
> So your manifest might look like:
> [update]
> compatible=rauc-example
> version=2021.05-1
>
> [bundle]
> format=verity
>
> [image.kernel]
> filename=kernel.img
>
> [image.rootfs]
> filename=rootfs.tar
>
> [image.appfs]
> filename=appfs.tar
>
>
> Best regards,
> Jan
>
>
>
My system.conf (using my example partition layout for earlier email) file
would look something like:
[system]
compatible=rauc-example
bootloader=uboot
[keyring]
path=/etc/rauc/ca.cert.pem
[slot.kernel.0]
device=/dev/mmcblk2gp0p1
type=vfat
parent=rootfs.0
[slot.kernel.1]
device=/dev/mmcblk2gp1p1
type=vfat
parent=rootfs.1
[slot.rootfs.0]
device=/dev/mmcblk2gp0p2
type=ext4
bootname=A
[slot.rootfs.1]
device=/dev/mmcblk2gp1p2
type=ext4
bootname=B
[slot.appfs.0]
device=/dev/mmcblk2p1
type=ext4
parent=rootfs.0
[slot.appfs.1]
device=/dev/mmcblk2p2
type=ext4
parent=rootfs.1
So I should use "parent" to tie both kernel and appfs slots to the rootfs?
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'?
Just trying to make sure I understand how to make manifest and system.conf
map together for making bundles etc.
Regards,
Brian
[-- Attachment #1.2: Type: text/html, Size: 4418 bytes --]
[-- Attachment #2: Type: text/plain, Size: 66 bytes --]
_______________________________________________
RAUC mailing list
next prev parent reply other threads:[~2021-06-15 4:17 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 [this message]
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
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=CAFZh4h8STJMD+KkzOXKMddrq_sZ9hq6QH7CFcOm+VZio+gJ5GA@mail.gmail.com \
--to=b.hutchman@gmail.com \
--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