3 ms·
I'm for right to repair, my point was about how it plays out in the "publics" eyes, not techies eyes. But the issue I personally have with "firmware write enab
by Crosseye_Jack 5y ago
I'm for right to repair, my point was about how it plays out in the "publics" eyes, not techies eyes.
But the issue I personally have with "firmware write enable" switches is that the ave person doesn't want to mess about with then every time there is an update and bootloader locks are still locks you often have to seek the permisson of the vendor to unlock OR they get disabled once you need "unsupported access" and not re-enabled (sometimes, re-enabling them disables what ever you needed it disabled for in the first place so you can't re-enable it).
One of the criticisms of Windows XP was that lots of "ave joes" just ignored Windows Updates, so even though MS released patches for bugs you could still find plently of vulnerable systems, after all your ave joe just wants to "get on with it" when they are using their computer. Putting in hinderances for the "avg joe" will (imo) only lead to fewer devices taking up firmware updates.
However a) we are talking about farm gear, so its not like its your "avg joe" using them, plently of farmers are used to getting it fixed, even if its just a bodge so they can get their job done b) if the bootloaders/firmware switch still allows updates from "a trusted source" while locked then it doesn't hinder auto-updates and allows the techies of the world to play outside the sandbox.
- atatatat 5y agoYou're describing an education problem, not a software problem. Trying to retrofit the same code to 100k different models of machine will never work, even when we're at Windows 18. Educate the people around you about basic computing shit, and donate to institutions that do it at scale.