CRUX
CRUX is a lightweight Linux distribution built for experienced users who want to get their hands dirty, not click through a wizard. The name itself is a small mystery. Per Lidén, the person behind CRUX, chose it simply because it "sounded cool" and ended in the letter X, placing it in the company of operating systems like IRIX, Ultrix, Mac OS X, and IBM AIX. That crux happens to be the Latin word for "cross" played no part in the decision. So from its first moment, CRUX announced something about its personality: it does not perform for you. It performs because you made it perform. What does it mean to build a Linux system where you compile your own kernel and write your own commands? And how does a distribution with no graphical installer, no hand-holding, and no parent distribution attract a dedicated following across more than two decades of releases?
CRUX targets the x86-64 architecture and delivers its software through a tar.gz-based package system with BSD-style initscripts. Crucially, it is not based on any other Linux distribution. That independence is unusual. Most distributions descend from Debian, Red Hat, or another major ancestor. CRUX starts from its own foundation, which means its design choices reflect its own philosophy rather than an inherited one. The distribution also uses a ports system for installing and upgrading applications, a model borrowed from BSD-based operating systems rather than the mainstream Linux tradition. That BSD influence runs through more than just initscripts; it shapes the entire package management architecture.
CRUX includes no graphical installation program. A new user boots the kernel from either a CD or a diskette, then proceeds entirely through shell commands. The sequence is demanding by design. The user partitions the hard disk using a tool like fdisk or cfdisk, creates the appropriate file systems on each partition, mounts the CD or an NFS share alongside those partitions, compiles a new kernel from scratch, and finally installs a bootloader. Simone Rota, reviewing CRUX for OSNews, observed that because users compile their own kernel and modules, the hardware compatibility list is effectively the same as the Linux kernel itself, which was version 2.4.21 on the release Rota tested. The bootable CD's kernel is compiled with a deliberately small set of options, just enough to boot and begin installation. If a piece of hardware is not supported and no third-party module is on the CD, the only path forward is to fetch the driver from another machine.
Each CRUX package consists of several distinct files. There is a Pkgfile, which is a shell script; any patches needed to make the program function correctly; md5sum hashes that verify the integrity of downloaded files; and a footprint file that lists exactly which files the package will install. These components are downloaded from a CRUX software repository. The system then compiles and installs them using the prt-get frontend. Software source code is fetched directly from each upstream project's own website, at whatever address the Pkgfile specifies. This design keeps CRUX close to original sources rather than maintaining its own mirrored archive, and it keeps the user aware of exactly what is being built and where it came from.
Version 1.0 arrived in December 2002, and the project has continued releasing steadily ever since. Version 2.0 came in March 2004, followed by a progression through the 2.x series that brought updates roughly every six months to a year. The 3.0 release landed in January 2013, crossing into new major-version territory. From there the project released 3.1 in July 2014, 3.2 in November 2015, 3.3 in February 2017, 3.4 in May 2018, 3.5 in June 2019, 3.6 in December 2020, and 3.7 in September 2022. The most recent entry in the release history is version 3.8, which arrived in April 2025. That span from December 2002 to April 2025 represents a remarkably consistent commitment for a project that operates outside the mainstream distribution ecosystem and carries no commercial backing.
Common questions
What is CRUX Linux and who is it designed for?
CRUX is a lightweight x86-64 Linux distribution targeted at experienced Linux users. It is delivered through a tar.gz-based package system with BSD-style initscripts and is not based on any other Linux distribution.
Why is CRUX Linux called CRUX?
Per Lidén chose the name CRUX because it "sounded cool" and ends in the letter X, placing it alongside other Unix-flavored names like IRIX, Ultrix, Mac OS X, and IBM AIX. The fact that crux is the Latin word for "cross" played no part in the naming decision.
How do you install CRUX Linux?
CRUX has no graphical installer. Users boot the kernel from a CD or diskette and then complete the entire installation through shell commands, including partitioning the disk with fdisk or cfdisk, creating file systems, compiling a new kernel, and installing a bootloader.
How does CRUX Linux manage packages?
CRUX uses a ports system similar to BSD-based operating systems. Packages consist of a Pkgfile shell script, required patches, md5sum hashes, and a footprint file. They are compiled and installed using the prt-get frontend, with source code fetched directly from upstream project websites.
When was CRUX Linux first released?
CRUX 1.0 was released in December 2002. The project has continued releasing steadily since then, with version 3.8 arriving in April 2025.
What did reviewers say about CRUX Linux hardware compatibility?
Simone Rota, reviewing CRUX for OSNews, noted that because users compile their own kernel and modules, the hardware compatibility list is essentially the same as the Linux kernel itself. On the tested release, that was kernel version 2.4.21.