From: Jan Kiszka <jan.kiszka@siemens.com>
To: Cedric Hombourger <chombourger@gmail.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/2] Mask systemd-firstboot
Date: Mon, 27 Feb 2023 13:37:16 +0100 [thread overview]
Message-ID: <8cab404f-b481-e49c-7595-4951055cf84c@siemens.com> (raw)
In-Reply-To: <3844ec51-9e5e-4138-a0ea-399b7052bc0dn@googlegroups.com>
On 27.02.23 13:23, Cedric Hombourger wrote:
>
>
> On Monday, February 27, 2023 at 5:39:30 AM UTC+1 Uladzimir Bely wrote:
>
> In mail from Saturday, 19 November 2022 21:20:29 +03 user T.
> Schaffner wrote:
> > From: Tobias Schaffner <tobias.s...@siemens.com>
> >
> > systemd-firstboot asks the user interactively for missing system
> > configurations like locale or hostname if not configured.
> >
> > Mask this service as we do not want to depend on user interaction
> to allow
> > an image to boot.
>
> This is IMO a distro/product level decision and I am not sure if Isar,
> as a build-system, should make such decisions
>
Does the current approach now prevent to re-enable it at that level -
obviously only after fixing all the issues that motivated the disabling?
Then we need to be aware of the use case, and things should be made
configurable.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2023-02-27 12:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 18:20 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
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 [this message]
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=8cab404f-b481-e49c-7595-4951055cf84c@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=chombourger@gmail.com \
--cc=isar-users@googlegroups.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