I do use LUKS on my laptop, but not my desktop. I guess I don't encounter those situations because I just use the default encrypted setup the Fedora installer gives me on one hard drive and one volume. Nor have I seen messages from any computer I've used Linux on telling me to shut down the computer because it couldn't handle it itself.
My impression of systemd is very different than yours. I think it's a godsend unifying group of technologies that harmonizes different distros, just as the kernel itself puts everything under the "Linux" umbrella. I can take common unit files, concepts, and ideas and share them from Arch to Debian to Fedora and others as well. Things like binary logs don't trouble me because tooling exists to decode them, just as cat and zcat exist to print text and compressed text files.
You know what's a bit funny to me? I actually just had an experience recently where I was rewriting a docker-compose file as a script to work with podman and for the containers to reside properly in a pod. If you don't know, podman doesn't officially support the compose files, they have more natural support for kubernetes kubes which looks pointlessly complicated... Anyway, so I went from the declarative config file (docker-compose.yml) to my own little handwritten mishmash.sh to create the more podman-centric script and I felt like it was a reverse of my experience of going from sysvinit to systemd.
I do use LUKS on my laptop, but not my desktop. I guess I don't encounter those situations because I just use the default encrypted setup the Fedora installer gives me on one hard drive and one volume. Nor have I seen messages from any computer I've used Linux on telling me to shut down the computer because it couldn't handle it itself.
My impression of systemd is very different than yours. I think it's a godsend unifying group of technologies that harmonizes different distros, just as the kernel itself puts everything under the "Linux" umbrella. I can take common unit files, concepts, and ideas and share them from Arch to Debian to Fedora and others as well. Things like binary logs don't trouble me because tooling exists to decode them, just as cat and zcat exist to print text and compressed text files.
You could move sysvinit files from distro to distro, mostly, too, mind you; that being said perhaps I'm just an old curmudgeon stuck in their habits.
True.
You know what's a bit funny to me? I actually just had an experience recently where I was rewriting a docker-compose file as a script to work with podman and for the containers to reside properly in a pod. If you don't know, podman doesn't officially support the compose files, they have more natural support for kubernetes kubes which looks pointlessly complicated... Anyway, so I went from the declarative config file (docker-compose.yml) to my own little handwritten mishmash.sh to create the more podman-centric script and I felt like it was a reverse of my experience of going from sysvinit to systemd.