On Wed, Sep 30, 2020 at 9:58 pm, Petr Menšík <pemensik@xxxxxxxxxx>
wrote:
Shouldn't it change resolv.conf only in case NM is active AND
resolv.conf is generated by Network Manager?
Correct, that's indeed what it does. (Since Zbigniew changed it
yesterday. Previously, it did not check if NM is active.)
The systemd RPM scriplet will run sed, sed will see "Generated by
dnssec-trigger-script" and say "that's not "Generated by
NetworkManager" and it will leave your resolv.conf alone. So you're
right, you don't need to worry about resolv.conf.
Even if it did try to remove the immutable /etc/resolv.conf, the
upgrade script ignores failures, so you would see an error message in
the middle of the transaction about rm failing but it wouldn't fail the
whole upgrade.
It *will* still 'systemctl enable systemd-resolved.service', though, so
you'll still need to disable that or you'll indeed have a battle for
port 53. It will indeed probably break any local resolver you have
configured.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx
