From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] machine-id
Date: Tue, 1 Apr 2014 16:18:19 +0200 [thread overview]
Message-ID: <20140401141819.GE31118@pengutronix.de> (raw)
In-Reply-To: <C9183576C7342045BFDCAE863EB3C37A148FB8@EKS-Exchange.eks-engel.local>
On Mon, Mar 31, 2014 at 01:13:28PM +0000, Gieseler, Christian wrote:
> while thinking how to preserve the existing machine-id after an complete
> update I had I look how this is generated. In the rc-once.d folder there is a
> script generating an id and systemd also has the capability to generate one
> and obviously does check for a valid machine-id and regenerates one in case
> of an invalid/non exisiting one.
> Looking into the dependencys the ptxdist machine-id script is selectd with
> systemd. Is the existance of the ptxdist machine-id necessary if systemd
> takes care of the machine id?
> And finaly coming back to the original question what is the best way to
> preserve the machine-id? Patching Systemd to change the hardcoded path? Or
> are there other smarter solutions?
The machine-id is read very early, so even if you change the path in
systemd, so the path must be in the rootfs and is probably overwritten
during a complete update.
You could explicitly save the machine-id before an update and copy it back
afterwards.
If you have an initrd then you could bind mount your machine-id to
/etc/machine-id before starting systemd.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-04-01 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 13:13 Gieseler, Christian
2014-04-01 14:18 ` Michael Olbrich [this message]
2014-04-02 14:25 ` Gieseler, Christian
2014-04-02 16:17 ` Michael Olbrich
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=20140401141819.GE31118@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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