Linux From Scratch ends SysVinit support

Post by simoncion » Tue, Feb 03, 2026, 3:50 AM UTC

ktm5j wrote: post #72

cf100clunk wrote: post #22

Earlier quoted context omitted.

If we look on LFS for its academic merit, I'm saddened that key historical elements of Unix/Linux design are being left behind, much like closing down a wing of a laboratory or museum and telling students that they'll need to whip up their own material to fill in those gaps.

From the announcement, it saddens them too: > 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. However the reasoning they provide makes sense.. It's hard to build a Linux system with a deskt…

Post by simoncion » Tue, Feb 03, 2026, 3:53 AM UTC

acdha wrote: post #58

eikenberry wrote: post #17

SysV init was the overengineered cousin to BSD init and I never liked it. Easily my least favorite of all init systems I've worked with over the last 30 years. On the flip side, daemontools or maybe runit were my favorites. Lots of good options for init/supervision tooling over the years and SysV was not among them.

SysV was this weird blind spot for many years. I remember installing daemontools on the OpenBSD server my office ran on because it was nicer to work with, and thinking that the Linux world would switch to avoid losing that particular feature war with Windows.

Post by anon7000 » Tue, Feb 03, 2026, 4:04 AM UTC

p_ing wrote: post #113

its_magic wrote: post #109

Earlier quoted context omitted.

I have been saying for years that Microsoft would eventually deprecate WinNT and switch Windows over to a Linux foundation. Things seem to be slowly but continually moving in that direction.

Makes no sense to dump a superior kernel and executive for Linux. The Win32 layer is the issue, not the underbelly.

Post by simoncion » Tue, Feb 03, 2026, 4:11 AM UTC

hparadiz wrote: post #48

antonyh wrote: post #27

All I want is init scripts and X11, but the horizons are shrinking. I've already compromised with systemd, and I don't like it. I see BSD in my future, or at least a linux distro from the list here https://nosystemd.org/ - probably Gentoo. Nothing to stop me, absolutely nothing at all. I just need a few days free to backup/wipe/reinstall/reconfigure/restore_data and I'll be good. Better make that a few weeks. Maybe o…

OpenRC on Gentoo works great. I have a full bleeding edge Wayland KDE Plasma with Pipewire setup that I game on. OpenRC recently added user "units" aka services running as a user after a session start. Something that many new GUI user space applications rely on for various things. There are growing pains. https://bugs.gentoo.org/936123 Especially when upstream hard requires systemd. More annoying when there's no real…

  #!/sbin/openrc-run
  
  command="/usr/bin/rsync"
  command_args="--daemon ${RSYNC_OPTS}"
  pidfile="/var/run/${SVCNAME}.pid"
  
  depend() {
   use net
  }

Post by ahartmetz » Tue, Feb 03, 2026, 4:23 AM UTC

LeFantome wrote: post #138

tapoxi wrote: post #24

Earlier quoted context omitted.

I don't have a dog in this fight but I find it funny that the anti-systemd crowd hates it because it doesn't "follow the Unix philosophy", but they tend to also hate Wayland which does and moves away from a clunky monolith (Xorg)

This one bothers me too. Systemd and Xorg are very similar in many ways. I do not know how you hate Systemd and love Xorg unless your real problem is just change. And, while I like Wayland, I think that liking the Wayland architecture should have you disliking Systemd. But that is just me.