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
SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Friday, December 03 2004 @ 02:50 AM EST

Here is SCO's Memorandum in Opposition to IBM's Motion for Partial Summary Judgment on its Counterclaim for Copyright Infringement (Eighth Counterclaim) [PDF] as text, wherein they accuse IBM of "unclean hands" for downloading software from SCO's website and in which they twist and turn, trying to scrape that pesky GPL off their shoe or at least escape or redefine its terms. They would very much like it if the court would exempt them from the consequences of breaching the GPL. Not that they directly admit doing so, but if they did, it was for a very short time, they say, and they are about to stop completely. Try that excuse for stealing money from a bank.

There isn't enough money in the universe to trade for the enjoyment I get from paragraph 19:

"19. SCO never repudiated the GPL, and it always endeavored to comply with its GPL obligations."

I gather the GPL is no longer unconstitutional in SCO's estimation. No, no, this helpful license is what gave SCO the right to copy and distribute Linux, including IBM's code therein, don't you know, and so it is part of their defense against copyright infringement. But on the other hand, they would like to be exempted from the consequences of breach, because it would be hard on them.

The proprietary software world is simply chock full of folks wanting the benefits of using GPL code, without having to abide by the license's terms.

Then they talk a lot about contracts and contract law, offering all kinds of fancy pants arguments, but that has nothing to do with the GPL, which is a copyright license.

They argue they never had notice from IBM that they were in breach. Again, they are talking contract. Their notice is the GPL's terms, and frankly, a company that IPO'd as a Linux company and distributed for years under the GPL should be expected to understand the terms of the license they made their money from and chose to use, and in fact they did understand it. Besides, I've been telling them since May of 2003, over and over and over, that they had problems with the GPL -- it was even a running joke that I was offering remedial courses in a "GPL Summer School", which they continuously flunked -- and because SCO has been quoted in the media as saying that they use Groklaw as a reference, we can assume that they were aware that Groklaw, at least, thought they were breaching the GPL. That at least ought to have made them look it up and make sure to avoid doing so, so their pretense that they were in the dark is a bit hard to swallow.

That's not even talking about the notice of copyright infringement they received from a kernel coder in June of 2003. In July of 2003, Open Source Victoria filed a complaint with the Australian Competition and Consumer Commission, in which it included the information that SCO was in breach of the GPL by seeking license fees from Linux users. This was all before August of 2003, when IBM filed its GPL counterclaim, after which SCO certainly had notice from IBM but did not stop distributing Linux. In September of 2003, Groklaw published an Open Letter to SCO, which was widely reported in the media, and in which we carefully explained that they were breaching the GPL:

"VIOLATIONS OF THE GPL AND COPYRIGHT LAW

"Our first purpose in writing to you is to draw to your attention that there are consequences to violating the GNU General Public License, the GPL.

"You have continued to distribute the Linux kernel, despite alleging that it contains infringing source code. Simultaneously, you are attempting to compel purchase of "Linux Intellectual Property" licenses for binary-only use, the terms of which are incompatible with freedoms granted under the GPL.

"According to the GPL, any violation of its license terms automatically and immediately terminates your permission to modify or distribute the software or derivative works. Note the wording of the GPL:

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

"Releasing software under the GPL is not the same as releasing it into the public domain. Authors retain their copyrights to software licensed under the GPL. Even when authors assign their copyrights to someone else, such as to the Free Software Foundation, the copyrights remain valid, but with the new owner. Therefore, subsequent to termination of your permissions under the GPL, you are in the unhappy position of violating the copyrights of the software authors, if you continue to distribute their software. Under copyright law, you are not allowed to distribute at all without their permission -- and they have chosen to grant that permission only by means of the GPL."

SCO really can't pretend they had no notice. As for their claim of being mostly in compliance with the GPL, I beg to differ. As just one example, look at paragraph 14. SCO acknowledges a GPL violation right there, I think. And as for their "Linux License" being actually a "Unix license", well, perhaps they made an error in naming what they were selling, not to mention the sales pitches we were subjected to for a year and a half. And that raises another issue. When Darl McBride announced SCO had Linux licensees, exactly what was he referring to? For example, note this March 4, 2004 article that repeatedly reports SCO talking about Computer Associates, Questar, Leggett & Platt all licensing SCO's "Intellectual Property License for Linux."

"Software giant Computer Associates Inc. has licensed The SCO Group Inc.'s Intellectual Property License for Linux, SCO Chief Financial Officer Bob Bench confirmed on Wednesday. Two other companies, natural gas supplier Questar Corp. and manufacturer Leggett & Platt Inc. have also signed up for the controversial licensing plan, Bench confirmed, bringing the total number of publicly announced licensees to four.

"SCO maintains that the Linux operating system contains numerous violations of its intellectual property, and in August, the Lindon, Utah, company began offering the IP License for Linux to select companies, saying that they could avert the risk of future litigation by paying $699 for each of their computer processors running Linux.

"On Monday, SCO revealed that EV1Servers.Net, the hosting division of Houston's Everyones Internet Ltd. had signed up for the IP License for Linux.

Now they would have us believe that these licenses had absolutely nothing to do with Linux:

"d. SCO's August 5, 2003 press release (IBM Ex. 31) announced the availability of the UNIX License, which permits 'the use of SCO's intellectual property' in Linux distributions, and this release does not reflect any attempt by SCO to license Linux or any IBM work;

"e. SCO's August 10, 2003 agreement with Computer Associates (IBM Ex. 32) granted a 'license to use SCO UNIX rights' on a Linux operating system, and did not license Linux or any IBM work;

"f. SCO's October 14, 2003 invoice to Leggett & Platt (IBM Ex. 33) for an 'IP Compliance License' does not even mention Linux and did not license Linux or any IBM work;

"g. SCO's December 19, 2003 agreement with Questar (IBM Ex. 34) granted a license to use 'SCO IP rights' which were defined as SCO's UNIX rights and expressly excluded Linux, and did not license Linux or any IBM product; . . .

"j. SCO's January 16, 2004 letter to Lehman Brothers Holdings (IBM Ex. 37) stated that legal action would be considered unless Lehman purchased a UNIX license, and this letter does not reflect any attempt by SCO to license Linux or any IBM product.

"k. SCO's March 1, 2004 agreement with Everyones Internet (IBM Ex. 38) granted a license to use SCO's proprietary UNIX code, and did not grant a license for Linux or any IBM product. . . .

"In an interview on Wednesday, SCO's CFO confirmed that the three companies were licensees, and claimed that his company had now signed up somewhere between 10 and 50 IP License for Linux customers.

"The company's SCOsource program, which seeks licensing fees for SCO's intellectual property, booked US$20,000 in revenue for its most recent quarter, Bench said, all of it from sales of the IP License for Linux. "

So, when were they being truthful? In March, when they were telling us these dopes were signing up for Linux Licenses, or are they telling the truth now, that there isn't a word about Linux in any of these deals? They can't both be true. So either they are lying to the court or they were lying to the market. What did the companies think they were buying? You may recall Mark Heise's February 4, 2004 letter to IBM's David Marriott regarding the licenses:

"Regarding IBM's concerns over SCO's document production, we will likewise address those matters seriatim. Under the heading 'First', Mr. Shaughnessy identified thirteen categories of documents. Each of those is specifically addressed below.

"(1)        'The Linux intellectual property licenses SCO has publicly claimed it has sold to at least ten companies.' At this juncture, I am only aware of a license with Computer Associates, Questar and Leggett & Platt."

So, how can they say Linux had nothing to do with it, when they called the license by the name Linux? There are many more issues that could be raised, but I'll save them for future articles.

You will notice that SCO quotes Larry Rosen's book to support its theory that the GPL raises restraint of trade issues under antitrust law. So I asked Mr. Rosen if he would like to comment, and here is his statement:

"I suppose I should be pleased that the SCO lawyers are reading my book -- or at least they are reading the free sample chapter about the GPL that is posted at Prentice Hall's website. The point they made from that quotation in their brief is a little misleading, however.

"They quoted my suggestion that three words from the GPL, "at no charge," are probably unenforceable as an illegal restraint of trade in some countries. So what? Some people sell free software. Hardly anybody complains that you can go to almost any computer store and buy a copy of Linux. Price isn't the issue; software freedom is.

"Perhaps SCO's lawyers missed the important point I made earlier in the book (in a chapter that cannot yet be freely downloaded from the Internet; they'll have to buy the book at B&N or Amazon): Anyone can sell GPL software. But that license (and every license that satisfies fundamental open source principles) guarantees the freedom to make unlimited copies at no additional charge. So no matter what a distributor charges for the first copy, the laws of economics suggest that the price per copy will quickly drop to the marginal cost of production and distribution. Inevitably someone will sell three copies at half price and make a profit.

"That's perhaps why SCO itself gave away its versions of Linux for free, including whatever of SCO's intellectual property that free software might have contained. They realized what it was worth and set their own price. We are now all free to make copies.

"I haven't been following lately all that SCO grousing to IBM about the GPL and so I couldn't get excited about the rest of their brief. I'm not up-to-date on all those factual and legal disputes between these two companies. But I'm surprised that SCO needed to quote a country lawyer from California to support their assault on Linux. I'm not on their side at all."

Thanks go to Steve Martin, pvant67, and tgf for OCRing, transcribing and helping with the HTML.

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

Brent O. Hatch (5715)
Mark F. James (5295)
HATCH, JAMES & DODGE
[address]
[phone]
[fax]

Robert Silver (admitted pro hac vice)
Edward Normand (admitted pro hac vice)
Sean Eskovitz (admitted pro hac vice)
BOIES, SCHILLER & FLEXNER LLP
[address]
[phone]
[fax]

Stephen N. Zack (admitted pro hac vice)
BOIES, SCHILLER & FLEXNER LLP
[address]
[phone]
[fax]

Attorneys for Plaintiff The SCO Group, Inc.

IN THE UNITED STATES DISTRICT COURT
FOR THE DISTRICT OF UTAH


THE SCO GROUP,

Plaintiff/Counterclaim-Defendant


vs.

INTERNATIONAL BUSINESS
MACHINES CORPORATION,

Defendant/Counterclaim-Plaintiff

SCO'S MEMORANDUM IN
OPPOSITION TO IBM'S MOTION
FOR PARTIAL SUMMARY
JUDGMENT ON ITS
COUNTERCLAIM FOR COPYRIGHT
INFRINGEMENT (EIGHTH
COUNTERCLAIM

Case No. 2:03CV0294DAK
Honorable Dale A. Kimball
Magistrate Judge Brooke C. Wells

TABLE OF CONTENTS

PRELIMINARY STATEMENT.................................................................... 1
SCO'S RESPONSE TO IBM'S "STATEMENT OF UNDISPUTED FACTS" ......................................................... 3
ARGUMENT .............................................................................................................. 11
I. THE GPL AUTHORIZED SCO TO DISTRIBUTE LINUX, INCLUDING ANY
CONTRIBUTIONS MADE BY IBM OF COPYRIGHTED MATERIAL............................................
12
II. SCO DID NOT REPUDIATE OR BREACH THE GPL.........................................................
13
A. SCO Did Not "Repudiate" the GPL..................................................................
13
B. SCO's Licensing Activities Did Not Violate the GPL.......................................................................
15
1. SCO Has Been Collecting Licensing Fees Only for Its
Own Code.......................................................................................
15
2. SCO Has Otherwise Complied With the GPL.......................................................................
17
C. IBM's Proposed Interpretation of the GPL Would Impermissibly
Interfere With Enforcement of Intellectual Property Rights and Would Raise
Serious Antitrust Concerns...........................................................................
19
1. The GPL Should Not Be Read to Interfere With SCO's Right
To Enforce Its Own Intellectual Property Rights............................................................................
19
2. The GPL Should Not Be Read to Allow a Competitor to Regulate
What May Be Charged for an Intellectual Property License...................................................................................
19
D. The GPL Provides No Basis for IBM to Retroactively Seek
Forteiture of SCO's Right to Distribute GPL-Licensed Works..............................................................................................
21
III. IBM'S UNCLEAN HANDS PRECLUDE ITS MOTION........................................................................ 25
A. IBM's Misappropriation of UNIX Code....................................................................
26
B. IBM's Unauthorized Access Into SCO's Website.......................................................................
27
CONCLUSION...................................................................................... 28


TABLE OF AUTHORITIES

Cases Page(s)
Allegro Corp. v. Only New Age Music, Inc., No. Civ. 01-790-HU
  2003 WL 23571745 (D. Or. Jan. 23, 2003).........................................................
10, 11, 21
Amoco Oil Co. v. Premium Oil Co.,
  313 F. Supp. 2d 1233 (D. Utah 2004)...............................................................
12
AOL, Inc. v. LCGM, Inc.,
  46 F. Supp. 2d 444 (E.D. Va. 1998).......................................................................
27
Bak-A-Lum Corp. of Am. v. Alcoa Bldg. Prods., Inc.,
  351 A.2d 349 (N.J. 1976)....................................................................................
24
Berger v. Computer Info. Pub'g Inc., No. 84 Civ. 0331 (JFK)
  1984 WL 595 (S.D.N.Y. July 2, 1984).....................................................................
21
Board of Directors and Officers, Forbes Federal Credit Union v.
National Credit Union Administration,

  477 F.2d 777 (10th Cir. 1973)......................................................................
20
Concrete Machinery Co., Inc. v. Classic Lawn Ornaments, Inc.,
  843 F.2d 600 (1st Cir. 1988)..........................................................................
19
Creative Computing v. GetLoaded.com LLC,
  386 F.3d 1314 (9th Cir. 2004)..............................................................................
28
Dow Chemical Co.v. United States,
  226 F.3d 1334 (Fed. Cir. 2000)..............................................................................
13
Estate of Harris v. Harris,
  218 F.3d 1140 (10th Cir. 2000).................................................................................
15
First Nationwide Bank v. Florida Software Services, Inc.,
  770 F.Supp. 1537 (M.D. Fla. 1991)............................................................................
16
Fleming v. Miles,
  181 F.Supp. 2d 1143 (D. Or. 2001).................................................................
27
Ford v. United States,
  273 U.S. 593 (1927).......................................................................................
12
Foresight Res. Corp. v. Pfortmiller,
  719 F. Supp. 1006 (D. Kansas 1989)........................................................................
10
Fusion, Inc. v. Nebraska Aluminum Castings,
  962 F.Supp. 1392 (D. Kan. 1997).............................................................................
25
Galvin v. S. Hotel Corp.,
  154 F.2d 970 (4th Cir. 1946)...........................................................................
22
Gates Rubber Co. v. Bando Chem. Indus. Ltd.,
  9 F.3d 823 (10th Cir. 1993).................................................................................
10
Gemveto Jewelry Co., Inc. v. Lambert Bros. Inc.,
  542 F.Supp. 933 (D.C.N.Y. 1982)............................................................................
27
Grady v. de Ville Motor Hotel, Inc.,
  415 F.2d 449 (10th Cir. 1969)..............................................................................
19
Graham F. James,
  144 F.3d 229 (2d Cir. 1998)..................................................................
11, 21
Grundberg v. Upjohn Co.,
  140 F.R.D. 459 (D. Utah 1991)..............................................................
19, 26
Guthart v. White,
  263 F.3d 1099 (9th Cir. 2001)..............................................................
20
Hamilton Tailoring Co. v. Delta Air Lines, Inc.,
  1974 WL 21756 (S.D. Ohio 1974)....................................................................
23
Hasbro, Inc. v. Catalyst USA, Inc.,
  367 F.3d 689 (7th Cir. 2004)............................................................................
17, 22
Humphrey v. C.G. Jung Educ. Ctr. of Houston Tex.,
  714 F.2d 477 (5th Cir. 1983)........................................................................
22
I.M.S. Inquiry Mgmt. Sys., Ltd. v. Berkshire Info. Sys. Inc.,
  307 F.Supp. 521 (S.D.N.Y. 2004)...................................................................
27
In re Indep. Serv. Organization Antitrust Litig.,
  964 F.Supp. 1469 (D. Kan. 1997)......................................................................
10
Jacob Maxwell, Inc. v. Veeck,
  110 F.3d 749 (11th Cir. 1997).........................................................................
21
Jo-Ann, Inc. v. Alfin Fragrances, Inc.,
  731 F.Supp 149 (D.N..J. 1989)...........................................................................
23
Justine Realty Co. v. American Nat'l Can Co.,
  976 F.2d 385 (8th Cir. 1992)...............................................................................
19
Lantec Inc. v. Novell, Inc.,
  306 F.3d 1003 (10th Cir. 2002)..............................................................................
12
Lawser v. Poudre Sch. Dist.R-1,
  171 F.Supp. 2d 1155 (D. Colo. 2001).......................................................................
14
Lippo v. Mobil Oil Corp.,
  776 F.2d 706 (7th Cir. 1985).........................................................................
22
Looney v. Farmers Home Admin.,
  749 F.2d 310 (7th Cir. 1986).........................................................................
25
Machinery Co., Inc. v. Classic Lawn Ornaments, Inc.,
  843 F.2d 600 (1st Cir. 1988)..............................................................................
21
MCA Television, Ltd. v. Public Interest Corp.,
  171 F.3d 126 (11th Cir. 1999).............................................................................
21
Mendler v. Winterland Prod., Ltd.,
  207 F.3d 1119 (9th Cir. 2000)...............................................................................
16
Miller v. Glenn Miller Prods.,
  318 F. Supp. 2d 923 (C.D. Cal. 2004).................................................................
16
N.L.R.B. v. Local 32B-32J Service Employees Intern. Union,
  353 F.3d 197 (2d Cir. 2003)..............................................................................
20
NYNEX Corp. v. Discon, Inc.,
  525 U.S. 128 (1998)..........................................................................................
20
Precision Instrument Mfg. Co. v. Auto Maint. Mach. Co.,
  324 U.S. 806 (1945).........................................................................................
25
Queens Boulevard Wine & Liquor Corp. v. Blum,
  503 F.2d 202 (2d Cir. 1974).............................................................................
25
Quinn v. City of Detroit,
  23 F.Supp 2d 741 (E.D. Mich. 1998).....................................................................
23
Rano v. Sipa Press,
  987 F.2d 580 (9th Cir. 1993)..............................................................................
22
Rixon, Inc. v. Racal-Milgo, Inc.,
  551 F. Supp. 163 (D. Del. 1982).............................................................................
27
Russ Berrie & Co. v. Jerry Elsner Co.,
  482 F. Supp. 980 (S.D.N.Y. 1980)...........................................................................
27
RW Power Partners, L.P. v. Va. Elec. & Power Co.,
  899 F. Supp. 1490 (E.D. Va. 1995)..........................................................................
22, 25
SAS Institute, Inc. v. S & H Computer Systems, Inc.,
  605 F. Supp. 816 (M.D. Tenn. 1985)........................................................................
16
San Huan New Materials High Tech. Inc. v. International Trade Comm'n,
  161 F.3d 1347 (Fed. Cir. 1998)..................................................................................
19
Seneca-Cayuga Tribe of Oklahoma v. National Indian Gaming Com'n,
  327 F.3d 1019 (10th Cir. 2003)...........................................................................
12
Sony Corp. of Am. v. Universal City Studio, Inc.,
  464 U.S. 429 (1984)................................................................................................
21
Stenograph L.L.C. v. Bossard Assoc., Inc.,
  144 F.3d 96 (D.C. Cir. 1998)....................................................................................
11, 21
Tempo Music, Inc. v. Myers,
  407 F.2d 503 (4th Cir. 1969).....................................................................................
25, 26
United States v. Alpine Land & Reservoir Co.,
  291 F.3d 1062 (9th Cir. 2002).................................................................................
22
United States v. Socony-Vacuum Oil Co.,
  310 U.S. 150 (1940)......................................................................................
20
Worden & Co. v. Cal. Fig Syrup Co.,
  187 U.S. 516 (1903)................................................................................
26
Worthington v. Anderson,
  386 F.3d 1314 (10th Cir. 2004).....................................................................
26
Rules and Codes
Fed. R. Civ. P. 8(e)(2)......................................................... 14
The Computer Fraud Abuse Act, 18 U.S.C. § 1030(a)(2)(C)............................................ 27
UCC § 2-309(1)............................................................................. 23
UCC § 2-309(3)............................................................................. 23
Other Authorities
3 Nimmer on Copyright § 10.15[A].......................................................... 21
4 Nimmer on Copyright §13.09 (2004)............................................................. 27
4 Nimmer on Copyright §13.09[B]................................................................... 26
5 M. Kniffin, Corbin on Contracts §24.22 (Rev. ed. 1998)................................................... 17, 23
13 R. Lord, Williston on Contracts §32.11 (4th ed. 2000)...................................................... 17
18 Am. Jur. 2d Copyright §220............................................................................... 25
Restatement (2d) of Contracts § 227(1).............................................................. 17
Restatement (2d) of Contracts § 229...................................................... 25
Restatement (2d) of Contracts § 241 (1981)............................................... 25
E. Allan Farnsworth, Contracts §§ 8.12 (2d ed. 1990)........................................ 26
R. Epstein, Why Open Source Is Unsustainable, FT.com (Oct. 21, 2004).................................. 17
D. Kennedy, A Primer on Open Source Licensing Legal Issues: Copyright,
Copyleft and Copyfuture,
20 St. Louis U. Pub. L. Rev. 345 (2001)....................................................
17


The SCO Group, Inc. ("SCO") respectfully submits this Memorandum in Opposition to IBM's Motion for Partial Summary Judgment on IBM's Counterclaim for Copyright Infringement (the Eighth Counterclaim).

PRELIMINARY STATEMENT

IBM's Eighth Counterclaim and its motion for summary judgment on that counterclaim are thinly veiled attempts to try to retaliate against SCO for seeking to enforce its contractual and intellectual property rights with respect to UNIX.

IBM's motion puts at issue sixteen programs in Linux that IBM licensed for free use under the GNU General Public License and Lesser General Public License (collectively, the "GPL"). IBM thus made its allegedly copyrighted material freely available for SCO's (and others') copying and distribution. IBM concedes that the GPL would authorize SCO's use of the programs, but claims both that SCO has "repudiated" the GPL (and thus cannot invoke it) and that SCO breached the GPL (and thus immediately "forfeited" its authorization). IBM's arguments to limit the scope and applicability of that authorization fails on several grounds.

First, SCO has not "repudiated" (or "renounced") the GPL. There is no question that the GPL expressly authorized third parties, including SCO, to distribute IBM's allegedly copyrighted code. The argument IBM advances here, without citation to any authority, is that SCO has retroactively lost its authorization to copy the programs at issue by asserting certain affirmative defenses in this litigation. SCO's assertion of defenses regarding the enforceability of supposed GPL restrictions does not constitute a repudiation. SCO also states that "IBM's claims are barred by license" (that is, the GPL) and that SCO has acted "within the contractual rights granted to it concerning software made freely available by IBM under the GPL." There is no basis in fact or in law for the type of retroactive copyright liability that IBM seeks to impose.

Second, SCO has not "forfeited" (let alone immediately and without notice) its GPL copying rights by charging for its Intellectual Property License for Linux (the "UNIX License"), beginning in August 2003. IBM asserts that SCO has thereby "collected, and attempted to collect, royalties and licensing fees from Linux users in excess of the fees permitted by the GPL." IBM Mem. ¶ 66. But what IBM attacks are SCO's licenses for its UNIX rights and releases of potential claims for the infringement of those rights -- not licenses of Linux. Neither the GPL nor any other agreement gives IBM the right to dictate how much or how little SCO may charge for the use of its own intellectual property, or for the release of claims.

In addition to the factually incorrect bases for its motion, moreover, IBM misapprehends the language and operation of the GPL. Even if the facts of SCO's conduct were different:

  • Nothing in the GPL prohibits a licensee from imposing "further restrictions" on a third party's use of GPL-licensed material that the third party did not receive from that licensee. SCO has sold its license for UNIX software only to those who acquired a Linux operating system from someone other than SCO; and
  • The GPL does not prohibit a licensee from collecting a royalty or licensing fee on verbatim (as opposed to modified) copies of GPL-licensed material.

Indeed, IBM proposes an interpretation of the GPL that would substantially interfere with licensees' enforcement of their intellectual property rights, and that would implicate the antitrust laws by allowing competitors to agree as to the respective nature and amount they may charge for distribution of Linux, let alone for licensing of their own intellectual property.

SCO has complied with the GPL as a matter of law and therefore is entitled to invoke those provisions of the license that plainly entitled SCO to copy and use IBM's programs as it did. The foregoing grounds themselves warrant denial of IBM's motion for summary judgment. Moreover, as a matter of equity, IBM comes to the Court with unclean hands; IBM seeks to enforce its alleged copyrights having itself misappropriated SCO's proprietary source code, and having improperly hacked into SCO's website to obtain the very evidence that is the supposed basis for IBM's motion.

SCO's RESPONSE TO IBM's "STATEMENT OF UNDISPUTED FACTS"

1. SCO copied and distributed the Linux kernel and other related Linux software for years prior to 2003, when SCO discovered that IBM and others had misappropriated SCO's copyrighted UNIX code by contributing it to Linux without SCO's approval. Promptly after this discovery, SCO suspended all sales and marketing of its entire Linux product line. Declaration of Erik W. Hughes (11/30/04) ("Hughes Decl.") ¶3.

2. In light of the legal issues arising from the misappropriation, SCO began offering its Intellectual Property License for Linux (the "UNIX License") for sale beginning on August 5, 2003. Hughes Decl. ¶6. The UNIX License is a license of SCO's UNIX software, not a license or sublicense of Linux or of any IBM-copyrighted work. Declaration of Chris Sontag (11/30/04) ("Sontag Decl.") ¶30. SCO has never attempted to license or sublicense Linux or any IBM copyrighted work, or any other GPL-licensed code. Id. (SCO therefore disputes IBM Statement of Undisputed Facts ("IBM St.") ¶66.) None of the documents listed in paragraph 66 of IBM's "Statement of Undisputed Facts" represents an attempt to collect royalties or licensing fees for Linux or any IBM product:

a. SCO's May 2003 letters to Fortune 1000 companies (IBM Ex. 28) stated that SCO intended to protect and enforce its "UNIX intellectual property" and did not attempt to license Linux or any IBM work;

b. SCO's May 14, 2003 press release (IBM Ex. 29) warned that "SCO's own UNIX software code is being illegally copied into Linux" and did not attempt to license Linux or any IBM work;

c. SCO's July 21, 2003 press release (IBM Ex. 30) announced that SCO would soon be offering "UnixWare® licenses" for the specific purpose of resolving intellectual property issues arising from the unauthorized contributions of SCO's proprietary code into Linux, and nowhere in this release did SCO make any attempt to license Linux or any IBM work;

d. SCO's August 5, 2003 press release (IBM Ex. 31) announced the availability of the UNIX License, which permits "the use of SCO's intellectual property" in Linux distributions, and this release does not reflect any attempt by SCO to license Linux or any IBM work;

e. SCO's August 10, 2003 agreement with Computer Associates (IBM Ex. 32) granted a "license to use SCO UNIX rights" on a Linux operating system, and did not license Linux or any IBM work;

f. SCO's October 14, 2003 invoice to Leggett & Platt (IBM Ex. 33) for an "IP Compliance License" does not even mention Linux and did not license Linux or any IBM work;

g. SCO's December 19, 2003 agreement with Questar (IBM Ex. 34) granted a license to use "SCO IP rights" which were defined as SCO's UNIX rights and expressly excluded Linux, and did not license Linux or any IBM product;

h. SCO's December 22, 2003 press release (IBM Ex. 35) announced "new initiatives to enforce and protect the company's intellectual property rights," and this release does not reflect any attempt by SCO to license Linux or any IBM product;

i. SCO's December 19, 2003 template letter (IBM Ex. 36) restated SCO's belief that SCO's proprietary code had been illegally copied into Linux, and this release does not reflect any attempt by SCO to license Linux or any IBM product;

j. SCO's January 16, 2004 letter to Lehman Brothers Holdings (IBM Ex. 37) stated that legal action would be considered unless Lehman purchased a UNIX license, and this letter does not reflect any attempt by SCO to license Linux or any IBM product.

k. SCO's March 1, 2004 agreement with Everyones Internet (IBM Ex. 38) granted a license to use SCO's proprietary UNIX code, and did not grant a license for Linux or any IBM product;

l. SCO's March 3, 2004 suit against AutoZone (IBM Ex. 39) alleges infringement of SCO's UNIX copyrights and does not reflect any attempt by SCO to license Linux or any IBM product;

m. In August 2004, SCO contemplated raising the price of its UNIX License (as noted in IBM Ex. 40), and SCO did not attempt to license Linux or any IBM product;

n. SCO's SCOSource division sells the UNIX License (as indicated in IBM Ex. 41), and neither this division nor any other part of SCO has ever attempted to license Linux or any IBM product.

3. SCO determined to offer its UNIX License, beginnning in August 2003, only because IBM had misappropriated SCO's proprietary source code and contributed hundreds of thousands of lines of that code into Linux. Hughes Decl. ¶6.

4. All sixteen of IBM's allegedly copyrighted programs at issue in this motion were licensed to SCO under the GPL. IBM Mem. at 12 ¶61.

5. Under the GPL, a licensee may charge a fee for its distribution of GPL-licensed software. GPL Preamble ¶¶2, 4; GPL ¶1. Indeed, companies such as Red Hat and SuSe built businesses based on the sale and service of Linux-based software. Red Hat's founder Robert Young, for example, has stated that "many people prefer to purchase Official Red Hat Linux in a box for $50 when they could download it for free or buy unofficial CD-ROM copies of Red Hat for as little as $2." Robert Young Interview, http://www.press.umich.edu/jep/04-03/young.html.

6. Section 1 of the GPL authorizes the general public to copy and distribute verbatim copies of the source code of the licensed program, subject to certain notice publication requirements. GPL §1. SCO complied with all of these requirements in all of its Linux distributions. Hughes Decl. ¶9. IBM does not contend otherwise.

7. Section 3 of the GPL authorizes the general public to copy and distribute verbatim copies of the licensed program in object code or executable form, subject to the condition that it be accompanied by the source code or by an offer to provide the source code. GPL §3. SCO complied with these conditions in all of its Linux distributions. Hughes Decl. ¶9. IBM does not contend otherwise.

8. Section 3 of the GPL does not prohibit a licensee from charging "royalty or licensing fees" on the licensed works. Section 3 does not even mention fees or royalties at all. GPL §3. (SCO therefore denies IBM St. ¶65.)

9. Section 2 states that, if a licensee modifies the licensed work, the modified work must be licensed at no charge. GPL§ 2. IBM does not allege that SCO modified any of the sixteen subject works; IBM relies on SCO's verbatim copying of these works. IBM Mem. at 6-12, 19; Declaration of Kathleen Bennett ("Bennett Decl.") ¶¶9, 11. In fact, SCO never modified any of these works. Sontag Decl. ¶31. In contrast to section 2 (which authorizes the copying of modified works), section 1 (which authorizes verbatim copying) does not require no-charge licensing.

10. In addition, even though the GPL would not have prohibited SCO from doing so, SCO has not sought to collect royalties or licensing fees for any of IBM's allegedly copyrighted works. Hughes Decl. ¶9; Sontag Decl. ¶30.

11. IBM has also claimed that, in violation of section 6 of the GPL, SCO has imposed "further restrictions" on a third party's use of licensed material. However, section 6 refers exclusively to situations where the third party has received the GPL-licensed material from the licensee. SCO has not attempted to sell the UNIX License to anyone who received a Linux distribution from SCO. Hughes Decl. ¶8. (SCO therefore disputes IBM St. ¶64.)

12. The GPL says that a licensee's use of licensed material beyond the scope of the License will "automatically terminate" the licensee's rights under the License, but it does not say when such termination becomes effective, and it provides no mechanism by which the licensee is put on notice of an alleged unauthorized use of the licensed material. GPL §4. (SCO therefore disputes IBM St. ¶63.)

13. Fifteen of the sixteen alleged IBM programs at issue in this motion were included verbatim in SCO Linux Server 4.0. The remaining one (the omni print driver) was included verbatim in the Asia CD of SCO Open Linux 3.1.1. IBM Mem. at 5, 6-12, 19-20. IBM alleges that SCO thereafter "forfeited" its GPL rights by attempting to sell the UNIX License, and that SCO infringed its copyrights by (1) distributing SCO Linux Server 4.0, IBM Mem. at 5 ¶26, and (2) making SCO Linux Server 4.0 and SCO Open Linux 3.1.1 available for public download via the internet. Id. at 5-12 ¶¶27-60.

14. SCO distributed SCO Linux Server 4.0 for only a few months, from November 19, 2002, until May 14, 2003. Hughes Decl. ¶¶2-3. A few months after determining that Linux was tainted with misappropriated SCO code, SCO suspended its sales of Linux products pending clarification of the intellectual property issues. Hughes Decl. ¶3. After May 14, 2003, SCO entered into no further obligations to sell SCO Linux Server 4.0 or any other Linux product. Id. SCO made limited post-May 14 sales to customers in consideration of its obligations to its customers. Id. ¶¶3-5; Sontag Decl. ¶¶12-14. The last sale of Linux Server 4.0 was on May 31, 2004. Hughes Decl. ¶4. (SCO therefore disputes IBM St. ¶26.) All of SCO's Linux distributions (both prior to and after May 2003) were made under the GPL, with no charge of any nature for royalties or licensing fees. Hughes Decl. ¶9.

15. In accordance with its obligations, SCO continued to provide its Linux customers with internet access to files containing Linux source code and enhancements thereto. SCO stored these files on its computers, which its customers could access via the internet. In accordance with its agreement with the UnitedLinux consortium, SCO provided customers who purchased SCO Linux Server 4.0 with a password to enter at a log-in screen on SCO's download site so that only they would have access. Sontag Decl. ¶17-19. (Password protection was in place for three of the four URLs listed in the declaration of Kathleen Bennett that IBM submits in support of its motion; the remaining URL was for OpenLinux files and did not provide access to any files for SCO Linux Server 4.0. Id. ¶29.) The only way a non-customer could access the Linux Server 4.0 code was to bypass the password-protected security system by hacking into the system. Id. ¶¶20-21. In addition, the download site contained an explicit notice that access to the Linux Server 4.0 files was limited to SCO customers. Id. ¶28.

16. Between October 31 and December 1, 2003, IBM repeatedly accessed the SCO log-in site but did not obtain access to the SCO Linux Server 4.0 files. Id. ¶25. After news of a bug in the SCO site's security system was reported on internet websites, IBM exploited the bug to bypass the security system, hack into SCO's website, and download the very files IBM has now attached to this motion. Id. ¶¶22-27 (SCO therefore disputes IBM St. ¶27.)

17. The files that IBM hacked remained on SCO's website after August 5, 2003, because of SCO's pre-existing contractual obligations with its customers and with the UnitedLinux consortium. Sontag Decl. ¶17-19. Under the GPL, each time SCO distributed a copy of IBM's purported works in executable form, SCO was to provide the customer "with the complete corresponding machine-readable source code" on a "medium customarily used for software interchange" or with an offer to provide the code at cost. GPL §3. SCO complied by making the source code available to its customers on its website. SCO will remove all Linux-related code from its website promptly after expiration of the last of its contractual commitments, on December 31, 2004. Hughes Decl. ¶11; Sontag Decl. ¶17. SCO's "distribution" of any Linux products, even in this limited fashion, will cease by the end of 2004. Id.

18. Prior to the filing of its Second Amended Counterclaim on March 29, 2004, IBM never provided SCO with any notice of its claim that SCO's rights under the GPL had terminated or that SCO was infringing its copyrights. Hughes Decl. ¶12.

19. SCO never repudiated the GPL, and it always endeavored to comply with its GPL obligations. Hughes Decl. ¶9; IBM Ex. 23 (Sontag Deposition) at 213:21-214:1.

20. IBM contributed at least one of the sixteen subject programs to Linux in violation of its contractual obligations to SCO, Declaration of Michael Davidson (11/22/04) ("Davidson Decl.") ¶¶10-52 (submitted with SCO's Memorandum in Opposition to IBM's Motion for Summary Judgment on SCO's Contract Claims (Nov. 30, 2004)), and (as detailed above) it supports this motion with documents obtained through unauthorized access into SCO's website. Sontag Decl. ¶¶18-27.

21. IBM St. ¶¶1-4 repeats IBM's erroneous statements on the history of Linux from its earlier briefs. SCO disputes each of these statements based on the evidence and reasons set forth in its Memorandum in Opposition to IBM's Motion for Summary Judgment on its Tenth Counterclaim for Declaratory Judgment of Non-Infringement ¶¶8-14.

22. SCO disputes IBM St. ¶8 and all other statements to the extent they refer to "IBM Copyrighted Works" or suggest that the sixteen subject works are owned by IBM or that IBM's copyrights are valid, because IBM may have misappropriated some or all of these works in violation of its agreements with SCO and, in any event, IBM may have assigned these works or failed to register them properly. SCO is conducting discovery on these issues.1

ARGUMENT

In order to prevail on its counterclaim, IBM bears the burden of proving that SCO violated the Copyright Act. See Allegro Corp. v. Only New Age Music, Inc., No. Civ. 01-790-HU, 2003 WL 23571745, at *10 (D. Or. Jan. 23, 2003) (Exh. A); Indep. Serv. Orgs. Antitrust Litig., 964 F. Supp. 1469, 1472 (D. Kan. 1997). This requires proof that SCO's actions were unauthorized. See Gates Rubber Co. v. Bando Chem. Indus., Ltd., 9 F.3d 823, 832 (10th Cir. 1993) ("Once the plaintiff has shown that it holds a valid copyright, it must next prove that the defendant unlawfully appropriated protected portions of the copyrighted work." (emphasis added)); Foresight Res. Corp. v. Pfortmiller, 719 F. Supp. 1006, 1011 (D. Kan. 1989) ("In general, a prima facie case of copyright infringement consists of proof that the plaintiff owns a valid copyright and the defendant has engaged in unauthorized copying.").

Given SCO's undisputed reliance on the GPL, IBM bears the burden of proving that SCO violated the license. See Allegro, 2003 WL 23571745, at *10 ("To prevail on their counterclaim of copyright infringement under a license, defendants must prove 1) ownership of copyright, and 2) 'copying' of protectible expression beyond the scope of the license."); see also Graham v. James, 144 F.3d 229, 236 (2d Cir. 1998) (noting that "the copyright owner bears the burden of proving that the defendant's copying was unauthorized under the license"); Stenograph L.L.C. v. Bossard Assocs., Inc., 144 F.3d 96, 99 (D.C. Cir. 1998) (explaining copyright plaintiff must prove defendant's copying of protected expression exceeded scope of "the license possessed by the defendant").

I. THE GPL AUTHORIZED SCO TO DISTRIBUTE LINUX, INCLUDING ANY
CONTRIBUTIONS MADE BY IBM OF COPYRIGHTED MATERIAL

Although in certain respects "the language of the GPL is opaque and it contains many ambiguities," Radcliffe, SCO v. IBM Part Deux, http://www.alwayson-network.com/comments, it clearly grants the public at large "freedom to distribute copies" of the licensed software and to "charge for this service if you wish". GPL Preamble ¶2. Section 1 of the GPL authorizes the public to "copy and distribute verbatim copies" of source code licensed thereunder, subject only to certain notice publication requirements. GPL §1. SCO complied with these requirements, Hughes Decl. ¶9, and thus was entitled to copy any material IBM licensed under the GPL.

Section 1 also permits the charging of fees for transfer of the software and for warranty protection. IBM appears to contend that the GPL's express grant of the permission to charge transfer and warranty fees should be read as a prohibition of all other types of fees. It is well established that this type of reasoning is unreliable and even "dangerous" in the construction of contracts and statutes. Ford v. United States, 273 U.S. 593, 612 (1927); Seneca-Cayuga Tribe of Okla. v. Nat'l Indian Gaming Comm'n, 327 F.3d 1019, 1034-35 & n.26 (10th Cir. 2003). Section 2(b), which prohibits licensing fees where the licensee distributed modified works, shows that the drafters knew how to write a fee prohibition where such as intended.

The GPL also authorizes a party to copy and distribute the licensed works verbatim in object code or executable form under the terms of section 1, as long as the party accompanies it with the source code or with an offer to provide the source code. GPL §3. It is undisputed that SCO complied fully with this condition. Hughes Decl. ¶9. GPL section 3 allows a licensee to comply by "offering access to copy from a designated place" (such as an internet site).

SCO complied with all of the GPL's requirements and therefore was authorized to distribute all sixteen of the works allegedly copyrighted by IBM that IBM contributed to Linux.

II. SCO DID NOT REPUDIATE OR BREACH THE GPL

IBM asserts that SCO "forfeited" its rights under the GPL by "repudiating" and "breaching" the GPL. IBM is wrong on both these points as a matter of law.

A. SCO Did Not "Repudiate" the GPL

IBM contends (without citations) that SCO was not authorized to copy and distribute IBM's allegedly copyrighted material because, IBM contends, SCO has since "repudiated" the GPL. SCO has not "repudiated" the GPL.

"A repudiation occurs when a party to a contract makes an overt communication of intention or an action which renders performance impossible or demonstrates a clear determination not to continue with performance." Amoco Oil Co. v. Premium Oil Co., 313 F. Supp. 2d 1233, 1238 (D. Utah 2004) (quotations and citation omitted); see also Lantec Inc. v. Novell, Inc., 306 F.3d 1003, 1014-15 (10th Cir. 2002). Put another way, a party "repudiates" a contract when it "refuses to perform and communicates that refusal distinctly and unqualifiedly to the other party." Dow Chem. Co. v. United States, 226 F.3d 1334, 1344 (Fed. Cir. 2000). IBM does not even allege that SCO made any such refusal, far less communicated any such refusal to anyone. In fact, in the very materials IBM cites, SCO Vice President Christopher Sontag confirms that, with respect to the GPL, SCO "treated it as an obligation for which it needed to abide by," and SCO "made our best efforts to abide by all of the obligations of the GPL agreement." IBM Ex. 23 at 213:21-214:1. On this basis alone, IBM's "repudiation" argument fails.

IBM also misapprehends the significance of the assertions SCO has made in its pleadings regarding the enforceability of the GPL. IBM ignores those assertions that directly contradict its characterization of SCO's supposed 'repudiation': SCO asserts as its Fourth Affirmative Defense that "IBM's claims are barred by license" (IBM's 2d Am. Countercl. at 19 (emphasis added)), and as its Eleventh Affirmative Defense that "SCO has acted legally and properly at all relevant times and IBM is therefore barred from any relief whatsoever" (id. at 20 (emphasis added)). In a portion of SCO's Response to IBM's Third Set of Interrogatories that IBM does not cite, SCO explains that it has acted "within the contractual rights granted to it concerning software made freely available by IBM under the GPL." Plaintiff SCO's Response to IBM's Third Set of Interrogatories at 20 (Apr. 19, 2004). SCO thus has not remotely stated that any licensee who relies on the GPL is liable for copyright infringement.

IBM also ignores the context in which SCO has made its forward-looking assertions regarding the enforceability of the GPL. In its Seventh Counterclaim, IBM asserts a state law claim for breach of contract based on the GPL. In response, SCO asserted the following affirmative defenses:

  • "The GPL is selectively enforced by the Free Software Foundation such taht enforcement of the GPL by IBM or others is waived, estopped or otherwise barred as a matter of equity." SCO's Am. Answer to IBM's Am. Countercl. at 16 (Mar. 11, 2004); accord SCO's Answer to IBM's 2d Am. Countercl. at 20 (Apr. 23, 2004); Plaintiff SCO's Response to IBM's Third Set of Interrogatories at 39; and

  • "The General Public License ('GPL') is unenforceable, void and/or voidable, and IBM's claims based thereon, or related thereto, are barred." SCO's Answer to IBM's 2d Am. Countercl. at 20; accord Plaintiff SCO's Response to IBM's Third Set of Interrogatories at 38.

In addition, in response to IBM's claim for "Breach of the GNU General Public License" (IBM's 2d Am. Countercl. at 33), SCO "denies the applicability or enforceability of the GPL" (SCO's Answer to IBM's 2d Am. Countercl. at 16). Indeed, SCO submits that the interpretation of the GPL that IBM proposes in its instant motion is unenforceable for several reasons. But SCO has not asserted, either literally or in the context of its responsive pleadings, that the GPL did not authorize the licensees thereunder to copy and distribute the licensed material. Such defensive assertions in litigation do not remotely qualify as a party's decision to "repudiate" the contract at issue. In sum, none of SCO's assertions could reasonably be construed to preclude SCO from arguing (and proving) that, under the GPL, SCO was authorized to copy and distribute the material at issue.

IBM's argument would fail, moreover, even if the Court accepted IBM's mischaracterization of SCO's assertions. IBM at most points to instances of permissible pleading in the alternative. See Fed. R. Civ. P.8(e)(2); see, e.g., Lawser v. Poudre Sch. Dist., 171 F.Supp.2d 1155, 1158 (D. Colo. 2001)(Rule 8(e)(2) "specifically provides that a party may plead in the alternative, even where the alternative claims are inconsistent"). Nor has IBM even claimed that it changed its position or relied on any of SCO's statements. See Estate of Harris v. Harris, 218 F.3d 1140, 1153 (10th Cir. 2000).

B. SCO's Licensing Activities Did Not Violate the GPL

IBM contends that SCO immediately, and without notice from anyone, "forfeited" its GPL rights by attempting to "license Linux." In fact SCO has never sought to license Linux (or any IBM program contained therein). In addition, regardless of how SCO's UNIX License is characterized, the sale of this claims-settlement license did not breach the GPL.

1. SCO Has Been Collecting Licensing Fees Only for Its Own Code.

SCO has not sought any fees or royalties for any material legitimately licensed under the GPL. The product to which IBM objects is SCO's UNIX License, which is a license and release that SCO has entered into with third parties to authorize use of UNIX and to release such parties from any potential liability arising from the unauthorized use of UNIX in a Linux operating system. That SCO's action is directed at protecting its UNIX rights is reflected in the legal actions, press releases, and letters about which IBM complains. IBM Br. ¶¶66(a)-(d), (h)-(j),(l)-(n). IBM may not approve of such activities, but they do not constitute a Linux "license fee or royalty." IBM points to nothing in the GPL -- and there is nothing -- that expressly or impliedly forbids actions aimed at enforcing a party's intellectual property rights.

IBM claims that SCO has sold Linux licenses to several companies. IBM Br. ¶¶66(e)-(g), (k). What IBM refers to is SCO's charging licensing fees for the use of its own UNIX software, by non-SCO customers. Sontag Decl. ¶30. IBM also omits to mention that the agreements contain releases of claims because they settle SCO's potential legal claims against the licensee. Id. The licenses include a covenant not to sue and a waiver of any copyright infringement claims that SCO might have against the licensee. Id.

IBM has wrongly claimed, for example, that SCO has sold a Linux license to Leggett & Platt, even though IBM's Exhibit 33, an invoice for the license in question, does not contain the word Linux anywhere in the document. IBM also points to the license that SCO sold to Questar, but that is only a license granting Questar permission "to use SCO IP Rights" for business purposes in connection with the use of a Linux operating system. That license (IBM Ex. 34 ¶2.1) defines "SCO IP Rights" as "SCO's intellectual property rights in any and all past, current or future versions or portions of the SCO's software products commonly known as UNIX System V and/or UnixWare" concurrent with run-time use of Linux. Id.¶1.11. The definition explicitly excludes Linux from its scope: "Except as expressly provided herein, SCO IP Rights shall not include any right to copy, distribute, modify or alter Linux Software." Id. ¶1.11.

The licensing clauses of all of the UNIX Licenses are worded similarly. Sontag Decl. ¶30. SCO has not attempted to "license Linux" or to collect Linux or IBM-program "royalties and licensing fees." Hughes Decl.¶3. Thus, IBM's contention that SCO breached the GPL fails because its underlying premise -- that SCO is licensing Linux -- is incorrect.

2. SCO Has Otherwise Complied with the GPL.

SCO did not breach the GPL by selling its UNIX license. The Court is to interpret a copyright license agreement in accordance with general principles of contract construction. See Miller v. Glenn Miller Prods., 318 F.Supp. 2d 923, 934 (C.D.Cal. 2004)("Courts apply general principles of contract interpretation when interpreting the terms and scope of a licensing agreement."); Mendler v. Winterland Prod., Ltd., 207 F.3d 1119, 1121 (9th Cir. 2000) (applying such principles in interpretation of copyright license). A copyright license includes implied covenants of good faith and fair dealing. First Nationwide Bank v. Fla. Software Servs., Inc., 770 F. Supp. 1537, 1542 (M.D. Fla. 1991); SAS Inst., Inc. v. S & H Computer Sys., Inc., 605 F. Supp. 816, 827-28 (M.D. Tenn. 1985). Under well-established doctrine, the Court should construe the agreement to avoid a harsh or unreasonable result, or a forfeiture. 5 M. Kniffin, Corbin on Contracts §24.22 (Rev. Ed. 1998) ("Corbin"); 13 R. Lord, Williston on Contracts §32.11(4th ed. 2000); Restatement (2d) of Contracts v227(1) ("Restatement of Contracts"). When the terms of a contract are "indefinite, uncertain and susceptible of two constructions," the "contract should be construed as not creating a forfeiture." Hasbro, Inc. v. Catalyst USA, Inc., 367 F.3d 689, 693 (7th Cir. 2004).

In arguing that SCO breached the GPL, IBM relies on GPL section 2, which states that, if a licensee modifies the licensed work, the modified work must be "licensed at no charge." GPL §2(b). IBM does not even allege that SCO modified any of the programs; rather IBM stresses that SCO copied the works verbatim. IBM Mem. at 6-12, 19; Bennett Decl. ¶¶9, 11. In fact SCO never modified any of these works. Sontag Decl. ¶31. In contrast to section 2 (which authorizes the copying of modified works), the GPL's section 1 (which authorizes verbatim copying) does not expressly require no-charge licensing.2 Even where (unlike here) section 2 does apply, the GPL disclaims any intent to "claim rights or contest your rights to work written entirely by you." GPL §2. Section 2 is inapplicable here, and it does not preclude SCO from enforcing its rights to UNIX. (In addition, the "at no charge" clause of section 2 is illegal and thus unenforceable. See Part II.C.2, below.)

IBM also contends that SCO has violated section 6 by imposing "further restrictions" by "collecting royalties or licensing fees" for Linux. IBM Mem. at 13, 22. IBM's argument fails for several independently sufficient reasons. Section 6 states:

"Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein."

Section 6 thus applies only to restrictions placed by the licensee on third parties to whom the licensee has distributed the GPL-licensed program.

IBM repeatedly quotes the second part of section 6 without quoting the first part, which says that section 6 applies "Each time you redistribute the Program." The section discusses the license that "the recipient" receives, and provides that the licensee "may not impose any further restrictions on the recipients' exercise of the rights granted herein." SCO has never attempted to collect licensing or royalty fees from anyone who received a Linux distribution from SCO, Hughes Decl. ¶8; Sontag Decl. ¶30, and IBM does not even purport to present any evidence to the contrary. SCO sold a UNIX License only to those who acquired a Linux operating system from another source. Hughes Decl. ¶¶8-9. SCO did not breach section 6.

Nor has SCO breached section 4 of the GPL, which states: "You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License." To the extent there is no breach of other sections of the GPL, such as Section 2 or 6, as argued above, there is no breach of Section 4, because SCO's distributions of IBM's programs were "as expressly provided under this License." Hughes Decl. ¶9. Moreover, Section 4 only deals with copying and distribution of GPL-licensed works; it does not and cannot be read to constitute an agreement by a licensee to refrain from charging for other products in which it holds a proprietary interest or to desist from enforcement of its intellectual property or contractual rights.

C. IBM's Proposed Interpretation of the GPL Would Impermissably
Interfere with Enforcement of Intellectual Property Rights and
Would Raise Serious Antitrust Concerns

1. The GPL Should Not Be Read to Interfere with SCO's
Right to Enforce Its Own Intellectual Property Rights

The above arguments easily suffice to resolve the pending motions, but there are additional reasons why IBM's position must be rejected. Nothing in the GPL expressly forbids a party from licensing its own software or entering into settlements to resolve potential infringement of such rights. Any construction of the GPL to do so should be rejected as inconsistent with the public policy in favor of protecting intellectual property, San Juan New Materials High Tech Inc. v. Int'l Trade Comm'n., 161 F.3d 1347, 1363 (Fed. Cir. 1998); Concrete Mach. Co., Inc. v. Classic Lawn Ornaments, Inc., 843 F.2d 600, 612 (1st Cir. 1988), as well as the public policy favoring and encouraging settlements. Grady v. de Ville Motor Hotel, 415 F.2d 449, 451 (10th Cir. 1969); Grundberg v. Upjohn Co., 140 F.R.D. 459, 468 (D. Utah 1991); see also Justine Realty Co. v. Am. Nat'l Can Co., 976 F.2d 385, 391 (8th Cir. 1992).

2. The GPL Should Not Be Read to Allow a Competitor to Regulate
What May Be Charged for an Intellectual Property License

By arguing that SCO breached the GPL by collecting "royalties and licensing fees in excess of the fees permitted by the GPL," IBM Mem. at 14, IBM seeks in essence an interpretation that the GPL fixes limits on the amounts that may be charged for unmodified works, even though the parties to the agreement are competitors. Agreements between competitors that fix a maximum price that may be charged for products are per se illegal under antitrust law. NYNEX Corp. v. Discon, Inc., 525 U.S. 128, 133 (1998); United States v. Socony-Vacuum Oil Co., 310 U.S. 150, 218 (1940).

While SCO has shown above that section 2 of the GPL (the only GPL provision requiring licensing "at no charge") is inapplicable here, because this motion does not involve modified works, this provision is illegal and unenforceable. The general counsel for the Open Source Initiative acknowledges in his recent treatise: "There is also a problem that may prevent enforcement of the GPL's at no charge provision. It may be an illegal restraint of trade in some countries. Ordinarily, companies are allowed to set their own prices, and it is improper for a GPL licensor to restrain that in any way." L. Rosen, Open Source Licensing 132 (2004), available at http://www.phptr.com/content/images/0131487876_ch06.pdf.

It is a "well settled principle that where a contract is susceptible of two interpretations, preference will be given to the interpretation which does not violate the law." Bd. of Dirs. and Officers, Forbes Fed. Credit Union v. Nat'l Credit Union Admin., 477 F.2d 777, 784 (10th Cir.1973); accord NLRB v. Local 32B-32J Serv. Employees Int'l Union, 353 F.3d 197, 202 (2d Cir. 2003); Guthart v. White, 263 F.3d 1099, 1104 (9th Cir. 2001). Accordingly, the Court should not construe the GPL as IBM suggests.

D. The GPL Provides No Basis for IBM to Retroactively
Seek Forfeiture of SCO's Right to Distribute GPL-Licensed Works

There is an additional flaw in IBM's position: a determination today that SCO has "repudiated" or breached the GPL does not serve as a basis upon which retroactively to declare SCO's actions to constitute an infringement of copyright. IBM's burden is to prove that, at the time SCO copied and distributed IBM's allegedly copyrighted work, SCO was not authorized to do so. See Allegro, 2003 WL 23571745, at *10 (counterclaim-plaintiff must prove copying "beyond the scope of the license."); Graham, 144 F.3d at 236 (alleged copyright owner must prove that the "copying was unauthorized under the license"); Stenograph, 144 F.3d at 99 (explaining copyright plaintiff must prove defendant's copying of protected expression exceeded scope of "the license possessed by the defendant"); Berger v. Computer Info. Pub'g, Inc., No. 84 Civ. 0331 (JFK), 1984 WL 595, at *2 (S.D.N.Y. July 2, 1984) (Exh.B) (action for copyright infringement lies "once a licensing contract expires," and not for conduct when the authorization "was still in effect"). That is, "anyone who is authorized by the copyright owner to use the copyrighted work in a way specified in the [Copyright Act] or who makes a fair use of the work is not an infringer of the copyright with respect to such use." Sony Corp. of Am. v. Universal City Studio, Inc., 464 U.S. 429, 433 (1984) (emphasis added).

The copyright cases expressly discussing the issue have rejected the "retroactive infringement" argument IBM advances herre. In MCA Television, Ltd. v. Public Interest Corp.., 171 F.3d 1265 (11th Cir. 1999), for example, the court explained:

The notion that MCA had the power retroactively to rescind the contract makes a mockery of that contractual agreement and would put any contracting party in PIC's position in terror of upsetting the licensor in any way for fear of being declared in breach, having the contracted-for licenses "retroactively revoked," and being sued both for breach of contract and in copyright for statutory damages that can far outweigh contractually negotiated licensing fees.

Id at 1274 n. 8; see also Jacob Maxwell, Inc. v. Veeck, 110 F. 3d 749, 753 (11th Cir. 1997) (holding that one party's breach does not automatically rescind a contract simply because that breach might give the other party the right to rescind); 3 Melvin B. Nimmer, Nimmer on Copyright §10.15[A] at 10-120(2004) ("[T]he license is terminated and the copyright proprietor may hold his former grantee liable as an infringer for subsequent use of the work. Failing such rescission . . . the grant continues in place . . . until such time as the copyright owner exercises his entitlement to rescind.").

This is consistent with the law's general disfavor of a forfeiture. United States v. Alpine Land & Reservoir Co., 291 F.3d 1062, 1077 (9th Cir. 2002). The rule across jurisdictions is that "when the terms of a contract are, or, by any act of parties under the contract, become indefinite, uncertain and susceptible of two constructions, and by giving them one construction one of the parties would be subject to forfeiture, and by giving them the other no such forfeiture would be incurred and no injustice would be done to the other party, the contract should be construed as not creating a forfeiture." Hasbro, Inc. v. Catalyst USA, Inc., 367 F.3d 689, 693 (7th Cir. 2004). 3 A court will not deem a party to a contract to have "forfeited" its rights thereunder unless the contractual language at issue gave the party clear notice of the potential bases for such forfeiture. See, e.g., RW Power Partners, L.P. v. Va. Elec. & Power Co., 899 F.Supp. 1490, 1502-03 (E.D. Va. 1995) (declaring electric utility improperly terminated purchase agreement because forfeiture provisions, which permitted termination upon supplier's failure "to perform any of the obligations pursuant to this Agreement," did not "clearly state" that supplier's non-material breach would trigger forfeiture rights); see also Humphrey v. C.G.Jung Educ. Ctr. of Houston Tex., 714 F.2d 477, 480 (5th Cir. 1983) ("Forfeitures clauses fail in the event they are ambiguously expressed.").

The GPL says that a licensee's use of licensed material beyond the scope of the License will "automatically terminate" the licensee's rights under the License, but does not say when such a termination becomes effective. In the absence of any such provision, and in light of the governing interpretive standards (cited above), the only reasonable interpretation of the GPL is one which permits the licensee a reasonable time to wind down its activities based on the use of the licensed material. Cf. UCC §2-309(1) (if no time period specified in contract, a reasonable time is implied); Jo-Ann, Inc. v. Alfin Fragrances731 F.Supp. 149, 160 (D.N.J. 1989) (terminated party must be given time "to make alternate arrangements or close its affairs in an economically proper manner"); Hamilton Tailoring Co. v. Delta Air Lines, Inc., 1974 WL 21756, 14 UCC Rep. Serv. 1310 (S.D. Ohio 1074) (Exh. C) (manufacturer must be allowed reasonable time to sell off inventory before termination became effective).

In Quinn v. City of Detroit, 23 F. Supp. 2d 741, 750 (E.D. Mich. 1998), for example, the court specifically rejected the licensor's argument that his revocation of the software license had immediate effect. The software at issue enabled the city-licensee to track ongoing cases. The court ruled that, without a transitional period to acquire and set up a replacement system, ''the City would have been left helpless, with no way to update cases or access information in the manner necessary to properly monitor cases.'' Id. Therefore, with respect to ''any agreement where hardship would result if sudden, immediate termination occurred,'' a reasonable time for transition is required. Id.

The transition period would begin, moreover, only when the licensee knew or had received notice of its alleged breach of the license agreement. See Corbin §24.22 (endorsing judicial precedent acknowledging ''public policy'' against forfeiture and construing a lease provision giving the landlord a termination right if the tenant breached to require notice and an opportunity for cure before the forfeiture would be effective); cf. UCC §2-309(3), comment 8 (good faith calls for ''such notification of the termination of a going contract relationship as will give the other party reasonable time to seek a substitute arrangement"); see also Bak-A-Lum Corp. of Am. v. Alcoa Bldg. Prods., 351 A.2d 349, 352 (N.J. 1976) (holding that a reasonable period of notice of termination of the distributorship, under all the circumstances, would have been twenty months). THe GPL provides no mechanism by which the licensee is put on notice of an alleged unauthorized use of the licensed material.

In this case, given the absence of any such provision in the GPL, SCO did not receive ''notice'' from IBM that it had alIegedly breached the GPL until IBM filed its Eighth Counterclaim, on March 29, 2004. IBM thus not only asks the Court to conclude that SCO forfeited its rights to copy and distribute IBM's allegedly copyrighted material, but also asks the Court to declare retroactively that SCO was obligated immediately to terminate that portion of its business that relates to the copying and distribution of material licensed under the GPL, upon SCO's supposed breach of the GPL of which IBM gave SCO no notice. SCO submits that, under the foregoing standards, no such ''forfeiture'' could apply.

Here, retroactive determinations are sought by IBM because SCO suspended its Linux distribution activities months before it began selling the UNIX License to allow parties to make use of SCO's UNIX intellectual property in connection with their use of Linux, and months before IBM registered any of the sixteen alleged copyrights. IBM Memo. at 3 ¶8. The few SCO Linux Server 4.0 sales thereafter (all based on what SCO believed to be obligations under pre-existing contracts) ceased six months ago: SCO's last sale of Linux Server 4.0 was on May 31, 2004, just two months after IBM filed its Eighth Counterclaim. Hughes Decl. ¶4. All Linux code will be taken off SCO's password-protected website at the end of 2004. Id. ¶11; Sontag Decl. ¶17. These actions were taken not because SCO is infringing any of IBM's copyright rights, but instead because of IBM's actions in violating SCO's proprietary rights through IBM's Linux activities. IBM's theory of retroactive infringement fails as a matter of law.4

III. IBM'S UNCLEAN HANDS PRECLUDE ITS MOTION

IBM's motion also fails for IBM's ''unclean hands.'' As a general matter, the doctrine ''closes the doors of a court of equity to one tainted with inequitableness or bad faith relative to the matter in which he seeks relief, however, improper may have been the behavior of the defendant.'' Precision Instrument Mfg. Co. v. Auto. Maint. Mach. Co., 324 U.S. 806, 814 (1945). The doctrine applies in the copyright context when the ''plaintiff's transgression is of serious proportions and relates directly to the subject matter of the infringement action.'' Tempo Music, Inc. v. Myers, 407 F2d 503, 507 & n.8 (4th Cir. 1969); see also 4 Nimmer, supra, § 13.09; 18 Am. Jur. 2d Copyright §220.

A. IBM's Misappropriation of UNIX Code

The Tenth Circuit has recently affirmed the following tenet of the ''unclean hands'' doctrine: "Where a plaintiff interferes with the defendant's ability to comply with his or her responsibilities, a court of equity will not turn a blind eye to the net effect on the parties' equitable relationship.'' Worthington v. Anderson, 386 F.3d 1314, 1321-22 (10th Cir. 2004). The court further, and specifically, affirmed in that case that the ''unclean hands'' doctrine applies where ''the plaintiff's own machinations had prevented the defendant from meeting the conditions of its licensing agreement.'' Id. at 1321; see, e.g., Tempo Music, 407 F.3d at 507-08 (applying doctrine of unclean hands in holding that it would be inequitabIe to permit the plaintiff to recover for copyright infringement that occurred, ''in part at least,'' by the plaintiff's ''dereliction''). It is also well established, in the intellectual-property context that the defense will apply if the claimant made ''material false statement in connection with the property which he seeks to protect.'' Worden & Co. v.Cal. Fig. Syrup Co., 187 U.S. 516, 528 (1903).

SCO determined to offer its UNIX license, beginning in August 2003, only because IBM had misappropriated SCO's proprietary source code and contributed thousands of lines of that code into Linux. Hughes Decl. ¶6. Indeed, based on the limited discovery to date, SCO has determined that among the material that IBM misappropriated and contributed to Linux is one of the very programs -- the ''Journaled File System'' -- for which IBM claims copyright in its instant motion. Davidson Decl. ¶¶10-52; compare SCO's Memorandum in Opposition to IBM's Motion for Summary Judgment on Its Tenth Counterclaim at 81 with IBM Br. at 8 ¶¶39-40.5

B. IBM's Unauthorized Access Into SCO's Website

Another well-established basis for the application of the doctrine in the context of the Copyright Act arises when the claimant has obtained evidence by improper means.6

SCO provided its customers who purchased SCO Server 4.O with a password to enter at a log-in screen so that only they could access source code via the internet. Sontag Decl. ¶17-19. After news of a bug in the website's security system was reported on internet websites, IBM exploited the bug to bypass SCO's security system, hack into SCO's computers, and download the very files IBM has now attached to its motion. Id. ¶¶20-27.

The Computer Fraud and Abuse Act, 18 U.S.C. §1030(a)(2)(C), makes it a felony for any person to access another person's computer, via the internet or otherwise, unless autharized to do so. See, e.g., Creative Computing v. GetLoaded.com, LLC, 386 F.3d 930 (9th Cir. 2004); I.M.S. Inquiry Mgmt. Sys., Ltd. v. Berkshire Info Sys., Inc., 307 F. Supp. 2d 521, 523-24, 526 (S.D.N.Y. 2004) (citing cases); AOL, Inc. v. LCGM, Inc., 46 F.Supp. 2d 444, 450 (E.D. Va. 1998). By improperly obtaining the evidence assertedly in support of its counterclaim and instant motion, IBM comes to the Court with unclean hands.

CONCLUSION

SCO respectfully submits, for the reasons set forth above, that the Court should deny IBM's motion for partial summary judgment.

Dated this 30th Day of November, 2004

___[signature]___
HATCH, JAMES & DODGE, P.C.
Brent O. Hatch
Mark F. James

BOIES, SCHILLER & FLEXNER LLP
Robert Silver, Esq. (admitted pro hac vice)
Stephen N. Zack (admitted pro hac vice)
Edward Normand (admitted pro hac vice)
Sean Eskovitz (admitted pro hac vice)

Attorneys for The SCO Group, Inc.


1 One of the subject programs, for example, is Linux Kernel S390 Support, IBM St. ¶17, even though IBM apparently has assigned "all of IBM's modifications to the kernel for use with IBM's S/390 mainframe computers" to the Free Software Foundation. Moglen, FSF Statement on SCO v. IBM, http://gnu.cdpa.nsysu.edu.tw/philosophy/sco-statement.html. Another subject program is Journaled File System ("JFS"), IBM St. ¶14, which appears to be a derivative of the JFS in UNIX. See Davidson Decl. ¶¶ 10-52.

2 See, e.g., R. Epstein, Why Open Source Is Unsustainable, FT.com (Oct. 21, 2004), at http://news.ft.com (Oct. 21, 2004) (noting that with respect to Section 2, "as a straight interpretive matter, it only states what the obligation of each programmer is with his own private improvements"); D. Kennedy, A Primer on Open Source Licensing Legal Issues: Copyleft and Copyfuture, 20 St. Louis U. Pub. L. Rev. 345, 363 (2001)("If a licensee distributes modifications of a program, source code must be made available and there is to be no fee other than copying and similar charges." (emphasis added)).

3 See also Lippo v. Mobil Oil Corp., 776 F.2d 706, 713-16 (7th Cir. 1985) (stating that "contract language upon which a right to forfeiture is grounded [must] be strictly and narrowly construed"); Galvin v. S. Hotel Corp., 154 F.2d 970, 973-74 (4th Cir. 1946) (stating that "every violation of a contract containing forfeiture provision does not necessarily require an actual forfeiture of the defaulting party's rights").

4 Given SCO's voluntary suspension of its Linux business, the limited extent of SCO's copying after the alleged forfeiture, and the lack of notice, Hughes Decl. ¶¶3-5, 12, any breach was immaterial. A forfeiture provision should not cause a party to lose a ''disproportionate'' share of contractual benefits. Restatement of Contracts, §229 and comment B; see also Looney v. Farmemrs Home Admin., 794 F.2d 310, 314 (7th Cir. 1986) (reversing summary judgment enforcing forfeiture clause in land saIe contract because ''result seems inequitable and unnecessary''); Queens Boulevard Wine & Liquor Corp. v. Blum, 503 F.2d 202, 206-07 (2d Cir. 1974) (declining to enforce termination clause because breach did not injure lessor and enforcement would needlessly harm lessee, creditors, and investors and ''would be grossly inequitable''). The courts apply the materiality standard in considering whether a ''forfeiture'' applies. See, e.g., RW Power, 899 F.Supp. at 1502-03 (declining to enforce forfeiture provision, which permitted termination upon supplier's failure ''to perform any of the obligations pursuant to this Agreement,'' because the provision did not ''clearly state'' that supplier's non-material breach would trigger forfeiture rights). That is, the ''risk of forfeiture'' is ''one factor to be considered in determining whether a breach of contract is material." Restatement of Contracts§241 & E. Allan Farnsworth, Contracts §§ 8/12, 8.16 (2d ed. 1990). In the forfeiture context, materiality is a question of fact. Fusion, Inc. v. Neb. Aluminum Castings, 962 F. Supp, 1392, 1395 (D. Kan. 1997).

5 For these same reasons, SCO disputes that IBM owns vaIid copyrights in the works at issue, and discovery on this issue has not been completed. SCO Statement of Facts ¶22. Although IBM' s copyright registrations are prima facie evidence of ownership, the presumption is rebuttable. Grundberg v. Upjohn Co., 137 F.R.D. 312, 379 (D. Utah 1991). This fact issue is an independent basis on which IBM's motion must be denied or at least continued.

6 See, e.g., Fleming v. Miles, 181 F. Supp. 2d 1143, 1154 (D. Or. 2001) (holding copyright registrant who denied existence of competing registration in his registration application could not recover damages for alleged infringement by competing registrant);Russ Berrie & Co. v. Jerry Elsner Co., 482 F. Supp. 980, 987-88 (S.D.N.Y. 1980) (declining to enforce copyright because the owner's knowing failure to disclose material facts in registration applications constituted ''reason for holding the registration invalid and thus incapable of supporting an infringement action, or denying enforcement''); Rixon, Inc. v. Racal-Milgo, Inc., 551 F. Supp. 163, 171 (D. Del. 1982) (''Unclean hands in the procurement of a patent from the Patent and Trademark Office or in prior enforcement action, for example, may render the patent unenforceable."); see also Nimmer, supra, §13.09[B] (the doctrine applies where the claimant "obtained information as to the nature of defendant's work through unfair means"); see also Gemveto Jewelry Co., Inc. v. Lambert Bros., Inc. , S42 F. Supp. 933, 939 (S.D.N.Y. 1982).


CERTIFICATE OF SERVICE

Plaintiff, The SCO Group, hereby certifies that a true and correct copy of the foregoing SCO's Memorandum in Opposition to IBM's Motion for Partial Summary Judgment on Its Counterclaim for Copyright Infringement (Eighth Counterclaim) was served via first class mail on this 30th day of November, 2004, to:

Alan L. Sullivan, Esq.
Todd M. Shaughnessy, Esq.
Snell & Wilmer L.L.P.
[address]

Evan R. Chesler, Esq.
Cravath, Swaine & Moore LLP
[address]

Donald J. Rosenberg, Esq.
[address]

Attorneys for Defendant/Counterclaim Plaintiff IBM Corp.

___[signature]___


Exhibits/Attachments to this document have not been scanned.

Please see the case file.


  


SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text | 464 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
OT stuff here
Authored by: Anonymous on Friday, December 03 2004 @ 04:32 AM EST
First post everrrrrr

[ Reply to This | # ]

PJ's description of the SCO brief
Authored by: marbux on Friday, December 03 2004 @ 04:49 AM EST
No mercy there, except the promise to save some evidence for later articles. :-)

---
Retired lawyer

[ Reply to This | # ]

what a mouthful
Authored by: Anni on Friday, December 03 2004 @ 04:55 AM EST
Usually it is possible to take a snippet or two from the text, quote them and
laugh hard at them.

This time it is impossible. The *whole* text is so full of it, you can't really
start separating any sentences without gagging after the twentieth.

Anni


---
Organic chemistry is the study of carbon compounds;
Biochemistry is the study of carbon compounds that crawl.

[ Reply to This | # ]

Corrections here please
Authored by: fudisbad on Friday, December 03 2004 @ 04:55 AM EST
Filler text.

---
FUD is not the answer.
FUD is the question.
The truth is the answer.

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: Anonymous on Friday, December 03 2004 @ 05:26 AM EST
This latest filing brings to mind some questions I'm hoping someone here can
help answer for me. SCOG is now once again raising the claim that IBM
misappropriated thousands of lines of its Unix code by placing it into Linux.
Wasn't one of their reasons for seeking dismissal of IBM's CC 10 their claim
that SCOG's case was not at all about such copyright violations? Here they seem
to be raising the very same copyright issues they denied were an issue in this
case. Accepting their arguments in either counterclaim defense would seem to
require rejecting conflicting claims made in the other. Does the judge rule on
each counterclaim in isolation, based only on the arguments made specifically
for each? Or can he consider the totality of evidence and arguments presented
throughout the case in making his decisions for each counterclaim?

It seems SCOG has failed to produce required evidence of specific copyright
violations to counter IBM's motion for PSJ on CC 10, yet waves those same
unsubstantiated claims of violations as part of its defense for CC 8. This seems
to negate any earlier arguments that CC 10 is irrelevant to this case. They also
point out in this filing that IBM has the burden of proof in showing a factual
basis for any purported copyright violations. Doesn't the same burden of proof
fall upon SCOG when they claim IBM's violations of SCOG's copyrights cause IBM
to have "unclean hands"? Can mere unsubstantiated claims of violations
be used as part of a defense, or must such claims also have some substantiating
evidence before a judge considers them in his decision?

[ Reply to This | # ]

You know what?
Authored by: inode_buddha on Friday, December 03 2004 @ 05:51 AM EST
Throughout the whole of this document, the one thing that fairly screamed out at me was this:

"FOSS can be given but it cannot be taken."

Since when does this concept preclude business? It only precludes certain business models based on artificial scarcity, just IMHO. In a like manner just IMHO there is no excuse for world hunger save for the sheer avarice of some individuals and governments. As for myself, the primary reason I am here is to try and do my part to keep the "free as in freedom". See sig below. Does this document not show the need for people to think deeper, and the real-world consequences of thoughts turned into actions?

pvant67 AKA "inode_buddha"

---
"When we speak of free software, we are referring to freedom, not price." -- Richard M. Stallman

[ Reply to This | # ]

Hang On, I've Got a Question
Authored by: Simon G Best on Friday, December 03 2004 @ 05:56 AM EST

First, I think I should say a few things up front: I am not a lawyer; there's lots of relevant stuff I haven't read or studied; and toothbrush (meaning that there must be something else I've forgotten, just like how it's traditional for one to forget ones toothbrush when going on vacation).

Here's the thing that struck me (nicely packaged in nutshell form by The SCO Group's very own lawyers):

Nothing in the GPL prohibits a licensee from imposing "further restrictions" on a third party's use of GPL-licensed material that the third party did not receive from that licensee. SCO has sold its license for UNIX software only to those who acquired a Linux operating system from someone other than SCO; ...

(That's from the fifth paragraph of their "Preliminary Statement", on page 7.)

As I understand it (not just from that snippet, but from other parts of that document, too), they're basically saying that they didn't violate the GPL because they didn't sell their "UNIX" license to those to whom they have been distributing copies of Linux.

For example, let's say that Alice and Bob both have copies of Linux. Alice got hers from The SCO Group, but Bob got his from RedHat.

Let's start with Alice first. The SCO Group didn't, and aren't, placing any further restrictions (beyond those in the GPL) on what Alice can do with her copy of Linux. So, when it comes to Alice, The SCO Group aren't violating the GPL.

Now Bob. The SCO Group did not provide Bob with a copy of Linux, so aren't bound by the GPL when it comes to whether or not they can sell Bob exemption from litigation for alleged infringement of The SCO Group's alleged 'IP'. So, if they sell Bob such a license, they aren't infringing the GPL by doing so, because they aren't bound by the GPL when it comes to their relationship with Bob in the first place. The GPL doesn't even come into it.

(Of course, that still leaves copyright law, but that doesn't come into it, either, as The SCO Group didn't do any copying or distribution of Linux when it comes to either Bob having a copy of Linux, or The SCO Group selling Bob an 'IP' license.)

That, at least, is how I understand what The SCO Group are claiming.

As I said up front, I'm rather ignorant of other, surely relevant stuff (for example, I haven't read the IBM counterclaims to which The SCO Group are responding), but it got my attention enough to actually raise it and ask about it.

So, where have I (and The SCO Group) gone wrong on this particular point?

(Of course, I'm glad that the GPL is getting a good work-out between the teams of lawyers, even if it doesn't get to the point of being ruled on by a judge. It's good to see that the GPL is a formidable thing that is not to be taken lightly. Particularly nice is that even The SCO Group are arguing that the GPL protects the rights granted through the GPL to copy and redistribute - delicious!)

---
Open Source - open and honest? Not while the political denial continues.

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: odysseus on Friday, December 03 2004 @ 06:01 AM EST
Well, I was just about to post my copy of Larry Rosen's
e-mail, but I see PJ beat me to it. Heh, it feels quite
strange to be in on an e-mail involving two such
illustrous parties :-)

John.

[ Reply to This | # ]

satire
Authored by: skip on Friday, December 03 2004 @ 06:04 AM EST
Satirical SCO press release (fake but fun)

Many people are feeling that our current court cases are unjust. This is not the
case. We are, in fact, a combined experimental court case/operating system
organistation. We are trying to establish whether or not certain court
procedures can be used to replace outdated Operating systems componants and
methods.

For example. Many operating systems use the round robin method for allocating
runnining processes time on the processor, thus ensuring each process gets an
equal share of time executing. We are thinking of replacing this with a circuler
pattern of court filings, where every possible theory gets presented to the
court over time. This has, we beleive, got a great deal of potential, and we
plan on patenting it asap. Of course this will mean suing the supreme court, but
that's for another day.

Further, Distribution is a major aspect of modern computing. However the
programming involved can be quite intense. We are currently exploring a legel
version of distribution, where tiny aspects of a case (analagous to a task) are
played out in courtrooms accross the country. In this scheme we have found that
we can be extremely economical in deciding which information is passed between
the various distributed nodes (courtrooms).
This we feel, could be extremely profitable if applied to, say, multiplayer
games, or, stock market manipulation (whoops, I mean 'analysis').

This method has proven to have some difficulties. It can, for instance, be hard
to shut down a task on a remote node (court proceeding) when we decide it is
advantagious to do so. We are currently refering to this as the 'DC effect'.
This scheduling issue is one we hope to address.

Lastly, handling Virus's. We have noticed that our experiments in an operating
system based on the US court system has been hit by a virus. This virus, which
we are naming PJ_Grkl_666, has proved to be extremely resistant. Recently there
have been some variants springing up, most recently the dBurns_94 worm (known
for accessing Universiy records through persistant Regent reqests), the
MaRbUcks_2004 virus has been tricky to locate, as it appears to be an older form
of a legal eficiency virus. Similar features to this virus have also been
witnessed in the IBM legal team, and in the teams of companies whom we have
graciously allowed to join us in court Court_OS experiment.

We hope to release the Beta version of our new OS once we have concluded the
destructive testing phase.

---
The above post is released under the Creative Commons license
Attribution-Noncommercial 2.0.
P.J. has permission for commercial use

[ Reply to This | # ]

Interesting reading for their alleged binary licensees
Authored by: Anonymous on Friday, December 03 2004 @ 06:22 AM EST
I imagine that these alleged purchasers, if any actually exist, might be calling
their vendors right now to ask yet again just exactly what it is that they
supposedly paid money for.

[ Reply to This | # ]

A better than usual effort I thought
Authored by: Anonymous on Friday, December 03 2004 @ 06:26 AM EST
I have to say that in my opinion this is at least a rational legal argument from
SCO. They are in fact arguing the way I would expect them to - the way that they
really have to argue given the nature of the GPL.

The people who wrote this appear sane and live in the same universe as the rest
of us, which is not something you could say about previous filings from SCO.
There is a touch of the old SCO bombast and absurdity in the bit about
`hacking', but on the whole the rest of it is reasonably well argued.

They are NOT going to win with this. But I doubt that a better argument could
really have been written given the lousy corner that SCO has at this point
backed itself into. I do congratulate SCOs lawyers this time for doing a
professional job on behalf of their client.

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: Steve Martin on Friday, December 03 2004 @ 09:25 AM EST

Nothing in the GPL prohibits a licensee from imposing "further restrictions" on a third party's use of GPL-licensed material that the third party did not receive from that licensee. SCO has sold its license for UNIX software only to those who acquired a Linux operating system from someone other than SCO;

I scratched my head for a long time over this paragraph. It seems to say that the GPL has no explicit provision preventing a party from hijacking someone else's work. Am I reading this right?? (Come to think of it, perhaps that's a relevant defense in this case...)

The GPL does not prohibit a licensee from collecting a royalty or licensing fee on verbatim (as opposed to modified) copies of GPL-licensed material.

I beg to differ. TSG's claim here is that GPL section 2, which mentions modified works) contains the "at no charge" restriction, whereas section 3 (which does not mention modifications) does not. If one looks closely at section 3, however, one will see that it reads

"You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

(emphasis added)

Thus, TSG's reading of the GPL in this fashion is simply an attempt to twist the language to support their licensing scheme.

---
"When I say something, I put my name next to it." -- Isaac Jaffee, "Sports Night"

[ Reply to This | # ]

And what about Red Hat Enterprise Linux?
Authored by: boban on Friday, December 03 2004 @ 09:27 AM EST
"Anyone can sell GPL software. But that license (and every license that
satisfies fundamental open source principles) guarantees the freedom to make
unlimited copies at no additional charge. So no matter what a distributor
charges for the first copy, the laws of economics suggest that the price per
copy will quickly drop to the marginal cost of production and distribution.
Inevitably someone will sell three copies at half price and make a
profit."

My point is, I recently bought a "pirated" version of RHEL3, and am
not sure if I did something not legal.

Boban.

[ Reply to This | # ]

And what unix ip are they liscensing exactly?
Authored by: NemesisNL on Friday, December 03 2004 @ 09:28 AM EST
They have been ordered to show what code in linux could possibly cover this unix
ip twice and failed to do so. That means they actualy sold liscences to people
without there even being a line of code in linux that would call for such a
liscence.

So there is no unix ip in linux and they still knock on your door trying to sell
you a liscence for using unix ip in linux????????

This sounds like a scam to me and I would urge the people who bought such a
liscence to seek legal advise in order to recover the money they paid for
something they do not need.

In order to sell such a liscence you would have to be able to show the need for
it. Since SCO appearantly can not do even that it surelu follows they were
selling red hearings.

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: Anonymous on Friday, December 03 2004 @ 09:38 AM EST
It's funny how companies can plead ignorance when their business revolves around
those issues they should be intamitely aware of. I've had the same problem with
a former employer. Everytime he does something wrong and gets caught, he pleads
ignorance. The really sad part is he's allowed to get away with it. Hopefully
this won't happen in the SCO case. I suspect that if it does, there will be
enough vocal people in the OSS community to challange the decision.

For the curious, my former employer was a pharmacists and he plead ignorance to
providing precription products without a prescription, at least 13,078 over 3
years. The accepted his plea of ignorance. But thanks to Groklaw I've been able
to setup a similar website that draws attention to the issue in the hopes of
overturning the decision. The idea of "many voices" is such a powerful
tool.

Darcy
www.snakeoil.ca

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: Anonymous on Friday, December 03 2004 @ 10:00 AM EST
I noticed that SCO say they only offered Linux for six months: Nov-02 to
May-03. Are they ignoring the Caldera side of their history with this
assertion?

[ Reply to This | # ]

important point?
Authored by: mossc on Friday, December 03 2004 @ 10:03 AM EST
"3. SCO determined to offer its UNIX License, beginnning in August 2003,
only because IBM had misappropriated SCO's proprietary source code and
contributed hundreds of thousands of lines of that code into Linux. Hughes Decl.
¶6."

So they are still claiming that IBM contributed SCOs! source code.

please list the hundreds of thousands of lines of SCO's source code.

Even if their derivative works distribution theory were accepted by the court
there is no way the code becomes their code, they are not argueing that, they
are saying it precludes IBM from distributing their own code.

Chuck

p.s. they also use the figure "thousands of lines" elsewhere:
"SCO determined to offer its UNIX license, beginning in August 2003, only
because IBM had misappropriated SCO's proprietary source code and contributed
thousands of lines of that code into Linux. Hughes Decl. ¶ 6"

[ Reply to This | # ]

But SCO website is still not updated.
Authored by: Anonymous on Friday, December 03 2004 @ 10:03 AM EST
As of 7:00 this morning, the SCO website still has Darl's letter about GPL being
unconstitutional and uneforceable, etc. And now they are hiding behind GPL? Go
figure that one out.

Also they are still offering binary only Linux IP licenses on the website.

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: mossc on Friday, December 03 2004 @ 10:21 AM EST
"SCO provided its customers who purchased SCO Server 4.O with a password to
enter at a log-in screen so that only they could access source code via the
internet. Sontag Decl. ¶ 17-19. After news of a bug in the website's security
system was reported on internet websites, IBM exploited the bug to bypass SCO's
security system, hack into SCO's computers, and download the very files IBM has
now attached to its motion. Id.¶ ¶ 20-27."

Have to look at Sontags declaration but I wonder is SCO really provided its
customers with a password.

Interesting intergatories: please provide contact information for the person who
actually implemented the password feature.
Please provide the customer list you used to contact your customers to provide
them with a login/password?

The deposition of that person would be interesting if they never actually put
the system in place. Password protecting a website is simple and basic. If
they really implemented this feature, correctly enabling it would be the a small
effort compared to the rest of the process of collecting customer data and
contacting them.

What repercussions are there for TSG if Sontag lied about this?

BTW, I have two legal copies of SCO linux server 4.0.
I did not get a notice of my account and password.
I suppose I should be able to contact them and get that information.

[ Reply to This | # ]

SCO's Achilles Heel
Authored by: Anonymous on Friday, December 03 2004 @ 10:26 AM EST
SCO never identified the UNIX code that was being licensed. As such, licensees
had no way of knowing which portions of the kernel they could redistribute, and
that effectively prevented redistributing any part of the kernel.

Couple that with public statements that IBM was the culprit, and licensees would
likely think that any IBM code included in the kernel was especially suspect.

I know, there are several other weaknesses, but I think if IBM conceded all
points for sake of argument, they can still win with this one.

[ Reply to This | # ]

Even if they're right they're wrong-- SCO's existing customers -- and SCO's SEC filings
Authored by: Anonymous on Friday, December 03 2004 @ 10:46 AM EST
Three points

1. It doesn't matter whether SCO is licensing all of Linux, parts of Linux, IBM
code in Linux, SCO code in Linux, etc.

The point is the condition for distributing IBM code in Linux, is that the WHOLE
OF LINUX is distributed under the GPL

(Whether SCO wants to distribute SCO's own code (if they can find it!) under
whatever license they like - they can -- but IBM's 8th counterclaim is about
IBM's code, not SCO's)


2. SCO's web site, says that SCO's existing customers have to sign up for a new
license - but it's free of charge

This additional license is a non-GPL license, and imposes additional terms.

The argument that they have only imposed their license on people who received
the code from other's than SCO, appears to be based on a false premise.


3. I believe if you check SCO's SEC filings (not to mention press releases - and
note some press releases have been attached to SEC filings)...

Anyway if you check the SEC filings, I believe you will see references to their
Linux licensing activities.

As they have received benefits from SEC filings (as all public companies do -
such as being able to receive investment funding, operate as a public
corporation, etc) -- I believe they may be barred from asserting a contrary egal
position in court [I posted a link to some cases where similar things had
occurred, for example, one I remember was a patent case]


Quatermass
IANAL IMHO etc

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: blacklight on Friday, December 03 2004 @ 10:52 AM EST
"B. SCO's Licensing Activities Did Not Violate the GPL.....
15 1. SCO Has Been Collecting Licensing Fees Only for Its Own
Code.....
15 2. SCO Has Otherwise Complied With the GPL..."

A woman is either pregnant or she isn't - there is no middle ground. Likewise,
either SCOG violated the terms of the GPL or SCOG didn't - there is no middle
ground.

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: Anonymous on Friday, December 03 2004 @ 11:01 AM EST
I think the GPL is actually copyright, people who write
and release work under the GPL are allowing other people
to use their work provided they do not break the
conditions that the owner has stipulated.

I don't think it matters who SCO is attempting to sell
licences to or where they got their software from. Every
copy of Linux was released by the original copyright
holders under the GPL and as far as they are concerned SCO
is attempting to attach extra conditions to people wanting
to use their work ( doesn't matter where it came from, the
copyright still belongs to the original owner ) and this
is one of the things which removes SCO's right to
distribute or use their GPL'd work.

If SCO were just selling licences for their own
copyrighted in material in Linux then they wouldn't have a
problem but since they obviously didn't do that then they
are in trouble.

[ Reply to This | # ]

SCO's "IP License"
Authored by: mosborne on Friday, December 03 2004 @ 11:02 AM EST
SCO's agruments are becoming more convoluted than a new roller coaster.

SCO claims that their "IP license" does not cover anything by IBM, yet
this entire lawsuit is about software created and given to Linux by IBM. How is
this possible?

By this declaration, none of the code created by IBM (e.g., JFS, NUMA, etc.) is
covered by the SCO "IP license". If that's the case then what did
these folks buy a right to?

They acknowledge that the stuff IBM gave to Linux was created and owned by IBM.
They say that their contract with IBM gives them control over who IBM can
license that IP to.

Even if you accept SCO's premise that they have control rights to the stuff IBM
developed and can tell IBM who they can license it to (Which I think is
hogwash). Nothing in the IBM-SCO contract can remotely be intrepreted as
granting direct licensing rights to that IP. Especially since many of the folks
who purchased said "IP license" weren't even UNIX licensees.


[ Reply to This | # ]

Applicable GPL details
Authored by: mossc on Friday, December 03 2004 @ 11:10 AM EST
From GPL section 2:
b) You must cause any work that you distribute or publish, that in whole or in
part contains or is derived from the Program or any part thereof, to be licensed
as a whole at no charge to all third parties under the terms of this License.

-----------------------

From GPL Section 3:
3. You may copy and distribute the Program (or a work based on it,under Section
2) in object code or executable form under the terms of Sections 1 and 2 above
provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source
code, which must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to
give any third party, for a charge no more than your cost of physically
performing source distribution, a complete machine-readable copy of the
corresponding source code, to be distributed under the terms of Sections 1 and 2
above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to
distribute corresponding source code. (This alternative is allowed only for
noncommercial distribution and only if you received the program in object code
or executable form with such an offer, in accord with Subsection b above.)
---------------------------------------------

I pulled the gpl code off of my SCO linux server 4.0 CDs that do not appear to
contain the linux kernel source.

According to section 2 they are still violating the GPL with their
"unix" license. "to be licensed as a whole at no charge to all
third parties under the terms of this License
"

Seems pretty clear.

According to section 3 they are required to make the source available to THIRD
PARTIES under the terms of the GPL. So to be compliant with the GPL anyone must
be able to request the linux kernel source licensed under the GPL from them.

to TSG are you distributing the linux kernel to anyone today?
If yes, your only right to distribute is the GPL, everyone in the world can then
get a copy licensed under the GPL.

If no, then you are in violation of the GPL all instances of distribution in the
last three years violated copyright.

[ Reply to This | # ]

Sitting on a forked stick is uncomfortable
Authored by: codswallop on Friday, December 03 2004 @ 11:11 AM EST
It seems to me SCO is faced with a rather unpalatable choice. To be in
compliance with the GPL concerning IBM's code, they can't have been sublicensing
it with their Linux IP license. They can say:

1) The IP license doesn't cover the IBM code, because they make no claims
against it which would require the license to release. This rather undercuts the
rest of their case.

2) The IBM code is a derivative work in the sense of copyright law and their
license is for the material from the parent work(s), but not for IBM's
contibution. This tries to poke a loophole in the GPL in a rather clever way,
but contradicts some of their other representations and supports some of IBM's
counterclaims. It's hard to repudiate public statements when you replicate them
in your own briefs.

3) The IBM code is restricted in some nebulous way that requires an enduser to
get a license, but this isn't a sublicense. This is a bit hard to swallow.

4) There is other code in Linux that requires users to get an IP license, but
the enduser has no liability with regard to the IBM code, tus the IBM code isn't
being sublicensed. This is strictly between IBM and SCO. This is their best
argument, but it largely guts SCOSource. What other large block of code is there
to justify a license?


---
IANAL This is not a legal opinion.
SCO is not a party to the APA.
Discovery relevance is to claims, not to sanity.

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: dopple on Friday, December 03 2004 @ 11:22 AM EST
"SCO determined to offer its UNIX license, beginning in August 2003, only because IBM had misappropriated SCO's proprietary source code and contributed thousands of lines of that code into Linux. Indeed, based on the limited discovery to date, SCO has determined that among the material that IBM misappropriated and contributed to Linux is one of the very programs -- the ''Journaled File System'' -- for which IBM claims copyright in its instant motion."

This is an interesting claim... correct me if I'm wrong, but I didn't think that even the most lenient reading of the UNIX licence would make JFS become "SCO's proprietary source code." Or is this supposed to be one of those vaguely-written things where just because the sentences appear to refer to each other in the same paragraph, they're really talking about something different in the second one?

---
Never play chicken with Nazgul. It only gets you wounds
that never heal and an annoyed judge.

[ Reply to This | # ]

how many?
Authored by: maco on Friday, December 03 2004 @ 11:40 AM EST
how many ways can you say "weasel"?

[ Reply to This | # ]

Does this now make Windows into Open Source?
Authored by: DannyB on Friday, December 03 2004 @ 11:52 AM EST
Follow my reasoning.

SCO states that they were in full compliance with the GPL when they distributed
Linux.

Therefore, any modifications SCO made are also licensed under the GPL.

According to SCO's theory of derrivitive works, how much of SCO's IP is now
subject to the GPL?

Microsoft and Sun bought a license to SCO's IP.

Presumably, Sun and Microsoft have used that IP in their own products. For
instance Microsoft uses the SCO license IP in Services For Unix (SFU). (the
very rationale that MS gave for buying SCO's license!)

According to SCO's theory of derrivitive works, this makes Microsoft Services
for Unix subject to the GPL. Any other code linked with SFU would be GPL.

Does SFU link to any critical parts of Windows, i.e. the GUI or the Kernal?

---
The price of freedom is eternal litigation.

[ Reply to This | # ]

Non-GPL code cannot be licensed for use linked with GPL Linux code.
Authored by: Anonymous on Friday, December 03 2004 @ 11:53 AM EST
SCO cannot link it's proprietary licensed code (if there
is any in Linux) to other people's GPLed code except under
a GPL license. This means SCO's code must be removed from
Linux if SCO wishes to license it under other terms than
GPL otherwise SCO is violating other people's copyright
including IBM's.

[ Reply to This | # ]

Well, this must be a breach of GPL
Authored by: Anonymous on Friday, December 03 2004 @ 12:01 PM EST
From:
ftp://ftp.sco.com/pub/scolinux/server/4.0/updates/SRPMS/Legal_Notice
2004-12-03
------------------------------------------------------------
NOTICE: SCO has suspended new sales and distribution of SCO Linux until the
intellectual property issues surrounding Linux are resolved. SCO will, however,
continue to support existing SCO Linux and Caldera OpenLinux customers
consistent with existing contractual obligations. SCO offers at no extra charge
to its existing Linux customers a SCO UNIX IP license for their use of prior SCO
or Caldera distributions of Linux in binary format. The license also covers
binary use of support updates distributed to them by SCO. This SCO license
balances SCO's need to enforce its intellectual property rights against the
practical needs of existing customers in the marketplace.

Dear SCO customer,

Starting on November 1, 2003, SCO will institute new procedures for you to
access binary updates and source rpms. If you own an SCO licensed copy of Linux
(such as such as OpenLinux, eDesktop, etc.), it will be necessary for you to
register (or re-register) in order to continue to receive support files. During
the registration process you will receive instructions on how the new access
procedure will
work o
-----------------------------------------------------------

Well, it seems like the updates and any continued use requires the "SCO
UNIX IP license". If any of those updates includes any GPLed code they are
in breach of GPL.

[ Reply to This | # ]

Did IBM assign copyright to FSF? Or just release under GPL
Authored by: Liquor A. on Friday, December 03 2004 @ 12:15 PM EST
SCO references a somewhat incorrect link in footnote 1 to support a contention that IBM assigned the copyright on their code to the FSF (and thus has no standing for a copyright claim): http://gnu.cdp a.nsysu.edu.tw/philosophy/sco-statement.html

Why they used a website from Taiwan, as a reference, I don't know - but I think the link might because the taiwan site (a mirror of gnu.org) was not a true copy. The origninal is probably http://www.gnu.org/phil osophy/sco-statement.html.

I suspect that the document that they are referencing is actually http://www.gnu.org/philo sophy/sco/sco-v-ibm.html which in turn has the statement(emphasis added):
The Foundation notes that despite the alarmist statements SCO's employees have made, the Foundation has not been sued, nor has SCO, despite our requests, identified any work whose copyright the Foundation holds-including all of IBM's modifications to the kernel for use with IBM's S/390 mainframe computers, assigned to the Foundation by IBM--that SCO asserts infringes its rights in any way.
This specifically references the S390 kernel mods - which I don't think is one of the parts which IBM itemizes in it's counterclaim and, if so, would be moot - but even so I am wondering just how far the confusion is going betweeen 'copyright assigned to the FSF' and 'released under the GPL'. I can see releasing the code under GPL as being an assignment of rights, but not being an actual copyright transfer.

Did Eben Moglen misinterpret or misstate something? Or did I? Or how could someone other than IBM be the actual copyright holder?

---
Liquor A.

[ Reply to This | # ]

Did IBM assign copyright to FSF? Or just release under GPL
Authored by: Liquor A. on Friday, December 03 2004 @ 12:19 PM EST
SCO references a somewhat incorrect link in footnote 1 to support a contention that IBM assigned the copyright on their code to the FSF (and thus has no standing for a copyright claim): http://gnu.cdp a.nsysu.edu.tw/philosophy/sco-statement.html

Why they used a website from Taiwan, as a reference, I don't know - but I think the link might because the taiwan site (a mirror of gnu.org) was not a true copy. The origninal is probably http://www.gnu.org/phil osophy/sco-statement.html.

I suspect that the document that they are referencing is actually http://www.gnu.org/philo sophy/sco/sco-v-ibm.html which in turn has the statement(emphasis added):
The Foundation notes that despite the alarmist statements SCO's employees have made, the Foundation has not been sued, nor has SCO, despite our requests, identified any work whose copyright the Foundation holds-including all of IBM's modifications to the kernel for use with IBM's S/390 mainframe computers, assigned to the Foundation by IBM--that SCO asserts infringes its rights in any way.
This specifically references the S390 kernel mods - which I don't think is one of the parts which IBM itemizes in it's counterclaim and, if so, would be moot - but even so I am wondering just how far the confusion is going betweeen 'copyright assigned to the FSF' and 'released under the GPL'. I can see releasing the code under GPL as being an assignment of rights, but not being an actual copyright transfer.

Did Eben Moglen misinterpret or misstate something? Or did I? Or how could someone other than IBM be the actual copyright holder?

---
Liquor A.

[ Reply to This | # ]

Shouldn't this have been said at the hearing?
Authored by: Anonymous on Friday, December 03 2004 @ 01:37 PM EST
Seems to me these issues should have been brought up at the hearing, not two
months after.

As a procedural issue, can one side keep arguing their case after the hearing
for a long as the case is under advisement?

[ Reply to This | # ]

GNU GPL section 7
Authored by: Anonymous on Friday, December 03 2004 @ 01:49 PM EST
Section 3 of the GPL does not prohibit a licensee from charging "royalty or licensing fees" on the licensed works. Section 3 does not even mention fees or royalties at all. GPL §3. (SCO therefore denies IBM St. ¶65.)

True, but SCO, have you read the GPL completely? Section 7 might be of interest for you.

[ Reply to This | # ]

Have they ever actually shown this code yet ?
Authored by: Pop69 on Friday, December 03 2004 @ 01:51 PM EST
"3. SCO determined to offer its UNIX License, beginnning in August 2003,
only because IBM had misappropriated SCO's proprietary source code and
contributed hundreds of thousands of lines of that code into Linux. Hughes
Decl."

This one rears its' ugly head again and STILL no-one has actually seen this
supposed code. If there are hundreds of thousands of lines of code that are
copied, all SCO has to do is point them out and it's an open and shut case.

Perhaps they lost the keys to Blepps briefcase and can't show them ?

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: rp$eeley on Friday, December 03 2004 @ 02:51 PM EST
Talk about a tangled web!
Will it never cease?

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: Anonymous on Friday, December 03 2004 @ 03:20 PM EST
Did or did not SCOGroup repudiate the GPL?

A good trial on this would probably do a world of good.

It would certainly be an eduational experience for the world at large, and for
lawyers who will be facing this issue in the future.

[ Reply to This | # ]

A much better defense
Authored by: PolR on Friday, December 03 2004 @ 03:38 PM EST
SCOG should have argued the following:

We have not violated the GPL because the SCO IP in Linux is non existent.
Therefore the additional restrictions applicable to GPLed code are void and
unenforceable. In the absence of such restrictions, no violation of the GPL
occured.

I write this as a joke, but given CC10, perhaps the judge will see things this
way...

IANAL

[ Reply to This | # ]

SCO selling Linux IP Licensing...a satire
Authored by: drakaan on Friday, December 03 2004 @ 03:46 PM EST
SCO: (sits down at table) Okay, it's come to our attention that your company
uses Linux. A lot of it, in fact. We'd like to take this opportunity to give
you a chance at using it legally.

Clueless Company: We're not using it legally? We bought boxed copies from
RedHat...is that illegal?

SCO: Well, Linux is not just the product of random coders working for some
altruistic goal. Actually, some important parts of Linux were stolen, that's
right...STOLEN from code that SCO owns the rights to. It's just terrible,
really.

CC: Wow. Nobody ever mentioned that before. What exactly did they steal?

SCO: Various things, but let's get on to the heart of the matter. How many
copies of Linux are you using at your company, and on how many processors?

CC: Well, I'm not sure. My IT department said we could basically install it on
whatever we wanted, but that we'd have to apply patches manually or something
like that. Maybe 400?

SCO: Okay, that'll be...$279,600.00. Pocket change, really. How will you be
paying?

CC: Well, hold on a minute. What exactly are we paying for. I mean, is
everybody signing up for licenses, or is the stuff you have rights to stuff that
we can just take out and not use or something?

SCO: You'd be surprised how many companies are signing up...we certainly were
(grumble, swear). The things that we have rights to are so important to Linux
that Linux would crumble...*CRUMBLE* if they were removed. Mark my words, if
you don't buy this, you're making a BIG mistake my friend.

CC: Okay, okay...let me page legal for an opinion. (pages legal dept.). So,
while we wait, what kind of rights do you have exactly? Patents? Copyright,
Trade Secrets?

SCO: Well, we have to be careful not to disclose too much, you know. We have
lawsuits in the works, you see. We own the copyrights to all of UNIX! We
bought them, lock, stock, and barrel from Novell, and if anybody else says
differently, they're lying!

CC: Wow! All of UNIX! That's really something. So, there is UNIX code in
Linux? I thought it was basically created from scratch by some Linus guy. How
much code is it exactly?

SCO: That's just the thing. You see, certain other companies have taken our
UNIX code and they've looked at it and created other code that works with it to
do certain things. Once they do that, that code belongs to
us...MUAHAHAHAAAAA!!! Ahem, sorry about that. Once they do that, it becomes
*our* code. What they did was horrible. They took some of the code that they
developed themselves (thatbelongstous) and they contributed it to Linux! Can
you imagine??? (lawyer comes in) So, as you can see, this is very serious, and
potentially damaging to every linux user out there.

CC: I can see how it *might* be, I guess...what do you think Sam (Sam is the
lawyer, of course)?

Sam: I tell you what, Boss, let me talk to this gentleman for a few minutes and
try to get a handle on this.

CC: Okay, I need more coffe anyway (leaves room) Oops, forgot my coffe cup
(opens door)

Sam: (quickly stuffing a wad of cash in his pocket) Right! So...boss, I thinkk
that "better safe than sorry" is the appropriate way to go here. We
don't need to take needless risks.

SCO: You're absolutely right. Belive me, this is one decision that you'll
never regret... (fade to black, cue music, fin)

[ Reply to This | # ]

Can we stop all this for a minute............
Authored by: jim Reiter on Friday, December 03 2004 @ 03:57 PM EST

TSG has yet to prove it actually owns these copyrights.

TSG has yet to present any documentation regarding what
TSG acquired from Old SCO.

There is a contractual question as to what control TSG can
exercise over the SVRX licenses.

There is a contractual question over TSG's right to sell
addition SVRX licenses, except in conjunction with the
Netware/Unixware business.

What does TSG actually own and how did they (TSG) come to
own it?

So far not very much.

[ Reply to This | # ]

Historical note on "repudiation"
Authored by: marbux on Friday, December 03 2004 @ 04:14 PM EST
According to the fifth edition of Black's Law Dictionary, it looks like "repudiation" has its root in the Latin "repudium:"

In Roman law, a breaking off of the contract of espousals, or of a marriage intended to be solemnized. Sometimes translated 'divorce;' but this was not the proper sense."

---
Retired lawyer

[ Reply to This | # ]

This may be the best test of the GPL in court
Authored by: BrianW on Friday, December 03 2004 @ 04:32 PM EST
I’ve read comments here that the GPL can not really be tested in court because
violators are technically breaking copyright law, not a license agreement. So
the terms of the GPL won’t even come into play since a copyright holder has no
alternative but to use copyright law, not the GPL, to take violators to task.

I’ve also read PJ’s comments that the GPL will not be tested in court here
because SCO has now, at least for the purposes of this PSJ, embraced the GPL and
intends to use it as a defense of its actions. I quite disagree with this
assessment. The way things are shaping up, I believe this could be the best
court-case test imaginable for the GPL.

With IBM suing for copyright violations and SCO embracing the GPL as a defense,
the court will have no alternative but to examine the terms of the GPL to the
extent that such terms could be used to defend SCO’s actions. While it is still
true that, in the end, SCO will be found to have violated (or not violated)
copyright law, not the GPL, the use of the GPL as a defense for their actions
certainly brings the license and its terms into the discussion.

Until now, I think it has been presumed that “bad-faith” copyright violators
would realize the futility of using the GPL as a defense, and “good-faith”
violators would fess up and either stop copying/distributing or comply with the
GPL. Who knew that we’d ever encounter a “bad-faith” copyright violator who
would be clueless enough to use the GPL as a defense for copyright violation?
But, well, there you have it. Now the judge will be forced not only to apply
copyright law, but also to determine the extent to which the terms of the GPL
apply as a defense.

What could be a better test of the GPL?


---
//Brian
#define IANAL

[ Reply to This | # ]

Hacking Indeed!
Authored by: mobrien_12 on Friday, December 03 2004 @ 04:47 PM EST
"SCO provided its customers who purchased SCO Server 4.O with a password to
enter at a log-in screen so that only they could access source code via the
internet. Sontag Decl. ¶17-19. After news of a bug in the website's security
system was reported on internet websites, IBM exploited the bug to bypass SCO's
security system, hack into SCO's computers, and download the very files IBM has
now attached to its motion."

Entering a blank username and password is not a "bug" that allows one
to "hack into SCO's computers." It means that SCOG ALLOWED ANONYMOUS
LOGINS.

The very fact that this was known for a very long time after it was published
(wasn't it months before they removed the anonymous access?) verifies this.

[ Reply to This | # ]

Copyright vs. Contract
Authored by: Anonymous on Friday, December 03 2004 @ 04:47 PM EST

IANAL, just some punk kid who just finished Business Law I in college and who's otherwise a general know-it-all :).

We were taught about the different primary branches of US law:

  • Criminal
  • Tort
  • Property (including real, personal, and intellectual property)
  • Contract
  • Domestic relations

So what's the exact difference between this being a copyright case and a contract case? SCO is claiming things based on it being a contract case. PJ blows them off by asserting that it's really a copyright (property law) case, not a contract case.

The way I see it, publishing code under the GPL is an offer (in the legal, contractual sense) by the copyright owner of a bilateral contract offering permission to distribute the copyrighted code in exchange for certain consideration, particularly that you agree to certain ways of handling it or any derivative works thereof. You indicate acceptance (again, in the legal, contractual sense) by certain action, similar to {shrink,click}wrap licenses:

You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

PJ responds thusly:

Then they talk a lot about contracts and contract law, offering all kinds of fancy pants arguments, but that has nothing to do with the GPL, which is a copyright license.

OK, so a copyright is a piece of property (RMS notwithstanding). Rights or interests in property are conveyed from one party to another via contracts. If I want to lease an apartment, I sign a contract that conveys right of possession, under certain terms. Thinking in those terms, to me PJ's argument sounds like: If I take the landlord to court over some grievance, talking about the grievance using contract law is silly because this is a case about property, thus using property law, not contract law (even though we signed a contract).

So what am I missing? I know that the copyright vs. contract debate has come up in FLOSS circles before (probably including here), but it looks like it could use a rehashing, at least for my sake :).

So can somebody please explain why PJ's right--or <shudder> why she's wrong--preferably with some sort of pointers to outside sources where I can try to dig into it more myself, if I'm so inclined?

[ Reply to This | # ]

My crystal ball says CC10 PSJ will have to wait
Authored by: Anonymous on Friday, December 03 2004 @ 05:32 PM EST
I think Judge Kimball will now wait until after the hearing on CC 8 before he rules on CC10. And he may wait until much later. Reason? He doesn't want to have to wade through any more sewage than necessary.

The way SCOX is basing all their logic on IBM using SCOX's copyrighted code, if the judge rules before the hearing, I'd expect to see another round of long submissions (are any SCOX submissions ever at or under length?), as they try to rescue their case from Darl's monomania. After he's been fully briefed, and the motions argued, he can deny motions to submit another brief. Comments?

[ Reply to This | # ]

When does IBM reply to this?
Authored by: jaydee on Friday, December 03 2004 @ 05:45 PM EST
I can't wait...he he he



---
Micro$oft. What's broken today?

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: tredman on Friday, December 03 2004 @ 06:06 PM EST
I'm convinced that the main impetus regarding the flurry of motions that SCOX
files is that, with so many varied and contradictory strategies used, they're
hoping that IBM's lawyers will leave out things in their opposition briefs and
reply memorandums, purely through distraction.

It's a shame for them that IBM's lawyers aren't wired like SCOX lawyers.

Tim

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: blacklight on Friday, December 03 2004 @ 06:34 PM EST
"Therefore, by modifying or distributing the Program (or any work based on
the Program), you indicate your acceptance of this License to do so" From
tthe text of the GPL

So what SCOG's distinguishing between modified and unmodified GPLed software is
apparently a distinction without a diference.

[ Reply to This | # ]

I just don't get it
Authored by: Anonymous on Friday, December 03 2004 @ 07:06 PM EST
"SCO determined to offer its UNIX license, beginning in August 2003, only
because IBM had misappropriated SCO's proprietary source code and contributed
thousands of lines of that code into Linux"

How can they even submit this? Can IBM have it stricken in its entirety?
Doesn't this go right back to their original complaint, which they have
withdrawn, and which despite two court orders they have failed to identify even
one line?

In a logical world, that in itself should throw this whole thing out. They
spend a third of the document re-stating claims that they have already
withdrawn, and that they cannot prove.

[ Reply to This | # ]

A confusion of IP rights?
Authored by: soronlin on Friday, December 03 2004 @ 07:24 PM EST
There are a limited number of types of IP, and they are all different. We know that SCOG are not claiming patents or trademarks, so that only leaves copyrights and trade secrets.

If the SCOG IP in Linux is copyright, then SCOG are able to find and identify it with ease. The only way to show copyright violation is if some SCO copyrighted code from UNIX showed up verbatim or disguised in Linux. They do not have to have any AIX source or any other code to find it. No matter what permutations the code has gone through there has to be a substantial quantity of UNIX code in Linux. That is not hard to find or to demonstrate. SCOG have not done so, and are on record as saying that this is not what they are talking about.

If the SCOG IP in Linux is trade secrets, then SCOG are not limited to copyright-type infringements. They may or may not find various versions of AIX useful to find a link between UNIX and Linux. That is a matter of contract interpretation, and is moot here. The fact remains that maybe IBM or another licencee may have broken their contract by contributing code to Linux, but that is where the buck stops. It's a contract argument, and it is not binding on third parties. Nobody else is guilty of anything; the trade secrets are secret no longer, and SCOG can only claim damages from their direct licencee, eg IBM.

If SCOG do not prove copyright violation then nobody needs a SCO licence to use Linux.

[ Reply to This | # ]

and now for the other side.
Authored by: Anonymous on Friday, December 03 2004 @ 08:31 PM EST
I dont know why exactly, but this latest thing from the
sco-circus reminds me of a joke.


A newly married couple spend their honeymoon in a nice
hotel. But when they check out of the hotel, the husband
is quite surprised to see a fairly large charge for the
condiments in the hotel.

He says to the desk clerk, "Why is this on my bill?"

To which the desk clerk says that the charge is for the
the peanuts, fruit and bottles of vodka that were in the
room.

"But we didnt use any of that" says the husband, getting a
little irate.

The desk clerk calls over his manager and the husband
explains the problem. The manager then said "Sir, we
provided those items, if you didnt use them thats not our
fault. They were there for you".

Without any warning, the husband then punches the manager
in the nose.

Surprised and holding a bleeding nose, the manager asks
"What did you do that for?"

"For sleeping with my wife!" exclaimed the husband.

"Your wife? I didnt sleep with your wife!" screeches the
manager.

To which the husband replied... "ahhh... but she was
there..."

[ Reply to This | # ]

Liars, perjurers, and nut jobs
Authored by: Anonymous on Friday, December 03 2004 @ 08:46 PM EST
Looks to me like SCOG attorneys are trying a new version of "It's not in
this court, it's in *that* one over there". Only this time it's "No
not that text or speech or claim, this one over here". What a pathetic
bunch of liars.

They did repudiate GPL, by not making the code available to customers, OR they
did make it available, and IBM may or may not have downloaded it and it doesn't
matter if they did, or Joe Schmoe did.

They're also perjurers. Not only can't both statements be true (and so, it
doesn't matter which is), but lets hope the judge takes few minutes needed to
look for "Linux" in the earlier filings, and "Unix" in this.
Beside, they quote the GNU GPL. Huh? Are these idiots so stupid they don't
know GNU means "GNU's Not Unix" So how could the "license"
Unix under a Not Unix license? The Luddites from Lindon haven't proven they
have ownership of Unix either, nor any right to license it. So even if they did
NOT repudiate GPL, they haven't shown that a) ANYTHING in Linux is a violation
and b) even if it was, they have a right to license a "cure".

Nut jobs that they are, they then try to twist their court records and public
statements like mobsters. Frankie goes out and with his mafiosa friends, beats
a competitor to the point where he is breathing and eating through tubes (not
dead, just a veg), and puts the word out that they did it. Then they go around
demanding money, with the implied threat that "ya know what happened to the
last guy". They don't have to say more because word is out, and that is
EXACTLY WHAT SCOG AND THEIR ATTORNEYS DID with help from fellow conspirators in
the "press" and Redmond.

Now they try to turn the words around and claim the exact opposite. This is an
old propaganda trick: loudly blame somebody for something, and the raucous tone
sticks in peoples mind but not the details. Later, you go back and say
"And remember how he wronged me?". People remember the rancor, forget
the details, and that you switched position. "Oh yeah, those bad
folks" they say. SCOG is trying to play the same "both sides of a
coin" game.

If it wasn't so pathetic, and probably illegal because of stock fraud or wild
DMCA and other *copyright* claims (did you see how they referred to Computer
Fraud statute here?), it would be hilarious to see otherwise
"intelligent" people like Yarrow, Tibbits, McBride, Stowell, Sontag,
and cronies trying this grammar school stunt. Is it only in Utah such stupid,
lying fools think they can get away with such fraud?

[ Reply to This | # ]

There is confusion about the GPL--let's dispell it
Authored by: Philip Stephens on Friday, December 03 2004 @ 10:12 PM EST
There seems to be confusion about what the clauses of the GPL really mean. I
have a copy of the GPL version 2 in front on me, and here is what it means in
plain language:

Section 0: Preamble. Simply explains that this license applies to a program
which contains a notice by the copyright holder refering to this license. It
also explains that the license only covers copying, distribution and
modification of the program--not it's use.

Section 1: If you distribute a verbatim copy of the program, you must include
the copyright notices and a copy of the license (meaning it's still licensed
under the GPL).

Section 2: If you distribute a modified version of the program, it must be
licensed under the GPL.

Section 3: If you only distribute the binary, you must make the source code
available to those that ask for it.

Section 4: If you try to sublicense the program or a modified version under
different terms, YOUR license to the program is terminated (though not the
license transfered to those you distributed the program or modified program
to).

Section 5: You don't have to accept the license, but if you don't the copyright
laws of your country will apply (meaning in general you have no rights at all).

Section 6: Redistribution automatically confers the license to the recipient,
who therefore gains all the rights you have to the software. You cannot impose
further restrictions onto the recipient.

Section 7: If there is a legal question as to whether a portion of the program
can be licensed under the GPL, you cannot distribute the program at all. The
legal question must be resolved first.

Section 8: If certain countries have laws that prevent you from distributing
this program under the GPL, you can exclude that country from recieving copies
of the program.

Section 9: FSF reserves the right to publish new versions of the GPL.

Section 10: If you want to include portions of the program with another whose
distribution conditions are different, ask permission from the copyright
holder(s).

Section 11: No warranty is implied, to the extent permitted by law.

Section 12: No liability for damages as a result of using the program is
implied.





[ Reply to This | # ]

Doin' the Time Warp
Authored by: rsteinmetz70112 on Friday, December 03 2004 @ 10:38 PM EST
Like every thing else in SCOG's alternate reality time seems to flow one way,
their way.

DCC gets 30 days to respond to a request concerning a perfectly legal activity
they stopped doing seven years ago and DCC's failure to respond is an unbearable
hardship on SCOG. 45 days later they get sued.

SCOG gets a "reasonable" time two year window to wind down an illegal
activity they are proclaiming to all to be a threat the foundations of the world
economy. There is no consideration of alternate ways of terminating their Linux
business, like providing copies of Unixware to all Linux customers or simply
discontinuing support of an illegal product or by simply refunding the customers
money.

SCOG equates their own violation of someone else's copyrights which were
terminated automatically by SCOG's own actions to take effect at some
indeterminate time in the future.

I sure hope DCC picks this up, especially the statement about the automatic
termination not meaning immediate. Perhaps this should be included in any
proposed revisions to the GPL.

I can't believe anyone who reads this stuff can came do any thing except stand
in awe of the sheer gall of these guys.

It's like dealing with two year olds, except your average two year old can't do
this much damage.

---
Rsteinmetz

"I could be wrong now, but I don't think so."

[ Reply to This | # ]

  • Indeed - Authored by: Anonymous on Saturday, December 04 2004 @ 02:00 AM EST
Other errors and issues
Authored by: Anonymous on Friday, December 03 2004 @ 10:50 PM EST
Without reiterating everything already discussed

There are some ADDITIONAL issues that appear not to have been discussed. Among
others, these include:

1. SCO issuing their own responsive list of undisputed facts, rather than
responding point by point to IBM's list. (see how IBM responded in their reply
motion in support of PSJ on CC10 when SCO did this previously - they cited cases
where courts routinely disregarded such counterstatements).

2. SCO making assertions that do not appear to reference affidavits or other
exhibits (again IBM appears to have cited cases where mere allegations or
references to the pleadings are insufficient to deny a summary judgement
motion)

3. SCO simply getting dates wrong. In their brief they say that there was no
notice of their breach of the GPL prior to IBM's 2nd amended counterclaim in
February 2004.

This is simply untrue

IBM's first counterclaims (IBM-27) - 6th cause of action breach of the GPL - was
served on SCO 6th August 2003

IBM's amended counterclaims (IBM-41) - 6th cause of action breach of the GPL,
8th cause of action copyright infringement - was served on SCO - 25 September
2003

(it is true that the 2nd amended counterclaim from February does include
ADDITIONAL copyright registrations in the 8th cause of action, but AFAICS that
is the *ONLY* substantive difference)

4. The copyright conundrum

Part of SCO's defense to copyright infringement charges raised against that by
IBM, is that IBM has unclean hands because of IBM's alleged copyright
infringement of SCO's copyrights

In order to succeed in this defense they will eventually have to present some
evidence of IBM's copyright infringements in Linux - but even by their own
admission, they are currently unable to do so (they explicitly said their
opposition to IBM CC10 was founded solely on rule 56f, and not at all on 56e --
although this contradicted earlier statements they made to the same court).

Furthermore, in order to succeed in this defense, they will have to prove
something (copyright infringement by IBM's Linux activities) that they do not
think should be part of the case (they have told the court this too in writing
following the Kimball hearing in June and in their motion to dismiss IBM CC10).



Quatermass
IANAL IMHO etc

[ Reply to This | # ]

SCO's use of the phrase "license Linux"
Authored by: Anonymous on Saturday, December 04 2004 @ 12:02 AM EST
SCO repeatedly states that they did not "license" Linux. This
statement misses
the point by a mile. The copyright counterclaim relates to SCO's distribution
of Linux without a valid license to do so -- based on their repudiation and/or
breach of the GPL. The remedy IBM is seeking is that SCO stop distributing
Linux. SCO doesn't want to do that, interestingly enough.

Regards,

Mark Wilson

[ Reply to This | # ]

  • Not quite - Authored by: Anonymous on Saturday, December 04 2004 @ 12:31 AM EST
HP Violated GPL????
Authored by: Anonymous on Saturday, December 04 2004 @ 01:08 AM EST
Everyone here keeps saying that SCO violated the GPL by sublicensing the kernel
under their own terms...and I fully agree with them. But, doesn't that mean that
when HP offered customers indemnity in exchange for money as long as they
surrendered their rights under the GPL...that HP was in fact also violating the
GPL??? I was wondering about that and was wondering if anyone had any thoughts
on this.

Also, would the terms of the GPL still count since SCO wasn't distributing the
software, but instead just selling a license??

I am in no way pro-SCO...I think they are a bunch of scum bag losers. Just
wondering what your thoughts are on this?

[ Reply to This | # ]

Repudiating license Vs Contract
Authored by: Naich on Saturday, December 04 2004 @ 04:42 AM EST
"A repudiation occurs when a party to a contract..." etc.

It's been pointed out that the GPL is not a contract, but what are the
implications here? SCO might have shown that it has not repudiated a contract,
but I'm getting begging questions in my head along the lines of:

1. Have SCO met the conditions for repudiating a _license_?

Does the phrase in the GPL clause that "Therefore, by modifying or
distributing the Program (or any work based on the Program), you indicate your
acceptance of this License to do so" mean that whatever you may say, you
have not repudiated the license because you are still distributing it?

2. What happens if you have repudiated a license? Do you get the same rights
(e.g. "reasonable time to wind down") as the ones that occur when you
repudiate a contract?

[ Reply to This | # ]

A different approach.
Authored by: Anonymous on Saturday, December 04 2004 @ 05:50 AM EST
What is this trial about? It is, among other things, about contributions made by IBM to Linux which breach SCO's rights.

Has SCO given any example of IBM's contributions that breach UNIX licence? I think they have. They have repeatedly mentioned NUMA, JFS, etc...

When SCO launched their UNIX licence, they were licencing all the contributions that were improperly made to Linux, implicitly including all the examples they have publicly claimed (that is, NUMA, JFS, etc..).

IBM registered the copyrights of SCO's examples. SCO did not oppose to them, which would have been the logical reaction.

In the late days I have seen no rectification of these claims (until we see the last amended complaint), nor a drop in UNIX licence price reflecting any change. So today SCO is trying to charge for a work made by IBM and released with a GPL licence.

I think we can try to deconstruct any argument made by SCOs lawyers. But first they must explain why trying to licence something that they have not written nor bought is not a copyright violation.

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: blacklight on Saturday, December 04 2004 @ 07:14 AM EST
"Nothing in the GPL prohibits a licensee from imposing "further
restrictions" on a third party's use of GPL-licensed material that the
third party did not receive from that licensee. SCO has sold its license for
UNIX software only to those who acquired a Linux operating system from someone
other than SCO"

The fact is that SCOG has imposed the same onerous "further
restrictions" both on those who acquired Linux from non-SCOG distributors
at $799 a pop, and on on SCOG's own customers "at no charge". These
onerous "further restrictions" violate the terms of the GPL, and I
doubt that anyone in his or her right mind wrote the GPL or any other EULA for
the sheer pleasure of watching them get violated with impunity. The
"sale" argument is a red herring.

[ Reply to This | # ]

SCO's Memo in Opposition to IBM's Motion for PSJ on CC for Copyright Infringement - as text
Authored by: blacklight on Saturday, December 04 2004 @ 07:29 AM EST
"In this case, given the absence of any such provision in the GPL, SCO did
not receive ''notice'' from IBM that it had alIegedly breached the GPL until IBM
filed its Eighth Counterclaim, on March 29, 2004. IBM thus not only asks the
Court to conclude that SCO forfeited its rights to copy and distribute IBM's
allegedly copyrighted material, but also asks the Court to declare retroactively
that SCO was obligated immediately to terminate that portion of its business
that relates to the copying and distribution of material licensed under the GPL,
upon SCO's supposed breach of the GPL of which IBM gave SCO no notice. SCO
submits that, under the foregoing standards, no such ''forfeiture'' could
apply." SCOG pleading

I don't believe that any "notice" is needed when the violation of the
terms of the GPL is deliberate and premeditated, Caldera was compliant with the
terms of the GPL until Darl the Snarl did his magic, and the GPL is written so
that a teen ager can understand the terms [1].

Fotnote 1: [1] there are some thorny issues that popped up and have turned the
resolution of these specific issues into a challenge, but none of these issues
are germane to any of SCOG's litigations.

[ Reply to This | # ]

Customers Only DLs violate GPL.
Authored by: darkonc on Saturday, December 04 2004 @ 10:23 AM EST
If SCO did notdistribute it's Linux software with all sources, then having a members-only website for download of the sources is a violation of the GPL.
From the GPL:
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
(emphasis mine).

If they actually intended to limit who could get copies of the source, then they're obviously not making it available to "any third party".

BLAM! ... One toe gone.

---
Powerful, committed communication. Touching the jewel within each person and bringing it to life..

[ Reply to This | # ]

Footnote 6
Authored by: Anonymous on Saturday, December 04 2004 @ 12:56 PM EST
Maybe it's just me, but there appears to be a disconnect between footnote 6, the
cases cited therein, and the proposition that SCO is trying to use them to
support.

Thoughts anybody?

Quatermass
IANAL IMHO etc

[ Reply to This | # ]

Did SCO also contribute code intentionally?
Authored by: sjgibbs on Saturday, December 04 2004 @ 03:39 PM EST
I understand that as long as SCO are in breach of the GPL IBM's claim has teeth.
SCO have argued that because they did not distribute the particular copy/version
of Linux used by their Linux IP Licensees the GPL does not prevent their
restriction of that third party's rights.

But didn't SCO, as Caldera, also contribute code deliberately to Linux, or else
to a wider audience (the public) that later included Linux?

Suppose Alice got her Linux CD from SCO and is OK by Darl, but Bob got his from
RedHat and that isn't OK by Darl. Now isn't Darl breaking the GPL by asking Bob
to sign a license restricting his use of RH Linux *which includes code
contributed by Caldera*.

Cutting it another way, SCO cannot claim to never have distributed anything to
Bob when Bobs CD includes Caldera on the contributors list. This being the case
as I understand it.

IANAL, nor a Linux guru, so may be wrong, but to me this might represent another
viable theory of breach.

In any case, I'd like for the precedant here to be that SCO's license is such a
squirm job that it should be considered to be *in effect* exactly what IBM claim
it is, since to allow otherwise makes a mockery of the relevant law.

SJG

[ Reply to This | # ]

And another neglected point - effect on contract claims
Authored by: Anonymous on Saturday, December 04 2004 @ 07:19 PM EST
One of IBM's bases for PSJ on SCO's contract claims 1-4. is that SCO has waived
any purported confidentiality requirement in any source code that IBM
contributed to Linux, by SCO distributing the very same source code itself to
Linux users.

It would seem to me, that SCO's claim that they have given (and intend to
continue giving) their own customers Linux source code in accordance with the
GPL, would provide some support for this particular IBM waiver argument.

Quatermass
IANAL IMHO etc

[ Reply to This | # ]

Maureen triumphant
Authored by: _Arthur on Sunday, December 05 2004 @ 04:49 PM EST
Maureen O'Gara called the shots 4 months early.

Because Judge Kimball gave SCO 2 months to answer CC8, it is only now that
SCO accuses IBM Corporation of FELONY, FRAUD and HaXXoring, as
anticipated.

How could she know ???

Because she sits on SCO's Propaganda Board ?

_Arthur

[ Reply to This | # ]

Let me get this straight
Authored by: bstone on Tuesday, December 07 2004 @ 06:22 AM EST
As of this filing, SCO is claiming that they have never contributed so much as a single line of code to Linux (someone who knows where the change logs are could perhaps look this up), while at the same time claiming that their contributions to Linux are worth more than three times the amount of Microsoft's contributions to Windows XP in a fair market ($699 vs. $199)?

[ 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 )