A number of users have reported that running "rm --no-preserve-root -rf /" not only deletes all their files (as expected), but also permanently bricks their computers (which is not). Tracing the issue revealed that the ultimate cause was that SystemD mounted the EFI pseudo-fs as read-write even when this FS was not listed in fstab, and deleting certain files in this pseudo-fs causes certain buggy, but very common, firmware not to POST anymore. A user reported this bug on SystemD's GitHub issue tracker, asking that the FS be mounted read-only instead of read-write, and said bug was immediately closed as invalid. The comment thread for the bug was locked shortly after. Discuss.
Links:
https://github.com/systemd/systemd/issues/2402
http://thenextweb.com/insider/2016/02/01/running-a-single-delete-command-can-permanently-brick-laptops-from-inside-linux/
(Score: 1, Funny) by Anonymous Coward on Tuesday February 09 2016, @12:43PM
If you caught Mother Teresea finger banging a 6 year old Indian boy, I dont care what she has done over the years, shes a fucking child rapist.
Redhat is metaphorically fingerbaning Linux users in the asshole right now. And your only response is "slamming the only ally that the open source community has been able to consistently rely on for two decades."
Obviously we cannot rely on them with this fucking systemd they are trying to fingerbang into you anus, so your point on being able to consistently rely on them has been proven false.