About Aelum

What Aelum is

An Arch Linux distribution with one unusual property: the installer carries every package it installs. Most of the rest of this page follows from that.

What is Aelum, exactly?

An Arch Linux distribution whose installer needs no network. The ISO carries a complete package mirror, so the install reads only from the USB stick you booted it on. What it writes is a normal Arch desktop — Hyprland with Dux Shell, a media player and a package manager — on a disk layout the installer prepares itself, with its own boot entry and its own boot splash.

Is it Arch Linux? A fork of Arch?

It installs from Arch's official repositories with pacstrap, and after the install it is an Arch system: the same pacman, the same systemd, the same repositories, the same AUR — plus one signed repository of Aelum's own, holding the applications the distro ships, which the installer enables and trusts for you. Everything else Aelum is the parts around that base: the live session, the installer, the desktop configuration, the boot theme. It is an independent project, not an official Arch Linux product and not a fork of Arch.

Do I have to reinstall to stay current?

No. The ISO is only a starting point, and its version is the date it was built. Once installed, your system moves forward the way any Arch machine does: sudo pacman -Syu. A newer ISO matters only when you want to install on another machine.

Why bother with an offline installer?

An install that needs no network cannot fail at a mirror, and a machine that has just been wiped — no drivers configured yet, no cable plugged in — still ends up with a complete desktop. It also means the install is reproducible: the packages you got are the packages that were in the image.

Is it free and open source?

GPL-3.0, in every part of it: the live session, the installer, the pipeline that builds the ISO, and this website. The source is public, and every release is signed so you can check the file you downloaded against the key published on this domain.

Does Aelum collect anything about me or my machine?

Nothing. The install makes no network calls at all, and the installed system ships no account, no telemetry service and no update path that goes through Aelum instead of Arch. We have no way to know you installed it unless you tell us.

Before you boot

Hardware, firmware and the live session

The installer checks the disk before it writes anything to it. These are the requirements it enforces, and the ones it deliberately leaves alone.

What machine do I need?

The installer enforces the disk size and nothing else. There is no swap partition or swap file to make room for either: the installed system uses zram, compressed swap in RAM, so the space you have left is yours.

  • A 64-bit x86_64 machine.
  • UEFI firmware.
  • At least 8 GB free on the disk it installs to — a smaller disk is refused before anything is written.
  • A USB drive large enough for the 4.41 GB image.
Legacy BIOS or UEFI?

The image boots either way — syslinux for legacy BIOS, GRUB for UEFI — so you can start the live session on an older machine. Installing wants UEFI: an EFI system partition, rEFInd, and a firmware boot entry are what make the installed system start on its own.

What about Secure Boot?

The installer does not configure Secure Boot and does not sign the kernel or the boot loader for it. On a machine that enforces it, turn Secure Boot off (or enroll your own keys) before installing.

Do I need internet to install?

No — that is the point of the ISO. Every package comes from the mirror inside it, and the installer never opens a connection. You need a network afterwards: for updates, and for anything you add yourself.

Can I try Aelum without installing it?

No. The ISO is installation media. The live session exists to run the installer: it boots, logs in, and opens the installer window. The desktop's own apps are in the live session too, so you can open the player or the package manager while you wait — but that session is a read-only overlay, and nothing you change in it survives the reboot.

Does it run in a virtual machine?

Yes — with UEFI firmware (OVMF / edk2) and a virtual disk of 8 GB or more. Every install variation Aelum publishes is tested exactly this way: a real virtual disk, a real partition table, a real firmware boot entry, checked after the install.

Can I install onto a USB SSD or an external drive?

Yes. The installer treats it like any other disk and writes its own firmware boot entry. Some firmware keeps removable devices out of the boot order, so the first boot may need one pick from your firmware's boot menu.

Can I boot the ISO from Ventoy?

Yes. Ventoy, BalenaEtcher and dd all work; the Download page walks through each one. The Aelum boot theme even ships its own Ventoy and USB glyphs, so a Ventoy stick in the menu is recognisable at a glance.

Will it work on my GPU?

The installer reads the PCI bus and installs the driver set that matches your card: vulkan-radeon or vulkan-intel for AMD and Intel, nvidia-open-lts for Turing-and-newer NVIDIA, and vulkan-nouveau for older NVIDIA. The right Vulkan driver is on the system before its first boot, so nothing asks you to choose a provider later.

Will Steam or other 32-bit software work?

Yes. The installer turns on Arch's [multilib] repository — the one Steam, Wine and their 32-bit libraries live in, which a stock pacman.conf ships commented out — and the GPU driver set it picks always provides lib32-vulkan-driver alongside the 64-bit one. So sudo pacman -S steam has an answer for every dependency instead of stopping to ask which Vulkan driver you want.

The installer

Running the installer

Four questions, eight steps, less than 2 minutes. The window and the command line run the same implementation, so they end in the same system.

What does the installer actually ask?

Four things, in this order: a language, a username and password, a disk, and a confirmation. The language screen also shows a location, filled in from the language, for the case where your country is a different one. Filesystem, encryption and the partitioning mode are all on the disk screen, so there is no fifth question waiting for you later.

How long does an install take?

Less than 2 minutes on a modern disk. Two package-install stages do nearly all of it; partitioning, the boot loader and configuration take the rest. Each step is named in the window as it runs.

What happens after I press confirm?

Eight steps, in this order:

  • Format the disk
  • Mount the filesystem
  • Install the base system
  • Install the desktop
  • Create your user
  • Configure the system
  • Clear the package cache
  • Verify the result
What software do I get?

A desktop, not a base system you have to assemble yourself:

  • Hyprland, Dux Shell and the Dux Greeter login (greetd)
  • Videos (Aelum's media player) and Packages (Aelum's package manager)
  • Foot, Nautilus, GNOME Text Editor, Firefox, Loupe, Papers — and mpv, which the player is built on
  • PipeWire audio with WirePlumber
  • matugen and the GTK / Qt theming that follows it
  • btop, fastfetch, brightnessctl, ddcutil
  • NetworkManager, bluez, power-profiles-daemon, zram, sudo, vim, nano
  • base-devel, so an AUR build has a compiler and make already on the machine
  • rEFInd with the Aelum theme, and the Aelum Plymouth splash
  • On a btrfs install: snapper and btrfs-assistant
Does it set my keyboard layout, timezone and locale?

Yes, from the two answers on the first screen. Your language sets the system locale. The location beside it sets the timezone and NTP, the keyboard layout in the console and in the desktop session, the mirror list, and the weather the desktop reports. That location is already filled in from your language, so you change it only when your country is a different one; the choices are every country Arch's mirror list names a section for, plus a worldwide entry. The mirror list written for you takes that country's mirrors first and the worldwide ones after them. Change any of it later with localectl or timedatectl.

Can I run the install from the terminal?

The live session ships a headless installer next to the GUI. It runs the same eight steps and ends with the same system, which is what makes an install scriptable. Passwords are read from stdin only, never from a flag, and --dry-run walks the whole flow without touching a disk.

sudo /usr/local/bin/aelum-installer-cli --install /dev/sda
sudo /usr/local/bin/aelum-installer-cli --install /dev/sda --filesystem ext4
sudo /usr/local/bin/aelum-installer-cli --install /dev/sda --luks --lvm
sudo /usr/local/bin/aelum-installer-cli --install /dev/sda --gpu-driver nvidia
echo 'your password' | sudo /usr/local/bin/aelum-installer-cli --install /dev/sda
The install failed. Where do I look?

The live session keeps a log at /var/log/aelum-install-<timestamp>.log, and the window names the step and the command that failed. Open the newest file and search for ERROR:. Then roll the disk back and start again — and attach that log when you report the problem.

tail -50 "$(ls -t /var/log/aelum-install-*.log | head -1)"
sudo /usr/local/bin/aelum-installer-cli --rollback /dev/sda
Can I run the installer again on the same disk?

Yes. Automatic mode clears the partition table and starts from nothing; manual mode formats only the two partitions you assign. If an earlier attempt left something half-written, run the rollback first: it releases mounts and volume groups and wipes filesystem signatures.

The disk

Partitions, filesystems and encryption

The one decision that can cost you data, and the choices that decide what you can undo later.

Will automatic mode erase my disk?

Yes — completely. It drops the partition table, writes a 512 MB FAT32 Boot partition and one System partition with the rest of the disk, and the confirmation dialog says in plain words that all data on this disk will be permanently erased. Use it on a disk that is Aelum's alone.

I have another operating system, or files, on that disk.

Switch the same screen to manual mode. You designate one Boot and one System partition, only those two are formatted, and every other partition is left exactly as it was. Two things to know first: the disk needs a GPT partition table (an MBR disk is refused before anything on it is written, and automatic mode would clear it and write a GPT), and Aelum wants its own Boot partition — pointing it at another system's ESP formats that ESP and destroys that system's boot loaders.

  • Aelum mounts only the partitions it owns; mount your old data yourself afterwards.
  • Manual mode needs a 512 MB Boot and a 7680 MB System partition on top of the 8 GB floor.
btrfs or ext4?

btrfs is the default, and it is the one with the behaviour: subvolumes for @, @home, @srv, @cache, @tmp and @log; the system installed into @/.snapshots/1/snapshot, which is the filesystem's default subvolume; snapper configured for @ and @home; a snapshot pair around every pacman transaction; and a snapshot submenu under your boot entry. ext4 is one plain partition — no subvolumes, no snapper, no snapshot menu. Choose ext4 if you want the simplest layout you can inspect by hand; choose btrfs if you want a state you can go back to.

How much space does the installed system use?

Roughly 3.2 GB on btrfs and 4.7 GB on ext4. The 8 GB floor exists so the system has room to grow: your files, the package cache, and on btrfs the snapshot history.

Can I encrypt my disk?

Turn on LUKS2 on the disk screen and type a passphrase once. Afterwards the only thing that has changed is that you type that passphrase into the Aelum boot splash. Encryption covers the whole System partition — there is no home-only encryption — and it always sits below LVM when you choose both.

Can I add encryption to an install I already made?

Not with the installer: it has no re-encryption mode and no in-place LUKS conversion. Make the choice on the disk screen, or install again with encryption on.

What does LVM buy me?

One physical volume on the System partition, one volume group named after the install, and two logical volumes, root and home, which you can resize or move later. It changes nothing about how the system boots: the fstab and the boot entries reference filesystem UUIDs, never /dev/mapper paths.

Swap: partition or file?

Neither, on purpose. The installed system uses zram — compressed swap in RAM, configured through zram-generator — so no disk space is reserved for it and no snapshot carries an old swap file with it.

Can I install Aelum twice on one disk?

Yes, and each install needs its own pair of partitions. Automatic mode clears the partition table before it writes anything, so the second install has to run in manual mode with the first install's partitions left as Preserve. Manual mode always formats the Boot and System partitions you pick, so two installs cannot share one Boot partition — the second install would erase the first one's boot loaders.

  • Each install gets its own Boot partition, its own rEFInd on it, and its own firmware boot entry.
  • Each keeps its kernel and initramfs in aelum/<id>/ on its own ESP, bind-mounted at /boot, and its own menu fragment at EFI/refind/aelum/<id>.conf.
  • Menu entries and firmware entries are titled with the root partition, so the two read as Aelum (sda2) and Aelum (sda3).
Where is the EFI partition once installed?

Mounted at /efi. That install's boot directory is bind-mounted at /boot, which is why pacman and mkinitcpio keep working exactly as usual while the files physically stay in the install's own ESP directory.

Boot & recovery

Boot menu, snapshots and going back

On a btrfs install, every pacman transaction leaves a state behind. This is how you find one, boot it, and make it the system again.

What bootloader do I get?

rEFInd, written into Aelum's Boot partition with the Aelum theme, plus one menu entry per install that boots that install's own kernel by filesystem UUID. rEFInd also scans the other ESPs on the disk, so another operating system usually appears in the same menu.

How do I reach the snapshots?

On a btrfs install: in the boot menu, select the Aelum entry and press F2 — Insert, Tab and + work too. The submenu lists your snapshots, each titled with its number, date and type. Choosing one boots that state read-only as /.

How do I make an older state the system again?

Boot it. The desktop then asks — in the language your system uses — whether to restore that state. OK runs the restore helper and, once it succeeds, offers the reboot that boots the restored system; CANCEL closes the prompt and changes nothing. A rollback takes an undo snapshot of the state you were in first, so this is reversible.

  • From a terminal, name the number: without one, snapper rollback means "the state I am booted in", which is only the right answer from inside a snapshot.
  • Your user is in wheel and snapper allows wheel, so this needs no sudo.
  • /home, /srv, /var/cache, /var/tmp and /var/log are separate subvolumes and stay the live ones: a rollback changes the system, not your files.
pkexec /usr/local/bin/aelum-snapshot-restore --reboot
snapper -c root rollback 7
Which snapshots exist, and where do they come from?

Every transaction makes its own pair, and only the states someone chose are kept:

  • A pre and post snapshot around every pacman transaction, so an update's effect can be listed exactly.
  • A third hook marks that pair important when the transaction touched a kernel, glibc, systemd, btrfs-progs, snapper, refind, mkinitcpio, the firmware or a Mesa / Vulkan driver — the states a rollback is for.
  • Timed snapshot creation is off: a timer that fired at 03:00 is not a state anyone decided to be able to return to.
  • Limits are set as ranges, so old ordinary pairs are cleaned up automatically while important ones are kept.
Are snapshots a backup?

No. They live in @/.snapshots, on the same disk. They save you from a bad update, not from a dead drive — copy what matters somewhere else.

Can I see what an update changed?

Yes. Two snapshots of the same transaction are a diff waiting to be read: snapper -c root undochange 7..8 lists what changed between them. btrfs-assistant is installed on btrfs systems as the window onto the same history.

Booting a snapshot feels different. Is something wrong?

The root is read-only, and that is deliberate: it lets you log in, compare and copy before deciding. The installer plans for it — a systemd generator puts tmpfs over the state directories a read-only root cannot write, so a snapshot boot reaches the greeter instead of a text login, and /etc/resolv.conf is a symlink to the running resolver, so a snapshot still resolves names. The desktop prompt tells you which state you are in.

There is no Aelum entry in my firmware boot menu.

Some firmware — and some virtual machines — refuses the NVRAM write. The installer logs it as a warning and finishes; the system is still bootable. Pick the drive in your firmware's boot menu and choose EFI/refind/refind_x64.efi.

Another operating system doesn't appear in the menu.

rEFInd scans every readable ESP; Aelum's own config suppresses only duplicate fallback loaders. Check that the other system's loader actually exists on its ESP — EFI/systemd/systemd-bootx64.efi, or a linux* entry under loader/entries — and that refind.conf has no dont_scan_dirs or dont_scan_files line covering it.

Can I replace rEFInd with GRUB or systemd-boot?

It is Arch — you can. Know what you are removing: the Aelum theme, the per-install entries and the snapshot submenu are rEFInd pieces. Without it you keep your system and lose the boot menu that lists your states.

I chose ext4. Where are my snapshots?

There are none. An ext4 install has no subvolumes, no snapper and no snapshot submenu — it is a plain filesystem, and going back means your own backup or a reinstall.

The desktop

Living on Hyprland + Dux Shell

The parts that are already configured, and the few things that deliberately are not.

The colours change when I change the wallpaper. Why?

That is matugen. Pick a wallpaper in the control center and the shell, your GTK apps and your Qt apps follow it; light, dark or automatic is a setting in the same place. The point is that you choose a picture, not a palette.

How do I start applications?

Press Super + Space and start typing. A handful of apps is already installed — files, browser, editor, media player, package manager, terminal — and anything else you add from the repositories shows up there too.

How do I install or remove programs?

Open Packages — it is already installed. It has a page for what you installed, one for everything in your repositories, one for Aelum's own applications, one for the AUR, and one for whatever has an update waiting. Installing, removing and updating authenticate once through polkit, the same action the snapshot restore uses, and every transaction shows pacman's real output, so a failure is never silent. Double-clicking a .pkg.tar.zst installs it through the same window, and pacman in a terminal still does exactly what it always did.

  • The AUR page searches the AUR when you type, and installing a result brings in its repository dependencies, builds the PKGBUILD on your own machine with makepkg, and installs what the build produced — one log for the whole request.
  • Nothing is fetched from the AUR until you ask: the tab carries no badge and the app makes no unasked call to it.
  • A dependency that several packages could answer gets one chooser in that window, before the transaction starts, with pacman's own default already selected.
Is it Wayland only? Will my X11 apps run?

Hyprland is a Wayland compositor and the login screen is greetd with Dux Greeter, not an X11 display manager. Older X11 applications run through XWayland.

Can I use GNOME, KDE or another compositor instead?

Yes — the installed system is Arch. Install another desktop from the repositories and it is there, with its own session. What you would be replacing is Aelum's own configuration: the greeter, the theme, and the snapshot prompt that lives in the shell.

Do I need a root password?

No. The user you created is in wheel and sudo works with your password. The privileged actions the desktop offers as buttons — restoring a snapshot, and every package transaction in the Packages window — go through polkit, so they ask for that same authentication instead of a separate secret.

Can I change the language after installing?

The system locale is yours to change with localectl. The shell's own translations are not complete in every language yet — the desktop language is a setting in Dux Shell, and the prompt that asks about a booted snapshot follows the system's language at the moment it appears.

Is there an ad blocker in Firefox?

Firefox ships themed to match the desktop, and a distribution policy installs uBlock Origin on its first launch. That first launch needs internet; after it, nothing is fetched for the add-on.

Will it print?

Not out of the box: there is no CUPS in the image, so there is no printer queue set up. Install cups and your driver from the repositories if you need one.

Bluetooth, brightness, power?

Bluetooth is installed and enabled, as is NetworkManager. Screen brightness goes through brightnessctl, external-monitor power through ddcutil, and power profiles through power-profiles-daemon — all of them already wired to the shell's controls.

Can I use a VPN?

Yes — the shell carries a VPN toggle in the bar and the control center, and every install ships the protocols for it to speak. OpenVPN and the AnyConnect family (GlobalProtect, Fortinet) arrive as NetworkManager plugins; WireGuard needs no plugin at all, because NetworkManager and the kernel carry it, and the wg/wg-quick tools your provider's setup doc names ship too. The VPN page of Dux Shell's settings imports the .ovpn or .conf file you were given and answers its authentication prompts. For an RSA SecurID token, import the seed file your employer gave you with stoken import in a terminal, or restore the “Software Token” app in the shell's Hidden apps settings — the applet ships beside OpenConnect on every install, and the launcher starts with it hidden because a token app with no seed has nothing to show. Anything else is a package install away: IKEv2 takes networkmanager-strongswan, L2TP takes networkmanager-l2tp, and the shell lists whatever plugin pacman puts in place.

Updates & help

Updates, source and getting help

After the install, Aelum behaves like Arch. Here is where the Aelum-specific parts stop.

How do I update the system?

Open Packages and go to its Updates page: the updates waiting are listed there, and one click on Update All starts the system upgrade as one transaction. In a terminal it is sudo pacman -Syu, like any Arch machine, and it is the same command the button runs. Both sync through the mirrorlist the installer wrote for the location you chose, and the [aelum] repository it enabled carries the distro's own applications into the same upgrade. Your home also starts with three shortcuts in ~/.bashrc: app-search (pacman -Ss) to look for a package, app-install (sudo pacman -Syu) to update and install, and app-remove (sudo pacman -Rsn) to drop one along with the dependencies nobody else needs. They are ordinary aliases — change or delete them in that file whenever you like:

app-search <name>
app-install <name>
app-remove <name>
My mirrors are slow or down. How do I change them?

The installer writes a mirrorlist of Arch mirrors for the location you chose, and /etc/pacman.d/mirrorlist is what every pacman -Sy reads. To change it in a window: open Packages, press Update mirrors in its menu, and search for a country — you get that country's twenty newest HTTPS mirrors, in the order of the download rate Arch measures for each. Leave the search empty for every mirror in Arch's list instead of one country's. reflector, the program that ranks mirrors, is not installed by default, so the first press installs it in the same transaction. From a terminal it is the same file, and you can edit it by hand as well:

sudo pacman -S reflector
sudo reflector --latest 20 --protocol https --country de --sort rate --save /etc/pacman.d/mirrorlist
Why does pacman say a package's signature is invalid or its key is missing?

Pacman checks every package and every repository database against the signing keys in /etc/pacman.d/gnupg, and when that check fails you get required key missing from keyring, invalid PGP signature, or invalid or corrupted package (PGP signature). Those keys are themselves a package — archlinux-keyring — so on a machine that has not been updated for a few months they can simply be older than the keys Arch signs current packages with. A damaged keyring directory, or one left with permissions pacman cannot use, ends the same way; pacman-key names that case by telling you to run it with --init. One repair covers both, and it needs no network: the keys come from files already on your system. In a window, open Packages and press Repair signing keys in its menu. In a terminal it is the first two commands below — the first creates whatever the keyring is missing, its local signing key and its file permissions among them, and the second imports the keys archlinux-keyring ships and signs them. The last two bring the current archlinux-keyring onto your system, then update as usual. That single-package sync leaves your databases newer than your system until you finish it, so run the full upgrade straight after:

sudo pacman-key --init
sudo pacman-key --populate
sudo pacman -Sy archlinux-keyring
sudo pacman -Syu
Where do Aelum's own applications come from?

From the [aelum] repository, which the installer turns on and trusts for you. It is an ordinary signed pacman repository on the same CDN as the ISOs, signed with the Aelum release key, and it holds the distro's applications: the media player, the package manager, and whatever comes next. A fresh install already has those apps from the ISO's own mirror; the repository is what carries their updates into pacman -Syu. Another Arch system can use it too — add the repository block to pacman.conf and import the key once:

curl -O https://cdn.aelum.dev/repo/aelum.gpg
sudo pacman-key --add aelum.gpg
sudo pacman-key --lsign-key 728F5F59FB2F5A88C6EE28D4930A672A3A1B5B60
Is the AUR available?

Yes — it is Arch. The Packages window has an AUR page: it searches the AUR as you type, and installing a result brings in its repository dependencies, builds the PKGBUILD on your machine with makepkg, and installs what the build produced. The build tools (base-devel) are installed with the base system, so any AUR helper you like works too. Four of the desktop's own pieces (qtengine, dux-greeter-bin, fluent-icon-theme, nautilus-open-any-terminal) are built from the AUR into the ISO, which is why they are already there when you boot.

How do I know the ISO I downloaded is genuine?

Every release publishes SHA-256 and SHA-512 checksums and a detached GPG signature, and the release key is published on this domain over WKD so gpg can fetch it by email. The three commands are on the Download page.

How often does a new ISO come out?

A release is published when there is something to ship, and its version is the date of that build. You never need a new ISO to keep an installed system current.

Where do I report a problem?

On GitHub, against the repository that owns the behaviour: the installer for anything that happens during or right after an install, the live-ISO profile for the live session and the boot theme, and the separate video-player and package-installer repositories for the desktop's own apps. Include what you expected, what you got, the disk and filesystem you chose, the ISO version, and the install log — it names the step and the command.

Where do I ask questions?

Discord is where the project is discussed day to day: install questions, desktop questions, and the parts of the docs that turned out to be unclear.

Can I build my own ISO?

Yes. The live session profile and the installer are separate public repositories under the same GitHub organisation, both GPL-3.0: the profile is archiso content, and the installer is Go and Svelte with tests you can run without a disk. Building an ISO from them needs an Arch machine, root, and about 25 GB of free space.

Get started

Ready to install Aelum?

Download the ISO, write it to a USB stick, and boot from it. You need no internet for the install, and it takes less than 2 minutes.