Bonum Certa Men Certa

Combatting Revisionist History (Post From 2015, Years Before IBM Bought Red Hat and Increased Vendor Lock-in)

A day ago (Debian Developer from Japan):

Debian Developer from Japan on systemd

Keanu Approves/Disapproves IBM: They tell us they combat racism; But more people find out it's a PR stunt
Smokescreen that serves to distract from the very racist nature of IBM and its founder



Summary: Today we republish this forum post from more than 6 years ago; in light of what IBM did to CentOS and its vicious attack on the founder of the GNU/Linux operating system we must understand the systemd agenda, which the FSF can more openly speak about now that there are no financial strings

I'm something of a historian, I can't help but be troubled by the revisionist history I see unfolding in the aftermath of the recent controversy over systemd. So, from the “you are entitled to your own opinion, but not your own facts” department, as a kind of parting gift to this community, I'd like to do what I can to marshal what I perceive to be the pertinent facts into a single bucket.

Disclaimer: For the benefit of those who may stumble on this post without any knowledge of my feelings on the matter, it's safe to call me the original systemd hater. In fact, it was my own headlong flight from systemd that originally led me to Debian in the first place. (And depending on your POV, that may constitute Yet Another Reason to hate systemd.) I make no claim nor pretense to "balance" or "fairness" regarding systemd any more than I would for, say, arsenic poisoning. My aim is to challenge and hopefully dispel certain memes that I see emerging from the systemd aftermath.

With that out of the way...

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.

Speaking of noise...


There was never a systemd debate
Debian came late to the systemd party. Systemd has been controversial since its inception in 2010. During the intervening four years, people have fled and even forked distros over systemd. By the time Debian's GR rolled around, anyone and everyone who was going to have a strong opinion about systemd already had it. Nobody was going to change their minds, thus there was no true “debate.”

We humans love to imagine that we are rational creatures, driven by logic and reason, capable of making reasoned, optimal decisions. Which is great except what we really are is short-sighted, pig-headed, and stupid. Psychology has a boatload of experiments that demonstrate that once you get to the choose-up-sides stage, then argument becomes dramatically less effective. (Google “confirmation bias” and “backfire effect” to learn more.)


The GR was not a mandate for systemd
I have no idea where systemd fanbois get the idea that a victory lap is appropriate.

The results of the GR vote were diluted and obfuscated by two non-resolution outcomes. Of the three technologically-relevant resolutions to the GR, one was unequivocally pro-systemd, the other two were contra-systemd, differing primarily in phrasing (essentially the difference between “must not” and “should not”).

(Aside: I confess to being a “must not” guy at heart, but I grudgingly admit that those who suggest that an absolute prohibition might prove unnecessarily inflexible or self-limiting might have a valid point. Maybe. But I don't have to like doing it.)

But here's the thing, and there is just no getting around it. Once you eliminate the ass-covering "no GR required" amendment, “systemd is a bad idea, the only real question is how bad” didn't place third.

It placed first. By a substantial margin.

Conversely, “systemd is a good idea” didn't place first.

It placed last.

If this surprises you, even a little, then by all means, go look it up. And for the love of whatever you hold Sacred, refrain from uttering a single word of GR-related drivel until you do.

(Edit: My exhortation above to refrain from drivel absent sufficient research was predictably futile. So, for the benefit of those who are unable or unwilling to do the math themselves, a pre-digested version of the analysis can be found here: viewtopic.php?f=20&t=120652&p=576562#p576502)


Speaking of the GR...


The GR was too necessary
As noted above, the only reason “systemd is a bad idea” wasn't the outcome of the GR vote is because of the “political cover” amendment that allowed “This conversation is superfluous” to pretend to be the correct answer (which it absolutely isn't).

In a dichotomous, up-or-down, yes-or-no vote (aka Option1 -vs- Option3), the Debian dev community is split 60/40 (or 40/60, depending on one's POV) on the issue of systemd. When a large plurality of your engineering team tells you that you're doing something fundamentally wrong, dismissing their concerns with “we don't need no steenkin' conversation” bespeaks a complacency bordering on negligence, all the moreso when when your actions have very, very large consequences. (Google “Challenger disaster” for more information.)

Which leads me to...


Debian isn't other distros
Every time I see someone spout some variation of the bandwagon fallacy, or refer to Arch as a “major” distro, I have an urge to do harm.

News flash: There is exactly one Debian, and nothing--nothing--compares to it.

NASA doesn't run Arch. Amazon and Google don't rely on Mageia.

In terms of sheer impact on both the larger LinuxSphere and the global economy, there are exactly two “major” distros: Debian and RedHat. (SUSE is a very distant third, and everything else is just noise.)

A change in Debian affects mission-critical and life-critical software across the globe, touches literally tens of thousands of organizations, and ripples through a hundred derivatives and spinoffs.

So no, it doesn't matter, not even a little, whether your desktop machine boots a few seconds faster or “seems to work ok” under systemd. The cost of downtime on a hobbyist machine is all-but-unmeasurable, whereas the cost of downtime on a scientific supercomputer is somewhere between large and catastrophic.

Speaking of costs...


Change costs, and big change costs big
There's a reason why sysadmins in large organizations are routinely among systemd's biggest detractors.

Downtime is expensive in terms of both time and money. So is re-training. So is rewriting gigabytes of artificially-obsoleted documentation. Add them all up, factor in the associated opportunity costs, multiply by a planet's worth of installs, and before you know it, the cost to the global economy associated with systemd deployment reaches into the billions (or thousands of millions, if you prefer) of dollars/euros.

And for what exactly?

Even if systemd were a demonstrably superior technology (which it isn't), adequately spec'ed (which it isn't) elegantly designed (which it isn't), well-coded (which it isn't), properly documented (which it isn't),or developed by a responsive and responsible community with a history of delivering robust and reliable software (*cough*pulseaudio*cough*), systemd would still be at best problematic, for one simple reason: it's insanely expensive to implement, particularly given the fact that it doesn't solve any actual problem.

Insofar as I'm aware, no one has ever articulated a value proposition for systemd that addresses its implementation costs, or comes remotely close to calculating a payback period. More to the point, no one has successfully articulated any value proposition for systemd that goes beyond “it's better” or “it's more modern.”

Global warming, antibiotic resistant bacteria, oilspills, and nuclear accidents are all “modern,” but that doesn't make them good. And “better” is a meaningless term until and unless one specifies a metric or quantitative criteria that can be used to measure “better” in a systematic and reliable way. Otherwise, “new and improved!” is just marketing hype.

At the end of the day, the crux of the systemd question comes down to a matter of how much Unix one wants in one's Linux. Casual users and hobbyists probably won't care. Professionals will care deeply and passionately.

Recent Techrights' Posts

New XBox Leaks Probably Serve to Confirm XBox's Collapse (Many More Layoffs)
It's very much consistent with what many other sites have reported lately
 
Slopwatch: Serial Sloppers, Google News Gifting Slopfarms, and Fake News/Plagiarism About "Linux"
Google itself is a slop pusher these days
Qualcomm, the New Owner of Arduino, Blasted for Its Software Patents Tax on 'Smartphones'
A lot of Qualcomm's patents are on software. We wrote about this in prior years.
XBox Layoffs Rumours, Downtime, and Criticism From XBox Co-Founder
"everyone is ditching the xbox."
Links 10/10/2025: Honoring The Legacy Of Robert Murray-Smith, Many Articles on the Hey Hi (AI) Bubble
Links for the day
Gemini Links 09/10/2025: October Gothic and Reading Middle Earth Role Playing; C and Ada
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, October 09, 2025
IRC logs for Thursday, October 09, 2025
Links 09/10/2025: Farewell to Jane Goodall, California Bans Algorithmic Price-Fixing
Links for the day
Gemini Links 09/10/2025: Lost Wages and a Saga Of Continuing To Use Palm PDAs
Links for the day
Richard Stallman's Talk in Helsinki is Done. Tomorrow Göteborg.
There are scarce details in Finnish about Dr. Stallman's talk
The Slop Song
The train wreck marches on
LLM Slop/Advanced Plagiarism Flooding the Zone With Capital That Does Not Exist
Many publishers out there still participate in this bubble instead of calling it what it is
Links 09/10/2025: Sacked Microsoft Workers Make "Sackbird", IBM Taps CockroachDB for PostgreSQL
Links for the day
"Happy Hacking Day" Richard Stallman Talk This Afternoon (From 14:00 to 16:00) at Haaga-Helia University in Pasila
Richard Stallman in Helsinki, Finland
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, October 08, 2025
IRC logs for Wednesday, October 08, 2025
Links 09/10/2025: Impact of Microsoft Layoffs, More Data Breaches
Links for the day
Gemini Links 09/10/2025: Autumn Blues and C IRC Bot
Links for the day
Slopwatch Appreciated by Real Authors of GNU/Linux Articles
We do try to keep on top of those things
Upgraded R.R.R.R.R.R. Today
The Web of 2025 is full of garbage, not limited to slopfarms
Freedom From Proprietary Prisons
Forking always an option
IBM's Watson Died in 1956, Now Watson Dies Again
IBM is becoming just a reseller of GAFAM and other stuff
Slopwatch: LinuxSecurity, UbuntuPIT, and Google News
We've also just noticed more slop from UbuntuPIT
Microsoft Says That Constant Mass Layoffs Are Success, the Media Isn't Buying This Microsoft Narrative Anymore
If people in the media feel an obligation to repeat whatever lies Microsoft tells, what point will there be to the media?
Links 08/10/2025: "Mali Puts Free Speech on Trial" And Apple Enforces Dictatorship
Links for the day
Links 08/10/2025: ‘Death to Spotify’ and Law to Ban Loud Commercials on Streaming (Dis)Services
Links for the day
Links 08/10/2025: Real Innovation and Nina.chat is Dead
Links for the day
Links 08/10/2025: Y2K38 Bug is a Vulnerability, Chat Control in Europe a Threat
Links for the day
Microsoft Windows is No Longer an Operating System, It's Surveillance Project
Why is this even legal to preload on PCs outside the US?
How and Why Once-Legitimate Sites Turn Into Slopfarms
Many sites will go offline and many social control networks will shut down once they realise or even openly admit they spend money and time gardening a bunch of bots and slop
UbuntuPIT Became a Slopfarm and Gnoppix Tarnishes Its Own Brand With Slop
It fits all the characteristics of mildly-edited (if at all) slop
Slopwatch: Linux Journal and Other Slopfarms
GAFAM needs to go the way of the dodo
Gemini Links 08/10/2025: "Seek Seek Revolution" and Gradient Backgrounds
Links for the day
Qualcomm Arduino Takes Aim at Raspberry Pi
Qualcomm is a Microsoft partner
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, October 07, 2025
IRC logs for Tuesday, October 07, 2025
Stagnation of the Economy and What Free Software Can (or Could) Do For It
If your economic model is based on a pyramid of lies, it won't last very long
Social Control Media is Sinking
it would rightly seem like the era of centralised "social" sites (they're not social, they're about controlling the users) is ending, not overnight but gradually