Could simpletons like me have some information about what systemd is, why Debian and Ubuntu switched to it and why some people wouldn't want it?
Just links if you don't feel like explaining.
For now I found that (french) but I'm not sure if that covers everything that is needed to understand the "problem".
This might clear some things up a bit :http://without-systemd.org/wiki/index.php/Main_Page
Your article only talks about systemd-sysv but it also fail to mention it is also a dhcp client, a logger, dns discovery, uefi loader,
a firewall and more... all of this in PID 1.
How Debian adopted systemd is controversal in itself. They basically held a secret voting where they only showed as alternatives the old
They decided to adopt systemd while failling to consider alternatives such as runit and very few decided on the matter.
In fact, this alone led to Devuan.
As for Ubuntu, well at first they were against using systemd but as it is based on Debian, rather than forking,
they decided to accept Debian's decision to switch to systemd.
Some of the bugs that seriously make a cry are :https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658
If you think Debian cares about your privacy, you must read this.
This was a "feature" introduced by systemd when they would fall back to google nameservers.
This is a huge privacy issue but how the maintener answered the concerned ?
By calling critics google haters and linking to google's privacy terms, saying it is a company that cares about privacy.
In the end, nothing has changed and it is still falling back to Google nameservers when using systemd to this day.https://github.com/systemd/systemd/issues/437
Another Google related issue.https://github.com/systemd/systemd/issues/2402
You can hard-brick some non-compliant UEFI computers by simply doing rm -rf /.
Another bug i discovered when i used to be on Ubuntu 14.04.
Having this in /etc/network/interfaces :
iface lo inet loopback
And systemd will attempt to connect it and assuming it's going to have internet.
What's even worse is the fact it will wait 30 more seconds before it proceeds,
and this delay is completely arbitrary.
Another similar issue i found but this time on Ubuntu 16.04 using encryption.
Select the "encrypted" home folder upon installation and you'll have horrible boot times
because systemd adds an arbitrary delay of 1 minute and 30 seconds.
During this long delay, it does absolute nothingness.
Switching to Upstart fixes this issue and results in much better boot times.
I also want to mention that systemd is a major CPU and memory hog. (not as much as X11 but pretty close)
, is in a nutshell is why systemd is so bad, even if streetwalrus might tell you the contrary.
Or you know, don't use the even bigger disease that ubuntu and every other distro in the debian family are in the first place.
I know but currently, all the other distributions has some issues or they don't carry the packages i need.
I had tried Void Linux in the past and but the xbps thing and the fact there is nothing like a padoka's ppa or even something like Debian testing
I also never was able to complete a Gentoo installation mainly due to my slow connection.