Difference between revisions of "Beginners' guide"

From ArchWiki
Jump to: navigation, search
(Wireless: no need to leave the chroot. And some other changes...)
(#REDIRECT Installation guide, merge completed, see Talk:Installation_guide#BG_merge)
Line 1: Line 1:
#REDIRECT [[Installation guide]]
[[Category:Getting and installing Arch]]
[[Category:About Arch]]
[[da:Beginners' Guide/Installation]]
[[es:Beginners' Guide/Installation]]
[[hr:Beginners' Guide/Installation]]
[[hu:Beginners' Guide/Installation]]
[[it:Beginners' Guide/Installation]]
[[ko:Beginners' Guide/Installation]]
[[nl:Beginners' Guide/Installatie]]
[[pt:Beginners' Guide/Installation]]
[[ru:Beginners' Guide/Installation]]
[[sr:Beginners' Guide/Installation]]
[[zh-CN:Beginners' Guide/Installation]]
{{Tip|This is part of a multi-page article for The Beginners' Guide. '''[[Beginners' Guide|Click here]]''' if you would rather read the guide in its entirety.}}
== Installation ==
You are now presented with a shell prompt, automatically logged in as root.
=== Change the keymap ===
{{Tip|This step is optional for the vast majority of users and it can be used at any point during the instalation. Useful only if you plan on writing in your own language in any of the configuration files, if you use diacritical marks in the wifi password, etc.}}
By default, the keyboard layout is set to {{ic|us}}. If you have a non-[[Wikipedia:File:KB_United_States-NoAltGr.svg|US]] keyboard layout, run:
# loadkeys ''layout''
...where ''layout'' can be {{ic|fr}}, {{ic|uk}}, {{ic|be-latin1}}, etc. See [[KEYMAP#Keyboard_layouts|here]] for a comprehensive list.
{{Keypress|Alt + Shift}} activates it.
Don't worry if some of the letters show up as white squares or as other symbols. It's probably just the console font missing those glyphs. The glyph codes are correct and if you press the correct keys they will show up fine when ''(or if)'' you set up a graphical environment later.
=== Establish an internet connection ===
The {{ic|dhcpcd}} network daemon is started automatically at boot and it will attempt to start a wired connection, if available. Try pinging a website to see if it was successful. And since Google is always on...
{{hc|# ping -c 3 www.google.com|2=
PING www.l.google.com ( 56(84) bytes of data.
64 bytes from wb-in-f105.1e100.net ( icmp_req=1 ttl=50 time=17.0 ms
64 bytes from wb-in-f105.1e100.net ( icmp_req=2 ttl=50 time=18.2 ms
64 bytes from wb-in-f105.1e100.net ( icmp_req=3 ttl=50 time=16.6 ms
--- www.l.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 16.660/17.320/18.254/0.678 ms}}
If you get a {{ic|ping: unknown host}} error, you will need to set up the network manually, as explained below.
Otherwise, move on to [[#Prepare_the_storage_drive|Prepare the storage drive]].
==== Wired ====
Follow this procedure if you need wired connectivity (Ethernet) during the installation process.
If your computer is connected to an Ethernet network, in most cases, you will have one interface, called {{ic|eth0}}. If you have additional network cards (apart from the one integrated on the motherboard, for example), their name will follow the sequence {{ic|eth1}}, {{ic|eth2}}, etc.
You need to know these settings:
* Static IP address.
* Subnet mask.
* Gateway's IP address.
* Name servers' (DNS) IP addresses.
* Domain name (unless you're on a local LAN, in which case you can make it up).
Activate the connected Ethernet interface, e.g. for {{ic|eth0}}:
# ip link set eth0 up
Add the address:
# ip addr add <ip address>/<subnetmask> dev <interface>
For example:
# ip addr add dev eth0
For more options, run {{ic|man ip}}.
Add your gateway like this, substituting your own gateway's IP address:
# ip route add default via <ip address>
For example:
# ip route add default via
Edit {{ic|resolv.conf}}, substituting your name servers' IP addresses and your local domain name:
{{hc|# nano /etc/resolv.conf|
nameserver 61.95.849.8
search example.com}}
{{Note|Currently, you may include a maximum of 3 {{ic|nameserver}} lines.}}
You should now have a working network connection. If you do not, check the detailed [[Configuring Network]] page.
==== Wireless ====
Follow this procedure if you need wireless connectivity (WiFi) during the installation process.
The wireless drivers and utilities are now available to you in the live environment of the installation media. A good knowledge of your wireless hardware will be of key importance to successful configuration. Note that the following quick-start procedure ''executed at this point in the installation'' will initialize your wireless hardware for use ''in the live environment of the installation media''. These steps (or some other form of wireless management) '''must be repeated from the actual installed system after booting into it'''.
Also note that these steps are optional if wireless connectivity is unnecessary at this point in the installation; wireless functionality may always be established later.
{{Note|The following examples use {{ic|wlan0}} for the interface and {{ic|linksys}} for the ESSID. Remember to change these values according to your setup.}}
The basic procedure will be:
* (optional) Identify the wireless interface:
# lspci | grep -i net
or, if using a USB adapter:
# lsusb
* Ensure udev has loaded the driver, and that the driver has created a usable wireless kernel interface with {{ic|iwconfig}}:
{{hc|# iwconfig|<nowiki>
lo no wireless extensions.
eth0 no wireless extensions.
wlan0    unassociated  ESSID:""
        Mode:Managed  Channel=0  Access Point: Not-Associated
        Bit Rate:0 kb/s  Tx-Power=20 dBm  Sensitivity=8/0
        Retry limit:7  RTS thr:off  Fragment thr:off
        Power Management:off
        Link Quality:0  Signal level:0  Noise level:0
        Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
        Tx excessive retries:0  Invalid misc:0  Missed beacon:0</nowiki>}}
{{ic|wlan0}} is the available wireless interface in this example.
{{Note|If you do not see output similar to this, then your wireless driver has not been loaded. If this is the case, you must load the driver yourself. Please see [[Wireless Setup]] for more detailed information.}}
* Bring the interface up with:
# ip link set wlan0 up
A small percentage of wireless chipsets also require firmware, in addition to a corresponding driver. If the wireless chipset requires firmware, you are likely to receive this error when bringing the interface up:
{{hc|# ip link set wlan0 up|
SIOCSIFFLAGS: No such file or directory}}
If unsure, invoke {{ic|dmesg}} to query the kernel log for a firmware request from the wireless chipset.
Example output from an Intel chipset which requires and has requested firmware from the kernel at boot:
{{hc|# dmesg <nowiki>|</nowiki> grep firmware|
firmware: requesting iwlwifi-5000-1.ucode}}
If there is no output, it may be concluded that the system's wireless chipset does not require firmware.
{{Warning|Wireless chipset firmware packages (for cards which require them) are pre-installed under {{ic|/usr/lib/firmware}} in the live environment (on CD/USB stick) '''but must be explicitly installed to your actual system to provide wireless functionality after you reboot into it!''' Package installation is covered later in this guide. Ensure installation of both your wireless module and firmware before rebooting! See [[Wireless Setup]] if you are unsure about the requirement of corresponding firmware installation for your particular chipset. This is a very common error.}}
Next, use {{pkg|netcfg}}'s wifi-menu to connect to a network:
# wifi-menu
You should now have a working network connection. If you do not, check the detailed [[Wireless Setup]] page.
==== xDSL (PPPoE), analog modem or ISDN ====
If you have a modem or a router in bridge mode, run:
# pppoe-setup
* Type in the username that the ISP provided you with.
* Press {{Keypress|Enter}} for "eth0".
* Press {{Keypress|Enter}} for "no", so that it stays up continuously.
* Type {{ic|server}} (since this is usually the case).
* Press {{Keypress|1}} for a firewall.
* Type in the password that the ISP provided you with.
* Press {{Keypress|y}} at the end.
To use these settings and connect to your ISP, run:
# pppoe-start
For an ''analog'' modem, see [[Direct Modem Connection]].
==== Behind a proxy server ====
If you are behind a proxy server, you will need to export the {{ic|http_proxy}} and {{ic|ftp_proxy}} environment variables. '''[[Proxy|Click here]]''' for more information.
=== Prepare the storage drive ===
{{Warning|Partitioning can can destroy data. You are '''strongly''' cautioned and advised to backup any critical data before proceeding.}}
Absolute beginners are encouraged to use a graphical partitioning tool. [http://gparted.sourceforge.net/download.php GParted] is a good example, ran from a "live" Linux distribution such as [[Wikipedia:Parted_Magic|Parted Magic]], [[Wikipedia:Ubuntu_(operating_system)|Ubuntu]], [[Wikipedia:Linux_Mint|Linux Mint]], etc. See [[Partitioning]] for some general tips and make sure to format the partitions with a filesystem (e.g. '''ext4''', '''btrfs''', etc) before rebooting.
If you have already done so, proceed to [[#Mount_the_partitions|Mount the partitions]].
Otherwise, see the following example.
==== Example ====
The Arch Linux install media includes the following partitioning tools:
* [[Wikipedia:cfdisk|cfdisk]] – supports only [[MBR]] partition tables.
* [[Wikipedia:gdisk|gdisk]] – supports only [[GPT]] partition tables.
* [[Wikipedia:parted|parted]] – supports both.
This example uses '''cfdisk''', but it can be easily followed using '''gdisk''', which will allow for GPT partitioning.
{{Note|If you are installing to a USB flash key, see [[Installing Arch Linux on a USB key]].}}
{{Note|If you are not dual booting with Windows, then it is advisable to use [[GPT]] instead of [[MBR]]. GPT partitioning can only be done with '''gdisk''' or '''parted'''. Read [[GPT]] for the list of advantages.}}
# cfdisk /dev/sda
The example system will contain a 15GB root ({{ic|/}}) partition, a 1GB {{ic|swap}} partition, and a {{ic|/home}} partition for the remaining space.
It should be emphasized that partitioning is a personal choice and that this example is only for illustrative purposes. See [[Partitioning]].
{{Note|If you have a UEFI motherboard you will need another partition to host the UEFI System partition. Read [[Unified_Extensible_Firmware_Interface#Create_an_UEFI_System_Partition_in_Linux|this article]].}}
* Choose New (or press {{Keypress|N}}).
* Press {{Keypress|Enter}} for Primary.
* Type "15440".
* Press {{Keypress|Enter}} for Beginning.
* Press {{Keypress|Enter}} for Bootable.
* Press the down arrow to move to the free space area and choose New (or press {{Keypress|N}}).
* Press {{Keypress|Enter}} for Primary.
* Type "1024".
* Press {{Keypress|Enter}} for Beginning.
* Choose Type (or press {{Keypress|T}}).
* Press any key to scroll down the list.
* Press {{Keypress|Enter}} for {{ic|82}}.
* Press the down arrow to move to the free space area and choose New (or press {{Keypress|N}}).
* Press {{Keypress|Enter}} for Primary.
* Press {{Keypress|Enter}} to use the rest of the drive (or you could type in the desired size).
Here's how it should look like:
Name    Flags    Part Type    FS Type          [Label]      Size (MB)
sda1    Boot      Primary    Linux                            15440
sda2              Primary    Linux swap / Solaris              1024
sda3              Primary    Linux                            133000*
Double check and make sure that you are happy with the partition sizes as well as the partition table layout before continuing.
If you would like to start over, you can simply select Quit (or press {{Keypress|Q}}) to quit without saving changes and then restart cfdisk.
If you are satisfied, choose Write (or press {{Keypress|Shift+W}}) to finalize and to write the partition table to the drive. Type "yes" and choose Quit (or press {{Keypress|Q}}) to exit cfdisk without making any more changes.
Simply partitioning is not enough; the partitions also need a [[File Systems|filesystem]]. To format the partitions with an ext4 filesystem:
# mkfs.ext4 /dev/sda1
# mkfs.ext4 /dev/sda3
Format and activate the swap partition:
# mkswap /dev/sda2
# swapon /dev/sda2
=== Mount the partitions ===
Each partition is identified with a number suffix. For example, {{ic|sda1}} specifies the first partition of the first drive, while {{ic|sda}} designates the entire drive.
To see the current drive identities and layout:
# fdisk -l
First, mount the root partition on {{ic|/mnt}}:
# mount /dev/sda3 /mnt
Then mount any other separate partition (/home, /boot, /var, etc), if you have any:
# mkdir /mnt/home
# mount /dev/sda4 /mnt/home
# mkdir /mnt/boot
# mount /dev/sda1 /mnt/boot
=== Select installation mirror ===
Before installing, you may want to edit the {{ic|mirrorlist}} file and place your preferred mirror first. A copy of this file will be installed on your new system by {{ic|pacstrap}} as well, so it's worth getting it right.
{{hc|# nano /etc/pacman.d/mirrorlist|2=
## Arch Linux repository mirrorlist
## Sorted by mirror score from mirror status page
## Generated on 2012-MM-DD
## Score: #, Country
Server = http://mirror.example.xyz/archlinux/$repo/os/$arch
* {{Keypress|Alt+6}} to copy a {{ic|Server}} line.
* {{Keypress|PageUp}} key to scroll up.
* {{Keypress|Ctrl+U}} to paste it at the top of the list.
If you want, you can make it the ''only'' mirror available by getting rid of everything else (using {{Keypress|Ctrl+K}}), but it's usually a good idea to have a few more, in case the first one goes offline.
{{Tip|Use the [http://www.archlinux.org/mirrorlist/ Mirrorlist Generator] to get an updated list for your country. HTTP mirrors are faster than FTP, because of something called [[Wikipedia:Keepalive|keepalive]]. With FTP, pacman has to send out a signal each time each time it downloads a package, resulting in a brief pause.}}
=== Install the base system ===
The base system is installed using the [https://github.com/falconindy/arch-install-scripts/blob/master/pacstrap.in pacstrap] script.
# pacstrap /mnt base base-devel
* {{Grp|base}}: Software packages from the [core] repo to provide the minimal base environment.
* {{Grp|base-devel}}: Extra tools from [core] such as {{ic|make}}, and {{ic|automake}}. Most beginners should choose to install it, as it will likely be needed to expand the system. The ''base-devel'' group will be required to install software from the [[Arch User Repository]].
This will give you a basic Arch system. Other packages can be installed later using [[pacman]].
{{Note|If pacman fails to verify your packages, check your system time. If the system date is invalid (e.g. it shows year 2010), signing keys will be considered expired (or invalid), signature checks on packages will fail and installation will be interrupted. Make sure to correct the system time, either by doing so manually or with the {{Pkg|ntp}} client, and retry running the pacstrap command. Refer to [[Time]] page for more information on correcting system time.}}
=== Generate an fstab ===
Generate an [[fstab]] file with the following command. If you prefer to use UUIDs or labels, add the {{ic|-U}} or {{ic|-L}} option, respectively. It's also a good idea to check it before continuing:
{{Note|If you encounter errors running genfstab or later in the install process, do '''not''' run genfstab again; just edit the fstab file.}}
# genfstab -p /mnt >> /mnt/etc/fstab
# nano /mnt/etc/fstab
Only the "/" partition needs "1" for the last field. Everything else should have "2" or "0" (see [[Fstab#Field_definitions|Field definitions]]).
=== Chroot into the system ===
Next we [[chroot]] into our newly installed system.
# arch-chroot /mnt
=== Configure the base system ===
{{Tip|Closely following and understanding these steps is of key importance to ensure a properly configured system.}}
At this stage of the installation, you will configure the primary configuration files of your Arch Linux base system.
{{ic|/etc/rc.conf}} is the configuration file for Arch's initscripts, and in the past used to also contain configurations for other parts of the system. Unless you are using an alternate init system like [[systemd]], this file specifies which daemons to start during boot-up and some networking and storage information.
{{Note|Using the legacy configuration options in {{ic|rc.conf}} for system configuring still works (for now) with the default init system, but the new configuration files take precedence and using them is recommended. The new files will also work for configuring [[systemd]].}}
{| class="wikitable"
! scope="col"| Configuration
! scope="col"| Configuration file(s)
! scope="col"| Legacy [https://projects.archlinux.org/initscripts.git/tree/rc.conf?id=97f0cd6751e8d22c14d7492cdc2186cf41157ba6 rc.conf] section
| align="center"|Hostname
| align="left"|{{ic|/etc/hostname}}
| align="center"|{{ic|NETWORKING}}
| align="center"|Console fonts and keymap
| align="left"|{{ic|/etc/vconsole.conf}}
| align="center"|{{ic|LOCALIZATION}}
| align="center"|Locale
| align="left"|{{ic|/etc/locale.conf}}
| align="center"|{{ic|LOCALIZATION}}
| align="center"|Timezone
| align="left"|{{ic|/etc/timezone}}
| align="center"|{{ic|LOCALIZATION}}
| align="center"|Hardware clock
| align="left"|{{ic|/etc/adjtime}}
| align="center"|{{ic|LOCALIZATION}}
| align="center"|Kernel modules
| align="left"|{{ic|/etc/modules-load.d/}}
| align="center"|{{ic|HARDWARE}}
| align="center"|Daemons
| align="left"|{{ic|/etc/rc.conf}}
| align="center"|{{ic|DAEMONS}}
| align="center"|Wired network
| align="left"|{{ic|/etc/rc.conf}}
| align="center"|{{ic|NETWORKING}}
Configuration files can be created if they do not exist, or edited if you wish to change the defaults.
For this, you can use the editor [[Nano]]. Press {{Keypress|Ctrl+X}} and when prompted to save changes, press {{Keypress|Y}} and {{Keypress|Enter}} to use the same filename, or you can press {{Keypress|N}} to exit without saving.
==== Hostname ====
Add your ''hostname'' in {{ic|/etc/hostname}}:
# echo '''myhostname''' > /etc/hostname
Set it to your liking (e.g. ''arch''). This is the name of your computer. And add it to {{ic|/etc/hosts}}, as well:
{{Warning|This format, including {{ic|localhost}} and your actual hostname, is required for program compatibility. Errors in these entries may cause poor network performance and/or certain programs to open very slowly, or not work at all.}}
{{hc|# nano /etc/hosts|  localhost.localdomain  localhost '''myhostname'''
::1        localhost.localdomain  localhost '''myhostname'''
# '''myhostname'''.domain.org '''myhostname'''  #Uncomment if you use a static IP and remove this comment.}}
{{Note|{{ic|::1}} is the IPv6 equivalent of {{ic|}} and should be added.}}
{{Tip|For convenience, you may also use {{ic|/etc/hosts}} aliases for hosts on your network, and/or on the Web. media data
The above example would allow you access a media and data server on your network by name and without the need for typing out their respective IP addresses.}}
==== Console fonts and keymap ====
To edit {{ic|vconsole.conf}}:
{{hc|# nano /etc/vconsole.conf|2=
* {{ic|KEYMAP}} – If you want, you can use the one from the beginning of the install process: [[#Change_the_keymap|Change the keymap]], but the default ({{ic|us}}) is fine for the vast majority of keyboards. Please note that this setting is only valid for your TTYs, not any graphical window managers or '''Xorg'''.
* {{ic|FONT}} – Available alternate console fonts reside in {{ic|/usr/share/kbd/consolefonts/}}. The default (blank) is safe.
* {{ic|FONT_MAP}} – Defines the console map to load with the setfont program at boot. Possible maps are found in {{ic|/usr/share/kbd/consoletrans}}, if needed. The default (blank) is safe.
See [[Fonts#Console_fonts|Console fonts]] and {{ic|man vconsole.conf}} for more information.
==== Timezone ====
Available time zones and subzones can be found in the {{ic|/usr/share/zoneinfo/<Zone>/<SubZone>}} directories.
To view the available <Zone>, check the directory {{ic|/usr/share/zoneinfo/}}:
# ls /usr/share/zoneinfo/
Similarly, you can check the contents of directories belonging to a <SubZone>:
# ls /usr/share/zoneinfo/Europe
Create a symbolic link {{ic|/etc/localtime}} to your zone file {{ic|/usr/share/zoneinfo/<Zone>/<SubZone>}} using this command:
# ln -s {{ic|/usr/share/zoneinfo/<Zone>/<SubZone>}} /etc/localtime
# ln -s /usr/share/zoneinfo/Europe/Minsk /etc/localtime
If you are using systemd's timedated, you might wish to also edit the file {{ic|/etc/timezone}} and write your {{ic|Zone}}/{{ic|Subzone}}.
{{hc|# nano /etc/timezone|
Read {{ic|man tzset}} for more options.
The need for {{ic|/etc/timezone}} might go away in the future [http://cgit.freedesktop.org/systemd/systemd/commit/?id=9cb48731b29f508178731b45b0643c816800c05e].
==== Locale ====
Locales are used by '''glibc''' and other locale-aware programs or libraries for rendering text, correctly displaying regional monetary values, time and date formats, alphabetic idiosyncrasies, and other locale-specific standards. For a comprehensive list of locales and what they stand for, see [http://www.greendesktiny.com/support/knowledgebase_detail.php?ref=EUH-483 here].
If you would like to receive system messages in English during the install process and after rebooting, keep reading. Otherwise, see the [[#Example_for_languages_other_than_English|example]].
There are two files that need editing: {{ic|locale.gen}} and {{ic|locale.conf}}.
* The {{ic|locale.gen}} file is empty by default (everything is commented out) and you need to remove the {{ic|#}} in front of the line(s) you want. You may uncomment more lines than just English, as long as you choose their [[Wikipedia:UTF-8|UTF-8]] encoding.
{{hc|# nano /etc/locale.gen|
en_US.UTF-8 UTF-8
# locale-gen
This will run on every '''glibc''' upgrade, generating all the locales specified in {{ic|/etc/locale.gen}}.
* The {{ic|locale.conf}} file doesn't exist by default. Setting only {{ic|LANG}} should be enough. It will act as the default value for all other variables.
# echo "LANG=en_US.UTF-8" > /etc/locale.conf
To use other {{ic|LC_*}} variables, first run {{ic|locale}} to see the available options. For example, this will change the US {{ic|mm/dd/yyyy}} (AM/PM) time format to UK's {{ic|dd/mm/yyyy}} (24h):
{{hc|# nano /etc/locale.conf|2=
{{Warning|Using the {{ic|LC_ALL}} variable is strongly discouraged because it overrides everything.}}
===== Example for languages other than English =====
If you would like to receive system messages in some other language than English during the install process and after rebooting ''(German, in this example)'', the above procedures are:
{{hc|# nano /etc/locale.gen|
en_US.UTF-8 UTF-8
de_DE.UTF-8 UTF-8}}
# locale-gen
# echo "LANG=de_DE.UTF-8" > /etc/locale.conf
# export LANG=de_DE.UTF-8
==== Hardware clock ====
This is set in {{ic|/etc/adjtime}}. Set the hardware clock mode uniformly between your operating systems on the same machine. Otherwise, they will overwrite the time and cause clock shifts (which can cause time drift correction to be miscalibrated).
You can generate {{ic|/etc/adjtime}} automatically by using one of the following commands.
{{Note|Make sure that {{ic|HARDWARECLOCK}} in {{ic|/etc/rc.conf}} is not set when using this method.}}
* [[Wikipedia:Coordinated Universal Time|UTC]] (recommended)
# hwclock --systohc --utc
{{Note|Using UTC for the hardware clock does not mean time will be displayed in UTC in software.}}
* '''localtime''' (discouraged) - Used by default in Windows
# hwclock --systohc --localtime
{{Warning|Using ''localtime'' may lead to several known and unfixable bugs. However, there are no plans to drop support for ''localtime''.}}
===== Setting time in a Windows dual boot setup =====
If you are setting up a dual-boot with Windows on your system, you have two options:
* Recommended: Set both Arch Linux and Windows to use UTC (a quick registry fix is needed, see [https://help.ubuntu.com/community/UbuntuTime#Make_Windows_use_UTC this page] for instructions). Also, be sure to prevent Windows from synchronizing the time with the Internet, as it will make the hardware clock use ''localtime'' again. If you want such functionality (NTP sync), you should use [[ntpd]] on your Arch Linux installation instead.
* Not recommended: Set Arch Linux to ''localtime'' and remove {{ic|hwclock}} from the {{ic|DAEMONS}} array in {{ic|/etc/rc.conf}} (Windows will take care of hardware clock corrections).
==== Kernel modules ====
{{Tip|All needed modules are automatically loaded by udev, so you will rarely need to add something here. Only add modules that you know are missing.}}
For kernel modules to load during boot, place a {{ic|*.conf}} file in {{ic|/etc/modules-load.d/}}, with a name based on the program that uses them.
{{hc|# nano /etc/modules-load.d/virtio-net.conf|
# Load 'virtio-net.ko' at boot.
If there are more modules to load per {{ic|*.conf}}, the module names can be separated by newlines. A good example can be found [[VirtualBox#Auto-start_modules|here]].
Empty lines and lines starting with {{ic|#}} or {{ic|;}} are ignored.
==== Daemons ====
{{Tip|The {{ic|DAEMONS}} line need not be changed at this time, but it is useful to explain what daemons are, as they will be addressed later in this guide.}}
[[Wikipedia:Daemon (computing)|Daemons]] are programs that run in the background, waiting for events to occur and offering services. A few good examples are: a web server that waits for a request to deliver a page (e.g. {{ic|httpd}}), an SSH server waiting for a user to log in (e.g. {{ic|sshd}}), a daemon which writes system messages to a log file (e.g. {{ic|syslog-ng}}), a BitTorrent client (e.g. {{ic|rtorrent}}, {{ic|deluged}}), a music player (e.g. {{ic|mpd}}), a login manager (e.g. {{ic|gdm}}, {{ic|slim}}), a firewall (e.g. {{ic|iptables}}), etc. While these are full-featured applications, their work is usually not that visible. Their main advantage is that even if Xorg crashes (or is absent from the system), they will continue to work.
Daemons can be added to the {{ic|DAEMONS}} line in {{ic|/etc/rc.conf}} and they will start when the system boots, in the order that they are placed. Their names are the equivalent scripts from {{ic|/etc/rc.d/}}.
{{hc|# nano /etc/rc.conf|2=
DAEMONS=(network @syslog-ng netfs @crond)}}
* If a script name is prefixed with a bang ({{ic|!}}), it is not run.
* If a script is prefixed with an "at" symbol ({{ic|@}}), it is run in the background; the startup sequence will not wait for successful completion of this daemon before continuing to the next (this may shorten system boot time). Do not background daemons that are needed by other daemons. For example, {{ic|mpd}} depends on {{ic|network}}, so backgrounding {{ic|network}} may cause {{ic|mpd}} to break.
* Edit this line whenever new system services are installed, if starting them automatically during boot is desired.
A list of available services (and their running status) can be found using the command:
# rc.d list
=== Configure the network ===
You need to configure the network again, but this time for your newly installed environment. The procedure and prerequisites are very similar to the one described [[#Establish_an_internet_connection|above]], except we are going to make it persistent and automatically run at boot.
{{Note|For more in-depth information on network configration, visit [[Configuring Network]] and [[Wireless Setup]].}}
==== Wired ====
If you only use a single wired network connection, you can use the {{ic|network}} daemon, a simple solution for both dynamic and static IP addressing.
First, ensure that the daemon is listed in the {{ic|DAEMONS}} array:
{{hc|# nano /etc/rc.conf|2=
DAEMONS=(... network ...)}}
Then configure the {{ic|NETWORKING}} section of {{ic|/etc/rc.conf}} as follows, depending on your IP addressing type:
; Dynamic IP
Assuming the network interface to activate at start is {{ic|eth0}}, use this configuration:
Your DNS server addresses will be automatically filled in by the {{ic|dhcpcd}} daemon.
; Static IP
If you have a static IP address, use this configuration:
You will also need to add your name servers' (DNS) IP addresses and your local domain name to your {{ic|/etc/resolv.conf}} like this:
nameserver 61.95.849.8
search example.com
{{Tip|The {{ic|network}} daemon is suitable for systems connecting wired to a single network. For multiple network configurations (e.g. using a laptop), it is recommended to use a network manager program, such as [[netcfg]], which has been designed to manage both wired and wireless connections.}}
==== Wireless ====
The {{ic|network}} daemon is not sufficient to handle wireless networking. You will need to install other programs to configure and manage wireless network profiles, such as [[netcfg]]. [[NetworkManager]] and [[Wicd]] are popular alternatives.
* Install the required packages:
# pacman -S wireless_tools netcfg
If you use WPA/WPA2 encryption, install:
# pacman -S wpa_supplicant wpa_actiond
If your wireless adapter requires a firmware (as described [[#Wireless_1|above]] and also [[Wireless_Setup#Drivers_and_firmware|here]]), install the package containing your firmware. For example:
# pacman -S zd1211-firmware
* Create a network profile for your wireless connection in the {{ic|/etc/network.d}} directory:
** Copy and rename a configuration template from {{ic|/etc/network.d/examples/}} to {{ic|/etc/network.d/mynetwork}} (''mynetwork'' being an example; the name is not a network setting and does not need to match the wireless network name (SSID)). These templates are adapted to the type of your wireless connection, such as {{ic|wireless-wep}} or {{ic|wireless-wpa}}. See [[Netcfg#Configuration|here]] for a list of available templates and their usage.
** Set {{ic|INTERFACE}} to the correct wireless interface. This can be checked with {{ic|iwconfig}}.
** Ensure the {{ic|ESSID}} and {{ic|KEY}} (passkey) are set correctly for wireless connections. Typos in these fields are common errors.
*** Note that WEP ''string'' keys (not ''hex'' keys) must be specified with a leading {{ic|s:}} (e.g. {{ic|<nowiki>KEY="s:somepasskey"</nowiki>}}).
*** For WPA-Personal, it is possible to specify the passkey in plain text or as an encoded hex.
* Add {{ic|net-auto-wireless}} to the {{ic|DAEMONS}} array in {{ic|/etc/rc.conf}}:
{{hc|# nano /etc/rc.conf|2=
DAEMONS=(... net-auto-wireless ...)}}
* And specify the desired wireless interface with the {{ic|WIRELESS_INTERFACE}} variable in {{ic|/etc/conf.d/netcfg}}:
{{hc|# nano /etc/conf.d/netcfg|2=
It is also possible to define a list of network profiles that should be automatically connected with the {{ic|AUTO_PROFILES}} variable in {{ic|/etc/conf.d/netcfg}}. If {{ic|AUTO_PROFILES}} is not set, all wireless networks will be tried.
{{Note|[[netcfg|Netcfg]] also provides other daemons to connect automatically, including both wireless and wired networking. Refer to the [[netcfg]] article for more information.}}
==== Direct Modem Connection ====
For xDSL, analog modem (dial-up) and ISDN, see [[Direct Modem Connection]] for detailed instructions.
=== Create an initial ramdisk environment ===
Configure {{ic|/etc/mkinitcpio.conf}} as needed (see [[mkinitcpio]]) and create an initial ramdisk with
# mkinitcpio -p linux
{{Tip|Most users can simply accept the defaults provided in the {{ic|/etc/mkinitcpio.conf}} file.}}
=== Install and configure a bootloader ===
Install either Syslinux or GRUB. There is no need to install both. Syslinux is considered to be easier to understand and to configure because it has only one configuration file. In spite of GRUB's many configuration files ''(for which the recommended method is to re-generate the {{ic|grub.cfg}} file each time you change anything in one of those files)'', using GRUB could make it more comfortable to transition to BURG in the future, a much more [http://code.google.com/p/burg/wiki/Screenshots customizable] GRUB fork. Of course, Syslinux can also be customized. [https://bbs.archlinux.org/viewtopic.php?pid=1109328#p1109328 (*)]
==== Syslinux ====
{{Note|Syslinux does not yet support [[UEFI]].}}
Install the {{Pkg|syslinux}} package and edit {{ic|syslinux.cfg}} to point to the right root partition. This step is vital. If it points to the wrong partition, Arch Linux will not boot.
{{hc|# pacman -S syslinux
# nano /boot/syslinux/syslinux.cfg|<nowiki>
LABEL arch
        APPEND root=/dev/sda3 ro
Change {{ic|/dev/sda3}} to reflect your root partition (if you partitioned your drive as we did in the example, your root partition is sda1). Do the same for {{ic|LABEL archfallback}}.
Then type the following command to ''install'' the files ({{ic|-i}}), mark the partition ''active'' with the ''boot'' flag ({{ic|-a}}), and install the ''MBR'' boot code ({{ic|-m}}):
# syslinux-install_update -iam
For more information on configuring and using Syslinux, see [[Syslinux]].
==== GRUB ====
For BIOS motherboards:
# pacman -S grub-bios
# grub-install --target=i386-pc --recheck /dev/sda
For UEFI motherboards:
# pacman -S grub-efi-x86_64
# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck
{{Note|In rare cases you may need to use {{ic|grub-efi-i386}} instead; on older macs for instance, where Apple hardware uses some kind of mixture between UEFI v1.x and v2.x. In such cases, GRUB would only work with 32 bit modules, even though the CPU may be 64 bit.}}
{{Note|GRUB is not the only UEFI bootloader available. See [[UEFI Bootloaders]].}}
To prevent a (harmless) error message at boot time:
# mkdir -p /boot/grub/locale
# cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
Create the {{ic|grub.cfg}} file:
{{Tip|To automatically search for other operating systems on your computer, install {{Pkg|os-prober}} before running the next command:
# pacman -S os-prober
# grub-mkconfig -o /boot/grub/grub.cfg
For more information on configuring and using GRUB, see [[GRUB]].
=== Root password ===
Set the root password with:
# passwd
=== Unmount the partitions and reboot ===
Exit from the chroot environment:
# exit
Since the partitions are mounted under {{ic|/mnt}}, we use the following command to unmount them.
# umount /mnt/{boot,home,}
Exit the install, and reboot:
# reboot
{{Tip|Be sure to remove the installation media and change the boot preference in your BIOS (if you changed it to install); otherwise you may boot back into the installation media!}}<noinclude>{{Beginners' Guide navigation}}</noinclude>

Latest revision as of 11:34, 23 August 2016

Redirect to: