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) by purple_cobra on Thursday April 20 2017, @12:47PM (1 child)
TrueOS, for reasons of marketing...
I tried sticking it on an expendable netbook to see what would happen: the SATA driver shits itself and the suggested solution - dropping to a shell mid-boot and setting a kernel hint - makes it work. I later find out that there's some issue with UEFI systems and GRUB, so I should use the BSD bootloader...which it doesn't give me the option to install. OpenBSD installed on the same machine quickly and worked fine until I flattened the HD to try TrueOS instead. Maybe I'll try it again after they've updated the install images. And it works so well in a VM!
(Score: 1) by purple_cobra on Thursday April 20 2017, @01:37PM
*sigh* Fat-fingered that comment...
The suggested fix *doesn't* make it work and it continues to throw errors about a controller that OpenBSD and a few Linux distributions (with and without systemd) can happily use without issue.