SCO adamant discovery process backs Linux claims

Files produced by IBM back up SCO's claims Big Blue "improperly contributed code to Linux," the Unix seller said in a memorandum to a US court last week.

In a strongly worded discovery submission to the US District Court in Utah, SCO said the files provided by Big Blue to date, though "only partial responses to SCO's requests for information and materials," revealed the Dynix/ptx enterprise-class operating system "contains material and significant Unix system V code".

SCO claims AIX and Dynix, "considered as whole programs," are derivative works of Unix System V.

SCO said that while it only had the partial responses to work with, the fact Dynix code "contains some historical commentary" meant it could trace some sources of contributions to the code.

"AIX almost certainly has a similar history, but because AIX's code does not contain any historical comments, or at least the AIX code provided did not, SCO has had difficulty determining all the portions of AIX that were taken from Unix System V," the SCO filing said.

SCO said IBM had to date only produced selected pieces of AIX and Dynix, while consistently refusing to produce all requested versions of AIX or Dynix or revision control systems for either program.

The filing is the latest move in the legal brawl between Utah-based SCO and Big Blue over the controversial Unix seller's claims the tech heavyweight breached SCO's intellectual property rights by copying some of the source code from Unix into Linux.

Operating without the items it was seeking through the discovery process, SCO said it had spent "countless hours -- and sometimes fruitless effort -- trying to track the improper use of Unix System V code in Linux through AIX and Dynix".

SCO said it had been forced to rely on alternative methods to try to establish proof, including: identification of all publicly available code patches contributed by IBM/Sequent engineers to Linux, to the extent identified on IBM's Web site and in Linux forums; tracing of code in available code patches to versions of AIX and Dynix; and identification of IBM's public statements regarding its roadmap for building Linux and its technology contributions to Linux.

The company said: "To trace the foundations of AIX source code and to have a complete understanding of Dynix' source code origins, SCO must have

  • access to all interim and final versions of AIX, Dynix and ptx;
  • access to programmer notes and design documents that reveal the work behind the revisions to the programs;
  • and most importantly, access to all revision control systems that track changes to AIX and Dynix, thus exposing the sources of IBM's current AIX and Dynix code and revealing what portions of Unix System V made their way from AIX and Dynix into Unix.

IBM last month filed a motion for summary judgment in the case, claiming SCO had produced no evidence to back up its copyright claims and was unlikely to do so. Big Blue said the claims should be dropped.

"Despite the fact that SCO has been claiming for months that IBM's Linux activities infringe SCO copyrights," the filing reads, "SCO still fails to adduce the basic evidence necessary to support its copyright assertions".

However, SCO hit back in its filing, dated 28 May, stating: "IBM is apparently taking the position that in order for SCO to succeed in its contract claims, SCO must prove copyright infringement.

"This position -- if taken as a description of the sole basis for IBM's liability for breach -- confuses contract with copyright and thereby essentially eliminates the protections of the contract for SCO.

"Nevertheless, SCO recognises that the rules of discovery obligate it to respond, to the best of its ability, to IBM's discovery requests.

"And in any event, SCO, like any plaintiff, is entitled to proceed under alternate theories of liability and to obtain the discovery needed to allow it to do so".

The filing added that [SCO had] "attempted to follow IBM's scattered path through the winding history of countless alterations, derivations and revisions, but the task is nearly impossible without a map, a map so easily accessible to IBM, so clearly relevant to this case and so absolutely essential to SCO that IBM's withholding of it and subsequent filing of a summary judgement motion is unconscionable".

Advertisement

Talkback 5 comments

    A load of bullshit from SCO... ...Anonymous -- 03/06/04

    A load of bullshit from SCO.....

    They have actually said in their legal filings that IBM did not infinge their copyrights, and only that IBM misused their AIX code after a supposed "termination". Here is the quote:

    "With SCO's Second Amended Complaint being the final amendment and not containing a claim for infringement arising out of IBM's Linux Activities, the need for IBM's Tenth Counterclaim seeking such a declaratory judgment is nil."

    SCO are a bunch of liars. When the first started this case A YEAR AGO they claimed to have proof of "one million" lines of Linux code infringing. Yet in their legal filings they admit that is a lie.

    This is news? IBM and Sequent ...Anonymous -- 03/06/04

    This is news? IBM and Sequent had licenses to use System V Code. Wouldn't SCO expect to see System V code in AIX and Dynix? I thought that was why they negotiated licenses from AT&T.

    It was my understanding that a licensee takes a license because he wants to use the code that belongs to another.

    "SCO said it had been for ...Anonymous -- 04/06/04

    "SCO said it had been forced to rely on alternative methods to try to establish proof"

    Cute, because according to this (among many others found in groklaw.net 's quote database):

    "What we found was that the infringements went way beyond just IBM's involvement and that other parties had contributed things improperly... in going through the process, we counted over a million lines of code that we allege are infringed in the Linux kernel today out of a total code base of five million" - McBride, 09/11/2003

    They supposedly had all the proof they needed prior to having to beg for *even more* code from IBM.

    Their discovery helped prove nothing and there's nothing there that "backs [TSG's] Linux claims". The only thing they "found" was that AIX/Dynix has its foundations (or parts of it) in SysV, which no one (to the best of my knowledge, please correct me if I'm wrong) disputes. Their "Linux claims" is that SysV code, the stuff they believe they own, is in Linux. This discovery has not, and further discovery will not further or support their claims. Why? Because there is no SysV code in Linux. Everything they've done is nothing but fishing and delay tactics.

    Let us be very clear about thi ...Anonymous -- 04/06/04

    Let us be very clear about this: IBM has already supplied SCO with the official releases of AIX and Dynix; this supplemental is asking for their entire source code repository *in addition to* the releases they already have.

    According to SCO, there is an infringing path of code that goes like this:

    SysV -> AIX -> Linux

    Since before the case even began, SCO have been in posession of entire source trees of both SysV and Linux going back to genesis. It is questionable as to whether they even need the AIX code to demonstrate copyright violation, should one exist. But now they have the official releases of both AIX and Dynix/ptx as well, and they say that *still* isn't sufficient. Many readers would be thinking about fishing expeditions at this point.

    Since AT&T (from whom IBM originally licensed Unix) have specifically stated (long before SCO came along) that any code the licensor develops to add to Unix themselves is their own to do with how they please, this means that any new code IBM wrote is unencumbered by the license.

    According to recent court documents, virtually all of the code that SCO has identified in Linux as allegedly infringing is code that IBM has _added_ to AIX or Dynix/ptx. (Or from OS/2 in the case of JFS2).

    SCO are clearly trying to redefine the well-established definitions of concepts such as "derivative works" with respect to copyright law. They speak of "non-literal copying", "sequences and structure", and "methods and techniques". This goes way beyond copyright law as protecting "the expression of an idea", ie. the "words and sentences" of the code.

    ...and the motivations of SCO ...Anonymous -- 04/06/04

    ...and the motivations of SCO are summed up nicely in the <a href=http://www.opensource.org/halloween/halloween10.html>Halloween files</a>...

Add your opinion

Latest Videos

Sponsored content

Power Centre - Content from our premier sponsors

Blogs

  • Suzanne Tindal Sick of broken tender sites
    Some of the state governments desperately need to invest in more user-friendly tender sites so that looking for information on government tenders doesn't have to be a game of blind man's bluff.
  • Array Cyberwar: What is it good for?
    In this week's episode, Cyberwar. What is Australia's place in the world of digital warfare? What are the implications for the NBN?
  • Array Is wholesale-only backhaul just a pipedream?
    The potential acquisition of Pipe Networks by SP Telemedia has raised the question about whether vertically integrated backhaul providers will mean higher wholesale prices for ISP customers.
  • More blogs »

Tags

Back to top

Featured