Arguments against systemd

From Without Systemd
(Difference between revisions)
Jump to: navigation, search
(further reading: additional links)
(add Missing features section & move fsck issue there, replace soylentnews.org link with direct sources)
Line 1: Line 1:
 
__TOC__
 
__TOC__
  +
== Missing features ==
  +
  +
* fsck cannot be cancelled (used to be possible via C-c or c on the console). [https://bugzilla.redhat.com/show_bug.cgi?id=719952 Reported in 2011], [https://cgit.freedesktop.org/systemd/systemd/commit/?id=7f110ff9b8 Added to TODO in 2012]
   
 
== Conceptional problems ==
 
== Conceptional problems ==
   
* [http://soylentnews.org/article.pl?sid=14/12/21/0145243 systemd prevents the skipping of fsck while booting] - still unresolved
 
 
* [http://soylentnews.org/article.pl?sid=14/12/21/1554227 systemd disables the Linux magic SysRq key] - closed as "NOTABUG"
 
* [http://soylentnews.org/article.pl?sid=14/12/21/1554227 systemd disables the Linux magic SysRq key] - closed as "NOTABUG"
 
* [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658 Please do not default to using Google nameservers] - Debian package maintainer refuses to acknowledge the privacy leak and closed the bug.
 
* [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658 Please do not default to using Google nameservers] - Debian package maintainer refuses to acknowledge the privacy leak and closed the bug.

Revision as of 09:41, 16 April 2018

Contents

Missing features

Conceptional problems

Debunking the myth of unit files being significantly shorter than scripts used by all other init systems: A side-by-side look at run scripts and service units

Poor design

Scope creep

Systemd anigif.gif

Systemd scopecreep chart.png

Scope creep leads to vulnerabilities

Absurd bugs and responses

Breaking promises and immaturity

"After udev is merged into the systemd tree you can still build it for usage outside of systemd systems, and we will support these builds officially. In fact, we will be supporting this for a long time"

"...this will effectively also mean that we will not support non-systemd systems with udev anymore starting at that point. Gentoo folks, this is your wakeup call."

Linux (kernel) coup attempt: "kdbus support is no longer compile-time optional ... We encourage all downstream distributions to begin testing kdbus by adding it to the kernel images in the development distributions, and leaving kdbus support in systemd enabled." comment on this on LKML

"The kdbuswreck"

"kdbus now out-of-tree"

"kdbus dropped in favor of BUS1"

unmet stability promises:

To quote from the systemd stability promise:

"Starting with version 26 (the first version released with Fedora 15) we promise to keep a number of them stable and compatible for the future."

One of their promises is for the export format:

"Entry metadata that is not actually a field is serialized like it was a field, but beginning with two underscores. "

This is not true for version 44 of systemd for example.

Ignorance of fundamental operating system concepts


further reading: additional links


The new order.jpg

Personal tools