Ive been runing Debian 12 (kde) since bookworm was released and am loving it.
I have recently discovered Devuan which seems to be Debian without systemd - what is the benefit of removing this init system?
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I was reading about Slackware today and it seems their init system still uses system V and lots of scripts.
So I'd definitely recommend that OS to anyone curious about the old style of init system.
Slackware uses the sysvinit program, but doesn't have System V-style scripts. Which is somewhat confusing, but sysvinit is a basic init program that will just do whatever
/etc/inittabtells it, so you can write your startup scripts to work however you want.Slackware uses what people tend to call a BSD-style init, but it's nothing like the modern BSDs, nor the older BSDs, not really. If you use Slackware, you'll learn how Slackware's init system works, but that's about it.
Ah my mistake. I'm just generally curious about what distros use an alternative to systemd (not that I have any issues with systemd myself but I like variety).
So I googled what init system Slackware uses and read this page.
http://slackware.com/config/init.php (no https)
They mention several scripts on that page and that's why I thought they use scripts.
But I haven't actually used the Slackware yet. Suppose I should though since I'm interested.
No, you're right that it has scripts, they're just not the scripts used by SysV-style init systems. They have different names, are in different locations, and are executed differently.
I used Slackware for several years back in the 90s, and from that experience I'd recommend against learning it. I mean, with VMs today it's simple to try new distributions, so go for it, but I'd put it waaaaay down the list of distributions/operating systems to try. If you have anything else you're interested, put it first. Slackware is standard Linux so there's nothing really special you'd find when using it, and it's just a painful experience in general. I think some people will argue that it helps you "really learn Linux", but I don't think so. It just helps you learn Slackware's idiosyncrasies, and learning pretty much any other distribution would be more beneficial than that.
Slackware has advanced from when I used it in the 90s, but only barely (they have a network-based package manager now, I guess, although it proudly avoids dependency resolution!)
Oof that stance on dependency resolution is a big no for me. As much as I hated building gnome from source it was amazing that Gentoo can do that in a single command.