Arch Linux · Hyprland · ARCHMAC Galaxy · Quickshell · Wayland
Beautiful. Repairable. Yours.
ARCHMAC is a reproducible Arch Linux desktop environment built around Hyprland and the ARCHMAC Galaxy Quickshell shell.
The reference platform is the Apple MacBookPro9,2 — 13-inch, Mid 2012.
ARCHMAC is designed to remain:
- inspectable
- repairable
- reproducible
- portable
- hardware-aware
- recoverable
This repository is not merely a dotfiles archive.
It is the engineering record and canonical configuration of a real working Linux workstation.
| Component | ARCHMAC |
|---|---|
| Hardware | Apple MacBookPro9,2 |
| Model | 13-inch, Mid 2012 |
| CPU | Intel Core i5-3210M |
| Graphics | Intel HD Graphics 4000 |
| OS | Arch Linux |
| Kernel | Linux 7.1.11-arch1-1 |
| Session | Wayland |
| Compositor | Hyprland 0.56.2 |
| Desktop shell | ARCHMAC Galaxy |
| Shell framework | Quickshell |
| Terminal | Kitty |
| Audio | PipeWire / WirePlumber |
| Network | NetworkManager |
| Bluetooth | BlueZ |
Galaxy is the current ARCHMAC desktop shell.
It replaces the previous Waybar/Mako-centred desktop with a unified Quickshell environment using centralized services for system state and interaction.
Galaxy provides:
- top bar
- workspace state and navigation
- native system tray
- Control Centre
- Wi-Fi integration
- Bluetooth integration
- audio control
- brightness control
- battery and power state
- hardware telemetry
- hardware monitor
- system OSD
- notification server
- notification history
- application launcher
- calculator
- searchable clipboard history
- spatial workspace overview
- Galaxy Command Centre
- lock/session integration
- power/session menu
- ARCHMAC mode integration
ARCHMAC follows ten rules:
- Inspect before modifying.
- Preserve working behaviour until its replacement is proven.
- Maintain one authoritative state owner per subsystem.
- Prefer event-driven native interfaces over duplicated polling.
- Hyprland owns composition and workspace behaviour.
- Quickshell owns shell presentation and interaction.
- Services own system state.
- Hardware-specific behaviour must remain explicit.
- Configuration must remain portable.
- Verify live behaviour before declaring work complete.
Development flow:
Inspect → Understand → Change → Verify → Diff → Commit
Full desktop effects with balanced power.
Reduced compositor overhead for sustained workloads.
Reduced visual overhead and power-saving behaviour.
archmac/
├── .github/
├── assets/
├── bin/
├── config/
├── docs/
├── manifests/
├── state/
├── install.sh
├── CHANGELOG.md
└── README.md
Before kernel or boot changes, inspect the actual machine state:
findmnt /boot
findmnt /efi 2>/dev/null || true
lsblk -f
bootctl status
uname -r
pacman -Q linux
Before rebooting after kernel work, verify:
- the actual EFI/boot filesystem is mounted;
- the kernel image exists;
- the initramfs exists;
- matching kernel modules exist;
- boot entries reference the correct paths.
Recovery takes precedence over convenience.
ARCHMAC keeps reference state so faults can be compared against a working machine.
The goal is to answer:
What did the system look like when it was known to work?
SOVEREIGN WORKSTATION
│
├── understand the machine
├── reduce unnecessary software
├── keep configuration reproducible
├── preserve recovery paths
├── automate repeatable work
├── record known-good state
└── remove friction before adding complexity
The goal is:
minimum friction per unit of useful work
Useful contributions include:
- MacBookPro9,2 hardware improvements
- Arch Linux compatibility fixes
- Hyprland / Wayland improvements
- Quickshell / Galaxy fixes
- recovery improvements
- documentation improvements
- validation improvements
- simplification
Never commit:
- passwords
- API keys
- private keys
- tokens
- cookies
- credentials
- machine-specific secrets
Tyson Barnes
Engineering · Automation · Systems · Software