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: 5, Insightful) by https on Monday April 17 2017, @11:59PM
He's allowed to continue because it brings Red Hat closer to their wet dream of nobody being able to run linux in an enterprise without needing their commercial support.
Systemd quite literally has no design documentation, and it's been admitted that this is deliberate, that the APIs are a moving target.
There are so many things wrong with systemd that it is hard work to put together a coherent critique of it, kind of like accidentally engaging with a young-earth creationist who thinks UFOs are the angel's chariots. The interaction will not be an "argument" in the canonical sense.
Offended and laughing about it.