From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
"T. Schaffner" <tobias.schaffner@siemens.com>,
isar-users@googlegroups.com
Cc: quirin.gylstorff@siemens.com
Subject: Re: [PATCH 2/2] Warn if systemd-firstboot misses configurations
Date: Tue, 22 Nov 2022 11:24:53 +0100 [thread overview]
Message-ID: <892fe496354a967054e63a67fbba59268f372548.camel@siemens.com> (raw)
In-Reply-To: <08d391d5-cb8c-4a49-826d-51b69cd7ef07@ilbers.de>
On Tue, 2022-11-22 at 13:04 +0300, Anton Mikanovich wrote:
> 19.11.2022 21:20, T. Schaffner wrote
> > From: Tobias Schaffner <tobias.schaffner@siemens.com>
> >
> > systemd-firstboot checks the existence of different system configurations
> > like locale or hostname. Debian packages may trust that these configurations
> > are in the location that systemd-firstboot enforced.
> >
> > Warn the user in the image postproc step if systemd-firstboot misses any
> > configurations in the image.
> >
> > Signed-off-by: Tobias Schaffner <tobias.schaffner@siemens.com>
>
> If we have a warning here, do we really need to mask the service in p1?
> User should fix the reason but not hide it, and masking can be optional just
> in case there are no other ways.
I didn't have the time to review the patches in detail yet, so I might
be wrong. But: If systemd-firstboot is enabled (not masked) and we miss
one of the config settings that it checks the image won't boot up.
It will enter a interactive mode and ask you questions on how to
configure your system (locale, keyboard layout, ...). Especially for CI
and embedded systems that's a real issue.
So I guess the idea was to simply mask systemd-firstboot (we don't like
interactive mode) and warn the user that the system might not be fully
configured.
Tobias, please correct me if need to.
Florian
>
next prev parent reply other threads:[~2022-11-22 10:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 18:20 [PATCH 0/2] Mask systemd-firstboot T. Schaffner
2022-11-19 18:20 ` [PATCH 1/2] " T. Schaffner
2022-11-19 18:20 ` [PATCH 2/2] Warn if systemd-firstboot misses configurations T. Schaffner
2022-11-22 10:04 ` Anton Mikanovich
2022-11-22 10:24 ` Florian Bezdeka [this message]
2023-02-23 11:43 ` Uladzimir Bely
2023-02-24 11:36 ` Schaffner, Tobias
2023-02-27 4:39 ` [PATCH 0/2] Mask systemd-firstboot Uladzimir Bely
2023-02-27 12:23 ` Cedric Hombourger
2023-02-27 12:37 ` Jan Kiszka
2023-02-27 12:53 ` Uladzimir Bely
2023-02-27 12:55 ` Jan Kiszka
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=892fe496354a967054e63a67fbba59268f372548.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=quirin.gylstorff@siemens.com \
--cc=tobias.schaffner@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