Hehe [LWN.net]

Hehe

Posted Sep 23, 2025 17:11 UTC (Tue) by archaic (subscriber, #111970) [Link] (2 responses)

Or rather, use an enterprise OS for "important systems". Systemd works fine across our 2500+ servers in all manner of different configurations and different major versions.

Hehe

Posted Sep 23, 2025 18:48 UTC (Tue) by ju3Ceemi (subscriber, #102464) [Link] (1 responses)

Do they not use systemd ?

Hehe

Posted Oct 7, 2025 10:40 UTC (Tue) by jengelh (guest, #33263) [Link]

They do use systemd. But not Debian ;-)

Hehe

Posted Sep 23, 2025 18:42 UTC (Tue) by MortenSickel (subscriber, #3238) [Link] (6 responses)

Two questions:
1) From where is the quote? I'm not able to find it in the text above.
2) What should be the alternative to systemd?

Hehe

Posted Sep 23, 2025 18:50 UTC (Tue) by ju3Ceemi (subscriber, #102464) [Link] (5 responses)

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112535...

"Regardless of what one's opinions may be, the fact is that the default
in Debian is network-manager for desktops and ifupdown for the rest,
so anybody demanding nothing less than perfection would do well to
stick to those defaults instead of being adventurous and then throwing
abuse when experimental things don't work."

As he said, everybody demending nothing less than a working network system would do well to stick to the default: network-managed for destkops and ifupdown for the rest;

Hehe

Posted Sep 23, 2025 19:02 UTC (Tue) by rahulsundaram (subscriber, #21946) [Link]

Your original quote is just not in there. The bug report is clearly making a distinction between systemd which is the default and systemd-network which is an optional non default component in that distro. Although the response from the maintainer is more dismissive than I prefer, the distinction shouldn't be collapsed in a misleading way.

Hehe

Posted Sep 24, 2025 18:24 UTC (Wed) by MortenSickel (subscriber, #3238) [Link]

I didn't see what you put in quotes there, and I'm still waiting to hear what should br the better alternative to systemd.

Hehe

Posted Sep 25, 2025 2:34 UTC (Thu) by mirabilos (subscriber, #84359) [Link] (2 responses)

Next release, systemd will declare one of the two other methods obsolete and unsupported, and where are you left then?

Hehe

Posted Sep 25, 2025 12:27 UTC (Thu) by pizza (subscriber, #46) [Link]

> Next release, systemd will declare one of the two other methods obsolete and unsupported, and where are you left then?

You are confusing "systemd" with "Debian"

Meanwhile, Debian obsoletes/removes features with every single release.

Hehe

Posted Sep 26, 2025 3:37 UTC (Fri) by ATLief (subscriber, #166135) [Link]

Presumably Debian would continue to support the version series that was included in Stable for the remainder of its support period. That being said, bigger projects almost always provide plenty of warning, and many of them even maintain older version series themselves.

Hehe

Posted Sep 25, 2025 2:33 UTC (Thu) by mirabilos (subscriber, #84359) [Link]

It’s a bit sad, but OTOH now the systemd users get to feel how bluca and Co. are like, the same way the proponents of init system diversity got to feel for years and years.

But independent of that… if there’s a regression in a documented functionality, especially a segfault (something that, other due to user-caused stack exhaustion in things that do allow user-controlled recursion like generic programming languages, is always a hard bug in the software itself), then that ought to be fixed before it spreads. *sigh…*

That handling… sure is skirting the lines of the SC.

Hehe

Posted Sep 25, 2025 7:30 UTC (Thu) by parametricpoly (subscriber, #143903) [Link] (2 responses)

Systemd is good, but the incompetent maintainers like this are the reason for bad reputation.

Hehe

Posted Sep 25, 2025 8:09 UTC (Thu) by em (subscriber, #91304) [Link] (1 responses)

Yeah, sure, calling people whose work everybody benefits from "incompetent" is going to help. Just like creating a thread with "Hehe" as the title. And then people are not surprised that maintainers do not react quickly. I am amazed that they are not in full burnout already.

(In)competence

Posted Sep 25, 2025 20:56 UTC (Thu) by smurf (subscriber, #17840) [Link]

Competence manifests in more than the ability to code.

When you're as dismissive and abrasive as bluca to people who happen to hold different opinions, sorry but I call that incompetence. Plain and simple. Not in coding but in relating to people, and in understanding their concerns.

Also, let's be brutally plain here: regardless of *any* nonsense in your config files, it is *never* OK to segfault, and by extension it's also never OK to dismiss a segfault-inducing bug as unimportant.

Not if you're a core system component.