| Chimera Linux | |
|---|---|
| | |
| Screenshot of Chimera Linux with default GNOME 44.2 desktop environment | |
| Developer | Chimera Linux developers |
| OS family | Linux (Unix-like) |
| Working state | Current |
| Source model | Open source |
| Latest release | Rolling release / 20 December 2025 [1] |
| Repository | https://github.com/chimera-linux/ |
| Marketing target | General purpose |
| Update method | Rolling release |
| Package manager | apk-tools, cports, flatpak |
| Supported platforms | x86-64, aarch64, loongarch64, ppc64le, ppc64, PowerPC, RISC-V |
| Kernel type | Monolithic (Linux) |
| Userland | BSD |
| Default user interface | GNOME Shell, FreeBSD's Almquist shell [2] |
| Official website | chimera-linux |
Chimera Linux is a Linux distribution striving for the minimum complexity of system configuration while retaining and expanding on the flexibility common to general purpose Linux based systems. The project emphasizes coherent system design, careful component selection, and correctness of implementation rather than incremental evolution of existing GNU/Linux conventions.
The distribution has no upstream and defines itself as "independent" from this perspective.
The defining feature of Chimera Linux is a set of pragmatic choices that deviate from traditional Linux distribution assumptions about which components are used. The aim is to make Linux, as a complete operating system, leaner without limiting its functionality—or, as its original developer q66 puts it, to achieve 90 percent of the outcome with just 10 percent of the complexity. In selecting components, particular attention is paid to code quality and the correctness of their implementation.
A core aspect of this approach is that the rethinking of individual system components and the rethinking of their integration into a complete operating system are intentionally pursued at the same time. By doing so, Chimera Linux avoids the classic chicken or the egg problem common in core system development: whether a new component shall be adapted to an existing system, or an existing system shall be reshaped to accommodate a new component.
This design philosophy results in the following technical choices: [3] [4]
These decisions are not eternally binding. If a better solution for a component becomes available, replacement is an option.
A strict default security model, employing the in-development Dinit init system and the FreeBSD userland are some of the more radical approaches. Such changes would have been very hard for a distribution with an existing user base. [3] [5] [6] [7]
By combining the Linux kernel with a BSD-derived userland and non-GNU core components, Chimera Linux provides an alternative leaner and cleaner implementation of the Linux OS architecture while remaining compatible with existing Linux software. [3] Together with the LLVM toolchain this distribution provides an alternative to the common GNU-based systems, without explicitly excluding GNU tools or GPL licensed software in general.
Chimera Linux follows a rolling release model.
Native software for Chimera Linux is distributed exclusively using APKv3 (Alpine Package Keeper 3 a.k.a. apk-tools) from Alpine Linux. [4] Nonetheless, Chimera does not re-use Alpine packages. It rather uses its own novel Python-based package build system cports inspired by xbps-src and initially to a lesser extent by abuild. [3]
As of March 2025 [update] , Chimera Linux was already using APKv3, at a time when this version was not yet adopted by Alpine Linux itself. [5]
Because Chimera Linux uses musl instead of glibc, some proprietary and closed-source applications that assume glibc compatibility cannot run without additional measures. To address this limitation, Flatpak is included in the distribution.
Flatpak allows applications to bundle their required runtime libraries and run in a sandboxed environment, making proprietary software such as Steam available on Chimera Linux.
As of January 2026, the Chimera Linux repositories provide the following desktop environments:
Chimera Linux was started in 2021 by former Void Linux maintainer “q66”. [5] [4]
The project entered its alpha stage on 11 June 2023, marking the point at which it considered itself suitable for early adopters, with a more stable infrastructure and expanding repositories. [8]
The beta phase began on 27 December 2024, when the package management tools were tagged as release candidates, indicating the transition from alpha to beta quality. [9]
Live image version 20251220 introduced a text-based installer. [10]