zlacker

[return to "Linux From Scratch ends SysVinit support"]
1. cf100c+n[view] [source] 2026-02-02 17:47:14
>>cf100c+(OP)
This is a mindblower. To quote Bruce Dubbs:

''As a personal note, I do not like this decision. To me LFS is about learning how a system works. Understanding the boot process is a big part of that. systemd is about 1678 "C" files plus many data files. System V is "22" C files plus about 50 short bash scripts and data files. Yes, systemd provides a lot of capabilities, but we will be losing some things I consider important.

However, the decision needs to be made.''

◧◩
2. soldou+a6[view] [source] 2026-02-02 18:14:49
>>cf100c+n
I am looking forward to UnixFromScratch and Year of Unix on the desktop as Linux more and more sells itself out to the overstuffed software virus that is System D.
◧◩◪
3. procon+D9[view] [source] 2026-02-02 18:30:34
>>soldou+a6
I know this is a bit tongue in cheek, but the systemd hate is so old and tiresome at this point.

I need my systems to work. Not once in my career have I experienced a showstopping issue with systemd. I cannot say the same for sysV.

◧◩◪◨
4. simonc+dU1[view] [source] 2026-02-03 03:38:57
>>procon+D9
> Not once in my career have I experienced a showstopping issue with systemd.

Like clockwork, we'd have a SystemD edge case cause a production-down incident at a (single!) customer site once per year. Inevitably, we'd burn anywhere from a half day to a week attempting to figure out WTF, and end up in some Github Issue where Systemd Project heavyweights go "Wow. Yeah, that looks bad. Maybe we should document it. Or fix it? IDK." and they'd do neither.

The project is full of accidental complexity that its maintainers can't be bothered to fix when unplanned interactions cause problems and are brought to their attention. I certainly don't blame them; that sort of work is only interesting to a very specific sort of personality, and that sort of personality doesn't tend to thrive in a typical software company.

I can also absolutely say that I've never had a showstopping problem with OpenRC in the nearly twenty-five years I've been using it. It's remarkable how reliable it is.

◧◩◪◨⬒
5. happym+rq2[view] [source] 2026-02-03 08:26:58
>>simonc+dU1
> and end up in some Github Issue where Systemd Project heavyweights go "Wow. Yeah, that looks bad. Maybe we should document it. Or fix it? IDK." and they'd do neither.

Do you have a reference? Not that I don't believe you, but I hated this behaviour from Poettering (although he seemed to more often blame the user) and we should totally raise up issue like this. It's a mature product that shouldn't have sharp edges any more.

◧◩◪◨⬒⬓
6. simonc+df4[view] [source] 2026-02-03 18:34:38
>>happym+rq2
I'm afraid I don't have a reference. The combination of the facts that the bugs are always damn obscure, there are so many Github Issues filed against systemd/systemd, $DAYJOB keeps me so busy with a huge variety of tasks, and the inappropriate lack of giveashit demonstrated by the project maintainers made me so angry means that the details just get blown out of my head.

> ...we should totally raise up issue like this. It's a mature product that shouldn't have sharp edges any more.

To whom would these issues be raised to? Based on my personal and professional experience, the SystemD maintainers (and -for those who are paid to work on the project- those who manage them) seem to disagree that "eliminating sharp edges" is a big priority!

[go to top]