Running this command on a Linux laptop can change the device bricks permanently.

Running this command on a Linux laptop can change the device bricks permanently.

A user posted a question on the Arch Linux Forum last month, why is it that his notebook cannot be started after running a simple "rm-rf-no-preserve-root/" command. If you have a Linux foundation, you should know that running this command is actually stupid, But it generally does not produce any destructive hardware results. However, running this command on an MSI notebook may cause the EFI boot partition to be completely cleared.

The user who posted a post on the forum is called "9233". In his post, he said: "Today, my friend and I ran the rm-rf-no-preserve-root command on an MSI notebook because we wanted to solve the Arch installation expansion problem. You can also format the root partition and reinstall Arch ." (He mentioned later that instead we thought it wocould be fun seeing the GNOME installation die ...)

In fact, the path to damage the system is/sys/firmware/efi/efivars, which stores the information required to start with the EFI standard (replacement of the old BIOS. After the folder is damaged, the device cannot be started. The notebook is changed to a brick and cannot be repaired.

The discussion was also initiated on GitHub. Developers all said that the directory of EFI startup data should not be completely writable. It is unreasonable to run a command to change hardware bricks. At present, this problem seems to have only affected the MSI notebook. Since there should not be many people who dare to make such an attempt, it will not attract much attention.

However, a device can be permanently destroyed so easily and permanently, which is still a terrible thing, even if the command itself is stupid.

This article permanently updates the link address: