Jump to content

Arch Linux: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
minor fixes
DorganBot (talk | contribs)
15,527 edits
m r2.7.3) (Robot: Modifying sr:Arč
Line 218: Line 218:
[[sk:Arch Linux]]
[[sk:Arch Linux]]
[[sl:Arch Linux]]
[[sl:Arch Linux]]
[[sr:Arch]]
[[sr:Arč]]
[[sh:Arch Linux]]
[[sh:Arch Linux]]
[[fi:Arch Linux]]
[[fi:Arch Linux]]

Revision as of 22:09, 5 May 2012

Not to be confused with Ark Linux.
Arch Linux
Arch Linux logo
DeveloperAaron Griffin and team[1]
OS familyUnix-like
Working stateCurrent
Source modelFree and open source software
Initial releaseMarch 11, 2002; 22 years ago (2002-03-11)
Latest release(Rolling release) / Installation CD 2011.08.19
Repository
Marketing targetGeneral purpose
Update methodPacman
Package managerPacman
Platformsi686, x86-64
Kernel typeMonolithic (Linux)
UserlandGNU
Default
user interface		Bash
LicenseVarious[2]
Official websitewww.archlinux.org

Arch Linux (or Arch, pronounced /ˈɑrtʃ/[3]) is an independently developed, Linux-based operating system for i686 and x86-64 computers.[4] It is composed predominantly of free and open source software,[5] and supports community involvement.[6]

The design approach of the development team focuses on simplicity from a developer's standpoint rather than a user's standpoint, elegance, code correctness, and minimalism.[7] A package manager written specifically for Arch Linux, pacman, is used to install, remove and update software packages.

Arch Linux uses a rolling release model, such that a regular system update is all that is needed to obtain the latest Arch software; the installation images released by the Arch team are simply up to date snapshots of the main system components.[8]

History

Inspired by CRUX, another minimalist distribution, Judd Vinet started Arch Linux in March 2002. Vinet led the project until 1 October 2007, when he stepped down due to lack of time, transferring control of the project to Aaron Griffin.[9]

Design and principles

Arch is largely based around binary packages. Packages are targeted for i686 and x86-64 microprocessors to assist performance on modern hardware. A ports/ebuild-like system is also provided for automated source compilation, known as the Arch Build System.

Arch Linux focus on simplicity and developers meaning that the main effort in assisting the user is not to provide a graphical interface to work with — the package manager, for example, does not have an official graphical front-end — but making well-annotated configuration files and extensive use of shell scripts.[10] This has earned it a reputation as a distribution for "intermediate and advanced Linux users who aren't afraid of the command line".[11]

Relying on complex tools to manage and build your system is going to hurt the end users. [...] "If you try to hide the complexity of the system, you'll end up with a more complex system". Layers of abstraction that serve to hide internals are never a good thing. Instead, the internals should be designed in a way such that they NEED no hiding.

— Aaron Griffin[12]

init framework

Arch uses a BSD-style init framework, a tradeoff of flexibility for simplicity. It also includes and permits use of System V runlevels and the inittab file, but there is little differentiation between runlevels. This is because the modules and daemons loaded at startup are arranged as arrays in the central configuration file, /etc/rc.conf, as opposed to System V's system of a directory for each runlevel containing a numbered symbolic link for each daemon.[13] There is also the ability to start processes asynchronously, which neither the original BSD init nor the original Sys V init have. See init for more detail on the differences between the two systems.

Installation

The Arch Linux website supplies ISO images that can be run from CD or USB. The Arch Linux installer is a shell script using dialog for user interaction. The default install is minimalist.[14] Further system customization and expansion (adding a window manager, desktop environment, etc.) must be done manually, installing packages downloaded from online repositories. Arch is therefore generally considered relatively involved to install, in comparison to other operating systems.[15]

An alternative to using CD or USB images for installation is to use the static version of the package manager Pacman, from within another GNU/Linux based operating system.[16] The user can mount his or her newly formatted drive partition, and use Pacman with the appropriate command-line switch to have it use the mountpoint of the device as root for its operations. This way the base package group and any additional packages can be installed on the newly formatted partition by having Pacman retrieve them from its mirrors. However, there are further actions that need to be taken before the system is ready for use after this process, most notably installing a bootloader, and making various configurations to the new system.

Package management

Pacman

Main article: Pacman (package manager)

To facilitate regular package changes, pacman was developed by Judd Vinet to provide Arch with its own package manager able to track dependencies.[17]

All packages are managed using the Pacman package manager. Pacman handles package installation, upgrades, removal and downgrades, and features automatic dependency resolution. The packages for Arch Linux are obtained from the Arch Linux package tree and are compiled for either i686 or x86-64 architectures. Arch Linux is primarily based on binary packages in the tar.gz and tar.xz format.[18]

Repositories

Currently, the following basic official repositories exist:

  • core, which contains all the packages needed to set up a base system
  • extra, which holds packages not required for the base system, including desktop environments and programs
  • community, which contains packages built and voted on by the community; includes packages that have sufficient votes and have been adopted by a "trusted user".
  • multilib, a centralized repository for x86_64 users to more readily support 32-bit applications in a 64-bit environment.

In addition, there also exist testing repositories that include package candidates for other repositories. Currently, the following testing repositories exist:

  • testing, with packages for core and extra.
  • community-testing, with packages for community.
  • multilib-testing, with packages for multilib.

The staging and community-staging repositories are used for some rebuilds to avoid broken packages in testing.

The unstable repository was dropped in July 2008 and most of the packages moved to other repositories.[19] In addition to the official repositories, there are a number of unofficial user repositories, the most well-known being the Arch User Repository, or AUR, hosted on the Arch Linux site.

Repository security

Until version 4.0.0[20] Arch Linux's package manager lacked support for signed packages.[21] Packages and metadata were not verified for authenticity by pacman during the download-install process. Without package authentication checking, tampered-with or malicious repository mirrors can compromise the integrity of a system.[22] Pacman 4 allows verification of the package database and packages, but it is, by now, disabled by default. In November 2011 package signing became mandatory for new package builds[23] and as of March 21 2012 every package is signed.

Arch Build System

The Arch Build System is a ports-like source packaging system that compiles source tarballs into binary packages, which are installed via Pacman.[24] The Arch Build System provides a directory tree of shell scripts, called PKGBUILDs, that enable any and all official Arch packages to be customized and compiled. Rebuilding the entire system using modified compiler flags is also supported by the Arch Build System. The Arch Build System makepkg tool can be used to create custom pkg.tar.xz packages from third-party sources. The resulting packages are also installable and trackable via Pacman.

Arch User Repository

In addition to the repositories, the Arch User Repository provides user-made PKGBUILD scripts for packages not included in the repositories. The PKGBUILD scripts simplify building from source by explicitly listing and checking for dependencies and configuring the install to match the Arch architecture. The scripts are available for download from http://aur.archlinux.org. Arch User Repository helper programs can further streamline the downloading and building process. However, such tools that search, download and run PKGBUILD scripts automatically will never be included in the official repositories because of potential security risks.[25][specify]

Users can create packages compatible with pacman using the Arch Build System and custom PKGBUILD scripts.[26] This functionality has helped support the Arch User Repository, which consists of user contributed packages to supplement the official repositories.[27]

The Arch User Repository provides the community with packages that are not included in the repositories. Reasons include:

  • License issues. Software that cannot be redistributed, but is free to use, can be included in the Arch User Repository since all that is hosted by the Arch Linux web site is a shell script that downloads the actual software from elsewhere. Examples include proprietary freeware such as Google Earth and RealPlayer.
  • Modified official packages. The Arch User Repository also contains many variations on the official packaging as well as beta versions of software that is contained within the repositories as stable releases.
  • Rarity of the software. Some new or rarely used programs have not been added to the official repositories (yet).

PKGBUILDs for any software can be contributed by ordinary users and any PKGBUILD that is not confined to the Arch User Repository for policy reasons can be voted into the community repositories.

Versions

"Rolling releases"

Similar to Gentoo, and unlike other major distributions such as Ubuntu and Fedora, Arch Linux does not schedule releases for specific dates but uses a "rolling release" system, with new packages provided daily. Its package management allows users to keep systems up-to-date easily.[28] Rather than encouraging users to move between discrete releases, 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 gets installed if updates are installed afterwards. In fact, some members of the Arch forums take pride in showing the age of the installation.

From version 2009.02 the goal is to bring coordinated releases following the rhythm of kernel releases, in order to provide optimal hardware support, this means a new release every 3 or 4 months.[29]

As of May 2012, the latest image is 2011.08.19, dated 19 August 2011.[30]

Install media history

Color Meaning
Yellow Old release
Green Current release
Blue Future release
Version Code name Date Notes
0.1[31] Homer 2002-03-11 First release built from scratch.
0.2[32] Vega 2002-04-17
0.3[33] Firefly 2002-08-07
0.4[34] Dragon 2002-12-18
0.5[35] Nova 2003-07-21 Support for PAM, LVM, GRUB.
0.6[36] Widget 2004-03-01 Support for JFS and XFS added.
0.7[37] Wombat 2005-01-24
0.8[38] Voodoo 2007-03-31
2007.05[39] Duke 2007-05-17 Pacman 3
2007.08[40] Don't Panic 2007-08-05
2008.06[41] Overlord 2008-06-24 Availability of USB disk images.
2009.02[29] — 2009-02-16 Inclusion of AIF (Arch Linux Installation Framework).
2009.08[42] — 2009-08-10 Pacman 3.3, Usage of new AIF installer, better boot device detection, better date/time setting, re-factored grub installation routines.[43]
2010.05[44] — 2010-05-17 First snapshot with isohybrid support, dual arch images, using isolinux exclusively and pxe support.
2011.08.19[45] — 2011-08-19 Linux 3.0.3, syslinux bootloader support, btrfs and nilfs2 experimental filesystem support.

See also

References

  1. ^ Aaron Griffin, Lead Developer at ArchLinux
  2. ^ "Licenses". wiki.archlinux.org. 2011-09-24. Retrieved 2011-10-02.
  3. ^ "[arch] Pronunciation of our beloved distribution's name". Osdir.com. 2005-08-24. Retrieved 2009-10-19.
  4. ^ "Arch Linux - About". www.archlinux.org. Retrieved 2011-09-27.
  5. ^ "GNU Project - Explaining Why We Don't Endorse Other Systems". www.gnu.org. Retrieved 2011-09-28.
  6. ^ "DistroWatch.com: Arch Linux". www.distrowatch.com. Retrieved 2011-09-28.
  7. ^ "The Arch Way". Wiki.archlinux.org. 2009-10-09. Retrieved 2009-10-19.
  8. ^ "Rolling with Arch Linux". lwn.net. 2010-03-10. Retrieved 2011-09-30.
  9. ^ "Arch Linux Forums / Arch Leadership". Bbs.archlinux.org. Retrieved 2009-10-19.
  10. ^ "Arch Linux: An End To My Distro Shuffle?". OSNews.com. 2004-02-10. Retrieved 2009-10-19.
  11. ^ "Archlinux". Wiki.polishlinux.org. Retrieved 2009-10-19.
  12. ^ Archway, phraktured.net, 2007-11-09, retrieved 2012-01-22
  13. ^ "Rc.conf". Wiki.archlinux.org. Retrieved 2009-10-19.
  14. ^ "Beginners Guide". Wiki.archlinux.org. 2009-09-17. Retrieved 2009-10-19.
  15. ^ "Arch 2008.06 Review". Celettu.wordpress.com. 2008-06-25. Retrieved 2009-10-19.
  16. ^ "Install From Existing Linux". Wiki.archlinux.org. 2009-11-21. Retrieved 2009-12-05.
  17. ^ "Arch Linux: Why It Rocks". www.osnews.com. 2005-03-21. Retrieved 2011-09-30.
  18. ^ Pierre Schmitz (2010-03-23). "Switching to xz compression for new packages". Archlinux.org. Retrieved 2010-03-23.
  19. ^ "Arch Linux Newsletter 08-04-2008". Archlinux.org. Retrieved 2009-10-19.
  20. ^ Pacman NEWS file as of 4.0.0, retrieved 14 October 2011
  21. ^ "FS#5331 - Signed packages". Retrieved 7 August 2011.
  22. ^ "Attacks on Package Managers". cs.arizona.edu. 2008-07-10. Retrieved 2010-09-14.
  23. ^ "Pacman Package Signing – 4: Arch Linux". Allan McRae. 2011-12-17. Retrieved 2012-02-29.
  24. ^ "Arch Build System". Wiki.archlinux.org. Retrieved 2009-10-19.
  25. ^ "Arch Linux: Popular KISS distro – Interview – Part II". Hardware.no. Retrieved 2009-10-19.
  26. ^ "Using the Arch Build System". library.linode.com. 2011-09-08. Retrieved 2011-09-30.
  27. ^ "Arch Linux". linuxdistroreview.com. 2011-03-08. Retrieved 2011-09-30.
  28. ^ "Arch Linux Review". DVD-Guides.com. Retrieved 2009-10-19.
  29. ^ a b Aaron Griffin (2009-02-16) 2009.02 ISO Release.
  30. ^ "2011.08.19 installation media". Arch Linux. 2011-08-19. Retrieved 2011-08-19.
  31. ^ Judd Vinet (2002-03-11) Arch Linux 0.1 Released.
  32. ^ Judd Vinet (2002-04-17) Arch Linux 0.2 Released.
  33. ^ Judd Vinet (2002-08-07) Arch Linux 0.3 Released.
  34. ^ Judd Vinet (2002-12-18) Arch Linux 0.4 Released.
  35. ^ Judd Vinet (2003-07-21) Arch Linux 0.5 Released.
  36. ^ Judd Vinet (2004-03-01) Arch Linux 0.6 Released.
  37. ^ Judd Vinet (2005-01-24) Arch Linux 0.7 (Wombat) Released!
  38. ^ Tobias Powalowski (2007-03-31) 0.8 Voodoo ISOs finally released!
  39. ^ Tobias Powalowski (2007-05-17) 2007.05 Duke ISOs released.
  40. ^ Tobias Powalowski (2007-08-05) 2007.08 Don't Panic ISOs released.
  41. ^ Simo Leone (2008-06-24) 2008.06 Overlord ISOs released.
  42. ^ Dieter Plaetinck (2009-08-10) 2009.08 images.
  43. ^ "News - 2009.08 images". Arch Linux. 2009-08-10. Retrieved 2009-10-19.
  44. ^ Dieter Plaetinck (2010-05-17) 2010.05 snapshots. Less is more..
  45. ^ Dieter Plaetinck (2011-08-19) 2010.05 snapshots. Less is more..
Retrieved from "https://en.wikipedia.org/w/index.php?title=Arch_Linux&oldid=490854451"