Analysis of SCO vs. IBM

icantblvitsnotbutter writes "An excellent -- and clear! -- article over at LinuxWorld.com has a multipoint analysis of SCO's 40-page complaint (this is a brief?!). For all those IANAL's out there, here's something to sink your teeth into. On the balance, the outlook seems positive for IBM. Still, the parallel invocation of a contractural clause potentially nixing AIX lends some credence to claims that this is a just way for SCO to coerce IBM into buying them out..." Some old documents from a similar lawsuit have surfaced, and naturally ESR has his own take on the case.

Comments

Re:Almost nothing new here

[PerryMason]

What I would have really liked is something on the lines of "Here is patent number 1" and here is how linux is different/same.....It is not as if SCO patent reads like "WE patent UNIX and everything that looks like it. And that is that

Quoting from the SCO complaint;
18. SCO is the present owner of all software code and licensing rights to System V Technology.

Pretty much summarises what they are saying.

Re:In ESR's take...

[BacOs]

Amicus Curiae

Definition: Latin term meaning "friend of the court". The name for a brief filed with the court by someone who is not a party to the case

Slashdot interview...

[gmuslera]

I don't remember it this was posted already in previous discussions, but in this interview with IBM Kernel Hackers from last year, some points are raised, some good and some bad for IBM, specially in the 2nd question. In short, the people at IBM that was into the linux kernel development can't take parts of i.e. AIX code and put into Linux and viceversa, but some interchange of ideas could have been happened if a developer of one team talks with one of another.

Re:Slashdot interview...

[binaryDigit]

some points are raised, some good and some bad for IBM, specially in the 2nd question

They answered:

We are definitely not allowed to cut and paste proprietary code into any open source projects (or vice versa!). There is an IBM committee who can and do approve the release of IBM proprietary or patented technology, like RCU.

I don't see how this is "bad" for IBM. It shows that they are actively protecting any proprietary interests to the point that they actually have a committee.

but some interchange of ideas could have been happened if a developer of one team talks with one of another.

Again they replied:

Having solved the problem once, our non-Linux peers can help steer us without spelling it out for us, allowing us to still develop solutions that can then be open sourced.

Again, IBM seems to be keenly aware of the cross pollenation issue and actively taking steps to avoid any issues. It reads to me like it's all pro IBM?

Re:Slashdot interview...

[Vlad_the_Inhaler]

That was in the ESR rebuttal, something that seemed to me - IANAL - to be far more informative than that somewhat vague LinuxWorld article.
If ESR has done his homework, and it certainly looks like it, then over 90% of that document of his looks as though it could be used to murder that lawsuit in very short order.

definition of Amicus Curiae

[sczimme]

Black's Legal Dictionary defines amicus curiae: "A person with a strong interest in or views on the subject matter of an action may petition the court for permission to file a brief ostensibly on behalf of a party, but actually to suggest a rationale consistent with its own views. Such amicus curiae briefs are commonly filed in appeals concerning matters of broad public interest; e.g. civil rights cases".

I found this item here.

Re:Random Programming

[Anonymous Coward]

It is also interesting that SCO actually appears to believe that. Even without the headers the API to any library can be reverse engineered with nm and gdb in about two days.

As for "Shared libraries are by their nature unique creations..." I'm not even sure where to start. How is some code a "unique creation" simply because I have compiled it as a shared library? If I build it as a static library, is it no longer unique? Do SCO not understand that one of the points of using shared libraries is that they are inherently interchangable? That one just makes my head spin.

Finally, I also seem to remember Linus owning a Quad Xeon box, back in the mid-90's. So whats this about the Linux developers only having uniprocessor boxes?

SCO SMP licensed from Corollary; 2 more i386 UNIX

[Anonymous Coward]

One trivia point: SCO's SMP implementation was not written by SCO but was licensed from Corollary.

Two more i386 ports that ESR has forgotten about: Altos (later purchased by Acer). I was one of the engineers that ported SCO 3.2.0 (or was it 3.2.2?) to the Altos 1000 (see Google groups for info). The second is the "Sun 386i" 80386 computer which everybody seems to have forgotten about. Again, see Google groups.

IMHO the only thing of value SCO was to contribute to Monterey was the X server.

I believe that from a legal standpoint AIX is licensed SVR3 code (although having seen AIX kernel code, SCO OpenServer and UnixWare source, and "pure" virgin SVR3 code I can attest that AIX is a complete overhaul and bears no resemblence to pure SVR3 (or SVR4) except in the bowels of STREAMS).

full disclosure: ex-SCO employee who worked on all kernels including Monterey prior to Caldera.

Re:The article is flawed.

[0xB00F]

As an example, the author takes issue with the SCO's claim that IBM must have stolen SCO trade secrets in order to improve Linux by saying "OK, then, diff the code."

Perhaps. But if I were you, do what I did: download the kernel changelogs for 2.4 (and if you like 2.2) and grep them for ibm.com (i.e. commits from someone at IBM).

For example, I fetch the changelogs from here. And then I ran:

$ grep -il "ibm\\.com" *

in the directory containing the changelogs to get the filenames with commits from an IBM email address. Use a pager with regexp search capability (like 'less') to view the files, in this case the changelogs for 2.4.19 and 2.4.20.

What?!? You're not running linux?!? Shame on you!

As you will see, most of the checkins involve bug fixes for IBM's JFS, some patches for IPV6, and few ones for s390. Gotta love version control, eh?

Suppose part of the validation test set for Monterey consisted of a stress test written by SCO and owned by SCO.

Project Monterey was a plan that never happened. It was a plan to put Unix on IA-64 machines that died during conception. What we have is a lot of white papers on the subject but no written, working code. Of course I could be wrong, and if there was working code it would have probably been written by IBM developers anyway with a "Copyright (c) 2000 IBM Corp." near the top of the sources.

Let us further suppose that code was used in the Linux development work, and found a key set of bugs. (Don't tell me it isn't possible that it would have been -- developers tend to think of tools as just tools, and forget that they may be encumbered.)

Probably, but one of the accusations SCO makes is that IBM allegedly handed out Unix code owned by SCO to Linux kernel hackers. And that Linux would not have advanced if IBM had not handed out said code. But so far, all code commits from IBM appear to be mostly patches to existing code. What's more SCO accuses IBM of handing out code from SCO Unix to improve Linux's SMP capabilities. However, Linux's SMP support was one of the primary reasons why IBM adopted Linux in the first place (for proof, see my earlier post in this thread). Ergo, by adopting an Open, Freely Available variant of Unix with SMP support would lessen their development efforts.

What I find rather interesting is Caldera's Logo on the IA-64 Linux page. And it lists them as one of the players in this project. And even more interesting is the missing links on SCO's website pointing to details of the Itanium Netfarm they have presumably made available to IA-64 Linux developers.

- casts polymorph other spell on grue... 0xB00F!

UnixWare to Linux Porting Guide

[PiotrK]

Please help others moving from SCO to Linux and post links to documentation like this:

UnixWare to Linux Porting Guide (development tools and the API)
http://people.redhat.com/drepper/
http://people.redhat.com/drepper/sco-porting.pdf

SCO mentions MONTEREY explicitly!!!

[Anonymous Coward]

I would agree with you if SCO had even mentioned their recent work with IBM, but they didn't (probably because the IBM lawyers wrote a contract that is unassailable). The entire case stems around the original UNIX source code that SCO acquired from Novell. As such it is a ridiculously specious case. Don't believe me, go read SCO's filing.

From THE COMPLAINT ITSELF:

Project Monterey

50. As SCO was poised and ready to expand its market and market share for UnixWare targeted to high-performance enterprise customers, IBM approached SCO to jointly develop a new 64-bit UNIX-based operating system for Intel-based processing platforms. This joint development effort was widely known as Project Monterey.

51. Prior to this time, IBM had not developed any expertise to run UNIX on an Intel chip and instead was confined to its Power PC chip.

52. In furtherance of Project Monterey, SCO expended substantial amounts of money and dedicated a significant portion of SCO's development team to completion of the project.

53. Specifically, plaintiff and plaintiff's predecessor provided IBM engineers with valuable information and trade secrets with respect to architecture, schematics, and design of UnixWare and the UNIX Software Code for Intel-based processors.

54. By about May 2001, all technical aspects of Project Monterey had been substantially completed. The only remaining tasks of Project Monterey involved marketing and branding tasks to be performed substantially by IBM.

55. On or about May 2001, IBM notified plaintiff that it refused to proceed with Project Monterey, and that IBM considered Project Monterey to be "dead." In fact, in violation of its obligations to SCO, IBM chose to use and appropriate for its own business the proprietary information obtained from SCO.

ESR goes for the jugular:

[talks_to_birds]

"...If Darl McBride and complainants did not know at the time of the complaint that their own company had played a lead role in the very development they accuse IBM of having unfairly and unlawfully pursued, they are incompetent. If they did know, their complaint appears to verge closely upon perjury..."

You go, ESR...

t_t_b