[kirkstone] "overlayfs-etc: add option to skip creation of mount dirs" backport

[kirkstone] "overlayfs-etc: add option to skip creation of mount dirs" backport

[Sébastien RAILLET]

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

Re: [kirkstone] "overlayfs-etc: add option to skip creation of mount dirs" backport

[Steve Sakoman]

On Mon, Oct 21, 2024 at 7:28 AM Sébastien RAILLET
<sebastien.raillet@gmail.com> wrote:
>
> 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.

Since this is a simple cherry-pick there is no need to send a patch,
the above request is fine.

Thanks!

Steve

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