- Mysterious PID1 crash related to timedatectl, resolved by replacing /etc/localtime with a regular file instead of symlink (to a file on same FS). How do you s

- Mysterious PID1 crash related to timedatectl, resolved by replacing /etc/localtime with a regular file instead of symlink (to a file on same FS). How do you strace PID1 to get some idea what's going on? You don't. Good thing timezone management needs to be part of init! - Mysterious issue in resolvectl, some sort of race condition, 2-year old bug report https://github.com/systemd/systemd/issues/22775 https://github.com/systemd/systemd/issues/22775 - at least you actually don't have to use this one. And those are just the two that I've had to spend hours on in the past few years. Not using systemd is barely a choice, even if you don't use systemd itself you nearly have to use things which are designed in exactly the same bad ways (polkit, systemd-udevd), there are several (negative) changes which even systemd-resistant distros have adopted for conformity which were first driven by systemd, lots of software has completely removed their provided init-scripts and replaced them with systemd unit files only so you have to write your own or go dig it up from the git history... Oh and it's extremely brittle and one little piece breaking means you can't boot at all, not even in single user, since everything is jammed into PID1... so good luck even examining what's going on. I could go on but of course you've already seen and chosen to ignore any argument I could make, because this dead horse has indeed been beaten, by the people who constantly ask "what's wrong with it" when many, many answers are a simple Google away.