public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schaffner, Tobias" <tobias.schaffner@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>,
	Anton Mikanovich <amikan@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Gylstorff, Quirin" <quirin.gylstorff@siemens.com>,
	"Bezdeka, Florian" <florian.bezdeka@siemens.com>
Subject: Re: [PATCH 2/2] Warn if systemd-firstboot misses configurations
Date: Fri, 24 Feb 2023 11:36:06 +0000	[thread overview]
Message-ID: <5870122b-17c7-373c-12bb-ceb768c44933@siemens.com> (raw)
In-Reply-To: <15530605.Emhk5qWAgF@home>

On 23.02.23 12:43, Uladzimir Bely wrote:
> In the email from Tuesday, 22 November 2022 13:24:53 +03 user Florian Bezdeka wrote:
>> 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
>>
>>>
>>
>>
> 
> We are still waiting for the answer, so the merge process is delayed.
> 
> Anyway, CI on recent `next` is still passed OK with the patch, so if no one against, we would merge it soon.

Hi Uladzimir,

sorry for the late reply. It behaves as Florian described it. We want to 
avoid a non booting image in any case but utilize systemd-firstboot to 
warn the user about possibly missing configurations.

Tobias

  reply	other threads:[~2023-02-24 11:36 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
2023-02-23 11:43       ` Uladzimir Bely
2023-02-24 11:36         ` Schaffner, Tobias [this message]
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=5870122b-17c7-373c-12bb-ceb768c44933@siemens.com \
    --to=tobias.schaffner@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=florian.bezdeka@siemens.com \
    --cc=isar-users@googlegroups.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