From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] Makefile: check rootfs overlays with BR2_ROOTFS_MERGED_USR enabled
Date: Mon, 7 May 2018 09:13:12 +0200 [thread overview]
Message-ID: <20180507091312.4848b555@windsurf> (raw)
In-Reply-To: <20180506213116.25084-4-casantos@datacom.ind.br>
Hello,
On Sun, 6 May 2018 18:31:15 -0300, Carlos Santos wrote:
> Fix the problem by adding a step in target-finalize that checks each
> overlay, using the same criteria used in skeleton-custom.mk.
>
> Add a paragraph to the documentation clarifying that rootfs overlays
> should not contain /bin, /lib or /sbin.
Same comment here: I'm sure plenty of people want to add some stuff to
their filesystem (scripts, etc.) that might need to be in /bin or /sbin
(/lib is less likely).
So I'm not a big fan of this additional constraint, just like I said
for the skeleton case.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-07 7:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 21:31 [Buildroot] [PATCH 0/4] Improve verification of custom rootfs skeletons and overlays Carlos Santos
2018-05-06 21:31 ` [Buildroot] [PATCH 1/4] skeleton-custom: use a script to check merged usr structure Carlos Santos
2018-05-06 21:31 ` [Buildroot] [PATCH 2/4] skeleton-custom: install /bin, /lib, and /sbin Carlos Santos
2018-05-07 7:08 ` Thomas Petazzoni
2018-05-07 11:16 ` Carlos Santos
2018-05-07 11:28 ` Thomas Petazzoni
2018-05-06 21:31 ` [Buildroot] [PATCH 3/4] Makefile: check rootfs overlays with BR2_ROOTFS_MERGED_USR enabled Carlos Santos
2018-05-07 7:13 ` Thomas Petazzoni [this message]
2018-05-06 21:31 ` [Buildroot] [PATCH 4/4] system: allow selecting merged /usr along with custom rootfs skeleton Carlos Santos
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=20180507091312.4848b555@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.