IBM Puts Pressure On SCO

inode_buddha writes "An article at Groklaw shows IBM's legal team dissecting the whole SCO thing professionally and thoroughly. I'm almost willing to bet the case gets dropped with extreme prejudice, especially now that Novell is getting involved. Is anyone taking bets as to when the case actually closes and how?" I suggest the MIT Technology Review add this one to their markets.

Comments

Re:Fraud

[MatthewB79]

It's been said by SEC representatives already (as posted in other forums and here on /.) that SCO and Darl do not represent enough "pump-n-dump" to affect the current market. In other words, he's not even on thier radar.

Re:Good or bad?

[DaEMoN128]

Actually, the SCO case can be dismissed and not affect the IBM countersuit. The GPL issue isn't brought up in the SCO case; it is part of the IBM case. The GPL will still be tested even if Judge Kimball tells SCO to quit smoking crack and continue with discovery for the suit that IBM brought against them.

It gets better!

[Larsing]

SCO has filed a motion to compel discovery against IBM and IBM has responded...

Timeline

[Kalak]

It appears that "IBM's motion to compel is scheduled for oral arguments on Dec. 5." (stolen from Groklaw). Hopefully after that, things will tank and we can get back to normal.

GPL in court

[Ender Ryan]

Actually, the GPL has already "stood up" in court, see MySQL vs. Nusphere.

http://www.linuxworld.com/story/34553.htm

Specifically, In the process, a federal judge deemed the GPL enforceable and binding.

Re:but there are thousands of lines of copied code

[michael_cain]

SCO pulled up some 519 files which have around 300,000 lines of code, which might or might not contain tainted code. That is something like 1 percent of Linux kernel code. Rewriting the whole thing might take a month or two at the maximum, assuming cleanroom specs can be developed out of it.

First point -- on the assumption that the case will continue, which I believe, it may be some time before anyone knows which lines are "tainted". For example, SCO points at the source files for JFS and says "These may be tainted." IBM says, "Which lines?" SCO responds with, "Any lines which you developed under AIX. Which are those?" SCO's legal theory seems to be that any features of AIX which were transfered to Linux are a violation, unless IBM can prove that the code given to Linux was developed as part of a non-AIX operating system, then ported to Linux directly from that non-AIX system. IBM is using the obvious tactic of providing a mountain of raw information, then demanding that SCO sift through it and identify the lines that are in question -- make it too EXPENSIVE for SCO to continue the case.

Second point -- on the assumption that SCO wins, which I don't believe will happen, generating cleanroom specs may well be a problem. As I understand it, the contract forbids revealing the methods as well as the source code. IBM would be in the position of having to say to the Linux community, "The code and documentation that we revealed to you, and on which your specs are based, were trade secrets that we did not have the right to reveal." ANY use of that information -- such as writing specs -- could be deemed improper by a court. However, if SCO wins and gets a large settlement from IBM, I would expect the judge to rule that SCO has now been compensated for the loss of their trade secrets, and that the Linux community is free to make use of those "secrets".

SCO appears to have (although IANAL) a simple case that is at least arguable. I have to believe that all of the public posturing, much if not all of which is irrelevant, is intended to run the share price up so that the executives can cash out.