From: Anton Mikanovich <amikan@ilbers.de>
To: "Schmidl, Tobias" <tobiasschmidl@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"Moessbauer, Felix" <felix.moessbauer@siemens.com>,
"Schild, Henning" <henning.schild@siemens.com>
Subject: Re: [PATCH v3] fix on-first-boot for systemd >= 247
Date: Wed, 10 Aug 2022 10:10:44 +0300 [thread overview]
Message-ID: <647885ee-94f3-447e-7b60-30e6a86664be@ilbers.de> (raw)
In-Reply-To: <943064177567880c3c7bc2466a4d390e03b42aab.camel@siemens.com>
09.08.2022 22:01, Schmidl, Tobias wrote:
> Hi all,
>
> Am Dienstag, dem 02.08.2022 um 12:39 +0200 schrieb Felix Moessbauer:
>> This patch fixes the bug that /etc/machine-id is never
>> generated when running from within an initrd with an ro rootfs.
>>
>> In this case, the magic value "uninitialized" has to be used
>> instead of deleting the file.
>>
>> For older systemd versions, we set it to the empty string
>> which is non-documented, but works as identified
>> in various tests on debian buster (systemd version 241).
>>
>> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
>> ---
> What is the status of this patch? Are there any impediments?
>
> Kinds regards,
>
> Tobias
>
Hello Tobias,
This patch was tested and looks ok.
A week past from the patch receiving, so we are ready to apply it.
Didn't managed to merge it yesterday, will do it today.
next prev parent reply other threads:[~2022-08-10 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 10:39 Felix Moessbauer
2022-08-09 19:01 ` Schmidl, Tobias
2022-08-10 7:10 ` Anton Mikanovich [this message]
2022-08-10 11:33 ` Anton Mikanovich
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=647885ee-94f3-447e-7b60-30e6a86664be@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