On 06/11/2018 09:22 PM, Stefan Seyfried wrote:
https://bugzilla.opensuse.org/show_bug.cgi?id=1018387 is open for over than one year, nobody even attempts to fix it.
I looked at the original bug report and at first look, the symbolic link is just wrong. /etc/resolv.conf should point to /run/systemd/ resolve/resolv.conf: root@tirpitz:~> ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 32 Apr 27 2016 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf root@tirpitz:~>
Even more: because of a bug / issue in another place (live image building), systemd-networkd is kept unusable.
That's a shame. I like systemd-networkd and -resolved, it just works(TM). I use it on lots of the buildds I am maintaining for Debian Ports and I never ran into any issues. It works on any architecture, even on my Amiga 4000 with Debian unstable ;).
Last week, I attended a workshop on how to use systemd-networkd. Of course the trainer advised everyone not to use openSUSE but Arch, fedora, ... you name it, because "SUSE does not even include it" (he was used to SLES12...).
Works on Debian as well.
I convinced everyone that current openSUSE and SLES versions do include it. Only to find out, directly afterwards, that it's unusable.
That's a pity, really.
And when I try to fix it (https://build.opensuse.org/request/show/616099), it gets declined because the maintainer (who has done nothing about this bug for over one year) wants a perfect solution, not a working one.
Hmm, I would also agree to rather fix the actual bug instead of adding a hack. I don't quite understand what the original issue is that we don't use the proper symlink that upstream uses. If the fix involves upstream work, I can help with that. I have contributed something like 10 patches to systemd upstream in the past. Adrian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org