SoylentNews is people
SoylentNews
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, @02:14PM
The lack of a link is just a sign this is a shit story.
The actual content of the story is the real problem.
Its an exaggeration nearly to the point of being a conspiracy theory.
To recap:
(1) Not an rm unix command, its a systemd internal function call
(2) Not censored, comments limited to collaborators
(3) Limit only made after 3 drive-by flame posts that literally added no new technical information, 10 days after last informative post
It's also interesting to note that the story was submitted here just 4 hours after the discussion was limited to collaborators.
Makes me suspicious that the submitter was one of the flamers and is butthurt that his anti-social behavior was rejected.
What are the chances that some random person 'discovers' this horrible case of censorship so quickly?