decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
IBM'S FIRST SET OF INTERROGATORIES AND FIRST REQUEST FOR THE PRODUCTION OF DOCUMENTS
Sunday, January 04 2004 @ 12:56 AM EST

Thanks once again to Henrik Grouleff, we now have as text IBM'S First Set of Interrogatories and First Request for the Production of Documents, which was attached as Exhibit D to IBM's Memorandum in Support of its [First] Motion to Compel Discovery. The original Exhibit D is here.

I found the requests for documents very interesting indeed. These are particularly intriguing, when you consider that in discovery you ask for things that you believe exist and believe are related in some way to your case:

REQUEST NO. 58:

All documents concerning the unfair competition lawsuit brought by plaintiff against Microsoft Corporation.

REQUEST NO. 59:

All documents concerning the destruction of documents relating to the unfair competition lawsuit brought by plaintiff against Microsoft Corporation. . . .

REQUEST NO. 62:

A copy of all source code and object code relating to all releases of any product ever manufactured, marketed, sold, or distributed by plaintiff, including but not limited to: (a) UnixWare; (b) SCO OpenServer; (c) ReliantHA; (d) NeTraverse Merge; (e) each of the "Optional Services" for the UnixWare product ever described on plaintiff's website; (f) SCO XENIX; and (g) Skunkware.

REQUEST NO. 63:

All documents concerning any of plaintiff's Beta Projects, including but not limited to copies of source code and object code for every software product ever tested or currently being tested by plaintiff in its Closed Beta or Open Beta projects.

Why Xenix? Is it just one on a list, or is there some significance to this request? And what do they think they will find in beta projects? Because you are not supposed to go on fishing expeditions, this list makes me begin to seriously think about why they are asking for these things, particularly for materials from the lawsuit against Microsoft and pointedly for all documents regarding the shredding of the documents in that lawsuit.

They are asking for all documents, presumably email, letters, notes, memos, anything related to that decision to shred. Some of these court documents Sun was able to obtain for use in its case against Microsoft, but only a small portion. The case settled in 2000. This shredding happened in May:

Three million pages of Microsoft documents, once part of a suit against the software maker, are being shredded and are destined to become toilet paper.

The 937 boxes of court-ordered documents had been safeguarded by Redman Records of Salt Lake City since the mid-1990s as part of Caldera International's unfair-competition lawsuit against Microsoft.

That suit was settled in January 2000, and Caldera -- now The SCO Group -- was paying up to $1,500 a month to store the documents. In October, the company persuaded U.S. District Judge Dee Benson to order their destruction.

However, just as the shredding was to begin, Sun Microsystem's attorneys halted it with a subpoena. The company, seeking evidence that might help in its own antitrust suit against Microsoft, eventually pulled out 40 boxes of the computer giant's secret internal communications for digital imaging.

So as you go down the list of documents requested and the interrogatories, the way to read it is to ask yourself, what is IBM thinking? What hints can we get from this list? Why might they be asking for this piece of evidence? For example, what does this mean? Is it talking just about the USL-BSDi case?

REQUEST NO. 16:

All documents concerning any lawsuit relating to the Disputed Material.

REQUEST NO. 17:

All documents concerning any agreement between plaintiff and any other person regarding actual or prospective litigation relating to the Disputed Material.

I'm thinking we could probably give them more documentation on the BSDi case than SCO. Joke. But I do smile when I think of SCO trying to answer Interrogatories 2-4 and trying to find the documents for document requests 11, 12 and 14, 15, and 16, all related to trade secrets and how well SCO and its predecessors in interest through the years maintained the secrets of Unix. Then I can't help but wonder, what exactly was the Microsoft case about? And what led to the decision to shred those documents? And what about request 22? Is it possible that Project Monterey was entered into without any contract? Or is IBM highlighting again that any contract they may have had was between IBM and the now-Tarantella? I guess you can tell I am finding this document fascinating, trying to figure out IBM's strategy. Of course, the one that interests us the most is 31, the allegedly infringing code in Linux. But I'd like to see what they produce in response to Request No. 47 too, because I want to know if they really had MIT mathematicians and spectral analysis and all that or if that was just so much fluff.

Don't skip the definitions in the Exhibit. That's where experienced attorneys try to win a few points.

Now, this document is archived as text, and lawyers and law students and paralegals can look at it and learn how to do discovery. I do believe you could teach a class just from this case, using IBM's documents.

There still exists a Caldera Statement of Facts from their case against Microsoft online. I wonder if there may be more documents hidden away here or there. I reported both the shredding of the documents and provided a link to the Statement of Facts back in May and early June, but most of you weren't reading Groklaw back then, so here you go again. There are more of us now, so perhaps you will find things I may have missed in my earlier research.

IBM misses absolutely nothing.

UPDATE:

Nicholas sends us this link to the court papers in the Caldera lawsuit against Microsoft. There are also some news stories about the case, so we can dig in. Thanks!

****************************************************************

Alan L. Sullivan (3152)
Todd M. Shaughnessy (6651)
SNELL & WILMER L.L.P.
[address, phone, fax]

CRAVATH, SWAINE & MOORE
Evan R. Chesler (admitted pro hac vice)
Thomas G. Rafferty (admitted pro hac vice)
David R. Marriott (pending admission)
[address, phone]

Attorneys for Defendant International Business
Machines Corporation

IN THE UNITED STATES DISTRICT COURT
FOR THE DISTRICT OF UTAH

CALDERA SYSTEMS, INC, d/b/a
THE SCO GROUP,

Plaintiff,

vs.

INTERNATIONAL BUSINESS
MACHINES CORPORATION

Defendants.

DEFENDANT IBM'S FIRST SET OF
INTERROGATORIES AND FIRST
REQUEST FOR THE PRODUCTION OF
DOCUMENTS

Civil No. 2:03cv0294

Honorable Dale A. Kimball

Pursuant to Rules 33 and 34 of the Federal Rules of Civil Procedure, defendant International Business Machines Corporation ("IBM") submits this First Set of Interrogatories and First Request for the Production of Documents to plaintiff Caldera Systems, Inc., d/b/a The SCO Group ("plaintiff")

Plaintiff is directed to give answers to the written interrogatories separately, fully, in writing, under oath, and in accordance with the following definitions and instructions. Plaintiff is requested to produce the documents and things in its possession, custody or control pursuant to the document requests.

Answers to the interrogatories, and all documents and things responsive to the document requests must be served on the undersigned attorneys for IBM at the offices of Cravath, Swaine & Moore LLP, 825 Eighth Avenue, New York, NY 10019 within 30 days of service of these interrogatories and document requests.

Interrogatories

INTERROGATORY NO. 1:

Please identify, with specificity (by product, file and line of code, where appropriate) all of the alleged trade secrets and any confidential or proprietary information that plaintiff alleges or contends IBM misappropriated or misused, including but not limited to as alleged in ¶ 105 of the Complaint.

INTERROGATORY NO. 2:

For each alleged trade secret or any confidential or proprietary information identified in response to Interrogatory No.1, please identify: (a) all persons who have or have had rights to the alleged trade secret or confidential or proprietary information; (b) the nature and source of the rights; and (c) all efforts by any person to maintain the secrecy or confidentiality of the alleged trade secrets and any confidential or proprietary information.

INTERROGATORY NO. 3:

For each alleged trade secret and any confidential or proprietary information identified in response to Interrogatory No, 1, please identify all persons to whom the alleged trade secret or confidential or proprietary information is known or has been disclosed and describe, in detail, the circumstances under which it became known or was disclosed, including but not limited to: (a) the date on which the alleged trade secret or confidential or proprietary, information was disclosed or became known to such persons; (b) the specific terms on which the information was disclosed or became known, such as pursuant to a confidentiality agreement; (c) all documents or agreements relating to the disclosure; and (d) all places or locations where the alleged trade secret or confidential or proprietary information may be found or accessed.

INTERROGATORY NO. 4:

For each alleged trade secret and any confidential or proprietary information identified in response to Interrogatory No.1, please describe, in detail, each instance in which plaintiff alleges or contends that IBM misappropriated or misused the alleged trade secret or confidential or proprietary information, including but not limited to: (a) the date of the alleged misuse or misappropriation; (b) all persons involved in any way in the alleged misuse or misappropriation; (c) the specific manner in which IBM is alleged to have engaged in misuse or misappropriation; and (d) with respect to any code or method plaintiff alleges or contends that IBM misappropriated or misused, the location of each portion of such code or method in any product, such as AIX, in Linux, in open source, or in the public domain.

INTERROGATORY NO. 5:

For each alleged trade secret and any confidential or proprietary information identified in response to Interrogatory No.1, please identify: (a) all agreements relating to the alleged trade secret or confidential or proprietary information including but not limited to the parties to and the terms of the agreements; and (b) all copyrights and patents relating to the alleged trade secret or confidential or proprietary information including but not limited to the owners, licensors, licensees, assignors or assignees of those copyrights or patents.

INTERROGATORY NO. 6:

For each line of source or object code and each method identified in response to Interrogatory No.1, please identify; (a) the origin of the code or method, including when, where and by whom the code or method was created; and (b) all products in which, in whole or in part, the code or method is included or on which, in whole or in part, the code or method is based.

INTERROGATORY NO. 7:

Please describe, in detail, each instance in which plaintiff alleges that IBM engaged in unfair competition, including but not limited to: (a) the dates on which IBM allegedly engaged in any unfair competition; (b) all persons involved in the alleged unfair competition; and (c) the specific manner in which IBM is alleged to have engaged in unfair competition including but not limited to as alleged in ¶ 118 of the Complaint.

INTERROGATORY NO. 8:

Please identify all agreements with which plaintiff alleges IBM interfered and describe, in detail, each instance in which plaintiff alleges or contends that IBM interfered with those agreements, including but not limited to; (a) the date of the alleged interference; (b) all persons involved in the alleged interference; (c) the specific manner in which IBM is alleged to have interfered with the agreement; (d) the specific actions, if any, that IBM induced or encouraged plaintiff's customers or licensees to take; (e) the specific action, if any, that plaintiff's customer or licensee took as a result of the actions allegedly induced or encouraged by IBM; and (f) the specific trade secret or confidential or proprietary information, if any, involved in the alleged interference.

INTERROGATORY NO. 9:

Please identify all agreements that plaintiff alleges or contends that IBM has breached, including the specific provisions or portions of those agreements that plaintiff alleges or contends that IBM breached, and describe, in detail, each instance in which plaintiff alleges or contends that IBM breached those agreements, including but not limited to; (a) the date of the alleged breach; (b) all persons involved in the alleged breach; and (c) the specific manner in which IBM is alleged to have breached the agreement.

INTERROGATORY NO. 10:

Separately, for each of plaintiff's claims for relief, please identify all persons (including but not limited to present or former employees of plaintiff or plaintiff's predecessors in interest) with knowledge relating to plaintiff's claims and contentions and the general nature of, or the categories of, facts known by each person.

INTERROGATORY NO. 11:

Please identify all products ever marketed, sold or distributed by plaintiff or plaintiff's predecessors in interest, including but not limited to the terms on which each was marketed, sold or distributed.


Document Requests

REQUEST NO. 1:

All documents identified in response to IBM's interrogatories to plaintiff.

REQUEST NO. 2:

All documents used or referred to in responding to IBM's interrogatories to plaintiff.

REQUEST NO. 3:

All documents upon which plaintiff intends to rely at any trial or hearing or in connection with any motion in this action.

REQUEST NO. 4:

All documents concerning the creation or development of the Disputed Material.

REQUEST NO. 5:

All documents concerning any change or modification to the Disputed Material.

REQUEST NO. 6:

All documents concerning the ownership of, or property rights in, the Disputed Material.

REQUEST NO. 7:

All documents concerning any agreement relating to the Disputed Material.

REQUEST NO.8:

All documents concerning any efforts to ensure or maintain the secrecy or confidentiality of the Disputed Material.

REQUEST NO.9:

All documents concerning any rule, policy, practice or procedure relating to the confidentiality or secrecy, or lack of confidentiality or secrecy, of the Disputed Material.

REQUEST NO. 10:

All documents concerning any breach of any rule, policy, practice or procedure, relating to the confidentiality or secrecy, or lack of confidentiality or secrecy, of the Disputed Material.

REQUEST NO. 11:

All documents concerning the use by any person other than plaintiff of the Disputed Material.

REQUEST NO. 12:

All documents concerning the disclosure or availability of the Disputed Material to any person other than the plaintiff.

REQUEST NO. 13:

Documents sufficient to identify all licensees, sublicensees or assignees of the Disputed Material.

REQUEST NO. 14:

Documents sufficient to identify all persons to whom the Disputed Material has been disclosed.

REQUEST NO. 15:

All documents concerning any unlicensed or unauthorized use of the Disputed Material.

REQUEST NO. 16:

All documents concerning any lawsuit relating to the Disputed Material.

REQUEST NO. 17:

All documents concerning any agreement between plaintiff and any other person regarding actual or prospective litigation relating to the Disputed Material.

REQUEST NO. 18:

All documents concerning any copyright relating to, or any attempt to copyright, the Disputed Material.

REQUEST NO. 19:

All documents concerning any patent relating to, or any attempt to patent, the Disputed Material.

REQUEST NO. 20:

Documents sufficient to identify all persons who have ever licensed UNIX software products, code or methods.

REQUEST NO. 21:

All documents concerning any contract or licensing agreement with which plaintiff alleges IBM interfered.

REQUEST NO. 22:

All documents concerning any agreement involving IBM and plaintiff.

REQUEST NO. 23:

All documents concerning any agreement referenced in the Complaint including but not limited to the "AT&T UNIX Software Agreements", "AT&T UNIX Sublicensing Agreements", "AT&T UNIX Agreements", "AT&T / IBM UNIX Agreements'', the "Side Letter", "IBM Amendment X", and the "Software Agreement".

REQUEST NO. 24:

All documents concerning the value, if any, of the Disputed Material.

REQUEST NO. 25:

All documents concerning Project Monterey.

REQUEST NO. 26:

All documents provided to IBM by plaintiff or received by plaintiff from IBM.

REQUEST NO. 27:

All documents concerning any alleged disclosure by IBM to any third party or to the public of any Disputed Material.

REQUEST NO. 28:

All documents concerning any Disputed Material allegedly disclosed by IBM to any third party or to the public.

REQUEST NO. 29:

All documents concerning any Disputed Material disclosed by plaintiff to any third party or to the public,

REQUEST NO. 30:

All documents concerning any disclosure by plaintiff to any third party or to the public of any Disputed Material.

REQUEST NO. 31:

All documents concerning any Disputed Material found in Linux, open source, or the public domain.

REQUEST NO. 32:

All documents concerning plaintiff's purchase or acquisition of the Disputed Material.

REQUEST NO. 33:

All documents concerning the Disputed Material, UNIX, or Linux received by plaintiff from AT&T, USL, Novell, or Tarantella.

REQUEST NO. 34:

All documents concerning any agreement involving AT&T, USL, Novell, Tarantella, or plaintiff relating to UNIX or Linux.

REQUEST NO. 35:

All documents concerning the formation of USL and the transfer by AT&T to USL of rights and property relating to UNIX.

REQUEST NO. 36:

All documents concerning the sale by AT&T and USL of USL's capital stock.

REQUEST NO. 37:

All documents concerning the acquisition of USL by Novell.

REQUEST NO. 38:

All documents concerning the sale by Novell to Tarantella of UNIX assets.

REQUEST NO. 39:

All documents concerning the sale of assets by Tarantella to plaintiff including but not limited to Tarantella's Server Software and Professional Services divisions.

REQUEST NO. 40:

All documents concerning any communication relating to this litigation including but not limited to communications with plaintiff's employees, shareholders, directors or officers.

REQUEST NO. 41:

All documents concerning any public statement made by plaintiff concerning this litigation.

REQUEST NO. 42:

All documents concerning plaintiff's decision to commence or pursue this lawsuit or other lawsuits relating to plaintiff's alleged contract or property rights relating to UNIX or Linux.

REQUEST NO. 43:

All documents concerning plaintiff's decision to attempt to terminate any IBM license.

REQUEST NO. 44:

All documents concerning plaintiff's decision to suspend its distribution of Linux products or code.

REQUEST NO. 45:

All documents concerning plaintiff's decision to change its name.

REQUEST NO. 46:

All documents concerning any analysis of any IBM product, code, or public disclosure.

REQUEST NO. 47:

All document concerning any analysis of Linux or of any other open source code.

REQUEST NO. 48:

All documents concerning United Linux.

REQUEST NO. 49:

All documents concerning the General Public License.

REQUEST NO. 50:

All documents concerning any contributions to Linux or to Open source made by AT&T, USL, Novell, Tarantella, or plaintiff.

REQUEST NO. 51:

All documents concerning the resumes or curricula vitae of any person on whom plaintiff intends to rely as a witness, declarant or affiant in this action.

REQUEST NO. 52:

Documents sufficient to show plaintiff's organizational or personnel structure, including but not limited to organization charts, flow charts and personnel directories.

REQUEST NO. 53:

All documents concerning any communication with AT&T, USL, Novell, or Tarantella relating to the Disputed Material or any copyright, patent, or trademark relating to the Disputed Material.

REQUEST NO. 54:

All documents concerning any statement, affidavit, declaration, or opinion relating to the Disputed Material or any patent, copyright, or trademark relating to the Disputed Material.

REQUEST NO. 55:

All documents concerning any statement, affidavit, declaration, or opinion relating to this litigation.

REQUEST NO. 56:

All documents concerning any code or other material disclosed by plaintiff to any person, including but not limited to Laura Didio of the Yankee Group and Bill Claybrook of the Aberdeen Group, relating to plaintiff's allegation that IBM or others have misappropriated, misused or infringed plaintiff's intellectual or other property rights or have otherwise breached an obligation to plaintiff.

REQUEST NO. 57:

All documents concerning any analysis, assessment, opinion, or statement relating to plaintiff's allegation that IBM or others have misappropriated, misused or infringed plaintiff's intellectual or other property rights or have otherwise breached an obligation to plaintiff.

REQUEST NO. 58:

All documents concerning the unfair competition lawsuit brought by plaintiff against Microsoft Corporation.

REQUEST NO. 59:

All documents concerning the destruction of documents relating to the unfair competition lawsuit brought by plaintiff against Microsoft Corporation.

REQUEST NO. 60:

A copy of all source code and object code relating to the Disputed Material.

REQUEST NO. 61:

A copy of all source code and object code relating to all releases of any UNIX or Linux product.

REQUEST NO. 62:

A copy of all source code and object code relating to all releases of any product ever manufactured, marketed, sold, or distributed by plaintiff, including but not limited to: (a) UnixWare; (b) SCO OpenServer; (c) ReliantHA; (d) NeTraverse Merge; (e) each of the "Optional Services" for the UnixWare product ever described on plaintiff's website; (f) SCO XENIX; and (g) Skunkware.

REQUEST NO. 63:

All documents concerning any of plaintiff's Beta Projects, including but not limited to copies of source code and object code for every software product ever tested or currently being tested by plaintiff in its Closed Beta or Open Beta projects.

REQUEST NO. 64:

A copy of all Linux, open source, or public domain source code and object code ever manufactured, marketed, sold, or distributed by plaintiff, including but not limited to all releases and versions of Caldera OpenLinux and SCO Linux.

REQUEST NO. 65:

Documents sufficient to show all persons to whom plaintiff or plaintiff's predecessors in interest have ever marketed, sold or distributed any products.

REQUEST NO. 66:

Documents sufficient to show the dates on which plaintiff or plaintiff's predecessors in interest have ever marketed, sold or distributed their products.

REQUEST NO. 67:

A copy of any IBM source code or object code or product documentation in plaintiff's possession, custody or control.

REQUEST NO. 68:

All documents concerning plaintiff's allegation that IBM misappropriated or misused the Disputed Material including but not limited to as alleged in ¶¶ 104-114 of the Complaint.

REQUEST NO. 69:

All documents concerning plaintiff's allegation that IBM engaged in unfair competition including but not limited to as alleged in ¶¶ 115 - 121 of the Complaint.

REQUEST NO. 70:

All documents concerning plaintiff's allegation that IBM interfered with plaintiff's contracts or prospective contractual relations including but not limited to as alleged in ¶¶ 122-127 of the Complaint.

REQUEST NO. 71:

All documents concerning plaintiff's allegation that IBM breached its contractual obligations including but not limited to as alleged in ¶¶ 128-136 of the Complaint.

REQUEST NO. 72:

All documents concerning plaintiff's alleged termination of IBM's right to use the Disputed Materials, including but not limited to as alleged in ¶ 135 of the Complaint.

REQUEST NO. 73:

All documents concerning the nature, calculation, and basis of any damages and injuries plaintiff claims in this matter.


Instructions and Definitions

Defendant IBM hereby incorporates by reference all instructions, definitions and rules contained in Rule 33 and Rule 34 of the Federal Rules of Civil Procedure and the local rules or individual practices of this Court and supplements them with the following definitions and instructions:

A. Definitions
1. The term "AIX" shall mean the UNIX-branded operating system distributed and/or developed by IBM, including all prior versions, releases and maintenance modifications.
2. The term "AT&T" shall mean and include, collectively and/or individually, AT&T Corporation and all its directors, officers, authorized agents, employees, consultants, attorneys, sales representatives, distributors, dealers, direct and indirect contractors, entities that were acquired by or merged with AT&T, subsidiaries of AT&T, including but not limited to AT&T Technologies, Inc., and/or all other persons acting on behalf of AT&T.
3. The term "communication" shall mean any transmittal of information, whether oral or written, including correspondence, electronic mail and other internet transmissions, web pages, Internet Relay Chat logs, telex, facsimile transmissions, telecopies, recordings in any medium of oral communication, telephone and message logs, notes or memoranda relating to written or oral communications.
4. The term "Complaint" shall mean the Complaint filed in March 2003 by Caldera against IBM in Utah state court and removed to the United States District Court for the District of Utah, Central Division, with the civil docket number 2:03CV-0294, and any amendment thereto.
5. The term "concerning" shall mean relating to, referring to, reflecting, describing, evidencing, referencing, discussing or constituting.
6. The term "describe" shall mean in the case of an event or circumstance, to set forth in detail the date, time, place, individuals or entities involved and context and content of the event or circumstance.
7. The term "Disputed Material" shall mean any software product, know-how, concept, idea, methodology, standard, specification, programming technique, code, architecture, or schematic in which plaintiff is alleged to have rights, including but not limited to the alleged trade secrets or confidential or proprietary information that IBM is alleged to have misappropriated, misused, or improperly disclosed.
8. The term "document" shall be synonymous in meaning and usage to the broadest scope of the term used in Rule 34(a) of the Federal Rules of Civil Procedure. The term "document" shall include without limitation all "Written, phonic, graphic or recorded matter, including without limitation, information stored on computers, disks, tapes (i.e., magnetic or other storage media), World Wide Web pages, electronic mailing lists or automated fax support systems. The term "document" specifically includes electronic mail, electronic correspondence, or electronic peer-to-peer messages ("e-mail") and any attachments and files created and maintained in electronic form in the normal course of business.
9. The term "IBM" shall mean and include, collectively and/or individually, defendant International Business Machines Corporation and all its directors, officers, authorized agents, employees, consultants, attorneys, sales representatives, distributors, dealers, direct and indirect contractors, entities that were acquired by or merged with IBM, subsidiaries of IBM, and/or all other persons acting on behalf of IBM.
10. The term "identify" shall mean:
a. in the case of a natural person, to state the full name, current or last known job title and position, current or last known full address, current or last known home and work telephone numbers, and current or last known electronic mail address, and to indicate the basis of that person's knowledge, including but not limited to the identification of documents and communications and a description of his/her personal involvement in any transaction, meeting, software development, marketing, or other activity relating in any way to the allegations of the Complaint and any counterclaims or defenses;

b. in the case of any entity other than a natural person, to state its name, address, principal place of business and, if applicable, place of incorporation and a contact person at the entity;

c. in the case of a document, to state the author(s), title, subject matter, date, place, source of publication of the document and substance of the document;

d. in the case of an oral communication, to give a complete description of such oral communication, including but not limited to: (i) the speaker(s) and actual or intended recipient(s) or witnesses of the communication, (ii) the date of the communication, and (iii) the substance of the communication;

e. in the case of alleged trade secrets or confidential or proprietary information, whether computer code, methods or otherwise, to give a complete and detailed description of such trade secrets or confidential or proprietary information, including but not limited to an identification of the specific lines and portions of code claimed as trade secrets or confidential or proprietary information, and the location (by module name, file name, sequence number or otherwise) of those lines of code within any larger software product or property.

f. in the case of an alleged right, to give a complete and detailed description of such right, including but not limited to: (i) the issuer of the right; (ii) the date the right became effective; (iii) the date the right expired; and (iv) any limitations placed upon such right.
11. The term "include" or "including" shall mean including without limitation.
12. The term "Novell" shall mean and include, collectively and/or individually, Novell, Inc. and all its directors, officers, authorized agents, employees, consultants, attorneys, sales representatives, distributors, dealers, direct and indirect contractors, entities that were acquired by or merged with Novell, subsidiaries of Novell, and/or all other persons acting on behalf of Novell.
13. The term "object code" shall mean output from a compiler or assembler which is itself executable machine code or is suitable for processing to produce executable machine code.
14. The term "open source" shall mean any software code that is made available in source code form without any confidentiality restrictions, including but not limited to any code made available under the General Public License, the BSD license, or the MIT license.
15. The term "person" refers to natural persons or all private or public entities.
16. The term "plaintiff" shall mean and include, collectively and/or individually, plaintiff Caldera Systems, Inc., Caldera International, Inc., or The SCO Group, Inc., and all its directors, officers, authorized agents, employees, consultants, attorneys, sales representatives, distributors, dealers, direct and indirect contractors, entities that were in part or in whole acquired by or merged with Caldera Systems, Inc., Caldera International, Inc., or The SCO Group, Inc., affiliates, subsidiaries or predecessor companies of Caldera Systems, Inc., Caldera International, Inc., or The SCO Group, Inc., and/or all other persons acting on behalf of Caldera Systems, Inc., Caldera International, Inc., or The SCO Group, Inc. This includes the Server Software and Professional Services divisions acquired in 2001 by Caldera International, Inc. from Tarantella, Inc., f/k/a The Santa Cruz Operation, Inc ("Tarantella").
17. The terms "SCO UNIX" or "SCO OpenServer" shall mean the UNIX-branded operating systems distributed and/or developed by Tarantella or plaintiff for running on Intel processors, including all prior versions, releases and maintenance modifications.
18. The term "source code" shall mean the human-readable form of a computer program written in the original and preferred form for human inspection and modification, and includes but is not limited to source code listings; compiler and/or assembler output listings for such source code; source code listings for macros or "includes" (both executable and mapping) listings used in such source code; job control language files; and/or other files required to create an executable version of a program, including but not limited to user interface components; panels; screen definitions and help text; and c-lists.
19. The term "Tarantella" shall mean and include, collectively and/or individually, Tarantella, Inc. f/k/a The Santa Cruz Operation, Inc. and all its directors, officers, authorized agents, employees, consultants, attorneys, sales representatives, distributors, dealers, direct and indirect contractors, entities that were acquired by or merged with Tarantella, subsidiaries of Tarantella, and/or all other persons acting on behalf of Tarantella.
20. The term "UNIX" shall mean any and all versions, flavors, or other variants of any UNIX computer operating system, including but not limited to all operating systems certified as conforming to the UNIX-brand standards set by The Open Group, the owner of the UNIX trademark.
21. The term "UnixWare" shall mean the UNIX operating system acquired by Tarantella from Novell in 1995.
22. The term "USL" shall mean and include, collectively and/or individually, UNIX Systems Laboratories, Inc. and all its directors, officers, authorized agents, employees, consultants, attorneys, sales representatives, distributors, dealers, direct and indirect contractors, entities that were acquired by or merged with USL, subsidiaries of USL, and/or all other persons acting on behalf of USL.
B. General Instructions
1. Each paragraph should herein be construed independently and, unless otherwise directed, without reference to any other paragraph for the purpose of limitation.

2. The use of any definition for the purposes of this request shall not be deemed to constitute an agreement or acknowledgment on the part of defendant that such definition is accurate, meaningful or appropriate for any other purpose in this action.
C. Additional Instructions for Interrogatories
1. Information requested in these interrogatories shall include information within the knowledge or possession of any of plaintiff's agents, employees, attorneys, investigators or any other persons, firms or entities directly or indirectly subject to plaintiff's control in any way whatsoever.

2. Each interrogatory shall be answered in its entirety. If any interrogatory or subsection thereof cannot be answered in full, it shall be answered to the fullest extent possible with an explanation as to why a complete answer is not provided.

3. If there is a claim of privilege as to any communication concerning information requested by these interrogatories, specify the privilege claimed, the communication and/or answer to which that claim is made, the topic discussed in the communication and the basis upon which the claim is asserted.

4. These interrogatories are continuing in nature and require supplemental or additional responses in accordance with Rule 33 of the Federal Rules of Civil Procedure.

5. Separate and complete responses (or, as the case may be, separate objections) are required for each interrogatory or subpart thereof.
D. Additional Instructions for Document Requests
1. Unless otherwise specified, the documents requested are the responsive documents in the possession, control or custody of the plaintiff that were prepared, written, sent, dated, received, applicable or in effect at any time up to the date of plaintiff's compliance with this demand.

2. Each requested document shall be produced in its entirety. If a document responsive to any request cannot be produced in full, it shall be produced to the extent possible with an explanation stating why production of the remainder is not possible.

3. Each page or sheet produced by plaintiff is to be marked with a consecutive document control number.

4. All documents produced in response to these requests shall be produced in the same order as they are kept or maintained in the ordinary course of business and, where multiple pages or documents are assembled, collated, grouped, or otherwise attached, shall not be separated or disassembled.

5. With respect to any document responsive to this request that is withheld from production based upon a claim of privilege, please provide the information required pursuant to Rule 26(b)(5) of the Federal Rules of Civil Procedure.

6. If, for reasons other than a claim of privilege, you refuse to produce any document requested herein, state the grounds upon which the refusal is based with sufficient specificity to permit a determination of the propriety of such refusal.

7. If there are no documents responsive to any paragraph or subparagraph set forth in the requests, please provide a written response so stating.

8. This request is a continuing one and, pursuant to Rule 26(e) of the Federal Rules of Civil Procedure requires further and supplemental production by the plaintiff as and whenever the plaintiff acquires, makes or locates additional documents between the time of the initial production hereunder and the time of the trial in this action.

DATED this 13th day of June, 2003.

SNELL & WILMER L.L.P.

[signature]
Alan L. Sullivan
Todd M. Shaughnessy

CRAVATH, SWAINE & MOORE LLP
Evan R. Chesler
Thomas G. Rafferty
David R. Marriott

Attorneys for Defendant/Counterclaim-Plaintiff International Business Machines Corporation

Of counsel:

INTERNATIONAL BUSINESS MACHINES CORPORATION
Donald J. Rosenberg
[address,phone]

Attorneys for Defendant International Business Machines Corporation


  


IBM'S FIRST SET OF INTERROGATORIES AND FIRST REQUEST FOR THE PRODUCTION OF DOCUMENTS | 159 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Toilet Paper from lawsuit files
Authored by: Anonymous on Sunday, January 04 2004 @ 03:20 AM EST
The paper is destined to become toilet paper. I guess
this is appropriate seeing the parties involved in the
case (SCO and Microsoft).

:-P

[ Reply to This | # ]

IBM'S FIRST SET OF INTERROGATORIES AND FIRST REQUEST FOR THE PRODUCTION OF DOCUMENTS
Authored by: Maserati on Sunday, January 04 2004 @ 04:39 AM EST
From definition 16, which specifies who IBM considers the plaintiff to be, we
find ", and/or all other persons acting on behalf of Caldera Systems,
Inc."

That could cast a very wide net if the defendants deifinition of plaintiff means
anything.

[ Reply to This | # ]

Mountains of paper
Authored by: Anonymous on Sunday, January 04 2004 @ 04:49 AM EST

I see all these "all documents concerning...", and think of the mounds of paper I irregularly clean off my table as a developer in just minor software projects.

Complying with these kinds of discovery requests must be extremely taxing, both for the unfortunate souls trying to collect the documents, and those receiving, cataloguing, and interpreting them...

[ Reply to This | # ]

IBM'S FIRST SET OF INTERROGATORIES AND FIRST REQUEST FOR THE PRODUCTION OF DOCUMENTS
Authored by: Anonymous on Sunday, January 04 2004 @ 05:39 AM EST
With regard to requests 62 and 63, weren't people moaning about how similar
requests made by SCO were irrelevent or overly burdensome?

[ Reply to This | # ]

Caldera v Microsoft: a choice irony
Authored by: anwaya on Sunday, January 04 2004 @ 07:07 AM EST
Caldera's lawsuit with Microsoft was initially over Microsoft implementing code
in Windows 3.1 to detect whether W31 was running on DR-DOS, which provided
applications with an ABI very similar to MS-DOS, and refuse to run if it was.
The history of these two Operating Systems is well documented elsewhere, and
rather tangled. The irony lies in the fact that the MS-DOS ABI, the programming
interface, was implemented in DR-DOS.

Caldera got DR-DOS through Novell, which bought it from Digital Research. What
kind of license there was between Microsoft and Digital Research, if any, I do
not know: and perhaps, just perhaps, evidence one way or the other has now been
made into toilet paper.

Certainly, the timing of the decision to pulp the records is very suspicious:
the process starts in October 2002, but Sun gets an injunction to halt the
shredding, presumably for the Java lawsuit. In March, SCO sues IBM. In mid May,
Microsoft and Sun announce their intent to buy SCOSource licenses. And at the
end of May, shredding resumes: Sun's injunction must have been lifted.

[ Reply to This | # ]

Definition #20
Authored by: ijramirez on Sunday, January 04 2004 @ 07:34 AM EST
IBM threw a jab at SCO in defintion 20. SCO always describes themselves as the
owners of UNIX and IBM sets the record straight by stating that Unix is a
trademark of The Open Group and by stating that The Open Group certifies
conformance to the Unix-standard.

[ Reply to This | # ]

IBM'S FIRST SET OF INTERROGATORIES AND FIRST REQUEST FOR THE PRODUCTION OF DOCUMENTS
Authored by: Anonymous on Sunday, January 04 2004 @ 08:20 AM EST
mmm the only way I can describe this document is that SCO is in a world of hurt.
IBM means business. Serious business. Go IBM!!! Big blue, yep it's gonna be
a big blue alright (blue is aussie lingo for fight).

Dave

[ Reply to This | # ]

OT: Nazgul
Authored by: Anonymous on Sunday, January 04 2004 @ 09:43 AM EST
The IBM legal team is sometimes referred to as the Nazgul.:nbsp; I'm not sure if the term applies to the local attorneys with which IBM works, such as Amy F. Sorenson of Snell and Wilmer.  Still, if you run into Amy again at the courthouse, I hope you will ask her:
What's a Nazgul like you doing in a case like this?
Scott McKellar
http://home.swbell.net/mck9/sco/

[ Reply to This | # ]

IBM'S FIRST SET OF INTERROGATORIES AND FIRST REQUEST FOR THE PRODUCTION OF DOCUMENTS
Authored by: Anonymous on Sunday, January 04 2004 @ 09:58 AM EST
Why is there not a definition of "Linux?"

Even IBM with all their lawyers are not able to define Linux?

[ Reply to This | # ]

"preferred form"
Authored by: Anonymous on Sunday, January 04 2004 @ 11:06 AM EST
18. The term "source code" shall mean the human-readable form of a computer program written in the original and preferred form for human inspection and modification

Compare the wording to the GPL:
The source code for a work means the preferred form of the work for making modifications to it.

I've read several times from (would be?) lawyers that preferred form is ambiguous and this would be a big problem for the GPL in court. IBM's team decided to use preferred, thus this weakness of the GPL appears to be a /. myth.

[ Reply to This | # ]

IBM, Trade secrets, copyrights and patents
Authored by: PeteS on Sunday, January 04 2004 @ 11:28 AM EST
For those of us who have been around the industry a few decades, this is no surprise.

It was then, and now, well known that IBM copyrights and/or patents (as appropriate) everything it can. IBM also maintains strict controls on access to proprietary material it considers trade secrets. I know that because I have dealt with some of their hardware line, and the appropriate driver source under a strict NDA. Note that both the hardware and the source were separately covered.

What I am leading up to here is that IBM has decades of legal experience in this area, with literally thousands of filings, and this interrogatory shows it. Indeed, IBM, or more correctly, every division of IBM, has a fully staffed office (more like a building !) of lawyers, paralegals and various other assistants simply to deal with it's intellectual property. They have historically used outside companies to do the actual filings, relying on their inhouse people for research and documentation.

Given all that experience, I am intrigued that Linux is not defined (although they can do that in a subsequent filing if necessary) but it appears to have shown the SCOX legal team does not have the experience to object by saying

'Define Linux, because otherwise we can not respond properly to your request'

Look for IBM to make more of that if necessary, or ironically, look for Darl & Co to make more of it when they sue someone else.

---
Artificial Intelligence is no match for natural stupidity

[ Reply to This | # ]

Beyond SCO
Authored by: Anonymous on Sunday, January 04 2004 @ 11:37 AM EST
It would seem IBM is preparing for more than the case du jour.

[ Reply to This | # ]

IBM asks to know what SCO has been feeding analists
Authored by: corran__horn on Sunday, January 04 2004 @ 11:44 AM EST

My own favorite request, as this seems to be how SCO gets its FUD out (by saying just enough to get the press to jump to the final conclusion that SCO wants). Now we will see anything else that (hopefully, for them) fleshes out why analysts were so in love with SCO.

REQUEST NO. 56:

All documents concerning any code or other material disclosed by plaintiff to any person, including but not limited to Laura Didio of the Yankee Group and Bill Claybrook of the Aberdeen Group, relating to plaintiff's allegation that IBM or others have misappropriated, misused or infringed plaintiff's intellectual or other property rights or have otherwise breached an obligation to plaintiff.

REQUEST NO. 57:

All documents concerning any analysis, assessment, opinion, or statement relating to plaintiff's allegation that IBM or others have misappropriated, misused or infringed plaintiff's intellectual or other property rights or have otherwise breached an obligation to plaintiff.

---
#INCLUDE IANAL.h

[ Reply to This | # ]

  • Relevancy - Authored by: Anonymous on Sunday, January 04 2004 @ 12:46 PM EST
    • Relevancy - Authored by: Anonymous on Monday, January 05 2004 @ 03:19 PM EST
Why Xenix?
Authored by: PeteS on Sunday, January 04 2004 @ 12:04 PM EST
PJ asked this in the narrative, so I have unashamedly borrowed some information from The OSI position paper on the subject.

SCO lineage

SCO's own versions of Unix date back to 1979, originally under the name XENIX. After old SCO acquired the Bell Labs codebase in 1995 it sold two Unixes: OpenServer based on the XENIX code, and a UnixWare descendant. All SCO Unixes are genetic Unix, trademark Unix, and proprietary.

From this (I purchased a version of Xenix in 1991 for my then employer, so it definitely predates their purchase of the At&T codebase) IBM may be trying to show that Xenix (or it's derivatives) may have improperly used IBM and/or GPL'd code; or perhaps they are just ensuring they get the entire lineage of SCO's products in discovery.

Then this interesting part (you need to read the position paper and see the lineage for this to make complete sense)

Note that SCO OpenServer (at the end of the line of Unixes descended from XENIX) and SCO Unixware (at the end of the line of AT&T Unixes) are two different products of SCO; but XENIX was old SCO's original Unix, while UnixWare was what it picked up when it bought the AT&T codebase. The dashed arrow between OpenServer and UnixWare 7 reflects the fact that it was a product designed to merge OpenServer 5 with UnixWare 2 (5 + 2 = 7) after old SCO bought the AT&T codebase.

So Xenix is (apparently) part of the codebase where SCOX is alleging trade secret and contract violations. Because Xenix may (and I have no idea) have been part of the codebase that IBM licensed, IBM probably wants to see it, separately.

I can think of three possible reasons here

1. So they can see if Xenix found it's way into AIX (highly improbable, as it wan't that good)

2. If Xenix is part of the SCO source, and not part of the AIX codebase (and therefore not part of any Linux codebase), it removes a large amount of potential source from any infringement claim.

3. Has Xenix (or updated files from the Xenix codebase) improperly used other copyrighted material (from IBM, BSD or GPL'd code, for instance) without proper attribution, assuming the copyright permits redistribution.

Although I have seen nothing about this in the SCOX filings, the fact that Xenix is, or may be, still part of the SCO offerings makes it properly a subject for discovery.

---
Artificial Intelligence is no match for natural stupidity

[ Reply to This | # ]

IBM'S FIRST SET OF INTERROGATORIES AND FIRST REQUEST FOR THE PRODUCTION OF DOCUMENTS
Authored by: Anonymous on Sunday, January 04 2004 @ 01:35 PM EST
<i>REQUEST NO. 52:

Documents sufficient to show plaintiff's organizational or personnel structure,
including but not limited to organization charts, flow charts and personnel
directories.</i><p>
Perhaps some of these people have contributed things to open-source projects?
Things SCO claims are trade secrets?

[ Reply to This | # ]

What will SCO do?
Authored by: mitphd on Sunday, January 04 2004 @ 02:23 PM EST
Looking at this list (especially the list of documents), it's obvious that SCO hasn't a hope of completing it in 30 days. However, they will have had seven months from the date of IBM's request, so I don't know how much slack the Court will give them.

We can expect that SCO will partially comply with the court order, and will then say "we tried our best, but we need more time". My question is: what is that absolute minimum that SCO must produce on Jan. 11 to avoid serious sanctions? [I'm sure that SCO's counsel have been asking themselves that question ever since the Dec. 5 hearing.]

IBM's requests are quite broad, and will include many documents of little interest along with the material IBM really wants. Can SCO get away with producing only the dross, and put off discovery of the good stuff until some indefinite future time when they can get around to it?

[ Reply to This | # ]

OT : Absolutely totally blown away
Authored by: Anonymous on Sunday, January 04 2004 @ 02:57 PM EST
My most successful incursion into linux territory yet...
A bootable cd called Knoppix. Im on it now.
Brilliant.

Sorry, but I had to tell someone !!!

[ Reply to This | # ]

This is gonna make Tolstoy look like a lightweight.
Authored by: Anonymous on Sunday, January 04 2004 @ 03:58 PM EST
Unix, Xenix, Linux, Microsoft, SCO, Sun, IBM, ATT, et al... man the level of
interconnection mixed with FUD has raised the intrigue to a fever pitch. Will
anyone ever fully get a grasp on what has gone on behind the scenes on all this.
This is the most complex mystery ever contemplated my mankind. I hope the
judge has taken a good speed reading course.

[ Reply to This | # ]

Signs of boilerplate?
Authored by: Anonymous on Sunday, January 04 2004 @ 04:24 PM EST

Interestingly, the definition of "source code" looks like it is IBM boilerplate, not specifically written for this document.

18. The term "source code" shall mean the human-readable form of a computer program written in the original and preferred form for human inspection and modification, and includes but is not limited to source code listings; compiler and/or assembler output listings for such source code; source code listings for macros or "includes" (both executable and mapping) listings used in such source code; job control language files; and/or other files required to create an executable version of a program, including but not limited to user interface components; panels; screen definitions and help text; and c-lists. [Emphasis mine.]

The reference to "job control language" is telling, since Unix doesn't have a Job Control Language, but IBM mainframes do. Few Unix programs have "screen definitions" except embedded in their C source code, but separate definitions are used by some of the programming environments used with IBM mainframes and terminals. In contrast, things like makefiles, perl and shell scripts, message catalogs, and linker configuration files are included only categorically, as "...other files required to create an executable...".

This paragraph must be boilerplate, perhaps developed by the IBM legal department over time. The meaning is clear enough, but it shows a bias towards IBM's older product lines, and perhaps, the scars of battles fought long ago. Since the meaning of this paragraph has already been significant in the case, it's interesting to see that it apparently wasn't written specifically for SCO.

The meaning of "panels" and "c-lists" might give more insight into the history of this paragraph. Does anyone know what they are? Are they mainframe terms?

[ Reply to This | # ]

IBM'S FIRST SET OF INTERROGATORIES AND FIRST REQUEST FOR THE PRODUCTION OF DOCUMENTS
Authored by: TechnoCat on Sunday, January 04 2004 @ 06:57 PM EST
Am I correct in my assumption that because...
  • This list was submitted by IBM in June and
  • SCO didn't challenge these interrogatories as inappropriate to Judge Wells (they did challenge and have thrown out two in December I recall)
  • Judge Wells did toss out two, numbers 9 and 10, without significant objection from IBM but otherwise ordered SCO to fully comply
  • Judge Wells specified in her order compelling discovering IBM is to provide SCO a list of requested documents ... and SCO is to produce all requested documents.
therefore they are obligated to these and cannot now challenge them? In other words, that IBM's enormous request was granted nearly in entirety and SCO has to provide it to continue the process?

[ Reply to This | # ]

OT: Open Source for Windows
Authored by: Anonymous on Sunday, January 04 2004 @ 07:05 PM EST
Wonder if this might let you take baby steps toward migrating your users, or yourself, from Windows to Linux. It's a repository of open source software that has been ported to Windows.

Or, if you're forced to work in Windows, these might help you ease the pain.

You can download individual programs, I think, and there's also a CD available, though they can't get EVERYTHING onto one CD.

http://gnuwin.epfl.ch/apps/en/in dex.html

[ Reply to This | # ]

Request Number 62
Authored by: orgngrndr on Sunday, January 04 2004 @ 07:37 PM EST
REQUEST NO. 62:

A copy of all source code and object code relating to all releases of any
product ever manufactured, marketed, sold, or distributed by plaintiff,
including but not limited to: (a) UnixWare; (b) SCO OpenServer; (c) ReliantHA;
(d) NeTraverse Merge; (e) each of the "Optional Services" for the
UnixWare product ever described on plaintiff's website; (f) SCO XENIX; and (g)
Skunkware.


Remember Microsoft licensed Xenix early on in a feeble attempt to actually sell
a Unix product to its consumer base.

I read somewhere, but can't remember where, that the license was "in
perpetuity" much like how AIX and Sun's products were licensed.

IBM probably want's to know if Microsoft Xenix licensing plan has anything to
do with Microsoft's licensing of SCO source or whether it, as M$ claims, is
needed for it unix compatibility tools.

[ Reply to This | # ]

Xenix aspect is Complicated
Authored by: Anonymous on Sunday, January 04 2004 @ 07:46 PM EST

Why Xenix? Well, it touches on Microsoft involvement as well as contributions to the Kernel ABI code.

The Xenix side of the story is quite complicated. It's well known that Microsoft was involved in the port of Unix to micros (Xenix) and that that was the first OS that MS worked on. (In fact, early DOS technical references and marketing material trumpeted the fact that DOS would eventually include many features from Xenix).

What's not as well known is that MS was involved in the port of Unix to the 386; this was known as Unix/386 early on. As part of that work, AT&T agreed that all Intel-compatible versions of Unix-- forever-- would have a certain basic compatibility with Xenix and would be able to run a set of Microsoft Xenix applications, including the ancient Multiplan spreadsheet (I don't remember the other applications, but I suspect that the Xenix character-mode version of Word 5 was one of them). This arcane and burdensome requirement was inherited by Univel, Novell, and Old SCO. Old SCO finally used the European Commission's Anti-Trust laws to get free from this requirement in 1997 (Microsoft's Press Release (happy, happy!); "Boycott Microsoft" commentary on the MS press release; Short CNet article on that ruling).

So the Xenix code is important in determining the lineage of Intel Unix. It may also be important in understanding Microsoft's role in all of this, including the relationship between MS and Old SCO.

But the place that Xenix touches Linux is in the area of application binary interface (ABI) compatability. A lot of the ABI/iBCS (Intel Binary Compatability Specification) work in Linux focussed on getting Xenix applications to work properly on Linux. It may seem odd that anyone cared about this, but ABI/iBCS was important to companies migrating from SCO to Linux; for example, many s upport messages at RedHat mention it. Two of my clients are still running mission-critical Xenix/Unix software on Linux (including "Microsoft FoxPro 2.6 for Unix") using the ABI/iBCS features (though not the SCO shared libraries, FoxPro is statically linked).

Thus, the request for the Xenix code seems reasonable, considering Mr. Hellwig's work on the Linux ABI code while working for SCO, SCO's emphasis on ABI, and the potential damage to SCO in terms of customers migrating away from the SCO Unix products.

[ Reply to This | # ]

And the object code
Authored by: hardcode57 on Sunday, January 04 2004 @ 07:56 PM EST
I love that IBM are also demanding the object code. In effect they are saying
'and prove that what you sent us actually compiles into what you released'.
SCO must be getting the feeling that they can run but they can't hide.

[ Reply to This | # ]

IBM'S FIRST SET OF INTERROGATORIES AND FIRST REQUEST FOR THE PRODUCTION OF DOCUMENTS
Authored by: suppafly on Monday, January 05 2004 @ 01:06 AM EST
Some of IBM's demands look like they are specifically trying to make SCO prove
the lineage of the unix they claim to have inherited.

[ Reply to This | # ]

IBM'S FIRST SET OF INTERROGATORIES AND FIRST REQUEST FOR THE PRODUCTION OF DOCUMENTS
Authored by: Anonymous on Monday, January 05 2004 @ 12:34 PM EST
IBM appears to be fishing, even if their lawyers won't admit it.

If I were the judge, I'd tell IBM "Which of these is directly related to
the Linux-source-code issue, and why" and only grant discovery on those
issues, at least at first.

After I see that SCO is lying, or at least being reckless about its Unix/Linux
claims - and IMHO SCO *is* doing one or both of those - then I'd be much more
inclined to "look under the rug" and expose all of SCO to scrutiny.
Can you say "grand jury investigation" and "criminal
fraud"? I knew you could.

Personally, I detest SCO's actions, but IBM has a responsibility to take the
moral high ground. This means no fishing.


I see SCOX declaring bankruptcy sometime in 2004. Perhaps as early as late
January.

[ Reply to This | # ]

Xenix
Authored by: Anonymous on Monday, January 05 2004 @ 03:23 PM EST
IIRC:

Xenix was developed by Microsoft.

When SCO was founded, part of buying the rights to Xenix was that SCO was to carry over particular parts of the code to any successor product, and pay Microsoft for the use of that code.

The EU unfair competition courts found that this was unfair, and forced Microsoft to release SCO from this requirement if Microsoft wanted to keep selling their products in the EU.

I can't figure out why IBM would want to know the providence of the Xenix code, unless they think Microsoft colluded with SCOX in some way on this suit.

[ Reply to This | # ]

Requests 40,41,42
Authored by: RealProgrammer on Monday, January 05 2004 @ 03:56 PM EST
IBM wants to all documents concerning any communication relating to this
litigation including but not limited to:

- (40) communications with plaintiff's employees, shareholders, directors or
officers.

- (41) the public

- (42a) the decision to commence or pursue this lawsuit or

- (42b) other lawsuits relating to UNIX or Linux.

In other words, "show us what you really want to get out of this".
I suspect that will be expressed in terms of shareholder value :-).


---
(I'm not a lawyer, but I am a literate citizen)

[ Reply to This | # ]

My favourite:
Authored by: turambar386 on Monday, January 05 2004 @ 03:57 PM EST
REQUEST NO. 45:

All documents concerning plaintiff's decision to change its name.


This one really interests me. I'd love to see these documents!

[ Reply to This | # ]

Xenix - Don't forget Willows Project
Authored by: Anonymous on Monday, January 05 2004 @ 05:40 PM EST
Ray Noorda funded a project to put a GPL'd version of the Windows API on L/Unix. This also would be ABI level compatibility?
Here's a Random Googled link Just look for Noorda + "Windows API" and you find a lot. to one of the discussions of that era. willows.com is on same subnet as NFT.com (Noorda Family Trust) and one subnet away from SCO.com.

[ Reply to This | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )