Stalwarts Claim Asus eeePC Violates GPL
WirePosted writes "Members of the Linux community have complained that the hot new sub-notebook from Asus, the eeePC, may have violated the spirit of the Linux General Public License (GPL). Some Linux advocates claim the eeePC has not included required source code with the installed Xandros Linux distribution and does not easily enable users to install another distro. However, there are indications that eeePC fans probably don't care."
Is it just me? Or does there seem to be coordinated effort on the part of Microsoft and their cronies to fragment the Linux community by using legal offensives, everything from the patent agreements mentioned in TFA to out and out violations of the GPL, such as this one from ASUS? I think it's sort of a divide and conquer strategy... BUt I also don't think that they fully understand the dynamics involved ... there isn't just the 'purists' vs. the 'pragmatists'... we're a lot more complicated than that, or so I'd like to think.
My blog
BTW the Asus Eee PC is a great little machine although like most Linux dists the UI is a little rough around the edges.
A couple of things, let's wait an see.
On the GPL issue I like that the poster actually purchased the PC. Give them a few weeks to respond to a request for the sources. Seems easy enough. The GPL is pretty clearcut.
On the upgrades/breaking seals void warranty, that seems completely understandable. If you've tested hardware in one configuration with a specific set of components, that is obviously what you'll warranty.
I don't understand why people think companies should warranty things if you add random, $15 no-name memory or an overclocked, overheating PCI-E card etc. They have no control. Odds are you won't have a problem of course. But anyone who has used computers will realize that even a small change can throw things off. And is a super pain to track down, especially if you weren't the one making the change. This even I have experienced. A good first question is to ask what has changed recently on this system when there are problems.
I did a very short and small stint doing embedded systems programming. Pretty standard small parts under the hood. But that didn't mean if you unscrewed the housing and "upgraded" things we'd feel obligated to warranty it. Especially because there were safety of life implications.
Secondly, there is a simple route to take here. Have someone who actually owns copyright on code make a complaint, or take your complaint to the company, and failing that forward to the FSF/SFLC or whomever....
Sounds like the author of asus_acpi has a lawsuit on his/her hands.
It sounds, though, like there isn't an attributable author.
Is there anybody to sue??
Can second, third, and fourth-hand distribution of unattributed but non-compliant formerly GPL'd work be prohibited?
Does the eeePC support booting from the net? (pxe, rarp, etc)
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
http://www.google.co.uk/search?sourceid=mozclient&ie=utf-8&oe=utf-8&q=%22general+public+license%22+-gnu
Yes, a lot of those are references to the GNU GPL without mentioning the word "GNU", and there are some mentions of the Affero licence too, but there are still quite a few "General Public Licenses" that have nothing to do with the FSF.
What do you mean, "stolen by ASUS"? The original GPL code is still there, freely available from wherever the ASUS folks got it from. The owners are still in full posession of the code. Does not compute. EOF
From the article: "However, the issue highlighted by the latest revelations concerning the Asus eeePC and the GPL signals a growing rift developing between Linux pragmatists such as Xandros and Novell's Suse, and Linux purists such as Red Hat and Canonical-funded Ubuntu." Dude... I mean - how 'purist' is Ubuntu when it delivers those binary nVidia/ATi blobs out of the box? You tell me.
...in other words, it was formerly distributed under the GPL and is now just a warez thing.
Ok, I can see that. Thanks for the clarification.
Beware of he who would deny you access to information, for in his heart he dreams himself your master.
asus_acpi isn't even the worst of it. Their modified madwifi supports a chipset that the rest of the madwifi community has been wanting support for for months. I read something somewhere about madwifi being licensed in a way which allows this (which seems silly, on the surface, as the community now has to duplicate asus' efforts), but it still doesn't make sense to me. it's not a secret what the wifi chipset in the eee is, so I don't see what they gain by not allowing other linux distros to support it...it's not like they're making millions selling Xandros licenses.
Stasis is death. Embrace change.
check out http://support.asus.com/download/download_item.aspx?product=20&model=Eee%20PC%204G(701)&SLanguage=en-us
and click on "Source Code"
Regards, Stu
Why Linux on the desktop will never happen, reason #137: The instant some vendor ships a nice, cheap, Linux-based desktop PC, a zillion Linux fanboys will descend on them complaining that they've violated some usage condition so obscure that it takes a hundred-message thread just to explain it.