On Tuesday, July 28, 2020 9:22:58 AM MST Michael Catanzaro wrote:
I agree we should not replace /etc/resolv.conf if it's not
already a
symlink (although this will not be a common case, since by default it
is a symlink managed by NetworkManager).
I haven't found any systems where that's the case, though my systems have been
upgraded all along through from ~F24. Looking at my latest install, which has
been upgraded from F30, /etc/resolv.conf is still just a file by default.
On Tue, Jul 28, 2020 at 11:07 am, Neal Gompa
<ngompa13(a)gmail.com> wrote:
> We can be smart here and replace the file when we detect that it's
> managed by NetworkManager. Otherwise we won't replace it.
Currently we actually don't touch it at all, which is not good because
it means systemd-resolved will not be managing resolv.conf on upgraded
systems.
That's not necessarily a bad thing. Regardless of what we do here, systemd-
resolved is a consumer of NetworkManager's configuration.
We should replace it with a symlink to systemd if (and only
if) it's managed by NetworkManager.
Sounds good.
--
John M. Harris, Jr.