On Mo, 22.02.21 17:15, Petr Menšík (pemensik@xxxxxxxxxx) wrote: > Wouldn't it be much simpler, if I could just dnf remove systemd-resolved > in case I don't want it? Then I don't have to make a proxy, but install > indeed a different package providing resolvconf. I think I would submit > that PR on Fedora package instead. Or don't have any > /usr/sbin/resolvconf, in which case openvpn or dhclient knows it should > try to rewrite /etc/resolv.conf itself. Unless driven by NM or similar. Quite frankly, I am not sure it would be a good idea to do things that way. note that resolved should be fine as a resolvconf replacement, even if you don't want to use it as a resolver: just set the /etc/resolv.conf symlink to /run/systemd/resolve/resolv.conf (instead of the usual /run/systemd/resolve/stub-resolv.conf) and you get the upstream servers listed there, as any other resolvconf implementation would do it. The thing is, there's a bunch of software these days that can talk to to resolved's D-Bus interface to set DNS servers and such. You lose all that if you insist that systemd-resolved is so terrible that you cannot even use it as a resolvconf reimplementation, that is more than a bunch of shell scripts. Another option might be https://docs.fedoraproject.org/en-US/packaging-guidelines/Alternatives/ btw. Lennart -- Lennart Poettering, Berlin _______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
