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

["Moessbauer, Felix" <felix.moessbauer@siemens.com>]

> -----Original Message-----
> From: Anton Mikanovich <amikan@ilbers.de>
> Sent: Monday, August 1, 2022 5:52 PM
> To: Moessbauer, Felix (T CED SES-DE) <felix.moessbauer@siemens.com>;
> isar-users@googlegroups.com
> Cc: Schmidl, Tobias (T CED SES-DE) <tobiasschmidl@siemens.com>; Schild,
> Henning (T CED SES-DE) <henning.schild@siemens.com>; Kiszka, Jan (T CED)
> <jan.kiszka@siemens.com>
> Subject: Re: [PATCH v2 0/1] fix on-first-boot for systemd >= 247
> 
> 26.07.2022 00:09, Felix Moessbauer wrote:
> > Changes since v1:
> >
> > - check if systemd is installed
> >
> > Felix Moessbauer (1):
> >    fix on-first-boot for systemd >= 247
> >
> >   meta/classes/image-postproc-extension.bbclass | 9 ++++++++-
> >   1 file changed, 8 insertions(+), 1 deletion(-)
> >
> Hello,
> Because this is not working in buster systemd version should be changed.
> The best way will be to find out exact one, but looks like ">= 241" just works.

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