Arch Linux is a powerful, minimalist, and rolling-release distribution of Linux that appeals to advanced users and system administrators. While it is known for its flexibility and customization, it also comes with a steeper learning curve, particularly in the installation process. Unlike many other Linux distributions that provide graphical installers or automated setup tools, Arch Linux offers a command-line-driven installation process that requires users to manually configure key system components.
This guide provides a detailed, step-by-step walkthrough of installing Arch Linux using the official installation image and standard tools. Based on official documentation and verified user guides, it is tailored for U.S.-based users and IT professionals who are interested in deploying a custom, tailored Linux environment.
Overview of the Installation Process
The installation of Arch Linux involves several key steps, including downloading the ISO image, creating a bootable USB drive, configuring hardware settings, partitioning the disk, installing the core system, setting up a bootloader, and optionally installing a desktop environment. The process is fully text-based, and users are expected to have a working knowledge of Linux commands and system configuration.
The installation is supported on any x86_64-compatible machine, and a minimum of 512 MiB RAM is recommended for the live environment. Additionally, a working internet connection is required throughout the installation process to fetch packages from the Arch Linux repositories.
Official documentation and community-maintained guides are the primary sources of information for installation steps. While some guides provide additional tips and tricks—such as changing the terminal font size—these are not mandatory and are included to enhance user experience.
Step 1: Download the Arch Linux ISO
The installation begins by obtaining the official Arch Linux ISO file from the Arch Linux download page. This page provides multiple download options, including direct HTTP downloads, torrent files, and netboot images. For most users, the standard ISO file is the best choice.
To ensure a fast and reliable download, users are advised to select a mirror that is geographically closer to their location. After downloading the ISO, it is recommended to verify its authenticity using checksums to confirm the file's integrity and security.
Step 2: Create a Bootable USB Drive
Once the ISO file is downloaded, the next step is to create a bootable USB drive. This is typically done using the dd command in a Linux or macOS terminal, or using tools such as Rufus or Balena Etcher on Windows systems.
The dd command allows for direct writing of the ISO to a USB drive, bypassing file systems and ensuring the drive is bootable. The basic syntax is as follows:
dd if=archlinux-YYYY.MM.DD-x86_64.iso of=/dev/sdX bs=4M status=progress
Replace /dev/sdX with the appropriate device identifier for your USB drive. It is crucial to verify the correct device path before proceeding, as an incorrect command could overwrite other storage devices.
Step 3: Boot into the Live Environment
After the USB drive is prepared, insert it into the target machine and restart the system. The BIOS or UEFI firmware must be configured to boot from the USB drive rather than the internal hard drive.
In some systems, Secure Boot must be disabled in the firmware settings to allow booting from the live USB. This is especially true for UEFI-based systems. Once the system boots, it will load the Arch Linux live environment, which provides a minimal root shell for the installation process.
At this point, the system is ready for the next steps, which include network configuration, disk partitioning, and system installation.
Step 4: Configure the Network Connection
A working internet connection is essential for the installation process, as packages are fetched from Arch Linux's remote repositories. To ensure connectivity, users can check the status of their network interface using the ip or ping command.
For wired connections, the live environment typically detects and configures the network automatically. However, for wireless connections, users may need to use the iwctl command to connect to a Wi-Fi network. This involves scanning for available networks, connecting to the desired one, and providing the necessary credentials.
Once connected, users should verify the connection by pinging an external server, such as ping archlinux.org. A successful ping confirms that the system can access the internet and retrieve required packages.
Step 5: Partition the Disk
Partitioning the disk is one of the most critical steps in the installation process. Users must decide on the layout of their partitions, including the root partition (/), swap space (optional), and potentially a separate home partition (/home).
This step is typically performed using tools like fdisk, cfdisk, or parted. For UEFI-based systems, a small EFI System Partition (ESP) must also be created and formatted as FAT32. This partition is required for the bootloader.
After the partitions are created, they must be formatted with appropriate file systems. Common choices include ext4 for the root and home partitions, and swap for the swap space.
Once the partitions are created and formatted, they must be mounted to the appropriate mount points using the mount command. The root partition is typically mounted to /mnt, while the EFI partition is mounted to /mnt/boot or /mnt/efi, depending on the system configuration.
Step 6: Install the Base System
With the disk partitions in place, the next step is to install the core Arch Linux system. This is done using the pacstrap command, which installs the base system along with essential packages such as the kernel, system utilities, and basic development tools.
The command to install the base system is as follows:
pacstrap /mnt base base-devel
This command installs the base and base-devel packages, which form the foundation of the Arch system. Additional packages can be added depending on the user's needs, such as a window manager, desktop environment, or development tools.
Once the installation is complete, the system must be configured further, including setting up the filesystem table (fstab) and configuring the bootloader.
Step 7: Configure the Filesystem Table (fstab)
After the base system is installed, the next step is to generate the fstab file, which defines how disk partitions and logical volumes are mounted at boot time. This file is created using the genfstab command, which automatically detects the mounted partitions and writes the appropriate entries.
The command to generate the fstab file is:
genfstab -U /mnt >> /mnt/etc/fstab
This command appends the generated entries to the fstab file located in the new system's /etc directory. It is important to verify the contents of the file to ensure that all partitions are correctly listed and that there are no errors or duplicate entries.
Step 8: Chroot into the New System
With the fstab file in place, the next step is to chroot into the new system. This allows the user to continue the installation process from within the context of the new system, rather than the live environment.
The command to chroot into the new system is:
arch-chroot /mnt
Once inside the chroot environment, the user can proceed with further configuration steps, including setting the system's time zone, locale, hostname, and bootloader configuration.
Step 9: Set System Time and Localization
Inside the chroot environment, the first task is to set the system's time zone and synchronize the hardware clock. This is done using the ln command to create a symbolic link to the appropriate time zone file:
ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime
Next, the hardware clock is set to use UTC time, which is the standard for most systems:
hwclock --systohc
Localization settings are configured by editing the /etc/locale.gen file and enabling the desired locales. Once the file is updated, the locale-gen command is used to generate the locales:
locale-gen
The default locale is set using the /etc/locale.conf file, where the LANG variable is defined:
LANG=en_US.UTF-8
Step 10: Configure the Hostname and Hosts File
The hostname of the system is defined in the /etc/hostname file. A simple text editor such as nano can be used to create or modify this file:
nano /etc/hostname
Inside the file, the desired hostname—such as arch-pc—is written. After saving the file, the /etc/hosts file must be updated to include the hostname:
127.0.0.1 localhost
::1 localhost
127.0.1.1 arch-pc.local domain arch-pc
This allows the system to resolve its own hostname and domain correctly.
Step 11: Install and Configure the Bootloader
The final major step in the installation process is setting up the bootloader. Arch Linux supports several bootloaders, but systemd-boot is a recommended option for UEFI-based systems.
To install systemd-boot, the following command is used:
bootctl install
This command installs the bootloader to the EFI System Partition and creates the necessary configuration files. A configuration file must be created at /boot/loader/entries/arch.conf to define the default boot entry:
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=PARTUUID=uuid-here rw
The PARTUUID should be replaced with the actual UUID of the root partition, which can be obtained using the blkid command.
Once the bootloader is configured, the system is ready to be rebooted.
Step 12: Reboot and Remove the Live USB
After the installation is complete, the system is rebooted using the reboot command. Once the system restarts, it should boot into the newly installed Arch Linux system without requiring the live USB.
Before removing the USB drive, users should ensure that the system boots correctly and that all necessary services and configurations are in place.
Step 13: Install a Desktop Environment (Optional)
While Arch Linux is a minimal system by design, many users prefer to install a desktop environment for a more user-friendly experience. Popular choices include GNOME, KDE Plasma, XFCE4, and i3 Window Manager.
For example, to install XFCE4 and i3, the following command can be used:
pacman -S xfce4 i3
After installation, users can configure their display manager (such as lightdm or sddm) and set the default session to use the installed desktop environment.
Step 14: Create a Regular User Account
For security reasons, it is recommended to create a regular user account rather than relying solely on the root account. This is done using the useradd command:
useradd -m -g users -G wheel -s /bin/bash username
A password can be set for the new user using the passwd command:
passwd username
To grant the user sudo privileges, the sudo package must be installed, and the user must be added to the wheel group:
pacman -S sudo
EDITOR=nano visudo
Inside the sudoers file, the line %wheel ALL=(ALL) ALL should be uncommented to allow members of the wheel group to use sudo.
Step 15: Final System Setup and Reboot
After the installation is complete and all desired packages and configurations are in place, the system can be rebooted one final time to ensure everything works as expected. The user can then log in using the newly created account and begin using the system.
Conclusion
Installing Arch Linux requires a solid understanding of Linux fundamentals and system configuration. However, with the help of official documentation and community guides, the process can be manageable for even intermediate users. The manual setup of partitions, bootloaders, and system configurations allows for a highly customized and optimized system.
This guide has walked through each step of the installation process, from downloading the ISO to setting up a desktop environment and user account. By following these steps, users can build a tailored Linux system that meets their specific needs and preferences.
For users who prefer a more guided approach, the archinstall script provides an automated installation option. However, it is still in experimental stages and may not be suitable for all use cases.
Ultimately, the installation of Arch Linux is a rewarding experience that gives users full control over their system and deepens their understanding of Linux internals.