> systemd doesn't inself create /etc/machine-id when missing, which it
should.
I think the solution to "my system-imaging setup isn't working" is to
get that bug (presumably a systemd bug?) fixed - this one is rather
minor by comparison. Do you have a correct bug# for it?
> I've put a lot of
Simon McVittie [2015-10-29 11:55 -]:
> > systemd doesn't inself create /etc/machine-id when missing, which it
> should.
>
> I think the solution to "my system-imaging setup isn't working" is to
> get that bug (presumably a systemd bug?) fixed - this one is rather
> minor by comparison. Do you
Oops, sorry for the confusion, haven't been sleeping enough lately :P
I meant to refer to lp:1508766 which I filed about systemd not creating
/etc/machine-id if it's missing:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1508766
Now that /var/lib/dbus/machine-id is a symlink to
That situation should never arise, because if the symlink exists, then
it was created by a successful boot with systemd sometime in the past;
systemd's API is that it guarantees to create /etc/machine-id before
running third-party code; and systemd never deletes the machine ID after
it has created
Which I guess raises another question... when booting with sysvinit or
Upstart, what should dbus do when /var/lib/dbus/machine-id is a symlink
to /etc/machine-id and the latter doesn't exist?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> Or at least dbus wont (and arguably it shouldn't... seems to me
systemd should be doing this)
I agree with that reasoning. It's fine for D-Bus to be responsible for
creating its own older machine ID file if necessary, but it shouldn't be
responsible for creating the one that belongs to systemd
