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
Your contributions keep Groklaw going.
To donate to Groklaw 2.0:

Groklaw Gear

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


To read comments to this article, go here
Exhibit A to SCO's Notice to Cure Continued
Saturday, July 11 2009 @ 03:43 PM EDT

Another 100 or so pages of lists of contracts and leases, quite a few from last century, SCO's Exhibit A continued, attached to SCO's Notice to Cure:
07/10/2009 - 833 - Exhibit A (Continued) to Notice of Cure Amounts in Connection with the Assumption and Assignment of Unexpired Leases and Executory Contracts (related document(s) 815 , 832 ) Filed by The SCO Group, Inc.. (Attachments: # 1 Exhibit A Part 2 # 2 Exhibit A Part 3) (Makowski, Kathleen) (Entered: 07/10/2009)

I see what looks like some duplication, but the final pages of the first PDF are interesting, where SCO lists contracts with money due various folks. This continuation of Exhibit A is in three parts, around a hundred pages in all. The first part of the second PDF is intriguing, in that they didn't just copy some old lists. There is a note, which to my mind doesn't seem to support SCO's trial theories about UNIX and Unixware.

Here's the relevant part of the note:
1) In all cases, (except for Open Source components) binary distribution rights are limited to UNIX or UnixWare products. Definitions vary somewhat, but the intent is often to limit binary sublicensing to products substantially based on UnixWare.
2) Veritas and Symbios source licenses are limited to support of UnixWare -- e.g., OEM reselling UnixWare and wanting to provide customer support. We cannot license this source for any other purposes.
3) Binary distribution of our license manager does not make sense -- it is of value only for our product and for use with licenses sold by SCO
4) Source code to the SGI NF8 graphics driver can only be delivered for use in creating a product that is compatible with an SCO UnixWare Operating System.
Isn't that weird? It's arguing a point on a list. And excuse me for remembering, but didn't SCO swear on a Bible at the trial in Utah in SCO v. Novell, that UNIX and UnixWare are the same thing and that the only way to get UNIX any more was to license UnixWare?
Darl McBride: SCO -- that is correct. SCO UnixWare is a little bit unique in this diagram in that it serves both as the trunk of the tree and also as a branch.

And so if somebody came to the company and said, we want to get the core intellectual property to UNIX, and we want to take a license for that, for example, IBM did that with us in 1998, we said, okay, if you want to get core access to the UNIX intellectual property or the trunk code, the way you do that is through a UnixWare license. So UnixWare is unique compared to any of these other branches in that the core trunk is where the UNIX intellectual property was held was inside of UnixWare.

Q. Well, isn't it true that when you arrived in Caldera in late 2002, you realized that the revenues from the branches UnixWare and OpenServer were, in your words, marching south and dying off; correct?

A. They were under severe competition from primarily Linux but also from others. But, yes, they had been going south for a number of years.

Q. And because the revenues from the branches UnixWare and OpenServer were marching south and dying off, your strategy was to focus on maximizing the value of the trunk; correct?

A. In part, that's correct.

Q. And the trunk of the tree is the core SVRX code; correct?

A. We call it different things along the way. Sometimes we call it SCO UNIX; sometimes we call it System V; and sometimes we call it SVRX; sometimes we call it UnixWare. But it's all basically the core IP UNIX.

Q. And that's the core IP that dates back at AT&T?

A. It started at AT&T, but it had evolved dramatically over the years.

Q. And it was the core UNIX IP that you and Mr. Sontag and others sought to mine with the SCO source program at SCO in 2002 through 2004; correct?

A. We sought to take the core UNIX ownership rights that we had that were primarily embodied in UnixWare and be able to get more value in the marketplace out of that core intellectual property.

Q. But you don't know, do you, whether all of the code from the core UNIX IP exists in UnixWare; correct?

A. The core -- no, that's not correct. The core code of UnixWare is where the older versions of UNIX have been embodied. It's been that way for years. I worked at Novell, and it was the case then and it's the case now 15 years later.

Q. But my question is, do you know if every line of code of the trunk here, do you know if every line of code in this trunk exists in UnixWare?

A. I know that if you want to license the trunk code, you'd have to do it through UnixWare.

Q. That wasn't my question. My question was, do you know if every line of code in the UnixWare, this core trunk exists in UnixWare?

A. That's my understanding.

I don't know, but I'm thinking perhaps they read Groklaw. If not, maybe they should. It would enhance consistency. And might a bystander like myself begin to wonder why unXis wants to buy assets that the CEO himself testified have been "going south" for years? If unXis isn't interested in the litigation, where's the business plan here?

And look at the first PDF, page 30, the last page. It's the end of Exhibit A-1, a list of 3rd party software licenses for UnixWare and OpenServer. It shows HP as 3rd party licensor of something listed as Open Desktop Secureware, and SCO lists it as "Obsolete - Special Order". Open Desktop is UNIX, not UnixWare. You can see that in this press release, which was sent out by SCO to announce the partnering with SecureWare:

The Santa Cruz Operation (SCO) and SecureWare have launched the first commercial product to allow users to run UNIX and Commercial-Off-The-Shelf (COTS) MS DOS and MS Windows 3.1 applications at distinct security levels within separate windows on a single Intel desktop....A secure version of SCO UnixWare is also available.
It pays to go over this kind of filing with care to details. That's where you guys come in. Many eyeballs.

  View Printable Version


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 )