On 28 Apr at 17:27, Tom Horsley <horsley1...@gmail.com> wrote:
> But systemd-timedated tries to supplant them all :-). This is where
> my "computer fungus" description comes from. Every systemd release
> seems to take over something else that worked fine without systemd
> engulfing it.
I've been working in Unix since about 1980--I wrote custom BIOS code for
BTL products, Unix drivers and kernel internals while at BTL Naperville,
and rewrote cut and paste for contribution to the Gnu Project (and
wasn't *that* fun, but another story.) Suffice to say I've been around
a long time.
The biggest problem I have with systemd is that it violates, on so many
levels, the Unix mantra "do one thing and do it well". It may have been
a good idea when it was only supposed to provide an efficient replacement
for the admittedly fractured different system initialization system.
With it growing to subsume so many different, and usually unrelated,
tasks, it's turned into the kind of thing that we were trying so hard to
get away from--the monolithic OS with complex interrelated interactions
that was prevalent at the time.
And everything that we wanted to avoid is resurfacing with systemd. It's
become a glop of totally unrelated features and services, difficult
to diagnose and maintain, and prone to unwanted and unforseen
interactions. Tug this strand, and the spiderweb shivers.
$0.02, and I know nobody's going to listen to me, but listening to the
conflicts on this topic just make me sigh.
Sincerely,
--
Dave Ihnat
dih...@dminet.com
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
