On Wed 10 Apr 2024 at 14:36:20 (-0400), Jeffrey Walton wrote: > On Wed, Apr 10, 2024 at 7:00 AM Vincent Lefevre <vinc...@vinc17.net> wrote: > > > > On one machine, I have > > > > lrwxrwxrwx 1 root root 35 2023-10-07 13:43:24 > > /etc/systemd/system/sockets.target.wants/dm-event.socket -> > > /lib/systemd/system/dm-event.socket > > > > and on another one, I have > > > > lrwxrwxrwx 1 root root 39 2024-01-05 16:54:09 > > /etc/systemd/system/sockets.target.wants/dm-event.socket -> > > /usr/lib/systemd/system/dm-event.socket > > > > These symlinks were created at Debian installation time, and in > > both cases, the dmeventd version is 2:1.02.196-1+b1. > > > > Shouldn't the system ensure that symlinks are consistent on different > > machines (even though the above symlinks are equivalent), for instance > > to ease the comparison of configurations between machines? > > > > For instance, shouldn't usr-is-merged convert the symlinks to a > > canonical path? > > Be careful of fiddling with the Systemd symlinks. If you convert the > relative ones to absolute ones, then the machine will fail to boot.
I don't think there should be any relative systemd symlinks in /etc/systemd/ unless, for some peculiar reason, you've hand-crafted them yourself. Cheers, David.
