Linus Torvalds admitted at the Maintainers Summit that he used Claude Code to draft a set of kernel folio lookup patches, pushing 8-thread contended reads to roughly 3x the baseline, and the first branch has already landed on the mailing list under review (cf. https://www.solidot.org/story?sid=85608). At the same time, the same news cycle pulled an opposite reaction out of an unlikely quarter: NetBSD, the deliberately quiet BSD derivative, just booked 120,282 USD in September donations, more than double its 50,000 USD funding target.
NetBSD as the unlikely AI-free refuge
NetBSD has banned AI-generated code since 2024: its contribution guidelines list ChatGPT, GitHub Copilot, Microsoft tooling, Meta Code Llama and friends as sources of "tainted" code that require explicit written approval from the core team before submission. For years, this was an unremarkable internal rule.
In October 2026, The Register reported the donation spike (syndicated by Solidot and DiscoverBSD), giving the project a moment of unexpected visibility. Combined with the Linux ecosystem's open embrace of LLM tooling from Linus himself to Debian, Ubuntu, and Red Hat, NetBSD's older rule suddenly looks like a position rather than a footnote. In subscription/donation-driven open-source projects, "we don't take AI code" only becomes a selling point in 2026.
While Linux pulls LLMs deeper into the workflow
The contrast lands harder because Linux made the opposite move in the same news cycle. Linus Torvalds shipped a Claude-Code-assisted page-cache patch series whose cover letter openly credits the AI for the initial code, tests, and pre-review checklist. Debian, Ubuntu, and Red Hat added LLM-coding components to their roadmaps. The implicit message from Linux — that AI-assisted contributions now default to acceptable until proven otherwise — is the inverse of NetBSD's stance.
Both communities can now quote each other. Linux says LLM kernel code delivers "3x faster contended reads". NetBSD replies that LLM code is a source of contamination regardless of measurable wins. The same capability, two opposing narratives — and both are technically defensible.
Why the AI-free stance pays off
NetBSD's rule becomes valuable precisely because AI coding tools have become ambient. When most contributors use Copilot, Cursor, Claude Code, or Codex CLI daily, a high-stakes project like the Linux kernel relies on contributor self-reporting. Reviewers cannot reliably tell which patch was AI-generated, and that ambiguity is exactly the problem NetBSD is trying to remove.
By stating the rule upfront, NetBSD pushes the contamination question back onto the submitter. That makes downstream usage simpler: a consumer can read the project's policy and decide whether the input contract matches their regulatory environment. Finance, telecom, medical, government — all of these have stronger incentives to adopt projects with explicit AI-input policies than to rely on a contributor-reviews-contributor model.
Underneath, NetBSD's codebase culture emphasizes portability, minimalism, low layers — the opposite priority from cloud AI tools' push to "write more, faster." NetBSD's budget is to write less, own every line, and slow down, which fits a buyer base LLM-native projects cannot serve.
Anti-AI camp won't go mainstream, but it will stay a stable coordinate
Linux, Debian, Ubuntu, Red Hat will not pause their LLM integration; that's the natural arc of this tooling cycle. NetBSD, OpenBSD, Gentoo, FreeBSD — projects that hold the line on human-written code — become more useful precisely because they are rare. In hiring packets, critical-infrastructure procurement, and long-tenure maintenance contracts, "we don't take AI code here" is more legible than it has ever been.
USD 120,282 a month is not a lot of money. NetBSD will not approach Linux in corporate footprint. But the number signals something the open-source world has not seen: a meaningful cohort of developers willing to pay for an AI-unfriendly baseline. Linux keeps pushing the AI-assisted coding frontier. NetBSD keeps preserving the human-only counter-sample. That is layer formation, not forking.
The real meaning here isn't how much NetBSD raised. It's that open source has, for the first time, separated into two independent funding currents over a question of AI-assisted contribution. One current flows toward "build faster." The other flows toward "build slower, cleaner." Both can coexist for years. Neither has to eat the other.