SCO Fails to Produce Evidence 651
BlueSteel writes "For those of you that need that daily SCO fix, Groklaw has the declaration of Ryan E. Tibbitts of SCO, stating why they haven't produced any evidence... and that they need recent AIX and Dynix/ptx code from IBM before they can comply."
uh.. (Score:5, Funny)
For those of you that need that daily SCO fix
Daily? Has
Re:uh.. (Score:5, Funny)
No. See today's story, for example. Oh, wait...
Re:uh.. (Score:5, Funny)
1. well, it has been the holidays and
2. if you want your sco stories to be delivered on time, ibm will have to hand over some code from aix first.
Re:uh.. (Score:5, Funny)
Topic in #os: hey guyz, stop pickin on irix.
<SCO> w00t! i bought unix! im gonna b so rich!
<novell>
<novell> whoops. was that out loud?
<atnt> rotfl
<ibm> lol
<SCO> why r u laffin at me?
<novell> dude, unix is so 10 years ago. linux is in now.
<SCO> wtf?
<SCO> hey guyz, i bought caldera, I have linux now.
<red_hat> haha, your linux sucks.
<novell> lol
<atnt> lol
<ibm> lol
<SCO> no wayz, i will sell more linux than u!
<ibm> your linux sucks, you should look at SuSE
<SuSE> Ja. Wir bilden gutes Linux fur IBM.
<SCO> can we do linux with you?
<SuSE> Ich bin nicht sicher...
<ibm> *cough*
<SuSE> Gut lassen Sie uns vereinigen.
* SuSE is now SuSE[UL]
* SCO is now caldera[UL]
<turbolinux> can we play?
<conectiva> we're bored... we'll go too.
<ibm> sure!
* turbolinux is now turbolinux[UL]
* conectiva is now conectiva[UL]
<ibm> redhat: you should join!
<SuSE[UL]> Ja! Wir sind vereinigtes Linux. Widerstand ist vergeblich.
<red_hat> haha. no.
<red_hat> lamers.
<ibm> what about you debian?
<debian> we'll discuss it and let you know in 5 years.
<caldera[UL]> no one wants my linux!
<turbolinux[UL]> i got owned.
<caldera[UL]> u all tricked me. linux is lame.
* caldera[UL] is now known as SCO
<SCO> i'm going back to unix.
<SGI> yeah! want to do unix with me?
<SCO> haha. no. lamer.
<novell> lol
<ibm> snap!
<SGI>
<SCO> hey, u shut up. im gonna sue u ibm.
<ibm> wtf?
<SCO> yea, you stole all the good stuff from unix.
<red_hat> lol
<SuSE[UL]> heraus laut lachen
<ibm> lol
<SCO> shutup. i'm gonna email all your friends and tell them you suck.
<ibm> go ahead. baby.
<SCO> andandand... i revoke your unix! how do you like that?
<ibm> oh no, you didn't. AIX is forever.
<novell> actually, we still own unix, you can't do that.
<SCO> wtf? we bought it from u.
<novell> whoops. our bad.
<SCO> i own u. haha
<SCO> ibm: give me all your AIX now!
<ibm> whatever. lamer.
* ibm sets mode +b SCO!*@*
* SCO has been kicked from #os (own this.)
Re:uh.. (Score:5, Funny)
* SuSE[UL] is now novell[SuSE]
Re:uh.. (Score:3, Informative)
Yes. We form good Linux fur IBM.
I am not certain..
You let unite us goods.
out loudly laugh
Gentoo! (Score:4, Funny)
Re:Gentoo! (Score:5, Funny)
Re:Gentoo! (Score:4, Funny)
Re:Gentoo! (Score:5, Funny)
[16:05] gentoo has joined #os
[16:06] gentoo: PORTAGE IS COOL!! RPM & DEB SUCK ASS!
[16:06] gentoo: PORTAGE IS COOL!! RPM & DEB SUCK ASS!
[16:06] gentoo: PORTAGE IS COOL!! RPM & DEB SUCK ASS!
[16:06] gentoo: PORTAGE IS COOL!! RPM & DEB SUCK ASS!
[16:07] debian sets mode +b gentoo!*@*
[16:07] gentoo has been kicked from #os (stop flooding lamer)
Re:uh.. (Score:5, Funny)
[SuSE] Herr Mandrake, willst du mitgekommen?
[Mdk] Je ne sais pas. Peut-etre je me rendrai juste a la faillite.
[SuSE] Na ja.
Re:uh.. (Score:5, Informative)
Because I copied it from bash.org, and I didn't want to take credit for it.
Summary (Score:5, Informative)
(1) Hey, it was the holidays. This lawsuit isn't important enough to bother our directors with over Christmas.
(2) Well, we're pretty sure that they're infringing somehow, but despite the fact that we claim to own this stuff, doggone if we can't find a current version of it. Anyway, once IBM spells it all out for us I'm sure we'll come up with something that looks like that other thing. Probably.
Another FA you can avoid R'ing (link found at Groklaw): the Motley Fool [fool.com] looks at the 'shakedown' of Linux providers: "with the entire computing world putting its money behind Linux, it appears that, for SCO, the apocalypse is now."
Re:Summary (Score:5, Funny)
Re:Summary (Score:3, Interesting)
They need *proprietary* code from IBM in order to prove that Linux, an *open source* OS, the source widely downlodable... contains SCO proprietary code?
Re:Summary (Score:5, Insightful)
Actually, SCO has a point. They claim ownership of the code in UNIX derivatives, of which AIX and the rest are examples. The fact that SCO has never seen or handled that code in any way is irrelevant. It is perfectly possible that IBM has infringed on SCO's property by copying code that IBM wrote for AIX/others into Linux. In which case, the only copy that SCO currently has access to is the Linux copy. After all SCO didn't write the code. IBM did. SCO just owns the rights.
Re:Summary (Score:5, Informative)
Re:Summary (Score:5, Insightful)
I think SCO's case -- the real case, the one that has to be argued in court -- will acknowledge that IBM owns their own work, and that they can do anything they want in terms of embedding it in binary form in their own products, but that IBM requires SCO's permission to reveal the source code or even the methods used to third parties. That's a fairly fine distinction. There are lots of situations where you own something, but there are constraints on the uses that you can make of it. I think SCO will lose, mostly on grounds that (a) most of the SysV "trade secrets" aren't, (b) the previous owners of the contract didn't adequately protect their trade secret rights (so SCO can't successfully attempt to reclaim those rights), and (c) neither party who signed the contract in 1985 intended for it to apply this far into the future.
Re:Summary (Score:5, Informative)
Ergo, SCO is smoking crack.
Re:Summary (Score:5, Interesting)
Re:Summary (Score:5, Informative)
Except that's not quite right. The truly pathetic side to this story is that it isn't IBM that produced the evidence that the license doesn't say what SCO claims it does. It was SCO. That's right, they attached the side letter (as Exhibit C [sco.com]) establishing that IBM had rights to their own work to their original complaint. It's still right there on their website. Their own evidence debunks the main theory behind their case!
Re:Summary (Score:5, Interesting)
Now Mr. Tibbits says they need recent AIX and Dynix/ptx code from IBM before they can comply.
Have they identified offending lines in the kernel source or have they not. Darl claims they have already matched code to the Unixware code and now they can't seem to reproduce it for the court. What's wrong with this picture?
Re:Summary (Score:5, Informative)
Re:I don't understand... (Score:5, Insightful)
The court should order SCO and IBM to both put their codes into blind escrow and then release the code from both to the legal team for each so that no funny business can go on =and= so that both sides have equal footing for making their cases. Same for any other participants who have been accused by SCO.
May not be standard procedure, but this is a rather odd case. It would definitely help both companies show to their customers that they are playing fair.
Additional code discovery could happen, but it should always be under view of the court.
There is little if any code ... (Score:4, Insightful)
Re:Summary (Score:5, Insightful)
They may have taken steps to ensure that current programmers had never had any access to protected UNIX or AIX code, but I doubt it goes much further than that.
Surveys show that adoption of Linux is being affected very little by this thing.
IBM already has enough lawyers to darken the skys and a few million $ spent probably will be more than offset by the press and PR of it all when things are finally settled.
As far as I can see only SCO is really being affected. They haven't produced anything new for some time so that's notthe issue... but according to their SEC filings, this thing is costing them millions. (Something like $9 million in the last quarter alone.)
Re:Summary (Score:5, Informative)
I hope not (Score:5, Interesting)
That would be awful both for Red Hat and IBM (who should otherwise be getting some amount of reparations in their countersuits) and for SCO's current investors, some of whom probably imagine that the US has a swift justice system that wouldn't allow SCO to make outright lies without sanction.
Reserve your ire for SCO's current leaders, particularly the ones whose insider trades (filing to buy stock options and sell shares after SCO's internal discussion of the IBM litigation but before that litigation became public knowledge) and deception have earned them millions of dollars [yahoo.com] so far. These guys are next to the Enron executives in the United States' ongoing [pcworld.com] experiment [guardian.co.uk]: "How hard is it to profit from million dollar lies and escape punishment?"
Amazing (Score:5, Funny)
Shock horror! (Score:5, Funny)
Re:Shock horror! (Score:4, Funny)
-bk
Re:Shock horror! (Score:5, Funny)
Exactly. That's why they need more time. to PRODUCE the evidence
Re:Shock horror! (Score:4, Funny)
Somewhere on the planet, at this precise moment, an SCO lawyer is corralling about a million monkeys into a room with about a million workstations...
Re:Shock horror! (Score:4, Funny)
Re:Shock horror! (Score:3)
Re:Shock horror! (Score:5, Funny)
what was the gist of the south park episode again?
Re:Shock horror! (Score:5, Insightful)
It's worse than that. In the 5 December hearing, the judge ruled that they can't ask for ANY of IBM's stuff until they provide answers to IBM.
Tibbets' declaration seems to say, "give us the stuff you said we can't have, and then we'll give you the stuff you told us we had to provide".
Since when... (Score:5, Insightful)
Re:Since when... (Score:5, Funny)
The Ministry of Truth feels your comments are ... (Score:5, Funny)
Oh, and the chocolate rations have been increased to 5 units.
Re:Since when... (Score:3, Insightful)
Ummm... Isn't it IBM who is being sued, and therefore is the defendant. SCO has to prove that an offence was committed, then it's up to IBM to defend themselves.
SCO hasn't provided any evidence of infringement for IBM to defend themselves against.
Re:Since when... (offtopic) (Score:5, Informative)
Not entirely related, however, an interesting facet of UK law as it stands at the moment, when presented with a NIP (Notice of Intended Prosecution) for a speeding charge (taken by a speed camera), the recipient has two choices:
1. Fill in, sign the form and send it back, thus incriminating yourself.
2. Refuse to fill it in and get charged with obstruction of justice.
There is a "loophole" that involves, amongst other things, the defendant returning the form without signing it, going to court, adn finding the police can't use it as evidence. Somethign along those lines, anyway.
That snippet of our law aside, what SCO are attempting to do would surely be laughed out of every court in teh land. I await the judges decision with baited breath. SCO is going down - of that there's no doubt, however, I wonder whether the main protagonists in this case will be able to walk away scot free under the protection of Canopy. I sincerely hope that won't be the case.
Re:Since when... (Score:4, Interesting)
No, but it is his job to turn over evidence to the prosecution in accordance with court orders. For instance, if you wanted to prosecute someone for a GPL viokation, you'd probably need to demonstrate that your suspicions of GPL violations are credible, at which point a court will for the defendent to hand over source code to you to verify your claim and win your court case.
There is no defendant (Score:4, Informative)
In civil court you CAN be compelled to give up things to help the plantiff's (what you call the person that brought the suit) case. There are limits, of course.
Civil and criminal courts play by very different rules.
Where's the news? (Score:4, Funny)
Re:Where's the news? (Score:3, Insightful)
This just in.. (Score:5, Funny)
If anyone believed SCO, I hope they feel silly right now...
And it completely unrelated news (Score:5, Funny)
I'm not convinced they're unrelated.
Old version? (Score:5, Interesting)
I doubt that IBM would have just turned over source to AIX as part of the trial, much less an old version, so how did they get it?
Re:Old version? (Score:5, Informative)
A few years back, when Intel was first spouting off about Itanium, IBM and SCO were working togethere on a next-generation Unix project targeted at Itanium. That project was called "MERCED". That's most likely where that code came from.
Re:Old version? (Score:5, Informative)
Re:Old version? (Score:5, Informative)
Project Monterey was going to take the best bits of SCO UnixWare (basically SVR4.2), SCO OpenServer (SVR3.2 but with lots of user/admin friendly stuff which is why people bought $200m of it each year) and AIX (ancient roots in SVR3.2 but thoroughly IBMized), and combine them all into a kick-ass UNIX for Itanium. Itanium was perceived at the time as where the commodity 64 bit chip market was going and the idea was to band together against Sun (Sparc) and Compaq/Digital (Alpha).
Work did start on Monterey, but the problem was that IBM ended up doing most of the work. It was supposed to be equal, but SCO just did not have the people. (At the time Windows NT and Linux were advancing so quickly that SCO was having a hard time even pretending to be relevant any more).
SCO ended up doing less and less towards Monterey and eventually IBM just gave up and called it quits.
Both Windows NT and Linux were eating away at SCO's UNIXes. SCO tried various things such as clustering and data center acceleration programs, but it was a lost cause. There was however some one time revenue from people doing Y2K upgrades, which SCO's able management didn't realise was one time.
Caldera then got interested in the SCO channel (15,000 mom and pop shops around the world that sold OpenServer in conjunction with other software, hardware and services - think outfitting a dentists office). SCO and Caldera came up with some very convoluted agreement that even the SEC couldn't understand. They then did a second agreement, and all the UNIX stuff when to Caldera, and the original SCO became Tarantella.
Caldera continued to suck because the 15,000 mom and pop shops did not like being lectured to, and could do Linux by themselves. They didn't need Caldera. Caldera couldn't make money at $24 a copy. Eventually they decided to plunder the OpenServer/UnixWare revenue stream (OpenServer customers are extremely loyal) and came up with various licensing plans noone was interested in.
Finally they decided to take a gamble on taking on IBM
(Disclaimer: I am an ex-SCO employee, but had nothing to do with any of the crap other than as a highly critical observer).
Re:Old version? (Score:3, Funny)
Let's see if it works:
1. Sue Microsoft on basis that they have infringing code in windows.
2. Request windows source in order to comply with courts to provide the "infringing code".
3. Have a good long laugh reading the source.
Re:Old version? (Score:4, Insightful)
SCO Attorney: Please, IBM, give us evidence (Score:5, Funny)
Judge to commence laughing in 5..4..3..
Can't wait... (Score:5, Funny)
[sits back and grabs some popcorn] This should be good...
IBM: Not exactly "Fire Breathing" (Score:5, Funny)
Not sure if "fire breathing" is quit the right way to describe the IBM guys...
As we know from the fact that while "The Darl" God, his parents must have hated him) et al spew FUD like an angry volcano, IBM has more or less been quietly operating in the background, most likely when the time is right the IBM suits will calmly pop open their identical briefcases and extract the dental drills, pliers, and electrical probes...
SCO says: (Score:5, Funny)
D'oh! (Score:5, Funny)
I'm sure glad... (Score:4, Funny)
Re:I'm sure glad... (Score:5, Funny)
Sounds like a Spongebob Squarepants character.
Re:I'm sure glad... (Score:4, Interesting)
SCO has certainly earned quite a reputation. I am sure it will be very difficult for SCO employees to find work elsewhere because employers will fear that SCO will go after them for absurd acusations of IP theft.
Proboably not (Score:4, Informative)
Having picked the fight, SCO is now powerless to stop it. By the time the dust settles, SCO should have been proved to have no IP interest in anyting because of Novel's "non-exclusive right to use, with no transfer or ownership" sale of rights to SCO of System V code.
IBM's counter-suit will probably bankrupt SCO, and if it doesn't it will pre-prove as a matter of legal record, the baselessness of SCO's claims. That "Takes care of" the hard part of Red Hat's suit, leaving them to suck up any unspent tidbits.
Since there won't be enough money to go around, one of these other companies will end up with the bulk of any possible IP SCO would have.
the natural outcome may well be the complete open-sourcing of whatever there is to be had. Neither IBM nor Rred Hat, having devalued SCO's claims, are likely to miss the PR win of taking that near-zero-value spoils of war and tossing it to the OS comunity.
The "all of your base belong to whoever wants it" final stab in the eye at Daryl would be all of 1) poetic justice, 2) wonderfully vengeful, 3) good PR use of a proven-unenforceable, depreciated assett, 4) likely to simplify the lives of whoever ends up "successor in interest" in this stuff, as it would prevent any form of back-blast claims.
So IBM and/or Red Hat just say, "here, we pryed this out of their cold, dead hands. We didn't really want it, and it will do everybody the most good if we put it here on (source-forge, etc). Share and enjoy..."
Oh, man, I'm picturing Lionel Hutts (Score:5, Funny)
Was it the one where he sued over Itchy & Scratchy?
He stammers out something like "Well, um, we don't have a copy of it... we were kind of hoping that you did."
Re:Oh, man, I'm picturing Lionel Hutts (Score:3, Funny)
Hutz: We have hearsay and conjectural, those are KINDS of evidence.
Re:Oh, man, I'm picturing Lionel Hutts (Score:3, Funny)
Hutz (SCO Lawyer): We have plenty of hearsay and conjecture, those are KINDS of evidence.
And from the street... (Score:5, Funny)
SCO logic (Score:3, Insightful)
- cnb
Increasingly hilarious (Score:5, Funny)
IBM: prove it
SCO: no, you prove it!
wtf? How did they get this far? I rarely root for the 800 lb gorilla, but it appears the strategy for SCO is just to tie this up in litigation as long as possible.
There is a different issue here... this has nothing to do with copyright infringement anymore, it is political maneuvering of consumer views. But, I'm preaching to the choir at this point.
This case should stop now... (Score:3, Interesting)
Solution (Score:5, Funny)
IBM response (Score:5, Funny)
MotleyFool is writing off SCO (Score:5, Informative)
Well... (Score:3, Funny)
Techie: That's not how it works, s--
Darl: Don't question me! You have a law degree, right?
Techie: Uh, yes, I do... u--
Darl: Then from now on you're our goddamn lawyer, and MAKE SOME EVIDENCE.
Please Copy and Distribute prosecute-sco.html (Score:5, Interesting)
From the page:
It also suggests complaining to the securities and exchange commission, which you're entitled to do if you've lost investment money as a result of any wrongdoing that SCO might have committed.Thank you for your attention.
Question for the lawers among us ... (Score:5, Funny)
Just curious.
Re:Question for the lawers among us ... (Score:5, Funny)
So I believe the answer to your question would be "please sir (or ma'am), may I have some more?"
Statements 14, 15 and 16 (Score:5, Funny)
"15. Further, we have only one CD of Dynix/ptx source code that was produced by IBM, and this CD only contains a limited history of Dynix/ptx releases. It was therefore not possible to directly compare IBM's contributions to Linux with another likely source of those contributions, namely the missing versions of Dynix/ptx.
"16. Our engineers have reached the conclusion that parts of Linux have almost certainly been copied or derived from AIX or Dynix/ptx. In those cases, confirmation of this opinion would require access to more current versions of AIX and Dynix/ptx.
Ok, I'm confused. Since when do two false's make a positive.
Ohh..they must be XORing the system. That makes perfect sense.
Okay so is it over now? (Score:3, Interesting)
So they failed and the excuse is pretty ridiculous. Their claim is that Linux's code is owned, in part, by SCO. To prove this, they only need to show their code in their source in their product and show where it is identical within Linux's code. How is it necessary that IBM show completely unrelated code from AIX?
The judge didn't care that it was over the holidays and was probably very aware of that fact. Using the judge's knowledge as an excuse is probably just insulting enough to make the judge rule against SCO on this matter.
So I guess we wait to hear the wrath of the judge now?
So they've never had specific proof ! (Score:5, Interesting)
In other words they've never had specific proof.
So their whole case is apparently hinged upon their tenuous claim to ownership of IBM authored code which they claim they own, but have never seen. They hope they can claim ownership of that code on the basis of a very broad interpretation of derivitive works and that code IBM wrote into AIX was derived (by their incredible definition) from their copyright works (the missing link) and that they then moved this into Linux.
IANAL but you can't run around claiming someone infringes on your copyrights and then go on a fishing expedition for the evidence, you need something evidence to present to the court in the first place.
This bubble may burst much sooner than I had anticipated.
Talk About Inaccurate (Score:3, Informative)
So c'mon people, RTFA first before cheering "woohoo! SCO suck! We are win!".
Not exactly true (Score:5, Insightful)
So, while they have complied in legal terms, they have weakened their case in a significant order of magnitude. Not only that, but they have also weakened their case for any of their prosprective targets in their scoSource shakedown fiasco.
Maybe inaccurate on a legal basis, but significant when looking at the big picture.
I read Groklaw as well by the way.
Fiduciary Duty (Score:5, Insightful)
With a $3Billion (pinky to mouth) lawsuit at stake, the friggin' directors couldn't give up their holiday vacation to provide info that the Court specifically ordered them to? Now, IANAL and IANACPA, but that would seem to be a breach of fiduciary duty!
Obviously (Score:5, Insightful)
If they were saying that AT&T gave IBM the Unix source, and SCO inherited the Unix source, and IBM put the Unix source into Linux, then SCO would have a copy of the source of the infringement. If SCO doesn't have a copy, then that's a damn good sign that they never owned it.
Clearly their interpretation is that anything IBM ever wrote related to UNIX is covered by their new UNIX copyright.
Does George Lucas own the copyright to every Star Wars book ever published--say, the Timothy Zahn trilogy?
Re:Obviously (Score:4, Informative)
Yes, actually, he does.
Improper initial statement (Score:4, Informative)
what Groklaw? (Score:5, Interesting)
I was trying to keep an eye on Groklaw when it suddenly stopped responding, so I figured it was time to head over to slashdot and see what was new. Sure enough, I found this article pointing to the smoking ruins of what used to be an informative site.
I wonder if it's time for OSDL to offer their hosting services to Pamela?
New SCO deal (Score:4, Funny)
The thing that's most amazing to me.. (Score:5, Informative)
but put it in context, and it's absolutely mind-bogglingly stupid.
SCO and IBM have been going back and forth for months on the issue of discovery. SCO keeps saying they need evidence from IBM before they can produce their own proof, and IBM says that they need to know what they're being accused of.
The judge reads all this crap from SCO (about how they can't prove their case until IBM gives them evidence) and decides that IBM is in the right - but she decides to give SCO the benefit of the doubt.. she tells them "I've read everything you've given me, and you're wrong. Unless you can convince me otherwise, I'm going to force you to comply with IBM's discovery.
So SCO goes on about how they can't prove their case until IBM gives them evidence - and the judge says "You have failed to convince me. Either you have evidence they did something wrong or you don't, it's shit-or-get-off-the-pot time. You have 30 days to produce evidence to back up your claims. If that's not enough time, tell me now, and I'll extend it."
SCO says "No, that's enough time."
So 30 days pass, and SCO's answer is "We can't do it because IBM won't give us the evidence."
I mean - come on - refusing to comply to a compel order is stupid, but repeating the exact same excuse the judge has already rejected as your reason for refusing to comply is so completely unbelievable it's unreal.
And then (to salt the wound) they claim they didn't have enough time - after explicitly being asked by the judge if 30 days was enough.
Is SCO trying to lose on purpose?
Information content analysis (Score:5, Funny)
Seems thier case is going to sink or swim (Score:5, Interesting)
I (we) uniformly disagree on the theory that everything IBM added to AIX must not also be added to Linux. Because substantive technologies are not derivative works, specifically:
However, to devil's-advocate this:
Device, filesystem drivers used with Linux may be considered derivative works, even if not shipped with the Linux distribution, and therefor subject to GPL. *Linus* has said exactly this, and while I personally doubt that SCO is going to prevail (see contract details between AT&T/Novell/SCO/IBM which decidedly establish that this type of additions are not restricted to confidentiality or considered deriviative works.
Which means basically that if the FSF had licensed a GPL Unix to IBM, they would right now be taking the reciprocal (but logically identical) position as SCO is with respect to license requirements.
I continue to think SCO loses (and continues to look like halfassed morons), with this tack but remember the Linux community does apply similar logic around IP.
Dear Darl! (Score:4, Funny)
Finally everyone also laughs at you.
I hope the money is worth all that.
A Theory (Score:5, Interesting)
I think what happened is this:
Now things are going to get nasty for SCO. What I'm surprised about is how people keep getting surprised by IBM's "Ninja Lawyers" and how tight their IP controls are. It's a long running industry gag.
Santa Claus, the Easter Bunny, and the SCO... (Score:4, Funny)
That's a lot of holidays! (Score:4, Funny)
Article is GROSSLY misleading (Score:5, Insightful)
This includes an answer to IBM's request that they identify (with specificity) all rights that they claim to the Linux operating system.
We haven't seen this answer (yet). IBM will presumably claim that SCO has NOT answered its questions on January 23rd. But the title of the article is false. SCO _HAS_ produced evidence. The only question is whether or not that evidence is meaningful.
Versions (Score:4, Informative)
For one, demanding newer versions of Dynix past 4.6.1 is apparently amusing, considering no newer versions exist. I suppose IBM could write one, but that's pushing discovery a bit far.
Secondly, failing to find misappropriated code between Linux and a version of AIX SCO has rights to is significant -- it means anything AIX-like that IBM has in Linux has to post-date the granting of code from SCO (or SCO's predecessors). Since the contract explicitly gives property rights to IBM for all of their own modifications, IBM has neatly caused SCO to show that Linux's similarities to AIX, if any, did not occur within the "protected window" that SCO purchased ownership of.
Elegant.
--Dan
I KNOW how SCO can get their proof!!! (Score:4, Interesting)
HAHAHAHA
What a JOKE.
It gets better if you actually READ the documentation that is posted on GROKLAW - like section 13 for instance.
The premise of the SCO claim is becoming painfully apparent. The claim is that the moment IBM put ANY new code into AIX that this new code became a derivative copy of AIX and thus SCO has the right to control it.
I shall use an analogy here - an opera.
======================
I write an opera and you listen to it. You also are a talented song writer just as I am - perhaps more talented and you can easily write your own operas. But - this is not what happens. For whatever reasons you decide to IMPROVE my opera and then release it.
So you add in some new songs of yours to my opera and your version becomes more popular than mine. Mine in fact dies. So - do I have claims apon your version of the opera? Do I have claims against your songs? Do I have claims against say a single line you modified in one of my songs? How about individual words you might have changed? What if you changed the spelling of some of these words? Should I have claims against the sequence of letters you used to spell a word?
So you see - since YOU had the power to NOT use or contribute to my opera, I do get to make all sorts of outragous claims and I do get to control you.
On the other hand, suppose you are NOT a talented writer. Suppose you are just talented at arrangments. Suppose your friend is a talented writer and you find he has all these great songs that you can import into my opera. Clearly, your friend will not lose the rights to his copyrights by your actions. In fact, he may and I may grant you the right to make a derived opera so it is clear in this case that nobody has stepped on anyone's toes and there can be no claims by me on you.
The confusion stems from the fact that there is no boundry when you make the modifications. I get to claim you are making a derivative work - which you may have the right to do. And the question then becomes whether I get to control your work because some of it happened to be used in something I wrote before you did.
In staying with the analogy of the opera, suppose we get to the point where you feel your songs have a life of their own and you chop out 100% of my original material. Basically this is what IBM did.
Well, when at least _SOME_ of my material was in the derived work I may have had the right to control some aspects of the derivative work. When NONE of my material exists any longer we are left with the question of whether what you created is still a derived work which I get to control.
===============
So is it?
Well - In a way it is. And in a way it isn't. The way I read copyright law, I may in fact still get to control your work even though it is exclusively your work.... simply because during its history it was co mingled with mine. The premise for this claim is that your work would NEVER have existed were it not for my work and the structure it imparted.
This is a very important premise because when we look at software projects, the vast majority of new clean implementations suffer very bad teething problems and often lose their market share. Examples include Wordperfect, Mozilla and many others.
However, the practice in our industry is that each separate function bears its own copyright. As to code inserted in-line in functions - well - that is not as well sorted out. It becomes pretty arbitrary and the vast majority of us simply chose to not waste our time fighting about it.
===============
New analogy:
Lets look at a house. I build a house on my lot and you buy the lot next door and live in my house. You pay rent to me and get a contract from me that you can make tenant improvments. You ar
WTF? (Score:4, Insightful)
15. Further, we have only one CD of Dynix/ptx source code that was produced by IBM, and this CD only contains a limited history of Dynix/ptx releases. It was therefore not possible to directly compare IBM's contributions to Linux with another likely source of those contributions, namely the missing versions of Dynix/ptx.
They said they HAVE the proof and you needed to sign an NDA to see it. Yet no all the sudden they don't have all the information required to FIND the evidence they need. So, all these claims are just speculation now? Well, if I can sue for 3 billion off speculation, someones poor multi-billion dollar company is in alot of trouble. Hmmm, I wonder how the judge will see this. What they claim to have had, and what they have are two different things. They have nothing and just admited to it.
SCO wants AIX and Dynix/ptx source code first (Score:4, Interesting)
SCO claims that their contract with IBM gives SCO all rights to any improvements to these Unix licensed products. In a way, that's kind of like GPL, except for corporate greed, although it seems that it did not provide for any means for SCO to actually get that source code they claim to own. SCO believes that IBM did develop improvements for AIX and/or Dynix/ptx (I presume the original Sequent license for Dynix had a similar provision), and that IBM also contributed those improvements to Linux. SCO thus believes that code they own is in Linux, but cannot positively identify it because they don't have the AIX and Dynix/ptx code to cross check with. Apparently SCO would assert that any code found in AIX or Dynix/ptx is either code originally licensed, or code that was added later by IBM and still covered under the license agreement.
The clause that gives SCO ownership of improvements to AIX and Dynix/ptx is itself suspect. If there is no provision for transferring that code to SCO, then how is such a clause to have any meaning. And how can it be determined if any improvements were developed by IBM or simply acquired by IBM under other licensing (including GPL) and integrated? If I had sold a piece of code to IBM that would improve AIX and/or Dynix/ptx, a contract between SCO and IBM cannot take ownership of the rights to that code away from me (and I have no contract with SCO). It would not be any different if IBM did this with GPL code. Nor would it make any difference if IBM did this with BSD code. And it wouldn't even make any difference with public domain code (since the public by definition has all rights to use it, so any ownership is moot in that case).
Suppose there is some common code in both Linux and AIX. SCO might well assert ownership of that code. But what if the code was originally in Linux and subsequently put in AIX (if it is GPL that might be a problem, but suppose it is a public domain, or BSD licensed piece of code). What if the code was in another free licensed OS like FreeBSD, and subsequently put in both Linux and AIX (in either order of time). Or it could be public domain code. SCO won't have any ownership rights to that code (although they could likely have usage right like anyone else).
SCO will have to do more than merely show that some code is in both Linux and AIX. They will have to prove that IBM developed the code and put it in AIX first, before putting it in Linux. If IBM put the code in Linux first, even under a GPL license, as original owner they also have the right to put it in another system under another license ... and more importantly, cannot subsequently withdraw the rights already granted under the first contribution. So if they put code in Linux under GPL, then put it in AIX under SCO's assertion of ownership rights through the Unix license (which is in dispute), IBM would not be obligated to make AIX open under GPL (since it is not putting it as GPL'd code in AIX). And since the rights under GPL are already released, even if SCO prevails to own the code because IBM developed it, it has no means to withdraw the rights already released under GPL. What SCO would have to prove is that the development was done at IBM, under IBM ownership, for AIX and/or Dynix/ptx, now subject to the disputed license, then donated to Linux under GPL. Just looking at the AIX and Dynix/ptx code isn't going to show that.
Suppose the worst happens and SCO prevails and the courts believe that certain (at that point identified in court) pieces of code are owned by SCO and their unlicensed distribution and use infringes on SCO's intellectual property. Linux can deal with this very effectively by simply releasing a new version (wanna place bets on how quickly that will happen) without any of that code from IBM. SCO's current case is against IBM, not against Linux. So even if SCO were to prevail, their recovery under that case is only against IBM. There will be two areas of infringement in Linux to consider: the past and the future.