From: Michael Adler <michael.adler@siemens.com>
To: Gylstorff Quirin <quirin.gylstorff@siemens.com>
Cc: isar-users@googlegroups.com, Uladzimir Bely <ubely@ilbers.de>,
felix.moessbauer@siemens.com, jan.kiszka@siemens.com
Subject: Re: [RFC] image-postproc-extension: Configurable systemd first boot
Date: Fri, 4 Aug 2023 13:33:47 +0200 [thread overview]
Message-ID: <oilx4y7utqqt2qgvm44rhrln424q5euxlyv2cunv6k6ult5upp@5pzgy6tcknhm> (raw)
In-Reply-To: <2466d455-d5e0-780c-dc2b-ee28a2594df8@siemens.com>
Hi Quirin,
> In case of a writable root file system 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.
I've stumbled upon the same problem. It took me quite a while to figure out
why systemd services which where explicitly *not* enabled at build time where
somehow still enabled and started on system boot. I did not suspect systemd to
be the culprit! This behavior is unexpected and irritating to say the least.
> The Default implementation will not trigger the first boot condition.
That makes sense. After all, we are fully in control of the root filesystem at
build time. I don't want to deal with surprises at boot time.
Kind Regards,
Michael
--
Michael Adler
Siemens AG
Technology
Connectivity & Edge
Smart Embedded Systems
T CED SES-DE
Otto-Hahn-Ring 6
81739 Munich, Germany
Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim Hagemann
Snabe; Managing Board: Roland Busch, Chairman, President and Chief Executive
Officer; Cedrik Neike, Matthias Rebellius, Ralf P. Thomas, Judith Wiese;
Registered offices: Berlin and Munich, Germany; Commercial registries:
Berlin-Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322
prev parent reply other threads:[~2023-08-04 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 9:50 Systemd first boot with rw rootfs Gylstorff Quirin
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 [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=oilx4y7utqqt2qgvm44rhrln424q5euxlyv2cunv6k6ult5upp@5pzgy6tcknhm \
--to=michael.adler@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.com \
--cc=ubely@ilbers.de \
/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