https://wiki.archlinux.org/api.php?action=feedcontributions&user=Panth0r&feedformat=atomArchWiki - User contributions [en]2024-03-28T09:50:56ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Beginners%27_guide&diff=302849Beginners' guide2014-03-02T08:06:28Z<p>Panth0r: /* Configure the network */ systemd v209 disable "predictable" interface names</p>
<hr />
<div><noinclude><br />
[[Category:Getting and installing Arch]]<br />
[[Category:About Arch]]<br />
[[ar:Beginners' Guide/Installation]]<br />
[[da:Beginners' Guide/Installation]]<br />
[[el:Beginners' Guide/Installation]]<br />
[[es:Beginners' Guide/Installation]]<br />
[[hr:Beginners' Guide/Installation]]<br />
[[hu:Beginners' Guide/Installation]]<br />
[[it:Beginners' Guide/Installation]]<br />
[[ja:Beginners' Guide/Installation]]<br />
[[ko:Beginners' Guide/Installation]]<br />
[[nl:Beginners' Guide/Installatie]]<br />
[[pl:Beginners' Guide/Installation]]<br />
[[pt:Beginners' Guide/Installation]]<br />
[[ro:Ghidul începătorilor/Instalare]]<br />
[[ru:Beginners' Guide/Installation]]<br />
[[sr:Beginners' Guide/Installation]]<br />
[[zh-CN:Beginners' Guide/Installation]]<br />
[[zh-TW:Beginners' Guide/Installation]]<br />
{{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.}}<br />
</noinclude><br />
== Installation ==<br />
<br />
You are now presented with a shell prompt, automatically logged in as root.<br />
For editing text files, the console editor nano is suggested. If you are not familiar with it, see [[nano#nano usage]].<br />
<br />
=== Change the language ===<br />
<br />
{{Tip|These are optional for the majority of users. Useful only if you plan on writing in your own language in any of the configuration files, if you use diacritical marks in the Wi-Fi password, or if you would like to receive system messages (e.g. possible errors) in your own language.<br />
Changes here ''only'' affect the installation process.}}<br />
<br />
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:<br />
<br />
# loadkeys ''layout''<br />
<br />
...where ''layout'' can be {{ic|fr}}, {{ic|uk}}, {{ic|dvorak}}, {{ic|be-latin1}}, etc. See [[Wikipedia:ISO 3166-1 alpha-2#Officially assigned code elements|here]] for 2-letter country code list. Use the command {{ic|localectl list-keymaps}} to list all available keymaps.<br />
<br />
The font should also be changed, because most languages use more glyphs than the 26 letter [[Wikipedia:English alphabet|English alphabet]]. Otherwise some foreign characters may show up as white squares or as other symbols. Note that the name is case-sensitive, so please type it ''exactly'' as you see it:<br />
<br />
# setfont Lat2-Terminus16<br />
<br />
By default, the language is set to English (US). If you would like to change the language for the install process ''(German, in this example)'', remove the {{ic|#}} in front of the [[locale]] you want from {{ic|/etc/locale.gen}}, along with English (US). Please choose the {{ic|UTF-8}} entry.<br />
<br />
{{hc|# nano /etc/locale.gen|<br />
en_US.UTF-8 UTF-8<br />
de_DE.UTF-8 UTF-8}}<br />
<br />
# locale-gen<br />
# export LANG=de_DE.UTF-8<br />
<br />
=== Establish an internet connection ===<br />
<br />
{{Warning|As of v197, udev no longer assigns network interface names according to the wlanX and ethX naming scheme. If you are coming from a different distribution or are reinstalling Arch and not aware of the new interface naming style, please do not assume that your wireless interface is named wlan0, or that your wired interface is named eth0. You can use the command {{ic|ip link}} to discover the names of your interfaces.}}<br />
<br />
The {{ic|dhcpcd}} network daemon starts automatically during boot and it will attempt to start a wired connection. Try to ping a server to see if a connection was established. For example, Google's webservers:<br />
<br />
{{hc|# ping -c 3 www.google.com|2=<br />
PING www.l.google.com (74.125.132.105) 56(84) bytes of data.<br />
64 bytes from wb-in-f105.1e100.net (74.125.132.105): icmp_req=1 ttl=50 time=17.0 ms<br />
64 bytes from wb-in-f105.1e100.net (74.125.132.105): icmp_req=2 ttl=50 time=18.2 ms<br />
64 bytes from wb-in-f105.1e100.net (74.125.132.105): icmp_req=3 ttl=50 time=16.6 ms<br />
<br />
--- www.l.google.com ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2003ms<br />
rtt min/avg/max/mdev = 16.660/17.320/18.254/0.678 ms}}<br />
<br />
If you get a {{ic|ping: unknown host}} error, first check if there is an issue with your cable or wireless signal strength. If not, you will need to set up the network manually, as explained below. Once a connection is established move on to [[#Prepare the storage drive|Prepare the storage drive]].<br />
<br />
==== Wired ====<br />
<br />
Follow this procedure if you need to set up a wired connection via a static IP address.<br />
<br />
First, disable the dhcpcd service which was started automatically at boot:<br />
<br />
# systemctl stop dhcpcd.service<br />
<br />
Identify the name of your Ethernet interface.<br />
<br />
{{hc|# ip link|<br />
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT<br />
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br />
2: enp2s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000<br />
link/ether 00:11:25:31:69:20 brd ff:ff:ff:ff:ff:ff<br />
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT qlen 1000<br />
link/ether 01:02:03:04:05:06 brd ff:ff:ff:ff:ff:ff}}<br />
<br />
In this example, the Ethernet interface is {{ic|enp2s0f0}}. If you are unsure, your Ethernet interface is likely to start with the letter "e", and unlikely to be "lo" or start with the letter "w".<br />
<br />
You also need to know these settings:<br />
<br />
* Static IP address.<br />
* Subnet mask.<br />
* Gateway's IP address.<br />
* Name servers' (DNS) IP addresses.<br />
* Domain name (unless you are on a local LAN, in which case you can make it up).<br />
<br />
Activate the connected Ethernet interface (e.g. {{ic|enp2s0f0}}):<br />
<br />
# ip link set enp2s0f0 up<br />
<br />
Add the address:<br />
<br />
# ip addr add ''ip_address''/''mask_bits'' dev ''interface_name''<br />
<br />
For example:<br />
<br />
# ip addr add 192.168.1.2/24 dev enp2s0f0<br />
<br />
For more options, run {{ic|man ip}}.<br />
<br />
Add your gateway like this, substituting your own gateway's IP address:<br />
<br />
# ip route add default via ''ip_address''<br />
<br />
For example:<br />
<br />
# ip route add default via 192.168.1.1<br />
<br />
Edit {{ic|resolv.conf}}, substituting your name servers' IP addresses and your local domain name:<br />
<br />
{{hc|# nano /etc/resolv.conf|<br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com}}<br />
<br />
{{Note|Currently, you may include a maximum of three {{ic|nameserver}} lines. In order to overcome this limitation, you can use a locally caching nameserver like [[Dnsmasq]]. }}<br />
<br />
You should now have a working network connection. If you do not, check the detailed [[Network configuration]] page.<br />
<br />
==== Wireless ====<br />
<br />
Follow this procedure if you need wireless connectivity (Wi-Fi) during the installation process.<br />
<br />
First, identify the name of your wireless interface.<br />
<br />
{{hc|# iw dev|2=<br />
phy#0<br />
Interface wlp3s0<br />
ifindex 3<br />
wdev 0x1<br />
addr 00:11:22:33:44:55<br />
type managed<br />
}}<br />
<br />
In this example, {{ic|wlp3s0}} is the available wireless interface. If you are unsure, your wireless interface is likely to start with the letter "w", and unlikely to be "lo" or start with the letter "e". <br />
<br />
{{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 network configuration]] for more detailed information.}}<br />
<br />
Bring the interface up with:<br />
<br />
# ip link set wlp3s0 up<br />
<br />
To verify that the interface is up, inspect the output of the following command:<br />
<br />
{{hc|# ip link show wlp3s0|<br />
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000<br />
link/ether 00:11:22:33:44:55 brd ff:ff:ff:ff:ff:ff<br />
}}<br />
<br />
The {{ic|UP}} in {{ic|<BROADCAST,MULTICAST,UP,LOWER_UP>}} is what indicates the interface is up, not the later {{ic|state DOWN}}.<br />
<br />
Most wireless chipsets require firmware in addition to a corresponding driver. The kernel tries to identify and load both automatically. If you get output like {{ic|SIOCSIFFLAGS: No such file or directory}}, this means you will need to manually load the firmware. If unsure, invoke {{ic|dmesg}} to query the kernel log for a firmware request from the wireless chipset. For example, if you have an Intel chipset which requires and has requested firmware from the kernel at boot:<br />
<br />
{{hc|# dmesg <nowiki>|</nowiki> grep firmware|<br />
firmware: requesting iwlwifi-5000-1.ucode}}<br />
<br />
If there is no output, it may be concluded that the system's wireless chipset does not require firmware.<br />
<br />
{{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 network configuration]] if you are unsure about the requirement of corresponding firmware installation for your particular chipset.}}<br />
<br />
Next, use [[netctl]]'s {{ic|wifi-menu}} to connect to a network:<br />
<br />
# wifi-menu wlp3s0<br />
<br />
You should now have a working network connection. If you do not, check the detailed [[Wireless network configuration]] page.<br />
<br />
===== Without wifi-menu =====<br />
<br />
Alternatively, use {{ic|iw dev wlp3s0 scan <nowiki>|</nowiki> grep SSID}} to scan for available networks, then connect to a network with:<br />
<br />
# wpa_supplicant -B -i wlp3s0 -c <(wpa_passphrase "''ssid''" "''psk''")<br />
<br />
You need to replace ''ssid'' with the name of your network (e.g. "Linksys etc...") and ''psk'' with your wireless password, '''leaving the quotes around the network name and password.'''<br />
<br />
Finally, you have to give your interface an IP address. This can be set manually or using the dhcp:<br />
<br />
# dhcpcd wlp3s0<br />
<br />
If that does not work, issue the following commands:<br />
<br />
# echo 'ctrl_interface=DIR=/run/wpa_supplicant' > /etc/wpa_supplicant.conf<br />
# wpa_passphrase <ssid> <passphrase> >> /etc/wpa_supplicant.conf<br />
# ip link set <interface> up # May not be needed, but does no harm in any case<br />
# wpa_supplicant -B -D nl80211 -c /foobar.conf -i <interface name><br />
# dhcpcd -A <interface name><br />
<br />
==== Analog modem, ISDN, or PPPoE DSL ====<br />
<br />
For xDSL, dial-up, and ISDN connections, see [[Direct Modem Connection]].<br />
<br />
==== Behind a proxy server ====<br />
<br />
If you are behind a proxy server, you will need to export the {{ic|http_proxy}} and {{ic|ftp_proxy}} environment variables. See [[Proxy settings]] for more information.<br />
<br />
=== Prepare the storage drive ===<br />
<br />
{{Warning|Partitioning can destroy data. You are '''strongly''' cautioned and advised to backup any critical data before proceeding.}}<br />
<br />
==== Choose a partition table type ====<br />
<br />
You have to choose between [[GUID Partition Table]] (GPT) and [[Master Boot Record]] (MBR). GPT is more modern and recommended for new installations.<br />
<br />
* If you want to setup a system which dual boots with windows, this must be taken into account as explained in [[Partitioning#Choosing between GPT and MBR]].<br />
* It is recommended to always use GPT for UEFI boot, as some UEFI firmwares do not allow UEFI-MBR boot.<br />
* Some BIOS systems may have issues with GPT. See http://mjg59.dreamwidth.org/8035.html and http://rodsbooks.com/gdisk/bios.html for more info and possible workarounds.<br />
<br />
{{Note|If you are installing to a USB flash key, see [[Installing Arch Linux on a USB key]].}}<br />
<br />
==== Partitioning tool ====<br />
<br />
Absolute beginners are encouraged to use a graphical partitioning tool. [http://gparted.sourceforge.net/download.php GParted] is a good example, and is [http://gparted.sourceforge.net/livecd.php provided as a "live" CD]. It is also included on live CDs of most Linux distributions such as [[Wikipedia:Ubuntu (operating system)|Ubuntu]] and [[Wikipedia:Linux Mint|Linux Mint]]. A drive should first be [[partitioning|partitioned]] and afterwards the partitions should be formatted with a [[File Systems|file system]].<br />
<br />
{{Tip|When using Gparted, selecting the option to create a new partition table gives an "msdos" partition table by default. If you are intending to follow the advice to create a GPT partition table then you need to choose "Advanced" and then select "gpt" from the drop-down menu.}}<br />
<br />
While gparted may be easier to use, if you just want to create a few partitions on a new disk you can get the job done quickly by just using one of the [[Partitioning#Partitioning tools|fdisk variants]] which are included on the install medium. In the next section short usage instructions for both [[Partitioning#Gdisk usage summary|gdisk]] and [[Partitioning#Fdisk usage summary|fdisk]] follow.<br />
<br />
==== Partition scheme ====<br />
<br />
You can decide into how many partitions the disk should be split, and for which directory each partition should be used in the system. The mapping from partitions to directories (frequently called 'mount points') is the [[Partitioning#Partition scheme|Partition scheme]]. The simplest, and not a bad choice, is to make just one huge {{ic|/}} partition. Another popular choice is to have a {{ic|/}} and a {{ic|/home}} partition.<br />
<br />
'''Additional required partitions:'''<br />
* If you have a [[UEFI]] motherboard, you will need to create an extra [[Unified Extensible Firmware Interface#EFI System Partition|EFI System Partition]].<br />
* If you have a BIOS motherboard (or plan on booting in BIOS compatibility mode) and you want to setup GRUB on a GPT-partitioned drive, you will need to create an extra [[GRUB#GUID Partition Table (GPT) specific instructions|BIOS Boot Partition]] of size 1 or 2 MiB and {{ic|EF02}} type code. Syslinux does not need one.<br />
* If you have a requirement for a [[Disk encryption]] of the system itself, this must be reflected in your partition scheme. It is unproblematic to add encrypted folders, containers or home directories after the system is installed.<br />
* If you are planning to use any filesystem for root filesystem different than ext4 (-3,-2) , you should check first if GRUB supports it. If it is not supported you need to create a GRUB compatible partition (such as [[Ext4|ext4]]) and use it for {{ic|/boot}}.<br />
<br />
See [[Swap]] for details if you wish to set up a swap partition or swap file. A swap file is easier to resize than a partition and can be created at any point after installation, but cannot be used with a Btrfs filesystem.<br />
<br />
==== Considerations for dualbooting with Windows ====<br />
<br />
If you have an existing OS installation, please keep in mind that if you were to just write a completely new partition table to disk then all the data which was previously on disk would be lost. <br />
<br />
The recommended way to setup a Linux/Windows dual booting system is to first install Windows, only using part of the disk for its partitions. When you have finished the Windows setup, boot into the Linux install environment where you can create additional partitions for Linux while leaving the existing Windows partitions untouched.<br />
<br />
Some newer computers come pre-installed with Windows 8 which will be using Secure Boot. Arch Linux currently does not support Secure Boot, but some Windows 8 installations have been seen not to boot if Secure Boot is turned off in the BIOS. In some cases it is necessary to turn off both Secure Boot as well as Fastboot in the BIOS options in order to allow Windows 8 to boot without Secure Boot. However there are potential security risks in turning off Secure Boot for booting up Windows 8. Therefore, it may be a better option to keep the Windows 8 install intact and have an independent hard drive for the Linux install - which can then be partitioned from scratch using a GPT partition table. Once that is done, creating several ext4/FAT32/swap partitions on the second drive may be a better way forward if the computer has two drives available. This is often not easy or possible on a small laptop. Currently, Secure Boot is still not in a fully stable state for reliable operation, even for Linux distributions that support it.<br />
<br />
{{Warning|Windows 8 includes a new feature called Fast Startup, which turns shutdown operations into suspend-to-disk operations. The result is that filesystems shared between Windows 8 and any other OS are almost certain to be damaged when booting between the two OSes. Even if you don't intend to share filesystems, the EFI System Partition is likely to be damaged on an EFI system. Therefore, you should disable Fast Startup, as described [http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html here,] before you install Linux on any computer that uses Windows 8.}}<br />
<br />
If you have already created your partitions, proceed to [[#Create filesystems]].<br />
<br />
Otherwise, see the following example.<br />
<br />
==== Example ====<br />
<br />
The Arch Linux install media includes the following partitioning tools: {{ic|fdisk}}, {{ic|gdisk}}, {{ic|cfdisk}}, {{ic|cgdisk}}, {{ic|parted}}.<br />
<br />
{{Tip|Use the {{ic|lsblk}} command to list the hard disks attached to your system, along with the sizes of their existing partitions. This will help you to be confident you are partitioning the right disk.}}<br />
<br />
The example system will contain a 15 GB root partition, and a [[Partitioning#/home|home]] partition for the remaining space. Choose either [[MBR]] or [[GPT]]. Do not choose both!<br />
<br />
It should be emphasized that partitioning is a personal choice and that this example is only for illustrative purposes. See [[Partitioning]].<br />
<br />
===== Using cgdisk to create GPT partitions =====<br />
<br />
# cgdisk&nbsp;/dev/sda<br />
<br />
;Root:<br />
* Choose ''New'' (or press {{ic|N}}) – {{ic|Enter}} for the first sector (2048) – type in {{ic|15G}} – {{ic|Enter}} for the default hex code (8300) – {{ic|Enter}} for a blank partition name.<br />
<br />
;Home:<br />
* Press the down arrow a couple of times to move to the larger free space area.<br />
* Choose ''New'' (or press {{ic|N}}) – {{ic|Enter}} for the first sector – {{ic|Enter}} to use the rest of the drive (or you could type in the desired size; for example {{ic|30G}}) – {{ic|Enter}} for the default hex code (8300) – {{ic|Enter}} for a blank partition name.<br />
<br />
Here is what it should look like:<br />
<br />
Part. # Size Partition Type Partition Name<br />
----------------------------------------------------------------<br />
1007.0 KiB free space<br />
1 15.0 GiB Linux filesystem<br />
2 123.45 GiB Linux filesystem<br />
<br />
Double check and make sure that you are happy with the partition sizes as well as the partition table layout before continuing.<br />
<br />
If you would like to start over, you can simply select ''Quit'' (or press {{ic|Q}}) to exit without saving changes and then restart ''cgdisk''.<br />
<br />
If you are satisfied, choose ''Write'' (or press {{ic|Shift+W}}) to finalize and to write the partition table to the drive. Type {{ic|yes}} and choose ''Quit'' (or press {{ic|Q}}) to exit without making any more changes.<br />
<br />
===== Using fdisk to create MBR partitions =====<br />
{{Note|There is also ''cfdisk'', which is similar in UI to ''cgdisk'', but it currently does not automatically align the first partition properly. That is why the classic ''fdisk'' tool is used here.}}<br />
<br />
Launch ''fdisk'' with:<br />
<br />
# fdisk /dev/sda<br />
<br />
Create the partition table:<br />
<br />
* {{ic|Command (m for help):}} type {{ic|o}} and press {{ic|Enter}}<br />
<br />
Then create the first partition:<br />
<br />
# {{ic|Command (m for help):}} type {{ic|n}} and press {{ic|Enter}}<br />
# Partition type: {{ic|Select (default p):}} press {{ic|Enter}}<br />
# {{ic|Partition number (1-4, default 1):}} press {{ic|Enter}}<br />
# {{ic|First sector (2048-209715199, default 2048):}} press {{ic|Enter}}<br />
# {{ic|Last sector, +sectors or +size{K,M,G} (2048-209715199....., default 209715199):}} type {{ic|+15G}} and press {{ic|Enter}}<br />
<br />
Then create a second partition:<br />
<br />
# {{ic|Command (m for help):}} type {{ic|n}} and press {{ic|Enter}}<br />
# Partition type: {{ic|Select (default p):}} press {{ic|Enter}}<br />
# {{ic|Partition number (1-4, default 2):}} press {{ic|Enter}}<br />
# {{ic|First sector (31459328-209715199, default 31459328):}} press {{ic|Enter}}<br />
# {{ic|Last sector, +sectors or +size{K,M,G} (31459328-209715199....., default 209715199):}} press {{ic|Enter}}<br />
<br />
Now preview the new partition table:<br />
<br />
* {{ic|Command (m for help):}} type {{ic|p}} and press {{ic|Enter}}<br />
<br />
{{bc|<br />
Disk /dev/sda: 107.4 GB, 107374182400 bytes, 209715200 sectors<br />
Units &#61; sectors of 1 * 512 &#61; 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
Disk identifier: 0x5698d902<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 2048 31459327 15728640 83 Linux<br />
/dev/sda2 31459328 209715199 89127936 83 Linux<br />
}}<br />
<br />
Then write the changes to disk:<br />
<br />
* {{ic|Command (m for help):}} type {{ic|w}} and press {{ic|Enter}}<br />
<br />
If everything went well fdisk will now quit with the following message:<br />
{{bc|<br />
The partition table has been altered!<br />
<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks. <br />
}}<br />
<br />
In case this does not work because ''fdisk'' encountered an error, you can use the {{ic|q}} command to exit.<br />
<br />
==== Create filesystems ====<br />
<br />
Simply partitioning is not enough; the partitions also need a [[File Systems|filesystem]]. To format the partitions with an ext4 filesystem:<br />
<br />
{{Warning|Double check and triple check that it is actually {{ic|/dev/sda1}} and {{ic|/dev/sda2}} that you want to format. You can use {{ic|lsblk}} to help with this.}}<br />
<br />
# mkfs.ext4 /dev/sda1<br />
# mkfs.ext4 /dev/sda2<br />
<br />
If you have made a partition dedicated to swap (code 82), do not forget to format and activate it with:<br />
<br />
# mkswap /dev/sda''X''<br />
# swapon /dev/sda''X''<br />
<br />
For UEFI, you should format the EFI System Partition (for example /dev/sd''XY'') with:<br />
<br />
# mkfs.fat -F32 /dev/sd''XY''<br />
<br />
=== Mount the partitions ===<br />
<br />
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.<br />
<br />
To display the current partition layout:<br />
<br />
# lsblk /dev/sda<br />
<br />
{{Note|Do not mount more than one partition to the same directory. And pay attention, because the mounting order is important.}}<br />
<br />
First, mount the root partition on {{ic|/mnt}}. Following the example above (yours may be different), it would be:<br />
<br />
# mount /dev/sda1 /mnt<br />
<br />
Then mount the home partition and any other separate partition ({{ic|/boot}}, {{ic|/var}}, etc), if you have any:<br />
<br />
# mkdir /mnt/home<br />
# mount /dev/sda2 /mnt/home<br />
<br />
In case you have a UEFI motherboard, mount the EFI System Partition at your preferred mountpoint ({{ic|/boot}} used for example):<br />
<br />
# mkdir /mnt/boot<br />
# mount /dev/sd''XY'' /mnt/boot<br />
<br />
=== Select a mirror ===<br />
<br />
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 is worth getting it right.<br />
<br />
{{hc|# nano /etc/pacman.d/mirrorlist|<br />
##<br />
## Arch Linux repository mirrorlist<br />
## Sorted by mirror score from mirror status page<br />
## Generated on 2012-MM-DD<br />
##<br />
<br />
<nowiki>Server = http://mirror.example.xyz/archlinux/$repo/os/$arch</nowiki><br />
...}}<br />
<br />
If you want, you can make it the ''only'' mirror available by deleting all other lines, but it is usually a good idea to have a few more, in case the first one goes offline.<br />
<br />
{{Tip|<br />
* Use the [https://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 it downloads a package, resulting in a brief pause. For other ways to generate a mirror list, see [[Mirrors#Sorting mirrors|Sorting mirrors]] and [[Reflector]].<br />
* [https://archlinux.org/mirrors/status/ Arch Linux MirrorStatus] reports various aspects about the mirrors such as network problems with mirrors, data collection problems, the last time mirrors have been synced, etc.}}<br />
<br />
{{Note|<br />
* Whenever in the future you change your mirrorlist, refresh all package lists with {{ic|pacman -Syy}}, to ensure that the package lists are updated consistently. See [[Mirrors]] for more information.<br />
* If you are using an older installation medium, your mirrorlist might be outdated, which might lead to problems when updating Arch Linux (see {{Bug|22510}}). Therefore it is advised to obtain the latest mirror information as described above.<br />
* Some issues have been reported in the [https://bbs.archlinux.org/ Arch Linux forums] regarding network problems that prevent pacman from updating/synchronizing repositories (see [https://bbs.archlinux.org/viewtopic.php?id&#61;68944] and [https://bbs.archlinux.org/viewtopic.php?id&#61;65728]). When installing Arch Linux natively, these issues have been resolved by replacing the default pacman file downloader with an alternative (see [[Improve pacman performance]] for more details). When installing Arch Linux as a guest OS in [[VirtualBox]], this issue has also been addressed by using "Host interface" instead of "NAT" in the machine properties.}}<br />
<br />
=== Install the base system ===<br />
<br />
The base system is installed using the ''pacstrap'' script. The {{ic|-i}} switch can be omitted if you wish to install every package from the {{Grp|base}} group without prompting. You may also want to include {{Grp|base-devel}}, as you will need these packages should you want to build from the AUR.<br />
<br />
# pacstrap -i /mnt base<br />
<br />
{{Note|<br />
* If pacman fails to verify your packages, stop the process with {{ic|Ctrl+C}} and check the system time with {{ic|cal}}. If the system date is invalid (e.g. it shows the 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, using the command {{ic|ntpd -qg}}, and retry running the pacstrap command. Refer to [[Time]] page for more information on correcting system time.<br />
* If pacman complains that {{ic|error: failed to commit transaction (invalid or corrupted package)}}, run the following command:<br />
# pacman-key --init && pacman-key --populate archlinux<br />
}}<br />
<br />
This will give you a basic Arch system. Other packages can be installed later using [[pacman]].<br />
<br />
=== Generate an fstab ===<br />
<br />
Generate an [[fstab]] file with the following command. UUIDs will be used because they have certain advantages (see [[fstab#Identifying filesystems]]). If you would prefer to use labels instead, replace the {{ic|-U}} option with {{ic|-L}}.<br />
<br />
# genfstab -U -p /mnt >> /mnt/etc/fstab<br />
# nano /mnt/etc/fstab<br />
<br />
{{Warning|The fstab file should always be checked after generating it. If you encounter errors running genfstab or later in the install process, do '''not''' run genfstab again; just edit the fstab file.}}<br />
<br />
A few considerations:<br />
<br />
* The last field determines the order in which partitions are checked at start up: use {{ic|1}} for the (non-{{ic|btrfs}}) root partition, which should be checked first; {{ic|2}} for all other partitions you want checked at start up; and {{ic|0}} means 'do not check' (see [[fstab#Field definitions]]).<br />
* All [[btrfs]] partitions should have {{ic|0}} for this field. Normally, you will also want your ''swap'' partition to have {{ic|0}}.<br />
<br />
=== Chroot and configure the base system ===<br />
<br />
Next, [[chroot]] into your newly installed system:<br />
<br />
# arch-chroot /mnt /bin/bash<br />
<br />
{{Note|Leave out {{ic|/bin/bash}} to chroot into the sh shell.}}<br />
At this stage of the installation, you will configure the primary configuration files of your Arch Linux base system. These can either be created if they do not exist, or edited if you wish to change the defaults.<br />
<br />
Closely following and understanding these steps is of key importance to ensure a properly configured system.<br />
<br />
==== Locale ====<br />
<br />
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.<br />
<br />
There are two files that need editing: {{ic|locale.gen}} and {{ic|locale.conf}}.<br />
<br />
Uncomment as many lines as needed. Remove the {{ic|#}} in front of the line(s) you want to use. Using {{ic|UTF-8}} is highly recommended over {{ic|ISO-8859}}:<br />
{{hc|# nano /etc/locale.gen|<br />
#en_PH.UTF-8 UTF-8<br />
#en_PH ISO-8859-1<br />
#en_SG.UTF-8 UTF-8<br />
#en_SG ISO-8859-1<br />
en_US.UTF-8 UTF-8<br />
#en_US ISO-8859-1<br />
#en_ZA.UTF-8 UTF-8<br />
#en_ZA ISO-8859-1<br />
}}<br />
<br />
{{Note|The {{ic|locale.gen}} file has everything commented out by default.}}<br />
<br />
Generate the locale(s) specified in {{ic|/etc/locale.gen}}:<br />
# locale-gen<br />
<br />
{{Note|This will also run with every update of '''glibc'''.}}<br />
<br />
Create the {{ic|/etc/locale.conf}} file substituting your chosen locale:<br />
<br />
# echo LANG=en_US.UTF-8 > /etc/locale.conf<br />
<br />
{{Note|<br />
* The locale specified in the {{ic|LANG}} variable must be uncommented in {{ic|/etc/locale.gen}}.<br />
* The {{ic|locale.conf}} file does not exist by default. Setting only {{ic|LANG}} should be enough as it will act as the default value for all other variables.<br />
}}<br />
<br />
Export substituting your chosen locale:<br />
<br />
# export LANG=en_US.UTF-8<br />
<br />
{{Tip|To use other locales for other {{ic|LC_*}} variables, run {{ic|locale}} to see the available options and add them to {{ic|locale.conf}}. It is not recommended to set the {{ic|LC_ALL}} variable. See [[Locale#Setting system-wide locale]] for details.}}<br />
<br />
==== Console font and keymap ====<br />
<br />
If you set a keymap at [[#Change the language|the beginning]] of the install process, load it now, as well, because the environment has changed. For example:<br />
<br />
# loadkeys ''de-latin1''<br />
# setfont Lat2-Terminus16<br />
<br />
To make them available after reboot, edit {{ic|vconsole.conf}} (create it if it does not exist):<br />
<br />
{{hc|# nano /etc/vconsole.conf|2=<br />
KEYMAP=de-latin1<br />
FONT=Lat2-Terminus16<br />
}}<br />
<br />
* {{ic|KEYMAP}} – Please note that this setting is only valid for your TTYs, not any graphical window managers or Xorg.<br />
<br />
* {{ic|FONT}} – Available alternate console fonts reside in {{ic|/usr/share/kbd/consolefonts/}}. The default (blank) is safe, but some foreign characters may show up as white squares or as other symbols. It is recommended that you change it to {{ic|Lat2-Terminus16}}, because according to {{ic|/usr/share/kbd/consolefonts/README.Lat2-Terminus16}}, it claims to support "about 110 language sets".<br />
<br />
* Possible option {{ic|FONT_MAP}} – Defines the console map to load at boot. Read {{ic|man setfont}}. Removing it or leaving it blank is safe.<br />
<br />
See [[Fonts#Console fonts]] and {{ic|man vconsole.conf}} for more information.<br />
<br />
==== Time zone ====<br />
<br />
Available time zones and subzones can be found in the {{ic|/usr/share/zoneinfo/<Zone>/<SubZone>}} directories.<br />
<br />
To view the available <Zone>, check the directory {{ic|/usr/share/zoneinfo/}}:<br />
<br />
# ls /usr/share/zoneinfo/<br />
<br />
Similarly, you can check the contents of directories belonging to a <SubZone>:<br />
<br />
# ls /usr/share/zoneinfo/Europe<br />
<br />
Create a symbolic link {{ic|/etc/localtime}} to your zone file {{ic|/usr/share/zoneinfo/<Zone>/<SubZone>}} using this command:<br />
<br />
# ln -s /usr/share/zoneinfo/<Zone>/<SubZone> /etc/localtime<br />
<br />
'''Example:'''<br />
<br />
# ln -s /usr/share/zoneinfo/Europe/Minsk /etc/localtime<br />
<br />
==== Hardware clock ====<br />
<br />
Set the hardware clock mode uniformly between your operating systems. Otherwise, they may overwrite the hardware clock and cause time shifts.<br />
<br />
You can generate {{ic|/etc/adjtime}} automatically by using one of the following commands:<br />
<br />
* '''UTC''' (recommended)<br />
<br />
: {{Note|Using [[Wikipedia:Coordinated Universal Time|UTC]] for the hardware clock does not mean that software will display time in UTC.}}<br />
<br />
: {{bc|# hwclock --systohc --utc}}<br />
<br />
* '''localtime''' (discouraged; used by default in Windows)<br />
<br />
: {{Warning|Using ''localtime'' may lead to several known and unfixable bugs. However, there are no plans to drop support for ''localtime''.}}<br />
<br />
: {{bc|# hwclock --systohc --localtime}}<br />
<br />
{{Tip|If you have (or plan on having) a dual boot setup with Windows:<br />
<br />
* Recommended: Set both Arch Linux and Windows to use UTC. A quick [[Time#UTC in Windows|registry fix]] is needed. Also, be sure to prevent Windows from synchronizing the time on-line, because the hardware clock will default back to ''localtime''.<br />
<br />
* Not recommended: Set Arch Linux to ''localtime'' and disable any time-related services, like [[Network Time Protocol daemon|NTPd]] . This will let Windows take care of hardware clock corrections and you will need to remember to boot into Windows at least two times a year (in Spring and Autumn) when [[Wikipedia:Daylight saving time|DST]] kicks in. So please do not ask on the forums why the clock is one hour behind or ahead if you usually go for days or weeks without booting into Windows.}}<br />
<br />
==== Kernel modules ====<br />
<br />
{{Tip|This is just an example, you do not need to set it. 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.}}<br />
<br />
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.<br />
<br />
{{hc|# nano /etc/modules-load.d/virtio-net.conf|<br />
# Load 'virtio-net.ko' at boot.<br />
<br />
virtio-net}}<br />
<br />
If there are more modules to load per {{ic|*.conf}}, the module names can be separated by newlines. A good example are the [[VirtualBox#Arch Linux guests|VirtualBox Guest Additions]].<br />
<br />
Empty lines and lines starting with {{ic|#}} or {{ic|;}} are ignored.<br />
<br />
==== Hostname ====<br />
<br />
Set the [[Wikipedia:hostname|hostname]] to your liking (e.g. ''arch''):<br />
<br />
# echo ''myhostname'' > /etc/hostname<br />
<br />
{{Note|There is no need to edit {{ic|/etc/hosts}}.}}<br />
<br />
=== Configure the network ===<br />
<br />
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.<br />
<br />
{{Note|<br />
* For more in-depth information on network configration, visit [[Network configuration]] and [[Wireless network configuration]].<br />
* If you would like to use the old interface naming scheme (ie. eth* and wlan*) you can accomplish this by creating an empty file at {{ic|/etc/udev/rules.d/80-net-name-slot.rules}} (starting with systemd v209, this file should be {{ic|/etc/udev/rules.d/80-net-setup-link.rules}}) which will mask the file of the same name located under {{ic|/usr/lib/udev/rules.d}}.<br />
}}<br />
<br />
==== Wired ====<br />
<br />
===== Dynamic IP =====<br />
<br />
; Using dhcpcd<br />
<br />
If you only use a single fixed wired network connection, you do not need a network management service and can simply enable the {{ic|dhcpcd}} service:<br />
<br />
# systemctl enable dhcpcd.service<br />
<br />
{{Note|If it does not work, use: {{ic|# systemctl enable dhcpcd@''interface_name''.service}} }}<br />
<br />
; Using netctl<br />
<br />
Copy a sample profile from {{ic|/etc/netctl/examples}} to {{ic|/etc/netctl}}:<br />
<br />
# cd /etc/netctl<br />
# cp examples/ethernet-dhcp my_network<br />
<br />
Edit the profile as needed (update {{ic|Interface}} from {{ic|eth0}} to match network adapter ID as shown by running {{ic|ip link}}):<br />
<br />
# nano my_network<br />
<br />
Enable the {{ic|my_network}} profile:<br />
<br />
# netctl enable my_network<br />
<br />
{{Note|You will get the message "Running in chroot, ignoring request.". This can be ignored for now.}}<br />
<br />
; Using netctl-ifplugd<br />
<br />
{{Warning|You cannot use this method in conjunction with explicitly enabling profiles, such as {{ic|netctl enable <profile>}}.}}<br />
<br />
Alternatively, you can use {{ic|netctl-ifplugd}}, which gracefully handles dynamic connections to new networks:<br />
<br />
Install {{Pkg|ifplugd}}, which is required for {{ic|netctl-ifplugd}}:<br />
<br />
# pacman -S ifplugd<br />
<br />
Then enable for interface that you want:<br />
<br />
# systemctl enable netctl-ifplugd@<interface>.service<br />
<br />
{{Tip|[[Netctl]] also provides {{ic|netctl-auto}}, which can be used to handle wired profiles in conjunction with {{ic|netctl-ifplugd}}.}}<br />
<br />
===== Static IP =====<br />
<br />
; Manual connection at boot using netctl<br />
<br />
Copy a sample profile from {{ic|/etc/netctl/examples}} to {{ic|/etc/netctl}}:<br />
<br />
# cd /etc/netctl<br />
# cp examples/ethernet-static my_network<br />
<br />
Edit the profile as needed (modify {{ic|Interface}}, {{ic|Address}}, {{ic|Gateway}} and {{ic|DNS}}):<br />
<br />
# nano my_network<br />
<br />
* Notice the {{ic|/24}} in {{ic|Address}} which is the [[wikipedia:Classless Inter-Domain Routing#CIDR notation|CIDR notation]] of a {{ic|255.255.255.0}} netmask<br />
<br />
Enable above created profile to start it at every boot:<br />
<br />
# netctl enable my_network<br />
<br />
; Manual connection at boot using systemd<br />
<br />
See [[Network configuration#Manual connection at boot using systemd]].<br />
<br />
==== Wireless ====<br />
<br />
{{Note|If your wireless adapter requires a firmware (as described in the above [[#Wireless|Establish an internet connection]] section and also [[Wireless network configuration#Device driver|here]]), install the package containing your firmware. Most of the time, the {{Pkg|linux-firmware}} package will contain the needed firmware. Though for some devices, the required firmware might be in its own package. For example:<br />
{{bc|# pacman -S zd1211-firmware}}<br />
See [[Wireless network configuration#Installing driver/firmware]] for more info.}}<br />
<br />
Install {{Pkg|iw}} and {{Pkg|wpa_supplicant}} which you will need to connect to a network:<br />
<br />
# pacman -S iw wpa_supplicant<br />
<br />
===== Adding wireless networks =====<br />
<br />
; Using wifi-menu<br />
<br />
Install {{Pkg|dialog}}, which is required for {{ic|wifi-menu}}:<br />
<br />
# pacman -S dialog<br />
<br />
After finishing the rest of this installation and rebooting, you can connect to the network with {{ic|wifi-menu ''interface_name''}} (where {{ic|''interface_name''}} is the interface of your wireless chipset).<br />
<br />
# wifi-menu ''interface_name''<br />
<br />
{{Warning|This must be done *after* your reboot when you are no longer chrooted. The process spawned by this command will conflict with the one you have running outside of the chroot. Alternatively, you could just configure a network profile manually using the following templates so that you do not have to worry about using {{ic|wifi-menu}} at all.}}<br />
<br />
; Using manual netctl profiles<br />
<br />
Copy a network profile from {{ic|/etc/netctl/examples}} to {{ic|/etc/netctl}}:<br />
<br />
# cd /etc/netctl<br />
# cp examples/wireless-wpa my-network<br />
<br />
Edit the profile as needed (modify {{ic|Interface}}, {{ic|ESSID}} and {{ic|Key}}):<br />
<br />
# nano my-network<br />
<br />
Enable above created profile to start it at every boot:<br />
<br />
# netctl enable my-network<br />
<br />
===== Connect automatically to known networks =====<br />
<br />
{{Warning|You cannot use this method in conjunction with explicitly enabling profiles, such as {{ic|netctl enable <profile>}}.}}<br />
<br />
Install {{Pkg|wpa_actiond}}, which is required for {{ic|netctl-auto}}:<br />
<br />
# pacman -S wpa_actiond<br />
<br />
Enable the {{ic|netctl-auto}} service, which will connect to known networks and gracefully handle roaming and disconnects:<br />
<br />
# systemctl enable netctl-auto@''interface_name''.service<br />
<br />
{{Tip|[[Netctl]] also provides {{ic|netctl-ifplugd}}, which can be used to handle wired profiles in conjunction with {{ic|netctl-auto}}.}}<br />
<br />
==== Analog modem, ISDN or PPPoE DSL ====<br />
<br />
For xDSL, dial-up and ISDN connections, see [[Direct Modem Connection]].<br />
<br />
=== Create an initial ramdisk environment ===<br />
<br />
{{Tip|Most users can skip this step and use the defaults provided in {{ic|mkinitcpio.conf}}. The initramfs image (from the {{ic|/boot}} folder) has already been generated based on this file when the {{Pkg|linux}} package (the Linux kernel) was installed earlier with {{ic|pacstrap}}.}}<br />
<br />
Here you need to set the right [[Mkinitcpio#HOOKS|hooks]] if the root is on a USB drive, if you use RAID, LVM, or if {{ic|/usr}} is on a separate partition.<br />
<br />
Edit {{ic|/etc/mkinitcpio.conf}} as needed and re-generate the initramfs image with:<br />
<br />
# mkinitcpio -p linux<br />
<br />
{{Note|Arch VPS installations on QEMU (e.g. when using {{ic|virt-manager}}) may need {{ic|virtio}} modules in {{ic|mkinitcpio.conf}} to be able to boot.<br />
<br />
{{hc|# nano /etc/mkinitcpio.conf|2=<br />
MODULES="virtio virtio_blk virtio_pci virtio_net"<br />
}}<br />
}}<br />
<br />
=== Set the root password ===<br />
<br />
Set the root password with:<br />
<br />
# passwd<br />
<br />
=== Install and configure a bootloader ===<br />
<br />
==== For BIOS motherboards ====<br />
<br />
For BIOS systems, several boot loaders are available, see [[Boot Loaders]] for a complete list. Choose one as per your convenience. Here, two of the possibilities are given as examples:<br />
<br />
* Syslinux is (currently) limited to loading only files from the partition where it was installed. Its configuration file is considered to be easier to understand. An example configuration can be found [https://bbs.archlinux.org/viewtopic.php?pid=1109328#p1109328 here].<br />
<br />
* GRUB is more feature-rich and supports more complex scenarios. Its configuration file(s) is more similar to 'sh' scripting language, which may be difficult for beginners to manually write. It is recommended that they automatically generate one.<br />
<br />
===== Syslinux =====<br />
<br />
If you opted for a GUID partition table (GPT) for your hard drive earlier, you need to install the {{Pkg|gptfdisk}} package now for the installation of syslinux to work.<br />
<br />
# pacman -S gptfdisk<br />
<br />
Install the {{Pkg|syslinux}} package and then use the {{ic|syslinux-install_update}} script to automatically ''install'' the bootloader ({{ic|-i}}), mark the partition ''active'' by setting the boot flag ({{ic|-a}}), and install the ''MBR'' boot code ({{ic|-m}}):<br />
<br />
# pacman -S syslinux<br />
# syslinux-install_update -i -a -m<br />
<br />
Configure {{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. Change {{ic|/dev/sda3}} to reflect your root partition ''(if you partitioned your drive as in [[#Prepare the storage drive|the example]], your root partition is {{ic|/dev/sda1}})''. Do the same for the fallback entry.<br />
<br />
{{hc|# nano /boot/syslinux/syslinux.cfg|2=<br />
...<br />
LABEL arch<br />
...<br />
APPEND root='''/dev/sda3''' rw<br />
...}}<br />
<br />
For more information on configuring and using Syslinux, see [[Syslinux]].<br />
<br />
===== GRUB =====<br />
<br />
Install the {{Pkg|grub}} package and then run {{ic|grub-install}} to install the bootloader:<br />
<br />
# pacman -S grub<br />
# grub-install --target=i386-pc --recheck '''/dev/sda'''<br />
<br />
{{Note|<br />
* Change {{ic|/dev/sda}} to reflect the drive you installed Arch on. Do not append a partition number (do not use {{ic|sda''X''}}).<br />
* For GPT-partitioned drives on BIOS motherboards, you also need a "BIOS Boot Partition". See [[GRUB#GUID Partition Table (GPT) specific instructions|GPT-specific instructions]] in the GRUB page.<br />
* A sample {{ic|/boot/grub/grub.cfg }} gets installed as part of the grub package, and subsequent {{ic|grub-*}} commands may not over-write it. Ensure that your intended changes are in {{ic|grub.cfg}}, rather than in {{ic|grub.cfg.new}} or some such file.<br />
}}<br />
<br />
While using a manually created {{ic|grub.cfg}} is absolutely fine, it is recommended that beginners automatically generate one:<br />
<br />
{{Tip|To automatically search for other operating systems on your computer, install {{Pkg|os-prober}} ({{ic|pacman -S os-prober}}) before running the next command.}}<br />
<br />
# grub-mkconfig -o /boot/grub/grub.cfg<br />
<br />
{{Note|For new installations of GRUB it is possible that multiple redundant menu entries will be generated. This is because both the upstream default ''10_linux'' script and the Arch specific ''10_archlinux'' script are both creating menu entries when the grub-mkconfig command is run. To correct this behaviour disable the ''10_linux'' script: {{ic|chmod -x /etc/grub.d/10_linux}} and then run the grub-mkconfig command again.}}<br />
<br />
For more information on configuring and using GRUB, see [[GRUB]].<br />
<br />
==== For UEFI motherboards ====<br />
<br />
For UEFI systems, several boot loaders are available, see [[Boot Loaders]] for a complete list. Choose one as per your convenience. Here, two of the possibilities are given as examples:<br />
<br />
* [[gummiboot]] is a minimal UEFI Boot Manager which basically provides a menu for [[EFISTUB]] kernels and other UEFI applications. This is recommended UEFI boot method. <br />
* GRUB is a more complete bootloader, useful if you run into problems with Gummiboot.<br />
* [[rEFInd]] is a UEFI boot manager that can boot Archlinux kernels directly since the stock Archlinux kernel has the EFI stub loader built in, as well as dual boot systems with Windows 8/8.1.<br />
<br />
{{Note|For UEFI boot, the drive needs to be GPT-partitioned and an [[Unified Extensible Firmware Interface#EFI System Partition|EFI System Partition]] (512 MiB or larger, gdisk type {{ic|EF00}}, formatted with FAT32) must be present. In the following examples, this partition is assumed to be mounted at {{ic|/boot}}. If you have followed this guide from the beginning, you have already done all of these.}}<br />
<br />
===== Gummiboot =====<br />
<br />
First install the {{Pkg|gummiboot}} package and then run {{ic|gummiboot install}} to install the bootloader to the EFI System Partition:<br />
<br />
# mount -t efivarfs efivarfs /sys/firmware/efi/efivars # ignore if already mounted<br />
# pacman -S gummiboot<br />
# gummiboot install<br />
<br />
You will need to manually create a configuration file to add an entry for Arch Linux to the gummiboot manager. Create {{ic|/boot/loader/entries/arch.conf}} and add the following contents, replacing {{ic|/dev/sdaX}} with your root partition, usually {{ic|/dev/sda2}}:<br />
<br />
{{hc|# nano /boot/loader/entries/arch.conf|2=<br />
title Arch Linux<br />
linux /vmlinuz-linux<br />
initrd /initramfs-linux.img<br />
options root='''/dev/sdaX''' rw<br />
}}<br />
<br />
For more information on configuring and using gummiboot, see [[gummiboot]].<br />
<br />
===== GRUB =====<br />
<br />
Install the {{Pkg|grub}} and {{Pkg|efibootmgr}} packages and then run {{ic|grub-install}} to install the bootloader:<br />
<br />
# mount -t efivarfs efivarfs /sys/firmware/efi/efivars # ignore if already mounted<br />
# pacman -S grub efibootmgr<br />
# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=arch_grub --recheck<br />
<br />
Next, while using a manually created {{ic|grub.cfg}} is absolutely fine, it is recommended that beginners automatically generate one:<br />
<br />
{{Tip|To automatically search for other operating systems on your computer, install {{Pkg|os-prober}} before running the next command. However os-prober is not known to properly detect UEFI OSes.}}<br />
<br />
# grub-mkconfig -o /boot/grub/grub.cfg<br />
<br />
For more information on configuring and using GRUB, see [[GRUB]].<br />
<br />
===== rEFInd =====<br />
<br />
For sample use-case setups using rEFInd as the boot manager see [[rEFInd]]<br />
<br />
=== Unmount the partitions and reboot ===<br />
<br />
Exit from the chroot environment:<br />
<br />
# exit<br />
<br />
Since the partitions are mounted under {{ic|/mnt}}, use the following command to unmount them:<br />
<br />
# umount -R /mnt<br />
<br />
Reboot the computer:<br />
<br />
# reboot<br />
<br />
{{Tip|Be sure to remove the installation media, otherwise you will boot back into it.}}<br />
<noinclude>{{Beginners' Guide navigation}}</noinclude></div>Panth0rhttps://wiki.archlinux.org/index.php?title=SLiM&diff=263321SLiM2013-06-18T20:30:25Z<p>Panth0r: /* Zsh */ per /bin/ -> /usr/bin/ move; don't know current default slim.conf</p>
<hr />
<div>[[Category:Display managers]]<br />
[[cs:SLiM]]<br />
[[es:SLiM]]<br />
[[fr:SLiM]]<br />
[[hu:SLiM]]<br />
[[it:SLiM]]<br />
[[ja:SLiM]]<br />
[[ko:SLiM]]<br />
[[pt:SLiM]]<br />
[[ru:SLiM]]<br />
[[sk:SLiM]]<br />
[[tr:SLiM]]<br />
[[zh-CN:SLiM]]<br />
[[zh-TW:SLiM]]<br />
{{Article summary start}}<br />
{{Article summary text|Provides an overview of the Simple Login Manager.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Display Manager}}<br />
{{Article summary end}}<br />
<br />
[http://slim.berlios.de/ SLiM] is an acronym for Simple Login Manager. SLiM is simple, lightweight and easily configurable. SLiM is used by some because it does not require the dependencies of [[GNOME]] or [[KDE]] and can help make a lighter system for users that like to use lightweight desktops like [[Xfce]], [[Openbox]], and [[Fluxbox]].<br />
<br />
== Installation ==<br />
<br />
[[pacman|Install]] {{pkg|slim}} from the [[official repositories]].<br />
<br />
== Configuration ==<br />
<br />
=== Enabling SLiM ===<br />
<br />
{{Note|{{pkg|slim}} no longer has ConsoleKit support, but relies on systemd-logind, and the system being booted with systemd.}}<br />
<br />
Enable the '''slim''' [[Daemons|daemon]]. With systemd, it is no longer possible to start slim using {{ic|inittab}}.<br />
This can be done via the following<br />
{{ic| systemctl enable slim.service}}<br />
<br />
=== Single environments ===<br />
<br />
To configure SLiM to load a particular environment, edit your {{ic|~/.xinitrc}} to load your desktop environment:<br />
<br />
{{bc|<br />
#!/bin/sh<br />
<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
exec <session-command><br />
}}<br />
<br />
Replace {{ic|<session-command>}} with the appropriate session command. Some examples of different desktop start commands:<br />
<br />
{{bc|<br />
exec awesome<br />
exec dwm<br />
exec startfluxbox<br />
exec fvwm2<br />
exec gnome-session<br />
exec openbox-session<br />
exec startkde<br />
exec startlxde<br />
exec startxfce4<br />
exec enlightenment_start<br />
}}<br />
<br />
For detailed instructions on how to start the various environments, refer to the appropriate wiki pages.<br />
<br />
SLiM reads the local {{ic|~/.xinitrc}} configuration and then launches the desktop according to what is in that file. If you do not have a {{ic|~/.xinitrc}} file, you can use the skeleton file by:<br />
<br />
$ cp /etc/skel/.xinitrc ~<br />
<br />
Remember to make {{ic|~/.xinitrc}} executable:<br />
<br />
chmod +x ~/.xinitrc<br />
<br />
=== Autologin ===<br />
<br />
To make SLiM automatically login as a specified user (without having to type a password) the following lines in {{ic|/etc/slim.conf}} should be changed.<br />
# default_user simone<br />
<br />
Uncomment this line, and change "simone" to the user to be logged into automatically.<br />
<br />
# auto_login no<br />
<br />
Uncomment this line and change the 'no' to 'yes'. This enables the auto login feature.<br />
<br />
=== Zsh ===<br />
{{Note|If you don't know what zsh is and you did not install it - ignore this paragraph.}}<br />
<br />
The default login command will not initialize your environment correctly [http://www.edsel.nu/2010/06/04/slim-simple-login-manager-on-freebsd/ [source]]. Change the login_cmd line in {{ic|/etc/slim.conf}} to:<br />
<br />
#login_cmd exec /bin/sh - ~/.xinitrc %session<br />
login_cmd exec /usr/bin/zsh -l ~/.xinitrc %session<br />
<br />
=== Multiple environments ===<br />
<br />
To be able to choose from multiple desktop environments, SLiM can be setup to log you into whichever you choose.<br />
<br />
Put a case statement similar to this one in your {{ic|~/.xinitrc}} file and edit the sessions variable in {{ic|/etc/slim.conf}} to match the names that trigger the case statement. You can cycle through sessions at login time by pressing F1. Note that this feature is experimental.<br />
<br />
{{bc|1=<br />
# Adapted from: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample<br />
<br />
case $1 in<br />
kde)<br />
exec startkde<br />
;;<br />
xfce4)<br />
exec startxfce4<br />
;;<br />
wmaker)<br />
exec wmaker<br />
;;<br />
blackbox)<br />
exec blackbox<br />
;;<br />
icewm&#124;*)<br />
icewmbg &<br />
icewmtray &<br />
exec icewm<br />
;;<br />
esac<br />
}}<br />
<br />
{{Note|<nowiki>In the latest version (1.3.5), slim does not preset any default session, so using a DEFAULT_SESSION variable will not work the way it used to. Instead put your default session as the last case and |*) to the statement (see above)</nowiki>}}<br />
<br />
=== Themes ===<br />
<br />
Install the {{Pkg|slim-themes}} package:<br />
<br />
# pacman -S slim-themes archlinux-themes-slim<br />
<br />
The {{Pkg|archlinux-themes-slim}} packages contains several different themes ([http://imageshack.us/photo/my-images/27/slimthemes.png/ slimthemes.png]). Look in the directory of {{ic|/usr/share/slim/themes}} to see the themes available. Enter the theme name on the {{ic|current_theme}} line in {{ic|/etc/slim.conf}}:<br />
<br />
#current_theme default<br />
current_theme archlinux-simplyblack<br />
<br />
To preview a theme run while an instance of the Xorg server is running by:<br />
<br />
$ slim -p /usr/share/slim/themes/<theme name><br />
<br />
To close, type "exit" in the Login line and press Enter.<br />
<br />
Additional theme packages can be found in the [[AUR]].<br />
<br />
==== Dual screen setup ====<br />
<br />
You can customize the slim theme in {{ic|/usr/share/slim/themes/<your-theme>/slim.theme}} to turn these percents values. The box itself is 450 pixels by 250 pixels:<br />
<br />
input_panel_x 50%<br />
input_panel_y 50%<br />
<br />
into pixels values:<br />
<br />
# These settings set the "archlinux-simplyblack" panel in the center of a 1440x900 screen<br />
input_panel_x 495<br />
input_panel_y 325<br />
<br />
# These settings set the "archlinux-retro" panel in the center of a 1680x1050 screen<br />
input_panel_x 615<br />
input_panel_y 400<br />
<br />
If your theme has a background picture you should use the background_style setting ('stretch', 'tile', 'center' or 'color') to get it correctly displayed. Have a look at the [http://slim.berlios.de/themes_howto.php very simple and clear official documentation about slim themes] for further details.<br />
<br />
== Other options ==<br />
<br />
A few things you might like to try.<br />
<br />
=== Changing the cursor ===<br />
<br />
If you want to change the default X cursor to a newer design, the {{AUR|slim-cursor}} package is available.<br />
<br />
After installing, edit {{ic|/etc/slim.conf}} and uncomment the line:<br />
<br />
cursor left_ptr<br />
<br />
This will give you a normal arrow instead. This setting is forwarded to {{ic|xsetroot -cursor_name}}. You can look up the possible cursor names [http://cvsweb.xfree86.org/cvsweb/*checkout*/xc/lib/X11/cursorfont.h?rev=HEAD&content-type=text/plain here] or in {{ic|/usr/share/icons/<your-cursor-theme>/cursors/}}.<br />
<br />
To change the cursor theme being used at the login screen, make a file named {{ic|/usr/share/icons/default/index.theme}} with this content:<br />
<br />
[Icon Theme]<br />
Inherits=<your-cursor-theme><br />
<br />
Replace <your-cursor-theme> with the name of the cursor theme you want to use (e.g. whiteglass).<br />
<br />
=== Match SLiM and Desktop Wallpaper ===<br />
<br />
To share a wallpaper between SLiM and your desktop, rename the used theme background, then create a link from your desktop wallpaper file to the default SLiM theme:<br />
<br />
# mv /usr/share/slim/themes/default/background.jpg{,.bck}<br />
# ln -s /path/to/mywallpaper.jpg /usr/share/slim/themes/default/background.jpg<br />
<br />
=== Shutdown, reboot, suspend, exit, launch terminal from SLiM ===<br />
<br />
You may shutdown, reboot, suspend, exit or even launch a terminal from the SLiM login screen. To do so, use the values in the username field, and the root password in the password field:<br />
<br />
* To launch a terminal, enter '''console''' as the username (defaults to xterm which must be installed separately... edit {{ic|/etc/slim.conf}} to change terminal preference)<br />
* For shutdown, enter '''halt''' as the username<br />
* For reboot, enter '''reboot''' as the username<br />
* To exit to bash, enter '''exit''' as the username<br />
* For suspend, enter '''suspend''' as the username (suspend is disabled by default, edit {{ic|/etc/slim.conf}} as root to uncomment the {{ic|suspend_cmd}} line and, if necessary modify the suspend command itself (e.g. change {{ic|/usr/sbin/suspend}} to {{ic|sudo /usr/sbin/pm-suspend}}))<br />
<br />
=== SLiM init error with rc.d daemon ===<br />
<br />
If you initialize SLiM with {{ic|/etc/rc.conf}} inside the DAEMONS array and it fails to initialize it's most likely a lock file issue. SLiM creates a lock file in {{ic|/var/lock}} on each initialization, however, in most cases the lock folder in {{ic|/var}} does not exist preventing SLiM from initializing. Check to make sure {{ic|/var/lock}} exists, if it does not you can create it by typing the following:<br />
<br />
# mkdir /var/lock/<br />
<br />
=== Power-off error with Splashy ===<br />
<br />
If you use Splashy and SLiM, sometimes you can't power-off or reboot from menu in GNOME, Xfce, LXDE or others. Check your {{ic|/etc/slim.conf}} and {{ic|/etc/splash.conf}}; set the {{ic|1=DEFAULT_TTY=7}} same as {{ic|xserver_arguments vt07}}.<br />
<br />
=== Power-off tray icon fails ===<br />
<br />
If your power off tray icon fails, it could be due to not having root privileges. To start a tray icon with root privileges, be sure to have SLiM start the program. Edit {{ic|/etc/slim.conf}} as follows:<br />
sessionstart_cmd /path/to/tray/icon/program &<br />
<br />
=== Login information with SLiM ===<br />
<br />
By default, SLiM fails to log logins to utmp and wtmp which causes who, last, etc. to misreport login information. To fix this edit your {{ic|slim.conf}} as follows:<br />
<br />
sessionstart_cmd /usr/bin/sessreg -a -l $DISPLAY %user<br />
sessionstop_cmd /usr/bin/sessreg -d -l $DISPLAY %user<br />
<br />
=== Custom SLiM Login Commands ===<br />
<br />
You can also use the sessionstart_cmd/sessionstop_cmd in {{ic|/etc/slim.conf}} to log specific infomation, such as the session, user, or theme used by slim:<br />
<br />
sessionstop_cmd /usr/bin/logger -i -t ASKAPACHE "(sessionstop_cmd: u:%user s:%session t:%theme)"<br />
sessionstart_cmd /usr/bin/logger -i -t ASKAPACHE "(sessionstart_cmd: u:%user s:%session t:%theme)"<br />
<br />
Or if you want to play a song when slim loads (and you have the beep program installed)<br />
<br />
sessionstart_cmd /usr/bin/beep -f 659 -l 460 -n -f 784 -l 340 -n -f 659 -l 230 -n -f 659 -l 110<br />
<br />
=== SLiM and Gnome Keyring ===<br />
If you are using SLiM to launch a Gnome session and have trouble accessing your keyring, for example not being automatically authenticated on login, add the following lines to {{ic|/etc/pam.d/slim}} (as discussed [https://bugs.archlinux.org/task/18637 here]).<br />
auth optional pam_gnome_keyring.so<br />
session optional pam_gnome_keyring.so auto_start<br />
<br />
You also have to add to {{ic|/etc/pam.d/passwd}}:<br />
password optional pam_gnome_keyring.so<br />
<br />
If you use a screensaver you also have to add <br />
auth optional pam_gnome_keyring.so<br />
to {{ic|/etc/pam.d/gnome-screensaver}} for example (replace {{ic|gnome-screensaver}} with {{ic|slimlock}}, {{ic|slock}}, whatever you use). If you don't do that, your keyring is locked when screen is locked by your screensaver and not unlocked again after logging back in.<br />
<br />
However, this fix alone no longer works since Gnome 2.30. Further changes are necessary as described [https://bugs.archlinux.org/task/18930 here]. Modifying the {{ic|login_cmd}} line in {{ic|/etc/slim.conf}}:<br />
login_cmd exec dbus-launch /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1<br />
<br />
As of GNOME 3.4, you need to edit {{ic|<nowiki>/etc/pam.d/{slim,passwd}</nowiki>}} as mentioned above, so that {{ic|<nowiki>/etc/pam.d/slim</nowiki>}} looks like:<br />
#%PAM-1.0<br />
auth requisite pam_nologin.so<br />
auth required pam_env.so<br />
auth required pam_unix.so<br />
auth optional pam_gnome_keyring.so<br />
account required pam_unix.so<br />
session required pam_limits.so<br />
session required pam_unix.so<br />
session optional pam_gnome_keyring.so auto_start<br />
password required pam_unix.so<br />
and {{ic|<nowiki>/etc/pam.d/passwd</nowiki>}}<br />
#%PAM-1.0<br />
password required pam_unix.so sha512 shadow nullok<br />
password optional pam_gnome_keyring.so<br />
As of 2012-10-13, {{ic|<nowiki>/etc/pam.d/gnome-screensaver</nowiki>}} already contains the {{ic|<nowiki>pam_gnome_keyring.so</nowiki>}} instruction.<br />
<br />
The correct positioning of the {{ic|<nowiki>pam_gnome_keyring.so</nowiki>}} instructions were taken from [http://live.gnome.org/GnomeKeyring/Pam here].<br />
<br />
After editing the above files, you need to edit {{ic|<nowiki>/etc/inittab</nowiki>}}.<br />
<br />
The solutions mentioned here and also further information are found [http://live.gnome.org/GnomeKeyring/Pam here].<br />
<br />
If you have problems keeping the keyring unlocked for longer sessions, there is another thing that Gnome does: <br />
Look at {{ic|<nowiki>/etc/xdg/autostart/{gnome-keyring-gpg.desktop, gnome-keyring-pkcs11.desktop, gnome-keyring-secrets.desktop, gnome-keyring-ssh.desktop}</nowiki>}}. <br />
<br />
Append the following lines to .xinitrc just before you start your wm (example here is awesome wm):<br />
/usr/bin/gnome-keyring-daemon --start --components=gpg<br />
/usr/bin/gnome-keyring-daemon --start --components=pkcs11<br />
/usr/bin/gnome-keyring-daemon --start --components=secrets<br />
/usr/bin/gnome-keyring-daemon --start --components=ssh<br />
/usr/bin/awesome<br />
<br />
After login check if there is only one gnome-keyring-daemon instance running ({{ic|ps -A | grep gnome}}). If those lines are executed too early then you have 4 instances running which is not good.<br />
<br />
You also should notice that seahorse for example does not show any pkcs11 errors anymore and that your keyring is unlocked all the time and does not lock itself anymore. Finally {{pkg|gnome-keyring}} is fully functional like in Gnome. See also [https://bbs.archlinux.org/viewtopic.php?pid=1019845#p1019845 here].<br />
<br />
=== Setting DPI with SLiM ===<br />
<br />
The Xorg server generally picks up the DPI but if it doesn't you can specify it to SLiM. If you set the DPI with the argument -dpi 96 in {{ic|/etc/X11/xinit/xserverrc}} it will not work with SLiM. To fix this change your {{ic|slim.conf}} from:<br />
<br />
xserver_arguments -nolisten tcp vt07 <br />
<br />
to<br />
<br />
xserver_arguments -nolisten tcp vt07 -dpi 96<br />
<br />
=== Use a random theme ===<br />
<br />
Use the {{ic|current_theme}} variable as a comma separated list to specify a set from which to choose. Selection is random.<br />
<br />
===Move the whole session to another VT===<br />
Lets say you have commented out tty terminals 3-6 as you may not use them. (You may use screen and therefore only need one terminal)<br />
So, to move the X-Server you need to change one number in the {{ic|/etc/slim.conf}} file. Just a few lines down you should see:<br />
xserver_arguments -nolisten tcp vt07<br />
<br />
Simply change the vt07 to lets say vt03 as there is no agetty started there.<br />
<br />
=== Automatically mount your encrypted /home on login ===<br />
<br />
You can use [[Pam_mount#Slim|pam_mount]].<br />
<br />
=== Change Keyboard Layout ===<br />
<br />
Edit {{ic|/etc/X11/xorg.conf.d/10-evdev.conf}}, find the following section, add the two bolded lines, and replace ''dvorak'' with your preferred keymap:<br />
<br />
Section "InputClass"<br />
Identifier "evdev keyboard catchall"<br />
MatchIsKeyboard "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Driver "evdev"<br />
<br />
'''# Keyboard layouts'''<br />
'''Option "XkbLayout" "''dvorak''"'''<br />
EndSection<br />
<br />
== All Slim Options ==<br />
Here is a list of all the slim configuration options and their default values.<br />
<br />
{{Note|welcome_msg allows 2 variables '''%host''' and '''%domain'''<br>sessionstart_cmd allows '''%user''' ''(execd right before login_cmd)'' and it is also allowed in sessionstop_cmd<br>login_cmd allows '''%session''' and '''%theme'''}}<br />
<br />
{| class="wikitable collapsible collapsable collapsed"<br />
|-<br />
! Option Name || Default Value<br />
|-<br />
| default_path ||{{ic|/bin:/usr/bin:/usr/local/bin}}<br />
|-<br />
| default_xserver ||{{ic|/usr/bin/X}}<br />
|-<br />
| xserver_arguments ||{{ic|vt07 -auth /var/run/slim.auth}}<br />
|-<br />
| numlock ||<br />
|-<br />
| daemon || {{ic|yes}}<br />
|-<br />
| xauth_path ||{{ic|/usr/bin/xauth}}<br />
|-<br />
| login_cmd ||{{ic|exec /bin/bash -login ~/.xinitrc %session}}<br />
|-<br />
| halt_cmd ||{{ic|/sbin/shutdown -h now}}<br />
|-<br />
| reboot_cmd ||{{ic|/sbin/shutdown -r now}}<br />
|-<br />
| suspend_cmd ||<br />
|-<br />
| sessionstart_cmd ||<br />
|-<br />
| sessionstop_cmd ||<br />
|-<br />
| console_cmd ||{{ic|/usr/bin/xterm -C -fg white -bg black +sb -g %dx%d+%d+%d -fn %dx%d -T }}<br />
|-<br />
| screenshot_cmd ||{{ic|import -window root /slim.png}}<br />
|-<br />
| welcome_msg ||{{ic|Welcome to %host}}<br />
|-<br />
| session_msg ||{{ic|Session:}}<br />
|-<br />
| default_user ||<br />
|-<br />
| focus_password ||{{ic|no}}<br />
|-<br />
| auto_login ||{{ic|no}}<br />
|-<br />
| current_theme ||{{ic|default}}<br />
|-<br />
| lockfile ||{{ic|/var/run/slim.lock}}<br />
|-<br />
| logfile ||{{ic|/var/log/slim.log}}<br />
|-<br />
| authfile ||{{ic|/var/run/slim.auth}}<br />
|-<br />
| shutdown_msg ||{{ic|The system is halting...}}<br />
|-<br />
| reboot_msg ||{{ic|The system is rebooting...}}<br />
|-<br />
| sessions ||{{ic|wmaker,blackbox,icewm}}<br />
|-<br />
| sessiondir ||<br />
|-<br />
| hidecursor ||{{ic|false}}<br />
|-<br />
| input_panel_x ||{{ic|50%}}<br />
|-<br />
| input_panel_y ||{{ic|40%}}<br />
|-<br />
| input_name_x ||{{ic|200}}<br />
|-<br />
| input_name_y ||{{ic|154}}<br />
|-<br />
| input_pass_x ||{{ic|-1}}<br />
|-<br />
| input_pass_y ||{{ic|-1}}<br />
|-<br />
| input_font ||{{ic|1=Verdana:size=11}}<br />
|-<br />
| input_color ||{{ic|#000000}}<br />
|-<br />
| input_cursor_height ||{{ic|20}}<br />
|-<br />
| input_maxlength_name ||{{ic|20}}<br />
|-<br />
| input_maxlength_passwd ||{{ic|20}}<br />
|-<br />
| input_shadow_xoffset ||{{ic|0}}<br />
|-<br />
| input_shadow_yoffset ||{{ic|0}}<br />
|-<br />
| input_shadow_color ||{{ic|#FFFFFF}}<br />
|-<br />
| welcome_font ||{{ic|1=Verdana:size=14}}<br />
|-<br />
| welcome_color ||{{ic|#FFFFFF}}<br />
|-<br />
| welcome_x ||{{ic|-1}}<br />
|-<br />
| welcome_y ||{{ic|-1}}<br />
|-<br />
| welcome_shadow_xoffset ||{{ic|0}}<br />
|-<br />
| welcome_shadow_yoffset ||{{ic|0}}<br />
|-<br />
| welcome_shadow_color ||{{ic|#FFFFFF}}<br />
|-<br />
| intro_msg ||<br />
|-<br />
| intro_font ||{{ic|1=Verdana:size=14}}<br />
|-<br />
| intro_color ||{{ic|#FFFFFF}}<br />
|-<br />
| intro_x ||{{ic|-1}}<br />
|-<br />
| intro_y ||{{ic|-1}}<br />
|-<br />
| background_style ||{{ic|stretch}}<br />
|-<br />
| background_color ||{{ic|#CCCCCC}}<br />
|-<br />
| username_font ||{{ic|1=Verdana:size=12}}<br />
|-<br />
| username_color ||{{ic|#FFFFFF}}<br />
|-<br />
| username_x ||{{ic|-1}}<br />
|-<br />
| username_y ||{{ic|-1}}<br />
|-<br />
| username_msg ||{{ic|Please enter your username}}<br />
|-<br />
| username_shadow_xoffset ||{{ic|0}}<br />
|-<br />
| username_shadow_yoffset ||{{ic|0}}<br />
|-<br />
| username_shadow_color ||{{ic|#FFFFFF}}<br />
|-<br />
| password_x ||{{ic|-1}}<br />
|-<br />
| password_y ||{{ic|-1}}<br />
|-<br />
| password_msg ||{{ic|Please enter your password}}<br />
|-<br />
| msg_color ||{{ic|#FFFFFF}}<br />
|-<br />
| msg_font ||{{ic|1=Verdana:size=16:bold}}<br />
|-<br />
| msg_x ||{{ic|40}}<br />
|-<br />
| msg_y ||{{ic|40}}<br />
|-<br />
| msg_shadow_xoffset ||{{ic|0}}<br />
|-<br />
| msg_shadow_yoffset ||{{ic|0}}<br />
|-<br />
| msg_shadow_color ||{{ic|#FFFFFF}}<br />
|-<br />
| session_color ||{{ic|#FFFFFF}}<br />
|-<br />
| session_font ||{{ic|1=Verdana:size=16:bold}}<br />
|-<br />
| session_x ||{{ic|50%}}<br />
|-<br />
| session_y ||{{ic|90%}}<br />
|-<br />
| session_shadow_xoffset ||{{ic|0}}<br />
|-<br />
| session_shadow_yoffset ||{{ic|0}}<br />
|-<br />
| session_shadow_color ||{{ic|#FFFFFF}}<br />
|}<br />
== Uninstallation ==<br />
To completely remove SLiM:<br />
{{bc| # pacman -Rns slim<br />
# rm /etc/systemd/system/display-manager.service<br />
}}<br />
== See also ==<br />
<br />
* [http://slim.berlios.de/ SLiM homepage]<br />
* [http://slim.berlios.de/manual.php SLiM documentation]</div>Panth0rhttps://wiki.archlinux.org/index.php?title=Profile-sync-daemon&diff=261220Profile-sync-daemon2013-06-05T05:37:12Z<p>Panth0r: /* Edit /etc/psd.conf */ per "List browsers separated by spaces" ~~~~</p>
<hr />
<div>[[Category:Web Browser]]<br />
[[Category:Scripts]]<br />
{{Article summary start}}<br />
{{Article summary text|{{AUR|Profile-sync-daemon}} (psd) is a diminutive pseudo-daemon designed to manage your browser's profile in tmpfs and to periodically sync it back to your physical disc (HDD/SSD). This is accomplished via a symlinking step and an innovative use of rsync to maintain back-up and synchronization between the two. One of the major design goals of psd is a completely transparent user experience.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Anything-sync-daemon}}<br />
{{Article summary wiki|Firefox}}<br />
{{Article summary wiki|Chromium}}<br />
{{Article summary wiki|Opera}}<br />
{{Article summary wiki|SSD}}<br />
{{Article summary end}}<br />
<br />
== Benefits of Psd ==<br />
Running this daemon is beneficial for two reasons:<br />
#Reduced wear to physical discs<br />
#Speed<br />
<br />
Since the profile(s), browser cache*, etc. are relocated into tmpfs (RAM disk), the corresponding onslaught of I/O associated with using the browser is also redirected from the physical disc to RAM, thus reducing wear to the physical disc and also greatly improving browser speed and responsiveness. For example, the access time of RAM is on the order of nanoseconds while the access time of physical discs is on the order of milliseconds. This is a difference of six orders of magnitude or 1,000,000 times faster.<br />
<br />
{{Note|Chromium actually keeps its cache directory '''separately''' from its browser profile directory. It is not within the scope of profile-sync-daemon to modify this behavior; users are encouraged to refer to the [[Chromium_Tips_and_Tweaks#Cache_in_tmpfs]] section of the main [[Chromium_Tips_and_Tweaks]] article for several work-arounds.}}<br />
<br />
==Supported Browsers ==<br />
Currently, the following browsers are auto-detected and managed:<br />
*[[chromium]]<br />
*{{AUR|conkeror}}<br />
*[[firefox]] (all flavors including stable, beta, and aurora)<br />
*[http://www.webupd8.org/2011/05/install-firefox-nightly-from-ubuntu-ppa.html firefox-trunk]: An Ubuntu-only browser<br />
*{{AUR|google-chrome}}<br />
*[https://bbs.archlinux.org/viewtopic.php?id=117157 heftig's version of aurora]: An Arch Linux only browser<br />
*[[midori]]<br />
*[[opera]]<br />
*{{AUR|opera-next}}<br />
*Qupzilla<br />
<br />
==Setup and Installation==<br />
{{AUR|profile-sync-daemon}} is available for download from the [[Arch User Repository|AUR]]. Build it and install like any other package. <br />
<br />
=== Edit /etc/psd.conf ===<br />
Edit the included {{ic|/etc/psd.conf}} defining which user(s) will have their profiles managed by psd.<br />
<br />
Example:<br />
# List users separated by spaces whose browser(s) profile(s) will get symlinked <br />
# and sync'ed to tmpfs.<br />
# Do NOT list a user twice!<br />
USERS="facade happy"<br />
<br />
{{Note|At least one user must be defined.}}<br />
<br />
Optionally uncomment the BROWSERS array and populate it with whichever browser(s) are to be sync'ed to tmpfs. If the BROWSERS array stays commented (default) then all supported browser profiles will be sync'ed if they exist.<br />
<br />
Example: Let's say that Chromium, Opera and Midori are installed but only Chromium and Opera are to be sync'ed to tmpfs since the user keeps Midori as a backup browser and it is seldom used:<br />
<br />
# List browsers separated by spaces to include in the sync. Useful if you do not<br />
# wish to have all possible browser profiles sync'ed.<br />
#<br />
# Possible values:<br />
# chromium<br />
# conkeror.mozdev.org<br />
# firefox<br />
# firefox-trunk<br />
# google-chrome<br />
# heftig-aurora <br />
# midori<br />
# opera<br />
# opera-next<br />
# qupzilla<br />
#<br />
# If the following is commented out (default), then all available/supported <br />
# browsers will be sync'ed, separated by comma<br />
BROWSERS="chromium opera"<br />
<br />
== Using PSD ==<br />
=== Preview Mode (Parse) ===<br />
The 'parse' option can be called to show users exactly what psd will do based on the /etc/psd.conf entered. Call it like so:<br />
$ profile-sync-daemon parse<br />
Profile-sync-daemon v5.24<br />
<br />
Psd will manage the following per /etc/psd.conf settings:<br />
<br />
browser/psname: chromium/chromium<br />
owner/group: facade/users<br />
sync target: /home/facade/.config/chromium<br />
tmpfs dir: /tmp/facade-chromium<br />
profile size: 81M<br />
<br />
browser/psname: firefox/firefox<br />
owner/group: facade/users<br />
sync target: /mnt/data/docs/facade/mozilla/firefox/1Zp9V43q.banking<br />
tmpfs dir: /tmp/facade-firefox-1Zp9V43q.banking<br />
profile size: 5.9M<br />
<br />
browser/psname: firefox/firefox<br />
owner/group: facade/users<br />
sync target: /mnt/data/docs/facade/mozilla/firefox/obg67zqQ.proxy<br />
tmpfs dir: /tmp/facade-firefox-obg67zqQ.proxy<br />
profile size: 17M<br />
<br />
As shown in the output and as stated above, if no specific browser or subset of browsers are defined in the BROWSERS array, psd will sync ALL supported profiles that it finds for the given user(s).<br />
<br />
=== Running PSD to Manage Profiles ===<br />
Do not call {{ic|/usr/bin/profile-sync-daemon}} to sync or to unsync directly. Instead use the provided service files. <br />
<br />
Both a systemd service file and a timer are provided and should be used to interact with psd. Both should be invoked together! The role of the timer is update the tmpfs copy/copies back to the disk which it does once per hour. Failure to start the resync timer will result in the profile being sync'ed only on start up and shutdown.<br />
<br />
# systemctl [option] psd psd-resync<br />
<br />
Available options:<br />
start Turn on daemon and timer.<br />
stop Turn off daemon and timer.<br />
enable Autostart daemon and timer on boot-up.<br />
disable Don't autostart daemon and timer on boot-up.<br />
<br />
<br />
Start psd and its timer as well as set psd and its timer to start/stop at boot/shutdown ''(highly recommended)'':<br />
# systemctl enable psd psd-resync<br />
# systemctl start psd psd-resync<br />
<br />
Obviously, you must first close your browser before starting the service.<br />
<br />
=== Sync at More Frequent Intervals (Optional) ===<br />
The package provided timer syncs once per hour. Users may optionally redefine this behavior simply be creating their own timer with whatever interval is desired. The example below syncs once every ten minutes:<br />
<br />
{{hc|/etc/systemd/system/my-psd-resync.timer|2=<nowiki><br />
[Unit]<br />
Description=My own profile resync<br />
After=psd.service<br />
Conflicts=psd-resync.timer<br />
<br />
[Timer]<br />
Unit=psd-resync.service<br />
OnUnitActiveSec=10min<br />
</nowiki>}}<br />
{{Note|The 'Conflicts...' line disables the package-provided timer and allows 'my-psd-resync.timer' to take over and work with psd-resync.service.}}<br />
<br />
See `man systemd.timer` for additional options.<br />
<br />
== Caveats for Firefox and Heftig's Aurora ONLY ==<br />
The way psd keeps track of browser profiles and sync targets requires users to have a unique name as the ''last directory'' for all profiles in their respective $HOME/.mozilla/<browser>/profiles.ini files. Psd will check when it is called to run for this and refuse if this rule is not satisfied. The following is an example of a BAD profile that will fail the the test. Note that although each full path is unique, they both ''end'' in the same name! Again, the user must modify the profiles.ini and the corresponding directory on the filesystem to correct this in order to use Psd.<br />
<br />
$ cat ~/.mozilla/firefox/profiles.ini<br />
<br />
[General]<br />
StartWithLastProfile=1<br />
<br />
[Profile0 for user facade]<br />
Name=normal<br />
IsRelative=0<br />
Path=/mnt/data/docs/'''facade'''/mozilla/firefox/'''myprofile.abc'''<br />
Default=1<br />
<br />
[Profile1 for user happy]<br />
Name=proxy<br />
IsRelative=0<br />
Path=/mnt/data/docs/'''happy'''/mozilla/firefox/'''myprofile.abc'''<br />
<br />
== Support ==<br />
Post in the [https://bbs.archlinux.org/viewtopic.php?pid=1026974 discussion thread] with comments or concerns.<br />
<br />
== PSD On Other Distros ==<br />
Psd is a simple bash script and should therefore run on any Linux distro. Below is a list of distros known to package psd, and a link to download their respective packages. As noted above, these are unsupported by the author due to their own, unique init scripts:<br />
<br />
=== Chakra ===<br />
http://chakra-linux.org/ccr/packages.php?ID=5008<br />
<br />
=== Debian ===<br />
To add the PPA (personal package archive) to your Debian (tested on squeeze) system, and to install psd:<br />
<br />
# echo "deb http://ppa.launchpad.net/graysky/utils/ubuntu quantal main" > /etc/apt/sources.list.d/graysky.list<br />
# echo "deb-src http://ppa.launchpad.net/graysky/utils/ubuntu quantal main" >> /etc/apt/sources.list.d/graysky.list<br />
# apt-key adv --keyserver keyserver.ubuntu.com --recv-keys FF7F9516<br />
# apt-get update<br />
# apt-get install profile-sync-daemon<br />
<br />
=== Exherbo ===<br />
http://git.exherbo.org/summer/packages/net-www/profile-sync-daemon<br />
<br />
=== Fedora 18 ===<br />
http://repo-ck.com/fedora_rpms<br />
<br />
=== Gentoo ===<br />
http://packages.gentoo.org/package/www-misc/profile-sync-daemon<br />
=== Ubuntu ===<br />
To add the PPA (personal package archive) to your Ubuntu (packages available for Lucid and newer) system, and to install psd:<br />
<br />
$ sudo add-apt-repository ppa:graysky/utils<br />
$ sudo apt-get update<br />
$ sudo apt-get install profile-sync-daemon<br />
<br />
== External Links Mentioning PSD ==<br />
*http://www.webupd8.org/2013/02/keep-your-browser-profiles-in-tmpfs-ram.html<br />
*http://bernaerts.dyndns.org/linux/250-ubuntu-tweaks-ssd</div>Panth0rhttps://wiki.archlinux.org/index.php?title=Profile-sync-daemon&diff=261218Profile-sync-daemon2013-06-05T05:28:03Z<p>Panth0r: /* Setup and Installation */ Feel as though the "Profile-sync-daemon" AUR link should be all lowercased (despite opening a sentence) ~~~~</p>
<hr />
<div>[[Category:Web Browser]]<br />
[[Category:Scripts]]<br />
{{Article summary start}}<br />
{{Article summary text|{{AUR|Profile-sync-daemon}} (psd) is a diminutive pseudo-daemon designed to manage your browser's profile in tmpfs and to periodically sync it back to your physical disc (HDD/SSD). This is accomplished via a symlinking step and an innovative use of rsync to maintain back-up and synchronization between the two. One of the major design goals of psd is a completely transparent user experience.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Anything-sync-daemon}}<br />
{{Article summary wiki|Firefox}}<br />
{{Article summary wiki|Chromium}}<br />
{{Article summary wiki|Opera}}<br />
{{Article summary wiki|SSD}}<br />
{{Article summary end}}<br />
<br />
== Benefits of Psd ==<br />
Running this daemon is beneficial for two reasons:<br />
#Reduced wear to physical discs<br />
#Speed<br />
<br />
Since the profile(s), browser cache*, etc. are relocated into tmpfs (RAM disk), the corresponding onslaught of I/O associated with using the browser is also redirected from the physical disc to RAM, thus reducing wear to the physical disc and also greatly improving browser speed and responsiveness. For example, the access time of RAM is on the order of nanoseconds while the access time of physical discs is on the order of milliseconds. This is a difference of six orders of magnitude or 1,000,000 times faster.<br />
<br />
{{Note|Chromium actually keeps its cache directory '''separately''' from its browser profile directory. It is not within the scope of profile-sync-daemon to modify this behavior; users are encouraged to refer to the [[Chromium_Tips_and_Tweaks#Cache_in_tmpfs]] section of the main [[Chromium_Tips_and_Tweaks]] article for several work-arounds.}}<br />
<br />
==Supported Browsers ==<br />
Currently, the following browsers are auto-detected and managed:<br />
*[[chromium]]<br />
*{{AUR|conkeror}}<br />
*[[firefox]] (all flavors including stable, beta, and aurora)<br />
*[http://www.webupd8.org/2011/05/install-firefox-nightly-from-ubuntu-ppa.html firefox-trunk]: An Ubuntu-only browser<br />
*{{AUR|google-chrome}}<br />
*[https://bbs.archlinux.org/viewtopic.php?id=117157 heftig's version of aurora]: An Arch Linux only browser<br />
*[[midori]]<br />
*[[opera]]<br />
*{{AUR|opera-next}}<br />
*Qupzilla<br />
<br />
==Setup and Installation==<br />
{{AUR|profile-sync-daemon}} is available for download from the [[Arch User Repository|AUR]]. Build it and install like any other package. <br />
<br />
=== Edit /etc/psd.conf ===<br />
Edit the included {{ic|/etc/psd.conf}} defining which user(s) will have their profiles managed by psd.<br />
<br />
Example:<br />
# List users separated by spaces whose browser(s) profile(s) will get symlinked <br />
# and sync'ed to tmpfs.<br />
# Do NOT list a user twice!<br />
USERS="facade happy"<br />
<br />
{{Note|At least one user must be defined.}}<br />
<br />
Optionally uncomment the BROWSERS array and populate it with whichever browser(s) are to be sync'ed to tmpfs. If the BROWSERS array stays commented (default) then all supported browser profiles will be sync'ed if they exist.<br />
<br />
Example: Let's say that Chromium, Opera and Midori are installed but only Chromium and Opera are to be sync'ed to tmpfs since the user keeps Midori as a backup browser and it is seldom used:<br />
<br />
# List browsers separated by spaces to include in the sync. Useful if you do not<br />
# wish to have all possible browser profiles sync'ed.<br />
#<br />
# Possible values:<br />
# chromium<br />
# conkeror.mozdev.org<br />
# firefox<br />
# firefox-trunk<br />
# google-chrome<br />
# heftig-aurora <br />
# midori<br />
# opera<br />
# opera-next<br />
# qupzilla<br />
#<br />
# If the following is commented out (default), then all available/supported <br />
# browsers will be sync'ed, separated by comma<br />
BROWSERS="chromium,opera"<br />
<br />
== Using PSD ==<br />
=== Preview Mode (Parse) ===<br />
The 'parse' option can be called to show users exactly what psd will do based on the /etc/psd.conf entered. Call it like so:<br />
$ profile-sync-daemon parse<br />
Profile-sync-daemon v5.24<br />
<br />
Psd will manage the following per /etc/psd.conf settings:<br />
<br />
browser/psname: chromium/chromium<br />
owner/group: facade/users<br />
sync target: /home/facade/.config/chromium<br />
tmpfs dir: /tmp/facade-chromium<br />
profile size: 81M<br />
<br />
browser/psname: firefox/firefox<br />
owner/group: facade/users<br />
sync target: /mnt/data/docs/facade/mozilla/firefox/1Zp9V43q.banking<br />
tmpfs dir: /tmp/facade-firefox-1Zp9V43q.banking<br />
profile size: 5.9M<br />
<br />
browser/psname: firefox/firefox<br />
owner/group: facade/users<br />
sync target: /mnt/data/docs/facade/mozilla/firefox/obg67zqQ.proxy<br />
tmpfs dir: /tmp/facade-firefox-obg67zqQ.proxy<br />
profile size: 17M<br />
<br />
As shown in the output and as stated above, if no specific browser or subset of browsers are defined in the BROWSERS array, psd will sync ALL supported profiles that it finds for the given user(s).<br />
<br />
=== Running PSD to Manage Profiles ===<br />
Do not call {{ic|/usr/bin/profile-sync-daemon}} to sync or to unsync directly. Instead use the provided service files. <br />
<br />
Both a systemd service file and a timer are provided and should be used to interact with psd. Both should be invoked together! The role of the timer is update the tmpfs copy/copies back to the disk which it does once per hour. Failure to start the resync timer will result in the profile being sync'ed only on start up and shutdown.<br />
<br />
# systemctl [option] psd psd-resync<br />
<br />
Available options:<br />
start Turn on daemon and timer.<br />
stop Turn off daemon and timer.<br />
enable Autostart daemon and timer on boot-up.<br />
disable Don't autostart daemon and timer on boot-up.<br />
<br />
<br />
Start psd and its timer as well as set psd and its timer to start/stop at boot/shutdown ''(highly recommended)'':<br />
# systemctl enable psd psd-resync<br />
# systemctl start psd psd-resync<br />
<br />
Obviously, you must first close your browser before starting the service.<br />
<br />
=== Sync at More Frequent Intervals (Optional) ===<br />
The package provided timer syncs once per hour. Users may optionally redefine this behavior simply be creating their own timer with whatever interval is desired. The example below syncs once every ten minutes:<br />
<br />
{{hc|/etc/systemd/system/my-psd-resync.timer|2=<nowiki><br />
[Unit]<br />
Description=My own profile resync<br />
After=psd.service<br />
Conflicts=psd-resync.timer<br />
<br />
[Timer]<br />
Unit=psd-resync.service<br />
OnUnitActiveSec=10min<br />
</nowiki>}}<br />
{{Note|The 'Conflicts...' line disables the package-provided timer and allows 'my-psd-resync.timer' to take over and work with psd-resync.service.}}<br />
<br />
See `man systemd.timer` for additional options.<br />
<br />
== Caveats for Firefox and Heftig's Aurora ONLY ==<br />
The way psd keeps track of browser profiles and sync targets requires users to have a unique name as the ''last directory'' for all profiles in their respective $HOME/.mozilla/<browser>/profiles.ini files. Psd will check when it is called to run for this and refuse if this rule is not satisfied. The following is an example of a BAD profile that will fail the the test. Note that although each full path is unique, they both ''end'' in the same name! Again, the user must modify the profiles.ini and the corresponding directory on the filesystem to correct this in order to use Psd.<br />
<br />
$ cat ~/.mozilla/firefox/profiles.ini<br />
<br />
[General]<br />
StartWithLastProfile=1<br />
<br />
[Profile0 for user facade]<br />
Name=normal<br />
IsRelative=0<br />
Path=/mnt/data/docs/'''facade'''/mozilla/firefox/'''myprofile.abc'''<br />
Default=1<br />
<br />
[Profile1 for user happy]<br />
Name=proxy<br />
IsRelative=0<br />
Path=/mnt/data/docs/'''happy'''/mozilla/firefox/'''myprofile.abc'''<br />
<br />
== Support ==<br />
Post in the [https://bbs.archlinux.org/viewtopic.php?pid=1026974 discussion thread] with comments or concerns.<br />
<br />
== PSD On Other Distros ==<br />
Psd is a simple bash script and should therefore run on any Linux distro. Below is a list of distros known to package psd, and a link to download their respective packages. As noted above, these are unsupported by the author due to their own, unique init scripts:<br />
<br />
=== Chakra ===<br />
http://chakra-linux.org/ccr/packages.php?ID=5008<br />
<br />
=== Debian ===<br />
To add the PPA (personal package archive) to your Debian (tested on squeeze) system, and to install psd:<br />
<br />
# echo "deb http://ppa.launchpad.net/graysky/utils/ubuntu quantal main" > /etc/apt/sources.list.d/graysky.list<br />
# echo "deb-src http://ppa.launchpad.net/graysky/utils/ubuntu quantal main" >> /etc/apt/sources.list.d/graysky.list<br />
# apt-key adv --keyserver keyserver.ubuntu.com --recv-keys FF7F9516<br />
# apt-get update<br />
# apt-get install profile-sync-daemon<br />
<br />
=== Exherbo ===<br />
http://git.exherbo.org/summer/packages/net-www/profile-sync-daemon<br />
<br />
=== Fedora 18 ===<br />
http://repo-ck.com/fedora_rpms<br />
<br />
=== Gentoo ===<br />
http://packages.gentoo.org/package/www-misc/profile-sync-daemon<br />
=== Ubuntu ===<br />
To add the PPA (personal package archive) to your Ubuntu (packages available for Lucid and newer) system, and to install psd:<br />
<br />
$ sudo add-apt-repository ppa:graysky/utils<br />
$ sudo apt-get update<br />
$ sudo apt-get install profile-sync-daemon<br />
<br />
== External Links Mentioning PSD ==<br />
*http://www.webupd8.org/2013/02/keep-your-browser-profiles-in-tmpfs-ram.html<br />
*http://bernaerts.dyndns.org/linux/250-ubuntu-tweaks-ssd</div>Panth0rhttps://wiki.archlinux.org/index.php?title=Lenovo_ThinkPad_X60_Tablet&diff=232085Lenovo ThinkPad X60 Tablet2012-10-28T05:55:56Z<p>Panth0r: /* WiFi */</p>
<hr />
<div>[[Category:Lenovo]]<br />
{{Article summary start}}<br />
{{Article summary text|Installation instructions for the Lenovo Thinkpad X60 Tablet}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|IBM ThinkPad X60}}<br />
{{Article summary wiki|IBM ThinkPad X60s}}<br />
{{Article summary end}}<br />
<br />
= Pre installation notes =<br />
Remember to back up the restore partition if you plan to restore to Microsoft Windows, or even leave it.<br />
<br />
As the laptop does not have a built-in CD/DVD drive you might have to use a USB stick or similar device. Look in this how to [[Install_from_USB_stick | install from USB stick]] for more information.<br />
<br />
Follow the [[Official Arch Linux Install Guide]]<br />
<br />
= Accessing the recovery partition with GRUB =<br />
Edit your '''/boot/grub/menu.lst''' file and add the following:<br />
# booting "Rescue and Recovery" partition from Lenovo<br />
title Thinkpad Maintenance<br />
unhide (hd0,0)<br />
rootnoverify (hd0,0)<br />
chainloader +1<br />
<br />
= Configuration =<br />
== Sound ==<br />
Sound works out of the box. All modules are loaded upon boot. <br />
<br />
Refer to following guides to set it up:<br />
<br />
[[OSS]]<br />
<br />
[[ALSA]]<br />
<br />
[[PulseAudio]]<br />
<br />
There might be others.<br />
Personally I use ALSA and Pulseaudio, but some say that OSS has better sound, try for yourself.<br />
<br />
== Ethernet ==<br />
Works out of the box.<br />
<br />
Modules used:<br />
*e1000e<br />
<br />
== WiFi ==<br />
Works out of the box, no extra firmware needs to be installed.<br />
# pacman -S wireless_tools<br />
Then please refer to [https://wiki.archlinux.org/index.php/Wireless#Part_II:_Wireless_management Wireless management]<br />
<br />
== Firewire ==<br />
Works out of the box.<br />
<br />
== USB ==<br />
Works out of the box.<br />
<br />
Following modules are used:<br />
<br />
*uhci_hcd<br />
*ehci_hcd<br />
*usbhid<br />
<br />
== Bluetooth ==<br />
Works out of the box.<br />
<br />
Following modules are used:<br />
<br />
*bluetooth<br />
*btusb<br />
*l2cap<br />
*rfcomm<br />
*hci_usb<br />
*ehci-hcd<br />
*uhci-hcd<br />
<br />
== SD-card reader ==<br />
Works out of the box.<br />
<br />
Following modules are used:<br />
<br />
*usb-storage<br />
*sdhci<br />
*sdhci_pci<br />
<br />
== Graphics card ==<br />
Works install '''xf86-video-intel'''<br />
<br />
pacman -S xf86-video-intel<br />
<br />
Configure xorg with:<br />
<br />
X -configure<br />
<br />
You can get my Xorg.conf here [http://ostebaronen.dk/downloads/xorg.conf Lenovo Thinkpad X60 Tablet SXGA+ xorg.conf]<br />
<br />
== Stylus ==<br />
You can get the stylus to work by installing '''linuxwacom'''. Find the latest in [https://aur.archlinux.org/packages.php?ID=16912 AUR]<br />
<br />
Add the following sections to your '''xorg.conf''' to make it work:<br />
<br />
Section "ServerLayout"<br />
...<br />
InputDevice "Cursor" "SendCoreEvents"<br />
InputDevice "Stylus" "SendCoreEvents"<br />
InputDevice "Eraser" "SendCoreEvents"<br />
...<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Cursor"<br />
Driver "wacom"<br />
Option "Device" "/dev/ttyS0"<br />
Option "Type" "cursor"<br />
Option "ForceDevice" "ISDV4"<br />
Option "KeepShape" "on"<br />
Option "Mode" "Absolute"<br />
Option "BottomY" "18432"<br />
Option "BottomX" "24576"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Stylus"<br />
Driver "wacom"<br />
Option "Device" "/dev/ttyS0"<br />
Option "Type" "stylus"<br />
Option "ForceDevice" "ISDV4"<br />
Option "KeepShape" "on"<br />
Option "TPCButton" "off"<br />
Option "BottomY" "18432"<br />
Option "BottomX" "24576"<br />
Option "Mode" "Absolute"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Eraser"<br />
Driver "wacom"<br />
Option "Device" "/dev/ttyS0"<br />
Option "Type" "eraser"<br />
Option "ForceDevice" "ISDV4"<br />
Option "KeepShape" "on"<br />
Option "BottomY" "18432"<br />
Option "BottomX" "24576"<br />
EndSection<br />
<br />
Also add the following if '''X -configure''' does not do it:<br />
<br />
Section "Monitor"<br />
DisplaySize 245 18<br />
...<br />
EndSection<br />
<br />
== Automatic rotation ==<br />
Refer to [[Acpi_hotkeys | Acpi Hotkeys]] on how to edit '''handler.sh'''.<br />
<br />
I've written a set of small scripts to help rotating the screen if the screen is swiveled down, up and when the rotate button is pressed.<br />
<br />
Automatic rotation needs acpi daemon in order to work. Install it:<br />
pacman -S acpid<br />
<br />
Now start the daemon and put it in your '''/etc/rc.conf''' under daemons.<br />
/etc/rc.d/acpid start<br />
<br />
Now you should be able to grab events with '''acpi_listen'''. My tablet creates the following events when swivelling it down:<br />
ibm/hotkey HKEY 00000080 00005009<br />
When swiveling up:<br />
ibm/hotkey HKEY 00000080 0000500a<br />
<br />
Now we can edit our '''/etc/acpi/handler.sh''' to grab these events when they occur.<br />
Add the following under '''case "$1"''' somewhere:<br />
ibm/hotkey)<br />
case "$2" in<br />
HKEY)<br />
case "$4" in<br />
00005009)<br />
#Swiveling down<br />
/bin/sh /etc/acpi/actions/swivel-down<br />
;;<br />
0000500a)<br />
#Swiveling up<br />
/bin/sh /etc/acpi/actions/swivel-up<br />
;;<br />
esac<br />
;;<br />
esac<br />
;;<br />
<br />
If you're using [[HAL]] for configuring your Xorg you'll need to get the device names used by xsetwacom. If you're using the '''xorg.conf''' from above you can leave the device names as they are.<br />
<br />
xsetwacom --list dev<br />
<br />
Will give you something like this:<br />
<br />
PnP Device (WACf008) eraser ERASER <br />
PnP Device (WACf008) touch TOUCH <br />
PnP Device (WACf008) STYLUS<br />
<br />
You'll just need to cut off the all caps identifier at the end. So the device name for the eraser in the example above would be:<br />
<br />
PnP Device (WACf008) eraser<br />
<br />
Now create the files specified in '''handler.sh'''.<br />
<br />
'''/etc/acpi/actions/swivel-down:'''<br />
#!/bin/bash<br />
/usr/bin/xrandr -o inverted<br />
xsetwacom set "Stylus" Rotate half<br />
xsetwacom set "Cursor" Rotate half<br />
xsetwacom set "Eraser" Rotate half<br />
<br />
'''/etc/acpi/actions/swivel-up:'''<br />
#!/bin/bash<br />
/usr/bin/xrandr -o normal<br />
xsetwacom set "Stylus" Rotate none<br />
xsetwacom set "Cursor" Rotate none<br />
xsetwacom set "Eraser" Rotate none<br />
<br />
Make them executable:<br />
chmod +x /etc/acpi/actions/swivel*<br />
<br />
Now we only need to set up the rotate button, which can be done by finding out what X event it creates when it is pressed. You can use '''xev''' to find out:<br />
xev | grep keycode<br />
<br />
Now press the rotate button a couple of times and it should give you a keycode. The one for mine was 199.<br />
state 0x0, keycode 199 (keysym 0x0, NoSymbol), same_screen YES<br />
<br />
Create a file in your home directory called '''.Xmodmap''', this file should contain:<br />
keycode 199 = F19<br />
<br />
Before we go any further we have to put the following rotate script somewhere, it could be in your home directory, or maybe in '''/usr/local/bin/''':<br />
#!/bin/bash<br />
# This is a script that toggles rotation of the screen through xrandr,<br />
# and also toggles rotation of the stylus, eraser and cursor through xsetwacom<br />
<br />
# Check orientation<br />
orientation=`xrandr --verbose -q | grep LVDS | awk '{print $5}'`<br />
# Rotate the screen and stylus, eraser and cursor, according to your preferences.<br />
if [ "$orientation" = "normal" ]; then<br />
/usr/bin/xrandr -o right<br />
xsetwacom set "Stylus" Rotate cw<br />
xsetwacom set "Cursor" Rotate cw<br />
xsetwacom set "Eraser" Rotate cw<br />
elif [ "$orientation" = "inverted" ]; then<br />
/usr/bin/xrandr -o left<br />
xsetwacom set "Stylus" Rotate ccw<br />
xsetwacom set "Cursor" Rotate ccw<br />
xsetwacom set "Eraser" Rotate ccw<br />
elif [ "$orientation" = "right" ]; then<br />
/usr/bin/xrandr -o inverted<br />
xsetwacom set "Stylus" Rotate half<br />
xsetwacom set "Cursor" Rotate half<br />
xsetwacom set "Eraser" Rotate half<br />
elif [ "$orientation" = "left" ]; then<br />
/usr/bin/xrandr -o normal<br />
xsetwacom set "Stylus" Rotate none<br />
xsetwacom set "Cursor" Rotate none<br />
xsetwacom set "Eraser" Rotate none<br />
fi<br />
<br />
Make the file executable with '''chmod +x''' and create a '''.xbindkeysrc''' file in your home directory, with the following content:<br />
"/path/to/rotatescript"<br />
F19<br />
<br />
Run: <br />
xmodmap ~/.Xmodmap<br />
xbindkeys<br />
/etc/rc.d/acpid restart<br />
<br />
Now rotate button and when you swivel the screen down and up it should rotate.<br />
<br />
{{Box Note|You have to run:<br />
xmodmap ~/.Xmodmap<br />
xbindkeys<br />
Every time you start Xorg.}}<br />
<br />
You might also want to take a look at [http://luke.no-ip.org/x60tablet/examples/rotate this rotate script] written by Luke<br />
<br />
== Trackpoint ==<br />
Works, if you want to scroll while holding the middle mouse button down you can add the following to an .fdi file:<br />
<br />
/etc/hal/fdi/policy/11-trackpoint-mw.fdi:<br />
<match key="info.product" contains="TrackPoint"><br />
<merge key="input.x11_options.EmulateWheel" type="string">true</merge><br />
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge><br />
<merge key="input.x11_options.ZAxisMapping" type="string">4 5</merge><br />
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge><br />
</match<br />
<br />
What it does is that it sets emulates wheel on button two, which is middle button and maps in what directions it will emulate the scroll wheel, it will at the same time emulate 3 mouse buttons.<br />
<br />
You can read more about the new [[Xorg_input_hotplugging | Xorg input hotplugging here]]<br />
<br />
== ThinkFinger ==<br />
Works, read [[ThinkFinger]] for reference and examples.<br />
<br />
== Backlight ==<br />
To make backlight buttons turn the backlight turn up and down you can do the following.<br />
<br />
First edit '''/etc/modprobe.d/modprobe.conf''' to make the '''thinkpad_acpi''' module load with some special options:<br />
<br />
'''/etc/modprobe.d/modprobe.conf:'''<br />
options thinkpad_acpi brightness_enable=1 hotkey=enable,0xffffff<br />
<br />
Restart acpid and grab the events they key combinations make with '''acpi_listen''':<br />
/etc/rc.d/acpid restart<br />
acpi_listen<br />
<br />
The backlight down button on my machine creates:<br />
ibm/hotkey HKEY 00000080 00001010<br />
backlight up button creates:<br />
ibm/hotkey HKEY 00000080 00001011<br />
<br />
Edit '''/etc/acpi/handler.sh:'''<br />
ibm/hotkey)<br />
case "$2" in<br />
HKEY)<br />
case "$4" in<br />
00001010)<br />
# backlight down<br />
# Check current state<br />
typeset -i state=`cat /sys/class/backlight/thinkpad_screen/brightness`<br />
# Subtract one from the current state and echo it to the file<br />
down=$((state-=1))<br />
echo "$down" > /sys/class/backlight/thinkpad_screen/brightness<br />
;;<br />
00001011)<br />
# backlight up<br />
# Check current state<br />
typeset -i state=`cat /sys/class/backlight/thinkpad_screen/brightness`<br />
# Add one to the current state and echo it to the file<br />
state+=1<br />
echo "$state" > /sys/class/backlight/thinkpad_screen/brightness<br />
;;<br />
<br />
Restart acpid:<br />
/etc/rc.d/acpid restart<br />
<br />
= Hardware info =<br />
== Specifications ==<br />
Specifications can be found here [http://www.thinkwiki.org/wiki/Category:X60_Tablet on ThinkWiki]<br />
== lspci ==<br />
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)<br />
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)<br />
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)<br />
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)<br />
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)<br />
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)<br />
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)<br />
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)<br />
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)<br />
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b4)<br />
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 09)<br />
15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 18)<br />
<br />
== lsusb ==<br />
Bus 005 Device 003: ID 0a5c:2110 Broadcom Corp. <br />
Bus 005 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader<br />
Bus 005 Device 001: ID 1d6b:0001 <br />
Bus 004 Device 001: ID 1d6b:0001 <br />
Bus 003 Device 001: ID 1d6b:0001 <br />
Bus 002 Device 001: ID 1d6b:0001 <br />
Bus 001 Device 001: ID 1d6b:0002</div>Panth0rhttps://wiki.archlinux.org/index.php?title=Netbeans&diff=225155Netbeans2012-09-26T04:24:04Z<p>Panth0r: /* Netbeans starts with a completely grey window */ wooo, happy to get netbeans working after these two unusual headaches!</p>
<hr />
<div>[[Category:Development]]<br />
'''Netbeans''' is an integrated development environment (IDE) for developing with Java, JavaScript, PHP, Python, Ruby, Groovy, C, C++, Scala, Clojure, and other languages.<br />
<br />
From [[Wikipedia:Netbeans|Wikipedia article]]:<br />
:"''The NetBeans IDE is written in Java and can run anywhere a compatible JVM is installed, including Windows, Mac OS, Linux, and Solaris. A JDK is required for Java development functionality, but is not required for development in other programming languages.''"<br />
<br />
== Tips and tricks ==<br />
{{Note|The global netbeans.conf {{Ic|/usr/share/netbeans/etc/netbeans.conf}} will be overwritten during updates. To keep changes add them to your local netbeans.conf {{ic|~/.netbeans/<ver>/etc/netbeans.conf}} (you will need to create the etc dir and the .conf file).}}<br />
*Settings in local version of netbeans.conf override the same settings in the global copy of the file.<br />
*Command-line options override settings in either of the configuration files.<br />
=== Font antialiasing in Netbeans ===<br />
==== Netbeans Specifically ====<br />
Add {{Ic|-J-Dswing.aatext&#61;TRUE -J-Dawt.useSystemAAFontSettings&#61;on}} to the 'netbeans_default_options' line of your netbeans.conf file.<br />
<br />
==== Java Generally ====<br />
See [[Java#Better font rendering ]].<br />
<br />
=== GTK look and feel ===<br />
To change Netbeans look and feel to GTK add switch {{Ic|--laf com.sun.java.swing.plaf.gtk.GTKLookAndFeel}} to IDE command line by appending it to ‘netbeans_default_options’ section of {{Ic|/usr/share/netbeans/etc/netbeans.conf}} or editing ''.desktop'' file with which you launch Netbeans.<br />
<br />
== Troubleshooting ==<br />
=== OpenJDK vs Sun's JDK ===<br />
Netbeans 7.0-1 will not ALWAYS work with OpenJDK. Some reported issues are:<br />
* Starting - In some cases, netbeans will not start.<br />
* Installation - The .sh script provided by netbeans will not launch wizard (any proofs?).<br />
* JavaFX module does not work (see {{Bug|29843}}).<br />
<br />
=== Glassfish server - Can`t download Glassfish server I/O Exception ===<br />
If you are trying add new Glassfish server, you can`t download the server. Netbeans returns<br />
I/O Exception: http://java.net/download/glassgish/3.0.1/release/glassfish-3.0.1-ml.zip<br />
<br />
Solution is:<br />
* Download GlassFish Server Open Source Edition manualy from official site, actual link is http://download.java.net/glassfish/3.0.1/release/glassfish-3.0.1-ml.zip<br />
* Extract from zip to any location<br />
<br />
=== Netbeans doesn't start after its first start ===<br />
If you receive a message like this when executing from terminal:<br />
{{hc|# netbeans -h|<br />
Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/libsplashscreen.so: libgif.so.4: cannot open shared object file: No such file or directory<br />
}}<br />
<br />
You have two options:<br />
* You can start Netbeans using the --nosplash option:<br />
# netbeans --nosplash<br />
* Or, install the missing library ({{Pkg|libungif}}), then starting Netbeans as usual will work.<br />
<br />
[https://bbs.archlinux.org/viewtopic.php?id=118930 Arch forum thread]<br />
<br />
=== Netbeans starts with a completely grey window ===<br />
{{Out of date|most likely fixed in current versions of OpenJDK}}<br />
See [[Java#Impersonate Another Window Manager]]<br />
<br />
This may not be quite 100% out of date; the problem occurred while using NetBeans 7.2, OpenJDK 7.u7_2.3.2-2, "$ java -version" reporting 1.7.0_07. The following is robbed from Awesome's wiki (although I experienced the problem using Xmonad), which fixed my all-grey window problem:<br />
<br />
<pre>$ _JAVA_AWT_WM_NONREPARENTING=1; export _JAVA_AWT_WM_NONREPARENTING</pre></div>Panth0rhttps://wiki.archlinux.org/index.php?title=Talk:Yaourt&diff=171520Talk:Yaourt2011-11-29T06:54:02Z<p>Panth0r: /* tmpfs usage */ new section</p>
<hr />
<div>==Regarding general opinion on yaourt==<br />
A great deal of people still ask for yaourt support, even though more recent helpers have less issues that outright break installing from AUR, and less problems that degrade performance. Maybe the article should reflect what is actually happening; people are pointing towards others like packer and bauerbill. [[User:Dres|Dres]] 23:13, 26 January 2010 (EST)<br />
<br />
* I wasn't the person who removed your comment about Yaourt being unmaintained, but the most recent changelog is on 17 Aur 2009. That seems pretty recent to me.<br><br>I don't think it's a good idea to add information about other AUR helpers on the Yaourt page. The Yaourt page should only give information about Yaourt. If we add information about Packer or Bauerbill then it will just look like we are advertising another AUR helper. :P<br><br>It's strange how new Arch Linux users seem to just "know" that they should use Yaourt. It happened to me: I have been using Arch Linux for less than a year, and when I wanted to start using the AUR, I used Yaourt. The funny thing is, I don't even remember where I learned that I should use Yaourt.<br><br>I think as people start moving away from suggesting Yaourt in the wiki documentation and in the Arch Linux forums, people will begin to use other AUR helpers. The best thing is when people use the best program for the job they want to do, even if it is Yaourt. ;) [[User:drcouzelis|drcouzelis]] 17:17, 12 March 2010 (EST)<br />
<br />
== Prefer yaourt-git ? ==<br />
<br />
I'm kinda intrigued by this line, I am using the "normal" yaourt from the AUR and do not seems to have any trouble, what kind of features are broken ? Is there a risk for my system if I keep using this "broken" yaourt ?<br />
<br />
I can see that the last edit was late january 2010, almost a century in computing :) Is it still true ?<br />
<br />
:I've not seen any problems either, nor has anybody else that I know use Yaourt daily. However, on the AUR page, there are comments about it having problems with the latest AUR, though the comments don't go into detail. Since the last release was in May 2009, if the bug was in place in january, that still hasn't changed. It probably would be good to find the exact problem, and say, "Yaourt release has broken feature foo-bar, use Yaourt git if you need this..." [[User:Pierre Monteux|Pierre Monteux]] 10:37, 13 March 2010 (EST)<br />
<br />
==<s>Deal with package replacement?</s>==<br />
The article states twice that yaourt shouldn't be used to manage official packages because of issues with replacements:<br />
<br />
"Please bear in mind that yaourt does not presently deal with package replacement. Using it to update the system is [https://bbs.archlinux.org/viewtopic.php?id=118399 not recommended]."<br />
<br />
"You should use pacman for anything not related to the [[AUR]], because yaourt may not fully take care of necessarily steps such as replaces."<br />
<br />
However, AFAIK that is indeed a problem of pacman itself ({{Bug|24904}}), and yaourt suffers of it only because it's a <u>wrapper</u> for pacman, which means that it uses the currently installed version of pacman for managing packages, only adding and coloring some output, and providing the ability to download and build AUR packages (but not installing the built packages, which again is done with a pacman call). This is proved also by the fact that in /etc/yaourtrc you have to specify the command to use to manage packages:<br />
<br />
# Command<br />
PACMAN=pacman #could be "pacman-color" or even something else<br />
#DIFFEDITCMD="vimdiff"<br />
<br />
I would remove those statements, as I think they do not belong here. -- [[User:Kynikos|Kynikos]] 07:20, 4 July 2011 (EDT)<br />
:Statements have been removed: [https://wiki.archlinux.org/index.php?title=Yaourt&action=historysubmit&diff=167537&oldid=167369] and [https://wiki.archlinux.org/index.php?title=Yaourt&diff=next&oldid=167539]. Closing. -- [[User:Kynikos|Kynikos]] 08:21, 6 November 2011 (EST)<br />
<br />
== tmpfs usage ==<br />
<br />
As I understand, Yaourt uses /tmp when building from the AUR; however, I've run into one particularily large package (planeshift) that requires more than what's available in /tmp (with a GB of memory, my /tmp is just over 500 MB).<br />
<br />
planeshift required about 2.5GB (at least on my system) allocated to /tmp to install; so I had to edit /etc/fstab and increase the amount allocated to /tmp (I increased it to 4 GB). After doing so, I rebooted, installed my package, rebooted again, reset fstab to its original values and finally rebooted a third time (sorry if all that rebooting is noob).<br />
<br />
I think it'd be nice for this to be documented more clearly as this may (and is likely to complete beginners) seem to prevent the installation of bulky packages via Yaourt (well, any package whose download/build takes up > 1/2 of their memory by default.<br />
<br />
[[User:Panth0r|Panth0r]] 01:54, 29 November 2011 (EST)</div>Panth0rhttps://wiki.archlinux.org/index.php?title=Google_Earth&diff=171404Google Earth2011-11-28T05:01:28Z<p>Panth0r: /* Related */ Added Yaourt, as it is mentioned earlier in the article but a link is lacking</p>
<hr />
<div>{{i18n|Google Earth}}<br />
[[Category:Internet Applications (English)]]<br />
<br />
''[http://earth.google.com/ Google Earth] lets you fly anywhere on Earth to view satellite imagery, maps, terrain, 3D buildings, from galaxies in outer space to the canyons of the ocean. You can explore rich geographical content, save your toured places, and share with others.''<br />
<br />
== Installation ==<br />
<br />
Google Earth is present in the [[AUR]] as an unsupported [[PKGBUILD]]. Three-dimensional hardware acceleration is required; see [[Xorg]] for details.<br />
<br />
=== To install the package with yaourt: ===<br />
<br />
yaourt -S google-earth<br />
<br />
=== Or download the Tarball from the AUR:===<br />
<br />
* {{Package AUR|google-earth}} (i686) and (x86_64)<br />
<br />
Extract into a suitable build directory, compile, and install the package:<br />
<br />
tar -zxvf google-earth.tar.gz<br />
cd google-earth<br />
makepkg -cs<br />
pacman -U *.pkg.tar.gz<br />
<br />
== Related ==<br />
<br />
# [[ABS]]<br />
# [[makepkg]]<br />
# [[pacman]]<br />
# [[Yaourt]]</div>Panth0r