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: 2) by tangomargarine on Tuesday February 09 2016, @02:56PM
I thought they were already "in charge of" CentOS?
In January 2014, Red Hat announced that it would sponsor the CentOS project, "helping to establish a platform well-suited to the needs of open source developers that integrate technologies in and around the operating system".[16] As the result of these changes, ownership of CentOS trademarks was transferred to Red Hat,[17] which now employs most of the CentOS head developers; however, they work as part of the Red Hat's Open Source and Standards team, which operates separately from the Red Hat Enterprise Linux team.[7] A new CentOS governing board was also established.[8]
(wiki [wikipedia.org])
Can't say I understood that when I heard it happened but it's quite possible I'm misunderstanding.
"Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
(Score: 2) by turgid on Tuesday February 09 2016, @03:04PM
So it has begun!
I refuse to engage in a battle of wits with an unarmed opponent [wikipedia.org].