On Tue, 12 Jun 2018 15:29:54 +0200
John Paul Adrian Glaubitz
On 06/12/2018 03:23 PM, John Paul Adrian Glaubitz wrote:
On 06/12/2018 03:11 PM, Thorsten Kukuk wrote:
On Tue, Jun 12, John Paul Adrian Glaubitz wrote:
But I don't want to delve into bike-shedding.
I'm just reporting what upstream does
Upstream is still using /etc/resolv.conf and I haven't seen any discussions to change that.
So "old-fashioned" is the new NEW?
https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS#n350
And here is the commit upstream:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=4805be...
dns-manager: make /etc/resolv.conf a symlink to /run/NetworkManager/resolv.conf.default Related:
* https://bugzilla.gnome.org/show_bug.cgi?id=732941 * https://bugzilla.redhat.com/show_bug.cgi?id=1116999
Acked-By: Thomas Haller
Acked-By: Dan Williams Adrian
Please note that this change only one of backends for writting dns.resolv. Network manager currently support 5 backends and two use symlink ( default and systemd-resolved ), other two not and the last one does not modify it at all. So in fact part of backends find that useful, but not all of them. And also default backend can be configured to not use symlink. So it use symlink as default, but can operate also with file. see https://developer.gnome.org/NetworkManager/stable/NetworkManager.conf.html keys dns and rc-manager So some only some projects find useful to use symlink and even network manager have it only optional and not mandatory. But I am pretty sure that if we by default change to symlink many parts will break and it also will require non-trivial changes in YaST. Josef -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org