Slashdot Mirror
IBM Asks Court To Declare Linux Non-Infringing
A Cyclic Graph writes "We finally have a redacted version of IBM's Reply Memorandum in Support of Summary Judgment on Counterclaim 10 in SCO v. IBM. In short, IBM is asking the Court to declare that Linux doesn't infringe upon any of SCO's purported intellectual property. This document is the last word on that matter until the Court either declares there to be no doubt that Linux is free of infringement, or decides that that issue has to be decided by the jury. In their brief, IBM points out that SCO puts forth a convoluted set of non-answers referencing each other to disguise it's inability to answer IBM. Their set of cross-references is so complex that Groklaw readers graphed the claims to make what little sense of them they could."
It reads like the Pamela Jones version of an Andrew Dice Clay monologue.
Lacking <sarcasm> tags,
the NPG electrode was replaced with carbon blac
That graph is the very image of the mighty Flying Spaghetti Monster! Seems like he will soon touch SCO people with His noodly appendage. That explains why SCO called Linux people pirates tho, seems like it was some kind of flattery, or something like that.
> Their set of cross-references is so complex that Groklaw readers graphed the claims to make what little sense of them they could.
*deadpans* Honestly, that doesn't mean much--Groklaw readers will graph anything.
*clicks on link*
Oh, now. See, it's only about nine references deep. (Unless you get caught in an infinite loop between documents 27 and 187.)
Go look at the latest postings on Groklaw. There is a *ton* of redundancy between the various filings, but that's legal wrangling for ya. Anyway, if there was ever a time to actually go and read through this stuff, now's the time. I personally recommend the transcripts of the lawyers arguing the motions before the judge.
These filings show that IBM sees this whole thing was a baseless land-grab effected by a change in management. The estoppal and waiver arguments are so convincing and indisputable that you'd think a stock-holder lawsuit would be forthcoming. I mean, both Caldera and Santa Cruz had significant Linux business for significant periods of time. Presumably the shareholders held stock in part because of this. Apparently not enough to get rid of the board and management upon commencement of these shenanigans, but hopefully enough to make some noise once a verdict comes down.
In a similar vein, did SuSE stock get converted to Novell stock, or were they bought out with cash? If it got converted, then former SuSE stock holders may very well file a suit for the MS deal. Overall, in both cases, in seems curious that the stock holders seem helpless. If these companies were traditional F/OSS enemies, there'd be no surprise, but will people who bought stock in a Linux company really support being a traitor? I mean, really, these aren't people who bought stock in an oil company or GM. It's like investing in a solar power company or something you do at least in part for the principle of it.
SCO has no interest in a timely end to this trial and I question their ability to cover IBM's costs. Seems to me like SCO is screwing IBM's shareholders.
(IMHO)
A circle represents SCO's response to IBM on any one given point.
The number inside the circle represents IBM's claim.
The arrow (including the line) represents SCO's (so called) response.
e.g. the (187) -> (45) in the middle of the image means in response to IBM's claim 187, SCO is redirecting the court to SCO's response to IBM in IBM's claim 45. and so forth.
Its actually a pretty darn interesting ways to represents SCO's bullshit.
IBM does not really benefit is suing. SCO is broke. What are they going to get?
Engineering is the art of compromise.
from the good 'o days of "Hunt the Wumpus". http://en.wikipedia.org/wiki/Hunt_the_wumpus/
You mean it's not a Finite State machine?
-Ben
I have not seen IBM make this claim. What IMB has stated is that the 300-odd lines of code identified by SCO as infringing lack the originality required for copyright protection. Most are comments. Many of the remaining are #DEFINE statements in c language header files, the kind of stuff previously established in common law as unqualified for copyright protection.
Consider this:
I am a man. (copyright Gary Dunn, all rights reserved).
I could claim it, but no court would uphold my claim.
Now, go relax and unwind your brain. Software is generally recongnized as subject to copyright protection; there are specific portions of law which apply specifically to software. Don't worry, the GPL is not going to die.
Gary Dunn
Open Slate Project
I wish ... one could see such graphs ... for statements made by politicians.
Unfortunately, that cannot be mapped in three dimensions.
When our name is on the back of your car, we're behind you all the way!
"Without copyright the GPL would be unenforceable. It would also be unnecessary."
Completely untrue.
Without copyright, companies could (perhaps would have no choice but) release binary-only software with strong "product activation" which could take a while to crack. The next version of Microsoft windows and all future propriatory software would require hardware TPM. Hardware manufacturers would stop documenting anything at all, because they have no other protection for their designs.
And they'd be completely free to take and modify previously open-source code to do it.
Without any copyright protection, OSS would be dead in fairly short order.
455fe10422ca29c4933f95052b792ab2
Read http://news.com.com/SCO+seals+deal+for+legal+expen se+cap/2100-7344_3-5440361.html
The lawyers clearly have a vested interest in dragging this case out and, being a good family man, why should Darl complain?
Engineering is the art of compromise.
Reading the filings you can see why some lawyers cost so much. At the same IBM's lawyers building an almost invincible legal position on every one of their claims, they take huge swipes at SCO's claims. They point out flaws in SCO's arguments and point out when SCO has failed to address an important point. No detail is forgotten even the little detail of SCO's use of cross referencing to hide their lack of evidence. Unfortunately for SCO's lawyers, they didn't have much in the way of evidence and are reduced to lawyer's tricks.
Groklaw is hosed right now but there was one moment in the March 7th transcript that is indicative of the case. SCO's Brent Hatch is referring to an IBM document. IBM's lawyer, Amy Sorenson, reminds the court that the document is marked confidential and trying to work out an agreeable way of handling it whether it meant clearing the court room. SCO responds that IBM could waive the confidentiality. The court interjects noting that IBM wouldn't have mentioned the confidentiality if they wanted to waive it. While the judge and Ms. Sorenson continue to discuss how to best proceed in terms of procedure, SCO's Hatch begins to argue that nothing in the document (in his opinion) should be marked confidential. Ms. Sorenson responds with a "that's your opinion" and says as long as the document isn't directly quoted, IBM is satisfied with SCO referencing it in open court. IBM and the court are working on a case. SCO is offering red herrings.Well, there's spam egg sausage and spam, that's not got much spam in it.
the creator of the graph could have done a better job, in the top portion which is a tangled mess, if my count is correct, there are 56 edges (counting the loops between 233 and 222, 27 and 187 and as one) and 43 vertices, Eulers corollary states that if |E| = 3|V| - 6, that is 56 = 143 (even if my count was off a bit this is clearly true) then that can be drawn on the same plane (no intersecting lines)... I didnt take the time to find a good way to redraw it, but I have proven it could be done... This depiction makes it look overly complicated (not that it isnt complicated enough)
The BSD license allows for what you describe, it's "truly free", in a sense, to my knowledge. It still exists, so OSS would not be dead. Now, would it be more or less dead? I'm not sure, but I think people would have been upset all the same, so would they have formed groups that upheld the "lets keep everything free and open" attitude, or would they have found some other solution? Using the law to enforce an anti-monopolistic idea seems to be a good thing, though. In the real world, Capitalism seems to require anti-monopoly laws to keep things in check, otherwise it seems to me it is a failed system. Software is much harder to destroy/control/monopolize though, so it would do much better than material businesses in a completely open economy. It's really hard to think about what life would be like in such an open system, and where we'd be at in terms of technology and software. Perhaps people would have found some interesting ways to fight back under such a system in order to keep things more open and competitive and pro-consumer.
Promote true freedom - support standards and interoperability.
BSD aren't currently faced with supporting completely undocumented and intentionally obfuscated (TPM-style) hardware.
In a copyright-free world, it could fall either way. MSFT might become insignificant and the rest of the world become more open. Or MSFT might survive by leveraging TPM as an alternative to copyright, with the help of hardware manufacturers who would rather sell to Microsoft's 90% market than OSS's 10%, and conveniently kill off the OSS community. BSD too.
We don't need to wait for a copyright-free world anyhow; Microsoft's big push towards Protected Media Path and TPM has little to do with protecting the MAFIAA companies, and much more to do with pushing hardware manufacturers to choose between Microsoft and FOSS by making it much harder to support both.
455fe10422ca29c4933f95052b792ab2
In internal documents, SCO developers acknowledged that "
SECTION REDACTED
The mere fact that some or all of the 2.4 kernel may have predated SCO Linux 4.0 does not mean that
SECTION REDACTED
If the term
SECTION REDACTED
then sections of the JDC assignment provisions would be rendered superfluous. As stated, the JDC
SECTION REDACTED
If SCO were correct that
SECTION REDACTED
would be rendered superfluous because SCO's reading of the
SECTION REDACTED
would necessarily exclude such materials from assignment.
Wow, why was this document chopped to bits? Anybody know?
The truth shall set you free!
Reading the filings you can see why some lawyers cost so much. At the same IBM's lawyers building an almost invincible legal position on every one of their claims, they take huge swipes at SCO's claims. They point out flaws in SCO's arguments and point out when SCO has failed to address an important point. No detail is forgotten even the little detail of SCO's use of cross referencing to hide their lack of evidence.
IBM is represented by Cravath, Swayne, and Moore, and that's how Cravath works. They have a very organized staff checking everything the other side puts out. Everything goes into a litigation support system (Cravath was the first law firm to use one, and it was developed by IBM for a famous IBM case). At least two different lawyers check over everything. One of Cravath's slogans used to be "For those must-win cases". Cravath often wins simply because the other side makes mistakes, and they don't.
All this is incredibly expensive, but it works.
Obviously Linux in total is a superset of IBM's contribution to Linux. IBM probably doesn't have standing in the court to ask for a declaration covering the whole of Linux, and if they attempt to do so, that is likely to cause the entire motion to fail.
If, however, IBM wins this Partial Summary Judgement motion, as they may well do, then this is still an extremely important result for linux. Unlike the poster who recommended reading the oral arguments, I recommend skipping the oral arguments and go instead for IBM's written motions and briefs. They are very well written and logical.
IBM constructs their motions as a form of logical-or. If the Judge accepts $REASON1 or $REASON2 or $REASON3 then the judge must rule in IBM's favour. So IBM offers multiple concurrent chains of logic supporting their case. The judge needs only to accept one of them, in order to rule for IBM. But each $REASON is fully detailed - supported by facts, evidence, legal argument, case history precedents.
SCO's filings on the other hand, are like a shell game. It's hard to pin them down to facts. They pretend to be Caldera and Santa Cruz and even AT&T when it suits them; at other times they treat them as different entities. Their answers frequently say "please refer to some other answer", and (as this latest IBM filing says), SCO's replies don't really answer the question or dispute the fact, they raise some other issue or introduce non-relevant assertions.
All in all, it's most entertaining.
'' I'm not a lawyer and have difficulty understanding Legalese, but doesn't this sort of orchestrated fictionalization and avoidance of answering questions qualify as some kind of contempt of court? It struck me that SCO's attorneys had no respect whatever for the judge or the process. Redacted to its essence, I could hear a snotty voice intoning, "NYAH-nyah-NYAH-nyah-nyah!" Or does the judge have to put up with this kind of bratty behavior? ''
I think the judge doesn't care at all. He just looks through the papers, sees what in there is evidence (nothing), what in there refutes what IBM is saying (nothing), and ignores anything else. It's his job, and he is used to that. It's like if you gave me twenty lines of code that don't do what they are supposed to do, plus hundred pages of text claiming that your code actually works - those hundred pages won't confuse me, because I just look at the twenty lines and see they don't work. When you or I as a non-lawyer read SCOs nonsense, we are just confused. The judge isn't. He checks: Is it evidence? Does it refute IBM's claims? if it doesn't, it can be ignored.