On 12/2/20 6:44 PM, Dudemanguy via artix-general wrote:
> The dbus-uuidgen page says:
> >The important properties of the machine UUID are that 1) it remains
> unchanged until the next reboot
> https://dbus.freedesktop.org/doc/dbus-uuidgen.1.html
>
> So it should be fine for it to change on every reboot. I'm not sure what
> pulseaudio setting exactly expects the UUID to always be the same, but
> that doesn't sound like correct behavior. Technically, the script as it
> is will always overwrite machine-id if you bring down and back up
> (something you probably shouldn't do but still). That could be improved.
>
> That being said, the page does also mention using
> /var/lib/dbus/machine-id. I'm not sure what Arch does here exactly. It
> seems like a good idea to try and implement it somehow though.
So as a followup on this. It turns out that the systemd manual page for
machine-id says:
> The machine ID is usually generated from a random source during system
> installation or first boot and stays constant for all subsequent
> boots.
https://www.freedesktop.org/software/systemd/man/machine-id.html
This isn't the same as the dbus spec but unfortunately it seems some
applications do expect the machine-id to always persist across boot
(thanks systemd). I've introduced an option in the conf file in the
dbus-srv directory to always regenerate the /etc/machine-id whenever
the service is brought up (previously it always did this). It defaults
to "no" for compatibility but you can change it to "yes" if you're extra
paranoid (like me). Currently in gremlins.
More information about the artix-general
mailing list