From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "Schild, Henning" <henning.schild@siemens.com>,
"Schmidl, Tobias" <tobiasschmidl@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"Schmidl, Tobias" <tobiasschmidl@siemens.com>
Subject: RE: [PATCH 1/1] fix on-first-boot for systemd >= 247
Date: Fri, 22 Jul 2022 08:34:17 +0000 [thread overview]
Message-ID: <AM9PR10MB486963F7DDCB3D46E8743E3889909@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220722102705.39e876ed@md1za8fc.ad001.siemens.net>
> -----Original Message-----
> From: Schild, Henning (T CED SES-DE) <henning.schild@siemens.com>
> Sent: Friday, July 22, 2022 10:27 AM
> To: Schmidl, Tobias (T CED SES-DE) <tobiasschmidl@siemens.com>
> Cc: isar-users@googlegroups.com; Moessbauer, Felix (T CED SES-DE)
> <felix.moessbauer@siemens.com>; Kiszka, Jan (T CED)
> <jan.kiszka@siemens.com>; Schmidl, Tobias (SI EP MF GWA EA 4)
> <tobias.schmidl@siemens.com>
> Subject: Re: [PATCH 1/1] fix on-first-boot for systemd >= 247
>
> Am Fri, 22 Jul 2022 10:02:35 +0200
> schrieb "Schmidl, Tobias (T CED SES-DE)" <tobiasschmidl@siemens.com>:
>
> > Hi Felix,
> >
> > Am Freitag, dem 22.07.2022 um 00:04 +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.
> > >
> >
> > Unfortunately, this doesn't seem to work on debian-buster (for
> > qemuamd64):
> >
> > ```
> > Jul 22 07:52:21 localhost systemd[1]: System cannot boot: Missing
> > /etc/machine-id and /etc is mounted read-only. Jul 22 07:52:21
> > localhost systemd[1]: Booting up is supported only when: Jul 22
> > 07:52:21 localhost systemd[1]: 1) /etc/machine-id exists and is
> > populated. Jul 22 07:52:21 localhost systemd[1]: 2) /etc/machine-id
> > exists and is empty. ```
>
> Sounds like one more >= cases to cover, and another number to find for when it
> changed in systemd.
I don't know if we will find a solution for buster as the bug only has been fixed for system >= 247.
For the technical reasoning, have a look here at [1].
> Ideally the numbers would be the ones where systemd
> really changed things, not the numbers we find in debian releases ... who knows
> whether ubuntu uses the same ones, or what is in some inbetween package
> feeds like backports.
The corresponding commit in systemd is a48627ef and I just checked which git tags contain that commit to get the version number.
So that should be fine.
PS: I just added the "right" Tobias and removed the other one.
Please apology for the confusion.
Felix
[1] https://github.com/systemd/systemd/pull/16939
>
> Henning
>
> > Kind regards,
> >
> > Tobias
prev parent reply other threads:[~2022-07-22 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 22:04 [PATCH 0/1] " Felix Moessbauer
2022-07-21 22:04 ` [PATCH 1/1] " Felix Moessbauer
2022-07-22 7:34 ` Henning Schild
2022-07-22 8:37 ` Moessbauer, Felix
2022-07-25 14:00 ` Moessbauer, Felix
2022-07-22 8:02 ` Schmidl, Tobias
2022-07-22 8:27 ` Henning Schild
2022-07-22 8:34 ` Moessbauer, Felix [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=AM9PR10MB486963F7DDCB3D46E8743E3889909@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
--to=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