Arguments against systemd

From Without Systemd
(Difference between revisions)
Jump to: navigation, search
(Breaking promises and immaturity: reformat Linux (kernel) coup attempt)
(Breaking promises and immaturity: rewrite unmet stability promises)
Line 88: Line 88:
 
[https://github.com/systemd/kdbus "kdbus now out-of-tree"]
 
[https://github.com/systemd/kdbus "kdbus now out-of-tree"]
   
[https://en.wikipedia.org/wiki/D-Bus#kdbus "kdbus dropped in favor of BUS1"]<br>
+
[https://en.wikipedia.org/wiki/D-Bus#kdbus "kdbus dropped in favor of BUS1"]
   
<b>unmet stability promises:</b>
+
systemd promised that their [https://www.freedesktop.org/wiki/Software/systemd/journal-files/ Journal File Format] is stable starting with version 26.[https://www.freedesktop.org/wiki/Software/systemd/InterfacePortabilityAndStabilityChart/]
+
Version 44 however does not follow, "Entry metadata that is not actually a field is serialized like it was a field, but beginning with two underscores."
To quote from the systemd [http://www.freedesktop.org/wiki/Software/systemd/InterfaceStabilityPromise/ 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 [http://www.freedesktop.org/wiki/Software/systemd/InterfacePortabilityAndStabilityChart/ promises] is for the [http://www.freedesktop.org/wiki/Software/systemd/export/ 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 ==
 
== Ignorance of fundamental operating system concepts ==

Revision as of 08:33, 17 April 2018

Contents

Please objectively explain issues and link a reliable source (commit, bug report or documentation).

Issues

  • fsck cannot be cancelled (used to be possible via C-c or c on the console). 7f110ff9b8, Fedora#719952
  • systemd defaults to Google's DNS nameservers. e16cb2e4ef, Debian#761658
  • systemd defaults to Google's NTP servers, which serve leap-smeared time. GitHub#437
  • systemd by default uses Predictable Network Interface Names, which are actually less predictable when you only have one interface per type.
  • systemd by default kills background processes after the user logs out. 97e5530cf2, Debian#825394
    "In my view it was actually quite strange of UNIX that it by default let arbitrary user code stay around unrestricted after logout." -Poettering[1]
  • As systemd depends on many files on a rootfs, in case of any problems with rootfs, it is not able to control processes and (cleanly) shutdown/reboot when Crtl-Alt-Del is pressed.[2]
  • systemd-resolved breaks the traditional glibc behavior by skipping a DNS server in all following queries, if it does not respond once. GitHub#5755, [3]

Conceptional problems

Poor design

Scope creep

See Wikipedia:File:Systemd components.svg

To be added: systemd-cryptsetup, pam_systemd, acpi, cgroups, gnome-session, tcpwrapper, audit

Scope creep leads to vulnerabilities

Absurd bugs and responses

Breaking promises and immaturity

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."[9]

LKML comment

"The kdbuswreck"

"kdbus now out-of-tree"

"kdbus dropped in favor of BUS1"

systemd promised that their Journal File Format is stable starting with version 26.[10] Version 44 however does not follow, "Entry metadata that is not actually a field is serialized like it was a field, but beginning with two underscores."

Ignorance of fundamental operating system concepts

See also

Forum posts and discussions:

Other links:

Personal tools