Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Sébastien RAILLET" <sebastien.raillet@gmail.com>
To: "Steve Sakoman" <steve@sakoman.com>,
	"openembedded-core" <openembedded-core@lists.openembedded.org>
Subject: [kirkstone] "overlayfs-etc: add option to skip creation of mount dirs" backport
Date: Mon, 21 Oct 2024 16:39:28 +0200	[thread overview]
Message-ID: <D51K87UE3UQ8.W74RI71RDRD@gmail.com> (raw)

Hello,

I would like to discuss the possibility of backporting commit
3d433d8559467d255bd19af2d0999c65ea24a48d [1] into the kirkstone
branch.

Currently, on the kirkstone branch, combining overlayfs-etc and
read-only-rootfs in IMAGE_FEATURES results in the root filesystem
being mounted as read-write during the startup phase. This behavior
may not be what users expect when enabling read-only-rootfs in
IMAGE_FEATURES. By backporting this commit, users would have the
option to disable this behavior if needed.

The commit I mentioned is conservative, as it preserves the current
behavior by default.

For your information, I have followed the Yocto contribution guide on
how to request a backport in a stable branch. However, if a patch is
preferred, I would be happy to propose one.

Thanks,
Sébastien

[1]: https://git.openembedded.org/openembedded-core/commit/?id=3d433d8559467d255bd19af2d0999c65ea24a48d


             reply	other threads:[~2024-10-21 14:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 14:39 Sébastien RAILLET [this message]
     [not found] <D51JZNT0Z0V4.2JRO6YCG6DMLR@gmail.com>
2024-10-21 14:41 ` [kirkstone] "overlayfs-etc: add option to skip creation of mount dirs" backport Steve Sakoman

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=D51K87UE3UQ8.W74RI71RDRD@gmail.com \
    --to=sebastien.raillet@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=steve@sakoman.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