Slashdot Mirror
SCO Prepares To Sue Linux End Users
Bootsy Collins writes "In a brief article,
Computer Business Review Online quotes Darl McBride as saying that SCO has been busily identifying Linux end users and is
preparing to launch lawsuits against them in order to encourage more such end users to buy licenses from SCO. SCO indicates that they'll start with a company that uses AIX, Dynix and Linux, so as to 'settle several legal arguments in one go.'" Not everyone is going to take the SCO approach sitting down; read on for a story on how (among others) Weta Digital and Australia's Massey University aren't jumping to say Uncle to SCO. Update: 08/20 13:11 GMT by T : Oops! Massey University is in New Zealand, not Australia.
Chris Brewer writes "Massey University's Helix supercomputer would incur a licensing charge of nearly US$100,000 for it's 132 CPU Beowulf cluster, and Weta Digital's render farm could cost somewhere between US$1.15 and US$1.5 million dollars at SCO's 'introductory' pricing, according to this Computerworld article. Massey's parallel computing director says it's unlikely that they'll buy a licence, instead, waiting for what the U.S. Courts decide. Weta's CTO Scott Houston says that they're also not going to buy a licence, but are focusing on making movies in the meantime."
If you look at what SCO has done since the start of this debacle you really have to question the method and means. They started by saying that the open source community wasn't good enough to produce Linux, they have now gone on to openly attack the GPL Itself.
We shouldn't be worrying about the gritty details of what they are doing at treat this as what it is. SCO has declared war on the foundations of the open source community and we should be responding appropriately.
If they are claiming the GPL is invalid, the copyright holders of relevant software should be sending them personal letters telling them they are denied use of gcc, samba, apache, perl and all the other mainstays of modern computing that are released under the GPL. I'm not suggesting engaging in any illegal activity but what is kneaded here is attack rather than passive defence. Obviously the RedHat suit is a pretty good thing. The IBM counter suit I'm not sure about, there patent portfolio is a weapon that could just as easily be turned on us.
The only code they've so far shown anybody (2 snippets snapped at their show by Heisse) is from Ancient Unix and is covered by the BSD License from BSD 2.2 Onwards also released from its original 16bit Unix V5 under a BSD license by Caldera / the SCO group a couple of years back.
The license you bought, you can wipe your arse with, it's all its good for.
Economic Left/Right: -0.62
Social Libertarian/Authoritarian: -3.69
I'm proudly registered at the Linux Counter with number #150681, and I'm going show it off on my homepage.
"It is more complicated than you think" (The Eighth Networking Truth from RFC 1925)
Assuming for the moment that Linux does contian SCO copyrighted code,
I was under the impression that it was the distribution of copyrighted
materials that consituted copyright infringement, not the posession.
Is there a valid legal argument that makes users vulnerable to litigation
on the basis of copyright infringement?
*sigh* back to work...
... why SCO can even sue Linux users at this point? I mean, don't they have to actually WAIT for the court decision vs. IBM to come through before suing the users? They're basically saying "following the court decision in our favor in the case of SCO vs IBM that went to court in 2005, you owe us money". Do they have a time travel section in addition to their litigation one?
Christ, have them stop already. They haven't even been to court yet and are acting as if they won. I wonder how the courts will react to these legal proceeding against the users on the basis of a pending legal case.
Anyway, lets assume that a lot of people has filed complaints against the behaviour of SCO... then why don't we see any results of those complaints? Are the people that received the complaints all sleeping or is SCO protected from legal investigation?
Sorry for my little understanding of US law, but here in Germany SCO had to shut up quite quickly after complaints were filed, but it looks like that in the US nothing of that sort happens.
---Letter Ripped off of Linux Today---
:
Over the past few months, the SCO (Santa Cruz Operation) Corporation (formerly Caldera International, Inc. a Linux distribution vendor) has been complaining about violations of its Copyright works by the Linux kernel code.
Recently, Darl McBride, the Chief Executive Officer of SCO has been making pejorative statements regarding the license used by the Linux kernel, the GNU GPL. In a keynote speech he recently said
"At the end of the day, the GPL is not about making software free; it's about destroying value."
In light of this it is the depths of hypocrisy that at the same event SCO also announced the incorporation of the Samba3 release into their latest OpenServer product. Samba is an Open Source/Free Software project that allows Linux and UNIX servers to interoperate with Microsoft Windows clients. The reason for this is clear; Samba3 allows Linux and UNIX servers to replace Microsoft Windows NT Domain Controllers and will add great value to any Operating System which includes it. However, Samba is also developed and distributed under the GNU GPL license, in exactly the same manner as the Linux kernel code that SCO has been criticizing for its lack of care in ownership attribution.
We observe that SCO is both attacking the GPL on the one hand and benefiting from the GPL on the other hand. SCO can't have it both ways. SCO has a clear choice: either pledge not to use any Open Source/Free Software in any of their products, or actively participate in the Open Source/Free Software movement and reap the benefits. For SCO to continue to use Open Source/Free Software while attacking others for using it is the epitome of hypocrisy.
The strength of Open Source/Free Software is that it is available to all without restrictions on fields of endeavor, as the Samba Team believes the ability to freely use, modify and learn from software code is one of the grounding principles of computer science, and a basic freedom for all.
Because of this, we believe that the Samba must remain true to our principles and be freely available to use even in ways we personally disapprove of.
Even when used by rank hypocrites like SCO.
Jeremy Allison,
Marc Kaplan,
Andrew Bartlett,
Christopher R. Hertel,
Jerry Carter,
Jean Francois Micouleau,
Paul Green,
Rafal Szczesniak.
Samba Team.
What is being stated is as follows:
:)
1. To use GPL covered software you have to agree with the GPL.
2. SCO says GPL is invalid
3. Therefore SCO cannot agree with the GPL.
4. If you disagree with the GPL you are not allowed to use the software.
5. Kernel, GCC, GNU, samba, etc all sue SCO for violation of the license and SCO goes away.
*6. ???
*7. Profit
Note: * 6 and 7 are just for a bit of karma whoring
it is only after a long journey that you know the strength of the horse.
SCO won't be protecting users of GPL software it distributes either.
This is just doubletalk.
I would love to see SCO explain how their distribution of GCC, Samba or any other GPL code is any different from someone elses.
I don't think SCO has a general IP strategy. They are using open source, and fighting it at the same time.
I heard they had a Using GNU tools seminar at the same conference where they informed people about the dangers of the GPL. Maybe a corporate strategy would help them?
GPl is based in copyright. You are setting out a set of copying rights that increase, not decrease the minimum allowed rights granted under the consitiution and law. As such, it is well established that a person may fairly grant or not grant rights of copying to other persons as they see fit. You may forbid coying entirely (legal), you may grant Public domain (you retain no rights to restrict copying) or you may stipulate resonable actions to allow copying. Mostly, this means money paid to the copyright holder.
The GPL thence is misnamed - it is more fo a copyright "rules of copying". As you have agreed to release your code under the GPL (read, rules of copying), the person doing the copying is bound by the rule you allowed or disallowed copying.
You follow me?
Okay, in this case the GPL says you are allowed to copy as long as you provide source code for free and a whole bunch of other blah in the same vein. As the copyright holder you are allowed to stipulate these resonable actions so that others may legally copy your work.
Thence, SCO is misstating the GPL - it is NOT a licence as per say. The only case the GPL has to be examined for is IF it is a resonable set of copying rules. I believe that as SCO has and continues to release code under the GPL, a case can be made they accepted these terms of copying as fair so to be honest even fi the first court has a brain fart and rules for SCO, it will not survive appeal. Copyright law is well understood and believe it or not, fairly clear.
SCO therefore they have a problem. Code is still copyrighted by the original writers and unless you public domain your right, it is never lost. SCO is copying Linux code AGAINST the wishes of the real copyright holders.
I'm afraid the GPL is better thought out that some realise and it's strength is the fact it is allowable under copyright law. That is a clear fact. The ONLY problem it could face is if it is an unresonable demand to grant rights of copying.
And if it is shown to be such, SCO is still fucked, cause they are distributing copyright code they dont own. Case reverts to normal copyright laws. All it will take is ONE person to sue SCO under copyright breach.
I really dont see how SCO can win.
So, if I bought a book by Stephen Ambrose, who has been accused of plagiarism, can the 'original' author sue me? It seems to me that plagiarism is the same as or similar to the type of copyright infringement that SCO is suing about. The book I bought isn't covered by any type of license that I'm aware of, and as far as I know, I have nothing that indemnifies me from any copyright infringement that might be in the book. Or if there are laws that protect me personally from legal action in owning a book that contains plagiarized text, why would I be personally liable from using a Linux kernel that may contain some of SCO's copyrighted code? After all, I obtained both in the good faith understanding that I wasn't intentionally committing some type of legal offense (or crime).
I've read that future editions of Ambrose's works will contain the correct attributions. How is this different that the potentially offending code being removed from the Linux kernel? And as far as I know there still isn't anything that compels me to purchase the newly corrected edition of the book. That would seem to leave it up to me to either upgrade/downgrade my kernel or not...
--All I want is a warm bed, a kind word, and unlimited power.--