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: 0) by Anonymous Coward on Tuesday April 18 2017, @10:28PM (1 child)
This story is the systemd equivalent of Benghazi:
Poettering said something dumb when he didn't have all the information. People who are desperate to bash him for their own reasons decided to blow it way out of proportion and then a bunch of low-information suckers took those people at their word and ran with it. Demonstrating that fact-checking and critical thinking are in short supply wherever amateurs gather.
(Score: 0) by Anonymous Coward on Tuesday April 18 2017, @10:40PM
> Demonstrating that fact-checking and critical thinking are in short supply wherever amateurs gather.
Perhaps parent is an exemplar?
Came here to say - this "1 (2)" business at the bottom, whaaat up? really? aren't we grownups who can manage a page or two of text? Many lols for multipages!