It sucks to hear that a project like LFS is forced to drop System V support. I never was a fan of systemd, so this is a bit dissapointing, albeit understandable.
I hope something similar doesn’t happen to Slackware…
Fuck Systemd
Yah! Screw them 20 line unit files. We roll with 500 line bash scripts.
/sarcasm
U mad bro ?
I just don’t like that Cthulhu like creature of unimaginable horrors called Systemd that thrusts its tentacles into every subsystem.
The cancer spreads.
Systemd abstracts so much stuff away that it does not feel like learning Linux “from scratch” :/
(I like having it in my daily driver, but it’s sad LFS had to drop support for a “lower level” init system)
(I like having it in my daily driver, but it’s sad LFS had to drop support for a “lower level” init system)
It’s not lower-level, it’s just worse.
I’m not a huge fan managing an OS with system V. but in a educational context it effectively make way more sense than systemd
From the mail it doesn’t exactly look like “upstream dependencies on systemd” but rather like a lack of features in sysvinit:
The second reason for dropping System V is that packages like GNOME and soon KDE’s Plasma are building in requirements that require capabilities in systemd that are not in System V. This could potentially be worked around with another init system like OpenRC, but beyond the transition process it still does not address the ongoing workload problem.
So it seems a bit like sysvinit is simply a dead end and there is definitively not enough manpower for a transition to openrc/elogind/whatever…and it’s a good chance to consolidate the exiting workforce on a single version. Sounds all pretty reasonable to me. But it can’t really serve as example for systemd being an absolute requirement even for LFS now and them being “forced” to use it.
