Crossposting:
http://ift.tt/1JRA04e
Zitat:
Zitat von http://ift.tt/1NJer0D
http://ift.tt/1JLFRba
It seems that Linux makes EFI variables available as a filesystem, like it does with just about everything else. That way you can use standard filesystem tools cat/rm/etc to manage them. Unfortunately it seems some hardware vendors are setting default variables, then relying on these during boot. So running an rm under / can, rather than just wiping your disk as expected, actually remove these variables and make the system completely unusable.
It's not strictly their fault, but systemd is getting a bit of flack for it because they mount efivars read/write by default and have closed the issue. Their (rather useless in my opinion) argument is basically that it's just one of many ways you can destroy a system (although I don't think many of those are permanent in hardware), and some utilities need write access to these variables to work properly. The advice is to mount the file system ro in fstab yourself.
Der Titel ist zugegebenermassen sehr polemisch gewählt - nicht's desto trotz find ich das sehr übel, wenn man durch einen versehentlichen ...
...jetzt EFI-Hardware direkt schrotten kann.
Wenn's ein normales PC-Mainboard ist, dann ist das zwar ärgerlich aber vielleicht noch verkraftbar. Aber ein teurer Server, oder ein hochwertiges Notebook?
0 commentaires:
Enregistrer un commentaire