User:Pointone/Overviews

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

Implemented

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]

Feature comparison

Note:
  • Boot loaders only need to support the file system on which kernel and initramfs reside (the file system of the partition on which /boot is located).
  • As GPT is part of the UEFI specification, all UEFI boot loaders support GPT disks. GPT on BIOS systems is possible, using either "hybrid booting", or the new GPT-only protocol. This protocol may however cause issues with certain BIOS implementations; see rodbooks for details.
  • Encryption mentioned in file system support is filesystem-level encryption, it has no bearing on block-level encryption.

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: Fill in the unknowns. (Discuss in User talk:Pointone/Overviews#)
Name Firmware Multi-boot File systems Notes
BIOS UEFI Btrfs ext4 ReiserFS v3 VFAT XFS
GRUB Yes Yes Yes Yes Yes Yes Yes Yes On BIOS/GPT configuration requires GRUB BIOS boot partition.
systemd-boot No Yes Yes No No No Yes No Cannot launch binaries from partitions other than ESP.
syslinux Yes Partial Partial without: multi-device volumes, compression, encryption without: 64bit feature, encryption No Yes v4 on MBR only No support for certain file system features [2]
EFISTUB No Yes N/A N/A N/A N/A N/A N/A
rEFInd No Yes Yes without encryption without: 64bit feature, encryption without tail-packing feature Yes No
Clover emulates UEFI Yes Yes No Unknown No Yes No Main target audience is Hackintosh users.
LILO Yes No Unknown Unknown Unknown Unknown Unknown MBR only [3] Deprecated. Does not support GUID Partition Table.
GRUB Legacy Yes No Yes No No Yes Yes v4 only Deprecated. Does not support GUID Partition Table.
NeoGRUB Yes No Yes Unknown Unknown Unknown Unknown Unknown

See also

Graphical user interface

Category:X Server

Networking

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.

Ideas

Common applications

System recovery

Sound