>Systemd is an exploit kit just waiting to be activated. And once it is active, only those who wrote it will be able to defuse it — and check whether it is defused. And it is starting: How to crash systemd in one tweet? Alternatives? Use OpenRC for system services. That’s simple and fast and full-featured with minimal fuss. Use runit for process supervision of user-services and system-services alike. draketo.de/light/english/top-5-systemd-troubles
>[...]In a September 2014 ZDNet interview, prominent Linux kernel developer Theodore Ts’o expressed his opinion that the dispute over systemd’s centralized design philosophy, more than technical concerns, indicates a dangerous general trend toward uniformizing the Linux ecosystem, alienating and marginalizing parts of the open-source community, and leaving little room for alternative projects. In this he found similarities with the attitude he found in the GNOME project toward non-standard configurations. On social media, Ts’o also later compared the attitudes of two key developers to that of GNOME’s developers.
Topic: Systemd is not an init system!! If someone characterizes systemd as an “init system,” you may safely assume that s/he is either utterly clueless or deliberately obfuscating the discussion. Calling systemd an init system is like calling an automobile a cup holder. Not even Lennart Poettering pretends that systemd is anything but the “Core OS” (sic).
What systemd is is an effort to re-create large portions of existing userspace (including login, job scheduling, and networking, just to name a few) inside a single process traditionally reserved for the sole purpose of starting *nix userspace. (Just in case it isn't clear, there is a huge difference between starting userspace (init) and being userspace (systemd).)
At the end of the day, how one perceives this re-creation of existing userspace strongly influences one's reaction to systemd. There are plenty of perfectly legitimate reasons to be troubled by this re-invention of the wheel; they range from the philosophical and aesthetic, to the technical and mechanical, even the purely political and brutally practical.
And that's part of the problem when folks start to “debate” systemd. Very few folks have the chops to think about, much less talk about all of these areas simultaneously. As a result, the discussion becomes fractured and disjointed, in what is literally the textbook definition of bikeshedding. Suddenly, a talking head who's never written a line of code in his/her life offers up an authoritative-sounding-but-utterly-bogus opinion on systemd's maintainability. Add in the fact that folks on both sides (including Poettering himself) act as if name-calling is a perfectly good substitute for empirical evidence, and the “debate” becomes indistinguishable from white noise.
>Linux is a shitty clusterfuck made up of thousands of autists arguing worldwide
More at 10.
Anthony Barnes
Who will be King Autismus Maximus? I don't know and I don't care. Indeed, I hope he never ascends to the throne, because the moment that one system achieves supremacy is the moment that system will start going to shit.
Isaac Rodriguez
>a german globalist is the cover up, red hat paid debian to force systemd fixed
Mason Morris
well every major dristro implemented it even do their communities disapproved it very hard. So something had to be happening behind scenes.
Maibe it was like this >DRM laptops are coming and we are going to be the only ones managing the signatures so fuckers if you don't put this shit in your distro you will disappear in darkness
Adrian Adams
>OpenRC >full-featured Doesn't even have concurrency.
Eli Lee
>well every major dristro implemented it false. Only debian-based distros PCLinuxOS, Arch, Manjaro, Gentoo, Chromium OS, Slackware are all systemd-free
Elijah Thomas
Arch and Manjaro are using systemd. So is Fedora.
Owen Perez
>PCLinuxOS, Arch, Manjaro, Gentoo, Chromium OS, Slackware are all systemd-free >major dristro this must be bait also arch is not systemd free
Nathan Torres
Include a quick redpill explanation on these posts.
John Carter
shoo shoo systemd shills
Ryder Mitchell
Arch is a joke distro, for the majority of Arch users it has no any effect whether it's systemd running the show or not.
>making corrections to a wrong comment >BTFOO SHILLLS BOSDFSDF go sleep kid
Jaxson Fisher
yeah ok
Jeremiah Lopez
...
Gavin Jenkins
Yeah, except that systemd is so shit because it's the opposite of "fragmented". It's a single point of failure that makes it extremely hard to avoid using if it doesn't suit your needs. It is an attempt to turn Linux into Windows.
"Fragmentation" is an epithet by morons that don't know how the real world works outside of middle management. Forcing everyone to do things one way is not efficient because bureaucrats are not developers.
Henry Bailey
2010: a german kid spent 5 years writing a sound server 2011: hired to develop systemd in 2 major distros
it's a scam
Jaxson Peterson
>Linux
Charles Hall
I would be more okay with SystemD if their modules weren't chosen at compile-time. It sort of defeats the purpose of modularity if you can only add or remove parts at the source and recompile.
Christopher Murphy
The NSA outsourced systemd to Bangladesh's top coders, and Pottering is just the "family-friendly face" of the project.
