Linked by Thom Holwerda on Sat 29th Dec 2012 16:37 UTC
Thread beginning with comment 546602
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2005-07-12
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.