From: Matthias Luescher <lueschem@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: "[ext] claudius.heine.ext@siemens.com"
<claudius.heine.ext@siemens.com>,
isar-users@googlegroups.com, Claudius Heine <ch@denx.de>,
Matthias Luescher <lueschem@gmail.com>
Subject: Re: [PATCH 3/3] image-postproc-extension: add removal of machine-id
Date: Wed, 29 May 2019 09:00:32 +0200 [thread overview]
Message-ID: <CAMhkXVOsFMy3jVTrm5zKaT7h-ADXPjDJKDrkTVg_iEGnJ-NahQ@mail.gmail.com> (raw)
In-Reply-To: <20190528215130.6b79bd37@md1za8fc.ad001.siemens.net>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
Hi Henning
Maybe you can add a
>
> Reported-by: Matthias Lüscher <m.luescher@datacomm.ch>
>
> He is the maintainer of https://www.get-edi.io/ and mentioned that in a
> talk i attended before i brought that up for Isar.
>
> Matthias let us know if you care.
>
I am fine if you would like to add me as a reporter.
However, what is probably more important is that the ISAR users are aware
of the systemd preset behavior that gets triggered by the removal of
/etc/machine-id:
https://www.get-edi.io/11-Traps-to-Avoid-When-Building-Debian-Images/ (9.
systemd Preset Behavior).
I am looking forward to learn more about ISAR during the upcoming OSADL
networking day!
Best regards
Matthias
[-- Attachment #2: Type: text/html, Size: 1255 bytes --]
next prev parent reply other threads:[~2019-05-29 7:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 8:58 [PATCH 0/3] Filesystem mounting and machine-id fix claudius.heine.ext
2019-05-28 8:58 ` [PATCH 1/3] wks: added 'rw' to kernel arguments claudius.heine.ext
2019-05-28 17:29 ` Henning Schild
2019-05-29 6:38 ` Claudius Heine
2019-05-28 8:58 ` [PATCH 2/3] image.bbclass: remove fstab generation claudius.heine.ext
2019-05-28 17:34 ` Henning Schild
2019-05-29 6:47 ` Claudius Heine
2019-05-29 11:11 ` Henning Schild
2019-05-28 8:58 ` [PATCH 3/3] image-postproc-extension: add removal of machine-id claudius.heine.ext
2019-05-28 17:44 ` Henning Schild
2019-05-29 7:00 ` Claudius Heine
2019-05-29 11:06 ` Henning Schild
2019-05-28 19:51 ` Henning Schild
2019-05-29 7:00 ` Matthias Luescher [this message]
2019-05-29 7:06 ` Claudius Heine
2019-06-06 17:18 ` Maxim Yu. Osipov
2019-06-04 20:09 ` [PATCH 0/3] Filesystem mounting and machine-id fix Maxim Yu. Osipov
2019-06-05 6:45 ` Claudius Heine
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=CAMhkXVOsFMy3jVTrm5zKaT7h-ADXPjDJKDrkTVg_iEGnJ-NahQ@mail.gmail.com \
--to=lueschem@gmail.com \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@siemens.com \
--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