The SCO controversy around Linux involved several disputes and several kinds of legal claim. To understand it, keep the parties, rights, documents and procedural stage attached to each statement. A press release, a complaint and a final decision answer different questions.
This historical guide concentrates on the copyright-ownership branch between SCO and Novell and the public Linux concerns surrounding it. It explains how to read the evidence, with particular attention to the 2009 and 2011 appeals. It is not a complete docket history of every SCO-related case.
Separate the questions before reading the claims
Ownership asks who holds a particular right. Infringement asks whether a particular act violates a protected right. Contract asks what obligations or permissions an agreement creates. A party may raise several of these issues, but evidence about one does not automatically resolve the others.
The U.S. Copyright Office's computer-program registration circular distinguishes copyrightable program expression from functional aspects such as algorithms and system design. For a software dispute, identify the specific material and asserted rights, the relevant agreement, and the conduct at issue before interpreting a broad claim about an operating system.
The historical SCO–Novell question centered on rights in earlier UNIX and UnixWare technology and the meaning of transaction documents. That is a narrower, more precise question than whether all software described as “Linux” is lawful or unlawful.
Follow the ownership dispute through its procedural stages
On a small screen, scroll the table sideways to read all columns.
| Date or period | Record and event | How to interpret it |
|---|---|---|
| 2003 | SCO-related claims generated public concern; Eben Moglen issued an FSF response. | A dated advocacy statement explains the author's position at that time. |
| 2007 | The district court resolved key ownership issues in Novell's favor on summary judgment. | Read it together with the later appeal; this was not the end of the ownership proceedings. |
| August 24, 2009 | The Tenth Circuit reversed in part and remanded, including disputed ownership-related issues. | The decision required further proceedings on those issues; it did not award SCO the copyrights. |
| 2010 | After remand, a jury found that Novell owned the disputed copyrights; the judge separately addressed contractual rights. | Distinguish the jury's finding from the judge's determinations. |
| August 30, 2011 | The Tenth Circuit affirmed the challenged determinations in its second appeal decision. | The decision is an unpublished order and judgment, with the status identified in its opening footnote. |
The 2009 published appellate opinion, No. 08-4217, explains the transaction, district-court proceedings and issues sent back for further consideration. Its conclusion affirms some matters and reverses others. Summarizing the entire decision with a single “won” or “lost” obscures that division.
The 2011 unpublished order and judgment, No. 10-4122, opens by explaining the earlier remand, the jury's ownership finding and the separate ruling on Novell's retained contractual rights. The appellate court affirmed. Read those opening pages and the conclusion before following an argument quoted from the middle of the opinion.
Read the documents in the right role
Eben Moglen's June 25, 2003 FSF statement is a primary source for the FSF's response to the controversy. It is valuable for understanding contemporary arguments and concerns. Its statements should be attributed to their author and date, and assessed separately from what a court later found.
A complaint sets out what a party alleges and requests. A motion asks the court to act. A brief argues for a position. An opinion explains judicial reasoning. A judgment or order records an outcome or procedural direction. Exhibits can contain important agreements or correspondence, but their significance depends on authenticity, context and the issue being decided.
Within an opinion, watch for changes in voice: a court may summarize SCO's argument, quote Novell's position, describe a lower-court ruling and then reach its own conclusion. Copying a sentence without that context can reverse its meaning.
Make a small evidence record
- Record the case name, court, docket number, document number and filing date from the document itself.
- Write the specific question in one sentence, such as whether an agreement transferred particular copyrights.
- Label the statement as an allegation, party argument, evidence description, finding or holding.
- Read the surrounding section and the conclusion. Record what the court actually did and which issues remained.
- Follow the later procedural history for the same issue before using the result in a summary.
The worksheet below is designed for this kind of reading. Keep your paraphrase separate from short source quotations, and include a page reference that another reader can locate in the original PDF.
Keep historical findings and current compliance distinct
The outcome of this ownership dispute has a defined scope. A current software release still requires its own component provenance, license identification and review of how copies are used or distributed. Document the actual code and permissions for that release; a historical case name cannot replace that work.
For a concrete modern compliance task, use Open-Source Licenses: A Practical Compliance Workflow. For an actual legal demand, preserve the documents and involve qualified counsel with the relevant facts and jurisdiction. The transferable habit is precise evidence: who asserted what, about which material, under which agreement, and with what adjudicated result.
Keep a working record
Download the sco evidence reading record (plain text). Save a copy and fill in the evidence for your own task.