Arch Linux (or Arch) is a Linux distribution intended to be lightweight and simple. The design approach of the development team focuses on simplicity, elegance, code correctness and minimalism. “Simplicity”, according to Arch, is defined as “…without unnecessary additions, modifications, or complications..” and is defined from a developer standpoint, rather than a user standpoint.
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. He transferred his control of the project to Aaron Griffin.
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 laid it’s focus on simplicity and economy for developers means, among other things, that the main effort in assisting the user is not expended in crafting GUI configuration tools. The package manager, for example, does not have an official graphical front-end, but makes use of well-annotated configuration files and extensive use of shell scripts.
This has earned it a reputation as a distribution for “intermediate and advanced Linux users who aren’t afraid of the command line”.
Arch uses a BSD-style init framework, a trade off of flexibility for simplicity. It also includes and permits use of System V run-levels and the inittab file, but there is little differentiation between run-levels. This is because the modules and daemons loaded at startup are arranged very simply as arrays in the central configuration file, /etc/rc.conf, as opposed to System V’s system of a directory for each run-level containing a numbered symbolic link for each daemon.
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.
The Arch Linux website supplies both CD (ISO) and USB images for ease of use. The default install is slim. 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.
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 operating system. 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 mount point 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 boot-loader, and making various configurations to the new system.
This is by far my personal favorite Linux distribution. It’s simplicity just rocks and kicks all other distro’s their “behinds”. Yes, you do need to know what you are doing, but the things you get in return are just amazing. I’m a happy camper( Arch ) user for a long time already. I’ve tried and tried but nothing beats this simplicity “IMO”
The second thing i liked about Arch is, it has its own package manager (Pacman) and a lot of other packages within AUR
To use AUR, you need a AUR helper like: <strong>yay</strong> or <strong>pikaur</strong>. Small notice, Yaourt was also very popular but, unfortunately it’s outdated and package security can no longer be guaranteed.