From: Sergey Matveev <stargrave@stargrave.org>
Date: Sun, 16 Apr 2017 07:25:18 +0000 (+0300)
Subject: An init system must be an init system
X-Git-Url: http://www.git.stargrave.org/?a=commitdiff_plain;h=31f078265237d0533bd9abf0c0a40b9b060a3a8e;p=stargrave-blog.git

An init system must be an init system

http://systemd-free.org/
Arch Linux пользователь жалуется на ад, наступивший с systemd:

    Since the adoption of systemd by Arch Linux I've encountered many
    problems with my systems, ranging from lost temporary files which
    systemd deemed proper to delete without asking (changing default
    behaviour on a whim), to total, consistent boot lockups because
    systemd-210+ couldn't mount an empty /usr/local partition (whereas
    systemd-208 could; go figure).

    As each "upgrade" of systemd aggressively assimilated more and more
    key system components into itself, it became apparent that the only
    way to avoid this single most critical point of failure was to stay
    as far away from it as possible.

    Reading the list of those system components is daunting: login, pam,
    getty, syslog, udev, cryptsetup, cron, at, dbus, acpi, cgroups,
    gnome-session, autofs, tcpwrappers, audit, chroot, mount... How
    about defaulting KillUserProcesses to yes, which effectively kills
    all backgrounded user processes (tmux and screen included) on
    logout?
---