You mean a very specific command like systemd-tmpfiles that you have to manually execute and feed with the parameter --purge while omitting a config file in order for it to do so? Because of a bug that was quickly fixed in 256.1, not even 2 weeks after the 256(.0) release? [1]
This is not some random cgi script to generate a photo gallery that was whipped up over a weekend. This is systemd. It touches every aspect of each distribution that chooses to use systemd. It is important software. There is a minimum level of care that should go into development and release of software that does what systemd does.
They introduced functionality that deletes files and failed to run it through its paces before release. That's not merely failing a smell test, it's a big red flag that the developers of systemd should not be working on something as important as systemd.
Oh, and now the creator of systemd wants to add on functionality for privilege escalation. Knowing how they handle systemd, do you think they'll do a good job at making sure their proposed 'run0' thing will work as it says on the box, or is it going to have untested warts?
> Oh, and now the creator of systemd wants to add on functionality for privilege escalation. Knowing how they handle systemd, do you think they'll do a good job at making sure their proposed 'run0' thing will work as it says on the box, or is it going to have untested warts?
This feature isn't something new and has been present as `systemd-run` for ages...
[1] https://www.theregister.com/2024/06/20/systemd_2561_data_wip...