Re: [PATCH 1/1] fix on-first-boot for systemd >= 247

[Henning Schild <henning.schild@siemens.com>]

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. 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.

Henning

> Kind regards,
> 
> Tobias