From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"Schild, Henning" <henning.schild@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH v2 2/4] meta-isar: add example how to split rootfs across partitions
Date: Thu, 12 May 2022 11:37:33 +0000 [thread overview]
Message-ID: <AM9PR10MB4869815CCAD5592A434921B889CB9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <0f7ae0d235a81234a8c4e7e236f9e5bc6a6aaeae.camel@siemens.com>
> From: Bezdeka, Florian (T CED SES-DE) <florian.bezdeka@siemens.com>
> Sent: Thursday, May 12, 2022 12:55 PM
> To: isar-users@googlegroups.com; Moessbauer, Felix (T CED SES-DE)
> <felix.moessbauer@siemens.com>
> Cc: Kiszka, Jan (T CED) <jan.kiszka@siemens.com>; Schild, Henning (T CED SES-
> DE) <henning.schild@siemens.com>
> Subject: Re: [PATCH v2 2/4] meta-isar: add example how to split rootfs across
> partitions
>
> On Thu, 2022-05-12 at 11:45 +0200, Felix Moessbauer wrote:
> > +# put home last to support auto-expand of this partition part /home
> > +--ondisk sda --source rootfs --rootfs-dir=${IMAGE_ROOTFS}/home
> > +--fstype=ext4 --mkfs-extraopts "-T default" --label platform --align
> > +1024 --exclude-path boot home
>
> "home" is part of the --exclude-path for /home? Is that really right?
Good catch. On /home, we don't need the exclude path.
Will send a v3.
>
> How are the paths given in --exclude-path interpreted when --rootfs-dir is given?
> Relative to --rotfs-dir? Maybe we can simply remove --exclude-path?
>
The exclude paths are relative to the --rootfs-dir. These have to be specified as relative dirs and if the path ends in '/', that means the path is created but all child paths are excluded.
A common mistake I saw in downstream layers is that --rootfs-dir was specified multiple times, providing one path each.
This just excludes a single path (ATM I don't even know which one) but copies all others into the partition.
Felix
next prev parent reply other threads:[~2022-05-12 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 9:45 [PATCH v2 0/4] wic: Update to the latest revision Felix Moessbauer
2022-05-12 9:45 ` [PATCH v2 1/4] " Felix Moessbauer
2022-05-12 9:45 ` [PATCH v2 2/4] meta-isar: add example how to split rootfs across partitions Felix Moessbauer
2022-05-12 10:54 ` Bezdeka, Florian
2022-05-12 11:37 ` Moessbauer, Felix [this message]
2022-05-12 9:45 ` [PATCH v2 3/4] use multipart image for qemuamd64-bookworm target Felix Moessbauer
2022-05-12 9:45 ` [PATCH v2 4/4] ci: test partition layout of splitted-rootfs image Felix Moessbauer
2022-05-12 10:16 ` [PATCH v2 0/4] wic: Update to the latest revision Henning Schild
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=AM9PR10MB4869815CCAD5592A434921B889CB9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
--to=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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