SCO–Linux controversies

From Wikipedia, the free encyclopedia
Jump to: navigation, search

The SCO–Linux controversies are a series of legal and public disputes between the software company SCO Group (SCO) and various Linux vendors and users. The SCO Group alleges that its license agreements with IBM means that source code that IBM wrote and donated to be incorporated into Linux was added in violation of SCO's contractual rights. Members of the Linux community disagree with SCO's claims; IBM, Novell and Red Hat have ongoing claims against SCO.

On August 10, 2007 a federal district court judge in SCO v. Novell ruled on summary judgment that Novell, not the SCO Group, is the rightful owner of the copyrights covering the Unix operating system. The court also ruled that "SCO is obligated to recognize Novell's waiver of SCO's claims against IBM and Sequent". After the ruling Novell announced they have no interest in suing people over Unix and stated "We don't believe there is Unix in Linux".[1][2][3][4] The final district court ruling, on November 20, 2008, affirmed the summary judgment, and added interest and a constructive trust.[5]

On August 24, 2009, the U.S. Court of Appeals for the Tenth Circuit partially reversed the district court judgment. The appeals court remanded back to trial on the issues of copyright ownership and Novell's contractual waiver rights. The court upheld the $2,547,817 award granted to Novell for the 2003 Sun agreement.[6]

On March 30, 2010, following a jury trial, Novell, and not The SCO Group, was unanimously found to be the owner of the UNIX and UnixWare copyrights.[7] The SCO Group, through bankruptcy trustee Edward Cahn, has decided to continue the lawsuit against IBM for causing a decline in SCO revenues.[8]

SCO–Linux controversies
Overview
Litigation
Companies involved
Individuals involved
Other

Background[edit]

At the beginning of 2003, SCO claimed that there had been "misappropriation of its UNIX System V code into Linux". However, the company refused to identify the specific segments of code, claiming that it was a secret which they would reveal only to the court. They did say that the code could be found in the SMP, RCU and a few other parts of the Linux kernel.

On 6 March 2003 they announced[9] that they were suing IBM for $1 billion, claiming that IBM transferred SCO trade secrets into Linux. That amount later rose to $3 billion, and then again to $5 billion.

Some educated parties[who?] note that the USL v. BSDi case had shown that the Unix copyrights are weak and unenforceable. SCO has not claimed patent infringement, as according to the US Patent and Trademark Office database, no AT&T or Novell patent was ever assigned to SCO. The UNIX trademark was not owned by SCO. That left arguing over trade secrets, which after some opposition, was hard to take beyond a breach of contract between SCO and IBM, and consequentially a claim only against IBM. SCO was looking for something directed at the greater Linux community, and has since explicitly dropped all trade secret claims from their case.

SCO now had little legal ground at this point and therefore began numerous legal claims and threats against many of the major names in the computer industry, including IBM, Hewlett-Packard, Microsoft, Novell, Silicon Graphics, Sun Microsystems and Red Hat.

By mid-2004, five major lawsuits had been filed

In cases SCO publicly implied that a number of other parties have committed copyright infringement, including not only Linux developers but also Linux users.

UNIX SVRx[edit]

SCO's claims are derived from several contracts that may have transferred UNIX System V Release 4 intellectual property assets. The UNIX IP rights originated with Unix System Laboratories (USL), a division of AT&T. In 1993, USL sold all UNIX rights and assets to Novell, including copyrights, trademarks, and active licensing contracts. Some of these rights and assets, plus additional assets derived from Novell's development work, were then sold to the Santa Cruz Operation in 1995. The Santa Cruz Operation had developed and was selling a PC-based UNIX until 2000, when it then resold its UNIX assets to Caldera Systems, which later reorganized into Caldera International and changed its name to SCO Group.

Through this chain of sales, SCO claims to be the "owner of UNIX". The validity of these claims is hotly contested by others. SCO claims copyright to all UNIX code developed by USL, referred to as SVRx, and licensing contracts originating with AT&T, saying that these are inherited through the same chain of sales. The primary document SCO presents as evidence of these claims is the "Asset Purchase Agreement",[10] defining the sale between Novell and the Santa Cruz Operation. SCO says that this includes all copyrights to the UNIX code base and contractual rights to the licensing base. The other parties disagree.

UNIX copyrights ownership[edit]

The status of copyrights from USL is murky, since UNIX code is a compilation of elements with different copyright histories. Some code was released without copyright notice before the Copyright Act of 1976 made copyright automatic. This code may be in the public domain and not subject to copyright claims. Other code is affected by the USL v. BSDi case, and is covered by the BSD License.

Groklaw uncovered an old settlement made between Unix System Laboratories (USL) and The University of California in the case of USL v. BSDi.[11] This settlement ended a copyright infringement suit against the University for making BSD source code freely available that USL felt infringed their copyrights. The university filed a counter suit, saying that USL had taken BSD source code and put it in UNIX without properly acknowledging the university's copyright. This settlement muddies the question of SCO's ownership of major parts of the UNIX source code. This uncertainty is particularly significant in regard to SCO's claims against Linux, which uses some BSD code.

Novell challenges SCO's interpretation of the purchase agreement. In response to a letter SCO sent to 1500 companies on May 12, 2003,[12] Novell exchanged a series of letters[13] with SCO beginning in May 2003, claiming that the copyrights for the core UNIX System V were not included in the asset purchase agreement and are retained by Novell. In October 2003, Novell registered those copyrights with the US Copyright Office.

In response to these challenges from Novell, SCO filed a "slander of title" suit against Novell, SCO v. Novell. This claimed that Novell was interfering with their business activities by clouding the ownership of UNIX copyrights. SCO's claim for special damages was dismissed on June 9, 2004 for "failure to specifically plead special damages."[14] However, SCO was given 30 days "to amend its complaint to more specifically plead special damages". In the same ruling, the judge expressed doubt that the Asset Purchase Agreement transferred the relevant copyrights.[citation needed]

SCO filed an amended complaint. In late July, 2005, Novell filed an answer to SCO's complaint, denying all of its accusations. Novell also filed its own Slander of Title counter-lawsuit against SCO. Novell has also filed claims for numerous breaches of the APA (Asset Purchase Agreement) between Novell and the Santa Cruz Operation. Under the APA, Santa Cruz (and later SCO after SCO purchased Santa Cruz Operation's Unix Business) was given the right to market and sell Unixware as a product, retaining 100% of all revenues. Santa Cruz Operation (and later SCO) also was given the responsibility of administering Unix SVR4 license agreements on behalf of Novell. When money was paid for licensing, SCO was to turn over 100% of the revenue to Novell, and then Novell would return 5% as an Administration Fee. Novell claims that SCO signed Unix SVR4 licensing agreements with Microsoft and Sun Microsystems, as well as with numerous Linux End Users for Unix IP allegedly in the Linux Kernel, and then refused to turn the money over to Novell. Novell is suing for 100% of the revenue, claiming SCO is not entitled to the 5% administration fee since they breached their contract with Novell. Novell's counterclaims proposed asking the court to put appropriate funds from SCO into escrow until the case is resolved, since SCO's cash is diminishing quickly.

Novell also retained the right to audit SCO's Unix Licensing Business under the APA. Novell claims that SCO has not turned over vital information about the Microsoft, Sun and Linux End User License Agreements, despite repeated demands by Novell for them to do so. Novell, in another claim that is part of their counter suit, is asking the court to compel SCO to allow Novell to perform this audit of SCO's Unix Business.

On August 10, 2007 Judge Dale Kimball, hearing the SCO v. Novell case, ruled that "...the court concludes that Novell is the owner of the UNIX and UnixWare Copyrights".[15][16]

License administration standing[edit]

The Novell to Santa Cruz Operation Asset Purchase Agreement also involved the administration of some 6000 standing licensing agreements between various UNIX users and the previous owners. These licensees include universities, software corporations and computer hardware companies. SCO's claimed ownership of the licenses has become an issue in three aspects of the SCO–Linux controversies. The first was the cancellation of IBM's license, the second was SCO's complaint against DaimlerChrysler (see SCO v. DaimlerChrysler), and the third is the derivative works claim of the SCO v. IBM case.

In May 2003, SCO canceled IBM's SVRx license to its version of UNIX, AIX. This was based on SCO's claim of unrestricted ownership of the System V licensing contracts inherited from USL. IBM ignored the license cancellation, claiming that an amendment to the original license[17] made it "irrevocable." In addition, as part of the Purchase Agreement, Novell retained certain rights of control over the administration of the licenses which were sold, including rights to act on SCO's behalf in some cases. Novell exercised one of these rights by revoking SCO's cancellation of the IBM license. SCO disputed the validity of both of these actions, and amended its SCO v. IBM complaint to include copyright infringement, based on IBM's continued sale and use of AIX without a valid SVRx license.

In December 2003, SCO demanded that all UNIX licensees certify some items, some related to the use of Linux, that were not provided for in the license agreement language. Since DaimlerChrysler failed to respond, SCO filed the SCO v. DaimlerChrysler suit in March 2004. All claims related to the certification demands were summarily dismissed by the court.

Control of derivative works[edit]

The third issue based on the UNIX licensees agreement is related to SCO's claims of control of derivative works.

Many UNIX licensees have added features to the core UNIX SVRx system and those new features contain computer code not in the original SVRx code base. In most cases, software copyright is owned by the person or company that develops the code. SCO, however, claims that the original licensing agreements define this new code as a derivative work. They also claim that they have the right to control and restrict the use and distribution of that new code.

These claims are the basis of SCO v. IBM. SCO's initial complaint,[18] said that IBM violated the original licensing agreement by not maintaining confidentiality with the new code, developed and copyrighted by IBM, and releasing it to the Linux project.

IBM claims that the license agreement (noted in the $Echo newsletter of April 1985)[19] and subsequent licenses defines derivative works as the developer's property. This leaves IBM free to do as it wishes with its new code. In August 2004, IBM filed a motion for partial summary judgment. The motion stated that IBM has the right to do as it wishes with software not part of the original SVRx code. In February 2005, the motion was dismissed as premature, because discovery was not yet complete. IBM refiled this motion along with other summary judgment motions as noted below in September 2006.[citation needed]

SCO allegations of copyright and trade secret violations[edit]

SCO claims that Linux infringes SCO's copyright, trade secrets, and contractual rights. This claim is fundamental to the SCOsource program, where SCO has demanded that Linux users obtain licenses from SCOsource to be properly licensed to use the code in question. Exactly which parts of Linux are involved remains unclear as many of their claims are still under seal in the SCO v. IBM lawsuit.

SCO originally claimed in SCO v. IBM that IBM had violated trade secrets. But these alleged violations by IBM would not have involved Linux distributors or end users. SCO's trade secret claims were dropped by SCO in their amended complaint.[20]

SCO also claimed line-for-line literal copying of code from UNIX code files to Linux kernel files and obfuscated copying of code, but originally refused to publicly identify which code was in violation. SCO submitted to the court evidence of their claims under seal but much of it was excluded from the case after it was challenged by IBM as not meeting the specificity requirements to be included.

These examples have fallen into two groups. The first are segments of files or whole files alleged to originate in UNIX SVRx code such as the errno.h header file. The second group are files and materials contributed by IBM that originated with IBM development work associated with AIX and Dynix, IBM's two UNIX products.

Each of these has a different set of issues. In order for copyright to be violated, several conditions must be met. First, the claimant must be able to show that they own the copyrights for the material in question. Second, all or a significant part of the source must be present in the infringing material. There must be enough similarity to show direct copying of material.

SVRx code allegedly in Linux[edit]

The issue of ownership of the SVRx code base was discussed above. Besides the unresolved issue of what was actually transferred from Novell to Santa Cruz Operation, there are also the portions of the SVRx code base that are covered by BSD copyrights or that are in the public domain.

SCO's first public disclosure of what they claim is infringing code was at SCO Forum in August 2003. The first, known as the Berkeley Packet Filter, was distributed under the BSD License and is freely usable by anyone. The second example was related to memory allocation functions, also released under the BSD License. It is no longer in the Linux code base.[21]

SCO has also claimed that code related to application programming interfaces was copied from UNIX. However, this code and the underlying standards they describe are in the public domain and are also covered by rights USL sold to The Open Group.[22] A later claim was made to code segments related to ELF file format standards. This material was developed by the Tool Interface Standard (TIS) Committee and placed in the public domain.[23] SCO claims that the TIS Committee had no authority to place ELF in the public domain, even though SCO's predecessor in interest was a member of the committee.[citation needed]

SCO has claimed that some are violating UNIX SVRx copyrights by putting UNIX code into Linux. They may or may not have brought this claim directly in any of their cases. The IBM case is about derivative works, not SVRx code (see below). The Novell case is about copyright ownership. DaimlerChrysler was about contractual compliance statements.

The "may or may not" comes from AutoZone's case.[original research?] In AutoZone, SCO's complaint claimed damages for AutoZone's use of Linux. However, when objecting to AutoZone's request for a stay pending the IBM case, SCO apparently contradicted their written complaint, claiming that the case was entirely about AutoZone copying certain libraries (outside the Linux kernel) from a UNIX system to a Linux-based system to facilitate moving an internal application to the Linux platform faster; SCO's original complaint does not appear to mention these libraries. AutoZone denies having done this with UNIX libraries. If SCO's oral description of their case is the correct one, then their AutoZone claim has nothing to do with the Linux kernel or the actions of any distributors.

The copyright issue is addressed directly in two of the cases. The first is by IBM in their counterclaim in SCO v. IBM. The issue is central to a pending motion by IBM, stating that IBM violated no copyrights in its Linux related activities. It is also addressed by Red Hat in the Red Hat v. SCO case. Red Hat claims that SCO's statements about infringement in Linux are unproven and untrue, damaging to them and violates the Lanham Act. Red Hat asks for an injunction to stop claims of violations without proof. They also ask for a judgment that they violated no SCO copyrights. A hearing on the IBM motion was held on September 15, 2004. Judge Kimball took the motion under advisement. The Red Hat case is on hold.

Allegations of reverse copying[edit]

EWeek has reported allegations that SCO may have copied parts of the Linux kernel into SCO UNIX as part of its Linux Kernel Personality feature.[24] If true, this would mean that SCO is guilty of a breach of the Linux kernel copyrights. SCO has denied this allegation, but according to Groklaw, one SCO employee confirmed it in a deposition.[25]

IBM code in Linux[edit]

SCO has claimed a number of instances of IBM Linux code as breaches of contract. These examples include code related to Symmetric multiprocessing (SMP), Journaled File System (JFS), Read-copy-update (RCU) and Non-Uniform Memory Access (NUMA). This code is questionably in the Linux kernel,[citation needed] and may have been added by IBM through the normal kernel submission process. This code was developed and copyrighted by IBM. IBM added features to AIX and Dynix.

SCO claims that they have "control rights" to this due to their licensing agreements with IBM. SCO disavows claiming that they own the code IBM wrote, rather comparing their "control rights" to an easement, rights which allow them to prohibit IBM from publicizing the code they wrote, even though IBM owns the copyrights. They base this claim on language in the original license agreement that requires non-disclosure of the code and claim that all code developed by UNIX licensees that is used with the code under license be held in confidence. This claim is discussed above at Control of derivative works.

SCO and the GPL[edit]

Before changing their name to the SCO Group, the company was known as Caldera International.

Caldera was one of the major distributors of Linux between 1994 and 1998. In August 1998, the company split into Caldera Systems and Caldera Thin Clients, with Caldera Systems taking over the Linux systems business and Caldera Thin Clients concentrating on the Thin Clients and embedded business. The parent and shell company Caldera, Inc. ceased to exist in 2000 after a settlement with Microsoft in the Caldera v. Microsoft lawsuit.

Caldera Systems was reorganized to become Caldera International in 2001, the company, which was renamed to The SCO Group in 2002.

Some, like Eben Moglen,[26] have suggested that because Caldera[citation needed] distributed the allegedly infringing code under the GNU General Public License, or GPL, that this act would license any proprietary code in Linux.[27]

SCO has stated that they did not know their own code was in Linux, so releasing it under the GPL does not count. However, as late as July and August 2006, long after that claim was made, they were still distributing ELF files (the subject of one of SCO's claims regarding SVRx) under the GPL.[28][29]

SCO has also claimed, in early stages of the litigation, that the GPL is invalid and non-binding and legally unenforceable.[30] In response, supporters of the GPL, such as Eben Moglen, claimed that SCO's right to distribute Linux relied upon the GPL being a valid copyright license.[31] Later court filings by the SCO Group in SCO v. IBM use SCO's alleged compliance with the license as a defense to IBM's counterclaims.[32]

The GPL has become an issue in SCO v. IBM. Under U.S. copyright law, distribution of creative works whose copyright is owned by another party is illegal without permission from the copyright owner, usually in the form of a license; the GPL is such a license, and thus allows distribution, but only under limited conditions. Since IBM released the relevant code under the terms of the GPL, it claims that the only permission that SCO has to copy and distribute IBM's code in Linux is under the terms and conditions of the GPL, one of which requires the distributor to "accept" the GPL. IBM says that SCO violated the GPL by denouncing the GPL's validity, and by claiming that the GPL violates the U.S. Constitution, together with copyright, antitrust and export control laws. IBM also claims that SCO's SCOsource program is incompatible with the requirement that redistributions of GPLed works must be free of copyright licensing fees (fees may be charged for the acts of duplication and support). IBM has brought counterclaims alleging that SCO has violated the GPL and breached IBM's copyrights by collecting licensing fees while distributing IBM's copyrighted material.[33]

Status of current lawsuits[edit]

SCO v. IBM[edit]

Main article: SCO v. IBM

On March 7, 2003, SCO filed suit against IBM. Initially this lawsuit was about breach of contract and trade secrets. Later, SCO dropped the trade secrets claim, so the claim is breach of contract. SCO also added a copyright claim related to IBM's continued use of AIX, but not related to Linux. The judge subsequently stated that the SCO Group had indeed made a claim of copyright infringement against IBM regarding Linux. IBM filed multiple counter claims, including charges of both patent violations, which were later dropped, and violation of copyright law. Discovery in the case is still underway.

On February 8, 2005 Judge Kimball ruled that IBM's motions for summary judgment were premature but added:

Viewed against the backdrop of SCO's plethora of public statements concerning IBM's and others' infringement of SCO's purported copyrights to the UNIX software, it is astonishing that SCO has not offered any competent evidence to create a disputed fact regarding whether IBM has infringed SCO's alleged copyrights through IBM's Linux activities.[34]

On June 28, 2006 Judge Brooke Wells granted, in part, IBM's motion to limit SCO's claims and excluded 186 of SCO's 294 items of allegedly misused intellectual property (IBM had challenged 201 of them for various reasons).[35] Wells cited a number of factors including SCO's inability to provide sufficient specificity in these claims:

In December 2003, near the beginning of this case, the court ordered SCO to, "identify and state with specificity the source code(s) that SCO is claiming forms the basis of their action against IBM." Even if SCO lacked the code behind methods and concepts at this early stage, SCO could have and should have, at least articulated which methods and concepts formed "the basis of their action against IBM." At a minimum, SCO should have identified the code behind their method and concepts in the final submission pursuant to this original order entered in December 2003 and Judge Kimball’s order entered in July 2005.[36]

This left about 100 of SCO's items of allegedly misused intellectual property (the merits of which have not yet been judged), out of 294 items originally disclosed by SCO.

Following the partial summary judgment rulings in the SCO vs Novell Slander of Title case, Judge Kimball asked[37] the parties in SCO v IBM to prepare by August 31, 2007 a statement of the status of this case.

Red Hat v. SCO[edit]

Main article: Red Hat v. SCO

Red Hat filed suit against SCO on August 4, 2003. Red Hat sued SCO for false advertising, deceptive trade practices and asked for a declaratory judgment of noninfringement of any of SCO's copyrights. This case has been stayed pending resolution of the IBM case.

SCO v. Novell[edit]

Main article: SCO v. Novell

After SCO initiated their Linux campaign, they said that they were the owners of UNIX. Novell claimed these statements were false, and that they still owned the rights in question. After Novell registered the copyrights to some key UNIX products, SCO filed suit against Novell on January 20, 2004.[38] Novell removed the suit to federal court on February 6, 2004.[39]

On July 29, 2005, Novell filed its answer with the court, denying SCO's claims. Novell also filed counterclaims asking the court to force SCO to turn over the revenues it had received from UNIX licenses, less a 5% administrative fee. Additionally, Novell asked the court to place the funds in a "constructive trust" in order to ensure that SCO could pay Novell since the company's assets were depleting rapidly.

On August 10, 2007, Judge Dale Kimball, hearing the SCO v. Novell case, ruled that "...the court concludes that Novell is the owner of the UNIX and UnixWare Copyrights". Novell was awarded summary judgments on a number of claims, and a number of SCO claims were denied. SCO was instructed to account for and pass to Novell an appropriate portion of income relating to SCOSource licences to Sun Microsystems and Microsoft. A number of matters are not disposed of by Judge Kimball's ruling, and the outcome of these are still pending.[1][16]

On July 16, 2008, the trial court issued an order awarding Novell $2,547,817 and ruled that SCO was not authorized to enter into the 2003 agreement with Sun.[40] On November 20, 2008, final judgment in the case[5] affirmed the August 10 ruling, and added interest of $918,122 plus $489 per diem after August 29, 2008, along with a constructive trust of $625,486.90.

On August 24, 2009, the U.S. Court of Appeals for the Tenth Circuit partially reversed the August 10, 2007 district court summary judgment ruling. The appeals court remanded back to trial on the issues of copyright ownership and Novell's contractual waiver rights. The court upheld the $2,547,817 award granted to Novell for the 2003 Sun agreement.[6] On March 30, 2010, after a three-week trial before Judge Ted Stewart, a jury returned a verdict "confirming Novell's ownership of the Unix copyrights."[41]

On June 10, 2010, Judge Ted Stewart denied SCO's motion for another trial and ruled for Novell on all remaining issues.[42]

On July 7, 2010, SCO appealed the new judgments to the United States Court of Appeals for the Tenth Circuit.[43]

On August 30, 2011, the Tenth Circuit Court of Appeals affirmed the District Court ruling in its entirety, rejecting SCO's attempt to re-argue the case before the Court of Appeals.[44]

SCO v. AutoZone[edit]

AutoZone, a corporate user of Linux and former user of SCO OpenServer, was sued by SCO on March 3, 2004.[45] SCO claims AutoZone violated SCO's copyrights by using Linux. The suit was stayed pending the resolution of the IBM, Red Hat and Novell cases.

On September 26, 2008, Judge Robert C. Jones lifted the stay, effective December 31, 2008.[46] He initially scheduled discovery for April 9, 2010.[47] SCO filed an amended complaint on August 14, 2009. On August 31, 2009, AutoZone replied, and filed a motion to dismiss in part.[48]

On October 22, 2009, Edward Cahn, SCO's Chapter 11 trustee, sought bankruptcy court approval for an agreement he reached with AutoZone. According to the court filings, the confidential settlement resolves all claims between SCO and AutoZone.[49]

SCO v. DaimlerChrysler[edit]

Main article: SCO v. DaimlerChrysler

In December 2003, SCO demanded that some UNIX licensees certify certain issues regarding their use of Linux. DaimlerChrysler, a former UNIX user and current Linux user, did not respond to this demand. On March 3, 2004 SCO filed suit against DaimlerChrysler for violating their UNIX license agreement by failing to respond to the certification request. Almost every claim SCO made has been ruled against in summary judgment.[50] The last remaining issue, that of whether DaimlerChrysler made a timely response, was dismissed by agreement of SCO and DaimlerChrysler in December 2004. SCO retains the right to continue this case at a future date, providing it pays legal fees to DaimlerChrysler.

Other issues and conflicts[edit]

SCO announces that it will not sue its own customers[edit]

On June 23, 2003, SCO sent out a letter announcing that it would not be suing its own Linux customers.[51] In the letter, it states:

"SCO will continue to support our SCO Linux and OpenLinux customers and partners who have previously implemented those products and we will hold them harmless from any SCO intellectual property issues regarding Linux."

SCO and SGI[edit]

In August 2003, SCO presented two examples of what they claimed was illegal copying of copyrighted code from UNIX to Linux. One of the examples (Berkeley Packet Filter) was not related to original UNIX code at all. The other example did, however, seem to originate from the UNIX code and was apparently contributed by a UNIX vendor, Silicon Graphics. However, an analysis by the Linux community later revealed that:

  • The code originated from an even older version of UNIX which at some point was published by Caldera[citation needed], thus making any claim of copyright infringement shaky.
  • The code did not do anything. It was in a part of the Linux kernel that was written in anticipation of a Silicon Graphics architecture that was never released.
  • It had already been removed from the kernel two months earlier.
  • The contested segment was small (80 lines) and trivial.

SCO and BayStar Capital[edit]

In October 2003, BayStar Capital and Royal Bank of Canada invested US$50 million in The SCO Group to support the legal cost of SCO's Linux campaign. Later it was shown that BayStar was referred to SCO by Microsoft, whose proprietary Windows operating system competes with Linux. In 2003, BayStar looked at SCO on the recommendation of Microsoft, according to Lawrence R. Goldfarb, managing partner of BayStar Capital: "It was evident that Microsoft had an agenda".[52]

On April 22, 2004, The New York Times reported that BayStar Capital, a private hedge fund which had arranged for $50M in funding for SCO in October 2003, was asking for its $20M back. The remainder of the $50M was from Royal Bank of Canada. SCO stated in their press release that they believed that BayStar did not have grounds for making this demand.[53]

On August 27, 2004 SCO and BayStar resolved their dispute.[54]

SCO and Canopy Group[edit]

The Canopy Group is an investment group with shares in a trust of different companies. It is a group owned by the Noorda family, also founders of Novell.

Until February 2005, Canopy held SCO shares, and the management of SCO held shares of Canopy. The two parties became embroiled in a bitter dispute when the Noorda family sought to oust board member Ralph Yarro III on claims of misappropriation. With internal problems not made public (which included the suicides of Canopy's director of information systems, Robert Penrose,[55] and Val Kriedel, the daughter of Ray Noorda[56]),[57][58][59] the Canopy Group agreed to buy back all the shares that SCO had in Canopy in exchange for their SCO shares and cash.

SCO and Canopy Group are now mostly independent, though SCO continues to rent their Utah office space from Canopy.[60]

Microsoft funding of SCO controversy[edit]

On March 4, 2004, a leaked SCO internal e-mail detailed how Microsoft had raised up to $106 million via the BayStar referral and other means.[61] Blake Stowell of SCO confirmed the memo was real.[62] BayStar claimed the deal was suggested by Microsoft, but that no money for it came directly from them.[63] In addition to the Baystar involvement, Microsoft paid SCO $6M (USD) in May 2003 for a license to "Unix and Unix-related patents", despite the lack of Unix-related patents owned by SCO.[64] This deal was widely seen in the press as a boost to SCO's finances which would help SCO with its lawsuit against IBM.[65][66]

SCOsource[edit]

After their initial claim of copyright infringement in the Linux kernel, The SCO Group started their SCOsource initiative which sells licenses of SCO's claimed copyrighted software, other than OpenServer and Unixware licenses. After a small number of high profile sales (including one that was denied by the claimed purchaser), SCO claimed to offer corporate users of Linux a license at $699 (USD) per processor running Linux. However, many individuals have found it impossible to buy such a license from SCO. SCO says that participants of the SCOsource initiative are not liable for any claims that SCO makes against Linux users.

The Michael Davidson E-Mail[edit]

On July 14, 2005, an email[67] was unsealed that had been sent from Michael Davidson to Reg Broughton (both Caldera International employees) in 2002, before many of the lawsuits. In it, Davidson reported how the company had hired an outside consultant because

The consultant was to review the Linux code and compare it to Unix source code, to find possible copyright infringement. Davidson himself said that he had not expected to find anything significant based on his own knowledge of the code and had voiced his opinion that it was "a waste of time". After 4 to 6 months of consultant's work, Davidson says: "...we had found absolutely *nothing*. i.e. no evidence of any copyright infringement whatsoever."[67]

See also[edit]

Portal icon Free software portal

References[edit]

  1. ^ a b MEMORANDUM DECISION AND ORDER Civil Case No. 2:04CV139DAK
  2. ^ Montalbano, Elizabeth (2007-08-15). "Novell Won't Pursue Unix Copyrights". PC World. Retrieved 2007-09-04. 
  3. ^ Markoff, John (2007-08-11). "Judge Says Unix Copyrights Rightfully Belong to Novell". New York Times. Retrieved 2007-08-15. 
  4. ^ "Court Rules: Novell owns the UNIX and UnixWare copyrights! Novell has right to waive!". Groklaw. 2007-08-10. Retrieved 2007-08-15. 
  5. ^ a b Kimball, Dale (November 20, 2008). "Final Judgment in SCO v. Novell: SCO Loses Again". United States District Court for the District of Utah. Groklaw. Retrieved 2008-11-20. 
  6. ^ a b "Appeal from the United States District Court for the District of Utah" (PDF). U.S. Court of Appeals for the Tenth Circuit. August 24, 2009. Retrieved August 26, 2009. 
  7. ^ 03/30/2010 - 846 - JURY VERDICT for Defendant Novell. (slm) (Entered: 03/30/2010)
  8. ^ Jury says Novell owns Unix copyrights
  9. ^ CNET news article
  10. ^ in the original or transcribed
  11. ^ The full settlement available from Groklaw's website
  12. ^ May 12, 2003 letter to Novell Chairman and CEO Jack Messman hosted by Novell.
  13. ^ Novell's Unique Legal Rights
  14. ^ Judge Kimbal's Order available from Groklaw's website
  15. ^ Memorandum order and decision, document 377 in case 2:04CV139DAK, the court order on Groklaw
  16. ^ a b Novell statement on today’s SCO ruling[dead link], Novell Open PR, 2007-08-10
  17. ^ Groklaw - Amendment X as Text
  18. ^ The SCO Group v
  19. ^ Groklaw - $ echo April 1985
  20. ^ The SCO Group v
  21. ^ Bruce Perens, Analysis of SCO's Las Vegas Slide Show[dead link] Archived April 6, 2010 at the Wayback Machine
  22. ^ Bruce Perens, SCO's failing case against IBM[dead link], zdnet.com.au, March 10, 2004.
  23. ^ Groklaw - A Tall Tale About ELF - by Frank Sorenson, Dr Stupid and PJ
  24. ^ Did SCO Violate the GPL?
  25. ^ Groklaw - Erik Hughes Deposition: LKP Did Include Linux Kernel Code
  26. ^ Moglen, Eben (2003-06-27). "FSF Statement on SCO v. IBM". Free Software Foundation, Inc. 
  27. ^ SCO Faces Hurdles in Linux Claims
  28. ^ Groklaw - SCO is Distributing ELF Under the GPL Still. Yes. Now. Today
  29. ^ Groklaw - SCO Is Still Distributing ELF Under the GPL, Part 2
  30. ^ SCO Group Launches Broadside Against GPL
  31. ^ GPL Awaits Test in SCO Group/IBM Dispute
  32. ^ Groklaw - SCO's Memo in Opp. to IBM's Motion for SJ on Claim of Copyright Infringement
  33. ^ Groklaw - IBM's Second Amended Counterclaims Lists 9 Newly Registered Copyrights
  34. ^ Groklaw - Kimball Memorandum and Order - as text
  35. ^ Groklaw - Wells Grants in Part IBM's Motion to Limit SCO's Claims! In *Large* Part
  36. ^ (paragraph 30)
  37. ^ http://www.groklaw.net/pdf/IBM-1077.pdf
  38. ^ "SCO's Complaint In the Third Judicial District Court of Salt Lake County, State of Utah". 2004-01-20. 
  39. ^ "Novell's Removal Notice". Groklaw. 2004-02-06. 
  40. ^ Kimball, Dale (July 16, 2008). "Findings of Fact, Conclusions of Law, and Order" (PDF). United States District Court for the District of Utah. Groklaw. Retrieved 2008-07-17. 
  41. ^ Harvey, Tom (2010-03-30). "Jury says Novell owns Unix copyrights". The Salt Lake Tribune. MediaNews Group. 
  42. ^ "Groklaw - Stewart Rules: Novell Wins! CASE CLOSED!". 
  43. ^ "Notice of Appeal". Groklaw. 2010-07-07. Retrieved 2010-07-07. 
  44. ^ "Order and Judgment". Groklaw. 2011-08-30. Retrieved 2011-08-31. 
  45. ^ Primary court documents pertaining to this case can be found at http://sco.tuxrocks.com/?Case=AutoZone.
  46. ^ "Stay Lifted on AutoZone as of December 31st - Updated". Groklaw. 2008-09-26. Retrieved 2009-10-23. 
  47. ^ "Members Only -- Docket Update - BK and AutoZone". Groklaw. 2009-01-21. Retrieved 2009-10-23. 
  48. ^ "Autozone Timeline". Groklaw. Retrieved 2009-10-23. 
  49. ^ "SCO's Chapter 11 Trustee Moves to Settle AutoZone". Groklaw. 2009-10-22. Retrieved 2009-10-23. 
  50. ^ Not dismissed, see the hearing transcript, page 15
  51. ^ The SCO Group, Inc. | Scosource | Letter_to_partners[dead link]
  52. ^ Lohr, Steve (April 22, 2004). "TECHNOLOGY; Investor's Pullout Stirs Doubts About SCO Group". The New York Times. Retrieved May 23, 2010. 
  53. ^ TECHNOLOGY; Investor's Pullout Stirs Doubts About SCO Group
  54. ^ SCO closes BayStar deal
  55. ^ [1] Rob Penrose
  56. ^ [2] Noorda bio
  57. ^ Daily Herald - Canopy founder's daughter found dead
  58. ^ [3] Canopy at Heart of Feud
  59. ^ [4][dead link] Sex, Drugs, and Unix
  60. ^ Jones, Pamela (2007-12-19). "SCO Asks Bankruptcy Court to Approve New Leases in NJ and Utah". Groklaw. 
  61. ^ Halloween Document 10
  62. ^ Leaked Memo Revives SCO-Microsoft Connection Furor
  63. ^ BW Online | March 11, 2004 | SCO's Suit: A Match Made in Redmond?
  64. ^ SCO strikes gold, Verizon just strikes | InfoWorld | Column | 2003-08-08 | By Robert X. Cringely
  65. ^ Microsoft to license Unix code | CNET News.com
  66. ^ The SCO Group | Investor Relations | SCO Announces UNIX Licensing Deal With Microsoft
  67. ^ a b http://www.groklaw.net/pdf/IBM-459-22.pdf

External links[edit]
Organization
Linux kernel
Support
Technical
Debugging
Start-up process
ABIs
APIs
in userspace
FS, daemons
wrapper libraries
part of kernel
System Call Interface
In-kernel
Linux kernel
components
Variants
Virtualization
Linux adoption
Linux range of use
Adopters
People
General
Operating system
families
Development
History
Organizations
Licenses
License types
and standards
Challenges
Related topics
Retrieved from "http://en.wikipedia.org/w/index.php?title=SCO–Linux_controversies&oldid=634258936"