The SCO Wars
Linux, Unix copyrights, and a seven-year legal fight over open source
In 2003, The SCO Group sued IBM and claimed that Linux contained Unix code SCO controlled. The case stretched for years, unsettled enterprise Linux users, and eventually collapsed when courts found that SCO did not own the copyrights it had sued over.
Background
SCO's history with Linux was complicated. In August 2000, Caldera — then a Linux company — acquired SCO assets in a deal meant to combine Unix and Linux strengths. By 2003 the company, renamed The SCO Group under CEO Darl McBride, was struggling as Linux displaced its Unix products. Its response was litigation, not a stronger product.
SCO v. IBM
On March 7, 2003, SCO filed suit against IBM, alleging breach of contract and copyright infringement tied to Unix. The claim was enormous in scope: that Linux contained stolen Unix code, and that commercial Linux users might owe SCO licensing fees.
SCO also sent letters to commercial Linux users asserting intellectual property claims. The practical effect was fear, uncertainty, and doubt — hesitation among enterprises that were adopting or considering Linux.
Pushback
The response from the Linux ecosystem was organized. Red Hat sued SCO in August 2003, arguing that SCO was harming the Linux market by spreading uncertainty. IBM contested the claims with substantial legal resources. Independently, developers examined SCO's public allegations and argued that cited material was original Linux code, predated Unix, or had been contributed under valid terms.
The ownership problem
SCO's case depended on owning Unix copyrights. In related litigation, courts concluded those rights had not transferred as SCO claimed and remained with Novell. Novell also waived SCO's claims against IBM and Sequent and stated it did not believe Unix code was in Linux.
In 2009 a jury found that the Unix copyrights never transferred to SCO. SCO's stock fell sharply afterward. The company later terminated McBride's contract and moved toward bankruptcy. The legal assault on Linux failed.
What the episode showed
A few points still matter:
- Collaborative development is not, by itself, copyright infringement.
- Intellectual property claims need clear ownership; SCO sued over rights it did not hold.
- The open source community and commercial vendors can defend a project with both technical review and litigation.
- Enterprise confidence in Linux grew after the claims were tested in court.
The cost was real — years of uncertainty and large legal expenses — but the outcome strengthened Linux's legal footing rather than weakening it.