On Mon, 18 Apr 2022 15:29:01 -0400
Matthew Miller <mattdm(a)fedoraproject.org> wrote:
On Sun, Apr 17, 2022 at 06:34:48PM -0400, Sam Varshavchik wrote:
> but it was mostly working, so stayed under the radar, until the
> recent update broke it. Additionally, the systemd-resolved rpm is
> actively hijacking /etc/resolv.conf. From the package's scriptlet:
Sam, can you _please_ not use such colorfully-negative lagnguage here?
None of this is "infestation", "hijacking", or something to
"fumigate". This
is all from an approved Change for Fedora Linux 33, which you can read here:
https://fedoraproject.org/wiki/Changes/systemd-resolved, and which was
documented in the release notes at
https://docs.fedoraproject.org/en-US/fedora/f33/release-notes/sysadmin/Ne....
You're welcome to disagree with the technical decision (although _elaborate_
disagreement isn't very helpful without an alternative plan and someone to
implement it!). But, as you can see from the "Benefit to Fedora" section of
the proposal, this was done by people actively working to make Fedora Linux
better for users, and the Fedora Engineering Steering Committee weighed that
benefit along with considerable feedback in making the decision.
So, all of this language which implies pestilence or some kind of illicit
undertaking is wildly out of line.
Better for users? Are you kidding?
All this systemd is reinventing the wheel.
Go back to Windows, when you grow up.
Without BR, Bob