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: 2) by julian on Monday April 17 2017, @09:56PM (1 child)
Tried it. It's an exercise in reliving all the frustrations of running Linux in the late 90s, early 2000s.
systemd is actually the path of least resistance, and I'm including even other non-systemd Linux distros. There's nothing as complete and polished as Ubuntu in the non-systemd world. Sucks, but that's where we are.
(Score: 2) by FatPhil on Tuesday April 18 2017, @07:46AM
Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves