Is Licensing SCO Unix Legally Dangerous? 85
cheros asks: "I'm starting to get very puzzled by the SCO licensing scheme - am I mistaken or is licensing SCO actually about the most dangerous thing you can do as business or end user using Linux? [disclaimer: IANAL and AFAIK, so get decent legal council - I might be completely wrong ;-)]
If I buy a copy of Linux from a provider, my contract is with that provider, NOT with SCO. In other words, if said provider has supplied me with something dodgy (and that is still very much an open question IMO), the issue lies with SCO and the provider, not with me and SCO, as I have no contractual relation with SCO in any way, shape or form. So, licensing SCO might actually CREATE that relationship and thus enable SCO to play further games with enforceable contractual obligations, something it currently lacks with end users. If that is correct it puts SCO in an even worse light (if that's possible) as that could mean deception as well as FUD. The latter might have become accepted in business and politics, but the former might actually be illegal in some countries. In short, as far as I can see you don't actually have a problem as a Linux end user...until you get a license. Comments?"
The one thing that licensing SCO linux will do is (Score:5, Funny)
Re:The one thing that licensing SCO linux will do (Score:5, Funny)
Linux users have friends? I mean, other than the little stuffed penguin I^H *ahem* they keep on the monitor?
Re:The one thing that licensing SCO linux will do (Score:2, Funny)
Re:The one thing that licensing SCO linux will do (Score:2)
Re:The one thing that licensing SCO linux will do (Score:2, Funny)
Re:The one thing that licensing SCO linux will do (Score:2)
You mean even less flattering than the nickname I already have?
This is worse than college football speculation. (Score:4, Informative)
Use linux, ignore SCO until they are done with IBM. And for the love of god quit asking slashdot, ask your lawyer.
Re:This is worse than college football speculation (Score:1, Funny)
Your contract is with the distributor (Score:5, Informative)
The upshot of this is that you as a consumer are safe from litigation, but if you were a distributor of the code (even passing a CD around the office would suffice) then you can be charged with copyright violations of SCO's code.
Re:Your contract is with the distributor (Score:2, Interesting)
Sco
Copies
Opensource
In which case I would like to see all SCO customers getting letters from linux kernel developers for violation of their copyrights. Linux developers have the same legal claim over SCO software, that SCO has over Linux, until a court decides something one way or the other.
Re:Your contract is with the distributor (Score:5, Insightful)
Re:Your contract is with the distributor (Score:3, Interesting)
Quoted from the July 28th edition of Information Week magazine in an Article by Larry Greenmeier titled "Sco Group Threatens Users in Linux Fight" p.24 -- sorry, I couldn't find a link online.
-Derek
NO NEED CONTRACT TO BREAK LAW (Score:1)
THROG HAVE STONE AXE. OOGG TELL Dancin Santa, TAKE AXE FROM THROG, GIVE OOGG. THROG angry. OOGG say "I don't have any contract with you, THROG, so your beef is with Dancin Santa." THROG probably say "THROG NO CARE, OOGG HAVE THROG AXE," crack OOGG in head with club.
Many examples of breaking law without contract. Examples include: theft, copyright infringement, cra
Re:NO NEED CONTRACT TO BREAK LAW (Score:1)
Let's say I steal your axe. you still have title to it, even though I have posession of it. When I'm caught, it will be returned to you.
However, let's say I sell your axe to CmdrTaco. If CmdrTaco reasonably believes that it is my axe, and pays fair value, he recieves title to the axe. Even if I am caught, CmdrTaco can keep the axe. However, I am liable for selling your axe without permission. This rule exists to protect buyers -- if I go to a store as a bu
ugh.. (Score:1)
So.. (Score:4, Funny)
Re:So.. (Score:3, Funny)
127.0.0.1 sco.slashdot.org
Re:So.. (Score:2, Informative)
Re:So...Show SCO how to ho! (Score:2)
"...may not produce anything of note anymore, but they do appear to know how to..." be really, really annoying. Let me suggest that SCO (Caldera? SCOCAL!) would produce something of value if they just had an idea, ya know, a clue of what to do?
Here's a an idea from which SCOCAL can attempt to make all the many millions they expected from riding Linux to the bank ("Hey, get off my penguin you fat bastards!"):
The problem: I keep pop-ups "turned off" on my browser (Opera) because they are annoying and on
Re:So.. (Score:2)
a) provable false
b) irrelevent to the point at hand
There is no case, SCO will lose in court. There is no difference between SCO suing IBM over JFS and me suing IBM over the Kennedy assassanation.
OSDL paper by Eben Moglen (Score:5, Informative)
It's a very well written 5-page document by FSF General counsel Eben Moglen, and can be found here [osdl.org].
Ciaran O'Riordan
--
Re:OSDL paper by Eben Moglen (Score:3, Informative)
Not a great rebuttal (Score:2)
I was looking forward to a good rebuttal but Mark Radcliffe's points are quite weak.
He argues that GNU/Linux users could be in violation because "Every time you load software into the processor of the computer, you're making a copy". If that's the best argument against Moglen's position then I'll continue to bet on Moglen. It could be deemed worthy of a day (year) in court but I'm content that it would ultimately fail.
Radcliffe also points out that "the only lawsuit on record to
Exactly! (Score:3, Insightful)
Boy, this legal stuff is fun -- hit me with another one!
Re:Exactly! (Score:3, Interesting)
Why should I, a purchaser (if I spent the money) and user of a product who acquired said product from a distributor who is responsible for the software bundling/creation, be responsible for it's illegal origins?
It's the vendors who should be penalized for the wrong doing, not the user. If Microsoft added software to the Windows without the proper licensing, then Microsoft should be to blame, not I. If GM steals an IP idea from another auto make
Re:Exactly! (Score:5, Informative)
Say you buy a used stereo you find listed in the classified ads of your local newspaper. Then, a week later, the cops knock on your door to tell you it was originally stolen. What do you think happens then?
If you bought it in good faith, you don't get arrested, no. But the cops take the stereo, and you're left to try and get your money back from the sleazeball that sold it to you.
"Intellectual Property" isn't an accidental name -- it's property. If, instead of a stereo, it was a piece of software, I'd be very surprised if the actual owner who's work was ripped off would actually be so hamstrung; rather, I'll bet they could very easily drag you into court and demand that you either a) pay up, or b) stop using the software.
Gee, kinda like SCO's doing right now! If we discover we actually ARE in some weird bent universe where SCO wins out in all this, fifty bucks says we WILL have to pay them or be branded pirates. But, we'll get to sue the hell out of RedHat, IBM, etc, to the extent that we actually paid them in the first place.
Now, this DOESN'T mean that I think SCO has a case here, at all. I'm merely suggesting that this argument doesn't strike me as holding much water (otherwise, an Ask Slashdot wouldn't be the first place we heard about it -- it's an angle the more legally attuned Bigs would be pounding SCO with in much more public fashion).
No, SCO is going to wind up in a world of hurt because they've ALREADY given their code away under the GPL.
Further, five bucks says there's a handful greybeards out there who have full sets of circa 1974 unix source code, fresh from their personal archives, ready and waiting to be grep'ed for whatever code SCO is claiming is theirs. Given Unix's long, crufty evolution, there's doubtless TONS of code in there that SCO is assuming is theirs, but in actuality isn't.
That, and they already gave away all their damn code under the GPL anyway. But then, I already said that
Re:Exactly! (Score:4, Insightful)
Re:Exactly! (Score:2)
Whether it's full-blown "Property" or not, you can't deny that Microsoft has considerable rights, and thus considerable say, about who can / can't use WindowsXP.
I don't think the minor semantic issues invalidate my point. I do apologize, however, for actually thinking, and occasionally coming to the conclusion that, from time to time, some o
Re:Exactly! (Score:2)
It's not a "minor semantic issue".
If you buy a book, and it turns out that the author is guilty of plagarism, does that mean you're liable?
No, it doesn't. As long as you're not making copies of the book (which would be illegal anyway), the plagarized authour would have no legal recourse against you.
Software is more like a book than a stereo - it's covered by the same laws, in fact. So your argument doesn't hold water.
Re:Exactly! (Score:3, Insightful)
I'll deny it. Microsoft has no rights regarding who can and can't use WindowsXP. They have one right about who can make copies of it. That's it. That is their only right, the right to control the creation of copies.
Re:Exactly! (Score:5, Insightful)
The problem is that they don't validate your point, either. Legally, your choices here are copyright infringement, patent infringement, and trademark infringement. Its clear that we do not infringe on SCO's trademarks because "Linux" is registered and in Torvald's name.
Our next choice is patent infringement. Their claims that every variant of Unix and piece of software written for Unix infringes on their "Intellectual Property" might have a claim here... but nobody's been able to turn up a patent in their name covering this. No patent, no infringement.
The last choice is copyright infringement. Here they might have some small fraction of their case against IBM: If someone at IBM took their written code and inserted it into Linux, SCO has a case. Even if the code was changed a little to avoid being a word-for-word copy, it would still bear the taint of being a derivative work or otherwise plagarized. In no way, though, could SCO claim to have copyrights on every piece of code in existance for Unix.
Failing that, their only recourse is breach of contract, which would be an issue strictly between IBM and SCO. If SCO wins on the grounds of that, they have NO recourse against any Linux user, because their contract is only between IBM and SCO.
I am not a lawyer, and there may be other laws I am unaware of, but that seems to pretty much cover the field as far as I'm aware.
Re:Exactly! (Score:2)
The only rights that Microsoft has via copyright law are the rights to determine how many copies of XP are sold. The so-called 'considerable rights' that microsoft claims to have come from your supposed acceptance of their shrink-wrap license. If you don't agree to their license then they don't have any hold on you...
If, for example, I buy
Re:Exactly! (Score:3, Insightful)
In other words, Linux is not in danger, as the cops knock on our door, take the offending code and we're left with some kernel hacker writing it based on established research papers, such as the RCU paper (sorry, not going to bother to link), and we're stuck getting our money back.
I don't want to both getting my money back from Re
Re:Exactly! (Score:5, Interesting)
It's not the same thing, because your example deals with physical property and the article's example is related to intellectual property and contractual agreements.
Why bother, when you get even the easy ones wrong. Especially when the article is basically rephrasing what Eben Moglen said; you know, the professor who actually does know "legal stuff".
But why do I get the impression that you're going to keep talking anyway.
Re:Exactly! (Score:2)
Moglen points out that copyright law is not relevant to customers "using" Linux. In much the same way that readers can enjoy a book or a newspaper without a copyright license, so can users of software -- unless they have agreed to additional use restrictions in, for example, a shrink-wrapped box of software.
If this
Re:Exactly! (Score:3, Insightful)
Because they have nothing to lose.
NOTHING about SCO's position makes sense. They're fucked, they know it, and they're trying a "hail mary" to see if they can stay afloat long enough to drive the share price up so they can dump their stock and have enough to retire on.
Re:Exactly! (Score:3, Insightful)
No, not exactly, but the analogy is there. What he is referring to is the nemo plus rule (from "nemo plus iuris ad alium transferre postest quam ipse habet"). This says you can never transfer more rights to anything than you had in the first place.
What you call physical property, is nothing but rights you have to a certain piece of matter. It
Re:Exactly! (Score:1)
If someone has 1 billion pieces of candy and you take one away then, yes they are deprived.
However, if someone has 1 billion pieces of candy and you make an exact copy, then they STILL HAVE 1 BILLION PIECES OF CANDY and you have one piece. Not 999,999,999 pieces.
So your analogy isn't quite correct.
Since this is a technically inclined group, allow me to pose a questi
Re:Exactly! (Score:2)
When, instead of buying a CD, you decide to download an mp3, you very well deprive the copyright holder of a right that's split from his right to licence it. So they are deprived of their right.
You can yell that they
Re:Exactly! (Score:2)
<sarcasm>And so many legal decisions are based on analogies rather than the law</sarcasm>
I merely quoted Eben Moglen. If you're saying he's wrong then that's your call, but I'm betting he knows more about copyright law than you do.
Re:Exactly! (Score:2)
Yes, they are. It's an often used tool for legal reasoning. In fact, the whole common law system is based on analogies and distictions between a case and precedents.
If you want to read about it:
http://plato.stanford.edu/entries/legal-reas - inter pret/
http://cyber.law.harvard.edu/bridge/Analogy
http://academic.udayton.edu/legaled/online
I merely quoted Eben Moglen. I
Re:Exactly! (Score:2)
You get 0/10 for using the tired cliche of saying something is "obvious" to lend a veneer of false credibility to your indefensible opinion.
You get negative points for choosing to call me a liar by claiming a misquote! That's your best argument? You're pathetic.
Re:Exactly! (Score:1)
Suppose I have a stereo. Then someone stole it to me. When the thief get caugh, it's too late because he sold my stereo to you. So I am screwed and I can't get my stereo back?
Hmmm. (Score:2)
Re:Exactly! (Score:3, Informative)
Since you bought it in good faith, and in legal fashion, you get to keep it!
Um, no, no you don't. There is a legal doctrine, nemo dat quod non habet (trans. "You can't give away what you don't have") that says otherwise. Since a vendor of stolen property does not possess title in the property, s/he can't possibly transfer it to someone else. Your only right over the property is a bare possessory right that's good against the entire world, except for the true owner.
After all, you didn't do anything wron
Re:Exactly! (Score:2)
Good point. So, if that's the case, why should SCO be denied their right to control the use of their code (assuming, for the sake of argument, that their claims are all t
Re:Exactly! (Score:2)
Re:Exactly! (Score:2)
However, when you start throwing terms like "primary estoppel" around, you very clearly a) more than just get any point that I might be trying to make, and b) are going to kick my ass, hard, if I try and argue against you any further on this, 'cause I'm clearly wa
Re:Exactly! (Score:3)
SCO is actively evading any attempt to make it show it's reciept. It is quite reasonable to think that they are full of sh*t.
Re:Exactly! (Score:2)
Good faith would also imply that the purchase was from a reputable dealer and not the crack head junky on the corner yelling "Stereo, 25 bucks homie!"
Re:Exactly! (Score:2)
For some reason the scenario that brings to mind is of Charlton Heston buying a gun that turns out to be stolen:
Perhaps I'm a sick fsck.
Stephen
SCO legal advice on slashdot. Just stop it. (Score:2, Interesting)
Seriously though, you're asking about the details of copyrights, sub-licensing and contract law on a site, which you have to admit, has shown it's opinion on this matter pretty strongly before.
If you are being pressured into buying an SCO license, how about you ask those that are pressuring you what exactly you are licensing? what rights does it grant you and how may those rights be revoked?
ie: Ask a lawyer. Don't ask slashdot.
why... (Score:1, Flamebait)
If you get busted with a dimebag, the police will confiscate it. It doesn't matter if you paid for it or stole it, or found it lying on the ground.
Re:why... (Score:1, Flamebait)
of course they take a dimebag you twit! if it were a can of soda, or some dorritos, or something LEGAL, then they wouldn't take it.
where does the dimebag come into this arguement? or did you just finnish off your dimebag before posting?
again, your are an idiot.
Don't contact SCO yet - if at all (Score:3, Interesting)
Before I start, they haven't even started offering Unixware for Linux licenses yet - so why are you considering taking precipitate action. At the very least wait until they offer it! (and no I'm not advising you necessarily take it when they do)
At least one lawyer seems to think you should not contact SCO [computerworld.com.au], but maybe that's just Australia!
A couple of other points have been raised from time to time:
1. If you download Linux from ftp.sco.com (or get a CD), then you are getting from SCO under a GPL license. Some might say it's the end of the story, but even if it's not... SCO supplied it to you under a GPL license which they claim to have rescinded or not accepted (even while distributing it) - what is to stop them also rescinding or saying that they don't accept (in future) whatever new license terms you get their stuff under? They've done it once (GPL), how do you know they won't do it again (Unixware license for Linux)
2. If you get Linux under some SCO license, you might be violating the GPL license of all the other kernel contributors (including individuals and large companies). If SCO gets destroyed, or even if not, as a result of this law suit, these people/entities could allege you broke their license, and sue you.... and I think yes they will find out who you are if they really want to, even if you SCO deal is confidential. The route they would take would (a) sue SCO, (b) get the list of SCO Unixware for Linux licensees from SCO through (a), (c) sue the Unixware for Linux licensees.
Re:Don't contact SCO yet - if at all (Score:2)
Re:Don't contact SCO yet - if at all (Score:2)
-a
Re:Don't contact SCO yet - if at all (Score:2)
Re:Don't contact SCO yet - if at all (Score:2)
-a
Note : Kernel on ftp.sco.com (Score:2)
they can offer other open sources software without destroying their case, but if they offer the kernel, which is GPL, then they release all code in the kernel via GPL. This is not like you can make SuSE linux GPL but not the artwork, the artwork is not IN SuSE Linux, but a file with it. The (supposedly)offending kernel code is IN the kernel theirfor would be GPL'd.
but again, i can't find kernel sources available on their site, and im not sure if the linux they release
Re:Note : Kernel on ftp.sco.com (Score:1)
Isn't this a kernel?
ftp://ftp.sco.com/pub/scolinux/server/4.0/update s/SRPMS/kernel-source-2.4.19.SuSE-106.nosrc.rpm
I'm too lazy to actually download it and check, but it certainly looks like it's a kernel.
Re:Note : Kernel on ftp.sco.com (Score:2)
still confusing why they're supplying patches to a kernel source they argue we shouldn't have.
Re:Note : Kernel on ftp.sco.com (Score:1)
Heh... just noticed you said "kernel source" not just kernel. Still... I'm wondering why they would call it kernel-source-2.4.19.SuSE-106.nosrc.rpm
Re:Note : Kernel on ftp.sco.com (Score:1)
I have searched for it in the past two weeks and see a "patch" but not the kernel itself, at least what I can tell is the kernel.
Seems the S.tupid C.orporate O.gre finally realized, after they said they were not distributing the source anymore, that they actually were for about six weeks or more, and finally removed it.
If anyone has logs of having downloaded the kernel source (complete with the code they say was "copied" to it) after the
Is Licensing SCO Unix Dangerous? (Score:1, Redundant)
Oh, now that I think about it I guess it would be dangerous to give SCO more money to try to destroy Linux with.
Re:Is Licensing SCO Unix Dangerous? (Score:1)
Could you lose your rights under GPL ? (Score:2)
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License [...then you can't distribute the work at all...]
So if you sign a licence with SCO, then that licence might impose conditions on you wrt. Linux that would be contrary to the GPL - and then you would no longer be able to copy Linux a
Correct (Score:4, Interesting)
And in this article [pcw.co.uk] he mentions "contract" 12 times, but only mentions copyright once, and that's only in regard to removing copyright statements. It's almost as if he is being coy -- making it sound as if there is copyright infringement without ever directly saying it. In other interviews, he also avoids the word, choosing instead words such as "infringing" and "Intellectual Property". The SCOvsIBM page [iwethey.org] makes a similar observation:
An important thing to remember is that you cannot be sued over the contract that SCO has with IBM. Third parties cannot be held liable for contracts that they did not agree to. So if you have no contract with SCO, they can only sue you on the basis of copyright infringement. And you can only be sued for copyright infringement if you have copied or distributed something.Do you really want to give SCO a new avenue by which to sue you? Given that SCO has not shown any evidence that anyone has infringed their copyrights, I don't see why you'd want to do that. SCO hasn't been exactly acting in good faith recently; I don't know if I'd trust any contracts they write up. Here's what Darl McBride says about SCO's use of contracts [yahoo.com] against their partners and customers:
If I were you, I wouldn't even let them know that you use Linux. Why give them any evidence to use against you later? Try to stay off their radar.