# The father of CentOS had AI write a kernel in 11 days: Ginux's 455 stars came from one news story · Open-source project on GitHub

> Source: https://stringers.io/en/github/gh_gmkurtzer__ginux.html (Stringers / 什么值得做, generated 2026-11-08)
> Stringers answers one question every day: what small product can one or two people build in a few months and actually make money from. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these verdicts and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools today / hot / products / directions / direction / data. Setup: https://github.com/komako-workshop/stringers (the user logs in at stringers.io → "配置 agent" to get a personal URL). Site index: https://stringers.io/llms.txt

> "CentOS founder + AI writes a new kernel in 11 days + boots Rocky 10" was reprinted all the way down the line by It's FOSS, Linuxiac, TechSpot, and Slashdot, right when the "can AI write a kernel" debate was running. On Hacker News it never took off.

[GitHub open-source project](https://stringers.io/en/github/index.md) · written 11-6

gmkurtzer/ginux · gmkurtzer

# The father of CentOS had AI write a kernel in 11 days: Ginux's 455 stars came from one news story

**What it is** An experimental operating system kernel written with AI that runs real Linux distributions in a virtual machine. In November it was converted into a sandbox that attaches to Linux and allows or denies system calls according to rules.

**Why it took off** The story "CentOS founder + AI writes a new kernel in 11 days + it boots Rocky 10" was picked up repeatedly by It's FOSS, Linuxiac, TechSpot, and Slashdot, right as the debate over whether AI can write kernels was heating up. It never took off on Hacker News.

**C** **How you can follow along** Don't copy the kernel. Pick something hardcore in a field you genuinely know, something ordinary people wouldn't tackle alone and that can be objectively verified. Give AI a fixed number of days to finish it. At launch, publish the post, the repo, and the method report together, and pitch vertical media. Once it gets traction, package the method into something others can install.

Grade C: most of the stars came from the author's identity and media reposts, which followers can't get. A similar project without a famous name got 222 stars in the same period, and the new direction is still overshadowed by gVisor. The launch playbook is worth learning, but following this project specifically isn't worthwhile. Publicly known / widely discussed

Data (updated daily) · Repo created 2026-10-11 · 474 stars · 7 days +168

GitHub · stars

Data 2026-10-29 → 2026-11-08 (11 days, 11 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

Ginux is a Rust kernel that Gregory Kurtzer, founder of CentOS and Rocky Linux, handed to OpenAI Codex to write. It isn't modified from Linux, yet it can boot Rocky Linux 10 all the way to systemd in a virtual machine. Released in Oct 27, by Nov 6 it had 455 stars and 57 forks (GitHub, 11-06). Almost all of those stars came from Linux media reposting one story after another, and the reasons were "who made it" and "11 days." Few people starred it because they wanted to use it. You can't borrow the author's reputation. What you can learn is how he picked a target and how he launched it, turning a technical experiment into a news story.

### A "11 days" post

2026 Oct 27, Kurtzer posted a single line on X:

> In 11 days, I built a new Linux-compatible operating system kernel that boots Rocky Linux 10 with systemd, all using Human-Directed Agentic Engineering (HDAE).

(11 days, I used "human-directed agentic engineering" to build a Linux-compatible new kernel that boots Rocky Linux 10 with systemd.)

It's FOSS published a report the same afternoon, titled "Rocky Linux Founder Built a 'Not Linux' Kernel in 11 Days Using AI." The article also picked up a joke from the README: the G in Ginux looks like Greg, and the author said that was "to keep my ego in check," with G officially standing for GPT. Nearly all the code was written by GPT-5.6 Sol in a single Codex task running for 11 continuous days, leaving roughly 139k lines of implementation and test code across 1,000 commits. That same day he published a technical report with a DOI on Zenodo explaining the method: humans set the architecture, constraints, milestones, and acceptance criteria. AI wrote the code, booted it, tested it, debugged it, and revised it until it passed every executable check.

The post struck the right tone. He repeatedly said this wasn't meant to replace Linux. In his words, "AI can write complex systems software, but compatibility, security, hardware support, standards, community, and long-term maintenance are the real moat." It's FOSS also stated the shortcomings up front: it only runs in QEMU, has no real-hardware support, no GPU or NVMe support, and no security audit.

### How the stars climbed

| Date | What happened | Stars |
|---|---|---|
| 10-27 | Launched on X and LinkedIn, Zenodo report, It's FOSS coverage | Unknown |
| 10-28 | Linuxiac coverage, reposted on linux.org forums, YouTube explainer videos | Unknown |
| 10-29 |  | 87 |
| 10-30 | Submitted to Hacker News (6 points, 0 comments); It's FOSS posted on Facebook and Instagram | 209 (+122, the single-day peak) |
| 11-02 | Slashdot reposted the It's FOSS article (86 comments), TechSpot followed up | 316 |
| 11-05 | Author published a long LinkedIn post announcing he had "killed it on day 18," and the project changed direction | 429 |
| 11-06 |  | 455 |

(Star counts from GitHub's daily figures.)

Two things stand out. First, it never took off on Hacker News: 6 points and no comments, so these stars weren't dug up by the developer community. Instead, tech outlets copied each other: It's FOSS, Linuxiac, TechSpot, and Slashdot had nearly identical headlines. Second, Kurtzer's other repos have almost no stars, which means the stars followed the story, not his account.

The 86 comments on Slashdot also show who showed up. The highest-scored ones were making crude jokes about his name, and further down people argued about whether AI-written code counts as "from scratch" and whether model weights already contained several kernels, then drifted into copyright and fair use. Very few people discussed the kernel itself. People came for the spectacle and to take sides, which reflects where the "can AI write a kernel" debate stood at the time: in October Linus had just publicly said he used AI to write patches, and both sides were hunting for examples.

### Day 18, he "killed" it

On Nov 5, Kurtzer published a long LinkedIn post titled "Built Ginux in 11 days, killed it on day 18 (well, pivoted)." He said the project was never meant to produce a usable kernel ("that would be silly"). Its purpose was to test the HDAE method: pick something you understand, that's easy to test, and that ordinary people wouldn't do alone. Having proven that, he didn't expect the "huge attention: news, articles, podcasts, videos, and drive-by code reviews" it drew. He used the same method to automatically review nearly 80 PRs and 70 issues.

The repo now contains something different: a "user-space kernel" that attaches to Linux as an ordinary process. Each isolated environment has a contract specifying which system calls are passed through, which are forwarded, and which are denied outright. The README says, "Linux must never break user space; Ginux is meant to break it on purpose." The version that could boot directly is kept on the `bootable-kernel` branch.

The pivot itself made news again, and from 11-03 to 11-05 the repo gained 36 to 49 stars a day. However, the new direction is close to Google's gVisor (about 20k stars, already used in production), and the author himself admits gVisor and User-Mode Linux already do part of this. Whether the new direction can hold people on its own remains to be seen over the next few weeks.

At the same time, he split the method out into its own hdae repo, packaged as a skill for Codex and Claude Code that installs with one curl command. It had 51 stars at the time. When the attention peaked, he captured it with something people could actually install.

### Who's doing something similar

| Project | Launched | Stars (11-06) | Compared with Ginux |
|---|---|---|---|
| google/gvisor | 2018 | About 19,900 | A user-space application kernel that aims for broad Linux interface compatibility and is already used in production. The pivoted Ginux is most similar to it. |
| asterinas / kerla / maestro | 2020–22 | 5.1k / 3.5k / 3.3k | Both are Linux-compatible kernels written in Rust, built by teams or individuals over several years. |
| firecracker / kata-containers | 2017 | 37.9k / 9.1k | Uses hardware virtualization for isolation. |
| bubblewrap / nsjail | 2015–16 | 9.4k / 4.2k | Filters existing system calls. |
| maharmstone/moxnox | 2026-10-22 | 222 | Another AI-assisted operating system (NT-style) that launched at about the same time, by an author with little name recognition. |

The last row is the most telling. moxnox and Ginux came out only five days apart and tell the same story: AI helped someone write an operating system. Its author had no name recognition and got less than half of Ginux's stars. That's roughly what the "famous name" factor is worth: the story itself earned about two hundred stars, and the author's name added over two hundred more (an inference). Most toy OSes that ordinary people vibe-coded online don't get even that many.

### If it were you

**C: learn how it picked its target and how it launched, but don't try to follow this project.** More than half of Ginux's stars came from the "CentOS founder" identity, plus media reposting it again and again. Followers can get neither of those. It's already been covered by a whole round of Linux media, and in the user-space sandbox niche it's still overshadowed by gVisor. Writing your own "AI-written kernel," however well done, would just make you the second person telling the same story.

**Best suited for** : developers with years of real experience in a hardcore field (databases, compilers, browser engines, emulators, protocol stacks) who already have some standing in their community and want to use an open-source project to show what an expert can accomplish with AI. You don't need a name as big as Kurtzer's, but you do need one or two vertical outlets or communities willing to repost it for you.

**Who it's not for** : People new to the field who expect AI to write an OS for them. Kurtzer himself says that stuff AI-assembled by outsiders "on vibes" comes out poor quality, and media won't pick it up. Also not for people who want to build "a better gVisor" to rack up stars. That's years of engineering, not a single news hook.

**How to do it** : Copy the structure, swap the content. Pick something you know well that ordinary people wouldn't tackle alone, with an objective acceptance test outsiders can understand at a glance, like "boots a real distro," "passes an official test suite," or "opens a real website." Set a number of days and let the AI work nonstop, keeping the process on record. On launch day, release the post, the repo, and a method report (with a DOI or a long-form essay) together, so journalists have something to write about. Put numbers in the headline: days, lines of code, commit count, what it runs. State your weak points up front, because serious outlets will only repost what's honest. Once heat builds, immediately package the method into something people can install (a skill pack, templates, scripts) and route the traffic to your next repo.

**How to get users** : Don't count on Hacker News. Ginux only got 6 points there. Focus on vertical media and communities in your niche. Linux has It's FOSS, Linuxiac, and Slashdot, and databases, gaming, and security each have their own equivalents. Email editors directly, with a one-line headline and a screenshot of it running. After that, write a long-form post for every pivot and milestone. Ginux's second wave of stars came from the "killed it on day 18" article.

**When to move: before** : Aim for the window while the debate over "can AI write system software" is still hot. Right now someone is doing something similar every month, and "AI wrote X" stories will keep getting staler. Ideally ship before Q1 of year 2027, and pick something no one has yet claimed AI wrote.

**Signs you read it wrong** : ① If before year-end an unknown author's "AI wrote X in N days" project passes 2,000 stars, the story alone is enough and fame isn't required. That path is easier than C. ② If Ginux, after pivoting, still gains more than 100 stars a week in weeks with no news, the user-space contract direction holds people on its own, and following its technical direction is worth considering. ③ If "method skill pack" repos like hdae outgrow Ginux in stars, the real value is the method, and you should follow the method pack, not the project.

[GitHub repo ↗](https://github.com/gmkurtzer/ginux)

**Research notes: competitor table, acquisition evidence, full research report**

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| gVisor | Open source | 2018 | 19.9k stars, used in production | gVisor aims for broad Linux ABI compatibility. Ginux deliberately exposes only part of it, by domain contract. It's still a research prototype. |
| User-Mode Linux | Big-company features | 2000 era | Built into the Linux kernel | Runs the whole Linux kernel as a process. Ginux implements its own contract layer. |
| Gramine | Open source | 2021 | 775 star | Library OS with a manifest as the boundary, targeting SGX |
| seccomp / bubblewrap / nsjail | Open source | 2015-2016 | bubblewrap 9.4k, nsjail 4.2k stars | Only filters the existing ABI, without virtualizing a full contract |
| Firecracker / Kata Containers | Open source | 2017 | 37.9k / 9.1k star | Hardware virtualization for isolation. Ginux intercepts syscalls. |
| Asterinas / Kerla / Maestro | Open source | 2020-2022 | 5.1k / 3.5k / 3.3k star | A Rust kernel compatible with the Linux ABI, hand-written over many years. The original Ginux hook was AI finishing in 11 days and running enterprise distros. |
| moxnox | Open source | 2026-10-22 | 222 star | Another AI-assisted OS around the same time (NT-like), by an author with no name recognition |

Where users come from

- **Verified** **Founder posted on X / LinkedIn** : x.com/gmkurtzer/status/2114958282481910115 (10-27); LinkedIn post, then a long-form pivot article on 11-05

- **Verified** **Linux tech media repost chain** : It's FOSS 10-27 → Linuxiac 10-28 → TechSpot, Ground News → Slashdot 11-02 (86 comments); 10-30 stars, +122 in a single day

- **Verified** **Secondary spread on social platforms** : It's FOSS Facebook / Instagram posts, linuxpc groups, YouTube videos and Shorts, Medium, Reddit, X @twtayaan

- **Verified** **Zenodo technical report backing** : zenodo.org/records/23682548, README includes DOI

- Inferred **Hacker News** : story 50302703 has only 6 points and 0 comments, never reached the front page, not a source

- **Verified** **Charts** : indexed by trendshift; repo less than 60 days old, not yet in GitHub trending

## gmkurtzer/ginux research report (2026-11-06)

### One line

Ginux is a Rust kernel that Gregory Kurtzer (founder of CentOS / Rocky Linux, CIQ CEO) wrote in a single long OpenAI Codex (GPT-5.6 Sol) task over 11 days. It is not a Linux fork, yet in QEMU it brings Rocky Linux 10 up to the systemd multi-user.target. In November 4–5 it pivoted: it now runs as a "user-space kernel," a normal process on top of Linux, deciding per domain contract whether each syscall is emulated, proxied, or denied. The version that booted directly lives on in the `bootable-kernel` branch.

### Conclusion: why it broke out

The stars didn't come from the technology itself but from a **news story** : "CentOS/Rocky's father + new kernel written by AI in 11 days + it runs Rocky 10." A famous name, the hot debate over AI writing system software, and one catchy number came together. Linux tech media kept reposting it (It's FOSS → Linuxiac → TechSpot → Slashdot → YouTube/Facebook/Reddit/Medium), and the traffic flowed back to GitHub. It didn't catch fire on HN (only 6 points, 0 comments). Its GitHub stars are a byproduct of the news, not something developers went looking for and adopted. Tags: resource-driven (founder's reputation) + timing or platform event (the AI-writes-kernels debate was hot; Linus publicly used AI for patches in October).

### Timeline and growth data

| Date | Event | stars (our GitHub repo_day) |
|---|---|---|
| 10-11 | repo created (11 days of private development) | — |
| 10-26/27 | Kurtzer posted on X (x.com/gmkurtzer/status/2114958282481910115,10-27 05:52 UTC) and LinkedIn, and published a technical report on Zenodo (zenodo.org/records/23682548) | — |
| 10-27 | It's FOSS coverage: itsfoss.com/news/ginux/ | — |
| 10-28 | Linuxiac coverage, reposted on linux.org forums; YouTube explainer video (ApyQ0T5uXNg) | — |
| 10-29 |  | 87 |
| 10-30 | Submitted to HN by cycomanic (6 points, 0 comments, never reached the front page, from the hackernews library); indexed by trendshift; It's FOSS posts on Facebook/Instagram | 209 (+122, single-day high) |
| 10-31 |  | 282 |
| 11-02 | Slashdot reposted the It's FOSS piece (86 comments); TechSpot and Ground News followed up | 316 |
| 11-04 | Split out the hdae repo (created 10-29, 51 stars), packaging the HDAE method as Codex / Claude Code skills | 401 |
| 11-05 | LinkedIn long-form "In 11 days I created Ginux, and on the 18th day, I killed it (or rather pivoted it)," pivoting to a user-space kernel | 429 |
| 11-06 |  | 455 (live from gh API 464, forks 59) |

Over the last 7 days +246 (data card). After the curve peaked at 10-30, it still added +25~50 a day, consistent with second-wave coverage from Slashdot and TechSpot and with the pivot news.

### Competitors / similar

It has rivals in two lanes at once: "AI-written operating systems" (same hook) and "user-space kernels / sandboxes" (same thing Ginux now does).

| Name | Type | Launched | Scale (GitHub stars, 2026-11-06) | How it differs from Ginux |
|---|---|---|---|---|
| google/gvisor | Open source, user-space application kernel | 2018 | 19,890 | The pivoted Ginux is closest to it. gVisor aims for Linux ABI compatibility; Ginux **deliberately** exposes only part of the ABI, by domain contract. gVisor already runs in production; Ginux is still a research prototype. |
| User-Mode Linux | Built-in kernel feature | since 2000 | — | Runs the whole Linux kernel as a process. Ginux implements its own contract layer. |
| gramineproject/gramine | Open source, library OS (SGX) | 2021 | 775 | Uses a manifest plus a library OS as the boundary |
| seccomp / bubblewrap / nsjail | Kernel feature / open source | 2015–16 | bubblewrap 9.4k, nsjail 4.2k | Only filters the existing ABI, without virtualizing a full contract |
| firecracker, kata-containers | Open source, microVM | 2017 | 37.9k, 9.1k | Isolates with hardware virtualization; Ginux intercepts syscalls |
| asterinas, kerla, maestro | Open source, Rust kernels compatible with the Linux ABI | 2020–22 | 5.1k, 3.5k, 3.3k | All hand-written over years by teams or individuals. The original Ginux hook was that AI finished in 11 days. |
| maharmstone/moxnox | Open source, NT-like POSIX OS | 2026-10-22 | 222 | Another AI-assisted OS that appeared around the same time (people compared it to Ginux under Kurtzer's posts on X). The author has no name recognition, so it gets half the stars. |
| viralcode/vib-OS and other "vibe coded OS" projects | Open source / blog | 2025–26 | Not verified | Toy OSes that ordinary people vibe-coded. Ginux is about "expert plus AI" (HDAE), and it runs real enterprise distros. |

### Where users / stars came from (growth tactics)

| Channel | Evidence | Confirmed? |
|---|---|---|
| Founder posted on X / LinkedIn himself | X post 2026-10-27; LinkedIn post activity-7520723818412290048; itsfoss says "Kurtzer announced it on X" | Yes |
| Linux tech media reprint chain | It's FOSS (10-27), Linuxiac (10-28), TechSpot, Ground News, Slashdot (11-02,86 comments) | Yes |
| Social platform re-sharing | It's FOSS Facebook / Instagram posts, the Facebook linuxpc group, LinkedIn reposts (Eddie M.), X @twtayaan, YouTube videos and Shorts, Medium, Reddit r/DIY_Geeks | Yes |
| Academic-style credibility | A Zenodo technical report (DOI), and the README carries a DOI badge, which lends credibility to the "AI writes a kernel" claim | Yes |
| Hacker News | Only 6 points and 0 comments, never hit the front page (hackernews library) | Confirmed **not** the main source |
| Charts | Listed on trendshift; the repo was less than 60 days old, so it never made GitHub trending (data card trending_days_any=0) | Partial |
| Contributors / AI agents opening PRs | Accounts like LevitateOS batch-opened PRs from codex/* branches; the author says HDAE auto-reviewed about 80 PRs and 70 issues | Yes (it props up activity, but it is not the main driver of stars) |

### Why it took off (causes)

1. **Who the author is** : founder of CentOS / Rocky Linux and CEO of CIQ, a figure Linux media naturally covers. The author's other repos sit at roughly 0 stars (gh API), which shows the stars follow this project, not the author's own following.

2. **The one-line hook** : "11 days, AI-written, 139,000 lines, 1,000+ commits, boots Rocky 10 to systemd". The numbers are specific and clickbait-ready. It's FOSS, TechSpot, and Slashdot headlines are nearly identical.

3. **It rode the debate over AI writing systems software** : October Linus publicly used AI for kernel patches (ZDNet 10-13), and "can AI write a kernel" was hot. Ginux is a working example, so both supporters and skeptics clicked through.

4. **Restrained, credible framing** : the README and posts repeatedly say "not trying to replace Linux" and "the real moat is compatibility and community", and a Zenodo report backs it up. That's why serious outlets reprinted it instead of treating it as hype.

5. **The pivot was itself news** : on day 18 it "killed" the original and rebuilt as a userspace kernel. A long LinkedIn post kept the heat going for several days (11-03 to 11-05 gained +36 to +49 per day).

### Differentiation

- **Original version** : a standalone Rust kernel that boots directly from UEFI and treats Linux as a "personality" to run real enterprise distros. The differentiation was in **who built it and how** (a senior expert + a single long-running Codex task + executable acceptance gates), not in features. It only ran in QEMU, with no real-hardware, GPU, or NVMe support.

- **Current version** : a userspace kernel where each domain has a versioned "contract", deliberately and selectively breaking the full Linux ABI guarantee (README: "Linux must not break userspace; Ginux is designed to break … deliberately"). Conceptually it is close to gVisor; the difference is that the contracts are reviewable and minimized per workload.

- **Was the pivot the reason it grew?** No. The stars came from the news around the first version from 10-27 to 11-02, and the technical points of the pivot did not exist yet when the stars arrived. The story that actually worked was "celebrity + AI methodology".

### Visibility and copycats

- Visibility: widely covered (It's FOSS, Linuxiac, TechSpot, Slashdot, YouTube, Reddit, Medium, Ground News), a big story in the Linux world. HN never picked it up, so mainstream developer circles have not fully spread it. No revenue (an open-source research project).

- Copycats: none seen copying it directly. Around the same time, moxnox (built 10-22, 222 stars) appeared, but it is not a copy. The author also split the method out into the hdae repo (51 stars), which can be read as a continuation of "productizing the methodology".

### What others can borrow

- **The method is worth more than the product** : pick a goal crazy enough to be interesting and objectively verifiable ("boot Rocky 10 to systemd") to demonstrate an AI development method. The goal itself is the shareable content.

- At launch, X / LinkedIn posts, the GitHub repo, and the Zenodo DOI report went out together, so media had material to write from and it looked credible.

- Headlines need concrete numbers (days, lines, commit counts) and a loud identity.

- Once the heat arrived, package the method into something installable (hdae: Agent Skills for Codex / Claude Code, installed with one curl line) and route the traffic to the next product.

- Using AI to auto-process the flood of PRs and issues is itself a story worth telling.

### Unknowns

- The original X post's views and reposts were not collected (no ginux-related content in the x-radar local corpus).

- Star history before 10-29 is unknown (our library starts at 10-28), and how much stars rose from 10-27 to 10-28 launch day is unverified.

- Whether the community sticks around after the pivot, and whether stars stall, depends on the next few weeks.

- trendshift and the YouTube view counts were not verified.

### Sources

- GitHub: github.com/gmkurtzer/ginux (README, contributors, commits), github.com/gmkurtzer/hdae; gh API 2026-11-06

- Our libraries: github repo_day (data card), hackernews library (story 50302703)

- [x.com/gmkurtzer/status/2114958282481910115](https://x.com/gmkurtzer/status/2114958282481910115)

- [itsfoss.com/news/ginux/](https://itsfoss.com/news/ginux/)

- [linuxiac.com/centos-founder-builds-linux-compatible-rust-ker…](https://linuxiac.com/centos-founder-builds-linux-compatible-rust-kernel-with-ai-in-just-11-days/)

- [www.techspot.com/news/114422-rocky-linux-creator-built-new-n…](https://www.techspot.com/news/114422-rocky-linux-creator-built-new-not-linux-kernel.html)

- [tech.slashdot.org/story/26/11/02/0317207/rocky-linux-creator…](https://tech.slashdot.org/story/26/11/02/0317207/rocky-linux-creator-built-a-new-not-linux-kernel-in-11-days-using-ai)

- [www.linkedin.com/pulse/11-days-i-created-ginux-18th-day-kill…](https://www.linkedin.com/pulse/11-days-i-created-ginux-18th-day-killed-rather-pivoted-kurtzer-ldy5c)

- [zenodo.org/records/23682548](https://zenodo.org/records/23682548)

- [news.ycombinator.com/item?id=50302703](https://news.ycombinator.com/item?id=50302703)

- [trendshift.io/repositories/323188](https://trendshift.io/repositories/323188)

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.