From ArchWiki
< User:Pointone
Revision as of 01:01, 23 November 2013 by Kynikos (Talk | contribs) (Implemented: sorry, last time I edit here, again see Help_talk:Style/Article_summary_templates#Deprecation_of_summaries_and_overviews)

Jump to: navigation, search


Access control

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.

Boot process

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.

Note: Loading Microcode updates requires adjustments in boot loader configuration. [1]

Partition table support

Name BIOS UEFI Dual-boot Notes
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.
syslinux Yes Partial Partial
rEFInd No Yes Yes
Clover No Yes Yes
LILO Yes No Unknown
GRUB Legacy Yes No Yes
NeoGRUB Yes No Yes

See also

Graphical user interface

Category:X Server


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.

Package management

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.


Common applications

System recovery