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 Azuma Hazuki on Tuesday April 18 2017, @01:53PM (2 children)
Good point...I meant to type transfusion, but haven't been sleeping properly for months so...yeah. And I would be a little wary of Devuan; at this point you may as well go full-on FreeBSD or Gentoo if you have the hardware for it. I am beginning to wonder if at some point around 2019 or 2020 Gentoo, Slackware, etc will fork off and call themselves something different, maybe even maintaining their own Linux kernel without the creeping systemd hooks...
I am "that girl" your mother warned you about...
(Score: 2) by FatPhil on Tuesday April 18 2017, @02:14PM (1 child)
Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves
(Score: 2) by tibman on Tuesday April 18 2017, @05:04PM
I've had good success with melatonin as well. Using some random gummi brand from amazon.
SN won't survive on lurkers alone. Write comments.