Users and groups are used on GNU/Linux for access control. The superuser (root) has complete access to the operating system and its configuration; it is intended for administrative use only. Unprivileged users can use the su and sudo programs for controlled privilege escalation.
In order to boot Arch Linux, a Linux-capable boot loader must be installed to the Master Boot Record or the GUID Partition Table. It is the first piece of software started by the BIOS or UEFI. It is responsible for loading the kernel with the wanted kernel parameters, and initial RAM disk before initiating the boot process.
Partition table support
|GRUB||Yes||Yes||Yes||On BIOS/GPT configuration requires GRUB BIOS boot partition.|
|systemd-boot||No||Yes||Yes||Cannot launch binaries from partitions other than ESP.|
- Rod Smith - Managing EFI Boot Loaders for Linux
- Rod Smith - rEFInd, a fork or rEFIt
- Linux Kernel Documentation on EFISTUB
- Linux Kernel EFISTUB Git Commit
- Rod Smith's page on EFISTUB
- rEFInd Documentation for booting EFISTUB Kernels
Graphical user interface
Arch Linux provides netctl for network management.
netctl supports wired connections on desktops and servers, as well as wireless setups and roaming for mobile users, facilitating easy management of network profiles. For alternatives see Network managers.
Packages in Arch Linux are built using makepkg and a custom build script for each package (known as a PKGBUILD). Once packaged, software can be installed and managed with pacman. PKGBUILDs for software in the official repositories are available from the ABS tree; thousands more are available from the (unsupported) Arch User Repository.
- Web Browsers (idea)
- Multimedia in Arch Linux (could do without "in Arch Linux")
- VirtualBox, QEMU, VMware (or a separate "virtualization" overview?)