Arguments against systemd

From Without Systemd
(Difference between revisions)
Jump to: navigation, search
(move tmux issue to Unprofessionalism)
(Absurd bugs and responses: reformat to show bug site & id, rm responses, readers should see the original bug reports)
Line 62: Line 62:
 
== Absurd bugs and responses ==
 
== Absurd bugs and responses ==
   
* [https://bugs.freedesktop.org/show_bug.cgi?id=74589 Unchecked null pointer dereferencing in PID 1 not considered a serious issue] - <i>"To make this work we'd need a patch, as nobody of us tests this."</i>, <i>"I will not work on this"</i> - systemd <b>requires</b> cgroups and segfaults if there is no cgroups support.
+
* [https://bugs.freedesktop.org/show_bug.cgi?id=74589 freedesktop#74589] Unchecked null pointer dereferencing in PID 1 not considered a serious issue.
* [http://www.phoronix.com/scan.php?page=news_item&px=MTYwMzg Screen locking issues (including a security issue) with gnome-shell] -- remained unfixed for over a year
+
* [https://bugzilla.opensuse.org/show_bug.cgi?id=918226 openSUSE#918226] systemd segfaults after updating from 208-23.3 to 208-28.1
* [http://soylentnews.org/article.pl?sid=14/12/21/1343258 PID 1 segfaulting on upgrade; journalctl usability issue] - bug report still marked as "NEW"
+
* [https://github.com/systemd/systemd/issues/2402 GitHub#2402] Mount efivarfs read-only - Doing rm -rf / bricks your computer
* [https://lists.debian.org/debian-user/2015/02/msg00010.html "Tried to boot my laptop from a cafe..."]
+
* [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776171 Debian#776171] Unable to shutdown
* [https://bugzilla.opensuse.org/show_bug.cgi?id=918226 systemd segfaults after updating from 208-23.3 to 208-28.1]
+
* [https://bugs.freedesktop.org/show_bug.cgi?id=61191 freedesktop#61191] systemd-journald eats 100% CPU
* [https://github.com/systemd/systemd/issues/2402 Mount efivarfs read-only] - Doing rm -rf / bricks your computer
+
* [https://bugs.freedesktop.org/show_bug.cgi?id=64116 freedesktop#64116] Corrupted binary logs
* [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776171 Unable to shutdown]
+
* [https://github.com/systemd/systemd/issues/5644 GitHub#5644] tmpfiles: R! /dir/.* destroys root, also see [https://www.preining.info/blog/2017/04/systemd-again/ systemd again (or how to obliterate your system)]
* [https://bugs.freedesktop.org/show_bug.cgi?id=61191 journald eats up CPU]
+
* [https://github.com/systemd/systemd/issues/6237 GitHub#6237] systemd can't handle the process previlege that belongs to user name startswith number, such as 0day
* [https://bugs.freedesktop.org/show_bug.cgi?id=64116 Corrupted binary logs]
+
  +
Missing bug report link:
  +
 
* [https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet how to crash systemd in one sweet] (works as any user, not just root) and [https://medium.com/@davidtstrauss/how-to-throw-a-tantrum-in-one-blog-post-c2ccaa58661d response] and [https://www.agwa.name/blog/post/systemd_is_not_magic_security_dust rebuttal]
 
* [https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet how to crash systemd in one sweet] (works as any user, not just root) and [https://medium.com/@davidtstrauss/how-to-throw-a-tantrum-in-one-blog-post-c2ccaa58661d response] and [https://www.agwa.name/blog/post/systemd_is_not_magic_security_dust rebuttal]
 
* [http://www.openwall.com/lists/oss-security/2017/01/24/4 systemd v228 local root exploit]
 
* [http://www.openwall.com/lists/oss-security/2017/01/24/4 systemd v228 local root exploit]
* [https://github.com/systemd/systemd/issues/5644 tmpfiles: R! /dir/.* destroys root] See also [https://www.preining.info/blog/2017/04/systemd-again/ systemd again (or how to obliterate your system)], Poettering's response: <i>"I am not sure I'd consider this much of a problem. Yeah, it's a UNIX pitfall, but "rm -rf /foo/.*" will work the exact same way, no?"</i> (Hint: no.)
 
* [https://github.com/systemd/systemd/issues/6237 systemd can't handle the process previlege that belongs to user name startswith number, such as 0day] Poettering: "not a bug, a feature"
 
 
* [https://serverfault.com/questions/755818/systemd-using-4gb-ram-after-18-days-of-uptime systemd Using 4GB RAM After 18 Days of Uptime]
 
* [https://serverfault.com/questions/755818/systemd-using-4gb-ram-after-18-days-of-uptime systemd Using 4GB RAM After 18 Days of Uptime]
  +
* [http://www.phoronix.com/scan.php?page=news_item&px=MTYwMzg Phoronix - Screen locking issues (including a security issue) with gnome-shell] -- remained unfixed for over a year
  +
* [http://soylentnews.org/article.pl?sid=14/12/21/1343258 SoylentNews - PID 1 segfaulting on upgrade; journalctl usability issue] - bug report still marked as "NEW"
  +
* [https://lists.debian.org/debian-user/2015/02/msg00010.html "Tried to boot my laptop from a cafe..."]
   
 
== Unprofessionalism ==
 
== Unprofessionalism ==

Revision as of 09:11, 17 April 2018

Contents

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

Scope creep

systemd suffers from scope creep.

See Wikipedia:File:Systemd components.svg.

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

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[6]
  • 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.[7]
  • systemd-resolved breaks the traditional glibc behavior by skipping a DNS server in all following queries, if it does not respond once. GitHub#5755, [8]

Conceptional problems

Poor design

Scope creep leads to vulnerabilities

Absurd bugs and responses

Missing bug report link:

Unprofessionalism

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