On 06/11/2018 11:25 PM, Patrick Shanahan wrote:
Yes, because network-manager detected that another process has touched your resolv.conf :).
only yast, not edited by hand.
but if you wish, I *can* provide output that does not claim a modified /etc/resolv.conf and with networkmanager active still provides resolv.conf /as a file below /etc.
And you're still wrong, sorry.
From the NEWS file of NetworkManager:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS#n347
* Management of resolv.conf can be changed at runtime, private resolv.conf is always written in /run. * NetworkManager can now write DNS options to resolv.conf. * Added an option to enable the old-fashioned /etc/resolv.conf handling (using a symlink) You might want to Google the term "stateless system" so you understand why many modern plumberland parts are moving towards a read-only /etc and put runtime data into /run. Adrian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org