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: 1, Insightful) by Anonymous Coward on Monday April 17 2017, @09:23PM (1 child)
Do we have enough of a reason now to get all the distributions to dump systemd? This should be proof enough of total incompetence to make it happen.
(Score: 0) by Anonymous Coward on Tuesday April 18 2017, @04:35PM
There are many which do NOT use systemd, and for those that do, you can often replace it with openrc.
I run these which do NOT install systemd: SlackWare, Alpine, RedHat/CentOS 6 (NOT 7!)
go here: http://without-systemd.org/wiki/index.php/Main_Page [without-systemd.org]
CentOS 6 is not listed but I'm running it on a live webserver that rocks.