Do you remember how we laughed when SCO first announced its "Intellectual Property Compliance Licence for Linux" in August of 2003? You can read it in its original form on that linked page. I simply could not write about it seriously at the time. After mentioning some of what I considered the most egregious highlights of the license terms, I wrote: Far be it from me to tell anyone what to do, either SCO with its business, or anyone out there wanting to get one of these things. No doubt you have your attorney you can ask to advise you.
But, as long as we're getting misty eyed about rights, does anyone really want to be treated like this? SCO has brought that question to the fore, and speaking only for myself, I can't see how anything could highlight more plainly the difference between proprietary and free software than this case and this license do. Does it sound like both sides have rights, in an equitable arrangement of benefit to both parties, or does it read like a plea bargain deal? As you can see if you read the article, I thought it was ridiculous and I teased them about it. I couldn't imagine anyone paying good money for a SCOsource license. Then when EV1 actually took a license in March of 2004, we all wondered how in the world anyone could agree to a license that was, at a minimum, to our eyes out of conformity with the GPL in order to license something SCO hadn't proved it even owned. We were not alone in our puzzlement: George Weiss, an analyst at Gartner Inc. in Stamford, Conn., said some corporate Linux users will respond to SCO's posturing and sign similar licensing deals. "There's too much at stake in a worst-case scenario," Weiss said. But for other users, the decision will remain a matter of assessing their risk and looking at the ongoing case as it unfolds.
Weiss said that EV1Servers.net is taking a monetary risk by paying for a license before the case is decided. "I'm not sure why or how they came to that conclusion now," he said. Now we get to find out precisely why and how, and from none other than the victim himself, Robert Marsh, the CEO of EV1. He has been good enough to provide IBM with a declaration [PDF], Exhibit 224 of IBM's collection of 597 exhibits supporting its various summary judgement motions. It will knock your socks off to hear how the deal went down. We get to see the communications back and forth during the negotiations and we get to see the final Agreement, plus adjustments after things starting going sour, and he tells us how it felt to be ambushed by SCOsource, as he now clearly views it.
How did IBM get this declaration? I don't know, but I note on the list of exhibits that IBM deposed Mr. Marsh. I'm guessing they noted his unhappiness with the deal and just asked. A thank you to Groklaw volunteer feldegast for the OCR'd text of this Exhibit. I still had to type up a lot of the contract by hand, so if you find errors, let me know. Certain things were told to Marsh, according to his account, that were not true or were overstatements at least. And certain things were said to the media about the value of the deal that upset Marsh, because he viewed the statements as violations of the agreement, aside from being not true, in his eyes. As you will see, he paid a lot less than full price, after telling SCO if he paid full price, it would put him out of business. Part of the eventual deal was he had to do media interviews to talk up the license, for which he was able to negotiate a discount, and to induce him to sign, I note he was told he'd get lots of publicity. Heaven only knows that part came true, but it wasn't favorable publicity at all. SCO specifically mentioned that Forbes and Bloomberg would be very interested in talking to him if he signed. Blech. SCO also made representations about the terms of the BSDI settlement agreement. They also represented to him that there were many other licensees about to sign also, that their IP claims were "certain," and that he was about to face litigation if he didn't take a license. In short, he was terrified, he was concerned about his customers and wanted to protect them, he didn't know about Red Hat's various protections for Linux users, he believed SCO's representations (in part, I think, because he failed to read Groklaw, which wrote about all the various legal indemnification and defense funds -- note that the date is January, the same time general period when this deal was beginning to be negotiated, so that makes his lack of information a little easier to understand), and so he signed, only to regret it almost immediately. He relates that he lost customers and he was unhappy with SCO's behavior. It's a sorry tale. But on SCO's side, while they made representations to EV1, they would likely say that, short of fraud, it isn't their job to do EV1's due diligence. Fraud might actually be Marsh's precise thought, of course. And SCO got this paragraph put into the eventual license signed, which isn't in the original standard agreement language: SCO represents and warrants that it has full right and title to grant the rights hereunder to the SCO IP and related materials, and all copyrights, trade secret and other intellectual proprietary rights therein, are and remain the valuable property of SCO and its
suppliers. SCO makes no representations or guarantees concerning the outcome of any pending or potential litigation, as outlined above, regarding SCO's claims of violations of its IP or contractual rights in the Operating System. Licensee acknowledges that SCO's claims regarding its IP as it relates to the Operating System are being litigated in one or more cases, with possibly more litigation to follow, and that SCO has not guaranteed that it will ultimately prevail in any of this litigation. Licensee, to avoid any such litigation and to effectuate a productive and prompt resolution of any and all issues relating to use of SCO's IP, desires to obtain this license. Is that true, that part about SCO having full and unquestioned rights? SCO certainly knew that Novell was contesting SCO's ownership. And had Marsh read Groklaw, he could have known also, because we published the Novell-SCO correspondence. There are numerous other changes in the final agreement, many in EV1's favor or to accommodate the facts of its business, so while Marsh says he felt rushed and the whole deal was accomplished quickly -- negotiations began in late January or early February, he tells us, and the agreement was signed in early March -- he did take time, as he also relates in his declaration, to make changes. And he had a lawyer. The part no one can probably explain away would be the assertions regarding the BSDI settlement. At the time, it was not publicly available, because Groklaw didn't get the legal right to publish it until November of 2004, so even if EV1 had done thorough due diligence, there is no way they could have compared SCO's assertions with the agreement itself. I think you'll find it of interest to make that comparison yourself. And finally, after you read how EV1 got pressured, according to Marsh's account, ask yourself how true this line from the press release announcing the deal was: "The SCO IP licensing program was created in response to customer requests..." Clearly EV1 wasn't requesting it. Maybe SCO meant Microsoft. Joke. But if it's not Microsoft, then who? Who, with specificity, asked for SCOsource? It was only on reviewing these events from 2004 that I realized that it was at precisely this time period that SCO began attacking Groklaw in the media, pretending that they thought IBM was behind Groklaw. It's also when trolls and apparent shills showed up en masse leaving comments about alleged bias and how you couldn't trust Groklaw's conclusions. They still do that, of course, but what has time demonstrated? Now, for the first time, on reading Marsh's Declaration, I think I understand why SCO launched an antiGroklaw campaign just exactly then. I now believe they preferred folks like Mr. Marsh be kept in the dark as to his alternatives to a SCOsource license, or if they read things on Groklaw, to discount what they read. In fact, he was in the dark. He testifies that he didn't know before he signed on the dotted line that Red Hat had indemnification packages and money for legal defense that would have helped him and his customers. He doesn't even mention all the others available. He didn't know. Obviously, he wasn't reading Groklaw, because we told the world. And that is why we have endured 2 years of nonstop abuse and villification, because we told the world the whole story. Something else came to my mind on reading this declaration, and particularly in reading the signed agreement. I can see why Microsoft might have wanted Linux to be bound in licensing chains such as SCOsource represented, now that we have had a chance to read the perfectly extraordinary restrictive license terms for Vista. Microsoft would likely have known back then what it was planning in the way of tightening the screws on end users in its
Vista EULA [PDF], and the contrast with the freedom of Linux is stark. But if SCO could get Linux tied up in overbearing license terms, then the contrast wouldn't look so bad. Could that have been a factor? I don't know. But it occurred to me. Microsoft's backing has been alleged in Larry Goldfarb's Declaration, as well as in Michael Anderer's leaked memo, but it has yet to be proven in a court of law, and Microsoft has denied it. However, as I read the agreement, I said to myself that I could see why SCOsource might have appealed to a company about to release a product under the most stringent terms ever, terms no one would agree to if they had a viable choice, I don't think. And Linux is a viable choice. Finally, Marsh makes reference to some exhibits that we don't have. I don't know for sure if that is because we somehow cut them off when our script divided the one large PDF of all 597 exhibits into 597 individual PDFs, or if IBM neglected to attach them here. And with those musings, here is Robert Marsh's Declaration.
***********************************
EXHIBIT 224
1
SNELL & WILMER LLP.
Alan L. Sullivan (3152)
Todd M. Shaughnessy (6651)
Amy F. Sorenson (8947)
[Address]
[Phone]
[Fax]
CRAVATH, SWAINE & MOORE LLP
Evan R. Chesler (admitted pro hac vice)
David R. Marriott (7572)
[Address]
[Phone]
[Fax]
Attorneys for Defendant/Counterclaim-Plaintif
International Business Machines
Corporation
IN THE UNITED STATES DISTRICT COURT
FOR THE DISTRICT OF UTAH |
THE SCO GROUP, INC.
Plaintiff/Counterclaim-Defendant,
vs.
INTERNATIONAL BUSINESS
MACHINES CORPORATION,
Defendant/Counterclaim-Plaintiff. |
DECLARATION OF
ROBERT A. MARSH
Case No. 2:03CV-0294 DAK
Honorable Dale A. Kimball
Magistrate Judge Brooke C . Wells |
2
DECLARATION OF ROBERT A. MARSH
I, Robert A. Marsh, declare as follows:
1. This declaration is submitted in connection with the lawsuit entitled The SCO
Group Inc. v. International Business Machines Corperation, Civil No. 2:03CV-0294 DAK (D.
Utah 2003). Unless otherwise stated, I make this declaration based upon personal knowledge
and review of the documents referenced herein. This declaration is prepared in accordance with
the protective order in place in this case.
2. On October 6, 1998, I and two associates, Roy Marsh III and Randy Williams,
founded Everyones Internet, Inc., in Houston, Texas. Subsequently the operations of Everyones
Internet, Inc. were transferred to Everyones Internet, Ltd., a Texas limited partnership ("EV1").
I have served as the CEO of EV1 since its founding.
3. EVI began commercial operations on December 1, 1998. We are currently one of
the largest independent Internet service providers in the United States.
4. In 2000, we launched EV1's hosting division, EV1Servers.net. EV1Servers.net
offers users a choice of Windows and Linux operating systems. EV1Servers.net features Red
Hat Enterprise Linux as its primary Linux offering.
5. In late 2003, EV1Servers.net became the largest dedicated hosting provider in the
world measured by number of servers. Today, our total servers under management exceeds
20,000.
6. On December 19, 2003, we received a letter from The SCO Group's ("SCO")
general counsel, Ryan Tibbitts, a true and correct copy of which is attached hereto as Exhibit 1.
3
Mr. Tibbitts informed us that our "use of the Linux operating system" violated SCO's
copyrights.
7. on January 13, 2004, Philip Langer. SCO's Regional Director of Intellectual
Property Licensing, sent another letter to EV1, a true and correct copy of which is attached
hereto as Exhibit 2. Mr. Langer again informed us that our use of Linux violated SCO's
copyrights. He requested a meeting with EV1 to "discuss the alternatives that are available to
[EV1]" and to "propose solutions that will be agreeable and economically feasible for [EV1]."
Mr. Langer also threatened legal action against EV1 if we did not "pursue a licensing
arrangement" with SCO.
8. I contacted SCO in late January or early February 2004 to discuss possible ways
to address the violations asserted in SCO's two letters to us. I do not recall specifically with
whom I first spoke, but it was likely Mr. Langer, the individual at SCO with whom I dealt with
primarily. I also recall having a face-to-face meeting around this time with a number of SCO
representatives, including Mr. Langer, to discuss the possibilityof EV1 pursuing a licensing
arrangement with SCO.
9. Although Mr. Langer had stated in his January 13, 2004, letter that we would
discuss the alternatives and solutions available to EV1, Mr. Langer made it clear from the
beginning of our discussions that there was only one course that would satisfy SCO: EV1's
agreement to purchase a Linux license from SCO called SCOsource. There was not any
discussion of any alternative other than a SCOsource license or litigation.
10. In my initial conversations with Mr. Langer and others at SCO, I expressed a need
for further information concerning SCOsource before I could agree to anything. I recall
4
inquiring why EV1 needed to purchase a SCOsource license. Mr. Langer and others at SCO told
me that the Linux operating system contained code which infringed upon SCO's copyrights.
They further told me that the infringement was "pervasive" and "certain." They also told me that
the infringement was both "verbatim" and "derived."
11. In describing the infringement in Linux as pervasive, Mr. Langer and the others
never expressed any doubt as to the strength or certainty of their claims. The impression I
received was that it was only a matter of time before SCO would prevail in its lawsuits against
various Linux companies and users. They also told me that many other companies would be
sued in the immediate future.
12. Mr. Langer explained that because Linux was a derivative of UNIX EV1 needed
to purchase a Linux license from SCO in order to legally continue running Linux on the servers
managed by EV1Servers.net. They described the SCOsource license as a "Linux license' or a
"Linux IP license." For example, in a February 10, 2004, email to me, a true and correct copy of
which is attached hereto as Exhibit 3, Mr. Langer twice referred to the SCOsource license as a
"Linux IP license." At no time did they specify or describe to me the code in Linux that was
allegedly copied from or derived from UNIX. It was my understanding, based on the SCO
representatives' explanations, that SCOsource was a Linux license and that EV1 could not
legally run Linux on its servers without it.
13. I believed that if EV1 did not purchase a SCOsource license, SCO would likely
sue EV1 and/or its customers for copyright infringement. I was advised that SCO was in the
process of picking various types of Linux users to name as defendants and that, among the
possible targets, they were considering three hosting companies, including EV1. They told me
5
that they planned to initiate the lawsuits very soon. I believed that if EV1 did not purchase a
SCOsource license, EV1 was likely to be named in a lawsuit.
14. Mr. Langer or others representing SCO told me that a lawsuit against EV1 or our
customers could result in a temporary restraining order or an injunction mandating an immediate
shut-down of EV1Server.net's Linux servers. I take great pride in the consistency and
reliability of our hosting infrastructure, qualities for which EV1Servers.net are well-known in the
industry. A shut-down, or even the possibility of one, would have been severely damaging to
our hosting business. I felt pressure and urgency to avoid that outcome.
15. I was told by Mr. Langer or others at SCO that SCO had already signed up several
licensees, whose identities could not be disclosed because of confidentiality provisions. I was
further informed that numerous other Linux customer or users were entering into SCOSource
licensing arrangements, leading me to believe that EV1 ultimately would be just one of many
licensees.
16. In his February 10, 2004, email, Mr. Langer told me that by agreeing to a
SCOsource license, I could "expect EV1 to gain a great amount of exposure throughout the IT
trade publications as well as on Wall Street." (See Exhibit 3.)
17. Around early February 2004, I decided that EV1 should purchase a SCOsource
license to insulate EV1 and our customers from SCO's threats of litigation. I made a calculated
business decision based on the information provided by Mr. Langer and others at SCO
concerning the reasons that a license was necessary and the likely consequences to my business
of not purchasing one. I wanted to create a "safe haven" for our customers. The customers of
EV1Servers.net are primarily small and medium-sized businesses, who I believe would lack
6
sufficient resources to defend themselves in lawsuits brought by SCO. In agreeing to a
SCOsource license, I intended to provide certainty to my customers by ensuring them that they
would never have to worry about being sued by SCO.
18. SCO's explicit threats of a temporary restraining order or an injunction against
EV1 were also a factor in my decision. I wanted to eliminate the possibility that our hosting
infrastructure could be disrupted.
19. Negotiations over the terms of the license took place throughout February 2004.
The majority of negotiations concerned the license fee. In his February 10, 2004, email, Mr.
Langer informed me that the "list pricing" for the SCO license was "$699 per server processor
for a one time license fee and $140 per server processor for a 1-year license." (See Exhibit 3.)
At $699 per server processer, a one-time license covering all of our Linux servers would have
cost us several million dollars. I informed Mr. Langer that paying such a price would put us out
of business. (See Exhibit 3.)
20. In an email dated February 11, 2004, a true and correct copy of which is attached
hereto as Exhibit 4, Mr. Langer offered EV1 a discount at 75% of the list price.
21. In my response to Mr. Langer, I wrote, "Pricing is what we have substantial
problems with. As I don't want to ever have any potential issues with SCO, I feel it important to
have a 'company' license, rather than a per-unit." (See Exhibit 4). In a follow-up phone
conversation with Mr. Langer, we agreed that a fixed license fee would fully cover EV1,
regardless of the number of servers managed by EV1 Servers.net.
22. In his February 11, 2004, email to me, Mr. Langer also stated that SCO and EV1
would agree to the following: (i) SCO and EV1 would engage in joint marketing efforts; (ii) no
7
one within the employment of SCO or EV1 may make public comments regarding the agreement
except myself and a "single pre-determined named person at SCO;" (iii) final negotiations would
be confidential, except as required by federal law; (ii) no one within the employment of SCO or
EV1 "may reference the discounted amounts that were granted under the special pricing for
volume;" and (iv) I would agree to "participate in a joint press release and to assist in the
arrangement of interviews with at least 10 members of the press." (See Exhibit 4.)
23. Mr. Langer and another representative at SCO offered a net license fee of
$800,000 that would reflect a volume discount and a substantial promotional discount for certain
efforts to be undertaken by EV1 and SCO to publicize EV1's agreement with SCO. The specific
promotional efforts were to be set forth in detail in the license agreement. I agreed to the
$800,000 net license fee.
24. In late February 2004, we commenced the drafting of the license agreement. By
email dated February 20, 2004, a true and correct copy of which is attached hereto as Exhibit 5,
Mr. Langer sent a proposed SCOsource contract to my attorney, Eric Schaeffer.
25. Bill Broderick, SCO's Director of Software Licensing, and Mr. Schaeffer were
primarily responsible for drafting the license agreement. I was copied on some of their
correspondence and occasionally reviewed the various drafts and suggested or approved certain
changes to the contractual language.
26. On February 29, 2004, I reviewed and approved the final agreement for execution
("the Agreement").
8
27. On March 1, 2004, I signed the Agreement on behalf of EV1. The same day,
Chris Sontag signed the Agreement on behalf of SCO. A true and correct copy of the Agreement
is attached hereto as Exhibit 6.
28. A $600,000 Licensee Promotional Allowance was granted by SCO for my
agreement to participate in a "mutually agreed upon advertising campaign related to this
Agreement, specifically excluding any pricing related information." (See Exhibit 6.)
29. The promotional activities to which I agreed include: (i) issuing a joint press
release; (ii) favorably discussing the benefits of the Agreement in mutually agreed-to interviews,
including providing SCO with an executive quote or endorsement for SCO's press releases; (iii)
allowing SCO to "write up a success story for its web site and press usage;" (iv) agreeing to talk
with the media about SCOsource and (v) agreeing to commence within 30 days of the
Agreement an advertising campaign for national and international publications, with each party
reserving the right to approve any advertisements prior to distribution. (See Exhibit 6.)
30. The Agreement requires the joint agreement of SCO and EV1 to any press
releases and other publicity relating to the Agreement. The Agreement also requires that SCO
obtain EV1's prior approval for the content of any references in the press by SCO to EV1 as a
SCOsource licensee. (See Exhibit 6.) These provisions were specifically included in the
Agreement so that I could retain control over SCO's statements to the media regarding our
purchase of a SCOsource license.
31. On March 1, 2004, SCO issued a joint press release announcing EV1's purchase
of a SCOsource license, a true and correct copy of which is attached hereto as Exhibit 7.
9
32. As required by the Agreement, I provided a quote or endorsement which was
contained in the March 1, 2004, press release. I stated, "The SCO agreement eliminates
uncertainty from our clients' hosting infrastructure. Our current and future users now enjoy the
peace of mind of knowing that their websites and data are hosted on a SCO IP compliant
platform. This agreement demonstrates EV1's commitment to providing customers with stable,
long-term solutions that they can depend on for their growth." (See Exhibits 6 and 7.) I also
considered my statement to be a favorable discussion of the benefits of the Agreement to EV1
and our customers, consistent with the requirements of the Promotional Allowance. (See Exhibit
6.)
33. In the March 1, 2004, joint press release, Darl McBride of SCO stated, "We know
(our intellectual property] has tremendous value and are pleased that other companies -- like
EV1Servers.Net -- recognize our investment and the importance of SCO's valuable IP asset as
well." (See Exhibit 7.)
34. I was given a brief opportunity to review the joint press release before it was
issued, but did not fully consider Mr. McBride's statement before giving my approval. Mr.
McBride's statement was a mischaracterization of our decision. During negotiations, I told
Mr. Langer that my decision was based solely on business considerations. There was never any
understanding on my part that EV1 was endorsing the validity of SCO's copyright claims.
35. Within an hour of the issuance of the March 1, 2004, press release, I began to
receive criticism from my customers over my decision to purchase a license from SCO. Many of
my customers considered EV1's payment for the license tantamount to funding SCO's litigation
efforts and its attack on Linux. The criticism intensified over the ensuing weeks. We received
10
hate-mail from people interpreting our agreement as validating or endorsing SCO. We were
accused of betraying our customers and aligning ourselves with a company considered to be the
enemy of the open source community. Some of our customers threatened to, and did, leave
EV1Servers.net.
36. I did not anticipate the overwhelmingly negative response from our customer
base. In agreeing to purchase the SCOsource license, I believed that I was serving the interests
of our customers by shielding them from SCO's threats of litigation. Ironically, although my
intention was to take EV1 and our customers out of the fray, my decision resulted in EV1 being
placed at the center of it. As reported in a March 25, 2004, article in InfoWorld, a true and
correct copy of which is attached hereto as Exhibit 8, I stated, "All of a sudden we went from
being reasonably good guys to being, in some people's eyes, akin to the devil."
37. On March 2, 2004, I posted a letter to my customers on the EV1Servers.net
website, explaining my decision and addressing the characterization by Mr. McBride and our
customers that we were endorsing SCO's claims. A true and correct copy of my letter is attached
hereto as Exhibit 9. I wrote, "We make no endorsement of SCO nor do we make any admission
as to their claims." (Id.) That sentence was immediately and widely reported in the press. True
and correct copies of two articles quoting the sentence are attached hereto as Exhibit 10.
39. I also took issue with SCO's repeated public statements concerning the amount of
EV1's license fee. I consider such statements to be in violation of our agreement. The
agreement concerning the promotional campaign "specifically exclude[ed] any pricing related
information." (See Exhibit 6.) Moreover, on February 11, 2004, Mr. Langer stated that "(n)o
one within SCO or EV1 may reference discounted amounts that were granted under the special
11
pricing for volume." (See Exhibit 4.) Mr. Langer and Blake Stowell, SCO's Public Relations
Director, also made verbal assurances as we were finalizing the Agreement that the pricing
information would remain confidential.
39. Nonetheless, I learned that SCO was repeatedly providing inaccurate or
misleading information to the press concerning the amount of the license fee. As reported in a
March 1, 2004, article in internetnews.com, a true and correct copy of which is attached hereto as
Exhibit 11, Mr. Stowell suggested that the license fee was "worth at least $1 million." In a
March 2, 2004, article in Linux Pipeline, a true and correct copy of which is attached hereto as
Exhibit 12, Mr. Stowell is quoted as stating that the deal was worth "north of seven figures" to
SCO. In a March 4, 2004, article in Netcraft, a true and correct copy of which is attached hereto
as Exhibit 13, Mr. Stowell is quoted as stating that EV1Servers.net "didn't pay full retail price on
each server, but the deal was still worth seven figures all together for SCO."
40. As reported in the March 4, 2004, Netcraft article, I stated, "I would discount any
reports or quotes of a 7 figure cash payment as has been reported. We did agree to a one time
payment, however we did not agree to pay a 7 figure cash payment as reported in the media."
(See Exhibit 13.)
41. Of course, the Agreement clearly indicates, and there is no dispute, that EV1
agreed to pay $800,000, factoring in the promotional discount. SCO never claimed that EV1 had
forfeited the promotional discount. (See Exhibit 6.)
42. Although SCO agreed that no one at SCO or EV1 except myself and a "single
pre-determined named person at SCO" would be permitted to discuss the Agreement in the press
12
(see Exhibit 4) both Mr. Stowell and Mr. McBride made numerous public statements concerning
the Agreement.
43. On March 25, 2004, I stated publicly that I regretted my decision to purchase a
SCOsource license. As reported in various publications, I stated, "Would I do it again? No. I'll
go on the record as saying that. I certainly know a lot more today than I knew a month ago, in a
lot of respects." (See e.g. Exhibit 8.)
44. I affirm my statement that I would not have purchased a SCOsource license if I
had another chance to make my decision. I learned many things after I signed the Agreement
that would have changed my decision. SCO advised me that they had evidence of pervasive
infringement in Linux and that the evidence was certain. I was told that a lawsuit against us was
likely and imminent. I felt rushed to make a decision. I also learned that there were not
numerous licensees as SCO had led me to believe, but that EV1 was one of only a handful of
licensees.
45. At the time, I was not aware of alternatives to SCOsource. However, after
executing the Agreement, I learned that in late January 2004, Red Hat announced that it would
protect its end users by guaranteeing that it would replace any code found to be infringing. Red
Hat also established an "Open Source Now Fund" to assist its users with legal expenses resulting
from their use of Linux. I believe that Red Hat's protections would have applied to the
customers of EV1Servers.net who rely on Red Hat Enterprise Linux. Had I been aware of the
"Open Source Now Fund" at the time, I would probably have considered refusing to sign the
Agreement, especially because a major factor in my decision was my concern that our customers
would not be able to afford legal expenses to defend a lawsuit by SCO.
13
46. After learning of SCO's public comments regarding the confidential pricing terms
of the license, I told Mr. Langer that I believed SCO's disclosures violated the Agreement and
that EV1 was considering terminating the Agreement. In order to satisfy EV1's concerns, the
parties entered into an amendment to the Agreement. On June 7, 2004, I executed on behalf of
EV1 Amendment No. One, a true and correct copy of which is attached hereto as Exhibit 14.
Amenchnent No. One revised the promotional obligation of EV1 to allow full credit for the
Promotional Allowance if EV1 included an Intellectual Property compliant message, such as "IP
Compliant," in connection with its print advertising. Amendment No. One also extended the
fixed license fee payment terms through December 2005. The parties extended the payment
terms through December 2006 by a subsequent amendment.
47. 1 declare under penalty of perjury under the laws of the United States of America
that the foregoing is true and correct.
Executed: April 5, 2006
Houston, Texas.
_______Signature____
Robcrt A. Marsh
14
EXHIBIT 1
15
[SCO logo]
December 19, 2003
Randell Williams
CTO
RadioShack
[Address]
Re: The SCO Group, Inc. ("SCO")
Unix Licensee,
In May 2003, SCO warned about enterprise use of the Linux operating system in
violation of its intellectual property rights in UNIX technology. Without exhausting or
explaining all potential claims, this letter addresses one specific area in which certain
versions of Linux violate SCO's rights in UNIX.
In this letter we are identifying a portion of our copyright protected code that has
been incorporated into Linux without our authorization. Also, our copyright management
information has been removed from these files. These facts support our position that the
use of the Linux operating system in a commercial setting violates our rights under the
United States Copyright Act, including the Digital Millennium Copyright Act. We are
notifying you of these facts so you can take steps to discontinue these violations. We
believe these violations are serious, and we will take appropriate actions to protect our
rights. No one may use our copyrighted code except as authorized by us. The details of
our position are set forth below. Once you have reviewed our position, we will be happy
to further discuss your options and work with you to remedy this problem.
Certain copynghted application binary interfaces ("ABI Code") have been copied
verbatim from the UNIX System V code base and contributed to Linux for distribution
under the General Public License ("GPL") without proper authorization and without
copyright attribution. While some application programming interfaces ("API Code")
have been made available over the years through POSIX and other open standards, the
UNIX System V ABI Code has only been made available under copyright restrictions.
AT&T made these binary interfaces available in order to support application
development to System V-based operating systems and to assist System V licensees. in
the development process. The System V ABI were never intended or authorized for
unrestricted use or distribution under the GPL in Linux. As the copyright holder, SCO
has never granted such permission. Nevertheless, many of the ABIs contained in Linux,
and improperly distributed under the GPL, are direct copies of UNIX System V
copyrighted software code.
Any part of any Linux file that includes the copyrighted binary interface code
must be removed. Files in Linux version 2.4.21 and other versions that incorporate the
copyrighted binary interfaces include:
16
include/asm-alpha/errno.h
include/asm-arm/errno.h
include/asm-cris/errno.h
include/asm-i386/errno.h
include/asm-ia64/errno.h
include/asm-m68k/errno.h
include/asm-mips/errno.h
include/asm-mips64/errno.h
include/asm-parisc/errno.h
include/asm-ppc/errno.h
include/asm-ppc64/errno.h
include/asm-s390/errno.h
include/asm-s390x/errno.h
include/asm-sh/errno.h
include/asm-sparc/errno.h
include/asm-sparc64/errno.h
include/asm-x86_64/errno.h
include/asm-alpha/signal.h
include/asm-arm/signal.h
include/asm-cris/signal.h
include/asm-i386/signal.h
include/asm-ia64/signal.h
include/asm-m68k/signal.h
include/asm-mips/signal.h
include/asm-mips64/signal.h
include/asm-parisc/signal.h
include/asm-ppc/signal.h
include/asm-ppc64/signal.h
include/asm-s390/signal.h
include/asm-s390x/signal.h
include/asm-sh/signal.h
include/asm-sparc/signal.h
include/asm-sparc64/signal.h
include/asm-x86_64/signal.h
include/linux/stat.h
include/linux/ctype.h
lib/ctype.c
include/asm-alpha/ioctl.h
include/asm-alpha/ioctls.h
include/asm-arm/ioctl.h
include/asm-cris/ioctl.h
include/asm-i386/ioctl.h
include/asm-ia64/ioctl.h
include/asm-m68k/ioctl.h
include/asm-mips/ioctl.h
include/asm-mips64/ioctl.h
include/asm-mips64/ioctls.h
include/asm-parisc/ioctl.h
include/asm-parisc/ioctls.h
include/asm-ppc/ioctl.h
include/asm-ppc/ioctls.h
include/asm-ppc64/ioctl.h
include/asm-ppc64/ioctls.h
include/asm-s390/ioctl.h
include/asm-s390x/ioctl.h
include/asm-sh/ioctl.h
include/asm-sh/ioctls.h
include/asm-sparc/ioctl.h
include/asm-sparc/ioctls.h
include/asm-sparc64/ioctl.h
include/asm-sparc64/ioctls.h
include/asm-x86_64/ioctl.h
include/linux/ipc.h
include/linux/acct.h
include/asm-sparc/a.out.h
include/linux/a.out.h
arch/mips/boot/ecoff.h
include/asm-sparc/bsderrno.h
include/asm-sparc/solerrno.h
include/asm-sparc64/bsderrno.h
include/asm-sparc64/solerrno.h
The code identified above was also part of a settlement agreement between the University of California at Berkeley and Berkeley Systems Development, Inc. (collectively "BSDI") and UNIX Systems Laboratories, Inc. regarding alleged violations by BSDI of USL's rights in UNIX technology. The settlement agreement between USL and BSDI addressed conditions upon which BSDI could continue to distribute its version of UNIX, BSD Lite 4.4, or any successor versions. One condition was that BSD retain USL copyrights in 91
17
files (the "UNIX Derived Files"). A complete listing of the UNIX Derived Files is attached. The ABI Code identified above are part of the UNIX Derived Files and, as such, must carry USL/SCO copyright notices and may not be used in any GPL distribution, inasmuch as the affirmative consent of the copyright holder has not been obtained, and will not be obtained, for such a distribution under the GPL.
Use in Linux of any ABI Code or other UNIX Derived Files identified above constitutes a violation of the United States Copyright Act. Also, distribution of the copyrighted code identified above as part of a source or binary distribution of Linux, with copyright management information deleted or altered, violates the Digital Millennium Copyright Act (“DMCA”) codified by Congress at 17 U.S.C.§1202. DMCA liability extends to those who have reasonable grounds to know that a distribution (or re-distribution as required by the GPL) of the altered code or copyright information will induce, enable, facilitate, or conceal an infringement of any right under the DMCA. In addition, neither SCO nor any predecessor in interest has ever placed an affirmative notice in Linux that the copyrighted code in question could be used or distributed under the GPL. As a result, any distribution of Linux by a software vendor or a re-distribution of Linux by an end user that contains any of the identified UNIX code violates SCO's rights under the DMCA, insofar as the distributor knows of these violations.
As stated above, SCO's review is ongoing and will involve additional disclosures of code misappropriation. Certain UNIX code, methods and concepts, which we also claim are being used improperly in Linux, will be produced in the pending litigation between SCO and IBM under a confidentiality order.
Thank you for your attention to these matters.
Sincerely,
THE SCO GROUP, INC.
By: ____[Signature]_____
Ryan E. Tibbits
General Counsel
18
[SCO logo]
December 19, 2003
Randall Williams
CTO
EVERYONES INTERNET
[Address]
Re: The SCO Group, Inc. ("SCO")
Unix Licensee,
In May 2003, SCO warned about enterprise use of the Linux operating system in
violation of its intellectual property rights in UNIX technology. Without exhausting or
explaining all potential claims, this letter addresses one specific area in which certain
versions of Linux violate SCO's rights in UNIX.
In this letter we are identifying a portion of our copyright protected code that has
been incorporated into Linux without our authorization. Also, our copyright management
information has been removed from these files. These facts support our position that the
use of the Linux operating system in a commercial setting violates our rights under the
United States Copyright Act, including the Digital Millennium Copyright Act. We are
notifying you of these facts so you can take steps to discontinue these violations. We
believe these violations are serious, and we will take appropriate actions to protect our
rights. No one may use our copyrighted code except as authorized by us. The details of
our position are set forth below. Once you have reviewed our position, we will be happy
to further discuss your options and work with you to remedy this problem.
Certain copynghted application binary interfaces ("ABI Code") have been copied
verbatim from the UNIX System V code base and contributed to Linux for distribution
under the General Public License ("GPL") without proper authorization and without
copyright attribution. While some application programming interfaces ("API Code")
have been made available over the years through POSIX and other open standards, the
UNIX System V ABI Code has only been made available under copyright restrictions.
AT&T made these binary interfaces available in order to support application
development to System V-based operating systems and to assist System V licensees in
the development process. The System V ABI were never intended or authorized for
unrestricted use or distribution under the GPL in Linux. As the copyright holder, SCO
has never granted such permission. Nevertheless, many of the ABIs contained in Linux,
and improperly distributed under the GPL, are direct copies of UNIX System V
copyrighted software code.
Any part of any Linux file that includes the copyrighted binary interface code
must be removed. Files in Linux version 2.4.21 and other versions that incorporate the
copyrighted binary interfaces include:
19
include/asm-alpha/errno.h
include/asm-arm/errno.h
include/asm-cris/errno.h
include/asm-i386/errno.h
include/asm-ia64/errno.h
include/asm-m68k/errno.h
include/asm-mips/errno.h
include/asm-mips64/errno.h
include/asm-parisc/errno.h
include/asm-ppc/errno.h
include/asm-ppc64/errno.h
include/asm-s390/errno.h
include/asm-s390x/errno.h
include/asm-sh/errno.h
include/asm-sparc/errno.h
include/asm-sparc64/errno.h
include/asm-x86_64/errno.h
include/asm-alpha/signal.h
include/asm-arm/signal.h
include/asm-cris/signal.h
include/asm-i386/signal.h
include/asm-ia64/signal.h
include/asm-m68k/signal.h
include/asm-mips/signal.h
include/asm-mips64/signal.h
include/asm-parisc/signal.h
include/asm-ppc/signal.h
include/asm-ppc64/signal.h
include/asm-s390/signal.h
include/asm-s390x/signal.h
include/asm-sh/signal.h
include/asm-sparc/signal.h
include/asm-sparc64/signal.h
include/asm-x86_64/signal.h
include/linux/stat.h
include/linux/ctype.h
lib/ctype.c
include/asm-alpha/ioctl.h
include/asm-alpha/ioctls.h
include/asm-arm/ioctl.h
include/asm-cris/ioctl.h
include/asm-i386/ioctl.h
include/asm-ia64/ioctl.h
include/asm-m68k/ioctl.h
include/asm-mips/ioctl.h
include/asm-mips64/ioctl.h
include/asm-mips64/ioctls.h
include/asm-parisc/ioctl.h
include/asm-parisc/ioctls.h
include/asm-ppc/ioctl.h
include/asm-ppc/ioctls.h
include/asm-ppc64/ioctl.h
include/asm-ppc64/ioctls.h
include/asm-s390/ioctl.h
include/asm-s390x/ioctl.h
include/asm-sh/ioctl.h
include/asm-sh/ioctls.h
include/asm-sparc/ioctl.h
include/asm-sparc/ioctls.h
include/asm-sparc64/ioctl.h
include/asm-sparc64/ioctls.h
include/asm-x86_64/ioctl.h
include/linux/ipc.h
include/linux/acct.h
include/asm-sparc/a.out.h
include/linux/a.out.h
arch/mips/boot/ecoff.h
include/asm-sparc/bsderrno.h
include/asm-sparc/solerrno.h
include/asm-sparc64/bsderrno.h
include/asm-sparc64/solerrno.h
The code identified above was also part of a settlement agreement between the University of California at Berkeley and Berkeley Systems Development, Inc. (collectively "BSDI") and UNIX Systems Laboratories, Inc. regarding alleged violations by BSDI of USL's rights in UNIX technology. The settlement agreement between USL and BSDI addressed conditions upon which BSDI could continue to distribute its version of UNIX, BSD Lite 4.4, or any successor versions. One condition was that BSD retain USL copyrights in 91
20
files (the "UNIX Derived Files"). A complete listing of the UNIX Derived Files is attached. The ABI Code identified above are part of the UNIX Derived Files and, as such, must carry USL/SCO copyright notices and may not be used in any GPL distribution, inasmuch as the affirmative consent of the copyright holder has not been obtained, and will not be obtained, for such a distribution under the GPL.
Use in Linux of any ABI Code or other UNIX Derived Files identified above constitutes a violation of the United States Copyright Act. Distribution of the copyrighted ABI Code, or binary code compiled using the ABI code, with copyright management information deleted or altered, violates the Digital Millennium Copyright Act (“DMCA”) codified by Congress at 17 U.S.C. §1202. DMCA liability extends to those who have reasonable grounds to know that a distribution (or re-distribution as required by the GPL) of the altered code or copyright information will induce, enable, facilitate, or conceal an infringement of any right under the DMCA. In addition, neither SCO nor any predecessor in interest has ever placed an affirmative notice in Linux that the copyrighted code in question could be used or distributed under the GPL. As a result, any distribution of Linux by a software vendor or a re-distribution of Linux by an end user that contains any of the identified UNIX code violates SCO's rights under the DMCA, insofar as the distributor knows of these violations.
As stated above, SCO's review is ongoing and will involve additional disclosures of code misappropriation. Certain UNIX code, methods and concepts, which we also claim are being used improperly in Linux, will be produced in the pending litigation between SCO and IBM under a confidentiality order.
Thank you for your attention to these matters.
Sincerely,
THE SCO GROUP, INC.
By: ____[Signature]_____
Ryan E. Tibbits
General Counsel
21
EXHIBIT 2
22
[SCO logo]
January 13, 2004
Randell Williams
CTO
RadioShack
[Address]
Dear Mr. Williams:
I am following up on the SCO letter dated December 19th, regarding the use of SCO copyright
protected code that has been incorporated into Linux without our authorization. As stated in the letter:
"No one may use our copyrighted code except as authorized by us.
...Certain copyrighted application binary interfaces ("ABI Code") have been copied verbatim from
our copyrighted UNIX code base and oontributed to Linux for distribution under the General Public
License ("GPL") without proper authorization and without copyright attribution. While some application
programming interfaces ("API Code") have been made available over the years through POSIX and other
open standards, the UNIX ABI Code has only been made avalable under copyright restrictions. AT&T
made these binary interfaces available in order to support application-development to UNIX operating
systems and to assist UNIX licensees in the development process. The UNIX ABIs were never
intended or authorized for unrestricted use or distribution under the GPL in Linux
....Use in Linux of any ABI Code or other UNIX Derived Files identified above constitutes a violation of the United States Copyright Act. Distribution of the copyrighted ABI Code, or binary code compiled using the ABI code, with copyright management information deleted or altered, violates the Digital Millennium Copyright Act (“DMCA”) codified by Congress at 17 U.S.C. §1202. DMCA liability extends to those who have reasonable grounds to know that a distribution (or re-distribution as required by the GPL) of the altered code or copyright information will induce, enable, facilitate, or conceal an infringement of any right under the DMCA. In addition, neither SCO nor any predecessor in interest has ever placed an affirmative notice in Linux that the copyrighted code in question could be used or distributed under the GPL. As a result, any distribution of Linux by a software vendor or a re-distribution of Linux by an end user that contains any of the identified UNIX code violates SCO's rights under the DMCA, insofar as the distributor knows of these violations."
I am requesting a meeting so that we may discuss the alternatives that are available to your firm. WE
BELIEVE WE CAN PROPOSE SOLUTIONS THAT WILL BE AGREEABLE AND ECONOMICALLY
FEASIBLE FOR YOU. I look forward to hearing from you. If you fail to respond to our efforts to pursue a
licensing arrangement, WE WILL TURN YOUR NAME OVER TO OUR OUTSIDE COUNSEL FOR
CONSIDERATION OF LEGAL ACTION.
Please contact me immediately so we may schedule a meeting. My telephone number is [redacted]
or email [redacted].
Yours truly,
Philip Langer
Regional Director, Intellectual Licensing
SCO
Encl: Letter December 19, 2003
Cc: Ryan E. Tibbitts, SCO General Counsel
23
EXHIBIT 3
24
----- Original Message -----
From: Philip Langer [mailto:[redacted]]
Sent: Tuesday, February 10, 2004 6:19 PM
To: [redacted]@ev1.net
Subject: SCO IP License
Robert,
I tried sending this to [redacted]@ev1.net and it got kicked back should I continue using the
[redacted] address.
Before I can send out a formal proposal, I want to be sure that you and I are on the same page.
We concur that a joint marketing position will benefit both EV1 and SCO. We are confident that
Forbes and Bloomberg will be quite anxious to speak with you (I suspect that you will receive
more requests for interviews than initially perceived.). You can expect EV1 to gain a great
amount of exposure throughout the IT trade publications as well as on Wall Street. It is also
understood that with any type of marketing alliance, only Robert Marsh and authorized SCO
personnel (as agreed by EV1) may comment on any agreement. Is this the type of public
marketing/exposure that EV1 is looking for?
As far as pricing goes, the list pricing for SCO's IP License is $699 per server processor for a one
time license fee and $140 per server processor for a 1-year license. Obviously, this list pricing is
for all general licenses of our Linux IP license. Thus for a customer of EV1's size, lets just
estimate 10,000 server processors -- the list price for a one-time Linux IP license would be
6,999,000 and 1,400,000 for a one-year agreement. This is not the price I am proposing to EV1;
however this is the value that SCO puts on its IP that is in use in Linux. As per our conversation
on Monday, I do understand that the hosting business is a small margin business; thus with a
requirement for a site license I would like to know what type of discounts do you typically
25
request from your vendors?
Regards,
Philip Langer
Regional Director
SCO Intellectual Property Licensing
The SCO Group Inc (NASDAQ: SCOX)
[address]
[phone]
[email address]
This e-mail message and any attachments are confidential and may be
privileged If you are not the intended recipient, please notify me
immediately by replying to this message and please destroy all copies of
this message and attachments. Thank you
26
EXHIBIT 4
27
From: Robert Marsh [email address redacted]
Sent: Tuesday, February 10, 2004 7:38 PM
To: 'Philip Langer'
Cc: [email address redacted]
Subject: RE: SCO IP License
I forgot.. my apologies as it has been a VERY tough day.
We are on the same page with regard to the concept. I do realize that SCO has set the pricing as they have but I
think it better for these discussion no to dwell on conceptual issues. Once we have an agreement, I'll "tote the
company line".
The numbers you mention are just not affordable for us. At that point, we'd be paying you even more than we pay
Red Hat.... Substantially more .... Mucho mucho mucho more. I know you have your point with that as well.
I just can't afford millions of dollars. It would put us out of the hosting business which doesn't make sense for
anyone especially my 2 year old who will some day want daddy to buy him a Ferrari. [smiley face]
You guys seem like the type that we can get a deal done with. I think we have some of the same goals.
I look forward to hearing back from you.
My new cell.. [phone number].
Robert
----- Original Message -----
From: Philip Langer [mailto:[email address redacted]]
Sent: Tuesday, February 10, 2004 6:19 PM
To: [email address]
Subject: SCO IP License
Robert,
I tried sending this to [redacted]@ev1.net and it got kicked back should I continue using the
[redacted] address.
Before I can send out a formal proposal, I want to be sure that you and I are on the same page.
We concur that a joint marketing position will benefit both EV1 and SCO. We are confident that
Forbes and Bloomberg will be quite anxious to speak with you (I suspect that you will receive
more requests for interviews than initially perceived.). You can expect EV1 to gain a great
amount of exposure throughout the IT trade publications as well as on Wall Street. It is also
understood that with any type of marketing alliance, only Robert Marsh and authorized SCO
personnel (as agreed by EV1) may comment on any agreement. Is this the type of public
marketing/exposure that EV1 is looking for?
As far as pricing goes, the list pricing for SCO's IP License is $699 per server processor for a one
time license fee and $140 per server processor for a 1-year license. Obviously, this list pricing is
for all general licenses of our Linux IP license. Thus for a customer of EV1's size, lets just
estimate 10,000 server processors -- the list price for a one-time Linux IP license would be
6,999,000 and 1,400,000 for a one-year agreement. This is not the price I am proposing to EV1;
however this is the value that SCO puts on its IP that is in use in Linux. As per our conversation
on Monday, I do understand that the hosting business is a small margin business; thus with a
requirement for a site license I would like to know what type of discounts do you typically
28
request from your vendors?
Regards,
Philip Langer
Regional Director
SCO Intellectual Property Licensing
The SCO Group Inc (NASDAQ: SCOX)
[address]
[phone]
[email address]
This e-mail message and any attachments are confidential and may be
privileged If you are not the intended recipient, please notify me
immediately by replying to this message and please destroy all copies of
this message and attachments. Thank you
29
EXHIBIT 5
30
From: Philip Langer [email address redacted]
Sent: Friday, February 20, 2004 1:40 PM
To: [eshaeffer@email address of attorney redacted]
Cc: [email address redacted@ev1.net]; [email address redacted@sco.com]; bill Broderick
Subject: SCO Contract
Eric,
I have included an electronic version of the SCO contract for your review. Please feel free to direct any
of the contract questions to Bill Broderick, I have provided his contact information below.
SCO contracts contact
Bill Broderick
[Phone]
[email address]
If you have any further question I can be reached at [phone number redacted] throughout the weekend.
Regards,
Philip Langer
Regional Director - Intellectual Property Licensing
The SCO Group Inc (NASDAQ: SCOX)
[address]
[phone]
[email address]
This e-mail message and any attachments are confidential and may be
privileged. If you are not the intended recipient, please notify me
immediately by replying to this message and please destroy all copies of
this message and attachments. Thank you
31
Draft - For review and discussion purposes - SCO Legal will provide executable documents.
THE SCO GROUP, INC.
INTELLECTUAL PROPERTY LICENSE
This Intellectual Property License Agreement ("Agreement") is made and entered into on the date last executed
below by and between The SCO Group, Inc., a corporation of the State of Delaware, for itself and its Subsidiaries
(collectively referred to herein as "SCO"), with its place of business at [redacted], Lindon,
Utah 84042, U.S.A., and Everyones Internet EV1, a corporation of the State of Texas, (referred to herein as
"Licensee"), with its place of business at [address redacted] Texas 77098.
WHEREAS, SCO owns all right, title and interest in and to certain SCO intellectual property (as hereinafter
defined); and
WHEREAS, Licensee is in the business of providing hosting services through its hosting centers; and
WHEREAS, SCO wishes to grant and Licensee wishes to obtain certain limited rights and licenses to use SCO IP,
which rights Licensee wishes to accept, all in accordance with the terms and conditions hereinafter set forth;
NOW, THEREFORE, in consideration of the mutual promises made herein it is agreed as follows:
1.0 DEFINITIONS
1.1 "Code" shall mean computer programming instructions.
1.2 "CPU " means a single physical computer processor.
1.3 "Customer" means those entities who purchase hosting services from Licensee's through Licensee's
hosting center.
1.4 "Desktop System" means a single user computer workstation controlled by a single instance of the
Operating System. It may provide personal productivity applications, web browsers and other client
interfaces (e.g., mail, calendering, instant messaging, etc). It may not host services for clients on
other systems.
1.5 "General Purpose Computer System" means a commercially available system which is intended to be
reprogrammable by the end user and is either (i) intended for primary use as a general purpose
business computer, a personal computer, or a scientific/technical workstation; or (ii) part of a network
configuration whose primary purpose is for executing general application programs supporting
general business, personal, or scientific/technical activities.
1.6 "Method" means the human or machine methodology for, or approach to, design, structure,
modification, upgrade, de-bugging, tuning, improvement or adaptation of Code.
1.7 "Object Code" means the Code that results when Source Code is processed by a software compiler
and is directly executable by a computer.
1.8 "Operating System" means software operating system Code (or Code that substantially performs the
functions of an operating system) that is a distribution, rebranding, modification or derivative work
of the Linux operating system.
1.9 "Point of Sale/Embedded System" means a computer system, controlled by a single instance of the
Operating System, that can not be used as a General Purpose Computer System and, as such, is (1)
restricted in normal use to the execution of a predefined set of special purpose applications, and (2)
does not allow an end user, directly or indirectly, to (i) add or run general purpose application
software; (ii) add or administer users; or (iii) provide system administration functions other than
diagnostics and maintenance.
1.10 "SCO IP" means the SCO intellectual property included in its UNIX-based Code in Object Code
format licensed by SCO under SCO's standard commercial license.
1.11 "Software" means the Operating System in Object Code format.
Page 1 of 6
SCO Intellectual Property License
Contract No. EV12004IP
CONFIDENTIAL
32
Draft - For review and discussion purposes - SCO Legal will provide executable docuinents.
1.12 "Source Code" means the human-readable form of the Code and related system documentation,
including all comments and any procedural language.
1.13 "System" means a computer system, containing the licensed CPUs, controlled by a single instance of
the Operating System.
1.14 "UNIX-based Code" means any Code or Method that: (i) in its literal or non-literal expression,
structure, format use, functionality or adaptation (ii) is based on, developed in, derived from or is
similar to (iii) any Code contained in or Method devised or developed in (iv) UNIX System V or
UnixWare, or (v) any modification or derivative work based on or licensed under UNIX System V
or UnixWare.
1.15 "Update" means the updates or revisions in Object Code format of the Software that You may receive.
Update shall not include any alteration, modification or derivative work of the Operating System
prepared by You.
2.0 GRANT OF RIGHTS
2.1 SCO hereby grants Licensee and Licensee hereby accepts from SCO the following limited, non-exclusive, non-transferable right and license to use SCO IP, for its internal business purposes and its
Customers who purchase system and application hosting services from Licensee, concurrent with run-time use of the Operating System, in Object Code format only on Systems owned by and under the
control of Licensee, for which Licensee has paid the applicable licensing fee to SCO. Anything
herein to the contrary notwithstanding, Licensee shall have the right to make copies of the SCO IP so
long as such copies are used in connection with the properly licensed SCO IP hereunder solely for
back-up and recovery purposes.
2.2 Except as otherwise expressly provided in Section 2.1 above, no right to copy, modify, distribute,
transfer or alter any part of the Operating System or the Software is granted under this Agreement.
2.3 No right to create derivative works or modifications of UNIX-based Code, or any other software
owned or licensed by SCO is granted under this Agreement.
2.4 This Agreement does not grant the right to receive any distribution of software from SCO or any third
party.
2.5 This Agreement does not extend to contractors or joint venture partners of Licensee. No third party
shall acquire any additional rights under this Agreement by acquisition of the assets or stock of
Licensee or the merger with or acquisition of a third party. Specifically but without limitation, an
acquiring company shall not and is not intended to receive for itself any benefit of the SCO waiver of
clamis and covenant that is extended to Licensee under the Covenant and Waiver of Certain Claims
provisions of this Agreement. Conversely, Licensee shall not acquire any additional rights under this
Agreement by acquisition of the assets or stock of a third party. In any stock or asset acquisition of a
third party, the release of claims and covenant shall not extend to or benefit Licensee with respect to
any infringing use of Software or the Operating System by any third party acquired by Licensee after
the date of this Agreement. Anything herein to the contrary notwithstanding, Licensee may request
additional licenses hereunder to cover any acquired third party and such request shall not be
unreasonably denied by SCO.
2.6 No right may be implied beyond those expressly granted hereunder. Any ambiguity in this Grant of
Rights or Agreement will be resolved against the grant of any additional right not specifically and
expressly granted hereunder.
3.0 SCO COVENANT AND WAIVER OF CERTAIN CLAIMS
Provided Licensee does not exceed the Grant of Rights under this Agreement from and after the date hereof,
SCO will not consider such use of the SCO EP licensed by Licensee under this Agreement to be in violation
of SCO's intellectual property ownership rights and SCO shall not bring any legal action alleging
infringement of the SCO IP by Licensee or Licensee's Customers.
Page 2 of 6
SCO Intellectual Property License
Contract No. EV12004IP
CONFIDENTIAL
33
Draft - For review and discussion purposes - SCO Legal will provide executable documents.
4.0 ORDERS, PRICE AND PAYMENT
4.1 Licensee will pay the applicable licensing fee included in Exhibit A of this Agreement to SCO.
4.2 Licensee's order for licenses under this Agreement is included in Exhibit A of this Agreement. SCO
shall invoice Licensee, at the time of execution of this Agreement, pursuant to the information
provided for in Exhibit A.
4.3 License Fees are exclusive of all applicable taxes. Licensee agrees to pay all taxes associated with
right-to-use licenses ordered under this Agreement, including but not limited to sales, use, excise,
added value and similar taxes and all customs, duties or governmental impositions, but excluding
taxes on SCO's net income.
4.4 All fees, costs and charges shall be due and payable thirty (30) days from date of receipt of invoice.
SCO may charge Licensee interest at the rate of 1 1/2 percent per month, or such maximum rate as
may be permitted by law, whichever shall be less, with respect to any sum that is not paid when due.
4.5 Licensee shall make all payments in United States Dollars -- or as agreed to in writing by the parties.
5.0 RECORD KEEPING AND AUDIT
5.1 Licensee shall keep full, clear and accurate records with respect to licenses granted hereunder for the
Systems owned or operated by Licensee. Such records shall contain all information necessary to
determine all fees due hereunder and shall be maintained for a period of five (5) years.
5.2 Licensee hereby grants SCO the right to cause an audit to be made with respect to the fees due
hereunder. If any discrepancies are found with respect to Licensee's payment of fees due hereunder
then a prompt adjustment shall be made by the proper party to compensate for any errors or omissions
disclosed by such audit. Any such audit shall be conducted no more frequently than once per
calendar year, during regular business hours at Licensee's offices and in such a manner as not to
interfere with Licensee's normal business activities. In the event that an audit discloses an
underpayment by Licensee to SCO of the lesser of five percent (5%) or the equivalent of Five
Thousand United States Dollars ($5,000), then Licensee shall pay for the cost of the audit, within
thirty (30) days of demand therefore.
5.3 In the event that SCO makes any claim against Licensee for payment with respect to such audit, upon
written request, SCO agrees to promptly make available to Licensee, its records and reports and those
prepared for SCO by third parties pertaining to the audit.
6.0 TERM OF AGREEMENT; OBLIGATIONS UPON TERMINATION
This Agreement shall remain in effect until terminated as set forth herein. Licensee may terminate this
Agreement without any right to refund or reimbursement by notifying SCO of such termination. SCO may
terminate this Agreement, upon thirty (30) days notice and without judicial or administrative resolution, if
Licensee or any of Licensee's employees, consultants or Customers breach any material term or condition
hereof and such breach is not cured within such thirty (30) day period.
Upon the termination of this Agreement for any reason, all rights granted to Licensee hereunder will cease.
7.0 PROPRIETARY NATURE OF SCO PRODUCTS AND OWNERSHIP
SCO represents and warrants that UNIX-based Code and related materials, and all copyrights, trade secret
and other intellectual and proprietary rights therein, are and remain the valuable property of SCO and its
suppliers.
8.0 LIMITATION OF WARRANTY
SCO MAKES NO WARRANTIES OF ANY KIND EXPRESS OR IMPLIED WITH RESPECT TO ANY
RIGHTS OTHER THAN TO THE SCO IP DEFINED BY THIS AGREEMENT.
SCO WARRANTS THAT IT IS ENPOWERED TO GRANT THE RIGHTS AND LICENSES GRANTED
HEREIN.
Page 3 of 6
SCO Intellectual Property License
Contract No. EV12004IP
CONFIDENTIAL
34
Draft - For review and discussion purposes - SCO Legal will provide executable documents.
EXCEPT AS SET EXPLICITLY FORTH IN THE PRECEDING SENTENCE, ALL WARRANTIES,
TERMS, CONDITIONS, REPRESENTATIONS, INDEMNITIES AND GUARANTEES WITH RESPECT
TO THE RIGHTS, WHETHER EXPRESS OR IMPLIED, ARISING BY LAW, CUSTOM, PRIOR ORAL
OR WRITTEN STATEMENTS BY ANY PARTY OR OTHERWISE (INCLUDING, BUT NOT LIMITED
TO ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE OR
ANY IMPLIED WARRANTY OF NON INFRINGEMENT OF THIRD PARTY INTELLECTUAL
PROPERTY RIGHTS) ARE HEREBY OVERRIDDEN, EXCLUDED AND DISCLAIR[ED. SOME
STATES OR COUNTRIES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE
ABOVE EXCLUSION MAY NOT APPLY.. THIS WARRANTY GIVES SPECIFIC LEGAL RIGHTS
AND LICENSEE MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM STATE TO STATE OR
COUNTRY TO COUNTRY.
9.0 LIMITION OF LIABILITY
UNDER NO CIRCUMSTANCES WILL SCO OR ITS REPRESENTATIVES BE LIABLE FOR ANY
CONSEQUENTIAL, INDIRECT, SPECIAL, PUNITIVE, OR INCIDENTAL DAMAGES, WHETHER
FORESEEABLE OR UNFORESEEABLE, BASED ON LICENSEE'S CLAIMS OR THOSE OF ITS
CUSTOMERS (INCLUDING BUT NOT LIMITED TO, CLAIMS FOR LOSS OF DATA, GOODWILL,
PROFITS, USE OF MONEY OR USE OF THE SCO PRODUCTS, INTERRUPTION IN USE OR
AVAILABILITY OF DATA, STOPPAGE OF OTHER WORK OR RAPAIRMENT OF OTHER ASSETS,
TRADEMARK, PATENT OR COPYRIGHT INFRINGEMENT), ARISING OUT OF BREACH OR
FAILURE OF EXPRESS OR IMPLIED WARRANTY, BREACH OF CONTRACT,
MISREPRESENTATION, NEGLIGENCE, STRICT LIABILITY IN TORT OR OTHERWISE, EXCEPT
ONLY IN THE CASE OF PERSONAL INJURY WHERE AND TO THE EXTENT THAT APPLICABLE
LAW REQUIRES SUCH LIABILITY IN NO EVENT WILL-THE AGGREGATE LIABILITY WHICH
SCO MAY INCUR IN ANY ACTION OR PROCEEDING ARISING OUT OF THIS AGREEMENT OR
OTHERWISE EXCEED THE TOTAL AMOUNT ACTUALLY PAID BY LICENSEE TO SCO FOR THE
LICENSE OF THE SCO PRODUCT THAT DIRECTLY CAUSED THE DAMAGE.
SOME JURISDICTIONS DO NOT ALLOW THE LIMITATION OF EXCLUSION OF LIABILITY FOR
INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES SO THE ABOVE
LIMITATION MAY NOT APPLY IN CERTAIN CIRCUMSTANCES..
10. LICENSEE INDEMNIFICATION
Licensee will defend, indemnify and hold harmless SCO, its parents and subsidiaries, against any third party
claim against it for loss, damage, liability or expense (including but not limited to attorneys' fees) arising
out of any unauthorized representations, warranties, or willful acts or omissions of Licensee in connection
with its activities under this Agreement.
11.0 MISCELLANEOUS
11.1 Neither party shall be liable for any delay or failure in its performance hereunder due to any cause
beyond its control provided, however, that this provision shall not be construed to relieve Licensee of
its obligation to make any payments pursuant to this Agreement.
11.2 Licensee may not assign, sublicense, rent lend, lease, pledge or otherwise transfer or encumber this
Agreement or the rights granted under this Agreement the SCO IP, any of the individual licenses
granted under it or Licensee's rights or obligations hereunder Any purported assignment shall be
null and void. Change of control is deemed an assignment and not effective without SCO's express
written consent.
11.3 All notices and requests in connection with this Agreement may be sent or delivered to the addresses
above by hand, by certified mail return receipt requested, by fax, or by courier.
11.4 Support and maintenance are not available under this Agreement.
11.5 This Agreement shall be governed by, and construed and enforced in accordance with, the laws of the
State of Utah and the United States of America, specifically excluding the United Nations Convention
Page 4 of 6
SCO Intellectual Property License
Contract No. EV12004IP
CONFIDENTIAL
35
Draft - For review and discussion purposes - SCO Legal will provide executable docuntents.
on Contracts for the International Sale of Goods, and without giving effect to conflict of laws. Any
litigation or arbitration between the Parties shall be conducted exclusively in the State of Utah.
Licensee expressly consents to the jurisdiction of such courts. Process may be served by U.S. mail,
postage prepaid, certified or registered, return receipt requested, by express courier such as DHL or
Federal Express, or by such other method as is authorized by law. Nothing in this Section will
prevent SCO from seeking injunctive relief against Licensee or filing legal actions for payment of
outstanding and past due debts in the courts.
11.6 If any provision or provisions of this Agreement shall be held to be invalid, illegal or unenforceable,
the validity, legality and enforceability of the remaining provisions shall not in any way be affected or
unpaired thereby. The Parties will seek in good faith to agree on replacing an invalid, illegal, or
unenforceable provision with a valid, legal, and enforceable provision that, in effect, will, from an
economic viewpoint most nearly and fairly approach the effect of the invalid, illegal, or
unenforceable provision.
11.7 Each Party acknowledges that the parties to this Agreement are independent contractors and that it
will not, except in accordance with this Agreement, represent itself as an agent or legal representative
of the other. This Agreement does not create a joint venture or fiduciary relationship of any kind
between the Parties.
11.8 Company represents and warrants that all consents of governmental officials necessary for this
Agreement to become effective have been obtained, or will be obtained, before Company places any
orders under this Agreement. Company will comply, at its own expense, with all statutes,
regulations, rules, ordinances, and orders of any governmental body, department or agency that apply
to or result from Company's obligations under this Agreement.
11.9 No High Risk Activities: The SCO IP is NOT fault-tolerant and are not designed, manufactured or
intended for use or resale as on-line control equipment in hazardous environments requiring fail-safe
performance, such as in the operation of nuclear facilities, aircraft navigation or communication
systems, air traffic control, direct life support machines, or weapons systems, in which the failure of
the Product could lead to death, personal injury, or severe physical or environmental damage ("High
Risk Activities"). SCO specifically disclaims any express or implied warranty of fitness for High
Risk Activities.
11.10 This Agreement (including all Exhibits) sets forth the entire understanding and supersedes and
merges all prior and contemporaneous agreements between the parties relating to the subject matter
contained herein. Neither Party shall be bound by any provision, amendment or modification other
than as expressly stated in or contemplated by this Agreement or as subsequently shall be set forth in
writing and executed by a duly authorized representative of the Party to be bound thereby.
IN WITNESS WHEREOF, the parties hereto have executed this Agreement, effective as of the last date properly
executed by both parties. All signed copies of this Agreement shall be deemed originals.
THE SCO GROUP, INC |
LICENSEE |
By:
|
____________________________ |
By:
|
____________________________ |
Name:
|
____________________________ |
Name:
|
____________________________ |
Title:
|
____________________________ |
Title:
|
____________________________ |
Date:
|
____________________________ |
Date:
|
____________________________ |
Page 5 of 6
SCO Intellectual Property License
Contract No. EV12004IP
CONFIDENTIAL
36
Draft - For review and discussion purposes - SCO Legal will provide executable documents.
® Linux is a registered trademark of Linus Torvalds in the US and other countries.
® UNIX and UnixWare are a registered trademarks of The Open Group in the US and other countries.
Page 6 of 6
SCO Intellectual Property License
Contract No. EV120041IP
CONFIDENTIAL
37
Draft - For review and discussion purposes - SCO Legal will provide executable documents.
EXHIBIT A
LICENSE FEES AND ADDITIONAL TERMS AND CONDITIONS
LICENSE FEES:
The following License Fees are not subject to any additional discounts and may not be used for purposes of
aggregating to any other SCO discounts.
Subject to Section 2 of this Agreement SCO grants licensee a limited, non-exclusive, non-transferable right and
license to use SCO IP, for its own internal business purposes, concurrent with run-time use of the Operating
System, in Object Code format only, on all Systems owned and operated by Licensee. Licensee agrees to pay SCO
the following License Fees:
Total Site License Fee |
US$2,000,000 |
(total fee payable including advertising) |
Less: Licensee Promotional Allowance |
US$ 600,000 |
(less promotional allocation) |
SCO Discount/Contribution Allowance |
US$ 600,000 |
(less applied discount) |
Net License Fee |
US$800,000 |
(payable to SCO per below) |
Net License Fee will be paid pursuant to the following schedule:
Upon Execution -
US$ 100,000
March 31, 2004 - US$ 100,000
April 30, 2004 -
US$ 100,000
May 31, 2004 - US$ 100,000
June 30, 2004 -
US$ 100,000
July 31, 2004 -
US$ 100,000
August 31, 2004 -
US$ 100,000
September 30, 2004 -
US$ 100,000
Promotional Allowance:
In consideration of Licensee's commitment ($600,000 Promotional Allowance) to participate in mutually agreed
upon advertising campaign related to this Agreement, specifically excluding any pricing related information, SCO
is granting Licensee a reduction in Licensee Fees payable. Should Licensee fail to comply with this commitment,
the Net License Fee shall be adjusted accordingly. SCO and Licensee will mutually agree upon the costs to be
applied by Licensee toward satisfaction of its Promotional Allowance.
Both Parties will work together to complete a joint press release by the parties to be issued upon execution of this
Agreement. Licensee further agrees to favorably discuss the benefits of this Agreement in mutually agreed to
interviews including provide the an executive quote/endorsement that SCO can use in press releases, allow SCO to
write up a success story for its web site and press usage and Licensee agrees to talk with the press about SCO's
Intellectual Property License.
Licensee agrees to commence advertising campaign for national/international publications within the first thirty
(30) days of this Agreement SCO and Licensee reserve the right to approve final advertising copy prior to
distribution. Other advertising initiatives may include, but not to be limited to advertising and press release
opportunities, joint participation at events, or other venues, etc.
SCO and Licensee will jointly agree on press releases and other publicity related to this Agreement. SCO will be
free to reference Licensee as a licensee of the SCO Intellectual Property License subject to Licensee's prior
approval of the content. Such approval by Licensee shall not be unreasonably delayed or withheld. Approval shall
be deemed granted if SCO does not receive an objection from Licensee within five (5) business days of such
request. This includes but is not limited to references with industry and financial analysts.
Each Party will be free to reference the other as the licensor/licensee of the SCO Intellectual Property License
subject to the other party's prior approval of the content. Such approval shall not be unreasonably delayed or
withheld. Approval shall be deemed granted if the requesting party does not receive an objection within five (5)
business days of such request. This includes but is not limited to references with industry and financial analysts.
Page 7 of 6
SCO Intellectual Property License
Contract No. EV12004IP
CONFIDENTIAL
38
EXHIBIT 6
39
COPY
THE SCO GROUP. INC.
INTELLECTUAL PROPERTY LICENSE
This Intellectual Property License Agreement ("Agreement") is made and entered into on the date last executed
below by and between The SCO Group, Inc., a corporation of the State of Delaware, for itself and its Subsidiaries
(collectively referred to herein as "SCO"), with its place of business at [redacted], Lindon,
Utah 84042, U.S.A., and Everyones Internet EV1, a corporation of the State of Texas, (referred to herein as
"Licensee"), with its place of business at [address redacted] Texas 77098.
WHEREAS, SCO owns all right, title and interest in and to certain SCO intellectual property (as hereinafter
defined); and
WHEREAS, Licensee is in the business of providing hosting services through its hosting centers; and
WHEREAS, SCO wishes to grant and Licensee wishes to obtain certain limited rights and licenses to use SCO IP,
which rights Licensee wishes to accept, all in accordance with the terms and conditions hereinafter set forth;
NOW, THEREFORE, in consideration of the mutual promises made herein it is agreed as follows:
1.0 DEFINITIONS
1.1 "Code" shall mean computer programming instructions.
1.2 "Customer" means those persons and entities who now or hereafter purchase, lease, license, subscribe to, or otherwise obtain ISP Business and Hosting Business services, or both, from Licensees.
1.3 "Method" means the human or machine methodology for, or approach to, design, structure,
modification, upgrade, de-bugging, tuning, improvement or adaptation of Code.
1.4 "Network System" means the computers and computer network systems and equipment utilized by Licensee to provide ISP Business and Hosting Business services (including, without limitation, all servers owned, lessed, licensed, or utilized and controlled by Licensee to operate, conduct, and maintain the Businesses), or both, to its Customers and the computers and computer network systems and equipment utilized by Licensee in connection with its internal business operations.
1.5 "Object Code" means the Code that results when Source Code is processed by a software compiler
and is directly executable by a computer.
1.6 "Operating System" means software operating system Code (or Code that substantially performs the
functions of an operating system) that is a distribution, rebranding, modification or derivative work
of the Linux operating system.
1.7 "SCO IP means the SCO UNIX(r)-based Code alleged by SCO to be included, embodied, or otherwise utilized in the [Linux] Operating System.
1.8 "Software" means the Operating System in Object Code format.
1.9 "Source Code" means the human-readable form of the Code and related system documentation,
including all comments and any procedural language.
1.10 "UNIX-based Code" means any Code or Method that: (i) in its literal or non-literal expression,
structure, format, use, functionality or adaptation (ii) is based on, developed in, derived from or is
similar to (iii) any Code contained in or Method devised or developed in (iv) UNIX System V or
Page 1 of 8
SCO Intellectual Property License
Contract No. EV12004IP
Confidential
40
UnixWare, or (v) any modification or derivative work based on or licensed under UNIX System V
or UnixWare.
1.11 "Update" means the updates or revisions in Object Code format of the Software that You may receive. To the extent that the SCO IP includes patents, "Update" shall include all extensions, divisionals, continuations, continuations-in-part, examinations and reissue patents of such patents, as well as patent applications thereof. TO the extent that the SCO IP includes copyrights "Update" shall include any and all renewals and extensions thereof..
2.0 GRANT OF RIGHTS
2.1 SCO hereby grants Licensee and Licensee hereby accepts from SCO the following limited, non-exclusive, worldwide and perpetual, subject to Section 6, right and license to use SCO IP solely in Object Code format, for or in connection with: (a) Licensee's internal business purposes; (b) the Network Systems owned, lessed, licensed, or utilized and controlled by Licensee to operate, conduct, and maintain the Businesses; and (c) providing ISP Business and Hosting Business services, or both, to the Customers through Licensee's hosting center(s) identified in Exhibit A of this Agreement. Subject to the provisions included in Sectin 2.5 below, such changes and or additions to Licensee's hosting centers whall not require additional SCO IP license fees. Anything herein to the contrary notwithstanding, Licensee shall have the right to make a reasonable number of copies of the SCO IP so long as such copies are used in connection with the properly licensed SCO IP hereunder solely for archival, back-up and recovery purposes.
2.2 Except as otherwise expressly provided in Section 2.1 above, no right to copy, modify, distribute,
transfer or alter any part of the Operating System or the Software is granted under this Agreement.
2.3 No right to create derivative works or modifications of UNIX-based Code, or any other software
owned or licensed by SCO is granted under this Agreement.
2.4 This Agreement does not grant the right to receive any distribution of software from SCO.
2.5 This Agreement does not extend to contractors or joint venture partners of Licensee. No third party
shall acquire any additional rights under this Agreement by acquisition of the assets or stock of
Licensee or the merger with or acquisition of a third party. Specifically but without limitation, an
acquiring company shall not and is not intended to receive for itself any benefit of the SCO waiver of
claims and covenant that is extended to Licensee under the Covenant and Waiver of Certain Claims
provisions of this Agreement. Conversely, Licensee shall not acquire any additional rights under this
Agreement by acquisition of the assets or stock of a third party. In any stock or asset acquisition of a
third party, the release of claims and covenant shall not extend to or benefit Licensee with respect to
any infringing use of SCO IP by any third party. Anything herein to the contrary notwithstanding, Licensee may request
additional licenses hereunder to cover any acquired third party and such request shall not be
unreasonably denied by SCO.
Notwithstanding anything contained herein to the contrary, should Licensee decide to sell its interest in either, or both, of the Businesses, SCO grants Licensee a one-time right to assing this license, with the exception of Section 9.2 which is hereby excluded from any such assignment, to a third party (hereinafter referred to as a "Purchaser") who purchases either or both Businesses. In such case Purchaser shall, provided such Purchaser agrees, in writing to SCO, to be bound by the terms and conditions of this Agreement, have the limited rights granted to Licensee pursuant to this Agreement, with the exception of Section 9.2, solely for the Network Systems covered by this Agreement at the time of transfer to the extent, and only to the extent, the limited rights transferred relate to those assets of the Business purchased. The limited assignment right granted in this Section shall further extend to a Purchaser of the Hosting Business, for said Purchaser's organic growth of the Hosting Business only through the addition of Customers and the resulting additional Network Systems required to service such additional Customers directly related to the Hosting Business so acquired from Licensee. The extension of the limited assignment right to such growth specifically excludes additions or growth by Purchaser through joint ventures, mergers, acquisitions of the assets or stock of a third party, and shall not apply to any other assets, businesses, including the ISP Business or uses owned or controlled by such Purchaser or any other prior or concurrent uses of the SCO IP by Purchaser either before or after the transaction with Licensee. Furthermore, and notwithstanding anything contained herein to the contrary, in the event Licensee spins-off either the ISP Business or Hosting Business into a new entity under majority ownership control of Licensee, then provided such spin-off entity agrees, in writing to
Page 2 of 8
SCO Intellectual Property Licence
Contract No. EV12004IP
Confidential
41
SCO, to be bound by the terms and conditions of this Agreement, such spin-off entity shall be entitled to the benefits of the waiver, releases, and indemnities contained herein to the extent, and only to the extent, as such rights, uses, waivers, releases and indemnities rrelate to those assets, businesses, and uses covered by this Agreement and shall not extend to any other assets, businesses or uses owned or controlled by such spin-off entity or any other prior or concurrent uses of the SCO IP by such spin-off entity.
Licensee shall keep full, clear and accurate records with respect to all servers owned, lessed, licensed, or utilized and controlled by Licensee to operate, conduct, and maintain the Businesses. Such records shall contain all information necessary to determine compliance with this Section 2.5.
2.6 No right may be implied beyond those expressly granted hereunder. Any ambiguity in this Grant of
Rights or Agreement will be resolved against the grant of any additional right not specifically and
expressly granted hereunder.
3.0 SCO COVENANT AND WAIVER OF CERTAIN CLAIMS
Upon full payment of the one-time licensing fee described in Exhibit A of this Agreement,
SCO will not consider such use of the SCO IP or future use of the SCO IP and Updates licensed by Licensee under the rights granted under this Agreement (provided Licensee does not exceed the Grant of Rights under the Agreement) to be in violation
of SCO's intellectual property ownership rights and SCO shall not bring any legal action alleging
infringement of the SCO IP by Licensee or Licensee's Customers for usage of SCO IP solely in connection with Licensee's Businesses. In that regard, upon full payment of the license fee described in Exhibit A of this Agreement, Licensee and its Customers shall be forever released and discharged from any and all claims, liabilities, suits, demands, or obligations arising from any authorized use of the SCO IP in connection with: (a) Licensee's internal business purposes; (b) the Network Systems owned, lessed, licensed, or utilized and controlled by Licensee to operate, conduct, and maintain the Businesses; and (c) providing ISP Business and Hosting Business services by Licensee to its Customers through the date of the final payment of the one-time licensing fee. Nothing contained herein shall be deemed, interpreted or construed as an admission of liability on the part of Licensee for any unauthorized use of the SCO IP prior to the date hereof.
4.0 ORDERS, PRICE AND PAYMENT
4.1 Licensee will pay the applicable licensing fee included in Exhibit A of this Agreement to SCO.
4.2 Licensee's order for licenses under this Agreement is included in Exhibit A of this Agreement. SCO
shall invoice Licensee, at the time of execution of this Agreement, pursuant to the information
provided for in Exhibit A.
4.3 License Fees are exclusive of all applicable taxes. Licensee agrees to pay all taxes associated with
right-to-use licenses ordered under this Agreement, including but not limited to sales, use, excise,
added value and similar taxes and all customs, duties or governmental impositions, but excluding
taxes on SCO's net income.
4.4 All fees, costs and charges shall be due and payable thirty (30) days from date of receipt of invoice.
SCO may charge Licensee interest at the rate of 1 1/2 percent per month, or such maximum rate as
may be permitted by law, whichever shall be less, with respect to any sum that is not paid when due.
4.5 Licensee shall make all payments in United States Dollars -- or as agreed to in writing by the parties.
5.0 TERM OF AGREEMENT; OBLIGATIONS UPON TERMINATION
This Agreement shall remain in effect until terminated as set forth herein. Licensee may terminate this
Agreement without any right to refund or reimbursement by notifying SCO of such termination. SCO may
terminate this Agreement, upon thirty (30) days notice and without judicial or administrative resolution, if
Licensee or any of Licensee's employees, consultants or Customers breach any material term or condition
hereof and such breach is not cured within such thirty (30) day period.
Upon the termination of this Agreement for any reason, all rights granted to Licensee hereunder will cease; PROVIDED, however, that Licensee's rights of indemnity for Licensee claims arising during the term hereof shall survive the termination of this Agreement.
6.0 PROPRIETARY NATURE OF SCO PRODUCTS AND OWNERSHIP
Page 3 of 8
SCO Intellectual Property License
Contract No. EV12004IP Confidential
42
SCO represents and warrants that it has full right and title to grant the rights hereunder to the SCO IP and related materials, and all copyrights, trade secret and other intellectual proprietary rights therein, are and remain the valuable property of SCO and its
suppliers. SCO makes no representations or guarantees concerning the outcome of any pending or potential litigation, as outlined above, regarding SCO's claims of violations of its IP or contractual rights in the Operating System. Licensee acknowledges that SCO's claims regarding its IP as it relates to the Operating System are being litigated in one or more cases, with possibly more litigation to follow, and that SCO has not guaranteed that it will ultimately prevail in any of this litigation. Licensee, to avoid any such litigation and to effectuate a productive and prompt resolution of any and all issues relating to use of SCO's IP, desires to obtain this license.
7.0 LIMITATION OF WARRANTY
SCO MAKES NO WARRANTIES OF ANY KIND EXPRESS OR IMPLIED WITH RESPECT TO ANY
RIGHTS OTHER THAN TO THE SCO IP DEFINED BY THIS AGREEMENT.
SCO WARRANTS THAT IT IS ENPOWERED TO GRANT THE RIGHTS AND LICENSES GRANTED
HEREIN SUBJECT TO THE QUALIFICATIONS SET FORTH IN SECTION 6.0.
EXCEPT AS SET EXPLICITLY FORTH IN THE PRECEDING SENTENCE, ALL WARRANTIES,
TERMS, CONDITIONS, REPRESENTATIONS, INDEMNITIES AND GUARANTEES WITH RESPECT
TO THE RIGHTS, WHETHER EXPRESS OR IMPLIED, ARISING BY LAW, CUSTOM, PRIOR ORAL
OR WRITTEN STATEMENTS BY ANY PARTY OR OTHERWISE (INCLUDING, BUT NOT LIMITED
TO ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE OR
ANY IMPLIED WARRANTY OF NON INFRINGEMENT OF THIRD PARTY INTELLECTUAL
PROPERTY RIGHTS) ARE HEREBY OVERRIDDEN, EXCLUDED AND DISCLAIMED. SOME
STATES OR COUNTRIES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE
ABOVE EXCLUSION MAY NOT APPLY. THIS WARRANTY GIVES SPECIFIC LEGAL RIGHTS
AND LICENSEE MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM STATE TO STATE OR
COUNTRY TO COUNTRY.
8.0 LIMITATION OF LIABILITY
UNDER NO CIRCUMSTANCES WILL SCO OR ITS REPRESENTATIVES BE LIABLE FOR ANY
CONSEQUENTIAL, INDIRECT, SPECIAL, PUNITIVE, OR INCIDENTAL DAMAGES, WHETHER
FORESEEABLE OR UNFORESEEABLE, BASED ON LICENSEE'S CLAIMS OR THOSE OF ITS
CUSTOMERS (INCLUDING BUT NOT LIMITED TO, CLAIMS FOR LOSS OF DATA, GOODWILL,
PROFITS, USE OF MONEY OR USE OF THE SCO PRODUCTS, INTERRUPTION IN USE OR
AVAILABILITY OF DATA, STOPPAGE OF OTHER WORK OR RAPAIRMENT OF OTHER ASSETS,
TRADEMARK, PATENT OR COPYRIGHT INFRINGEMENT), ARISING OUT OF BREACH OR
FAILURE OF EXPRESS OR IMPLIED WARRANTY, BREACH OF CONTRACT,
MISREPRESENTATION, NEGLIGENCE, STRICT LIABILITY IN TORT OR OTHERWISE, EXCEPT
ONLY IN THE CASE OF PERSONAL INJURY WHERE AND TO THE EXTENT THAT APPLICABLE
LAW REQUIRES SUCH LIABILITY IN NO EVENT WILL THE AGGREGATE LIABILITY WHICH
SCO MAY INCUR IN ANY ACTION OR PROCEEDING ARISING OUT OF THIS AGREEMENT OR
OTHERWISE EXCEED THE TOTAL AMOUNT ACTUALLY PAID BY LICENSEE TO SCO FOR THE
LICENSE OF THE SCO PRODUCT THAT DIRECTLY CAUSED THE DAMAGE.
SOME JURISDICTIONS DO NOT ALLOW THE LIMITATION OF EXCLUSION OF LIABILITY FOR
INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES SO THE ABOVE
LIMITATION MAY NOT APPLY IN CERTAIN CIRCUMSTANCES.
9. INDEMNIFICATION
9.1 Licensee will defend, indemnify and hold harmless SCO, its parents and subsidiaries, against any third party
claim against it for loss, damage, liability or expense (including but not limited to attorneys' fees) arising
out of any unauthorized representations, warranties, or willful acts or omissions of Licensee in connection
with its activities under this Agreement.
9.2 SCO shall indemnify and hold Licensee harmless from and against and defend any claim, suit or proceeding, and pay any settlement amounts or damages awarded by a court of final jurisdiction, for claims filed by a third party against Licensee claiming damages caused by a breach of SCO's representations and warranties set forth in this Agreement and claims that the SCO IP infringes any
Page 4 of 8
SCO Intellectual Property License
Contract No. EV 12004IP
Confidential
43
copyright, patent, trade mark or other intellectual property right, provided Licensee promptly notifies SCO in writing of any such claim, suit or proceeding, and permits SCO to control the settlement or defense thereof. Licensee has the option to be represented by Counsel at its own expense.
If, pursuant to any such claim, a court of competent jurisdiction removes or restricts Licensee's right to continue to exercise it rights granted hereunder to the SCO IP, SCO shall, at its sole option (i) procure for Licensee the right to continue to exercise it rights granted hereunder to the SCO IP; (ii) modify the SCO IP, provided the functionality thereof is not substantially affected, so as to make it non-infringing; or (iii) refund the Net License Fees paid SCO discounted over a three (3) year period, subject to a pro rata adjustment for prior usage of the SCO IP. In addition, SCO shall have the right to exercise any of options (i) through (iii) at any time following receipt of a claim of infringement of copypright or other proprietary right.
SCO shall have no obligation under this section with respect to any claim of infringement of a proprietary right based upon any modification of the SCO IP by Licensee or any other entity or the combination, operation or use of SCO IP with materials not supplied by SCO provided that it is such modification, combination, operation or use which caused the claimed infringement.
THE ABOVE STATES THE ENTIRE LIABILITY OF SCO WITH RESPECT TO INFRINGEMENT OF PATENTS, COPYRIGHTS, TRADEMARKS OR ANY OTHER FORM OF INTELLECTUAL PROPERTY RIGHT BY ANY PRODUCT SUPPLIED BY SCO.
10.0 MISCELLANEOUS
10.1 Neither party shall be liable for any delay or failure in its performance hereunder due to any cause
beyond its control provided, however, that this provision shall not be construed to relieve Licensee of
its obligation to make any payments pursuant to this Agreement.
10.2 Except as otherwise provided for Section 2.5, Licensee may not assign, sublicense, rent, lend, lease, pledge or otherwise transfer or encumber this
Agreement or the rights granted under this Agreement, the SCO IP or Licensee's rights or obligations hereunder without SCO prior written consent which shall not be unreasonably withheld. Any purported assignment shall be
null and void. Change of control is deemed an assignment and not effective without SCO's express
written consent.
10.3 All notices and requests in connection with this Agreement may be sent or delivered to the addresses
above by hand, by certified mail return receipt requested, by fax, or by courier.
10.4 Support and maintenance are not available under this Agreement.
10.5 This Agreement shall be governed by, and construed and enforced in accordance with, the laws of the
State of Utah and the United States of America, specifically excluding the United Nations Convention on Contracts for the International Sale of Goods, and without giving effect to conflict of laws. Any
litigation or arbitration between the Parties shall be conducted exclusively in the State of Utah.
Licensee expressly consents to the jurisdiction of such courts. Process may be served by U.S. mail,
postage prepaid, certified or registered, return receipt requested, by express courier such as DHL or
Federal Express, or by such other method as is authorized by law. Nothing in this Section will
prevent SCO from seeking injunctive relief against Licensee or filing legal actions for payment of
outstanding and past due debts in the courts.
10.6 If any provision or provisions of this Agreement shall be held to be invalid, illegal or unenforceable,
the validity, legality and enforceability of the remaining provisions shall not in any way be affected or
unpaired thereby. The Parties will seek in good faith to agree on replacing an invalid, illegal, or
unenforceable provision with a valid, legal, and enforceable provision that, in effect, will, from an
economic viewpoint most nearly and fairly approach the effect of the invalid, illegal, or
unenforceable provision.
10.7 Each Party acknowledges that the parties to this Agreement are independent contractors and that it
will not, except in accordance with this Agreement, represent itself as an agent or legal representative
of the other. This Agreement does not create a joint venture or fiduciary relationship of any kind
between the Parties.
10.8 SCO and Licensee represent and warrant that all consents of governmental officials necessary for this
Agreement to become effective have been obtained, or will be obtained, before the parties execute this Agreement. Each party will comply, at its own expense, with all statutes,
regulations, rules,
Page 5 of 8
SCO Intellectual Property License
Contract No. EV12004IP
Confidential
44
ordinances, and orders of any governmental body, department or agency that apply
to or result from such party's obligations under this Agreement.
10.9 No High Risk Activities: The SCO IP is NOT fault-tolerant and are not designed, manufactured or
intended for use or resale as on-line control equipment in hazardous environments requiring fail-safe
performance, such as in the operation of nuclear facilities, aircraft navigation or communication
systems, air traffic control, direct life support machines, or weapons systems, in which the failure of
the Product could lead to death, personal injury, or severe physical or environmental damage ("High
Risk Activities"). SCO specifically disclaims any express or implied warranty of fitness for High
Risk Activities.
10.10 This Agreement (including all Exhibits) sets forth the entire understanding and supersedes and
merges all prior and contemporaneous agreements between the parties relating to the subject matter
contained herein. Neither Party shall be bound by any provision, amendment or modification other
than as expressly stated in or contemplated by this Agreement or as subsequently shall be set forth in
writing and executed by a duly authorized representative of the Party to be bound thereby.
10.11 This Agreement may be executed in any number of counterparts and via facsimile, each of which shall be deemed an original instrument, but all of which together shall constitute only one and the same instrument.
IN WITNESS WHEREOF, the parties hereto have executed this Agreement, effective as of the last date properly
executed by both parties. All signed copies of this Agreement shall be deemed originals.
THE SCO GROUP, INC |
EVERYONES INTERNET, LTD.
By its Sole General Partner, E. I. MANAGEMENT, LLC |
By:
|
____________________________ |
By:
|
__[signature]____ |
Name:
|
____________________________ |
Name:
|
Robert Marsh |
Title:
|
____________________________ |
Title:
|
President |
Date:
|
____________________________ |
Date:
|
3/1/04 |
® Linux is a registered trademark of Linus Torvalds in the US and other countries.
® UNIX and UnixWare are a registered trademark of The Open Group in the US and other countries.
Page 6 of 8
SCO Intellectual Property License
Contract No. EV12004IP
Confidential
45
EXHIBIT A
LICENSE FEES AND ADDITIONAL TERMS AND CONDITIONS
SCO's standard unit quantity discount applicable to SCO's US Price List for one thousand (1,000) licenses is fifty percent (50%) for standard corporate licensees and is applied to the cumulative unit purchases made by a licensee under a Corporate Agreement.
In consideration for the estimated number of SCO IP Licenses to be granted and the unique nature of the internet access services and webhosting services business, including but not limited to the ongoing changes to computer systems configurations, and Licensee's cooperation and commitments agreed to below, including the fact that Licensee is the first such company to seek such a license from SCO, SCO is agreeing to the following License Fees.
LICENSE FEES:
The following one-time License Fee is not subject to any additional discounts and may not be used for purposes of
aggregating to any other SCO discounts.
In consideration for the rights,
licenses waivers and releases contained in the Agreement, Licensee agrees to pay SCO
the following one-time License Fees:
Total Site License Fee |
US$1,400,000 |
(total fee payable including advertising) |
Less: Licensee Promotional Allowance |
US$ 600,000 |
(less promotional allocation) |
Net License Fee |
US$800,000 |
(payable to SCO per below) |
Net License Fee will be paid pursuant to the following schedule:
Upon Execution -
US$ 100,000
March 31, 2004 - US$ 100,000
April 30, 2004 -
US$ 100,000
May 31, 2004 - US$ 100,000
June 30, 2004 -
US$ 100,000
July 31, 2004 -
US$ 100,000
August 31, 2004 -
US$ 100,000
September 30, 2004 -
US$ 100,000
Promotional Allowance:
In consideration of Licensee's commitment ($600,000 Promotional Allowance) to participate in mutually agreed
upon advertising campaign related to this Agreement, specifically excluding any pricing related information, SCO
is granting Licensee a reduction in Licensee Fees payable. Should Licensee fail to comply with this commitment,
the Net License Fee shall be adjusted accordingly. SCO and Licensee will mutually agree upon the costs to be
applied by Licensee toward satisfaction of its Promotional Allowance.
Both Parties will work together to complete a joint press release by the parties to be issued upon execution of this
Agreement. Licensee further agrees to favorably discuss the benefits of this Agreement in mutually agreed to
interviews including providing an executive quote/endorsement that SCO can use in press releases, allow SCO to
write up a success story for its web site and press usage and, Licensee agrees to talk with the press about SCO's
Intellectual Property License.
Licensee agrees to commence an advertising campaign for national/international publications within the first thirty
(30) days of this Agreement. SCO and Licensee reserve the right to approve final advertising copy prior to
distribution. Other advertising initiatives may include, but not to be limited to advertising and press release
opportunities, joint participation at events, or other venues, etc.
SCO and Licensee will jointly agree on press releases and other publicity related to this Agreement. SCO will be
free to reference Licensee as a licensee of the SCO Intellectual Property License subject to Licensee's prior
approval of the content. This includes but is not limited to references with industry and financial analysts.
Each Party will be free to reference the other as the licensor/licensee of the SCO Intellectual Property License
subject to the other party's prior approval of the content. This includes but is not limited to references with industry and financial analysts.
Page 7 of 8
SCO Intellectual Property License
Contract No. EV12004IP
Confidential
46
It is expressly agreed that wherever the prior approval or consent of any party hereto is required under the terms hereof that the party from whom such consent or approval is required (the "Receiving Party") agrees not to unreasonably condition, withhold or delay such consent or approval. Furthermore, the Receiving Party shall have five (5) days from written requrest for same by the requesting party (the "Requesting Party") to consent to or disapprove of such request, press release, advertising, or any other item requiring concsent or approval hereunder (an "Advertisement") and, if the Receiving Party disapproves of such Advertisement it shall provide the Requesting party with written notice thereof within such five (5) day period along with the particular reasons for such disapproval and written editorial comments or suggestions to the Advertisement which if incorporated therein by the Requesting Party the Receiving Party would then be deemed to have approved or consented to such Advertisement as modified.
Any notice, request, approval, consent or other communication required or contemplated by this Agreement must be in writing, and may, unless otherwise in this Agreement expressly provided, be given or be served by depositing the same in the United States Postal Service, post-paid and certified and addressed to the party to be notified, with return receipt requested, or by delivering the same in person to such party (or, in case of a corporate party, to an officer of such party), or by prepaid telegram or express overnight mail service, when appropriate, addressed to the party to be notified, or by facsimile to the facsimile numbers below with confirmation of receipt. Notice deposited in the mail in the manner hereinabove described shall be effective from and after three (3) days (exclusive of Saturdays, Sundays and postal holidays) after such deposit. Notice given in any other manner shall be effective only if and when delivered to the party to be notified or at such party's address for purposes of notice as set forth herein. For purposes of notice the addresses of the parties shall, until changed as herein provided, be as follows:
NOTICE AND APPROVALS:
For SCO: Chris Sontag
[address, fax]
For EV1: Robert Marsh
[address, fax}
LICENSEE'S HOSTING SITES:
Licensee is required to notify SCO in writing related to any changes or additions to its hosting sites prior to any such change or addition.
____[address]____
____[address]____
Page 8 of 8
SCO Intellectual Property License
Contract No. EV12004IP
Confidential
47
EXHIBIT 7
48
FOR IMMEDIATE RELEASE
Contact:
Blake Stowell/Marc Modersitzki
The SCO Group
[Email Address]
[Telephone]
www.sco.com |
Avi Dines/David Close
Schwartz Communications
[Email Address]
[Telephone]
|
SCO SIGNS INTELLECTUAL PROPERTY LICENSE AGREEMENT WITH
LEADING DEDICATED SERVER PROVIDER
EV1Servers.Net Becomes First Dedicated Hosting Firm to Achieve
SCO IP Certified Status
LINDON, Utah -March 1, 2004- The SCO Group, Inc. ("SCO") (Nasdaq: SCOX), the
owner of the UNIX operating system and a leading provider of UNIX-based solutions, today
announced an intellectual property licensing agreement with EV1Servers.Net, a dedicated
hosting division of Houston-based Everyones Internet (EVI.Net). Under the terms of the
agreement, SCO will provide EV1Servers.Net with a site license that allows the use of SCO IP in
binary form on all Linux servers managed by EV1Servers.Net in each of its hosting facilities.
EV1Servers.Net joins other Fortune 1000 companies that have signed up for a SCO IP license,
which was initially offered in August 2003. EV1Servers.Net is one of the world's leading
dedicated server providers, with more than 20,000 servers under management. The SCO site
license allows EV1Servers.Net and its customers to continue running business operations on
Linux servers without interruption or concern regarding SCO IP issues.
"The SCO agreement eliminates uncertainty from our clients' hosting infrastructure," says
Robert Marsh, Head Surfer and CEO of Everyones Internet. "Our current and future users now
enjoy the peace of mind of knowing that their websites and data are hosted on a SCO IP
compliant platform. This agreement demonstrates EV1's commitment to providing customers
with stable, long term solutions that they can depend on for their growth."
"The most valuable asset of any software company is its intellectual property," said Darl
McBride, president and CEO, The SCO Group. "Hundreds of millions of dollars have been
invested to make our UNIX software the robust, mature operating system that it is today. We
-more-
49
know it has tremendous value and are pleased that other companies -- like EV1Servers.Net --
recognize our investment and the importance of SCO's valuable IP asset as well."
The SCO IP licensing program was created in response to customer requests and is specifically
designed to provide end users with a license that allows them to continue running business
operations on a SCO IP compliant platform. On Jan. 15, 2004, SCO began offering the SCO IP
license to all companies worldwide. To learn more about the SCO IP licensing program, contact
a SCO representative or visit the SCO Website at:
http://www.thescogrogp.com/scosource/license-program.html.
About EV1Servers.Net
Houston, Texas-based EV1Servers is the world's leading dedicated server hosting provider, with over 20,000 web servers under
management The company is the first hosting provider to achieve SCO IP certification. For more information on EV1Servers,
visit http://www.ev1servers.net or call [redacted].
About SCO
The SCO Group (NASDAQ: SCOX) helps millions of customers in more than 82 countries to grow their businesses everyday.
Headquartered in Lindon, Utah, SCO has a worldwide network of more than 11,000 resellers and 4,000 developers. SCO Global
Services provides reliable localized support and services to partners and customers. For more information on SCO products and
services, visit http://thescogroup.com or http://www. sco.com
SCO and the associated SCO logo are trademarks or registered trademarks of The SCO Group, Inc. in the U.S. and other countries. UNIX is a
registered trademark of The Open Group. All other brand or product names are or may be trademarks of and are used to identify products or
services of, their respective owners.
Forward Looking Statements
This press release contains forward-looking statements about the value of SCO's intellectual property, the SCO IP licensing program and the
benefits received by SCO IP licensees. SCO wishes to advise readers that a number of important factors could cause actual results to differ
materially from those anticipated in such forward-looking statements. These and other factors that could cause actual results to differ materially
from those anticipated are discussed in more detail in SCO's filings with the Securities and Exchange Commission.
###
50
EXHIBIT 8
51
[This exhibit is Robert McMillan's article for InfoWorld, March 25, 2004, "SCO Linux licensee has second thoughts on deal": "Less than one month after becoming the first publicly announced purchaser of The SCO Group Inc.'s controversial intellectual property license for Linux, Houston-based Internet service provider Everyones Internet Ltd. is reconsidering the benefits of doing business with the Linux community's enemy number one."] 52-54
|