Product1 distinct publisher3 min readPublished
The long Linux ownership fight ends on an accrual rule rather than on ownership: the panel called IBM's 2001 taking a one-time event, so the clock closed years before the 2021 filing.
The Product Desk · Product desk

Compiled by The Product DeskSomething wrong?How this is made
Two clocks were available to the panel, and only one of them was ever going to help Xinuos. Under the Copyright Act an infringement claim can be brought within three years of any infringing act, so a defendant that keeps shipping keeps supplying fresh starting points; an ownership claim accrues once, when a diligent plaintiff should have known about it [5]. The Second Circuit put this case in the second bucket by looking at what was actually contested. IBM has never argued about how much it copied, only about whether it was allowed to, so the dispute "does not involve the nature, extent or scope, of copying", and "IBM's taking of the code in 2001 was a one-time event" [6]. The products IBM continues to iterate and release for sale [3] therefore generate no new accrual date.
The arithmetic that follows is not close. From the 2001 taking to the March 2021 complaint is twenty years [1]. On the court's most generous alternative, knowledge in 2011, the window shut in 2014, seven years before Xinuos filed [2].
The odd part is that Xinuos won the characterisation argument. The district court had treated the case as an ownership dispute; the appeals court said both sides had framed it as a fight over IBM's right to use the code, which reflects a licence dispute, and cited a 2007 ruling that a non-exclusive licence conveys no ownership interest [8]. Then it affirmed anyway, because accrual lands in the same place [8]. A correction with no consequence for the loser.
The contract carried a shorter clock than either statute. Section 22.3 of the Joint Development Agreement gave the parties two years from a breach [10], and IBM terminated Project Monterey in 2001 [11], which put that window's close around 2003 [3] - the year Caldera sued in Utah [12].
Almost everything after that concerned who held the claims rather than what was in the code. SCO Group went bankrupt in 2007 [12] and sold its software business to Xinuos in January 2011, carving out rights and causes of action related to IBM [13]. SCO settled with IBM in August 2021 for $14.25m, a figure The Register reads as reflecting years of failing to produce strong evidence [14]. Xinuos told the bankruptcy court the release could be read to cover its own claims and was overruled [15]. Its own suit, filed on 31 March 2021 [16], lost on summary judgment in January 2024 and reached final judgment on 2 April 2025 [17], with Crowell & Moring for Xinuos and Latham & Watkins for IBM [18].
Across twenty-two years from the first Utah filing to that judgment [4], no court ruled on the thing IBM has spent the whole time asserting: that it had the right to reuse the code [4]. Linux runs in billions of devices [21], and the provenance question under one contribution route is now not answered but unanswerable, on a summary order that formally decides nothing beyond this case [2].
Ranked by verification strength, evidence, and original report placement.
The court found the claim accrues once: because IBM never disputed taking the code, the dispute "does not involve the nature, extent or scope, of copying" but whether IBM had the legal right, and "the contested action, IBM's taking of the code in 2001, was a one-time event".
A Joint Development Agreement governed Project Monterey; each party licensed the other its code, and Section 22.3 gave them two years from any breach to bring a related claim.
Caldera sued IBM in Utah in March 2003, later renamed itself SCO Group, and filed for bankruptcy in 2007.
Xinuos now has one long-shot move left.
The appeals court threw out the last live claim in the long fight over who owns Linux; the dispute began in 1998, and Simon Sharwood reported the ruling for The Register.
Three judges of the US Court of Appeals for the Second Circuit - Guido Calabresi, Steven Menashi and Sarah Merriam - affirmed the Southern District of New York's judgment on 10 August in a summary order, calling Xinuos's remaining arguments "without merit".
Follow any of these and your For You feed starts watching them — no settings page required.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Specific court record, single reporting channel
The core factual spine is unusually checkable: named panel members, a dated 10 August summary order, quoted holdings on accrual and on the licence-versus-ownership framing, and a docket trail from the March 2021 complaint through the January 2024 bench ruling to the 2 April 2025 final judgment. What holds the score down is provenance breadth rather than specificity - a single publisher relaying The Register, no order text or docket link, no party or counsel comment, and interpretive items (settlement-size reading, the sub-0.03% en banc rate) carried second-hand.
Deeply entrenched code, unquantified
Adoption here is the real-world entrenchment of the disputed code, and it is qualitatively strong and undisputed: IBM concedes it put Monterey code into products it continues to iterate and release for sale, has shipped on that basis for about twenty-five years, and still sells mainframes. Linux is said to run in billions of devices. The ceiling is that no figure in the cluster quantifies how much of that footprint traces to the disputed code - no unit counts, revenue lines, or product inventories are supplied.
Framing runs ahead of a non-precedential order
The underlying ruling is narrow: a summary order with no precedential effect that expressly does not decide whether IBM was entitled to the code, only that the question is time-barred. The surrounding presentation is broader - a headline about a 28-year fight over 'who owns Linux' being nearly over, and a stakes section that sizes the prize by analogy to Huawei's $0.50 per-unit Wi-Fi 7 rate and gestures at unrelated open-code monetisation and security items. The gap is one of framing amplitude rather than factual error; the legal claims themselves are stated with care and the non-precedential caveat is disclosed.
Adversarial litigants, court-sourced core
Every interested party here has a directional stake: Xinuos is pursuing royalties on a quarter-century of shipped product and has announced it will seek rehearing, IBM benefits from finality, and both sides are represented by firms named in the piece. The countervailing factor is that the load-bearing claims come from the panel's own order rather than from party advocacy, so incentive pressure sits mostly on the interpretive margins - the reading of the $14.25m settlement, the framing of what remains possible - rather than on the holdings.
Solid on the holding, thin on corroboration
Confidence is high that the reported disposition, dates and quoted holdings are accurate, because they are specific, internally consistent across the article's sections, and drawn from a public order. It is materially lower on everything interpretive: one publisher, itself relaying another outlet, with no party comment, no primary document, and second-hand statistics. The assessment therefore rests firmly on what the court did and lightly on what it is said to mean.
build
Hugging Face's $13B process puts most teams' model pipeline under a single owner2 distinct publishers
security
AI skills now in 28.5% of security job ads, and the SOC job family is being quietly rewritten2 distinct publishers
product
IBM says buyers moved June capex to hardware, and its mainframe software stack paid for it1 distinct publisher
build
Fabricated SQLite CVEs cleared NVD, CISA ADP and Red Hat before anyone ran the code1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 25, 2026