Can someone tell me what's so bad about SystemD?
I hear mint is adding it next release and that's supposedly going to kill the OS.
GIF related I suppose.
1. Its main developers are self-entitled assholes that do not care about users (that means you) or their needs/problems. On top of that the main developer works for a company that is totally dependent on the USA army revenue. Thus causing concerns that this will be a easy vector for backdoors into Linux systems.
2. Initially it was a modern init system supposedly fast and straight forward. What they are building is a web of heavy bloated interdependent tools that try to do everything including taking over the functions of many programs that have nothing to do with an init system (thus OP's Pic)
Point 1 is silly. The Linux kernel alone is so big that it would be ridiculous to assume that there isn't at least one critical vulnerability.
Point 2 I agree with. It's horrible program design to take on so much functionality in one program.
Does anyone have a graph/analysis that shows what exactly systemd slows down? Is it really something I would notice? I mean, okay, it's bloated, but how much of an issue is it on modern hardware compared to whatever else you can compare it to.
Point 1 is silly. The Linux kernel got a lot of various contributors. Systemd will claim hundreds of contributors but only 10 of them contribute to it seriously.
I'll add a 3 :
They don't fucking get how sudo works and want to implement something else to replace it. Which makes me asking two questions : how the fuck can they be that retarded ? What the fuck have sudo to do with an init system ?
I don't see what the number of "serious" contributors has to do with it. There is a large number of lines of code in the kernel, so it is only logical to assume that bugs exist.
Lennart is now claiming that systemd is a "core OS" to build on top of. It's a mammoth of a program for sure.
Also, the UNIX way is "make the program do one thing and do it right".
Systemd is a huge dependence-hungry bloated sub-system whose developers used the kernel argument "debug" in such way it spilled so much shit into the prompt, it killed the kernel due to timeouts.
The devs are stupid assholes and most major distributions are adopting it since it solves the modern-days problem of init being script based and single-threaded.
>There is a large number of lines of code in the kernel, so it is only logical to assume that bugs exist
There is bugs, sure, but I'm pretty sure there's more people, proportionally, that reviews the kernel source code than the systemd code
Bill Gates' EEE (embrace, extend, extinguish) methodology is being applied to Linux as we speak. Linux as we knew it was "embraced" by certain parties, is now being irreversibly "extended" by systemd, and is due to be "extinguished" in the foreseeable future.
>They don't fucking get how sudo works
Dunno about sudo, but Poettering declared su as "being a broken concept" recently IIRC.
>Lennart is now claiming that systemd is a "core OS" to build on top of.
What else is needed to prove that systemd is literally hijacking what we knew as Linux for the past 25 or so years?
There's no real issue other than it seems forced onto distro's as an init system. Some dev's have rebelled. It went downhill from there really resulting in a fork or two from the parent distro's, Devuan being the most famous and nastiest fork split, from Debian, so far.
>since it solves the modern-days problem of init being script based and single-threaded.
systemd is not the only init system who supports parallel initiation.
It was widely adopted because it made some key software depend on it. (read: gnome)
>UNIX is do one thing and do it right
UNIX philosophy since the inception has been: It doesn't need to be good or correct, but it has to be small.
It's never been about functionality, but about having a program do just one thing in order to make it as small as possible.
As hardware got more powerful, the small bit became less relevant but nobody told UNIX and UNIX programmers that the code had to start being good or correct. UNIX is crap and full of random inconsistent poorly made garbage where the only benefit to it is that it ported easily. Just like a virus. Just like the virus UNIX is, as well.
If systemd bothers you so much why don't you develop something that will be better.
Oh wait you tried
and all attempts were a failure
>the code had to start being good or correct.
Not if it breaks lots of things. Let alone if it threatens to hijack and/or destroy Linux as we knew it eventually.
As>>52387352 said, it has been being adopted by everyone and their dog not because it's better than its alternatives or because it's even good at all (which it isn't), but because of some cunning lobbying, shilling, and artificially conjured interdependencies.
>Literally everyone is already running systemd
http://www.gabordemooij.com/index.php?p=/escape_from_systemd (scroll down)
>many more smaller distros
Are you even trying?
systemd is supposed to be an init system, but it's slowly but surely taking over the entire OS. I'm pretty sure the GNU coreutils will be gone and replaced by systemd in less than 5 years.
It's like having your video drivers slowly replace your entire operating system "because everything gets displayed to the screen".
I've wondered why after so many years this feature wasn't implemented.
And it hit me.
Literally noone besides imageboard users needs this in everyday life.
I mean who else other than obsessive channers have a 1GB+ directory full of unsorted, unrelated imagery with cryptic filenames?
I'd say https://bugzilla.gnome.org/show_bug.cgi?id=655041
is a much more valid example of Gnome devs not wanting to pull their heads out of their asses.
Fuck them seriously.
>want to be able to enable hibernation after a rough history with it on linux
>add resume=/dev/disk/by-uuid/uuid to the grub config
>it works after the first reboot
systemBotnet is okay in my book.
GNU + Linux + Pulseaudio + systemd + Wayland + Vulkan will make Year of the Linux desktop happen.
Mark my words.
>If SystemD is so bad, why haven't people made their own alternatives?
At least I'm using Openrc.
Problem is when you install ubuntu for you fathers pc and then find out that it has been infested with systemd.
>yet use X11, one of the most bloated graphical protocols. Driver vendors still implement 1980s features that nobody even uses anymore. Network transparency is a farce since X11 clients draw themselves anyhow.
I'm actually glad that GNU never gave a shit about unix memesophy.
Thanks to this you get quality tools like GNU coreutils with proper error handling,instead of typical unixy "lol u fucked go figure it out))))) and emacs
I provided you a better example of gnome devs being human garbage.
>Nice attempt at using your brain
sorry can't think when the smell of curry and diarrhea your spread hits my nostrils panjeet.
Sorry but I have to agree with him.
Standards are there for a reason.
When you want to use OS X, you get hardware thats supported on OS X
When you want to use Windows, you get the hardware that's supported on Windows
When you want to use Linux, you should use the exact same fucking rule you applied to the previous operating systems yet you fucks love to ramble how Linux doesn't work on your cheap, plastic chinese garbage made by a manufacturer with no regard for hardware standards but instead estimating the quality of it by "that will do".
Just buy a high end dell. They're at least somewhat optimized to work with Linux.
But do you know how it works?
Or how to fix it when it breaks?
Or are you just going to reinstall each time a new systemd comes out
Sysinit=file is located in one place with the rest of the configuration files
systemd=config is located in 20 places,10 of which are skeleton that take over config, if you dont specify the service file before hand.Then it depends on if the service wants to parse your config that is on the letter of how to format a systemd service file
>only high end dell laptops ship with linux
>only high end workstation PCs ship with linux
Nicely memed, go back to your vidya
I don't understand why you think it's a joke.
Systemd's socket activation is indeed quite awful:
If you say "literally everyone" it means a full 100%.
Unless you meant "literally" figuratively and not literally - which should get you the death penalty for crimes against the English language.
I just started using GNU/Linux a few months ago but somehow I instinctively deeply distrust systemd, can't even tell why...
Can anyone enlighten me in this respect in terms of privacy?
Also anyone got experiences with Devuan?
Seems like the way to go for me now