decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
That doesn't make sense | 474 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
That doesn't make sense
Authored by: Anonymous on Monday, July 02 2012 @ 03:52 PM EDT
If we end up choosing a motherboard that does not allow us to switch off secure boot:
I suspect that will equate to picking a name brand PC. Likely something Canonical wants to let distributors use.

How far would Canonical get with telling their distributors that they shouldn't be using one of those?

[ Reply to This | Parent | # ]

That doesn't make sense
Authored by: Anonymous on Monday, July 02 2012 @ 04:51 PM EDT
> If you want to blame anyone, place the blame squarely where it belongs:
> First: On the hardware manufacturer
> Second: On the entity that decided to use the hardware by said
manufacturer.

Case 1: the manufacturer advertises hardware as Linux Ready - boom
Case 2: non-Linux capable hardware installed by customer - boom

Canonical stands by with an innocent smile?

Consider case 3, where Canonical and the manufacturer collaborate
to use a MS key to sign the bootloader. Then MS does something that
obliges the manufacturer to change the hardware so Ubuntu breaks.
Whose fault now? Clue, it's not the FSF, they're still standing in the
corner wringing their hands.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )