From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: michael.opdenacker@rootcommit.com, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Simple solution to create a non-root partition image?
Date: Mon, 4 May 2026 15:08:36 +0200 [thread overview]
Message-ID: <cfb57d23-982a-4dd8-bc24-ff36904ec2ba@rootcommit.com> (raw)
In-Reply-To: <fe2c7d25-c2dd-47ca-a08b-e0115c3648b4@cherry.de>
Hi Quentin,
Thanks a lot for the tip!
On 5/4/26 10:47 AM, Quentin Schulz wrote:
> Do you need to generate an image for that partition or can you simply
> have what will be part of that partition be generated along with the
> "root partition" image?
>
> As far as I remember, wic can split files/directories into a separate
> partition from the rootfs, so that would be an option that doesn't
> require hacking things around.
Interesting! Unfortunately, I'm not using Wic but Toradex Easy Installer
on this project. Therefore I do need to generate a partition image
beforehand.
Thanks anyway! I good to know for another time.
Cheers
Michael.--
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com
next prev parent reply other threads:[~2026-05-04 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 20:40 Simple solution to create a non-root partition image? Michael Opdenacker
2026-05-04 8:47 ` [yocto] " Quentin Schulz
2026-05-04 13:08 ` Michael Opdenacker [this message]
2026-05-04 13:15 ` Quentin Schulz
2026-05-04 13:39 ` Cleiton Bueno
2026-05-04 13:55 ` Michael Opdenacker
2026-05-14 16:45 ` Michael Opdenacker
[not found] ` <684BE1E8-500C-4169-B5AF-C72E064F28E8@siliconbladeconsultants.com>
2026-05-04 13:27 ` Michael Opdenacker
2026-05-04 14:05 ` Francesco Cervigni
2026-05-14 16:27 ` Michael Opdenacker
2026-05-04 17:58 ` Francesco Valla
2026-05-06 9:44 ` Felix Mellmann
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=cfb57d23-982a-4dd8-bc24-ff36904ec2ba@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=quentin.schulz@cherry.de \
--cc=yocto@lists.yoctoproject.org \
/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