On Fri, 8 Mar 2019 19:18:10 +0100, KatolaZ wrote in message
<20190308181810.7wnfugnqmqtiex37@???>:

> anyway:
>
> - /etc/hostid is defined in POSIX 2001 and POSIX 2008 (man gethostid)
>
> - /proc/sys/kernel/random/boot_id is randomly generated by the kernel
> at each boot (see drivers/char/random.c and kernel/sysctl.c in the
> kernel tree)
>
> - /var/lib/dbus/machine-id is used by dbus, and at the moment seems to
> not being re-generated at each boot (my recollection was wrong: we
> will fix it)

..do we need /var/lib/dbus/machine-id et al ID files at all?

..if we need them, can we recreate the(se) ID file(s) by e.g.
restarting dbus e.g. every minute?


..should we allow e.g. web browsers to read these ID files?

..if we allow e.g. web browsers to read these ID files, do we
offer One Devuan ID for Mankind, or do we drown them in an
avalance of random machine IDs?

> - /etc/machine-id should be used only by systemd components.

..totally agree, but e.g. chromium (ab)uses it:
"[20478:20478:0307/101807.205617:ERROR:browser_dm_token_storage_linux.cc(101)]
Error: /etc/machine-id contains 0 characters (32 were expected)"

..given their history, I wouldn't be surprised to learn they use
any of the other ID files.

--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.