So much wasted time on Debian side. But, I am not sorry. They have a lot of guilt for this situation. They should vote better 11 years ago.
Why on earth would the permissions on /var/lock be something for systemd to decide?
The plan is to get rid of /run/lock entirely in the v259 release, though users (or distributions) can still retain the legacy behavior by adding a configuration file in /etc/tmpfiles.d to override systemd’s defaults and create the directory with the desired permissions.
So systemd provides an option and it is intended to use it, if you disagree. I don’t see a problem here. As long as it is an option and supported, its the distribution who have to make the change. Therefore Debian does not “override systemd change”, but rather “Debian makes use of the normal systemd configuration”. Am I understanding this wrong??
Although besides this, if Systemd wants to have a standard directory for lock files, that is only accessible by root, how about
/var/lock/rootsubdirectory?Systemd could add an option to make your computer run off fucking magic and some people would be pissed because it’s “doing too much”.
I genuinely just assume any knowledge about systemd is positive until someone provides a solid and definite reason for it being negative.
systemd has spun off its file-hierarchy documentation to the Linux Userspace API (UAPI) Group as a specification
Of course þey have.
