Software:Arch Linux

From HandWiki
Revision as of 12:40, 9 February 2024 by StanislovAI (talk | contribs) (correction)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Short description: Rolling release distribution of Linux
Arch Linux
Archlinux-logo-standard-version.png
DeveloperLevente Polyak (lead developer)[1]
OS familyLinux (Unix-like)
Working stateCurrent
Source modelOpen-source
Initial release11 March 2002; 22 years ago (2002-03-11)
|Final release|Latest release}}2024.01.01 [2] / 10 months ago
Repositorygitlab.archlinux.org github.com/archlinux
Marketing targetGeneral purpose
Update methodRolling release
Package managerpacman, libalpm (back-end),[3] Arch build system
Platforms
Kernel typeMonolithic (Linux kernel)
UserlandGNU
InfluencedEndeavourOS, Manjaro, Garuda Linux, Artix Linux, Antergos
Influenced byCRUX, BSD
Default user interfaceCommand-line interface (Zsh as the default shell in Live CD or Live USB and Bash as the default shell after installation)
LicenseFree software (GNU GPL and other licenses)[7]
Official website{{{1}}}

Arch Linux (/ɑːr/)[8][9] is an independently developed, x86-64 general-purpose Linux distribution that strives to provide the latest stable versions of most software by following a rolling-release model. The default installation is a minimal base system, configured by the user to only add what is purposely required.[10]

Pacman, a package manager written specifically for Arch Linux, is used to install, remove and update software packages.[11]

Arch Linux uses a rolling release model, meaning there are no "major releases" of completely new versions of the system; a regular system update is all that is needed to obtain the latest Arch software; the installation images released every month by the Arch team are simply up-to-date snapshots of the main system components.[12]

Arch Linux has comprehensive documentation, consisting of a community-run wiki known as the ArchWiki.[13][14][15]

History

Inspired by CRUX, another minimalist distribution, Judd Vinet started the Arch Linux project in March 2002. The name was chosen because Vinet liked the word's meaning of "the principal," as in "arch-enemy".[8][16]

Originally only for 32-bit x86 CPUs, the first x86_64 installation ISO was released in April 2006.[17]

Vinet led Arch Linux until 1 October 2007, when he stepped down due to lack of time, transferring control of the project to Aaron Griffin.[18]

The migration to systemd as its init system started in August 2012,[19] and it became the default on new installations in October 2012.[20] It replaced the SysV-style init system, used since the distribution's inception.[21]

The end of i686 support was announced in January 2017, with the February 2017 ISO being the last one including i686[22] and making the architecture unsupported in November 2017.[23] Since then, the community derivative Arch Linux 32[24] can be used for i686 hardware.

On 24 February 2020, Aaron Griffin announced that due to his limited involvement with the project, he would, after a voting period, transfer control of the project to Levente Polyak.[25] This change also led to a new 2-year term period being added to the Project Leader position.[26]

In March 2021, Arch Linux developers were thinking of porting Arch Linux packages to x86 64-v3, roughly correlating to the Intel Haswell era of processors.[27][28]

In April 2021, Arch Linux installation images began including a guided installation script by default.[29]

In late 2021, the Arch Linux developers released Pacman 6.0, which enabled parallel downloads.[30]

In February 2022, the Arch Linux developers began offering debug packages.[31]

Repository security

Until Pacman version 4.0.0,[32] Arch Linux's package manager lacked support for signed packages.[33] 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 could compromise the integrity of a system.[34] Pacman 4 allowed verification of the package database and packages, but it was disabled by default. In November 2011, package signing became mandatory for new package builds, and as of March 2012, every official package is signed.[35] In June 2012, package signing verification became official and is now enabled by default in the installation process.[36][37]

Design and principles

Arch is largely based on binary packages. Packages target 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.[38]

Arch Linux focuses on simplicity of design, meaning that the main focus involves creating an environment that is straightforward and relatively easy for the user to understand directly, rather than providing polished point-and-click style management tools — the package manager, for example, does not have an official graphical front-end. This is largely achieved by encouraging the use of succinctly commented, clean configuration files that are arranged for quick access and editing.[39] This has earned it a reputation as a distribution for "advanced users" who are willing to use the command line.[40]

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[41]

Installation

Screenshot of pacstrap during installation

The Arch Linux website supplies ISO images that can be run from CD or USB. After a user partitions and formats their drive, a simple command line script (pacstrap) is used to install the base system.[37] The installation of additional packages which are not part of the base system (for example, desktop environments), can be done with either pacstrap, or Pacman after booting (or chrooting) into the new installation.[42][43][11]

Neofetch output of an Arch Linux Installation

An alternative to using CD or USB images for installation is to use the static version of the package manager Pacman, from within another Linux-based operating system.[44] The user can mount their newly formatted drive partition, and use pacstrap (or Pacman with the appropriate command-line switch) to install base and additional packages with the mountpoint of the destination device as the root for its operations. This method is useful when installing Arch Linux onto USB flash drives, or onto a temporarily mounted device which belongs to another system.[45]

Regardless of the selected installation type, further actions need to be taken before the new system is ready for use, most notably by installing a bootloader and configuring the new system with a system name, network connection, language settings, and graphical user interface.[46]

Arch Linux does not schedule releases for specific dates but uses a "rolling release" system where new packages are provided throughout the day. Its package management allows users to easily keep systems updated.[47]

Occasionally, manual interventions are required for certain updates, with instructions posted on the news section of the Arch Linux website.[48]

Guided automated install script

An experimental guided installer named archinstall is included in all Arch ISO images released since 2021. It allows users to easily install and configure Arch Linux including drivers, disk partitioning, network configuration, accounts setup, and installation of desktop environments.[49][50][51]

archinstall

Package management

Pacman

Example of pacman usage

All packages are managed using Pacman, a package manager written specifically for Arch Linux.[52] Pacman handles package installation, upgrades, downgrades, removal and features automatic dependency resolution.[53] The packages for Arch Linux are obtained from the Arch Linux package tree and are compiled for the x86-64 architecture.

Pacman typically uses binary packages with a .pkg.tar.zst extension,[54][55][56] (for zstd compression), with .pkg placed before this to indicate that it is a Pacman package (giving .pkg.tar.zst);[53] though other compression formats are also valid, such as .pkg.tar.xz.[57]

For example, packages can be installed via pacman -S package name, while pacman -Syu can also be used to perform a full system upgrade.[58]

As well as Arch Linux, Pacman is also used for installing packages under MSYS2 (a fork of Cygwin) on Windows.[59]

Repositories

The following official binary repositories exist:[60]

  • core, which contains all the packages needed to set up a base system. Packages in this repository include kernel packages and shell languages.
  • extra, which holds packages not required for the base system, including desktop environments and programs.
  • multilib, a centralized repository for x86-64 users to more readily support 32-bit applications in a 64-bit environment. Packages in this repository include Steam and Wine.

Additionally, there are testing repositories which include binary package candidates for other repositories. Currently, the following testing repositories exist:

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

The core-staging and extra-staging repositories are used for some rebuilds to avoid broken packages in testing. The developers recommend not using these repositories for any reason, stating that any system updating from them will "unquestionably break."[61]

There are also two other repositories that include the newest version of certain desktop environments.

  • gnome-unstable, which contains packages of a new version of the software from GNOME before being released into testing.
  • kde-unstable, which contains packages of a new version of KDE software before being released into testing.

The unstable repository was dropped in July 2008 and most of the packages moved to other repositories.[62] The community repository was merged with extra and the testing and staging repositories were split in May 2023.[63][64] In addition to the official repositories, there are a number of unofficial user repositories.

The most well-known unofficial repository is the Arch User Repository, or AUR, hosted on the Arch Linux site. The AUR does not host binary packages but instead a collection of build scripts known as PKGBUILDs. PKGBUILD scripts are executed by the makepkg command, which downloads the necessary files from the software's repository and builds them using the Arch build system.

The Arch Linux repositories contain both libre and nonfree software, and the default Arch Linux kernel contains nonfree proprietary blobs, hence the distribution is not endorsed by the GNU project.[65] The linux-libre kernel can be installed from the AUR or by enabling Parabola's repositories.

Arch build system (ABS)

The Arch build system (ABS) is a ports-like source packaging system that compiles source tarballs into binary packages, which are installed via Pacman.[66] 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.zst packages from third-party sources. The resulting packages are also installable and trackable via Pacman.[67][68]

Arch User Repository (AUR)

In addition to the repositories, the Arch User Repository (AUR) provides user-made PKGBUILD scripts for packages not included in the repositories. These PKGBUILD scripts simplify building from source by explicitly listing and checking for dependencies and configuring the install to match the Arch architecture.[69] Arch User Repository helper programs can further streamline the downloading of PKGBUILD scripts and associated building process. However, this comes at the cost of executing PKGBUILDs not validated by a trusted person; as a result, Arch developers have stated that the utilities for automatic finding, downloading and executing of PKGBUILDs will never be included in the official repositories.[70]

Users can create packages compatible with Pacman using the Arch build system and custom PKGBUILD scripts.[71] This functionality has helped support the Arch User Repository, which consists of user contributed packages to supplement the official repositories.[72]

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

  • Licensing 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 website 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.
  • Popularity of the software: rarely used programs have not been added to the official repositories (yet).
  • Betas or "nightly" versions of the software which are very new and thus unstable. Examples include the "firefox-nightly" package, which gives new daily builds of the Firefox web browser.

PKGBUILDs for any software can be contributed by ordinary users.[73] Any PKGBUILD that has 10 or more votes or more than 1% usage from pkgstats can be promoted into the extra repository.[74]

Reproducible builds

Arch Linux is working on making all official packages reproducible.[75] This means that when a package is rebuilt in a different environment it should be bit-by-bit identical. This allows users and researchers to verify the integrity of the packages found in the official repository. The status of this effort can be monitored on the dedicated status page.

Derivatives

There are several projects working on porting the Arch Linux ideas and tools to other kernels, including PacBSD (formerly ArchBSD) and Arch Hurd,[76] which are based on the FreeBSD and GNU Hurd kernels, respectively. There is also the Arch Linux ARM project, which aims to port Arch Linux to ARM-based devices, including the Raspberry Pi, as well as the Arch Linux 32 project, which continued support for systems with 32-bit only CPUs after the mainline Arch Linux project dropped support for the architecture in November 2017.[77][78]

Various distributions are focused on providing an Arch base with an easier install process, such as EndeavourOS, CachyOS, Manjaro and Garuda Linux.[79]

SteamOS 3.0, the version of SteamOS used in the Steam Deck by Valve, is based on Arch Linux.[80][81][82][83]

The current Arch Linux logo was designed by Thayer Williams[84][85] in 2007 as part of a contest to replace the previous logo.[86]

Reception

OSNews reviewed Arch Linux in 2002.[87] OSNews also has five later reviews about Arch Linux.[88][89][90][91][92]

LWN.net wrote a review about Arch Linux in 2005.[93] LWN.net also has two later reviews about Arch Linux.[94][95]

Tux Machines reviewed Arch Linux in 2007.[96]

Chris Smart from DistroWatch Weekly wrote a review about Arch Linux in January 2009.[97] DistroWatch Weekly reviewed Arch Linux again in September 2009 and in December 2015.[98][99]

The Linux kernel developer and maintainer Greg Kroah-Hartman (GKH)[100] has stated that he uses Arch Linux and that it "works really really well". He has also praised the Arch Wiki, the distribution's rolling release model, and the feedback loop with the community.[101]

In a 2023 DistroWatch poll, about half of the responders maintained that they were running either Arch (17%) or an Arch derivative (30%).[102] As of 2023, Arch also enjoys the highest average rating of any Linux distribution on DistroWatch with a rating of 9.34.[103]

See also

Notes

  1. i686 support is maintained by the Arch Linux 32 project.[4]
  2. ARM support is maintained by the Arch Linux ARM project.
  3. PowerPC support is maintained by the ArchPOWER project.[5]
  4. RISC-V support is maintained by the Arch Linux RISC-V project.[6]

References

  1. "Arch Linux - News: The Future of the Arch Linux Project Leader". https://archlinux.org/news/the-future-of-the-arch-linux-project-leader/. 
  2. "Arch Linux - Downloads". https://archlinux.org/download/. 
  3. "Pacman Home Page". https://www.archlinux.org/pacman/. 
  4. "Arch Linux 32". https://archlinux32.org/. 
  5. "ArchPOWER". https://archlinuxpower.org/. 
  6. "Arch Linux RISC-V". https://archriscv.felixc.at/. 
  7. * "Copyright". https://www.archlinux.org/pacman/#_copyright. "Pacman is [...] and is licensed through the GNU General Public License, version 2 or later." 
  8. 8.0 8.1 Aaron Griffin (24 August 2005). "Pronnounciation [sic] of our beloved distribution's name". Osdir.com. https://osdir.com/ml/linux.arch.general/2005-08/msg00253.html. 
  9. "Arch terminology - ArchWiki". https://wiki.archlinux.org/title/Arch_terminology#Arch_Linux. "Officially, the 'Arch' in "Arch Linux" is pronounced /ɑːr/ as in an "archer"/bowman, or "arch-nemesis", and not as in "ark" or "archangel"." 
  10. "Arch Linux Wiki homepage". https://wiki.archlinux.org/title/Arch_Linux. 
  11. 11.0 11.1 "Pacman Home Page". https://www.archlinux.org/pacman/. 
  12. Ivan Jelic (10 March 2010). "Rolling with Arch Linux". https://lwn.net/Articles/378030/. 
  13. Smith, Jesse (21 December 2015). "Arch Linux - Feature Story". https://distrowatch.com/weekly.php?issue=20151221#arch. 
  14. Linton, Susan (17 July 2015). "Debian Project Lead: Snappy and Mir Bad Ideas". OStatic. http://ostatic.com/blog/debian-project-lead-snappy-and-mir-bad-ideas. "One of the first questions wondered if McGovern was jealous of anything from any other distro. To that he answered Arch's wiki calling it "an absolutely amazing resource" that he himself uses." 
  15. "The Arch Way | Linux Journal". https://www.linuxjournal.com/content/arch-way. 
  16. "Interview with Judd Vinet". https://distrowatch.com/dwres.php?resource=interview-arch. 
  17. "Arch Linux - News: Official Arch64 install cd available". https://www.archlinux.org/news/official-arch64-install-cd-available/. 
  18. apeiro (Judd Vinet) (1 October 2007). "Arch Leadership". https://bbs.archlinux.org/viewtopic.php?id=38024. 
  19. Gaudreault, Stéphane (14 August 2012). "Migration to systemd". arch-dev-public (Mailing list). Archived from the original on 20 October 2020. Retrieved 24 September 2020.
  20. Bächler, Thomas (13 October 2012). "systemd is now the default on new installations". https://www.archlinux.org/news/systemd-is-now-the-default-on-new-installations/. 
  21. "Archlinux installer 0.1". https://archive.archlinux.org/iso/0.1/. 
  22. Bartłomiej Piotrowski (25 January 2017). "Phasing out i686 support". https://www.archlinux.org/news/phasing-out-i686-support/. 
  23. Bartłomiej Piotrowski (8 November 2017). "The end of i686 support". https://www.archlinux.org/news/the-end-of-i686-support/. 
  24. "Arch Linux 32". https://archlinux32.org/. 
  25. "Arch Linux - News: The Future of the Arch Linux Project Leader". https://www.archlinux.org/news/the-future-of-the-arch-linux-project-leader/. 
  26. "DeveloperWiki:Project Leader - ArchWiki". https://wiki.archlinux.org/index.php/DeveloperWiki:Project_Leader. 
  27. "Arch Linux Developers Discuss Idea Of Providing An x86-64-v3 Port" (in en). https://www.phoronix.com/scan.php?page=news_item&px=Arch-Linux-x86-64-v3-Port-RFC. 
  28. "Provide a x86_64_v3 microarchitecture level port (!2) · Merge requests · Arch Linux / rfcs" (in en). 2 March 2021. https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/2. 
  29. "Arch Linux - News: Installation medium with installer". https://archlinux.org/news/installation-medium-with-installer/. 
  30. "Update NEWS for pacman-6.0.1 release (d5e2c0a5) · Commits · Pacman / Pacman" (in en). 4 September 2021. https://gitlab.archlinux.org/pacman/pacman/-/commit/d5e2c0a5512413c8a37437e4b5fe9350121a5963. 
  31. "Arch Linux - News: Debug packages and debuginfod". https://archlinux.org/news/debug-packages-and-debuginfod/. 
  32. "NEWS - pacman.git - The official pacman repository". https://git.archlinux.org/pacman.git/tree/NEWS?id=d3d3b861ac2c4ce63c306e00395945bfa3c1b6c6. 
  33. "FS#5331 : Signed packages". https://bugs.archlinux.org/task/5331. 
  34. "Attacks on Package Managers". cs.arizona.edu. 10 July 2008. https://www.cs.arizona.edu/stork/packagemanagersecurity/attacks-on-package-managers.html. 
  35. McRae, Allan (17 December 2011). "Pacman Package Signing – 4: Arch Linux". http://allanmcrae.com/2011/12/pacman-package-signing-4-arch-linux/. 
  36. Gaetan Bisson (4 June 2012). "Having pacman verify packages". https://www.archlinux.org/news/having-pacman-verify-packages/. 
  37. 37.0 37.1 Pierre Schmitz (22 July 2012). "Install media 2012.07.15 released". https://www.archlinux.org/news/install-media-20120715-released/. 
  38. Campbell, Alex; Hacker, Tech; PT, PCWorld | (2 November 2016). "5 reasons to opt for a Linux rolling distro vs. a standard release" (in en). https://www.pcworld.com/article/3133030/5-reasons-to-opt-for-a-linux-rolling-distro-vs-a-standard-release.html. 
  39. "The Arch Way". 9 October 2009. https://wiki.archlinux.org/index.php/The_Arch_Way. 
  40. Williams, rew; April 2020, Brian Turner 16. "Best Linux distros of 2020: for beginners and advanced users" (in en). https://www.techradar.com/uk/best/best-linux-distros. 
  41. "FS#43302 - [pacman provide workaround for removing --asroot from makepkg"]. https://bugs.archlinux.org/task/43302. 
  42. "pacman - ArchWiki". https://wiki.archlinux.org/index.php/Pacman#Installing_packages. 
  43. "General recommendations - ArchWiki". https://wiki.archlinux.org/index.php/General_recommendations. 
  44. "Install From Existing Linux". 21 November 2009. https://wiki.archlinux.org/index.php/Install_From_Existing_Linux. 
  45. "Install Arch Linux on a removable medium - ArchWiki". https://wiki.archlinux.org/title/Install_Arch_Linux_on_a_removable_medium#Installation. 
  46. "Installation guide - ArchWiki". https://wiki.archlinux.org/index.php/Installation_guide. 
  47. "Arch Linux Review". DVD-Guides.com. 2007. https://www.dvd-guides.com/dvdguides/index.php/linux-reviews/212-arch-linux-review. 
  48. "News". https://www.archlinux.org/news/. 
  49. "archinstall - ArchWiki". https://wiki.archlinux.org/index.php/Archinstall. 
  50. Nestor, Marius (2021-04-11). "Latest Arch Linux ISO Release Comes with the ArchInstall CLI Guided Installer" (in en-US). https://9to5linux.com/latest-arch-linux-iso-release-comes-with-the-archinstall-cli-guided-installer. 
  51. "Arch Linux Now Comes With Easier to Use Guided Installer" (in en-US). 2021-04-06. https://www.makeuseof.com/arch-linux-now-comes-with-easier-to-use-guided-installer/. 
  52. Eugenia Loli (21 March 2005). "Arch Linux: Why It Rocks". OSNews. https://www.osnews.com/story/10047. 
  53. 53.0 53.1 "pacman". 6 August 2017. https://wiki.archlinux.org/index.php/Pacman. 
  54. "Arch Linux Nears Roll-Out Of Zstd Compressed Packages For Faster Pacman Installs - Phoronix". https://www.phoronix.com/scan.php?page=news_item&px=Arch-Linux-Pacman-Zstd-Near. 
  55. Broda, Robin (March 24, 2019). "[arch-dev-public RFC: (devtools) Changing default compression method to zstd"]. https://lists.archlinux.org/pipermail/arch-dev-public/2019-March/029520.html. 
  56. "Arch Linux - News: Required update to recent libarchive". https://www.archlinux.org/news/required-update-to-recent-libarchive/. 
  57. "Pacman: Configuration options for makepkg" . 2021.
  58. "Man pages of Pacman". https://archlinux.org/pacman/pacman.8.html. 
  59. "Package Management - MSYS2". https://www.msys2.org/docs/package-management/. 
  60. "Official Repositories". https://wiki.archlinux.org/index.php/Official_Repositories. 
  61. "Official repositories - ArchWiki". https://wiki.archlinux.org/title/Official_repositories#Staging_repositories. 
  62. "Arch Linux Newsletter 08-04-2008". 4 August 2008. https://www.archlinux.org/static/magazine/2008/newsletter-2008-Aug-04.html. 
  63. Larabel, Michael (2023-05-16). "Arch Linux Prepares For Repository Changes, Discontinuing SVN Access". https://www.phoronix.com/news/Arch-Linux-Discontinues-SVN. 
  64. van der Waa, Jelle (2023-05-15). "Git migration announcement". https://archlinux.org/news/git-migration-announcement/. 
  65. "Explaining Why We Don't Endorse Other Systems". GNU Project. https://www.gnu.org/distros/common-distros.html#Arch. 
  66. "Arch Build System". https://wiki.archlinux.org/index.php/Arch_Build_System. 
  67. "Makepkg". https://wiki.archlinux.org/index.php/Makepkg. 
  68. "Arch Linux - News: Now using Zstandard instead of xz for package compression". https://www.archlinux.org/news/now-using-zstandard-instead-of-xz-for-package-compression/. 
  69. "AUR (en) - Home". https://aur.archlinux.org/. 
  70. Robin Heggelund Hansen (25 March 2008). "Arch Linux: Popular KISS distro – Interview – Part II". Hardware.no. http://www.hardware.no/artikler/aaron_griffin_english/49507/3. 
  71. "Using the Arch Build System". library.linode.com. 8 September 2011. https://library.linode.com/using-linux/package-management#sph_using-the-arch-build-system-abs. 
  72. Bo Milanovich (8 March 2011). "Arch Linux". linuxdistroreview.com. http://www.linuxdistroreview.com/arch-linux. 
  73. "Arch User Repository - ArchWiki". https://wiki.archlinux.org/title/Arch_User_Repository. "In the AUR, users are able to contribute their own package builds[.]" 
  74. "AUR Trusted User guidelines - ArchWiki". https://wiki.archlinux.org/title/AUR_Trusted_User_guidelines#Rules_for_packages_entering_the_extra_repository. 
  75. "ArchWiki - Reproducible builds". https://wiki.archlinux.org/title/Reproducible_builds. 
  76. "Arch Hurd". Arch Hurd. https://www.archhurd.org. 
  77. "Arch Linux ARM". Arch Linux ARM. https://archlinuxarm.org/. 
  78. "Arch Linux 32". Arch Linux 32. https://archlinux32.org/. 
  79. "Arch-based distributions - ArchWiki". https://wiki.archlinux.org/title/Arch-based_distributions. 
  80. Duckett, Chris. "Steam Deck is an AMD-powered handheld PC from Valve that runs KDE on Arch Linux" (in en). https://www.zdnet.com/article/steam-deck-is-an-amd-powered-handheld-pc-from-valve-that-runs-kde-on-arch-linux/. 
  81. "Valve's handheld console 'The Steam Deck' is heard with an Arch Linux based OS" (in en-US). 2021-07-16. https://technosports.co.in/2021/07/16/valves-handheld-console-the-steam-deck-is-heard-with-an-arch-linux-based-os/. 
  82. Prasad (2021-07-15). "Valve Steam Deck is a handheld gaming PC that runs SteamOS". GSMArena. https://gsmarena.com/valve_steam_deck_is_a_handheld_gaming_pc_that_runs_steamos-news-50073.php. "The Steam Deck runs on Valve's SteamOS 3.0. This is primarily based on Arch Linux and uses the compatibility layer Proton to run games designed for Windows" 
  83. "Valve has formally announced the Steam Deck, a portable handheld console with SteamOS" (in en). 15 July 2021. https://www.gamingonlinux.com/2021/07/valve-has-formally-announced-the-steam-deck-a-portable-handheld-console-with-steamos. 
  84. Willard, Travis (22 December 2007). "Arch Linux - News: Logo Contest Results (and Winner!)". https://www.archlinux.org/news/logo-contest-results-and-winner/. 
  85. Williams, Thayer (2007). "Arch Linux logo submission". https://pkgbuild.com/~jelle/logo-contest/thayer/1-archer.png. 
  86. Willard, Travis (24 October 2007). "Arch Linux - News: Arch Linux Logo Competition". https://www.archlinux.org/news/arch-linux-logo-competition/. 
  87. "Introduction to Arch Linux – OSnews". https://www.osnews.com/story/2264/. 
  88. "Arch Linux: A Better Distribution – OSnews". https://www.osnews.com/story/4827/. 
  89. "Arch Linux: An End To My Distro Shuffle? – OSnews". https://www.osnews.com/story/5971/. 
  90. "A Week in the Life of an Arch Linux Newbie – OSnews". https://www.osnews.com/story/9540/. 
  91. "Arch Linux: Why It Rocks – OSnews". https://www.osnews.com/story/10047/. 
  92. "Watching the Evolution of Arch Linux – OSnews". https://www.osnews.com/story/15075/. 
  93. "Arch Linux for Power Users [LWN.net"]. https://lwn.net/Articles/121784/. 
  94. "Rolling with Arch Linux [LWN.net"]. https://lwn.net/Articles/378030/. 
  95. "The grumpy editor's Arch Linux experience [LWN.net"]. https://lwn.net/Articles/637341/. 
  96. Fallen Under the Spell of Arch Voodoo | Tux Machines 20 April 2007
  97. "Arch Linux in review". https://distrowatch.com/weekly.php?issue=20090119#feature. 
  98. "A distro odyssey, part 2 - the Arch way". https://distrowatch.com/weekly.php?issue=20090914#feature. 
  99. "Arch Linux". https://distrowatch.com/weekly.php?issue=20151221#arch. 
  100. "git.kernel.org - linux/kernel/git/torvalds/linux-2.6.git/blob - MAINT…". 2013-01-13. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=MAINTAINERS. 
  101. "Let's Talk To Linux Kernel Developer Greg Kroah-Hartman - Open Source Summit, 2019". 2019-09-10. https://www.youtube.com/watch?v=sDrRvrh16ws&t=1574s. "[Arch developers'] idea of a constantly rolling, forward-moving system is the way to go. It's neutral, it's community-based, it has everything I need. It works really really well [...] Their Wiki is amazing. The documentation -- it's like one of the best resources out there these days. If you look up any userspace program and how to configure it and use it. Actually, the systemd Arch Wiki pages are one of the most amazing resources out there. [...] One of the main policies of Arch, or philosophies, is you stay as close to the upstream as possible. And as a developer, I want that. They're really good in feedback to the community. Because I want that testing -- I want to make sure that things are fixed. And if it is broken, I learn about it quickly and I fix it and push the stuff out. So that's actually a really good feedback loop." 
  102. "DistroWatch.com: Put the fun back into computing. Use Linux, BSD.". https://distrowatch.com/polls.php?poll=390. 
  103. "DistroWatch.com: Put the fun back into computing. Use Linux, BSD.". https://distrowatch.com/index.php?dataspan=score. 

External links