←back to thread

279 points the_why_of_y | 1 comments | | HN request time: 0.2s | source
Show context
Mic92 ◴[] No.11153454[source]
Instead of flaming systemd developers for mounting efivars read/write, the kernel is the right place to fix the problem for everybody!
replies(1): >>11153544 #
ajross ◴[] No.11153544[source]
No, the firmware is the right place to fix the problem. A BIOS that bricks itself because of within-specification deletion of variables via a standard API is just plain broken.

But in the real world no one ever fixes firmware bugs, so this is the best we can do.

replies(3): >>11153652 #>>11153744 #>>11153940 #
kbenson ◴[] No.11153652[source]
I think we can all compromise on "The firmware is the right place to fix the problem, the kernel is the right place to mitigate the problem."
replies(2): >>11153705 #>>11153827 #
1. eikenberry ◴[] No.11153827[source]
+1

The kernel developers are continuously working around bad behaviour by bios/firmware authors. It is the right place.