Linked by Thom Holwerda on Sat 29th Dec 2012 16:37 UTC
Linux It's sad that we need this, but alas - Matthew Garret has made a list of Linux distributions that boot on Windows 8 PCs with Secure Boot enabled. Tellingly enough, the list is short. Very short. Can someone hack this nonsense into oblivion please?
Thread beginning with comment 546598
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by Drumhellar
by WereCatf on Sat 29th Dec 2012 19:22 UTC in reply to "Comment by Drumhellar"
Member since:

What about the list of distros that boot on Windows 8 PCs with secure boot disabled, because, you know, Microsoft acquiesced to pressure and makes the ability to disable secure boot a requirement for the Windows 8 logos...

Well, the thing is, they do not mandate how one must be able to disable secure boot -- OEMs are free to use whatever means they want. This could include a physical switch on the motherboard or having to call up the OEM for an unlocking - key or whatever they feel like.

It all makes it quite a bit more difficult for novice users to try Linux, and it makes development of custom OSes even harder.

Reply Parent Score: 4

RE[2]: Comment by Drumhellar
by Drumhellar on Sat 29th Dec 2012 19:55 in reply to "RE: Comment by Drumhellar"
Drumhellar Member since:

Any of those solutions requires added complexity that an OEM will likely not add. A physical switch? That's an extraordinarily expensive solution (It would be useful in specific situations, and if an OEM does implement this, would likely be as a value-add option). A phone call to retrieve an unlock code? Again, that's extra complexity in the support side. OEMs have no reason make this more difficult; They don't benefit when users DON'T install Linux.

No, the simplest way to implement this is just an on/off in the firmware setup, right next to all the other options that are usually available. There are few reasons NOT to implement it this way.

Reply Parent Score: 7