public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schaffner, Tobias" <tobias.schaffner@siemens.com>
To: "Schild, Henning" <henning.schild@siemens.com>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: bookworm/sid: new interactive system locale setting on first boot
Date: Thu, 20 Oct 2022 11:11:44 +0000	[thread overview]
Message-ID: <a8961696-b81d-4967-a199-e33356c67866@siemens.com> (raw)
In-Reply-To: <20221020125434.44e580fc@md1za8fc.ad001.siemens.net>

On 20.10.22 12:54, Schild, Henning (T CED SES-DE) wrote:

> I think for the time being we want to just disable it via the cmdline.
> It is unexpected and breaks non-interactive booting.
> 
> But looking at what that thing can do ... it seems valuable to keep it
> in mind. It in fact does 3 key things which we kind of want to do in
> any isar image as well. (and it can do more we also might want)
> - hostname (part of almost every layer i know)
> - rootpw (part of isar core)
> - locales (part of isar core)
> 
> Maybe we can eventually use it for these purposes and drop our
> implementations.
> 
> But back to the question on locale.conf. Generating that might also be
> an option. Here i would suggest to see where it comes from in a debian
> installed with the debian installer, if it is generated together with
> locale.gen and friends ... yes we likely want to generate it in the
> extension and solve the problem that way. Also have a look at the
> reconfigure scripts that we cater for, and how they changed with that
> more recent systemd.
> 
> Henning

I would suggest to provide the locale.conf even if we disable systemd-firstboot 
via the command line. Other packages might rely on a the new file as firstboot 
ensures that it will be present on bookworm.

  reply	other threads:[~2022-10-20 11:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 13:25 Jan Kiszka
2022-10-07 13:55 ` Henning Schild
2022-10-07 14:10   ` Jan Kiszka
2022-10-12  7:39     ` Florian Bezdeka
2022-10-12  8:03       ` Henning Schild
2022-10-13 12:50 ` Henning Schild
2022-10-20  8:51   ` Schaffner, Tobias
2022-10-20  9:18     ` Moessbauer, Felix
2022-10-20 10:54     ` Henning Schild
2022-10-20 11:11       ` Schaffner, Tobias [this message]
2022-10-20 11:14         ` Henning Schild
2022-10-19 11:28 ` Henning Schild

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=a8961696-b81d-4967-a199-e33356c67866@siemens.com \
    --to=tobias.schaffner@siemens.com \
    --cc=henning.schild@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