3 ms·
My first experience was with Arch Linux right when they switched to Systemd. I hated it, but I didn't really get what it was, not knowing what an init system or
by panick21_ 4y ago
My first experience was with Arch Linux right when they switched to Systemd. I hated it, but I didn't really get what it was, not knowing what an init system or a process even is.
But I was then quite surprised a few years later when it was just the normal thing for me when people in Debian were basically fighting a war over it.
- dijit 4y agoMy first experience with systemd was similar, it was in Fedora 15 and it basically was such an incredible source of frustration. Seems to be quite serviceable on the happy path, and I quite like it for desktop linux honestly. But I find it's usually a bit too opaque and "magic" for servers; even if it's causing less and less issues. I liken the issue to the same one pulseaudio had: a software ecosystem that is poorly designed but foisted together into a perfectly serviceable product by incredible amounts of effort for all involved in its development and release to public.
- xani_ 4y agoIt allowed us to remove literally thousands of lines of code, including a bunch of rewritten init scripts, because apparently "simple" SysV scripts still have plenty of traps for the developers that start to rear their ugly heads when used with say Pacemaker. I dislike its "let's just reinvent features that worked entirely fine" (like journalctl binary logs WITH NO FUCKING INDEXING, so they are slower than text files for usual operation somehow), but at its core competence it's extremely useful.