From: david.kauschke.ext@zeiss.com
To: cip-dev@lists.cip-project.org
Subject: Re: [isar-cip-core][QUESTION] initramfs-overlay-hook: tmpFS for overlay storage
Date: Mon, 08 Sep 2025 00:49:54 -0700 [thread overview]
Message-ID: <1657.1757317794982820595@lists.cip-project.org> (raw)
In-Reply-To: <b844bdcbffd7352de6dc18e9a3ee1368fcd26177.camel@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
Thank you for your help Alexander, Jan and Quirin!
Topic can be closed.
After discussion and your informations, I plan to switch to this approach:
1) Use /var as the overlay storage path and encrypt the /var partition.
2) Symlink /home to /var/home, so the only persistent partition is /var (following the move-homedir-var recipe).
This way, there’s no major divergence from the upstream CIP layer, while the encrypted /var partition addresses the security concerns.
David
[-- Attachment #2: Type: text/html, Size: 658 bytes --]
prev parent reply other threads:[~2025-09-08 7:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 5:53 [isar-cip-core][QUESTION] initramfs-overlay-hook: tmpFS for overlay storage d.kauschke154
2025-08-24 10:16 ` Jan Kiszka
2025-08-28 10:48 ` Quirin Gylstorff
2025-09-01 8:13 ` [cip-dev] " Heinisch, Alexander
2025-09-08 7:49 ` david.kauschke.ext [this message]
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=1657.1757317794982820595@lists.cip-project.org \
--to=david.kauschke.ext@zeiss.com \
--cc=cip-dev@lists.cip-project.org \
/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