5 ms·
> What most systemd critics consider "bloat", I consider necessary complexity to solve a complex problem generically. As a distro and philosophy, Archlinux was
by KingMachiavelli 7y ago
> What most systemd critics consider "bloat", I consider necessary complexity to solve a complex problem generically.
As a distro and philosophy, Archlinux was bound to adopt systemd eventually. e.g. Maintaining you're own init system/scripts is not KISS. Creating a custom init file to adapt 90% of software from systemd to another init system is not KISS.
- deleted 7y ago[deleted]
- deleted 7y ago[deleted]
- m45t3r 7y agoYeah. Most people misunderstand Arch's KISS principle. If you look for most decisions Arch took in the last years, most of them were focused in simplifying the distro and reducing the maintainer burden. So things like removing the TUI installer (does someone remember it?) and migrating to systemd. Even the fact that Arch ships with most packages with few or no changes compared to upstream is focused on it: reduce the burder on maintainer.
- djsumdog 7y agoGentoo, Alpine and Void still default to using their own init systems.
- MuffinFlavored 7y agoIt seems Alpine uses Gentoo's OpenRC init system from a quick Google. https://wiki.alpinelinux.org/wiki/Alpine_Linux_Init_System https://wiki.alpinelinux.org/wiki/Alpine_Linux_Init_System https://wiki.gentoo.org/wiki/OpenRC https://wiki.gentoo.org/wiki/OpenRC
- sterlind 7y agoAlpine has to use OpenRC rather than systemd because it's designed to run in containers. Using cgroups or lxc requires running your container with elevated privileges. This doesn't only affect systemd, it also makes it impossible for me to run Nix builds in unprivileged containers with isolation enabled, since isolation requires cgroups.