Case study · Summer 2025–Present
Custom Linux Environment
A hand-configured Arch Linux daily driver with Hyprland, custom services, logging, permissions, and automated setup.
- Discipline
- Linux · Systems operations
- Technology
- Arch Linux · Hyprland · systemd · Bash · FACL
systemctl: active
journal: clean
hyprland: ready
permissions: verified
aakkash@arch ~ $ _Overview
This is less a weekend project than an operating practice: I built and maintain my own Arch environment, author systemd services, inspect journald logs, and automate setup with Bash.
System map
How the pieces connect
The challenge
What made the problem worth solving
Using Linux as a daily driver turns configuration into an ongoing systems exercise: services fail, dependencies change, permissions matter, and every convenient abstraction eventually exposes the layer below.
The approach
Turning the problem into an engineering plan
- 01
Built the desktop around Arch Linux and Hyprland instead of treating a preconfigured VM as the finished environment.
- 02
Authored service units and managed dependencies, targets, and logging with systemd and journald.
- 03
Used POSIX permissions, file access-control lists, and Bash automation to make the environment repeatable.
Result
Maintaining the environment made systems knowledge part of my everyday workflow—not a list of commands learned once for a course.