public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schmidl, Tobias" <tobiasschmidl@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Moessbauer, Felix" <felix.moessbauer@siemens.com>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
	"Schmidl, Tobias" <tobias.schmidl@siemens.com>,
	"Schild, Henning" <henning.schild@siemens.com>
Subject: Re: [PATCH 1/1] fix on-first-boot for systemd >= 247
Date: Fri, 22 Jul 2022 08:02:35 +0000	[thread overview]
Message-ID: <8eb54821376a92287a19f3162342a50c8d43b78e.camel@siemens.com> (raw)
In-Reply-To: <20220721220404.1069481-2-felix.moessbauer@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.
```

Kind regards,

Tobias

  parent reply	other threads:[~2022-07-22  8:02 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 [this message]
2022-07-22  8:27     ` Henning Schild
2022-07-22  8:34       ` Moessbauer, Felix

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=8eb54821376a92287a19f3162342a50c8d43b78e.camel@siemens.com \
    --to=tobiasschmidl@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=tobias.schmidl@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