Arch Linux Setup
Overview
Switched to Arch Linux in 2023 as the main development machine — built from scratch, no installer hand-holding. Before settling, tried Void Linux for a stretch: musl libc and runit were interesting but the lack of an AUR equivalent meant too much manual work for daily use. Void got shelved. Arch has been the stable choice since.
Switched to Arch Linux in 2023 as the primary development machine — installed from scratch, no GUI installer, no hand-holding.
Before settling on Arch, ran Void Linux for a stretch. musl libc and runit were genuinely interesting, but the lack of an AUR equivalent made daily-use package management too manual. Void got shelved.
Arch has been stable since. The AUR covers everything that matters, and the rolling release model means the system stays current without major upgrade ceremonies.
Running Hyprland as the compositor — a tiling Wayland compositor that stays out of the way and does exactly what's configured.
Stack
Tooling / AI
System / OS
Other
Inspiration
Wanted full control over the development environment — no cruft, no mystery processes, no OS getting in the way of the work.
Structure
Blueprint
Layered system stack — bootloader (systemd-boot) → kernel → Hyprland compositor → shell → terminal → dev toolchains.
Composition
How it works
Base Install
Partition, format, mount, and install base system via archinstall or manual pacstrap.
Bootloader
systemd-boot configured for fast, minimal startup.
Hyprland
Wayland compositor with tiling layout, keybindings, and display config.
Dotfiles
Config files for shell, editor, terminal, and compositor version-controlled in git.
AUR & Packages
paru as AUR helper — dev tools, fonts, and utilities installed and maintained.
Dev Environment
Node, Python, Docker, and language toolchains layered on top.