Unix Ownership Battle Refuses to Die: Xinuos Revives Claims Against IBM in 2026 Hearing

The ancient dispute over ownership of UNIX, and perhaps Linux too, has returned to court. Again. The latest twist arrived on June 22 when Xinuos, the company that acquired assets from the long-troubled SCO Group, faced off against IBM in a federal appeals court hearing that mixed 1990s code-sharing agreements with modern procedural arguments.

Simon Sharwood laid out the essentials in a report for The Register. The roots trace to 1998. IBM teamed with Santa Cruz Operation, then a vendor of UNIX for x86 systems. Intel and Sequent joined them in Project Monterey. The goal was straightforward. Build one unified UNIX that ran well across multiple processors and hardware types. Code from both IBM and SCO flowed into the effort. By 2001 the project stood close to delivering results.

Then Linux gained traction. It already ran on multiple processors. IBM saw the momentum and walked away from Monterey. SCO later claimed IBM took elements of the joint work and contributed them to Linux as well as its own AIX and z/OS systems. The accusation triggered a 2003 lawsuit. SCO demanded billions. The case dragged through years of motions, bankruptcies and appeals. Most observers thought it had finally ended in 2021. That year brought a settlement between the parties with no admission of fault from IBM, according to coverage in ZDNet.

But the story refused to stay buried. SCO had sold its UNIX software business and related intellectual property to Xinuos in 2011. At first the new owner signaled it wanted to focus on products rather than litigation. That stance shifted. In 2021 Xinuos filed fresh claims against both IBM and Red Hat. The suit accused the two companies of copyright infringement, antitrust violations and misuse of Xinuos code in their server operating systems. A Slashdot summary of the latest developments captured the mood. The dispute had become a zombie that kept shuffling forward.

The June 22 hearing, available as an audio recording on CourtListener, revisited the same core questions. Did IBM hold a valid license to the SCO-derived code under the original Monterey agreements? Could Xinuos still assert rights to that code decades later? Lawyers for Xinuos argued that IBM never received proper licensing for certain SCO contributions. IBM’s side countered that the contracts permitted its actions and that any claims had long since expired under statutes of limitations or prior settlements.

Observers noted procedural oddities. The hearing took place online. At one point the judge appeared to speak while muted, an accidental reminder that even high-stakes intellectual property fights now occur over video links. Yet the substance stayed old school. Arguments circled back to Project Monterey, the precise wording of license grants from the late 1990s, and whether earlier litigation had fully resolved ownership questions.

And the stakes still matter. A victory for Xinuos could reopen questions about code provenance in Linux distributions and IBM’s enterprise products. Even a narrow procedural win might allow discovery that forces IBM to produce decades-old engineering records. The company has long maintained that Linux development followed clean-room principles and that no infringing code entered its contributions.

Yet the broader context has changed. Linux now powers the majority of cloud infrastructure, smartphones through Android, and countless servers. IBM itself embraced open source after acquiring Red Hat in 2019 for $34 billion. The idea that a successor to a bankrupt vendor from the early 2000s could still extract significant damages feels distant to many in the industry. Still, the case persists.

Xinuos has kept the litigation alive through multiple rounds of motions. Recent social media discussion on X reflected familiar skepticism. One Japanese account summarized the hearing by noting that even after SCO’s bankruptcy, asset sale for roughly $600,000 and a $14.25 million settlement, the fight returned to federal appeals court with changed parties and slightly updated legal theories. The code under discussion remains the same material written for that 1998 joint project.

Legal experts following the matter point to a central tension. Contract language drafted before Linux’s rise must now be interpreted in an era when open-source contributions drive trillion-dollar markets. IBM has consistently denied any wrongdoing. It has also argued that Xinuos lacks standing to bring certain claims because prior agreements transferred or extinguished those rights.

The hearing did not produce an immediate ruling. The court will likely issue a written decision in coming months that could either dismiss the case or send it back for further proceedings in district court. Either outcome risks additional appeals. So the dispute could easily stretch into 2027 or beyond. Some veterans of the original SCO litigation joke that resolution will arrive only at the heat death of the universe. Or the year of Linux on the desktop. Whichever comes first.

Meanwhile the UNIX trademark itself rests safely with The Open Group, an industry standards body. That organization certifies compliant systems under the Single UNIX Specification. Systems such as IBM’s AIX, Oracle’s Solaris and even macOS have earned the designation after paying fees. The trademark fight that once consumed SCO’s energy has long been settled. The current battle concerns copyrights and contract interpretation instead.

Recent coverage has stayed measured. No new bombshell documents emerged from the June hearing. No surprise witnesses appeared. The arguments sounded familiar to anyone who followed the original case. But the persistence itself carries weight. It shows how intellectual property claims born in the client-server era can linger into the cloud age. Companies that build on decades-old codebases must still account for license terms written when the internet ran on dial-up.

Xinuos continues to sell updated versions of OpenServer and UnixWare. Those products maintain a small but real customer base in industries that value binary compatibility with older applications. The company’s decision to pursue litigation alongside product development suggests it sees strategic value in clarifying its rights. IBM and Red Hat, for their part, have shown no public sign of concern. Their statements over the years have emphasized confidence in the strength of their licenses and the openness of Linux development.

So the case shuffles on. Short bursts of legal activity. Long periods of quiet. Another hearing. Another set of briefs. The code in question is older than many engineers now working on cloud-native systems. Yet the documents that govern its use still command courtroom time. That fact alone makes the saga noteworthy for anyone who follows software governance, open source licensing or the long shadow of 1990s enterprise deals.

Whether this latest revival produces meaningful precedent or simply burns more legal fees remains uncertain. What is clear is that the question of who owns which pieces of UNIX has outlived the original companies, multiple bankruptcies and several generations of technology. The zombie keeps moving. And the courts keep listening.