SCO's 294 Alleged Violations

A summary of SCO's sealed Final Disclosure, reverse engineered from open court documents in SCO v IBM (U.S. District Court, District of Utah, case number 2-03-cv-294).

This chart is dedicated in gratitude to each of the developers named below.

Recent changes

v10.0.2 16 August 2007 corrected hearing URLs/dates
v10.0.1 18 April 2007 updated items 94, amended 112; 'precluded' instead of 'dismissed' re. Order 718
v10.0 9 April 2007 Extensive revision. New items 58, 61, 68, 74, 86 re. document 981/981-H. Updated items as marked below re. documents 897, 902, 913, 950, 956, 960, 968, 981, 983, recent hearings and recent research. New scorecard and index of motions; filename column folded into detail column.

Scorecard

Items in SCO's Final Disclosure 294 217 in Interim Disclosure 2004-10-28 [SCO 542 p.2]
294 in Final Disclosure 2004-12-22 [SCO 589 p.2 incorrectly states total 293]
Precluded (too vague) 187 200 requested: items 2-112, 143-149, 165-182, 186-193, 204, 232-271, 279-293
2 requests withdrawn: items 2, 204
11 request denied: items 23, 43, 90, 94, 186-192
187 request granted: items 3-22, 24-42, 44-89. 91-93, 95-112, 143-149, 165-182, 193, 232-271, 279-293
Abandoned by SCO 7 6 re. use of SVID spec: items 273-278
1 'numerous kernel patches': item 294
Inoperative 11 10 precluded (Monterey/AIX): items 194-203
1 no misconduct (SysV/Dynix): item 204
Ongoing, challenged by MSJ 780
(contractual)		 43 items 1, 2, 23, 43, 90, 94, 113-142, 186-192
Ongoing, challenged by MSJ 785
(non-infringement)		 46 52 requested: items 150-164, 183-185, 205-231, 272-278
6 abandoned by SCO: items 273-278
Percent of items still ongoing 30.3%  

The Items

Item Status Allegation
IBM 835 Exh 588 pp#45-47
unless otherwise noted		 Detail
1 Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		Disclosure of AIX JFS Journaling File System
[SCO 707 p.6] 		Breach of contract relating to the AIX operating system [IBM 832-2 p.63]. Only one of the Items identifies any UNIX System V source code. That Item identifies 17 lines of code from one version of a UNIX System V file. SCO's experts do not address this file in their expert reports. SCO does not allege that IBM disclosed this file to Linux or otherwise [IBM 832-2 p.63]. The Final Disclosures alleged IBM "literally copied code from Unix System V Release 2.1" and identified one System V file and one AIX file [IBM 696 p.9]. Literally copied code from Unix System V Release 2.1 is present in PFS [SCO 707 p.7]. Barry Arndt: "SCO has alleged in Item 1 of its Final Disclosures that I disclosed the "AIX JFS Journaling File System" to Linux. I did not." [IBM 835 Exh 162]. Steve Best [IBM 835 Exh 168]. David Kleikamp [IBM 835 Exh 218]. Mark Peloquin [IBM 835 Exh 243]. Ben Rafanello [IBM 835 Exh 248].
2 Ongoing
Motion to Limit withdrawn,
Summary Judgment 780 pending		 Read-Copy-Update code
[SCO 724 p.8] 		Breach of contract relating to the Dynix operating system [IBM 832-2 p.63]. IBM's motion to limit included one Item inadvertently (No. 2) [IBM 657 p.2 fn1]. Paul McKenney [IBM 835 Exh 231]. Dipankar Sarma [IBM 835 Exh 258].
3
updated 		Precluded
Motion to Limit granted,
Motion to Reconsider pending 		NUMA Aware locks from ptx to Linux NUMA/ptx locking routines contributed to Linux. The December Submission states (at 5) that the "code in the 4 associated source code files appeared in a patch for the 2.4.6 kernel" and provides an internet address for the patch [SCO 724 p.35]. Relates to the deposition of Tim Wright [SCO 725 pp.3-4]. SCO seeks new depositions of Wright, Lindsley, Huizenga and Vogel [IBM 950 pp.5-6]. Not negative know how [IBM 950 p.10].
  • See http://lse.sourceforge.net/numa/locking/.
    Filenames touched by the patches on that page:
    arch/i386/kernel/numalock.c
    arch/ia64/kernel/numalock.c
    include/asm-i386/numalock.h
    include/asm-ia64/numalock.h
4
updated 		Precluded
Motion to Limit granted,
Motion to Reconsider pending 		Disclosure of Dynix/PTX NUMA-aware spinlocks and statement that they have been ported to Linux SCO seeks new depositions of Wright, Lindsley, Huizenga and Vogel [IBM 950 pp.5-6]. Not negative know how [IBM 950 p.10].
  • See lse-tech post by Jack Vogel.
    Filenames touched by the patch in that post:
    arch/i386/kernel/irq.c
    arch/i386/kernel/numalock.c
    include/asm-i386/numalock.h
    include/asm-i386/smplock.h
5
updated 		Precluded
Motion to Limit granted		 Disclosure of Dynix/PTX "jlock" by porting it to Linux
6 Precluded
Motion to Limit granted		 Disclosure of "decoder ring" with ptx primitives in column 1 and the closest Linux equivalent in column 2  
7 Precluded
Motion to Limit granted		    
8
updated 		Precluded
Motion to Limit granted		 Confirmation that all ptx optimizations are in patch submitted to Linux by D. Sarma
9
updated 		Precluded
Motion to Limit granted		 Disclosure of several internal implementation details of the Dynix/PTX NUMA API [IBM 981-H p#5] SCO refers to a password-protected IBM website [IBM 620 p.4 fn2]. SCO has claimed that disclosure of an API is a violation of its rights [IBM 981-H p#5]
10 Precluded
Motion to Limit granted		 Port of highly parallel distributed lock manager from ptx to Linux One of SCO's less precise items [IBM 657 pp.7-8].
11 Precluded
Motion to Limit granted		 Port of Sequent SPIE test suites to Linux SCO refers to a password-protected IBM website [IBM 620 p.4 fn2]. Includes lines and files of testing technology [SCO 707 p.8 fn2].
12 Precluded
Motion to Limit granted		 Evidence of disclosure of ptx RCU into Linux  
13 Precluded
Motion to Limit granted		    
14 Precluded
Motion to Limit granted		    
15
updated 		Precluded
Motion to Limit granted,
Motion to Reconsider pending 		Detailed disclosure of ptx NUMA-aware locks for adaptation and use in Linux Not negative know how [IBM 950 p.10].
16
updated 		Precluded
Motion to Limit granted		 O_Direct ptx SPIE tests ported to Linux and also disclosed in documentation to "Andrea" IBM contributed 15 testing files to Linux [IBM 696 p.9]. Mr. Rochkind quotes the same email as Item 16 and provides the same level of detail (what little there is) as Item 16. The only difference between Item 16 and Mr. Rochkind's new material is that Mr. Rochkind simply adds 73 additional files to Item 16's list of 15 files [IBM 968 p.33].
17
updated 		Precluded
Motion to Limit granted		 Port of discontiguous memory code from ptx to Linux 2.5
18 Precluded
Motion to Limit granted		 150,000 lines of testing code ported from ptx spie test suites to Linux Test Project. Additional test suites and test cases ported from ptx and AIX to Linux. SCO refers to a password-protected IBM website [IBM 620 p.4 fn2]. Includes lines and files of testing technology [SCO 707 p.8 fn2].
19 Precluded
Motion to Limit granted		 Disclosure of Dynix/PTX implementations of NUMA-aware locking  
20 Precluded
Motion to Limit granted		 Confirmation that ptx was used as source reference for Linux development  
21 Precluded
Motion to Limit granted		    
22 Precluded
Motion to Limit granted		 Port of ptx NUMA code to Linux  
23
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Limit denied		 Disclosure of problems with the error event subsystem (EES) used in PTX
[IBM 835 Exh 292] 		Breach of contract relating to the Dynix operating system [IBM 832-2 p.63]. Martin Bligh [IBM 835 Exh 292]. A disclosure of negative knowhow, where they are discussing how not to do something, to avoid a blind alley, which is part, we would submit, of the confidential information protected by our agreements. And you have an express discussion in e-mail by another identified IBM employee; in this case, Martin Bligh. It relates to the way Dynix and ptx used this system. He states, quote, "We are trying to get for Linux the benefits of blank --" you have that -- "without the associated pain." [Hearing 2006-04-14 p.55]. The material was disclosed in marketing materials [Hearing 2007-03-01 p.27].
24 Precluded
Motion to Limit granted		 Confirmation that ptx was used as source reference for Linux development  
25 Precluded
Motion to Limit granted		 Use of ptx and AIX technology as roadmap for Linux in various significant areas (locks, counters, search trees, allocators and RDBMS)  
26 Precluded
Motion to Limit granted		    
27 Precluded
Motion to Limit granted		 Transferring ptx source code to AIX developers  
28 Precluded
Motion to Limit granted		 Disclosure of implementation of reference counters from ptx to Linux  
29 Precluded
Motion to Limit granted		    
30 Precluded
Motion to Limit granted		    
31 Precluded
Motion to Limit granted		 Implementation of ptx locking algorithms in Linux  
32 Precluded
Motion to Limit granted		 Submission of NUMA APIs from Dynix/ptx and AIX to open source, release of krlock from ptx to Linux and AIX, and suspected release of NUMA-aware locks to Linux Item No. 32 (Tab 22) [SCO 724 p.42]. Tab 22, this is another method and concept dealing with multi processing from Dynix into AIX and from Dynix into AIX for use in Linux. [...] Mr. [McKenney]. You have specific e-mails [...] which embrace the disclosure. You have deposition testimony where, at page 255, there is admission and there were disclosures from ptx and AIX. And [...] you have admissions that certain Sequent technology, subject to contractual protection, was contributed to the AIX kernel and used to enhance AIX [Hearing 2006-04-14 p.55].
33 Precluded
Motion to Limit granted		 Authorization for open-source disclosure of AIX and ptx NUMA-aware locking primitives  
34 Precluded
Motion to Limit granted		    
35 Precluded
Motion to Limit granted		   Item 35 faulted IBM for an alleged "disclosure of how Dynix/PTX dealt with this problem" and cited a one-page email containing the minutes to a conference call as well as an unrelated presentation dated more than three years after the conference call. SCO identified three Linux files that it claimed contained the allegedly misused material, but no versions or lines code for these Linux files. There was not even a hint of where Dynix/ptx actually "dealt with this problem". [IBM 748 p.57].
36 Precluded
Motion to Limit granted		    
37 Precluded
Motion to Limit granted		    
38 Precluded
Motion to Limit granted		 Checking Updates in Memory
[Hearing 2006-10-24 p.14] 		Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. This is a disclosure of a method and concept that actually goes back to UNIX System V. It relates to an automatic method of checking for updates in memory. [...] the IBM employee, Mr. Irwin, who made the disclosure. [...] it shows the actual e-mail of how this should be handled, an express reference to SVR4, which is System V release four, which prove that there are, and then it goes on to get into the merits of the method and concept [Hearing 2006-04-14 p.54]. The Minutes from the February 21, 2003 teleconference during which the disclosure was made are referenced, as are the specific Linux files involved [SCO 724 p.42]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
39 Precluded
Motion to Limit granted		 Use of ptx as source reference for programming Linux  
40 Precluded
Motion to Limit granted		    
41 Precluded
Motion to Limit granted		 Use of ptx as source reference for memory programming in Linux  
42 Precluded
Motion to Limit granted		    
43
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Limit denied		   Breach of contract relating to the Dynix operating system [IBM 832-2 p.63]. Negative know how, learning from TCP failures to help networking and storage for Linux [Order 718 p.36]. The material had nothing to do with Dynix/ptx [Hearing 2007-03-01 p.26]. Possibly related to the deposition of Tim Wright [IBM 981-A2 p.115, referring to sealed IBM 835 Exh 507].
44 Precluded
Motion to Limit granted		    
45 Precluded
Motion to Limit granted		    
46 Precluded
Motion to Limit granted		   Item No. 46 is a February 26, 2003 email exchange between IBM developers Martin Bligh, James Cleverdon and a public Linux mailing list in which Bligh and Cleverdon describe a "bug fix" Bligh made to Linux and how it was based on the method from Dynix/ptx. SCO actually cited the files and lines where this code occurs in Linux. [...] Moreover, these same lines of Linux source were included in the patch Bligh disclosed to Linux, which SCO included as December Submission Item 236 [SCO 724 pp.43-44].
47 Precluded
Motion to Limit granted		    
48 Precluded
Motion to Limit granted		    
49 Precluded
Motion to Limit granted		    
50 Precluded
Motion to Limit granted		    
51 Precluded
Motion to Limit granted		    
52 Precluded
Motion to Limit granted		    
53 Precluded
Motion to Limit granted		 Semaphores
[Hearing 2006-10-24 p.14] 		Method used in Dynix to handle semaphores (which are used in "locking" to restrict access to shared resources in a multiprocessing environment) [SCO 724 p.42]. This is a method and concept which deals with improving locking [...] an IBM employee, Mr. Wright [...] It refers to the e-mails and quotes them, where those were actually made to a Daniel Phillips, who was a Linux developer, and it makes specific references that they are getting this from Dynix/ptx. You have references that this method, this particular method, quote, "is not currently used in Linux." You have another reference at the bottom of that page saying the classic quoting style in Dynix/ptx is then and goes on and provides source code in the context of the e-mail saying that this is the right way to go about it [Hearing 2006-04-14 p.53]. Possibly related to Item 85 and Item 294 [SCO 725].
54 Precluded
Motion to Limit granted		    
55 Precluded
Motion to Limit granted		 Disclosure of Dynix/PTX code and method for avoiding a lock via "cut-and-paste from ptx code". Possibly related to Item 146 and Item 294 [SCO 725].
56 Precluded
Motion to Limit granted		    
57 Precluded
Motion to Limit granted		    
58
NEW 		Precluded
Motion to Limit granted		   Discloses methods in Dynix/ptx for avoiding shuttling shared data between CPUs, so as to improve NUMA performance [IBM 981-H p#2]
59 Precluded
Motion to Limit granted		    
60 Precluded
Motion to Limit granted		    
61
NEW 		Precluded
Motion to Limit granted		   Disclosure that high performance VM efforts in Dynix/PTX resulted in good TLB (translation look-aside buffer) savings [IBM 981-H p#2]
62 Precluded
Motion to Limit granted		   Possibly related to Item 63 and Item 236 [SCO 725].
63 Precluded
Motion to Limit granted		   Possibly related to Item 62 and Item 236 [SCO 725].
64 Precluded
Motion to Limit granted		 Use of Dynix/ptx as source reference for programming memory virtual address space in Linux  
65 Precluded
Motion to Limit granted		    
66 Precluded
Motion to Limit granted		    
67 Precluded
Motion to Limit granted		    
68
NEW 		Precluded
Motion to Limit granted		   Disclosure that hand-placing/binding are frequently used in Dynix/ptx for benchmarks, in tuning customer applications, and in working around performance bugs [IBM 981-H p#2]. A three page email on performance tuning [IBM 981-H p#6].
69 Precluded
Motion to Limit granted		    
70 Precluded
Motion to Limit granted		    
71 Precluded
Motion to Limit granted		    
72 Precluded
Motion to Limit granted		    
73 Precluded
Motion to Limit granted		    
74
NEW 		Precluded
Motion to Limit granted		   Discloses method used in Dynix/ptx for keeping related processes together so as to improve performance for Oracle and BAAN applications [IBM 981-H p#2]
75 Precluded
Motion to Limit granted		    
76 Precluded
Motion to Limit granted		    
77 Precluded
Motion to Limit granted		    
78 Precluded
Motion to Limit granted		    
79 Precluded
Motion to Limit granted		 Confirmation that an earlier RCU patch was based on the Dynix/PTX algorithm  
80 Precluded
Motion to Limit granted		    
81 Precluded
Motion to Limit granted		    
82
updated 		Precluded
Motion to Limit granted		 Disclosure that patch is based on the Dynix/PTX implementation, and that it uses a per-CPU context-switch counter
83 Precluded
Motion to Limit granted		    
84 Precluded
Motion to Limit granted		 Discloses RCU patches, and acknowleges that they were based on original Dynix/PTX code  
85 Precluded
Motion to Limit granted		   Possibly related to Item 53 and Item 294 [SCO 725].
86
NEW 		Precluded
Motion to Limit granted		   In 1998 Paul E. McKenney and John D. Slingwine (the inventors of RCU) wrote a paper titled 'Read-Copy-Update: Using Execution History to Solve Concurrency Problems' which appeared in the October 1998 Parallel and Distributed Systems conference. This paper forms the basis of Item 86 [IBM 981 p.87 fn61].
87 Precluded
Motion to Limit granted		 Disclosure of Dynix/PTX RCU code, documentation, and API  
88 Precluded
Motion to Limit granted		    
89 Precluded
Motion to Limit granted		    
90
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Limit denied		 Disclosure of problems with PTX's method for event logging
[IBM 835 Exh 292] 		Breach of contract relating to the Dynix operating system [IBM 832-2 p.63]. Negative know how, avoiding a logging event that caused problems in PTX [Order 718 p.36]. Martin Bligh [IBM 835 Exh 292]. The material was disclosed in marketing materials [Hearing 2007-03-01 p.27].
91 Precluded
Motion to Limit granted		 Dynix/ptx RCU facilities in AIX  
92
updated 		Precluded
Motion to Limit granted		 Information that IBM contributed Dynix/PTX code to Linux from "michael," who appears to be a former Sequent employee. Possibly M. Anderson. An anonymous posting somewhere on the internet by a person purported to be called Michael, purported to have been a former employee of IBM saying that Sequent didn't get into the business of contributing Dynix/ptx code to Linux, IBM did. That's it. While we could in theory search the haystack of this code for the allegedly misued information, the real problem here, Your Honor, is that the needles that we have been sent to find are undefined needles [Hearing 2006-10-24 pp.54-55].
93 Precluded
Motion to Limit granted		   For some of the Items (e.g., Item 93), the Final Disclosures reveal little more than the minimal description found in SCO's Complaint [IBM 672 p.8]. It says IBM made NUMA contributions [Hearing 2006-04-14 p.66].
94
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Limit denied		 Statement as to the value to LTC of having worked at Sequent on NUMA and SMP
[IBM 835 Exh 293] 		Breach of contract relating to the Dynix operating system [IBM 832-2 p.63]. Patricia Gaughen: "As far as I am aware, all IBM's Linux contributions relating to NUMA and SMP were original IBM works." [IBM 835 Exh 293]. The material had nothing to do with Dynix/ptx [Hearing 2007-03-01 p.26].
  • Possibly relates to: 'during an interview with Linux Magazine about the state of the Linux kernel in 2001, IBM programmer Patricia Gaughen stated that Linux was "not where the proprietary Unixe[s] are yet, but we are making much faster progress due to the experienced Dynix/IRIX/AIX/SN1/Yalnix/ <fill_in_the_blank> hackers"' [SCO 724 p.50 fn15]. See 'State of the Kernel' 2002-01-15 (needs reg/bugmenot), which features Ms Gaughen, but not the words of which SCO complains (possibly an unused part of an email interview).
95 Precluded
Motion to Limit granted		    
96 Precluded
Motion to Limit granted		    
97 Precluded
Motion to Limit granted		    
98 Precluded
Motion to Limit granted		 Use of ptx NUMA internals in Linux SCO refers to a password-protected IBM website [IBM 620 p.4 fn2].
99
updated 		Precluded
Motion to Limit granted		 NUMA aware spinlocks developed originally for ptx ported to Linux
100 Precluded
Motion to Limit granted		 Sequent Lock Manager (SLM) ported from ptx to Linux 2.4 using RCU locks and patches of other ptx primitives  
101 Precluded
Motion to Limit granted		    
102 Precluded
Motion to Limit granted		 Suspected disclosure of AIX APIs to SuSE for use in Linux and disclosure of training slideset on ptx scheduler for use in Linux scheduler maintenance  
103 Precluded
Motion to Limit granted		 Disclosure of AIX and ptx APIs for NUMA in Linux  
104 Precluded
Motion to Limit granted		 Confirmation of intended disclosure of design documents and API descriptions from ptx to SuSE  
105 Precluded
Motion to Limit granted		 Suspected disclosure of AIX and ptx design documents to SuSE  
106 Precluded
Motion to Limit granted		    
107 Precluded
Motion to Limit granted		 Reference to ptx source when creating Linux RCU  
108
updated 		Precluded
Motion to Limit granted		 Suspected use of SMP scaling data points from AIX and ptx for use in Linux "The SMP-scaling work will necessarly be high-level, but we can get (very rough) data points from AIX and ptx" [IBM 981-H p#4]
109 Precluded
Motion to Limit granted		 Use of ptx design information (Macsyma scripts) to do rclock performance analysis in Linux for NUMA and SMP Possibly related to Item 6 [SCO 725]. Seems to say that an internal tool was used first with Dynix/ptx, then later was used with Linux [IBM 835 Exh 588 p#74].
110 Precluded
Motion to Limit granted		    
111 Precluded
Motion to Limit granted		    
112 Precluded
Motion to Limit granted		 Suspected disclosure of System V package tools for use by Verizon in Linux Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
113
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract relating to the Dynix operating system. Code from Sequent's SPIE Test Suites as well as code from the Linux Test Project. None of that testing code is part of either the Dynix or Linux operating systems [IBM 832-2 p.64]. Wayne Boyer [IBM 835 Exh 173]. John George [IBM 835 Exh 196]. Total approximately 9000 lines of code [Hearing 2006-11-30 p.9]. The e-mail on which SCO's expert, Mr. Rochkind, relies in saying that the Linux LTP contribution was actually from DYNIX is talking about a different set of LTP code than that which is at issue in this case. Mr. Rochkind's testimony is unsupportive of SCO's position. [Hearing 2007-03-01 p.56].
114
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
115
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
116
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
117
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
118
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
119
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
120
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
121
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
122
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
123
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
124
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
125
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
126
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
127
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
128
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
129
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
130
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
131
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
132
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
133
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
134
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
135
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
136
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
137
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
138
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
139
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
140
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
141
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
142
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Amend pending 		  Breach of contract re. SPIE Test Suites. As Item 113 above.
143 Precluded
Motion to Limit granted		 Disclosure of nineteen test suites from ptx to Linux Test Project Includes lines and files of testing technology [SCO 707 p.8 fn2].
144 Precluded
Motion to Limit granted		 Disclosure of Dynix/ptx and AIX algorithms and techniques via the K42 development project  
145 Precluded
Motion to Limit granted		 Evidence of IBM's building on ptx performance and correctness experience in coding Linux  
146
updated 		Precluded
Motion to Limit granted		 Use of Dynix/ptx for Linux development Method and concept [SCO 724 p.8]. Item 146, one of SCO's more precise items, faults IBM for "Use of Dynix/ptx for Linux development" [IBM 657 pp.7-8] by reference to: (1) an email asking for help with a performance problem, (2) an email response with a suggested analysis technique (differential profiling), (3) a technical paper written by Paul McKenney, (4) a URL reference to scripts that might be of help, and (5) a list of 11 Linux files (names only, no versions or lines) [IBM 835 Exh 588 p#12]. The idea is to compare corresponding buckets of the profile data to determine which portion of the code is most responsible for the slowdown [IBM 835 Exh 588 p#14]. Possibly related to Item 55 [SCO 725 p.6]. Mr Rochkind couldn't go behind IBM's apparent protection on the internet to get at that source code because it's on an internal IBM server where that source code is located and so the most we could do is identify the reference to where it could be found [Hearing 2006-10-24 p.12]. 4 of the 11 Linux filenames in SCO's Item 146 are simply incorrect: there is no Linux file named
arch/i386/oprofile/rmi_int.c,
arch/i386/oprofile/rmi_int.h,
arch/i386/oprofile/op_counter.c, or
arch/i386/oprofile/op_x86_model.c
There are files whose names are close to these, and are likely what was intended, but this presents yet another step IBM must take to determine what SCO actually means [IBM 835 Exh 588 p#19 fn4].
147 Precluded
Motion to Limit granted		 Delivery of 400 ptx test cases to Linux Test Project  
148 Precluded
Motion to Limit granted		 Coding Linux equivalent for kmem goodptr primitive; ported ktest rc from ptx to Linux  
149 Precluded
Motion to Limit granted		 Emulation of the SVR4 system implementation in memory mapping Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
150 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files) [IBM 838-1 p.15 and pp.48-49]. Line-for-line code copied from System V into STREAMS modules used by, among others, enterprise Linux customers to operate "Carrier Grade Linux" [SCO 724-A p.2]. Distributed in Caldera Network Desktop and Caldera OpenLinux under the GPL [IBM 838-1 p.11 and p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
151 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files). As Item 150 above.
152 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files) [IBM 838-1 p.15 and pp.56-57]. Line-for-line code copied from System V into STREAMS modules used by, among others, enterprise Linux customers to operate "Carrier Grade Linux" [SCO 724-A p.2]. Distributed in Caldera Network Desktop and Caldera OpenLinux under the GPL [IBM 838-1 p.11 and p.14]. STREAMS Header file required by POSIX.1 [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
153 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files) [IBM 838-1 p.15 and pp.48-49]. Line-for-line code copied from System V into STREAMS modules used by, among others, enterprise Linux customers to operate "Carrier Grade Linux" [SCO 724-A p.2]. Distributed in Caldera Network Desktop and Caldera OpenLinux under the GPL [IBM 838-1 p.11 and p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
154 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files) [IBM 838-1 p.15 and pp.48-49]. Line-for-line code copied from System V into STREAMS modules used by, among others, enterprise Linux customers to operate "Carrier Grade Linux" [SCO 724-A p.2]. Distributed in Caldera OpenLinux under the GPL [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70].
155 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files) [IBM 838-1 p.15 and pp.48-49]. Line-for-line code copied from System V into STREAMS modules used by, among others, enterprise Linux customers to operate "Carrier Grade Linux" [SCO 724-A p.2]. Distributed in Caldera OpenLinux under the GPL [IBM 838-1 p.14].
156 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files). As Item 150 above.
157 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files) [IBM 838-1 p.15 and pp.48-49]. Line-for-line code copied from System V into STREAMS modules used by, among others, enterprise Linux customers to operate "Carrier Grade Linux" [SCO 724-A p.2]. Distributed in Caldera Network Desktop and Caldera OpenLinux under the GPL [IBM 838-1 p.11 and p.14]. STREAMS header file required by POSIX.1 [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
158 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files) [IBM 838-1 p.15 and pp.48-49]. Line-for-line code copied from System V into STREAMS modules used by, among others, enterprise Linux customers to operate "Carrier Grade Linux" [SCO 724-A p.2]. Distributed in Caldera OpenLinux under the GPL [IBM 838-1 p.14]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
159 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files). As Item 150 above.
160 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files). As Item 150 above.
161 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files). As Item 150 above.
162 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files). As Item 150 above.
163 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files). As Item 150 above.
164 Ongoing
Summary Judgment 785 pending		   Copyright: Streams material (LiS header files). As Item 150 above.
165 Precluded
Motion to Limit granted		 Disclosure of Streams implementation from SVR4
[SCO 707 p.14] 		The whole of the Streams framework as implemented in Linux infringes SCO's copyrights [SCO 707 p.14]. Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
166
updated 		Precluded
Motion to Limit granted		 Disclosure of Streams implementation from SVR4
[SCO 707 p.14] 		The whole of the Streams framework as implemented in Linux infringes SCO's copyrights [SCO 707 p.14]. Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48]. The basis for its claim is an email which refers to "Sun's documentation [web]site" [IBM 981-H p#9]
167 Precluded
Motion to Limit granted		 Disclosure of SVR4 mapping of virtual memory page 0 as "read only" Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
168 Precluded
Motion to Limit granted		   Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
169 Precluded
Motion to Limit granted		 Copying from SVR4 ELF specifications for IBM S390 Linux implementation Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
170 Precluded
Motion to Limit granted		 Memory mapping page 0 as "read only", copying from SVR4 Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
171 Precluded
Motion to Limit granted		 Use of SVR4 ABI as source reference in Linux programming, revealing details of SVR4 ELF/ABI specification and use of SVR4 ELF/ABI specification to develop Linux The entirety of ELF, including the ELF specification, is being challenged. "Use of SVR4 ABI as source reference in Linux programming, revealing details of SVR4 ELF/ABI specification and use of SVR4 ELF/ABI specification to develop Linux" [SCO 707 p.13]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
172 Precluded
Motion to Limit granted		 Attempts to reference of SV43/i386 specs from SCO website as source reference for Linux programming and revealing information from SVR4/ABI specification Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
173 Precluded
Motion to Limit granted		 Use of SVR4 ABI as source reference for programming Linux Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
174 Precluded
Motion to Limit granted		 Proposal for use of SVR4 internals for Linux development Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. Includes lines and files of testing technology [SCO 707 p.8 fn2]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
175 Precluded
Motion to Limit granted		 Use of SVR4 as source reference for programming memory mapping system call in Linux Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
176 Precluded
Motion to Limit granted		 Use of ptx as source reference for programming ESR in Linux Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3].
177 Precluded
Motion to Limit granted		 Use of SVR4 as source reference in programming VFS for Linux Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
178 Precluded
Motion to Limit granted		 Disclosure of Enterprise Volume Management System code from AIX to Linux SCO refers to a password-protected IBM website [IBM 620 p.4 fn2].
179 Precluded
Motion to Limit granted		 Disclosure of Enterprise Class Event Logging code from AIX and Dynix to Linux  
180 Precluded
Motion to Limit granted		 Use of SVR4 internals as a reference for programming Linux Misappropriation in the form of non-literal transfers of methods, structures and sequences from System V contributed to Linux [SCO 724-A p.3]. Item 180 claims only that IBM misused the "internals" of System V Release 4, without any mention of which part of the several-million-line operating system was misused [IBM 672 p.8]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. Copyright infringement [IBM 838-1 p.48].
181 Precluded
Motion to Limit granted		    
182
updated 		Precluded
Motion to Limit granted		 Disclosure of Dynix/PTX Direct I/O Test Suite Includes lines and files of testing technology [SCO 707 p.8 fn2]. An email that refers to Direct I/O [IBM 981 p.43 fn23].
183 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel [SCO 724-A p.2] Misappropriation in the form of changed or revised code [SCO 724-A p.3]. SCO's proprietary System V code was simply copied and pasted into the Linux kernel or associated libraries that were then included in a Red Hat distribution [SCO 724-A p.3]. (Regarding the "Dear Unix Licensee" letter:) A material part of the code identified in this letter was part of the December 2005 Submission [SCO 724-A p.4]. ("ABI Code": errno.h/bsderrno.h/solerrno.h, signal.h, ioctl.h/ioctls.h, ipc.h, acct.h, a.out.h, ecoff.h, stat.h, ctype.h/ctype.c). Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. Header file required by POSIX.1 and the LSB [IBM 838-1 p.14 and p.18]. A Linux kernel file, ownership assigned by Caldera to United Linux [IBM 838-1 p.32]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70].
184 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel [SCO 724-A p.2]. Misappropriation in the form of changed or revised code [SCO 724-A p.3]. SCO's proprietary System V code was simply copied and pasted into the Linux kernel or associated libraries that were then included in a Red Hat distribution [SCO 724-A p.3]. (Regarding the "Dear Unix Licensee" letter:) A material part of the code identified in this letter was part of the December 2005 Submission [SCO 724-A p.4]. ("ABI Code": errno.h/bsderrno.h/solerrno.h, signal.h, ioctl.h/ioctls.h, ipc.h, acct.h, a.out.h, ecoff.h, stat.h, ctype.h/ctype.c). Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. Header file required by POSIX.1 [IBM 838-1 p.14]. A Linux kernel file, ownership assigned by Caldera to United Linux [IBM 838-1 p.32]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70].
185 Ongoing
Summary Judgment 785 pending		   Copyright: Memory allocation code. Line-for-line code copied from System V into the Linux kernel [SCO 724-A p.2]. "One example of many", the specific example shown by Mr Sontag to analysts in June 2003 [SCO 724-A p.3]. Verbatim copying of 80-100 lines of code [SCO 724-A p.5]. Memory allocation code distributed in SCO Linux 4.0 under the GPL [IBM 838-1 p.32]. A Linux kernel file, ownership assigned by Caldera to United Linux [IBM 838-1 p.32]. Less than 25 lines of memory allocation code [IBM 838-1 p.40]. Copyright infringement [IBM 838-1 p.48]. Memory allocation code apparently contributed to Linux by Silicon Graphics but removed from the kernel before IBM submitted its Tenth Counterclaim [IBM 838-1 p.49]. 24 lines [Hearing 2006-11-30 p.10].
186
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Limit denied		 Dynix/ptx event logging techniques
[IBM 835 Exh 237] 		Breach of contract relating to the Dynix operating system. Exposure to Dynix. [IBM 832-2 p.63]. Hien Nguyen [IBM 835 Exh 237]. Jim Keniston [IBM 835 Exh 211]. Larry Kessler [IBM 835 Exh 216]. Haren Babu Myneni [IBM 835 Exh 235]. The programmers allegedly making the disclosure did not have experience in Dynix in the particular technology area cited by SCO [IBM 832-2 p.72]. Undisputed [SCO-960-A3 p.117].
  • Filenames from all four declarations:
    fs/jfs/jfs_logmgr.c
    fs/xfs/xfs_log.c
    kernel/printk.c
    fs/ntfs/logfile.c
187
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Limit denied		 Disclosure of Dynix/ptx networking technology
[IBM 835 Exh 210] 		Breach of contract relating to the Dynix operating system. Exposure to Dynix. [IBM 832-2 p.63]. Vivek Kashyap [IBM 835 Exh 210]. Hal Porter [IBM 835 Exh 246]. The programmers allegedly making the disclosure did not have experience in Dynix in the particular technology area cited by SCO [IBM 832-2 p.72]. Undisputed [SCO-960-A3 p.117]. In some cases the cited technology did not even exist in Dynix [IBM 832-2 p.72]. Undisputed [SCO-960-A3 p.117].
  • Filenames from both declarations:
    net/ipv4/*
    net/ipv6/*
    net/sctp/*
188
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Limit denied		 Dynix/ptx TCP/IP and networking file system technology
[IBM 835 Exh 263] 		Breach of contract relating to the Dynix operating system. Exposure to Dynix. [IBM 832-2 p.63]. Nivedita Singhvi: "All the material that I contributed to these subsystems was developed independently for Linux [...] The Dynix/ptx operating system did not implement the IPv6 networking technology." [IBM 835 Exh 263]. Shirley Ma [IBM 835 Exh 222]. Venkata Jagana [IBM 835 Exh 206] In some cases the cited technology did not even exist in Dynix [IBM 832-2 p.72]. Undisputed [SCO-960-A3 p.117].
  • Filenames from both declarations:
    include/net/tcp.h
    include/linux/tcp.h
    net/ipv4/*
    net/ipv6/*
189
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Limit denied		 Disclosure of Dynix/ptx MPIO technology Breach of contract relating to the Dynix operating system. Exposure to Dynix. [IBM 832-2 p.63]. Mike Anderson: "I have never made any contributions to these files." [IBM 835 Exh 161 pp.2-3]. Based on knowledge available in public literature [Hearing 2007-03-01 p.27].
  • Filenames [IBM 835 Exh 161 p.3]
    drivers/md/multipath.c
    include/linux/raid/multipath.h
190
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Limit denied		 Disclosure of Dynix/ptx driver implementation techniques Breach of contract relating to the Dynix operating system. Exposure to Dynix. [IBM 832-2 p.63]. Mike Anderson [IBM 835 Exh 161]. Jay Vosburgh: "I did not work on device driver implementation techniques in Dynix/ptx" [IBM 835 Exh 274]. The programmers allegedly making the disclosure did not have experience in Dynix in the particular technology area cited by SCO [IBM 832-2 p.72]. Undisputed [SCO-960-A3 p.117].
191
updated 		Ongoing
Summary Judgment 780 pending,
Motion to Limit denied		 Disclosure of Dynix/ptx performance management techniques
[IBM 835 Exh 225] 		Breach of contract relating to the Dynix operating system. Exposure to Dynix. [IBM 832-2 p.63]. Michael Mason: "I have never made any contributions to these files." [IBM 835 Exh 225]. Ruth Forester: "I have never made any contributions to these files." [IBM 835 Exh 188]. The programmers allegedly making the disclosure did not have experience in Dynix in the particular technology area cited by SCO [IBM 832-2 p.72]. Undisputed [SCO-960-A3 p.117].
  • Filenames from both declarations:
    include/linux/oprofile.h
    include/linux/profile.h
    kernel/profile.c
    arch/i386/oprofile/backtrace.c, init.c, Kconfig, op_model_p4.c
    arch/i386/oprofile/rmi_int.c, rmi_timer_int.c, op_counter.c, op_86_model.c     (nonexistant files, see Item 146)
    arch/ia64/kernel/perfmon.c, perfmon_default_smpl.h, perfmon_generic.h
    arch/ia64/oprofile/perfmon.c
    drivers/cpufreq/cpufreq_performance.c
192 Ongoing
Summary Judgment 780 pending,
Motion to Limit denied		 Disclosure of Dynix/ptx virtual memory implementation techniques Breach of contract relating to the Dynix operating system. Exposure to Dynix. [IBM 832-2 p.63]. Martin Bligh [IBM 835 Exh 292].
193 Precluded
Motion to Limit granted		 Disclosure of Dynix/ptx fast walk and dcache implementation techniques Contractual violations [Order 718 p.37, see footnote 1 below]. Only supported by the Richard Moore presentation [Order 718 p.35, see footnote 2 below] and a few references to Linux files [Order 718 p.37].
194 Inoperative
Summary Judgment 785 pending		   Copyright, Non-Linux re. AIX for Power (Monterey). The Final Disclosures appear to accuse IBM of copyright infringement with respect to IBM's inclusion into AIX for Power of code from a project known as Project Monterey, but the Court declined to allow SCO to add a claim for copyright infringement relating to that conduct and it has nothing to do with Linux. [IBM 838-1 p.51]
195 Inoperative
Summary Judgment 785 pending		   Copyright, Non-Linux re. AIX for Power (Monterey). As Item 194 above.
196 Inoperative
Summary Judgment 785 pending		   Copyright, Non-Linux re. AIX for Power (Monterey). As Item 194 above.
197 Inoperative
Summary Judgment 785 pending		   Copyright, Non-Linux re. AIX for Power (Monterey). As Item 194 above.
198 Inoperative
Summary Judgment 785 pending		   Copyright, Non-Linux re. AIX for Power (Monterey). As Item 194 above.
199 Inoperative
Summary Judgment 785 pending		   Copyright, Non-Linux re. AIX for Power (Monterey). As Item 194 above.
200 Inoperative
Summary Judgment 785 pending		   Copyright, Non-Linux re. AIX for Power (Monterey). As Item 194 above.
201 Inoperative
Summary Judgment 785 pending		   Copyright, Non-Linux re. AIX for Power (Monterey). As Item 194 above.
202 Inoperative
Summary Judgment 785 pending		   Copyright, Non-Linux re. AIX for Power (Monterey). As Item 194 above.
203 Inoperative
Summary Judgment 785 pending		   Copyright, Non-Linux re. AIX for Power (Monterey). As Item 194 above.
204
updated 		Inoperative
Motion to Limit withdrawn,
Summary Judgment 785 pending 		  Non-Linux. Demonstrating that Dynix was based on UNIX System V [SCO 724 p.8]. Although SCO does provide versions and line numbers for the files identified in Item No. 204, SCO makes no claim as to any misuse of the code identified in Item No. 204. Under the heading "Improperly Disclosed Code, Method, or Concept", SCO states: "N/A" [IBM 620 p.4 fn1]. No IBM misconduct [IBM 657 p.2 fn1]. IBM's challenges to Item Numbers 2 and 204 were withdrawn [SCO 669 Exh B]. SCO expressly included some of the Disputed Items in its copyright claim [IBM 748 p.41]. The only item that identifies System V code in any version of Dynix [IBM 981-A1 p.43].
205
updated 		Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel [SCO 724-A p.2]. Misappropriation in the form of changed or revised code [SCO 724-A p.3]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. Not in Spec 1170 nor in first version of SUS [SCO 956-A1 p.8].
206
updated 		Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. SUS header file required by POSIX.1 [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. Not in Spec 1170 nor in first version of SUS [SCO 956-A1 p.8].
207 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70].
208 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
209 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. The 1999 Swartz study concluded this code was derived from UNIX [IBM 838-1 p.25]. A Linux kernel file, ownership assigned by Caldera to United Linux [IBM 838-1 p.32]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
210 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. The 1999 Swartz study concluded this code was derived from UNIX [IBM 838-1 p.25]. A Linux kernel file, ownership assigned by Caldera to United Linux [IBM 838-1 p.32]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
211 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
212 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. A Linux kernel file, ownership assigned by Caldera to United Linux [IBM 838-1 p.32]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
213 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14].
214 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. A Linux kernel file, ownership assigned by Caldera to United Linux [IBM 838-1 p.32]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
215 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70].
216 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70].
217
updated 		Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. Copyright infringement [IBM 838-1 p.48]. Files declared to be copyrighted by BSD, not USL [IBM 838-2 p.70]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. SCO has in fact claimed copyright protection for alleged components of SVr4 that were created entirely by others, such as BSD [IBM 983 p.62]
218
updated 		Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. Files declared to be copyrighted by BSD, not USL [IBM 838-2 p.70]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70]. SCO has in fact claimed copyright protection for alleged components of SVr4 that were created entirely by others, such as BSD [IBM 983 p.62]
219 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70].
220 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
221 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. The 1999 Swartz study concluded this code was derived from UNIX [IBM 838-1 p.25]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
222 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. The 1999 Swartz study concluded this code was derived from UNIX [IBM 838-1 p.25]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70].
223
updated 		Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. The 1999 Swartz study concluded this code was derived from UNIX [IBM 838-1 p.25]. Files declared to be copyrighted by BSD, not USL [IBM 838-2 p.70]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70]. SCO has in fact claimed copyright protection for alleged components of SVr4 that were created entirely by others, such as BSD [IBM 983 p.62]
224 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. A Linux kernel file, ownership assigned by Caldera to United Linux [IBM 838-1 p.32]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70].
225 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. A Linux kernel file, ownership assigned by Caldera to United Linux [IBM 838-1 p.32].
226 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
227 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14].
228 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. A Linux kernel file, ownership assigned by Caldera to United Linux [IBM 838-1 p.32]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
229
updated 		Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. Files declared to be copyrighted by BSD, not USL [IBM 838-2 p.70]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. SCO has in fact claimed copyright protection for alleged components of SVr4 that were created entirely by others, such as BSD [IBM 983 p.62]
230
updated 		Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. Files declared to be copyrighted by BSD, not USL [IBM 838-2 p.70]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70]. SCO has in fact claimed copyright protection for alleged components of SVr4 that were created entirely by others, such as BSD [IBM 983 p.62]
231 Ongoing
Summary Judgment 785 pending		   Copyright: Single Unix Specification material (header files) [IBM 838-1 pp.48-49]. Line-for-line code copied from System V into the Linux kernel. Material was included in the first version of the Single Unix Specification [IBM 838-1 p.8]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. SUS header file required by POSIX.1 [IBM 838-1 p.14]. The 1999 Swartz study concluded this code was derived from UNIX [IBM 838-1 p.25]. A Linux kernel file, ownership assigned by Caldera to United Linux [IBM 838-1 p.32]. 4.4BSD-Lite material outside the control of SCO and its alleged predecessors [IBM 838-2 p.70]. BSD net/2 material that predates the creation of the SVR4.2 copyrights alleged to be infringed [IBM 838-2 p.70].
232 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. In 39 of the Items (Items 232 to 270) SCO accuses IBM of making improper reference to Dynix source code as a basis for writing additional code, while providing essentially no further information. Each of these 39 items has an "Improper Disclosure" claim of the form: "Use of ptx [i.e., Dynix] programming experience (and a fortiori exposure to related aspects of Unix System V) in programming [or 'implementing'] _________," where the blank contains things such as "MP preemption and synchronization code", "i686 large-memory SMP systems", "code for SCSI Mid-layer Multi-Path IO", and so forth [IBM 835 Exh 588 p#11]. Supported by the Richard Moore presentation [Order 718 p.35, see footnote 2 below], a link to a Linux Kernel archive and a brief list of Linux files [Order 718 p.37]. There is not deposition testimony supporting these alleged misappropriated items [Order 718 p.38].
233 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
234 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
235 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
236
updated 		Precluded
Motion to Limit granted		   Item No. 46 is a February 26, 2003 email exchange between IBM developers Martin Bligh, James Cleverdon and a public Linux mailing list in which Bligh and Cleverdon describe a "bug fix" Bligh made to Linux and how it was based on the method from Dynix/ptx. SCO actually cited the files and lines where this code occurs in Linux. [...] Moreover, these same lines of Linux source were included in the patch Bligh disclosed to Linux, which SCO included as December Submission Item 236 [SCO 724 pp.43-44 and fn12-13, see also footnote 3 below]. Contractual violations [Order 718 p.37].
237 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
238 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
239 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
240 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
241 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
242 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
243 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
244 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
245 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
246 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
247 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
248 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
249 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
250 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
251 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
252 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
253 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
254 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
255 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
256 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
257 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
258 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
259 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
260 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
261 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
262 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
263 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
264 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
265 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
266 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
267 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
268 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
269 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
270 Precluded
Motion to Limit granted		   Contractual violations [Order 718 p.37, see footnote 1 below]. As Item 232.
271
updated 		Precluded
Motion to Limit granted		 All IBM UNIX-based patents from AIX or Dynix/ptx [IBM 981-H p#3] AIX and Dynix/ptx patented technologies, based on UNIX System V, were improperly released for the benefit of, and use by, the Linux development community in developing Linux. SCO merely attaches 34 patents. None of these 34 patents lists any versions, files or lines of code [IBM 620 p.6]. Cites, among others, US Patent Nos. 4,742,447, 4,742,450, and 5,039,979 [IBM 981-H p#3].
272
updated 		Ongoing
Summary Judgment 785 pending		   Copyright: ELF material [IBM 838-1 pp.48-49]. Partially header files; all the Linux kernel material in Item 272 consists of header file code [IBM 838-2 p.59]. elf.h [IBM 838-1 p.14]. Line-for-line code copied from System V into the Linux tool chain used to compile and operate Linux [SCO 724-A p.2]. SCO's proprietary System V code was simply copied and pasted into the Linux kernel or associated libraries that were then included in a Red Hat distribution [SCO 724-A p.3]. Distributed in Caldera Network Desktop under the GPL [IBM 838-1 p.11]. This file is used by lxrun [IBM 838-1 p.20]. A Linux kernel file, ownership assigned by Caldera to United Linux [IBM 838-1 p.32]. Of the 19 files claimed in this one item, only one file (elf.h) is in the Linux kernel [IBM 838-1 p.57]. The part of Item 272 that is implementation is a collection of two dozen elementary functions for accessing ELF data structures [IBM 838-2 p.58]. Some of the infringing ELF material in Linux, including material in Item 272, was not part of the TIS specification [SCO 956-A4 p.107].
  • See SCO 157-28-G. The 18 non-kernel files are probably in binutils and/or glibc.
  • include/linux/elf.h
273
updated 		Abandoned by SCO
Summary Judgment 785 pending 		  Copyright: ELF/SVID material [IBM 838-1 pp.48-49 and IBM 835 Exh 176 p.3]. Not in the Linux kernel [IBM 838-1 p.50]. SCO's allegations of misuse with regard to specification documents lay claim to material that is not owned by SCO. The allegedly infringed specification document material includes 239 segments of material relating to the X Windows System, which SCO neither owns nor controls. The X Windows system is currently owned by M.I.T. [IBM 838-2 p.71]. SCO does not claim copyright in the material in Items 273-278. [SCO 956-A4 p.134] IBM acknowleges that SCO abandons all copyright in the material in Items 273-278. [IBM 983-A2 p.222].
274
updated 		Abandoned by SCO
Summary Judgment 785 pending 		  Copyright: ELF/SVID material. As Item 273 above.
275
updated 		Abandoned by SCO
Summary Judgment 785 pending 		  Copyright: ELF/SVID material. As Item 273 above.
276
updated 		Abandoned by SCO
Summary Judgment 785 pending 		  Copyright: ELF/SVID material. As Item 273 above.
277
updated 		Abandoned by SCO
Summary Judgment 785 pending 		  Copyright: ELF/SVID material. As Item 273 above.
278
updated 		Abandoned by SCO
Summary Judgment 785 pending 		  Copyright: ELF/SVID material. As Item 273 above.
279
updated 		Precluded
Motion to Limit granted,
Motion to Reconsider pending 		  Methods IBM developer Rick Lindsley contributed to improving Linux in the technology area of locking after he had been exposed to Dynix/ptx locking techniques. [...] Supported by deposition testimony admissions from Lindsley himself [...] source code patches contributed by IBM to Linux that consist of hundreds of lines of source code identified by file, version and line [SCO 724 p.43]. Provides a URL address on which numerous patches indicate file, version and line [SCO 902 p.2].
280
updated 		Precluded
Motion to Limit granted,
Motion to Reconsider pending 		  Methods IBM developer Rick Lindsley contributed to improving Linux in the technology area of locking after he had been exposed to Dynix/ptx locking techniques. [...] Supported by deposition testimony admissions from Lindsley himself [...] source code patches contributed by IBM to Linux that consist of hundreds of lines of source code identified by file, version and line. [SCO 724 p.43]. Provides a URL address on which numerous patches indicate file, version and line [SCO 902 p.2].
281 Precluded
Motion to Limit granted		 Port of ptx ktest-rc from ptx to Linux  
282 Precluded
Motion to Limit granted		 Use of ptx performance counters in programming Linux  
283 Precluded
Motion to Limit granted		    
284 Precluded
Motion to Limit granted		 Dynix/ptx implementation of RCU  
285 Precluded
Motion to Limit granted		 Dynix/ptx implementation of RCU  
286 Precluded
Motion to Limit granted		 Dynix/ptx implementation of RCU  
287 Precluded
Motion to Limit granted		 Dynix/ptx implementation of RCU  
288 Precluded
Motion to Limit granted		 Dynix/ptx implementation of RCU  
289 Precluded
Motion to Limit granted		 AIX network test tool Seems to say that an internal tool was used first with Dynix/ptx, then later was used with Linux. [IBM 835 Exh 588 p#74].
290 Precluded
Motion to Limit granted		    
291 Precluded
Motion to Limit granted		 Port of ptx lightweight reader-writer lock  
292 Precluded
Motion to Limit granted		 Dynix/ptx kmem  
293 Precluded
Motion to Limit granted		 Dynix/ptx totimeout  
294 Abandoned by SCO   Extensive use of ptx programming experience (and a fortiori exposure to UNIX System V) in creating numerous Linux kernel patches. SCO attaches a computer disk containing 33,000 single-spaced pages of proposed code contributions. [IBM 620 p.6]. SCO withdrew Item Number 294 [SCO 669 p#16].

Footnotes

[1]"IBM has breached its contracts by permitting IBM developers exposed to Dynix/ptx methods and concepts to contribute to Linux in the same area where each developer worked." [Order 718 p.37]
[2]"Many of SCO's submissions are supported by a presentation given by Richard Moore of IBM's Linux Technology Center in June 2005. In the presentation it appears Mr. Moore discusses the uniqueness of Linux, Linux's advantages and how IBM has helped with Linux development. It briefly compares Linux to other operating systems such as UNIX, Solaris, AIX, HPUX, IRIX, and Dynix. In the court's view this is largely a presentation to help generate interest and business for IBM that does nearly nothing specific to demonstrate what SCO claims was misappropriated. While it discusses Kernel patches, thread locks and NUMA there is nothing that links these back to being originally owned by SCO. And even with a related "smoking gun" email there is once again little connection back to what is allegedly owned by SCO." [Order 718 p.35]
[3] SCO names and shames arch/i386/kernel/apic.c lines 331-336 and arch/x86_64/kernel/apic.c lines 284-289. 
        /* Pound the ESR really hard over the head with a big hammer - mbligh */
        if (esr_disable) {
                apic_write(APIC_ESR, 0);
                apic_write(APIC_ESR, 0);
                apic_write(APIC_ESR, 0);
                apic_write(APIC_ESR, 0);
        }
[SCO 724 p.44 fn13] (lines 429-435 of i386's apic.c in 2.6.17. SCO's legal filing crassly omits the closing brace.)

Motions affecting the Items

Motion to Limit IBM's Motion to Limit SCO's Claims Relating to Allegedly Misused Material [IBM 619]. An Order dismissing or upholding various Items (as noted above) was issued by the Magistrate Judge on 2006-06-28. This Order was upheld in its entirety (against SCO's objections) by the District Judge in a further Order on 2006-11-29.
Motion to Reconsider SCO's Motion for Reconsideration of November 29th Order [SCO 897]. This motion seeks reconsideration of SCO's objections against the Order which upheld the prior Order which dismissed certain Items as above. The motion is now fully briefed but no date for a hearing has yet been set.
Summary Judgment 780 IBM's Motion for Summary Judgment on SCO's Contract Claims (SCO's First, Second, Third and Fourth Causes of Action) [IBM 780]. A hearing was held on 2007-03-01 and judgment is awaited.
Summary Judgment 785 IBM's Motion for Summary Judgment on its Claim for Declaratory Judgment of Non-Infringement (IBM's Tenth Counterclaim) [IBM 785]. A hearing was held on 2007-03-07 and judgment is awaited.
Motion to Amend SCO's Motion to Amend its December 2005 Submission [SCO 913]. This motion seeks to enlarge the December 2005 'Final Disclosure' with additional claims from SCO's subsequent Expert Reports. The motion is now fully briefed but no date for a hearing has yet been set.

Valid XHTML 1.0 CC by-nc-sa Main