[RFC] Fixing the machine id
mzqohf at 0pointer.de
Fri Mar 4 14:44:53 PST 2011
On Fri, 04.03.11 17:38, James (purpleidea at gmail.com) wrote:
> > So, here's what systemd now does at boot: when it finds /etc/machine-id
> > populated, then everything is fine. If it is not populated, it tries to
> > initialize it from /var/lib/dbus/machine-id, with a fallback on
> > /dev/urandom. If that works, then everything is fine. If it doesn't but
> > the file exists and is suitable as mount point we instead store the id
> > we generated in a file in /dev/.systemd/ and then bind mount it over
> > /etc/machine-id. If that works, then everything is fine. If that doesn't
> > work or we cannot create the mount point then we simply fail and give
> > up.
> The one thing that comes to mind; from my sysadmin point of view is that
> files named /dev/.something pop up as warnings in daemons like rkhunter.
> Maybe it would be sane to send them a patch so they know to expect these
> new things. Maybe a small trivial point, but it's free.
Well, it's kinda common already: udev, MD and systemd have been doing
this for a while, and mount now too.
Lennart Poettering - Red Hat, Inc.
More information about the dbus