From: "Yong Li" <yong.b.li@linux.intel.com>
To: "'OpenBMC Maillist'" <openbmc@lists.ozlabs.org>
Cc: <yong.b.li@linux.intel.com>
Subject: system_232 upgrade to 234?
Date: Wed, 13 Dec 2017 10:34:17 +0800 [thread overview]
Message-ID: <000001d373ba$e03dbc90$a0b935b0$@linux.intel.com> (raw)
Hi All,
I am working on the replacement for
chassis_control.py(https://github.com/openbmc/skeleton/blob/master/pychassis
ctl/chassis_control.py), using
https://github.com/openbmc/phosphor-state-manager. And would like to add the
uuid property into chassis-stats-manager.
I found this uuid property is using the same content in /etc/machine-id(from
the above chassis_contro.py). Based on
https://www.freedesktop.org/software/systemd/man/machine-id.html: This ID
uniquely identifies the host. It should be considered "confidential", and
must not be exposed in untrusted environments, in particular on the network.
And there is a new API(sd_id128_get_machine_app_specific(3)) to generate an
application specific ID.
It seems to me that we need to use the new systemd API to change the current
uuid generation logic. I can cherry-pick several systemd patch files to
backport the new API from 234 to 232. Or can we just upgrade the current
systemd_232 to 234(from yocto 2.4)? Any doc/plan about the upgrade?
Thanks for your comments/suggestions!
Yong Li
reply other threads:[~2017-12-13 2:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000001d373ba$e03dbc90$a0b935b0$@linux.intel.com' \
--to=yong.b.li@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.