public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
To: isar-users <isar-users@googlegroups.com>,
	"Moessbauer,
	Felix (T RDA IOT SES-DE)" <felix.moessbauer@siemens.com>,
	"Kiszka, Jan (CT RDA IOT SES-DE)" <jan.kiszka@siemens.com>
Subject: Systemd first boot with rw rootfs
Date: Tue, 29 Nov 2022 10:50:57 +0100	[thread overview]
Message-ID: <d9328d30-351f-2cee-faf8-80e405847ed9@siemens.com> (raw)

Hi all,


currently we trigger a first boot by removing the machine-id from the
root file system[1]. In case of a writable root filesystem systemd will 
enable all units in /usr/lib/systemd/system with the vendor preset 
enable. This will also enable units in /usr/lib/systemd/system which are 
disable during the installation like ssh.socket[2].

This will not happen in a Debian installation as first boot is the 
installation boot as defined by:
"For normal operating system installations, where a custom image is 
created for a specific machine, /etc/machine-id should be populated 
during installation."[3]


If a first boot is not detected, e.g. by using an empty /etc/machine-id, 
the units are started as defined during the installation [4].

Another possibility is to mask the units during the the installation.

[1]: 
https://github.com/ilbers/isar/blob/49854b625a6b0dc9339a33c3b4d78b2ce418b377/meta/classes/image-postproc-extension.bbclass#L57
[2]: https://gitlab.com/cip-project/cip-core/isar-cip-core/-/issues/48
[3]: 
https://manpages.debian.org/bullseye/systemd/machine-id.5.en.html#INITIALIZATION
[4]: 
https://manpages.debian.org/bullseye/systemd/machine-id.5.en.html#FIRST_BOOT_SEMANTICS
-- 


With best regards,
Quirin Gylstorff

Siemens AG
Technology



             reply	other threads:[~2022-11-29  9:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29  9:50 Gylstorff Quirin [this message]
2022-11-29 10:46 ` [RFC] image-postproc-extension: Configurable systemd first boot Quirin Gylstorff
2023-08-04 11:07   ` Gylstorff Quirin
2023-08-04 11:33     ` Michael Adler

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=d9328d30-351f-2cee-faf8-80e405847ed9@siemens.com \
    --to=quirin.gylstorff@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@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