X Linux

X Linux

Arch-based, snapshot-first Linux with a script-driven installer and its own package tooling — docs and downloads in one place.

Downloads

x86_64 SHA-256 b02af9a09d932928… SHA256SUMS · .sig

aarch64 SHA-256 88d31ba2b9fd2c2e… SHA256SUMS · .sig

A look at X

Real screens from an X install — desktop, tools, boot and installer.

X Linux desktop (light theme)

01 / 11Hyprland desktop (equisdots) — light and dark themes.

Tree diagram of the six X Linux layers: Arch base at the roots, the X system as the trunk, and generations, desktop choices, shell and apps, and signed delivery along the branches.

Foundation

Arch, without the mystery

A familiar base, extended with intent.

Kernel, systemd and pacman stay where you expect them. X adds the text installer, btrfs generations, signed packages and a desktop layer you can replace.

See the project layout
01 / Kernel
linux · linux-lts · linux-zen
02 / Init
systemd · journald · logind
03 / Packages
pacman · [x] · keyring
04 / Filesystem
btrfs · subvolumes · snapshots

X / SYSTEM MAP

The system, in one map

Packages, repository and delivery around one core.

xpm, xpm-aur, xpkg and the signed [x] repository are one graph: build native or Arch-compatible packages, pull from the AUR and install everything through the same transaction model.

Read the docs

Anatomy

Built-in desktops

One system, four ways to land.

Hyprland and niri ship the equisdots stack; KDE Plasma gets X Dark branding. They all sit on the same Arch base, generations, signed packages and X tooling.

Choose the desktop in the text installer. The rest of the system stays the same.

See the desktop guide

Hyprland

equisdots · Lua · light/dark

niri

equisdots · scrollable tiling

KDE Plasma

X Dark · Plasma 6

Console

no desktop · minimal

Root to canopy — the desktop is a choice at install time, not a fork.

Generations

Rollback is a layer

Every transaction leaves a bootable snapshot.

x gen records packages, services, the kernel and /etc as a generation. Boot it, diff it, pin it or restore a single path.

Read the generations

Kernel

Upstream kernels with the X mark

linux-x and linux-x-mainline, built from the official recipes.

X Kernel does not fork Linux. It reuses Arch’s packaging recipe for stable/testing and the AUR mainline recipe, changes only the package base and description, builds in a clean chroot and publishes signed packages to dedicated repositories.

X kernels are additional, not replacements: Arch linux / linux-lts remain the default entries and the fallback.

stable

published
7.3.4.arch1-1[x-kernel]

Arch core/linux recipe. Published and bundled in the 2026.11.15 ISO.

testing

preview
7.3.4.arch1-2local preview

Arch core-testing/linux recipe. Never published by the scripts.

mainline

experimental
7.4rc1-1[x-kernel-mainline]

AUR linux-mainline recipe. Experimental moving line.

From the upstream recipe at the root to the signed SourceForge repositories in the canopy — builds and publication are manual.

Why X

What you get on top of a stock Arch base.

Bootable generations

01

Every package transaction is captured as a btrfs snapshot with its own boot entry. Roll back, diff, verify, pin or export signed and encrypted bundles.

Script-driven installer

02

BIOS or UEFI, GRUB or systemd-boot, LUKS, dualboot, core or full profiles, and Hyprland, niri or KDE Plasma as the desktop — all in the terminal.

Multi-kernel

03

Choose linux, linux-lts or linux-zen at install time or later with x kernel install and remove, protected by guard rails.

Native tooling

04

xpm (manager), xpm-aur (AUR helper) and xpkg (builder) drive the signed [x] repository through native .xp and ALPM packages — built in Rust.

Runs on WSL

05

An importable rootfs plus a friendly first-run setup for terminal-only use on Windows.

Signed end to end

06

The ISO, checksums and [x] packages are signed; the installed system trusts the embedded keyring.

06

system layers

04

desktop choices

02

boot modes

03

package paths

Install in four steps

From ISO to the first bootable generation — the installer runs in the terminal.

1 · Download the ISO

Get the latest signed ISO from SourceForge — the stable link always points to the current release.

Download ISO

2 · Flash a USB drive

Replace /dev/sdX with your device:

sudo dd if=x-<version>-x86_64.iso of=/dev/sdX bs=8M conv=fsync status=progress

3 · Boot and follow the installer

Pick disk layout, kernel, desktop and profile; the first generation is created for you.

Read the install guide

4 · Boot generation 0001

Reboot into the first btrfs snapshot. Roll back, diff or pin it whenever you need.

/@ · btrfs · 0001

Repositories

Every component of the X Linux project lives in the equislinux organization.

Three packaging paths

X combines Arch-compatible packages for pacman, its own native format for xpm, and an AUR helper that routes every transaction through xpm.

[x]pacman

pacman · [x] repository

Arch-compatible .pkg.tar.zst packages served from x-repo. Add the [x] repository to pacman.conf and install with pacman -S.

[x]
Server = https://equislinux.github.io/x-repo/repo/x86_64
.xpxpm

xpm · native .xp

Native packages built by xpkg from XBUILD recipes and installed with xpm. The endpoint lives under x-repo/x/x86_64.

[[repo]]
server = ["https://equislinux.github.io/x-repo/x/$arch"]
AURxpm-aur

xpm-aur · AUR

A Rust AUR helper: resolves dependencies, builds with makepkg in clean chroots and installs or removes everything through xpm.

xpm-aur install <pkg>
xpm-aur upgrade --aur --devel

Documentation

Guides for the distro, WSL, provisioning, packaging and the package repository — in English and Spanish.

Browse documentation