|Summary help replacing me|
|This section will cover various must-do procedures after installation such as updating your new system and adding a regular, non-root user.|
- 1 Post-Installation
- 1.1 Update
- 1.1.1 Update, Sync, and Upgrade the system with pacman
- 1.1.2 Get familiar with pacman
- 1.1.3 /etc/pacman.conf
- 1.1.4 Mirrors
- 1.1.5 Initialize package verification
- 1.1.6 Update the System
- 1.2 Adding a User
- 1.1 Update
Congratulations, and welcome to your new Arch Linux system!
Your new Arch Linux base system is now a functional GNU/Linux environment ready for customization. From here, you may build this elegant set of tools into whatever you wish or require for your purposes.
Login with the root account. We will configure pacman and update the system as root.
Update, Sync, and Upgrade the system with pacman
Now we will update the system using pacman. Pacman is the package manager of Arch Linux. It manages your entire package system and handles installation, removal, package downgrade (through cache), custom compiled package handling, automatic dependency resolution, remote and local searches and much more. Pacman will now be used to download software packages from remote repositories and install them onto your system.
Get familiar with pacman
Pacman is the Arch user's best friend. It is highly recommended to study and learn how to use the pacman tool. Try:
$ man pacman
To make any changes to your repository selections or pacman options, edit
Repositories are described below; enable all desired repositories by removing the # in front of the 'Include =' and '[repository]' lines.
A software repository is a storage location from which software packages may be retrieved and installed on a computer. Arch Linux package maintainers (developers and Trusted Users) maintain a number of official repositories containing software packages for essential and popular software, readily accessible via pacman. This article outlines those officially-supported repositories. See Official Repositories for more information including details about the purpose of each repository.
Most people will want to use [core], [extra] and [community]. If you want to run 32-bit applications on Arch x86_64, enable the [multilib] repository by adding the lines below to
[multilib] Include = /etc/pacman.d/mirrorlist
The Arch User Repository (AUR) holds the [community] and [unsupported] branches. Unlike the other branches, [unsupported] contains no binary packages and cannot (by design) be accessed directly by pacman. This branch is a collection of PKGBUILD bash scripts written by Arch users to build packages from source using the Arch Build System. Software in [unsupported] is generally not available in the other branches. When an [unsupported] package acquires enough popular votes, it may be moved to the [community] binary repository if one of the Trusted Users is willing to adopt and maintain it there.
Same Arch packages are stored on multiple servers across the world. Selected mirrors are listed in
/etc/pacman.d/mirrorlist, ordered by priority. Initially
/etc/pacman.d/mirrorlist contains list of all known mirrors, some of which should be enabled to proceed any further.
Choosing up-to-date mirrors
Arch Linux MirrorStatus reports various aspects about the mirrors such as network problems with mirrors, data collection problems, the last time mirrors have been synced, etc. Mirrorlist Generator uses this information to automatically rank mirrors close to your location by how up-to-date they are. Generated list can be simply inserted in
/etc/pacman.d/mirrorlist. You obviously can uncomment other mirrors based on your own guesses (remove the '#' in front of entry to uncomment it).
Using faster mirrors
To get the fastest mirrors refer to Mirrors#Sorting mirrors.
Refreshing mirror list
Force pacman to refresh all package lists with the new mirrorlist in place:
# pacman -Syy
-y flags forces pacman to refresh all package lists even if they are considered to be up to date. Issuing
pacman -Syy whenever a mirror is changed, is good practice and will avoid possible headaches.
Initialize package verification
# pacman-key --init
To generate the master-key, entropy is needed. You should press random keys on your keyboard, move your mouse around, or switch to another console and run a disk-intensive command such as
ls -R /. After the pacman-key command completes, run the following command to setup the keys.
# pacman-key --populate archlinux
Take time to verify the Master Signing Keys when prompted as these are used to co-sign (and therefore trust) all other packager's keys.
Update the System
Often the developers will provide important information about required configurations and modifications for known issues. The Arch Linux user is expected to consult these places before performing an upgrade:
- Arch news. If you did not read this before an upgrade and you encounter an error, check the news before you post a question on the forum!
- Announce mailing list.
Sync, refresh, and upgrade your entire new system with:
# pacman -Syu
# pacman --sync --refresh --sysupgrade
Pacman will now download a fresh copy of the master package list from the server(s) defined in
/etc/pacman.conf and perform all available upgrades. You may be prompted to upgrade pacman itself at this point. If so, respond by entering yes, and then reissue the
pacman -Syu command when finished.
Reboot if a kernel upgrade has occurred.
Pacman output is saved in
See Package Management FAQ for answers to frequently asked questions regarding updating and managing your packages.
After executing the command
pacman -Syu, the entire system will be updated. It is possible to prevent a package from being upgraded. A typical scenario would be a package for which an upgrade may prove problematic for the system. In this case, there are two options; indicate the package(s) to skip in the pacman command line using the
--ignore switch (
pacman -S --help for details) or permanently indicate the package(s) to skip in the
/etc/pacman.conf file in the
IgnorePkg array. For more information, please see the pacman wiki entry.
Please note that the power user is expected to keep the **whole** system up-to-date with
pacman -Syu, rather than selectively upgrading packages. You may diverge from this typical usage as you wish; just be warned that there is a greater chance that things will not work as intended and that it could break your system. The majority of complaints happen when selective upgrading, unusual compilation or improper software installation is performed. Use of
/etc/pacman.conf is therefore discouraged, and should only be used sparingly, if you know what you are doing. Use of
IgnorePkg is analogous to "voiding the warranty".
The Arch rolling release model
Keep in mind that Arch is a rolling release distribution. This means the user is not required to reinstall or perform elaborate system rebuilds to upgrade to the newest version. Issuing
pacman -Syu periodically (and noting the above warning) keeps the entire system up-to-date and on the bleeding edge. At the end of this upgrade, the system will be completely current. Remember to reboot if a kernel upgrade has occurred.
Adding a User
Add a normal user account instead, using one of the two following methods, both creating the user archie as an example:
You will be asked to enter some information in an interactive way:
Login name for new user : archie User ID ('UID') [ defaults to next available ]: Initial group [ users ]: Additional groups (comma separated) : audio,games,lp,optical,power,scanner,storage,video Home directory [ /home/archie ]: Shell [ /bin/bash ]: Expiry date (YYYY-MM-DD) :
As shown in the example, you are advised to enter values only for the Login name and the Additional groups, and leave empty all the other fields.
The list of Additional groups in the example is a typical choice for a desktop system, hence it is recommended especially for beginners:
- audio - for tasks involving sound card and related software
- games - for write permission for games in the games group
- lp - for managing printing tasks
- optical - for managing tasks pertaining to the optical drive(s)
- power - for allowing interactions with power options (e.g. shutdown with power button)
- scanner - for using a scanner
- storage - for managing storage devices
- video - for video tasks and hardware acceleration
For additional information about listed and other groups see Groups#User groups.
Now you will be presented with a preview of your new account, and the ability to cancel or continue operations: after pressing Template:Keypress the account will be created, and you will be prompted to enter additional, optional information for the new user (e.g. the full name). After that, you will be asked to enter the password for your account.
# useradd -m -g users -G audio,games,log,lp,optical,power,scanner,storage,video,wheel -s /bin/bash archie
You will have to set a password using
passwd. To enter additional information you can use the
Deleting the user account
In the event of error, or if you wish to delete this user account in favor of a different name or for any other reason, use
# userdel -r [username]
-r option will remove the user's home directory and its content, along with the the user's mail spool.
Read Users and Groups for further information. If you want to change the name of your user or any existing user, consult the Change username page. You may also check the man pages for
Template:Beginners' Guide navigation