Edit: The link.
There were lots of good titles for this submission, as in "Breaking news: Poettering clueless?" to finally disprove Betteridge's law, or "systemd surprisingly not as good as advertised" or "Breaking new: systemd broken" or "Poettering censors critics after epic fail".
Systemd implementation of "rm -rf .*" will follow ".." to upper directory and erase /
How to reproduce:
# mkdir -p /foo/dir{1,2}
# touch /foo/.bar{1,2}
# cat /etc/tmpfiles.d/test.conf
R! /foo/.* - - - - -
Reboot.
After the issue was fixed, finally Poettering added this gem of wisdom:
I am not sure I'd consider this much of a problem. Yeah, it's a UNIX pitfall, but "rm -rf /foo/.*" will work the exact same way, no?
The answer to this question, as many clarified for him, obviously is a loud "NO!". After being told a couple of times in no uncertain terms, the thread was closed for non-developers
poettering locked and limited conversation to collaborators 4 hours ago
for which I proposed the "freedom-of-speech" department (although I admit it is a weak proposal).
(Score: 2) by Alphatool on Tuesday April 18 2017, @11:16AM (1 child)
Well, from a systemd point of view you've got this backwards! Why should the operating system have a duplicated implementation of rm when there can be a perfectly good one built into the init system?? It's even better at deleting things than the legacy implementation was!! Next up, twitter integration!!!
(Score: 3, Funny) by maxwell demon on Tuesday April 18 2017, @06:38PM
I'm looking forward to the binary twitter messages. ;-)
The Tao of math: The numbers you can count are not the real numbers.