Hi,
On Sun, 14 Aug 2022 04:29:52 +0200 Raphaël Halimi
<raphael.hal...@gmail.com> wrote:
And finally, my opinion:
After reading the mail thread in this bug report, I thought the plan was
to separate systemd-resolvconf (as Arch did, IIUC), not the entire
systemd-resolved service.
IMHO this is a **very** bad idea, and not only because of the broken DNS
resolution broken after the upgrade in some cases... The whole point of
systemd-resolved is that it's included in systemd (so basically in every
Linux system nowadays) and, alongside systemd-networkd, provides an
entire network configuration/management stack, without the need to
install optional packages, but most importantly, standard across all
distributions (no need to learn and/or master ifupdown, sysconfig,
netplan, whatever, etc).
If it's not too late, I strongly suggest to reintegrate systemd-resolved
in the main systemd package (as it was before), and split only
systemd-resolvconf.
I agree that the decision should be revisited, but for a different
reason. I see no reason why resolvconf cannot be used with resolved;
OTOH the current split prevents that, which I find very undesirable.
I was very surprised when I learnt today systemd-resolved has a
Conflicts against resolvconf, that was contrary to my expectations, and
I suspect I’m not the only person concerned about this.
--
Cheers,
Andrej
