mail archive of the meta-rauc mailing list
 help / color / mirror / Atom feed
From: "Enrico Jörns" <ejo@pengutronix.de>
To: BAUER Bernd <bernd.bauer@ses-imagotag.com>,
	"meta-rauc@pengutronix.de" <meta-rauc@pengutronix.de>
Subject: Re: [meta-rauc] How to generate update bundle: With genimage or with recipe?
Date: Tue, 22 Nov 2022 20:28:46 +0100	[thread overview]
Message-ID: <4f5a52f8963256cd00ae1439b7fddb2c7c2c78d3.camel@pengutronix.de> (raw)
In-Reply-To: <PR0P264MB3289337D2964EA2FCB209FDBD20A9@PR0P264MB3289.FRAP264.PROD.OUTLOOK.COM>

Hi Bernd,

Am Montag, dem 21.11.2022 um 12:20 +0000 schrieb BAUER Bernd:
> Hi!
> 
> I use genimage for image generation.
> This is an A/B system.
> The bootloader is u-boot and switching the root partitions already works.
> 
> Looks something like this...
> 8<------------------------------------
> 
> 8<------------------------------------
> 
> Now I want to create an update bundle for one of the system partitions with rauc.
> What is the best way to make the update bundle here?
> With a recipe and "inherit bundle"?

this is the recommended way with meta-rauc, yes.

Since you only need the root file system image, this should be very little effort to create a bundle
recipe. Just have a look at

https://github.com/rauc/meta-rauc/blob/master/recipes-core/bundles/core-bundle-minimal.bb 

> Or should I do it with genimage?

Generating bundles with genimage is possible, too (as e.g. PTXdist does this), but I do not see any
benefit here in this constellation.

> I did this with a recipe and used my rootfs recipe as base.

(Ok, so my above example should not even be needed ;) )

> Here I get an update bundle out, that is about 3GB big. This much too large.

How did you get a 3 GB image for you (< 512MiB?) rootfs? Thus the images in your deploy dir should
have the same size? Maybe you have configured a large free space (IMAGE_ROOTFS_SIZE,
IMAGE_ROOTFS_EXTRA_SPACE or IMAGE_OVERHEAD_FACTOR)?


Best regards

Enrico

> Greets Bernd
> 
> 

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Embedded Linux Consulting & Support        | https://www.pengutronix.de/ |
Steuerwalder Str. 21                       | Phone: +49-5121-206917-180  |
31137 Hildesheim, Germany                  | Fax:   +49-5121-206917-9    |




      reply	other threads:[~2022-11-22 19:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 12:20 BAUER Bernd
2022-11-22 19:28 ` Enrico Jörns [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=4f5a52f8963256cd00ae1439b7fddb2c7c2c78d3.camel@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=bernd.bauer@ses-imagotag.com \
    --cc=meta-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