Asahi Linux moves all repositories to GPLv2 or later

By Marcus Bennett

Asahi Linux has begun moving all of its repositories, or software code collections, from the MIT license to the GNU General Public License version 2 or later, the project said in Progress Report 7.3.

The change covers the project that reverse-engineers drivers for Apple Silicon chips, meaning it reconstructs the low-level software needed for Linux to communicate with modern Mac hardware. Asahi Linux says those drivers gave Mac owners an operating-system option they otherwise would not have had.

Against that technical role, the announcement sets a licensing confrontation with a direct AI dimension. The project says some copied code was rewritten with large language model (LLM), or generative AI, assistance to obscure its origin.

The change matters because the license now governs who may reuse the driver work that sustains Linux on Apple Silicon. Asahi Linux also says demand for high-quality training data from frontier AI labs helped drive the appropriation it alleges.

Why did Asahi Linux abandon its MIT strategy?

Asahi Linux says it first used MIT to build a Free Software ecosystem for Apple Silicon and encourage participation from the BSDs, meaning Berkeley Software Distribution operating systems, and other free-software projects.

"When Asahi Linux was first started, it was with the intent that we develop a Free Software ecosystem for the Apple Silicon platform. To facilitate and encourage the participation of our friends at the BSDs and other Free Software operating systems, we endeavoured to licence as much of our code as possible under the permissive MIT licence."

The retrospective makes the reversal explicit. Asahi Linux describes MIT as an ecosystem-building choice intended to widen participation, not as a default applied without strategic purpose.

Under that approach, permissive terms let outside projects reuse more of the work. The project says BSD and other free-software operating systems formed part of the constituency it wanted to attract.

The linked post provides no starting year for the project and names no BSD implementation or other operating system. Its stated rationale therefore describes a licensing principle rather than a documented participation record.

The reason for revisiting that principle appears in the project's account of a longer history of software appropriation.

"Unfortunately, this is no longer viable. The malicious practices of the 90s and 2000s have reared their ugly heads once again, this time driven in large part by both the insatiable appetite of frontier AI labs for high-quality training data, and militant animosity toward the Free Software community."

Asahi Linux attributes the recurrence to two forces: demand from frontier AI labs, or organizations developing advanced AI systems, and what the project calls militant animosity toward the Free Software community.

The project does not name those laboratories, provide dates or quantify their role. Its statement establishes a claimed motive rather than a documented case against an identified AI company.

The source also cites no regulatory inquiry or court finding. That distinction matters because a broad claim about a class of laboratories does not establish responsibility for any specific act of copying.

The immediate licensing action does not depend on such a determination. Asahi Linux can change the terms governing future reuse of its code without waiting for a legal ruling against an unidentified party.

What did the project say was copied?

The most concrete part of the announcement is the project's allegation of multiple license-exploitation attempts aimed at replacing Asahi Linux and monetising its work.

"Some time ago, we were made aware of multiple attempts to exploit our permissive licensing to hijack our work, with a direct view to replacing the project and aggressively monetising Linux on Apple Silicon."

"In some extreme cases, in-development feature code was being lifted straight out of our personal forks and published without attribution or lazily rewritten with LLM assistance to obfuscate its origin."

"The MIT licence explicitly allows this, and has no carveouts to protect against bad faith actors."

The source describes personal forks as developer-specific copies used to stage in-progress changes. That makes the alleged theft more than a dispute over finished code; it targets work still under development.

An unattributed copy removes the author's credit. An LLM-assisted rewrite, according to Asahi Linux, changes the surface form while leaving the underlying work derived from its code.

The project says both methods facilitated a replacement effort and aggressive commercialisation of Linux on Apple Silicon. It does not identify a company, laboratory or recipient connected to any attempt.

The announcement also leaves several verification points unresolved:

• It names no repository, commit, developer, recipient, company, laboratory or date for any alleged attempt.
• It reports no takedown, lawsuit, licensing negotiation or estimate of financial loss.
• It provides no example that independently confirms the project’s account.

Those omissions leave the announcement documenting a pattern according to Asahi Linux, rather than a case-by-case audit. The source nevertheless gives a specific trigger for the license change: code taken from personal forks and published without credit or with its origin obscured.

What does the GPL switch change?

Operationally, the project says it is moving every repository and will license all future code under strong copyleft terms.

"As such, we made the difficult decision to begin the process of transitioning all of our repositories to the GNU General Public License version 2 or later."

"Going forward all Asahi Linux code will be licenced under strong copyleft licences only. Those who do not learn from history are doomed to repeat it."

Asahi Linux calls the new terms strong copyleft licenses. Copyleft carries source-license obligations into distributed derivatives, preventing downstream users from simply detaching the work from the conditions that govern the original project.

That mechanism supplies the project's answer to the alleged hijacking. Asahi Linux expects downstream reuse to preserve the copyleft relationship rather than permit an independent replacement under different terms.

The source does not say that every repository conversion is complete, despite describing the process as already under way. It also sets no deadline and identifies no enforcement target.

The license policy remains more concrete than the motive claims. Its stated scope covers all repositories and all code going forward, while its stated objective focuses on preventing exploitation of Asahi Linux's work.

By choosing strong copyleft across the project, Asahi Linux revises the tradeoff it made at launch. It trades some of the flexibility that supported broad collaboration for stronger protection against independent commercial appropriation.

The source does not report whether BSD or other operating-system projects object to the shift. It presents the decision as Asahi Linux's response to conduct affecting its own code, not as evidence of a wider licensing revolt.

Why does AI appear in the dispute?

The announcement's AI claim requires separation from its copying allegations. Asahi Linux does not say that a named model trained on a repository, and it publishes no model, dataset size, benchmark, price, funding amount or training-run figure.

It instead describes LLM assistance in rewriting code that had already been taken from personal forks. In the project's account, AI helped obscure the origin after copying; it did not independently create the replacement operation.

The source links the conduct to frontier laboratories' appetite for high-quality training data and to hostility toward free software. Those motives differ. One seeks data for AI development, while the other seeks to displace or weaken a Free Software ecosystem.

Because the source identifies no specific laboratory, its broad causal language does not constitute an independently established finding against the AI industry. The absence of a named model also narrows the evidence supporting the industry's role.

Conversely, the announcement documents a concrete policy response regardless. Asahi Linux changed the license across its repositories because it says exploitation occurred, including some copying paired with LLM-assisted obfuscation.

The reference to the 1990s and 2000s supplies a historical analogy, not a timeline for the Asahi Linux incidents. The source names no older case and gives no date for the phrase "some time ago."

Asahi Linux therefore presents its response as a recurrence of an older appropriation pattern. The announcement establishes the new licensing policy and the project's allegations, while leaving its historical comparison unsupported in detail.

Why does the change matter for Apple Silicon Linux?

The stakes begin with the project's technical role. Asahi Linux reverse-engineers the drivers required to run Linux on modern Macs, according to the source, and the project calls its work an engineering marvel.

Because the project reconstructs those drivers, reuse of its code can affect both who operates Asahi Linux and who presents Linux on Apple Silicon to users.

Asahi Linux says the hijacking attempts aimed at replacing the project and aggressively monetising Linux on Apple Silicon. That is the market issue named in the announcement, even though it provides no revenue amount, funding total, customer count or commercial product.

The policy issue is narrower. No government body or industry regulator appears in the source, and the announcement neither creates an AI rule nor adjudicates training-data rights.

Instead, the project changes the conditions attached to its own code. Every repository moves to GNU GPL version 2 or later, and future code uses strong copyleft licenses only.

That decision directly revises the collaboration strategy stated in the original MIT rationale. Asahi Linux says it once favoured permissiveness to attract BSD and other operating-system projects; it now favours reciprocal licensing obligations across all its work.

For free-software users, the practical test is whether the stronger terms prevent a commercial or hostile fork from absorbing the driver work while preserving Asahi Linux's ability to operate and improve it.

For frontier AI labs, the announcement supplies a warning rather than a general rule. Demand for high-quality training data, the project says, has made permissive software repositories targets for appropriation.

Nothing in the source establishes an industry-wide licensing shift. The evidence and policy remain confined to Asahi Linux's code and the project's account of hijacking attempts.

The next checkpoint is practical and legal: whether every repository completes conversion to GNU GPL version 2 or later, and whether prospective replacements honor those terms instead of publishing rewritten code without attribution.

Asahi Linux sets no completion date, names no enforcement target and reports no legal action, leaving the effectiveness of the change untested.

For Mac owners, the outcome matters because the driver work the project wants protected is what makes Linux an option on modern Apple Silicon hardware. The source's forward guarantee is narrow but significant: going forward, Asahi Linux says all of its code will use strong copyleft licenses.