This is an old revision of the document!


future page for init freedom article

maybe use already installed sync plugin to pull resources from devuan wiki

As systemd doesn't follow our Social Contract, we have decided to remove it and use OpenRC as our default init system. The decision means that the Stable v0.1 will be the first and the last version supporting systemd.

To ease the transition, systemd support will remain in the stable repositories for the time being, while we are removing it in the Testing version and creating our OpenRC migration guide. As of Stable v0.2 release, systemd support will be completely removed without further notice.

Further details:

  Unchecked null pointer dereferencing in PID 1 not considered a serious issue (https://bugs.freedesktop.org/show_bug.cgi?id=74589)
  Mount efivarfs read-only (https://github.com/systemd/systemd/issues/2402)
  Unable to shutdown (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776171)
  journald eats up CPU (https://bugs.freedesktop.org/show_bug.cgi?id=61191)
  Corrupted binary logs (https://bugs.freedesktop.org/show_bug.cgi?id=64116)
  tmpfiles: R! /dir/.* destroys root (https://github.com/systemd/systemd/issues/5644)
  systemd again (or how to obliterate your system) (https://www.preining.info/blog/2017/04/systemd-again/)
  systemd can't handle the process previlege that belongs to user name startswith number, such as 0day (https://github.com/systemd/systemd/issues/6237)
  systemd Using 4GB RAM After 18 Days of Uptime (https://serverfault.com/questions/755818/systemd-using-4gb-ram-after-18-days-of-uptime)
  Please do not default to using Google nameservers (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658)
  journal ip anonymization (https://github.com/systemd/systemd/issues/2447)
  systemd kill background processes after user logs out (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394)
  systemd-resolved DNS cache poisoning (https://seclists.org/oss-sec/2014/q4/592)