Ubuntu
dbus package

  1. Bug #1508697
  2. Comment #3

Comment 3 for bug 1508697

Revision history for this message
Jason Gerard DeRose (jderose) wrote : Re: Wily: /var/lib/dbus/machine-id is symlink on desktop, file on server

@seb128: yes.

The two are related in that when /var/lib/dbus/machine-id is a symlink, the act of starting the system dbus instance can't (or wont, I guess) generate a machine-id (as the path in question is there, just the symlink target is missing).

And because of lp:1508697, systemd doesn't inself create /etc/machine-id when missing, which it should.

This is an obscure issue in the end, but it's caused problems with the System76 imaging system. I've put a lot of effort into making sure things that should be unique between machines, things that are unique when you do a manual Ubuntu install, are actually unique when we image a system. I used to just delete /var/lib/dbus/machine-id when building our golden image tarballs and let dbus generate the machine-id with dbus-uuid upon first boot. Now I have to generate /etc/machine-id during imaging, before we boot into the installed OS.