From: "alexander.heinisch via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: Alexander Heinisch <alexander.heinisch@siemens.com>
Subject: [PATCH 0/1] classes/image-postproc: chroot before postprocessing /etc/machine-id
Date: Fri, 27 Jun 2025 11:47:55 +0200 [thread overview]
Message-ID: <20250627094756.151803-1-alexander.heinisch@siemens.com> (raw)
From: Alexander Heinisch <alexander.heinisch@siemens.com>
We were experimenting with /etc-overlay removal
ending up with systemd detecting first-boot conditions due to
unitinitialized /etc/machine-id.
To circumvent this on ro etc, we put a link on /etc/machine-id to
a mutable location instead. Without chroot writing to /etc/machine-id
linked to e.g. /var/local/machine-id resolves to the hosts /var partition
instead of the file in ${IMAGE_ROOTFS}.
Apart from that overriding the machine-id-commit service was needed
to make this setup work properly. Not sure if a patch for that is
desired as well?
Alexander Heinisch (1):
classes/image-postproc: chroot before postprocessing /etc/machine-id
meta/classes/image-postproc-extension.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.39.5
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20250627094756.151803-1-alexander.heinisch%40siemens.com.
next reply other threads:[~2025-06-27 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 9:47 alexander.heinisch via isar-users [this message]
2025-06-27 9:47 ` [PATCH 1/1] " alexander.heinisch via isar-users
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=20250627094756.151803-1-alexander.heinisch@siemens.com \
--to=isar-users@googlegroups.com \
--cc=alexander.heinisch@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