this post was submitted on 10 Aug 2023
341 points (96.7% liked)
Linux
48074 readers
720 users here now
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.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
systemd is cancer.
Ah yes, a piece of software that people can choose to use or not use is just like an unexpected, devastating disease that no one in their right mind would ever choose to have and that causes huge amounts of suffering and can be incredibly difficult or impossible to treat.
Yep, cancer patients and survivors totally think having cancer is just like using systemd. 🤦🏻♀️
Except you're NOT free to choose, every major distro shoves it into your face
And it BEHAVES like cancer, that's what I meant
You can't have been using Linux long if you think this is what not being free to choose means.
Don't use a "major distro", use one made by likeminded folks. Example: https://www.devuan.org/
Why do major distros have to make only the decisions you want them to make? Bugs the shit out of me that Gnome is the default desktop damn near everywhere, but so what? Are you paying their bills or otherwise contributing to some degree that they should change their decisions to suit you?
Here's a list from 2021: https://www.howtogeek.com/713847/the-best-linux-distributions-without-systemd/
Another from2022: https://itsfoss.com/systemd-free-distros/
Or build LFS without systemd.
Or build Arch yourself without systemd.
Want to remove it from Ubuntu? Here you go. I'm sure there are similar howtos for most major distros.
The freedom of Linux and FLOSS is that you can roll up your sleeves and do it differently if you want to. Not that anyone owes it to you to do it for you. For that you have to hope other folks who have rolled up their sleeves have the same opinions you do - and in this case, some do!
I have no concern about your opinion on systemd. But you seem really confused about what freedom is.
How is that different to when every distribution shoved their implementation of sysv-init into your face? You were never free to choose your init, it always came from the distribution. You could (and still can) replace the init system, if you are willing to do the work involved.
That's the whole point: Nobody is willing to do the work for one distribution, if they can just improve systemd and fix a whole bunch of distributions at once. That's why developers flock to the systemd umbrella project to implement their ideas there, which is why systemd keeps getting cool be features for the plumbing layer of Linux -- which is far more than just the init system.
Thinking about it from your point of view, maybe MS was right and Linux is a cancer too. Technically it behaves similarly to systemd, since most Unixes are actually Linuxes nowadays (excluding BSD ofc, but they are still in the minority, similarly to alternatives to systemd). It even is a binary blob as well!
Should every distro use/develop a different kernel? Should we focus our resources on providing alternatives and again have a multitude of different Unix versions, every incompatible with each other? Isn't it better that we have this solid foundation and make it as good as it can be?
Overall I think standardization of init is not so bad, just like adopting the Linux kernel was. It is actually quite nice that you can hop from distro to distro and know what to expect from such a basic thing as init process.
Anyways, in Linux land you actually have a possibility to replace it. Granted, it is not as easy, however there are plenty of distros that allow you to ditch systemd in favor of something else.
Every major distro uses systemd, because before that it was nearly impossible to properly implement things that distros have to provide.
Most startup scripts were incredible set of hacks to make services behave. Those were very inefficient (they could not be efficient being shell scripts calling other commands for various simple repetitive tasks) and would often break when circumstances were different from ideal.
Systemd just makes building Linux distribution much easier, and the resulting system is more reliable, more consistent and more flexible. Why would distro developers chose anything else?
Missing my point. It's a shitty comparison that is incredibly insensitive towards people who suffer with cancer and their friends and family.
"I went to McDonald's and they kept shoving burgers and fries in my face! smh"
How on earth can you say that? Systemd, while not perfect, creates a system that helps newbies come in and understand Linux, helps Linux grow. Afterwards they can shift to a non systemd distro, but systemd provides a valuable tool.
Hmm that's an interesting take on systemd. Not sure if anyone would be pivoting to a non-systemd distro after experiencing it... Well I've been using Linux before systemd and I wouldn't switch back to what we had before simply because it makes my life easier in so many ways.
But yes, I see how less fragmented and more approachable a systemd distro will look for a beginner.
Not sure about this.
A new user probably don't care (and rightly so) about how a certain service is started or stopped, it just need to work, which was true even before systemd.
Actually, its an opaque system that makes it much harder to understand what is going on because it's a declarative file that is consumed in a non-obvious way by code written in c which is not going to be remotely comprehensible to them. Most people are apt to google for the magic incantation that appears to match their problem without understanding anything.
Not only are simple and easy not the same they are opposing interests in most actual practices.
I had an extremely simple Funtoo (Gentoo derived) installation it had bios boot -> 4 line grub.cfg with explicitly specified kernel and initrd. Making a kernel involved cding to the directory where the new kernel was making it copying a file and changing a text file to point to the new kernel. Understanding how software was built was work because you actually have to specify things you want vs don't want but it was extremely simple. In fact everything was like that from boot, build, services. Anyone who took a few hours could probably trace it from the first line of grub.cfg to the last service starting up.
I have a more complicated void install that uses rEFInd -> zfsbootmenu . When a new kernel is installed dkms rebuilds modules and dracut handles preparing the boot up, updating automatically creates a snapshot and zfsbootmenu makes it possible to boot into a prior version of your OS. I set none of it up it was configured by an installer and when I messed something up it was a LOT more work to understand how it works and it was impossible to trace it from end to end without googling and reading documentation.
I have a single board computer running a derivative of Ubuntu. The official installation procedure that you are supposed to be able to do remotely doesn't work at all so I plugged a monitor and keyboard to it loaded the image to a sd card and booted and ran the commands it said to run and it works without issue. It's opaque but easy to use and if it ever doesn't I'll probably just reinstall the image from scratch and run the commands it said to run.
I would recommend Ubuntu/Mint if you just want to do things. If you actually want to understand it for its own sake I would recommend something simple instead of easy.
And it would be cancer because...?
Same reason as for all those years these old people are holding a grudge for...
It is not Unix philosophy (nothing is these days), it does not solve any problem they ever had (it does), it is no improvement over what we had before (it is) and even makes some broken and moronic things harder (it does), it is insecure (it improves overall system security), and it is one monolithic blob (it is not). Before systemd nothing depended on the init system (true, but then it did nothing useful that made having such a dependency worthwhile), and before systemd we were all free to use other init systems and distributions did not pick one for their users (they always did, offering additional inits only as unsupported iption just likenthey do now).
That's the typical list you get.
Oh, and it was shoved down all our throats by the mighty Lennart himself, backed by several multi billion dollar companies that brided thousands of distribution developers to destroy Linux (it was not).
Funnily enough it is pretty much the same BS we had when that monster of complexity called sysv init was introduced into distributions, replacing a simple script with a forest of symlinks. Of course the community was much smaller then and so we had a loser number of idiots to shout at everybody else.
It seems that, in many people's view, it's better to have janky scripts starting systems, having to delegate logging management and service monitorization to the services themselves or cumbersome tools poorly used by most distros such as logrotate? Systemd offers a good thing, easy configuration and IT DOES fix a LOT of issues. People who never tried it won't see how better it is, just try it... like I did 10 years ago.
One of the moments where we see the true power of systemd is when we use it for containers and suddenly realize that the tools used to manage the system such as
systemctlandjournalctlcan be used to inspect and affect a container without even having to enter it. Another equally interesting moment in the systemd journey is when you've an ARM system with 512MB of RAM or even less and you figure out that it will save you precious resources for other things.Not at all: I listed the arguments you will get for that question of yours. They all are bogus, as I tried to explain between the parens.
I also updated my reply to make it more clear. It wasn't "aimed at you".
The person you replied to is not criticizing systemd he's criticizing systemd detractors.
http://web.archive.org/web/20140428103624/http://boycottsystemd.org/
Just to name a few reasons.
The fact the original website is no longer available tells us a LOT about it. Maybe the server running it crashed because it didn't have proper service monitoring... or all the init jankiness was wasting so much resources the guy paying for the server run out of money :D
Now in all seriousness: I don't disagree with most points however, systemd also provides a TON of functionally that was never this easy and stable. Also if you consider the grand scheme of things Docker and whatnot are a bigger virus than systemd is or will ever be and the irony is that systemd does run containers with less overhead :).
No need to drag that BS from the archives. It was never correct nor convincing.
Wow wonder what happened to those guys?:)