Kolibri, which only needs a handful of RAM and disk space
post
Void, because it works really well on my super low-resource chromebook!
An hour in and no mention of Slackware yet?
No, but I use Arch btw.
Thanks for making me not the first person to mention slackware for once. I don't have any beef with systemd. It's just foreign to me. I installed slackware some time in the late 90s and found my life's calling.
Since you asked for OS and not Linux: OpenBSD and FreeBSD are beautiful systems w/o systemd. I would switch in a heartbeat if I wouldn't need Linux for work reasons.
This feels like an "I would switch to Linux if I didn't need Windows for work" comment from another universe.
Fair point. :-)
At the end of the day, the OS has to run the software/applications one needs to get shit done... if it is macOS or Windows, that's okay.
In my defense, I ran NetBSD for several years a long time back, and it was one of the best OS experiences I ever had. I am just old/pragmatic/flexible enough, to choose setups with less friction, if possible. ;-)
Still, I think it is a shame that Linux mostly took over the UNIX world and the BDS are left for hardcore nerds/embedding/game consoles and Solaris and co are not viable options anymore. Portable software and its stability benefited a lot from bugs detected on other platforms (OpenBSD was always a forerunner here).
BSD is to Linux users what Linux is to Windows users.
Not sure what you want to express. I actually used BSD a long time back, and the quality/documentation/coherence/beauty of the system are/were just on another level... Running Debian for nearly a decade now, because of compatibility (with hardware and software I need)... Linux improved a lot in the last nearly 3 decades and I am happy it exists, still I would be more happy if the BSDs would have stayed at least on an equal footing.
I think the comment speaks for itself. There wasn't anything deep behind it. It literally just mean "Linux users look at BSD users how Windows users look at Linux." Bewildered, mystified maybe? It's just lower on the "food chain", and they are surprised to see people using it because it's missing "X" feature they can't live without, for many people that being gaming. I'm in the same camp.
It was not a comment on the quality of the software, as I have never used it. I would love to tinker with it one day to see the differences, but I can't see myself ever switching to it, even if I admire/envy some of the better parts compared to Linux.
Thanks for clarification!
... and I think you are point on, by now, the ship has sailed. I could use FreeBSD/OpenBSD on servers, but I'd rather run Debian everywhere. On desktops and for day to day usage, the BSDs are no viable options anymore, they simply lack support for common hardware (Wifi etc.) alone and the BSDs will realistically never be able to catch up the chasm anymore.
I feel there's a similar relation between Mac :: Ubuntu (me) :: Arch.
I try to explain to folks that I have very little interest in anything outside of /home. I truly use Ubuntu because I like the desktop and Steam works and I have all the dev tools I need. But a certain type of otherwise competent Mac-using developer thinks I must be a 1337 h4x0r to even dare to use Linux for actual work.
Why should I not use systemd?
Contrarianism
When you want to feel special but not enough to go to the effort of using FreeBSD
If you have to ask, then there's no reason not to. It's people who tinker with their systems that encounter issues with it, or more often random annoyances that add up over tme to those memes.
When you're not using your computer
because the over 70 different binaries of systemd are "not modular" because they are designed to work together. What makes a monolith is, apparently, the name of the overarching project, not it being a single binary (which again, it's not)
Gentoo with OpenRC
This is the shit.
Gentoo is the best distro, can't imagine going back to binary blobs.
And it's so stable and easy to use.
It needs a solid CPU to update, that's a downside, but for me it's absolutely worth it.
System service managers like systemd, OpenRC, runit, or SysVinit often come down to user preference. While these systems are crucial for initializing and managing services on servers, where uptime, resource allocation, and specific daemon behaviors are important, their impact on a typical desktop or laptop is generally minimal.
For most personal devices, the primary functions of a service manager occur largely out of sight. As long as the system boots reliably and applications run smoothly, the underlying service manager rarely registers as a significant factor in the daily user experience.
For many, including myself, systemd simply works without much fuss. My choice to stick with it isn't due to strong conviction or deep technical analysis, but rather the simple fact that I've rarely, if ever, had to interact with it directly. For my personal desktop and laptop, it reliably handles booting, service management, and shutdown in the background. If it's not broken and isn't hindering my daily computing, there's no compelling reason to explore alternatives.
System service managers like systemd, OpenRC, runit, or SysVinit often come down to user preference.
And coding best-practice. And a philosophy borne of bad luck and bad software that aims to resist monoculture.
But that lennart kid is cool for a Microsoft employee.
I suppose that would be Android, since that's the only non systemd OS I use.
"systemd is the worst implementation of init, except all those other inits that have been tried from time to time" -Churchill, if he had been a nerd
What's wrong with systemd?
All I hear about it is that it doesn't follow the Unix philosophy of a program should do one thing and do it well. And while it does seem quite large and do a lot of things, out of all the times I have broken my system, systemd has never been to blame.
Edit: deleted duplicate comment.
It tries to do everything.
Think of a thing you want to do in Linux and there is a systemd plugin for it. Itβs not the unix way
Not everything is a file either. I don't see many complaints about that
Wait until you learn about the Linux kernel and the plethora of modules and patches
General principals are great until you take them to an extreme. There's always cases where you need to do something a bit different
Systemd is broken down into smaller parts. You don't need to use it for everything.
I personally do not like that systemd gets more and more integrated with other software. For example Gnome. That makes it harder to use that software on non systemd linux, or other OS.
Nothing, but it's new so people hate it. See also: PulseAudio, Pipewire, Wayland.
I don't care about the init system, however i do love void mainly because of the package manager.
I have to say as someone who uses NixOS I love systemd, because it makes a lot of things very easy. For example hardening services ( systemd-analyze security) or replacing cron (system timer).
Alpine.
Have used crux but using low end / old hardware results in almost permanent building software.
I wonder how far we are from CI drivers ala Nix that fork builds out to idle hardware like a distributed torrent network. As someone with three out of tree modules in use, there must be dozens of us I'd like to think.
Scans room
Windows 11.

Normie here, what's wrong with systemd?
Some people think it handles too many low-level systems. It's a valid concern because if systemd itself were to become compromised (like Xz Utils was) or a serious bug was introduced, all of the userland processes would be affected. People who are stuck in the 90s and think that the Unix philosophy is still relevant will also point out that it's a needlessly complex software suite and we should all go back to writing initscripts in bash.
Red Hat, the owner of systemd, has also had its fair share of controversies. It's a company that many distrust.
Ultimately, those whose opinion mattered the most decided that systemd's benefits outweigh the risks and drawbacks. Debian held a vote to determine the project's future regarding init systems. Arch Linux replaced initscripts because systemd was simply better, and replicating and maintaining its features (like starting services once their dependencies are running) with initscripts would've been unjustifiably complicated.
I agree with you, but please let's stop acting like there are only two init systems.
I hate it when people argue that systemd is better than init.d. So is everything else, I'm more than happy with OpenRC, and love it more than systemd.
There really is just one init system. Everyone and there dog uses systemd. It is the old people who hate change that are complaining.
I changed to OpenRC and I've never been happier.
Gentoo rules.
OpenRC has all the issues of systemd and none of the benefits
I can't say I understand your view point
What issues do you mean? And what benefits?
Nothing, it's just bloated but in practice if your system meets normal distros system requirements systemd isn't going to make that much of a difference in practical use.
Bloated when being run on a potato.
Luckily 99.9% of people do not compute on a potato.
https://wiki.aosc.io/aosc-os/retro/intro/
It can run on a system with 32mb of ram
As a user, why should I care whether the distro I use uses systemd? I use Mint and I don't remember having to interact with that kind of low-level nonsense. The distro maintainers can use whatever reasoning they want to pick these details.
If you are just a user, in that a computer is just a tool you use, then you're right, there's comparatively little reason to be concerened or even know about the underlying details of the system. If you go further and start making changes to your system, or even building more complex systems, over time you will find yourself forming quite firm opinions about various parts of the underlying system, especially if you've had experience with other options.
Tribalism exists in every circle, perhaps moreso in tech circles. Ironically anyone who hates on a distro could just switch, or build their own distro if they were so inclined, but it's often the hating that people participate more in than using their system. Use what works for you, and if it no longer works for you use something else.
As a user, why should I care whether the distro I use uses systemd?
Um, because as a user you may have to deal with services, or other systemd features?
Let's say you want to start ssh-agent when you login to your desktop environment. Well, there's a systemd service for that that you can enable, and on another distro you'd have to do it another way (autostart script or something).
Debian, installed without systemd as per the wiki. So far I've not hit any issues, whilst I've recently ended up diving through both kernel and systemd code to find the root cause of an issue I was hitting on one server. I could have just bodged past it, but I wanted to actually understand what the issue was, and what else it was going to affect.
Maybe a stupid question, but is the thing you did fundamentally different from Devuan?
I'm the same here. I don't know enough or care to know enough about systemd. I simply enjoy the minimalism of Alpine.
The downside is that I have to learn a bit more to make it work how I want but as a hobby I enjoy it.
When I first started with linux, Mint with systemd just worked for my laptop. For the people who are less computer literate, that should be good enough. They don't want to worry about how to make their computer work, they just wanna do basic computer things without hassle.
Debian that i haven't updated in 10 years


top 100 comments