Initially the bug report was shot down by systemd developer Luca Boccassi of Microsoft with:
So an option that is literally documented as saying “all files and directories created by a tmpfiles.d/ entry will be deleted”, that you knew nothing about, sounded like a “good idea”? Did you even go and look what tmpfiles.d entries you had beforehand?
Maybe don’t just run random commands that you know nothing about, while ignoring what the documentation tells you? Just a thought eh"
Good devs, good product, I’m really excited about out shitty, shitty future.
It is shown by non-systemd distros that systemd doesn’t really solve problems for desktop usage. When you switch away, not much changes basically. I sometimes hear that it is a different story on servers.
Wonder what their usages are, especially in a container-focused context, where most containers simply don’t have an init, and the base system just needs, at most, to have a container runtime (+/- a few other things, see: talos linux and their 130MB bare-metal ISOs).
Systemd is very useful for managing (rootless) Podman containers.
I actually do use quadlets on my server which are absolutely fantastic and hook into systemd, but I don’t see any reason why a similar init system couldn’t do similar or even contribute something like
podman generate systemdbut for a different init system.