If you do more than just boot up your machine and do typical consumer stuff like watching or even editing videos, surfing or writing emails and letters then you will at some point have a need to start and stop services, write a script to reset permissions at startup for a piece of software that won't play ball etc.
Apart from philosophical and security concerns, I have over time amassed quite a collection of startup and shutdown scripts on my Slackware boxen. I prefer to be able to have full control over what my machines do and hand crafted and edited scripts have never let me down so far. If it's written correctly, it works and does exactly as it says on the tin. That's the beauty of an old-fashioned operating system like Slackware. You may be running a VPN server, offer VNC or ssh login and whatnot. The most reliable way to control them is via your own scripts - and you will know where you put them, thereby learning more about the system you're using. I'm afraid systemd is more of an abstraction layer that will separate users from understanding what us actually being called, what is actually going on under the hood. It may be fine for professional admins who, once they have learned the new commands, will know what they're doing as they know their Linux, but for a lot of private users this will just be a step towards another 'walled garden' operating system that they don't understand. Of course, many don't want to and only want to use an appliance that does the job, and that is fine. It is dumbing down nevertheless and potentially dangerous, in a time when everyone needs to understand the implications of the technology they're using, not the least to safeguard themselves and their families.
Anyway, if you're reading this you most likely care about what init system you're using and what it does. You will also know the reservations that have been expressed against introducing the systemd kraken into distributions too rapidly. This exercise is merely to try and take stock of what's left to run for those of us who do not wish to have an init system foisted upon us, for whatever reason. You may know most or all of these distributions already, certainly if you're an avid DWW reader, but a listing may be helpful to some nonetheless. So here we go, in alphabetical order and without attaching any value judgement:
This distribution is based on Debian Testing but with a difference. The developer announced antiX would not be following Debian with the implementation of systemd and that sysvinit will continue to be the default init system in antiX. The current testing images of antiX 15 can be found here on Sourceforge and are rock solid. I have tested both previous beta releases as well as the 14 RV (full) images and in fact they appeared to be even smoother than the previous release. Don't ask me, it's a while ago, but lots of small things made the difference in my opinion, such as the inclusion of Wicd for network connections. I have reviewed antiX twice on this blog and may have been a little hard on it. Antix is definitely recommended.
The full version comes equipped with very nicely done JWM and Fluxbox window managers, but all other desktop environments available in the corresponding Debian repositories can be installed. The usual caveats about dependencies apply. Depending on what you install you may end up with systemd anyway, but nobody would install GNOME 3 on antiX, right?
CRUX is definitely for the more advanced among us. It gives users a minimal system with compilers and all the necessary system libraries and tools by default install, with Openbox for window manager. As part of the install you compile the kernel. As this is a source based system it will get replaced by more optimised code as updates come out - if you choose to set the correct compiler flags. I think of it as somewhere between Gentoo and Slackware. The ports system has something going for it but precompiled packages are also available from the community. CRUX is x64 only but several alternative architectures as well as CRUX ports for OpenBSD are offered and maintained, again, by the community.
The website offers a comprehensive install guide and a wiki section. You can read my more in-depth review here.
This is an interesting one. It's not so much a distribution per se yet than the goal to be able to offer a base that allows users to run Debian 8 "Jessie" without systemd. "We are working towards a stable, production ready fork of Debian Jessie, free from the entangling web of dependencies imposed by systemd.
One can just migrate to Devuan by installing devuan-baseconf.deb which will re-configure the system with our source repository".
If you like Debian but would like another alternative to run it without the intrusion of a new application that is spreading its tentacles throughout the system you could make a difference by supporting this project with a small donation, as yours truly has.
Funtoo is a variant of Gentoo Linux that offers utmost customizability and optimization at compile time. It uses a ports tree system inspired by the BSD's and more importantly for us, it does not force systemd on its users in any default install. The developers have managed to make GNOME work without relying on the daemon so users will have the option of running the Shell as well. You can have your cake and eat it if GNOME 3 is your preferred environment.
The LinuxConsole is another independent Linux system, just like CRUX, that is not based on anything else. It comes with LXDE as default environment and offers an extensive choice of software installable as modules. No need to compile anything so the entry barrier should be lower than with CRUX. It's a fairly basic system that does not need systemd but which seems strangely modern and good-looking in its simplicity. The LinuxConsole offers media to be run as liveCD, liveDVD or liveusb or can be installed. It's first and foremost intended as a desktop and gaming platform or for educational use for kids but is so light weight it can run on a Pentium 2 which should make it interesting for all sorts of user groups.
Interestingly it also includes kdelibs by default so you can run those favorite KDE applications of yours like ktorrent.
Linux Mint Debian Edition (LMDE)
LMDE 2 offers a Debian install without systemd as the developers at Linux Mint decided to stick with the old init system for the Debian edition - for now. This was great news at the time as it basically offers an easy point of entry into a fresh install of "Jessie" without having to end up with systemd by default which would have entailed some major surgery right after the install to replace it.
Images are available with the Cinnamon and MATE desktops for both 32 and 64-bit architectures which may suit particularly beginners better than starting out with a more barren window manager. LMDE 2 will be tracking the current Debian stable for life as opposed to its predecessor which was a rolling distribution based on the Testing branch.
Manjaro is based on Arch Linux which was among the first to adopt systemd. They're usually drawing heavily on the Arch repositories and are sticking quite close to it but apparently a community maintained Openbox edition provides openrc as an alternative startup management/ init system.
PCLOS has been around for quite a while by now and could almost start to qualify as one of the oldtimer distributions, not counting Slackware and Debian of course! Anyway, the distro is remarkably easy to use and has been popular with beginners and users of all skill levels over the years but really seems more aimed at the consumer. That is fine, we like PCLOS very much here and had a good few years with it. Actually, there aren't many distributions I have run longer.
They have also decided to stick to the old fashioned way and not jump on the systemd bandwaggon. This distribution is a solid alternative and offers images with KDE, LXDE and MATE desktops (and sometimes other community spins). You can read a rather old review of mine of the Openbox edition here.
This one is a new distribution from Turkey that is developed independently, i.e. an original effort not based on anything else. It's a continuation of the Pardus Linux distribution which was well received in its time. Unfortunately I don't know enough about this little gem except that Pisi is using KDE as default user interface, has its own package manager (called Pisi) and is squarely aimed at the desktop. So far it is still systemd-free.
There's a reason why Slackware is seen as conservative and that means it's not jumping head first into uncharted territories, or unproven technology, because someone else said so. Pam for example has still not made it into the distribution, same as Pulseaudio, although there are builds to fool the system into thinking it's installed to satisfy dependencies and software like Skype. Perhaps due to all the changes around the move to Qt5 and KDE Plasma 5, the linux kernel and systemd there hasn't been a release in 19 months but tracking the current branch works fine together with a few choice packages from alienBOB and Slackbuilds. Read a review of 13.37 here.
No systemd here, and this of course also goes for all derivatives like Slackel. Vectorlinux and Zenwalk releases based on Slackware 14.1 are quite old now but Zenwalk has testing images from this year for the (for them) new x64 architecture based on Current and Xfce 4.12 has recently arrived in the repos.
SMS deserves a mention for a Slackware based server that is set up for many tasks out of the box and comes with an eFax service. Easy to control via scripts that can be edited through the webmin GUI.
Void Linux is a relatively new arrival that uses runit as the default init system. It is an independent, rolling release distribution and they've managed to package GNOME 3.16 without requiring systemd, obviously. May have something to do with Funtoo. Same tricks? It just goes to show that it can be done and all the dependencies between GNOME, network manager and systemd in other distributions were really made out of choice, not necessity.
So far it seems it is mostly the more advanced distributions that are offering init-freedom. However, Manjaro, PCLOS, LMDE and even antiX should offer a good start and be manageable for even relative newbies to Linux, or simply people who do not want to learn the ins and outs of compiling software and installing their own kernels.
There are a few other options:
Debian: I did not include this in the list as the default install will always land you with systemd and they could have made alternative install images with the old sysvinit available but didn't. Nevertheless, it is possible to replace it with a different init system and run Debian without it. Read How to remove systemd from a Debian jessie/sid installation.
The fact that this hasn't been made part of the official documentation speaks volumes. On top of that, you may not be able to install certain software like network-manager and policykit without ending up with broken dependencies as the Debian devs, unnecessarily, opted for implementing an intricate web of dependencies rather than making them recommended or optional. So, although it is possible to upgrade from "Wheezy" with sysvinit, you would have to change to Wicd (for example) to manage network connections graphically, but due to the different capabilities like VPN support that is not an option for many. The only way would be recompiling the affected packages without the requirement for systemd, which is where Devuan comes in.
BSD: PC-BSD seems to be the most desktop and beginner friendly system and also comes with its own new desktop environment called Lumina on top of offering all the other window managers and desktops people are used to from Linux in an easily accessible fashion.
All BSD types are an option as systemd has not cross-pollinated here. Here's a search result. And who knows, you might get to like some of the unique technological offerings like file system snapshotting better and find it more advanced than your previous Linux distribution.
Feel free to let me know of any others and I'll add them to the list.
The Kraken image is courtesy of openclipart.org.
Updated 20/07/2015 to add Pisi Linux to the list. A more complete list can be found here: http://without-systemd.org/wiki/index.php/Main_Page
https://wiki.debian.org/systemd - Installing without systemdReplyDelete
You can install debian without systemd or choice to remove it later.
Thanks for that link. However, it's not possible without some major surgery and effort which certainly does not make for an easy install and may prevent you from using certain software thereafter. When looking at https://wiki.debian.org/systemd#Installing_without_systemd [quote] it is possible to use preseed to replace systemd with sysvinit at the end of the install (This probably won't work if selecting one of the desktop environments that require systemd specific features however) [unquote].Delete
I completely remove systemd from debian 8 installation, and install sysvinit instead, without any problem.Delete
I use apt pinning to prevent systemd and related softwares to install again, and system works like my old debian 7 without any problem.
Personally I find all this fear of systemd unfounded, and the reasons I read everywhere are, It not adheres to "unix philosophy", and it a bit unstable (or presumably it)
But if you see, a lot of software were unstable on linux, or not adhering to "unix philosophy", It's only a matter of time they will be usable or more stable, and they have to be used to reach this state imo...
Sorry for my bad english, I hope to gave my concept about clear :]
Thanks for your article. :-)ReplyDelete
I have to say that knowing *exactly* how your system is starting up, which scripts are going to run, and the ability to chmod certain scripts to disable them is elegance all in itself. If it were not for the inconvenience of installing packages and some other Linux-related issues, I'd still be using Slackware. Slackbuilds is a great resource, but I'm lazy and like my dependencies figured out for me (to a point). I now use FreeBSD, and lately it's worked so well, it's almost boring. ;-)
I'm also looking forward to installing Void Linux on bare metal to check out the fixes to issues I (and others) reported. The Void Linux folks are pretty responsive and patient.
I was using Arch Linux when they made systemd default, and I have to say I didn't like it. I liked the previous way of editing /etc/rc.conf, but I guess the Arch folks thought that was too easy for the users and decided to let 'em have it. hahaha
Again, thanks for the article and the listing of systemd-free distros. :-)
Thanks for your articleReplyDelete
one more link
Archlinux under runit without systemd. Complete graphical environment is available, repository for pacman containing packages rebuilded without systemd, rolling release without particular problems, runit service maintaining by pacman etc etc.....
It not use systemd and It no plans to use in the future.