Difference between revisions of "Beginners' Guide/Post-Installation (Hrvatski)"

From ArchWiki
Jump to navigation Jump to search
(Started translating to Croatian.)
(No difference)

Revision as of 03:53, 9 October 2011

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Tip: Ovo je dio višestraničnog vodiča za početnike. Klikni ovdje ako želiš čitati vodič u cijelosti.

Nakon instalacije

Čestitamo! Dobrodošli u svoj novi sustav Arch Linux!

Ova sekcija će prolaziti kroz razne obavezne procedore nakon instalacije poput nadogradnje novog sustava i dodavanje regularnog korisnika ne-administratora.


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.

Note: Virtual consoles 1-6 are available. You may switch between them with <ALT>+F1...F6

Configure the network (if necessary)

If you properly configured your system, you should have a working network. Try to Template:Codeline to verify: Template:Command

If you have successfully established a network connection, continue with Update, Sync, and Upgrade the system with pacman.

If, after trying to ping www.google.com, an "unknown host" error is received, you may conclude that your network is not properly configured. You may choose to double-check the following files for integrity and proper settings:

Template:Filename - Specifically, check your HOSTNAME and NETWORKING section for typos and errors.

Template:Filename - Double-check for format, typos, and errors.

Template:Filename - If you are using a static IP. If you are using DHCP, this file will be dynamically created and destroyed by default.

Tip: Advanced instructions for configuring the network can be found in the Network article.
Wired LAN

Check your Ethernet with Template:Cli All interfaces will be listed. You should see an entry for eth0, or perhaps eth1. These examples will use eth0.

Static IP

If required, you can set a new static IP with: Template:Cli and the default gateway with Template:Cli Verify that Template:Filename contains your DNS server and add it if it is missing. Check your network again with Template:Codeline. If everything is working now, adjust Template:Filename as described above for static IP.


If you have a DHCP server/router in your network try: Template:Cli If this is working, adjust Template:Filename as described above, for dynamic IP.

Wireless LAN

Please see Wireless Quickstart For the Live Environment for details on connecting to a wireless network. Although you are no longer running off the installation media, the commands are the same as long as you installed all related wireless packages during package selection. Remember, your wireless device may need firmware in order to operate. For troubleshooting, check the detailed Wireless Setup page.

Proxy Server

If you are behind a proxy server, edit Template:Filename and set http_proxy and ftp_proxy in it.

Analog Modem, ISDN, and DSL (PPPoE)

See Internet Access for detailed instructions.

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.

Note: If you installed via a Netinstall, many, if not all, of your packages will already be up to date. However, it is still advisable to run through this update process.

pacman will attempt to read Template:Filename each time it is invoked. This configuration file is divided into sections, or repositories. Each section defines a package repository that pacman can use when searching for packages. The exception to this is the Template:Codeline section, which defines global options.

Note: The defaults should work, so modifying at this point may be unnecessary, but verification is always recommended. Further info available in the Mirrors article.


Repositories are described below; enable all desired repositories by removing the # in front of the 'Include =' and '[repository]' lines.

Note: When choosing repos, be sure to uncomment both the repository header lines in [brackets] as well as the 'Include =' lines. Failure to do so will result in the selected repository being omitted! This is a very common error.
Package Repositories

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 Template:Filename:

Include = /etc/pacman.d/mirrorlist

The Arch User Repository (AUR) also contains the unsupported branch, which cannot be accessed directly by pacman. AUR [unsupported] does not contain binary packages. Rather, it provides more than thirty-one thousand PKGBUILD scripts for building packages from source, that may be unavailable through the other repos. When an AUR unsupported package acquires enough popular votes, it may be moved to the AUR [community] binary repo, if a trusted user (TU) is willing to adopt and maintain it there.

  • TU maintained
  • All PKGBUILD bash build scripts
  • Not pacman accessible by default
Note: There are a number of pacman wrappers (AUR Helpers) available to help you seamlessly access AUR.


Defines pacman repository mirrors and priorities.

Note: If your installation medium is old, your mirrorlist might be outdated, which might lead to problems when updating archlinux with pacman (see here for the bug report). Therefore it is a good idea to get the latest version of the mirrorlist from the pacman mirror list generator page. Copy the freshly generated list to Template:Filename before you continue.

Open Template:Filename in an editor and uncomment (remove the '#' in front) a server close to you. Then issue a complete package refresh: Template:Cli Passing two Template:Codeline or Template:Codeline flags forces pacman to refresh all package lists even if they are considered to be up to date. Issuing Template:Codeline whenever a mirror is changed, is good practice and will avoid possible headaches.


Alternatively, you can use Template:Codeline. Template:Codeline is a bash script which will attempt to detect uncommented mirrors specified in Template:Filename which are closest to the installation machine based on latency. Faster mirrors will dramatically improve pacman performance, and the overall Arch Linux experience. This script may be run periodically, especially if the chosen mirrors provide inconsistent throughput and/or updates. Note that Template:Codeline does not test for throughput. Tools such as Template:Codeline or Template:Codeline may be used to effectively test for mirror throughput after a new Template:Filename has been generated.

Issue the following command to completely refresh package database, upgrade and install Template:Codeline: Template:Cli

  • If you get an error at this step, use the command Template:Codeline and uncomment a server that suits you.

Template:Codeline to the Template:Filename directory: Template:Cli Backup the existing Template:Filename: Template:Cli Edit mirrorlist.backup and uncomment all mirrors on the same continent or within geographical proximity to test with rankmirrors. Template:Cli Run the script against the mirrorlist.backup with the -n switch and redirect output to a new /etc/pacman.d/mirrorlist file: Template:Cli

Note: -n 6: will rank the 6 closest mirrors

Force pacman to refresh all package lists with the new mirrorlist in place: Template:Cli

Mirrorcheck for up-to-date packages

Since Template:Codeline does not take into account how up-to-date a mirror's package list is, it is important to note that one or more of the mirrors it selects as fastest may still be out-of-date. ArchLinux MirrorStatus reports various aspects about the mirrors such as network problems with mirrors, data collection problems, the last time mirrors have been synced, etc. One may wish to manually inspect Template:Filename, ensuring that the file contains only up-to-date mirrors if having the latest package versions is a priority.

Alternatively, the Mirrorlist Generator can automatically rank mirrors close to your location by how up-to-date they are.

Tip: For a script that automates the process of getting and installing a Template:Filename file from the Pacman Mirrorlist Generator, see Mirrors.

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(8) tool. Try: Template:Cli

For more information, have a look at the pacman wiki entry at your own leisure, or check out the pacman rosetta entry for a comparison to other popular package managers.

Update the System

You are now ready to upgrade your entire system. Before you do, read through the news (and optionally the announce mailing list). Often the developers will provide important information about required configurations and modifications for known issues. Consulting these pages before any upgrade is good practice.

Sync, refresh, and upgrade your entire new system with: Template:Cli or: Template:Cli

pacman will now download a fresh copy of the master package list from the server(s) defined in Template:Filename and perform all available upgrades. You may be prompted to upgrade pacman itself at this point. If so, say yes, and then reissue the Template:Codeline command when finished.

Reboot if a kernel upgrade has occurred.

Note: Occasionally, configuration changes may take place requiring user action during an update; read pacman's output for any pertinent information. See Pacnew and Pacsave Files for more details.

Pacman output is saved in Template:Filename.

See Package Management FAQ for answers to frequently asked questions regarding updating and managing your packages.

Ignoring Packages

After executing the command Template:Codeline, 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 (Template:Codeline for details) or permanently indicate the package(s) to skip in the Template:Filename 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 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 IgnorePkg in Template:Filename is therefore discouraged, and should only be used sparingly, if you know what you are doing.

The Arch rolling release model

Keep in mind that Arch is a rolling release distribution. This means there is never a reason to reinstall or perform elaborate system rebuilds to upgrade to the newest version. Simply issuing Template:Codeline periodically keeps your entire system up-to-date and on the bleeding edge. At the end of this upgrade, your system is completely current. Remember to reboot if a kernel upgrade has occurred.

Adding a User

Note: Before adding your users, consider hardening your system by switching from md5 password hashes to sha512 password hashes (see: SHA password hashes).

Linux is a multi-user environment. You should not do your everyday work using the root account: it is more than poor practice, it is dangerous. Use root for administrative tasks only and instead add a normal user account using the Template:Codeline program:


You will be asked to enter some information in an interactive way. In the following example we are creating the user archie:

Login name for new user []: archie

User ID ('UID') [ defaults to next available ]:

Initial group [ users ]:

Additional groups (comma separated) []: audio,lp,optical,storage,video,wheel,games,power,scanner

Home directory [ /home/archie ]:

Shell [ /bin/bash ]:

Expiry date (YYYY-MM-DD) []:

As showed 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
  • lp - for managing printing tasks
  • optical - for managing tasks pertaining to the optical drive(s)
  • storage - for managing storage devices
  • video - for video tasks and hardware acceleration
  • wheel - for using sudo
  • games - needed for write permission for games in the games group
  • power - used with power options (e.g. shutdown with power button)
  • scanner - for using a scanner

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 informations for the new user (e.g. the full name). After that, you will be asked to enter the password for your account.

Your new non-root user has finally been created, complete with a home directory and a login password.

See 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:Codeline and Template:Codeline.

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 Template:Filename: Template:Cli The Template:Codeline option will remove the user's home directory and its content, along with the the user's mail spool.


You should now have a completely functional Arch system which will act as a suitable base for you to build upon based on your needs. However, most people are interested in a desktop system, complete with sound and graphics. This part of the guide will provide a brief overview of the procedure to acquire these extras.

Create DVD and CDROM symlinks

Many desktop applications will expect the presence of CDROM and DVD symlinks to the Template:Filename device node. Four useful symlinks may be created as so: Template:Cli To make the symlinks persistently created after each boot, add the above command to Template:Filename.

Alternatively, you may wish to add the commands sequentially for readability:

# /etc/rc.local: Local multi-user startup script.
# create optical drive symlinks
ln -s /dev/sr0 /dev/cdrom
ln -s /dev/sr0 /dev/cdrw
ln -s /dev/sr0 /dev/dvd
ln -s /dev/sr0 /dev/dvdrw


Install Sudo: Template:Cli To add a user as a sudo user (a "sudoer"), the visudo command must be run as root.

By default, the visudo command uses the editor vi. If you do not know how to use vi, you may set the EDITOR environment variable to the editor of your choice, such as in this example with the editor "nano":

# EDITOR=nano visudo
Note: Please note that you are setting the variable and starting visudo on the same line at the same time. This will not work properly as two separated commands.

If you are comfortable using vi, issue the visudo command without the EDITOR=nano variable: Template:Cli This will open the file Template:Filename in a special session of vi. visudo copies the file to be edited to a temporary file, edits it with an editor, (vi by default), and subsequently runs a sanity check. If it passes, the temporary file overwrites the original with the correct permissions.

Warning: Do not edit Template:Filename directly with an editor; errors in syntax can cause annoyances (like rendering the root account unusable). You must use the visudo command to edit Template:Filename.

In the previous section we added your user to the "wheel" group. To give users in the wheel group full root privileges when they precede a command with "sudo", uncomment the following line:

%wheel	ALL=(ALL) ALL

Now you can give any user access to the sudo command by simply adding them to the wheel group.

For more information, such as sudoer <TAB> completion, see Sudo.


If you want sound, proceed to Advanced Linux Sound Architecture for instructions. Alternatively, proceed to the next section first, and set up sound later.

Note: ALSA usually works out-of-the-box, it just needs to be unmuted.

The Advanced Linux Sound Architecture (ALSA) is included with the kernel and it is recommended to try it first. However, if it does not work or you are not satisfied with the quality, the Open Sound System is a viable alternative. OSSv4 has been released under a free license and is generally considered a significant improvement over the older OSSv3 which was replaced by ALSA. Instructions can be found in the OSS article.

If you have advanced audio requirements, take a look at Sound for an overview of various articles.

Graphical User Interface

Install X

The X Window System (commonly X11, or X) is a networking and display protocol which provides windowing on bitmap displays. It provides the standard toolkit and protocol to build graphical user interfaces (GUIs).

Note: If you are installing Arch as a Virtualbox guest, you need a different way to complete X installation. See Arch Linux VirtualBox Guest, then jump to the configuration part below.

Now we will install the base Xorg packages using pacman.

Install the base packages: Template:Cli

Install mesa for 3D support: Template:Cli

The 3D utilities glxgears and glxinfo are included in the mesa-demos package. Install if needed: Template:Cli

Install video driver

Next, you should install a driver for your graphics card.

You will need knowledge of which video chipset your machine has. If you do not know, use the Template:Filename program: Template:Cli

Note: The vesa driver is the most generic, and should work with almost any modern video chipset. If you cannot find a suitable driver for your video chipset, vesa should work with any video card, but it offers only unaccelerated 2D performance.

For a complete list of all open-source video drivers, search the package database: Template:Cli

Note: Proprietary drivers for NVIDIA and ATI are covered in the next sections. If you plan on doing heavy 3D processing such as gaming, consider using these.

Use pacman to install the appropriate video driver for your video card/onboard video. Example for the Savage driver: Template:Cli

Tip: For some Intel graphics cards, configuration may be necessary to get proper 2D or 3D performance, see Intel for more information.
NVIDIA Graphics Cards

NVIDIA users have three options for drivers (in addition to the vesa driver):

  • The open-source nouveau driver, which offers fast 2d acceleration and experimental 3d support which is good enough for basic compositing (note: does not fully support powersaving yet). Feature Matrix.
  • The open-source (but obfuscated) nv driver, which is very slow and only has 2d support.
  • The proprietary nvidia drivers, which offer good 3d performance and powersaving. Even if you plan on using the proprietary drivers, it is recommended to start with nouveau and then switch to the binary driver after you have X set up and working. Nouveau often works out-of-the-box, while nvidia will require configuration and likely some troubleshooting. See NVIDIA for more information.

The open-source nouveau driver should be good enough for most users and is recommended: Template:Cli

For experimental 3D support: Template:Cli

Tip: For advanced instructions, see Nouveau.
ATI Graphics Cards

ATI owners have two options for drivers (in addition to the vesa driver):

  • The open source radeon driver provided by the xf86-video-ati package. See the radeon feature matrix for details.
  • The proprietary fglrx driver provided by the catalyst package located in the AUR. It supports only newer devices (HD2xxx and newer). It was once a package offered by Arch in the extra repository, but as of March 2009, official support has been dropped because of dissatisfaction with the quality and speed of development of the proprietary driver. See ATI Catalyst for more information.

The open-source driver is the recommended choice. Install the radeon ATI Driver: Template:Cli

Tip: For advanced instructions, see ATI.

Install input drivers

Udev should be capable of detecting your hardware without problems and evdev (xf86-input-evdev) is the modern, hotplugging input driver for almost all devices so in most cases, installing input drivers is not needed. At this point, evdev has already been installed as a dependency of Xorg.

If evdev does not support your device, install the needed driver from the xorg-input-drivers group.

For a complete list of available input drivers, invoke a pacman search: Template:Cli

Note: You only need xf86-input-keyboard or xf86-input-mouse if you plan on disabling hotplugging, otherwise, evdev will act as the input driver.

Laptop users (or users with a touchscreen) will also need the synaptics package to allow X to configure the touchpad/touchscreen: Template:Cli

Tip: For instructions on fine tuning or troubleshooting touchpad settings, see the Touchpad Synaptics article.

Configure X (Optional)

Warning: Proprietary drivers usually require a reboot after installation along with configuration. See NVIDIA or ATI Catalyst for details.

X Server features auto-configuration and therefore can function without an Template:Filename. If you still wish to manually configure X Server, please see the Xorg wiki page.

Non-US keyboard

If you do not use a standard US keyboard, you need to set the keyboard layout in Template:Filename:

Section "InputClass"
    Identifier "evdev keyboard catchall"
    MatchIsKeyboard "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    Option "XkbLayout" "be"

If, for example, you wish to use a variant of the US keyboard, add the following into the same section from the previous example:

Option "XkbLayout" "us"
Option "XkbVariant" "dvorak"
Note: The XkbLayout key may differ from the keymap code you used with the km or loadkeys command. A list of many keyboard layouts and variants can be found in Template:Filename (see text after line beginning with Template:Codeline). For instance the layout: gb corresponds to "English (UK)".

Testing X

This section will explain how to start a very basic graphical environment in order to test X. This uses the simple default X window manager, twm.

Install the default test environment:


The default X environment is rather bare. This section below will deal with installing a desktop environment or window manager of your choice to supplement X.

If you installed Xorg before creating your regular user, there will be an empty Template:Filename file in your $HOME that you need to either delete or edit in order to start a graphical environment. Simply deleting it will cause X to run with the default environment (twm, xclock, xterm).


Message bus
Note: dbus is likely required for many of your applications to work properly, if you know you do not need it, skip this section.

Install dbus: Template:Cli

Start the dbus daemon: Template:Cli Add dbus to your DAEMONS array so it starts automatically on boot: Template:File

Start X
Note: The Ctrl-Alt-Backspace shortcut traditionally used to kill X has been deprecated and will not work to exit out of this test. You can enable Ctrl-Alt-Backspace by editing Template:Filename, as described here.

Finally, start Xorg: Template:Cli

or: Template:Cli

A few movable windows should show up, and your mouse should work. Once you are satisfied that X installation was a success, you may exit out of X by issuing the Template:Codeline command into the prompts until you return to the console.

If the screen goes black, you may still attempt to switch to a different virtual console (CTRL-Alt-F2, for example), and login blindly as root, followed by <Enter>, followed by root's password followed by <Enter>.

You can attempt to kill the X server with Template:Filename (note the capital letter X): Template:Cli

If pkill does not work, reboot blindly with: Template:Cli

In case of errors

If a problem occurs, look for errors in Template:Filename. Be on the lookout for any lines beginning with Template:Codeline which represent errors, and also Template:Codeline which are warnings that could indicate other issues. Template:Cli

Errors may also be searched for in the console output of the virtual console from which X was started.

See the Xorg article for detailed instructions and troubleshooting.

Need Help?

If you are still having trouble after consulting the Xorg article and need assistance via the Arch forums, be sure to install and use wgetpaste:

Template:Cli Use wgetpaste and provide links for the following files when asking for help in your forum post:

  • ~/.xinitrc
  • /etc/X11/xorg.conf
  • /var/log/Xorg.0.log
  • /var/log/Xorg.0.log.old

Use it like so: Template:Cli Post the corresponding links given within your forum post. Be sure to provide appropriate hardware and driver information as well.

Note: It is very important to provide detail when troubleshooting X. Please provide all pertinent information as detailed above when asking for assistance on the Arch forums.

Install Fonts

At this point, you may wish to save time by installing visually pleasing, true type fonts, before installing a desktop environment/window manager. DejaVu is a set of high quality, general-purpose fonts.

Install with: Template:Cli

  • Refer to Font Configuration for how to configure font rendering and Fonts for font suggestions and installation instructions.
  • Steps to install Microsoft fonts are detailed in the MS Fonts article.

Choose and install a graphical interface

The X Window System provides the basic framework for building a graphical user interface (GUI).

Note: Choosing your DE or WM is a very subjective and personal decision. Choose the best environment for your needs.
Window Manager (WM) 
Controls the placement and appearance of application windows in conjunction with the X Window System. See Window managers for more information.
Desktop Environment (DE)
Works atop and in conjunction with X, to provide a completely functional and dynamic GUI. A DE typically provides a window manager, icons, applets, windows, toolbars, folders, wallpapers, a suite of applications and abilities like drag and drop. See Desktop environments for more information.
Note: You can build your own DE by using a WM and the applications of your choice.

After installing a graphical interface, you may wish to continue with General Recommendations for post-installation instructions.

Methods for starting your Graphical Environment


You might prefer to start X manually from your terminal rather than booting straight into the desktop. For DE-specific commands, please see the wiki page corrosponding to your DE for more information. For more generic X commands, please see the section on the Xorg page.


You might prefer to have the desktop start automatically during boot instead of starting X manually. See Display Manager for instructions on using a login manager or Start X at Boot for two lightweight methods that do not rely on a display manager.Template:Beginners' Guide navigation