Kevin Fenzi writes:
On Thu, May 30, 2024 at 04:25:44PM GMT, Sam Varshavchik wrote:
Kevin Fenzi writes:
So, I think if you:
disable systemd-resolved or make /etc/resolv.conf a real file, not a link. or set 'DNSStubListener=no' in /etc/systemd/resolved.conf
It will not be replaced anymore.
I did not even /have/ systemd-resolved installed.
dnf system-upgrade installed it on its own, enabled it, and
/etc/resolv.conf
was replaced as a result.
Interesting. So, the only thing I see that requires systemd-resolved is anaconda-core. However, systemd itself has a 'recommends' for it, so perhaps thats what pulled it back in?
That's probably it. Sifting through /var/log/dnf.log: this was removed together with systemd-resolved, when I removed it.
But this is a red herring. It was anaconda itself that was also pulled in as a dependency.
Installing dependencies: anaconda x86_64 40.22.3-1.fc40 fedora 102 k anaconda-core x86_64 40.22.3-1.fc40 fedora 2.8 M anaconda-gui x86_64 40.22.3-1.fc40 fedora 562 k anaconda-tui x86_64 40.22.3-1.fc40 fedora 228 k
So, possibly keeping it installed, but masked is a better way to make sure it never gets enabled?
Masking is just solving the X of an XY problem. Either the dependencies being masked are not needed, or if they are needed masking would break something.