Arch Linux

Arch Linux [ ɑ ː rtʃ linʊks ] is a i686 and AMD64 - optimized Linux distribution according to the KISS principle. Because of this minimalist approach Arch Linux is seen as a distribution for advanced users, there is waived graphical installation and configuration aids in favor of simplicity. Arch Linux was introduced in early 2001 by Judd Vinet, inspired by Crux and BSD. On 1 October 2007 Vinet gave his resignation as Director of Projects, and was succeeded by Aaron Griffin.

Arch Linux is from an approximately 25-member core team and helpers from the growing community, so-called " Trusted Users", further developed. All distribution-specific developments are released under the GPL. In Germany, the distribution gained special notoriety as a supplement of the magazine Linux user.

• 2.1 Pacman
• 2.2 repositories
• 2.3 Repository Safety
• 2.4 Arch Build System (ABS )
• 2.5 Arch User Repository

• 4.1 Inactive Projects

Special features of the distribution

Arch Linux has been developed completely new with Linux From Scratch, but is based on CRUX and other distributions. For Arch, the construction of a Slackware Linux respectively a BSD system with a Debian -like package management and build system of Gentoo was combined. Similar to the Gentoo releases are only snapshots from the current level of development ( "Rolling Release ").

The default init system systemd is used also when reinstalling since October 2012. Configuration utilities for the installation and setup of the base system and for application and server programs do not exist, instead, refer to the original documentation and configuration, so that general howtos and instructions can be used.

Philosophy

Arch Linux was developed as a " base operating system for advanced users ." The philosophy of Arch Linux is based on the following two points:

• Easy to hold, not overloaded. Follow the KISS principle.
• No GUI Tools for configuration use that hide the actual events from the user.

Package Management

Arch Linux is designed for the use of binary packages. Basically, packages are structured with the proprietary package manager Pacman, in addition, with the Arch Build System (ABS ) creates new packages for software that exists only in the source code.

Pacman

Pacman is a package manager, which was developed specifically for Arch Linux, but is also used in other Linux distributions. Pacman can resolve dependencies and automatically download all the necessary packages from the Arch repositories, install, update and remove, similar to Debian's APT. The special thing about Pacman is its consistent application even with local sources present mostly as the Arch Build System (ABS ) Created Packages.

As a critical point in terms of the safety of the package distribution infrastructure, the lack of integrity check of the package metadata was considered. While it existed checksums of individual packages, these metadata were not provided with a digital signature, which is why malicious modifications to packages could not be found. This was addressed by a contribution of the renowned online magazine LWN.net in March 2011. Since January 16, 2012 supports pacman, in version 4.0, now officially the verification of digitally signed packages.

Repositories

The official Arch Linux packages are managed in four software repositories:

• Core contains packets which are required for the operation of the base system.
• Extra contains packages that extend the functionality, eg desktop environments, database systems, etc.
• Community contains packages that are serviced by the community, so the " Trusted Users".
• Multilib contains packages that allow on an AMD64 system run i686 native programs.

The main part of the development takes place in the Testing repositories instead of before the packages are moved to the stable repositories:

• Testing, testing and community - multilib - testing contained packages that might be defective and need to be tested.

It must transfer of packages that move from testing for core, previously approved by several developers. Their respective developers are responsible for packages in the other repositories.

In addition, third-party repositories can be integrated, which offer customized or newer versions of the software packages.

Repository safety

Up to version 4.0.0 of the package manager Pacman lacked the support for signed packages. Packages and metadata have not been reviewed by Pacman during the download process on authenticity. Pacman 4 allowed the verification of the package database and packages, but this was disabled by default. In November 2011, the package - signing was mandatory for new packages and since March 21, 2012 every official package is signed.

In June 2012, the review of the Package signing was officially and is enabled by default after installation.

Arch Build System (ABS )

The Arch Build System is a ports -like package management. Arch uses in each case a text file called PKGBUILD, containing, among other things, the instructions to download and configure the respective programs. The user can adjust with this file, the programs contained in the package manager of Arch his own needs by, for example, inserting a patch. The makepkg program executes these instructions and compiled and / or prepare packages for installation by pacman. An Arch package is no longer needed as a compressed tar archive that contains the files to install one file (. Pkginfo ) with all metadata that Pacman for handling packages, basically.

In addition, ABS offers the opportunity to own compiler flags to rebuild the entire system.

Arch User Repository

In addition to the repositories provide users in the Arch User Repository ( AUR) homemade PKGBUILD scripts for packages that are not included in the repositories. The PKGBUILD scripts simplify building packages from source by explicitly listing and checking of dependencies and configure the installation to match the Arch architecture. Because of the potential security risks, this PKGBUILD scripts will never be automatically available in the official repositories.

The Arch User Repository provides the community packages that are not included in the official repositories. Reasons for this are:

• Licensing issues: software may not be distributed by third parties, you may however use free of charge can be included in the Arch User Repository, this case, only a shell script is hosted on the Arch site that downloads the latest version of the software. Example of this is proprietary freeware such as Google Earth and Real Player.
• Changes in official packages: The Arch User Repository also contains many variations of packages from the official repositories, and beta versions of software, which is included in the repositories as stable releases.
• Rarity of the software: Some new or rarely used programs (yet ) have not been added to the official repositories.

Versions

Unlike other major distributions such as Ubuntu and Fedora, Arch Linux does not plan his versions of certain data, but uses a "rolling release " system. The package management allows users to keep their systems up to date. Instead of moving the user between discrete versions, Arch Linux releases are simply snapshots of the current set of packages, sometimes with revised installation software. Therefore, it makes no difference from which release Arch was installed when you installed updates. In fact, some members of the Arch forums proudly display the age of their installation.

On July 22, 2012 it was announced that the installation program will be replaced by a set of simple scripts to avoid delays in the release cycle. It is now beginning of each month a new image offered, which carries the release date as the version in the file name; For example 01/04/2013 for the image that appeared on January 4, 2013.

Derivatives

There are several distributions that are based either directly on Arch Linux or utilize its programs.

• Antergos - continuation of the Arch derivative Cinnarch and comes standard therefore with the desktop Gnome; However, the user can also opt for Cinnamon, Xfce or Razor -qt during installation.

• Arch BSD, a FreeBSD derivative, which uses the package management software from Arch.

• ArchBang - variant that uses Openbox and is optimized for high speed. Because - like all Arch -based derivatives - is compiled for i686, it is not suitable despite Openbox necessarily for CPUs that were produced before 1998, but for netbooks or nettops. Unlike Arch ArchBang provides a preconfigured, based on Openbox desktop environment.

• ArchLinuxARM - one based on Arch Linux distribution for various small computer with ARMv5, ARMv6 and ARMv7. Such as the BeagleBoard, PandaBoard, Raspberry Pi or the TrimSlice. The result is the distribution by the teams of ArchMobile and plug Apps.

• BBQLinux - distribution, compile and develop the specialized of Android.

• Bridge Linux - provides preconfigured systems with Xfce, KDE, Gnome and LXDE.

• Chakra - distribution that consistently focuses on Qt programs. Chakra offers a live CD with a graphical installer and is addressed to users who prefer to use graphical tools. On May 22, 2010, the developer announced that they are planning to want to solve in the future of Arch Linux base system.

• Frugalware - one originally based on Slackware Linux distribution that uses the Pacman package manager. It will be offered at intervals of 6 months stable snapshots.

• Manjaro - a very young Arch Linux derivative with its own installer and its own end for package management, which is aimed at both beginners and advanced users. As a standard surface Xfce is provided, but also Gnome, KDE and Cinnamon are available. Manjaro Linux uses its own package repositories that serve to provide stable snapshots of the Arch Linux repositories. This Manjaro is not quite as up to date as Arch Linux.

• Parabola GNU / Linux - one based on Arch Linux distribution that uses only absolutely free software (comparable to dyne: bolic or Ututo ). As such, it is guided by the Free Software Foundation in a list of corresponding distributions. Parabola GNU / Linux is available for i686 and AMD64.

• Arch Hurd - replaces the Linux kernel with GNU Hurd.

Inactive projects

• ArchMobile - port for (mobile) ARM devices, mainly for Openmoko NeoFreeRunner but also the Beagle Board and other devices are supported. Is gone up in ArchLinuxARM,

• ArchLinuxPPC - Arch Linux port for the PowerPC architecture.

• ArchServer - to put on Arch Linux based distribution with the goal of stable releases are available which are not rolling release based. Thus, the use of Arch Linux to be more reliable on servers.

• Cinnarch - was delivered with the familiar Linux Mint Cinnamon Desktop interface. The difficulties in adapting to the Cinnamon fast update cycles of Arch Linux resulted in a switch to Gnome and brought to rename the project in Antergos with it.

• ConnochaetOS - formerly DeLi Linux is a Linux distribution that was designed for older hardware and based on free software.

• KahelOS - one based on Arch Linux distribution that uses Gnome as the default desktop environment.

• Larch - less a derivative of ArchLinux, but rather a powerful tool, with which it is possible to easily create a live Arch Linux system. The tool consists of a collection of scripts that can be controlled via an intuitive Python GUI however. Thus larch not only allows the creation of custom ArchLinux live systems, but, as these can also be installed, it can be used as a starting point for creating ArchLinux derivatives. Larch was abandoned because Arch Linux support on any longer, but this has represented an essential component for Larch.

• Lowarch - one for the i486 and i586 architectures translated and therefore specially designed for older hardware Arch Linux derivative.

• Plug apps - based on Arch Linux distribution for Plug Computer. By natively compiled packages they went very quickly even with limited resources. It was abandoned in favor of Arch Linux arm.