public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: alexander.heinisch@siemens.com, cip-dev@lists.cip-project.org
Cc: quirin.gylstorff@siemens.com
Subject: Re: [isar-cip-core][PATCH 0/3] Added support for rootfs-overlay (for development).
Date: Tue, 18 Feb 2025 09:46:09 +0100	[thread overview]
Message-ID: <15b8d12e-46ce-47ce-be49-e22b2d8c16ea@siemens.com> (raw)
In-Reply-To: <20250217100024.42995-1-alexander.heinisch@siemens.com>

On 17.02.25 11:00, alexander.heinisch@siemens.com wrote:
> From: Alexander Heinisch <alexander.heinisch@siemens.com>
> 
> Updateable images based on isar-cip-core come with immutable rootfs
> out of the box. During development this oftentimes comes with the penalty
> of having to either rebuild images with additional files, packages aso.
> to accomplish development and debugging tasks or derive from the production
> image in a way that some fundamental features like verity, squashfs, swupdate, aso.
> are not part of such.
> 
> Both cases are far from optimal. With this patch series we want to share
> our attempt to streamline development by staying as close as possible to
> our production image by overlaying the squashfs or erofs based ro filesystem
> with an overlay. To make changes redundant accross reboots, we decided
> to use a persistent storage option in favour of a tmpfs based approach.
> (Although, technically there is no limitation on doing so)
> 
> Keep in mind, support for the root overlay is thought as a development
> feature! Thus, it is not thought for production, as it invalidates many
> of the properties we have from ro-filesystems. Also, keep in mind that
> changes on the overlay may partially hide updates or lead to "unexpected"
> results after applying updates.
> 
> Alexander Heinisch (3):
>   Removed "ro" option from read-only-rootfs's fstab.
>   Fix return value handling on filesystem check
>   Added support for rootfs-overlay.
> 
>  classes/read-only-rootfs.bbclass              |  2 +-
>  .../files/local-bottom.tmpl                   | 97 ++++++++++++++++---
>  .../initramfs-overlay-hook_0.3.bb             |  2 +-
>  3 files changed, 87 insertions(+), 14 deletions(-)
> 

Thanks, already applied patches 1 and 2. 3 is still under review and
will need at least some rewording.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center


  parent reply	other threads:[~2025-02-18  8:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 10:00 [isar-cip-core][PATCH 0/3] Added support for rootfs-overlay (for development) alexander.heinisch
2025-02-17 10:00 ` [isar-cip-core][PATCH 1/3] Removed "ro" option from read-only-rootfs's fstab alexander.heinisch
2025-02-17 10:00 ` [isar-cip-core][PATCH 2/3] Fix return value handling on filesystem check alexander.heinisch
2025-02-17 10:00 ` [isar-cip-core][PATCH 3/3] Added support for rootfs-overlay alexander.heinisch
2025-02-18  8:39   ` Quirin Gylstorff
2025-02-20 13:00     ` Heinisch, Alexander
2025-02-20 13:11       ` [cip-dev] " Nussel, Ludwig
2025-02-21 13:13         ` Heinisch, Alexander
2025-02-24 12:29       ` Quirin Gylstorff
2025-02-24 12:49         ` Heinisch, Alexander
2025-02-24 12:53           ` Jan Kiszka
2025-02-24 13:05             ` Heinisch, Alexander
2025-02-18  8:46 ` Jan Kiszka [this message]
2025-02-21 12:05   ` [isar-cip-core][PATCH 0/3] Added support for rootfs-overlay (for development) Heinisch, Alexander
     [not found] ` <1824F69F112B9158.31881@lists.cip-project.org>
2025-02-21 12:31   ` [cip-dev] [isar-cip-core][PATCH 1/3] Removed "ro" option from read-only-rootfs's fstab Heinisch, Alexander
2025-02-24  6:09     ` Jan Kiszka
2025-02-24 12:17       ` Quirin Gylstorff
2025-02-24 12:42         ` Jan Kiszka
2025-02-24 13:03           ` Heinisch, Alexander
2025-02-24 13:18             ` Jan Kiszka
2025-02-24 17:50               ` Heinisch, Alexander

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=15b8d12e-46ce-47ce-be49-e22b2d8c16ea@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=alexander.heinisch@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=quirin.gylstorff@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