Barry Scott writes:
> On 29 May 2024, at 23:49, Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote: > > I updated from F39 to F40. I used to have: > > /etc/resolv.conf -> /run/NetworkManager/no-stub-resolv.conf > > Everything got messed up because the update hijacked this symlink again: >> lrwxrwxrwx. 1 root root 39 May 29 09:44 /etc/resolv.conf - > ../run/systemd/resolve/stub-resolv.conf>> I was confident that F39 did not have systemd-resolved installed, it must've been pulled into the update.>> I repeated the experiment on two other F39 systems today. I confirmed that neither one of them had systemd-resolved installed. F40 pulled it in, and the package's scriptlet clobbered /etc/resolv.conf>> It would be real nice if someone finally STOPed this repeated hijacking of /etc/resolv.conf, and breaking network connectivity, is this too much to ask? Although this was fairly simple to fix, this kind of behavior does not improve systemd's existing reputation.My understanding is that you can configure either systemd-resolved or NetworkManger to setup what you needto be in resolv.conf and then can leave how the symlink is managed as is. Have you thought to do that setup?
That's exactly what I've done. I'm using NetworkManager. The symlink normally points to NetworkManager-written resolv.conf.
dnf system-upgrade download --releasever=40 followed by dnf system-upgrade reboot ended up installing systemd-resolved, and then replacing the symlink. That's precisely the problem.
Attachment:
pgpMcNlQeRdgA.pgp
Description: PGP signature
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
