From: Anton Mikanovich <amikan@ilbers.de>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schmidl, Tobias" <tobiasschmidl@siemens.com>,
"Schild, Henning" <henning.schild@siemens.com>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: [PATCH v2 0/1] fix on-first-boot for systemd >= 247
Date: Tue, 2 Aug 2022 10:56:28 +0300 [thread overview]
Message-ID: <c4a028fc-bb18-a24b-8ae6-33d40eb09990@ilbers.de> (raw)
In-Reply-To: <AM9PR10MB4869A71F85F0A23A026498D3899A9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>
01.08.2022 19:28, Moessbauer, Felix wrote:
>> Hi,
>>
>> as stated in the patch, this solution will only work for systemd >= 247 as there the "uninitialized" support has been added.
>> As there is not systemd >= 247 for buster, we simply cannot support it OOTB.
>> For buster, you have to make the rootfs rw right from the beginning on, so the /etc/machine-id file can be created.
>> That's why we have two code paths in the patch.
>>
>> Felix
>>
Hm, I've tried to set machine-id to 'uninitialized' for Buster and it
worked.
But looks like even create empty file do the trick.
Creating empty machine-id makes even Bullseye systemd generate id, but we
probably should follow official way with 'uninitialized' there. So the new
proposal is to create empty file for <247 and 'uninitialized' for others.
prev parent reply other threads:[~2022-08-02 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 21:09 Felix Moessbauer
2022-07-25 21:09 ` [PATCH v2 1/1] " Felix Moessbauer
2022-07-26 9:09 ` Moessbauer, Felix
2022-07-27 9:20 ` Henning Schild
2022-08-01 15:52 ` [PATCH v2 0/1] " Anton Mikanovich
2022-08-01 16:28 ` Moessbauer, Felix
2022-08-02 7:56 ` Anton Mikanovich [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=c4a028fc-bb18-a24b-8ae6-33d40eb09990@ilbers.de \
--to=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=tobiasschmidl@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