Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” bricking UEFI

Re:Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” brickin... by gpm on Monday February 22, 2016 @02:58PM (#11153772)

So if I understand this correctly, now instead of bricking the system it will just fuck up the bootloader, even if the bootloader is completely unrelated to the linux install you are `rm -rf /sys`ing. Since the useful efivars that set up bootloaders must be on the whitelist.

It's an improvement, but it seems like we should do this in addition to default mounting read only.

[ Parent | on HN ]

Re:Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” brickin... by protomyth on Monday February 22, 2016 @03:04PM (#11153830)

It still seems to me that Linux should follow FreeBSD and not mount it as a filesystem and just use a library to manipulate the values. It clearly has some huge problems with being a filesystem. This isn't Plan 9 and everything does not have to be a file.

[ Parent | on HN ]

Re:Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” brickin... by floatboth on Monday February 22, 2016 @05:06PM (#11154662)

FreeBSD actually doesn't have any support for EFI variables at all! It just installs the loader into the default location (bootx64.efi) and the loader does everything.

[ Parent | on HN ]

Re:Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” brickin... by protomyth on Monday February 22, 2016 @05:18PM (#11154748)

I guess I counted the loader as part of the system. Its installed by FreeBSD to do the job.

[ Parent | on HN ]

Re:Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” brickin... by eternal_july on Monday February 22, 2016 @05:01PM (#11154628)

Of course everything doesn't have to be a file (it is only that way on Unices). On Linux everything is a filesystem!

[ Parent | on HN ]