Beginners' Guide/Installation (Српски)
- 1 Install the Base System
- 1.1 Select an installation source
- 1.2 Set Clock
- 1.3 Prepare Hard Drive
- 1.4 Select Packages
- 1.5 Install Packages
- 1.6 Configure the System
- 1.6.1 /etc/rc.conf
- 1.6.2 /etc/fstab
- 1.6.3 /etc/mkinitcpio.conf
- 1.6.4 /etc/modprobe.d/modprobe.conf
- 1.6.5 /etc/resolv.conf
- 1.6.6 /etc/hosts
- 1.6.7 /etc/hosts.deny and /etc/hosts.allow
- 1.6.8 /etc/locale.gen
- 1.6.9 Pacman-Mirror
- 1.6.10 Root password
- 1.6.11 Done
- 1.7 Install Bootloader
- 1.8 Reboot
Install the Base System
As root, run the installer script from tty1:
You should next see the displayed Arch Linux Installation Framework screen.
Select an installation source
After a welcome screen, you will be prompted for an installation source. Choose the appropriate source for the installer you are using. If using a Netinstall image, relative speed and update status of source repository mirrors may be checked here.
- If you chose the CORE installer and wish to use the packages on the CD, select CD-ROM as source
- Alternatively, or if you're using the Netinstall installation media, select NET and see section below (Configure Network).
Configure Network (Netinstall)
You shall be prompted to load ethernet drivers manually, if desired. Udev is quite effective at loading the required modules, so you may assume it has already done so. At the next screen, select Setup Network. You may verify this by pressing <Alt>+F3 and invoking ifconfig -a. When done, return to tty1 by pressing <Alt>+F1
Available Interfaces will be presented. If an interface and HWaddr (HardWare address) is listed, then your module has already been loaded. If your interface is not listed, you may probe it from the installer, or manually do so from another virtual console. Select your interface to continue.
The installer will then ask if you wish to use DHCP. Choosing Yes will run dhcpcd to discover an available gateway and request an IP address; Choosing No will prompt you for your static IP, netmask, broadcast, gateway DNS IP, HTTP proxy, and FTP proxy. Afterwards, you will be returned to the Net Installation Menu
Select Choose Mirror and select an FTP/HTTP mirror. When finished, return to main menu.
(A)DSL Quickstart for the Live Environment
(If you have a modem or router in bridge mode to connect to your ISP)
Switch to another virtual console (<Alt> + F2), login as root and invoke
If everything is well configured in the end you can connect to your ISP with
Return to first virtual console with <ALT>+F1. Continue with Set Clock
Wireless Quickstart For the Live Environment
(If you need wireless connectivity 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 quickstart 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.
The basic procedure will be:
- Switch to a free virtual console, e.g.: <ALT>+F3
- Login as root
- (Optional) Identify the wireless interface:
# lspci | grep -i net
- Ensure udev has loaded the driver, and that the driver has created a usable wireless kernel interface with
wlan0 is the available wireless interface in this example.
- Bring the interface up with
/sbin/ifconfig <interface> up.
# ifconfig 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:
If unsure, invoke
/usr/bin/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:
If there is no output, it may be concluded that the system's wireless chipset does not require firmware.
- If the ESSID has been forgotten or is unknown, use
/sbin/iwlist <interface> scanto scan for nearby networks.
# iwlist wlan0 scan
- If using WPA encryption:
Using WPA encryption requires that the key be encrypted and stored in a file, along with the ESSID, to be used later for connection via
wpa_supplicant. Thus, a few extra steps are required:
For the purpose of simplifying and backup, rename the default wpa_supplicant.conf file:
# mv /etc/wpa_supplicant.conf /etc/wpa_supplicant.conf.original
wpa_passphrase, provide your wireless network name and WPA key to be encrypted and written to /etc/wpa_supplicant.conf
The following example encrypts the key 'my_secret_passkey' of the 'linksys' wireless network, generates a new configuration file (<file>/etc/wpa_supplicant.conf</file>), and subsequently redirects the encrypted key, writing it to the file:
# wpa_passphrase linksys "my_secret_passkey" > /etc/wpa_supplicant.conf
Check WPA Supplicant for more information and troubleshooting.
- Associate your wireless device with the access point you want to use. Depending on the encryption (none, WEP, or WPA), the procedure may differ. You need to know the name of the chosen wireless network (ESSID).
|No Encryption|| |
|WEP w/ Hex Key|| |
|WEP w/ ASCII passphrase|| |
- After utilizing the appropriate association method outlined above, wait a few moments and confirm you have successfully associated to the access point before continuing. e.g.:
# iwconfig wlan0
Output should indicate the wireless network is associated with the interface.
- Request an IP address with
/sbin/dhcpcd <interface>. e.g.:
# dhcpcd wlan0
- Lastly, ensure you can route using
# ping -c 3 www.google.com
You should have a working network connection. For troubleshooting, check the detailed Wireless Setup page.
Return to tty1 with <ALT>+F1. Continue with Set Clock
- UTC - Choose UTC if running only UNIX-like operating system(s).
- localtime - Choose local if multi-booting with a Microsoft Windows OS.
Prepare Hard Drive
Verify current disk identities and layout by invoking
/sbin/fdisk with the
-l (lower-case L) switch.
Open another virtual console (<ALT>+F3) and enter:
# fdisk -l
Take note of the disk(s)/partition(s) to utilize for the Arch installation.
Switch back to the installation script with <ALT>+F1
Select the first menu entry "Prepare Hard Drive".
- Option 1: Auto-Prepare (Erases an ENTIRE hard drive and sets up partitions)
Auto-Prepare divides the disk into the following configuration:
- ext2 /boot partition, default size 32MB. You will be prompted to modify the size to your requirement.
- swap partition, default size 256MB. You will be prompted to modify the size to your requirement.
- A Separate / and /home partition, (sizes can also be specified). Available filesystems include ext2, ext3, ext4, reiserfs, xfs and jfs, but note that both / and /home shall share the same fs type if choosing the Auto Prepare option.
Be warned that Auto-prepare will completely erase the chosen hard drive. Read the warning presented by the installer very carefully, and make sure the correct device is about to be partitioned.
- Option 2: Manually Partition Hard Drives (with cfdisk)- recommended.
This option will allow for the most robust and customized partitioning solution for your personal needs.
- Option 3: Manually Configure block devices, filesystems and mountpoints
If this is selected, the system will list what filesystems and mountpoints it has found and ask you if you wish to use these. If selecting "Yes", you will be given a choice to select the desired method of identification, ie. by dev, label or uuid.
- Option 4: Rollback last filesystem changes
At this point, more advanced GNU/Linux users who are familiar and comfortable with manually partitioning may wish to skip down to Select Packages below.
Partition Hard Drives
Partitioning a hard disk drive defines specific areas (the partitions) within the disk, that will each appear and behave as a separate disk and upon which a filesystem may be created (formatted).
- There are 3 types of disk partitions:
Primary partitions can be bootable, and are limited to 4 partitions per disk or raid volume. If a partitioning scheme requires more than 4 partitions, an extended partition which will contain logical partitions will be required.
Extended partitions are not usable by themselves; they are merely a "container" for logical partitions. If required, a hard disk shall contain only one extended partition; which shall then be sub-divided into logical partitions.
When partitioning a disk, one can observe this numbering scheme by creating primary partitions sda1 through sda3 followed by creating an extended partition, sda4, and subsequently creating logical partition(s) within the extended partition; sda5, sda6, and so on.
A swap partition is a place on the drive where virtual ram resides, allowing the kernel to easily use disk storage for data that does not fit into physical RAM.
Historically, the general rule for swap partition size was 2x the amount of physical RAM. Over time, as computers have gained ever larger memory capacities, this rule has become increasingly deprecated. Generally, on machines with up to 512MB RAM, the 2x rule is usually quite sufficient. If the installation machine provides gratuitous amounts of RAM (more than 1024 MB) it may be possible to completely forget a swap partition altogether, since the option to create a swap file is always available later. A 1 GB swap partition will be used in this example.
A disk partitioning scheme is a very personalized preference. Each user's choices will be unique to their own computing habits and requirements. If you would like to dual boot Arch Linux and a Windows operating system please see Windows and Arch Dual Boot.
Filesystem candidates for separate partitions include:
/ (root) The root filesystem is the primary filesystem from which all other filesystems stem; the top of the hierarchy. All files and directories appear under the root directory "/", even if they are stored on different physical devices. The contents of the root filesystem must be adequate to boot, restore, recover, and/or repair the system. Therefore, certain directories under / are not themselves candidates for separate partitions. (See warning below).
/boot This directory contains the kernel and ramdisk images as well as the bootloader configuration file, and bootloader stages. /boot also stores data that is used before the kernel begins executing userspace programs. This may include saved master boot sectors and sector map files. /boot is essential for booting, but is unique in that it may still be kept on its own separate partition (if required).
/home Provides subdirectories, each named for a system user, for miscellaneous personal data storage as well as user-specific configuration files for applications.
/usr While root is the primary filesystem, /usr is the secondary hierarchy for all system users' data, including the majority of multi-user utilities and applications. /usr is shareable, read-only data. This means that /usr shall be shareable between various hosts and must not be written to, except in the case of system update/upgrade. Any information that is host-specific or varies with time is stored elsewhere.
/tmp directory for programs that require temporary files such as '.lck' files, which can be used to prevent multiple instances of their respective program until a task is completed, at which point the '.lck' file will be removed. Programs must not assume that any files or directories in /tmp are preserved between invocations of the program and files and directories located under /tmp will typically be deleted whenever the system is booted.
/var contains variable data; spool directories and files, administrative and logging data, pacman's cache, the ABS tree, etc. /var exists in order to make it possible to mount /usr as read-only. Everything that historically went into /usr that is written to during system operation (as opposed to installation and software maintenance) must reside under /var.
There are several advantages for using discrete filesystems, rather than combining all into one partition:
- Security: Each filesystem may be configured in /etc/fstab as 'nosuid', 'nodev', 'noexec', 'readonly', etc.
- Stability: A user, or malfunctioning program can completely fill a filesystem with garbage if they have write permissions for it. Critical programs, which reside on a different filesystem remain unaffected.
- Speed: A filesystem which gets written to frequently may become somewhat fragmented. (An effective method of avoiding fragmentation is to ensure that each filesystem is never in danger of filling up completely.) Separate filesystems remain unaffected, and each can be defragmented separately as well.
- Integrity: If one filesystem becomes corrupted, separate filesystems remain unaffected.
- Versatility: Sharing data across several systems becomes more expedient when independent filesystems are used. Separate filesystem types may also be chosen based upon the nature of data and usage.
In this example, we shall use separate partitions for /, /var, /home, and a swap partition.
How big should my partitions be?
This question is best answered based upon individual needs. You may wish to simply create one partition for root and one partition for swap or only one root partition without swap or refer to the following examples and consider these guidelines to provide a frame of reference:
- The root filesystem (/) in the example will contain the /usr directory, which can become moderately large, depending upon how much software is installed. 15-20 GB should be sufficient for most users.
- The /var filesystem will contain, among other data, the ABS tree and the pacman cache. Keeping cached packages is useful and versatile; it provides the ability to downgrade packages if needed. /var tends to grow in size; the pacman cache can grow large over long periods of time, but can be safely cleared if needed. If you are using an SSD, you may wish to locate your /var on an HDD and keep the / and /home partitions on your SSD to avoid needless read/writes to the SSD. 8-12 Gigs on a desktop system should be sufficient for /var, depending largely upon how much software you intend to install. Servers tend to have relatively larger /var filesystems.
- The /home filesystem is typically where user data, downloads, and multimedia reside. On a desktop system, /home is typically the largest filesystem on the drive by a large margin. Remember that if you chose to reinstall Arch, all the data on your /home partition will be untouched (so long as you have a separate /home partition).
- An extra 25% of space added to each filesystem will provide a cushion for unforeseen occurrence, expansion, and serve as a preventive against fragmentation.
From the guidelines above, the example system shall contain a ~15GB root (/) partition, ~10GB /var, 1GB swap, and a /home containing the remaining disk space.
Create Partitions with cfdisk
Start by creating the primary partition that will contain the root, (/) filesystem.
Choose New -> Primary and enter the desired size for root (/). Put the partition at the beginning of the disk.
Also choose the Type by designating it as '83 Linux'. The created / partition shall appear as sda1 in our example.
Now create a primary partition for /var, designating it as Type 83 Linux. The created /var partition shall appear as sda2
Next, create a partition for swap. Select an appropriate size and specify the Type as 82 (Linux swap / Solaris). The created swap partition shall appear as sda3.
Lastly, create a partition for your /home directory. Choose another primary partition and set the desired size.
Likewise, select the Type as 83 Linux. The created /home partition shall appear as sda4.
Name Flags Part Type FS Type [Label] Size (MB) ------------------------------------------------------------------------- sda1 Primary Linux 15440 #root sda2 Primary Linux 10256 #/var sda3 Primary Linux swap / Solaris 1024 #swap sda4 Primary Linux 140480 #/home
Choose Write and type 'yes'. Beware that this operation may destroy data on your disk. Choose Quit to leave the partitioner. Choose Done to leave this menu and continue with "Set Filesystem Mountpoints".
Set Filesystem Mountpoints
Specify each partition and corresponding mountpoint to your requirements. (Recall that partitions end in a number. Therefore, sda is not itself a partition, but rather, signifies an entire drive)
Again, a filesystem type is a very subjective matter which comes down to personal preference. Each has its own advantages, disadvantages, and unique idiosyncrasies. Here is a very brief overview of supported filesystems:
1. ext2 Second Extended Filesystem- Old, reliable GNU/Linux filesystem. Very stable, but without journaling support. May be inconvenient for root (/) and /home, due to very long fsck's. An ext2 filesystem can easily be converted to ext3.
2. ext3 Third Extended Filesystem- Essentially the ext2 system, but with journaling support. ext3 is backward compatible with ext2. Extremely stable, mature, and by far the most widely used, supported and developed GNU/Linux FS.
3. ext4 Fourth Extended Filesystem- Backward compatible with ext2 and ext3. Introduces support for volumes with sizes up to 1 exabyte and files with sizes up to 16 terabytes. Increases the 32,000 subdirectory limit in ext3 to 64,000. Offers online defragmentation ability.
4. ReiserFS (V3)- Hans Reiser's high-performance journaling FS uses a very interesting method of data throughput based on an unconventional and creative algorithm. ReiserFS is touted as very fast, especially when dealing with many small files. ReiserFS is fast at formatting, yet comparatively slow at mounting. Quite mature and stable. ReiserFS (V3) is not actively developed at this time. Generally regarded as a good choice for /var/.
5. JFS - IBM's Journaled FileSystem- The first filesystem to offer journaling. JFS had many years of use in the IBM AIX® OS before being ported to GNU/Linux. JFS currently uses the least CPU resources of any GNU/Linux filesystem. Very fast at formatting, mounting and fsck's, and very good all-around performance, especially in conjunction with the deadline I/O scheduler. (See JFS.) Not as widely supported as ext or ReiserFS, but very mature and stable.
6. XFS - Another early journaling filesystem originally developed by Silicon Graphics for the IRIX OS and ported to GNU/Linux. XFS offers very fast throughput on large files and large filesystems. Very fast at formatting and mounting. Generally benchmarked as slower with many small files, in comparison to other filesystems. XFS is very mature and offers online defragmentation ability.
7. Btrfs - Also known as "Better FS" is a new filesystem with substantial new and powerful features similar to Sun/Oracle's excellent ZFS. These include snapshots, multi-disk striping and mirroring (basically software raid without mdadm), checksums, incremental backup, and on-the-fly compression (which can give a significant performance boost as well as save space), and more. It is still considered "unstable" as of January 2011, but has been merged into the mainline kernel under experimental status. Btrfs looks to be the future of linux filesystems, and is now offered as a root filesystem choice in Ubuntu 10.10, OpenSUSE 11.3 and other major distribution installers.
- JFS and XFS filesystems cannot be shrunk by disk utilities (such as gparted or parted magic)
A note on Journaling
All above filesystems, except ext2, utilize journaling. Journaling file systems are fault-resilient file systems that use a journal to log changes before they are committed to the file system to avoid metadata corruption in the event of a crash. Note that not all journaling techniques are alike; specifically, only ext3 and ext4 offer data-mode journaling, (though, not by default), which journals both data and meta-data (but with a significant speed penalty). The others only offer ordered-mode journaling, which journals meta-data only. While all will return your filesystem to a valid state after recovering from a crash, data-mode journaling offers the greatest protection against file system corruption and data loss but can suffer from performance degradation, as all data is written twice (first to the journal, then to the disk). Depending upon how important your data is, this may be a consideration in choosing your filesystem type.
Choose and create the filesystem (format the partition) for / by selecting yes. You will now be prompted to add any additional partitions. In our example, sda2 and sda4 remain. For sda2, choose a filesystem type and mount it as /var. Finally, choose the filesystem type for sda4, and mount it as /home. Template:Box Note Return to the main menu.
All packages during installation are from the [core] repository. They are further divided into Base, and Base-devel. Package information and brief descriptions are available here.
First, select the package category:
- Packages from the [core] repo to provide the minimal base environment. Always select this and only remove packages that will not be used.
- Extra tools from [core] such as
automake. Most beginners should choose to install it, as many will probably need it later.
After category selection, you will be presented with the full lists of packages, allowing you to fine-tune your selections. Use the space bar to select and unselect.
After selecting the needed packages, leave the selection screen and continue to the next step, Install Packages.
Install Packages will install the selected packages to your new system. If you selected a CD/USB as the source, package versions from the CD/USB will be installed. If you opted for a Netinstall, fresh packages will be downloaded from the internet and installed.
After the packages have been downloaded, the installer will check their integrity. Next it will create the kernel from the packages downloaded.
Configure the System
At this stage of the installation, you will configure the primary configuration files of your Arch Linux base system. Previous versions of the installer included hwdetect to gather information for your configuration. This has been deprecated and replaced with udev, which should handle most module loading automatically at boot.
Now you will be asked which text editor you want to use; choose nano, joe or [[Vim|vi]. nano is generally considered the easiest of the three. Please see the releated wiki pages of the editor you wish to use for instructions on how to use them. You will be presented with a menu including the main configuration files for your system.
Can the installer handle this more automatically?
Hiding the process of system configuration is in direct opposition to The Arch Way. While it is true that recent versions of the kernel and hardware probing tools offer excellent hardware support and auto-configuration, Arch presents the user all pertinent configuration files during installation for the purposes of transparency and system resource control. By the time you have finished modifying these files to your specifications, you will have learned the simple method of manual Arch Linux system configuration and become more familiar with the base structure, leaving you better prepared to use and maintain your new installation productively.
Arch Linux uses the file Template:Filename as the principal location for system configuration. This one file contains a wide range of configuration information, principally used at system startup. As its name directly implies, it also contains settings for and invokes the /etc/rc* files, and is, of course, sourced by these files.
LOCALE="en_US.utf8" HARDWARECLOCK="localtime" USEDIRECTISA="no" TIMEZONE="US/Eastern" KEYMAP="us" CONSOLEFONT= CONSOLEMAP= USECOLOR="yes"
- This sets your system locale, which will be used by all i18n-aware applications and utilities. You can get a list of the available locales by running Template:Codeline from the command line. This setting's default is usually fine for US English users. However if you experience any problems such as some characters not printing right and being replaced by squares you may want to go back and replace "en_US.utf8" with just "en_US".
- Specifies whether the hardware clock, which is synchronized on boot and on shutdown, stores UTC time, or localtime. UTC makes sense because it greatly simplifies changing timezones and daylight savings time. localtime is necessary if you dual boot with an operating system such as Windows, that only stores localtime to the hardware clock.
- Use direct I/O request instead of Template:Filename for hwclock
- Specify your TIMEZONE. (All available zones are under Template:Filename).
- The available keymaps are in Template:Filename. Please note that this setting is only valid for your TTYs, not any graphical window managers or X.
- Available console fonts reside under Template:Filename if you must change. The default (blank) is safe.
- Defines the console map to load with the setfont program at boot. Possible maps are found in Template:Filename, if needed. The default (blank) is safe.
- Select "yes" if you have a color monitor and wish to have colors in your consoles.
# Scan hardware and load required modules at boot MOD_AUTOLOAD="yes" # Module Blacklist - Deprecated MOD_BLACKLIST=() # MODULES=(!net-pf-10 !pcspkr loop)
- Setting this to "yes" will use udev to automatically probe hardware and load the appropriate modules during boot, (convenient with the default modular kernel). Setting this to "no" will rely on the user's ability to specify this information manually, or compile their own custom kernel and modules, etc.
- This has become deprecated in favor of adding blacklisted modules directly to the MODULES= line below.
- Specify additional MODULES if you know that an important module is missing. If your system has any floppy drives, add "floppy". If you will be using loopback filesystems, add "loop". Also specify any blacklisted modules by prefixing them with a bang (!). Udev will be forced NOT to load blacklisted modules. In the example, the IPv6 module as well as the annoying pcspeaker are blacklisted.
- Set your HOSTNAME to your liking. This is the name of your computer. Whatever you put here, also put it in Template:Filename
- 'Ethernet, card 0'. If you are using static IP, adjust the interface IP address, netmask and broadcast address. Set eth0="dhcp" if you want to use DHCP for dynamic/automatic configuration.
- Specify all interfaces here. Multiple interfaces should be separated with a space as in: (eth0 wlan0)
- If you are using static IP, set the gateway address. If using DHCP, you can usually ignore this variable, though some users have reported the need to define it.
- If you are using static IP, remove the ! in front of 'gateway'. If using DHCP, you can usually leave this variable commented out with the bang (!), but again, some users require the gateway and ROUTES defined. If you experience networking issues with pacman, for instance, you may want to return to these variables.
Example w/ Dynamic IP (DHCP):
HOSTNAME="arch" #eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255" eth0="dhcp" INTERFACES=(eth0) gateway="default gw 192.168.0.1" ROUTES=(!gateway)
Example w/ Static IP:
HOSTNAME="arch" eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255" INTERFACES=(eth0) gateway="default gw 192.168.0.1" ROUTES=(gateway)
This array simply lists the names of those scripts contained in /etc/rc.d/ which are to be started during the boot process, and the order in which they start. Asynchronous initialization by backgrounding is also supported and useful for speeding up boot.
DAEMONS=(network @syslog-ng netfs @crond)
- If a script name is prefixed with a bang (!), it is not executed.
- If a script is prefixed with an "at" symbol (@), it shall be executed in the background; the startup sequence will not wait for successful completion of each daemon before continuing to the next. (Useful for speeding up system boot). Do not background daemons that are needed by other daemons. For example "mpd" depends on "network", therefore backgrounding network may cause mpd to break.
- Edit this array whenever new system services are installed, if starting them automatically during boot is desired.
The 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.
A daemon is a program that runs in the background, waiting for events to occur and offering services. A good example is a web server that waits for a request to deliver a page (e.g.:httpd) or an SSH server waiting for a user login (e.g.:sshd). While these are full-featured applications, there are also daemons whose work is not that visible. Examples are a daemon which writes messages into a log file (e.g. syslog, metalog), and a daemon which provides a graphical login (e.g.: gdm, kdm). All these programs can be added to the daemons line and will be started when the system boots. Useful daemons will be presented during this guide.
Historically, the term daemon was coined by the programmers of MIT's Project MAC. They took the name from Maxwell's demon, an imaginary being from a famous thought experiment that constantly works in the background, sorting molecules. *nix systems inherited this terminology and created the backronym disk and execution monitor.
The fstab (for file systems table) is part of the system configuration listing all available disks and disk partitions, and indicating how they are to be initialized or otherwise integrated into the overall system's filesystem. The /etc/fstab file is most commonly used by the mount command. The mount command takes a filesystem on a device, and adds it to the main system hierarchy that you see when you use your system. mount -a is called from /etc/rc.sysinit, about 3/4 of the way through the boot process, and reads /etc/fstab to determine which options should be used when mounting the specified devices therein. If noauto is appended to a filesystem in /etc/fstab, mount -a will not mount it at boot.
An example of Template:Filename
# <file system> <dir> <type> <options> <dump> <pass> none /dev/pts devpts defaults 0 0 none /dev/shm tmpfs defaults 0 0 /dev/sda1 / jfs defaults,noatime 0 1 /dev/sda2 /var reiserfs defaults,noatime,notail 0 2 /dev/sda3 swap swap defaults 0 0 /dev/sda4 /home jfs defaults,noatime 0 2
- <file system>
- describes the block device or remote filesystem to be mounted. For regular mounts, this field will contain a link to a block device node (as created by mknod which is called by udev at boot) for the device to be mounted; for instance, '/dev/cdrom' or '/dev/sda1'. Note: If your system has more than one hard drive, the installer will default to using UUID rather than the sdx naming scheme, for consistent device mapping. Utilizing UUID has several advantages and may also be preferred to avoid issues if hard disks are added to the system in the future. Due to active developments in the kernel and also udev, the ordering in which drivers for storage controllers are loaded may change randomly, yielding an unbootable system/kernel panic. Nearly every motherboard has several controllers (onboard SATA, onboard IDE), and due to the aforementioned development updates, /dev/sda may become /dev/sdb on the next reboot. (See this wiki article for more information on persistent block device naming. )
- describes the mount point for the filesystem. For swap partitions, this field should be specified as 'swap'; (Swap partitions are not actually mounted.)
- describes the type of the filesystem. The Linux kernel supports many filesystem types. (For the filesystems currently supported by the running kernel, see /proc/filesystems). An entry 'swap' denotes a file or partition to be used for swapping. An entry 'ignore' causes the line to be ignored. This is useful to show disk partitions which are currently unused.
- describes the mount options associated with the filesystem. It is formatted as a comma-separated list of options with no intervening spaces. It contains at least the type of mount plus any additional options appropriate to the filesystem type. For documentation on the available options for non-nfs file systems, see mount(8).
- used by the dump(8) command to determine which filesystems are to be dumped. dump is a backup utility. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be backed up. Note that dump is not installed by default.
- used by the fsck(8) program to determine the order in which filesystem checks are done at boot time. The root filesystem should be specified with a <pass> of 1, and other filesystems should have a <pass> of 2 or 0. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked.
Expanded information available in the Fstab wiki entry.
Most users will not need to modify this file at this time, but please read the following explanatory information.
This file allows further fine-tuning of the initial ram filesystem, or initramfs, (also historically referred to as the initial ramdisk or "initrd") for your system. The initramfs is a gzipped image that is read by the kernel during boot. The purpose of the initramfs is to bootstrap the system to the point where it can access the root filesystem. This means it has to load any modules that are required for devices like IDE, SCSI, or SATA drives (or USB/FW, if you are booting from a USB/FW drive). Once the initrramfs loads the proper modules, either manually or through udev, it passes control to the kernel and your boot continues. For this reason, the initramfs only needs to contain the modules necessary to access the root filesystem. It does not need to contain every module you would ever want to use. The majority of common kernel modules will be loaded later on by udev, during the init process.
mkinitcpio is the next generation of initramfs creation. It has many advantages over the old
- It uses glibc and busybox to provide a small and lightweight base for early userspace.
- It can use udev for hardware autodetection at runtime, thus preventing numerous unnecessary modules from being loaded.
- Its hook-based init script is easily extendable with custom hooks, which can easily be included in pacman packages without having to modifiy mkinitcpio itself.
- It already supports lvm2, dm-crypt for both legacy and luks volumes, raid, swsusp and suspend2 resuming and booting from usb mass storage devices.
- Many features can be configured from the kernel command line without having to rebuild the image.
- The mkinitcpio script makes it possible to include the image in a kernel, thus making a self-contained kernel image is possible.
- Its flexibility makes recompiling a kernel unnecessary in many cases.
If using RAID or LVM on the root filesystem, the appropriate HOOKS must be configured. See the wiki pages for RAID and /etc/mkinitcpio for more info. If using a non-US keyboard. add the "
keymap" hook to load your local keymap during boot. Add the "
usbinput" hook if using a USB keyboard. Don't forget to add the "
usb" hook when installing arch on an external hard drive, Comfact Flash, or SD card, which is connected via usb, e.g.:
HOOKS="base udev autodetect pata scsi sata usb filesystems keymap usbinput"
(Otherwise, if boot fails for some reason you will be asked to enter root's password for system maintenance but will be unable to do so.)
If you need support for booting from USB devices, FireWire devices, PCMCIA devices, NFS shares, software RAID arrays, LVM2 volumes, encrypted volumes, or DSDT support, configure your HOOKS accordingly.
This file can be used to set special configuration options for the kernel modules. It is unnecessary to configure this file in the example.
The resolver is a set of routines in the C library that provide access to the Internet Domain Name System (DNS). One of the main functions of DNS is to translate domain names into IP addresses, to make the Web a friendlier place. The resolver configuration file, or /etc/resolv.conf, contains information that is read by the resolver routines the first time they are invoked by a process.
If you use a static IP, set your DNS servers in /etc/resolv.conf (nameserver <ip-address>). You may have as many as you wish. An example, using OpenDNS:
nameserver 188.8.131.52 nameserver 184.108.40.206
If you are using a router, you will probably want to specify your DNS servers in the router itself, and merely point to it from your Template:Filename, using your router's IP (which is also your gateway from Template:Filename). Example:
If using DHCP, you may also specify your DNS servers in the router, or allow automatic assignment from your ISP, if your ISP is so equipped.
This file associates IP addresses with hostnames and aliases, one line per IP address. For each host a single line should be present with the following information:
<IP-address> <hostname> [aliases...]
Add your hostname, coinciding with the one specified in /etc/rc.conf, as an alias, so that it looks like this:
127.0.0.1 localhost.localdomain localhost yourhostname
127.0.0.1 localhost.localdomain localhost archErrors in this entry may cause poor network performance and/or certain programs to open very slowly, or not work at all. This is a very common error for beginners.
If you use a static IP, add another line using the syntax: <static-IP> <hostname.domainname.org> <hostname> e.g.:
192.168.1.100 yourhostname.domain.org yourhostname
220.127.116.11 www.google.com g 192.168.1.90 media 192.168.1.88 dataThe above example would allow you to access google simply by typing 'g' into your browser, and access to a media and data server on your network by name and without the need for typing out their respective IP addresses.
/etc/hosts.deny and /etc/hosts.allow
Modify these configurations according to your needs if you plan on using the ssh daemon. The default configuration will reject all incoming connections, not only ssh connections. Edit your /etc/hosts.allow file and add the appropriate parameters:
- Let everyone connect to you
- Restrict it to a certain ip
- Restrict it to your local LAN network (range 192.168.0.0 to 192.168.0.255)
- Restrict for an IP range
If you do not plan on using the ssh daemon, leave this file at the default, (empty).
/usr/sbin/locale-gen command reads from /etc/locale.gen to generate specific locales. They can then be used by glibc and any other locale-aware program or library for rendering text, correctly displaying regional monetary values, time and date formats, alphabetic idiosyncrasies, and other locale-specific standards.
By default Template:Filename is an empty file with commented documentation. Once edited, the file remains untouched.
locale-gen runs on every glibc upgrade, generating all the locales specified in Template:Filename.
Choose the locale(s) you need (remove the # in front of the lines you want), e.g.:
en_US ISO-8859-1 en_US.UTF-8
The installer will now run the locale-gen script, which will generate the locales you specified. You may change your locale in the future by editing /etc/locale.gen and subsequently running 'locale-gen' as root.
Choose a mirror repository for
pacman. Remember that archlinux.org is throttled, limiting downloads to 50KB/s.
Finally, set a root password and make sure that you remember it later. Return to the main menu and continue with installing bootloader.
When you select "Done", the system will rebuild the images and put you back to the Main Menu. This may take some time.
Because we have no secondary operating system in our example, we will need a bootloader. GRUB is the recommended bootloader and will be used in the following examples. Alternatively, you may choose LILO or Syslinux. Please see the related wiki and documentation pages if you choose to use a bootloader other than GRUB.
The provided GRUB configuration (Template:Filename) should be sufficient, but verify its contents to ensure accuracy (specifically, ensure that the root (/) partition is specified by UUID on line 3). You may want to alter the resolution of the console by adding a vga=<number> kernel argument corresponding to your desired virtual console resolution. (A table of resolutions and the corresponding numbers is printed in the Template:Filename.)
- A printed menu selection. "Arch Linux (Main)" will be printed on the screen as a menu selection.
- GRUB's root; the drive and partition where the kernel (/boot) resides, according to system BIOS. (More accurately, where GRUB's stage2 file resides). NOT necessarily the root (/) file system, as they can reside on separate partitions. GRUB's numbering scheme starts at 0, and uses an hdx,x format regardless of IDE or SATA, and enclosed within parentheses. The example indicates that /boot is on the first partition of the first drive, according to the BIOS, so (hd0,0).
- This line specifies:
- The path and filename of the kernel relative to GRUB's root. In the example, /boot is merely a directory residing on the same partition as / and vmlinuz26 is the kernel filename; Template:Filename. If /boot were on a separate partition, the path and filename would be simply Template:Filename, being relative to GRUB's root.
- The root= argument to the kernel statement specifies the partition containing the root (/) directory in the booted system, (more accurately, the partition containing Template:Filename). An easy way to distinguish the 2 appearances of 'root' in Template:Filename is to remember that the first root statement informs GRUB where the kernel resides, whereas the second root= kernel argument tells the kernel where the root filesystem (/) resides.
- Kernel options. In our example, ro mounts the filesystem as read-only during startup, (usually a safe default; you may wish to change this in case it causes problems booting). Depending on hardware, rootdelay=8 may need to be added to the kernel options in order to be able to boot from an external usb hard drive.
- The path and filename of the initial RAM filesystem relative to GRUB's root. Again, in the example, /boot is merely a directory residing on the same partition as / and kernel26.img is the initrd filename; /boot/kernel26.img. If /boot were on a separate partition, the path and filename would be simply /kernel26.img, being relative to GRUB's root.
title Arch Linux (Main) root (hd0,0) kernel /boot/vmlinuz26 root=/dev/sda1 ro initrd /boot/kernel26.img
Example for /boot on a separate partition
title Arch Linux (Main) root (hd0,0) kernel /vmlinuz26 root=/dev/sda3 ro initrd /kernel26.img
Install the GRUB bootloader to the master boot record (/dev/sda in our example).
That's it; You have configured and installed your Arch Linux base system. Exit the install, and reboot: