Your message dated Wed, 29 Apr 2015 15:12:10 +0200
with message-id <[email protected]>
and subject line Re: Bug#783716: base-files: /etc/machine-id should be
symlinked to /var/lib/dbus/machine-id
has caused the Debian Bug report #783716,
regarding base-files: /etc/machine-id should be symlinked to
/var/lib/dbus/machine-id
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
783716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783716
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: base-files
Version: 8
Severity: important
Dear Maintainer,
/etc/machine-id should probably be symlinked to /var/lib/dbus/machine-id
http://www.freedesktop.org/software/systemd/man/machine-id.html says:
"The simple configuration file format of /etc/machine-id originates in the
/var/lib/dbus/machine-id file introduced by D-Bus. In fact, this latter file
might be a symlink to /etc/machine-id."
The /var/lib/dbus/machine-id file is randomly generated by dbus-uuidgen,
typically invoked by the post-install script of a D-Bus package. It can also be
a symlink to /etc/machine-id.
So these two files should be identical yes?
Right now I have a system that this is not the case:
debian8:~# cat /var/lib/dbus/machine-id
f2cbc914bd90a387226fdd590010b30e
debian8:~# cat /etc/machine-id
85779930452d4a6682d24fef13ffa0c8
what I did was remove /etc/machine-id and rebooted the system, which caused
this file to be regenerated. Although /var/lib/dbus/machine-id stays the same,
which could potensially make software missmatch depending on which file it
looks for. There might be a reason to why there are two uniqe files but from
where I stand now
It would be better if /etc/machine-id was a symlink to /var/lib/dbus/machine-id.
debian8:~# dbus-uuidgen
91766c951b045eb821a146435540cd13
-- System Information:
Debian Release: 8.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-042stab106.4 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages base-files depends on:
ii gawk [awk] 1:4.1.1+dfsg-1
base-files recommends no packages.
base-files suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Apr 29, 2015 at 02:42:57PM +0200, Stefan wrote:
> Package: base-files
> Version: 8
> Severity: important
>
> Dear Maintainer,
>
> /etc/machine-id should probably be symlinked to /var/lib/dbus/machine-id
>
> http://www.freedesktop.org/software/systemd/man/machine-id.html says:
>
> "The simple configuration file format of /etc/machine-id originates in the
> /var/lib/dbus/machine-id file introduced by D-Bus. In fact, this latter file
> might be a symlink to /etc/machine-id."
>
> The /var/lib/dbus/machine-id file is randomly generated by dbus-uuidgen,
> typically invoked by the post-install script of a D-Bus package. It can also
> be a symlink to /etc/machine-id.
>
> So these two files should be identical yes?
No, documentation says they are in the same *format*, not that they
have to be the same file.
Because they follow the same format, a symlink is allowed, but they
don't really have to be the same.
BTW: Please do not inflate bug severities. For this issue to be
"important" you would have to specify clearly which program break
horribly by those files not being the same, and so far, everything
works ok when those files are not the same.
> Right now I have a system that this is not the case:
>
> debian8:~# cat /var/lib/dbus/machine-id
> f2cbc914bd90a387226fdd590010b30e
> debian8:~# cat /etc/machine-id
> 85779930452d4a6682d24fef13ffa0c8
>
> what I did was remove /etc/machine-id and rebooted the system, which caused
> this file to be regenerated. Although /var/lib/dbus/machine-id stays the
> same,
> which could potensially make software missmatch depending on which file it
> looks for. There might be a reason to why there are two uniqe files but from
> where I stand now
> It would be better if /etc/machine-id was a symlink to
> /var/lib/dbus/machine-id.
Whether or not it would be better, I don't know, but in either case
/etc/machine-id does not belong to base-files.
See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745876
for details.
Thanks.
--- End Message ---
