From: "Gieseler, Christian" <CG@eks-engel.de>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] machine-id
Date: Wed, 2 Apr 2014 14:25:29 +0000 [thread overview]
Message-ID: <C9183576C7342045BFDCAE863EB3C37A1496D0@EKS-Exchange.eks-engel.local> (raw)
In-Reply-To: <20140401141819.GE31118@pengutronix.de>
Hi Michael,
> -----Original Message-----
> From: ptxdist-bounces@pengutronix.de [mailto:ptxdist-
> bounces@pengutronix.de] On Behalf Of Michael Olbrich
> Sent: Tuesday, April 01, 2014 4:18 PM
> To: ptxdist@pengutronix.de
> Subject: Re: [ptxdist] machine-id
>
> 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.
Ok, thats clear and easy to implement.
Can you explain why one needs the script /etc/rc.once.d/machine-id if the machine id is generated by systemd?
Best regards
Christian
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-04-02 14:26 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
2014-04-02 14:25 ` Gieseler, Christian [this message]
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=C9183576C7342045BFDCAE863EB3C37A1496D0@EKS-Exchange.eks-engel.local \
--to=cg@eks-engel.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