Package Categories and References

Unknown — Wed, 29 Apr 2026 16:28:36 +0100

🔗</a>1. Core System</h1>
These packages form the absolute foundation of the operating system. Without them, the machine will not boot or function correctly.
🔗</a>Base System</h2>
The minimal package set required for a bootable Arch Linux installation. It includes the GNU core utilities, the C library, systemd, and the Pacman package manager. Without this layer, the system simply does not exist.

Examples: `base</code>, base-devel</code></li>`
`Why it matters: base</code> pulls in the fundamental userspace tools needed to interact with the system, while base-devel</code> provides the compilation toolchain (gcc</code>, make</code>, fakeroot</code>) required to build packages from the Arch User Repository (AUR) or compile software from source.</li> </ul>`🔗</a>Linux Kernel</h2> The core software layer managing memory, processes, hardware devices, and system calls. The kernel acts as the bridge between your physical hardware and your software applications. Arch ships the vanilla upstream kernel by default, though alternatives exist with modified scheduling, patching, or hardening characteristics. Examples: linux</code>, linux-lts</code>, linux-zen</code>, linux-hardened</code>, linux-headers</code></li> Why it matters: The standard linux</code> kernel moves fast and tracks stable upstream releases. linux-lts</code> provides long-term support, which is invaluable as a reliable fallback if a leading-edge driver breaks. linux-zen</code> applies tuning and scheduling tweaks optimised for desktop responsiveness and low-latency workloads. The linux-headers</code> package is strictly required to compile out-of-tree kernel modules for custom hardware drivers, virtualization software, or virtual private networks.</li> </ul> 🔗</a>Firmware</h2> Binary blobs loaded by the kernel onto hardware devices during the boot sequence. This includes graphics unit microcode, wireless network interfaces, audio digital signal processors, and NVMe controllers. Missing firmware results in uninitialised hardware or severely degraded performance. Examples: linux-firmware</code>, sof-firmware</code></li> Why it matters: Modern hardware relies heavily on proprietary firmware blobs to initialise hardware controllers. Without linux-firmware</code>, your Wi-Fi card will not scan for networks and your GPU will fail to accelerate graphics. sof-firmware</code> (Sound Open Firmware) is critical for modern laptop audio routing and digital microphone arrays.</li> </ul> 🔗</a>CPU Microcode</h2> Processor-specific stability and security updates applied by the bootloader or initramfs before the operating system initialises. These patches address hardware errata directly at the silicon level without requiring a motherboard BIOS update. Examples: intel-ucode</code>, amd-ucode</code></li> Why it matters: Silicon is rarely bug-free. Microcode updates mitigate critical processor vulnerabilities and hardware stability bugs. You install the specific package corresponding to your processor manufacturer, and the system applies the patches into the CPU registers during early boot.</li> </ul> 🔗</a>Bootloader</h2> The initial executable initiated by the motherboard firmware (UEFI or BIOS). It locates the kernel image, passes command-line parameters, and transfers execution control to the operating system. Without a bootloader, the system will not start. Examples: grub</code>, efibootmgr</code>, systemd-boot</code>, refind</code>, sbctl</code></li> Why it matters: grub</code> is the traditional, feature-rich bootloader capable of handling complex storage configurations like LUKS encryption and LVM out of the box. efibootmgr</code> interacts directly with motherboard UEFI variables to modify boot order entries. systemd-boot</code> offers a minimalist, lightweight alternative integrated directly into the systemd ecosystem. For users requiring Secure Boot verification, sbctl</code> automates the creation and enrolment of custom cryptographic keys.</li> </ul> 🔗</a>Init System</h2> The primary user-space process (PID 1) started by the kernel. It mounts filesystems, initialises hardware daemons, manages system services, and orchestrates user sessions. Arch Linux relies on systemd as its default init software. You do not replace this unless you know exactly why. Examples: systemd</code></li> Why it matters: systemd is more than just an init system; it is a suite of system management building blocks. It manages service dependencies, socket activation, logging (journald</code>), device management (udev</code>), and user session tracking (systemd-logind</code>).</li> </ul> 🔗</a>Filesystem Utilities</h2> User-space tools required to create, check, resize, and repair filesystems. You also need these packages to mount external storage formatted with non-native filesystems such as Windows NTFS or FAT32 partitions. Examples: xfsprogs</code> (XFS), e2fsprogs</code> (ext4), dosfstools</code> (FAT32), btrfs-progs</code> (Btrfs), ntfs-3g</code> (NTFS), exfatprogs</code> (exFAT)</li> Why it matters: The kernel contains the drivers to read and write to filesystems, but userspace utilities are required to format (mkfs</code>), label, or repair (fsck</code>) those volumes. Installing tools like ntfs-3g</code> and exfatprogs</code> ensures seamless read and write compatibility when connecting external drives or USB flash media from Windows and macOS environments.</li> </ul> 🔗</a>Man Pages</h2> The local manual and documentation system. Installing these ensures you have complete offline technical references for shell commands, system calls, and configuration syntax. Without this, you will rely on the internet for every minor syntax query. Examples: man-db</code>, man-pages</code>, texinfo</code></li> Why it matters: man-db</code> provides the reading engine and manual indexing, while man-pages</code> supplies the documentation for Linux system calls, C library functions, and kernel interfaces. A terminal-first workflow relies heavily on local documentation for immediate problem solving.</li> </ul> 🔗</a>Time Synchronisation</h2> Network Time Protocol (NTP) daemons maintain accurate system clocks by querying external time servers. An uncalibrated clock causes HTTPS certificate validation failures, authentication token rejection, and inaccurate system logging. Examples: systemd-timesyncd</code>, chrony</code></li> Why it matters: systemd-timesyncd</code> is already present on most Arch installations and handles lightweight, SNTP-based clock synchronisation perfectly for standard workstations. chrony</code> is a robust alternative designed for hardware that frequently sleeps, disconnects from the network, or requires sub-millisecond precision.</li> </ul> 🔗</a>Disk Encryption</h2> Cryptographic tools that secure physical storage volumes against unauthorised offline access. If you implement LUKS encryption during installation, cryptsetup</code> manages container unlocking at boot. Examples: cryptsetup</code>, lvm2</code>, veracrypt</code></li> Why it matters: cryptsetup</code> provides the command-line interface for configuring LUKS (Linux Unified Key Setup) volumes, ensuring data remains unreadable without the correct decryption passphrase or keyfile. lvm2</code> provides Logical Volume Management, allowing you to carve a single encrypted LUKS container into flexible, resizable logical volumes for root, home, swap, and system variable storage.</li> </ul> 🔗</a>2. Display & Compositor</h1> 🔗</a>Wayland Compositor</h2> The core software managing window placement, input device routing, output display configurations, and graphical rendering. On a standard desktop environment like GNOME or KDE, the compositor is bundled in. On a standalone window manager setup, it is its own standalone package. On Wayland, the compositor functions simultaneously as the window manager and the display server. Examples: niri</code>, sway</code>, river</code>, hyprland</code></li> Why it matters: niri</code> operates as a scrollable-tiling Wayland compositor designed for dynamic, keyboard-driven workflows, arranging windows in an infinite horizontal ribbon. sway</code> provides a drop-in Wayland replacement for the i3 tiling window manager. river</code> is a dynamic tiling compositor built around custom tags and programmable layout generators.</li> </ul> 🔗</a>Display Manager (Login Manager)</h2> A graphical or terminal-based login interface that authenticates user credentials and initialises the desktop session environment. While you can initiate a compositor directly from a terminal console using a shell script or session wrapper, a display manager automates the login sequence cleanly. Examples: ly</code>, greetd</code> (with tuigreet</code>), sddm</code>, gdm</code></li> Why it matters: ly</code> is a lightweight, TUI-based display manager that renders cleanly in the console without pulling in heavy graphical toolkit dependencies. greetd</code> is a minimal, agnostic login daemon that pairs with greeters like tuigreet</code> to provide a fast, terminal-styled authentication prompt.</li> </ul> 🔗</a>Wayland Session Manager</h2> A utility that launches a Wayland compositor within a structured systemd user session. This ensures environment variables export correctly, D-Bus user buses initialise, and desktop portal services bind to the session cleanly. Examples: uwsm</code></li> Why it matters: uwsm</code> (Universal Wayland Session Manager) wraps the execution of Wayland compositors into dedicated systemd scope units. This solves longstanding race conditions where desktop portals, audio servers, and authentication agents fail to start because they cannot locate the active display server socket or D-Bus session variables.</li> </ul> 🔗</a>XDG Desktop Portal</h2> Standardised D-Bus interfaces enabling sandboxed applications and native Wayland programs to access desktop integration features safely. Portals handle screen sharing, file selection dialogs, camera access, and URI opening. A standard deployment requires a desktop-specific portal alongside a GUI toolkit fallback. Examples: xdg-desktop-portal-gnome</code>, xdg-desktop-portal-gtk</code>, xdg-desktop-portal-wlr</code>, xdg-desktop-portal-hyprland</code></li> Why it matters: Without the correct desktop portals running, web browsers cannot capture your screen during video calls, applications cannot spawn native file saving dialogs, and Flatpak software remains completely isolated from system services. You typically install the portal matching your compositor ecosystem alongside xdg-desktop-portal-gtk</code> as a universal fallback for GTK-based applications.</li> </ul> 🔗</a>XWayland</h2> An X11 server running as a Wayland client. It provides backwards compatibility for legacy applications that lack native Wayland support, allowing them to render inside your compositor. Examples: xwayland</code>, xorg-xwayland</code></li> Why it matters: While most modern Linux software is Wayland-native, older proprietary binaries, specific video games, and legacy development tools still rely on the X11 rendering protocol. xwayland</code> translates those X11 drawing commands into Wayland surfaces seamlessly, preventing application crashes and rendering failures.</li> </ul> 🔗</a>GPU Drivers</h2> User-space graphics drivers and graphics API implementations (OpenGL and Vulkan) that allow applications to utilise hardware rendering. Without these libraries, the system falls back to software rendering, resulting in high CPU usage and severe visual latency. Examples: mesa</code>, vulkan-intel</code>, intel-media-driver</code>, vulkan-radeon</code>, nvidia</code>, nvidia-utils</code></li> Why it matters: mesa</code> provides the open-source OpenGL and Vulkan implementations for AMD and Intel graphics hardware. For Intel integrated GPUs, vulkan-intel</code> delivers low-level Vulkan API access. Without these user-space drivers installed, your window compositor will struggle to composite windows smoothly, and graphical applications will render at a crawl.</li> </ul> 🔗</a>Video Acceleration</h2> Hardware-accelerated video encoding and decoding libraries. Offloading video decoding to the integrated or discrete graphics unit reduces CPU thermal load and significantly extends laptop battery autonomy. Examples: intel-media-driver</code>, libva-mesa-driver</code>, libva-utils</code></li> Why it matters: When streaming video or playing high-resolution media files, hardware acceleration routes the decoding workload directly to dedicated ASIC chips on the GPU. intel-media-driver</code> provides VA-API support for modern Intel integrated graphics (Broadwell and newer). libva-utils</code> includes the vainfo</code> command-line diagnostic tool, used to verify that the system correctly recognises your video decoding hardware.</li> </ul> 🔗</a>Display Configuration Utilities</h2> Tools for managing display resolutions, monitor positioning, refresh rates, and scaling factors. While compositors manage outputs natively via their config files, utility software aids in debugging complex multi-monitor layouts or automating profile switching. Examples: wdisplays</code>, kanshi</code>, nwg-displays</code></li> Why it matters: wdisplays</code> provides a graphical interface similar to standard display settings panels, allowing you to drag and arrange display outputs visually. kanshi</code> is a background daemon that monitors connected display outputs and automatically applies pre-configured monitor profiles when you dock or undock a laptop from external monitors.</li> </ul> 🔗</a>3. Desktop Environment Components</h1> Standalone window managers and compositors require you to assemble the functional desktop environment independently by linking modular utilities together. 🔗</a>Status Bar (Panel)</h2> A persistent visual interface displaying system diagnostics, active workspaces, clock telemetry, battery percentages, and network state. Wayland bars communicate directly with the compositor via IPC protocols. Examples: waybar</code>, eww</code>, yambar</code>, ironbar</code></li> Why it matters: waybar</code> is the standard, highly configurable Wayland panel styled using CSS and JSON. It integrates natively with custom modules and scripts. eww</code> (Elkowars Wacky Widgets) allows you to construct complex, custom widget layouts using an XML-like configuration syntax. yambar</code> offers a minimalistic, lightweight alternative configured via simple YAML files.</li> </ul> 🔗</a>Application Launcher</h2> A dynamic, keyboard-driven menu system used to execute binaries, search local directories, or switch between active window states. Without one, you either open a terminal for every command or bind every application to a rigid keyboard shortcut. Examples: fuzzel</code>, wofi</code>, tofi</code>, rofi-wayland</code></li> Why it matters: fuzzel</code> is an extremely fast, lightweight Wayland-native launcher designed specifically for keyboard efficiency and low resource usage. rofi-wayland</code> is a Wayland-ported fork of the classic rofi</code> utility, offering extensive theming capabilities, custom script modes, and clipboard history browsing integration.</li> </ul> 🔗</a>Notification Daemon</h2> A background service that receives, formats, and displays visual notifications sent by desktop applications over D-Bus. Without a notification daemon, desktop alerts are silently dropped by the system. Examples: mako</code>, swaync</code>, dunst</code></li> Why it matters: mako</code> is a lightweight, Wayland-native notification daemon designed to render clean popups on lightweight compositors. swaync</code> (Sway Notification Center) replaces simple popups with a full GTK-based notification drawer, providing action buttons, do-not-disturb toggles, and widget support.</li> </ul> 🔗</a>Screen Lock</h2> Security software that intercepts user input and renders an authentication prompt over the display outputs when the workstation is left unattended. The lock screen sits between your unattended machine and anyone who walks up to it. Examples: swaylock</code>, swaylock-effects</code>, waylock</code>, hyprlock</code></li> Why it matters: swaylock</code> is the standard Wayland screen locking utility, binding directly to Wayland secure input protocols to prevent unauthorized session access. swaylock-effects</code> extends the base package by adding visual features such as real-time desktop blurring, clock rendering, and custom screenshots.</li> </ul> 🔗</a>Idle Daemon</h2> A background monitoring service that executes scheduled commands after defined periods of user inactivity, such as dimming displays, triggering the screen locker, or suspending hardware. Examples: swayidle</code>, hypridle</code></li> Why it matters: swayidle</code> listens to Wayland input events and executes shell commands when timers expire. It is typically configured to lock the screen after five minutes of inactivity, power down display monitors after ten minutes, and suspend the workstation after thirty minutes, protecting both machine security and battery life.</li> </ul> 🔗</a>Wallpaper Setter</h2> Wayland-native background utilities designed to render static images or solid colours onto the root desktop surface. X11 wallpaper utilities will not function inside a Wayland environment. Examples: swaybg</code>, swww</code>, mpvpaper</code></li> Why it matters: swaybg</code> is a lightweight, efficient utility that scales and renders background images with negligible system overhead. swww</code> offers dynamic, animated wallpaper transitions using custom shaders. mpvpaper</code> allows you to set running video files as your live background by rendering the output of the mpv</code> media player directly onto the desktop surface.</li> </ul> 🔗</a>Polkit Authentication Agent</h2> An interactive graphical prompt triggered when an unprivileged user process requests elevated system permissions (such as mounting internal drives or modifying network profiles). Without one, GUI privilege escalation requests fail silently. Examples: polkit-gnome</code>, polkit-kde-agent</code>, hyprpolkitagent</code>, lxqt-policykit</code></li> Why it matters: Polkit acts as the system-wide authorization manager. When a standard desktop application needs to perform an administrative task without invoking sudo</code> in a terminal, it calls Polkit. The authentication agent catches this request and presents a password dialog window, allowing secure privilege escalation.</li> </ul> 🔗</a>Keyring (Secret Storage)</h2> An encrypted local credential store implementing the Freedesktop Secret Service API. Web browsers, email clients, and development tools rely on this daemon to store authentication tokens securely without writing plaintext files to disk. Examples: gnome-keyring</code>, keepassxc</code>, seahorse</code>, libsecret</code></li> Why it matters: If your system lacks an active secret service daemon, applications like Firefox, Thunderbird, and Git credential helpers will repeatedly prompt for passwords on every launch, or fail to save OAuth tokens entirely. gnome-keyring</code> runs silently in the background, unlocking automatically when you log into your system session. keepassxc</code> can also act as the system secret service, routing all authentication storage directly into your primary password database.</li> </ul> 🔗</a>Clipboard Manager</h2> Wayland buffers clear clipboard contents immediately upon closing the source application. A clipboard manager daemonizes running copy events, preserving history in memory and providing search access to previously copied text or images. Examples: cliphist</code>, clipman</code>, wl-clipboard</code></li> Why it matters: wl-clipboard</code> provides the underlying command-line tools (wl-copy</code> and wl-paste</code>) required to interact with the Wayland clipboard from shell scripts and terminal applications. cliphist</code> works alongside wl-clipboard</code> by recording every copied text string or image surface into a local database, which you can subsequently query and paste using application launchers like rofi</code> or fuzzel</code>.</li> </ul> 🔗</a>Screenshot Utilities</h2> Software leveraging Wayland screencopy protocols to capture full screen outputs, specific windows, or defined graphical coordinates. Examples: grim</code>, slurp</code>, swappy</code>, hyprshot</code></li> Why it matters: Traditional X11 screenshot tools cannot grab Wayland surfaces due to strict graphical protocol sandboxing. grim</code> (Grab Images) communicates directly with the compositor to capture visual buffers. It is almost always paired with slurp</code>, an interactive command-line utility that lets you click and drag a selection rectangle across the screen to feed precise coordinates back into grim</code>. swappy</code> acts as a post-capture annotation tool, popping up automatically to let you draw arrows, highlight text, and crop screenshots before saving or copying them.</li> </ul> 🔗</a>Screen Recorder</h2> Video capture software utilising Wayland desktop portals or direct protocol access to record desktop activity to media files. Examples: wf-recorder</code>, gpu-screen-recorder</code>, obs-studio</code></li> Why it matters: wf-recorder</code> is a command-line utility that captures video feeds from Wayland compositors using the wlr-screencopy</code> protocol, encoding streams directly via FFmpeg. gpu-screen-recorder</code> leverages hardware-accelerated NVENC, VA-API, or QuickSync encoding paths to record screen output with almost zero impact on system CPU resources.</li> </ul> 🔗</a>Colour Picker</h2> A lightweight utility that samples pixel colour values from the display output and formats them as hexadecimal or RGB strings for theming workflows. Examples: hyprpicker</code>, wl-color-picker</code>, gpick</code></li> Why it matters: When modifying window manager border colours, terminal colour palettes, or web CSS files, a Wayland-native colour picker allows you to freeze the screen cursor and extract precise hex codes from any visible pixel on your monitors.</li> </ul> 🔗</a>On-Screen Display (OSD)</h2> Visual overlay indicators triggered during hardware state modifications, such as adjusting audio volume, muting microphones, or changing backlight levels. Examples: swayosd</code>, avizo</code>, libnotify</code> scripts via notify-send</code></li> Why it matters: When pressing keyboard media keys to adjust system speaker volume or monitor brightness, an OSD provides immediate visual confirmation of the new hardware state. Without this visual feedback, you are adjusting system levels completely blind.</li> </ul> 🔗</a>4. Audio</h1> 🔗</a>Audio Server</h2> The low-level audio processing engine bridging application hardware requests with the Linux kernel sound subsystem (ALSA). PipeWire handles dynamic audio routing, Bluetooth sink management, and low-latency professional audio processing while providing full backwards compatibility for PulseAudio and JACK applications. Examples: pipewire</code>, pipewire-pulse</code>, pipewire-alsa</code>, pipewire-jack</code>, wireplumber</code></li> Why it matters: PipeWire has completely replaced legacy PulseAudio on modern Linux systems. It unifies consumer audio playback with professional, low-latency audio production. wireplumber</code> acts as the mandatory session and policy manager for PipeWire, handling device connection rules, volume persistence, and audio routing profiles. Installing pipewire-pulse</code> and pipewire-alsa</code> ensures legacy software seamlessly outputs audio without modification.</li> </ul> 🔗</a>Volume Control (Mixer)</h2> Graphical or terminal interfaces for routing application audio streams, selecting input hardware, and adjusting channel gain levels. Examples: pavucontrol</code> (GUI), pulsemixer</code> (TUI), pamixer</code> (CLI), wpctl</code></li> Why it matters: While the audio server runs invisibly in the background, mixer utilities provide the controls required to mute specific application tabs, switch audio output from internal laptop speakers to Bluetooth headphones, and boost microphone input levels. pavucontrol</code> is the gold-standard graphical mixer, while pulsemixer</code> provides an efficient, ncurses-based interface for terminal-first workflows. wpctl</code> is the native command-line tool for WirePlumber, perfect for binding volume adjustments to keyboard media keys.</li> </ul> 🔗</a>5. Networking</h1> 🔗</a>Network Manager</h2> System daemons managing network interfaces, wireless authentication, DHCP leases, and routing tables. Examples: networkmanager</code>, iwd</code>, connman</code></li> Why it matters: networkmanager</code> is the robust, industry-standard daemon that handles wired ethernet, complex Wi-Fi authentication (WPA2/WPA3, 802.1x), and network bridging automatically. iwd</code> (iNet Wireless Daemon) is a modern, lightweight wireless daemon developed by Intel that can operate as a standalone Wi-Fi backend for NetworkManager, replacing legacy wpa_supplicant</code> with significantly faster scanning and connection speeds.</li> </ul> 🔗</a>Network Manager Frontend</h2> User-space applications providing interfaces to manage Wi-Fi connections and stored network profiles without manual command-line configuration. Examples: nm-applet</code>, nmtui</code>, networkmanager-dmenu</code></li> Why it matters: While NetworkManager runs as a system daemon, frontends provide ergonomic ways to interact with it. nmtui</code> provides an intuitive text-user interface inside the terminal for selecting Wi-Fi networks and editing static IP tables. nm-applet</code> sits in your Wayland status bar tray, offering quick graphical access to network toggles.</li> </ul> 🔗</a>DNS Resolver</h2> Services managing domain name translation. Configuring local caching resolvers or encrypted protocols (DNS-over-HTTPS or DNS-over-TLS) prevents ISP DNS tampering and query interception. Examples: systemd-resolved</code>, dnscrypt-proxy</code>, stubby</code></li> Why it matters: By default, standard DNS queries are transmitted in plain text, allowing network eavesdroppers or internet service providers to log your browsing destinations. systemd-resolved</code> provides local DNS caching and native DNS-over-TLS validation out of the box. dnscrypt-proxy</code> routes all system domain lookups through encrypted DNSCrypt or DoH relays, ensuring complete query privacy.</li> </ul> 🔗</a>VPN Client</h2> Software creating encrypted network tunnels to remote infrastructure or privacy providers. Examples: wireguard-tools</code>, openvpn</code>, networkmanager-openvpn</code></li> Why it matters: wireguard-tools</code> provides the userspace utilities (wg</code>, wg-quick</code>) required to configure WireGuard, a modern, extremely fast kernel-space VPN protocol utilizing state-of-the-art cryptography. openvpn</code> remains necessary for connecting to legacy corporate networks and traditional commercial VPN providers.</li> </ul> 🔗</a>Firewall</h2> Packet filtering interfaces regulating incoming and outgoing network traffic at the kernel level. Examples: ufw</code>, nftables</code>, iptables-nft</code>, gufw</code></li> Why it matters: The Linux kernel includes nftables</code> as its modern packet filtering framework. Directly editing raw nftables</code> rules can be complex; ufw</code> (Uncomplicated Firewall) provides a simplified command-line interface for establishing default-deny incoming policies and opening specific network ports safely.</li> </ul> 🔗</a>Remote Access Daemons</h2> Secure Shell server and client utilities for remote command execution and encrypted file transfer. Examples: openssh</code></li> Why it matters: openssh</code> provides the ssh</code> client tool required to access remote servers, git repositories, and headless hardware. Enabling the included sshd</code> daemon allows secure remote administration of your local machine over encrypted network sockets.</li> </ul> 🔗</a>Anonymity Networks</h2> Software routing TCP traffic through distributed network relays to obfuscate origin IP addresses. Examples: tor</code>, torsocks</code></li> Why it matters: The tor</code> daemon establishes multi-hop onion routing circuits across globally distributed volunteer nodes. The torsocks</code> utility wraps standard command-line applications (curl</code>, ssh</code>, git</code>), forcing their TCP connections transparently through the Tor proxy network to prevent IP address leaks.</li> </ul> 🔗</a>Network Diagnostics</h2> Utilities used to inspect routing paths, test port reachability, query DNS servers, and measure link throughput. Examples: nmap</code>, traceroute</code>, iperf3</code>, bind</code>, openbsd-netcat</code>, tcpdump</code></li> Why it matters: When networking breaks, basic ping</code> commands are rarely enough. nmap</code> scans network targets for open ports and listening services. iperf3</code> measures maximum real-world bandwidth between two network endpoints. The bind</code> package supplies dig</code> and nslookup</code>, essential CLI tools for diagnosing domain name propagation and interrogating DNS records. openbsd-netcat</code> (nc</code>) is the Swiss-Army knife of networking, capable of reading and writing arbitrary TCP and UDP data streams for socket debugging.</li> </ul> 🔗</a>6. Input & Hardware</h1> 🔗</a>Input Remapper</h2> System daemons intercepting kernel input events to reassign key codes, modify modifier behaviors, or implement custom layers across all attached keyboards and pointing devices. Examples: keyd</code>, xremap</code>, interception-tools</code></li> Why it matters: System-level input remappers operate directly on kernel /dev/input/event</code> devices, making your custom keyboard mappings universal across console TTYs, Wayland compositors, and X11 fallback applications. keyd</code> allows you to effortlessly map CapsLock to Control when held and Escape when tapped, or construct custom ergonomic navigation layers without requiring QMK hardware programmable keyboards.</li> </ul> 🔗</a>Brightness Control</h2> Command-line utilities adjusting display backlight brightness via sysfs hardware interfaces. Examples: brightnessctl</code>, light</code></li> Why it matters: Standard user accounts lack direct write permissions to /sys/class/backlight/</code> kernel controls. brightnessctl</code> safely interfaces with these hardware nodes, allowing you to bind display brightness increase and decrease commands directly to laptop function keys inside your compositor configuration.</li> </ul> 🔗</a>Fingerprint Reader</h2> Hardware drivers and PAM integration daemons enabling biometric authentication for login, screen unlocking, and privilege escalation. Examples: fprintd</code>, libfprint</code></li> Why it matters: If your hardware includes an integrated fingerprint sensor, libfprint</code> provides the necessary hardware communication drivers. The fprintd</code> daemon integrates this functionality into the Pluggable Authentication Module (PAM) architecture, allowing you to authenticate sudo</code> commands, unlock your screen locker, and log into your display manager with a finger scan.</li> </ul> 🔗</a>Power Management</h2> Automated system services optimising laptop power consumption by regulating CPU frequency scaling, PCI bus power states, and Wi-Fi radio power management. Examples: tlp</code>, tlp-rdw</code>, powertop</code>, auto-cpufreq</code>, power-profiles-daemon</code></li> Why it matters: Out of the box, Linux kernel default power settings prioritise hardware compatibility over maximum battery conservation. tlp</code> operates as an automated background daemon that dynamically tunes USB autosuspend rules, PCIe Active State Power Management (ASPM), and processor scaling governors based on whether the machine is connected to AC power or running on battery. powertop</code> is an interactive diagnostic tool by Intel that breaks down real-time power consumption by process and hardware bus.</li> </ul> 🔗</a>Bluetooth Stack</h2> The core hardware daemons and pairing managers required to operate Bluetooth interfaces and peripheral devices. Examples: bluez</code>, bluez-utils</code>, blueman</code>, bluetui</code></li> Why it matters: bluez</code> is the official Linux Bluetooth protocol stack daemon (bluetoothd</code>). The bluez-utils</code> package supplies bluetoothctl</code>, the interactive command-line utility used to scan, pair, trust, and connect wireless headsets, mice, and keyboards. blueman</code> provides a full graphical management panel, while bluetui</code> offers a fast terminal interface for managing wireless devices.</li> </ul> 🔗</a>Storage Diagnostics</h2> Monitoring utilities querying drive firmware for S.M.A.R.T. telemetry to identify failing NVMe or SATA storage blocks before catastrophic data loss occurs. Examples: smartmontools</code>, nvme-cli</code></li> Why it matters: Solid-state drives and mechanical disks track internal wear leveling, reallocation event counts, and temperature logs within their onboard controllers. The smartmontools</code> package provides smartctl</code>, which queries this Self-Monitoring, Analysis, and Reporting Technology data, allowing you to identify hardware degradation and replace storage media before read/write failures occur. For NVMe storage arrays, nvme-cli</code> communicates directly with controller registers to format drives, update controller firmware, and inspect health logs.</li> </ul> 🔗</a>7. Theming & Appearance</h1> 🔗</a>Fonts</h2> A complete typographic stack requires distinct categories to handle code rendering, UI layouts, document reading, and iconography correctly. Monospace (Nerd Font patched): ttf-jetbrains-mono-nerd</code>, ttf-firacode-nerd</code>, ttf-hack-nerd</code></li> Sans-Serif (Interface): inter-font</code>, noto-fonts</code>, ttf-ubuntu-font-family</code></li> Serif (Documents): adobe-source-serif-fonts</code>, noto-serif</code></li> Emoji: noto-fonts-emoji</code>, ttf-twemoji</code></li> Font Management: font-manager</code>, fontconfig</code></li> Why it matters: Terminal emulators and text editors require fixed-width Monospace fonts. Patching these fonts with "Nerd Font" glyphs embeds thousands of custom icons into the typography, ensuring status bars (waybar</code>), directory listings (eza</code>), and shell prompts (starship</code>) render visual icons correctly rather than broken rectangle characters. Sans-Serif fonts govern graphical application interfaces and web rendering, while Serif fonts provide optimal readability for long-form PDF document viewing and word processing. Installing noto-fonts-emoji</code> prevents web browsers and messaging clients from rendering missing emoji glyphs as empty boxes.</li> </ul> 🔗</a>Icon Theme</h2> Vector and raster icon packs utilised by graphical applications for file types, directory markers, and interface buttons. Always include the fallback theme to prevent missing icon rendering errors. Examples: papirus-icon-theme</code>, hicolor-icon-theme</code></li> Why it matters: Graphical file managers and application launchers rely on standardised icon naming specifications to render directory folders, file type badges, and system action buttons. papirus-icon-theme</code> is a comprehensive, modern SVG icon suite. hicolor-icon-theme</code> must always be installed; it acts as the freedesktop.org mandatory fallback icon theme. If an application requests an icon missing from your primary theme, the system gracefully falls back to hicolor</code> instead of displaying a broken graphical artifact.</li> </ul> 🔗</a>Cursor Theme</h2> Graphical pointer assets used by the Wayland display server. Examples: bibata-cursor-theme</code>, capitaine-cursors</code>, xcursor-themes</code></li> Why it matters: By default, bare window manager environments fall back to rudimentary, unstyled cursor pointers that change size and shape unpredictably when moving across different application window surfaces. Installing a unified cursor theme like bibata-cursor-theme</code> and defining it explicitly in your environment variables ensures consistent pointer rendering across all Wayland and XWayland windows.</li> </ul> 🔗</a>GTK Theming & Settings</h2> Configuration utilities and stylesheets controlling the visual rendering of GTK2, GTK3, and GTK4 applications. Examples: nwg-look</code>, adwaita-dark</code>, catppuccin-gtk-theme</code></li> Why it matters: Applications built using GNOME's GTK toolkit (such as Firefox, Thunderbird, and Thunar) require explicit theming instructions to avoid clashing visually with dark terminal aesthetics. nwg-look</code> is a Wayland-native GTK configuration utility that allows you to apply unified themes, custom icons, and cursor sets across your desktop without manually editing underlying ~/.config/gtk-3.0/settings.ini</code> files.</li> </ul> 🔗</a>Qt Theming</h2> Integration layers mapping Qt application rendering engines to match GTK desktop colour schemes and widget styling. Examples: qt5ct</code>, qt6ct</code>, kvantum</code>, qt5-wayland</code>, qt6-wayland</code></li> Why it matters: Applications developed with the Qt toolkit (such as qBittorrent, VLC, and KeePassXC) render using completely different design engines from GTK software. Without configuration, Qt applications display with glaring, unstyled Windows-95-era grey widgets. qt5ct</code> and qt6ct</code> act as environment controllers, forcing Qt applications to inherit unified colour palettes. kvantum</code> is an SVG-based theme engine that allows Qt applications to perfectly mimic modern GTK desktop themes. Installing qt5-wayland</code> and qt6-wayland</code> ensures these applications run natively on Wayland without falling back to blurry XWayland rendering.</li> </ul> 🔗</a>8. Shell & Terminal</h1> 🔗</a>Terminal Emulator</h2> The graphical window container hosting command-line interfaces. GPU-accelerated terminals offload text rendering grids to the graphics card for improved display latency. Examples: kitty</code>, foot</code>, alacritty</code>, wezterm</code>, ghostty</code></li> Why it matters: In a terminal-centric workflow, the terminal emulator is your primary interface. foot</code> is an exceptionally lightweight, minimalist Wayland-native terminal designed for speed and minimal memory consumption, featuring a client-server architecture. kitty</code> is a feature-rich, GPU-accelerated terminal supporting advanced image rendering protocols, ligatures, and scripting layouts. alacritty</code> focuses purely on OpenGL-accelerated rendering performance and stability without bundling graphical configuration tabs or scrollback manipulation features.</li> </ul> 🔗</a>Command Shell</h2> The primary command interpreter. While Bash is the default POSIX shell on Arch Linux, Zsh and Fish provide advanced interactive tab-completion and scripting ecosystems. Examples: bash</code>, zsh</code>, fish</code></li> Why it matters: The shell interprets your commands and executes scripts. bash</code> is ubiquitous and essential for POSIX compliance. zsh</code> provides an extensible interactive command-line experience, supporting advanced globbing, spelling correction, and massive community plugin frameworks (like syntax highlighting and autosuggestions). fish</code> (Friendly Interactive Shell) delivers out-of-the-box syntax highlighting, intelligent auto-suggestions based on command history, and web-based configuration without requiring complex setup scripts, though its scripting syntax deviates from standard POSIX bash.</li> </ul> 🔗</a>Shell Prompt</h2> Dynamic prompt engines displaying git repository status, execution time, python virtual environments, and working directories within the terminal line. Examples: starship</code>, oh-my-posh</code></li> Why it matters: A standard shell prompt displays minimal information. starship</code> is a cross-shell, Rust-powered prompt engine that evaluates your current directory context instantaneously. When you enter a code directory, it automatically renders active git branch states, modification flags, runtime versions (such as Node, Python, or Rust), and background job statuses directly into your prompt line with zero perceived latency.</li> </ul> 🔗</a>Terminal Multiplexer</h2> Software managing multiple persistent virtual console sessions within a single terminal window. Multiplexers preserve session state across SSH disconnects and X11/Wayland restarts. Examples: tmux</code>, zellij</code>, screen</code></li> Why it matters: Terminal multiplexers allow you to split a single terminal window into multiple panes, run background compilation jobs, and detach from active sessions without terminating running processes. tmux</code> is the industry-standard multiplexer, controllable entirely via keyboard shortcuts and highly scriptable. If your SSH connection drops while upgrading a remote server inside a tmux</code> session, the upgrade process continues safely in the background; you simply reconnect and re-attach to the session. zellij</code> is a modern, user-friendly Rust alternative featuring built-in layout tabs and floating windows out of the box.</li> </ul> 🔗</a>Pager</h2> Terminal utilities designed to scroll and navigate large text documents or standard output streams cleanly. Examples: less</code>, bat</code></li> Why it matters: When viewing long files, compiler logs, or man</code> pages, pagers control the vertical scrolling of text. less</code> is the standard UNIX pagination utility. bat</code> acts as a modern, supercharged replacement for both cat</code> and less</code>, integrating transparent syntax highlighting for hundreds of programming languages, git diff gutter markers, and automated line numbering directly into the terminal paging output.</li> </ul> 🔗</a>AUR Helper</h2> Wrapper scripts automating package compilation and dependency resolution from the Arch User Repository while handling official Pacman system updates seamlessly. Examples: paru</code>, yay</code></li> Why it matters: The Arch User Repository contains tens of thousands of user-submitted PKGBUILD scripts for software not found in official Arch repositories. Manually downloading, inspecting, compiling, and updating these packages via makepkg</code> is tedious. paru</code> (written in Rust) and yay</code> (written in Go) wrap the native pacman</code> command syntax, automatically resolving complex AUR dependency chains, displaying diffs of user build scripts for security inspection, and compiling packages cleanly into your system.</li> </ul> 🔗</a>9. Text Editors</h1> Different editing environments serve distinct functions across administration, scripting, and software development workflows. 🔗</a>Simple Terminal Editor</h2> Non-modal text editors that operate with standard keyboard navigation and immediate visual feedback. Highly practical for quick system configuration modifications, editing sudoers files, or modifying remote configurations over SSH. Examples: nano</code>, micro</code></li> Why it matters: When you are modifying a system configuration file at 3:00 AM or rescuing a broken bootloader from a chroot console, you do not want to wrestle with modal keybindings. nano</code> ships universally and provides straightforward, on-screen key prompts. micro</code> is a modern terminal editor that supports standard Ctrl+C / Ctrl+V clipboard operations, multi-cursor editing, and full mouse support inside the console without requiring manual configuration.</li> </ul> 🔗</a>Modal Terminal Editor</h2> Editors structured around distinct operational modes (Normal, Insert, Visual, and Command). By divorcing navigation from text insertion, every keyboard key functions as an editing operator. While the initial learning curve is steep, modal editors provide unmatched speed and text manipulation precision. Neovim extends traditional Vim architecture by integrating a Lua runtime for deep customisation and asynchronous plugin execution. Examples: neovim</code>, vim</code></li> Why it matters: In normal mode, your keyboard stops being a typewriter and becomes a command language for text manipulation. You do not reach for a mouse to select and delete words; you type structural commands like ciw</code> (change inside word) or dap</code> (delete around paragraph). vim</code> is installed on virtually every Unix server in existence. neovim</code> modernises this legacy by adding built-in Language Server Protocol (LSP) client support, asynchronous job execution, and an active ecosystem of Lua plugins, transforming a lightweight terminal editor into a complete, lightning-fast development environment.</li> </ul> 🔗</a>Integrated Development Environment (IDE)</h2> Comprehensive software suites bundling editors with visual debuggers, project file trees, database explorers, and build system integrations out of the box. Examples: code</code> / vscodium</code>, intellij-idea-community</code>, pycharm-community</code></li> Why it matters: While terminal modal editors excel at speed and system efficiency, large-scale enterprise software development often benefits from dedicated graphical IDEs. vscodium</code> provides the complete Visual Studio Code editor experience compiled directly from open-source repositories, completely stripping out Microsoft proprietary telemetry and tracking code. JetBrains community editions (intellij-idea-community</code>, pycharm-community</code>) offer deep, semantic code introspection, automated refactoring suites, and integrated visual debugging tools for complex Java, Kotlin, and Python codebases.</li> </ul> 🔗</a>10. Development & Version Control</h1> 🔗</a>Version Control System</h2> Software tracking file system modifications over time, facilitating collaborative development and configuration management (dotfiles). Examples: git</code></li> Why it matters: git</code> is the foundational infrastructure of modern software engineering. It tracks line-by-line code modifications, enables non-linear branch development, and allows safe experimentation without risking production stability. Beyond coding, git</code> is essential for managing personal system configurations (dotfiles</code>), allowing you to replicate your exact Wayland, Neovim, and shell setups across multiple machines instantaneously.</li> </ul> 🔗</a>Git Frontend (TUI)</h2> Interactive terminal interfaces simplifying branch navigation, staging diffs, and commit history inspection without executing verbose CLI commands. Examples: lazygit</code>, gitui</code></li> Why it matters: Performing complex git operations—such as interactive rebasing, staging individual lines of a modified file (patch staging), or untangling merge conflicts—can be tedious via raw command-line syntax. lazygit</code> and gitui</code> (written in Rust for speed) provide visual, keyboard-driven terminal interfaces that display visual branch trees, interactive diff panels, and simplified commit management directly within your terminal workspace.</li> </ul> 🔗</a>Diff & Merge Utilities</h2> Visual comparison tools highlighting file differences and resolving git merge conflicts. Examples: meld</code> (GUI), vimdiff</code> (terminal), delta</code></li> Why it matters: When two development branches modify the same lines of code, git generates a merge conflict. meld</code> provides a clean graphical three-way visual diff interface, allowing you to click and merge code blocks across conflicting files. In the terminal, vimdiff</code> leverages Neovim's split-window architecture to resolve conflicts. delta</code> replaces standard git diff terminal output with syntax-highlighted, side-by-side or inline code comparisons featuring word-level diff highlighting.</li> </ul> 🔗</a>Runtime Version Manager</h2> Tools automating the simultaneous installation and switching of multiple programming language runtimes across different project directories. Examples: mise</code>, pyenv</code>, nvm</code>, rustup</code></li> Why it matters: Relying solely on system-wide package manager runtimes for development is dangerous; Arch Linux rolling upgrades will update Python or Node to newer versions, potentially breaking older project dependencies. mise</code> (formerly rtx) acts as a high-performance, polyglot toolchain manager written in Rust. It automatically downloads and isolates specific versions of Node, Python, Ruby, or Terraform on a per-project basis, switching runtime environments instantly as you cd</code> into different project directories. rustup</code> is the official toolchain installer required to manage Rust stable, nightly, and cross-compilation targets.</li> </ul> 🔗</a>Language Runtimes & Toolchains</h2> The core compilers, interpreters, and package managers required to build and execute software. Examples: python</code>, python-pip</code>, nodejs</code>, npm</code>, rust</code>, gcc</code>, clang</code>, make</code>, cmake</code></li> Why it matters: These packages provide the foundational compilation and execution engines for software development. gcc</code> and clang</code> compile C and C++ source code into native machine binaries. make</code> and cmake</code> orchestrate complex multi-file compilation workflows. python</code> and nodejs</code> provide the scripting interpreters and package registries (pip</code>, npm</code>) required to execute modern web applications, backend services, and automated system utilities.</li> </ul> 🔗</a>Language Server Protocol (LSP) Servers</h2> Background analysis engines providing live syntax diagnostics, autocompletion, code formatting, and definition lookup to editors supporting the LSP specification. Examples: Managed via mason.nvim</code> in Neovim, or installed natively via Pacman (pyright</code>, rust-analyzer</code>, bash-language-server</code>, lua-language-server</code>)</li> Why it matters: The Language Server Protocol standardises how text editors communicate with programming language intelligence tools. Instead of every editor embedding its own custom code parser, a standalone background server processes your codebase. When integrated into Neovim, rust-analyzer</code> or pyright</code> inspects your code in real time, underlining syntax errors, providing intelligent method autocompletion, and enabling instant jump-to-definition across thousands of project files.</li> </ul> 🔗</a>API Testing Tools</h2> Command-line utilities and interfaces designed to construct HTTP requests and inspect REST or GraphQL API responses. Examples: curl</code>, httpie</code>, xh</code>, bruno</code></li> Why it matters: Developing and debugging backend network services requires tools to simulate client requests. While curl</code> is universally available, its syntax for sending complex JSON payloads or custom authentication headers is verbose. httpie</code> and xh</code> (a high-performance Rust port) provide human-readable command-line syntax, automated JSON formatting, and persistent session support. bruno</code> offers a fast, local-first graphical desktop API client that saves request collections directly as plain text files within your git repositories.</li> </ul> 🔗</a>Database Clients</h2> Interfaces used to connect to relational or document databases for query execution and schema inspection. Examples: dbeaver</code>, pgcli</code>, mycli</code>, sqlite3</code></li> Why it matters: When interacting with PostgreSQL, MySQL, or SQLite databases, you need structured interfaces to execute SQL queries and inspect table data. pgcli</code> and mycli</code> replace standard database command-line monitors with intelligent interactive terminals featuring auto-completion and syntax highlighting. dbeaver</code> provides an enterprise-grade graphical universal database tool capable of generating visual Entity-Relationship diagrams and managing complex data migrations across virtually any database engine.</li> </ul> 🔗</a>Container Runtime</h2> Software executing isolated Linux applications and development environments via kernel namespaces and cgroups. Examples: podman</code>, docker</code>, buildah</code>, incus</code></li> Why it matters: Containers package applications and their dependencies into standardized, isolated execution environments that run identically across any Linux host. docker</code> is the ubiquitous industry standard, relying on a background root daemon to manage containers. podman</code> provides a modern, daemonless, drop-in replacement for Docker that executes containers rootlessly under standard user accounts, significantly improving system security. incus</code> (the community fork of LXD) manages complete system containers and virtual machines, behaving like lightweight, instant-boot Linux servers running inside your primary machine.</li> </ul> 🔗</a>Virtualisation</h2> Hypervisor tools executing complete virtual machines with dedicated OS kernels. Examples: qemu-full</code>, virt-manager</code>, libvirt</code></li> Why it matters: While containers isolate application processes, virtualization hypervisors emulate complete physical computer hardware, allowing you to run entirely different operating systems (such as Windows 11, BSD, or isolated Linux distributions) simultaneously. qemu-full</code> provides the hardware emulation backend and KVM (Kernel-based Virtual Machine) acceleration. libvirt</code> manages virtual network bridges and storage pools, while virt-manager</code> provides an intuitive graphical interface for creating, configuring, and viewing virtual machine displays.</li> </ul> 🔗</a>Low-Level Debugging Utilities</h2> Diagnostic software tracing process system calls, memory allocations, and binary contents. Examples: strace</code>, ltrace</code>, gdb</code>, valgrind</code>, hexyl</code>, xxd</code></li> Why it matters: When an application crashes silently or fails to read a configuration file without generating an error log, low-level debuggers reveal exactly what the software is doing under the hood. strace</code> intercepts and records every system call a running process makes to the Linux kernel, instantly revealing if a program is crashing because it is attempting to open a missing file path or requesting denied network permissions. gdb</code> (GNU Debugger) allows you to step through compiled C/C++ binary execution line-by-line to isolate memory segmentation faults. hexyl</code> provides a clean, colour-coded terminal hex viewer for inspecting binary data layouts.</li> </ul> 🔗</a>11. File Management</h1> 🔗</a>File Manager</h2> Software for browsing directories, executing file operations, and managing storage permissions. Terminal interfaces provide rapid keyboard-driven navigation, while GUI managers offer drag-and-drop convenience and thumbnail rendering. Examples: yazi</code>, lf</code>, nnn</code> (TUI); thunar</code>, pcmanfm-qt</code> (GUI)</li> Why it matters: Terminal file managers integrate natively with your command-line workspace. yazi</code> is an asynchronous, Rust-powered terminal file manager featuring instant directory jumping, multi-threading, and native image preview rendering directly inside terminal grids via Wayland image protocols. lf</code> (List Files) offers an extremely minimalist, instant-launch file manager styled after standard Vim keybindings. For graphical workflows, thunar</code> provides a lightweight, reliable GTK file manager with robust external drive automounting and custom context-menu action support.</li> </ul> 🔗</a>Archive Utilities</h2> Compression and extraction libraries handling standard archive formats. Examples: 7zip</code>, unzip</code>, unrar</code>, tar</code>, zstd</code>, file-roller</code></li> Why it matters: Compressed archives are the universal distribution format for source code, datasets, and document bundles. While tar</code> and gzip</code> handle standard Unix archives, installing 7zip</code>, unzip</code>, and unrar</code> ensures you can decompress proprietary archives downloaded from external sources. zstd</code> (Zstandard) is a modern compression algorithm developed by Facebook that delivers real-time compression speeds with compression ratios matching legacy algorithms, used extensively by Arch Linux for official .pkg.tar.zst</code> system packages.</li> </ul> 🔗</a>Thumbnail Generator</h2> Background parsers generating visual previews for images, PDF documents, and video files inside graphical file managers. Examples: ffmpegthumbnailer</code>, tumbler</code></li> Why it matters: By default, graphical file managers like Thunar display generic, identical icons for all video files and images. Installing tumbler</code> alongside ffmpegthumbnailer</code> enables background thumbnail generation, automatically parsing video frames and document covers to render visual previews directly inside your file browsing directories.</li> </ul> 🔗</a>Disk Usage Analyser</h2> Diagnostic tools mapping file system consumption to locate storage anomalies and large cached directories. Examples: dust</code>, ncdu</code>, duf</code></li> Why it matters: When your NVMe storage fills up unexpectedly, traditional du</code> commands spit out unreadable, unindexed lists of numbers. ncdu</code> (NCurses Disk Usage) scans storage directories and renders an interactive, sorted terminal interface where you can navigate folders and delete space-wasting caches instantly. dust</code> is a modern Rust-powered alternative that renders visual graphical tree maps of storage consumption directly in the console. duf</code> replaces the legacy df</code> command, displaying clean, tabulated visual overviews of all mounted filesystems and available disk space.</li> </ul> 🔗</a>Partition & Storage Management</h2> Low-level disk partitioning and logical volume manipulation software. Examples: parted</code>, gptfdisk</code>, gparted</code>, lvm2</code></li> Why it matters: Whether setting up a new SSD, resizing logical volumes, or formatting USB flash drives, partition manipulation tools are mandatory system administration equipment. gptfdisk</code> provides gdisk</code> and cgdisk</code>, the authoritative interactive terminal tools for creating and editing modern GPT (GUID Partition Table) disk layouts. parted</code> provides scripted partition table manipulation, while gparted</code> offers a visual GTK interface for resizing filesystems without command-line calculation risks.</li> </ul> 🔗</a>Backup & Synchronisation</h2> Software performing incremental data backups, deduplication, encryption, and remote mirroring to prevent data loss. Examples: restic</code>, borgbackup</code>, rsync</code>, rclone</code>, syncthing</code></li> Why it matters: Storage hardware fails, rolling distributions break, and user error occurs. A robust backup strategy is mandatory. rsync</code> is the classic synchronization tool, perfect for local file mirroring and incremental transfers over SSH. restic</code> and borgbackup</code> represent modern backup architecture: they slice your directories into deduplicated, encrypted snapshots, storing only the modified data chunks to local hard drives or remote cloud buckets. rclone</code> acts as a command-line Swiss-Army knife for syncing data to arbitrary cloud storage providers (S3, Google Drive, Mega). syncthing</code> establishes continuous, peer-to-peer decentralized file synchronization across your laptops, servers, and mobile devices without relying on third-party cloud servers.</li> </ul> 🔗</a>Remote Desktop Client</h2> Graphical applications establishing remote desktop control sessions over VNC or RDP protocols. Examples: remmina</code>, freerdp</code>, wayvnc</code></li> Why it matters: When you need to manage remote Windows workstations or control graphical Linux desktops across a network, remmina</code> provides a comprehensive, multi-protocol graphical client supporting Remote Desktop Protocol (RDP), VNC, and SSH tunneling. Conversely, wayvnc</code> acts as a Wayland-native VNC server, allowing you to share and control your local Niri compositor session remotely from other devices.</li> </ul> 🔗</a>12. System Utilities</h1> 🔗</a>System & Process Monitors</h2> Interactive system telemetry tools detailing CPU core load, memory allocation, storage I/O, network bandwidth, and active process hierarchy. Examples: btop</code>, htop</code>, bottom</code>, procs</code></li> Why it matters: When system fans spin up or memory consumption spikes, process monitors identify the rogue application immediately. While top</code> is ubiquitous, htop</code> adds interactive process killing, tree-view process hierarchies, and clean visual metric bars. btop</code> elevates this further, rendering gorgeous, highly customizable terminal dashboards displaying real-time graphs for disk read/write speeds, network transfer rates, CPU temperatures, and storage utilization. procs</code> replaces legacy ps</code> command output with syntax-highlighted, human-readable process tables featuring automated Docker container mapping.</li> </ul> 🔗</a>Command-Line Search & Filtering</h2> Modern, high-performance replacements for legacy Unix search utilities. These tools leverage multi-threading and automatically ignore version-control directories. Examples: Fuzzy Finder: fzf</code>, sk</code></li> Content Search: ripgrep</code>, silversearcher-ag</code></li> File Name Search: fd</code></li> Directory Listing: eza</code>, lsd</code></li> </ul> </li> Why it matters: Traditional Unix tools like find</code> and grep</code> are slow when searching massive directories and require complex flag syntax. Modern Rust-powered replacements dramatically accelerate terminal workflows: ripgrep</code> (rg</code>) searches file contents recursively at blistering speeds, automatically respecting .gitignore</code> rules to avoid searching irrelevant dependency folders.</li> fd</code> replaces find</code> with sensible defaults, colour-coded output, and simplified regular expression searching.</li> eza</code> replaces ls</code>, adding git status badges, file modification timestamps, human-readable file sizes, and Nerd Font file icons directly to directory listings.</li> fzf</code> (Fuzzy Finder) is a revolutionary terminal filter; when piped into bash/zsh history or file searching, it allows you to instantly filter and open files, switch branches, or execute historical commands with minimal keystrokes.</li> </ul> </li> </ul> 🔗</a>Download & Network Utilities</h2> Command-line file downloaders supporting multi-connection parallel fetching and broken download resumption. Examples: aria2</code>, wget</code>, curl</code></li> Why it matters: Downloading large Linux ISOs or software archives via web browsers is inefficient and fragile. wget</code> is the classic tool for scripted file downloading and website mirroring. aria2</code> is a lightweight, multi-protocol download utility capable of accelerating download speeds by segmenting files and pulling chunks simultaneously across multiple HTTP, FTP, and BitTorrent connections.</li> </ul> 🔗</a>Calculators & Mathematical Tools</h2> Interactive expression evaluation utilities. Examples: qalculate</code>, bc</code></li> Why it matters: When calculating storage allocations, subnet masks, or general arithmetic, opening a heavy graphical calculator application breaks terminal momentum. bc</code> is an arbitrary-precision command-line calculator language. qalculate</code> (qalc</code>) is a phenomenal utility that understands natural mathematical syntax, physical unit conversions (currency, data sizes, measurements), symbolic calculus, and base conversions directly within the terminal console.</li> </ul> 🔗</a>Security Auditing & Maintenance</h2> Tools scanning installed packages against CVE databases and identifying redundant system files. Examples: arch-audit</code>, lynis</code>, rmlint</code>, fdupes</code></li> Why it matters: Maintaining system hygiene and security on a rolling release requires vigilance. arch-audit</code> queries the official Arch Linux security tracker, cross-referencing your installed package database against known Common Vulnerabilities and Exposures (CVEs) to warn you of unpatched software. lynis</code> performs deep automated security auditing, evaluating file permissions, firewall rules, kernel parameters, and user authentication setup to suggest hardening improvements. rmlint</code> and fdupes</code> scan filesystem directories to identify and strip out duplicate files, empty directories, and broken symlinks, reclaiming wasted storage space.</li> </ul> 🔗</a>13. Applications</h1> 🔗</a>Web Browser</h2> The primary internet client. Ensure Wayland-native flags are active to maintain fluid scrolling and video playback. Examples: firefox</code>, librewolf</code>, chromium</code>, brave</code></li> Why it matters: The web browser is often the most resource-intensive application running on a workstation. firefox</code> provides an independent, highly customizable rendering engine with robust privacy controls and native Wayland support. librewolf</code> is a custom fork of Firefox compiled with aggressive privacy hardening, uBlock Origin pre-installed, and all telemetry removed out of the box. chromium</code> provides the open-source base for Blink-engine rendering, essential for web development testing and specific proprietary web applications.</li> </ul> 🔗</a>Email Client</h2> Applications managing mail synchronisation via IMAP/SMTP protocols. Examples: thunderbird</code>, neomutt</code>, aerc</code></li> Why it matters: While webmail interfaces are common, dedicated local email clients provide offline access, unified multi-account management, and PGP cryptographic signing. thunderbird</code> offers a full-featured graphical personal information manager. For terminal purists, neomutt</code> and aerc</code> provide lightning-fast, keyboard-driven email management inside console windows, integrating directly with local mail synchronizers like offlineimap</code> or mbsync</code> and rendering plain-text emails effortlessly.</li> </ul> 🔗</a>Document & eBook Readers</h2> Lightweight viewing software for PDF, ePub, and DjVu files. Examples: zathura</code> (with zathura-pdf-mupdf</code>), evince</code>, okular</code>, foliate</code></li> Why it matters: Opening technical PDF manuals or research papers inside heavy web browsers is clumsy. zathura</code> is a minimalist, document viewer controlled entirely via Vim keybindings, offering instantaneous document rendering and distraction-free reading without interface borders. Installing the zathura-pdf-mupdf</code> backend ensures rapid rendering of complex vector graphics and large documents. For reading ePub eBooks, foliate</code> provides a beautiful, modern GTK reading interface featuring customizable typography, chapter pagination, and dictionary lookup integration.</li> </ul> 🔗</a>Media Viewers & Editors</h2> Software used to display, manipulate, and play image, audio, and video formats. Examples: Image Viewers: imv</code>, swayimg</code></li> Image Editors: imagemagick</code>, gimp</code>, inkscape</code></li> Video Players: mpv</code>, vlc</code></li> Media Downloader: yt-dlp</code></li> Music Daemons & Clients: mpd</code>, ncmpcpp</code>, mpc</code></li> </ul> </li> Why it matters: imv</code> and swayimg</code> are Wayland-native, keyboard-controlled image viewers that open instantly and scale images cleanly across tiled compositor windows.</li> imagemagick</code> is a vital CLI suite for automated image manipulation—capable of converting file formats, resizing photo batches, and generating screenshot composites via shell scripts without opening a GUI. gimp</code> and inkscape</code> handle complex raster photo editing and scalable vector graphic (SVG) design respectively.</li> mpv</code> is the undisputed champion of Linux video playback: an open-source, minimalist media player powered by FFmpeg that handles any video format, supports hardware decoding acceleration, and extends functionality via Lua scripting.</li> yt-dlp</code> is an indispensable command-line tool for downloading video and audio streams from thousands of websites (including YouTube, Vimeo, and Reddit), allowing you to archive educational material or media directly to local storage.</li> mpd</code> (Music Player Daemon) decouples audio playback from user interfaces by running as a background service that catalogs and plays your local music library. You control playback using lightweight terminal clients like ncmpcpp</code> or command-line triggers (mpc</code>), meaning your music continues playing uninterrupted even if your graphical desktop session restarts.</li> </ul> </li> </ul> 🔗</a>Productivity & Organisation</h2> Software managing personal knowledge bases, local credentials, and standard office documents. Examples: Note Taking: obsidian</code>, logseq</code></li> Password Management: keepassxc</code>, bitwarden-cli</code>, pass</code></li> Office Suite: libreoffice-fresh</code></li> Spell Checking: hunspell</code>, hunspell-en_gb</code>, libenchant</code></li> </ul> </li> Why it matters: Local-first knowledge management is essential for tracking technical documentation, projects, and personal research. obsidian</code> and logseq</code> organize your notes as folders of standard Markdown files stored locally on your hard drive, utilizing bi-directional linking to construct visual knowledge graphs without locking your data into proprietary cloud formats.</li> Password security requires encrypted local credential vaults. keepassxc</code> provides an offline, open-source password manager utilizing AES-256 encryption, featuring auto-type integration and SSH agent support. pass</code> (the standard UNIX password manager) embraces the Unix philosophy by storing each individual credential as an encrypted GPG file inside a standard git folder structure.</li> libreoffice-fresh</code> provides the comprehensive open-source office suite required to create and format standard Word documents, Excel spreadsheets, and presentation slides.</li> System-wide spell checking relies on underlying linguistic libraries. Installing hunspell</code> alongside regional dictionaries (hunspell-en_gb</code> for British English) ensures LibreOffice, email clients, and web browsers underline typographical errors accurately.</li> </ul> </li> </ul> 🔗</a>Communication & Feed Readers</h2> Clients for real-time messaging, federated social networks, and syndicated content feeds. Examples: telegram-desktop</code>, element-desktop</code>, discord</code>, tut</code>, newsboat</code>, qbittorrent</code></li> Why it matters: Native desktop messaging clients like telegram-desktop</code> and element-desktop</code> (for secure, decentralized Matrix communications) provide desktop notification integration and system tray persistence.</li> For Fediverse and Mastodon interactions, tut</code> delivers a clean, ncurses-based terminal user interface, allowing you to browse timelines and post updates directly from the console.</li> newsboat</code> is an RSS/Atom feed reader designed for the terminal. By subscribing to technical blogs, software release feeds, and news sources via newsboat</code>, you consume information rapidly without algorithmic distraction, ad trackers, or bloated web interfaces.</li> qbittorrent</code> is a reliable, open-source BitTorrent client featuring built-in torrent search engines, IP filtering, and automated RSS download rules for Linux distribution releases.</li> </ul> </li> </ul> 🔗</a>System Information Fetchers</h2> Terminal utilities displaying system architecture, kernel versions, memory usage, and ASCII logos. Examples: fastfetch</code>, macchina</code></li> Why it matters: While largely aesthetic, system fetch utilities provide immediate, clean visual verification of your active operating system environment, kernel release, uptime, memory consumption, and compositor configuration. fastfetch</code> is the modern, highly performant C-based successor to the unmaintained neofetch</code>, rendering system stats alongside customized ASCII or image distribution logos instantaneously.</li> </ul> 🔗</a>14. Fonts Reference Table</h1> Type</th> Primary Purpose</th> Recommended Packages</th> Why It Matters</th></tr></thead> Monospace (Nerd Font)</td> Terminals, text editors, status bar iconography</td> ttf-jetbrains-mono-nerd</code> ttf-firacode-nerd</code> ttf-hack-nerd</code></td> Fixed-width character spacing is mandatory for coding and terminal grids. Patched Nerd Fonts embed thousands of icon glyphs used by status bars and shell prompts.</td></tr> Sans-Serif</td> GTK/Qt UI layouts, desktop notifications, web browsers</td> inter-font</code> noto-fonts</code> ttf-ubuntu-font-family</code></td> Proportional sans-serif fonts govern graphical application interfaces and general reading readability across desktop window surfaces.</td></tr> Serif</td> Document reading, PDF viewing, word processing</td> adobe-source-serif-fonts</code> noto-serif</code></td> Traditional serif fonts provide superior legibility for long-form printed documents, formal reports, and eBook reading.</td></tr> Emoji</td> Universal emoji glyph rendering across all applications</td> noto-fonts-emoji</code> ttf-twemoji</code></td> Prevents modern Unicode emoji characters from rendering as broken, empty rectangular boxes in web browsers and communication clients.</td></tr> </tbody></table> 🔗</a>15. Master System Verification Checklist</h1> Use this structured audit to verify your installation completeness after deployment. 🔗</a>Core System</h2> Base operating system packages (base</code>, base-devel</code>)</li> Linux kernel and kernel headers (linux</code>, linux-headers</code>)</li> Hardware microcode and system firmware (intel-ucode</code> / amd-ucode</code>, linux-firmware</code>)</li> Bootloader configuration (grub</code>, efibootmgr</code>)</li> Local documentation system (man-db</code>, man-pages</code>)</li> Network time synchronisation service (systemd-timesyncd</code> or chrony</code> active)</li> Cryptographic volume tools (cryptsetup</code>, lvm2</code>)</li> </ul> 🔗</a>Display & Compositor</h2> Wayland compositor (niri</code>)</li> Graphics drivers and Vulkan APIs (mesa</code>, vulkan-intel</code>, vulkan-radeon</code>)</li> Video hardware acceleration libraries (intel-media-driver</code>, libva-utils</code>)</li> Display manager or TTY autologin wrapper (ly</code>, greetd</code>, or uwsm</code>)</li> XDG desktop portals (xdg-desktop-portal-gnome</code>, xdg-desktop-portal-gtk</code>)</li> X11 compatibility layer (xwayland</code>)</li> Display management utilities (wdisplays</code>, kanshi</code>)</li> </ul> 🔗</a>Desktop Environment Components</h2> Wayland status bar (waybar</code>)</li> Application launcher (fuzzel</code>, rofi-wayland</code>)</li> Notification daemon (mako</code>, swaync</code>)</li> Screen locker and inactivity monitor (swaylock</code>, swayidle</code>)</li> Background wallpaper utility (swaybg</code>)</li> Polkit graphical authentication agent (polkit-gnome</code>, polkit-kde-agent</code>)</li> Freedesktop secret storage daemon (gnome-keyring</code>, keepassxc</code>)</li> Clipboard manager (cliphist</code>, wl-clipboard</code>)</li> Screenshot and region selection utilities (grim</code>, slurp</code>, swappy</code>)</li> Screen recording software (wf-recorder</code>, obs-studio</code>)</li> Colour picker and hardware OSD (hyprpicker</code>, swayosd</code>)</li> </ul> 🔗</a>Audio & Networking</h2> Audio processing server (pipewire</code>, pipewire-pulse</code>, wireplumber</code>)</li> Audio mixer interface (pavucontrol</code>, pulsemixer</code>)</li> Network management daemon and UI (networkmanager</code>, nm-applet</code>, iwd</code>)</li> Host firewall configuration (ufw</code>, nftables</code>)</li> SSH server and client tools (openssh</code>)</li> Network diagnostic utilities (nmap</code>, traceroute</code>, bind</code>, iperf3</code>)</li> </ul> 🔗</a>Input, Hardware & Theming</h2> Backlight brightness controls (brightnessctl</code>)</li> Laptop power management daemon (tlp</code>, auto-cpufreq</code>)</li> Bluetooth audio and device managers (bluez</code>, blueman</code>)</li> S.M.A.R.T. disk monitoring utilities (smartmontools</code>, nvme-cli</code>)</li> Complete font stack (Monospace Nerd Font, Sans, Serif, Emoji)</li> GTK and Qt theming engines (nwg-look</code>, qt5ct</code>, qt6ct</code>, kvantum</code>)</li> Icon and cursor themes (papirus-icon-theme</code>, bibata-cursor-theme</code>)</li> </ul> 🔗</a>Terminal, Development & System Utilities</h2> GPU-accelerated terminal emulator (kitty</code>, foot</code>, alacritty</code>)</li> Shell environment and prompt engine (zsh</code>, starship</code>)</li> Terminal multiplexer and pager (tmux</code>, bat</code>)</li> AUR helper (paru</code>, yay</code>)</li> Modal text editor (neovim</code>, vim</code>)</li> Version control system and interactive TUI (git</code>, lazygit</code>)</li> Language version managers and toolchains (mise</code>, python</code>, nodejs</code>, rust</code>)</li> Containerisation runtime (podman</code>, docker</code>)</li> File manager and archive utilities (yazi</code>, 7zip</code>, unzip</code>, tar</code>, zstd</code>)</li> Automated backup system (restic</code>, borgbackup</code>, rsync</code>)</li> Modern CLI search and monitoring tools (btop</code>, ripgrep</code>, fd</code>, fzf</code>, eza</code>)</li> Essential GUI applications (Browser, Mail, PDF Viewer, Media Player, Office Suite)</li> </ul> Vim Unknown — Tue, 28 Apr 2026 14:41:48 +0100 🔗</a>PHILOSOPHY AND MODAL EDITING</h2> Vim's defining characteristic is that it is a modal editor. There is no persistent insert state. You are always in one mode, and that mode determines exactly what every keystroke means. The payoff: once you internalise the grammar, editing becomes a composable language. d3w</code> (delete three words), ci"</code> (change inside quotes), gUip</code> (uppercase inner paragraph) — these are statements in a grammar you can extend indefinitely. Core ideas: Keep your hands on the home row. The mouse is a context switch.</li> Spend most of your time in Normal mode — it is the command mode, not a waiting state.</li> Every operator + motion combination is a sentence. You do not need to remember two hundred commands; you learn a vocabulary of ~30 and combine them.</li> The dot (.</code>) command repeats the last change. Design your edits so they are repeatable.</li> Use text objects, not character-by-character selection. ci(</code> is faster than going to the first char, visually selecting, then deleting.</li> </ul> 🔗</a>Vim vs Neovim</h3> Feature</th> Vim</th> Neovim</th></tr></thead> Config language</td> Vimscript</td> Lua (first class), Vimscript (supported)</td></tr> Async</td> Limited</td> Full async via libuv</td></tr> Built-in LSP</td> No</td> Yes</td></tr> Built-in Treesitter</td> No</td> Yes</td></tr> Built-in terminal</td> Yes</td> Yes (better integration)</td></tr> RPC/remote plugins</td> Via Python/Ruby</td> Via msgpack-RPC</td></tr> Floating windows</td> No</td> Yes</td></tr> Default options</td> Conservative</td> More sensible defaults</td></tr> Active development</td> Maintenance mode</td> Active</td></tr> </tbody></table> For a modern installation, Neovim is the optimal choice. It offers native Lua support, integrated language server capabilities, and advanced UI features. 🔗</a>INSTALL AND UPGRADE</h2> 🔗</a>Neovim</h3> Arch Linux: sudo pacman -S neovim</code></pre> Ubuntu / Debian (Latest Stable): sudo add-apt-repository ppa:neovim-ppa/stable sudo apt update && sudo apt install neovim</code></pre> Build from source: sudo pacman -S base-devel cmake ninja unzip gettext curl git clone [https://github.com/neovim/neovim.git](https://github.com/neovim/neovim.git) cd neovim git checkout stable make CMAKE_BUILD_TYPE=Release sudo make install</code></pre>🔗</a>Clipboard Support</h3> Neovim delegates clipboard tasks to external tools. Your configuration uses unnamedplus</code> for Wayland integration. # Wayland sudo pacman -S wl-clipboard # provides wl-copy, wl-paste # X11 sudo pacman -S xclip # or xsel # check Neovim sees it nvim -c ':checkhealth' -c ':only'</code></pre> 🔗</a>CONFIG PATHS AND LAUNCH</h2> Neovim follows the XDG Base Directory Specification. Your main configuration file is ~/.config/nvim/init.lua</code>. Path</th> Purpose</th></tr></thead> ~/.config/nvim/init.lua</code></td> Main config (Lua)</td></tr> ~/.config/nvim/lua/</code></td> Lua modules directory</td></tr> ~/.local/share/nvim/</code></td> Data: plugins, undo history, swap files</td></tr> ~/.local/share/nvim/lazy/</code></td> lazy.nvim</code> plugin store</td></tr> ~/.local/state/nvim/</code></td> Log files, shada</td></tr> ~/.cache/nvim/</code></td> Cache</td></tr> </tbody></table> 🔗</a>Reloading Config</h3> To reload your configuration dynamically inside Neovim: :source $MYVIMRC</code></pre> 🔗</a>THE MODAL MODEL</h2> Vim has several modes. Understanding each and how to enter and exit them is the foundation of everything else. Mode</th> Indicator</th> Entry</th> Exit</th></tr></thead> Normal</td> (none)</td> Escape</code>, Ctrl-[</code>, Ctrl-c</code></td> — (this is home)</td></tr> Insert</td> -- INSERT --</code></td> i</code>, a</code>, o</code>, s</code>, c</code>, R</code>...</td> Escape</code></td></tr> Visual (char)</td> -- VISUAL --</code></td> v</code></td> Escape</code> or v</code></td></tr> Visual (line)</td> -- VISUAL LINE --</code></td> V</code></td> Escape</code> or V</code></td></tr> Visual (block)</td> -- VISUAL BLOCK --</code></td> Ctrl-v</code></td> Escape</code> or Ctrl-v</code></td></tr> Command-line</td> :</code> or /</code> or ?</code></td> :</code>, /</code>, ?</code>, !</code></td> Enter</code> or Escape</code></td></tr> Replace</td> -- REPLACE --</code></td> R</code></td> Escape</code></td></tr> Terminal</td> -- TERMINAL --</code></td> :terminal</code>, i</code> in term buf</td> Ctrl-\</code> then Ctrl-n</code></td></tr> </tbody></table> 🔗</a>Why Normal Mode is Home</h3> Every other editor puts you in an insert state by default. Vim inverts this: Normal mode is the resting state. Text editing breaks down into navigating to the edit, making the change, and returning to Normal to navigate again. Vim optimises for navigating. 🔗</a>NORMAL MODE — MOTIONS</h2> Motions move the cursor. Every motion can be preceded by a count. Motions combined with operators form the editing grammar. 🔗</a>Character Motions</h3> Key</th> Movement</th></tr></thead> h</code></td> Left one character</td></tr> j</code></td> Down one line</td></tr> k</code></td> Up one line</td></tr> l</code></td> Right one character</td></tr> 0</code></td> Column zero (start of line, including whitespace)</td></tr> ^</code></td> First non-blank character of line</td></tr> $</code></td> End of line (after last character)</td></tr> g_</code></td> Last non-blank character of line</td></tr> </tbody></table> 🔗</a>Word Motions</h3> A word is a sequence of alphanumeric characters and underscores. A WORD is any sequence of non-whitespace characters. Key</th> Movement</th></tr></thead> w</code></td> Start of next word</td></tr> W</code></td> Start of next WORD</td></tr> b</code></td> Start of previous word</td></tr> B</code></td> Start of previous WORD</td></tr> e</code></td> End of current/next word</td></tr> E</code></td> End of current/next WORD</td></tr> </tbody></table> 🔗</a>Find and To (Character Search on Line)</h3> Key</th> Movement</th></tr></thead> f{c}</code></td> Forward to next occurrence of character c</code> on line</td></tr> F{c}</code></td> Backward to previous occurrence of c</code> on line</td></tr> t{c}</code></td> Forward to just before next c</code></td></tr> T{c}</code></td> Backward to just after previous c</code></td></tr> ;</code></td> Repeat last f/F/t/T</code> in same direction</td></tr> ,</code></td> Repeat last f/F/t/T</code> in opposite direction</td></tr> </tbody></table> 🔗</a>Line Number and Document Motions</h3> Key</th> Movement</th></tr></thead> gg</code></td> First line of file</td></tr> G</code></td> Last line of file</td></tr> {N}G</code></td> Line N</td></tr> %</code></td> Matching bracket/paren/brace/HTML tag</td></tr> {</code></td> Start of previous paragraph</td></tr> }</code></td> Start of next paragraph</td></tr> </tbody></table> 🔗</a>NORMAL MODE — OPERATORS</h2> Operators act on the text covered by a following motion or text object. The pattern is: [count] {operator} [count] {motion}</code>. Key</th> Action</th></tr></thead> d</code></td> Delete (cut — goes into register)</td></tr> y</code></td> Yank (copy)</td></tr> c</code></td> Change (delete then enter Insert mode)</td></tr> ></code></td> Indent right</td></tr> <</code></td> Indent left</td></tr> =</code></td> Auto-indent (format indentation)</td></tr> gq</code></td> Format lines (wrap to textwidth)</td></tr> gU</code></td> Uppercase</td></tr> gu</code></td> Lowercase</td></tr> ~</code></td> Toggle case of character under cursor</td></tr> </tbody></table> 🔗</a>Composed Examples</h3> d3w</code> -- delete 3 words</li> d$</code> -- delete to end of line</li> dd</code> -- delete current line</li> dG</code> -- delete to end of file</li> yap</code> -- yank around paragraph</li> ci"</code> -- change inside double quotes</li> gUiw</code> -- uppercase inner word</li> </ul> 🔗</a>The Dot Command</h3> .</code> repeats the last change — not the last command. A change is any action that modified text: insert, delete, replace, etc. Design your edits for repeatability. For example: ciw<new text><Esc></code>, then press .</code> on the next word to apply the identical change. 🔗</a>TEXT OBJECTS</h2> Text objects allow selecting structured regions of text without navigating to their boundaries. They only work after an operator or in visual mode. Format: {i|a}{object}</code> — i</code> = inner (without delimiters), a</code> = around (with delimiters). Object</th> Inner (i)</th> Around (a)</th></tr></thead> w</code></td> Word</td> Word + surrounding whitespace</td></tr> W</code></td> WORD</td> WORD + surrounding whitespace</td></tr> s</code></td> Sentence</td> Sentence + whitespace</td></tr> p</code></td> Paragraph</td> Paragraph + blank lines</td></tr> "</code></td> Inside double quotes</td> Including double quotes</td></tr> '</code></td> Inside single quotes</td> Including single quotes</td></tr> (</code> or )</code></td> Inside parentheses</td> Including parentheses</td></tr> [</code> or ]</code></td> Inside square brackets</td> Including brackets</td></tr> {</code> or }</code></td> Inside curly braces</td> Including braces</td></tr> t</code></td> Inside HTML/XML tag</td> Including the tags</td></tr> </tbody></table> 🔗</a>Text Object Examples</h3> diw</code> -- delete inner word (leaves whitespace)</li> daw</code> -- delete around word (removes word + space)</li> ci(</code> -- change inside parentheses</li> yi'</code> -- yank inside single quotes</li> </ul> 🔗</a>INSERT MODE</h2> Insert mode is where you type text. The goal is to enter it, type the minimum, and leave. Key</th> Entry Point</th></tr></thead> i</code></td> Before the cursor</td></tr> I</code></td> Before first non-blank character of line</td></tr> a</code></td> After the cursor</td></tr> A</code></td> After the last character of line (end of line)</td></tr> o</code></td> Open new line below and enter insert</td></tr> O</code></td> Open new line above and enter insert</td></tr> s</code></td> Delete character under cursor and enter insert</td></tr> S</code></td> Delete entire line content and enter insert</td></tr> c{motion}</code></td> Delete through motion, enter insert</td></tr> </tbody></table> 🔗</a>Insert Mode Commands</h3> Key</th> Action</th></tr></thead> Ctrl-[</code></td> Exit Insert mode (same as Escape)</td></tr> Ctrl-w</code></td> Delete word before cursor</td></tr> Ctrl-u</code></td> Delete all characters before cursor on current line</td></tr> Ctrl-o</code></td> Execute one Normal mode command, return to Insert</td></tr> Ctrl-r {reg}</code></td> Insert contents of register</td></tr> </tbody></table> 🔗</a>VISUAL MODE</h2> Visual mode lets you select a region and then apply an operator to it. Key</th> Mode</th></tr></thead> v</code></td> Character-wise visual</td></tr> V</code></td> Line-wise visual</td></tr> Ctrl-v</code></td> Block visual</td></tr> gv</code></td> Reselect last visual selection</td></tr> o</code></td> Toggle cursor to opposite end of selection</td></tr> </tbody></table> 🔗</a>Block Visual Mode</h3> Block visual (Ctrl-v</code>) selects a rectangular region. Operations apply to each line of the block independently. This is extremely powerful for prepending text to multiple lines simultaneously (Ctrl-v</code>, select lines, I</code>, type text, Escape</code>). 🔗</a>COMMAND-LINE MODE</h2> Command-line mode is entered with :</code>, /</code>, ?</code>, or !</code>. It accepts Ex commands, search patterns, and shell commands. 🔗</a>Ranges</h3> Ranges prefix Ex commands to specify which lines they operate on. %</code> Entire file (same as 1,$</code>)</li> '<,'></code> Last visual selection (auto-populated when pressing :</code> in Visual mode)</li> 1,10</code> Lines 1 to 10</li> .,+5</code> Current line to 5 lines below</li> </ul> 🔗</a>Global Command (:g)</h3> :g/{pattern}/{command}</code> runs a command on every line matching a pattern. :g/TODO/d</code> " delete all TODO lines</li> :g/^$/d</code> " delete blank lines</li> :v/pattern/d</code> " delete all non-matching lines</li> </ul> 🔗</a>Filter Command (:!)</h3> :%!sort</code> " sort entire file</li> :'<,'>!python3</code> " run visual selection through python</li> </ul> 🔗</a>SEARCH AND SUBSTITUTE</h2> 🔗</a>Search</h3> /pattern</code> " search forward</li> ?pattern</code> " search backward</li> n</code> " next match (same direction)</li> N</code> " previous match (opposite direction)</li> </code> " search word under cursor forward (whole word)</li> </ul> Your configuration ensures searches are fast and ergonomic: ignorecase</code> is enabled so lowercase inputs match both cases.</li> smartcase</code> is enabled so queries containing uppercase letters strictly match case.</li> </ul> 🔗</a>Substitute</h3> :s/old/new/</code> " replace first match on current line</li> :%s/old/new/g</code> " replace all matches in file</li> :%s/old/new/gc</code> " replace all, confirm each</li> :'<,'>s/old/new/g</code> " replace in visual selection</li> </ul> 🔗</a>REGISTERS</h2> Registers store text. They are accessed with "</code> followed by the register name. Register</th> Name</th> Description</th></tr></thead> ""</code></td> Unnamed</td> Last deleted, changed, or yanked text</td></tr> "0</code></td> Yank</td> Most recent yank only (not affected by delete)</td></tr> "1</code>–"9</code></td> Numbered</td> Rolling history of deletes and changes</td></tr> "a</code>–"z</code></td> Named</td> User-controlled, explicitly named</td></tr> "+</code></td> Clipboard</td> System clipboard</td></tr> "_</code></td> Black hole</td> Discard — no register is affected</td></tr> "/</code></td> Search</td> Last search pattern</td></tr> </tbody></table> 🔗</a>The Unnamed and Yank Registers</h3> The most common confusion: "1</code> through "9</code> shift on every delete. But "0</code> only updates on explicit yanks, never on deletes. Always use "0p</code> to paste a yank after subsequent deletes. 🔗</a>MACROS</h2> Macros record a sequence of Normal, Insert, and Command-line mode actions into a register and replay them. q{register}</code> " begin recording into register (e.g. qq</code>)</li> q</code> " stop recording</li> @{register}</code> " execute macro once</li> {N}@{register}</code> " execute macro N times</li> @@</code> " repeat last executed macro</li> </ul> 🔗</a>WINDOWS, BUFFERS, AND TABS</h2> 🔗</a>Windows</h3> A window is a viewport onto a buffer. Ctrl-w v</code> Vertical split</li> Ctrl-w s</code> Horizontal split</li> Ctrl-w h/j/k/l</code> Move between windows</li> Ctrl-w =</code> Equalise all window sizes</li> Ctrl-w c</code> Close window</li> </ul> 🔗</a>Buffers</h3> A buffer is a file loaded into memory. It exists whether or not it is currently displayed in a window. :ls</code> " list all listed buffers</li> :b{N}</code> " switch to buffer N</li> :bn</code> / :bp</code> " next / previous buffer</li> :bd</code> " unload and remove current buffer</li> </ul> 🔗</a>Tabs</h3> Tabs in Vim are not like editor tabs — they are separate window layouts, each containing their own set of splits. Use tabs for distinct working contexts, not for individual files. :tabnew</code> " open new tab</li> gt</code> / gT</code> " Next / previous tab</li> </ul> 🔗</a>NEOVIM LUA ESSENTIALS</h2> Neovim exposes its API through the vim</code> global Lua object. vim.opt.number = true -- set an option vim.g.mapleader = " " -- set a global variable vim.fn.expand("%") -- call a Vim built-in function vim.cmd("w") -- execute Ex commands vim.api.nvim_get_current_buf() -- interact with the Neovim C API</code></pre>🔗</a>Neovim Lua Autocommands</h3> vim.api.nvim_create_autocmd("FileType", { pattern = { "lua", "sh", "markdown" }, callback = function() -- action to perform end, })</code></pre> 🔗</a>NEOVIM — THIS CONFIG DEEP-DIVE</h2> Your init.lua</code> sets up a highly tailored, keyboard-driven development environment, leaning on modern Lua plugins rather than legacy Vimscript. 🔗</a>Core Settings</h3> Your environment establishes standard editor behaviors and aesthetics natively: The mapleader</code> and maplocalleader</code> are bound to the Space</code> key.</li> Absolute line numbers (number = true</code>) and relative line numbering (relativenumber = true</code>) are both enabled to facilitate rapid vertical jumping.</li> Full mouse support is active across all modes (mouse = "a"</code>).</li> Case-insensitive searching is enabled (ignorecase = true</code>), which intelligently becomes case-sensitive if you type an uppercase character (smartcase = true</code>).</li> The updatetime</code> is lowered to 250</code> milliseconds, ensuring diagnostics and plugin updates feel responsive.</li> True 24-bit color is enforced with termguicolors = true</code>.</li> System clipboard integration is handled seamlessly using the unnamedplus</code> register.</li> The spelllang</code> is strictly set to "en_gb"</code>.</li> </ul> 🔗</a>Package Management: Lazy.nvim</h3> The setup utilizes lazy.nvim</code> as its package manager. It dynamically bootstraps itself via git clone</code> into stdpath("data") .. "/lazy/lazy.nvim"</code> if the directory does not exist. It targets the stable</code> branch and enforces a blobless clone (--filter=blob:none</code>) for speed. 🔗</a>Plugins</h3> 🔗</a>Theme: Flexoki</h4> The kepano/flexoki-neovim</code> plugin is loaded with top priority (priority = 1000</code>).</li> It executes the colorscheme flexoki-dark</code> command immediately upon loading.</li> It explicitly overrides the Normal</code> and NormalFloat</code> highlight groups, painting their backgrounds with the #100F0F</code> hex code to mesh perfectly with your broader Sway/system aesthetic.</li> </ul> 🔗</a>Syntax and Parsing: Nvim-Treesitter</h4> nvim-treesitter/nvim-treesitter</code> is configured to download and compile parsers natively.</li> It is explicitly instructed to install parsers for lua</code>, bash</code>, markdown</code>, and markdown_inline</code>.</li> A FileType</code> autocommand triggers vim.treesitter.start()</code> automatically whenever you open lua</code>, sh</code>, or markdown</code> files.</li> </ul> 🔗</a>Autocompletion: Nvim-Cmp</h4> The hrsh7th/nvim-cmp</code> plugin handles code completion, relying strictly on two local dependencies: cmp-path</code> and cmp-buffer</code>.</li> The sources</code> configuration limits data aggregation to local file paths ({ name = "path" }</code>) and current text buffers ({ name = "buffer" }</code>).</li> Key mappings are explicitly structured around standard control keys: <C-b></code> scrolls docs up, <C-f></code> scrolls docs down, <C-Space></code> manually triggers the menu, <C-e></code> aborts the operation, and <CR></code> confirms the selection.</li> </ul> 🔗</a>Buffer Navigation: Bufferline.nvim</h4> akinsho/bufferline.nvim</code> requires nvim-web-devicons</code> to function correctly in your setup.</li> The bar is configured in buffers</code> mode, rendering background buffers at the top of the terminal.</li> It displays ordinal</code> numbers on the tabs and hides all graphical closing icons (show_buffer_close_icons = false</code>, show_close_icon = false</code>) for a cleaner visual profile.</li> It enforces regular tabs (enforce_regular_tabs = true</code>), a thin separator (separator_style = "thin"</code>), and ensures the bar is always visible.</li> Custom keymaps are defined for navigation: <S-h></code> calls <cmd>BufferLineCyclePrev<CR></code>, <S-l></code> calls <cmd>BufferLineCycleNext<CR></code>, and <leader>x</code> terminates the active buffer with <cmd>bdelete<CR></code>.</li> </ul> 🔗</a>Markdown Enhancements: Render-Markdown</h4> MeanderingProgrammer/render-markdown.nvim</code> leverages both treesitter and devicons to paint Markdown files beautifully in the terminal.</li> Heading signs are disabled (sign = false</code>), and heading icons are replaced with a custom array of specialized font characters ('󰲡 '</code>, '󰲣 '</code>, '󰲥 '</code>, '󰲧 '</code>, '󰲩 '</code>, '󰲫 '</code>).</li> Code blocks disable the standard sign column, render natively as visual blocks (width = "block"</code>), and inject a minor right-side padding (right_pad = 1</code>).</li> </ul> 🔗</a>Writing Focus: Zen-mode.nvim</h4> folke/zen-mode.nvim</code> strips away terminal distractions.</li> The isolated window is restricted to a column width of 80 (width = 80</code>).</li> Absolute and relative line numbers are forcefully disabled within the Zen pane (number = false</code>, relativenumber = false</code>).</li> It is triggered instantly via the <leader>z</code> keybinding, invoking <cmd>ZenMode<CR></code>.</li> </ul> Archinstall Unknown — Wed, 22 Apr 2026 11:04:49 +0100 Pre-Flight Boot the Arch Linux live USB in UEFI mode and confirm the firmware interface:</li> </ol> # CHECK UEFI FIRMWARE VARIABLES ls /sys/firmware/efi/efivars</code></pre> Set the keyboard layout immediately. The default US layout will mangle your LUKS passphrase during creation if you rely on a UK keyboard. # LOAD UK KEYBOARD LAYOUT loadkeys uk</code></pre> Connect to the network and synchronise the system clock: # TEST NETWORK CONNECTIVITY ping -c 3 archlinux.org # CONNECT WIRELESSLY VIA IWCTL IF REQUIRED iwctl # station wlan0 scan # station wlan0 connect <ssid> # SYNCHRONISE SYSTEM CLOCK timedatectl set-ntp true timedatectl status</code></pre> Storage Architecture The system resides on a single NVMe drive. The partition table divides the drive into an EFI system partition, an unencrypted boot partition, and a primary encrypted container:</li> </ol> Partition</th> Size</th> Role</th> Filesystem</th></tr></thead> /dev/nvme0n1p1</code></td> 1 GiB</td> EFI System Partition</td> vfat, unencrypted</td></tr> /dev/nvme0n1p2</code></td> 2 GiB</td> /boot</code></td> ext4, unencrypted</td></tr> /dev/nvme0n1p3</code></td> ~253 GiB</td> LUKS2 container</td> encrypted XTS-plain64</td></tr> </tbody></table> Inside the LUKS container, Logical Volume Management carves out four volumes: Volume</th> Size</th> Filesystem</th> Role</th></tr></thead> vg0/swap</code></td> 16 GiB</td> swap</td> virtual memory and hibernation</td></tr> vg0/root</code></td> 50 GiB</td> XFS</td> system root</td></tr> vg0/var</code></td> 20 GiB</td> XFS</td> variable data and logs</td></tr> vg0/home</code></td> ~167 GiB</td> XFS</td> user directories</td></tr> </tbody></table> 2.1 Wipe the Drive # WIPE EXISTING SIGNATURES AND PARTITIONS wipefs -a /dev/nvme0n1</code></pre> 2.2 Partition # CREATE GPT PARTITION TABLE AND SLICES parted -s /dev/nvme0n1 mklabel gpt parted -s /dev/nvme0n1 mkpart ESP fat32 1MiB 1025MiB parted -s /dev/nvme0n1 set 1 esp on parted -s /dev/nvme0n1 mkpart primary ext4 1025MiB 3073MiB parted -s /dev/nvme0n1 mkpart primary 3073MiB 100%</code></pre> 2.3 Encrypt the Root Partition # INITIALISE LUKS2 CONTAINER WITH 512 BIT KEY cryptsetup luksFormat --type luks2 --cipher aes-xts-plain64 --key-size 512 /dev/nvme0n1p3 # OPEN ENCRYPTED CONTAINER cryptsetup open /dev/nvme0n1p3 cryptroot</code></pre> 2.4 LVM # INITIALISE PHYSICAL VOLUME AND VOLUME GROUP pvcreate /dev/mapper/cryptroot vgcreate vg0 /dev/mapper/cryptroot # ALLOCATE LOGICAL VOLUMES lvcreate -L 16G -n swap vg0 lvcreate -L 50G -n root vg0 lvcreate -L 20G -n var vg0 lvcreate -l 100%FREE -n home vg0</code></pre> 2.5 Format # FORMAT BOOT AND EFI PARTITIONS mkfs.vfat -F32 /dev/nvme0n1p1 mkfs.ext4 /dev/nvme0n1p2 # FORMAT LOGICAL VOLUMES mkfs.xfs /dev/vg0/root mkfs.xfs /dev/vg0/var mkfs.xfs /dev/vg0/home mkswap /dev/vg0/swap</code></pre> 2.6 Mount Mount the filesystems in strict hierarchical order to prevent directory obscuration: # MOUNT ROOT AND CREATE BASE DIRECTORY STRUCTURE mount /dev/vg0/root /mnt mkdir -p /mnt/{boot,home,var} # MOUNT BOOT AND CREATE EFI MOUNT POINT INSIDE IT mount /dev/nvme0n1p2 /mnt/boot mkdir -p /mnt/boot/efi mount /dev/nvme0n1p1 /mnt/boot/efi # MOUNT REMAINING LOGICAL VOLUMES AND ACTIVATE SWAP mount /dev/vg0/var /mnt/var mount /dev/vg0/home /mnt/home swapon /dev/vg0/swap</code></pre> Base Installation Install the base operating system, hardware drivers, Niri, and your Wayland utility stack:</li> </ol> # INSTALL BASE SYSTEM AND PACKAGES pacstrap -K /mnt \ base base-devel linux linux-headers linux-firmware \ intel-ucode \ lvm2 cryptsetup xfsprogs e2fsprogs dosfstools \ neovim tmux git networkmanager man-db man-pages sudo \ mesa vulkan-intel intel-media-driver \ niri waybar rofi-wayland \ xdg-desktop-portal-gnome xdg-desktop-portal-gtk \ xdg-user-dirs polkit-gnome \ ly \ kitty wl-clipboard grim slurp \ swaybg swaylock swayidle mako \ pipewire pipewire-alsa pipewire-pulse pipewire-jack wireplumber pavucontrol \ bluez bluez-utils \ tlp tlp-rdw acpid brightnessctl \ ttf-ibm-plex noto-fonts noto-fonts-emoji ttf-jetbrains-mono-nerd</code></pre> Generate the filesystem table using universally unique identifiers: # GENERATE FILESYSTEM TABLE genfstab -U /mnt >> /mnt/etc/fstab cat /mnt/etc/fstab</code></pre> System Configuration Enter the new system installation:</li> </ol> # ENTER CHROOT ENVIRONMENT arch-chroot /mnt</code></pre> 4.1 Timezone and Locale # CONFIGURE TIMEZONE AND CLOCK ln -sf /usr/share/zoneinfo/Africa/Lagos /etc/localtime hwclock --systohc # GENERATE AND APPLY LOCALE sed -i 's/^#en_GB.UTF-8 UTF-8/en_GB.UTF-8 UTF-8/' /etc/locale.gen locale-gen echo "LANG=en_GB.UTF-8" > /etc/locale.conf</code></pre> 4.2 Keymap Write the configuration directly to /etc/vconsole.conf</code>. The initramfs generation hooks read this file automatically: # PERSIST CONSOLE KEYBOARD LAYOUT echo "KEYMAP=uk" > /etc/vconsole.conf</code></pre> 4.3 Network Identity # SET HOSTNAME AND HOSTS ENTRIES echo "arch" > /etc/hostname cat <<EOF> /etc/hosts 127.0.0.1 localhost ::1 localhost 127.0.1.1 arch.localdomain arch EOF # ENABLE NETWORK MANAGEMENT systemctl enable NetworkManager</code></pre> 4.4 Initramfs Edit /etc/mkinitcpio.conf</code> and configure the HOOKS</code> array. Placing microcode</code> immediately after autodetect</code> bundles CPU microcode updates directly into the main kernel initramfs image: # MODIFY INITRAMFS HOOKS nvim /etc/mkinitcpio.conf</code></pre> Ensure the line reads exactly: HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block encrypt lvm2 resume filesystems fsck)</code></pre> Generate the boot images: # COMPILE INITRAMFS IMAGES mkinitcpio -P</code></pre> Bootloader</li> </ol> # INSTALL GRUB AND EFI BOOT MANAGEMENT TOOLS pacman -S grub efibootmgr</code></pre> Retrieve the UUID of your encrypted LUKS partition: # LOCATE LUKS PARTITION UUID blkid /dev/nvme0n1p3</code></pre> Edit /etc/default/grub</code> and populate the GRUB_CMDLINE_LINUX</code> variable with the LUKS UUID and LVM volume mappings: # CONFIGURE GRUB KERNEL PARAMETERS nvim /etc/default/grub</code></pre> Set the line as follows, substituting <uuid></code> with the actual string from blkid</code>: GRUB_CMDLINE_LINUX="cryptdevice=UUID=<uuid>:cryptroot root=/dev/mapper/vg0-root resume=/dev/mapper/vg0-swap"</code></pre> Install the bootloader to the EFI directory and generate the configuration file: # INSTALL GRUB TO EFI PARTITION grub-install --target=x86_64-efi --efi-directory=/boot/efi \ --bootloader-id=GRUB --removable # GENERATE GRUB CONFIGURATION grub-mkconfig -o /boot/grub/grub.cfg</code></pre> User Management</li> </ol> # ASSIGN ROOT PASSWORD passwd # CREATE PRIMARY USER ACCOUNT WITH HARDWARE GROUPS useradd -m -s /bin/bash -G wheel,video,audio,storage,input osaigbovo passwd osaigbovo # GRANT SUDO PRIVILEGES TO WHEEL GROUP EDITOR=nvim visudo</code></pre> Uncomment the %wheel ALL=(ALL:ALL) ALL</code> line inside the sudoers file. System Services Enable required system daemons before exiting the chroot environment:</li> </ol> # ENABLE DISPLAY MANAGER AND HARDWARE SERVICES systemctl enable ly systemctl enable bluetooth systemctl enable tlp systemctl enable tlp-rdw systemctl enable acpid # MASK RFKILL UNITS TO PREVENT TLP CONFLICTS systemctl mask systemd-rfkill.service systemd-rfkill.socket</code></pre> PipeWire and WirePlumber operate exclusively as user session daemons. Modern Arch Linux packages configure socket activation by default. When you log in as osaigbovo</code> for the first time, systemd automatically initiates the audio server and desktop portal infrastructure without requiring manual intervention. 7.1 Niri Configuration Create the Niri configuration directory and file under your standard user account after first boot: # CREATE NIRI CONFIGURATION DIRECTORY mkdir -p ~/.config/niri nvim ~/.config/niri/config.kdl</code></pre> Populate config.kdl</code> with your environment variables, background, locker, idle management, and status bar configurations: // CONFIGURE WAYLAND ENVIRONMENT VARIABLES FOR INTEL GRAPHICS environment { LIBVA_DRIVER_NAME "iHD" XDG_SESSION_TYPE "wayland" XDG_SESSION_DESKTOP "niri" XDG_CURRENT_DESKTOP "niri" QT_QPA_PLATFORM "wayland" MOZ_ENABLE_WAYLAND "1" } // SPAWN SESSION DAEMONS AND UTILITIES AT STARTUP spawn-at-startup "/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1" spawn-at-startup "mako" spawn-at-startup "waybar" spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/osaigbovo/.config/wallpaper.png" spawn-at-startup "swayidle" "-w" "timeout" "300" "swaylock -f" "timeout" "600" "niri msg action power-off-monitors" "resume" "niri msg action power-on-monitors"</code></pre> Finalisation Exit the chroot environment, unmount all disks, deactivate the logical volumes, seal the LUKS container, and reboot the machine:</li> </ol> # EXIT CHROOT exit # DEACTIVATE SWAP AND UNMOUNT FILESYSTEMS swapoff -a umount -R /mnt # DEACTIVATE VOLUME GROUP AND CLOSE LUKS CONTAINER vgchange -an vg0 cryptsetup close cryptroot # REBOOT SYSTEM reboot</code></pre> Linux is a Religion Unknown — Fri, 10 Apr 2026 23:49:00 +0000 Watching a digital crusade unfold in real-time on a Lemmy forum a few days ago, I was struck by a terrifying realisation. Dozens of users were locked in a fierce, polite, yet utterly unyielding holy war, each attempting to convert the heathens to their preferred Linux distribution. The rhetoric was indistinguishable from 16th-century theological debates, just heavily seasoned with acronyms. Unable to resist the gravitational pull of my own ego, I dropped a comment noting that I use Arch--a statement that effectively marks me as a fundamentalist. Seven people starred it. The dopamine hit was immediate, and deeply shameful. There is a unique kind of dread that creeps up on you when you have spent two decades walking the earth as a committed atheist, viewing faith communities with the polite, anthropological distance of someone who considers theological devotion a cognitive defect, only to wake up one morning and realise you have accidentally joined a cult. I have become doctrinaire. I am devotional. I become quietly, irrationally furious when I see someone using apt</code> instead of pacman</code>. I have stumbled backward into the Linux, open-source, and privacy ecosystem and discovered a complete, all-encompassing theological system to fawn over. < Calling a subculture a "religion" is usually just a lazy linguistic shortcut to describe people who care a little too much about CrossFit or veganism. But a true religion does specific, heavy lifting for the human psyche. It provides a cosmology: an account of how the universe is structured and the foundational values holding it together. It produces orthodoxy, aggressively policing the boundary between correct belief and heresy. It generates an eschatology--a prophetic vision of how the world will ultimately end. It relies on highly specific rituals to mark the initiate against the uninitiated. Finally, it reproduces itself through conversion experiences that believers inevitably describe as "seeing the light." The Linux community executes every single one of these functions with terrifying, structural precision. Every religion requires a Genesis myth and a pantheon of prophets. Our foundational cosmology is the free software philosophy, and like all cosmologies worth dying for, it is a moral position disguised as a technical one. In the beginning, the code was closed, and darkness was upon the face of the mainframe. Then came Richard Stallman. Stallman did not launch the GNU Project in 1983 because he crunched the numbers and calculated that open-source collaboration would yield fewer bugs. He launched it because he experienced a profound moral revulsion at the idea of proprietary software. To Stallman, a world where humans could not read, modify, and share the tools they depended on was a world where human autonomy had been fatally violated. He once wrote that he could have amused himself writing code for money, but knew that at the end of his career, he would look back on "years of building walls to divide people." That is pure, unadulterated Old Testament prophet energy. Stallman views proprietary software the way an exorcist views a demon. To him, the General Public License (GPL) is an unbreakable covenant holding the forces of corporate enclosure at bay. "Free as in speech, not as in beer." That distinction is the rock upon which the church is built. Then came Linus Torvalds, the architect of the kernel itself. Torvalds is the New Testament pragmatist. He does not share Stallman’s rigid theology, once famously quipping, "Talk is cheap. Show me the code." Torvalds is interested in what actually works, what compiles, and what scales, rather than maintaining absolute doctrinal purity. The tension between the Stallmanite moralists and the Torvalds pragmatists is the defining schism of the ecosystem. It is a disagreement over the fundamental nature of the shared project: What are we building this for? Who does it serve? What compromises will condemn our souls to the corporate abyss? Consequently, every single Linux distribution is forced to take a position in this theological landscape. Debian is the ancient orthodox church. Its commitment to free software purity is absolute. The installation is archaic, the packages are old, and the aesthetic is unforgiving, but it is ideologically flawless. Debian’s willingness to make your life difficult in exchange for ideological consistency is a pure confession of faith. Ubuntu is the megachurch. It has the fog machines, the coffee shop in the lobby, and the charismatic pastor wearing trainers. Ubuntu looked at the masses and decided that the church had to grow, even if it meant shipping proprietary drivers and pushing Snap packages onto the congregation. In doctrinal terms, Ubuntu made concessions to the secular world, making an easy path available--a move the orthodox view as an unforgivable temptation. Rocky Linux and the broader Red Hat Enterprise ecosystem sit in the Benedictine tradition. They are the enterprise monks: conservative, stable, and deeply uninterested in whatever shiny new toy the desktop users are arguing about. They patch what is known, certify what is tested, and serve massive financial institutions whose only prayer is five nines of uptime. I run Rocky in an Incus virtual machine right now while working through my CompTIA Linux+ certification, and I say this with reverence: there is deep, quiet dignity in an operating system that is exactly what it promises to be, and absolutely nothing else. Alpine is the monastery clinging to the side of a frozen mountain. Ascetic to the point of near-invisibility, it uses musl</code> instead of glibc</code> and BusyBox</code> instead of GNU coreutils. The container world reveres Alpine because it boots in milliseconds, occupies five megabytes of disk space, and does precisely what it is told without ever speaking out of turn. It simply exists, minimal and correct, like a hermit who has transcended the need for human language. Of course, no religion is complete without a vividly imagined Hell, and our world is well supplied with heretics and demons. The deepest, most fiery pit of Hell is Windows. Windows is Babylon. It is a corrupted, bloated leviathan powered by telemetry, forced updates, and corporate surveillance. To use Windows is to willingly sign over your digital sovereignty to a faceless corporation that views you not as a user, but as a harvestable data crop. Every time Microsoft injects an advertisement into the Start menu, a Linux user gets their wings. macOS occupies a much more complex theological space: Limbo, or perhaps an exceptionally well-decorated Purgatory. It shares ancient Unix genetic material with the faithful, allowing you to open a terminal and use grep</code>, awk</code>, and sed</code> just like the prophets intended. But the ecosystem is a gilded cage. It is utterly closed, unmodifiable, and strictly controlled by a trillion-dollar corporation with very aggressive opinions about what you are allowed to do with hardware you supposedly own. The people trapped in the Apple ecosystem are capable individuals who have simply chosen aesthetic comfort over freedom. I say this with the sheepish awareness of someone who actually discovered the command line on a 2018 MacBook Air. That machine was my gateway drug. I found the terminal, realised it was just a zsh</code> emulator, and discovered it could be modified. That tiny distinction--realising the interface was just a mask over the machine--cracked my entire reality open. My conversion began in earnest last August. Looking at my university degree and the catastrophic state of the Nigerian economy, I concluded that my current trajectory was not going to produce a liveable income. I discovered the concept of DevOps, and subsequently fell headfirst into the Linux rabbit hole. These two events are linked in the same way a first sip of whiskey is linked to waking up in a different state. I started on that MacBook Air, copying someone's zshrc</code> configuration from GitHub. I tweaked it, broke it, fixed it, and eventually built a highly customised terminal environment I pretentiously named Aethria Systems. Every time I added a new alias or changed the colour scheme, I versioned it, eventually stopping at version 2.1. It was an objectively absurd amount of emotional and intellectual investment poured into a text configuration file, and I regret absolutely nothing. My secondary machine was a Lenovo ThinkPad bloated with Windows. I discovered the Windows Subsystem for Linux (WSL2), spent weeks learning the basic incantations of the command line, and eventually grew disgusted by the layer of Microsoft abstraction. I moved to VirtualBox, successfully installed Ubuntu, and decided that was what I would eventually install on bare metal. Then, a friend intervened. He told me to use Arch. He delivered the recommendation with the wild-eyed, terrifying conviction of a man who had just returned from the mountaintop with stone tablets. He was relentless. I deleted my Ubuntu ISOs, ordered a blank USB stick, and spent the seven days before its arrival in a state of monastic preparation. I installed, wiped, and reinstalled Arch Linux inside VirtualBox dozens of times, memorising disk partitioning commands and learning to mount file systems. When the stick arrived, I wiped the ThinkPad and installed Arch on bare metal. By November, I had abandoned traditional desktop environments entirely, moving to Hyprland--a dynamic tiling window manager that operates entirely on keyboard shortcuts and requires forty hours of writing C++ configuration files to make it beautiful. In this religion, the installation is the initiation ritual. Most consumer distributions feature graphical installers that hold your hand, make complex partitioning decisions on your behalf, and deposit you gently into a working desktop. This is pragmatically wonderful and theologically bankrupt. The person who clicks "Next" six times knows they are using Linux; the person who manually formats their EFI partition, compiles their bootloader, and spends a week wrestling with Wayland compositors knows their machine. These are profoundly different states of knowledge, and the community treats them as such. Outsiders experience this dynamic as toxic gatekeeping; insiders experience it as necessary discernment. You cannot appreciate the cathedral if you did not haul the stones. The Arch Wiki serves as our scripture--vast, exhaustively accurate, and completely unforgiving. It punishes lazy reading and rewards deep meditation. During my initiation, I wrote a comprehensive, step-by-step installation guide based on my own agonising trial and error. Months later, the very friend who had aggressively evangelised Arch to me decided he was finally ready to install it on his own machine. I went to his house to gloat about my Hyprland workflow, feeling like a twenty-four-year-old wizard manipulating the fabric of the digital universe. I opened his laptop and discovered he was running Manjaro. Manjaro occupies a highly contested category. It is an Arch-derivative--close enough to the real thing that pure Arch users take its existence as a personal insult. My friend confessed he had attempted to install pure Arch using ChatGPT as his spiritual guide. It had been a bloodbath of hallucinated commands and destroyed partition tables. In a moment of weakness, he downloaded the Manjaro graphical installer and clicked his way to a working desktop. I offered absolutely no charity. I mocked him with the zeal of a medieval inquisitor. Later that evening, overcome with guilt, he called me. He was going to wipe the drive and attempt the true path again. He complained the official wiki was too dense, so I sent him my personal guide. An hour later, he called back in despair, staring at a black screen. He had forgotten to install the GRUB bootloader, and informed me that my guide--heavy on rambling philosophical tangents--was actually worse than the wiki. He returned to his AI companion, and they finished the installation together. The deeply unnatural relationship between my friend and his large language model is a matter I refuse to comment on further. Eventually, I went back to his house and we wiped the machine one last time. I wrote a physical list of checkpoints on a piece of paper. We moved through the ritual manually: Partitioning. Base install. Fstab. Chroot. Bootloader. NetworkManager. Every time we cleared a hurdle, I placed a tick on the paper. He finally achieved a working, pure Arch installation. His soul was saved. Which brings me back to Lemmy. A few weeks after saving my friend's soul, I saw a new user asking for a graphical user interface to install packages on Arch. Without a second thought, I typed: If you need a GUI to install packages on Arch, perhaps you should not be using Arch. My cursor blinked. When exactly did I become this person? When did I mutate into the insufferable gatekeeper standing at the threshold of the temple, demanding purity tests from the peasants? I hit reply anyway. pacman</code> is the greatest package manager ever coded, and I stand by the architectural substance of the comment. The elitist tone is something I am still unpacking in my quieter moments. Evangelism is the specific feature of religious communities that generates the maximum amount of friction with the secular world, but it is worth examining why it happens. It is the inescapable consequence of a cosmology that includes a definitive theory of the good life. If you genuinely believe that software freedom matters--that understanding the tools mediating your reality is a moral imperative--then telling your family about Linux is not enthusiasm. It is an act of deep concern. To the outsider, the Linux evangelist is offering incredibly annoying advice about a software preference. To the insider, it is a desperate moral intervention to save a loved one from the Matrix. And like all faiths, we have an eschatology. We call it the "Year of the Linux Desktop." It is the most affectionate, enduring joke in the community because it is also the most sincere, desperate hope. Every year, a prophet emerges to announce that the mainstream breakthrough is imminent. Every year, the rapture is delayed. Yet the hope is never fully abandoned. Valve’s Steam Deck has done more to advance desktop adoption in three years than a decade of screaming advocacy. The hardware compatibility nightmare is largely over. We keep building. We keep writing exhaustive documentation. Another teenager discovers the terminal. Another person wipes Windows and installs Arch. You do not abandon the faith just because the timeline slipped again; you continue because the work itself is the justification. I have watched communities close themselves off in the name of rigid orthodoxy. I have watched the pastoral function of religion get weaponised into raw political control. I have spent my life rolling my eyes at zealots. And then I found an operating system. I developed a cosmology, a theory of the good life, and a set of digital values I will absolutely refuse to compromise. I sit in my room writing scripts to automate things that do not need to be automated. I walk friends through ancient initiation rituals, checkbox by checkbox. I post arrogant, gatekeeping comments on decentralised forums and feel a rush of righteous adrenaline when I do. I have walked this world irreligious, and I have found a religion. Both of these facts are true, and I have finally made my peace with the contradiction. Use whatever distribution actually serves your needs. But read the wiki. Always read the wiki. Tmux Unknown — Thu, 09 Apr 2026 05:22:13 +0100 🔗</a>TMUX CHEATSHEET (PREFIX: C-b)</h1> 🔗</a>SERVER AND CLIENTS</h2> Command / Binding</th> Description</th></tr></thead> tmux</code></td> start new unnamed session</td></tr> tmux -L <socket> new</code></td> start server with isolated custom socket</td></tr> tmux -S /path/to/sock</code></td> start server with specific socket path</td></tr> tmux kill-server</code></td> kill server and all attached sessions</td></tr> tmux list-clients</code></td> show all connected users/clients</td></tr> tmux detach-client -a</code></td> detach all clients except the current one</td></tr> tmux suspend-client</code></td> suspend the current client</td></tr> C-b d</code></td> detach from current session</td></tr> C-b D</code></td> choose which client to detach interactively</td></tr> </tbody></table> 🔗</a>SESSION MANAGEMENT</h2> Command / Binding</th> Description</th></tr></thead> tmux new -s <name></code></td> start new named session</td></tr> tmux new -s <name> -d</code></td> start session in background (detached)</td></tr> tmux new -s <name> -c <dir></code></td> start session with specific working directory</td></tr> tmux new -t <target> -s <name></code></td> create grouped session (shared windows)</td></tr> tmux a</code></td> attach to most recently used session</td></tr> tmux a -t <name></code></td> attach to named session</td></tr> tmux a -d -t <name></code></td> detach others, then attach to session</td></tr> tmux ls</code></td> list active sessions</td></tr> tmux rename-session -t <old> <new></code></td> rename session from cli</td></tr> tmux kill-session -t <name></code></td> kill specific session</td></tr> tmux kill-session -a</code></td> kill all sessions except current</td></tr> C-b s</code></td> interactive session tree (switch/kill)</td></tr> C-b $</code></td> rename current session</td></tr> C-b (</code> / C-b )</code></td> switch to previous / next session</td></tr> C-b L</code></td> switch to last used session</td></tr> </tbody></table> 🔗</a>WINDOW MANAGEMENT</h2> Command / Binding</th> Description</th></tr></thead> C-b c</code></td> new window (inherits cwd)</td></tr> C-b ,</code></td> rename current window</td></tr> C-b n</code> / C-b p</code></td> next / previous window</td></tr> C-b 1-9</code></td> go to window by index (base 1)</td></tr> C-b w</code></td> interactive window list</td></tr> C-b &</code></td> kill window (prompts)</td></tr> C-b .</code></td> move window to new index interactively</td></tr> C-b f</code></td> find window by name</td></tr> tmux new-window -n <name></code></td> create named window from cli</td></tr> tmux select-window -t <name></code></td> switch to specific window</td></tr> tmux move-window -s <src> -t <dst></code></td> move window to new index or session</td></tr> tmux swap-window -s <1> -t <2></code></td> swap positions of two windows</td></tr> tmux link-window -s <src> -t <dst></code></td> link window so it appears in two sessions</td></tr> </tbody></table> 🔗</a>PANE MOVEMENT AND MANIPULATION</h2> Command / Binding</th> Description</th></tr></thead> C-b -</code></td> split horizontal (pane below, inherits cwd)</td></tr> C-b |</code></td> split vertical (pane right, inherits cwd)</td></tr> C-b h/j/k/l</code></td> navigate left/down/up/right</td></tr> C-b H/J/K/L</code></td> resize left/down/up/right by 5 (repeatable)</td></tr> C-b z</code></td> toggle zoom (fullscreen pane)</td></tr> C-b x</code></td> kill current pane (prompts)</td></tr> C-b !</code></td> break pane out into its own new window</td></tr> C-b {</code> / C-b }</code></td> swap pane with previous/next</td></tr> C-b Space</code></td> cycle through layout presets</td></tr> C-b q</code></td> show pane indices (press number to jump)</td></tr> C-b m</code> / C-b M</code></td> mark pane for join/swap operations / clear mark</td></tr> C-b S</code></td> toggle synchronise-panes (send keys to all)</td></tr> tmux split-window -h -p 30</code></td> split vertically, new pane takes 30% width</td></tr> tmux split-window -v -l 20</code></td> split horizontally, new pane is 20 lines high</td></tr> tmux split-window -f -h</code></td> split vertically, span full window height</td></tr> tmux join-pane -s <src> -t <dst></code></td> move pane from source window to target window</td></tr> tmux swap-pane -s <src> -t <dst></code></td> swap specific panes</td></tr> tmux select-layout main-vertical</code></td> force specific layout</td></tr> </tbody></table> 🔗</a>COPY MODE AND BUFFERS (VI + WAYLAND)</h2> Command / Binding</th> Description</th></tr></thead> C-b [</code></td> enter copy mode</td></tr> C-b PgUp</code></td> enter copy mode and scroll up</td></tr> h</code>, j</code>, k</code>, l</code></td> navigate cursor</td></tr> w</code>, b</code>, e</code></td> word forward, back, end of word</td></tr> 0</code>, $</code></td> start of line, end of line</td></tr> g</code>, G</code></td> top of buffer, bottom of buffer</td></tr> Ctrl-u</code>, Ctrl-d</code></td> page up, page down</td></tr> /</code>, ?</code></td> search forward, search backward</td></tr> n</code>, N</code></td> next match, previous match</td></tr> v</code></td> begin character selection</td></tr> V</code></td> begin line selection</td></tr> Ctrl-v</code></td> toggle block/rectangle selection</td></tr> o</code></td> swap cursor to other end of selection</td></tr> y</code></td> copy to wayland clipboard (wl-copy) & exit</td></tr> q</code> / Escape</code></td> exit copy mode</td></tr> C-b ]</code></td> paste from most recent tmux buffer</td></tr> C-b =</code></td> choose buffer interactively to paste</td></tr> C-b -</code></td> delete most recent buffer</td></tr> C-b #</code></td> list all paste buffers</td></tr> tmux show-buffer</code></td> print most recent buffer to stdout</td></tr> tmux save-buffer <file></code></td> write paste buffer to disk</td></tr> tmux set-buffer "text"</code></td> inject text into tmux buffer</td></tr> tmux delete-buffer -b <name></code></td> delete specific buffer</td></tr> </tbody></table> 🔗</a>OPTIONS AND ENVIRONMENT</h2> Command / Binding</th> Description</th></tr></thead> C-b :</code></td> enter command mode</td></tr> C-b r</code></td> reload ~/.tmux.conf</td></tr> C-b ?</code></td> list all key bindings</td></tr> tmux set -g <option> <value></code></td> set global session option</td></tr> tmux set -s <option> <value></code></td> set server option</td></tr> tmux set -w <option> <value></code></td> set window option</td></tr> tmux set -p <option> <value></code></td> set pane option</td></tr> tmux show-options -g</code></td> view all global options</td></tr> tmux show-environment</code></td> view variables passed to tmux</td></tr> tmux set-environment <var> <val></code></td> set environment variable for new panes</td></tr> </tbody></table> 🔗</a>PLUGINS (TPM, RESURRECT, CONTINUUM)</h2> Binding</th> Description</th></tr></thead> C-b I</code></td> install plugins listed in config</td></tr> C-b U</code></td> update all installed plugins</td></tr> C-b Alt-u</code></td> uninstall plugins removed from config</td></tr> C-b Ctrl-s</code></td> save session state manually (resurrect)</td></tr> C-b Ctrl-r</code></td> restore session state manually (resurrect)</td></tr> </tbody></table> 🔗</a>SCRIPTING AND AUTOMATION</h2> Command</th> Description</th></tr></thead> tmux send-keys -t <target> "cmd" Enter</code></td> send arbitrary keystrokes to pane</td></tr> tmux capture-pane -p -t <target></code></td> print pane scrollback to stdout</td></tr> tmux capture-pane -p -S -100</code></td> print last 100 lines of pane</td></tr> tmux pipe-pane -t <target> "cat > log"</code></td> stream pane output to file</td></tr> tmux display-message -p "#{session_name}"</code></td> print formatted variable to stdout</td></tr> tmux wait-for -S <channel></code></td> signal a wait channel</td></tr> tmux wait-for <channel></code></td> block script until channel signalled</td></tr> tmux if-shell "condition" "cmd"</code></td> run tmux command conditionally</td></tr> tmux set-hook -g after-new-window "cmd"</code></td> execute command automatically on event</td></tr> </tbody></table> 🔗</a>TARGET SYNTAX REFERENCE</h2> Syntax</th> Target</th></tr></thead> -t session</code></td> session by name or index</td></tr> -t session:window</code></td> specific window in session</td></tr> -t session:window.pane</code></td> specific pane in window</td></tr> -t :</code></td> current session</td></tr> -t :.</code></td> current pane</td></tr> -t :-</code> / -t :+</code></td> previous / next session</td></tr> -t :^</code> / -t :$</code></td> first / last window</td></tr> -t !</code></td> last (previously active) pane</td></tr> </tbody></table> Incus Unknown — Thu, 02 Apr 2026 08:26:14 +0100 Incus is a next-generation system container and virtual machine manager. It manages LXC containers and QEMU virtual machines through a unified command-line interface and REST API. Instances are persistent, full-system environments with their own init system, networking, and storage, distinct from the application containers that Docker and Podman manage. Incus originates from a community fork of LXD. In 2023, Canonical transferred LXD development exclusively to its own commercial organisation and removed the project from Linux Containers governance. The Linux Containers community forked the codebase as Incus under the LXC Project umbrella. Incus is FOSS, independently governed, and carries no commercial licensing terms. It represents the correct choice for operators who require system container infrastructure without dependency on Canonical's commercial roadmap. 🔗</a>1. Installation</h2> 🔗</a>Arch Linux</h3> Incus is available in the AUR. Install with an AUR helper: yay -S incus</code></pre> Or build manually: git clone [https://aur.archlinux.org/incus.git](https://aur.archlinux.org/incus.git) cd incus makepkg -si</code></pre> Enable and start the service: sudo systemctl enable --now incus sudo systemctl enable --now incus-user</code></pre> Add your user to the incus-admin</code> group: sudo usermod -aG incus-admin $USER</code></pre> Log out and back in for group membership to take effect. 🔗</a>Alpine Linux</h3> apk add incus incus-client rc-update add incusd rc-service incusd start</code></pre>🔗</a>Ubuntu / Debian</h3> Canonical's repositories ship LXD, the proprietary fork. Incus requires the Zabbly repository: curl -fsSL [https://pkgs.zabbly.com/key.asc](https://pkgs.zabbly.com/key.asc) | sudo gpg --dearmor -o /etc/apt/keyrings/zabbly.gpg echo "deb [signed-by=/etc/apt/keyrings/zabbly.gpg] [https://pkgs.zabbly.com/incus/stable](https://pkgs.zabbly.com/incus/stable) $(lsb_release -cs) main" \ | sudo tee /etc/apt/sources.list.d/zabbly-incus-stable.list sudo apt update sudo apt install incus sudo adduser $USER incus-admin</code></pre>🔗</a>Verify Installation</h3> incus --version incus info</code></pre> 🔗</a>2. Initial Configuration</h2> Run the interactive initialisation on first use: sudo incus admin init</code></pre> The wizard configures storage pools, networking, clustering, and remote access. For a minimal single-node setup, the following answers produce a functional environment: Question</th> Recommended Answer</th></tr></thead> Clustering</td> no</code></td></tr> Existing storage pool</td> no</code></td></tr> Storage backend</td> dir</code> (safe default) or zfs</code> (recommended)</td></tr> Remote access over network</td> no</code> (unless required)</td></tr> Automatic image updates</td> yes</code></td></tr> YAML output of config</td> optional</code></td></tr> </tbody></table> For production use, ZFS provides snapshots, clones, and copy-on-write storage that the dir</code> backend does not. Install ZFS before running incus admin init</code>: # Arch Linux sudo pacman -S zfs-utils sudo modprobe zfs</code></pre> 🔗</a>3. Core Architecture</h2> Component</th> Definition</th></tr></thead> Instance</td> A running container or virtual machine managed by Incus.</td></tr> Image</td> A compressed file-system used as the base for new instances.</td></tr> Profile</td> A named set of configuration options applied to instances. Multiple profiles stack.</td></tr> Storage pool</td> A named storage backend (zfs</code>, btrfs</code>, lvm</code>, dir</code>) hosting instance disks and images.</td></tr> Network</td> A managed bridge, VLAN, OVN overlay, or physical interface attached to instances.</td></tr> Project</td> A namespace isolating instances, images, profiles, and storage. Useful for multi-tenant environments.</td></tr> Remote</td> A reference to another Incus server or a public image registry.</td></tr> </tbody></table> 🔗</a>4. Images</h2> Incus instances launch from images. Images are distributed via remotes. The default remotes point to Linux Containers image servers. 🔗</a>Default Remotes</h3> incus remote list</code></pre>Default Remote</th> Content</th></tr></thead> images:</code></td> Community images (Alpine, Arch, Ubuntu, Rocky, Debian, and many others)</td></tr> ubuntu:</code></td> Official Ubuntu images</td></tr> ubuntu-daily:</code></td> Ubuntu daily builds</td></tr> </tbody></table> 🔗</a>Searching for Images</h3> incus image list images: incus image list images: alpine incus image list images: arch incus image list images: | grep -i rocky</code></pre>🔗</a>Image Properties</h3> Field</th> Meaning</th></tr></thead> ALIAS</code></td> Friendly name for the image</td></tr> FINGERPRINT</code></td> SHA-256 hash identifying the image uniquely</td></tr> PUBLIC</code></td> Whether the image is publicly accessible</td></tr> DESCRIPTION</code></td> Distribution, version, and architecture</td></tr> TYPE</code></td> CONTAINER</code> or VIRTUAL-MACHINE</code></td></tr> SIZE</code></td> Compressed image size</td></tr> UPLOAD DATE</code></td> When the image was cached locally</td></tr> </tbody></table> 🔗</a>Managing Local Images</h3> Command</th> Action</th></tr></thead> incus image list</code></td> List locally cached images</td></tr> incus image info {alias}</code></td> Show image metadata</td></tr> incus image delete {fingerprint}</code></td> Remove local image</td></tr> incus image export {alias} {path}</code></td> Export image to file</td></tr> incus image import {path} --alias {name}</code></td> Import image from file</td></tr> incus image copy images:{alias} local: --alias {name}</code></td> Copy remote image to local cache</td></tr> incus image refresh</code></td> Update cached images</td></tr> </tbody></table> 🔗</a>Publishing Instances as Images</h3> Use incus publish</code> to save a stopped container or virtual machine as a reusable image in your local image list. You can also publish from a snapshot. Command</th> Action</th></tr></thead> incus publish {instance} --alias {alias}</code></td> Create image from instance, assign alias</td></tr> incus publish {instance}/{snapshot} --alias {alias}</code></td> Create image from a snapshot</td></tr> incus publish {instance} --public --alias {alias}</code></td> Publish as a public image (visible to others)</td></tr> incus publish {instance} --expiry 30d</code></td> Set image to expire after 30 days</td></tr> incus publish {instance} --reuse</code></td> Replace existing image with same alias</td></tr> </tbody></table> # Publish a stopped container called "web-backup" as "my-website:1.0" incus publish web-backup --alias my-website:1.0 # Publish from a snapshot incus publish web-backup/snap0 --alias my-website:snap0 # List your published images incus image list</code></pre> Note: The source instance should be stopped unless you use --force</code>, but forcing may produce inconsistent file-systems. 🔗</a>Managing Image Aliases</h3> Aliases give human-friendly names to image fingerprints. Use them to reference images in incus launch</code>, incus copy</code>, etc. without typing the full hash. Command</th> Action</th></tr></thead> incus image alias list</code></td> List all aliases on the local server</td></tr> incus image alias list images:</code></td> List aliases on a remote (e.g., images:</code>)</td></tr> incus image alias create {alias} {fingerprint}</code></td> Assign an alias to an existing image</td></tr> incus image alias delete {alias}</code></td> Remove an alias</td></tr> incus image alias rename {old} {new}</code></td> Rename an existing alias</td></tr> </tbody></table> # List aliases you have defined locally incus image alias list # Create an alias "ubuntu-jammy" for image with fingerprint abc123... incus image alias create ubuntu-jammy abc123... # Delete an alias incus image alias delete my-old-alias # Rename an alias incus image alias rename my-website my-website:stable</code></pre> You can also assign aliases during incus publish</code>, incus copy</code>, or incus image import</code> using the --alias</code> flag: incus publish my-container --alias my-container:v1 incus image copy local:my-container:v1 images: --alias public-container</code></pre>🔗</a>Building Custom Images</h3> Incus accepts tarballs in its image format. The minimal structure requires a metadata.yaml</code> and a root file-system tarball. # BUILD A MINIMAL ALPINE IMAGE FOR IMPORT mkdir -p rootfs # populate rootfs with a base alpine system, then archive it tar -czf rootfs.tar.gz -C rootfs . # create metadata file cat > metadata.yaml <<EOF architecture: x86_64 creation_date: $(date +%s) properties: description: Custom Alpine minimal os: Alpine release: edge EOF # bundle metadata and rootfs into an incus image tarball tar -czf custom-alpine.tar.gz metadata.yaml rootfs.tar.gz # import image into local cache with alias incus image import custom-alpine.tar.gz --alias custom-alpine</code></pre> Git Unknown — Fri, 16 Jan 2026 23:25:51 +0100 🔗</a>1. Core Architecture & Configuration</h2> Git is a content-addressed, distributed version control system modeled as an immutable directed acyclic graph (DAG) of snapshots. 🔗</a>The Three Trees & State Transitions</h3> Every major Git operation transforms one or more of the three managed file collections: Working Tree: The local filesystem checkout where files are edited.</li> Index (Staging Area): A binary cache (.git/index</code>) representing the exact content of the next commit.</li> Repository (HEAD</code>): The immutable, committed history in the object database.</li> </ul> [Working Tree] <---(git restore <file>)--- [Index] <---(git restore --staged)--- [Repository (HEAD)] | ^ ^ +-------------(git add <file>)------------+ | | | +------------------------(git commit -a) / (git commit)-------------------------------+</code></pre>🔗</a>Essential Global Configuration (~/.gitconfig</code>)</h3> Apply these settings to enforce cryptographic integrity, accurate diffs, and automated conflict resolution: [user] name = Your Name email = you@example.com signingkey = ~/.ssh/id_ed25519.pub [core] editor = vim autocrlf = input # Convert CRLF to LF on input (Linux/macOS) pager = less -FRX fsmonitor = true # Enable filesystem event watcher integration untrackedCache = true [init] defaultBranch = main [pull] rebase = false # Default to merge on pull; set to true for linear workflows [push] default = simple autoSetupRemote = true followTags = true [fetch] prune = true # Delete tracking references for removed remote branches prunetags = true writeCommitGraph = true [diff] algorithm = histogram # Accurate diff algorithm for code block movements [merge] conflictstyle = zdiff3 # Show common ancestor (|||||||) in merge conflicts tool = vimdiff [rerere] enabled = true # Reuse Recorded Resolution for recurring conflicts autoupdate = true [gpg] format = ssh # Use SSH keys for signing [commit] gpgsign = true [tag] gpgsign = true</code></pre>🔗</a>High-Leverage Global Aliases</h3> git config --global alias.st status git config --global alias.co checkout git config --global alias.br "branch -vv" git config --global alias.lg "log --oneline --graph --decorate --all" git config --global alias.last "log -1 HEAD --stat" git config --global alias.unstage "restore --staged" git config --global alias.undo "reset --soft HEAD~1" git config --global alias.branches "for-each-ref --sort=-committerdate refs/heads/ --format='%(refname:short) %(committerdate:relative) %(authorname)'"</code></pre> 🔗</a>2. Object Model & Internals</h2> Every piece of data in Git is stored in .git/objects/</code> as one of four immutable, content-addressed object types. Object Type</th> Description</th> Internal Structure / Metadata Stored</th></tr></thead> blob</code></td> Raw file bytes.</td> Pure content. No filenames, modes, or timestamps.</td></tr> tree</code></td> Directory listing.</td> Array of entries containing file mode (100644</code>, 100755</code>, 040000</code>), name, and object SHA-1/SHA-256 hash.</td></tr> commit</code></td> Snapshot reference.</td> Root tree hash, parent commit hash(es), author/committer timestamps, commit message.</td></tr> tag</code></td> Annotated reference.</td> Hash of target object, tagger name/timestamp, tag message, GPG/SSH signature.</td></tr> </tbody></table> [Commit Object: a1b2c3] ---> [Root Tree: d4e5f6] ---> [Blob: g7h8i9] (README.md) | | | (Parent) +---> [Subtree: j0k1l2] (src/) ---> [Blob: m3n4o5] (main.py) v [Commit Object: p6q7r8]</code></pre>🔗</a>Low-Level Object Inspection (cat-file</code> & hash-object</code>)</h3> # Compute object hash from local file without writing to database git hash-object <file> # Compute hash and store the object in .git/objects/ git hash-object -w <file> # Print object type (blob, tree, commit, tag) git cat-file -t <hash> # Print raw object content / metadata git cat-file -p <hash> # Print byte size of stored object git cat-file -s <hash> # List all files and tree entries in a specific commit git ls-tree -r HEAD # Verify database integrity and connectivity git fsck --full</code></pre> 🔗</a>3. Daily Operations & Navigation</h2> 🔗</a>Staging, Committing & Inspecting State</h3> # Interactively stage diff hunks (y = stage, n = skip, s = split, e = edit) git add -p # Commit staged changes with GPG/SSH signature git commit -S -m "feat(module): descriptive subject" # Stage all tracked modified files and commit simultaneously git commit -a -m "message" # Replace tip commit with new commit object (use --no-edit to keep message) git commit --amend # View working tree and staging area status (short two-column format) git status -s # Show diff between working tree and staging area (unstaged changes) git diff # Show diff between staging area and HEAD (staged changes) git diff --staged # Show line-by-line attribution and commit hash for a specific file range git blame -L 20,40 src/main.py</code></pre>🔗</a>Branch & Reference Manipulation</h3> A branch is a 41-byte text file in .git/refs/heads/</code> containing a 40-character commit hash. # List local branches with upstream tracking and ahead/behind metrics git branch -vv # Create and switch to a new branch in a single atomic operation git switch -c <branch-name> # Switch to the previously checked-out branch (reads @{-1}) git switch - # Explicitly detach HEAD to inspect a tag or commit directly git switch --detach <hash-or-tag> # Delete a branch (fails if unmerged); use -D to force deletion git branch -d <branch-name> # Rename current branch and update tracking upstream git branch -m <old-name> <new-name></code></pre>🔗</a>Stashing</h3> Stashes are stored as 2-3 commit objects under refs/stash</code> recording the index, working tree, and untracked files. # Stash working tree and index changes with descriptive identifier git stash push -m "WIP: login feature" # Stash changes including untracked files git stash -u # Apply most recent stash and remove entry from stash list git stash pop # Apply a specific stash entry without deleting it from stash reflog git stash apply stash@{2}</code></pre> 🔗</a>4. History Manipulation & Integration</h2> 🔗</a>Merging vs. Rebasing</h3> Merge: Preserves divergent history by creating a new commit with multiple parents.</li> Rebase: Replays commits onto a new base commit, generating new commit objects with linear parentage. Never rebase commits pushed to shared remote branches.</li> </ul> # Perform a merge without fast-forwarding (creates merge commit for audit trail) git merge --no-ff <branch> # Rebase current branch onto target branch git rebase main # Rebase a range of commits, transplanting feature away from old-base onto new-base git rebase --onto <new-base> <old-base> <feature-branch> # Interactively rebase last N commits (pick, reword, edit, squash, fixup, drop, exec) git rebase -i HEAD~4 # Apply specific commit(s) from another branch as new commit objects git cherry-pick -x <hash></code></pre>🔗</a>The Three Reset Modes (git reset</code>)</h3> git reset</code> moves the current branch pointer (HEAD</code>) backward in the graph. [Commit A] <--- [Commit B] <--- [Commit C] (HEAD -> main) ^ (git reset HEAD~1) | +-----------------------------------+ | v [Mode: --soft] ---> Branch pointer moves to B. Index & Working Tree stay at C (changes staged). [Mode: --mixed] ---> Branch pointer & Index move to B. Working Tree stays at C (changes unstaged). [Mode: --hard] ---> Branch pointer, Index & Working Tree move to B. (Uncommitted changes lost!)</code></pre># Undo last commit; leave changes staged in Index git reset --soft HEAD~1 # Undo last commit; unstage changes into Working Tree (Default mode) git reset --mixed HEAD~1 # Reset branch, Index, and Working Tree to target commit (OVERWRITES WORKING TREE) git reset --hard HEAD~1 # Safely create an inverse commit that undoes the changes of target commit git revert <hash></code></pre>🔗</a>Advanced Conflict Resolution</h3> When a three-way merge conflicts, Git populates the Index with stage numbers: Stage 1 (common ancestor</code>), Stage 2 (ours</code>/HEAD</code>), and Stage 3 (theirs</code>/incoming</code>). # List all unmerged (conflicted) files in the index with stage numbers git ls-files -u # Extract specific stage versions of a conflicted file for inspection git show :1:file.py > ancestor.py git show :2:file.py > ours.py git show :3:file.py > theirs.py # Accept only our branch version or incoming branch version during resolution git checkout --ours file.py git checkout --theirs file.py</code></pre> 🔗</a>5. Distributed Workflows & Remotes</h2> A remote is a named URL reference stored in .git/config</code>. Communication relies on Refspecs formatted as +<src>:<dst></code>, which map remote references to local tracking branches in refs/remotes/<remote>/</code>. # Add a remote repository URL git remote add origin git@github.com:user/repo.git # Download objects and refs from remote; prune deleted tracking branches git fetch --prune origin # Push current branch and set upstream tracking reference in .git/config git push -u origin <branch-name> # Safely force-push: rejects push if remote branch was updated by another user git push --force-with-lease origin <branch-name> # Delete a branch on the remote server git push origin --delete <branch-name> # Push branch along with all reachable annotated tags git push --follow-tags</code></pre> 🔗</a>6. Emergency Recovery & Disaster Management</h2> Because Git commits are immutable snapshots, "destructive" operations (reset</code>, rebase</code>, branch -d</code>) merely move references away from commits. The unreferenced commit objects remain in .git/objects/</code> until garbage collection (git gc</code>) prunes them (default grace period: 30 days for unreachable reflog entries; 2 weeks for unreachable objects). [Incident Occurs] ---> 1. STOP! Do not run clean/gc. ---> 2. Locate lost hash via `git reflog` or `git fsck --lost-found`. ---> 3. Anchor object: `git branch recovery <hash>` or `git reset --hard <hash>`.</code></pre>🔗</a>Disaster Recovery Runbook</h3> # 1. Inspect Reference Movements (The Reflog) # Shows history of all HEAD movements, checkouts, resets, and rebases git reflog --all # 2. Recover from Accidental Hard Reset # Move branch pointer back to the reflog position prior to the reset git reset --hard HEAD@{1} # 3. Undo a Problematic Merge or Rebase Instantly # ORIG_HEAD records the pre-rebase / pre-merge tip of the branch git reset --hard ORIG_HEAD # 4. Recover a Deleted Branch # Find the branch's last commit hash in reflog, then re-create reference git branch <recovered-branch> <hash-from-reflog> # 5. Recover Lost Commits from Detached HEAD # Locate commit hashes generated in detached state, then anchor to a new branch git branch saved-work <detached-hash> # 6. Locate Unreachable Objects (When Reflog is Cleared/Expired) # Scans object database for orphaned commits not reachable from any ref git fsck --unreachable --no-reflogs # Write orphaned blobs and commits into .git/lost-found/commit/ and /other/ git fsck --lost-found</code></pre> 🔗</a>7. Advanced Administration & Tools</h2> 🔗</a>Worktrees (git worktree</code>)</h3> Maintain multiple simultaneous working tree checkouts attached to a single shared .git</code> object database. # Create a new working tree directory checked out to a specific branch git worktree add ../project-hotfix hotfix/1.1.1 # List active worktrees associated with the repository git worktree list # Remove worktree directory and prune tracking metadata git worktree remove ../project-hotfix</code></pre>🔗</a>Automated Debugging (git bisect</code>)</h3> Perform binary searches through DAG history in $O(\log n)$ steps to isolate regression-introducing commits. # Start bisect session and mark known bad/good boundaries git bisect start git bisect bad HEAD git bisect good v1.0 # Automate binary search using an executable test script (exit 0 = good, non-zero = bad) git bisect run ./test-regression.sh # Terminate bisect session and restore original HEAD checkout git bisect reset</code></pre>🔗</a>Large Scale History Rewriting (git filter-repo</code>)</h3> Requires Python tool: pip install git-filter-repo</code>. Replaces legacy filter-branch</code>. # Purge a sensitive file or secret from every commit in repository history git filter-repo --path secret.env --invert-paths # Extract a specific subdirectory into an independent, isolated repository git filter-repo --subdirectory-filter services/auth</code></pre>🔗</a>Monorepo & Performance Optimization</h3> # Perform a partial clone: download trees/commits, defer blob fetches until access git clone --filter=blob:none [https://github.com/org/repo.git](https://github.com/org/repo.git) # Enable sparse checkout in high-speed cone mode (limits working tree files) git sparse-checkout init --cone git sparse-checkout set services/api # Generate commit-graph and multi-pack index (MIDX) to accelerate DAG traversals git commit-graph write --reachable git multi-pack-index write # Repack loose objects into a single optimized packfile with reachability bitmaps git repack -a -d --write-bitmap-index # Schedule automated background repository optimization tasks (Git 2.29+) git maintenance start</code></pre> Filen Unknown — Fri, 16 Jan 2026 22:28:33 +0100 🔗</a>1. Installation & Environment</h2> # Install CLI (places binary in PATH) curl -sL [https://filen.io/cli.sh](https://filen.io/cli.sh) | bash # Verify installation filen --version filen --help # Version management filen install latest filen install canary filen install <version> # Override data directory ($XDG_CONFIG_HOME/filen-cli or ~/.config/filen-cli by default) filen --data-dir /path/to/dir <cmd> FILEN_CLI_DATA_DIR=/path/to/dir filen <cmd></code></pre> 🔗</a>2. Authentication</h2> # Interactive login filen # CLI flags authentication filen --email <email> --password <password> --two-factor-code <2fa> # Environment variable authentication FILEN_EMAIL=<email> FILEN_PASSWORD=<pwd> FILEN_2FA_CODE=<2fa> filen # Account management filen whoami # Show authenticated account filen logout # Remove saved credentials filen export-auth-config # Export unencrypted auth config (avoids rate limits in clustered setups) filen export-api-key # Export API key for Filen Rclone integration</code></pre> 🔗</a>3. Remote Filesystem & Metadata</h2> # Listing and inspection filen ls # List root directory filen ls /Documents # List specific remote path filen ls --long /Documents # List with detailed metadata (size, modified date) filen stat /remote/file.txt # Show metadata for a file or directory filen statfs # Show cloud drive storage information # Reading file contents filen cat /remote/file.txt # Print entire file contents filen head /remote/file.txt -n 20 # Print first 20 lines filen tail /remote/file.txt -n 20 # Print last 20 lines # Drive navigation filen recents # View recently used files and directories filen favorites # View all favourited items</code></pre> 🔗</a>4. Transfer Operations</h2> # Uploading filen upload localfile.txt /remote/path/ # Upload file to remote directory filen upload report.pdf /Documents/Q1-Report.pdf # Upload and rename remote file filen upload .log /Logs/ # Upload multiple files via glob pattern filen write /remote/notes.txt "some content here" # Write plain text directly to remote file # Downloading filen download /remote/file.txt ./localfile.txt # Download single remote file filen download /Backups/project ./local-project # Download entire remote directory filen download /Documents/notes.md . # Download to current working directory</code></pre> 🔗</a>5. File Management & Notes</h2> # Directory and file manipulation filen mkdir /remote/newdir # Create remote directory filen rm /remote/file.txt # Move file or directory to trash filen rm /remote/file.txt --no-trash # Permanently delete (bypasses trash) filen mv /remote/old-name.txt /remote/new-name.txt # Move or rename file/directory filen cp /remote/source.txt /remote/backup.txt # Copy file or directory # Item states and local editing filen favorite /remote/path # Favourite an item filen unfavorite /remote/path # Unfavourite an item filen open /remote/file.txt # Open remote file locally filen edit /remote/file.txt # Edit locally (re-uploads on save and close) filen export-notes ~/filen-notes # Export all notes to local directory</code></pre> 🔗</a>6. Synchronisation</h2> 🔗</a>Modes & Abbreviations</h3> Mode</th> Abbreviation</th> Behaviour</th></tr></thead> twoWay</code></td> tw</code></td> Changes on either side propagate to the other</td></tr> localToCloud</code></td> ltc</code></td> Local changes pushed to cloud; cloud-only files untouched</td></tr> localBackup</code></td> lb</code></td> Local to cloud; remote deletions not propagated</td></tr> cloudToLocal</code></td> ctl</code></td> Cloud changes pulled to local; local-only files untouched</td></tr> cloudBackup</code></td> cb</code></td> Cloud to local; local deletions not propagated</td></tr> </tbody></table> # CLI execution filen sync /local/path:/cloud/path # Basic pair (defaults to two-way) filen sync /local1:twoWay:/cloud1 /local2:ltc:/cloud2 # Explicit modes and multiple pairs filen sync /local/path:/cloud/path --continuous # Continuous loop synchronisation filen sync /local/path:/cloud/path --disable-local-trash # Disable local trash during sync # Configured sync pairs (~/.config/filen-cli/syncPairs.json) filen sync # Run all configured pairs from default JSON filen sync docs # Run specific configured pair by alias filen sync /path/to/custom-pairs.json # Run pairs from custom JSON configuration</code></pre>🔗</a>Sync Pairs Configuration (~/.config/filen-cli/syncPairs.json</code>)</h3> [ { "local": "/home/user/Documents", "remote": "/Backups/Documents", "syncMode": "localToCloud", "alias": "docs", "disableLocalTrash": false, "excludeDotFiles": true, "ignore": [".tmp", "node_modules/"] } ]</code></pre> 🔗</a>7. Mounting & Servers</h2> # Network Drive Mount (Requires FUSE3: pacman -S fuse3 / apt install fuse3) filen mount # Mount at default path (/tmp/filen on Linux) filen mount /mnt/filen # Mount at custom path fusermount3 -u /mnt/filen # Unmount filesystem (Linux) # WebDAV Server (Single-User Mode) filen webdav --w-user <u?> --w-password <p?> # Default server (0.0.0.0:80/443) filen webdav --w-user <u?> --w-password <p?> --w-https # HTTPS with self-signed certificate filen webdav --w-user <u?> --w-password <p?> --w-threads 0 # Enable clustering (0 = one thread per core) filen webdav --w-user <u?> --w-password <p?> --w-auth-scheme basic # Auth scheme: basic or digest # WebDAV Server (Proxy Mode - Multi-User) filen webdav-proxy --w-port 1900 # Users authenticate with own credentials # Password format: password=secret&twoFactorAuthentication=<OTP_OR_RECOVERY_CODE> # S3-Compatible Server (Set client s3ForcePathStyle=true and region="filen") filen s3 --s3-access-key-id <id> --s3-secret-access-key <key> # Start S3 server (0.0.0.0:80/443) filen s3 --s3-access-key-id <id> --s3-secret-access-key <key> --s3-https # HTTPS S3 server filen s3 --s3-access-key-id <id> --s3-secret-access-key <key> --s3-threads 0 # Clustered S3 server</code></pre> 🔗</a>8. Trash & Public Links</h2> # Trash management filen trash # List all trash items filen trash restore # Restore a specific trash item filen trash delete # Permanently delete a specific trash item filen trash empty # Permanently delete all trash items # Public links filen links # List all public links filen links /remote/path # Create, view, edit, or delete a link for a path</code></pre> 🔗</a>9. Updates & Execution Flags</h2> # Update behaviour flags filen --force-update <cmd> # Force check (bypasses 10-minute cache) filen --skip-update <cmd> # Skip update check entirely filen --auto-update <cmd> # Update binary without confirmation prompt # Canary channel filen canary # Toggle canary release channel</code></pre> 🔗</a>10. Automation & Scripting</h2> 🔗</a>Daily Backup Script</h3> #!/bin/bash set -e TIMESTAMP=$(date +%Y-%m-%d) LOCAL_PATH="$HOME/Documents" REMOTE_PATH="/Backups/Documents/$TIMESTAMP" echo "Starting Filen backup: $TIMESTAMP" filen sync "$LOCAL_PATH:localToCloud:$REMOTE_PATH" echo "Backup complete."</code></pre>🔗</a>Systemd Continuous Sync Service (~/.config/systemd/user/filen-sync.service</code>)</h3> [Unit] Description=Filen Cloud Sync After=network-online.target [Service] Type=simple ExecStart=/usr/bin/env filen sync %h/Documents:localToCloud:/Backups/Documents --continuous Restart=on-failure RestartSec=30 [Install] WantedBy=default.target</code></pre>🔗</a>Systemd Timer (~/.config/systemd/user/filen-sync.timer</code>)</h3> [Unit] Description=Run Filen Sync every 6 hours [Timer] OnBootSec=5min OnUnitActiveSec=6h Persistent=true [Install] WantedBy=timers.target</code></pre># Enable and start systemd automation systemctl --user daemon-reload systemctl --user enable --now filen-sync.timer systemctl --user status filen-sync.timer</code></pre>

🔗</a>Favourite Games</h2>

Final Fantasy</em> (I, II, IV, V, VII)</li>
Fire Emblem</em> (All entries up to Three Houses</em>)</li>
Persona 3</em></li>
Age of Empires</em></li>
Hogwarts Legacy</em></li> </ul> 🔗</a>Favourite Board Games</h2>

Chess</em></li>
Nonogram</em></li> </ul>

🔗</a>Favourite Board Games</h2>

Chess</em></li>
Nonogram</em></li> </ul>

Vim

Archinstall

Linux is a Religion

Tmux

Incus

Git

Filen

Daesorin

UFW

Algorithmic panic and the aesthetics of using arch

Automating Self-Hosted Backups with Tar, Age, and Systemd

About

Package Categories and References

Daesorin

UFW

Algorithmic panic and the aesthetics of using arch

Automating Self-Hosted Backups with Tar, Age, and Systemd

About

🔗</a>Certifications</h2> CompTIA Linux+ (In Progress)</li> </ul> 🔗</a>Interests</h2> Technology</li> Privacy</li> Open Source</li>

🔗</a>Interests</h2> Technology</li> Privacy</li> Open Source</li>

🔗</a>Hobbies</h2> Reading</li>

🔗</a>Favourite Movies</h2> 12 Angry Men</em></li> All the President’s Men</em></li> Children of Men</em></li> Solaris</em></li> Stalker</em></li>

🔗</a>Favourite Graphic Novels</h2> 20th Century Boys</em></li> Billy Bat</em></li> Dai Dark</em></li> Dorohedoro</em></li> Homunculus</em></li> Monster</em></li> Nausicaä of the Valley of the Wind</em></li> Pluto</em></li> Vagabond</em></li>

🔗</a>Favourite Shows</h2> Ergo Proxy</em></li> Fullmetal Alchemist</em></li> Line of Duty</em></li> Mr. Robot</em></li> One Piece</em></li> Paranoia Agent</em></li> Psycho-Pass</em></li> Severance</em></li> Texhnolyze</em></li> True Detective</em></li> Utopia</em></li>

🔗</a>Favourite Games</h2> Final Fantasy</em> (I, II, IV, V, VII)</li> Fire Emblem</em> (All entries up to Three Houses</em>)</li> Persona 3</em></li> Age of Empires</em></li>

Package Categories and References

Vim

🔗</a>Favourite Games</h2>

Final Fantasy</em> (I, II, IV, V, VII)</li>
Fire Emblem</em> (All entries up to Three Houses</em>)</li>
Persona 3</em></li>
Age of Empires</em></li>
Hogwarts Legacy</em></li> </ul> 🔗</a>Favourite Board Games</h2>

Chess</em></li>
Nonogram</em></li> </ul>