From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <pierre-loup.gosse@smile.fr>,
"Peter Bergin" <peter@berginkonsult.se>,
"Alexander Kanavin" <alex.kanavin@gmail.com>
Cc: <yoann.congal@smile.fr>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 1/1] wic: extra partition plugin
Date: Thu, 25 Sep 2025 17:20:21 +0200 [thread overview]
Message-ID: <DD1ZE7G2YIZ9.L1KYBCLSDBU@bootlin.com> (raw)
In-Reply-To: <CAHT-cZtr-en6sc7JaPfN9s7BFbwiV+iGrv9rQDKjr8rcXSpWFA@mail.gmail.com>
On Thu Sep 25, 2025 at 2:43 PM CEST, Pierre-loup GOSSE via lists.openembedded.org wrote:
>>
>> in the past I have used to rootfs plugin with '--exclude-path' [1] and
>> '--change-directory' [2] assuming that I have isolated all files going in
>> to the extra partition in to one directory of rootfs.
>
> This is a solution when files are installed in the rootfs but need to be
> split across multiple partitions.
>
> However, some files aren't or shouldn’t be in the rootfs. For instance,
> I’ve worked on boards requiring a dedicated VFAT partition just for the
> U-Boot script. Other use cases include keeping business software separate
> from the rootfs, especially when they are installed and updated
> independently (with a SWU package).
> Pierre-Loup,
Why not install all the files in IMAGE_ROOTFS in a single image, then do the
filtering in the WKS?
What I do is:
part rootfs --source rootfs --fstype=ext4 --exclude-path=data/ ...
part data --source rootfs --rootfs-dir=${IMAGE_ROOTFS}/data ...
In this case the rootfs partition will not include the files in /data, and the
data partition will include them.
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-09-25 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 7:22 [PATCH v2 0/1] wic: extra partition plugin pierre-loup.gosse
2025-09-25 7:22 ` [PATCH v2 1/1] " pierre-loup.gosse
2025-09-25 7:55 ` Yoann Congal
2025-09-25 8:22 ` [OE-core] " Alexander Kanavin
2025-09-25 9:13 ` Pierre-loup GOSSE
2025-09-25 10:58 ` Peter Bergin
2025-09-25 12:43 ` Pierre-loup GOSSE
2025-09-25 15:20 ` Antonin Godard [this message]
2025-09-26 8:30 ` Pierre-loup GOSSE
2025-09-26 7:07 ` [OE-core] [PATCH v2 0/1] " Mathieu Dubois-Briand
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=DD1ZE7G2YIZ9.L1KYBCLSDBU@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter@berginkonsult.se \
--cc=pierre-loup.gosse@smile.fr \
--cc=yoann.congal@smile.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.