From: Baurzhan Ismagulov <ibr@radix50.net>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] image-postproc-extension: empty mechine-id
Date: Wed, 10 Jul 2019 10:48:31 +0200 [thread overview]
Message-ID: <20190710084831.GE8266@yssyq.m.ilbers.de> (raw)
In-Reply-To: <8f32d02f4d6e433fb17bb80cd0ea5a66@siemens.com>
Hello Bao Cheng,
On Mon, Jul 08, 2019 at 10:57:36AM +0000, Su, Bao Cheng wrote:
> According to manpage of debian machine-id @
> https://manpages.debian.org/buster/systemd/machine-id.5.en.html,
> /etc/machine-id should be empty instead of removing.
>
> Also according to above manpage, the dbus machine-id is copied to
> /etc/machine-id if systemd machine-id is empty. However, the dbus
> machine-id is also created during isar building, which stays the same
> for every machine using the same image.
>
> So here instead of removing, empty this file, and the mechine id will
> be regenerated at the first boot. Also remove the dbus machine-id to
> prevent copying.
Thanks, applied to next.
I couldn't observe your original "sys-subsystem-net-devices-multi-user.device
timeouts" problem. Is it reproducible with stock Isar? Which architecture?
Also, at least for amd64, the machine id is only generated temporarily. The
file is not replaced since /etc is read-only at that moment. So we have to
revisit Claudius's rw patch. This works for arm since it is already rw.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-07-10 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 3:37 Su, Bao Cheng
2019-07-08 6:47 ` Claudius Heine
2019-07-08 10:57 ` Su, Bao Cheng
2019-07-10 8:48 ` Baurzhan Ismagulov [this message]
2019-07-10 9:19 ` Su, Bao Cheng
2019-07-10 11:44 ` Henning Schild
2019-07-11 4:06 ` Su, Bao Cheng
2019-07-11 5:34 ` Jan Kiszka
2019-07-11 10:25 ` Baurzhan Ismagulov
2019-07-11 16:37 ` Henning Schild
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=20190710084831.GE8266@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.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