Funtoo announced its own death and then took it back

The headline that still ranks for this question — Funtoo Linux is being discontinued, July 2024 — is out of date, and so is the correction everyone published three weeks later. Funtoo Linux · Ended was discontinued by Daniel Robbins on 26 July 2024, revived on 13 August 2024 as a personal project he called “hobby mode”, then ended a second time without a news cycle: the project’s own front page has said it is over since early September 2025. The tree stopped moving before that. The last push to any repository in the funtoo GitHub organisation — where ego sync pulls from by default — landed on 29 January 2025.

So the honest answer to “is Funtoo dead?” is: yes, twice, and the second time is the one that matters to your machine. The claims about the tree, the hosts and the artifacts are each checkable with a command printed next to them; the claims about what the project said are sourced to the post or page that said it, listed at the end. The last section turns the case into a general procedure, because Funtoo’s is the second of three shapes a distribution ending comes in, and telling them apart from the outside is a cheap skill worth having.

Two announcements, nineteen days apart

2024·07·26On 26 July 2024, Robbins posted a thread in the Funtoo forums’ News and Announcements section titled “All Good Things Must Come to an End…”. He had decided to end the project; Funtoo had stopped being the community of contributors he started it to be; there was no successor BDFL and he was not looking for one; the project would wind down through August, with hosted containers staying online until the end of that month so people could move their services.

That is an unusually candid shutdown notice: it names a cause — the volunteer community, not the technology — and declines the two moves that normally follow, the handover and the search for a successor. LWN covered it four days later and the aggregators followed.

2024·08·13Nineteen days later, on 13 August 2024, he posted again in the same subforum, under the title “Funtoo Continues in ‘Hobby Mode’”. The phrase was borrowed, and credited in the post itself, from Cameron Kaiser, who used it for TenFourFox, the PowerPC Firefox fork he stopped releasing officially in 2021.

What “hobby mode” actually committed anyone to

Read the August post as a contract and it is remarkably short. Funtoo would continue as a personal project, maintained for its author because he ran it himself anyway; users could still run ego sync and get periodic updates; the tree had been updated that day and would keep being updated “about once a week or so”. Everything else was withdrawn in the same post: bug tracker and community repositories stayed offline, forums and wiki went read-only, project logins would go away, and discussion moved to Reddit.

The register is worth admiring. It promises exactly one thing — a tree that keeps syncing — and declines to promise support, a bug process, or community contributions; serious contributors are told to write to him privately instead. The only cadence in the post is hedged twice over, “about once a week or so”, which is a description of a habit rather than a commitment. Compare the usual formulation, in which a project “remains available to the community” while quietly meaning the same thing.

But a contract with one clause is only as good as that clause, and this clause was a weekly tree update by one person. That is the cost structure that ends projects, and the same one that ended Sabayon: not a decision, a recurring bill that falls due whether or not anyone has time to pay it.

Hobby mode is not inherently a euphemism, because the person Robbins borrowed it from meant it. TenFourFox shipped its last official build on 3 October 2021 and went into hobby mode from there, and its author was still publishing security patch sets in February 2025 — three years and four months of an explicitly unpromised project delivering anyway. Funtoo’s ran five and a half months: announced 13 August 2024, and the tree stopped on 29 January 2025.

Does ego sync still work? Yes, and that is the problem

This is the question people with a Funtoo box actually type, and the answer is annoying: the command still exits successfully and brings you nothing.

The mechanism is the whole answer. ego clones and updates a git repository called meta-repo, which contains no packages itself — it is a set of pinned pointers to the package trees Funtoo calls kits. Its base URL is set in /etc/ego.conf, and the default it falls back to is GitHub:

So the sync path is intact. github.com/funtoo/meta-repo resolves, responds and hands over a HEAD. What it hands over is the point:

# the sync source is reachable, and answers
git ls-remote https://github.com/funtoo/meta-repo HEAD
d379fa0d6fdb8fccd342ae3d7e3e01c88611656d	HEAD

# when did the branch a current install follows last move?
gh api 'repos/funtoo/meta-repo/commits?sha=next&per_page=1' \
  --jq '.[0].commit.committer.date'
2025-01-29T04:08:43Z

# and the package tree it pins
gh api repos/funtoo/core-kit/commits/2facdaf3 --jq '.commit.committer.date'
2025-01-27T23:55:03Z

2025·01·29The newest push anywhere in the 72-repository funtoo GitHub organisation is that one, on 29 January 2025. Thirty of the 72 were pushed at some point that January and eighteen in its last five days — which is what a kit regeneration run looks like, and the commit messages confirm it: seventeen of those eighteen end on Autogenerated tree updates., and the eighteenth is meta-repo itself, ending on kit updates. That is the pipeline writing, not a person. It ran the job and never ran it again.

The primary home of those repositories is gone entirely. Funtoo hosted its own Bitbucket at code.funtoo.org, and the install guide still tells readers they are welcome to contribute there. That hostname no longer has an address: on 2026-08-04 it answers NOERROR with an empty answer section, its A and AAAA records deleted while a self-referential MX record is left behind. bugs.funtoo.org is in the same state. The GitHub mirrors outlived the originals, which is the reverse of how anyone plans it.

None of this surfaces as an error. ego sync against a frozen mirror is indistinguishable from ego sync in a week when nothing changed — which is why “does it still work?” is the wrong question about a hobby-mode distribution. The right question is when the tree last moved.

What is actually installed on a Funtoo box in 2026

A frozen tree is an abstraction; this is what it means concretely. At the exact commit meta-repo’s next branch still pins, the only OpenSSL ebuild in core-kit is openssl-1.1.1q, and that directory’s last update predates the freeze by more than two years.

“End of life” undersells it, and the undersell is worth correcting, because the usual reassurance — it stopped getting fixes in 2023, so you are two years behind — is not what the tree says. The pin is not the last 1.1.1; it is the fifth-from-last. Five public releases came out after 1.1.1q and before the series was retired, and the OpenSSL project’s own vulnerability index lists eleven CVEs that affect 1.1.1 and were fixed in one of them — four in 1.1.1t, four in 1.1.1u, two in 1.1.1v, one in 1.1.1w. One is rated High: CVE-2023-0286, an X.400 address type confusion in X.509 GeneralName, fixed in 1.1.1t on 7 February 2023. That is eighteen months before hobby mode was announced. A Funtoo box was already missing published fixes for a shipping TLS stack while the project was still calling next its current release, and the freeze only made the gap permanent.

None of that can be closed through the package manager, because the tree that would carry it forward has stopped. What it means in practice — a desktop behind NAT is a very different risk from anything with a listening port — is worked through in the first thirty days after your distro dies.

Reinstalling is not a way out either. The install guide’s stage-3 chapter still sends readers to build.funtoo.org, which still resolves, is still fronted by a CDN, and is completely empty. Both the URL the guide prints today and the one the Internet Archive recorded working in February 2024 answer the same way:

# the URL install guide chapter 8 prints today, and its signature
curl -sI https://build.funtoo.org/next/x86-64bit/generic_64/stage3-latest.tar.xz
curl -sI https://build.funtoo.org/next/x86-64bit/generic_64/stage3-latest.tar.xz.gpg

# the older path the Internet Archive recorded as HTTP 200 in Feb 2024
curl -sI https://build.funtoo.org/1.4-release-std/x86-64bit/generic_64/stage3-latest.tar.xz

# all three, identically
HTTP/2 404
content-type: application/xml
content-length: 137
server: CDN77-Turbo

# and the body, on every path tested on 2026-08-04, including /
curl -s https://build.funtoo.org/
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Error>
    <Code>NoSuchKey</Code>
    <Message>Key not found</Message>
</Error>

The Internet Archive’s last capture of that host, on 19 September 2025, still shows a plain directory index containing distfiles/, livecd/ and next/. Somewhere between that date and this one, the object store behind the CDN was emptied while the CDN kept being paid for. That ordering is worth internalising: the artifacts usually go before the infrastructure does, because artifacts cost storage every month and infrastructure costs a renewal nobody has cancelled.

September 2025: the second ending, which nobody reported

2025·09·05Between 2 and 6 September 2025 — a four-day window, closed by two archive captures — www.funtoo.org stopped redirecting its root to the wiki’s /Welcome page and served a statement instead. It is signed by Robbins and stamped 05 Sep 2025, which sits inside that window and dates the change to the day. Its opening line: “The existing Funtoo Linux project has ended and the community project has been officially disbanded.” Beneath the statement the page carries an archive notice telling readers the codebase is frozen and unmaintained and to choose an actively maintained distribution for anything production or security-sensitive. The wiki survives under a shorter sitewide banner of its own, which says the project has ended, calls the wiki a historical archive, and points at the statement — and says nothing about what to run instead.

I can find no news coverage of that second announcement at all: no LWN item, no aggregator pickup, nothing from the sites that covered July and August 2024 within days. That is the mechanical reason the 2024 discontinuation headline still ranks — the reversal got a news cycle; the re-reversal, the one that is true, got a page edit.

It generalises well past Funtoo. A project’s second ending is almost never reported, because the first one used up the story. Search results record what was interesting, not what is true, and for dying software those two diverge within about a year.

June 2026: the parts came back without the distribution

2026·06·07Kernel Seeds was relaunched on 7 June 2026 — the earliest item in its own news index — and on 12 June the funtoo.org statement page was rewritten to point at it. The rewrite describes work that will “fill the space Funtoo leaves behind” as a marked evolution rather than a continuation, and names the vehicle: funtoo-ng components, released as standalone projects rather than as a distribution.

That domain has its own history, which the site tells: kernel-seeds.org was the project of a Gentoo community member known as Pappy, built to demystify the kernel .config file, and he handed the domain to Robbins when he could no longer maintain it. What has shipped:

The first row is the one that changes the shape of the story. Keychain — the oldest thing Robbins maintains, older than Gentoo’s 1.0 — did not wait for the relaunch. It went back into release on 30 April 2025, three months after the package tree stopped and fourteen months before Kernel Seeds existed, and shipped nine times through November 2025. The tools were already moving while the distribution was not. June 2026 gave them a home and a name; it did not restart them.

Note what that list is not. It is not a distribution and is not trying to become one; the funtoo-ng page says the goal is explicitly not to recreate Funtoo as a single monolithic project. unroot is the clearest evidence for the model: fchroot was an internal Funtoo tool for building ARM and RISC-V userspaces on a PC, now re-released as something anyone can use whether or not they have heard of Funtoo.

A distribution is a bundle: a package tree, a toolchain, policies, an installer, an archive of artifacts, and half a dozen tools written because the bundle needed them. When the bundle stops being maintainable the tools are usually still good, and they usually die with it because nobody separates them out. Decomposition is the ending in which the reusable parts survive their container. The distribution is no less dead — a Funtoo box gets nothing from unroot — but the engineering is not lost, which is more than most shutdowns manage. The cost is worth naming: one person is now maintaining four projects instead of one.

Why this belongs on this domain

2020·11·20Because Sabayon ran through here. On 20 November 2020 Robbins posted that Funtoo and Sabayon were joining forces, and that Sabayon’s work would from then on be built on Funtoo. Sabayon published its counterpart announcements the same day, bundling the merger with a rename to MocaccinoOS and the replacement of Entropy by Luet — the sequence taken apart in what happened to Sabayon Linux.

That announcement was the source of the longest-running open cell in the Register, and it has since been closed from the build files rather than from the press: MocaccinoOS · Shipping assembles its desktop from a Gentoo autobuild stage 3 and a pinned commit of gentoo/gentoo, with no Funtoo anywhere in the chain, and the collaboration was formally wound up on 6 December 2021 — twelve and a half months after it was announced.

The dates here reinforce that from the other side, and are worth keeping straight, because the two projects’ endings are often collapsed into one story. MocaccinoOS took the last commit to its Funtoo tree on 22 November 2021 and declared the collaboration over two weeks later; Funtoo itself carried on for two and a half years after that, was discontinued in July 2024, revived, and only stopped moving in January 2025. Nothing that MocaccinoOS ships was ever downstream of the freeze this piece documents. The merger and the discontinuation are separate events three years and eight months apart, and reading them as cause and effect gets the history backwards.

Three endings, and how to tell which one you are looking at

This is the argument the rest of the piece was evidence for. Distributions rarely die the way people picture it — a farewell post, a mirror going dark, a clean date. What happens is that a project stops promising, months or years before anything visible changes. There are three shapes.

You can distinguish them from the outside in about five minutes, without asking anyone. Five checks, fastest first:

1. Date the tree, not the website. Find the git repository the package manager actually syncs from — it is in the config file, and there is usually a documented default — and get its last commit date. Websites are edited by hand; trees are pushed by pipelines, and a pipeline that has stopped is unambiguous.
2. Try to download the installer. Not the download page: the artifact URL, with curl -I. An empty bucket behind a live CDN is one of the most reliable signals there is, because it means somebody stopped paying for storage while a subscription renewed itself.
3. Resolve the developer-facing hostnames — bugs., code., git., build., mirror. Projects retire those long before the apex, because they cost money and serve few people. An apex that answers while the developer subdomains have no address record is a project whose last paid infrastructure is a domain renewal. Read the response code, not just the absence of an answer: code.funtoo.org and bugs.funtoo.org return NOERROR with nothing in the answer section, because both names still carry an MX record pointing at themselves while their A and AAAA records are gone. A name that has been deleted outright returns NXDOMAIN — funtoo.net does. The difference tells you whether someone tore the host down or someone edited one record and left.
4. Check whether the forum still accepts writes. Read-only is a decision, and it is nearly always made at the same meeting as the ending.
5. Read the front page for a date stamp, then check it against the archive. An “Updated:” line is a project telling you when it last thought about you. Compare it with the tree date from check 1: the gap is how long the project was over before it said so. For Funtoo, seven months.

Every one of those is cheap, public and dated, and none of them requires a project to have been honest with you.

If you have a Funtoo box right now

Three doors. Nothing here was run on a machine to produce it; it is what the package manager’s own configuration, the frozen tree and the project’s statements support, and where a step is inference rather than record I have said so.

• Move to Gentoo. The rule for a dead derivative is to move to what it was derived from, and Funtoo is an unusually clean case: it forked Gentoo’s tree rather than building a different system, so profiles, toolchain, ebuild format and emerge are the same objects. The kit-to-single-tree transition is real work and is not documented as a procedure anywhere I could find; the staged conversion pattern and its rollbacks are in Your distro just died: the first thirty days.
• Reinstall onto something current. For most machines this is faster and ends in a better state. If you chose Funtoo because you wanted Gentoo with fewer decisions, the 2026 answer is different from the 2019 one — Gentoo’s own binary host removes most of the compiling, signature-checked by default. The wider field is compared in The five candidates for “Sabayon in 2026”.
• Keep it, off the network. With no listening ports, or as a VM, it is fine and will keep booting. As an internet-facing desktop it is running an end-of-life TLS stack with no route to a fixed one.

What I could not establish

• Why the tree stopped on 29 January 2025. No post, thread or commit message explains it, and the forum where it would have been discussed was already read-only.
• Whether updates continued privately after that date on non-public infrastructure. The GitHub mirrors are the only public evidence, and they stop.
• The exact date the build.funtoo.org objects were deleted. The window is 19 September 2025 to 4 August 2026.
• The fate of the containers Robbins offered to keep running for individual users. That arrangement was private by design and left no public record.
• Whether anything survives of the one community continuation that did exist. It is easy to trace and it has already failed twice over. funtoo.net was registered through Namecheap on 29 April 2025 — three months after the tree stopped — and served an unofficial Funtoo wiki offering rebuilt stage-3 images, crediting a GitHub account called BlakaDivin. By 15 November 2025 the same URL served nothing but a meta-refresh back to www.funtoo.org. Today the BlakaDivin account returns 404 and funtoo.net is NXDOMAIN — not expired, but suspended: the registry lists it clientHold with the registration paid through 29 April 2028, which is a registrar action rather than a lapse. Why it was put on hold, and whether the images or the repositories were preserved anywhere, I could not determine. No fork of funtoo/meta-repo has been pushed since 25 July 2024. If any of it survives: editor@lxnaydesign.net.
• Funtoo’s first release date. It has none in the ordinary sense — it was a rolling tree, and the project’s own history page dates the work from December 2007 rather than to a release.

Read next

• Your distro just died: the first thirty days — what to freeze, what actually got more dangerous, and the staged conversion to a living base.
• What happened to Sabayon Linux — the rename ending, dated step by step, including the November 2020 merger with Funtoo from the other side.
• Gentoo ships 89 GB of binaries now — why “Gentoo without compiling” is a far weaker reason to run a derivative in 2026 than it was in 2019.
• MocaccinoOS: the successor, or the estate? — including the build files that settle whether the Funtoo base announced in November 2020 ever shipped.

Standing — 2026-08-04

Still true

ego sync runs and succeeds against the GitHub mirrors, which resolve and serve. The Funtoo wiki is online and readable. The forums are online and readable. Keychain is actively released, at 3.0.2 as of 31 July 2026, and unroot 1.0.0 shipped today.

Ended / rotted

The package tree: no push to any repository in the funtoo GitHub organisation since 29 January 2025. code.funtoo.org and bugs.funtoo.org have lost their address records — the names still exist, nothing answers on them. build.funtoo.org answers, but every stage-3 path, including the two the install guide prints, returns an empty-bucket error. Forums and wiki are read-only. The project is ended by its own statement. The one community continuation, funtoo.net, redirected to the official archive by November 2025 and is now on registrar hold.

Actively wrong

Every result that says Funtoo was discontinued in July 2024 and reversed — true in August 2024, misleading now. The Funtoo install guide, which still names next as “the current release”, invites contributions via a hostname that does not resolve, and sends readers to an empty download host; the sitewide archive banner is the only correction on it. Any 2024-era advice that hobby mode means your machine keeps getting updates.

Not established

Why the tree stopped on that date; whether private updates continued; when the stage-3 objects were deleted; why funtoo.net was suspended and whether anything it hosted survives; Funtoo’s first release date. Listed in full above.

Sources & method

This piece was assembled from the project’s own announcements and documentation read live rather than through an archive, from git, DNS and whois metadata, and from HTTP checks run against the hosts named in it. The Internet Archive was used for dating only — when the funtoo.org front page changed, when build.funtoo.org last served a directory listing, and what funtoo.net served on three dates in 2025 — and no text from it is reproduced here. Package-tree claims are taken from the repositories at the exact commits meta-repo pins, so any reader can reproduce them with the commands printed above. No Funtoo, Gentoo or MocaccinoOS machine was installed or run in the writing of this, and no claim above depends on one having been. All URLs accessed 2026-08-04.

1. Daniel Robbins, “All Good Things Must Come to an End…”, forums.funtoo.org topic 5182, 2024-07-26.
2. Daniel Robbins, “Funtoo Continues in ‘Hobby Mode’”, forums.funtoo.org topic 5185, 2024-08-13 — source for every clause of the hobby-mode contract and for the credit to Cameron Kaiser.
3. “Funtoo Linux is being discontinued”, LWN.net, 2024-07-30.
4. www.funtoo.org — the statement page, stamped “Updated: 12 Jun 2026”, and the sitewide wiki archive notice beneath it.
5. Internet Archive CDX index for www.funtoo.org/, 2024–2026, used only to date the change from a redirect to the statement page (last 301 captured 2025-09-02 09:18:34 UTC; first 200 at 2025-09-06 01:47:36 UTC, stamped 05 Sep 2025) and the 2026 rewrite (previous body digests last seen 2026-06-06; new body first captured 2026-06-17, stamped 12 Jun 2026). Rows for http://www.funtoo.org/ and http://funtoo.org/ are the HTTP-to-HTTPS hop and are excluded; they still return 301 today and say nothing about the page.
6. Funtoo install guide, Introduction and Chapter 8, Download and Extract Stage3 — for “the current release of Funtoo Linux is next”, the invitation to contribute via code.funtoo.org, the fchroot description, and the build.funtoo.org download target.
7. Funtoo Linux History — the project’s own timeline, dating the work to December 2007 and Metro’s first release to 2008-10-18.
8. funtoo/ego, files python/ego/config.py and doc/ego.conf.5.rst — the default sync_base_url and its documentation.
9. GitHub API: organisation funtoo, 72 repositories, newest pushed_at 2025-01-29T04:09:14Z, of which 30 were pushed during January 2025 and 18 on or after 2025-01-25; meta-repo branch next HEAD 2025-01-29T04:08:43Z; core-kit at the pinned SHA 2facdaf3, 2025-01-27T23:55:03Z; fork list of meta-repo, newest push 2024-07-25.
10. meta-repo metadata/kit-sha1.json and metadata/kit-info.json, branch next — the kit pins the tree resolves to.
11. core-kit at 2facdaf3, paths dev-libs/openssl and sys-libs/glibc, plus the commit history of the OpenSSL path on branch next (last touched 2022-10-21).
12. OpenSSL: the project’s “OpenSSL 1.1.1 End Of Life” notice of 2023-09-11; the old 1.1.1 releases index for the release dates of 1.1.1q (2022-07-05) and 1.1.1w (2023-09-12); and the 1.1.1 vulnerability index, counted on 2026-08-04, for the eleven CVEs recorded as affecting 1.1.1 and fixed in 1.1.1t, u, v or w — four, four, two and one respectively — including CVE-2023-0286 (High, 2023-02-07). Two further entries are marked fixed in 1.1.1x, which was never a public release, and are excluded from the count.
13. HTTP and DNS checks run 2026-08-04: www.funtoo.org 200, forums.funtoo.org 200 read-only, build.funtoo.org 404 with a NoSuchKey body on / and on every stage-3 path tested, including /next/x86-64bit/generic_64/stage3-latest.tar.xz and its .gpg. code.funtoo.org and bugs.funtoo.org: NOERROR with an empty answer section for A, AAAA and CNAME, and an MX record pointing at themselves, on the resolvers at 8.8.8.8, 1.1.1.1 and 9.9.9.9 and at the name.com authoritative servers; a nonexistent control name under funtoo.org returns NXDOMAIN, so the distinction is the zone’s, not the resolver’s. funtoo.net: NXDOMAIN. Internet Archive capture of build.funtoo.org/ at 2025-09-19, its last, showing a directory index containing distfiles/, livecd/ and next/.
14. funtoo.net: Verisign and Namecheap whois read 2026-08-04 — created 2025-04-29, updated 2026-03-19, expiry 2028-04-29, status clientHold. Internet Archive captures of funtoo.net/ at 2025-05-02 and 2025-07-17 (a community Funtoo wiki, sole outbound link github.com/BlakaDivin) and at 2025-11-15 (a bare meta-refresh to www.funtoo.org). Nothing from those captures is reproduced here. github.com/BlakaDivin returned 404 on 2026-08-04.
15. kernel-seeds.org news index, whose earliest items are “Relaunching Kernel Seeds” and “Keychain 3.x preview”, both 2026-06-07; the Funtoo-ng Components page for the standalone-component model, the “first public component” status of unroot and its descent from fchroot; the unroot page; and the Heritage page for the domain’s origin with Pappy.
16. GitHub API, danielrobbins/keychain releases — publication timestamps and release notes for 2.9.0 (2025-04-30) through 3.0.2 (2026-07-31), nine of them in the 2.9 shell series and six in the 3.0 Python series. The twenty-fifth-anniversary framing is the project’s own, in the 3.0.0 news item; it places Keychain’s first release in 2001, before Gentoo 1.0 of 31 March 2002.
17. Daniel Robbins, “Funtoo Linux and Sabayon joining forces”, forums.funtoo.org topic 4882, 2020-11-20. The disposal of that collaboration, and the build-file evidence that MocaccinoOS is Gentoo-based, are sourced in this site’s piece on MocaccinoOS rather than re-derived here.
18. For the TenFourFox comparison: “TenFourFox FPR32 SPR5 available (the last official build)”, 2021-10-03, and the blog index for the patch set of 2025-02-14. Used only to establish that “hobby mode” has a prior meaning and a project that honoured it.

Funtoo Linux, Sabayon Linux, MocaccinoOS and Gentoo Linux each have a row in the Register, with the date each status was last checked; Funtoo’s row was changed from “Hobby mode” to “Ended” on the strength of this piece. Corrections, with a source, go to editor@lxnaydesign.net and are published on Corrections.