https://wiki.archlinux.org/api.php?action=feedcontributions&user=Potamota&feedformat=atom
ArchWiki - User contributions [en]
2024-03-29T09:07:21Z
User contributions
MediaWiki 1.41.0
https://wiki.archlinux.org/index.php?title=GNOME_2&diff=70291
GNOME 2
2009-06-10T19:16:32Z
<p>Potamota: </p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|GNOME}}<br />
{{i18n_entry|Česky|GNOME (Česky)}}<br />
{{i18n_entry|Español|GNOME (Español)}}<br />
{{i18n_entry|Italiano|GNOME (Italiano)}}<br />
{{i18n_entry|Nederlands|GNOME(Nederlands)}}<br />
{{i18n_entry|Português do Brasil|GNOME (pt_br)}}<br />
{{i18n_entry|Русский|GNOME (Русский)}}<br />
{{i18n_entry|Türkçe|GNOME (Türkçe)}}<br />
{{i18n_entry|简体中文|GNOME (简体中文)}}<br />
{{i18n_entry|繁體中文|GNOME (繁體中文)}}<br />
{{i18n_entry|ไทย|GNOME (ไทย)}}<br />
{{i18n_links_end}}<br />
<br />
==What is GNOME?==<br />
<br />
The [http://www.gnome.org/ GNOME] project provides two things: The GNOME desktop environment, an intuitive and attractive desktop for end-users, and the GNOME development platform, an extensive framework for building applications that integrate into the rest of the desktop.<br />
<br />
==How to install the GNOME Desktop==<br />
<br />
Before installing GNOME Desktop make sure you have updated pacman itself by: <br />
# pacman -Syu <br />
# pacman -Syy<br />
<br />
This will bypass the error which is encountered while installing gnome-media package that depends on gstreamer0.10-gconf but its not there in the package list with the pacman out of the box version. An update is necessary prior to installation of GNOME.<br />
<br />
Install the base GNOME Desktop by: <br />
# pacman -S gnome<br />
<br />
This is a metapackage; which is a group of packages. An option will be given to install all or some of the packages in this group. All the packages can safely be installed and is highly recommended, but here is a list of some that may not be needed.<br />
<br />
*'''Epiphany''' is a web browser that comes with GNOME. If you are planning on using a different browser e.g. Firefox then this package is not needed. It is recommended that you at least try Epiphany as it is an excellent browser that unfortunately gets over shadowed by Firefox.<br />
*'''Evolution''' is a Personal Information Management PIM (e-mail, calendar, contacts, etc.) application for GNOME. If you are planning on using a different PIM; e.g. Thunderbird, or a web PIM like a google or yahoo account then you have no need for this package.<br />
*'''gnome-backgrounds''' is a collection of desktop backgrounds (wallpapers) that the GNOME community has selected for you to use. If you already know what you will be using for your background e.g. a picture of you sweetheart, then this package is not needed. <br />
*'''gnome-screensaver''' is a collection of screensavers for the GNOME desktop. If you will not be using a screensaver, i.e. using the GNOME power manager to shut the monitor off when not in use then this package is not needed.<br />
*'''gnome-themes''' is a collection of desktop themes. If you will be using a specific theme that you will be downloading separately then this package is not needed.<br />
*'''gnome2-user-docs''' and '''yelp''' are the help documents and help document reader for the GNOME desktop. If you are the kind of person that does not read documentation or you would rather use the large help documents known as google, then there would be no need to install these packages. This is not recommended. (Ironically, if you are the kind of person that does not read documentation then chances are you won’t be reading this.) <br />
*'''libgail-gnome''' is a GNOME accessibility implementation library used by the screen reader Orca. If you and everyone else that will be using this desktop have good vision then this package is not needed.<br />
<br />
Install the rest of the GNOME Desktop (highly recommended, see [[Gnome Tips]])by:<br />
# pacman -S gnome-extra<br />
<br />
Like before this is a metapackage, and it is recommended to install all packages in this group, but here is a list of some that may not be needed.<br />
<br />
*'''Alacarte''' is an editor for the gnome-menu, if you're planning on using the menu it's recommended to use this package, though it can be done manually.<br />
*'''Bug-Buddy''' reports bugs, if you don't want to report bugs this package is not needed.<br />
*'''Cheese''' uses your webcam to take photos and videos; if you don’t have a webcam then this package is not needed.<br />
*'''Dasher''' is a text entry application that uses the pointer instead of a keyboard. If you and everyone that will be using this desktop can use a keyboard then this package is not needed.<br />
*'''Deskbar-applet''' is an all-in-one search bar for the GNOME desktop. If you don't need a desktop search then this package is not needed.<br />
*'''Ekiga''' is a VOIP/Videoconferencing application. If you have no need for VOIP or use a different application like Skype, then this package is not needed.<br />
*'''EOG''' views almost all types of images, you may choose to take your own image viewer.<br />
*'''Evince''' is a simple document (e.g. pdf) viewer. If you are planning on using a different viewer e.g. Adobe Reader then this package is not needed.<br />
*'''Evolution-exchange''' is a plug in for Evolution that allows Evolution to connect to Exchange. If you don't use Exchange or Evolution then you have no need for this package. <br />
*'''Evolution-webcal''' is a web calendar plug in for Evolution. If you don't use Evolution then you have no need for this package.<br />
*'''Fast-user-switch-applet''' is an applet that allows the switching of users without going through a log out, and log in screen, i.e. you can switch users fast. If there is only one user on your computer or you like seeing the log in screen then you have no need for this package.<br />
*'''File-Roller''' is a gui archive manager which works as winzip/winrar. If you prefer to (un)pack archives through the commandline this package is not needed.<br />
*'''Gcalctool''' , a default calculator application with different views.<br />
*'''Gconf-editor''' , the backend editor for all gnome settings.<br />
*'''Gdm''' facilitates the starting of GNOME at boot up. If you like your computer to boot into a nice traditional command line and you will start GNOME only when you need it, then this package is not for you.<br />
*'''Gedit''' is a GUI based text editor. If you plan on using a different text editor – as most people’s devotion to their favorite text editor is religious you more than likely have an example in mind – then you have no need to install this package. (If you are devoted to gedit I apologize for suggesting it not be installed; I only did so for completeness.)<br />
*'''Gnome-audio''' is a collection of sounds for events in gnome. If you've your own sounds, don't want sounds or have no sound at all then this package is not needed.<br />
*'''Gnome-games''' and '''gnome-games-extra-data''' is a collection of simple desktop games; e.g. Nibbles, Sudoku, etc. If you feel that childish games are a waste of your time, hard drive space and bandwidth then this package is not for you.<br />
*'''Gnome-mag''' is a screen magnifier for people with poor vision. If you and everyone that will be using this desktop have good vision then you have no need for this package.<br />
*'''Gnome-nettool''' and '''gnome-netstatus''' are collections of GUI based networking tools. If you do all your networking stuff from the command line then this package is not for you.<br />
*'''Gnome-power-manager''' keeps track of battery status, and other power tracking tools. Only laptop users should use this package.<br />
*'''Gnome-system-monitor''' , an application that displays computer hardware information, and system resource usage.<br />
*'''Gnome-Terminal''' a gui terminal, if you prefer your own terminal application like xterm or aterm then this package is not needed.<br />
*'''Gnome-Utils''' is a collection of utilities for gnome, containing a file logger, logviewer, searchtool, dictionary, floppy drive support and a app for taking screenshots. It's recommended to take this package.<br />
*'''Gnome-Volume-Manager''' Automaticly mounts newly connected HD's (including usb drives) for you. If you prefer to mount drives through the commandline this package is not needed.<br />
*'''Gucharmap''' lets you view unicode characters.<br />
*'''Gok''' is the GNOME on screen keyboard. If you and every one using this desktop plan on using a standard keyboard for all your keyboard needs then don't install this package.<br />
*'''Hamster-applet''' is a time tracking applet. Please visited its web site [http://projecthamster.wordpress.com/ Project Hamster] to decide if you should install it or not. I am afraid that describing this applet in one or two sentences does not do the project justice.<br />
*'''Mousetweaks''' is accessibility software for users that have limited control of a mouse (e.g. can manipulate only one button). If you and every one that will be using this desktop have full control of the mouse then there is no need to install this package.<br />
*'''Nautilus-cd-burner''' allows the burning of files to CDs by dragging-and-dropping in the GNOME file manager, Nautilus. The only reason not to install this package is if you don’t have a CD burner on your computer. <br />
*'''Orca''' is a screen reader for the GNOME desktop to help users with limited vision. If you and everyone else that will be using this desktop have good vision then this package is not needed.<br />
*'''Seahorse''' and '''Seahorse-plugins''' are packages for de/encrypting information. Don't take this package unless you know what you're going to use it for.<br />
*'''Sound-juicer''' is a CD ripping application for Gnome. If you are planning on using a different application for ripping CD e.g. Banshee or don’t have a CD drive then you have no need to install this package.<br />
*'''Tomboy''' is a simple desktop note taking application. If you don’t take notes or simply use pen and paper for your simple note taking needs then you have no need for this package.<br />
*'''Totem''' is the official movie player of the GNOME desktop. If you plan on using a different movie player e.g. VLC then you have no need for this package.<br />
*'''Vinagre''' is a VNC client for the GNOME desktop. If you have no need for a VNC client then you have no need for this package.<br />
*'''Vino''' is a remote desktop server for the GNOME desktop. You can use it to share your Gnome session desktop with other users. If you have no need for a remote desktop server then you have no need for this package.<br />
*'''Zenity''' a tool that allows you to display GTK dialog boxes in commandline and shell scripts.<br />
<br />
You may have noticed the Gnome admin tools (''System &rarr; Administration'') are not included in the extra package. You will need the gnome-system-tools package which is installed in a discrete step. As mentioned above, this and other helpful info can be found on the [[Gnome Tips]]) wiki page which you should read through:<br />
<br />
# pacman -Sy gnome-system-tools<br />
<br />
==Daemons and Modules Needed by the GNOME Desktop==<br />
The GNOME desktop requires two daemons, '''FAM''' and '''HAL''' for proper operation. The File Alteration Monitor '''FAM''' daemon allows real-time representation of file alterations; i.e. give the GUI instant access to recently installed programs or changes in the file system. The Hardware Abstraction Layer '''HAL''' daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI.<br />
<br />
To start the HAL and FAM daemons:<br />
# /etc/rc.d/hal start<br />
# /etc/rc.d/fam start<br />
Or add these daemons to the '''DAEMONS''' array in {{Filename|/etc/[[rc.conf]]}} so they will start on boot up, e.g.:<br />
#<br />
# /etc/rc.conf - Main Configuration for Arch Linux<br />
#<br />
.<br />
.<br />
# -----------------------------------------------------------------------<br />
# DAEMONS<br />
# -----------------------------------------------------------------------<br />
#<br />
# Daemons to start at boot-up (in this order)<br />
# - prefix a daemon with a ! to disable it<br />
# - prefix a daemon with a @ to start it up in the background<br />
#<br />
.<br />
.<br />
DAEMONS=(syslog-ng network crond '''hal''' '''fam''')<br />
<br />
{{Note|You may instead want to remove FAM and install gamin, which doesn't require a system daemon to be running. }}<br />
<br />
'''GVFS''' allows the mounting of virtual file systems (e.g. file systems over FTP or SMB) to be used by other applications, including the GNOME file manager Nautilus. This is done with the use of '''FUSE''': a user space virtual file system layer kernel module.<br />
<br />
To load the FUSE kernel module:<br />
<br />
# modprobe fuse<br />
<br />
Or add the module to the '''MODULES''' array in {{Filename|/etc/rc.conf}} so they will load at boot up, e.g.:<br />
#<br />
# /etc/rc.conf - Main Configuration for Arch Linux<br />
#<br />
.<br />
.<br />
# -----------------------------------------------------------------------<br />
# HARDWARE<br />
# -----------------------------------------------------------------------<br />
#<br />
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed<br />
# MOD_BLACKLIST: Prevent udev from loading these modules<br />
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.<br />
#<br />
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.<br />
#<br />
MOD_AUTOLOAD="yes"<br />
#MOD_BLACKLIST=() #deprecated<br />
MODULES=('''fuse''' usblp)<br />
.<br />
.<br />
{{Note|FUSE is a kernel module not a daemon and does not go in the same array as HAL and FAM.}}<br />
<br />
==Running the GNOME Desktop==<br />
<br />
To start GNOME from the console, run:<br />
$ gnome-session<br />
<br />
If you add the following to your {{Filename|~/.xinitrc}} file (and make sure it is the only line that starts with "exec"):<br />
exec gnome-session<br />
<br />
or this if you have problem with automount:<br />
exec ck-launch-session gnome-session<br />
<br />
To make it a global setting which has effect on all users in stead of only one, in stead of {{Filename|~/.xinitrc}} add the line to the file {{Filename|/etc/X11/xinit/xinitrc}}:<br />
exec gnome-session<br />
<br />
Note: Only needed for gnome 2.14, gnome 2.16 and up do this for you:<br />
exec dbus-launch --exit-with-session /opt/gnome/bin/gnome-session<br />
<br />
GNOME will start when you enter the following command.<br />
$ startx<br />
<br />
==GDM (GNOME Display Manager)==<br />
<br />
If you want a graphical login, you will need to install [http://www.gnome.org/projects/gdm/ GDM] (which is also part of gnome-extra). To do so, type the following at a command prompt:<br />
# pacman -S gdm<br />
<br />
To make the graphical login the default method of logging into the system, add gdm to your list of daemons in {{Filename|/etc/rc.conf}}.<br />
<br />
If you are used to using the {{Filename|~/.xinitrc}} file to pass arguments to the X server when it is started, such as '''xmodmap''' or '''xsetroot''', you should note that you can add the same commands to the {{Filename|~/.xprofile}} file. My .xprofile looks like this:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
#<br />
# ~/.xprofile<br />
#<br />
# Executed by gdm at login<br />
#<br />
<br />
xmodmap -e "pointer = 1 2 3 6 7 4 5" #set mouse buttons up correctly<br />
xsetroot -solid black #sets the background to black<br />
</pre><br />
<br />
You can configure GDM (for changing default theme for example) in ''System &rarr; Administration &rarr; Login Window''. Or you can use this command (as root):<br />
# gdmsetup <br />
<br />
Note that with version 1.6.1 of xorg-server, {{Keypress|Ctrl}}+{{Keypress|Alt}}+{{Keypress|Backspace}} will NOT restart gdm anymore. For instructions on re-enabling this behavior, see the [[http://wiki.archlinux.org/index.php/Xorg#Ctrl-Alt-Backspace_doesn.27t_exit_X this section]] of the [[Xorg]] wiki article.<br />
<br />
For more information about Graphical Logins (DMs), see [http://endor.clublinux.org/RHCE-21.html this excellent page].<br />
<br />
==Troubleshooting==<br />
<br />
===Your computer crashes and gnome won't startup anymore.===<br />
<br />
Solution: delete ~/.gnome2/session<br />
<br />
===Panels wouldn't work correctly===<br />
<br />
Sourced from [http://bbs.archlinux.org/viewtopic.php?pid=248399 this forum page]<br />
<br />
Solution: Try with a fresh configuration by moving you old configs out of the way:<br />
for d in .gnome* .gconf*; do mv "$d" "$d.old"; done<br />
<br />
===GDM won't start===<br />
<br />
If you get this message:<br />
''"The greeter application appears to be crashing. Attempting to use a different one"''<br />
<br />
One possible reason is that your /tmp folder has the wrong permissions set. Run:<br />
# chmod 1777 /tmp<br />
<br />
As root and try again.<br />
<br />
===GNOME lags===<br />
<br />
If opening programs in GNOME takes an unusual long time. You may be able to fix this by editing {{Filename|/etc/hosts}} and adding your host name.<br />
# nano /etc/hosts<br />
<br />
Now, you should add the host name you have defined in {{Filename|/etc/rc.conf}} or your network profile if you have one (if you don't know, you probably don't).<br />
<br />
The {{Filename|/etc/hosts}} file usually looks like this:<br />
<br />
#<br />
# /etc/hosts: static lookup table for host names<br />
#<br />
<br />
#<ip-address> <hostname.domain.org> <hostname><br />
127.0.0.1 localhost.localdomain localhost<br />
<br />
# End of file<br />
<br />
Add your host name (in this example the host name "example_hostname" was picked) to the end of the line which starts with "127.0.0.1".<br />
Now it looks like this:<br />
<br />
#<br />
# /etc/hosts: static lookup table for host names<br />
#<br />
<br />
#<ip-address> <hostname.domain.org> <hostname><br />
127.0.0.1 localhost.localdomain localhost example_hostname<br />
<br />
# End of file<br />
<br />
===Screen gets dark while GNOME loading===<br />
<br />
If screen gets dark while GNOME loading, you may correct this problem as following.<br />
<br />
Open a terminal and run:<br />
$ gconf-editor<br />
<br />
Find:<br />
/ &rarr; apps &rarr; gnome-power-manager &rarr; backlight<br />
and change the value of<br />
brightness_ac<br />
from 100 to 0 by clicking on it. After restart the system, the problem should not be occur.<br />
<br />
{{Tip | If the problem will be corrected, the same problem will occur. Change to brightness_ac value from 0 to 100 to solve this problem if it will occur again.}}<br />
<br />
==See also==<br />
* [[Gnome Tips]]<br />
* [[Gnome Menu tweaking]]<br />
* [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]]<br />
* [[Build_order_for_Gnome|Build Order]]<br />
* [[Howto make GTK apps look nice| HOWTO: Make GTK1 apps look nice]]<br />
<br />
==External links==<br />
* [http://www.gnome.org/ The Official Website]<br />
* [http://www.gnome.org/learn/ The Official Documentation]<br />
* [http://gnomehelp.org/ GnomeHelp.org]<br />
* Themes, icons, and backgrounds:<br />
** [http://art.gnome.org/ Gnome Art]<br />
** [http://www.gnome-look.org/ Gnome Look]<br />
* GTK/Gnome programs:<br />
** [http://www.gnomefiles.org/ Gnome Files]<br />
** [http://www.gnome.org/projects/ Gnome Project Listing]</div>
Potamota
https://wiki.archlinux.org/index.php?title=Newcomers_Guide&diff=63862
Newcomers Guide
2009-03-04T06:51:46Z
<p>Potamota: </p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:About Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Article summary start}}<br />
{{Article summary text|Provides a highly detailed, explanatory guide to installing, configuring and using a full-featured Arch Linux system.}}<br />
{{Article summary heading|Available Languages}}<br />
{{i18n_entry|Česky|Průvodce začátečníka (Česky)}}<br />
{{i18n_entry|Dansk|Dansk_Begynderguide}}<br />
{{i18n_entry|简体中文|Arch 新手安装指南 (简体中文)}}<br />
{{i18n_entry|正體中文|Beginner's Guide 新手指南}}<br />
{{i18n_entry|Deutsch|Beginners Guide (Deutsch)}}<br />
{{i18n_entry|English|Beginners Guide}}<br />
{{i18n_entry|Español|Guía para Principiantes (Español)}}<br />
{{i18n_entry|Français|Manuel_du_Débutant_(Français)}}<br />
{{i18n_entry|Italiano|Beginners Guide (Italiano)}}<br />
{{i18n_entry|Lietuviškai|Pradedančiųjų gidas (Lietuviškai)}}<br />
{{i18n_entry|Nederlands|Beginners_Guide_(Nederlands)}}<br />
{{i18n_entry|Português Brasil|Guia do Iniciante(Português do Brasil)}}<br />
{{i18n_entry|Português|Guia para Principiantes(Português)}}<br />
{{i18n_entry|Русский|Руководство_для_новичков}}<br />
{{i18n_entry|Türkçe|Başlangıç Rehberi (Türkçe)}}<br />
{{i18n_entry|हिन्दी|नौसिखिया गाइड(हिन्दी)}}<br />
{{i18n_entry|Indonesia|Beginners_Guide_(Indonesia)}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|Official Arch Linux Install Guide}} (provides a more general approach)<br />
{{Article summary end}}<br />
==Preface==<br />
=====Everything you ever wanted to know about Arch, but were afraid to ask=====<br />
Welcome. This self-contained document will guide you through the process of installing and configuring [[Arch Linux]]; a simple, agile and lightweight GNU/Linux distribution, <code>UNIX</code>-like operating system. Arch Linux requires a certain level of intimate knowledge of its configuration and of <code>UNIX</code>-like system methodology and for this reason, extra explanatory information is included. This guide is aimed at new Arch users, but strives to serve as a strong reference and informative base for all.<br />
<br />
'''Arch Linux distribution highlights:'''<br />
* '''[[The Arch Way | Simple]]''' design and philosophy<br />
* Independently Developed Community distro built from scratch and targeted at competent GNU/Linux users<br />
* All packages compiled for '''i686/x86-64'''<br />
* Highly customizable system assembled by the user from the ground up<br />
* '''[[The Arch boot process | BSD-style init]]''' scripts, featuring one centralized configuration file<br />
* '''mkinitcpio''': a simple and dynamic initramfs creator <br />
* '''Rolling Release''' model<br />
* '''[[Pacman]]''' package manager is fast, written in '''C''', lightweight and agile, with a very modest memory footprint<br />
* '''[[ABS]]''': The '''A'''rch '''B'''uild '''S'''ystem, a ports-like package building system makes it simple to create your own easily installable Arch packages from source, to use and/or share with the community on the [[AUR]]<br />
* '''[[AUR]]''': The Arch User Repository, offering many thousands of build scripts for Arch user-provided software packages<br />
<br />
=====DON'T PANIC!=====<br />
The Arch Linux system is assembled by the ''user'', from the shell, using basic command line tools. This is '''[[The Arch Way]].''' Unlike the more rigid structures of other distributions and installers, there are no default environments nor configurations chosen for you. From the command line, ''you'' will add packages from the Arch repositories using the [[pacman]] tool via your internet connection and manually configure your installation by editing text files until your system is customized to your requirements. This method allows for maximum flexibility, choice, and system resource control ''from the base up''.<br />
<br />
Arch Linux is aimed at competent GNU/Linux users who desire minimal 'code separation' from their machine.<br />
<br />
=====License=====<br />
<br />
Arch Linux, pacman, documentation, and scripts are copyright<br />
©2002-2007 by Judd Vinet, ©2007-2008 by Aaron Griffin and are licensed under the GNU General Public License Version 2.<br />
=====[[The Arch Way]]=====<br />
<br />
'''''The design principles behind Arch are aimed at keeping it [[The Arch Way|simple]].'' '''<br />
<br />
'Simple', in this context, shall mean 'without unnecessary additions, modifications, or complications'. In short; an elegant, minimalist approach.<br />
<br />
'''Some thoughts to keep in mind:'''<br />
<br />
*''&quot; 'Simple' is defined from a technical standpoint, not a usability standpoint. It is better to be technically elegant with a higher learning curve, than to be easy to use and technically [inferior].&quot; -Aaron Griffin''<br />
*''Entia non sunt multiplicanda praeter necessitatem'' or &quot;Entities should not be multiplied unnecessarily.&quot; -Occam's razor. The term ''razor'' refers to the act of shaving away unnecessary complications to arrive at the simplest explanation, method or theory.<br />
*''&quot;The extraordinary part of [my method] lies in its simplicity..I always believe that the simple way is the right way.&quot;'' - Bruce Lee<br />
* The Arch wiki is an excellent resource and should be consulted for issues [http://wiki.archlinux.org/index.php/Main_Page first]; IRC (freenode #archlinux), and the [http://bbs.archlinux.org/ forums] are also available if the answer cannot be found.<br />
<br />
{{Note|Following this guide closely is essential in order to successfully install a properly configured Arch Linux system, so ''please'' read it thoroughly. It is strongly recommended you read each section completely before carrying out the tasks contained.}}<br />
<br />
Welcome to Arch! Enjoy the installation; take your time and have fun!<br />
<br />
Now, let's get started.<br />
<br />
Since GNU/Linux Distributions are fundamentally 'modular' by design, the guide is logically divided into 4 main components of a desktop <code>UNIX</code>-like operating system: <br />
<br />
'''[[#Part I: Install the Base System|Part I: Installing the Base system]]'''<br />
<br />
'''[[#Part II: Configure&Update the New Arch Linux base system|Part II: Configure&Update the New Arch Linux base system]]'''<br />
<br />
'''[[#Part III: Install X and configure ALSA|Part III: Installing X and configuring ALSA]]'''<br />
<br />
'''[[#Part IV: Installing and configuring a Desktop Environment|Part IV: Installing a Desktop Environment]]'''<br />
<br />
==Part I: Install the Base System==<br />
<br />
===Step 1: Obtain the latest Installation media ===<br />
<br />
You can obtain Arch's official archiso media from [http://archlinux.org/download/ here]. The latest version is 2009.02 <br />
<br />
You can obtain Tobias Powalowski's 2008.12 archboot media from [http://downloads.archlinux.de/iso/archboot/2008.12/ here].<br />
<br />
*Both the Core installer and the FTP/HTTP-downloads provide only the necessary packages to create an '''Arch Linux base system'''. ''Note that the Base System does not include a GUI. It is mainly comprised of the GNU toolchain, (compiler, assembler, linker, libraries, shell, and a few useful utilities) the Linux kernel, and a few extra libraries and modules.''<br />
<br />
====CD installer====<br />
Burn the .iso to a CD with your preferred burner, and continue with [[#Boot Arch Linux Installer | Boot Arch Linux Installer]]<br />
{{Box Note| Optical drives as well as CD media quality vary greatly, but generally, using a slow burn speed is recommended for reliable burns; Some users recommend speeds '''''as low as 4x or 2x.''''' If you are experiencing unexpected behavior from the CD, try burning at the minimum speed supported by your system. }}<br />
<br />
====USB stick====<br />
{{Warning|This will destroy all data on your USB stick.}}<br />
<br />
Insert an empty or expendable USB stick, determine its path, and dump the .img to the USB stick with the <code>/bin/dd</code> program:<br />
dd if=archlinux-2009.02-[core_or_ftp]-i686.img of=/dev/sd''x''<br />
where ''if='' is the path to the img file and ''of='' is your USB device. Make sure to use /dev/sd''x'' and not /dev/sd''x1''.<br />
<br />
'''Check md5sum (optional):'''<br />
<br />
Make a note of the number of records (blocks) read in and written out, then perform the following check:<br />
dd if=/dev/sd''x'' count=''number_of_records'' status=noxfer | md5sum<br />
The md5sum returned should match the md5sum of the downloaded archlinux image file; they both should match the md5sum of the image as listed in the md5sums file in the mirror distribution site.<br />
<br />
Continue with [[#Boot Arch Linux Installer | Boot Arch Linux Installer]]<br />
<br />
===Step 2: Boot Arch Linux Installer===<br />
Insert the CD or USB stick and boot from it. You may have to<br />
change the boot order in your computer BIOS or press a key (usually DEL, F1, F2, F11 or F12) during the BIOS POST phase.<br />
<br />
Memory requirements:<br />
<br />
* CORE : 160 MB RAM x86_64/i686 (all packages selected, with swap partition)<br />
* FTP : 160 MB RAM x86_64/i686 (all packages selected, with swap partition)<br />
<br />
Choose Boot Archlive or Boot Archlive [legacy IDE] if you have trouble with libata/PATA.<br />
<br />
To change boot options press '''e''' for editing the boot lines. Many users may wish to change the resolution of the framebuffer, for more readable console output. Append:<br />
vga=773<br />
to the kernel line, followed by <ENTER>, for a 1024x768 framebuffer.<br />
<br />
Hit '''b''' to boot.<br />
<br />
The system will now boot and present a login prompt. Login as 'root' without quotes.<br />
<br />
====Changing the keymap====<br />
If you have a non-US keyboard layout you can interactively choose your keymap/console font with the command:<br />
# km<br />
or use the loadkeys command:<br />
# loadkeys ''layout''<br />
(replace ''layout'' with your keyboard layout such as &quot;<code>fr</code>&quot; or &quot;<code>be-latin1</code>&quot;)<br />
<br />
====Documentation====<br />
The official install guide is available on the live system. The official guide covers installation and configuration of the base system only. Change to vc/2 with <ALT>+F2 and invoke <code>/usr/bin/less</code>:<br />
# less /arch/arch-linux-official-guide.txt<br />
<code>less</code> will allow you to page through the document. Change back to vc/1 with <ALT>+F1.<br />
<br />
Change back to vc/2 if you need to reference the Official Guide at any time.<br />
<br />
===Step 3: Start the Installation===<br />
As root, run the installer script from vc/1:<br />
# /arch/setup<br />
<br />
===A: Select an installation source===<br />
After a welcome screen, you will be prompted for an installation source. Choose the appropriate source for the installer you are using.<br />
* If you chose the CORE installer, continue below with [[#Prepare Hard Drive|Prepare Hard Drive]].<br />
* FTP/HTTP only: You shall be prompted to load ethernet drivers manually, if desired. Udev is quite effective at loading the required modules, so you may assume it has already done so. You may verify this by invoking ifconfig -a from vc/3. (Select OK to continue.)<br />
<br />
====Configure Network (FTP/HTTP)====<br />
Available Interfaces will be presented. If an interface and HWaddr ('''H'''ard'''W'''are '''addr'''ess) is listed, then your module has already been loaded. If your interface is not listed, you may probe it from the installer, or manually do so from another virtual console.<br />
<br />
The following screen will prompt you to ''Select the interface, Probe,'' or ''Cancel''. Choose the appropriate interface and continue.<br />
<br />
The installer will then ask if you wish to use DHCP. Choosing Yes will run '''dhcpcd''' to discover an available gateway and request an IP address; Choosing No will prompt you for your static IP, netmask, broadcast, gateway DNS IP, HTTP proxy, and FTP proxy. Lastly, you will be presented with an overview to ensure your entries are correct.<br />
<br />
=====Wireless Quickstart (If you need wireless connectivity during the installation process)=====<br />
<br />
The wireless drivers and utilities are now available to you in the live environment of the installation media. A good knowledge of your wireless hardware will be of key importance to successful configuration.<br />
<br />
If you need wireless functionality from the live installer environment onwards, the basic procedure will be:<br />
* Switch to a free virtual console, e.g.: <ALT>+F3<br />
* Ensure udev has loaded the driver, and that the driver has created a usable wireless kernel interface with <code>/usr/sbin/iwconfig</code>:<br />
# iwconfig<br />
(Output should show an available wireless interface)<br />
* Bring the interface up with <code>/sbin/ifconfig <interface> up</code>.<br />
An example, using an atheros card and madwifi driver:<br />
# ifconfig ath0 up<br />
(Remember, your interface may be named something else, depending on your module (driver) and chipset: wlan0, eth1, etc.)<br />
* Specify the id of the wireless network with iwconfig <interface> essid &quot;<youressid>&quot; key <yourwepkey> (give the essid (the 'network name') of the network in quotes), e.g.:<br />
# iwconfig ath0 essid &quot;linksys&quot; key 0241baf34c<br />
* Acquire an IP address with <code>/sbin/dhcpcd <interface> </code>. e.g.:<br />
# dhcpcd ath0<br />
* Ensure you can route using <code>/bin/ping</code>:<br />
# ping -c 3 www.google.com<br />
Done.<br />
{{Box Note | '''''In addition to the wireless module, some wireless chipsets, like ipw2100 and ipw2200, require corresponding firmware installation. The firmware packages must be explicitly installed to your actual system to provide wireless functionality after you reboot into your installed system. (Due to the firmware installation requirement, these chipsets may not work in the live environment.) Package selection and installation is covered below. Ensure installation of both your wireless module and firmware during the package selection step! See [[Wireless Setup]] if you are unsure about the requirement of corresponding firmware installation for your particular chipset. This is a very common error.'''''}}<br />
<br />
After the initial Arch installation is complete, you may wish to refer to [[Wireless Setup]] to ensure a permanent configuration solution for your system.<br />
<br />
Return to vc/1 with <ALT>+F1. Continue with [[#Prepare Hard Drive|Prepare Hard Drive]]<br />
<br />
===B: Prepare Hard Drive===<br />
<br />
{{Warning|Partitioning hard drives can destroy data. You are strongly cautioned and advised to backup your critical data if applicable.}}<br />
<br />
Verify your current disk identities and layout by invoking <code>/sbin/fdisk</code> with the <code>-l</code> (lower-case L) switch.<br />
<br />
Open another virtual console (<ALT>+F3) and enter:<br />
# fdisk -l<br />
Take note of the disk(s)/partition(s) you wish to utilize for your Arch installation.<br />
<br />
Switch back to the installation script with <ALT>+F1<br />
<br />
Select the first menu entry &quot;Prepare Hard Drive&quot;.<br />
* Option 1: Auto Prepare<br />
Auto-Prepare divides your disk into the following configuration:<br />
<br />
* ext2 /boot partition, default size 32MB. ''You will be prompted to modify the size to you requirement.''<br />
* swap partition, default size 256MB. ''You will be prompted to modify the size to you requirement.''<br />
* A Separate / and /home partition, (sizes can also be specified). You may choose from ext2, ext3, reiserfs, xfs and jfs, but note that ''both / and /home shall share the same fs type'' if choosing the Auto Prepare option.<br />
<br />
Be warned that Auto-prepare will completely erase the chosen hard drive. Read the <font color=&quot;red&quot;>warning</font> presented by the installer very carefully, and make sure the correct device is about to be partitioned.<br />
<br />
* Option 2: '''(Recommended)''' Partition Hard Drives (with cfdisk)<br />
<br />
This option will allow for the most robust and customized partitioning solution for your personal needs.<br />
<br />
''At this point, more advanced GNU/Linux users who are familiar and comfortable with manually partitioning may wish to skip down to '''[[#C: Select Packages|Select Packages]]''' below.''<br />
<br />
{{Box Note|If you plan to install onto a USB flash key, see [[Installing_Arch_Linux_on_a_USB_key]].}}<br />
<br />
====Partition Hard Drives====<br />
<br />
=====Partition Info=====<br />
<br />
Partitioning a hard disk drive defines specific areas (the partitions) within the disk, that will each appear and behave as a separate disk and upon which a filesystem may be created (formatted).<br />
*There exist 3 types of disk partitions:<br />
#Primary<br />
#Extended<br />
#Logical<br />
'''Primary''' partitions can be bootable, and are limited to 4. If a partitioning scheme requires more than 4 partitions, we are forced to use an '''extended''' partition which will contain '''logical''' partitions.<br />
<br />
Extended partitions are not usable by themselves; they are merely a &quot;container&quot; for logical partitions. If required, a hard disk shall contain only one extended partition; which shall then be sub-divided into logical partitions.<br />
<br />
When partitioning a disk, one can observe this numbering scheme by creating primary partitions sda1-3 followed by creating an extended partition, sda4, and subsequently creating logical partition(s) within the extended partition; sda5, sda6, and so on.<br />
<br />
=====Swap Partition=====<br />
A swap partition is a place on your hard drive where virtual ram resides, allowing the kernel to easily use disk storage for data that does not fit into physical RAM.<br />
<br />
Historically, the general rule for swap partition size was 2x the amount of physical RAM. Over time, as computers have gained ever larger memory capacities, this rule has become increasingly deprecated. Generally, on machines with up to 512MB RAM, the 2x rule is usually quite sufficient. On machines with 1GB RAM, generally a 1x rule is adequate. If you have gratuitous amounts of RAM (more than 1024 MB) it may be possible to completely forget a swap partition altogether, though this is not recommended. We will create a 1 GB swap partition in this example.<br />
{{Box Note|If you plan on using suspend-to-disk, (hibernate) you must have a swap partition at least '''equal''' in size to the amount of physical RAM, and some Arch users even recommend oversizing it beyond the amount of physical RAM by 10-15%, to allow for possible bad sectors.}}<br />
<br />
=====Partition Scheme=====<br />
A disk partitioning scheme is a very personalized preference. Each user's choices will be unique to their own computing habits and requirements.<br />
<br />
Filesystem candidates for separate partitions include:<br />
<br />
'''/''' (root) ''The root filesystem is the primary filesystem from which all other filesystems stem; the top of the hierarchy. All files and directories appear under the root directory &quot;/&quot;, even if they are stored on different physical devices. The contents of the root filesystem must be adequate to boot, restore, recover, and/or repair the system.''<br />
<br />
'''/boot''' ''This directory contains the kernel and ramdisk images as well as the bootloader configuration file, and bootloader stages. /boot also stores data that is used before the kernel begins executing userspace programs. This may include saved master boot sectors and sector map files.''<br />
<br />
'''/home''' ''User data and user specific configuration files for applications are stored in each user's home directory in a file that starts with the '.' character (a &quot;dot file&quot;).''<br />
<br />
'''/usr''' ''While root is the primary filesystem, /usr is the secondary hierarchy, for user data, containing the majority of (multi-)user utilities and applications. /usr is shareable, read-only data. This means that /usr shall be shareable between various hosts and must not be written to, except in the case of system update/upgrade. Any information that is host-specific or varies with time is stored elsewhere.''<br />
<br />
'''/tmp''' ''directory for programs that require temporary files''<br />
<br />
'''/var''' ''contains variable data; spool directories and files, administrative and logging data, pacman's cache, the ABS tree, etc.''<br />
{{Box Note | Besides /boot, directories essential for booting are: '/bin', '/dev', '/etc', '/lib', '/proc' and '/sbin'. Therefore, they must not reside on a separate partition from /.}}<br />
'''''There are several advantages for using discrete filesystems, rather than combining all into one partition''''':<br />
<br />
* Security: Each filesystem may be configured in /etc/fstab as 'nosuid', 'nodev', 'noexec', 'readonly', etc.<br />
* Stability: A user, or malfunctioning program can completely fill a filesystem with garbage if they have write permissions for it. Critical programs, which reside on a different filesystem remain unaffected.<br />
* Speed: A filesystem which gets written to frequently may become somewhat fragmented. (An effective method of avoiding fragmentation is to ensure that each filesystem is never in danger of filling up completely.) Separate filesystems remain unaffected, and each can be defragmented separately as well.<br />
* Integrity: If one filesystem becomes corrupted, separate filesystems remain unaffected.<br />
* Versatility: Sharing data across several systems becomes more expedient when independent filesystems are used. Separate filesystem types may also be chosen based upon the nature of data and usage.<br />
In this example, we shall use separate partitions for /, /var, /home, and a swap partition.<br />
<br />
{{Box Note | /var contains many small files. You may wish to take this into consideration when choosing a filesystem type for it, (if you choose to create its own separate partition).}}<br />
<br />
=====How big should my partitions be?=====<br />
This question is best answered based upon individual needs. If you have little or no experience with partitioning, you may wish to simply create one partition for root, and one partition for swap. Or, follow the example closely, and consider these guidelines to provide a frame of reference:<br />
* The root filesystem (/) in the example will contain the /usr directory, which can become moderately large, depending upon how much software is installed.<br />
<br />
* The /var filesystem will contain, among other data, the [[ABS]] tree and the pacman cache. Keeping cached packages is useful and versatile; it provides the ability to downgrade packages if needed. /var tends to grow in size; the pacman cache can grow large over long periods of time, but can be safely cleared if needed. 6-8 Gigs on a desktop system should therefore be sufficient for /var. Servers tend to have extremely large /var filesystems.<br />
* The /home filesystem is typically where user data, downloads, and multimedia reside. On a desktop system, /home is typically the largest filesystem on the drive by a large margin.<br />
* An extra 25% of space added to each filesystem will provide a cushion for unforeseen occurrence, expansion, and serve as a preventive against fragmentation.<br />
'''''From the guidelines above, the example system shall contain a ~15GB root (/) partition, ~6GB /var, 1GB swap, and a /home containing the remaining disk space.'''''<br />
<br />
=====cfdisk=====<br />
Start by creating the primary partition that will contain the '''root''', (/) filesystem.<br />
<br />
Choose '''N'''ew -> Primary and enter the desired size for root (/). Put the partition at the beginning of the disk.<br />
<br />
Also choose the '''T'''ype by designating it as '83 Linux'. The created / partition shall appear as sda1 in our example.<br />
<br />
Now create a primary partition for /var, designating it as '''T'''ype 83 Linux. The created /var partition shall appear as sda2<br />
<br />
Next, create a partition for swap. Select an appropriate size and specify the '''T'''ype as 82 (Linux swap / Solaris). The created swap partition shall appear as sda3.<br />
<br />
Lastly, create a partition for your /home directory. Choose another primary partition and set the desired size.<br />
<br />
Likewise, select the '''T'''ype as 83 Linux. The created /home partition shall appear as sda4.<br />
<br />
Example:<br />
<br />
Name Flags Part Type FS Type [Label] Size (MB)<br />
-------------------------------------------------------------------------<br />
sda1 Primary Linux 15440 #root<br />
sda2 Primary Linux 6256 #/var<br />
sda3 Primary Linux swap / Solaris 1024 #swap<br />
sda4 Primary Linux 140480 #/home<br />
<br />
Choose '''W'''rite and type ''''yes''''. Beware that this operation may destroy data on your disk. Choose '''Q'''uit to leave the partitioner.<br />
Choose Done to leave this menu and continue with &quot;Set Filesystem Mountpoints&quot;.<br />
<br />
{{Box Note | Since the latest developments of the Linux kernel which include the libata and PATA modules, all IDE, SATA and SCSI drives have adopted the sd''x'' naming scheme. This is perfectly normal and should not be a concern.}}<br />
<br />
====Set Filesystem Mountpoints====<br />
First you will be asked for your swap partition. Choose the appropriate partition (sda3 in this example). You will be asked if you want to create a swap filesystem; select yes. Next, choose where to mount the / (root) directory (sda1 in the example). At this time, you will be asked to specify the filesystem type.<br />
<br />
=====Filesystem Types=====<br />
Again, a filesystem type is a very subjective matter which comes down to personal preference. Each has its own advantages, disadvantages, and unique idiosyncrasies. Here is a very brief overview of supported filesystems:<br />
<br />
1. '''ext2''' ''Second Extended Filesystem''- Old, reliable GNU/Linux filesystem. Very stable, but ''without journaling support''. May be inconvenient for root (/) and /home, due to very long fsck's. ''An ext2 filesystem can easily be converted to ext3.'' Generally regarded as a good choice for /boot/.<br />
<br />
2. '''ext3''' ''Third Extended Filesystem''- Essentially the ext2 system, but with journaling support. ext3 is completely compatible with ext2. ''Extremely'' stable, mature, and by far the most widely used, supported and developed GNU/Linux FS.<br />
<br />
'''High Performance Filesystems:'''<br />
<br />
3. '''ext4''' ''Fourth Extended Filesystem''- Backward compatible with ext2 and ext3, Introduces support for volumes with sizes up to 1 exabyte and files with sizes up to 16 terabyte. Increases the 32,000 subdirectory limit in ext3 to 64,000. Offers online defragmentation ability.<br />
<br />
3. '''ReiserFS''' - Hans Reiser's high-performance journaling FS uses a very interesting method of data throughput based on an unconventional and creative algorithm. ReiserFS is touted as very fast, especially when dealing with many small files. ReiserFS is fast at formatting, yet comparatively slow at mounting. Quite mature and stable. ReiserFS is not actively developed at this time (Reiser4 is the new Reiser filesystem). Generally regarded as a good choice for /var/.<br />
<br />
4. '''JFS''' - IBM's '''J'''ournaled '''F'''ile'''S'''ystem- The first filesystem to offer journaling. JFS had many years of use in the IBM AIX® OS before being ported to Linux. JFS currently uses the least CPU resources of any GNU/Linux filesystem. Very fast at formatting, mounting and fsck's, and very good all-around performance, especially in conjunction with the deadline I/O scheduler. (See [[JFS]].) Not as widely supported as ext or ReiserFS, but very mature and stable.<br />
<br />
5. '''XFS''' - Another early journaling filesystem originally developed by Silicon Graphics for the IRIX OS and ported to Linux. XFS offers very fast throughput on large files and large filesystems. Very fast at formatting and mounting. Generally benchmarked as slower with many small files, in comparison to other filesystems. XFS is very mature and offers online defragmentation ability.<br />
* JFS and XFS filesystems cannot be ''shrunk'' by disk utilities (such as gparted or parted magic)<br />
<br />
===== A note on Journaling=====<br />
All above filesystems, except ext2, use [http://en.wikipedia.org/wiki/Journaling_file_system journaling]. Journaling file systems are fault-resilient file systems that use a journal to log changes before they're committed to the file system to avoid metadata corruption in the event of a crash. Note that not all journaling techniques are alike; specifically, only ext3 offers ''data-mode journaling'', (though, not by default), which journals ''both'' data ''and'' meta-data (but with significant speed penalty). The others only offer ''ordered-mode journaling'', which journals meta-data only. While all will return your filesystem to a valid state after recovering from a crash, ''data-mode journaling'' offers the greatest protection against file system corruption and data loss but can suffer from performance degradation, as all data is written twice (first to the journal, then to the disk). Depending upon how important your data is, this may be a consideration in choosing your filesystem type.<br />
<br />
'''''Moving on...'''''<br />
<br />
Choose and create the filesystem (format the partition) for / by selecting '''yes'''. You will now be prompted to add any additional partitions. In our example, sda2 and sda4 remain. For sda2, choose a filesystem type and mount it as /var. Finally, choose the filesystem type for sda4, and mount it as /home. Return to main menu.<br />
<br />
===C: Select Packages===<br />
<br />
Now we shall select packages to install in our system.<br />
*Core ISO: Choose CD as source and select the appropriate CD drive if you have more than one.<br />
*FTP ISO: Select an FTP/HTTP mirror. ''Note that archlinux.org is throttled to 50KB/s''.<br />
* 2008.06 installation media: Package category BASE is now installed by default.<br />
<br />
Package selection is split into two stages. First, select the package category:<br />
{{Box Note | For expedience, all packages in '''base''' are selected by default}}<br />
* '''Base''': The minimal base environment<br />
* '''Base-devel''': Extra tools such as '''make''', '''automake''' and '''wireless-tools''' as well as wireless drivers.<br />
<br />
After category selection, you will be presented with the full lists of packages, allowing you to fine-tune your selections. Use the space bar to select and unselect.<br />
<br />
{{Box Note | If you are going to require connection to a wireless network with WPA encryption, consider installing netcfg2 (as well as wireless_tools), which will enable you to do so.}}<br />
<br />
Once you're done selecting the packages you need, leave the selection<br />
screen and continue to the next step, Install Packages.<br />
<br />
===D: Install Packages===<br />
Next, choose 'Install Packages'. You will be asked if you wish to keep the packages in the pacman cache. If you choose 'yes', you will have the flexibility to [[Downgrade packages|downgrade]] to previous package versions in the future, so this is recommended (you can always clear the cache in the future). The installer script will now install the selected packages, as well as the default Arch 2.6 kernel, to your system.<br />
*FTP ISO: The [[Pacman]] package manager will now download and install your selected packages. (See vc/5 for output, vc/1 to return to the installer)<br />
*CORE ISO: The packages will be installed from the CD.<br />
<br />
Note: For Arch 2007.08 FTP installation: after 'Install Packages' you have to upgrade pacman (<ALT>+F3, pacman -Sy pacman) and again 'Install Packages'.<br />
<br />
===E: Configure the System===<br />
''Closely following and understanding these steps is of key importance to ensure a properly configured system.''<br />
<br />
At this stage of the installation, you will configure the primary configuration files of your Arch Linux base system.<br />
<br />
Previous versions of the installer included [[Hwdetect|hwdetect]] to gather information for your configuration. This has been deprecated, and udev should handle most module loading automatically at boot.<br />
<br />
'''The initramfs'''<br />
<br />
The initial ram filesystem, or initramfs, is a temporary file system used by the kernel during boot. It is used for making preparations, like hardware detection and module loading, before the real root file system can be mounted. Therefore, an initramfs allows for the use of a generic modular kernel for a wide variety of hardware, and without the need to compile a custom kernel for each end user.<br />
<br />
You will be prompted by a series of questions related to the configuration of your initramfs. You will be asked if you need support for booting from USB devices, FireWire devices, PCMCIA devices, NFS shares, software RAID arrays, LVM2 volumes, encrypted volumes, and DSDT support. Choose yes if you need it; in our example nothing is needed. Choosing 'yes' for any of the above will cause the installer script to place the appropriate hook(s) within the <code>/etc/mkinitcpio.conf</code> file.<br />
<br />
Now you will be asked which text editor you want to use; choose [http://en.wikipedia.org/wiki/Nano_%28text_editor%29 nano] or, if you are familiar with it, [http://en.wikipedia.org/wiki/Vim_%28text_editor%29 vim]. You will be presented with a menu including the main configuration files for your system.<br />
<br />
{{Box Note | ''It is very important at this point to edit, or at the very least, to verify by opening, every configuration file.'' The installer script relies on your input to create these files on your installation. A common error is to skip over these critical steps of configuration.}}<br />
<br />
=====Can the installer handle this more automatically?=====<br />
Hiding the process of system configuration is in direct opposition to [[The Arch Way]]. While it is true that recent versions of the kernel and hardware probing tools offer excellent hardware support and auto-configuration, Arch presents the user all pertinent configuration files during installation for the purposes of ''transparency and system resource control''. By the time you have finished modifying these files to your specifications, you will have learned the simple method of manual Arch Linux system configuration and become more familiar with the base structure, leaving you better prepared to use and maintain your new installation productively.<br />
<br />
====='''/etc/rc.conf'''=====<br />
Arch Linux follows in the '''*BSD''' tradition of utilizing '''/etc/rc.conf''' as the principal location for system configuration. This one file contains a wide range of configuration information, principally used at system startup. As its name directly implies, it also contains settings for and invokes the /etc/rc* files, and is, of course, sourced ''by'' these files.<br />
* '''LOCALIZATION''' section<br />
** '''LOCALE'''=: This sets your system locale, which will be used by all i18n-aware applications and utilities. You can get a list of the available locales by running 'locale -a' from the command line. This setting's default is fine for US English users.<br />
** '''HARDWARECLOCK'''=: Specifies whether the hardware clock, which is synchronized on boot and on shutdown, stores '''UTC''' time, or the '''localtime'''. UTC makes sense because it greatly simplifies changing timezones and daylight savings time. localtime is necessary if you dual boot with an operating system such as Windows, that only stores localtime to the hardware clock.<br />
** '''USEDIRECTISA''': Use direct I/O request instead of /dev/rtc for hwclock<br />
** '''TIMEZONE'''=: Specify your TIMEZONE. (All available zones are under /usr/share/zoneinfo/).<br />
** '''KEYMAP'''=: The available keymaps are in /usr/share/kbd/keymaps. Please note that this setting is only valid for your TTYs, not any graphical window managers or '''X'''.<br />
** '''CONSOLEFONT'''=: Available console fonts reside under /usr/share/kbd/consolefonts/ if you must change. The default (blank) is safe.<br />
** '''CONSOLEMAP'''=: Defines the console map to load with the setfont program at boot. Possible maps are found in /usr/share/kbd/consoletrans, if needed. The default (blank) is safe.<br />
** '''USECOLOR'''=: Select &quot;yes&quot; if you have a color monitor and wish to have colors in your consoles.<br />
<br />
LOCALE=&quot;en_US.utf8&quot;<br />
HARDWARECLOCK=&quot;localtime&quot;<br />
USEDIRECTISA=&quot;no&quot;<br />
TIMEZONE=&quot;US/Eastern&quot;<br />
KEYMAP=&quot;us&quot;<br />
CONSOLEFONT=<br />
CONSOLEMAP=<br />
USECOLOR=&quot;yes&quot;<br />
<br />
* '''HARDWARE''' section<br />
** '''MOD_AUTOLOAD'''=: Setting this to &quot;yes&quot; will use '''udev''' to automatically probe hardware and load the appropriate modules during boot-up, (convenient with the default modular kernel). Setting this to &quot;no&quot; will rely on the user's ability to specify this information manually, or compile their own custom kernel and modules, etc.<br />
** '''MOD_BLACKLIST'''=: This has become deprecated in favor of adding blacklisted modules directly to the '''MODULES=''' line below.<br />
** '''MODULES'''=: Specify additional MODULES if you know that an important module is missing. If your system has any floppy drives, add "floppy". If you'll use loopback device, add "loop". Also specify any blacklisted modules by prefixing them with a bang (!). Udev will be forced NOT to load blacklisted modules. In the example, the IPv6 module as well as the annoying pcspeaker are blacklisted.<br />
# Scan hardware and load required modules at boot<br />
MOD_AUTOLOAD=&quot;yes&quot;<br />
# Module Blacklist - Deprecated<br />
MOD_BLACKLIST=()<br />
#<br />
MODULES=(e100 eepro100 mii slhc snd-ac97-codec snd-intel8x0 soundcore !net-pf-10 !pcspkr !snd_pcsp loop)<br />
<br />
* '''NETWORKING''' section<br />
** '''HOSTNAME'''=:Set your HOSTNAME to your liking.<br />
** '''eth0'''=: 'Ethernet, card 0'. Adjust the interface IP address, netmask and broadcast address ''if'' you are using '''static IP'''. Set eth0=&quot;dhcp&quot; if you want to use '''DHCP'''<br />
** '''INTERFACES'''=: Specify any/all interfaces here. If you do not use DHCP to configure a device, just keep in mind that the value of the variable (whose name must be equal to the name of the device which is supposed to be configured) equals the line which would be appended to the ifconfig command if you were to configure the device manually in the shell.<br />
** '''gateway'''=: If you are using '''static IP''', set the gateway address. If using '''DHCP''', you can usually ignore this variable, though some users have reported the need to define it.<br />
** '''ROUTES'''=: If you are using static '''IP''', remove the '''!''' in front of 'gateway'. If using '''DHCP''', you can usually leave this variable commented out with the bang (!), but again, some users require the gateway and ROUTES defined. If you experience networking issues with pacman, for instance, you may want to return to these variables.<br />
<br />
Example, using '''DHCP''':<br />
HOSTNAME=&quot;arch&quot;<br />
#eth0=&quot;eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255&quot;<br />
eth0=&quot;dhcp&quot;<br />
INTERFACES=(eth0)<br />
gateway=&quot;default gw 192.168.0.1&quot;<br />
ROUTES=(!gateway)<br />
{{Box Note | Arch uses the '''dhcpcd''' DHCP client. Alternatively, '''dhclient''' is available from the [extra] repository via pacman.}}<br />
<br />
* '''DAEMONS''' section<br />
<br />
This array simply lists the names of those scripts contained in /etc/rc.d/ which are to be started during the boot process, and the order in which they start. <br />
DAEMONS=(@network syslog-ng netfs crond)<br />
*If a script name is prefixed with a bang (!), it is not executed.<br />
*If a script is prefixed with an &quot;at&quot; symbol (@), then it will be executed in the background; the startup sequence will not wait for successful completion of each daemon before continuing to the next. (Useful for speeding up system boot).<br />
*Edit this array whenever new system services are installed, if starting them automatically during boot is desired.<br />
<br />
This 'BSD-style' init, is the Arch way of handling what others handle with various symlinks to an /etc/init.d directory.<br />
<br />
=====About DAEMONS=====<br />
You do not have to change the [[daemons]] line at this time, but it is useful to explain what daemons are, because we need them later in this guide.<br />
A ''daemon'' is a program that runs in the background, waiting for events to occur and offering services. A good example is a webserver that waits for a request to deliver a page or an SSH server waiting for someone trying to log in. While these are full-featured applications, there are daemons whose work is not that visible. Examples are a daemon which writes messages into a log file (e.g. syslog, metalog), a daemon which lowers your CPU's frequency if your system has nothing to do (e.g.:cpufreq), and a daemon which offers you a graphical login (e.g.: gdm, kdm). All these programs can be added to the daemons line and will be started when the system boots. Useful daemons will be presented during this guide.<br />
<br />
Historically, the term ''daemon'' was coined by the programmers of MIT's Project MAC. They took the name from ''Maxwell's demon'', an imaginary being from a famous thought experiment that constantly works in the background, sorting molecules. <code>UNIX</code> systems inherited this terminology and created the backronym '''d'''isk '''a'''nd '''e'''xecution '''mon'''itor.<br />
<br />
{{Tip|All Arch daemons reside under /etc/rc.d/}}<br />
<br />
=====/etc/fstab=====<br />
The '''fstab''' (for '''f'''ile '''s'''ystems '''tab'''le) is part of the system configuration listing all available disks and disk partitions, and indicating how they are to be initialized or otherwise integrated into the overall system's filesystem. The '''/etc/fstab''' file is most commonly used by the '''mount''' command. The mount command takes a filesystem on a device, and adds it to the main system hierarchy that you see when you use your system. '''mount -a''' is called from /etc/rc.sysinit, about 3/4 of the way through the boot process, and reads /etc/fstab to determine which options should be used when mounting the specified devices therein. If '''noauto''' is appended to a filesystem in /etc/fstab, '''mount -a''' will not mount it at boot.<br />
<br />
An example '''/etc/fstab''':<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
none /dev/pts devpts defaults 0 0<br />
none /dev/shm tmpfs defaults 0 0<br />
#/dev/cdrom /media/cdrom auto ro,user,noauto,unhide 0 0<br />
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0<br />
#/dev/fd0 /media/fl auto user,noauto 0 0<br />
/dev/disk/by-uuid/0ec-933.. / jfs defaults,noatime 0 1<br />
/dev/disk/by-uuid/7ef-223.. /home jfs defaults,noatime 0 2<br />
/dev/disk/by-uuid/530-1e-.. swap swap defaults 0 0<br />
/dev/disk/by-uuid/4fe-110.. /var reiserfs defaults,noatime,notail 0 2<br />
{{Box Note | The 'noatime' option disables writing read access times to the metadata of files and may safely be appended to / and /home regardless of your specified filesystem type for increased speed, performance, and power efficiency. 'notail' disables the ReiserFS tailpacking feature, for added performance at the cost of slightly less efficient disk usage.}}<br />
{{Box Note | It may be beneficial to make a note of the UUID of the root (/) partition, as this may be required during GRUB configuration.}}<br />
<br />
* The first field, '''<file system>''', describes the block device or remote filesystem to be mounted. For regular mounts, this field will contain a link to a block device node (as created by mknod which is called by udev at boot) for the device to be mounted; for instance, '/dev/cdrom' or '/dev/sda1'. Instead of giving the device explicitly, the Arch installer indicates the filesystem that is to be mounted by its UUID by default.<br />
{{Box Note | As of 2008-04rc, Arch is now utilizing the UUID, or Universally Unique Identifier naming convention, for consistent device mapping. This is due to active developments in the kernel and also udev, which may randomly change the ordering in which drivers for storage controllers are loaded, yielding an unbootable system/kernel panic. Nearly every motherboard has several controllers (onboard SATA, onboard IDE), and due to the aforementioned development updates, /dev/sda may become /dev/sdb on the next reboot- hence the persistent device naming convention of UUID has been adopted for reliability. ''If you do not need nor wish to use UUID, simply change your fstab to use whatever naming convention desired.'' (See [[Persistent block device naming| this wiki article]] for more information on persistent block device naming. )}}<br />
ls -lF /dev/disk/by-uuid/<br />
Will list all partitions by uuid.<br />
<br />
* The second field, '''<dir>''', describes the mount point for the filesystem. For swap partitions, this field should be specified as 'swap'; (Swap partitions are not actually mounted.)<br />
<br />
* The third field, '''<type>''', describes the type of the filesystem. The Linux kernel supports many filesystem types. (For the filesystems currently supported by the running kernel, see /proc/filesystems). An entry 'swap' denotes a file or partition to be used for swapping. An entry 'ignore' causes the line to be ignored. This is useful to show disk partitions which are currently unused.<br />
<br />
* The fourth field, '''<options>''', describes the mount options associated with the filesystem. It is formatted as a comma separated list of options. It contains at least the type of mount plus any additional options appropriate to the filesystem type. For documentation on the available options for non-nfs file systems, see mount(8).<br />
<br />
* The fifth field, '''<dump>''', is used for these filesystems by the dump(8) command to determine which filesystems need to be dumped. dump is a backup utility. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be backed up. ''Note that dump is not installed by default.''<br />
<br />
* The sixth field, '''<pass>''', is used by the fsck(8) program to determine the order in which filesystem checks are done at boot time. The root filesystem should be specified with a <pass> of 1, and other filesystems should have a <pass> of 2 or 0. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked.<br />
<br />
*If you plan on using '''hal''' to automount media such as DVDs, you may wish to comment out the cdrom and dvd entries in preparation for '''hal''', which will be installed later in this guide.<br />
<br />
<br />
<br />
Expanded information available in the [[Fstab]] wiki entry.<br />
<br />
====='''[[Configuring mkinitcpio | /etc/mkinitcpio]].conf'''=====<br />
Editing this configuration is unnecessary at this point; this information is provided for explanation.<br />
<br />
This file allows you to fine-tune the initial ram filesystem (also commonly referred to as the initial ramdisk or &quot;initrd&quot;) for your system. The initrd is a gzipped image that is read by the kernel during boot. The purpose of the initrd is to bootstrap the system to the point where it can access the root filesystem. This means it has to load any modules that are required for devices like IDE, SCSI, or SATA drives (or USB/FW, if you are booting off a USB/FW drive). Once the initrd loads the proper modules, either manually or through udev, it passes control to the Arch system and your boot continues. For this reason, the initrd only needs to contain the modules necessary to access the root filesystem. It does not need to contain every module you would ever want to use. The majority of your everyday modules will be loaded later on by udev, during the init process.<br />
<br />
'''mkinitcpio''' is the next generation of '''initramfs creation'''. It has many advantages over the old '''mkinitrd''' and '''mkinitramfs''' scripts.<br />
<br />
* It uses '''klibc''' and '''kinit''' which are developed by Linux kernel devs to provide a small and lightweight base for early userspace.<br />
* It can use '''udev''' for hardware autodetection at runtime, thus prevents you from having tons of unnecessary modules loaded.<br />
* Its hook-based init script is easily extendable with custom hooks, which can easily be included in pacman packages without having to modifiy mkinitcpio itself.<br />
* It already supports '''lvm2''', '''dm-crypt''' for both legacy and luks volumes, '''raid''', '''swsusp''' and '''suspend2''' resuming and booting from '''usb mass storage''' devices.<br />
* Many features can be configured from the kernel command line without having to rebuild the image.<br />
* The '''mkinitcpio''' script makes it possible to include the image in a kernel, thus making a self-contained kernel image is possible.<br />
* Its flexibility makes recompiling a kernel unnecessary in many cases.<br />
'''mkinitcpio''' was developed by Aaron Griffin and Tobias Powalowski with some help from the community.<br />
<br />
===== /etc/modprobe.conf=====<br />
It is unnecessary to configure this file at this time.<br />
<br />
* '''modprobe.conf''' can be used to set special configuration options for the kernel modules<br />
<br />
=====/etc/resolv.conf (for Static IP)=====<br />
The ''resolver'' is a set of routines in the C library that provide access to the Internet Domain Name System (DNS). One of the main functions of DNS is to translate domain names into IP addresses, to make the Web a friendlier place. The resolver configuration file, or /etc/resolv.conf, contains information that is read by the resolver routines the first time they are invoked by a process.<br />
<br />
*''If you are using DHCP, you may safely ignore this file, as by default, it will be dynamically created and destroyed by the dhcpcd daemon. You may change this default behavior if you wish. (See [http://wiki.archlinux.org/index.php/Network#For_DHCP_IP Network]]).''<br />
<br />
If you use a static IP, set your DNS servers in /etc/resolv.conf (nameserver <ip-address>). You may have as many as you wish.<br />
An example, using OpenDNS:<br />
nameserver 208.67.222.222<br />
nameserver 208.67.220.220<br />
<br />
If you are using a router, you will probably want to specify your DNS servers in the router itself, and merely point to it from your '''/etc/resolv.conf''', using your router's IP (which is also your gateway from '''/etc/rc.conf'''), e.g.:<br />
nameserver 192.168.1.1<br />
<br />
If using '''DHCP''', you may also specify your DNS servers in the router, or allow automatic assignment from your ISP, if your ISP is so equipped.<br />
<br />
=====/etc/hosts=====<br />
This file associates IP addresses with hostnames and aliases, one line per IP address. For each host a single line should be present with the following information:<br />
<IP-address> <hostname> [aliases...]<br />
Add your ''hostname'', coinciding with the one specified in /etc/rc.conf, as an alias, so that it looks like this:<br />
127.0.0.1 localhost.localdomain localhost '''''yourhostname'''''<br />
{{Box Note |''This format, '''including the 'localhost' and your actual host name''', is required for program compatibility! Errors in this entry may cause poor network performance and/or certain programs to open very slowly, or not work at all. This is a very common error for beginners.''}}<br />
<br />
If you use a static IP, add another line using the syntax: <static-IP> <hostname.domainname.org> <hostname> e.g.:<br />
192.168.1.100 '''''yourhostname'''''.domain.org '''''yourhostname'''''<br />
<br />
{{Tip|For convenience, you may also use /etc/hosts aliases for hosts on your network, and/or on the Web, e.g.:<br />
64.233.169.103 www.google.com g<br />
192.168.1.90 media<br />
192.168.1.88 data<br />
The above example would allow you to access google simply by typing 'g' into your browser, and access to a media and data server on your network by name and without the need for typing out their respective IP addresses.}}<br />
<br />
=====/etc/hosts.deny and /etc/hosts.allow=====<br />
Modify these configurations according to your needs if you plan on using the [[SSH|ssh]] daemon. The default configuration will reject all incoming connections, not only ssh connections. Edit your '''/etc/hosts.allow '''file and add the appropriate parameters: <br />
<br />
* let everyone connect to you<br />
sshd: ALL<br />
<br />
* restrict it to a certain ip<br />
sshd: 192.168.0.1<br />
<br />
* OR restrict for an IP range<br />
sshd: 10.0.0.0/255.255.255.0<br />
<br />
If you do not plan on using the [[SSH|ssh]] daemon, leave this file at the default, (empty), for added security.<br />
<br />
=====/etc/locale.gen=====<br />
The '''/usr/sbin/locale-gen''' command reads from '''/etc/locale.gen''' to generate specific locales. They can then be used by '''glibc''' and any other locale-aware program or library for rendering &quot;peculiar&quot; text, correctly displaying regional monetary values, time and date formats, alphabetic idiosyncrasies, and other locale-specific standards. The ability to setup a default locale is a great built-in privilege of using a <code>UNIX</code>-like operating system.<br />
<br />
By default /etc/locale.gen is an empty file with commented documentation. Once edited, the file remains untouched. '''locale-gen''' runs on every '''glibc''' upgrade, generating all the locales specified in /etc/locale.gen.<br />
<br />
Choose the locale(s) you need (remove the # in front of the lines you want), e.g.:<br />
en_US ISO-8859-1<br />
en_US.UTF-8 <br />
<br />
The installer will now run the locale-gen script, which will generate the locales you specified. You may change your locale in the future by editing /etc/locale.gen and subsequently running 'locale-gen' as root.<br />
<br />
{{Box Note |'''''If you fail to choose your locale, this will lead to a &quot;The current locale is invalid...&quot; error. This is perhaps the most common mistake by new Arch users, and also leads to the most commonly asked questions on the forum.'''''}}<br />
<br />
=====Root password=====<br />
Finally, set a root password and make sure that you remember it later. Return to the main menu and continue with installing bootloader.<br />
<br />
=====Pacman-Mirror=====<br />
Choose a mirror repository for '''pacman'''. <br />
*''archlinux.org is throttled, limiting downloads to 50KB/s'' <br />
<br />
Return to the main menu.<br />
<br />
===F: Install Bootloader===<br />
Because we have no secondary operating system in our example, we will need a bootloader. [http://www.gnu.org/software/grub/ GNU GRUB] is the recommended bootloader. Alternatively, you may choose [http://lilo.go.dyndns.org/ LILO].<br />
<br />
====GRUB====<br />
The provided '''GRUB''' configuration ('''/boot/grub/menu.lst''') should be sufficient, but verify its contents to ensure accuracy (specifically, ensure that the root (/) partition is specified by UUID on line 3). You may want to alter the resolution of the console by adding a vga=<number> kernel argument corresponding to your desired virtual console resolution. (A table of resolutions and the corresponding numbers is printed in the menu.lst.)<br />
<br />
Example: <br />
title Arch Linux (Main)<br />
root (hd0,0) <br />
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/0ec1-9339.. ro vga=773<br />
initrd /boot/kernel26.img<br />
{{Box Note | ''The linux kernel, 'vmlinuz', is so named because it incorporated '''v'''irtual '''m'''emory capability early in its development. The '''z''' denotes a zipped (compressed) image.''}}<br />
<br />
Explanation:<br />
<br />
Line 1: '''title''': A printed menu selection. &quot;Arch Linux (Main)&quot; will be printed on the screen as a menu selection.<br />
<br />
Line 2: '''root''': '''GRUB''''s root; the drive and partition where the kernel (/boot) resides, according to system BIOS. (More accurately, where GRUB's stage2 file resides). '''NOT necessarily the root''' (/) file system, as they can reside on separate partitions. GRUB's numbering scheme starts at 0, and uses an hd''x,x'' format regardless of IDE or SATA, and enclosed within parentheses. <br />
<br />
The example indicates that /boot is on the first partition of the first drive, according to BIOS, or, (hd0,0).<br />
<br />
Line 3: '''kernel''': This line specifies:<br />
<br />
* The path and filename of the kernel '''''relative to GRUB's root'''''.<br />
In the example, /boot is merely a directory residing on the same partition as / and '''vmlinuz26''' is the kernel filename; '''/boot/vmlinuz26'''. ''If /boot were on a separate partition, the path and filename would be simply '''/vmlinuz26''', being relative to '''GRUB''''s root.'' <br />
<br />
* The root= argument to the kernel statement specifies the partition containing the root (/) directory in the booted system, (more accurately, the partition containing '''/sbin/init'''). If not already specified, you should enter the name of the partition, according to the UUID numbering scheme, using the ''/dev/disk/by-uuid/xxxx-xxxx-xxxx'' format. This UUID was found in the previous section regarding configuration of ''/etc/fstab''.<br />
<br />
*An easy way to distinguish the 2 appearances of 'root' in /boot/grub/menu.lst is to remember that the first root statement ''informs GRUB where the kernel resides'', whereas the second root= kernel argument ''tells the kernel where the root filesystem (/) resides''.<br />
<br />
* Kernel options. <br />
<br />
In our example, '''ro''' mounts the filesystem as read only during startup, and the '''&quot;vga=773&quot;''' argument will give a 1024x768 framebuffer with 256 color depth.<br />
<br />
Line 4: '''initrd''': (For Initial RAM disk) The path and filename of the initial RAM filesystem '''relative to GRUB''''s root. Again, in the example, /boot is merely a directory residing on the same partition as / and '''kernel26.img''' is the initrd filename; '''/boot/kernel26.img'''. ''If /boot were on a separate partition, the path and filename would be simply '''/kernel26.img''', being relative to '''GRUB''''s root.'' <br />
<br />
Install the '''GRUB''' bootloader (to the master boot record, sda in our example).<br />
<br />
===G: Reboot===<br />
That's it; You have configured and installed your Arch Linux base system. Exit the install, and reboot:<br />
# reboot<br />
(Be sure to remove the installer CD)<br />
<br />
==Part II: Configure&Update the New Arch Linux base system==<br />
Your new Arch Linux system will boot up and finish with a login prompt (you may want to change the boot order in your '''BIOS''' back to booting from hard disk).<br />
<br />
'''Congratulations, and welcome to your shiny, new Arch Linux base system!'''<br />
<br />
Your new Arch Linux base system is now a functional GNU/Linux environment ready for customization. From here, you may build this elegant set of tools into whatever you wish or require for your purposes. <br />
<br />
Login with the root account. We will configure pacman and update the system as root, then add a normal user. <br />
{{Box Note |Virtual consoles 1-6 are available.}}<br />
<br />
===Step 1: Configuring the network (if necessary)===<br />
*''This section will assist you in configuring most types of networks, if your network configuration is not working for you.''<br />
<br />
If you properly configured your system, you should have a working network. Try to ping www.google.com to verify this.<br />
# ping -c 3 www.google.com<br />
<br />
''If you have successfully established a network connection, continue with '''[[#Step 2: Update, Sync and Upgrade the system with pacman|Update, Sync and Upgrade the system with pacman]]'''.''<br />
<br />
If, after trying to ping www.google.com, you get an &quot;unknown host&quot; error, you may conclude that your network is not properly configured. You may choose to double-check the following files for integrity and proper settings:<br />
<br />
'''/etc/rc.conf''' # Specifically, check your HOSTNAME= and NETWORKING section for typos and errors.<br />
<br />
'''/etc/hosts''' # Double-check your format. (See above.)<br />
<br />
'''/etc/resolv.conf''' # If you are using a static IP. If you are using DHCP, this file will be dynamically created and destroyed by default, but can be changed to your preference. (See [[Network]].)<br />
<br />
Advanced instructions for configuring the network can be found in the [[Network]] article.<br />
<br />
====Wired LAN====<br />
<br />
Check your Ethernet with<br />
# ifconfig -a<br />
All interfaces will be listed. You should see an entry for eth0, or perhaps eth1. <br />
*'''Static IP'''<br />
<br />
If required, you can set a new static IP with:<br />
# ifconfig eth0 <ip address> netmask <netmask> up <br />
and the default gateway with<br />
# route add default gw <ip address of the gateway><br />
Verify that /etc/resolv.conf contains your DNS server and add it if it is missing. <br />
Check your network again with ping www.google.com. If everything is working now, adjust /etc/rc.conf as described above for static IP. <br />
*'''DHCP'''<br />
If you have a DHCP server/router in your network try:<br />
# dhcpcd eth0<br />
If this is working, adjust /etc/rc.conf as described above, for dynamic IP.<br />
<br />
====Wireless LAN====<br />
* Ensure the driver has created a usable interface:<br />
# iwconfig<br />
* Bring the interface up with <code>ifconfig <interface> up</code>. e.g.:<br />
# ifconfig ath0 up<br />
* (Optional) Scan for available access points:<br />
# iwlist ath0 scan | less<br />
* Specify the id of the wireless network with <code>iwconfig <interface> essid <youressid></code>. Or, if using WEP; <code>iwconfig <interface> essid <youressid> key <yourwepkey></code>, e.g.:<br />
# iwconfig ath0 essid linksys key 0241baf34c<br />
* Request an IP address with <code>dhcpcd <interface></code>. e.g.:<br />
# dhcpcd ath0<br />
* Ensure you can route:<br />
$ ping -c 3 www.google.com<br />
Done.<br />
<br />
Detailed setup guide: [[Wireless Setup]]<br />
<br />
====Analog Modem====<br />
To be able to use a Hayes-compatible, external, analog modem, you need to at least have the ppp package installed. Modify the file /etc/ppp/options to suit your needs and according to man pppd. You will need to define a chat script to supply your username and password to the ISP after the initial connection has been established. The manpages for pppd and chat have examples in them that should suffice to get a connection up and running if you're either experienced or stubborn enough. With udev, your serial ports usually are /dev/tts/0 and /dev/tts/1.<br />
Tip: Read [[Dialup without a dialer HOWTO]].<br />
<br />
Instead of fighting a glorious battle with the plain pppd, you may opt to install wvdial or a similar tool to ease the setup process considerably. In case you're using a so-called WinModem, which is basically a PCI plugin card working as an internal analog modem, you should indulge in the vast information found on the [http://www.linmodems.org/ LinModem] homepage.<br />
<br />
====ISDN====<br />
<br />
Setting up ISDN is done in three steps:<br />
# Install and configure hardware<br />
# Install and configure the ISDN utilities<br />
# Add settings for your ISP <br />
<br />
The current Arch stock kernels include the necessary ISDN modules, meaning that you will not need to recompile your kernel unless you're about to use rather odd ISDN hardware. After physically installing your ISDN card in your machine or plugging in your USB ISDN-Box, you can try loading the modules with modprobe. Nearly all passive ISDN PCI cards are handled by the hisax module, which needs two parameters: type and protocol. You must set protocol to '1' if your country uses the 1TR6 standard, '2' if it uses EuroISDN (EDSS1), '3' if you're hooked to a so-called leased-line without D-channel, and '4' for US NI1.<br />
<br />
Details on all those settings and how to set them is included in the kernel documentation, more specifically in the isdn subdirectory, and available online. The type parameter depends on your card; a list of all possible types can be found in the README.HiSax kernel documentation. Choose your card and load the module with the appropriate options like this:<br />
<br />
# modprobe hisax type=18 protocol=2<br />
<br />
This will load the hisax module for my ELSA Quickstep 1000PCI, being used in Germany with the EDSS1 protocol. You should find helpful debugging output in your /var/log/everything.log file, in which you should see your card being prepared for action. Please note that you will probably need to load some USB modules before you can work with an external USB ISDN Adapter.<br />
<br />
Once you have confirmed that your card works with certain settings, you can add the module options to your /etc/modprobe.conf:<br />
<br />
alias ippp0 hisax<br />
options hisax type=18 protocol=2<br />
<br />
Alternatively, you can add only the options line here, and add hisax to your MODULES array in the rc.conf. It's your choice, really, but this example has the advantage that the module will not be loaded until it's really needed.<br />
<br />
That being done, you should have working, supported hardware. Now you need the basic utilities to actually use it!<br />
<br />
Install the isdn4k-utils package, and read the manpage to isdnctrl; it'll get you started. Further down in the manpage you will find explanations on how to create a configuration file that can be parsed by isdnctrl, as well as some helpful setup examples. Please note that you have to add your SPID to your MSN setting separated by a colon if you use US NI1.<br />
<br />
After you have configured your ISDN card with the isdnctrl utility, you should be able to dial into the machine you specified with the PHONE_OUT parameter, but fail the username and password authentication. To make this work add your username and password to /etc/ppp/pap-secrets or /etc/ppp/chap-secrets as if you were configuring a normal analogous PPP link, depending on which protocol your ISP uses for authentication. If in doubt, put your data into both files.<br />
<br />
If you set up everything correctly, you should now be able to establish a dial-up connection with<br />
# isdnctrl dial ippp0<br />
as root. If you have any problems, remember to check the logfiles!<br />
<br />
====DSL (PPPoE)====<br />
<br />
These instructions are relevant to you only if your PC itself is supposed to manage the connection to your ISP. You do not need to do anything but define a correct default gateway if you are using a separate router of some sort to do the grunt work.<br />
<br />
Before you can use your DSL online connection, you will have to physically install the network card that is supposed to be connected to the DSL-Modem into your computer. After adding your newly installed network card to the modules.conf/modprobe.conf or the MODULES array, you should install the rp-pppoe package and run the pppoe-setup script to configure your connection. After you have entered all the data, you can connect and disconnect your line with<br />
<br />
# /etc/rc.d/adsl start<br />
<br />
and<br />
<br />
# /etc/rc.d/adsl stop<br />
<br />
respectively. The setup usually is rather easy and straightforward, but feel free to read the manpages for hints. If you want to automatically 'dial in' on boot-up, add adsl to your DAEMONS array, and put a ! before the network entry, since the network is handled by adsl now.<br />
<br />
===Step 2: Update, Sync and Upgrade the system with [[pacman]]===<br />
Now we will update the system using [[pacman]]. <br />
<br />
====A: Configuring pacman====<br />
<br />
=====What is pacman ?=====<br />
[[Pacman]] is the '''pac'''kage '''man'''ager of Arch Linux. Pacman is written in ''C'' and is designed from the ground up to be lightweight with a very modest memory footprint, fast, simple, and versatile. It manages your entire package system and handles installation, removal, package downgrade (through cache), custom compiled package handling, automatic dependency resolution, remote and local searches and much more. Arch uses the .tar.gz package format, which further enhances pacman's speed; Gzipped tarballs, though slightly larger, are decompressed many times faster than their Bzipped counterparts, and are therefore installed much more expediently. <br />
<br />
We will use pacman to download software packages from remote repositories and install them onto your system.<br />
<br />
Pacman is the most important tool in your Arch Linux toolbox for building the base system into whatsoever you please.<br />
<br />
=====Package Repositories and /etc/pacman.conf=====<br />
Arch currently offers the following 4 repositories readily accessible through pacman:<br />
<br />
'''[core]'''<br />
<br />
The simple principle behind [core] is to provide only one of each necessary tool for a base Arch Linux system; The GNU toolchain, the Linux kernel, one editor, one command line browser, etc. (There are a few exceptions to this. For instance, both vi and nano are provided, allowing the user to choose one or both.) It contains all the packages that MUST be in perfect working order to make sure your system continues to run. These are the absolute system-critical packages. Developer maintained.<br />
<br />
*''The Core installation media simply contains an installer script, and a snapshot of the core repository at the time of release.''<br />
<br />
'''[extra]'''<br />
<br />
The [extra] repository contains all Arch packages that are not themselves necessary for a base Arch system, but contribute to a more full-featured environment. '''X''', KDE, and Apache, for instance, can be found here. Developer maintained.<br />
<br />
'''[testing]'''<br />
<br />
The [testing] repository contains packages that are candidates for the [core] or [extra] repositories. New packages go into [testing] if:<br />
* they are expected to break something on update and need to be tested first<br />
* they require other packages to be rebuilt. In this case, all packages that need to be rebuilt are put into [testing] first and when all rebuilds are done, they are moved back to the other repositories. Developer maintained.<br />
<br />
[testing] is the only repository that can have name collisions with any of the other official repositories. <br />
<br />
{{Note|If enabled, [testing] must be the first repo listed in the user's <code>pacman.conf</code> file.}}<br />
<br />
{{Warning|Breakage is likely if the user performs a sysupgrade with [testing] enabled. Only experienced users should use this repository.}}<br />
<br />
'''[community]'''<br />
<br />
The [community] repository is maintained by the ''Trusted Users (TUs)'' and is part of the ''Arch User Repository ([[AUR]])''. It contains binary packages from the ''AUR'' that have enough votes and were adopted by a ''TU''. Like all repos listed above, [community] may be readily accessed by pacman.<br />
<br />
The '''[[AUR]]''' also contains the '''unsupported''' branch, which cannot be accessed directly by pacman*. [unsupported] contains more than nine thousand PKGBUILD scripts for building packages from source, that may be unavailable through the other repos. <br />
<br />
<nowiki>*</nowiki> '''''[[AUR Helpers]]''''' can help you seamlessly access AUR.<br />
<br />
'''/etc/pacman.conf'''<br />
<br />
pacman will attempt to read /etc/pacman.conf each time it is invoked. This configuration file is divided into sections, or repositories. Each section defines a package [[Official Repositories|repository]] that pacman can use when searching for packages. The exception to this is the options section, which defines global options.<br />
# nano /etc/pacman.conf<br />
Example:<br />
#<br />
# /etc/pacman.conf<br />
#<br />
# See the pacman.conf(5) manpage for option and repository directives<br />
<br />
#<br />
# GENERAL OPTIONS<br />
#<br />
[options]<br />
# The following paths are commented out with their default values listed.<br />
# If you wish to use different paths, uncomment and update the paths.<br />
#RootDir = /<br />
#DBPath = /var/lib/pacman/<br />
#CacheDir = /var/cache/pacman/pkg/<br />
#LogFile = /var/log/pacman.log<br />
HoldPkg = pacman glibc<br />
# If upgrades are available for these packages they will be asked for first<br />
SyncFirst = pacman<br />
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u<br />
#XferCommand = /usr/bin/curl %u > %o<br />
<br />
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup<br />
#IgnorePkg =<br />
#IgnoreGroup =<br />
<br />
#NoUpgrade =<br />
#NoExtract =<br />
<br />
# Misc options (all disabled by default)<br />
#NoPassiveFtp<br />
#UseSyslog<br />
#ShowSize<br />
#UseDelta<br />
#TotalDownload<br />
#<br />
# REPOSITORIES<br />
# - can be defined here or included from another file<br />
# - pacman will search repositories in the order defined here<br />
# - local/custom mirrors can be added here or in separate files<br />
# - repositories listed first will take precedence when packages<br />
# have identical names, regardless of version number<br />
# - URLs will have $repo replaced by the name of the current repo<br />
#<br />
# Repository entries are of the format:<br />
# [repo-name]<br />
# Server = ServerName<br />
# Include = IncludePath<br />
#<br />
# The header [repo-name] is crucial - it must be present and<br />
# uncommented to enable the repo.<br />
# <br />
<br />
# Testing is disabled by default. To enable, uncomment the following<br />
# two lines. You can add preferred servers immediately after the header,<br />
# and they will be used before the default mirrors.<br />
#[testing]<br />
#Include = /etc/pacman.d/mirrorlist<br />
<br />
[core]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
[extra]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist <br />
<br />
[community]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
# An example of a custom package repository. See the pacman manpage for<br />
# tips on creating your own repositories.<br />
#[custom]<br />
#Server = file:///home/custompkgs<br />
<br />
Enable all desired repositories (remove the # in front of the 'Include =' and '[repository]' lines).<br />
<br />
<br />
*'''''When choosing repos, be sure to uncomment both the repository header lines in [brackets] as well as the 'Include =' lines. Failure to do so will result in the selected repository being omitted! This is a very common error.'' '''<br />
<br />
=====/etc/pacman.d/mirrorlist=====<br />
Faster mirrors will dramatically improve pacman performance, and your overall Arch Linux experience.<br />
<br />
Edit /etc/pacman.d/mirrorlist:<br />
<br />
*''' Manually:'''<br />
# nano /etc/pacman.d/mirrorlist<br />
Remove all mirrors which are not on your continent, or are extremely distant. In nano, CTRL-K will cut each unneeded line. <br />
<br />
Edit /etc/pacman.d/mirrorlist by placing the best mirror at the top of the list. (Recall that archlinux.org is throttled to 50KB/s). In nano, Ctrl+A selects an area, cursor down marks the lines, Ctrl+K cuts the selected area and Ctrl+U uncuts, or pastes, it. <br />
<br />
*''' Alternative, using the rankmirrors script:'''<br />
<br />
<code>/usr/bin/rankmirrors</code> is a python script which will attempt to detect the mirrors which are closest to you. <br />
<br />
First, use pacman to install python:<br />
# pacman -Sy python <br />
'''cd''' to the /etc/pacman.d/ directory:<br />
# cd /etc/pacman.d<br />
Backup your existing /etc/pacman.d/mirrorlist:<br />
# cp mirrorlist mirrorlist.backup<br />
Edit mirrorlist.backup and uncomment mirrors you want to test with rankmirrors.<br />
<br />
Run the script against the mirrorlist.backup with the -n switch and redirect output to a new /etc/pacman.d/mirrorlist file:<br />
# rankmirrors -n 6 mirrorlist.backup > mirrorlist<br />
'''-n 6''': rank the 6 fastest mirrors<br />
<br />
'''Force pacman to refresh the package lists'''<br />
<br />
After creating/editing your /etc/pacman.d/mirrorlist, (manually or by <code>/usr/bin/rankmirrors</code>) issue the following command:<br />
# pacman -Syy<br />
Passing two --refresh or -y flags forces pacman to refresh all package lists even if they are considered to be up to date. Issuing pacman -Syy ''whenever a mirror is changed'', is good practice and will avoid possible headaches.<br />
<br />
=====Ignoring packages=====<br />
When you execute the command &quot;pacman -Syu&quot;, your entire system will be updated. It is possible that you want to prevent a package from being upgraded. An example could be the kernel (kernel26) or a package for which an upgrade may prove problematic for your system. In this case, you have two options; indicate the package(s) you want to skip in the pacman command line using the --ignore switch (do pacman -S --help for details) or permanently indicate the package(s) you want to skip in your /etc/pacman.conf file in the IgnorePkg array. List each package, with one intervening space :<br />
IgnorePkg = openoffice-base wine awesome <br />
The typical way to use Arch is to use pacman to install all packages unless there is no package available, in which case you can build your own package using [[ABS]]. Many user-contributed package build scripts are also available in the [[AUR]]. <br />
<br />
You are expected to keep your system up to date with pacman -Syu, rather than selectively upgrading packages. You may diverge from this typical usage as you wish; just be warned that there is a greater chance that things will not work as intended and that it could break your system. The majority of complaints happen when selective upgrading, unusual compilation or improper software installation is performed. Use of '''IgnorePkg''' in /etc/pacman.conf is therefore discouraged, and should only be used sparingly, if you know what you are doing.<br />
<br />
=====Ignoring Configuration Files=====<br />
In the same vein, you can also &quot;protect&quot; your configuration/system files from being overwritten during &quot;pacman -Su&quot; using the following option in your /etc/pacman.conf<br />
<br />
NoUpgrade = etc/lilo.conf boot/grub/menu.lst<br />
<br />
=====Get familiar with pacman=====<br />
pacman is the Arch user's best friend. It is highly recommended to study and learn how to use the pacman(8) tool. Try:<br />
man pacman<br />
<br />
For more information,please look up the [[pacman]] wiki entries at your leisure.<br />
<br />
====B: Update Pacman Itself (if necessary)====<br />
# pacman -Sy pacman<br />
<br />
===Step 3: Update System===<br />
You are now ready to upgrade your entire system. Before you do, read through the [http://www.archlinux.org/news/ news] (and optionally the [http://archlinux.org/pipermail/arch-announce/ announce mailing list]). Often the developers will provide important information about fixes for known issues. Consulting these pages before any upgrade is good practice. <br />
<br />
Sync, refresh, and upgrade your entire new system with:<br />
# pacman -Syu<br />
you may also use:<br />
# pacman --sync --refresh --sysupgrade<br />
<br />
pacman will now download a fresh copy of the master package list from the server(s) defined in pacman.conf(5) and perform all available upgrades. (You may be prompted to upgrade pacman itself at this point. If so, say yes, and then reissue the pacman -Syu command when finished.) <br />
<br />
Reboot if a kernel upgrade has occurred. <br />
<br />
{{Box Note|Occasionally, configuration changes may take place requiring user action during an update; read pacman's output for any pertinent information.}}<br />
<br />
Pacman output is saved in /var/log/pacman.log.<br />
<br />
{{Box Note|pacman might get updated, its mirrorlist configuration may be lost, so before you move on, make sure you reconfigure your pacman mirrorlist.}}<br />
<br />
See [[Package_Management_FAQs|Package Management FAQs]] for answers to frequently asked questions regarding updating and managing your packages.<br />
<br />
=====The Arch rolling release model=====<br />
Keep in mind that Arch is a '''rolling release''' distribution. This means there is never a reason to reinstall or perform elaborate system rebuilds to upgrade to the newest version. Simply issuing '''pacman -Syu''' periodically keeps your entire system up-to-date and on the bleeding edge. At the end of this upgrade, your system is completely current. '''Reboot''' if a kernel upgrade has occurred.<br />
<br />
===Step 4: Add a user and setup groups===<br />
<code>UNIX</code> is a multi-user environment. You should not do your everyday work using the root account. It is more than poor practice; it is dangerous. Root is for administrative tasks. Instead, add a normal, non-root user account using the <code>/usr/sbin/useradd</code> program:<br />
# useradd -m -G [groups] -s [login_shell] [username] <br />
* '''-m''' Creates user home directory as /home/'''username'''. Within their home directory, a user can write files, delete them, install programs, etc. Users' home directories shall contain their data and personal configuration files, the so-called 'dot files' (their name is preceded by a dot), which are 'hidden'. (To view dotfiles, enable the appropriate option in your file manager or run ls with the -a switch.) If there is a conflict between ''user'' (under /home/username) and ''global'' configuration files, (usually under /etc/) the settings in the ''user'' file will prevail. Dotfiles likely to be altered by the end user include .xinitrc and .bashrc files. The configuration files for xinit and Bash respectively. They allow the user the ability to change the window manager to be started upon login and also aliases, user-specified commands and environment variables respectively. When a user is created, their dotfiles shall be taken from the /etc/skel directory where system sample files reside.<br />
* '''-G''' A list of supplementary groups which the user is also a member of. ''Each group is separated from the next by a comma, with no intervening spaces''. The default is for the user to belong only to the initial group (users). <br />
* '''-s''' The name of the user´s login shell. Leaving this field blank will cause the system to select the default login shell.<br />
Useful groups for your non-root user include:<br />
*'''audio''' - for tasks involving sound card and related software<br />
*'''floppy''' - for access to a floppy if applicable<br />
*'''lp''' - for managing printing tasks<br />
*'''optical''' - for managing tasks pertaining to the optical drive(s)<br />
*'''storage''' - for managing storage devices<br />
*'''video''' - for video tasks and 3d acceleration<br />
*'''wheel''' - for using sudo/su<br />
*'''power''' - used w/ power options (ie. shutdown w/ off button) <br />
A typical example, adding a user named &quot;archie&quot; specifying bash as the login shell:<br />
# useradd -m -G users,audio,lp,optical,storage,video,wheel,power -s /bin/bash archie<br />
Next, add a password for your new user using <code>/usr/bin/passwd</code>.<br />
<br />
An example for our user, 'archie':<br />
# passwd archie<br />
(You will be prompted to provide the new <code>UNIX</code> password.)<br />
<br />
Your new non-root user has now been created, complete with a home directory and a login password.<br />
<br />
'''Alternative method, using <code>/usr/sbin/adduser</code>:'''<br />
<br />
Alternatively, you may use <code>adduser</code>, an interactive user adding program which will prompt you for the above data:<br />
# adduser<br />
'''Deleting the user account:'''<br />
<br />
In the event of error, or if you wish to delete this user account in favor of a different name or for any other reason, use <code>/usr/sbin/userdel</code>:<br />
# userdel -r [username]<br />
* '''-r ''' Files in the user´s home directory will be removed along with the home directory itself and the user´s mail spool.<br />
<br />
See the [[Groups]] and [[User Management]] articles for further information. You may also check the man pages for <code>usermod(8)</code> and <code>gpasswd(8)</code>.<br />
<br />
===Step 5: Install and setup Sudo (Optional)===<br />
To install Sudo:<br />
# pacman -S sudo<br />
To add a user as a sudo user (a &quot;sudoer&quot;), the visudo command must be run as root. If you do not know how to use vi, you may set the EDITOR environment variable to the editor of your choice before running visudo. e.g.:<br />
# EDITOR=nano visudo<br />
If you are comfortable using vi, issue the visudo command without the EDITOR=nano variable:<br />
# visudo<br />
This will open the file /etc/sudoers in a special session of vi. visudo copies the file to be edited to a temporary file, edits it with an editor, (vi by default), and subsequently runs a sanity check. If it passes, the temporary file overwrites the original with the correct permissions. <br />
<br />
{{Warning|Do not edit /etc/sudoers directly with an editor; Errors in syntax can cause annoyances (like rendering the root account unusable). You must use the ''visudo'' command to edit /etc/sudoers.}}<br />
<br />
To give the user full root privileges when he/she precedes a command with &quot;sudo&quot;, add the following line:<br />
USER_NAME ALL=(ALL) ALL<br />
where USER_NAME is the username of the individual.<br />
<br />
For more information, such as sudoer <TAB> completion, see [[Sudo]]<br />
<br />
==Part III: Install X and configure ALSA==<br />
<br />
<br />
===Step 1: Configure sound with alsamixer===<br />
The Advanced Linux Sound Architecture (known by the acronym '''ALSA''') is a Linux kernel component intended to replace the original Open Sound System (OSS) for providing device drivers for sound cards. Besides the sound device drivers, '''ALSA''' also bundles a user space library for application developers who want to use driver features with a higher level API than direct interaction with the kernel drivers.<br />
{{Box Note| Alsa is included in the Arch mainline kernel and udev will automatically probe your hardware on boot-up, loading the corresponding kernel module for your audio card. Therefore, your sound should already be working, but is muted by default.}}<br />
{{Box Note| OSS4.1 has been released under a free license and is generally considered a significant improvement over older OSS versions. If you have issues with ALSA, or simply wish to explore another option, you may choose OSS4.1 instead. Instructions can be found in [[OSS]]}} <br />
<br />
The alsa-utils package contains the alsamixer userspace tool, which will allow us to configure the sound device from the console. (You may also run alsamixer from an '''X''' environment later.)<br />
<br />
By default the kernel ships with snd_pcsp, the alsa pc speaker module. snd_pcsp is usually loaded before your &quot;actual&quot; sound card module. In most cases, it will be more convenient if this module is loaded last, as it will allow alsamixer to correctly control the desired sound card.<br />
<br />
To have snd_pcsp load last, add the following to /etc/modprobe.conf:<br />
options snd-pcsp index=2<br />
<br />
Alternatively, if you do not want snd_pcsp to load at all, blacklist it by adding the following to /etc/rc.conf:<br />
MODULES=(... !snd_pcsp)<br />
<br />
{{Box Note | You will need to unload all your sound modules and reload them for the changes to take affect. It might be easier to reboot. Your choice. }}<br />
<br />
Install the alsa-utils package:<br />
# pacman -S alsa-utils<br />
Also, you may want to install the alsa-oss package, which wraps applications written for [[OSS]] in a compatibility library and allowing them to work with [[ALSA]]. To install the alsa-oss package:<br />
# pacman -S alsa-oss <br />
Did you add your normal user to the audio group? If not, use <code>/usr/bin/gpasswd</code>. As root do:<br />
# gpasswd -a ''yourusername'' audio<br />
As '''''normal, non-root''''' user, invoke <code>/usr/bin/alsamixer</code>:<br />
# su - ''yourusername'' <br />
'''$''' alsamixer<br />
Unmute the Master and PCM channels by scrolling to them with cursor left/right and pressing '''M'''. Increase the volume levels with the cursor-up key. (70-90 Should be a safe range.) Some machines, (like the Thinkpad T61), have a '''Speaker''' channel which must be unmuted and adjusted as well. Leave alsamixer by pressing ESC. <br />
==== Sound test ====<br />
Ensure your speakers are properly connected, and test your sound configuration as normal user using <code>/usr/bin/aplay</code>:<br />
$ aplay /usr/share/sounds/alsa/Front_Center.wav<br />
You should hear a very eloquent woman say, &quot;Front, center.&quot;<br />
==== Saving the Sound Settings ====<br />
Exit your normal user shell and run <code>/usr/bin/alsactl</code> as root:<br />
$ exit<br />
# alsactl store<br />
This will create '/etc/asound.state', saving the alsamixer settings. <br />
<br />
Also, add the alsa ''daemon'' to your DAEMONS section in /etc/rc.conf to automatically restore the mixer settings on boot-up.<br />
# nano /etc/rc.conf<br />
DAEMONS=(syslog-ng network crond '''alsa''')<br />
''Note that the alsa daemon merely restores your volume mixer levels on boot up by reading /etc/asound.state. It is separate from the alsa audio library (and kernel level API).''<br />
<br />
Expanded information available in the [[ALSA]] wiki entry.<br />
<br />
===Step 2: Install X===<br />
The '''X''' Window System (commonly '''X11''', or just simply '''X''') is a networking and display protocol which provides windowing on bitmap displays. It provides the standard toolkit and protocol to build graphical user interfaces (GUIs) on <code>UNIX</code>-like operating systems.<br />
<br />
'''X''' provides the basic framework, or primitives, for building GUI environments: drawing and moving windows on the screen and interacting with a mouse and/or keyboard. '''X''' does not mandate the user interface — individual client programs handle this. <br />
<br />
'''X''' is so named because it was preceded by the '''W''' Window System, originally developed at Stanford University. <br />
<br />
{{Box Note| If you plan on using an '''open-source''' video driver, and need 3d acceleration, it is recommended to install the libgl library before installing Xorg:}}<br />
<br />
# pacman -S libgl<br />
''(Proprietary video drivers provide their own gl library implementations.)''<br />
<br />
====A: Install X====<br />
Now we will install the base Xorg packages using pacman. This is the first step in building a GUI.<br />
<br />
# pacman -S xorg<br />
With newer versions of xorg, it is suggested (and possibly necessary in most cases) to install the input driver evdev, which should be installed as a dependency for xorg-server, but many seem to be lacking somehow:<br />
# pacman -S xf86-input-evdev<br />
3d utilities such as glxgears are included in the '''mesa''' package:<br />
# pacman -S mesa<br />
<br />
====B: Install Video Driver Package====<br />
Now we have the base packages we need for running the '''X''' Server. You should add the driver for your graphics card now (e.g. xf86-video-<name>). The easiest way to configure X.org is by installing the correct driver packages first, and then generating /etc/X11/xorg.conf using an autoconfiguration script, like Xorg -configure.<br />
<br />
You will need knowledge of which video chipset your machine has. If you do not know, use the <code>/usr/sbin/lspci</code> program:<br />
# lspci | grep VGA<br />
<br />
If you need a list of all '''open-source''' video drivers, do: <br />
# pacman -Ss xf86-video | less<br />
Here is a list of '''open source''' drivers, and the corresponding video chipsets.<br />
*'''xf86-video-apm''' Alliance ProMotion video driver<br />
*'''xf86-video-ark''' ark video driver<br />
*'''xf86-video-ati''' ATI(AMD) video driver<br />
*'''xf86-video-chips''' Chips and Technologies video driver<br />
*'''xf86-video-cirrus''' Cirrus Logic video driver<br />
*'''xf86-video-dummy''' dummy video driver<br />
*'''xf86-video-fbdev''' framebuffer video driver<br />
*'''xf86-video-glint''' GLINT/Permedia video driver<br />
*'''xf86-video-i128''' Number 0 i128 video driver<br />
*'''xf86-video-i740''' Intel i740 video driver<br />
*'''xf86-video-i810''' Intel i810/i830/i9xx video drivers (deprecated - use -intel)<br />
*'''xf86-video-intel''' Newer Version of Intel i810/i830/i9xx video drivers<br />
*'''xf86-video-imstt''' Integrated Micro Solutions Twin Turbo vidoe driver<br />
*'''xf86-video-mga''' mga video driver (Matrox Graphics Adapter)<br />
*'''xf86-video-neomagic''' neomagic video driver<br />
*'''xf86-video-nv''' Nvidia nv video driver<br />
*'''xf86-video-rendition''' Rendition video driver<br />
*'''xf86-video-s3''' S3 video driver<br />
*'''xf86-video-s3virge''' S3 Virge video driver<br />
*'''xf86-video-savage''' savage video driver<br />
*'''xf86-video-siliconmotion''' siliconmotion video driver<br />
*'''xf86-video-sis''' SiS video driver<br />
*'''xf86-video-sisusb''' SiS USB video driver<br />
*'''xf86-video-tdfx''' tdfx video driver<br />
*'''xf86-video-trident''' Trident video driver<br />
*'''xf86-video-tseng''' tseng video driver<br />
*'''xf86-video-unichrome''' VIA S3 Unichrome video drivers<br />
*'''xf86-video-v4l''' v4l video driver<br />
*'''xf86-video-vesa''' vesa video driver<br />
*'''xf86-video-openchrome (testing)''' via video driver (currently in testing, try openchrome in the meantime)<br />
*'''xf86-video-vga''' VGA 16 color video driver<br />
*'''xf86-video-vmware ''' vmware video driver<br />
*'''xf86-video-voodoo ''' voodoo video driver<br />
<br />
* Note that the '''vesa''' driver is the most generic, and should work with almost any modern video chipset. If you cannot find a suitable driver for your video chipset, vesa '''should''' work.<br />
<br />
Use pacman to install the appropriate video driver for your video card/onboard video. e.g.:<br />
# pacman -S xf86-video-savage<br />
(for the Savage driver.)<br />
<br />
*If you have an NVIDIA or ATI video adapter, you may wish to install the proprietary NVIDIA or ATI drivers. '''Installing proprietary video drivers is covered below.'''<br />
-----<br />
<br />
====NVIDIA Graphic Cards====<br />
The NVIDIA proprietary drivers are generally considered to be of good quality, and offer 3D performance, whereas the open source '''nv''' driver offers only 2d support at this time. <br />
<br />
Before you configure your Graphics Card you will need to know which driver fits. Arch currently has several different driver packages that each match a certain subset of Cards: <br />
<br />
{{Box Note| Nvidia-71xx series proprietary drivers, which are required by extremely old cards like TNT and TNT2, have been removed because they do not work with the new Xorg that Arch makes use of, and nvidia has discontinued support for such. You should use the xf86-video-nv or xf86-video-vesa drivers instead or upgrade your card if you need 71xx.}}<br />
{{Box Note| Many suffer the same failure with 96xx as the above noted 71xx problem with the new xorg.}}<br />
<br />
'''1. nvidia-96xx''' ''slightly newer cards up to the GF 4.''<br />
<br />
'''2. nvidia-173xx''' ''Geforce FX series cards''<br />
<br />
'''3. nvidia''' ''newest GPUs after the GF FX''<br />
<br />
<br />
Consult the NVIDIA-Homepage to see which one is for you. The difference is only for the installation; Configuration works the same with every driver.<br />
<br />
Select and install the appropriate NVIDIA driver ''for your card'', e.g.: <br />
# pacman -S nvidia-96xx<br />
<br />
The NVIDIA package has a utility for updating your existing /etc/X11/xorg.conf for use with the NVIDIA driver:<br />
# nvidia-xconfig<br />
<br />
It also has several options which will further specify the contents and options of the xorg.conf file.<br />
For example,<br />
# nvidia-xconfig --composite --add-argb-glx-visuals<br />
<br />
For more detailed information, see nvidia-xconfig(1).<br />
<br />
Some useful tweaking options in the device section are (beware that these may not work on your system):<br />
Option &quot;RenderAccel&quot; &quot;true&quot;<br />
Option &quot;NoLogo&quot; &quot;true&quot;<br />
Option &quot;AGPFastWrite&quot; &quot;true&quot;<br />
Option &quot;EnablePageFlip&quot; &quot;true&quot;<br />
Make sure all instances of DRI are commented out:<br />
# Load &quot;dri&quot;<br />
Double check your /etc/X11/xorg.conf to make sure your default depth, horizontal sync, vertical refresh, and resolutions are acceptable.<br />
<br />
Update kernel module dependencies using <code>/sbin/depmod</code>:<br />
# depmod -a<br />
(A reboot may be necessary.)<br />
Advanced instructions for nvidia configuration can be found in the [[NVIDIA]] article.<br />
<br />
Continue with '''[[#Simple baseline X test(if necessary)|Simple baseline X test]]'''<br />
<br />
====ATI Graphic Cards====<br />
ATI owners have two options for drivers. If you are unsure which driver to use, please try the open-source one first. The open-source driver will suit most needs along with being generally less problematic.<br />
<br />
Install the '''proprietary''' ATI Driver with<br />
# pacman -S catalyst<br />
Use the aticonfig tool to modify the xorg.conf.<br />
<br />
Install the '''open-source''' ATI Driver with<br />
# pacman -S xf86-video-ati<br />
Currently, the performance of the open-source driver is not on par with that of the proprietary one. It also lacks TV-out, dual-link DVI support, and possibly other features. On the other hand, it supports Aiglx and has better dual-head support.<br />
{{Box Note| The latest proprietary driver does support [[AIGLX]] now. To use [[Compiz]] or [[Beryl]] add Option &quot;AIGLX&quot; &quot;True&quot; to Section ServerFlags.}}<br />
Advanced instructions for ATI configuration can be found in the [[ATI | ATI wiki]].<br />
<br />
edit by Adam King: <br />
ATI seem to have done slightly weird things with their drivers lately. <br />
Having installed arch from the Feb 09 release and hit major issues with catalyst 9.2.1 I thought this may be helpful. <br />
Firstly, installing catalyst at the standard time during installation seemed to break the X-server for me. so here was my working method:<br />
<br />
Do not install the catalyst driver during the arch install but make sure you have installed xorg, xf86-input-evdev and mesa (as detailed above). <br />
<br />
Carry on with the rest of the install until you have your desktop gui installed (gnome was my choice). <br />
<br />
Open an xterm prompt and run (as root or preferably sudo)<br />
# pacman -S catalyst<br />
Catalyst and catalyst-utils should be linked on most mirrors, you may wish to use<br />
# pacman -S catalyst catalyst-utils<br />
<br />
<br />
See the pacman output to make sure catalyst was installed with no errors. <br />
<br />
At this stage you should already have a working xorg.conf, you may wish to back this up (for example to an external drive).<br />
<br />
If your existing xorg.conf is in /etc/X11/xorg.conf simply run <br />
# aticonfig --initial<br />
if it is located elsewhere run <br />
# aticonfig --initial -i=<pathtofile><br />
<br />
Add fglrx to the modules section of /etc/rc.conf<br />
<br />
reboot and see catalyst working. <br />
<br />
*Note this was only tested using the ati radeon x1600. <br />
<br />
===Step 3: Configure X===<br />
<br />
====What is the xorg.conf file?====<br />
<br />
/etc/X11/xorg.conf is the main configuration file for your '''X''' Window System, the foundation of your '''G'''raphical '''U'''ser '''I'''nterface. It is a plain text file ordered into sections and subsections. Important sections are ''Files, InputDevice, Module, Monitor, Modes, Screen, Device, and ServerLayout''. Sections can appear in any order and there may be more than one section of each kind, for example, if you have more than one monitor, or if your laptop has a trackpoint as well as a mouse. <br />
<br />
By default, you will not have an Xorg config file, as the newest versions of Xorg feature autodetection. ''If'' the autodetection ''works satisfactorily'' and you do not need to specify special features such as aiglx, compositing and so forth, you may forgo creating an xorg.conf file. <br />
<br />
====A: Create /etc/X11/xorg.conf====<br />
<br />
Advanced users may wish to manually create their own xorg.conf file. You may also use the <code>/usr/bin/Xorg</code> program with the -configure option to generate a basic config file; As root, do:<br />
# Xorg -configure<br />
This will create a config file at /root/xorg.conf.new <br />
<br />
Copy the file to <code>/etc/X11/</code>:<br />
# cp /root/xorg.conf.new /etc/X11/xorg.conf<br />
<br />
====Alternative xorg.conf generation====<br />
* Note that if your machine has a successfully configured xorg.conf under another distribution and with the same Xorg version, you may easily copy it over to your current Arch system's <code>/etc/X11/</code> directory.<br />
* You may alternatively use the <code>/usr/bin/hwd</code> tool. Install with:<br />
# pacman -S hwd<br />
And run with<br />
# hwd -xa<br />
{{Box Note| At the time of this writing, hwd generates a xorg.conf with an invalid line for newer xorg packages. After using it, you need to remove or comment out the RgbPath line under Section &quot;Files&quot; via nano /etc/X11/xorg.conf or your equivalent, as root/sudo.}}<br />
<br />
* You may also try the <code>/usr/bin/xorgcfg</code> script:<br />
# xorgcfg <br />
* Lastly, you may choose <code>/usr/bin/xorgconfig</code>, which will interactively prompt you for hardware information to create a basic xorg.conf:<br />
# xorgconfig<br />
<br />
====B: Input hotplugging====<br />
<br />
Input hotplugging is enabled in the 1.5.x series of the xorg-server package, which is now included in the extra repo.<br />
When input hotplugging is enabled, X will purge any devices setup in xorg.conf that are using the kbd and mouse driver. <br />
<br />
{{Box Note | This may result in X appearing to freeze and result in your not being able to move your mouse or use your keyboard.}}<br />
<br />
There are two options to correct this(Choose '''Only''' one of them):<br />
<br />
1) '''Configure input hotplugging''' by installing the xf86-input-evdev driver and configuring HAL to use the kbd/mouse drivers.<br />
<br />
Install xf86-input-evdev:<br />
# pacman -S xf86-input-evdev<br />
Start the hal daemon before anything related to X.Org is started:<br />
# /etc/rc.d/hal start<br />
Add the hal daemon to the DAEMONS array in /etc/rc.conf to start it at every boot. See the article on [[Xorg input hotplugging]] for full details.<br />
<br />
Note: To start hal there must be a dbus user and group: To do so enter the following commands as root<br />
<br />
# /usr/sbin/groupadd -g 81 dbus<br />
# /usr/sbin/useradd -c 'System message bus' -u 81 -g dbus -d '/' -s /bin/false dbus<br />
<br />
<br />
2) '''Disable input hotplugging''' by adding ''Option &quot;AutoAddDevices&quot; &quot;False&quot;'' to ServerFlags in /etc/X11/xorg.conf. This will skip devices detected by hal and will use your keyboard/mouse configuration from xorg.conf<br />
# nano /etc/X11/xorg.conf<br />
and add the following<br />
Section &quot;ServerFlags&quot;<br />
Option &quot;AutoAddDevices&quot; &quot;False&quot;<br />
EndSection<br />
<br />
====C: Test X====<br />
<br />
First read the warning about input hotplugging in the previous section. To test the X server, run the '''X''' script with the ''-config'' flag against the ''path/to/xorg.conf'' file. e.g.:<br />
# X -config /etc/X11/xorg.conf<br />
'''X''' should start with the white hollow vector '''X''' in the center of the screen, which should respond to mouse, trackpoint or touchpad movement. Use CTRL-Alt-Backspace to exit '''X'''.<br />
<br />
====In case of errors====<br />
<br />
Inspect your config file:<br />
<br />
# nano /etc/X11/xorg.conf<br />
<br />
Ensure the Xorg -configure script has correctly specified your video driver. e.g.:<br />
Section &quot;Device&quot;<br />
<br />
...<br />
<br />
Driver &quot;savage&quot;<br />
<br />
...<br />
<br />
EndSection<br />
<br />
Ensure there are horizontal sync and vertical refresh specs under section &quot;Monitor&quot;. If not, add them:<br />
Section &quot;Monitor&quot;<br />
Identifier &quot;Monitor0&quot;<br />
VendorName &quot;Monitor Vendor&quot;<br />
ModelName &quot;Monitor Model&quot;<br />
HorizSync 30.0 - 130.0 # Safe for LCD's<br />
VertRefresh 50.0 - 100.0 # Safe for LCD's and most CRT's.<br />
EndSection<br />
(If you do not know these specs, consult your monitor's documentation.)<br />
<br />
Specify your default color depth under section &quot;Screen&quot;:<br />
Section &quot;Screen&quot;<br />
Identifier &quot;Screen0&quot;<br />
Device &quot;Card0&quot;<br />
Monitor &quot;Monitor0&quot;<br />
DefaultDepth 24<br />
(Typically, this will be set to 24 for true color.)<br />
<br />
Also add your desired Modes to your &quot;Display&quot; subsection, at least under the Depth 24 header, e.g.:<br />
SubSection &quot;Display&quot;<br />
Viewport 0 0<br />
Depth 24<br />
Modes &quot;1024x768&quot; &quot;800x600&quot; &quot;640x480&quot;<br />
Add the following section, if you wish to enable eye candy which requires the composite extension: <br />
Section &quot;Extensions&quot;<br />
Option &quot;Composite&quot; &quot;Enable&quot;<br />
EndSection<br />
Try your config again, after modifying:<br />
# X -config /etc/X11/xorg.conf<br />
Detailed instructions in the [[Xorg]] article.<br />
<br />
Continue with '''[[#Simple baseline X test(if necessary)|Simple baseline X test]]'''<br />
<br />
====Set the keyboard layout====<br />
=====When input hotplugging is enabled=====<br />
# cp /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi /etc/hal/fdi/policy/<br />
# nano /etc/hal/fdi/policy/10-keymap.fdi<br />
Edit the &quot;input.xkb.layout&quot; key and possibly the &quot;input.xkb.variant&quot; key in this file.<br />
Restart hal:<br />
# /etc/rc.d/hal restart<br />
<br />
=====When input hotplugging is disabled=====<br />
Add option lines in the &quot;InputDevice&quot; section of the /etc/X11/xorg.conf file specifying the keyboard layout and variant:<br />
Option &quot;XkbLayout&quot; &quot;be&quot;<br />
Option &quot;XkbVariant&quot; &quot;&quot;<br />
<br />
For more info see the article on [[Xorg input hotplugging]].<br />
<br />
===Simple baseline X test(if necessary)===<br />
At this point, you should have xorg installed, with a suitable video driver and an /etc/X11/xorg.conf configuration file. If you want to test your configuration quickly, to ensure your ability to successfully start '''X''' from the command line before installing a complete desktop environment, you can do so by configuring ~/.xinitrc to invoke '''Xterm'''. Xterm is a very simple terminal emulator which runs in the '''X '''Server environment; it is installed as part of the base xorg packages. More advanced users who are comfortable with '''X''' configuration may choose to skip this optional step.<br />
==== Prepare for the test by configuring ~/.xinitrc====<br />
<br />
One of the main functions of this file is to dictate what '''X''' Window client is invoked with the '''/usr/bin/startx''' and/or '''/usr/bin/xinit''' program ''on a per-user basis''. (The '''startx''' script is merely a front end to the more versatile '''xinit''' command.) There are vast amounts of additional configurable specifications and commands that may also be added to ~/[[.xinitrc]] as you further customize your system. <br />
{{Box Note | '''[[.xinitrc]]''' is a so-called 'dot' (.) file. Files in a UNIX filesystem which are preceded with a dot (.) are 'hidden', and will not show up with a regular 'ls' command, usually for the sake of keeping directories tidy. Dot files may be seen by issuing '''ls -a'''. The 'rc' denotes ''Run Commands'' and simply indicates that it is a configuration file. Since it controls how a program runs, it is (although historically incorrect) also said to stand for &quot;Run Control&quot;.}}<br />
<br />
'''startx/xinit''' will start the '''X''' server and clients. To determine the client to run, '''startx/xinit''' will first look to parse a [[.xinitrc]] file in the user's home directory. In the absence of file ~/[[.xinitrc]], it defaults to the global xinitrc in the xinit library directory; /etc/X11/xinit/xinitrc, which defaults to using the TWM window manager. (Hence, if you invoke startx without a ~/[[.xinitrc]] file, a TWM session will start.) Further details in the [[.xinitrc]] wiki entry.<br />
<br />
Switch to your '''''normal, non-root''''' user:<br />
# su - ''yourusername''<br />
* /etc/skel/ contains files and directories to provide sane defaults for newly created user accounts. The name '''skel''' is derived from the word '''skeleton''', because the files it contains form the basic structure for users' home directories.<br />
* If you installed from a fresh (Core) install, it does not include the X window manager, so .xinitrc does not exist in /etc/skel. Instead, use the sample provided [[Xinitrc#A_standard_.xinitrc | here]].<br />
Copy the sample xinitrc file from /etc/skel/ to your home directory: <br />
<br />
$ cp /etc/skel/[[.xinitrc]] ~/<br />
Edit the file: <br />
$ nano ~/.xinitrc<br />
and add &quot;<code>exec xterm</code>&quot; so that it looks like this:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
exec xterm<br />
# exec wmaker<br />
# exec startkde<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
<br />
{{Box Note | ''Be sure to have only '''one''' uncommented '''exec''' line in your ~/.xinitrc''.}}<br />
Below, we shall edit this file again to specify the appropriate desktop environment/window manager of your choice.<br />
<br />
====Perform the test====<br />
<br />
Test your configurations by starting '''X''' as '''normal, non-root''' user, with:<br />
<br />
$ startx<br />
or<br />
$ xinit<br />
<br />
You should have an '''xterm''' session open up. You can test your keyboard and its layout in it.<br />
<br />
You can exit the '''X''' Server with Ctrl+Alt+Backspace, or by typing &quot;exit&quot;. If you have problems starting '''X''', you can look for errors in the /var/log/Xorg.0.log file and on the console output of the console you started '''X''' from.<br />
<br />
If you prove a properly configured /etc/X11/xorg.conf by successfully running the test, you can be assured that your DE/WM of choice will work smoothly.<br />
<br />
Advanced instructions for Xorg configuration can be found in the [[Xorg]] article.<br />
<br />
==Part IV: Installing and configuring a Desktop Environment ==<br />
While The '''X''' Window System provides the basic framework for building a ''graphical user interface'' (GUI), a '''Desktop Environment''' (DE), works atop and in conjunction with '''X''', to provide a completely functional and dynamic GUI. A DE typically provides a window manager, icons, applets, windows, toolbars, folders, wallpapers, a suite of applications and abilities like drag and drop. The particular functionalities and designs of each DE will uniquely affect your overall environment and experience. Therefore, choosing a DE is a very subjective and personal decision. Choose the best environment for ''your'' needs.<br />
<br />
* If you want something full-featured and similar to Windows and Mac OSX, '''[[#KDE|KDE]]''' is a good choice<br />
* If you want something slightly more minimalist, which follows the K.I.S.S. principle more closely, '''[[#GNOME|GNOME]]''' is a good choice<br />
* '''[[#Xfce|Xfce]]''' is generally perceived as similar to GNOME, but lighter and less demanding on system resources, yet still visually pleasing and providing a very complete environment.<br />
* '''[[#LXDE|LXDE]]''' is a minimal DE based on the Openbox window manager. It provides most things you need for a modern desktop while keeping relatively low system resource usage. LXDE is a good choice for those who want a quick way of setting up a pre-configured Openbox system.<br />
<br />
If you desire a lighter, less demanding GUI to configure manually, you may choose to simply install a '''Window Manager''', or WM. A WM controls the placement and appearance of application windows in conjunction with the X Window System but does NOT include such features as panels, applets, icons, applications, etc., by default.<br />
* Lightweight floating WM's include: [[#Openbox|'''Openbox''']], [[#Fluxbox|'''Fluxbox''']], [[#fvwm2|'''fvwm2''']], '''Windowmaker, Pekwm, and TWM'''.<br />
* If you need something completely different, try '''Awesome, ion, wmii, dwm, or xmonad'''.<br />
<br />
===Step 1: Install Fonts===<br />
At this point, you may wish to save time by installing visually pleasing, true type fonts, before installing a desktop environment/window manager. Dejavu and bitstream-vera are good, general-purpose font sets. You may also want to have the Microsoft font sets, which are especially popular on websites. <br />
<br />
Install with:<br />
# pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera<br />
<br />
===Step 2: ~/.xinitrc (again)===<br />
<br />
As '''non-root user''', edit your /home/username/.xinitrc to specify the DE you wish to use. This will allow you to use '''startx/xinit''' from the shell, in the future, to open your DE/WM of choice:<br />
<br />
$ nano ~/.xinitrc<br />
<br />
Uncomment or add the ''''exec''' ..' line of the appropriate desktop environment/window manager. Some examples are below:<br />
<br />
For the Xfce4 desktop environment:<br />
exec startxfce4 <br />
<br />
For the KDE desktop environment:<br />
exec startkde<br />
A '''startkde''' or '''startxfce4''' command starts the KDE or Xfce4 desktop environment. This command does not finish until you logout of the DE. Normally the shell would wait for KDE to finish, then run the next command. The &quot;exec&quot; prefix to this command tells the shell that this is the last command, so the shell does not need to wait to run a subsequent command.<br />
<br />
Remember to have only one uncommented '''exec''' line in your ~/.xinitrc. <br />
<br />
Continue below, installing the DE/WM of your choice.<br />
<br />
* [[#GNOME|'''GNOME''']]<br />
* [[#KDE|'''KDE''']]<br />
* [[#Xfce|'''Xfce''']]<br />
* [[#LXDE|'''LXDE''']]<br />
* [[#Openbox|'''Openbox''']]<br />
* [[#Fluxbox|'''Fluxbox''']]<br />
* [[#fvwm2|'''fvwm2''']]<br />
<br />
===Step 3: Install a Desktop Environment===<br />
====GNOME====<br />
=====About GNOME=====<br />
The '''G'''NU '''N'''etwork '''O'''bject '''M'''odel '''E'''nvironment. The GNOME project provides two things: The GNOME desktop environment, an intuitive and attractive desktop for end-users, and the GNOME development platform, an extensive framework for building applications that integrate into the rest of the desktop.<br />
<br />
=====Installation=====<br />
Install the base GNOME environment with:<br />
# pacman -S gnome<br />
<br />
Additionally, you can install the extras:<br />
# pacman -S gnome-extra<br />
<br />
It's safe to choose all packages shown in the extra package. <br />
<br />
=====Useful DAEMONS for GNOME=====<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. Some users prefer to use the '''hal''' daemon. The '''hal''' daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The '''fam''' daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system. Both '''hal''' and '''fam''' can make life easier for the GNOME user. The hal and fam packages are installed when you install GNOME, but must be invoked to become useful.<br />
<br />
Start hal and fam:<br />
# /etc/rc.d/hal start<br />
<br />
# /etc/rc.d/fam start<br />
<br />
Add them to your /etc/rc.conf DAEMONS section, so they will be invoked at boot:<br />
# nano /etc/rc.conf<br />
<br />
DAEMONS=(syslog-ng network crond alsa '''hal fam gdm''')<br />
(If you prefer to log into the console and manually start X, leave out gdm.)<br />
<br />
<br />
You may want to install a graphical login manager. For GNOME, the '''gdm''' daemon is a good choice. <br />
<br />
As root:<br />
# pacman -S gdm<br />
<br />
As normal user, start X:<br />
$ startx<br />
or<br />
$ xinit<br />
If ~/.xinitrc is not configured for GNOME, you may always start it with '''xinit''', followed by the path to GNOME:<br />
$ xinit /usr/bin/gnome-session<br />
<br />
Advanced instructions for installing and configuring GNOME can be found in the [[Gnome]] article.<br />
<br />
Congratulations! Welcome to your GNOME desktop environment on your new Arch Linux system! You may wish to continue by viewing '''[[#Tweaks/Finishing touches|Tweaks and finishing touches]]''', or the rest of the information below. You may also be interested in the [[Post Installation Tips]] wiki article.<br />
<br />
=====Eye Candy=====<br />
By default, GNOME does not come with many themes and icons. You may wish to install some more attractive artwork for GNOME:<br />
<br />
A nice gtk (gui widget) theme engine (includes themes) is the murrine engine. Install with:<br />
# pacman -S gtk-engine-murrine<br />
<br />
Once it has been installed, select it with System -> Preferences -> Appearance -> Theme tab.<br />
<br />
The Arch Linux repositories also have a few more nice themes and engines. Install the following to see for yourself:<br />
<br />
# pacman -S gtk-engines gtk2-themes-collection gtk-aurora-engine gtk-candido-engine gtk-rezlooks-engine<br />
<br />
You can find many more themes, icons, and wallpapers at [http://www.gnome-look.org GNOME-Look].<br />
<br />
====KDE====<br />
=====About KDE=====<br />
The '''K''' '''D'''esktop '''E'''nvironment. KDE is a powerful Free Software graphical desktop environment for GNU/Linux and <code>UNIX</code> workstations. It combines ease of use, contemporary functionality, and outstanding graphical design with the technological superiority of <code>UNIX</code>-like operating systems.<br />
<br />
=====Installation=====<br />
Choose one of the following, then continue below with '''[[#Useful KDE DAEMONS|Useful KDE DAEMONS]]''': <br />
<br />
1. The package '''kde''' is the official and complete vanilla KDE 4.2 residing under the Arch [extra] repo.<br />
<br />
Install this before: <br />
# pacman -S zlib shared-mime-info<br />
Install with pacman: <br />
# pacman -S kde<br />
<br />
2. Alternatively, there exists a project called '''KDEmod''' (recently referred to collectively as the Chakra project). It is an Arch Linux exclusive, community-driven system, designed for modularity and offers a choice between KDE 3.5.10 or 4.x.x. KDEmod can be installed with pacman, after adding the proper repository to /etc/pacman.conf. The project website, including complete installation instructions, can be found at [http://kdemod.ath.cx/ http://kdemod.ath.cx/].<br />
<br />
=====Useful KDE DAEMONS=====<br />
<br />
KDE will require the '''hal''' ('''H'''ardware '''A'''bstraction '''L'''ayer) daemon. The '''kdm''' daemon is the '''K''' '''D'''isplay '''M'''anager, which provides a '''graphical login''', if desired.<br />
<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. Some users prefer to use the '''hal''' daemon. The hal daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The hal and kdm packages are installed when you install KDE, but must be invoked to become useful.<br />
-----<br />
Start hal:<br />
<br />
# /etc/rc.d/hal start<br />
<br />
{{Box Note|The hal daemon relies on, and will automatically start, the dbus daemon.}}<br />
Edit your DAEMONS array in /etc/rc.conf:<br />
# nano /etc/rc.conf<br />
Add '''hal''' to your DAEMONS array, to invoke it on boot. If you prefer a graphical login, add '''kdm''' as well: <br />
DAEMONS=(syslog-ng '''hal''' network crond alsa '''kdm''')<br />
{{Box Note|If you installed KDEmod3 instead of normal KDE, use kdm3 instead of kdm.}}<br />
<br />
*This method will start the system at runlevel 3, (/etc/inittab default, multiuser mode), and then start KDM as a daemon. <br />
<br />
*Some users prefer an alternative method of starting a display manager like KDM on boot by utilizing the /etc/inittab method and starting the system at runlevel 5. See [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]] for more.<br />
<br />
*If you prefer to log into the '''console''' at runlevel 3, and manually start X, leave out kdm, or comment it out with a bang, ( ! ).<br />
<br />
Now try starting your X Server as normal user:<br />
$ startx<br />
or<br />
$ xinit<br />
Advanced instructions for installing and configuring KDE can be found in the [[KDE]] article.<br />
<br />
Congratulations! Welcome to your KDE desktop environment on your new Arch Linux system! You may wish to continue by viewing '''[[Beginners Guide Appendix|The Beginners Guide Appendix]]''', or the rest of the information below. You may also be interested in the [[Post Installation Tips]] wiki article.<br />
<br />
====Xfce====<br />
=====About Xfce=====<br />
The cholesterol-free '''X''' environment. Xfce, like GNOME or KDE, is a desktop environment, but aims to be fast and lightweight while remaining visually appealing and easy to use. It contains a suite of apps like a root window app, window manager, file manager, panel, etc. Xfce is written using the GTK2 toolkit (like GNOME) and contains its own development environment (libraries, daemons, etc) similar to other big DEs. Unlike GNOME or KDE, Xfce is lightweight and designed more around CDE than Windows or Mac. It has a much slower development cycle, but is very stable and fast. Xfce is great for older hardware, and will perform excellently on newer machines as well.<br />
<br />
=====Installation=====<br />
Install Xfce: <br />
# pacman -S xfce4 <br />
You may also wish to install themes and extras:<br />
# pacman -S xfce4-goodies gtk2-themes-collection<br />
Note: '''xfce4-xfapplet-plugin''' (a plugin that allows the use of GNOME applets in the Xfce4 panel) is part of the '''xfce4-goodies''' group and depends on '''gnome-panel''', which in turn depends on '''gnome-desktop'''. You may wish to take this into consideration before installing, since it represents a significant number of extra dependencies.<br />
<br />
If you wish to admire 'Tips and Tricks' on login, install the '''fortune-mod''' package:<br />
# pacman -S fortune-mod<br />
<br />
=====Useful DAEMONS=====<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. Some Xfce users prefer to use the '''hal''' daemon. The hal daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The fam daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system. The hal and fam packages are installed when you install Xfce, but must be invoked to become useful.<br />
<br />
Start hal and fam:<br />
<br />
# /etc/rc.d/hal start<br />
<br />
# /etc/rc.d/fam start<br />
{{Box Note|The hal daemon relies on, and will automatically start, the dbus daemon.}}<br />
Edit your DAEMONS array in /etc/rc.conf:<br />
# nano /etc/rc.conf<br />
Add '''hal''' and '''fam''' to your DAEMONS array, to invoke them at boot.<br />
<br />
Advanced instructions for installing and configuring Xfce can be found in the [[Xfce]] article.<br />
<br />
If you wish to install one, see [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]]. Otherwise you can login in via the console and run:<br />
<br />
$ startxfce4<br />
<br />
Congratulations! Welcome to your Xfce desktop environment on your new Arch Linux system! You may also be interested in the [[Post Installation Tips]] wiki article.<br />
<br />
====LXDE====<br />
=====About LXDE=====<br />
LXDE, (for ''L''ightweight ''X''11 ''D''esktop ''E''nvironment), is a new project focused on providing a modern desktop environment which aims to be lightweight, fast, intuitive and functional while keeping system resource usage low. LXDE is quite different from other desktop environments, since each component of LXDE is a discrete and independent application, and each can be easily substituted by other programs. This modular design eliminates all unnecessary dependencies and provides more flexibility. Details and screenshots available at: http://lxde.org/ <br />
<br />
LXDE provides:<br />
# The OpenBox windowmanager<br />
# PCManFM File manager<br />
# LXpanel system panel<br />
# LXSession session manager<br />
# LXAppearance GTK+ theme switcher<br />
# GPicView image viewer<br />
# Leafpad simple text editor<br />
# XArchiver: Lightweight, fast, and desktop-independent gtk+-based file archiver<br />
# LXNM (still under development): Lightweight network manager for LXDE supporting wireless connections<br />
These lightweight and versatile tools combine for quick setup, modularity and simplicity.<br />
<br />
Install LXDE with: <br />
# pacman -S lxde<br />
Add:<br />
exec startlxde<br />
to your ~/.xinitrc and start with ''startx'' or ''xinit''<br />
<br />
Further information available at the [[LXDE]] wiki article.<br />
<br />
====*box====<br />
=====Fluxbox=====<br />
Fluxbox © is yet another windowmanager for X.<br />
It's based on the Blackbox 0.61.1 code. Fluxbox looks like blackbox and handles styles, colors, window placement and similar things exactly like blackbox (100% theme/style compability).<br />
<br />
Install Fluxbox using <br />
# pacman -S fluxbox fluxconf<br />
<br />
If you use gdm/kdm a new fluxbox session will be automatically added. Otherwise, you should modify your user's .xinitrc and add this to it:<br />
exec startfluxbox <br />
<br />
More information is available in the [[Fluxbox]] article.<br />
<br />
=====Openbox=====<br />
Openbox is a standards compliant, fast, light-weight, extensible window manager.<br />
<br />
Openbox works with your applications, and makes your desktop easier to manage. This is because the approach to its development was the opposite of what seems to be the general case for window managers. Openbox was written first to comply with standards and to work properly. Only when that was in place did the team turn to the visual interface.<br />
<br />
Openbox is fully functional as a stand-alone working environment, or can be used as a drop-in replacement for the default window manager in the GNOME or KDE desktop environments. <br />
<br />
Install openbox using<br />
# pacman -S openbox<br />
Additional configuration tools are also available, if desired:<br />
# pacman -S obconf obmenu<br />
<br />
Once openbox is installed you will get a message to move menu.xml & rc.xml to ~/.config/openbox/ in your home directory:<br />
# su - ''yourusername''<br />
$ mkdir -p ~/.config/openbox/<br />
$ cp /etc/xdg/openbox/rc.xml ~/.config/openbox/<br />
$ cp /etc/xdg/openbox/menu.xml ~/.config/openbox/<br />
<br />
'''rc.xml''' is the main configuration file for OpenBox. It may be manually edited, (or you can use OBconf). '''menu.xml''' configures the right-click menu.<br />
<br />
You may log into OpenBox via graphical login using KDM/GDM, or from the shell using '''startx''', in which case you will need to edit your ~/.xinitrc (as non-root user) and add the following:<br />
<br />
exec openbox-session<br />
You may also start OpenBox from the shell using '''xinit''':<br />
$ xinit /usr/bin/openbox-session<br />
* Openbox may also be used as the window manager for GNOME, KDE, and Xfce.<br />
For KDM there is nothing left to do; openbox is listed in the sessions menu in KDM.<br />
<br />
Some useful, lightweight programs for OpenBox are:<br />
* PyPanel or LXpanel if you want a panel<br />
* feh if you want to set the background<br />
* ROX if you want a simple file manager (also provides simple icons)<br />
* PcmanFM a lightweight but versatile file manager (also provides desktop icon functionality)<br />
* iDesk (available in [[AUR]]) for providing desktop icons<br />
* Graveman for burning CD's or DVD's<br />
<br />
More information is available in the [[Openbox]] article.<br />
<br />
====fvwm2====<br />
FVWM is an extremely powerful ICCCM-compliant multiple virtual desktop window manager for the X Window system. Development is active, and support is excellent. <br />
<br />
Install fvwm2 with<br />
# pacman -S fvwm <br />
<br />
fvwm will automatically be listed in kdm/gdm in the sessions menu. Otherwise, add <br />
exec fvwm <br />
<br />
to your user's .xinitrc.<br />
<br />
==Useful Applications==<br />
To install useful apps, codecs and plugins, see [[Useful Applications]].<br />
<br />
=APPENDIX=<br />
See [[Beginners Guide Appendix]]</div>
Potamota
https://wiki.archlinux.org/index.php?title=Allow_users_to_shutdown&diff=63857
Allow users to shutdown
2009-03-04T06:45:27Z
<p>Potamota: </p>
<hr />
<div>[[Category:Security (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Allow_users_to_shutdown}}<br />
{{i18n_entry|Italiano|Allow_users_to_shutdown (Italiano)}}<br />
{{i18n_entry|Русский|Как разрешить пользователям выключать компьютер}}<br />
{{i18n_entry|Українська|Як дозволити користувачу вимкнути комп'ютер}}<br />
{{i18n_entry|Indonesia|Shutdown_sebagai_users(Indonesia)}}<br />
{{i18n_links_end}}<br />
<br />
== The first way: setuid ==<br />
If you want the user to have the ability to shutdown or reboot you may change file permissions for the halt command. <code>reboot</code> is a symlink to <code>halt</code>, so that doesn't need to be changed. Type as root:<br />
<br />
# chmod +s /sbin/halt<br />
<br />
Note that this is considered a security threat, since the command will be executed as root and everyone will have access to it.<br />
<br />
'''Topic:''' http://bbs.archlinux.org/viewtopic.php?t=2787<br />
<br />
== The second way: sudo ==<br />
Another, generally safer option is to do this using <code>sudo</code>. First install sudo:<br />
# pacman -Sy sudo<br />
<br />
Then, as root, add the following to the end of <code>/etc/sudoers</code> using the <code>visudo</code> command. Substitute '''user''' for your username and '''hostname''' for the machine's hostname.<br />
<br />
'''user''' '''hostname'''=NOPASSWD: /sbin/shutdown -h now<br />
'''user''' '''hostname'''=NOPASSWD: /sbin/reboot<br />
<br />
or you can combine commands on a single line<br />
<br />
'''user''' '''hostname'''=NOPASSWD: /sbin/shutdown -h now,/sbin/reboot<br />
<br />
Now your user can shutdown with <code>sudo shutdown -h now</code>, and reboot with <code>reboot</code>.<br />
<br />
{{Box Note|For users wishing to power down a system <tt>poweroff</tt> or <tt>shutdown -P now</tt> may be preferable to <tt>shutdown -h now</tt> as it leaves no doubt as to the intention of the user initiated command.|}}<br />
<br />
== The third way: Gnome ==<br />
A third option, under Gnome is to perform the following commands:<br />
<br />
$ su<br />
your password<br />
# chmod +s /sbin/halt<br />
# cd /var/run<br />
# mkdir console<br />
# cd console<br />
# touch '''username'''<br />
<br />
This adds the "reboot" and "halt" options to Gnome's logout menu for the user defined. <!-- A little bit of description for what does this actually do would be very useful. --><br />
<br />
== The fourth way: Xfce ==<br />
A fourth option under XFCE, if you don't want to use shutting down using Hal, is to install sudo. Then add the following line to <code>/etc/sudoers</code> using the <code>visudo -f</code> command.<br />
<br />
* For all users:<br />
%users '''hostname'''=NOPASSWD:/usr/lib/xfce4/xfsm-shutdown-helper<br />
* For single user:<br />
'''user''' '''hostname'''=NOPASSWD:/usr/lib/xfce4/xfsm-shutdown-helper<br />
<br />
Substitute '''user''' for your username and '''hostname''' for the machine's hostname (you can use the <code>hostname</code> command to get it).<br />
<br />
This activates the "reboot" and "turn off" options to XFCE's session-manager logout dialog for the user defined.</div>
Potamota
https://wiki.archlinux.org/index.php?title=Frequently_asked_questions&diff=55738
Frequently asked questions
2008-12-17T17:42:07Z
<p>Potamota: /* Q) I installed Arch, and now I am at a bash login! What now? */</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:FAQs (English)]]<br />
{{FAQ i18n Links}}<br />
<br />
Besides the questions covered below, you may find [[The Arch Way]], [[Arch Linux]], and [[Devland]] helpful. All three contain a good deal of information about Arch Linux.<br />
<br />
= General =<br />
<br />
==Q) I am a complete GNU/Linux beginner. Should I use Arch?==<br />
'''A)''' This question has had much debate. Arch is targeted at more-advanced GNU/Linux users, but some people feel "Arch is a good place to start". If you are a beginner and want to use Arch, just be warned that you must be willing to learn as well as accept the fact that Arch is largely a do-it-yourself distribution. It is the user who assembles the system, and controls what it will be. Before asking any question, do your own independent research by googling, searching the Wiki, and searching the forum (and reading past FAQs). If you do that, you should be fine. Also know that many people do not want to answer the same basic questions over and over, so you are exposing yourself to that environment. ''There is a reason these resources were created/made available to you in the first place.'' Many thousands of ''volunteered'' hours have been spent compiling this excellent information. Recommended reading: The Arch Linux [[Beginners Guide|Beginners' Guide]].<br />
<br />
==Q) I really like Arch, except the development team needs to implement ''feature X''.==<br />
'''A)''' Before going further, did you read [[The Arch Way]]? Have you provided the feature/solution? Does it conform to the Arch philosophy of ''minimalism'' and ''code-correctness over convenience''? Get involved, contribute your code/solution to the community. If it is well regarded by the community and development team, perhaps it will be merged. The Arch community thrives on contribution and sharing of code and tools.<br />
<br />
==Q) When will the new release be made?==<br />
'''A)''' Arch Linux releases are merely a snapshot of the /core repository, combined with various features or modifications to the installer script itself. The rolling release model keeps every Arch Linux system current and on the bleeding edge by issuing one command.<br />
<br />
For this reason, releases are not terribly important in Arch, because the rolling-release system makes new releases out of date as soon as a package has been updated. If you are looking to obtain the latest Arch Linux release, you do not need to reinstall. You simply run the ''pacman -Syu'' command and your system will be identical to what you would get with a brand-new install.<br />
<br />
For this same reason, new Arch Linux releases are not typically full of new and exciting features. New and exciting features are released as needed with the packages that are updated, and can be obtained immediately via ''pacman -Syu''.<br />
<br />
==Q) Is Arch Linux a stable distro? Will I get frequent breakage? ==<br />
'''A)''' The long and short answer is: It is largely as stable as ''you'' make it. <br />
<br />
You assemble your own Arch system, atop the simple base environment, and you control system upgrades. Obviously, a larger, more bloated system incorporating multitudes of packages, multiple toolkits and desktop environments would be more likely to experience configuration issues due to upstream changes than a slimmer, more simple system would. General UNIX competence, good system maintenance and upgrade practices also play a large role in system stability. Also recall that Arch packages are predominantly unpatched, so most issues are inherently upstream.<br />
Therefore, it is ''the user'' who is ultimately responsible for the stability of his own rolling release system. The user decides when to upgrade, and merges necessary changes when required. If the the user reaches out to the community for help, it is often provided in a timely manner. The difference between Arch and other distributions in this regard is that Arch is truly a 'do-it-yourself' distro; complaints of breakage are misguided and unproductive, since upstream changes are not the responsibility of Arch devs.<br />
<br />
==Q) What exactly ''is'' this 'BSD-style' init framework I keep hearing about? ==<br />
<br />
Part of BSD's 30+ year heritage is the simple init framework that it has incorporated and which has remained largely unchanged. (The SysV init implemented on GNU/Linux systems came much later.) The main difference is that Arch's BSD-style init uses a single file (/etc/rc.conf) to point to scripts within a single directory (etc/rc.d/) for all system services, regardless of runlevel. A sysV init on the other hand would use a directory for each runlevel:/etc/rc.0,1,2,3,4,5,6, with a convoluted array of symlinks within the directory; one for each service, and each symlink pointing to a corresponding script in the /etc/init.d/ directory. Needless to say, the SysV method is much more complex; it could easily contain dozens of symlinks in each /etc/rc. directory. Keeping in line with its simple philosophy, Arch uses the BSD-style init.<br />
<br />
==Q) Arch needs more press (i.e. advertisement)==<br />
'''A)''' Arch gets plenty of press as it is. The goal of Arch Linux is not to be large. The goal is to provide an elegant, minimalist and bleeding edge distribution focused on simplicity and code-correctness. Growth occurs naturally amongst the target user base. Trying to force growth will just cause problems.<br />
<br />
Similarly, the development model does not restrict natural growth. More users might mean more devs to work on Arch Linux. This may cause some organizational issues at the "top", but those will be dealt with when they arrive.<br />
<br />
<br />
<br />
==Q) Arch needs more devs==<br />
'''A)''' Possibly so. Feel free to volunteer your time! Visit the forums, IRC channel, and mailing lists, and see what needs to be done.<br />
There is always a need for documentation; contribute to the wiki.<br />
<br />
==Q) Why is Arch so slow? I thought it's supposed to be fast!==<br />
'''A)''' Make sure that your hostname is correctly set in /etc/hosts (i.e., that it matches the hostname in /etc/rc.conf. Have a look at "Configure the System" in The [[Beginners_Guide]]). If the hostnames do not match, applications may start up very slowly.<br />
<br />
==Q) Why is my internet so slow compared to other operating systems?==<br />
'''A)''' Is your network configured correctly? Have you double checked your /etc/rc.conf /etc/hosts and /etc/resolv.conf? Have a look at "Configure the System" in The [[Beginners_Guide]].<br />
<br />
=Package Management=<br />
<br />
==Q) I've found an error with Package X. What should I do?==<br />
'''A)''' First, you need to figure out if this error is something the Arch team can fix. Sometimes it's not (that Firefox crash may be the fault of the Mozilla team) - this is called an ''upstream error''. If it is an Arch problem, there is a series of steps you can take:<br />
#Search the forums for information. See if anyone else has noticed it.<br />
#Notify the package maintainer. Try a "pacman -Qi <package name>" for this info.<br />
#Post a bug report with detailed information at http://bugs.archlinux.org.<br />
#If you'd like, write a forum post detailing the problem and the fact that you have reported it already. This will help prevent a lot of people from reporting the same error.<br />
<br />
==Q) Will Arch have a database for pacman?==<br />
'''A)''' Possibly. There is discussion over the issue. <br><br />
http://bbs.archlinux.org/viewtopic.php?id=11193 <br><br />
http://bbs.archlinux.org/viewtopic.php?id=10898 <br><br />
Look at http://bugs.archlinux.org/task/5328, too.<br />
<br />
==Q) Arch packages need to use a unique naming convention. .pkg.tar.gz is too long and/or confusing==<br />
'''A)''' This has been discussed on the Arch mailing list. Some proposed a .pac file extension. As far as is currently known, there is no plan to change the package extension.<br />
As Tobias Kieslich, one of the Arch devs, put it, "A package '''is''' a gzipped tarball! And it can be opened, investigated and manipulated by any tar-capable application. Moreover, the mime-type is automatically detected correctly by most applications."<br />
<br />
==Q) Pacman needs a library so other applications can easily access package information==<br />
'''A)''' Since version 3.0.0, pacman has been the front-end to libalpm, the "Arch Linux Package Management" library. This library allows alternative front-ends to be written (for instance, a GUI front-end).<br />
<br />
==Q) Why doesn't Pacman have an official GUI front-end?==<br />
'''A)''' Did you read [[The Arch Way]] and [[Arch Linux]] and [[Devland]]?<br />
The answer is basically that the Arch dev team will not be providing one. Feel free to use one of those developed by users. There is a nice list of them on the [[UserContributionsPage]] in the links section, and a selective list on [[Pacman GUI Frontends]].<br />
<br />
==Q) Pacman needs Feature X!==<br />
'''A)''' Did you read [[The Arch Way]] and [[Arch Linux]] and [[Devland]]?<br />
The Arch philosophy is "Keep It Simple". If you think the idea has merit, and does not violate this simple litany, then by all means, discuss it on the forum [http://bbs.archlinux.org/ here]. You might also like to check [http://bugs.archlinux.org here]; it's a place for feature requests if you find it is important.<br />
<br />
However, the best way to get a feature added to Pacman or Arch Linux is to implement it yourself. There's no telling whether the patch will be officially accepted, but others will appreciate and test your effort.<br />
<br />
==Q) Arch needs a stable package branch==<br />
'''A)'''<br />
Never say never.<br />
Some of the many discussions on the topic: <br><br />
http://bbs.archlinux.org/viewtopic.php?id=11288<br />
<br><br />
http://archlinux.org/pipermail/arch/2007-November/016048.html<br />
<br />
==Q) What's the difference between all these repositories?==<br />
'''A)''' See [[The Arch Linux Repositories]].<br />
<br />
<br />
<br />
==Q) I just installed Package X. How do I start it?==<br />
'''A)''' If you're using a desktop environment like KDE or GNOME, the program should automatically show up in your menu. If you're trying to run the program from a terminal and don't know the binary name, try executing "pacman -Ql packagename | grep bin". A common problem for packages like Firefox or OpenOffice is that they are installed to /opt, which is not in your $PATH - you can "source /etc/profile" or logout/login to fix this.<br />
<br />
=Installation=<br />
<br />
==Q) Arch needs a better installer. Maybe a GUI installer.==<br />
'''A)''' The discussion of a "better" installer is a subjective opinion. The best way to cope with these issues it to fit the installer to "the Arch way". If this opinion on a better installer is backed with more-concrete arguments, it might be taken into account for further development of the installer. Since installation doesn't occur often (see the question above on rolling release), it is not a high priority for developers or users.<br />
However, two unofficial methods exist: [http://archie.dotsrc.org/ Archie Live CD] for XFCE (other desktops in development) and [http://user-contributions.org/wikis/userwiki/index.php?title=Arch_Linux_Office_Install_CD Arch Linux Office Install CD] for KDE.<br />
<br />
==Q) I installed Arch, and now I am at a bash login! What now?==<br />
'''A)''' Have a look at the Arch Linux [[Beginners_Guide]]<br />
<br />
==Q) Arch is touted as a distribution which is built up from a minimal base system, installing only what is required by the user. Isn't this possible with virtually any distribution? What makes Arch unique in this regard?==<br />
<br />
'''A)''' A few distributions may provide minimal installation methods similar in design to the Arch installation process. However, a few points must be noted:<br />
# Arch has been fundamentally designed as a lightweight, minimal environment upon which to build. <br />
# Whether the FTP or Core images are used, the only way to install Arch is by building up from this minimal base.<br />
# The installation, as well as the entire distribution is inherently a K.I.S.S. design approach, which makes it uniquely suitable for its target base of users.<br />
# The simple Arch installer is designed for a high level of transparency and the base system is manually configured by the user to their needed specifications.<br />
# Arch provides thoroughly complete documentation to guide one through this process of system assembly.<br />
<br />
=Other=<br />
<br />
==Q) I get an error every time I use pacman saying 'warning: current locale is invalid; using default "C" locale'. What do I do?==<br />
'''A)''' As the error message says, your locale isn't correctly configured. Have a look at the [[Configuring locales|locale configuration wiki page]].<br />
<br />
==Q) How do I automount/mount something? ==<br />
'''A)''' If you use GNOME, install gnome-volume-manager:<br />
pacman -Sy gnome-volume-manager<br />
<br />
Now add yourself to the storage group:<br />
gpasswd -a ''your_user'' storage<br />
<br />
If you don't want to use gnome-volume-manager, check out the [[AutoFS_HowTo|AutoFS HowTo]].<br />
<br />
==Q) How do I connect to my wireless network?==<br />
'''A)''' See [[Wireless Setup]].<br />
<br />
==Q) How do I connect to my wired network?==<br />
'''A)''' See [[Configuring network]].<br />
<br />
==Q) What is this AUR thing I keep hearing about?==<br />
'''A)''' See [[AUR Q & A]].<br />
<br />
==Q) Why do I get a green screen whenever I try to watch a video?==<br />
'''A)''' Your colour depth is set wrong. It may need to be 24 instead of 16, for example.<br />
<br />
==Q) Spellcheck is marking all of my text as incorrect!==<br />
'''A)''' Have you installed an aspell dictionary? Use <tt>pacman -Ss aspell</tt> to see the available dictionaries.</div>
Potamota
https://wiki.archlinux.org/index.php?title=Frequently_asked_questions&diff=55737
Frequently asked questions
2008-12-17T17:41:33Z
<p>Potamota: /* Q) Why is Arch so slow? I thought it's supposed to be fast! */</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:FAQs (English)]]<br />
{{FAQ i18n Links}}<br />
<br />
Besides the questions covered below, you may find [[The Arch Way]], [[Arch Linux]], and [[Devland]] helpful. All three contain a good deal of information about Arch Linux.<br />
<br />
= General =<br />
<br />
==Q) I am a complete GNU/Linux beginner. Should I use Arch?==<br />
'''A)''' This question has had much debate. Arch is targeted at more-advanced GNU/Linux users, but some people feel "Arch is a good place to start". If you are a beginner and want to use Arch, just be warned that you must be willing to learn as well as accept the fact that Arch is largely a do-it-yourself distribution. It is the user who assembles the system, and controls what it will be. Before asking any question, do your own independent research by googling, searching the Wiki, and searching the forum (and reading past FAQs). If you do that, you should be fine. Also know that many people do not want to answer the same basic questions over and over, so you are exposing yourself to that environment. ''There is a reason these resources were created/made available to you in the first place.'' Many thousands of ''volunteered'' hours have been spent compiling this excellent information. Recommended reading: The Arch Linux [[Beginners Guide|Beginners' Guide]].<br />
<br />
==Q) I really like Arch, except the development team needs to implement ''feature X''.==<br />
'''A)''' Before going further, did you read [[The Arch Way]]? Have you provided the feature/solution? Does it conform to the Arch philosophy of ''minimalism'' and ''code-correctness over convenience''? Get involved, contribute your code/solution to the community. If it is well regarded by the community and development team, perhaps it will be merged. The Arch community thrives on contribution and sharing of code and tools.<br />
<br />
==Q) When will the new release be made?==<br />
'''A)''' Arch Linux releases are merely a snapshot of the /core repository, combined with various features or modifications to the installer script itself. The rolling release model keeps every Arch Linux system current and on the bleeding edge by issuing one command.<br />
<br />
For this reason, releases are not terribly important in Arch, because the rolling-release system makes new releases out of date as soon as a package has been updated. If you are looking to obtain the latest Arch Linux release, you do not need to reinstall. You simply run the ''pacman -Syu'' command and your system will be identical to what you would get with a brand-new install.<br />
<br />
For this same reason, new Arch Linux releases are not typically full of new and exciting features. New and exciting features are released as needed with the packages that are updated, and can be obtained immediately via ''pacman -Syu''.<br />
<br />
==Q) Is Arch Linux a stable distro? Will I get frequent breakage? ==<br />
'''A)''' The long and short answer is: It is largely as stable as ''you'' make it. <br />
<br />
You assemble your own Arch system, atop the simple base environment, and you control system upgrades. Obviously, a larger, more bloated system incorporating multitudes of packages, multiple toolkits and desktop environments would be more likely to experience configuration issues due to upstream changes than a slimmer, more simple system would. General UNIX competence, good system maintenance and upgrade practices also play a large role in system stability. Also recall that Arch packages are predominantly unpatched, so most issues are inherently upstream.<br />
Therefore, it is ''the user'' who is ultimately responsible for the stability of his own rolling release system. The user decides when to upgrade, and merges necessary changes when required. If the the user reaches out to the community for help, it is often provided in a timely manner. The difference between Arch and other distributions in this regard is that Arch is truly a 'do-it-yourself' distro; complaints of breakage are misguided and unproductive, since upstream changes are not the responsibility of Arch devs.<br />
<br />
==Q) What exactly ''is'' this 'BSD-style' init framework I keep hearing about? ==<br />
<br />
Part of BSD's 30+ year heritage is the simple init framework that it has incorporated and which has remained largely unchanged. (The SysV init implemented on GNU/Linux systems came much later.) The main difference is that Arch's BSD-style init uses a single file (/etc/rc.conf) to point to scripts within a single directory (etc/rc.d/) for all system services, regardless of runlevel. A sysV init on the other hand would use a directory for each runlevel:/etc/rc.0,1,2,3,4,5,6, with a convoluted array of symlinks within the directory; one for each service, and each symlink pointing to a corresponding script in the /etc/init.d/ directory. Needless to say, the SysV method is much more complex; it could easily contain dozens of symlinks in each /etc/rc. directory. Keeping in line with its simple philosophy, Arch uses the BSD-style init.<br />
<br />
==Q) Arch needs more press (i.e. advertisement)==<br />
'''A)''' Arch gets plenty of press as it is. The goal of Arch Linux is not to be large. The goal is to provide an elegant, minimalist and bleeding edge distribution focused on simplicity and code-correctness. Growth occurs naturally amongst the target user base. Trying to force growth will just cause problems.<br />
<br />
Similarly, the development model does not restrict natural growth. More users might mean more devs to work on Arch Linux. This may cause some organizational issues at the "top", but those will be dealt with when they arrive.<br />
<br />
<br />
<br />
==Q) Arch needs more devs==<br />
'''A)''' Possibly so. Feel free to volunteer your time! Visit the forums, IRC channel, and mailing lists, and see what needs to be done.<br />
There is always a need for documentation; contribute to the wiki.<br />
<br />
==Q) Why is Arch so slow? I thought it's supposed to be fast!==<br />
'''A)''' Make sure that your hostname is correctly set in /etc/hosts (i.e., that it matches the hostname in /etc/rc.conf. Have a look at "Configure the System" in The [[Beginners_Guide]]). If the hostnames do not match, applications may start up very slowly.<br />
<br />
==Q) Why is my internet so slow compared to other operating systems?==<br />
'''A)''' Is your network configured correctly? Have you double checked your /etc/rc.conf /etc/hosts and /etc/resolv.conf? Have a look at "Configure the System" in The [[Beginners_Guide]].<br />
<br />
=Package Management=<br />
<br />
==Q) I've found an error with Package X. What should I do?==<br />
'''A)''' First, you need to figure out if this error is something the Arch team can fix. Sometimes it's not (that Firefox crash may be the fault of the Mozilla team) - this is called an ''upstream error''. If it is an Arch problem, there is a series of steps you can take:<br />
#Search the forums for information. See if anyone else has noticed it.<br />
#Notify the package maintainer. Try a "pacman -Qi <package name>" for this info.<br />
#Post a bug report with detailed information at http://bugs.archlinux.org.<br />
#If you'd like, write a forum post detailing the problem and the fact that you have reported it already. This will help prevent a lot of people from reporting the same error.<br />
<br />
==Q) Will Arch have a database for pacman?==<br />
'''A)''' Possibly. There is discussion over the issue. <br><br />
http://bbs.archlinux.org/viewtopic.php?id=11193 <br><br />
http://bbs.archlinux.org/viewtopic.php?id=10898 <br><br />
Look at http://bugs.archlinux.org/task/5328, too.<br />
<br />
==Q) Arch packages need to use a unique naming convention. .pkg.tar.gz is too long and/or confusing==<br />
'''A)''' This has been discussed on the Arch mailing list. Some proposed a .pac file extension. As far as is currently known, there is no plan to change the package extension.<br />
As Tobias Kieslich, one of the Arch devs, put it, "A package '''is''' a gzipped tarball! And it can be opened, investigated and manipulated by any tar-capable application. Moreover, the mime-type is automatically detected correctly by most applications."<br />
<br />
==Q) Pacman needs a library so other applications can easily access package information==<br />
'''A)''' Since version 3.0.0, pacman has been the front-end to libalpm, the "Arch Linux Package Management" library. This library allows alternative front-ends to be written (for instance, a GUI front-end).<br />
<br />
==Q) Why doesn't Pacman have an official GUI front-end?==<br />
'''A)''' Did you read [[The Arch Way]] and [[Arch Linux]] and [[Devland]]?<br />
The answer is basically that the Arch dev team will not be providing one. Feel free to use one of those developed by users. There is a nice list of them on the [[UserContributionsPage]] in the links section, and a selective list on [[Pacman GUI Frontends]].<br />
<br />
==Q) Pacman needs Feature X!==<br />
'''A)''' Did you read [[The Arch Way]] and [[Arch Linux]] and [[Devland]]?<br />
The Arch philosophy is "Keep It Simple". If you think the idea has merit, and does not violate this simple litany, then by all means, discuss it on the forum [http://bbs.archlinux.org/ here]. You might also like to check [http://bugs.archlinux.org here]; it's a place for feature requests if you find it is important.<br />
<br />
However, the best way to get a feature added to Pacman or Arch Linux is to implement it yourself. There's no telling whether the patch will be officially accepted, but others will appreciate and test your effort.<br />
<br />
==Q) Arch needs a stable package branch==<br />
'''A)'''<br />
Never say never.<br />
Some of the many discussions on the topic: <br><br />
http://bbs.archlinux.org/viewtopic.php?id=11288<br />
<br><br />
http://archlinux.org/pipermail/arch/2007-November/016048.html<br />
<br />
==Q) What's the difference between all these repositories?==<br />
'''A)''' See [[The Arch Linux Repositories]].<br />
<br />
<br />
<br />
==Q) I just installed Package X. How do I start it?==<br />
'''A)''' If you're using a desktop environment like KDE or GNOME, the program should automatically show up in your menu. If you're trying to run the program from a terminal and don't know the binary name, try executing "pacman -Ql packagename | grep bin". A common problem for packages like Firefox or OpenOffice is that they are installed to /opt, which is not in your $PATH - you can "source /etc/profile" or logout/login to fix this.<br />
<br />
=Installation=<br />
<br />
==Q) Arch needs a better installer. Maybe a GUI installer.==<br />
'''A)''' The discussion of a "better" installer is a subjective opinion. The best way to cope with these issues it to fit the installer to "the Arch way". If this opinion on a better installer is backed with more-concrete arguments, it might be taken into account for further development of the installer. Since installation doesn't occur often (see the question above on rolling release), it is not a high priority for developers or users.<br />
However, two unofficial methods exist: [http://archie.dotsrc.org/ Archie Live CD] for XFCE (other desktops in development) and [http://user-contributions.org/wikis/userwiki/index.php?title=Arch_Linux_Office_Install_CD Arch Linux Office Install CD] for KDE.<br />
<br />
==Q) I installed Arch, and now I am at a bash login! What now?==<br />
'''A)''' Have a look at the Arch Linux [[Beginner's Guide]]<br />
==Q) Arch is touted as a distribution which is built up from a minimal base system, installing only what is required by the user. Isn't this possible with virtually any distribution? What makes Arch unique in this regard?==<br />
<br />
'''A)''' A few distributions may provide minimal installation methods similar in design to the Arch installation process. However, a few points must be noted:<br />
# Arch has been fundamentally designed as a lightweight, minimal environment upon which to build. <br />
# Whether the FTP or Core images are used, the only way to install Arch is by building up from this minimal base.<br />
# The installation, as well as the entire distribution is inherently a K.I.S.S. design approach, which makes it uniquely suitable for its target base of users.<br />
# The simple Arch installer is designed for a high level of transparency and the base system is manually configured by the user to their needed specifications.<br />
# Arch provides thoroughly complete documentation to guide one through this process of system assembly.<br />
<br />
=Other=<br />
<br />
==Q) I get an error every time I use pacman saying 'warning: current locale is invalid; using default "C" locale'. What do I do?==<br />
'''A)''' As the error message says, your locale isn't correctly configured. Have a look at the [[Configuring locales|locale configuration wiki page]].<br />
<br />
==Q) How do I automount/mount something? ==<br />
'''A)''' If you use GNOME, install gnome-volume-manager:<br />
pacman -Sy gnome-volume-manager<br />
<br />
Now add yourself to the storage group:<br />
gpasswd -a ''your_user'' storage<br />
<br />
If you don't want to use gnome-volume-manager, check out the [[AutoFS_HowTo|AutoFS HowTo]].<br />
<br />
==Q) How do I connect to my wireless network?==<br />
'''A)''' See [[Wireless Setup]].<br />
<br />
==Q) How do I connect to my wired network?==<br />
'''A)''' See [[Configuring network]].<br />
<br />
==Q) What is this AUR thing I keep hearing about?==<br />
'''A)''' See [[AUR Q & A]].<br />
<br />
==Q) Why do I get a green screen whenever I try to watch a video?==<br />
'''A)''' Your colour depth is set wrong. It may need to be 24 instead of 16, for example.<br />
<br />
==Q) Spellcheck is marking all of my text as incorrect!==<br />
'''A)''' Have you installed an aspell dictionary? Use <tt>pacman -Ss aspell</tt> to see the available dictionaries.</div>
Potamota
https://wiki.archlinux.org/index.php?title=Frequently_asked_questions&diff=55736
Frequently asked questions
2008-12-17T17:40:28Z
<p>Potamota: /* Q) Why is my internet so slow compared to other operating systems? */</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:FAQs (English)]]<br />
{{FAQ i18n Links}}<br />
<br />
Besides the questions covered below, you may find [[The Arch Way]], [[Arch Linux]], and [[Devland]] helpful. All three contain a good deal of information about Arch Linux.<br />
<br />
= General =<br />
<br />
==Q) I am a complete GNU/Linux beginner. Should I use Arch?==<br />
'''A)''' This question has had much debate. Arch is targeted at more-advanced GNU/Linux users, but some people feel "Arch is a good place to start". If you are a beginner and want to use Arch, just be warned that you must be willing to learn as well as accept the fact that Arch is largely a do-it-yourself distribution. It is the user who assembles the system, and controls what it will be. Before asking any question, do your own independent research by googling, searching the Wiki, and searching the forum (and reading past FAQs). If you do that, you should be fine. Also know that many people do not want to answer the same basic questions over and over, so you are exposing yourself to that environment. ''There is a reason these resources were created/made available to you in the first place.'' Many thousands of ''volunteered'' hours have been spent compiling this excellent information. Recommended reading: The Arch Linux [[Beginners Guide|Beginners' Guide]].<br />
<br />
==Q) I really like Arch, except the development team needs to implement ''feature X''.==<br />
'''A)''' Before going further, did you read [[The Arch Way]]? Have you provided the feature/solution? Does it conform to the Arch philosophy of ''minimalism'' and ''code-correctness over convenience''? Get involved, contribute your code/solution to the community. If it is well regarded by the community and development team, perhaps it will be merged. The Arch community thrives on contribution and sharing of code and tools.<br />
<br />
==Q) When will the new release be made?==<br />
'''A)''' Arch Linux releases are merely a snapshot of the /core repository, combined with various features or modifications to the installer script itself. The rolling release model keeps every Arch Linux system current and on the bleeding edge by issuing one command.<br />
<br />
For this reason, releases are not terribly important in Arch, because the rolling-release system makes new releases out of date as soon as a package has been updated. If you are looking to obtain the latest Arch Linux release, you do not need to reinstall. You simply run the ''pacman -Syu'' command and your system will be identical to what you would get with a brand-new install.<br />
<br />
For this same reason, new Arch Linux releases are not typically full of new and exciting features. New and exciting features are released as needed with the packages that are updated, and can be obtained immediately via ''pacman -Syu''.<br />
<br />
==Q) Is Arch Linux a stable distro? Will I get frequent breakage? ==<br />
'''A)''' The long and short answer is: It is largely as stable as ''you'' make it. <br />
<br />
You assemble your own Arch system, atop the simple base environment, and you control system upgrades. Obviously, a larger, more bloated system incorporating multitudes of packages, multiple toolkits and desktop environments would be more likely to experience configuration issues due to upstream changes than a slimmer, more simple system would. General UNIX competence, good system maintenance and upgrade practices also play a large role in system stability. Also recall that Arch packages are predominantly unpatched, so most issues are inherently upstream.<br />
Therefore, it is ''the user'' who is ultimately responsible for the stability of his own rolling release system. The user decides when to upgrade, and merges necessary changes when required. If the the user reaches out to the community for help, it is often provided in a timely manner. The difference between Arch and other distributions in this regard is that Arch is truly a 'do-it-yourself' distro; complaints of breakage are misguided and unproductive, since upstream changes are not the responsibility of Arch devs.<br />
<br />
==Q) What exactly ''is'' this 'BSD-style' init framework I keep hearing about? ==<br />
<br />
Part of BSD's 30+ year heritage is the simple init framework that it has incorporated and which has remained largely unchanged. (The SysV init implemented on GNU/Linux systems came much later.) The main difference is that Arch's BSD-style init uses a single file (/etc/rc.conf) to point to scripts within a single directory (etc/rc.d/) for all system services, regardless of runlevel. A sysV init on the other hand would use a directory for each runlevel:/etc/rc.0,1,2,3,4,5,6, with a convoluted array of symlinks within the directory; one for each service, and each symlink pointing to a corresponding script in the /etc/init.d/ directory. Needless to say, the SysV method is much more complex; it could easily contain dozens of symlinks in each /etc/rc. directory. Keeping in line with its simple philosophy, Arch uses the BSD-style init.<br />
<br />
==Q) Arch needs more press (i.e. advertisement)==<br />
'''A)''' Arch gets plenty of press as it is. The goal of Arch Linux is not to be large. The goal is to provide an elegant, minimalist and bleeding edge distribution focused on simplicity and code-correctness. Growth occurs naturally amongst the target user base. Trying to force growth will just cause problems.<br />
<br />
Similarly, the development model does not restrict natural growth. More users might mean more devs to work on Arch Linux. This may cause some organizational issues at the "top", but those will be dealt with when they arrive.<br />
<br />
<br />
<br />
==Q) Arch needs more devs==<br />
'''A)''' Possibly so. Feel free to volunteer your time! Visit the forums, IRC channel, and mailing lists, and see what needs to be done.<br />
There is always a need for documentation; contribute to the wiki.<br />
<br />
==Q) Why is Arch so slow? I thought it's supposed to be fast!==<br />
'''A)''' Make sure that your hostname is correctly set in /etc/hosts (i.e., that it matches the hostname in /etc/rc.conf. Have a look at "Configure the System" in The [[Beginner's Guide]]). If the hostnames do not match, applications may start up very slowly.<br />
<br />
==Q) Why is my internet so slow compared to other operating systems?==<br />
'''A)''' Is your network configured correctly? Have you double checked your /etc/rc.conf /etc/hosts and /etc/resolv.conf? Have a look at "Configure the System" in The [[Beginners_Guide]].<br />
<br />
=Package Management=<br />
<br />
==Q) I've found an error with Package X. What should I do?==<br />
'''A)''' First, you need to figure out if this error is something the Arch team can fix. Sometimes it's not (that Firefox crash may be the fault of the Mozilla team) - this is called an ''upstream error''. If it is an Arch problem, there is a series of steps you can take:<br />
#Search the forums for information. See if anyone else has noticed it.<br />
#Notify the package maintainer. Try a "pacman -Qi <package name>" for this info.<br />
#Post a bug report with detailed information at http://bugs.archlinux.org.<br />
#If you'd like, write a forum post detailing the problem and the fact that you have reported it already. This will help prevent a lot of people from reporting the same error.<br />
<br />
==Q) Will Arch have a database for pacman?==<br />
'''A)''' Possibly. There is discussion over the issue. <br><br />
http://bbs.archlinux.org/viewtopic.php?id=11193 <br><br />
http://bbs.archlinux.org/viewtopic.php?id=10898 <br><br />
Look at http://bugs.archlinux.org/task/5328, too.<br />
<br />
==Q) Arch packages need to use a unique naming convention. .pkg.tar.gz is too long and/or confusing==<br />
'''A)''' This has been discussed on the Arch mailing list. Some proposed a .pac file extension. As far as is currently known, there is no plan to change the package extension.<br />
As Tobias Kieslich, one of the Arch devs, put it, "A package '''is''' a gzipped tarball! And it can be opened, investigated and manipulated by any tar-capable application. Moreover, the mime-type is automatically detected correctly by most applications."<br />
<br />
==Q) Pacman needs a library so other applications can easily access package information==<br />
'''A)''' Since version 3.0.0, pacman has been the front-end to libalpm, the "Arch Linux Package Management" library. This library allows alternative front-ends to be written (for instance, a GUI front-end).<br />
<br />
==Q) Why doesn't Pacman have an official GUI front-end?==<br />
'''A)''' Did you read [[The Arch Way]] and [[Arch Linux]] and [[Devland]]?<br />
The answer is basically that the Arch dev team will not be providing one. Feel free to use one of those developed by users. There is a nice list of them on the [[UserContributionsPage]] in the links section, and a selective list on [[Pacman GUI Frontends]].<br />
<br />
==Q) Pacman needs Feature X!==<br />
'''A)''' Did you read [[The Arch Way]] and [[Arch Linux]] and [[Devland]]?<br />
The Arch philosophy is "Keep It Simple". If you think the idea has merit, and does not violate this simple litany, then by all means, discuss it on the forum [http://bbs.archlinux.org/ here]. You might also like to check [http://bugs.archlinux.org here]; it's a place for feature requests if you find it is important.<br />
<br />
However, the best way to get a feature added to Pacman or Arch Linux is to implement it yourself. There's no telling whether the patch will be officially accepted, but others will appreciate and test your effort.<br />
<br />
==Q) Arch needs a stable package branch==<br />
'''A)'''<br />
Never say never.<br />
Some of the many discussions on the topic: <br><br />
http://bbs.archlinux.org/viewtopic.php?id=11288<br />
<br><br />
http://archlinux.org/pipermail/arch/2007-November/016048.html<br />
<br />
==Q) What's the difference between all these repositories?==<br />
'''A)''' See [[The Arch Linux Repositories]].<br />
<br />
<br />
<br />
==Q) I just installed Package X. How do I start it?==<br />
'''A)''' If you're using a desktop environment like KDE or GNOME, the program should automatically show up in your menu. If you're trying to run the program from a terminal and don't know the binary name, try executing "pacman -Ql packagename | grep bin". A common problem for packages like Firefox or OpenOffice is that they are installed to /opt, which is not in your $PATH - you can "source /etc/profile" or logout/login to fix this.<br />
<br />
=Installation=<br />
<br />
==Q) Arch needs a better installer. Maybe a GUI installer.==<br />
'''A)''' The discussion of a "better" installer is a subjective opinion. The best way to cope with these issues it to fit the installer to "the Arch way". If this opinion on a better installer is backed with more-concrete arguments, it might be taken into account for further development of the installer. Since installation doesn't occur often (see the question above on rolling release), it is not a high priority for developers or users.<br />
However, two unofficial methods exist: [http://archie.dotsrc.org/ Archie Live CD] for XFCE (other desktops in development) and [http://user-contributions.org/wikis/userwiki/index.php?title=Arch_Linux_Office_Install_CD Arch Linux Office Install CD] for KDE.<br />
<br />
==Q) I installed Arch, and now I am at a bash login! What now?==<br />
'''A)''' Have a look at the Arch Linux [[Beginner's Guide]]<br />
==Q) Arch is touted as a distribution which is built up from a minimal base system, installing only what is required by the user. Isn't this possible with virtually any distribution? What makes Arch unique in this regard?==<br />
<br />
'''A)''' A few distributions may provide minimal installation methods similar in design to the Arch installation process. However, a few points must be noted:<br />
# Arch has been fundamentally designed as a lightweight, minimal environment upon which to build. <br />
# Whether the FTP or Core images are used, the only way to install Arch is by building up from this minimal base.<br />
# The installation, as well as the entire distribution is inherently a K.I.S.S. design approach, which makes it uniquely suitable for its target base of users.<br />
# The simple Arch installer is designed for a high level of transparency and the base system is manually configured by the user to their needed specifications.<br />
# Arch provides thoroughly complete documentation to guide one through this process of system assembly.<br />
<br />
=Other=<br />
<br />
==Q) I get an error every time I use pacman saying 'warning: current locale is invalid; using default "C" locale'. What do I do?==<br />
'''A)''' As the error message says, your locale isn't correctly configured. Have a look at the [[Configuring locales|locale configuration wiki page]].<br />
<br />
==Q) How do I automount/mount something? ==<br />
'''A)''' If you use GNOME, install gnome-volume-manager:<br />
pacman -Sy gnome-volume-manager<br />
<br />
Now add yourself to the storage group:<br />
gpasswd -a ''your_user'' storage<br />
<br />
If you don't want to use gnome-volume-manager, check out the [[AutoFS_HowTo|AutoFS HowTo]].<br />
<br />
==Q) How do I connect to my wireless network?==<br />
'''A)''' See [[Wireless Setup]].<br />
<br />
==Q) How do I connect to my wired network?==<br />
'''A)''' See [[Configuring network]].<br />
<br />
==Q) What is this AUR thing I keep hearing about?==<br />
'''A)''' See [[AUR Q & A]].<br />
<br />
==Q) Why do I get a green screen whenever I try to watch a video?==<br />
'''A)''' Your colour depth is set wrong. It may need to be 24 instead of 16, for example.<br />
<br />
==Q) Spellcheck is marking all of my text as incorrect!==<br />
'''A)''' Have you installed an aspell dictionary? Use <tt>pacman -Ss aspell</tt> to see the available dictionaries.</div>
Potamota
https://wiki.archlinux.org/index.php?title=Unofficial_user_repositories&diff=40545
Unofficial user repositories
2008-05-01T15:21:35Z
<p>Potamota: </p>
<hr />
<div>[[Category: Package management (English)]]<br />
[[Category: General (English)]]<br />
<br />
== Why unofficial user repositories ==<br />
Since the AUR only allows users to upload PKGBUILD and other package build related files, but does not provide a means for distributing a binary package, a user may want to create a binary repository of their packages elsewhere.<br />
<br />
'''However:''' Be advised, if you only put your packages in your private repo and neglect AUR, your package will never make it into community repo nor a central storage space(AUR) which is bad for users, since they will have to add 'YetAnotherThird-party-Repo'(YATR) to their /etc/pacman.conf which will make it slower to update. But the main reason you should not have repo-only packages is that not having packages in a central place confuses and gives users a second job in that they now have to search for ''Repositories'' in addition to ''Packages''.<br />
<br />
Thus the best way to have a private repo is to offer it as a ''supplement'' to the AUR for those users who don't want to compile. You should try to avoid to offer it as a ''substitute''.<br />
<br />
== The future of Unofficial repos ==<br />
I'd like to see more work of this type. Sometimes there are certain projects that don't mesh well with other things, such as the community repo. The 'kdemod' project is a good example.<br />
<br />
In the future, well-thought-out user repositories may be ideal for lots of supplementary things. Forming a "web of trust" is important in cases like this, so we may begin keeping a list of "recommended" repositories somewhere, in order to make it seem more official and trustworthy.<br />
<br />
[[User:Phrakture|Phrakture]] 12:50, 18 May 2007 (EDT)<br />
<br />
== The community repository, maintained by the TUs==<br />
<nowiki>[community]<br />
Server = ftp://ftp.archlinux.org/community/os/i686/</nowiki><br />
<br />
The community repository is included in pacman's default configuration, but disabled. You can enable it by removing the # in these two lines:<br />
<br />
[community]<br />
Include = /etc/pacman.d/community<br />
<br />
== List of PUR (unofficial user repositories) | i686 ==<br />
<nowiki><br />
[archlinuxfr]<br />
## The french Archlinux communities packages<br />
Server = http://repo.archlinux.fr/i686<br />
<br />
[Victor]<br />
Server = http://personales.ya.com/vmromanos/arch/pkgs<br />
<br />
[archie]<br />
Server = ftp://ftp.sunsite.dk/projects/archie/packages<br />
<br />
[dibble]<br />
Server = http://dtw.jiwe.org/pkgs/dibble<br />
<br />
[hussam]<br />
## Contains daily Firefox trunk cvs i686 packages.<br />
Server = http://ht990332.googlepages.com/<br />
<br />
[janitux]<br />
Server = http://janitux.mortals.dy.fi <br />
<br />
[kasmol]<br />
Server = http://kasmol.netsons.org/arch/software<br />
<br />
[kde-split]<br />
## Splitted kde packages. Original kdebase and kdelibs are required. Work in progress<br />
Server = http://gotux.altervista.org/arch/packages/i686/<br />
<br />
[Lapis]<br />
## Linux-sevenler packages.Zemberek , virtualbox and other stuff<br />
Server = http://arch.linux-sevenler.org/pkgs <br />
<br />
[nvidia-beta]<br />
## nvidia 0.9.* beta drivers<br />
Server = http://box.decemplex.net/~thomas/nvidia-beta/<br />
<br />
[obarchie]<br />
Server = http://dtw.jiwe.org/pkgs/obarchie<br />
<br />
[oo-voikko]<br />
## Openoffice and linguistic software and data for Finnish<br />
Server = http://www.kotikone.fi/purch/arch/oo-voikko/i686<br />
<br />
[perlcpan]<br />
## More info here: http://wiki.archlinux.org/index.php/PerlCPAN_Repository<br />
Server = http://arch.os-zen.net/perlcpan/packages<br />
<br />
[rabyte]<br />
Server = http://oxygen4.free.fr/arch<br />
<br />
[tango]<br />
# dmdtango package (dmd compiler + tango library)<br />
Server = http://downloads.dsource.org/projects/tango/archlinux/i686<br />
<br />
[kdemod]<br />
# splitted KDE... take a look:<br />
# - http://bbs.archlinux.org/viewtopic.php?t=23319<br />
# - http://kdemod.ath.cx/<br />
# if there's a big change and you would stay on the bleeding edge you may replace<br />
# 'current' with 'testing'<br />
Server = http://kdemod.ath.cx/repo/current/i686<br />
<br />
[seif]<br />
Server = http://seif.hopto.org/arch/<br />
<br />
[cgr-i686]<br />
# packages for some ChicoGeek's PKGBUILDs<br />
Server = http://cgr.i686.googlepages.com/<br />
<br />
[lnf]<br />
# packages include: firefox3-systemcairo, cairo-ubuntu (+deps)<br />
# tor-alpha, radeonhd-git, gajim-svn, mpd-svn, sonata-svn, vidalia<br />
Server = http://reactor.reality-protocol.de/lnf<br />
<br />
[compiz-fusion]<br />
#compiz-fusion-git<br />
Server = http://compiz.dreamz-box.de/i686<br />
</nowiki><br />
<br />
== The following repositories are no longer functioning (1 May 08) ==<br />
<nowiki><br />
[fatsobob]<br />
Server = http://www.animeroot.com/fatsobob/repo<br />
<br />
[blub]<br />
## by bobrik<br />
Server = http://bobrik.hovel.ru/archlinux/blub<br />
<br />
[chman]<br />
Server = http://arch.shakebox.org/pkg/<br />
<br />
[cjdj]<br />
Server = http://www.cjdj.org/arch/pkg <br />
<br />
[compiz-fusion]<br />
Server = http://arch.nesl247.org/i686<br />
<br />
[darwin]<br />
Server = http://darwin.info.tm/arch/i686<br />
<br />
[dsa]<br />
Server = http://sistemas.unilestemg.br/douglas/downloads/arch<br />
<br />
[fubar]<br />
Server = http://marcosaxo.madoka.be/files/arch<br />
<br />
[happymars]<br />
# D-related packages<br />
Server = http://happymars.yi.org/happymars/i686<br />
<br />
[karsten] <br />
## 32-bit<br />
Server = http://arch.os-zen.net/pkg/karsten/i686 <br />
<br />
[marfis]<br />
Server = http://arch.marfis.org/binaries<br />
<br />
[nooms]<br />
## visibility-svn/openbox-svn, works with pacman3 only<br />
Server = http://arch.nooms.de/<br />
<br />
[n0yd]<br />
## Misc pkg's (Songbird, kiba-dock, other "goodies" :D ) Note: Possible non-free contents<br />
Server = http://www.n0yd.net/arch<br />
<br />
[pharfox]<br />
Server = http://arch.debianbox.be<br />
<br />
[takhis] <br />
## e17, ...<br />
Server = ftp://takhis.net/arch<br />
<br />
[vegai]<br />
Server = http://people.jyu.fi/~vpkaihla/arch<br />
<br />
[venox]<br />
Server = http://arch.lworks.cjb.net/<br />
<br />
[wael]<br />
Server = http://wael.nasreddine.com/files/arch/repo/wael/os/i686/ <br />
<br />
[garbage]<br />
Server = http://exire.dyndns.org:8081/arch/repo<br />
<br />
[archlinux.pl]<br />
## The polish Archlinux communities packages<br />
Server = http://bednarek.org.pl/arch/i686<br />
<br />
[brain0]<br />
## gcc2, gvpe, siefs<br />
Server = http://www-users.rwth-aachen.de/thomas.baechler/arch/brain0/os/i686<br />
<br />
[danimoth]<br />
## Xgl and dependencies<br />
Server = http://jjdanimoth.altervista.org/arch/i686<br />
<br />
</nowiki><br />
<br />
== List of PUR (unofficial user repositories) | x86-64 ==<br />
<nowiki><br />
[archlinuxfr]<br />
## The french Archlinux communities packages<br />
Server = http://repo.archlinux.fr/x86_64/<br />
<br />
[kdemod]<br />
# splitted KDE... take a look:<br />
# - http://bbs.archlinux.org/viewtopic.php?t=23319<br />
# - http://kdemod.ath.cx/<br />
# if there's a big change and you would stay on the bleeding edge you may replace<br />
# 'current' with 'testing'<br />
Server = http://kdemod.ath.cx/repo/current/x86_64<br />
<br />
[olympus]<br />
## by zeus<br />
## see http://archlinux.org.ru/forum/index.php/topic,39.0.html for more info<br />
Server = http://zeus.hovel.ru/archlinux/olympus/<br />
<br />
[oo-voikko]<br />
## Openoffice and linguistic software and data for Finnish<br />
Server = http://www.kotikone.fi/purch/arch/oo-voikko/x86_64<br />
<br />
[homegnu]<br />
## Some packages for the tuxdroid + custom versions of some stuff<br />
Server = http://data.homegnu.net/archlinux<br />
<br />
[compiz-fusion]<br />
#compiz-fusion-git<br />
Server = http://compiz.dreamz-box.de/x86_64<br />
</nowiki><br />
<br />
== Add your own repository to this list ==<br />
If you have your own repository, please add this to this list, so that all other users knows where to find your packages.</div>
Potamota
https://wiki.archlinux.org/index.php?title=Map_Custom_Device_Entries_with_udev&diff=32580
Map Custom Device Entries with udev
2007-11-20T13:01:13Z
<p>Potamota: </p>
<hr />
<div>[[Category:Hardware detection and troubleshooting (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This information is basically mirrored from the gentoo wiki with some additional hints. Recently it was updated to reflect changes in udev >= 98 syntax.<br />
<br />
This process allows you to always map a specific device to the same <code>/dev</code> node. This can then be used in <code>fstab</code> to ensure you can always mount the device same device in exactly the same place - which is great for desktop shortcuts!<br />
<br />
<br />
==Get the udev info for your USB device==<br />
<br />
Make sure one of your target devices is plugged in and then run the following as root:<br />
udevinfo -a -p `udevinfo -q path -n /dev/sda`<br />
<br />
This gets the udev device info for the device on <code>/dev/sda</code> - if your device is not mapped to <code>/dev/sda</code> then obviously use the correct mapping. :)<br />
<br />
You should get some output like this:<br />
<pre><br />
<br />
Udevinfo starts with the device specified by the devpath and then<br />
walks up the chain of parent devices. It prints for every device<br />
found, all possible attributes in the udev rules key format.<br />
A rule to match, can be composed by the attributes of the device<br />
and the attributes from one single parent device.<br />
<br />
looking at device '/block/sda':<br />
KERNEL=="sda"<br />
SUBSYSTEM=="block"<br />
DRIVER==""<br />
ATTR{stat}==" 19 111 137 160 0 0 0 0 0 152 160"<br />
ATTR{size}=="2007040"<br />
ATTR{removable}=="1"<br />
ATTR{range}=="16"<br />
ATTR{dev}=="8:0"<br />
<br />
looking at parent device '/devices/pci0000:00/0000:00:02.2/usb1/1-5/1-5:1.0/host5/target5:0:0/5:0:0:0':<br />
KERNELS=="5:0:0:0"<br />
SUBSYSTEMS=="scsi"<br />
DRIVERS=="sd"<br />
ATTRS{ioerr_cnt}=="0x0"<br />
ATTRS{iodone_cnt}=="0x1c"<br />
ATTRS{iorequest_cnt}=="0x1c"<br />
ATTRS{iocounterbits}=="32"<br />
ATTRS{timeout}=="30"<br />
ATTRS{state}=="running"<br />
ATTRS{rev}=="1.20"<br />
ATTRS{model}=="01GB Tiny "<br />
ATTRS{vendor}=="Pretec "<br />
ATTRS{scsi_level}=="3"<br />
ATTRS{type}=="0"<br />
ATTRS{queue_type}=="none"<br />
ATTRS{queue_depth}=="1"<br />
ATTRS{device_blocked}=="0"<br />
ATTRS{max_sectors}=="240"<br />
<br />
looking at parent device '/devices/pci0000:00/0000:00:02.2/usb1/1-5/1-5:1.0/host5/target5:0:0':<br />
KERNELS=="target5:0:0"<br />
SUBSYSTEMS==""<br />
DRIVERS==""<br />
<br />
looking at parent device '/devices/pci0000:00/0000:00:02.2/usb1/1-5/1-5:1.0/host5':<br />
KERNELS=="host5"<br />
SUBSYSTEMS==""<br />
DRIVERS==""<br />
<br />
looking at parent device '/devices/pci0000:00/0000:00:02.2/usb1/1-5/1-5:1.0':<br />
KERNELS=="1-5:1.0"<br />
SUBSYSTEMS=="usb"<br />
DRIVERS=="usb-storage"<br />
ATTRS{modalias}=="usb:v4146pBA01d0100dc00dsc00dp00ic08isc06ip50"<br />
ATTRS{bInterfaceProtocol}=="50"<br />
ATTRS{bInterfaceSubClass}=="06"<br />
ATTRS{bInterfaceClass}=="08"<br />
ATTRS{bNumEndpoints}=="03"<br />
ATTRS{bAlternateSetting}==" 0"<br />
ATTRS{bInterfaceNumber}=="00"<br />
<br />
looking at parent device '/devices/pci0000:00/0000:00:02.2/usb1/1-5':<br />
KERNELS=="1-5"<br />
SUBSYSTEMS=="usb"<br />
DRIVERS=="usb"<br />
ATTRS{configuration}==""<br />
ATTRS{serial}=="14AB0000000096"<br />
ATTRS{product}=="USB Mass Storage Device"<br />
ATTRS{maxchild}=="0"<br />
ATTRS{version}==" 2.00"<br />
ATTRS{devnum}=="7"<br />
ATTRS{speed}=="480"<br />
ATTRS{bMaxPacketSize0}=="64"<br />
ATTRS{bNumConfigurations}=="1"<br />
ATTRS{bDeviceProtocol}=="00"<br />
ATTRS{bDeviceSubClass}=="00"<br />
ATTRS{bDeviceClass}=="00"<br />
ATTRS{bcdDevice}=="0100"<br />
ATTRS{idProduct}=="ba01"<br />
ATTRS{idVendor}=="4146"<br />
ATTRS{bMaxPower}==" 98mA"<br />
ATTRS{bmAttributes}=="80"<br />
ATTRS{bConfigurationValue}=="1"<br />
ATTRS{bNumInterfaces}==" 1"<br />
<br />
looking at parent device '/devices/pci0000:00/0000:00:02.2/usb1':<br />
KERNELS=="usb1"<br />
SUBSYSTEMS=="usb"<br />
DRIVERS=="usb"<br />
ATTRS{configuration}==""<br />
ATTRS{serial}=="0000:00:02.2"<br />
ATTRS{product}=="EHCI Host Controller"<br />
ATTRS{manufacturer}=="Linux 2.6.18-ARCH ehci_hcd"<br />
ATTRS{maxchild}=="6"<br />
ATTRS{version}==" 2.00"<br />
ATTRS{devnum}=="1"<br />
ATTRS{speed}=="480"<br />
ATTRS{bMaxPacketSize0}=="64"<br />
ATTRS{bNumConfigurations}=="1"<br />
ATTRS{bDeviceProtocol}=="01"<br />
ATTRS{bDeviceSubClass}=="00"<br />
ATTRS{bDeviceClass}=="09"<br />
ATTRS{bcdDevice}=="0206"<br />
ATTRS{idProduct}=="0000"<br />
ATTRS{idVendor}=="0000"<br />
ATTRS{bMaxPower}==" 0mA"<br />
ATTRS{bmAttributes}=="e0"<br />
ATTRS{bConfigurationValue}=="1"<br />
ATTRS{bNumInterfaces}==" 1"<br />
<br />
looking at parent device '/devices/pci0000:00/0000:00:02.2':<br />
KERNELS=="0000:00:02.2"<br />
SUBSYSTEMS=="pci"<br />
DRIVERS=="ehci_hcd"<br />
ATTRS{broken_parity_status}=="0"<br />
ATTRS{enable}=="1"<br />
ATTRS{modalias}=="pci:v000010DEd00000068sv00001043sd00000C11bc0Csc03i20"<br />
ATTRS{local_cpus}=="f"<br />
ATTRS{irq}=="17"<br />
ATTRS{class}=="0x0c0320"<br />
ATTRS{subsystem_device}=="0x0c11"<br />
ATTRS{subsystem_vendor}=="0x1043"<br />
ATTRS{device}=="0x0068"<br />
ATTRS{vendor}=="0x10de"<br />
<br />
looking at parent device '/devices/pci0000:00':<br />
KERNELS=="pci0000:00"<br />
SUBSYSTEMS==""<br />
DRIVERS==""<br />
<br />
</pre><br />
<br />
Bit too much information! The only bit of this you actaully need is the <code>ATTRS<serial}</code> part - so now you know what the above command does just grep out the bit you want in future cases:<br />
<br />
udevinfo -a -p `udevinfo -q path -n /dev/sda` | grep ATTRS{serial}<br />
<br />
output:<br />
<br />
ATTRS{serial}=="14AB0000000096"<br />
ATTRS{serial}=="0000:00:02.2"<br />
<br />
Hmm, two serials. Which one to use?<br />
<br />
udevinfo -a -p `udevinfo -q path -n /dev/sda` | grep ATTRS{product}<br />
<br />
and we get<br />
<br />
ATTRS{product}=="USB Mass Storage Device"<br />
ATTRS{product}=="EHCI Host Controller"<br />
<br />
So, we need to use first serial.<br />
<br />
<br />
==Create a udev rule==<br />
<br />
You then use the <code>ATTRS{serial}</code> in a udev rule as follows:<br />
<br />
Note: The convention for Arch Linux is to place custom rules into <code>/etc/udev/rules.d/00.rules</code><br />
You may, however create a file with a different name. Just remember that udev processes these files in alphabetical order.<br />
<br />
BUS=="usb", ATTRS{serial}=="14AB0000000096", KERNEL=="sd?1", NAME="%k", SYMLINK+="usbdrive", GROUP="storage"<br />
<br />
<br />
==Create an fstab entry and mount point==<br />
<br />
Create a directory:<br />
<br />
mkdir /mnt/usbdrive<br />
<br />
In your <code>/etc/fstab</code>, create an entry like this:<br />
<br />
/dev/usbdrive /mnt/usbdrive vfat rw,noauto,group,flush,quiet,nodev,nosuid,noexec,noatime,dmask=000,fmask=111 0 0<br />
<br />
Additionally, depending on your locale preferences, add something like <code>codepage=866,iocharset=utf-8</code> to be able to see non-Latin filenames correctly.<br />
<br />
Now root or any user who belongs to the <code>storage</code> group can mount the USB stick by simply doing<br />
<br />
mount /mnt/usbdrive<br />
<br />
BTW, all the last 3 additional mount options are meant to increase your system's security, e.g. they will prevent you running an executable file directly from the USB drive.<br />
<br />
To allow non-root users to acces to USB stick do<br />
gpasswd -a user1 storage<br />
gpasswd -a user2 storage<br />
<br />
==Restart udev==<br />
<br />
to test your updated rules you can run:<br />
udevcontrol reload_rules<br />
<br />
Only if really needed, you may restart udev like this. As root, run those 3 commands:<br />
/etc/./start_udev<br />
mount /dev/pts<br />
mount /dev/shm<br />
<br />
==Examples==<br />
<br />
Here are some examples from my system. My devices sometimes mount on <code>sda</code> or <code>sda1</code> so I have two rules for each - this is a work around for device not found problems. The sda node is also needed for disk-level activities e.g. <code>fdisk /dev/sda</code>.<br />
<br />
This always maps my disgo USB pen to <code>/dev/usbpen</code> which I then map in fstab to mount on <code>/mnt/usbpen</code><br />
<br />
# Symlink USB pen<br />
SUBSYSTEMS=="usb", ATTRS{serial}=="1730C13B18000B84", KERNEL=="sd?", NAME="%k", SYMLINK+="usbpen", GROUP="storage"<br />
SUBSYSTEMS=="usb", ATTRS{serial}=="1730C13B18000B84", KERNEL=="sd?1", NAME="%k", SYMLINK+="usbpen", GROUP="storage"<br />
<br />
If you have a device with with multiple partitions, the following example maps the device to <code>/dev/usbdisk</code>, and partitions 1, 2, 3 etc. to <code>/dev/usbdisk1</code>, <code>/dev/usbdisk2</code>, <code>/dev/usbdisk3</code> etc.<br />
<br />
# Symlink multi-part device<br />
SUSSYSTEMS=="usb", ATTRS{serial}=="1730C13B18000B84", KERNEL=="sd?", NAME="%k", SYMLINK+="usbdisk", GROUP="storage"<br />
SUBSYSTEMS=="usb", ATTRS{serial}=="1730C13B18000B84", KERNEL=="sd?[1-9]", NAME="%k", SYMLINK+="usbdisk%n", GROUP="storage"<br />
<br />
These rules are equivalent to the following one:<br />
<br />
# Symlink multi-part device<br />
SUBSYSTEMS=="usb", ATTRS{serial}=="1730C13B18000B84", KERNEL=="sd*", NAME="%k", SYMLINK+="usbdisk%n", GROUP="storage"<br />
<br />
You can also omit the NAME and GROUP statements, so that the defaults from <code>udev.rules</code> are used. So the shortest and simplest solution would be adding this rule:<br />
<br />
# Symlink multi-part device<br />
SUBSYSTEMS=="usb", ATTRS{serial}=="1730C13B18000B84", KERNEL=="sd*", SYMLINK+="usbdisk%n"<br />
<br />
This always maps our Olympus digicam to <code>/dev/usbcam</code> which I then map in fstab to mount on <code>/mnt/usbcam</code><br />
<br />
# Symlink USB camera<br />
SUBSYSTEMS=="usb", ATTRS{serial}=="000207532049", KERNEL=="sd?", NAME="%k", SYMLINK+="usbcam", GROUP="storage"<br />
SUBSYSTEMS=="usb", ATTRS{serial}=="000207532049", KERNEL=="sd?1", NAME="%k", SYMLINK+="usbcam", GROUP="storage"<br />
<br />
And this maps my Packard Bell MP3 player to <code>/dev/mp3player</code><br />
<br />
# Symlink MP3 player<br />
SUBSYSTEMS=="usb", ATTRS{serial}=="0002F5CF72C9C691", KERNEL=="sd?", NAME="%k", SYMLINK+="mp3player", GROUP="storage"<br />
SUBSYSTEMS=="usb", ATTRS{serial}=="0002F5CF72C9C691", KERNEL=="sd?1", NAME="%k", SYMLINK+="mp3player", GROUP="storage"<br />
<br />
To map your own usb key to <code>/dev/mykey</code> and all of other keys to <code>/dev/otherkey</code><br />
<br />
# Symlink USB keys<br />
SUBSYSTEMS=="usb", ATTRS{serial}=="insert serial key", KERNEL=="sd?1", NAME="%k", SYMLINK+="mykey"<br />
SUBSYSTEMS=="usb", KERNEL=="sd?1", NAME="%k", SYMLINK+="otherkey"<br />
<br />
Note the order of the lines. Since all the usb keys should create the /dev/sd<a||b> node, udev will first check if it is your own usb key, defined with the serial number. But if you plug another key witch you don't know the serial number, it will create a node too, with a generic name "otherkey". That rule should be the last one your rules file.<br />
<br />
<br />
This is an example how to distinguish USB HDD drive and USB sticks:<br />
<br />
BUS=="usb", ATTRS{product}=="USB2.0 Storage Device", KERNEL=="sd?", NAME="%k", SYMLINK+="usbdisk", GROUP="storage"<br />
BUS=="usb", ATTRS{product}=="USB2.0 Storage Device", KERNEL=="sd?[1-9]", NAME="%k", SYMLINK+="usbdisk%n", GROUP="storage"<br />
BUS=="usb", ATTRS{product}=="USB Mass Storage Device", KERNEL=="sd?1", NAME="%k", SYMLINK+="usbflash", GROUP="storage"<br />
<br />
Note that this udev rule doesn't use serials at all.</div>
Potamota
https://wiki.archlinux.org/index.php?title=Beginners%27_guide_(Indonesia)&diff=31633
Beginners' guide (Indonesia)
2007-11-02T15:05:12Z
<p>Potamota: /* Start the Installation */</p>
<hr />
<div>[[Category: Mendapatkan dan Instalasi Arch (Indonesia)]]<br />
[[Category:Tentang Arch (Indonesia)]]<br />
[[Category:HOWTOs (Indonesia)]]<br />
{{translateme}}<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Beginners Guide}}<br />
{{i18n_entry|Česky|Průvodce začátečníka (Česky)}}<br />
{{i18n_entry|Italiano|Beginners Guide (Italiano)}}<br />
{{i18n_entry|Lietuviškai|Pradedančiųjų gidas (Lietuviškai)}}<br />
{{i18n_entry|Indonesia|Beginners Guide (Indonesia)}}<br />
{{i18n_links_end}}<br />
==Pendahuluan==<br />
=====Segala hal yang ingin kamu tanyakan tentang instalasi Arch, tapi takut untuk menanyakan.=====<br />
Dokumen ini akan membimbing kamu dalam menginstalasi dan mengkonfigurasi ArchLinux. Walau petunjuk ini ditujuakan untuk membimbing kamu mendapatkan sistem Arch yang terkonfigurasi seluruhnya (desktop environment, menonton DVD/Video, mendengarkan musik, Internet, mail) namun tidak berisi semua pilihan yang dapat kamu gunakan untuk mengerjakan hal tersebut. Petunjuk ini difokuskan pada beberapa langkah-langkah penting/dasar saja; jika kamu ingin bahasan yang lebih dalam kamu bisa mengunjungi [[Main Page|Arch Linux Wiki]] atau [http://bbs.archlinux.org/ Arch Linux Forums]. Kamu juga bisa membaca [[The Arch Way]] untuk mengetahui prinsip-prinsip dasar ArchLinux.<br />
<br />
=====DON'T PANIC!=====<br />
Harap disadari bahwa instalasi ArchLinux mungkin sangat berbeda dengan distro lain yang pernah kamu coba, khususnya bagi pemula. Sistem ArchLinux dibangun oleh '''pengguna''', dari installer, sampai ''base system'' dengan hanya menggunakan shell bash dan beberapa tools dasar sistem saja. dari ''command line'', kamu dapat menambahkan paket dari ''Arch repositories'' menggunakan [[pacman]] melalui sambungan internet, sampai sistem kamu sesuai dengan kebutuhan/kegininan. Dengan hal ini kamu akan mendapatkan sistem yang fleksibel, sesuai pilihan dan dapat kamu kendalikan karena '''kamu''' sendiri yang membangunnya, kamu akan mengetahui apa yang ada di dalam sistem kamu.<br />
<br />
Jika kamu merasa ada yang kurang dari wiki ini silahkan ditambahkan, atau kamu bisa juga mengunjungi forum Arch ini [http://bbs.archlinux.org/viewtopic.php?t=29055 yang ditujukan untuk pemula. <br />
<br />
Selamat datang di Arch! Mari kita mulai :)<br />
<br />
==Dapatkan ISO terbaru==<br />
<br />
Kamu dapat mengunduh rilis Arch resmi terbaru dari [http://www.archlinux.org/download/ www.archlinux.org/download/].<br />
<br />
Sangat direkomendasikan untuk memilih '''base-CD''', untuk beberapa alasan.<br />
<br />
# Waktu/bandwidth yang dibutuhkan lebih sedikit untuk kamu dan server,<br />
# Paket di versi full mungkin nantinya akan ada yang konflik ketika kamu melakukan update.<br />
# Base system lebih mudah dan cepat untuk up-to-date, dan,<br />
# Petunjuk ini lebih ditujukan untuk installasi dari base-CD. <br />
<br />
==Instalasi base system ==<br />
<br />
Selain petunjuk ini, kamu dapat juga dapat menggunakan petunjuk resmi ini [[Official Arch Linux Install Guide]] atau [http://www.archlinux.org/static/docs/arch-install-guide.html versi yang dapat di print] juga tersedia.<br />
<br />
===Boot CD Arch Linux===<br />
<br />
Masukkan CD dan boot dari CD-ROM, kamu mungkin perlu mengganti urutan boot pada bios komputer kamu (biasanya dengan menekan F11 atau F12).<br />
<br />
Beberapa pilihan pada saat booting ArchLinux CD yang dapat kamu gunakan:<br />
* ide-legacy jika IDE drive kamu bermasalah.<br />
* noapic acpi=off pci=routeirq nosmp jika sistem kamu hangs ketika boot.<br />
* memtest86+ if jika kamu ingin memeriksa memorimu.<br />
<br />
Pilih "Arch Linux Installation / Rescue System". Jika kamu ingin merubah opsi boot tekan e.<br />
<br />
===Mengganti keymap===<br />
Tekan enter di welcome screen. Jika keyboard kamu non-US tekan<br />
km<br />
pada prompt dan pilih keymap yang sesuai.<br />
<br />
''Contoh''(untuk keymap norwegia) :<br />
<br />
Pada console keymap screen pilih<br />
no-latin1<br />
Pada console font screen pilih<br />
lat0-16<br />
<br />
Memilih "default8x16.psfu.gz" sebagai font console adalah pilihan aman.<br />
<br />
===Memulai instalasi===<br />
Pada console ketikkan<br />
/arch/setup <br />
lalu tekan enter untuk memulai instalasi. <br />
<br />
====Pilih sumber instalasi====<br />
Pilih CD jika kamu menggunakan base atau full (current) ISO, atau pilih FTP jika kamu menggunakan FTP ISO.<br />
<br />
====Prepare Hard Drive====<br />
Select the first menu entry "Prepare Hard Drive". Beware that "Auto-Prepare" may not be a safe choice because it will erase the entire hard drive.<br />
Here we will manually partition the hard drive. Choose "2. Partition Hard Drives", select the hard drive you want (/dev/sdx), and create some partitions. <br />
<br />
<br />
=====Partitions=====<br />
<br />
<br />
A partition is a section of hard disk space that will appear as a separate disk, and can be added to your Arch Linux file system. Partitions are broken up into "Primary", "Extended", and "Logical". <br />
Primary partitions can be bootable, and are limited to 4. For example, if you are using a PC with a single SATA drive, the first primary partition will be referred to as sda1. The second primary will be referred to as sda2, then sda3, and sda4. Beyond 4 partitions, we are forced to use an extended partition which will contain logical partitions.<br />
<br />
Extended partitions are not usable by themselves; they are merely a "container" for logical partitions. Logical partitions must be contained within this extended partition. When partitioning a disk, one can see this numbering scheme by creating primary partitions sda1-3 followed by creating an extended partition, sda4, and then creating logical partition(s) within the extended partition; sda5, sda6, and so on.)<br />
<br />
<br />
Everyone has a different opinion on how best to partition the disk. What you need at the least is one primary partition which contains the root [http://en.wikipedia.org/wiki/File_system Filesystem] ( / ) and one for swap. Other candidates for separate partitions are /boot (which mainly contains the kernel) and /home (which contains the user data). It is good practice to have / and /home on separate partitions. This makes it possible to reinstall Arch Linux (or even another distro) for any reason, while keeping your data, music, pictures, and desktop environment preferences.<br />
<br />
In this example guide, we will stick with one partition for /, one partition for /home, and a swap partition.<br />
<br />
=====Swap Partition=====<br />
A swap partition is a place on your hard drive where "virtual ram" resides. If your processes need more RAM than is physically available, Linux can't fulfill the request and an error occurs. A swap partition helps in this situation by supplementing the physical RAM with virtual RAM. Linux uses the space on the hard disk to store the information that won't fit into the physical RAM any more (it's actually a bit more complex because Linux tries to put information into the swap space that isn't frequently used). Because a hard disk is very slow compared to physical RAM, this is only<br />
a makeshift. <br />
<br />
<br />
Ask two people about a swap partition and you will get four different answers. If you have plenty of RAM (more than 1024 MB) it may be possible to not use a swap partition at all. Some people suggest using twice the amount of physical RAM, while others recommend not using more than 1024 MB. I believe keeping the swap size between 512 MB and 1 GB is a good choice. Therefore, we will create a 1 GB swap space in this example.<br />
<br />
Let's start creating the '''primary partition''' that will contain the '''root''' filesystem. Choose New -> Primary and enter the size you want (something between 4 and 8 GB is a good choice for a full-featured Linux system). Put the partition at the beginning of the disk. Select the newly created partition and choose "Bootable" to make this partition bootable. Add another '''partition for your home directory'''. Choose another primary partition and set the size to a value you like. The size really depends on what your users store in their home directories, so I cannot make any suggestions. The size may vary between a few hundred megabytes for some office documents up to hundreds of gigabytes for videos and MP3s. If you <br />
want to use the whole space on your hard disc, use the remaining space minus 512 MB - 1 GB for the size. At last we<br />
create a third '''partition for swap'''. Select a size between 512 MB and 1 GB and change the type to 82 (Linux swap / Solaris).<br />
<br />
This is what your Layout should look like (size may vary depending on your decisions):<br />
<br />
Name Flags Part Type FS Type [Label] Size (MB)<br />
-------------------------------------------------------------------------<br />
sda1 Boot Primary Linux (4096 - 8192)<br />
sda2 Primary Linux (> 100)<br />
sda3 Primary Linux swap / Solaris (512 - 1024)<br />
<br />
Choose Write and type yes. Beware that this operation may destroy data on your disk if you deleted partitions. Choose Quit to leave the partitioner. <br />
Choose Done to leave this menu and continue with "Set Filesystem Mountpoints".<br />
<br />
====Set File system Mountpoints====<br />
<br />
=====A few brief words about '''filesystems''' and "file systems":=====<br />
<br />
Technically, and for accuracy, a '''filesystem''' is a data format for information throughput, whereas a "file system" (notice the space) is a term referring to the layout of all files and directories on a given system. (In our case, the hierarchical UNIX file system.) Therefore, when you are asked if you want to create a '''filesystem''', you are being asked if you want to '''format''' the particular partition... but when you are asked for mount points, you are providing where the given partition will reside in your Arch Linux "file system". Let's begin.<br />
<br />
First you will be asked for your swap partition. Choose the appropriate partition (sda3 in this example). You will be asked if you want to create a swap filesystem; select yes. Next, choose where to mount the / (root) directory (sda1 in the example). You will be asked what kind of filesystem you want.<br />
<br />
Again, ask two people which filesystem to choose and you will get five different answers. Each one has its advantages and disadvantages. Here is a very brief overview of supported filesystems.<br />
<br />
1. '''ext2''' - Old, reliable GNU/Linux filesystem. Fast, and very stable, but without journaling.<br />
<br />
2. '''ext3''' - Essentially the ext2 system, but with journaling support. ''Slightly'' slower than ext2 and other filesystems. '''Extremely''' stable and the most widely used, supported, and developed.<br />
<br />
3. '''ReiserFS''' - Hans Reiser's high-performance journaling FS uses a very interesting method of data throughput. ReiserFS is very fast, especially when dealing with many small files. ReiserFS is quite well established and stable.<br />
<br />
4. '''JFS''' - IBM's Journaling FS. JFS is quite well established, fast, and stable.<br />
<br />
5. '''XFS''' - is a fast journaling filesystem which is best suited for large files, greater than 1 GB in size. Slower with small files. Quite stable.<br />
<br />
A major difference is [http://en.wikipedia.org/wiki/Journaling_file_system journaling] (something similar to transaction logs in database environments). All filesystems except ext2 use journaling. ext3 is completely compatible with ext2, so you can mount it even with very-old rescue CDs. A safe choice for the root partition is ext3. ReiserFS, XFS, and JFS are also OK to use because GRUB (the boot manager which we will install later) can boot from them too. Create the filesystem (format the partition) by selecting yes. You will now be prompted to add any additional partitions. In our example, only sda2 is remaining. Choose a filesystem type and mount it as /home. Again, create the filesystem and choose Done. Return to main menu.<br />
<br />
===Select Packages===<br />
Now we shall select packages to install in our system. Choose CD as source and select the appropriate CD drive if you have more than one.<br />
Since this guide is geared toward a '''base''' installation, choose the base category (keeping all base packages selected is a safe choice). If you chose the current ISO rather than the base ISO, it is up to you if you want to select more packages, but we will show you later how to install additional, up-to-date software more easily, rather than installing and reinstalling. (Since the install CD you are using has been created, there are no doubt numerous updates available for packages contained therein, and installing additional up-to-date software via pacman will be covered below.) If you are '''sure''' you will not be needing certain packages (for instance, a filesystem type you don't need, ISDN, or PPPoE support), feel free to remove them from the base package selection. <br />
<br />
Step forward to "Install Packages".<br />
<br />
===Install Packages===<br />
This is an easy task because everything happens automatically. Get yourself a cup of coffee (if you're into coffee ;)) and wait until the installation has finished (press continue if needed). Drink quickly, because the Arch Linux base packages install in just a couple of minutes.<br />
<br />
===Configure The System===<br />
You will be asked if you want to choose hwdetect to gather some information for your configuration. This is recommended so you should choose this option. <br />
Now you will be asked if you need support for booting from USB devices, FireWire devices, PCMCIA devices, NFS shares, software RAID arrays, LVM2 volumes, and encrypted volumes. Choose yes if you need it; in our example nothing is needed. Now you will be asked which text editor you want to use; choose [http://en.wikipedia.org/wiki/Nano_%28text_editor%29 nano] if you are not familiar with [http://en.wikipedia.org/wiki/Vim_%28text_editor%29 vi/vim]. You will now get a menu with most important config files for your system. We will do only some minor tweaks at this time. If you want to look up the available options as stated in rc.conf just press Alt+F2 to get a shell, look it up, and switch back to the installer with Alt+F1. <br />
<br />
=====/etc/rc.conf=====<br />
<br />
* Change your LOCALE if needed (e.g. "de_DE.utf8") (This locale must coincide with /etc/locale.gen. '''See below'''.)<br />
* Change your TIMEZONE if needed (e.g. "Europe/Berlin")<br />
* Change your KEYMAP if needed (e.g. "de-latin1-nodeadkeys")<br />
<br />
* Change MODULES if you know that an important module is missing (hwdetect should have filled in the most important modules)<br />
* Change your HOSTNAME<br />
* Change your Network settings:<br />
** Don't modify the lo line<br />
** Adjust the IP address, netmask and broadcast address if you are using a static IP<br />
** Set eth0="dhcp" if you have a router which dynamically assigns an IP address<br />
** If you have a static IP set the gateway address to the one of your router and remove the ! in front of the ROUTES entry<br />
=====About DAEMONS=====<br />
You don't have to change the [[daemons]] line at this time, but it is useful to explain what daemons are, because we need them later in this guide. Analogous to a Windows service, a daemon is a program that runs in the background, waiting for events to occur and offering services. A good example is a webserver that waits for a request to deliver a page or an SSH server waiting for someone trying to log in. While these are full-featured applications, there are daemons whose work is not that visible. Examples are a daemon which writes messages into a log file (e.g. syslog, metalog), a daemon which lowers your CPU's frequency if your system has nothing to do, and a daemon which offers you a graphical login (e.g. gdm, kdm). All these programs can be added to the daemons line and will be started when the system boots. Useful daemons will be presented during this guide.<br />
<br />
Use Ctrl+X to leave the editor.<br />
<br />
=====/etc/hosts=====<br />
Add the desired ''hostname'' (the one you set in rc.conf before) so that it looks like this:<br />
127.0.0.1 localhost.localdomain localhost ''yourhostname''<br />
This format, '''including the 'localhost' entries''', is required for program compatibility.<br />
For most users, simply adding the ''hostname'' to the end of the default line will work, however, some users recommend using the following syntax:<br />
127.0.0.1 ''yourhostname''.domain.org localhost.localdomain localhost ''yourhostname''<br />
If you use a static IP, add another line using the syntax: <static-ip> hostname.domainname.org hostname, <br />
e.g.:<br />
192.168.1.100 yourhostname.domain.org yourhostname<br />
<br />
===== /etc/fstab, mkinitcpio.conf and modprobe.conf=====<br />
We shouldn't need to edit mkinitcpio.conf, or modprobe.conf at this point. mkinitcpio configures the ramdisk (e.g. booting from RAID, encrypted volumes) and modprobe can be used to set some special config options for the modules).<br />
<br />
If you are planning on using the hal daemon to automate the mounting of disks, optical drives, usb drives, etc., you may wish to edit /etc/fstab by commenting out the entries for cdrom, floppy, and dvd.<br />
<br />
=====/etc/resolv.conf (for Static IP)=====<br />
If you use a static IP, set your DNS servers in /etc/[[resolv.conf]] (nameserver <ip-address>). You may have as many as you wish.<br />
<br />
If you are using a router, you will probably want to specify your DNS servers in the router itself, and merely point to it from your resolv.conf, using your router's IP (which is also your gateway from /etc/rc.conf), e.g.:<br />
nameserver 192.168.1.1<br />
Alternatively, add your preferred servers one by one, e.g.:<br />
nameserver 4.2.2.1<br />
nameserver 4.2.2.2<br />
<br />
=====/etc/locale.gen=====<br />
Choose the locale(s) you need (remove the # in front of the lines you want), e.g.:<br />
en_US ISO-8859-1<br />
en_US.UTF-8 <br />
('''Your locale must coincide with the one specified in /etc/rc.conf above.''')<br />
=====Root password=====<br />
Finally, set a root password and make sure that you remember it later. Return to the main menu and continue with installing a kernel.<br />
<br />
===Install Kernel===<br />
Not many choices here; choose v2.6 and continue. You may want to switch your kernel later. A fallback image will be created, keeping mkinitcpio as it is shown as a safe choice. Continue with installing a bootloader.<br />
<br />
===Install Bootloader===<br />
Because we have no secondary operating system in our example, we will need a bootloader. [http://www.gnu.org/software/grub/ GNU GRUB] is the recommended bootloader. Alternatively, you may choose [http://lilo.go.dyndns.org/ LILO]. The shown GRUB configuration (/boot/grub/menu.lst) should be sufficient. The only thing you may want to alter is the resolution of the console. Add<br />
a vga=<number> to the first kernel line. (A table of resolutions and the corresponding numbers is printed in the menu.lst.) <br />
title Arch Linux (Main)<br />
root (hd0,0)<br />
kernel /boot/vmlinuz26 root=/dev/sda1 ro vga=773<br />
initrd /boot/kernel26.img<br />
The "vga=773" argument will give a 1024x768 framebuffer with 256 color depth.<br />
<br />
Exit the install and type reboot.<br />
<br />
If everything goes well, your new Arch Linux system will boot up and finish with a login prompt (you may want to change the boot order in your BIOS back to booting from hard disk).<br />
<br />
Congratulations, and welcome to your shiny, new Arch Linux base system!<br />
<br />
==Configuring the base system ==<br />
Your new Arch Linux base system is now a functional GNU/Linux operating system ready for customization. From here, you may build this elegant set of tools into whatever you wish or require for your purposes!<br />
Let's begin.<br />
-----<br />
Login with your root account. We will configure pacman and update the system as root, then add a normal user. <br />
<br />
===Configuring pacman===<br />
Edit /etc/pacman.conf<br />
nano -w /etc/pacman.conf<br />
and remove the # in front of the "Include = /etc/pacman.d/community" and "[community]" lines to enable Arch's community repository, which offers many useful applications. Now edit /etc/pacman.d/community and move the mirrors which are located nearest to you up (if you use nano, Alt+A starts selecting an area, cursor down marks the lines, Ctrl+K cuts the selected area and Ctrl+U uncuts it). Repeat this for all files in /etc/pacman.d/.<br />
<br />
===Configuring the network (if necessary)===<br />
<br />
If everything went fine, you should have a working network. Try to ping www.google.com to verify this.<br />
ping -c 3 www.google.com<br />
<br />
If you have successfully established a network connection, continue with "Update, Sync and Upgrade the system with pacman".<br />
<br />
If, after trying to ping www.google.com, you get an "unknown host" error, you may conclude that your network is not configured. You may choose to double-check the following files for integrity and proper settings:<br />
<br />
'''/etc/rc.conf''' # Specifically, check your HOSTNAME= and NETWORKING section<br />
<br />
'''/etc/hosts''' # Double-check your format. (See above.)<br />
<br />
'''/etc/resolv.conf''' # If you are using a static IP. If you are using DHCP, this file will be dynamically created and destroyed by default, but can be changed to your preference. (See [[Network]].)<br />
<br />
Advanced instructions for configuring the network can be found in the [[Network]] article.<br />
<br />
====Wired LAN====<br />
<br />
Check your Ethernet with<br />
ifconfig<br />
where you should see an entry for eth0. If required, you can set a new static IP with<br />
ifconfig eth0 <ip address> netmask <netmask> up <br />
and the default gateway with<br />
route add default gw <ip address of the gateway><br />
Check to see if /etc/resolv.conf contains your DNS server and add it if it is missing. <br />
Check your network again with ping www.google.de. If everything is working now, adjust /etc/rc.conf as described in section 2.6 (static IP). If you have a DHCP server/router in your network try<br />
dhcpcd eth0<br />
If this is working, adjust /etc/rc.conf as described in section 2.6 (dynamic IP).<br />
<br />
====Wireless LAN====<br />
[[Wireless Setup]]<br />
(TODO) Simplify and generalize it, link only for more-advanced stuff<br />
<br />
====Analog Modem====<br />
To be able to use a Hayes-compatible, external, analog modem, you need to at least have the ppp package installed. Modify the file /etc/ppp/options to suit your needs and according to man pppd. You will need to define a chat script to supply your username and password to the ISP after the initial connection has been established. The manpages for pppd and chat have examples in them that should suffice to get a connection up and running if you're either experienced or stubborn enough. With udev, your serial ports usually are /dev/tts/0 and /dev/tts/1.<br />
Tip: Read [[Dialup without a dialer HOWTO]].<br />
<br />
Instead of fighting a glorious battle with the plain pppd, you may opt to install wvdial or a similar tool to ease the setup process considerably. In case you're using a so-called WinModem, which is basically a PCI plugin card working as an internal analog modem, you should indulge in the vast information found on the [http://www.linmodems.org/ LinModem] homepage.<br />
<br />
====ISDN====<br />
<br />
Setting up ISDN is done in three steps:<br />
# Install and configure hardware<br />
# Install and configure the ISDN utilities<br />
# Add settings for your ISP <br />
<br />
The current Arch stock kernels include the necessary ISDN modules, meaning that you won't need to recompile your kernel unless you're about to use rather odd ISDN hardware. After physically installing your ISDN card in your machine or plugging in your USB ISDN-Box, you can try loading the modules with modprobe. Nearly all passive ISDN PCI cards are handled by the hisax module, which needs two parameters: type and protocol. You must set protocol to '1' if your country uses the 1TR6 standard, '2' if it uses EuroISDN (EDSS1), '3' if you're hooked to a so-called leased-line without D-channel, and '4' for US NI1.<br />
<br />
Details on all those settings and how to set them is included in the kernel documentation, more specifically in the isdn subdirectory, and available online. The type parameter depends on your card; a list of all possible types can be found in the README.HiSax kernel documentation. Choose your card and load the module with the appropriate options like this:<br />
<br />
modprobe hisax type=18 protocol=2<br />
<br />
This will load the hisax module for my ELSA Quickstep 1000PCI, being used in Germany with the EDSS1 protocol. You should find helpful debugging output in your /var/log/everything.log file, in which you should see your card being prepared for action. Please note that you will probably need to load some USB modules before you can work with an external USB ISDN Adapter.<br />
<br />
Once you have confirmed that your card works with certain settings, you can add the module options to your /etc/modprobe.conf:<br />
<br />
alias ippp0 hisax<br />
options hisax type=18 protocol=2<br />
<br />
Alternatively, you can add only the options line here, and add hisax to your MODULES array in the rc.conf. It's your choice, really, but this example has the advantage that the module will not be loaded until it's really needed.<br />
<br />
That being done, you should have working, supported hardware. Now you need the basic utilities to actually use it!<br />
<br />
Install the isdn4k-utils package, and read the manpage to isdnctrl; it'll get you started. Further down in the manpage you will find explanations on how to create a configuration file that can be parsed by isdnctrl, as well as some helpful setup examples. Please note that you have to add your SPID to your MSN setting separated by a colon if you use US NI1.<br />
<br />
After you have configured your ISDN card with the isdnctrl utility, you should be able to dial into the machine you specified with the PHONE_OUT parameter, but fail the username and password authentication. To make this work add your username and password to /etc/ppp/pap-secrets or /etc/ppp/chap-secrets as if you were configuring a normal analogous PPP link, depending on which protocol your ISP uses for authentication. If in doubt, put your data into both files.<br />
<br />
If you set up everything correctly, you should now be able to establish a dial-up connection with<br />
isdnctrl dial ippp0<br />
as root. If you have any problems, remember to check the logfiles!<br />
<br />
====DSL (PPPoE)====<br />
<br />
These instructions are relevant to you only if your PC itself is supposed to manage the connection to your ISP. You do not need to do anything but define a correct default gateway if you are using a separate router of some sort to do the grunt work.<br />
<br />
Before you can use your DSL online connection, you will have to physically install the network card that is supposed to be connected to the DSL-Modem into your computer. After adding your newly installed network card to the modules.conf/modprobe.conf or the MODULES array, you should install the rp-pppoe package and run the pppoe-setup script to configure your connection. After you have entered all the data, you can connect and disconnect your line with<br />
<br />
/etc/rc.d/adsl start<br />
<br />
and<br />
<br />
/etc/rc.d/adsl stop<br />
<br />
respectively. The setup usually is rather easy and straightforward, but feel free to read the manpages for hints. If you want to automatically dial in on boot-up, add adsl to your DAEMONS array.<br />
<br />
==Update, Sync and Upgrade the system with [[pacman]]==<br />
Now we will update the system using [[pacman]], the package manager of Arch Linux. Pacman is fast, simple, and extremely powerful. It manages your entire package system and allows installation, package removal, package downgrade (through cache), custom compiled package handling, automatic dependency resolution, and much more.<br />
<br />
Update, sync, and '''upgrade''' your entire new system with:<br />
pacman -Syu<br />
pacman will now fetch the latest information about available packages and perform all available upgrades. (You may be prompted to upgrade pacman itself at this point. If so, say yes, and then reissue the pacman -Syu command when finished.)<br />
<br />
=====''Take note as to whether a kernel upgrade is occurring!''=====<br />
<br />
If the kernel is upgraded, modules such as nvidia will be rendered inoperable, since the new, upgraded versions will be built against the newer kernel, and your system is currently using an older one. A reboot will be necessary.<br />
<br />
=====The beauty of the rolling release=====<br />
Keep in mind that Arch is a '''rolling release''' distribution. This means there is never a reason to reinstall or perform elaborate system rebuilds to upgrade to the newest version. Simply issuing '''pacman -Syu''' periodically keeps your entire system up-to-date and on the bleeding edge. At the end of this upgrade, your system is completely current.<br />
<br />
=====Get familiar with pacman=====<br />
Pacman is the Arch user's best friend. It is highly recommended to study and learn how to use the pacman tool. Try:<br />
man pacman<br />
Check out the bottom of this article, and look up the [[pacman]] wiki entries at your leisure.<br />
<br />
<br />
<br />
===Add a user and setup groups===<br />
You should not do your everyday work using the root account. It is more than poor practice; it is dangerous. Root is for administrative tasks. Instead, add a normal user account using:<br />
adduser<br />
While most default options are safe to use, you may want to add at least audio and wheel to your additional groups. <br />
Audio allows your user to use the audio card, while wheel allows switching to the root account with su. Other groups to be added, (separated by a comma) include:<br />
<br />
*disk - for managing disks, including USB flash drives and such<br />
<br />
*storage - for managing storage devices<br />
<br />
*video - for managing video tasks<br />
<br />
*optical - for managing tasks pertaining to the optical drive(s)<br />
<br />
*floppy - for access to a floppy if necessary<br />
<br />
*lp - for managing printing tasks<br />
<br />
You may also consider adding optical to your additional groups to enable CD/DVD recording from your user account.<br />
<br />
See the [http://wiki.archlinux.org/index.php/Groups Groups] article to understand what groups you need to be a member of. <br />
You may also add your user to the desired groups like so, (as root):<br />
usermod -aG audio,video,floppy,lp,optical,network,storage,wheel USERNAME<br />
<br />
==Installing and configuring Hardware==<br />
===Configure the audio card===<br />
Your audio card should already be working, but you can't hear anything because it is muted by default. Install the alsa-utils <br />
pacman -S alsa-utils<br />
and use alsamixer to adjust the channels: <br />
alsamixer<br />
Unmute the Master and PCM channels by scrolling to them with cursor left/right and pressing '''M'''. Increase the volume levels with the cursor-up key. (70-90 Should be a safe range.) Leave alsamixer by pressing ESC and store the settings with<br />
alsactl store<br />
If you plan on using a desktop environment such as GNOME or KDE and would prefer that alsa remember your settings when you change them, do not execute the above command--your volume settings will be remembered automatically.<br />
Add alsa to your DAEMONS section in /etc/rc.conf to automatically restore the mixer on boot-up.<br />
nano /etc/rc.conf<br />
<br />
DAEMONS=(syslog-ng network crond '''alsa''')<br />
<br />
===Configuring CPU frequency scaling===<br />
Modern processors can decrease their frequency and voltage to reduce heat and power consumption. Less heat leads to a quieter system; even a desktop system will benefit from it. Install cpufrequtils with<br />
pacman -S cpufrequtils<br />
and add cpufreq to your daemons in /etc/rc.conf. Edit the config file /etc/conf.d/cpufreq and change <br />
governor="conservative"<br />
which dynamically increases the CPU frequency if needed (which is a safe choice on desktop systems too). Alter min_freq and max_freq to match your system's CPU spec. If you don't know the frequencies, run ''cpufreq-info'' after loading one of the frequency scaling modules. Add the frequency scaling modules to your /etc/rc.conf modules line. Most modern notebooks and desktops can simply use the ''acpi-cpufreq'' driver, however other options include the ''p4-clockmod, powernow-k6, powernow-k7, powernow-k8, and speedstep-centrino'' drivers. Load the module with<br />
modprobe <modulname> <br />
and start cpufreq with<br />
/etc/rc.d/cpufreq start<br />
For more details, see [[Cpufrequtils]]<br />
<br />
===Additional tweaks for laptops===<br />
ACPI support is needed if you want to use some special functions on your notebook (e.g. sleep, sleep when lid is closed, special keys...). Install acpid <br />
pacman -S acpid<br />
and add it to the daemons in /etc/rc.conf (acpid). Start it with<br />
/etc/rc.d/acpid start<br />
<br />
More-specific information about Arch Linux on various Laptops can be found at [[:Category:Laptops (English)]]<br />
<br />
==Installing and configuring X==<br />
The X Window System (commonly X11, or just simply X) is a networking and display protocol which provides windowing on bitmap displays. It provides the standard toolkit and protocol to build graphical user interfaces (GUIs) on Unix-like operating systems.<br />
<br />
X provides the basic framework, or primitives, for building GUI environments: drawing and moving windows on the screen and interacting with a mouse and/or keyboard. X does not mandate the user interface — individual client programs handle this. <br />
-----<br />
Now we will install the base Xorg packages using pacman. <br />
<br />
As root, do:<br />
pacman -S xorg-server xorg-xkb-utils xorg-xauth xorg-server-utils xorg-xinit xf86-video-vesa xf86-input-mouse xf86-input-keyboard<br />
(The old xorg group package has been removed. If it reappears, the option to use it will be given here.)<br />
Now we have the base packages we need for running the X Server. You should add the driver for your graphics card now (e.g. xf86-video-<name>). If you need a list of all '''open-source''' video drivers, do: <br />
pacman -Ss xf86-video | less<br />
If you don't know what graphics card you are using, do:<br />
lspci | grep VGA<br />
Here is a list of '''open source''' drivers, and corresponding video chipsets.<br />
*'''xf86-video-apm''' Alliance ProMotion video driver<br />
*'''xf86-video-ark''' ark video driver<br />
*'''xf86-video-ati''' ati video driver<br />
*'''xf86-video-chips''' Chips and Technologies video driver<br />
*'''xf86-video-cirrus''' Cirrus Logic video driver<br />
*'''xf86-video-dummy''' dummy video driver<br />
*'''xf86-video-fbdev''' framebuffer video driver<br />
*'''xf86-video-glint''' GLINT/Permedia video driver<br />
*'''xf86-video-i128''' Number 0 i128 video driver<br />
*'''xf86-video-i740''' Intel i740 video driver<br />
*'''xf86-video-i810''' Intel i810/i830/i9xx video drivers<br />
*'''xf86-video-imstt''' Integrated Micro Solutions Twin Turbo vidoe driver<br />
*'''xf86-video-mga''' mga video driver (Matrox Graphics Adapter)<br />
*'''xf86-video-neomagic''' neomagic video driver<br />
*'''xf86-video-nv''' nvidia nv video driver<br />
*'''xf86-video-rendition''' Rendition video driver<br />
*'''xf86-video-s3''' S3 video driver<br />
*'''xf86-video-s3virge''' S3 Virge video driver<br />
*'''xf86-video-savage''' savage video driver<br />
*'''xf86-video-siliconmotion''' siliconmotion video driver<br />
*'''xf86-video-sis''' SiS video driver<br />
*'''xf86-video-sisusb''' SiS USB video driver<br />
*'''xf86-video-tdfx''' tdfx video driver<br />
*'''xf86-video-trident''' Trident video driver<br />
*'''xf86-video-tseng''' tseng video driver<br />
*'''xf86-video-unichrome''' Unichrome video drivers<br />
*'''xf86-video-v4l''' v4l video driver<br />
*'''xf86-video-vesa''' vesa video driver<br />
*'''xf86-video-vga''' VGA 16 color video driver<br />
*'''xf86-video-via''' via video driver<br />
*'''xf86-video-vmware ''' vmware video driver<br />
*'''xf86-video-voodoo ''' voodoo video driver<br />
<br />
* Note that the '''vesa''' driver is the most generic, and should work with almost any modern video chipset. If you cannot find a suitable driver for your video chipset, vesa '''should''' work.<br />
<br />
*If you have an nVIDIA or ATI video adapter, you may wish to install the proprietary nVIDIA or ATI drivers. '''Installing proprietary video drivers is covered below''' under "Using proprietary Graphics Driver (nVIDIA, ATI)"<br />
<br />
Install the appropriate video driver for your video card/onboard video. e.g.:<br />
pacman -S xf86-video-i810<br />
(for the intel 810 chipset driver.)<br />
<br />
==Create /etc/X11/xorg.conf==<br />
=====What is /etc/X11/xorg.conf?=====<br />
/etc/X11/xorg.conf is the '''main configuration file''' for your '''X''' Window System, the foundation of your '''G'''raphical '''U'''ser '''I'''nterface. It is a plain text file ordered into sections and subsections. Important sections are ''Files, InputDevice, Monitor, Modes, Screen, Device, and ServerLayout''. Sections can appear in any order and there may be more than one section of each kind, for example, if you have more than one monitor, say a video projector and an on board LCD of a notebook. <br />
------<br />
By default, you will not have an Xorg config file, and with the newest versions of Xorg, you don't need one ''if'' the autodetection ''works satisfactorily'' and you don't need to turn on features such as aiglx and so on. ''Most people will still find that they need to generate a config file, however.''<br />
<br />
There are several ways of creating /etc/X11/xorg.conf:<br />
<br />
*The Xorg way to make a basic config file is to run<br />
Xorg -configure<br />
which will create /root/xorg.conf. Move the generated config file as appropriate, e.g.<br />
mv /root/xorg.conf.new /etc/X11/xorg.conf<br />
<br />
*Another way of making an xorg.conf without getting your hands dirty is Arch Linux's own developer tpowa's tool:<br />
hwd -xa<br />
hwd (to see the various options)<br />
<br />
*The proprietary video drivers also have tools to edit xorg.conf to configure the drivers (see below). These are <br />
aticonfig<br />
and<br />
nvidia-xconfig<br />
<br />
However, you should not be a stranger to editing the config file by hand (as this is usually needed to fix various issues from time to time):<br />
<br />
nano /etc/X11/xorg.conf<br />
<br />
Edit your /etc/X11/xorg.conf to specify your video driver. e.g.:<br />
Section "Device"<br />
Driver "i810"<br />
<br />
=====Simple baseline X test=====<br />
<br />
At this point, you should have xorg installed, with a suitable video driver and an /etc/X11/xorg.conf configuration file. If you want to test your configuration quickly, before installing a complete desktop environment, install '''xterm'''. Xterm is a very simple terminal emulator which runs in the X Server environment. Xterm will allow us to effectively test if your video driver and /etc/X11/xorg.conf are properly configured. Alternatively, you may wish to test if the X autodetection works satisfactorily, in the absence of /etc/X11/xorg.conf.<br />
pacman -S xterm<br />
Edit your /home/username/.xinitrc file, '''as normal user''', to dictate which X Server event is called upon with the 'startx' command:<br />
<br />
su yourusername<br />
<br />
nano ~/.xinitrc<br />
<br />
and add (or uncomment)<br />
<br />
exec xterm<br />
<br />
So that it looks like this:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
exec xterm<br />
# exec wmaker<br />
# exec startkde<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
<br />
(Be sure to have only one uncommented line in your ~/.xinitrc ) If you do not have ~/.xinitrc, simply create one with the above information.<br />
<br />
Start X Server as normal user, with:<br />
<br />
startx<br />
You should have an xterm session open up. You can exit the X Server with Ctrl+Alt+Backspace, or by typing "exit". If you have problems starting X, you can look for errors in the /var/log/Xorg.0.log file and on the console output of the console you started X from.<br />
<br />
Now you might want to install a graphical login manager (to avoid having to type startx everytime you start the computer) like [[GDM]] or [[KDM]], but this ''could'' wait, and advanced instructions for Xorg configuration can be found in the [[Xorg]] article.<br />
<br />
===Adjusting Keyboard Layout===<br />
You may want to change your keyboard layout. To do this edit your /etc/X11/xorg.conf and add these lines in the Input Section (keyboard0) (the example shows a German keyboard layout with no dead keys; alter this to fit your needs).<br />
Option "XkbLayout" "de"<br />
Option "XkbVariant" "nodeadkeys"<br />
<br />
===Adjusting Mouse for scroll wheel===<br />
While your mouse should be working out of the box, you may want to use your scroll wheel. Add this to your Input Section (mouse0):<br />
Option "ZAxisMapping" "4 5 6 7"<br />
<br />
===evdev===<br />
If you have a modern USB mouse with several thumb buttons and/or functions, you will most likely want to install the evdev mouse driver, which will allow you to exploit the full functionality of your mouse:<br />
<br />
pacman -S xf86-input-evdev<br />
Load the driver:<br />
modprobe evdev<br />
Find your mouse name:<br />
cat /proc/bus/input/devices | egrep "Name"<br />
Using the mouse name, configure your /etc/X11/xorg.conf InputDevice section accordingly, e.g.:<br />
Section "InputDevice"<br />
Identifier "Evdev Mouse"<br />
Driver "evdev"<br />
Option "Name" "Logitech USB-PS/2 Optical Mouse"<br />
Option "CorePointer"<br />
EndSection<br />
You must have only '''one''' "CorePointer" device specified in /etc/X11/xorg.conf, so be sure to comment out any other mouse entries until you feel safe removing the old, unused entries.<br />
<br />
Also edit the ServerLayout section to include Evdev Mouse as the CorePointer, e.g.:<br />
Section "ServerLayout"<br />
Identifier "Layout0"<br />
Screen 0 "Screen0"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
InputDevice "Evdev Mouse" "CorePointer"<br />
<br />
===Using proprietary Graphics Driver (nVIDIA, ATI)===<br />
You may choose to use the proprietary video drivers from nVIDIA or ATI. <br />
====nVIDIA Graphic Cards====<br />
The nVIDIA proprietary drivers are generally considered to be of excellent quality, and offer superior 3D performance.<br />
<br />
Before you configure your Graphics Card you will need to know which driver fits. Arch currently has 3 different drivers that each match a certain subset of Cards: <br />
<br />
'''1. nvidia-71xx''' ''for very old Cards like TNT and TNT2''<br />
<br />
'''2. nvidia-96xx''' ''slightly newer cards up to the GF 4''<br />
<br />
'''3. nvidia''' ''newest GPUs after the GF 4''<br />
<br />
Consult the nVIDIA-Homepage to see which one is for you. The difference is only for the installation; Configuration works the same with every driver.<br />
<br />
Install the appropriate nvidia driver, e.g.: <br />
pacman -S nvidia <br />
At this point, you have 3 choices as to how to proceed.<br />
<br />
*'''1.''' If you have no xorg.conf at all, or if you have an existing xorg.conf and want to '''generate a completely new one''' with the nVIDIA utility, back up the old one:<br />
mv /etc/X11/xorg.conf /etc/X11/xorg.old<br />
Then create the new /etc/X11/xorg.conf with<br />
nvidia-xconfig<br />
The nvidia-xconfig utility will usually create a very short, streamlined, easy-to-read xorg.conf<br />
<br />
It also has several options which will further specify the contents and options of the xorg.conf file.<br />
For example,<br />
nvidia-xconfig --composite --add-argb-glx-visuals<br />
<br />
For more detailed information, see nvidia-xconfig(1).<br />
<br />
*'''2.''' '''Expert Option:''' If you have an existing xorg.conf and want to keep it, edit your xorg manually as needed, and at the very least, adjust your '''Device''' Section by changing Driver "<olddrivername>" to Driver "nvidia".<br />
Section "Device"<br />
<br />
Driver "nvidia" <br />
*'''3.''' Alternatively, you may choose to keep your existing /etc/X11/xorg.conf, and run:<br />
nvidia-xconfig<br />
which will automatically '''update''' your /etc/X11/xorg.conf for use with the nVIDIA proprietary driver.<br />
<br />
Some useful tweaking options in the device section are (beware that these may not work on your system):<br />
Option "RenderAccel" "true"<br />
Option "NoLogo" "true"<br />
Option "AGPFastWrite" "true"<br />
Option "EnablePageFlip" "true"<br />
<br />
The nvidia-xconfig utility will automatically place the glx option in your xorg. If you did not use nvidia-xconfig, then you should add this to your module section:<br />
<br />
Load "glx"<br />
Double check your /etc/X11/xorg.conf to make sure your default depth, horizontal refresh, vertical refresh, and resolutions are acceptable.<br />
<br />
Logout and login.<br />
<br />
Start X server as normal user, to test your configuration:<br />
startx<br />
<br />
Advanced instructions for nvidia configuration can be found in the [[NVIDIA]] article.<br />
<br />
====ATI Graphic Cards====<br />
ATI owners have two options for drivers. If you are unsure which driver to use, please try the open-source one first. The open-source driver will suit most needs along with being generally less problematic.<br />
<br />
Install the '''proprietary''' ATI Driver with<br />
pacman -S fglrx<br />
Use the aticonfig tool to modify the xorg.conf. Note: The proprietary driver does not support [[AIGLX]]. To use [[Compiz]] or [[Beryl]] with this driver you would need to use [[XGL]].<br />
<br />
Install the '''open-source''' ATI Driver with<br />
pacman -S xf86-video-ati<br />
Currently, the performance of the open-source driver is not on par with that of the proprietary one. It also lacks TV-out, dual-link DVI support, and possibly other features. On the other hand, it supports Aiglx and has better dual-head support.<br />
<br />
Advanced instructions for ATI configuration can be found in the [[ATI | ATI wiki]].<br />
<br />
==Installing and configuring a Desktop Environment ==<br />
If you ask two people what the best Desktop Environment or Window Manager is, you will get six different answers. <br />
* If you want something full-featured and similar to Windows and Mac OSX, '''KDE''' is a good choice<br />
* If you want something more minimalist, which follows the K.I.S.S. principle more closely, '''GNOME''' is a good choice<br />
* If you have an older machine or want something lighter, '''xfce4''' is a good choice, still giving you a complete environment<br />
* If you need something even lighter, '''openbox, fluxbox or fvwm2''' may be right (not to mention all other lightweight window managers like '''windowmaker and twm''').<br />
* If you need something completely different, try '''ion, wmii, or dwm'''.<br />
<br />
===Install Fonts===<br />
At this point, you may want to install some good-looking fonts, '''before''' installing a desktop environment/window manager. Dejavu and bitstream-vera are nice font sets. For websites, you may want to have the Microsoft fonts too. Install with:<br />
pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera<br />
<br />
===GNOME===<br />
====About GNOME====<br />
The '''G'''NU '''N'''etwork '''O'''bject '''M'''odel '''E'''nvironment. The GNOME project provides two things: The GNOME desktop environment, an intuitive and attractive desktop for end-users, and the GNOME development platform, an extensive framework for building applications that integrate into the rest of the desktop.<br />
<br />
====Installation====<br />
Install GNOME with<br />
pacman -S gnome<br />
If you want a more-than-complete GNOME distribution with a lot of extras, do:<br />
pacman -S gnome-extra<br />
It's safe to choose all packages shown. <br />
=====Useful DAEMONS for GNOME=====<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. The '''hal''' daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The '''fam''' daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system. Both '''hal''' and '''fam''' make life easier for the GNOME user.<br />
<br />
You may want to install a graphical login manager. For GNOME, the '''gdm''' daemon is a good choice. Install gdm with<br />
pacman -S gdm<br />
You will almost certainly want the '''hal''' and '''fam''' daemons.<br />
<br />
Start hal and fam:<br />
/etc/rc.d/hal start<br />
<br />
/etc/rc.d/fam start<br />
<br />
Add them to your /etc/rc.conf DAEMONS section, so they will start on bootup:<br />
nano /etc/rc.conf<br />
<br />
DAEMONS=(syslog-ng network crond alsa '''hal fam gdm''')<br />
(If you prefer to log into the console and manually start X in the 'Slackware tradition', leave out gdm.)<br />
<br />
====~/.xinitrc====<br />
<br />
This file controls what occurs when you type 'startx'.<br />
<br />
Edit your /home/username/.xinitrc to utilize GNOME:<br />
<br />
nano ~/.xinitrc<br />
<br />
Uncomment the 'exec gnome-session' line so that it looks like this:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
#exec xterm<br />
#exec wmaker<br />
# exec startkde<br />
exec gnome-session<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
<br />
If you do not have a ~/.xinitrc file, simply create it with the above information. Remember, you must have only one uncommented line in your ~/.xinitrc. <br />
<br />
Switch to normal user:<br />
su username<br />
<br />
And test it with:<br />
startx<br />
<br />
You may want to install a terminal and an editor. I would recommend gnome-terminal (part of the group gnome-extra) and geany:<br />
pacman -S geany gnome-terminal<br />
<br />
Advanced instructions for installing and configuring GNOME can be found in the [[Gnome]] article.<br />
<br />
====Eye Candy====<br />
You may find the default GNOME theme and icons not very attractive. A nice gtk theme is murrine. Install it with<br />
pacman -S gtk-engine-murrine<br />
and select it with System->Preferences->Theme. You can find more themes, icons, and wallpaper at [http://www.gnome-look.org Gnome Look].<br />
<br />
===KDE===<br />
====About KDE====<br />
The '''K''' '''D'''esktop '''E'''nvironment. KDE is a powerful Free Software graphical desktop environment for Linux and Unix workstations. It combines ease of use, contemporary functionality, and outstanding graphical design with the technological superiority of UNIX-like operating systems.<br />
<br />
====Installation====<br />
Arch offers several versions of kde: '''kde, kdebase, and KDEmod'''. Choose '''one''' of the following, and continue below with '''"Useful KDE DAEMONS"''': <br />
<br />
'''1.)''' Package '''kde''' is the complete, vanilla KDE, ~300MB.<br />
pacman -S kde<br />
'''2.)''' Package '''kdebase''' is a slimmed-down version with less applications, ~80MB.<br />
pacman -S kdebase<br />
'''3.)''' Lastly, '''KDEmod''' is an Arch Linux exclusive, community-driven system which is modified for extreme performance and modularity. The KDEmod project website can be found at [http://kdemod.ath.cx/ http://kdemod.ath.cx/]. KDEmod is extremely fast, lightweight and responsive, with a pleasing, customized theme. <br />
<br />
To install KDEmod in 5 easy steps, just follow these installation instructions...<br />
Note: Before you start, please remember to read all of the install messages. They are fairly comprehensive and should solve any upcoming questions after the installation. If you cant scroll back to see all messages, just take a look into /var/log/pacman.log<br />
<br />
*1. Add the kdemod repo to your /etc/pacman.conf:<br />
nano /etc/pacman.conf<br />
Add one of these entries at the top of your server list:<br />
[kdemod]<br />
Server = http://kdemod.ath.cx/repo/current/i686<br />
for 32 bit Arch, or<br />
[kdemod]<br />
Server = http://kdemod.ath.cx/repo/current/x86_64<br />
for 64 bit Arch.<br />
<br />
*2. You must also activate the [community] repository in /etc/pacman.conf because KDEmod needs some packages from this repository. Make sure the following lines are uncommented:<br />
[community]<br />
Include = /etc/pacman.d/community<br />
<br />
<br />
*3. Update your package database with pacman -Syu. Now you can choose between two installations:<br />
<br />
pacman -S kdemod ''- installs a light base system''<br />
pacman -S kdemod-complete ''- installs the full KDE desktop''<br />
<br />
If you encounter any errors or conflicts at this step, check pacmans output, and if there are some unsolvable problems, tell us about them at the forums.<br />
*4. Install your localization. Take a look at the list of packages or simply do a pacman -Ss kdemod-kde-i18n to see which of them are already included.<br />
<br />
*5. Install all the extra apps you want. You can check out all available KDEmod packages by entering pacman -Sl kdemod<br />
<br />
====Useful KDE DAEMONS====<br />
<br />
KDE will require the '''hal''' ('''H'''ardware '''A'''bstraction '''L'''ayer) and '''fam''' ('''F'''ile '''A'''lteration '''M'''onitor) daemons. The '''kdm''' daemon is the '''K''' '''D'''isplay '''M'''anager, which provides a '''graphical login''', if desired.<br />
<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. The hal daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The fam daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system.. Both '''hal''' and '''fam''' make life easier for the KDE user, and are installed when you install KDE.<br />
<br />
Start hal and fam:<br />
<br />
/etc/rc.d/hal start<br />
<br />
/etc/rc.d/fam start<br />
<br />
Edit your DAEMONS section in /etc/rc.conf:<br />
nano /etc/rc.conf<br />
Add '''hal''' and '''fam''' to your DAEMONS section, to start them on bootup. If you prefer a graphical login, add '''kdm''' as well: <br />
DAEMONS=(syslog-ng network crond alsa '''hal fam kdm''')<br />
(If you prefer to log into the '''console''' and manually start X in the 'Slackware tradition', leave out kdm.)<br />
<br />
=====~/.xinitrc=====<br />
This file controls what occurs when you type 'startx'.<br />
<br />
Edit your /home/username/.xinitrc to utilize KDE:<br />
nano ~/.xinitrc<br />
Uncomment the 'exec startkde' line so that it looks like this:<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
#exec xterm<br />
#exec wmaker<br />
exec startkde<br />
# exec gnome-session<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
If you do not have a ~/.xinitrc file, simply create it with the above information. Remember, you must have only '''one''' uncommented line in your ~/.xinitrc.<br />
<br />
Switch to your normal user:<br />
su username<br />
Now try starting your X Server:<br />
startx<br />
<br />
Congratulations! Welcome to your KDE desktop environment on your new Arch Linux system! You may wish to continue by viewing [[Post Installation Tips]], or the rest of the information below.<br />
Advanced instructions for installing and configuring KDE can be found in the [[KDE]] article.<br />
<br />
===Xfce===<br />
====About Xfce====<br />
Xfce is a Desktop Environment, like GNOME or KDE. It contains a suite of apps like a root window app, window manager, file manager, panel, etc. Xfce is written using the GTK2 toolkit and contains its own development environment (libraries, daemons, etc) similar to other big DEs. Unlike GNOME or KDE, Xfce is lightweight and designed more around CDE than Windows or Mac. It has a much slower development cycle, but is very stable and extremely fast. Xfce is great for older hardware.<br />
<br />
====Installation====<br />
Install xfce with<br />
pacman -S xfce4 xfce4-goodies <br />
<br />
If you use kdm or gdm a new xfce session should have appeared. Alternatively, you can use<br />
startxfce4<br />
<br />
Advanced instructions for installing and configuring Xfce can be found in the [[Xfce]] article.<br />
<br />
===*box===<br />
====Fluxbox====<br />
Fluxbox © is yet another windowmanager for X.<br />
It's based on the Blackbox 0.61.1 code. Fluxbox looks like blackbox and handles styles, colors, window placement and similar things exactly like blackbox (100% theme/style compability).<br />
<br />
Install Fluxbox using <br />
pacman -S fluxbox fluxconf<br />
<br />
If you use gdm/kdm a new fluxbox session will be automatically added. Otherwise, you should modify your user's .xinitrc and add this to it:<br />
exec startfluxbox <br />
<br />
More information is available in the [[Fluxbox]] article.<br />
<br />
====Openbox====<br />
Openbox is a standards compliant, fast, light-weight, extensible window manager.<br />
<br />
Openbox works with your applications, and makes your desktop easier to manage. This is because the approach to its development was the opposite of what seems to be the general case for window managers. Openbox was written first to comply with standards and to work properly. Only when that was in place did the team turn to the visual interface.<br />
<br />
Openbox is fully functional as a stand-alone working environment, or can be used as a drop-in replacement for the default window manager in the GNOME or KDE desktop environments. <br />
<br />
Install openbox using<br />
pacman -S openbox obconf obmenu<br />
<br />
Once openbox is installed you will get a message to move menu.xml & rc.xml to ~/.config/openbox/ in your home directory:<br />
<br />
mkdir -p ~/.config/openbox/<br />
cp /etc/xdg/openbox/rc.xml ~/.config/openbox/<br />
cp /etc/xdg/openbox/menu.xml ~/.config/openbox/<br />
<br />
In the file "rc.xml" you can change various settings for Openbox (or you can use OBconf). In "menu.xml" you can change your right-click menu.<br />
<br />
To be able to log into openbox you can either go via graphical login using KDM/GDM or startx, in which case you will need to edit your ~/.xinitrc (as user) and add the following:<br />
<br />
exec openbox<br />
<br />
For KDM there is nothing left to do; openbox is listed in the sessions menu in KDM.<br />
<br />
Useful programs for openbox are:<br />
* PyPanel or LXpanel if you want a panel<br />
* feh if you want to set the background<br />
* ROX if you want a simple file manager and desktop icons<br />
<br />
More information is available in the [[Openbox]] article.<br />
<br />
===fvwm2===<br />
FVWM is an extremely powerful ICCCM-compliant multiple virtual desktop window manager for the X Window system. Development is active, and support is excellent. <br />
<br />
Install fvwm2 with<br />
pacman -S fvwm <br />
<br />
fvwm will automatically be listed in kdm/gdm in the sessions menu. Otherwise, add <br />
exec fvwm <br />
<br />
to your user's .xinitrc.<br />
<br />
Note that this stable version of fvwm is a few years old. If you want a more recent version of fvwm, there is a fvwm-devel package in the unstable repo.<br />
<br />
==HAL==<br />
Since you have now installed a desktop environment now would be a good time to also install HAL. HAL allows plug-and-play for your mobile phone, your iPod, your external HD's, etc. It will mount the device and make a nice visual icon on your desktop and/or in 'My Computer', allowing you to access the device after you have plugged it in instead of having to manually configure the /etc/fstab file or udev rules for each and every new device.<br />
<br />
KDE, GNOME and XFCE uses HAL.<br />
<br />
Refer to this article to install: [http://wiki.archlinux.org/index.php/HAL HAL]<br />
wikipedia: [http://en.wikipedia.org/wiki/HAL_(software) 1]<br />
<br />
==Useful Applications==<br />
This section will never be complete. It just shows some good applications for the everyday user. <br />
===Internet===<br />
<br />
=====Firefox=====<br />
The ever-popular Firefox web browser is available through pacman. Install with:<br />
<br />
pacman -S firefox<br />
Be sure and install 'flashplugin', 'mplayer', 'mplayer-plugin', and the 'codecs' packages for a complete web experience:<br />
pacman -S flashplugin mplayer mplayer-plugin codecs<br />
(The codecs package contains codecs for Quicktime and Realplayer content.)<br />
<br />
Thunderbird is useful for managing your emails. If you are using GNOME you may want to take a look at Epiphany and Evolution; if you are using KDE Konqueror and KMail could be your choice. If you want something completely different you can still use Opera. Finally, if you are working on the system console - or in a terminal session - you could use various text-based browsers like ELinks, Links and Lynx, and manage your emails with [[Mutt]]. Pidgin (previously known as Gaim) and Kopete are good instant messengers for GNOME and KDE, respectively. PSI and Gajim are perfect if you are using only Jabber or Google Talk.<br />
<br />
===Office===<br />
OpenOffice is a complete office suite (similar to Microsoft Office). Abiword is a good, small alternative word processor, and Gnumeric an Excel replacement for the GNOME desktop. KOffice is a complete office suite for the KDE Desktop. GIMP (or GIMPShop) is a pixel-based graphics program (similar to Adobe Photoshop), while Inkscape is a vector-based graphics program (like Adobe Illustrator). And, of course, Arch comes with a full set of LaTeX Programs.<br />
<br />
==Multimedia ==<br />
<br />
<br />
===Video Player===<br />
====VLC====<br />
VLC Player is a multimedia player for Linux. To install it, simply type the code below.<br />
<br />
pacman -S vlc<br />
<br />
(TODO) Instructions for VLC mozilla plug-in<br />
<br />
====Mplayer====<br />
MPlayer is a multimedia player for Linux. To install it, simply type the code below.<br />
<br />
pacman -S mplayer<br />
<br />
It also has a Mozilla plug-in for videos and streams embedded in web pages. To install it, simply type the code below.<br />
<br />
pacman -S mplayer-plugin<br />
<br />
If you use KDE, KMplayer is a better choice. It comes with a plug-in for videos and streams embedded in web pages, which works with Konqueror. To install it, simply type the code below.<br />
<br />
pacman -S kmplayer<br />
<br />
(TODO) GMPlayer instructions<br />
<br />
====GNOME====<br />
=====Totem=====<br />
[http://www.gnome.org/projects/totem/ Totem] is the official movie player of the GNOME desktop environment based on xine-lib or GStreamer (gstreamer is the default which installs with the arch totem package). It features a playlist, a full-screen mode, seek and volume controls, as well as keyboard navigation.<br />
It comes with added functionality such as:<br />
<br />
* Video thumbnailer for the file manager<br />
* Nautilus properties tab<br />
* Epiphany / Mozilla (Firefox) plugin to view movies inside your browser <br />
* Webcam utility (in development)<br />
<br />
Totem-xine is still the better choice if you want to watch DVDs.<br />
<br />
Totem is part of the gnome-extra group; the Totem webbrowser plugin isn't.<br />
<br />
To install separately:<br />
pacman -S totem<br />
<br />
To install the Totem webbrowser plugin:<br />
pacman -S totem-plugin<br />
<br />
====KDE====<br />
=====Kaffeine=====<br />
Kaffeine is a good option for KDE users. To install it, simply type the code below.<br />
<br />
pacman -S kaffeine<br />
<br />
===Audio Player===<br />
====Gnome/Xfce====<br />
=====Exaile=====<br />
[[Exaile]] is a music player written in Python that makes use of the GTK+ toolkit.<br />
=====Rhythmbox=====<br />
[http://www.gnome.org/projects/rhythmbox/ Rhythmbox] is an integrated music management application, originally inspired by Apple's iTunes. It is free software, designed to work well under the GNOME Desktop, and based on the powerful GStreamer media framework.<br />
<br />
Rhythmbox has a number of features, including:<br />
<br />
* Easy-to-use music browser<br />
* Searching and sorting<br />
* Comprehensive audio format support through GStreamer<br />
* Internet radio support<br />
* Playlists<br />
<br />
To install rhythmbox:<br />
pacman -S rhythmbox<br />
<br />
Other good audio players are: Banshee, Quodlibet, and Listen. See [http://gnomefiles.org/ Gnomefiles] to compare them.<br />
<br />
====KDE====<br />
=====Amarok=====<br />
[http://amarok.kde.org/ Amarok] is one of the best audio players and music library systems available for KDE. To install it, simply type the code below.<br />
<br />
pacman -S amarok-base<br />
<br />
====Console====<br />
Moc is a ncurses-based audio player for the console; another good choice is mpd.<br />
<br />
Another excellent choice is cmus[http://freshmeat.net/projects/cmus/].<br />
<br />
====Other X-based====<br />
(TODO) Xmms, audacious, bmpx.<br />
<br />
===Codecs and other multimedia content types===<br />
====DVD====<br />
You can use totem-xine, mplayer or kaffeine (just to name three of the big ones) to watch DVDs. The only thing you may miss is libdvdcss. Beware that using it may be illegal in some countries.<br />
<br />
====Flash====<br />
Install the flash plugin using<br />
pacman -S flashplugin<br />
to enable Macromedia (now Adobe) Flash in your browser.<br />
<br />
====Quicktime====<br />
Quicktime codecs are contained in the codecs package. Just type<br />
pacman -S codecs<br />
to install them.<br />
====Realplayer====<br />
The codec for Realplayer 9 is contained in the codecs package. Just type<br />
pacman -S codecs<br />
to install them. Realplayer 10 is available as a binary package for Linux. You can get it from AUR [http://aur.archlinux.org/packages.php?do_Details=1&ID=1590&O=0&L=0&C=0&K=realplay&SB=&SO=&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd here].<br />
<br />
===CD and DVD Burning===<br />
====GNOME====<br />
=====Brasero=====<br />
[http://www.gnome.org/projects/brasero/ Brasero] is an application that burns CDs/DVDs for the GNOME Desktop. It is designed to be as simple as possible and has some unique features to enable users to create their discs easily and quickly.<br />
<br />
To install:<br />
pacman -S brasero<br />
<br />
====KDE====<br />
=====K3b=====<br />
K3b - '''B'''urn, '''B'''aby, '''B'''urn in '''K'''DE<br />
-----<br />
[http://k3b.plainblack.com/ K3B] - CD/DVD burning application for Linux - optimized for KDE - licensed under the GPL.<br />
To install:<br />
pacman -S k3b<br />
<br />
<br />
<br />
<br />
(Todo) cdrecord, graveman...<br />
<br />
<br />
<br />
<br />
Most CD burners are wrappers for cdrecord:<br />
<br />
pacman -S cdrkit<br />
<br />
If you install packages for CD/DVD burning applications like Brasero or K3B it also installs the CD/DVD burning library for it, like libburn or cdrkit.<br />
<br />
A good command-line DVD-burning tool is growisofs:<br />
<br />
pacman -S dvd+rw-tools<br />
<br />
===TV-Cards===<br />
There are several things to do if you want to watch TV under (Arch) Linux. The most important task is to find out which chip your tuner is using. However, quite a bunch is supported. Be sure to check at a Hardware Database to be sure (e.g. [http://en.opensuse.org/HCL/TV_Cards]). Once you know your Model, there are just a few steps ahead to get you going.<br />
<br />
In most cases, you will need to use the bttv-drivers (other drivers exist, see [http://linux.bytesex.org/v4l2/drivers.html]) together with the I2C-modules. Configuring those is the hardest task. If you are lucky, a<br />
modprobe bttv<br />
will autodetect the card (check dmesg for results). In that case, you need only to install an application to watch TV. We will look at that later, though.<br />
If the autodetection did not work, you will need to check the file CARDLIST, which is included in the tarball of bttv[http://dl.bytesex.org/releases/video4linux/] to find out the right parameters for your card. A PV951 without radio support would need this line:<br />
modprobe bttv card=42 radio=0<br />
Some cards need the following line to produce sound:<br />
modprobe tvaudio<br />
However, that varies. So just try it out. Some other cards demand the following line:<br />
modprobe tuner<br />
This is object to trial-and-error, too.<br />
<br />
TODO: clarify the installation-procedure<br />
<br />
To actually watch TV, install the xawtv-package with<br />
pacman -S xawtv <br />
and read its manpage.<br />
<br />
TODO: clarify some possible problems and procedures. Introduction to XAWTV on another page?<br />
<br />
===Digital Cameras===<br />
Most newer digital cameras are supported as USB mass storage devices, which means that you can simply plug it in and copy the images. Older cameras may use the PTP (Picture Transfer Protocol) which requires a "special driver". gPhoto2 provides this driver and allows a shell-based transfer of the images; digikam (for KDE) and gthumb (for GNOME, gtkam would be another choice) use this driver and offer a nice GUI.<br />
<br />
===USB Memory Sticks / Hard Disks===<br />
USB Memory Sticks and hard disks are supported out of the box with the USB mass storage device driver and will appear as a new SCSI device (/dev/sdX). If you are using KDE or GNOME you should use dbus and hal (add them to your daemons in /etc/rc.conf), and they will be automatically mounted. If you use a different Desktop Environment you may have a look at ivman.<br />
<br />
==Maintaining the system==<br />
===Pacman===<br />
[[Pacman]] is both a binary and source package manager which is able to download, install, and upgrade packages from both remote and local repositories with full dependency handling, and has easy-to-understand tools for crafting your own packages too.<br />
<br />
A more-detailed description of Pacman can be found in [[Pacman|its article]].<br />
<br />
==== Useful commands ====<br />
<br />
To synchronize and update the local packages database with the remote repositories (it is a good idea to do this before installing and upgrading packages):<br />
pacman -Sy<br />
<br />
To '''upgrade''' all packages on the system:<br />
pacman -Su<br />
<br />
To sync, update, and '''upgrade''' all the packages on the system with one command:<br />
pacman -Syu<br />
<br />
To install or upgrade a single package or list of packages (including dependencies):<br />
pacman -S packageA packageB<br />
<br />
You can also sync, update the package database, and install packages in one command:<br />
pacman -Sy packageA packageB<br />
<br />
To remove a single package, leaving all of its dependencies installed:<br />
pacman -R package<br />
<br />
To remove a package and all of the package's dependencies which aren't used by any other installed package:<br />
pacman -Rs package<br />
<br />
To remove all of the package's dependencies now unneeded and do not make any backup of settings:<br />
pacman -Rsn package<br />
<br />
To search the remote (repo) package database for a list of packages matching a given keyword:<br />
pacman -Ss keyword<br />
<br />
To list all packages on your system<br />
pacman -Q<br />
<br />
To search (query) the local (your machine) package database for a given package:<br />
pacman -Q package <br />
<br />
To search (query) the local (your machine) package database for a given package and list all pertinent information:<br />
pacman -Qi package<br />
<br />
To defragment pacman's cache database and optimize for speed:<br />
pacman-optimize<br />
<br />
To count how many packages are currently on your system:<br />
pacman -Q | wc -l<br />
<br />
To install a package compiled from source using ABS and makepkg:<br />
pacman -U packagename.pkg.tar.gz<br />
<br />
Note: There are countless additional pacman functions and commands. Try man pacman and consult the [[pacman]] wiki entries.<br />
<br />
==Polishing & Further information==<br />
If after you have read this you want to do a bit of polishing, head to [[Post Installation Tips]]. For further information and support you can go to the [http://www.archlinux.org homepage], search the wiki, the [http://bbs.archlinux.org forums], the [http://wiki.archlinux.org/index.php/ArchChannel IRC channel], and the [http://www.archlinux.org/mailman/listinfo/ mailing lists].</div>
Potamota
https://wiki.archlinux.org/index.php?title=Beginners%27_guide_(Indonesia)&diff=31632
Beginners' guide (Indonesia)
2007-11-02T15:02:02Z
<p>Potamota: /* Changing the keymap */</p>
<hr />
<div>[[Category: Mendapatkan dan Instalasi Arch (Indonesia)]]<br />
[[Category:Tentang Arch (Indonesia)]]<br />
[[Category:HOWTOs (Indonesia)]]<br />
{{translateme}}<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Beginners Guide}}<br />
{{i18n_entry|Česky|Průvodce začátečníka (Česky)}}<br />
{{i18n_entry|Italiano|Beginners Guide (Italiano)}}<br />
{{i18n_entry|Lietuviškai|Pradedančiųjų gidas (Lietuviškai)}}<br />
{{i18n_entry|Indonesia|Beginners Guide (Indonesia)}}<br />
{{i18n_links_end}}<br />
==Pendahuluan==<br />
=====Segala hal yang ingin kamu tanyakan tentang instalasi Arch, tapi takut untuk menanyakan.=====<br />
Dokumen ini akan membimbing kamu dalam menginstalasi dan mengkonfigurasi ArchLinux. Walau petunjuk ini ditujuakan untuk membimbing kamu mendapatkan sistem Arch yang terkonfigurasi seluruhnya (desktop environment, menonton DVD/Video, mendengarkan musik, Internet, mail) namun tidak berisi semua pilihan yang dapat kamu gunakan untuk mengerjakan hal tersebut. Petunjuk ini difokuskan pada beberapa langkah-langkah penting/dasar saja; jika kamu ingin bahasan yang lebih dalam kamu bisa mengunjungi [[Main Page|Arch Linux Wiki]] atau [http://bbs.archlinux.org/ Arch Linux Forums]. Kamu juga bisa membaca [[The Arch Way]] untuk mengetahui prinsip-prinsip dasar ArchLinux.<br />
<br />
=====DON'T PANIC!=====<br />
Harap disadari bahwa instalasi ArchLinux mungkin sangat berbeda dengan distro lain yang pernah kamu coba, khususnya bagi pemula. Sistem ArchLinux dibangun oleh '''pengguna''', dari installer, sampai ''base system'' dengan hanya menggunakan shell bash dan beberapa tools dasar sistem saja. dari ''command line'', kamu dapat menambahkan paket dari ''Arch repositories'' menggunakan [[pacman]] melalui sambungan internet, sampai sistem kamu sesuai dengan kebutuhan/kegininan. Dengan hal ini kamu akan mendapatkan sistem yang fleksibel, sesuai pilihan dan dapat kamu kendalikan karena '''kamu''' sendiri yang membangunnya, kamu akan mengetahui apa yang ada di dalam sistem kamu.<br />
<br />
Jika kamu merasa ada yang kurang dari wiki ini silahkan ditambahkan, atau kamu bisa juga mengunjungi forum Arch ini [http://bbs.archlinux.org/viewtopic.php?t=29055 yang ditujukan untuk pemula. <br />
<br />
Selamat datang di Arch! Mari kita mulai :)<br />
<br />
==Dapatkan ISO terbaru==<br />
<br />
Kamu dapat mengunduh rilis Arch resmi terbaru dari [http://www.archlinux.org/download/ www.archlinux.org/download/].<br />
<br />
Sangat direkomendasikan untuk memilih '''base-CD''', untuk beberapa alasan.<br />
<br />
# Waktu/bandwidth yang dibutuhkan lebih sedikit untuk kamu dan server,<br />
# Paket di versi full mungkin nantinya akan ada yang konflik ketika kamu melakukan update.<br />
# Base system lebih mudah dan cepat untuk up-to-date, dan,<br />
# Petunjuk ini lebih ditujukan untuk installasi dari base-CD. <br />
<br />
==Instalasi base system ==<br />
<br />
Selain petunjuk ini, kamu dapat juga dapat menggunakan petunjuk resmi ini [[Official Arch Linux Install Guide]] atau [http://www.archlinux.org/static/docs/arch-install-guide.html versi yang dapat di print] juga tersedia.<br />
<br />
===Boot CD Arch Linux===<br />
<br />
Masukkan CD dan boot dari CD-ROM, kamu mungkin perlu mengganti urutan boot pada bios komputer kamu (biasanya dengan menekan F11 atau F12).<br />
<br />
Beberapa pilihan pada saat booting ArchLinux CD yang dapat kamu gunakan:<br />
* ide-legacy jika IDE drive kamu bermasalah.<br />
* noapic acpi=off pci=routeirq nosmp jika sistem kamu hangs ketika boot.<br />
* memtest86+ if jika kamu ingin memeriksa memorimu.<br />
<br />
Pilih "Arch Linux Installation / Rescue System". Jika kamu ingin merubah opsi boot tekan e.<br />
<br />
===Mengganti keymap===<br />
Tekan enter di welcome screen. Jika keyboard kamu non-US tekan<br />
km<br />
pada prompt dan pilih keymap yang sesuai.<br />
<br />
''Contoh''(untuk keymap norwegia) :<br />
<br />
Pada console keymap screen pilih<br />
no-latin1<br />
Pada console font screen pilih<br />
lat0-16<br />
<br />
Memilih "default8x16.psfu.gz" sebagai font console adalah pilihan aman.<br />
<br />
===Start the Installation===<br />
Enter<br />
/arch/setup <br />
to start the installation. <br />
<br />
====Select an installation source====<br />
You will be prompted for an installation source. Choose CD if you are using a base or full (current) ISO, or choose FTP if you are using the FTP ISO.<br />
<br />
====Prepare Hard Drive====<br />
Select the first menu entry "Prepare Hard Drive". Beware that "Auto-Prepare" may not be a safe choice because it will erase the entire hard drive.<br />
Here we will manually partition the hard drive. Choose "2. Partition Hard Drives", select the hard drive you want (/dev/sdx), and create some partitions. <br />
<br />
<br />
=====Partitions=====<br />
<br />
<br />
A partition is a section of hard disk space that will appear as a separate disk, and can be added to your Arch Linux file system. Partitions are broken up into "Primary", "Extended", and "Logical". <br />
Primary partitions can be bootable, and are limited to 4. For example, if you are using a PC with a single SATA drive, the first primary partition will be referred to as sda1. The second primary will be referred to as sda2, then sda3, and sda4. Beyond 4 partitions, we are forced to use an extended partition which will contain logical partitions.<br />
<br />
Extended partitions are not usable by themselves; they are merely a "container" for logical partitions. Logical partitions must be contained within this extended partition. When partitioning a disk, one can see this numbering scheme by creating primary partitions sda1-3 followed by creating an extended partition, sda4, and then creating logical partition(s) within the extended partition; sda5, sda6, and so on.)<br />
<br />
<br />
Everyone has a different opinion on how best to partition the disk. What you need at the least is one primary partition which contains the root [http://en.wikipedia.org/wiki/File_system Filesystem] ( / ) and one for swap. Other candidates for separate partitions are /boot (which mainly contains the kernel) and /home (which contains the user data). It is good practice to have / and /home on separate partitions. This makes it possible to reinstall Arch Linux (or even another distro) for any reason, while keeping your data, music, pictures, and desktop environment preferences.<br />
<br />
In this example guide, we will stick with one partition for /, one partition for /home, and a swap partition.<br />
<br />
=====Swap Partition=====<br />
A swap partition is a place on your hard drive where "virtual ram" resides. If your processes need more RAM than is physically available, Linux can't fulfill the request and an error occurs. A swap partition helps in this situation by supplementing the physical RAM with virtual RAM. Linux uses the space on the hard disk to store the information that won't fit into the physical RAM any more (it's actually a bit more complex because Linux tries to put information into the swap space that isn't frequently used). Because a hard disk is very slow compared to physical RAM, this is only<br />
a makeshift. <br />
<br />
<br />
Ask two people about a swap partition and you will get four different answers. If you have plenty of RAM (more than 1024 MB) it may be possible to not use a swap partition at all. Some people suggest using twice the amount of physical RAM, while others recommend not using more than 1024 MB. I believe keeping the swap size between 512 MB and 1 GB is a good choice. Therefore, we will create a 1 GB swap space in this example.<br />
<br />
Let's start creating the '''primary partition''' that will contain the '''root''' filesystem. Choose New -> Primary and enter the size you want (something between 4 and 8 GB is a good choice for a full-featured Linux system). Put the partition at the beginning of the disk. Select the newly created partition and choose "Bootable" to make this partition bootable. Add another '''partition for your home directory'''. Choose another primary partition and set the size to a value you like. The size really depends on what your users store in their home directories, so I cannot make any suggestions. The size may vary between a few hundred megabytes for some office documents up to hundreds of gigabytes for videos and MP3s. If you <br />
want to use the whole space on your hard disc, use the remaining space minus 512 MB - 1 GB for the size. At last we<br />
create a third '''partition for swap'''. Select a size between 512 MB and 1 GB and change the type to 82 (Linux swap / Solaris).<br />
<br />
This is what your Layout should look like (size may vary depending on your decisions):<br />
<br />
Name Flags Part Type FS Type [Label] Size (MB)<br />
-------------------------------------------------------------------------<br />
sda1 Boot Primary Linux (4096 - 8192)<br />
sda2 Primary Linux (> 100)<br />
sda3 Primary Linux swap / Solaris (512 - 1024)<br />
<br />
Choose Write and type yes. Beware that this operation may destroy data on your disk if you deleted partitions. Choose Quit to leave the partitioner. <br />
Choose Done to leave this menu and continue with "Set Filesystem Mountpoints".<br />
<br />
====Set File system Mountpoints====<br />
<br />
=====A few brief words about '''filesystems''' and "file systems":=====<br />
<br />
Technically, and for accuracy, a '''filesystem''' is a data format for information throughput, whereas a "file system" (notice the space) is a term referring to the layout of all files and directories on a given system. (In our case, the hierarchical UNIX file system.) Therefore, when you are asked if you want to create a '''filesystem''', you are being asked if you want to '''format''' the particular partition... but when you are asked for mount points, you are providing where the given partition will reside in your Arch Linux "file system". Let's begin.<br />
<br />
First you will be asked for your swap partition. Choose the appropriate partition (sda3 in this example). You will be asked if you want to create a swap filesystem; select yes. Next, choose where to mount the / (root) directory (sda1 in the example). You will be asked what kind of filesystem you want.<br />
<br />
Again, ask two people which filesystem to choose and you will get five different answers. Each one has its advantages and disadvantages. Here is a very brief overview of supported filesystems.<br />
<br />
1. '''ext2''' - Old, reliable GNU/Linux filesystem. Fast, and very stable, but without journaling.<br />
<br />
2. '''ext3''' - Essentially the ext2 system, but with journaling support. ''Slightly'' slower than ext2 and other filesystems. '''Extremely''' stable and the most widely used, supported, and developed.<br />
<br />
3. '''ReiserFS''' - Hans Reiser's high-performance journaling FS uses a very interesting method of data throughput. ReiserFS is very fast, especially when dealing with many small files. ReiserFS is quite well established and stable.<br />
<br />
4. '''JFS''' - IBM's Journaling FS. JFS is quite well established, fast, and stable.<br />
<br />
5. '''XFS''' - is a fast journaling filesystem which is best suited for large files, greater than 1 GB in size. Slower with small files. Quite stable.<br />
<br />
A major difference is [http://en.wikipedia.org/wiki/Journaling_file_system journaling] (something similar to transaction logs in database environments). All filesystems except ext2 use journaling. ext3 is completely compatible with ext2, so you can mount it even with very-old rescue CDs. A safe choice for the root partition is ext3. ReiserFS, XFS, and JFS are also OK to use because GRUB (the boot manager which we will install later) can boot from them too. Create the filesystem (format the partition) by selecting yes. You will now be prompted to add any additional partitions. In our example, only sda2 is remaining. Choose a filesystem type and mount it as /home. Again, create the filesystem and choose Done. Return to main menu.<br />
<br />
===Select Packages===<br />
Now we shall select packages to install in our system. Choose CD as source and select the appropriate CD drive if you have more than one.<br />
Since this guide is geared toward a '''base''' installation, choose the base category (keeping all base packages selected is a safe choice). If you chose the current ISO rather than the base ISO, it is up to you if you want to select more packages, but we will show you later how to install additional, up-to-date software more easily, rather than installing and reinstalling. (Since the install CD you are using has been created, there are no doubt numerous updates available for packages contained therein, and installing additional up-to-date software via pacman will be covered below.) If you are '''sure''' you will not be needing certain packages (for instance, a filesystem type you don't need, ISDN, or PPPoE support), feel free to remove them from the base package selection. <br />
<br />
Step forward to "Install Packages".<br />
<br />
===Install Packages===<br />
This is an easy task because everything happens automatically. Get yourself a cup of coffee (if you're into coffee ;)) and wait until the installation has finished (press continue if needed). Drink quickly, because the Arch Linux base packages install in just a couple of minutes.<br />
<br />
===Configure The System===<br />
You will be asked if you want to choose hwdetect to gather some information for your configuration. This is recommended so you should choose this option. <br />
Now you will be asked if you need support for booting from USB devices, FireWire devices, PCMCIA devices, NFS shares, software RAID arrays, LVM2 volumes, and encrypted volumes. Choose yes if you need it; in our example nothing is needed. Now you will be asked which text editor you want to use; choose [http://en.wikipedia.org/wiki/Nano_%28text_editor%29 nano] if you are not familiar with [http://en.wikipedia.org/wiki/Vim_%28text_editor%29 vi/vim]. You will now get a menu with most important config files for your system. We will do only some minor tweaks at this time. If you want to look up the available options as stated in rc.conf just press Alt+F2 to get a shell, look it up, and switch back to the installer with Alt+F1. <br />
<br />
=====/etc/rc.conf=====<br />
<br />
* Change your LOCALE if needed (e.g. "de_DE.utf8") (This locale must coincide with /etc/locale.gen. '''See below'''.)<br />
* Change your TIMEZONE if needed (e.g. "Europe/Berlin")<br />
* Change your KEYMAP if needed (e.g. "de-latin1-nodeadkeys")<br />
<br />
* Change MODULES if you know that an important module is missing (hwdetect should have filled in the most important modules)<br />
* Change your HOSTNAME<br />
* Change your Network settings:<br />
** Don't modify the lo line<br />
** Adjust the IP address, netmask and broadcast address if you are using a static IP<br />
** Set eth0="dhcp" if you have a router which dynamically assigns an IP address<br />
** If you have a static IP set the gateway address to the one of your router and remove the ! in front of the ROUTES entry<br />
=====About DAEMONS=====<br />
You don't have to change the [[daemons]] line at this time, but it is useful to explain what daemons are, because we need them later in this guide. Analogous to a Windows service, a daemon is a program that runs in the background, waiting for events to occur and offering services. A good example is a webserver that waits for a request to deliver a page or an SSH server waiting for someone trying to log in. While these are full-featured applications, there are daemons whose work is not that visible. Examples are a daemon which writes messages into a log file (e.g. syslog, metalog), a daemon which lowers your CPU's frequency if your system has nothing to do, and a daemon which offers you a graphical login (e.g. gdm, kdm). All these programs can be added to the daemons line and will be started when the system boots. Useful daemons will be presented during this guide.<br />
<br />
Use Ctrl+X to leave the editor.<br />
<br />
=====/etc/hosts=====<br />
Add the desired ''hostname'' (the one you set in rc.conf before) so that it looks like this:<br />
127.0.0.1 localhost.localdomain localhost ''yourhostname''<br />
This format, '''including the 'localhost' entries''', is required for program compatibility.<br />
For most users, simply adding the ''hostname'' to the end of the default line will work, however, some users recommend using the following syntax:<br />
127.0.0.1 ''yourhostname''.domain.org localhost.localdomain localhost ''yourhostname''<br />
If you use a static IP, add another line using the syntax: <static-ip> hostname.domainname.org hostname, <br />
e.g.:<br />
192.168.1.100 yourhostname.domain.org yourhostname<br />
<br />
===== /etc/fstab, mkinitcpio.conf and modprobe.conf=====<br />
We shouldn't need to edit mkinitcpio.conf, or modprobe.conf at this point. mkinitcpio configures the ramdisk (e.g. booting from RAID, encrypted volumes) and modprobe can be used to set some special config options for the modules).<br />
<br />
If you are planning on using the hal daemon to automate the mounting of disks, optical drives, usb drives, etc., you may wish to edit /etc/fstab by commenting out the entries for cdrom, floppy, and dvd.<br />
<br />
=====/etc/resolv.conf (for Static IP)=====<br />
If you use a static IP, set your DNS servers in /etc/[[resolv.conf]] (nameserver <ip-address>). You may have as many as you wish.<br />
<br />
If you are using a router, you will probably want to specify your DNS servers in the router itself, and merely point to it from your resolv.conf, using your router's IP (which is also your gateway from /etc/rc.conf), e.g.:<br />
nameserver 192.168.1.1<br />
Alternatively, add your preferred servers one by one, e.g.:<br />
nameserver 4.2.2.1<br />
nameserver 4.2.2.2<br />
<br />
=====/etc/locale.gen=====<br />
Choose the locale(s) you need (remove the # in front of the lines you want), e.g.:<br />
en_US ISO-8859-1<br />
en_US.UTF-8 <br />
('''Your locale must coincide with the one specified in /etc/rc.conf above.''')<br />
=====Root password=====<br />
Finally, set a root password and make sure that you remember it later. Return to the main menu and continue with installing a kernel.<br />
<br />
===Install Kernel===<br />
Not many choices here; choose v2.6 and continue. You may want to switch your kernel later. A fallback image will be created, keeping mkinitcpio as it is shown as a safe choice. Continue with installing a bootloader.<br />
<br />
===Install Bootloader===<br />
Because we have no secondary operating system in our example, we will need a bootloader. [http://www.gnu.org/software/grub/ GNU GRUB] is the recommended bootloader. Alternatively, you may choose [http://lilo.go.dyndns.org/ LILO]. The shown GRUB configuration (/boot/grub/menu.lst) should be sufficient. The only thing you may want to alter is the resolution of the console. Add<br />
a vga=<number> to the first kernel line. (A table of resolutions and the corresponding numbers is printed in the menu.lst.) <br />
title Arch Linux (Main)<br />
root (hd0,0)<br />
kernel /boot/vmlinuz26 root=/dev/sda1 ro vga=773<br />
initrd /boot/kernel26.img<br />
The "vga=773" argument will give a 1024x768 framebuffer with 256 color depth.<br />
<br />
Exit the install and type reboot.<br />
<br />
If everything goes well, your new Arch Linux system will boot up and finish with a login prompt (you may want to change the boot order in your BIOS back to booting from hard disk).<br />
<br />
Congratulations, and welcome to your shiny, new Arch Linux base system!<br />
<br />
==Configuring the base system ==<br />
Your new Arch Linux base system is now a functional GNU/Linux operating system ready for customization. From here, you may build this elegant set of tools into whatever you wish or require for your purposes!<br />
Let's begin.<br />
-----<br />
Login with your root account. We will configure pacman and update the system as root, then add a normal user. <br />
<br />
===Configuring pacman===<br />
Edit /etc/pacman.conf<br />
nano -w /etc/pacman.conf<br />
and remove the # in front of the "Include = /etc/pacman.d/community" and "[community]" lines to enable Arch's community repository, which offers many useful applications. Now edit /etc/pacman.d/community and move the mirrors which are located nearest to you up (if you use nano, Alt+A starts selecting an area, cursor down marks the lines, Ctrl+K cuts the selected area and Ctrl+U uncuts it). Repeat this for all files in /etc/pacman.d/.<br />
<br />
===Configuring the network (if necessary)===<br />
<br />
If everything went fine, you should have a working network. Try to ping www.google.com to verify this.<br />
ping -c 3 www.google.com<br />
<br />
If you have successfully established a network connection, continue with "Update, Sync and Upgrade the system with pacman".<br />
<br />
If, after trying to ping www.google.com, you get an "unknown host" error, you may conclude that your network is not configured. You may choose to double-check the following files for integrity and proper settings:<br />
<br />
'''/etc/rc.conf''' # Specifically, check your HOSTNAME= and NETWORKING section<br />
<br />
'''/etc/hosts''' # Double-check your format. (See above.)<br />
<br />
'''/etc/resolv.conf''' # If you are using a static IP. If you are using DHCP, this file will be dynamically created and destroyed by default, but can be changed to your preference. (See [[Network]].)<br />
<br />
Advanced instructions for configuring the network can be found in the [[Network]] article.<br />
<br />
====Wired LAN====<br />
<br />
Check your Ethernet with<br />
ifconfig<br />
where you should see an entry for eth0. If required, you can set a new static IP with<br />
ifconfig eth0 <ip address> netmask <netmask> up <br />
and the default gateway with<br />
route add default gw <ip address of the gateway><br />
Check to see if /etc/resolv.conf contains your DNS server and add it if it is missing. <br />
Check your network again with ping www.google.de. If everything is working now, adjust /etc/rc.conf as described in section 2.6 (static IP). If you have a DHCP server/router in your network try<br />
dhcpcd eth0<br />
If this is working, adjust /etc/rc.conf as described in section 2.6 (dynamic IP).<br />
<br />
====Wireless LAN====<br />
[[Wireless Setup]]<br />
(TODO) Simplify and generalize it, link only for more-advanced stuff<br />
<br />
====Analog Modem====<br />
To be able to use a Hayes-compatible, external, analog modem, you need to at least have the ppp package installed. Modify the file /etc/ppp/options to suit your needs and according to man pppd. You will need to define a chat script to supply your username and password to the ISP after the initial connection has been established. The manpages for pppd and chat have examples in them that should suffice to get a connection up and running if you're either experienced or stubborn enough. With udev, your serial ports usually are /dev/tts/0 and /dev/tts/1.<br />
Tip: Read [[Dialup without a dialer HOWTO]].<br />
<br />
Instead of fighting a glorious battle with the plain pppd, you may opt to install wvdial or a similar tool to ease the setup process considerably. In case you're using a so-called WinModem, which is basically a PCI plugin card working as an internal analog modem, you should indulge in the vast information found on the [http://www.linmodems.org/ LinModem] homepage.<br />
<br />
====ISDN====<br />
<br />
Setting up ISDN is done in three steps:<br />
# Install and configure hardware<br />
# Install and configure the ISDN utilities<br />
# Add settings for your ISP <br />
<br />
The current Arch stock kernels include the necessary ISDN modules, meaning that you won't need to recompile your kernel unless you're about to use rather odd ISDN hardware. After physically installing your ISDN card in your machine or plugging in your USB ISDN-Box, you can try loading the modules with modprobe. Nearly all passive ISDN PCI cards are handled by the hisax module, which needs two parameters: type and protocol. You must set protocol to '1' if your country uses the 1TR6 standard, '2' if it uses EuroISDN (EDSS1), '3' if you're hooked to a so-called leased-line without D-channel, and '4' for US NI1.<br />
<br />
Details on all those settings and how to set them is included in the kernel documentation, more specifically in the isdn subdirectory, and available online. The type parameter depends on your card; a list of all possible types can be found in the README.HiSax kernel documentation. Choose your card and load the module with the appropriate options like this:<br />
<br />
modprobe hisax type=18 protocol=2<br />
<br />
This will load the hisax module for my ELSA Quickstep 1000PCI, being used in Germany with the EDSS1 protocol. You should find helpful debugging output in your /var/log/everything.log file, in which you should see your card being prepared for action. Please note that you will probably need to load some USB modules before you can work with an external USB ISDN Adapter.<br />
<br />
Once you have confirmed that your card works with certain settings, you can add the module options to your /etc/modprobe.conf:<br />
<br />
alias ippp0 hisax<br />
options hisax type=18 protocol=2<br />
<br />
Alternatively, you can add only the options line here, and add hisax to your MODULES array in the rc.conf. It's your choice, really, but this example has the advantage that the module will not be loaded until it's really needed.<br />
<br />
That being done, you should have working, supported hardware. Now you need the basic utilities to actually use it!<br />
<br />
Install the isdn4k-utils package, and read the manpage to isdnctrl; it'll get you started. Further down in the manpage you will find explanations on how to create a configuration file that can be parsed by isdnctrl, as well as some helpful setup examples. Please note that you have to add your SPID to your MSN setting separated by a colon if you use US NI1.<br />
<br />
After you have configured your ISDN card with the isdnctrl utility, you should be able to dial into the machine you specified with the PHONE_OUT parameter, but fail the username and password authentication. To make this work add your username and password to /etc/ppp/pap-secrets or /etc/ppp/chap-secrets as if you were configuring a normal analogous PPP link, depending on which protocol your ISP uses for authentication. If in doubt, put your data into both files.<br />
<br />
If you set up everything correctly, you should now be able to establish a dial-up connection with<br />
isdnctrl dial ippp0<br />
as root. If you have any problems, remember to check the logfiles!<br />
<br />
====DSL (PPPoE)====<br />
<br />
These instructions are relevant to you only if your PC itself is supposed to manage the connection to your ISP. You do not need to do anything but define a correct default gateway if you are using a separate router of some sort to do the grunt work.<br />
<br />
Before you can use your DSL online connection, you will have to physically install the network card that is supposed to be connected to the DSL-Modem into your computer. After adding your newly installed network card to the modules.conf/modprobe.conf or the MODULES array, you should install the rp-pppoe package and run the pppoe-setup script to configure your connection. After you have entered all the data, you can connect and disconnect your line with<br />
<br />
/etc/rc.d/adsl start<br />
<br />
and<br />
<br />
/etc/rc.d/adsl stop<br />
<br />
respectively. The setup usually is rather easy and straightforward, but feel free to read the manpages for hints. If you want to automatically dial in on boot-up, add adsl to your DAEMONS array.<br />
<br />
==Update, Sync and Upgrade the system with [[pacman]]==<br />
Now we will update the system using [[pacman]], the package manager of Arch Linux. Pacman is fast, simple, and extremely powerful. It manages your entire package system and allows installation, package removal, package downgrade (through cache), custom compiled package handling, automatic dependency resolution, and much more.<br />
<br />
Update, sync, and '''upgrade''' your entire new system with:<br />
pacman -Syu<br />
pacman will now fetch the latest information about available packages and perform all available upgrades. (You may be prompted to upgrade pacman itself at this point. If so, say yes, and then reissue the pacman -Syu command when finished.)<br />
<br />
=====''Take note as to whether a kernel upgrade is occurring!''=====<br />
<br />
If the kernel is upgraded, modules such as nvidia will be rendered inoperable, since the new, upgraded versions will be built against the newer kernel, and your system is currently using an older one. A reboot will be necessary.<br />
<br />
=====The beauty of the rolling release=====<br />
Keep in mind that Arch is a '''rolling release''' distribution. This means there is never a reason to reinstall or perform elaborate system rebuilds to upgrade to the newest version. Simply issuing '''pacman -Syu''' periodically keeps your entire system up-to-date and on the bleeding edge. At the end of this upgrade, your system is completely current.<br />
<br />
=====Get familiar with pacman=====<br />
Pacman is the Arch user's best friend. It is highly recommended to study and learn how to use the pacman tool. Try:<br />
man pacman<br />
Check out the bottom of this article, and look up the [[pacman]] wiki entries at your leisure.<br />
<br />
<br />
<br />
===Add a user and setup groups===<br />
You should not do your everyday work using the root account. It is more than poor practice; it is dangerous. Root is for administrative tasks. Instead, add a normal user account using:<br />
adduser<br />
While most default options are safe to use, you may want to add at least audio and wheel to your additional groups. <br />
Audio allows your user to use the audio card, while wheel allows switching to the root account with su. Other groups to be added, (separated by a comma) include:<br />
<br />
*disk - for managing disks, including USB flash drives and such<br />
<br />
*storage - for managing storage devices<br />
<br />
*video - for managing video tasks<br />
<br />
*optical - for managing tasks pertaining to the optical drive(s)<br />
<br />
*floppy - for access to a floppy if necessary<br />
<br />
*lp - for managing printing tasks<br />
<br />
You may also consider adding optical to your additional groups to enable CD/DVD recording from your user account.<br />
<br />
See the [http://wiki.archlinux.org/index.php/Groups Groups] article to understand what groups you need to be a member of. <br />
You may also add your user to the desired groups like so, (as root):<br />
usermod -aG audio,video,floppy,lp,optical,network,storage,wheel USERNAME<br />
<br />
==Installing and configuring Hardware==<br />
===Configure the audio card===<br />
Your audio card should already be working, but you can't hear anything because it is muted by default. Install the alsa-utils <br />
pacman -S alsa-utils<br />
and use alsamixer to adjust the channels: <br />
alsamixer<br />
Unmute the Master and PCM channels by scrolling to them with cursor left/right and pressing '''M'''. Increase the volume levels with the cursor-up key. (70-90 Should be a safe range.) Leave alsamixer by pressing ESC and store the settings with<br />
alsactl store<br />
If you plan on using a desktop environment such as GNOME or KDE and would prefer that alsa remember your settings when you change them, do not execute the above command--your volume settings will be remembered automatically.<br />
Add alsa to your DAEMONS section in /etc/rc.conf to automatically restore the mixer on boot-up.<br />
nano /etc/rc.conf<br />
<br />
DAEMONS=(syslog-ng network crond '''alsa''')<br />
<br />
===Configuring CPU frequency scaling===<br />
Modern processors can decrease their frequency and voltage to reduce heat and power consumption. Less heat leads to a quieter system; even a desktop system will benefit from it. Install cpufrequtils with<br />
pacman -S cpufrequtils<br />
and add cpufreq to your daemons in /etc/rc.conf. Edit the config file /etc/conf.d/cpufreq and change <br />
governor="conservative"<br />
which dynamically increases the CPU frequency if needed (which is a safe choice on desktop systems too). Alter min_freq and max_freq to match your system's CPU spec. If you don't know the frequencies, run ''cpufreq-info'' after loading one of the frequency scaling modules. Add the frequency scaling modules to your /etc/rc.conf modules line. Most modern notebooks and desktops can simply use the ''acpi-cpufreq'' driver, however other options include the ''p4-clockmod, powernow-k6, powernow-k7, powernow-k8, and speedstep-centrino'' drivers. Load the module with<br />
modprobe <modulname> <br />
and start cpufreq with<br />
/etc/rc.d/cpufreq start<br />
For more details, see [[Cpufrequtils]]<br />
<br />
===Additional tweaks for laptops===<br />
ACPI support is needed if you want to use some special functions on your notebook (e.g. sleep, sleep when lid is closed, special keys...). Install acpid <br />
pacman -S acpid<br />
and add it to the daemons in /etc/rc.conf (acpid). Start it with<br />
/etc/rc.d/acpid start<br />
<br />
More-specific information about Arch Linux on various Laptops can be found at [[:Category:Laptops (English)]]<br />
<br />
==Installing and configuring X==<br />
The X Window System (commonly X11, or just simply X) is a networking and display protocol which provides windowing on bitmap displays. It provides the standard toolkit and protocol to build graphical user interfaces (GUIs) on Unix-like operating systems.<br />
<br />
X provides the basic framework, or primitives, for building GUI environments: drawing and moving windows on the screen and interacting with a mouse and/or keyboard. X does not mandate the user interface — individual client programs handle this. <br />
-----<br />
Now we will install the base Xorg packages using pacman. <br />
<br />
As root, do:<br />
pacman -S xorg-server xorg-xkb-utils xorg-xauth xorg-server-utils xorg-xinit xf86-video-vesa xf86-input-mouse xf86-input-keyboard<br />
(The old xorg group package has been removed. If it reappears, the option to use it will be given here.)<br />
Now we have the base packages we need for running the X Server. You should add the driver for your graphics card now (e.g. xf86-video-<name>). If you need a list of all '''open-source''' video drivers, do: <br />
pacman -Ss xf86-video | less<br />
If you don't know what graphics card you are using, do:<br />
lspci | grep VGA<br />
Here is a list of '''open source''' drivers, and corresponding video chipsets.<br />
*'''xf86-video-apm''' Alliance ProMotion video driver<br />
*'''xf86-video-ark''' ark video driver<br />
*'''xf86-video-ati''' ati video driver<br />
*'''xf86-video-chips''' Chips and Technologies video driver<br />
*'''xf86-video-cirrus''' Cirrus Logic video driver<br />
*'''xf86-video-dummy''' dummy video driver<br />
*'''xf86-video-fbdev''' framebuffer video driver<br />
*'''xf86-video-glint''' GLINT/Permedia video driver<br />
*'''xf86-video-i128''' Number 0 i128 video driver<br />
*'''xf86-video-i740''' Intel i740 video driver<br />
*'''xf86-video-i810''' Intel i810/i830/i9xx video drivers<br />
*'''xf86-video-imstt''' Integrated Micro Solutions Twin Turbo vidoe driver<br />
*'''xf86-video-mga''' mga video driver (Matrox Graphics Adapter)<br />
*'''xf86-video-neomagic''' neomagic video driver<br />
*'''xf86-video-nv''' nvidia nv video driver<br />
*'''xf86-video-rendition''' Rendition video driver<br />
*'''xf86-video-s3''' S3 video driver<br />
*'''xf86-video-s3virge''' S3 Virge video driver<br />
*'''xf86-video-savage''' savage video driver<br />
*'''xf86-video-siliconmotion''' siliconmotion video driver<br />
*'''xf86-video-sis''' SiS video driver<br />
*'''xf86-video-sisusb''' SiS USB video driver<br />
*'''xf86-video-tdfx''' tdfx video driver<br />
*'''xf86-video-trident''' Trident video driver<br />
*'''xf86-video-tseng''' tseng video driver<br />
*'''xf86-video-unichrome''' Unichrome video drivers<br />
*'''xf86-video-v4l''' v4l video driver<br />
*'''xf86-video-vesa''' vesa video driver<br />
*'''xf86-video-vga''' VGA 16 color video driver<br />
*'''xf86-video-via''' via video driver<br />
*'''xf86-video-vmware ''' vmware video driver<br />
*'''xf86-video-voodoo ''' voodoo video driver<br />
<br />
* Note that the '''vesa''' driver is the most generic, and should work with almost any modern video chipset. If you cannot find a suitable driver for your video chipset, vesa '''should''' work.<br />
<br />
*If you have an nVIDIA or ATI video adapter, you may wish to install the proprietary nVIDIA or ATI drivers. '''Installing proprietary video drivers is covered below''' under "Using proprietary Graphics Driver (nVIDIA, ATI)"<br />
<br />
Install the appropriate video driver for your video card/onboard video. e.g.:<br />
pacman -S xf86-video-i810<br />
(for the intel 810 chipset driver.)<br />
<br />
==Create /etc/X11/xorg.conf==<br />
=====What is /etc/X11/xorg.conf?=====<br />
/etc/X11/xorg.conf is the '''main configuration file''' for your '''X''' Window System, the foundation of your '''G'''raphical '''U'''ser '''I'''nterface. It is a plain text file ordered into sections and subsections. Important sections are ''Files, InputDevice, Monitor, Modes, Screen, Device, and ServerLayout''. Sections can appear in any order and there may be more than one section of each kind, for example, if you have more than one monitor, say a video projector and an on board LCD of a notebook. <br />
------<br />
By default, you will not have an Xorg config file, and with the newest versions of Xorg, you don't need one ''if'' the autodetection ''works satisfactorily'' and you don't need to turn on features such as aiglx and so on. ''Most people will still find that they need to generate a config file, however.''<br />
<br />
There are several ways of creating /etc/X11/xorg.conf:<br />
<br />
*The Xorg way to make a basic config file is to run<br />
Xorg -configure<br />
which will create /root/xorg.conf. Move the generated config file as appropriate, e.g.<br />
mv /root/xorg.conf.new /etc/X11/xorg.conf<br />
<br />
*Another way of making an xorg.conf without getting your hands dirty is Arch Linux's own developer tpowa's tool:<br />
hwd -xa<br />
hwd (to see the various options)<br />
<br />
*The proprietary video drivers also have tools to edit xorg.conf to configure the drivers (see below). These are <br />
aticonfig<br />
and<br />
nvidia-xconfig<br />
<br />
However, you should not be a stranger to editing the config file by hand (as this is usually needed to fix various issues from time to time):<br />
<br />
nano /etc/X11/xorg.conf<br />
<br />
Edit your /etc/X11/xorg.conf to specify your video driver. e.g.:<br />
Section "Device"<br />
Driver "i810"<br />
<br />
=====Simple baseline X test=====<br />
<br />
At this point, you should have xorg installed, with a suitable video driver and an /etc/X11/xorg.conf configuration file. If you want to test your configuration quickly, before installing a complete desktop environment, install '''xterm'''. Xterm is a very simple terminal emulator which runs in the X Server environment. Xterm will allow us to effectively test if your video driver and /etc/X11/xorg.conf are properly configured. Alternatively, you may wish to test if the X autodetection works satisfactorily, in the absence of /etc/X11/xorg.conf.<br />
pacman -S xterm<br />
Edit your /home/username/.xinitrc file, '''as normal user''', to dictate which X Server event is called upon with the 'startx' command:<br />
<br />
su yourusername<br />
<br />
nano ~/.xinitrc<br />
<br />
and add (or uncomment)<br />
<br />
exec xterm<br />
<br />
So that it looks like this:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
exec xterm<br />
# exec wmaker<br />
# exec startkde<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
<br />
(Be sure to have only one uncommented line in your ~/.xinitrc ) If you do not have ~/.xinitrc, simply create one with the above information.<br />
<br />
Start X Server as normal user, with:<br />
<br />
startx<br />
You should have an xterm session open up. You can exit the X Server with Ctrl+Alt+Backspace, or by typing "exit". If you have problems starting X, you can look for errors in the /var/log/Xorg.0.log file and on the console output of the console you started X from.<br />
<br />
Now you might want to install a graphical login manager (to avoid having to type startx everytime you start the computer) like [[GDM]] or [[KDM]], but this ''could'' wait, and advanced instructions for Xorg configuration can be found in the [[Xorg]] article.<br />
<br />
===Adjusting Keyboard Layout===<br />
You may want to change your keyboard layout. To do this edit your /etc/X11/xorg.conf and add these lines in the Input Section (keyboard0) (the example shows a German keyboard layout with no dead keys; alter this to fit your needs).<br />
Option "XkbLayout" "de"<br />
Option "XkbVariant" "nodeadkeys"<br />
<br />
===Adjusting Mouse for scroll wheel===<br />
While your mouse should be working out of the box, you may want to use your scroll wheel. Add this to your Input Section (mouse0):<br />
Option "ZAxisMapping" "4 5 6 7"<br />
<br />
===evdev===<br />
If you have a modern USB mouse with several thumb buttons and/or functions, you will most likely want to install the evdev mouse driver, which will allow you to exploit the full functionality of your mouse:<br />
<br />
pacman -S xf86-input-evdev<br />
Load the driver:<br />
modprobe evdev<br />
Find your mouse name:<br />
cat /proc/bus/input/devices | egrep "Name"<br />
Using the mouse name, configure your /etc/X11/xorg.conf InputDevice section accordingly, e.g.:<br />
Section "InputDevice"<br />
Identifier "Evdev Mouse"<br />
Driver "evdev"<br />
Option "Name" "Logitech USB-PS/2 Optical Mouse"<br />
Option "CorePointer"<br />
EndSection<br />
You must have only '''one''' "CorePointer" device specified in /etc/X11/xorg.conf, so be sure to comment out any other mouse entries until you feel safe removing the old, unused entries.<br />
<br />
Also edit the ServerLayout section to include Evdev Mouse as the CorePointer, e.g.:<br />
Section "ServerLayout"<br />
Identifier "Layout0"<br />
Screen 0 "Screen0"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
InputDevice "Evdev Mouse" "CorePointer"<br />
<br />
===Using proprietary Graphics Driver (nVIDIA, ATI)===<br />
You may choose to use the proprietary video drivers from nVIDIA or ATI. <br />
====nVIDIA Graphic Cards====<br />
The nVIDIA proprietary drivers are generally considered to be of excellent quality, and offer superior 3D performance.<br />
<br />
Before you configure your Graphics Card you will need to know which driver fits. Arch currently has 3 different drivers that each match a certain subset of Cards: <br />
<br />
'''1. nvidia-71xx''' ''for very old Cards like TNT and TNT2''<br />
<br />
'''2. nvidia-96xx''' ''slightly newer cards up to the GF 4''<br />
<br />
'''3. nvidia''' ''newest GPUs after the GF 4''<br />
<br />
Consult the nVIDIA-Homepage to see which one is for you. The difference is only for the installation; Configuration works the same with every driver.<br />
<br />
Install the appropriate nvidia driver, e.g.: <br />
pacman -S nvidia <br />
At this point, you have 3 choices as to how to proceed.<br />
<br />
*'''1.''' If you have no xorg.conf at all, or if you have an existing xorg.conf and want to '''generate a completely new one''' with the nVIDIA utility, back up the old one:<br />
mv /etc/X11/xorg.conf /etc/X11/xorg.old<br />
Then create the new /etc/X11/xorg.conf with<br />
nvidia-xconfig<br />
The nvidia-xconfig utility will usually create a very short, streamlined, easy-to-read xorg.conf<br />
<br />
It also has several options which will further specify the contents and options of the xorg.conf file.<br />
For example,<br />
nvidia-xconfig --composite --add-argb-glx-visuals<br />
<br />
For more detailed information, see nvidia-xconfig(1).<br />
<br />
*'''2.''' '''Expert Option:''' If you have an existing xorg.conf and want to keep it, edit your xorg manually as needed, and at the very least, adjust your '''Device''' Section by changing Driver "<olddrivername>" to Driver "nvidia".<br />
Section "Device"<br />
<br />
Driver "nvidia" <br />
*'''3.''' Alternatively, you may choose to keep your existing /etc/X11/xorg.conf, and run:<br />
nvidia-xconfig<br />
which will automatically '''update''' your /etc/X11/xorg.conf for use with the nVIDIA proprietary driver.<br />
<br />
Some useful tweaking options in the device section are (beware that these may not work on your system):<br />
Option "RenderAccel" "true"<br />
Option "NoLogo" "true"<br />
Option "AGPFastWrite" "true"<br />
Option "EnablePageFlip" "true"<br />
<br />
The nvidia-xconfig utility will automatically place the glx option in your xorg. If you did not use nvidia-xconfig, then you should add this to your module section:<br />
<br />
Load "glx"<br />
Double check your /etc/X11/xorg.conf to make sure your default depth, horizontal refresh, vertical refresh, and resolutions are acceptable.<br />
<br />
Logout and login.<br />
<br />
Start X server as normal user, to test your configuration:<br />
startx<br />
<br />
Advanced instructions for nvidia configuration can be found in the [[NVIDIA]] article.<br />
<br />
====ATI Graphic Cards====<br />
ATI owners have two options for drivers. If you are unsure which driver to use, please try the open-source one first. The open-source driver will suit most needs along with being generally less problematic.<br />
<br />
Install the '''proprietary''' ATI Driver with<br />
pacman -S fglrx<br />
Use the aticonfig tool to modify the xorg.conf. Note: The proprietary driver does not support [[AIGLX]]. To use [[Compiz]] or [[Beryl]] with this driver you would need to use [[XGL]].<br />
<br />
Install the '''open-source''' ATI Driver with<br />
pacman -S xf86-video-ati<br />
Currently, the performance of the open-source driver is not on par with that of the proprietary one. It also lacks TV-out, dual-link DVI support, and possibly other features. On the other hand, it supports Aiglx and has better dual-head support.<br />
<br />
Advanced instructions for ATI configuration can be found in the [[ATI | ATI wiki]].<br />
<br />
==Installing and configuring a Desktop Environment ==<br />
If you ask two people what the best Desktop Environment or Window Manager is, you will get six different answers. <br />
* If you want something full-featured and similar to Windows and Mac OSX, '''KDE''' is a good choice<br />
* If you want something more minimalist, which follows the K.I.S.S. principle more closely, '''GNOME''' is a good choice<br />
* If you have an older machine or want something lighter, '''xfce4''' is a good choice, still giving you a complete environment<br />
* If you need something even lighter, '''openbox, fluxbox or fvwm2''' may be right (not to mention all other lightweight window managers like '''windowmaker and twm''').<br />
* If you need something completely different, try '''ion, wmii, or dwm'''.<br />
<br />
===Install Fonts===<br />
At this point, you may want to install some good-looking fonts, '''before''' installing a desktop environment/window manager. Dejavu and bitstream-vera are nice font sets. For websites, you may want to have the Microsoft fonts too. Install with:<br />
pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera<br />
<br />
===GNOME===<br />
====About GNOME====<br />
The '''G'''NU '''N'''etwork '''O'''bject '''M'''odel '''E'''nvironment. The GNOME project provides two things: The GNOME desktop environment, an intuitive and attractive desktop for end-users, and the GNOME development platform, an extensive framework for building applications that integrate into the rest of the desktop.<br />
<br />
====Installation====<br />
Install GNOME with<br />
pacman -S gnome<br />
If you want a more-than-complete GNOME distribution with a lot of extras, do:<br />
pacman -S gnome-extra<br />
It's safe to choose all packages shown. <br />
=====Useful DAEMONS for GNOME=====<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. The '''hal''' daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The '''fam''' daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system. Both '''hal''' and '''fam''' make life easier for the GNOME user.<br />
<br />
You may want to install a graphical login manager. For GNOME, the '''gdm''' daemon is a good choice. Install gdm with<br />
pacman -S gdm<br />
You will almost certainly want the '''hal''' and '''fam''' daemons.<br />
<br />
Start hal and fam:<br />
/etc/rc.d/hal start<br />
<br />
/etc/rc.d/fam start<br />
<br />
Add them to your /etc/rc.conf DAEMONS section, so they will start on bootup:<br />
nano /etc/rc.conf<br />
<br />
DAEMONS=(syslog-ng network crond alsa '''hal fam gdm''')<br />
(If you prefer to log into the console and manually start X in the 'Slackware tradition', leave out gdm.)<br />
<br />
====~/.xinitrc====<br />
<br />
This file controls what occurs when you type 'startx'.<br />
<br />
Edit your /home/username/.xinitrc to utilize GNOME:<br />
<br />
nano ~/.xinitrc<br />
<br />
Uncomment the 'exec gnome-session' line so that it looks like this:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
#exec xterm<br />
#exec wmaker<br />
# exec startkde<br />
exec gnome-session<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
<br />
If you do not have a ~/.xinitrc file, simply create it with the above information. Remember, you must have only one uncommented line in your ~/.xinitrc. <br />
<br />
Switch to normal user:<br />
su username<br />
<br />
And test it with:<br />
startx<br />
<br />
You may want to install a terminal and an editor. I would recommend gnome-terminal (part of the group gnome-extra) and geany:<br />
pacman -S geany gnome-terminal<br />
<br />
Advanced instructions for installing and configuring GNOME can be found in the [[Gnome]] article.<br />
<br />
====Eye Candy====<br />
You may find the default GNOME theme and icons not very attractive. A nice gtk theme is murrine. Install it with<br />
pacman -S gtk-engine-murrine<br />
and select it with System->Preferences->Theme. You can find more themes, icons, and wallpaper at [http://www.gnome-look.org Gnome Look].<br />
<br />
===KDE===<br />
====About KDE====<br />
The '''K''' '''D'''esktop '''E'''nvironment. KDE is a powerful Free Software graphical desktop environment for Linux and Unix workstations. It combines ease of use, contemporary functionality, and outstanding graphical design with the technological superiority of UNIX-like operating systems.<br />
<br />
====Installation====<br />
Arch offers several versions of kde: '''kde, kdebase, and KDEmod'''. Choose '''one''' of the following, and continue below with '''"Useful KDE DAEMONS"''': <br />
<br />
'''1.)''' Package '''kde''' is the complete, vanilla KDE, ~300MB.<br />
pacman -S kde<br />
'''2.)''' Package '''kdebase''' is a slimmed-down version with less applications, ~80MB.<br />
pacman -S kdebase<br />
'''3.)''' Lastly, '''KDEmod''' is an Arch Linux exclusive, community-driven system which is modified for extreme performance and modularity. The KDEmod project website can be found at [http://kdemod.ath.cx/ http://kdemod.ath.cx/]. KDEmod is extremely fast, lightweight and responsive, with a pleasing, customized theme. <br />
<br />
To install KDEmod in 5 easy steps, just follow these installation instructions...<br />
Note: Before you start, please remember to read all of the install messages. They are fairly comprehensive and should solve any upcoming questions after the installation. If you cant scroll back to see all messages, just take a look into /var/log/pacman.log<br />
<br />
*1. Add the kdemod repo to your /etc/pacman.conf:<br />
nano /etc/pacman.conf<br />
Add one of these entries at the top of your server list:<br />
[kdemod]<br />
Server = http://kdemod.ath.cx/repo/current/i686<br />
for 32 bit Arch, or<br />
[kdemod]<br />
Server = http://kdemod.ath.cx/repo/current/x86_64<br />
for 64 bit Arch.<br />
<br />
*2. You must also activate the [community] repository in /etc/pacman.conf because KDEmod needs some packages from this repository. Make sure the following lines are uncommented:<br />
[community]<br />
Include = /etc/pacman.d/community<br />
<br />
<br />
*3. Update your package database with pacman -Syu. Now you can choose between two installations:<br />
<br />
pacman -S kdemod ''- installs a light base system''<br />
pacman -S kdemod-complete ''- installs the full KDE desktop''<br />
<br />
If you encounter any errors or conflicts at this step, check pacmans output, and if there are some unsolvable problems, tell us about them at the forums.<br />
*4. Install your localization. Take a look at the list of packages or simply do a pacman -Ss kdemod-kde-i18n to see which of them are already included.<br />
<br />
*5. Install all the extra apps you want. You can check out all available KDEmod packages by entering pacman -Sl kdemod<br />
<br />
====Useful KDE DAEMONS====<br />
<br />
KDE will require the '''hal''' ('''H'''ardware '''A'''bstraction '''L'''ayer) and '''fam''' ('''F'''ile '''A'''lteration '''M'''onitor) daemons. The '''kdm''' daemon is the '''K''' '''D'''isplay '''M'''anager, which provides a '''graphical login''', if desired.<br />
<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. The hal daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The fam daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system.. Both '''hal''' and '''fam''' make life easier for the KDE user, and are installed when you install KDE.<br />
<br />
Start hal and fam:<br />
<br />
/etc/rc.d/hal start<br />
<br />
/etc/rc.d/fam start<br />
<br />
Edit your DAEMONS section in /etc/rc.conf:<br />
nano /etc/rc.conf<br />
Add '''hal''' and '''fam''' to your DAEMONS section, to start them on bootup. If you prefer a graphical login, add '''kdm''' as well: <br />
DAEMONS=(syslog-ng network crond alsa '''hal fam kdm''')<br />
(If you prefer to log into the '''console''' and manually start X in the 'Slackware tradition', leave out kdm.)<br />
<br />
=====~/.xinitrc=====<br />
This file controls what occurs when you type 'startx'.<br />
<br />
Edit your /home/username/.xinitrc to utilize KDE:<br />
nano ~/.xinitrc<br />
Uncomment the 'exec startkde' line so that it looks like this:<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
#exec xterm<br />
#exec wmaker<br />
exec startkde<br />
# exec gnome-session<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
If you do not have a ~/.xinitrc file, simply create it with the above information. Remember, you must have only '''one''' uncommented line in your ~/.xinitrc.<br />
<br />
Switch to your normal user:<br />
su username<br />
Now try starting your X Server:<br />
startx<br />
<br />
Congratulations! Welcome to your KDE desktop environment on your new Arch Linux system! You may wish to continue by viewing [[Post Installation Tips]], or the rest of the information below.<br />
Advanced instructions for installing and configuring KDE can be found in the [[KDE]] article.<br />
<br />
===Xfce===<br />
====About Xfce====<br />
Xfce is a Desktop Environment, like GNOME or KDE. It contains a suite of apps like a root window app, window manager, file manager, panel, etc. Xfce is written using the GTK2 toolkit and contains its own development environment (libraries, daemons, etc) similar to other big DEs. Unlike GNOME or KDE, Xfce is lightweight and designed more around CDE than Windows or Mac. It has a much slower development cycle, but is very stable and extremely fast. Xfce is great for older hardware.<br />
<br />
====Installation====<br />
Install xfce with<br />
pacman -S xfce4 xfce4-goodies <br />
<br />
If you use kdm or gdm a new xfce session should have appeared. Alternatively, you can use<br />
startxfce4<br />
<br />
Advanced instructions for installing and configuring Xfce can be found in the [[Xfce]] article.<br />
<br />
===*box===<br />
====Fluxbox====<br />
Fluxbox © is yet another windowmanager for X.<br />
It's based on the Blackbox 0.61.1 code. Fluxbox looks like blackbox and handles styles, colors, window placement and similar things exactly like blackbox (100% theme/style compability).<br />
<br />
Install Fluxbox using <br />
pacman -S fluxbox fluxconf<br />
<br />
If you use gdm/kdm a new fluxbox session will be automatically added. Otherwise, you should modify your user's .xinitrc and add this to it:<br />
exec startfluxbox <br />
<br />
More information is available in the [[Fluxbox]] article.<br />
<br />
====Openbox====<br />
Openbox is a standards compliant, fast, light-weight, extensible window manager.<br />
<br />
Openbox works with your applications, and makes your desktop easier to manage. This is because the approach to its development was the opposite of what seems to be the general case for window managers. Openbox was written first to comply with standards and to work properly. Only when that was in place did the team turn to the visual interface.<br />
<br />
Openbox is fully functional as a stand-alone working environment, or can be used as a drop-in replacement for the default window manager in the GNOME or KDE desktop environments. <br />
<br />
Install openbox using<br />
pacman -S openbox obconf obmenu<br />
<br />
Once openbox is installed you will get a message to move menu.xml & rc.xml to ~/.config/openbox/ in your home directory:<br />
<br />
mkdir -p ~/.config/openbox/<br />
cp /etc/xdg/openbox/rc.xml ~/.config/openbox/<br />
cp /etc/xdg/openbox/menu.xml ~/.config/openbox/<br />
<br />
In the file "rc.xml" you can change various settings for Openbox (or you can use OBconf). In "menu.xml" you can change your right-click menu.<br />
<br />
To be able to log into openbox you can either go via graphical login using KDM/GDM or startx, in which case you will need to edit your ~/.xinitrc (as user) and add the following:<br />
<br />
exec openbox<br />
<br />
For KDM there is nothing left to do; openbox is listed in the sessions menu in KDM.<br />
<br />
Useful programs for openbox are:<br />
* PyPanel or LXpanel if you want a panel<br />
* feh if you want to set the background<br />
* ROX if you want a simple file manager and desktop icons<br />
<br />
More information is available in the [[Openbox]] article.<br />
<br />
===fvwm2===<br />
FVWM is an extremely powerful ICCCM-compliant multiple virtual desktop window manager for the X Window system. Development is active, and support is excellent. <br />
<br />
Install fvwm2 with<br />
pacman -S fvwm <br />
<br />
fvwm will automatically be listed in kdm/gdm in the sessions menu. Otherwise, add <br />
exec fvwm <br />
<br />
to your user's .xinitrc.<br />
<br />
Note that this stable version of fvwm is a few years old. If you want a more recent version of fvwm, there is a fvwm-devel package in the unstable repo.<br />
<br />
==HAL==<br />
Since you have now installed a desktop environment now would be a good time to also install HAL. HAL allows plug-and-play for your mobile phone, your iPod, your external HD's, etc. It will mount the device and make a nice visual icon on your desktop and/or in 'My Computer', allowing you to access the device after you have plugged it in instead of having to manually configure the /etc/fstab file or udev rules for each and every new device.<br />
<br />
KDE, GNOME and XFCE uses HAL.<br />
<br />
Refer to this article to install: [http://wiki.archlinux.org/index.php/HAL HAL]<br />
wikipedia: [http://en.wikipedia.org/wiki/HAL_(software) 1]<br />
<br />
==Useful Applications==<br />
This section will never be complete. It just shows some good applications for the everyday user. <br />
===Internet===<br />
<br />
=====Firefox=====<br />
The ever-popular Firefox web browser is available through pacman. Install with:<br />
<br />
pacman -S firefox<br />
Be sure and install 'flashplugin', 'mplayer', 'mplayer-plugin', and the 'codecs' packages for a complete web experience:<br />
pacman -S flashplugin mplayer mplayer-plugin codecs<br />
(The codecs package contains codecs for Quicktime and Realplayer content.)<br />
<br />
Thunderbird is useful for managing your emails. If you are using GNOME you may want to take a look at Epiphany and Evolution; if you are using KDE Konqueror and KMail could be your choice. If you want something completely different you can still use Opera. Finally, if you are working on the system console - or in a terminal session - you could use various text-based browsers like ELinks, Links and Lynx, and manage your emails with [[Mutt]]. Pidgin (previously known as Gaim) and Kopete are good instant messengers for GNOME and KDE, respectively. PSI and Gajim are perfect if you are using only Jabber or Google Talk.<br />
<br />
===Office===<br />
OpenOffice is a complete office suite (similar to Microsoft Office). Abiword is a good, small alternative word processor, and Gnumeric an Excel replacement for the GNOME desktop. KOffice is a complete office suite for the KDE Desktop. GIMP (or GIMPShop) is a pixel-based graphics program (similar to Adobe Photoshop), while Inkscape is a vector-based graphics program (like Adobe Illustrator). And, of course, Arch comes with a full set of LaTeX Programs.<br />
<br />
==Multimedia ==<br />
<br />
<br />
===Video Player===<br />
====VLC====<br />
VLC Player is a multimedia player for Linux. To install it, simply type the code below.<br />
<br />
pacman -S vlc<br />
<br />
(TODO) Instructions for VLC mozilla plug-in<br />
<br />
====Mplayer====<br />
MPlayer is a multimedia player for Linux. To install it, simply type the code below.<br />
<br />
pacman -S mplayer<br />
<br />
It also has a Mozilla plug-in for videos and streams embedded in web pages. To install it, simply type the code below.<br />
<br />
pacman -S mplayer-plugin<br />
<br />
If you use KDE, KMplayer is a better choice. It comes with a plug-in for videos and streams embedded in web pages, which works with Konqueror. To install it, simply type the code below.<br />
<br />
pacman -S kmplayer<br />
<br />
(TODO) GMPlayer instructions<br />
<br />
====GNOME====<br />
=====Totem=====<br />
[http://www.gnome.org/projects/totem/ Totem] is the official movie player of the GNOME desktop environment based on xine-lib or GStreamer (gstreamer is the default which installs with the arch totem package). It features a playlist, a full-screen mode, seek and volume controls, as well as keyboard navigation.<br />
It comes with added functionality such as:<br />
<br />
* Video thumbnailer for the file manager<br />
* Nautilus properties tab<br />
* Epiphany / Mozilla (Firefox) plugin to view movies inside your browser <br />
* Webcam utility (in development)<br />
<br />
Totem-xine is still the better choice if you want to watch DVDs.<br />
<br />
Totem is part of the gnome-extra group; the Totem webbrowser plugin isn't.<br />
<br />
To install separately:<br />
pacman -S totem<br />
<br />
To install the Totem webbrowser plugin:<br />
pacman -S totem-plugin<br />
<br />
====KDE====<br />
=====Kaffeine=====<br />
Kaffeine is a good option for KDE users. To install it, simply type the code below.<br />
<br />
pacman -S kaffeine<br />
<br />
===Audio Player===<br />
====Gnome/Xfce====<br />
=====Exaile=====<br />
[[Exaile]] is a music player written in Python that makes use of the GTK+ toolkit.<br />
=====Rhythmbox=====<br />
[http://www.gnome.org/projects/rhythmbox/ Rhythmbox] is an integrated music management application, originally inspired by Apple's iTunes. It is free software, designed to work well under the GNOME Desktop, and based on the powerful GStreamer media framework.<br />
<br />
Rhythmbox has a number of features, including:<br />
<br />
* Easy-to-use music browser<br />
* Searching and sorting<br />
* Comprehensive audio format support through GStreamer<br />
* Internet radio support<br />
* Playlists<br />
<br />
To install rhythmbox:<br />
pacman -S rhythmbox<br />
<br />
Other good audio players are: Banshee, Quodlibet, and Listen. See [http://gnomefiles.org/ Gnomefiles] to compare them.<br />
<br />
====KDE====<br />
=====Amarok=====<br />
[http://amarok.kde.org/ Amarok] is one of the best audio players and music library systems available for KDE. To install it, simply type the code below.<br />
<br />
pacman -S amarok-base<br />
<br />
====Console====<br />
Moc is a ncurses-based audio player for the console; another good choice is mpd.<br />
<br />
Another excellent choice is cmus[http://freshmeat.net/projects/cmus/].<br />
<br />
====Other X-based====<br />
(TODO) Xmms, audacious, bmpx.<br />
<br />
===Codecs and other multimedia content types===<br />
====DVD====<br />
You can use totem-xine, mplayer or kaffeine (just to name three of the big ones) to watch DVDs. The only thing you may miss is libdvdcss. Beware that using it may be illegal in some countries.<br />
<br />
====Flash====<br />
Install the flash plugin using<br />
pacman -S flashplugin<br />
to enable Macromedia (now Adobe) Flash in your browser.<br />
<br />
====Quicktime====<br />
Quicktime codecs are contained in the codecs package. Just type<br />
pacman -S codecs<br />
to install them.<br />
====Realplayer====<br />
The codec for Realplayer 9 is contained in the codecs package. Just type<br />
pacman -S codecs<br />
to install them. Realplayer 10 is available as a binary package for Linux. You can get it from AUR [http://aur.archlinux.org/packages.php?do_Details=1&ID=1590&O=0&L=0&C=0&K=realplay&SB=&SO=&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd here].<br />
<br />
===CD and DVD Burning===<br />
====GNOME====<br />
=====Brasero=====<br />
[http://www.gnome.org/projects/brasero/ Brasero] is an application that burns CDs/DVDs for the GNOME Desktop. It is designed to be as simple as possible and has some unique features to enable users to create their discs easily and quickly.<br />
<br />
To install:<br />
pacman -S brasero<br />
<br />
====KDE====<br />
=====K3b=====<br />
K3b - '''B'''urn, '''B'''aby, '''B'''urn in '''K'''DE<br />
-----<br />
[http://k3b.plainblack.com/ K3B] - CD/DVD burning application for Linux - optimized for KDE - licensed under the GPL.<br />
To install:<br />
pacman -S k3b<br />
<br />
<br />
<br />
<br />
(Todo) cdrecord, graveman...<br />
<br />
<br />
<br />
<br />
Most CD burners are wrappers for cdrecord:<br />
<br />
pacman -S cdrkit<br />
<br />
If you install packages for CD/DVD burning applications like Brasero or K3B it also installs the CD/DVD burning library for it, like libburn or cdrkit.<br />
<br />
A good command-line DVD-burning tool is growisofs:<br />
<br />
pacman -S dvd+rw-tools<br />
<br />
===TV-Cards===<br />
There are several things to do if you want to watch TV under (Arch) Linux. The most important task is to find out which chip your tuner is using. However, quite a bunch is supported. Be sure to check at a Hardware Database to be sure (e.g. [http://en.opensuse.org/HCL/TV_Cards]). Once you know your Model, there are just a few steps ahead to get you going.<br />
<br />
In most cases, you will need to use the bttv-drivers (other drivers exist, see [http://linux.bytesex.org/v4l2/drivers.html]) together with the I2C-modules. Configuring those is the hardest task. If you are lucky, a<br />
modprobe bttv<br />
will autodetect the card (check dmesg for results). In that case, you need only to install an application to watch TV. We will look at that later, though.<br />
If the autodetection did not work, you will need to check the file CARDLIST, which is included in the tarball of bttv[http://dl.bytesex.org/releases/video4linux/] to find out the right parameters for your card. A PV951 without radio support would need this line:<br />
modprobe bttv card=42 radio=0<br />
Some cards need the following line to produce sound:<br />
modprobe tvaudio<br />
However, that varies. So just try it out. Some other cards demand the following line:<br />
modprobe tuner<br />
This is object to trial-and-error, too.<br />
<br />
TODO: clarify the installation-procedure<br />
<br />
To actually watch TV, install the xawtv-package with<br />
pacman -S xawtv <br />
and read its manpage.<br />
<br />
TODO: clarify some possible problems and procedures. Introduction to XAWTV on another page?<br />
<br />
===Digital Cameras===<br />
Most newer digital cameras are supported as USB mass storage devices, which means that you can simply plug it in and copy the images. Older cameras may use the PTP (Picture Transfer Protocol) which requires a "special driver". gPhoto2 provides this driver and allows a shell-based transfer of the images; digikam (for KDE) and gthumb (for GNOME, gtkam would be another choice) use this driver and offer a nice GUI.<br />
<br />
===USB Memory Sticks / Hard Disks===<br />
USB Memory Sticks and hard disks are supported out of the box with the USB mass storage device driver and will appear as a new SCSI device (/dev/sdX). If you are using KDE or GNOME you should use dbus and hal (add them to your daemons in /etc/rc.conf), and they will be automatically mounted. If you use a different Desktop Environment you may have a look at ivman.<br />
<br />
==Maintaining the system==<br />
===Pacman===<br />
[[Pacman]] is both a binary and source package manager which is able to download, install, and upgrade packages from both remote and local repositories with full dependency handling, and has easy-to-understand tools for crafting your own packages too.<br />
<br />
A more-detailed description of Pacman can be found in [[Pacman|its article]].<br />
<br />
==== Useful commands ====<br />
<br />
To synchronize and update the local packages database with the remote repositories (it is a good idea to do this before installing and upgrading packages):<br />
pacman -Sy<br />
<br />
To '''upgrade''' all packages on the system:<br />
pacman -Su<br />
<br />
To sync, update, and '''upgrade''' all the packages on the system with one command:<br />
pacman -Syu<br />
<br />
To install or upgrade a single package or list of packages (including dependencies):<br />
pacman -S packageA packageB<br />
<br />
You can also sync, update the package database, and install packages in one command:<br />
pacman -Sy packageA packageB<br />
<br />
To remove a single package, leaving all of its dependencies installed:<br />
pacman -R package<br />
<br />
To remove a package and all of the package's dependencies which aren't used by any other installed package:<br />
pacman -Rs package<br />
<br />
To remove all of the package's dependencies now unneeded and do not make any backup of settings:<br />
pacman -Rsn package<br />
<br />
To search the remote (repo) package database for a list of packages matching a given keyword:<br />
pacman -Ss keyword<br />
<br />
To list all packages on your system<br />
pacman -Q<br />
<br />
To search (query) the local (your machine) package database for a given package:<br />
pacman -Q package <br />
<br />
To search (query) the local (your machine) package database for a given package and list all pertinent information:<br />
pacman -Qi package<br />
<br />
To defragment pacman's cache database and optimize for speed:<br />
pacman-optimize<br />
<br />
To count how many packages are currently on your system:<br />
pacman -Q | wc -l<br />
<br />
To install a package compiled from source using ABS and makepkg:<br />
pacman -U packagename.pkg.tar.gz<br />
<br />
Note: There are countless additional pacman functions and commands. Try man pacman and consult the [[pacman]] wiki entries.<br />
<br />
==Polishing & Further information==<br />
If after you have read this you want to do a bit of polishing, head to [[Post Installation Tips]]. For further information and support you can go to the [http://www.archlinux.org homepage], search the wiki, the [http://bbs.archlinux.org forums], the [http://wiki.archlinux.org/index.php/ArchChannel IRC channel], and the [http://www.archlinux.org/mailman/listinfo/ mailing lists].</div>
Potamota
https://wiki.archlinux.org/index.php?title=Beginners%27_guide_(Indonesia)&diff=31631
Beginners' guide (Indonesia)
2007-11-02T15:01:09Z
<p>Potamota: /* Changing the keymap */</p>
<hr />
<div>[[Category: Mendapatkan dan Instalasi Arch (Indonesia)]]<br />
[[Category:Tentang Arch (Indonesia)]]<br />
[[Category:HOWTOs (Indonesia)]]<br />
{{translateme}}<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Beginners Guide}}<br />
{{i18n_entry|Česky|Průvodce začátečníka (Česky)}}<br />
{{i18n_entry|Italiano|Beginners Guide (Italiano)}}<br />
{{i18n_entry|Lietuviškai|Pradedančiųjų gidas (Lietuviškai)}}<br />
{{i18n_entry|Indonesia|Beginners Guide (Indonesia)}}<br />
{{i18n_links_end}}<br />
==Pendahuluan==<br />
=====Segala hal yang ingin kamu tanyakan tentang instalasi Arch, tapi takut untuk menanyakan.=====<br />
Dokumen ini akan membimbing kamu dalam menginstalasi dan mengkonfigurasi ArchLinux. Walau petunjuk ini ditujuakan untuk membimbing kamu mendapatkan sistem Arch yang terkonfigurasi seluruhnya (desktop environment, menonton DVD/Video, mendengarkan musik, Internet, mail) namun tidak berisi semua pilihan yang dapat kamu gunakan untuk mengerjakan hal tersebut. Petunjuk ini difokuskan pada beberapa langkah-langkah penting/dasar saja; jika kamu ingin bahasan yang lebih dalam kamu bisa mengunjungi [[Main Page|Arch Linux Wiki]] atau [http://bbs.archlinux.org/ Arch Linux Forums]. Kamu juga bisa membaca [[The Arch Way]] untuk mengetahui prinsip-prinsip dasar ArchLinux.<br />
<br />
=====DON'T PANIC!=====<br />
Harap disadari bahwa instalasi ArchLinux mungkin sangat berbeda dengan distro lain yang pernah kamu coba, khususnya bagi pemula. Sistem ArchLinux dibangun oleh '''pengguna''', dari installer, sampai ''base system'' dengan hanya menggunakan shell bash dan beberapa tools dasar sistem saja. dari ''command line'', kamu dapat menambahkan paket dari ''Arch repositories'' menggunakan [[pacman]] melalui sambungan internet, sampai sistem kamu sesuai dengan kebutuhan/kegininan. Dengan hal ini kamu akan mendapatkan sistem yang fleksibel, sesuai pilihan dan dapat kamu kendalikan karena '''kamu''' sendiri yang membangunnya, kamu akan mengetahui apa yang ada di dalam sistem kamu.<br />
<br />
Jika kamu merasa ada yang kurang dari wiki ini silahkan ditambahkan, atau kamu bisa juga mengunjungi forum Arch ini [http://bbs.archlinux.org/viewtopic.php?t=29055 yang ditujukan untuk pemula. <br />
<br />
Selamat datang di Arch! Mari kita mulai :)<br />
<br />
==Dapatkan ISO terbaru==<br />
<br />
Kamu dapat mengunduh rilis Arch resmi terbaru dari [http://www.archlinux.org/download/ www.archlinux.org/download/].<br />
<br />
Sangat direkomendasikan untuk memilih '''base-CD''', untuk beberapa alasan.<br />
<br />
# Waktu/bandwidth yang dibutuhkan lebih sedikit untuk kamu dan server,<br />
# Paket di versi full mungkin nantinya akan ada yang konflik ketika kamu melakukan update.<br />
# Base system lebih mudah dan cepat untuk up-to-date, dan,<br />
# Petunjuk ini lebih ditujukan untuk installasi dari base-CD. <br />
<br />
==Instalasi base system ==<br />
<br />
Selain petunjuk ini, kamu dapat juga dapat menggunakan petunjuk resmi ini [[Official Arch Linux Install Guide]] atau [http://www.archlinux.org/static/docs/arch-install-guide.html versi yang dapat di print] juga tersedia.<br />
<br />
===Boot CD Arch Linux===<br />
<br />
Masukkan CD dan boot dari CD-ROM, kamu mungkin perlu mengganti urutan boot pada bios komputer kamu (biasanya dengan menekan F11 atau F12).<br />
<br />
Beberapa pilihan pada saat booting ArchLinux CD yang dapat kamu gunakan:<br />
* ide-legacy jika IDE drive kamu bermasalah.<br />
* noapic acpi=off pci=routeirq nosmp jika sistem kamu hangs ketika boot.<br />
* memtest86+ if jika kamu ingin memeriksa memorimu.<br />
<br />
Pilih "Arch Linux Installation / Rescue System". Jika kamu ingin merubah opsi boot tekan e.<br />
<br />
===Changing the keymap===<br />
Tekan enter di welcome screen. Jika keyboard kamu non-US tekan<br />
km<br />
pada prompt dan pilih keymap yang sesuai.<br />
<br />
''Contoh''(untuk keymap norwegia) :<br />
<br />
Pada console keymap screen pilih<br />
no-latin1<br />
Pada console font screen pilih<br />
lat0-16<br />
<br />
Memilih "default8x16.psfu.gz" sebagai font console adalah pilihan aman.<br />
<br />
===Start the Installation===<br />
Enter<br />
/arch/setup <br />
to start the installation. <br />
<br />
====Select an installation source====<br />
You will be prompted for an installation source. Choose CD if you are using a base or full (current) ISO, or choose FTP if you are using the FTP ISO.<br />
<br />
====Prepare Hard Drive====<br />
Select the first menu entry "Prepare Hard Drive". Beware that "Auto-Prepare" may not be a safe choice because it will erase the entire hard drive.<br />
Here we will manually partition the hard drive. Choose "2. Partition Hard Drives", select the hard drive you want (/dev/sdx), and create some partitions. <br />
<br />
<br />
=====Partitions=====<br />
<br />
<br />
A partition is a section of hard disk space that will appear as a separate disk, and can be added to your Arch Linux file system. Partitions are broken up into "Primary", "Extended", and "Logical". <br />
Primary partitions can be bootable, and are limited to 4. For example, if you are using a PC with a single SATA drive, the first primary partition will be referred to as sda1. The second primary will be referred to as sda2, then sda3, and sda4. Beyond 4 partitions, we are forced to use an extended partition which will contain logical partitions.<br />
<br />
Extended partitions are not usable by themselves; they are merely a "container" for logical partitions. Logical partitions must be contained within this extended partition. When partitioning a disk, one can see this numbering scheme by creating primary partitions sda1-3 followed by creating an extended partition, sda4, and then creating logical partition(s) within the extended partition; sda5, sda6, and so on.)<br />
<br />
<br />
Everyone has a different opinion on how best to partition the disk. What you need at the least is one primary partition which contains the root [http://en.wikipedia.org/wiki/File_system Filesystem] ( / ) and one for swap. Other candidates for separate partitions are /boot (which mainly contains the kernel) and /home (which contains the user data). It is good practice to have / and /home on separate partitions. This makes it possible to reinstall Arch Linux (or even another distro) for any reason, while keeping your data, music, pictures, and desktop environment preferences.<br />
<br />
In this example guide, we will stick with one partition for /, one partition for /home, and a swap partition.<br />
<br />
=====Swap Partition=====<br />
A swap partition is a place on your hard drive where "virtual ram" resides. If your processes need more RAM than is physically available, Linux can't fulfill the request and an error occurs. A swap partition helps in this situation by supplementing the physical RAM with virtual RAM. Linux uses the space on the hard disk to store the information that won't fit into the physical RAM any more (it's actually a bit more complex because Linux tries to put information into the swap space that isn't frequently used). Because a hard disk is very slow compared to physical RAM, this is only<br />
a makeshift. <br />
<br />
<br />
Ask two people about a swap partition and you will get four different answers. If you have plenty of RAM (more than 1024 MB) it may be possible to not use a swap partition at all. Some people suggest using twice the amount of physical RAM, while others recommend not using more than 1024 MB. I believe keeping the swap size between 512 MB and 1 GB is a good choice. Therefore, we will create a 1 GB swap space in this example.<br />
<br />
Let's start creating the '''primary partition''' that will contain the '''root''' filesystem. Choose New -> Primary and enter the size you want (something between 4 and 8 GB is a good choice for a full-featured Linux system). Put the partition at the beginning of the disk. Select the newly created partition and choose "Bootable" to make this partition bootable. Add another '''partition for your home directory'''. Choose another primary partition and set the size to a value you like. The size really depends on what your users store in their home directories, so I cannot make any suggestions. The size may vary between a few hundred megabytes for some office documents up to hundreds of gigabytes for videos and MP3s. If you <br />
want to use the whole space on your hard disc, use the remaining space minus 512 MB - 1 GB for the size. At last we<br />
create a third '''partition for swap'''. Select a size between 512 MB and 1 GB and change the type to 82 (Linux swap / Solaris).<br />
<br />
This is what your Layout should look like (size may vary depending on your decisions):<br />
<br />
Name Flags Part Type FS Type [Label] Size (MB)<br />
-------------------------------------------------------------------------<br />
sda1 Boot Primary Linux (4096 - 8192)<br />
sda2 Primary Linux (> 100)<br />
sda3 Primary Linux swap / Solaris (512 - 1024)<br />
<br />
Choose Write and type yes. Beware that this operation may destroy data on your disk if you deleted partitions. Choose Quit to leave the partitioner. <br />
Choose Done to leave this menu and continue with "Set Filesystem Mountpoints".<br />
<br />
====Set File system Mountpoints====<br />
<br />
=====A few brief words about '''filesystems''' and "file systems":=====<br />
<br />
Technically, and for accuracy, a '''filesystem''' is a data format for information throughput, whereas a "file system" (notice the space) is a term referring to the layout of all files and directories on a given system. (In our case, the hierarchical UNIX file system.) Therefore, when you are asked if you want to create a '''filesystem''', you are being asked if you want to '''format''' the particular partition... but when you are asked for mount points, you are providing where the given partition will reside in your Arch Linux "file system". Let's begin.<br />
<br />
First you will be asked for your swap partition. Choose the appropriate partition (sda3 in this example). You will be asked if you want to create a swap filesystem; select yes. Next, choose where to mount the / (root) directory (sda1 in the example). You will be asked what kind of filesystem you want.<br />
<br />
Again, ask two people which filesystem to choose and you will get five different answers. Each one has its advantages and disadvantages. Here is a very brief overview of supported filesystems.<br />
<br />
1. '''ext2''' - Old, reliable GNU/Linux filesystem. Fast, and very stable, but without journaling.<br />
<br />
2. '''ext3''' - Essentially the ext2 system, but with journaling support. ''Slightly'' slower than ext2 and other filesystems. '''Extremely''' stable and the most widely used, supported, and developed.<br />
<br />
3. '''ReiserFS''' - Hans Reiser's high-performance journaling FS uses a very interesting method of data throughput. ReiserFS is very fast, especially when dealing with many small files. ReiserFS is quite well established and stable.<br />
<br />
4. '''JFS''' - IBM's Journaling FS. JFS is quite well established, fast, and stable.<br />
<br />
5. '''XFS''' - is a fast journaling filesystem which is best suited for large files, greater than 1 GB in size. Slower with small files. Quite stable.<br />
<br />
A major difference is [http://en.wikipedia.org/wiki/Journaling_file_system journaling] (something similar to transaction logs in database environments). All filesystems except ext2 use journaling. ext3 is completely compatible with ext2, so you can mount it even with very-old rescue CDs. A safe choice for the root partition is ext3. ReiserFS, XFS, and JFS are also OK to use because GRUB (the boot manager which we will install later) can boot from them too. Create the filesystem (format the partition) by selecting yes. You will now be prompted to add any additional partitions. In our example, only sda2 is remaining. Choose a filesystem type and mount it as /home. Again, create the filesystem and choose Done. Return to main menu.<br />
<br />
===Select Packages===<br />
Now we shall select packages to install in our system. Choose CD as source and select the appropriate CD drive if you have more than one.<br />
Since this guide is geared toward a '''base''' installation, choose the base category (keeping all base packages selected is a safe choice). If you chose the current ISO rather than the base ISO, it is up to you if you want to select more packages, but we will show you later how to install additional, up-to-date software more easily, rather than installing and reinstalling. (Since the install CD you are using has been created, there are no doubt numerous updates available for packages contained therein, and installing additional up-to-date software via pacman will be covered below.) If you are '''sure''' you will not be needing certain packages (for instance, a filesystem type you don't need, ISDN, or PPPoE support), feel free to remove them from the base package selection. <br />
<br />
Step forward to "Install Packages".<br />
<br />
===Install Packages===<br />
This is an easy task because everything happens automatically. Get yourself a cup of coffee (if you're into coffee ;)) and wait until the installation has finished (press continue if needed). Drink quickly, because the Arch Linux base packages install in just a couple of minutes.<br />
<br />
===Configure The System===<br />
You will be asked if you want to choose hwdetect to gather some information for your configuration. This is recommended so you should choose this option. <br />
Now you will be asked if you need support for booting from USB devices, FireWire devices, PCMCIA devices, NFS shares, software RAID arrays, LVM2 volumes, and encrypted volumes. Choose yes if you need it; in our example nothing is needed. Now you will be asked which text editor you want to use; choose [http://en.wikipedia.org/wiki/Nano_%28text_editor%29 nano] if you are not familiar with [http://en.wikipedia.org/wiki/Vim_%28text_editor%29 vi/vim]. You will now get a menu with most important config files for your system. We will do only some minor tweaks at this time. If you want to look up the available options as stated in rc.conf just press Alt+F2 to get a shell, look it up, and switch back to the installer with Alt+F1. <br />
<br />
=====/etc/rc.conf=====<br />
<br />
* Change your LOCALE if needed (e.g. "de_DE.utf8") (This locale must coincide with /etc/locale.gen. '''See below'''.)<br />
* Change your TIMEZONE if needed (e.g. "Europe/Berlin")<br />
* Change your KEYMAP if needed (e.g. "de-latin1-nodeadkeys")<br />
<br />
* Change MODULES if you know that an important module is missing (hwdetect should have filled in the most important modules)<br />
* Change your HOSTNAME<br />
* Change your Network settings:<br />
** Don't modify the lo line<br />
** Adjust the IP address, netmask and broadcast address if you are using a static IP<br />
** Set eth0="dhcp" if you have a router which dynamically assigns an IP address<br />
** If you have a static IP set the gateway address to the one of your router and remove the ! in front of the ROUTES entry<br />
=====About DAEMONS=====<br />
You don't have to change the [[daemons]] line at this time, but it is useful to explain what daemons are, because we need them later in this guide. Analogous to a Windows service, a daemon is a program that runs in the background, waiting for events to occur and offering services. A good example is a webserver that waits for a request to deliver a page or an SSH server waiting for someone trying to log in. While these are full-featured applications, there are daemons whose work is not that visible. Examples are a daemon which writes messages into a log file (e.g. syslog, metalog), a daemon which lowers your CPU's frequency if your system has nothing to do, and a daemon which offers you a graphical login (e.g. gdm, kdm). All these programs can be added to the daemons line and will be started when the system boots. Useful daemons will be presented during this guide.<br />
<br />
Use Ctrl+X to leave the editor.<br />
<br />
=====/etc/hosts=====<br />
Add the desired ''hostname'' (the one you set in rc.conf before) so that it looks like this:<br />
127.0.0.1 localhost.localdomain localhost ''yourhostname''<br />
This format, '''including the 'localhost' entries''', is required for program compatibility.<br />
For most users, simply adding the ''hostname'' to the end of the default line will work, however, some users recommend using the following syntax:<br />
127.0.0.1 ''yourhostname''.domain.org localhost.localdomain localhost ''yourhostname''<br />
If you use a static IP, add another line using the syntax: <static-ip> hostname.domainname.org hostname, <br />
e.g.:<br />
192.168.1.100 yourhostname.domain.org yourhostname<br />
<br />
===== /etc/fstab, mkinitcpio.conf and modprobe.conf=====<br />
We shouldn't need to edit mkinitcpio.conf, or modprobe.conf at this point. mkinitcpio configures the ramdisk (e.g. booting from RAID, encrypted volumes) and modprobe can be used to set some special config options for the modules).<br />
<br />
If you are planning on using the hal daemon to automate the mounting of disks, optical drives, usb drives, etc., you may wish to edit /etc/fstab by commenting out the entries for cdrom, floppy, and dvd.<br />
<br />
=====/etc/resolv.conf (for Static IP)=====<br />
If you use a static IP, set your DNS servers in /etc/[[resolv.conf]] (nameserver <ip-address>). You may have as many as you wish.<br />
<br />
If you are using a router, you will probably want to specify your DNS servers in the router itself, and merely point to it from your resolv.conf, using your router's IP (which is also your gateway from /etc/rc.conf), e.g.:<br />
nameserver 192.168.1.1<br />
Alternatively, add your preferred servers one by one, e.g.:<br />
nameserver 4.2.2.1<br />
nameserver 4.2.2.2<br />
<br />
=====/etc/locale.gen=====<br />
Choose the locale(s) you need (remove the # in front of the lines you want), e.g.:<br />
en_US ISO-8859-1<br />
en_US.UTF-8 <br />
('''Your locale must coincide with the one specified in /etc/rc.conf above.''')<br />
=====Root password=====<br />
Finally, set a root password and make sure that you remember it later. Return to the main menu and continue with installing a kernel.<br />
<br />
===Install Kernel===<br />
Not many choices here; choose v2.6 and continue. You may want to switch your kernel later. A fallback image will be created, keeping mkinitcpio as it is shown as a safe choice. Continue with installing a bootloader.<br />
<br />
===Install Bootloader===<br />
Because we have no secondary operating system in our example, we will need a bootloader. [http://www.gnu.org/software/grub/ GNU GRUB] is the recommended bootloader. Alternatively, you may choose [http://lilo.go.dyndns.org/ LILO]. The shown GRUB configuration (/boot/grub/menu.lst) should be sufficient. The only thing you may want to alter is the resolution of the console. Add<br />
a vga=<number> to the first kernel line. (A table of resolutions and the corresponding numbers is printed in the menu.lst.) <br />
title Arch Linux (Main)<br />
root (hd0,0)<br />
kernel /boot/vmlinuz26 root=/dev/sda1 ro vga=773<br />
initrd /boot/kernel26.img<br />
The "vga=773" argument will give a 1024x768 framebuffer with 256 color depth.<br />
<br />
Exit the install and type reboot.<br />
<br />
If everything goes well, your new Arch Linux system will boot up and finish with a login prompt (you may want to change the boot order in your BIOS back to booting from hard disk).<br />
<br />
Congratulations, and welcome to your shiny, new Arch Linux base system!<br />
<br />
==Configuring the base system ==<br />
Your new Arch Linux base system is now a functional GNU/Linux operating system ready for customization. From here, you may build this elegant set of tools into whatever you wish or require for your purposes!<br />
Let's begin.<br />
-----<br />
Login with your root account. We will configure pacman and update the system as root, then add a normal user. <br />
<br />
===Configuring pacman===<br />
Edit /etc/pacman.conf<br />
nano -w /etc/pacman.conf<br />
and remove the # in front of the "Include = /etc/pacman.d/community" and "[community]" lines to enable Arch's community repository, which offers many useful applications. Now edit /etc/pacman.d/community and move the mirrors which are located nearest to you up (if you use nano, Alt+A starts selecting an area, cursor down marks the lines, Ctrl+K cuts the selected area and Ctrl+U uncuts it). Repeat this for all files in /etc/pacman.d/.<br />
<br />
===Configuring the network (if necessary)===<br />
<br />
If everything went fine, you should have a working network. Try to ping www.google.com to verify this.<br />
ping -c 3 www.google.com<br />
<br />
If you have successfully established a network connection, continue with "Update, Sync and Upgrade the system with pacman".<br />
<br />
If, after trying to ping www.google.com, you get an "unknown host" error, you may conclude that your network is not configured. You may choose to double-check the following files for integrity and proper settings:<br />
<br />
'''/etc/rc.conf''' # Specifically, check your HOSTNAME= and NETWORKING section<br />
<br />
'''/etc/hosts''' # Double-check your format. (See above.)<br />
<br />
'''/etc/resolv.conf''' # If you are using a static IP. If you are using DHCP, this file will be dynamically created and destroyed by default, but can be changed to your preference. (See [[Network]].)<br />
<br />
Advanced instructions for configuring the network can be found in the [[Network]] article.<br />
<br />
====Wired LAN====<br />
<br />
Check your Ethernet with<br />
ifconfig<br />
where you should see an entry for eth0. If required, you can set a new static IP with<br />
ifconfig eth0 <ip address> netmask <netmask> up <br />
and the default gateway with<br />
route add default gw <ip address of the gateway><br />
Check to see if /etc/resolv.conf contains your DNS server and add it if it is missing. <br />
Check your network again with ping www.google.de. If everything is working now, adjust /etc/rc.conf as described in section 2.6 (static IP). If you have a DHCP server/router in your network try<br />
dhcpcd eth0<br />
If this is working, adjust /etc/rc.conf as described in section 2.6 (dynamic IP).<br />
<br />
====Wireless LAN====<br />
[[Wireless Setup]]<br />
(TODO) Simplify and generalize it, link only for more-advanced stuff<br />
<br />
====Analog Modem====<br />
To be able to use a Hayes-compatible, external, analog modem, you need to at least have the ppp package installed. Modify the file /etc/ppp/options to suit your needs and according to man pppd. You will need to define a chat script to supply your username and password to the ISP after the initial connection has been established. The manpages for pppd and chat have examples in them that should suffice to get a connection up and running if you're either experienced or stubborn enough. With udev, your serial ports usually are /dev/tts/0 and /dev/tts/1.<br />
Tip: Read [[Dialup without a dialer HOWTO]].<br />
<br />
Instead of fighting a glorious battle with the plain pppd, you may opt to install wvdial or a similar tool to ease the setup process considerably. In case you're using a so-called WinModem, which is basically a PCI plugin card working as an internal analog modem, you should indulge in the vast information found on the [http://www.linmodems.org/ LinModem] homepage.<br />
<br />
====ISDN====<br />
<br />
Setting up ISDN is done in three steps:<br />
# Install and configure hardware<br />
# Install and configure the ISDN utilities<br />
# Add settings for your ISP <br />
<br />
The current Arch stock kernels include the necessary ISDN modules, meaning that you won't need to recompile your kernel unless you're about to use rather odd ISDN hardware. After physically installing your ISDN card in your machine or plugging in your USB ISDN-Box, you can try loading the modules with modprobe. Nearly all passive ISDN PCI cards are handled by the hisax module, which needs two parameters: type and protocol. You must set protocol to '1' if your country uses the 1TR6 standard, '2' if it uses EuroISDN (EDSS1), '3' if you're hooked to a so-called leased-line without D-channel, and '4' for US NI1.<br />
<br />
Details on all those settings and how to set them is included in the kernel documentation, more specifically in the isdn subdirectory, and available online. The type parameter depends on your card; a list of all possible types can be found in the README.HiSax kernel documentation. Choose your card and load the module with the appropriate options like this:<br />
<br />
modprobe hisax type=18 protocol=2<br />
<br />
This will load the hisax module for my ELSA Quickstep 1000PCI, being used in Germany with the EDSS1 protocol. You should find helpful debugging output in your /var/log/everything.log file, in which you should see your card being prepared for action. Please note that you will probably need to load some USB modules before you can work with an external USB ISDN Adapter.<br />
<br />
Once you have confirmed that your card works with certain settings, you can add the module options to your /etc/modprobe.conf:<br />
<br />
alias ippp0 hisax<br />
options hisax type=18 protocol=2<br />
<br />
Alternatively, you can add only the options line here, and add hisax to your MODULES array in the rc.conf. It's your choice, really, but this example has the advantage that the module will not be loaded until it's really needed.<br />
<br />
That being done, you should have working, supported hardware. Now you need the basic utilities to actually use it!<br />
<br />
Install the isdn4k-utils package, and read the manpage to isdnctrl; it'll get you started. Further down in the manpage you will find explanations on how to create a configuration file that can be parsed by isdnctrl, as well as some helpful setup examples. Please note that you have to add your SPID to your MSN setting separated by a colon if you use US NI1.<br />
<br />
After you have configured your ISDN card with the isdnctrl utility, you should be able to dial into the machine you specified with the PHONE_OUT parameter, but fail the username and password authentication. To make this work add your username and password to /etc/ppp/pap-secrets or /etc/ppp/chap-secrets as if you were configuring a normal analogous PPP link, depending on which protocol your ISP uses for authentication. If in doubt, put your data into both files.<br />
<br />
If you set up everything correctly, you should now be able to establish a dial-up connection with<br />
isdnctrl dial ippp0<br />
as root. If you have any problems, remember to check the logfiles!<br />
<br />
====DSL (PPPoE)====<br />
<br />
These instructions are relevant to you only if your PC itself is supposed to manage the connection to your ISP. You do not need to do anything but define a correct default gateway if you are using a separate router of some sort to do the grunt work.<br />
<br />
Before you can use your DSL online connection, you will have to physically install the network card that is supposed to be connected to the DSL-Modem into your computer. After adding your newly installed network card to the modules.conf/modprobe.conf or the MODULES array, you should install the rp-pppoe package and run the pppoe-setup script to configure your connection. After you have entered all the data, you can connect and disconnect your line with<br />
<br />
/etc/rc.d/adsl start<br />
<br />
and<br />
<br />
/etc/rc.d/adsl stop<br />
<br />
respectively. The setup usually is rather easy and straightforward, but feel free to read the manpages for hints. If you want to automatically dial in on boot-up, add adsl to your DAEMONS array.<br />
<br />
==Update, Sync and Upgrade the system with [[pacman]]==<br />
Now we will update the system using [[pacman]], the package manager of Arch Linux. Pacman is fast, simple, and extremely powerful. It manages your entire package system and allows installation, package removal, package downgrade (through cache), custom compiled package handling, automatic dependency resolution, and much more.<br />
<br />
Update, sync, and '''upgrade''' your entire new system with:<br />
pacman -Syu<br />
pacman will now fetch the latest information about available packages and perform all available upgrades. (You may be prompted to upgrade pacman itself at this point. If so, say yes, and then reissue the pacman -Syu command when finished.)<br />
<br />
=====''Take note as to whether a kernel upgrade is occurring!''=====<br />
<br />
If the kernel is upgraded, modules such as nvidia will be rendered inoperable, since the new, upgraded versions will be built against the newer kernel, and your system is currently using an older one. A reboot will be necessary.<br />
<br />
=====The beauty of the rolling release=====<br />
Keep in mind that Arch is a '''rolling release''' distribution. This means there is never a reason to reinstall or perform elaborate system rebuilds to upgrade to the newest version. Simply issuing '''pacman -Syu''' periodically keeps your entire system up-to-date and on the bleeding edge. At the end of this upgrade, your system is completely current.<br />
<br />
=====Get familiar with pacman=====<br />
Pacman is the Arch user's best friend. It is highly recommended to study and learn how to use the pacman tool. Try:<br />
man pacman<br />
Check out the bottom of this article, and look up the [[pacman]] wiki entries at your leisure.<br />
<br />
<br />
<br />
===Add a user and setup groups===<br />
You should not do your everyday work using the root account. It is more than poor practice; it is dangerous. Root is for administrative tasks. Instead, add a normal user account using:<br />
adduser<br />
While most default options are safe to use, you may want to add at least audio and wheel to your additional groups. <br />
Audio allows your user to use the audio card, while wheel allows switching to the root account with su. Other groups to be added, (separated by a comma) include:<br />
<br />
*disk - for managing disks, including USB flash drives and such<br />
<br />
*storage - for managing storage devices<br />
<br />
*video - for managing video tasks<br />
<br />
*optical - for managing tasks pertaining to the optical drive(s)<br />
<br />
*floppy - for access to a floppy if necessary<br />
<br />
*lp - for managing printing tasks<br />
<br />
You may also consider adding optical to your additional groups to enable CD/DVD recording from your user account.<br />
<br />
See the [http://wiki.archlinux.org/index.php/Groups Groups] article to understand what groups you need to be a member of. <br />
You may also add your user to the desired groups like so, (as root):<br />
usermod -aG audio,video,floppy,lp,optical,network,storage,wheel USERNAME<br />
<br />
==Installing and configuring Hardware==<br />
===Configure the audio card===<br />
Your audio card should already be working, but you can't hear anything because it is muted by default. Install the alsa-utils <br />
pacman -S alsa-utils<br />
and use alsamixer to adjust the channels: <br />
alsamixer<br />
Unmute the Master and PCM channels by scrolling to them with cursor left/right and pressing '''M'''. Increase the volume levels with the cursor-up key. (70-90 Should be a safe range.) Leave alsamixer by pressing ESC and store the settings with<br />
alsactl store<br />
If you plan on using a desktop environment such as GNOME or KDE and would prefer that alsa remember your settings when you change them, do not execute the above command--your volume settings will be remembered automatically.<br />
Add alsa to your DAEMONS section in /etc/rc.conf to automatically restore the mixer on boot-up.<br />
nano /etc/rc.conf<br />
<br />
DAEMONS=(syslog-ng network crond '''alsa''')<br />
<br />
===Configuring CPU frequency scaling===<br />
Modern processors can decrease their frequency and voltage to reduce heat and power consumption. Less heat leads to a quieter system; even a desktop system will benefit from it. Install cpufrequtils with<br />
pacman -S cpufrequtils<br />
and add cpufreq to your daemons in /etc/rc.conf. Edit the config file /etc/conf.d/cpufreq and change <br />
governor="conservative"<br />
which dynamically increases the CPU frequency if needed (which is a safe choice on desktop systems too). Alter min_freq and max_freq to match your system's CPU spec. If you don't know the frequencies, run ''cpufreq-info'' after loading one of the frequency scaling modules. Add the frequency scaling modules to your /etc/rc.conf modules line. Most modern notebooks and desktops can simply use the ''acpi-cpufreq'' driver, however other options include the ''p4-clockmod, powernow-k6, powernow-k7, powernow-k8, and speedstep-centrino'' drivers. Load the module with<br />
modprobe <modulname> <br />
and start cpufreq with<br />
/etc/rc.d/cpufreq start<br />
For more details, see [[Cpufrequtils]]<br />
<br />
===Additional tweaks for laptops===<br />
ACPI support is needed if you want to use some special functions on your notebook (e.g. sleep, sleep when lid is closed, special keys...). Install acpid <br />
pacman -S acpid<br />
and add it to the daemons in /etc/rc.conf (acpid). Start it with<br />
/etc/rc.d/acpid start<br />
<br />
More-specific information about Arch Linux on various Laptops can be found at [[:Category:Laptops (English)]]<br />
<br />
==Installing and configuring X==<br />
The X Window System (commonly X11, or just simply X) is a networking and display protocol which provides windowing on bitmap displays. It provides the standard toolkit and protocol to build graphical user interfaces (GUIs) on Unix-like operating systems.<br />
<br />
X provides the basic framework, or primitives, for building GUI environments: drawing and moving windows on the screen and interacting with a mouse and/or keyboard. X does not mandate the user interface — individual client programs handle this. <br />
-----<br />
Now we will install the base Xorg packages using pacman. <br />
<br />
As root, do:<br />
pacman -S xorg-server xorg-xkb-utils xorg-xauth xorg-server-utils xorg-xinit xf86-video-vesa xf86-input-mouse xf86-input-keyboard<br />
(The old xorg group package has been removed. If it reappears, the option to use it will be given here.)<br />
Now we have the base packages we need for running the X Server. You should add the driver for your graphics card now (e.g. xf86-video-<name>). If you need a list of all '''open-source''' video drivers, do: <br />
pacman -Ss xf86-video | less<br />
If you don't know what graphics card you are using, do:<br />
lspci | grep VGA<br />
Here is a list of '''open source''' drivers, and corresponding video chipsets.<br />
*'''xf86-video-apm''' Alliance ProMotion video driver<br />
*'''xf86-video-ark''' ark video driver<br />
*'''xf86-video-ati''' ati video driver<br />
*'''xf86-video-chips''' Chips and Technologies video driver<br />
*'''xf86-video-cirrus''' Cirrus Logic video driver<br />
*'''xf86-video-dummy''' dummy video driver<br />
*'''xf86-video-fbdev''' framebuffer video driver<br />
*'''xf86-video-glint''' GLINT/Permedia video driver<br />
*'''xf86-video-i128''' Number 0 i128 video driver<br />
*'''xf86-video-i740''' Intel i740 video driver<br />
*'''xf86-video-i810''' Intel i810/i830/i9xx video drivers<br />
*'''xf86-video-imstt''' Integrated Micro Solutions Twin Turbo vidoe driver<br />
*'''xf86-video-mga''' mga video driver (Matrox Graphics Adapter)<br />
*'''xf86-video-neomagic''' neomagic video driver<br />
*'''xf86-video-nv''' nvidia nv video driver<br />
*'''xf86-video-rendition''' Rendition video driver<br />
*'''xf86-video-s3''' S3 video driver<br />
*'''xf86-video-s3virge''' S3 Virge video driver<br />
*'''xf86-video-savage''' savage video driver<br />
*'''xf86-video-siliconmotion''' siliconmotion video driver<br />
*'''xf86-video-sis''' SiS video driver<br />
*'''xf86-video-sisusb''' SiS USB video driver<br />
*'''xf86-video-tdfx''' tdfx video driver<br />
*'''xf86-video-trident''' Trident video driver<br />
*'''xf86-video-tseng''' tseng video driver<br />
*'''xf86-video-unichrome''' Unichrome video drivers<br />
*'''xf86-video-v4l''' v4l video driver<br />
*'''xf86-video-vesa''' vesa video driver<br />
*'''xf86-video-vga''' VGA 16 color video driver<br />
*'''xf86-video-via''' via video driver<br />
*'''xf86-video-vmware ''' vmware video driver<br />
*'''xf86-video-voodoo ''' voodoo video driver<br />
<br />
* Note that the '''vesa''' driver is the most generic, and should work with almost any modern video chipset. If you cannot find a suitable driver for your video chipset, vesa '''should''' work.<br />
<br />
*If you have an nVIDIA or ATI video adapter, you may wish to install the proprietary nVIDIA or ATI drivers. '''Installing proprietary video drivers is covered below''' under "Using proprietary Graphics Driver (nVIDIA, ATI)"<br />
<br />
Install the appropriate video driver for your video card/onboard video. e.g.:<br />
pacman -S xf86-video-i810<br />
(for the intel 810 chipset driver.)<br />
<br />
==Create /etc/X11/xorg.conf==<br />
=====What is /etc/X11/xorg.conf?=====<br />
/etc/X11/xorg.conf is the '''main configuration file''' for your '''X''' Window System, the foundation of your '''G'''raphical '''U'''ser '''I'''nterface. It is a plain text file ordered into sections and subsections. Important sections are ''Files, InputDevice, Monitor, Modes, Screen, Device, and ServerLayout''. Sections can appear in any order and there may be more than one section of each kind, for example, if you have more than one monitor, say a video projector and an on board LCD of a notebook. <br />
------<br />
By default, you will not have an Xorg config file, and with the newest versions of Xorg, you don't need one ''if'' the autodetection ''works satisfactorily'' and you don't need to turn on features such as aiglx and so on. ''Most people will still find that they need to generate a config file, however.''<br />
<br />
There are several ways of creating /etc/X11/xorg.conf:<br />
<br />
*The Xorg way to make a basic config file is to run<br />
Xorg -configure<br />
which will create /root/xorg.conf. Move the generated config file as appropriate, e.g.<br />
mv /root/xorg.conf.new /etc/X11/xorg.conf<br />
<br />
*Another way of making an xorg.conf without getting your hands dirty is Arch Linux's own developer tpowa's tool:<br />
hwd -xa<br />
hwd (to see the various options)<br />
<br />
*The proprietary video drivers also have tools to edit xorg.conf to configure the drivers (see below). These are <br />
aticonfig<br />
and<br />
nvidia-xconfig<br />
<br />
However, you should not be a stranger to editing the config file by hand (as this is usually needed to fix various issues from time to time):<br />
<br />
nano /etc/X11/xorg.conf<br />
<br />
Edit your /etc/X11/xorg.conf to specify your video driver. e.g.:<br />
Section "Device"<br />
Driver "i810"<br />
<br />
=====Simple baseline X test=====<br />
<br />
At this point, you should have xorg installed, with a suitable video driver and an /etc/X11/xorg.conf configuration file. If you want to test your configuration quickly, before installing a complete desktop environment, install '''xterm'''. Xterm is a very simple terminal emulator which runs in the X Server environment. Xterm will allow us to effectively test if your video driver and /etc/X11/xorg.conf are properly configured. Alternatively, you may wish to test if the X autodetection works satisfactorily, in the absence of /etc/X11/xorg.conf.<br />
pacman -S xterm<br />
Edit your /home/username/.xinitrc file, '''as normal user''', to dictate which X Server event is called upon with the 'startx' command:<br />
<br />
su yourusername<br />
<br />
nano ~/.xinitrc<br />
<br />
and add (or uncomment)<br />
<br />
exec xterm<br />
<br />
So that it looks like this:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
exec xterm<br />
# exec wmaker<br />
# exec startkde<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
<br />
(Be sure to have only one uncommented line in your ~/.xinitrc ) If you do not have ~/.xinitrc, simply create one with the above information.<br />
<br />
Start X Server as normal user, with:<br />
<br />
startx<br />
You should have an xterm session open up. You can exit the X Server with Ctrl+Alt+Backspace, or by typing "exit". If you have problems starting X, you can look for errors in the /var/log/Xorg.0.log file and on the console output of the console you started X from.<br />
<br />
Now you might want to install a graphical login manager (to avoid having to type startx everytime you start the computer) like [[GDM]] or [[KDM]], but this ''could'' wait, and advanced instructions for Xorg configuration can be found in the [[Xorg]] article.<br />
<br />
===Adjusting Keyboard Layout===<br />
You may want to change your keyboard layout. To do this edit your /etc/X11/xorg.conf and add these lines in the Input Section (keyboard0) (the example shows a German keyboard layout with no dead keys; alter this to fit your needs).<br />
Option "XkbLayout" "de"<br />
Option "XkbVariant" "nodeadkeys"<br />
<br />
===Adjusting Mouse for scroll wheel===<br />
While your mouse should be working out of the box, you may want to use your scroll wheel. Add this to your Input Section (mouse0):<br />
Option "ZAxisMapping" "4 5 6 7"<br />
<br />
===evdev===<br />
If you have a modern USB mouse with several thumb buttons and/or functions, you will most likely want to install the evdev mouse driver, which will allow you to exploit the full functionality of your mouse:<br />
<br />
pacman -S xf86-input-evdev<br />
Load the driver:<br />
modprobe evdev<br />
Find your mouse name:<br />
cat /proc/bus/input/devices | egrep "Name"<br />
Using the mouse name, configure your /etc/X11/xorg.conf InputDevice section accordingly, e.g.:<br />
Section "InputDevice"<br />
Identifier "Evdev Mouse"<br />
Driver "evdev"<br />
Option "Name" "Logitech USB-PS/2 Optical Mouse"<br />
Option "CorePointer"<br />
EndSection<br />
You must have only '''one''' "CorePointer" device specified in /etc/X11/xorg.conf, so be sure to comment out any other mouse entries until you feel safe removing the old, unused entries.<br />
<br />
Also edit the ServerLayout section to include Evdev Mouse as the CorePointer, e.g.:<br />
Section "ServerLayout"<br />
Identifier "Layout0"<br />
Screen 0 "Screen0"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
InputDevice "Evdev Mouse" "CorePointer"<br />
<br />
===Using proprietary Graphics Driver (nVIDIA, ATI)===<br />
You may choose to use the proprietary video drivers from nVIDIA or ATI. <br />
====nVIDIA Graphic Cards====<br />
The nVIDIA proprietary drivers are generally considered to be of excellent quality, and offer superior 3D performance.<br />
<br />
Before you configure your Graphics Card you will need to know which driver fits. Arch currently has 3 different drivers that each match a certain subset of Cards: <br />
<br />
'''1. nvidia-71xx''' ''for very old Cards like TNT and TNT2''<br />
<br />
'''2. nvidia-96xx''' ''slightly newer cards up to the GF 4''<br />
<br />
'''3. nvidia''' ''newest GPUs after the GF 4''<br />
<br />
Consult the nVIDIA-Homepage to see which one is for you. The difference is only for the installation; Configuration works the same with every driver.<br />
<br />
Install the appropriate nvidia driver, e.g.: <br />
pacman -S nvidia <br />
At this point, you have 3 choices as to how to proceed.<br />
<br />
*'''1.''' If you have no xorg.conf at all, or if you have an existing xorg.conf and want to '''generate a completely new one''' with the nVIDIA utility, back up the old one:<br />
mv /etc/X11/xorg.conf /etc/X11/xorg.old<br />
Then create the new /etc/X11/xorg.conf with<br />
nvidia-xconfig<br />
The nvidia-xconfig utility will usually create a very short, streamlined, easy-to-read xorg.conf<br />
<br />
It also has several options which will further specify the contents and options of the xorg.conf file.<br />
For example,<br />
nvidia-xconfig --composite --add-argb-glx-visuals<br />
<br />
For more detailed information, see nvidia-xconfig(1).<br />
<br />
*'''2.''' '''Expert Option:''' If you have an existing xorg.conf and want to keep it, edit your xorg manually as needed, and at the very least, adjust your '''Device''' Section by changing Driver "<olddrivername>" to Driver "nvidia".<br />
Section "Device"<br />
<br />
Driver "nvidia" <br />
*'''3.''' Alternatively, you may choose to keep your existing /etc/X11/xorg.conf, and run:<br />
nvidia-xconfig<br />
which will automatically '''update''' your /etc/X11/xorg.conf for use with the nVIDIA proprietary driver.<br />
<br />
Some useful tweaking options in the device section are (beware that these may not work on your system):<br />
Option "RenderAccel" "true"<br />
Option "NoLogo" "true"<br />
Option "AGPFastWrite" "true"<br />
Option "EnablePageFlip" "true"<br />
<br />
The nvidia-xconfig utility will automatically place the glx option in your xorg. If you did not use nvidia-xconfig, then you should add this to your module section:<br />
<br />
Load "glx"<br />
Double check your /etc/X11/xorg.conf to make sure your default depth, horizontal refresh, vertical refresh, and resolutions are acceptable.<br />
<br />
Logout and login.<br />
<br />
Start X server as normal user, to test your configuration:<br />
startx<br />
<br />
Advanced instructions for nvidia configuration can be found in the [[NVIDIA]] article.<br />
<br />
====ATI Graphic Cards====<br />
ATI owners have two options for drivers. If you are unsure which driver to use, please try the open-source one first. The open-source driver will suit most needs along with being generally less problematic.<br />
<br />
Install the '''proprietary''' ATI Driver with<br />
pacman -S fglrx<br />
Use the aticonfig tool to modify the xorg.conf. Note: The proprietary driver does not support [[AIGLX]]. To use [[Compiz]] or [[Beryl]] with this driver you would need to use [[XGL]].<br />
<br />
Install the '''open-source''' ATI Driver with<br />
pacman -S xf86-video-ati<br />
Currently, the performance of the open-source driver is not on par with that of the proprietary one. It also lacks TV-out, dual-link DVI support, and possibly other features. On the other hand, it supports Aiglx and has better dual-head support.<br />
<br />
Advanced instructions for ATI configuration can be found in the [[ATI | ATI wiki]].<br />
<br />
==Installing and configuring a Desktop Environment ==<br />
If you ask two people what the best Desktop Environment or Window Manager is, you will get six different answers. <br />
* If you want something full-featured and similar to Windows and Mac OSX, '''KDE''' is a good choice<br />
* If you want something more minimalist, which follows the K.I.S.S. principle more closely, '''GNOME''' is a good choice<br />
* If you have an older machine or want something lighter, '''xfce4''' is a good choice, still giving you a complete environment<br />
* If you need something even lighter, '''openbox, fluxbox or fvwm2''' may be right (not to mention all other lightweight window managers like '''windowmaker and twm''').<br />
* If you need something completely different, try '''ion, wmii, or dwm'''.<br />
<br />
===Install Fonts===<br />
At this point, you may want to install some good-looking fonts, '''before''' installing a desktop environment/window manager. Dejavu and bitstream-vera are nice font sets. For websites, you may want to have the Microsoft fonts too. Install with:<br />
pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera<br />
<br />
===GNOME===<br />
====About GNOME====<br />
The '''G'''NU '''N'''etwork '''O'''bject '''M'''odel '''E'''nvironment. The GNOME project provides two things: The GNOME desktop environment, an intuitive and attractive desktop for end-users, and the GNOME development platform, an extensive framework for building applications that integrate into the rest of the desktop.<br />
<br />
====Installation====<br />
Install GNOME with<br />
pacman -S gnome<br />
If you want a more-than-complete GNOME distribution with a lot of extras, do:<br />
pacman -S gnome-extra<br />
It's safe to choose all packages shown. <br />
=====Useful DAEMONS for GNOME=====<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. The '''hal''' daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The '''fam''' daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system. Both '''hal''' and '''fam''' make life easier for the GNOME user.<br />
<br />
You may want to install a graphical login manager. For GNOME, the '''gdm''' daemon is a good choice. Install gdm with<br />
pacman -S gdm<br />
You will almost certainly want the '''hal''' and '''fam''' daemons.<br />
<br />
Start hal and fam:<br />
/etc/rc.d/hal start<br />
<br />
/etc/rc.d/fam start<br />
<br />
Add them to your /etc/rc.conf DAEMONS section, so they will start on bootup:<br />
nano /etc/rc.conf<br />
<br />
DAEMONS=(syslog-ng network crond alsa '''hal fam gdm''')<br />
(If you prefer to log into the console and manually start X in the 'Slackware tradition', leave out gdm.)<br />
<br />
====~/.xinitrc====<br />
<br />
This file controls what occurs when you type 'startx'.<br />
<br />
Edit your /home/username/.xinitrc to utilize GNOME:<br />
<br />
nano ~/.xinitrc<br />
<br />
Uncomment the 'exec gnome-session' line so that it looks like this:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
#exec xterm<br />
#exec wmaker<br />
# exec startkde<br />
exec gnome-session<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
<br />
If you do not have a ~/.xinitrc file, simply create it with the above information. Remember, you must have only one uncommented line in your ~/.xinitrc. <br />
<br />
Switch to normal user:<br />
su username<br />
<br />
And test it with:<br />
startx<br />
<br />
You may want to install a terminal and an editor. I would recommend gnome-terminal (part of the group gnome-extra) and geany:<br />
pacman -S geany gnome-terminal<br />
<br />
Advanced instructions for installing and configuring GNOME can be found in the [[Gnome]] article.<br />
<br />
====Eye Candy====<br />
You may find the default GNOME theme and icons not very attractive. A nice gtk theme is murrine. Install it with<br />
pacman -S gtk-engine-murrine<br />
and select it with System->Preferences->Theme. You can find more themes, icons, and wallpaper at [http://www.gnome-look.org Gnome Look].<br />
<br />
===KDE===<br />
====About KDE====<br />
The '''K''' '''D'''esktop '''E'''nvironment. KDE is a powerful Free Software graphical desktop environment for Linux and Unix workstations. It combines ease of use, contemporary functionality, and outstanding graphical design with the technological superiority of UNIX-like operating systems.<br />
<br />
====Installation====<br />
Arch offers several versions of kde: '''kde, kdebase, and KDEmod'''. Choose '''one''' of the following, and continue below with '''"Useful KDE DAEMONS"''': <br />
<br />
'''1.)''' Package '''kde''' is the complete, vanilla KDE, ~300MB.<br />
pacman -S kde<br />
'''2.)''' Package '''kdebase''' is a slimmed-down version with less applications, ~80MB.<br />
pacman -S kdebase<br />
'''3.)''' Lastly, '''KDEmod''' is an Arch Linux exclusive, community-driven system which is modified for extreme performance and modularity. The KDEmod project website can be found at [http://kdemod.ath.cx/ http://kdemod.ath.cx/]. KDEmod is extremely fast, lightweight and responsive, with a pleasing, customized theme. <br />
<br />
To install KDEmod in 5 easy steps, just follow these installation instructions...<br />
Note: Before you start, please remember to read all of the install messages. They are fairly comprehensive and should solve any upcoming questions after the installation. If you cant scroll back to see all messages, just take a look into /var/log/pacman.log<br />
<br />
*1. Add the kdemod repo to your /etc/pacman.conf:<br />
nano /etc/pacman.conf<br />
Add one of these entries at the top of your server list:<br />
[kdemod]<br />
Server = http://kdemod.ath.cx/repo/current/i686<br />
for 32 bit Arch, or<br />
[kdemod]<br />
Server = http://kdemod.ath.cx/repo/current/x86_64<br />
for 64 bit Arch.<br />
<br />
*2. You must also activate the [community] repository in /etc/pacman.conf because KDEmod needs some packages from this repository. Make sure the following lines are uncommented:<br />
[community]<br />
Include = /etc/pacman.d/community<br />
<br />
<br />
*3. Update your package database with pacman -Syu. Now you can choose between two installations:<br />
<br />
pacman -S kdemod ''- installs a light base system''<br />
pacman -S kdemod-complete ''- installs the full KDE desktop''<br />
<br />
If you encounter any errors or conflicts at this step, check pacmans output, and if there are some unsolvable problems, tell us about them at the forums.<br />
*4. Install your localization. Take a look at the list of packages or simply do a pacman -Ss kdemod-kde-i18n to see which of them are already included.<br />
<br />
*5. Install all the extra apps you want. You can check out all available KDEmod packages by entering pacman -Sl kdemod<br />
<br />
====Useful KDE DAEMONS====<br />
<br />
KDE will require the '''hal''' ('''H'''ardware '''A'''bstraction '''L'''ayer) and '''fam''' ('''F'''ile '''A'''lteration '''M'''onitor) daemons. The '''kdm''' daemon is the '''K''' '''D'''isplay '''M'''anager, which provides a '''graphical login''', if desired.<br />
<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. The hal daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The fam daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system.. Both '''hal''' and '''fam''' make life easier for the KDE user, and are installed when you install KDE.<br />
<br />
Start hal and fam:<br />
<br />
/etc/rc.d/hal start<br />
<br />
/etc/rc.d/fam start<br />
<br />
Edit your DAEMONS section in /etc/rc.conf:<br />
nano /etc/rc.conf<br />
Add '''hal''' and '''fam''' to your DAEMONS section, to start them on bootup. If you prefer a graphical login, add '''kdm''' as well: <br />
DAEMONS=(syslog-ng network crond alsa '''hal fam kdm''')<br />
(If you prefer to log into the '''console''' and manually start X in the 'Slackware tradition', leave out kdm.)<br />
<br />
=====~/.xinitrc=====<br />
This file controls what occurs when you type 'startx'.<br />
<br />
Edit your /home/username/.xinitrc to utilize KDE:<br />
nano ~/.xinitrc<br />
Uncomment the 'exec startkde' line so that it looks like this:<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
#exec xterm<br />
#exec wmaker<br />
exec startkde<br />
# exec gnome-session<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
If you do not have a ~/.xinitrc file, simply create it with the above information. Remember, you must have only '''one''' uncommented line in your ~/.xinitrc.<br />
<br />
Switch to your normal user:<br />
su username<br />
Now try starting your X Server:<br />
startx<br />
<br />
Congratulations! Welcome to your KDE desktop environment on your new Arch Linux system! You may wish to continue by viewing [[Post Installation Tips]], or the rest of the information below.<br />
Advanced instructions for installing and configuring KDE can be found in the [[KDE]] article.<br />
<br />
===Xfce===<br />
====About Xfce====<br />
Xfce is a Desktop Environment, like GNOME or KDE. It contains a suite of apps like a root window app, window manager, file manager, panel, etc. Xfce is written using the GTK2 toolkit and contains its own development environment (libraries, daemons, etc) similar to other big DEs. Unlike GNOME or KDE, Xfce is lightweight and designed more around CDE than Windows or Mac. It has a much slower development cycle, but is very stable and extremely fast. Xfce is great for older hardware.<br />
<br />
====Installation====<br />
Install xfce with<br />
pacman -S xfce4 xfce4-goodies <br />
<br />
If you use kdm or gdm a new xfce session should have appeared. Alternatively, you can use<br />
startxfce4<br />
<br />
Advanced instructions for installing and configuring Xfce can be found in the [[Xfce]] article.<br />
<br />
===*box===<br />
====Fluxbox====<br />
Fluxbox © is yet another windowmanager for X.<br />
It's based on the Blackbox 0.61.1 code. Fluxbox looks like blackbox and handles styles, colors, window placement and similar things exactly like blackbox (100% theme/style compability).<br />
<br />
Install Fluxbox using <br />
pacman -S fluxbox fluxconf<br />
<br />
If you use gdm/kdm a new fluxbox session will be automatically added. Otherwise, you should modify your user's .xinitrc and add this to it:<br />
exec startfluxbox <br />
<br />
More information is available in the [[Fluxbox]] article.<br />
<br />
====Openbox====<br />
Openbox is a standards compliant, fast, light-weight, extensible window manager.<br />
<br />
Openbox works with your applications, and makes your desktop easier to manage. This is because the approach to its development was the opposite of what seems to be the general case for window managers. Openbox was written first to comply with standards and to work properly. Only when that was in place did the team turn to the visual interface.<br />
<br />
Openbox is fully functional as a stand-alone working environment, or can be used as a drop-in replacement for the default window manager in the GNOME or KDE desktop environments. <br />
<br />
Install openbox using<br />
pacman -S openbox obconf obmenu<br />
<br />
Once openbox is installed you will get a message to move menu.xml & rc.xml to ~/.config/openbox/ in your home directory:<br />
<br />
mkdir -p ~/.config/openbox/<br />
cp /etc/xdg/openbox/rc.xml ~/.config/openbox/<br />
cp /etc/xdg/openbox/menu.xml ~/.config/openbox/<br />
<br />
In the file "rc.xml" you can change various settings for Openbox (or you can use OBconf). In "menu.xml" you can change your right-click menu.<br />
<br />
To be able to log into openbox you can either go via graphical login using KDM/GDM or startx, in which case you will need to edit your ~/.xinitrc (as user) and add the following:<br />
<br />
exec openbox<br />
<br />
For KDM there is nothing left to do; openbox is listed in the sessions menu in KDM.<br />
<br />
Useful programs for openbox are:<br />
* PyPanel or LXpanel if you want a panel<br />
* feh if you want to set the background<br />
* ROX if you want a simple file manager and desktop icons<br />
<br />
More information is available in the [[Openbox]] article.<br />
<br />
===fvwm2===<br />
FVWM is an extremely powerful ICCCM-compliant multiple virtual desktop window manager for the X Window system. Development is active, and support is excellent. <br />
<br />
Install fvwm2 with<br />
pacman -S fvwm <br />
<br />
fvwm will automatically be listed in kdm/gdm in the sessions menu. Otherwise, add <br />
exec fvwm <br />
<br />
to your user's .xinitrc.<br />
<br />
Note that this stable version of fvwm is a few years old. If you want a more recent version of fvwm, there is a fvwm-devel package in the unstable repo.<br />
<br />
==HAL==<br />
Since you have now installed a desktop environment now would be a good time to also install HAL. HAL allows plug-and-play for your mobile phone, your iPod, your external HD's, etc. It will mount the device and make a nice visual icon on your desktop and/or in 'My Computer', allowing you to access the device after you have plugged it in instead of having to manually configure the /etc/fstab file or udev rules for each and every new device.<br />
<br />
KDE, GNOME and XFCE uses HAL.<br />
<br />
Refer to this article to install: [http://wiki.archlinux.org/index.php/HAL HAL]<br />
wikipedia: [http://en.wikipedia.org/wiki/HAL_(software) 1]<br />
<br />
==Useful Applications==<br />
This section will never be complete. It just shows some good applications for the everyday user. <br />
===Internet===<br />
<br />
=====Firefox=====<br />
The ever-popular Firefox web browser is available through pacman. Install with:<br />
<br />
pacman -S firefox<br />
Be sure and install 'flashplugin', 'mplayer', 'mplayer-plugin', and the 'codecs' packages for a complete web experience:<br />
pacman -S flashplugin mplayer mplayer-plugin codecs<br />
(The codecs package contains codecs for Quicktime and Realplayer content.)<br />
<br />
Thunderbird is useful for managing your emails. If you are using GNOME you may want to take a look at Epiphany and Evolution; if you are using KDE Konqueror and KMail could be your choice. If you want something completely different you can still use Opera. Finally, if you are working on the system console - or in a terminal session - you could use various text-based browsers like ELinks, Links and Lynx, and manage your emails with [[Mutt]]. Pidgin (previously known as Gaim) and Kopete are good instant messengers for GNOME and KDE, respectively. PSI and Gajim are perfect if you are using only Jabber or Google Talk.<br />
<br />
===Office===<br />
OpenOffice is a complete office suite (similar to Microsoft Office). Abiword is a good, small alternative word processor, and Gnumeric an Excel replacement for the GNOME desktop. KOffice is a complete office suite for the KDE Desktop. GIMP (or GIMPShop) is a pixel-based graphics program (similar to Adobe Photoshop), while Inkscape is a vector-based graphics program (like Adobe Illustrator). And, of course, Arch comes with a full set of LaTeX Programs.<br />
<br />
==Multimedia ==<br />
<br />
<br />
===Video Player===<br />
====VLC====<br />
VLC Player is a multimedia player for Linux. To install it, simply type the code below.<br />
<br />
pacman -S vlc<br />
<br />
(TODO) Instructions for VLC mozilla plug-in<br />
<br />
====Mplayer====<br />
MPlayer is a multimedia player for Linux. To install it, simply type the code below.<br />
<br />
pacman -S mplayer<br />
<br />
It also has a Mozilla plug-in for videos and streams embedded in web pages. To install it, simply type the code below.<br />
<br />
pacman -S mplayer-plugin<br />
<br />
If you use KDE, KMplayer is a better choice. It comes with a plug-in for videos and streams embedded in web pages, which works with Konqueror. To install it, simply type the code below.<br />
<br />
pacman -S kmplayer<br />
<br />
(TODO) GMPlayer instructions<br />
<br />
====GNOME====<br />
=====Totem=====<br />
[http://www.gnome.org/projects/totem/ Totem] is the official movie player of the GNOME desktop environment based on xine-lib or GStreamer (gstreamer is the default which installs with the arch totem package). It features a playlist, a full-screen mode, seek and volume controls, as well as keyboard navigation.<br />
It comes with added functionality such as:<br />
<br />
* Video thumbnailer for the file manager<br />
* Nautilus properties tab<br />
* Epiphany / Mozilla (Firefox) plugin to view movies inside your browser <br />
* Webcam utility (in development)<br />
<br />
Totem-xine is still the better choice if you want to watch DVDs.<br />
<br />
Totem is part of the gnome-extra group; the Totem webbrowser plugin isn't.<br />
<br />
To install separately:<br />
pacman -S totem<br />
<br />
To install the Totem webbrowser plugin:<br />
pacman -S totem-plugin<br />
<br />
====KDE====<br />
=====Kaffeine=====<br />
Kaffeine is a good option for KDE users. To install it, simply type the code below.<br />
<br />
pacman -S kaffeine<br />
<br />
===Audio Player===<br />
====Gnome/Xfce====<br />
=====Exaile=====<br />
[[Exaile]] is a music player written in Python that makes use of the GTK+ toolkit.<br />
=====Rhythmbox=====<br />
[http://www.gnome.org/projects/rhythmbox/ Rhythmbox] is an integrated music management application, originally inspired by Apple's iTunes. It is free software, designed to work well under the GNOME Desktop, and based on the powerful GStreamer media framework.<br />
<br />
Rhythmbox has a number of features, including:<br />
<br />
* Easy-to-use music browser<br />
* Searching and sorting<br />
* Comprehensive audio format support through GStreamer<br />
* Internet radio support<br />
* Playlists<br />
<br />
To install rhythmbox:<br />
pacman -S rhythmbox<br />
<br />
Other good audio players are: Banshee, Quodlibet, and Listen. See [http://gnomefiles.org/ Gnomefiles] to compare them.<br />
<br />
====KDE====<br />
=====Amarok=====<br />
[http://amarok.kde.org/ Amarok] is one of the best audio players and music library systems available for KDE. To install it, simply type the code below.<br />
<br />
pacman -S amarok-base<br />
<br />
====Console====<br />
Moc is a ncurses-based audio player for the console; another good choice is mpd.<br />
<br />
Another excellent choice is cmus[http://freshmeat.net/projects/cmus/].<br />
<br />
====Other X-based====<br />
(TODO) Xmms, audacious, bmpx.<br />
<br />
===Codecs and other multimedia content types===<br />
====DVD====<br />
You can use totem-xine, mplayer or kaffeine (just to name three of the big ones) to watch DVDs. The only thing you may miss is libdvdcss. Beware that using it may be illegal in some countries.<br />
<br />
====Flash====<br />
Install the flash plugin using<br />
pacman -S flashplugin<br />
to enable Macromedia (now Adobe) Flash in your browser.<br />
<br />
====Quicktime====<br />
Quicktime codecs are contained in the codecs package. Just type<br />
pacman -S codecs<br />
to install them.<br />
====Realplayer====<br />
The codec for Realplayer 9 is contained in the codecs package. Just type<br />
pacman -S codecs<br />
to install them. Realplayer 10 is available as a binary package for Linux. You can get it from AUR [http://aur.archlinux.org/packages.php?do_Details=1&ID=1590&O=0&L=0&C=0&K=realplay&SB=&SO=&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd here].<br />
<br />
===CD and DVD Burning===<br />
====GNOME====<br />
=====Brasero=====<br />
[http://www.gnome.org/projects/brasero/ Brasero] is an application that burns CDs/DVDs for the GNOME Desktop. It is designed to be as simple as possible and has some unique features to enable users to create their discs easily and quickly.<br />
<br />
To install:<br />
pacman -S brasero<br />
<br />
====KDE====<br />
=====K3b=====<br />
K3b - '''B'''urn, '''B'''aby, '''B'''urn in '''K'''DE<br />
-----<br />
[http://k3b.plainblack.com/ K3B] - CD/DVD burning application for Linux - optimized for KDE - licensed under the GPL.<br />
To install:<br />
pacman -S k3b<br />
<br />
<br />
<br />
<br />
(Todo) cdrecord, graveman...<br />
<br />
<br />
<br />
<br />
Most CD burners are wrappers for cdrecord:<br />
<br />
pacman -S cdrkit<br />
<br />
If you install packages for CD/DVD burning applications like Brasero or K3B it also installs the CD/DVD burning library for it, like libburn or cdrkit.<br />
<br />
A good command-line DVD-burning tool is growisofs:<br />
<br />
pacman -S dvd+rw-tools<br />
<br />
===TV-Cards===<br />
There are several things to do if you want to watch TV under (Arch) Linux. The most important task is to find out which chip your tuner is using. However, quite a bunch is supported. Be sure to check at a Hardware Database to be sure (e.g. [http://en.opensuse.org/HCL/TV_Cards]). Once you know your Model, there are just a few steps ahead to get you going.<br />
<br />
In most cases, you will need to use the bttv-drivers (other drivers exist, see [http://linux.bytesex.org/v4l2/drivers.html]) together with the I2C-modules. Configuring those is the hardest task. If you are lucky, a<br />
modprobe bttv<br />
will autodetect the card (check dmesg for results). In that case, you need only to install an application to watch TV. We will look at that later, though.<br />
If the autodetection did not work, you will need to check the file CARDLIST, which is included in the tarball of bttv[http://dl.bytesex.org/releases/video4linux/] to find out the right parameters for your card. A PV951 without radio support would need this line:<br />
modprobe bttv card=42 radio=0<br />
Some cards need the following line to produce sound:<br />
modprobe tvaudio<br />
However, that varies. So just try it out. Some other cards demand the following line:<br />
modprobe tuner<br />
This is object to trial-and-error, too.<br />
<br />
TODO: clarify the installation-procedure<br />
<br />
To actually watch TV, install the xawtv-package with<br />
pacman -S xawtv <br />
and read its manpage.<br />
<br />
TODO: clarify some possible problems and procedures. Introduction to XAWTV on another page?<br />
<br />
===Digital Cameras===<br />
Most newer digital cameras are supported as USB mass storage devices, which means that you can simply plug it in and copy the images. Older cameras may use the PTP (Picture Transfer Protocol) which requires a "special driver". gPhoto2 provides this driver and allows a shell-based transfer of the images; digikam (for KDE) and gthumb (for GNOME, gtkam would be another choice) use this driver and offer a nice GUI.<br />
<br />
===USB Memory Sticks / Hard Disks===<br />
USB Memory Sticks and hard disks are supported out of the box with the USB mass storage device driver and will appear as a new SCSI device (/dev/sdX). If you are using KDE or GNOME you should use dbus and hal (add them to your daemons in /etc/rc.conf), and they will be automatically mounted. If you use a different Desktop Environment you may have a look at ivman.<br />
<br />
==Maintaining the system==<br />
===Pacman===<br />
[[Pacman]] is both a binary and source package manager which is able to download, install, and upgrade packages from both remote and local repositories with full dependency handling, and has easy-to-understand tools for crafting your own packages too.<br />
<br />
A more-detailed description of Pacman can be found in [[Pacman|its article]].<br />
<br />
==== Useful commands ====<br />
<br />
To synchronize and update the local packages database with the remote repositories (it is a good idea to do this before installing and upgrading packages):<br />
pacman -Sy<br />
<br />
To '''upgrade''' all packages on the system:<br />
pacman -Su<br />
<br />
To sync, update, and '''upgrade''' all the packages on the system with one command:<br />
pacman -Syu<br />
<br />
To install or upgrade a single package or list of packages (including dependencies):<br />
pacman -S packageA packageB<br />
<br />
You can also sync, update the package database, and install packages in one command:<br />
pacman -Sy packageA packageB<br />
<br />
To remove a single package, leaving all of its dependencies installed:<br />
pacman -R package<br />
<br />
To remove a package and all of the package's dependencies which aren't used by any other installed package:<br />
pacman -Rs package<br />
<br />
To remove all of the package's dependencies now unneeded and do not make any backup of settings:<br />
pacman -Rsn package<br />
<br />
To search the remote (repo) package database for a list of packages matching a given keyword:<br />
pacman -Ss keyword<br />
<br />
To list all packages on your system<br />
pacman -Q<br />
<br />
To search (query) the local (your machine) package database for a given package:<br />
pacman -Q package <br />
<br />
To search (query) the local (your machine) package database for a given package and list all pertinent information:<br />
pacman -Qi package<br />
<br />
To defragment pacman's cache database and optimize for speed:<br />
pacman-optimize<br />
<br />
To count how many packages are currently on your system:<br />
pacman -Q | wc -l<br />
<br />
To install a package compiled from source using ABS and makepkg:<br />
pacman -U packagename.pkg.tar.gz<br />
<br />
Note: There are countless additional pacman functions and commands. Try man pacman and consult the [[pacman]] wiki entries.<br />
<br />
==Polishing & Further information==<br />
If after you have read this you want to do a bit of polishing, head to [[Post Installation Tips]]. For further information and support you can go to the [http://www.archlinux.org homepage], search the wiki, the [http://bbs.archlinux.org forums], the [http://wiki.archlinux.org/index.php/ArchChannel IRC channel], and the [http://www.archlinux.org/mailman/listinfo/ mailing lists].</div>
Potamota
https://wiki.archlinux.org/index.php?title=Pdnsd&diff=31630
Pdnsd
2007-11-02T14:54:38Z
<p>Potamota: </p>
<hr />
<div>[[Category:Daemons and system services]]<br />
[[Category:Networking]]<br />
<tt>pdnsd</tt> is a DNS server designed for local caching of DNS information. Correctly configured, it can significantly increase browsing speed on a broadband connection.<br />
<br />
==Installation==<br />
pdnsd can be installed with Pacman if you [[Enabling_the_community_repositories|enable the community repository]].<br />
<br />
pacman -S pdnsd<br />
<br />
==Configuration==<br />
<br />
===Initial preparation===<br />
<br />
The sample configuration file that comes with pdnsd needs a few changes before the daemon can start. First, copy the file to where pdnsd expects it to be.<br />
<br />
cp /etc/pdnsd.conf.sample /etc/pdnsd.conf<br />
<br />
===Format===<br />
<br />
The <tt>pdnsd.conf</tt> file uses a fairly simple format, but it has some differences from most other configuration files you've likely encountered. It has a collection of sections of various types. A section is started with the name of the type of section and an opening curly bracket (<tt>{</tt>) and is ended by a closing curly bracket (<tt>}</tt>). Sections cannot be nested.<br />
<br />
Inside each block is a series of options of the following format:<br />
<br />
option_name=option_value;<br />
<br />
Notice the semicolon at the end; unlike some formats, it is not optional.<br />
<br />
Comments are started with either <tt>#</tt> or <tt>/*</tt>. The former goes to the end of the line, the latter continues until it reaches <tt>*/</tt>.<br />
<br />
===DNS servers===<br />
<br />
pdnsd needs to know the address of at least one DNS server to collect DNS information from. This part of the setup differs depending on whether you have a broadband connection or dial-up. Broadband users should use the first server section as a starting point, dial-up users the second, leaving the other server sections commented out.<br />
<br />
; label : The <tt>label</tt> option is used to uniquely identify a server section. It's completely arbitrary, but one good choice is the name of your ISP.<br />
; ip : This option, used in the default broadband configuration, tells pdnsd the addresses of DNS servers to use. Multiple addresses should be separated by a single comma, no space. You can just copy the addresses from <tt>/etc/resolv.conf</tt>.<br />
; file : The <tt>file</tt> option can be used instead of <tt>ip</tt> to specify a set of DNS server IPs. Its value is the path to a file with servers listed in <tt>resolv.conf</tt> format. The default dial-up configuration uses it because the PPP client writes <tt>/etc/ppp/resolv.conf</tt> with the addresses it gets from the PPP server. You shouldn't need to change it unless you want to use a different DNS server than your ISP gives you by default.<br />
<br />
The rest of the server section will work without any more changes. For details on all the available options, see the [http://www.phys.uu.nl/~rombouts/pdnsd/doc.html pdnsd manual].<br />
<br />
===Security===<br />
<br />
The default configuration has a security flaw. The daemon runs as <tt>nobody</tt>, a standard account often used when you want to give a user as few permissions as possible. This is a bad idea with pdnsd, as the daemon needs read/write access to the DNS cache. If a malicious user finds a vulnerability in another process running as nobody, they may have the ability to inject false DNS data into the cache, leading to all sorts of possible problems.<br />
<br />
To avoid this risk, you should run pdnsd as a separate user. First you need to create it.<br />
<br />
groupadd pdnsd<br />
useradd -d /var/cache/pdnsd -g pdnsd -s /bin/false pdnsd<br />
<br />
<tt>/var/cache/pdnsd</tt> was chosen for the home folder because that's where pdnsd stores its data.<br />
<br />
Next, go back to <tt>pdnsd.conf</tt>. This time we'll be editing the global section at the top of the file. Change <tt>run_as</tt> from <tt>nobody</tt> to <tt>pdnsd</tt>. You should also add the <tt>strict_setuid</tt> option for extra security. Set it to <tt>on</tt>.<br />
<br />
Now we've limited the server a little too much. It needs to write to a folder in <tt>/var/cache</tt>, but it can't, since it no longer has root privileges. Let's help it out a little.<br />
<br />
mkdir /var/cache/pdnsd<br />
chown pdnsd:pdnsd /var/cache/pdnsd<br />
chmod 700 /var/cache/pdnsd<br />
<br />
If you got hasty and tried starting the daemon before you got to this section, you already have a <tt>pdnsd.cache</tt> file, and it isn't owned by the pdnsd user. If that's the case, just delete it. It will be automatically regenerated.<br />
<br />
===Testing===<br />
<br />
You should now have a working pdnsd daemon. Fire it up and find out.<br />
<br />
/etc/rc.d/pdnsd start<br />
<br />
You can test it with the <tt>nslookup</tt> utility (from the <tt>dnsutils</tt> package).<br />
<br />
nslookup www.google.com 127.0.0.1<br />
<br />
If everything works, you should see a list of IP addresses associated with <tt>www.google.com</tt>.<br />
<br />
===System setup===<br />
<br />
Now it's time to point your system toward your brand-new DNS server.<br />
<br />
If you use DHCP to configure your network settings, you need to take a brief detour into the <tt>/etc/conf.d/dhcpcd</tt> config file. Add <tt>-R</tt> to the string of options. This prevents it from overwriting <tt>/etc/resolv.conf</tt>. It should look something like this:<br />
<br />
DHCPCD_ARGS="-t 10 -h $HOSTNAME -R"<br />
<br />
Now just edit <tt>/etc/resolv.conf</tt> and replace the contents with this.<br />
<br />
nameserver 127.0.0.1<br />
<br />
All that's left is adding <tt>pdnsd</tt> to your daemons array in <tt>/etc/rc.conf</tt>. It should be immediately after network, as it depends on the network to run, and some daemons that use the network rely on working DNS.<br />
<br />
Congratulations! You're done!<br />
<br />
==FAQs==<br />
<br />
; Q) It doesn't seem much faster to me. Why? : '''A)''' The extra speed gained from running a local DNS cache is all in how long it takes to connect to a server. Throughput, what people normally think of as speed, will not be affected. The difference is most noticeable when browsing the web, as that typically involves small downloads from several servers. With slower connections, especially dial-up, throughput is the primary bottleneck, so there won't be as large a difference percentage-wise.<br />
; Q) Why is it so much slower now than before? : '''A)''' You almost certainly have the <tt>proxy_only</tt> option turned off in one of the server sections of <tt>pdnsd.conf</tt>. By default, pdnsd frequently asks several DNS servers about a domain to get the most accurate response possible. The <tt>proxy_only</tt> option disables this feature. It should be turned on if you use the DNS server provided by your ISP.</div>
Potamota
https://wiki.archlinux.org/index.php?title=Beginners%27_guide_(Indonesia)&diff=30304
Beginners' guide (Indonesia)
2007-10-05T00:45:32Z
<p>Potamota: New page: Category: Mendapatkan dan Instalasi Arch (Indonesia) Category:Tentang Arch (Indonesia) Category:HOWTOs (Indonesia) {{translateme}} {{i18n_links_start}} {{i18n_entry|English|Beg...</p>
<hr />
<div>[[Category: Mendapatkan dan Instalasi Arch (Indonesia)]]<br />
[[Category:Tentang Arch (Indonesia)]]<br />
[[Category:HOWTOs (Indonesia)]]<br />
{{translateme}}<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Beginners Guide}}<br />
{{i18n_entry|Česky|Průvodce začátečníka (Česky)}}<br />
{{i18n_entry|Italiano|Beginners Guide (Italiano)}}<br />
{{i18n_entry|Lietuviškai|Pradedančiųjų gidas (Lietuviškai)}}<br />
{{i18n_entry|Indonesia|Beginners Guide (Indonesia)}}<br />
{{i18n_links_end}}<br />
==Pendahuluan==<br />
=====Segala hal yang ingin kamu tanyakan tentang instalasi Arch, tapi takut untuk menanyakan.=====<br />
Dokumen ini akan membimbing kamu dalam menginstalasi dan mengkonfigurasi ArchLinux. Walau petunjuk ini ditujuakan untuk membimbing kamu mendapatkan sistem Arch yang terkonfigurasi seluruhnya (desktop environment, menonton DVD/Video, mendengarkan musik, Internet, mail) namun tidak berisi semua pilihan yang dapat kamu gunakan untuk mengerjakan hal tersebut. Petunjuk ini difokuskan pada beberapa langkah-langkah penting/dasar saja; jika kamu ingin bahasan yang lebih dalam kamu bisa mengunjungi [[Main Page|Arch Linux Wiki]] atau [http://bbs.archlinux.org/ Arch Linux Forums]. Kamu juga bisa membaca [[The Arch Way]] untuk mengetahui prinsip-prinsip dasar ArchLinux.<br />
<br />
=====DON'T PANIC!=====<br />
Harap disadari bahwa instalasi ArchLinux mungkin sangat berbeda dengan distro lain yang pernah kamu coba, khususnya bagi pemula. Sistem ArchLinux dibangun oleh '''pengguna''', dari installer, sampai ''base system'' dengan hanya menggunakan shell bash dan beberapa tools dasar sistem saja. dari ''command line'', kamu dapat menambahkan paket dari ''Arch repositories'' menggunakan [[pacman]] melalui sambungan internet, sampai sistem kamu sesuai dengan kebutuhan/kegininan. Dengan hal ini kamu akan mendapatkan sistem yang fleksibel, sesuai pilihan dan dapat kamu kendalikan karena '''kamu''' sendiri yang membangunnya, kamu akan mengetahui apa yang ada di dalam sistem kamu.<br />
<br />
Jika kamu merasa ada yang kurang dari wiki ini silahkan ditambahkan, atau kamu bisa juga mengunjungi forum Arch ini [http://bbs.archlinux.org/viewtopic.php?t=29055 yang ditujukan untuk pemula. <br />
<br />
Selamat datang di Arch! Mari kita mulai :)<br />
<br />
==Dapatkan ISO terbaru==<br />
<br />
Kamu dapat mengunduh rilis Arch resmi terbaru dari [http://www.archlinux.org/download/ www.archlinux.org/download/].<br />
<br />
Sangat direkomendasikan untuk memilih '''base-CD''', untuk beberapa alasan.<br />
<br />
# Waktu/bandwidth yang dibutuhkan lebih sedikit untuk kamu dan server,<br />
# Paket di versi full mungkin nantinya akan ada yang konflik ketika kamu melakukan update.<br />
# Base system lebih mudah dan cepat untuk up-to-date, dan,<br />
# Petunjuk ini lebih ditujukan untuk installasi dari base-CD. <br />
<br />
==Instalasi base system ==<br />
<br />
Selain petunjuk ini, kamu dapat juga dapat menggunakan petunjuk resmi ini [[Official Arch Linux Install Guide]] atau [http://www.archlinux.org/static/docs/arch-install-guide.html versi yang dapat di print] juga tersedia.<br />
<br />
===Boot CD Arch Linux===<br />
<br />
Masukkan CD dan boot dari CD-ROM, kamu mungkin perlu mengganti urutan boot pada bios komputer kamu (biasanya dengan menekan F11 atau F12).<br />
<br />
Beberapa pilihan pada saat booting ArchLinux CD yang dapat kamu gunakan:<br />
* ide-legacy jika IDE drive kamu bermasalah.<br />
* noapic acpi=off pci=routeirq nosmp jika sistem kamu hangs ketika boot.<br />
* memtest86+ if jika kamu ingin memeriksa memorimu.<br />
<br />
Pilih "Arch Linux Installation / Rescue System". Jika kamu ingin merubah opsi boot tekan e.<br />
<br />
===Changing the keymap===<br />
Press enter at the welcome screen. If you have a non-US keyboard layout type<br />
km<br />
at the prompt and choose the appropriate keymap.<br />
<br />
''Example''(norwegian) for illustrative purposes:<br />
<br />
In console keymap screen select<br />
no-latin1<br />
In console font screen select<br />
lat0-16<br />
<br />
Choosing "default8x16.psfu.gz" for console font is a safe choice.<br />
<br />
===Start the Installation===<br />
Enter<br />
/arch/setup <br />
to start the installation. <br />
<br />
====Select an installation source====<br />
You will be prompted for an installation source. Choose CD if you are using a base or full (current) ISO, or choose FTP if you are using the FTP ISO.<br />
<br />
====Prepare Hard Drive====<br />
Select the first menu entry "Prepare Hard Drive". Beware that "Auto-Prepare" may not be a safe choice because it will erase the entire hard drive.<br />
Here we will manually partition the hard drive. Choose "2. Partition Hard Drives", select the hard drive you want (/dev/sdx), and create some partitions. <br />
<br />
<br />
=====Partitions=====<br />
<br />
<br />
A partition is a section of hard disk space that will appear as a separate disk, and can be added to your Arch Linux file system. Partitions are broken up into "Primary", "Extended", and "Logical". <br />
Primary partitions can be bootable, and are limited to 4. For example, if you are using a PC with a single SATA drive, the first primary partition will be referred to as sda1. The second primary will be referred to as sda2, then sda3, and sda4. Beyond 4 partitions, we are forced to use an extended partition which will contain logical partitions.<br />
<br />
Extended partitions are not usable by themselves; they are merely a "container" for logical partitions. Logical partitions must be contained within this extended partition. When partitioning a disk, one can see this numbering scheme by creating primary partitions sda1-3 followed by creating an extended partition, sda4, and then creating logical partition(s) within the extended partition; sda5, sda6, and so on.)<br />
<br />
<br />
Everyone has a different opinion on how best to partition the disk. What you need at the least is one primary partition which contains the root [http://en.wikipedia.org/wiki/File_system Filesystem] ( / ) and one for swap. Other candidates for separate partitions are /boot (which mainly contains the kernel) and /home (which contains the user data). It is good practice to have / and /home on separate partitions. This makes it possible to reinstall Arch Linux (or even another distro) for any reason, while keeping your data, music, pictures, and desktop environment preferences.<br />
<br />
In this example guide, we will stick with one partition for /, one partition for /home, and a swap partition.<br />
<br />
=====Swap Partition=====<br />
A swap partition is a place on your hard drive where "virtual ram" resides. If your processes need more RAM than is physically available, Linux can't fulfill the request and an error occurs. A swap partition helps in this situation by supplementing the physical RAM with virtual RAM. Linux uses the space on the hard disk to store the information that won't fit into the physical RAM any more (it's actually a bit more complex because Linux tries to put information into the swap space that isn't frequently used). Because a hard disk is very slow compared to physical RAM, this is only<br />
a makeshift. <br />
<br />
<br />
Ask two people about a swap partition and you will get four different answers. If you have plenty of RAM (more than 1024 MB) it may be possible to not use a swap partition at all. Some people suggest using twice the amount of physical RAM, while others recommend not using more than 1024 MB. I believe keeping the swap size between 512 MB and 1 GB is a good choice. Therefore, we will create a 1 GB swap space in this example.<br />
<br />
Let's start creating the '''primary partition''' that will contain the '''root''' filesystem. Choose New -> Primary and enter the size you want (something between 4 and 8 GB is a good choice for a full-featured Linux system). Put the partition at the beginning of the disk. Select the newly created partition and choose "Bootable" to make this partition bootable. Add another '''partition for your home directory'''. Choose another primary partition and set the size to a value you like. The size really depends on what your users store in their home directories, so I cannot make any suggestions. The size may vary between a few hundred megabytes for some office documents up to hundreds of gigabytes for videos and MP3s. If you <br />
want to use the whole space on your hard disc, use the remaining space minus 512 MB - 1 GB for the size. At last we<br />
create a third '''partition for swap'''. Select a size between 512 MB and 1 GB and change the type to 82 (Linux swap / Solaris).<br />
<br />
This is what your Layout should look like (size may vary depending on your decisions):<br />
<br />
Name Flags Part Type FS Type [Label] Size (MB)<br />
-------------------------------------------------------------------------<br />
sda1 Boot Primary Linux (4096 - 8192)<br />
sda2 Primary Linux (> 100)<br />
sda3 Primary Linux swap / Solaris (512 - 1024)<br />
<br />
Choose Write and type yes. Beware that this operation may destroy data on your disk if you deleted partitions. Choose Quit to leave the partitioner. <br />
Choose Done to leave this menu and continue with "Set Filesystem Mountpoints".<br />
<br />
====Set File system Mountpoints====<br />
<br />
=====A few brief words about '''filesystems''' and "file systems":=====<br />
<br />
Technically, and for accuracy, a '''filesystem''' is a data format for information throughput, whereas a "file system" (notice the space) is a term referring to the layout of all files and directories on a given system. (In our case, the hierarchical UNIX file system.) Therefore, when you are asked if you want to create a '''filesystem''', you are being asked if you want to '''format''' the particular partition... but when you are asked for mount points, you are providing where the given partition will reside in your Arch Linux "file system". Let's begin.<br />
<br />
First you will be asked for your swap partition. Choose the appropriate partition (sda3 in this example). You will be asked if you want to create a swap filesystem; select yes. Next, choose where to mount the / (root) directory (sda1 in the example). You will be asked what kind of filesystem you want.<br />
<br />
Again, ask two people which filesystem to choose and you will get five different answers. Each one has its advantages and disadvantages. Here is a very brief overview of supported filesystems.<br />
<br />
1. '''ext2''' - Old, reliable GNU/Linux filesystem. Fast, and very stable, but without journaling.<br />
<br />
2. '''ext3''' - Essentially the ext2 system, but with journaling support. ''Slightly'' slower than ext2 and other filesystems. '''Extremely''' stable and the most widely used, supported, and developed.<br />
<br />
3. '''ReiserFS''' - Hans Reiser's high-performance journaling FS uses a very interesting method of data throughput. ReiserFS is very fast, especially when dealing with many small files. ReiserFS is quite well established and stable.<br />
<br />
4. '''JFS''' - IBM's Journaling FS. JFS is quite well established, fast, and stable.<br />
<br />
5. '''XFS''' - is a fast journaling filesystem which is best suited for large files, greater than 1 GB in size. Slower with small files. Quite stable.<br />
<br />
A major difference is [http://en.wikipedia.org/wiki/Journaling_file_system journaling] (something similar to transaction logs in database environments). All filesystems except ext2 use journaling. ext3 is completely compatible with ext2, so you can mount it even with very-old rescue CDs. A safe choice for the root partition is ext3. ReiserFS, XFS, and JFS are also OK to use because GRUB (the boot manager which we will install later) can boot from them too. Create the filesystem (format the partition) by selecting yes. You will now be prompted to add any additional partitions. In our example, only sda2 is remaining. Choose a filesystem type and mount it as /home. Again, create the filesystem and choose Done. Return to main menu.<br />
<br />
===Select Packages===<br />
Now we shall select packages to install in our system. Choose CD as source and select the appropriate CD drive if you have more than one.<br />
Since this guide is geared toward a '''base''' installation, choose the base category (keeping all base packages selected is a safe choice). If you chose the current ISO rather than the base ISO, it is up to you if you want to select more packages, but we will show you later how to install additional, up-to-date software more easily, rather than installing and reinstalling. (Since the install CD you are using has been created, there are no doubt numerous updates available for packages contained therein, and installing additional up-to-date software via pacman will be covered below.) If you are '''sure''' you will not be needing certain packages (for instance, a filesystem type you don't need, ISDN, or PPPoE support), feel free to remove them from the base package selection. <br />
<br />
Step forward to "Install Packages".<br />
<br />
===Install Packages===<br />
This is an easy task because everything happens automatically. Get yourself a cup of coffee (if you're into coffee ;)) and wait until the installation has finished (press continue if needed). Drink quickly, because the Arch Linux base packages install in just a couple of minutes.<br />
<br />
===Configure The System===<br />
You will be asked if you want to choose hwdetect to gather some information for your configuration. This is recommended so you should choose this option. <br />
Now you will be asked if you need support for booting from USB devices, FireWire devices, PCMCIA devices, NFS shares, software RAID arrays, LVM2 volumes, and encrypted volumes. Choose yes if you need it; in our example nothing is needed. Now you will be asked which text editor you want to use; choose [http://en.wikipedia.org/wiki/Nano_%28text_editor%29 nano] if you are not familiar with [http://en.wikipedia.org/wiki/Vim_%28text_editor%29 vi/vim]. You will now get a menu with most important config files for your system. We will do only some minor tweaks at this time. If you want to look up the available options as stated in rc.conf just press Alt+F2 to get a shell, look it up, and switch back to the installer with Alt+F1. <br />
<br />
=====/etc/rc.conf=====<br />
<br />
* Change your LOCALE if needed (e.g. "de_DE.utf8") (This locale must coincide with /etc/locale.gen. '''See below'''.)<br />
* Change your TIMEZONE if needed (e.g. "Europe/Berlin")<br />
* Change your KEYMAP if needed (e.g. "de-latin1-nodeadkeys")<br />
<br />
* Change MODULES if you know that an important module is missing (hwdetect should have filled in the most important modules)<br />
* Change your HOSTNAME<br />
* Change your Network settings:<br />
** Don't modify the lo line<br />
** Adjust the IP address, netmask and broadcast address if you are using a static IP<br />
** Set eth0="dhcp" if you have a router which dynamically assigns an IP address<br />
** If you have a static IP set the gateway address to the one of your router and remove the ! in front of the ROUTES entry<br />
=====About DAEMONS=====<br />
You don't have to change the [[daemons]] line at this time, but it is useful to explain what daemons are, because we need them later in this guide. Analogous to a Windows service, a daemon is a program that runs in the background, waiting for events to occur and offering services. A good example is a webserver that waits for a request to deliver a page or an SSH server waiting for someone trying to log in. While these are full-featured applications, there are daemons whose work is not that visible. Examples are a daemon which writes messages into a log file (e.g. syslog, metalog), a daemon which lowers your CPU's frequency if your system has nothing to do, and a daemon which offers you a graphical login (e.g. gdm, kdm). All these programs can be added to the daemons line and will be started when the system boots. Useful daemons will be presented during this guide.<br />
<br />
Use Ctrl+X to leave the editor.<br />
<br />
=====/etc/hosts=====<br />
Add the desired ''hostname'' (the one you set in rc.conf before) so that it looks like this:<br />
127.0.0.1 localhost.localdomain localhost ''yourhostname''<br />
This format, '''including the 'localhost' entries''', is required for program compatibility.<br />
For most users, simply adding the ''hostname'' to the end of the default line will work, however, some users recommend using the following syntax:<br />
127.0.0.1 ''yourhostname''.domain.org localhost.localdomain localhost ''yourhostname''<br />
If you use a static IP, add another line using the syntax: <static-ip> hostname.domainname.org hostname, <br />
e.g.:<br />
192.168.1.100 yourhostname.domain.org yourhostname<br />
<br />
===== /etc/fstab, mkinitcpio.conf and modprobe.conf=====<br />
We shouldn't need to edit mkinitcpio.conf, or modprobe.conf at this point. mkinitcpio configures the ramdisk (e.g. booting from RAID, encrypted volumes) and modprobe can be used to set some special config options for the modules).<br />
<br />
If you are planning on using the hal daemon to automate the mounting of disks, optical drives, usb drives, etc., you may wish to edit /etc/fstab by commenting out the entries for cdrom, floppy, and dvd.<br />
<br />
=====/etc/resolv.conf (for Static IP)=====<br />
If you use a static IP, set your DNS servers in /etc/[[resolv.conf]] (nameserver <ip-address>). You may have as many as you wish.<br />
<br />
If you are using a router, you will probably want to specify your DNS servers in the router itself, and merely point to it from your resolv.conf, using your router's IP (which is also your gateway from /etc/rc.conf), e.g.:<br />
nameserver 192.168.1.1<br />
Alternatively, add your preferred servers one by one, e.g.:<br />
nameserver 4.2.2.1<br />
nameserver 4.2.2.2<br />
<br />
=====/etc/locale.gen=====<br />
Choose the locale(s) you need (remove the # in front of the lines you want), e.g.:<br />
en_US ISO-8859-1<br />
en_US.UTF-8 <br />
('''Your locale must coincide with the one specified in /etc/rc.conf above.''')<br />
=====Root password=====<br />
Finally, set a root password and make sure that you remember it later. Return to the main menu and continue with installing a kernel.<br />
<br />
===Install Kernel===<br />
Not many choices here; choose v2.6 and continue. You may want to switch your kernel later. A fallback image will be created, keeping mkinitcpio as it is shown as a safe choice. Continue with installing a bootloader.<br />
<br />
===Install Bootloader===<br />
Because we have no secondary operating system in our example, we will need a bootloader. [http://www.gnu.org/software/grub/ GNU GRUB] is the recommended bootloader. Alternatively, you may choose [http://lilo.go.dyndns.org/ LILO]. The shown GRUB configuration (/boot/grub/menu.lst) should be sufficient. The only thing you may want to alter is the resolution of the console. Add<br />
a vga=<number> to the first kernel line. (A table of resolutions and the corresponding numbers is printed in the menu.lst.) <br />
title Arch Linux (Main)<br />
root (hd0,0)<br />
kernel /boot/vmlinuz26 root=/dev/sda1 ro vga=773<br />
initrd /boot/kernel26.img<br />
The "vga=773" argument will give a 1024x768 framebuffer with 256 color depth.<br />
<br />
Exit the install and type reboot.<br />
<br />
If everything goes well, your new Arch Linux system will boot up and finish with a login prompt (you may want to change the boot order in your BIOS back to booting from hard disk).<br />
<br />
Congratulations, and welcome to your shiny, new Arch Linux base system!<br />
<br />
==Configuring the base system ==<br />
Your new Arch Linux base system is now a functional GNU/Linux operating system ready for customization. From here, you may build this elegant set of tools into whatever you wish or require for your purposes!<br />
Let's begin.<br />
-----<br />
Login with your root account. We will configure pacman and update the system as root, then add a normal user. <br />
<br />
===Configuring pacman===<br />
Edit /etc/pacman.conf<br />
nano -w /etc/pacman.conf<br />
and remove the # in front of the "Include = /etc/pacman.d/community" and "[community]" lines to enable Arch's community repository, which offers many useful applications. Now edit /etc/pacman.d/community and move the mirrors which are located nearest to you up (if you use nano, Alt+A starts selecting an area, cursor down marks the lines, Ctrl+K cuts the selected area and Ctrl+U uncuts it). Repeat this for all files in /etc/pacman.d/.<br />
<br />
===Configuring the network (if necessary)===<br />
<br />
If everything went fine, you should have a working network. Try to ping www.google.com to verify this.<br />
ping -c 3 www.google.com<br />
<br />
If you have successfully established a network connection, continue with "Update, Sync and Upgrade the system with pacman".<br />
<br />
If, after trying to ping www.google.com, you get an "unknown host" error, you may conclude that your network is not configured. You may choose to double-check the following files for integrity and proper settings:<br />
<br />
'''/etc/rc.conf''' # Specifically, check your HOSTNAME= and NETWORKING section<br />
<br />
'''/etc/hosts''' # Double-check your format. (See above.)<br />
<br />
'''/etc/resolv.conf''' # If you are using a static IP. If you are using DHCP, this file will be dynamically created and destroyed by default, but can be changed to your preference. (See [[Network]].)<br />
<br />
Advanced instructions for configuring the network can be found in the [[Network]] article.<br />
<br />
====Wired LAN====<br />
<br />
Check your Ethernet with<br />
ifconfig<br />
where you should see an entry for eth0. If required, you can set a new static IP with<br />
ifconfig eth0 <ip address> netmask <netmask> up <br />
and the default gateway with<br />
route add default gw <ip address of the gateway><br />
Check to see if /etc/resolv.conf contains your DNS server and add it if it is missing. <br />
Check your network again with ping www.google.de. If everything is working now, adjust /etc/rc.conf as described in section 2.6 (static IP). If you have a DHCP server/router in your network try<br />
dhcpcd eth0<br />
If this is working, adjust /etc/rc.conf as described in section 2.6 (dynamic IP).<br />
<br />
====Wireless LAN====<br />
[[Wireless Setup]]<br />
(TODO) Simplify and generalize it, link only for more-advanced stuff<br />
<br />
====Analog Modem====<br />
To be able to use a Hayes-compatible, external, analog modem, you need to at least have the ppp package installed. Modify the file /etc/ppp/options to suit your needs and according to man pppd. You will need to define a chat script to supply your username and password to the ISP after the initial connection has been established. The manpages for pppd and chat have examples in them that should suffice to get a connection up and running if you're either experienced or stubborn enough. With udev, your serial ports usually are /dev/tts/0 and /dev/tts/1.<br />
Tip: Read [[Dialup without a dialer HOWTO]].<br />
<br />
Instead of fighting a glorious battle with the plain pppd, you may opt to install wvdial or a similar tool to ease the setup process considerably. In case you're using a so-called WinModem, which is basically a PCI plugin card working as an internal analog modem, you should indulge in the vast information found on the [http://www.linmodems.org/ LinModem] homepage.<br />
<br />
====ISDN====<br />
<br />
Setting up ISDN is done in three steps:<br />
# Install and configure hardware<br />
# Install and configure the ISDN utilities<br />
# Add settings for your ISP <br />
<br />
The current Arch stock kernels include the necessary ISDN modules, meaning that you won't need to recompile your kernel unless you're about to use rather odd ISDN hardware. After physically installing your ISDN card in your machine or plugging in your USB ISDN-Box, you can try loading the modules with modprobe. Nearly all passive ISDN PCI cards are handled by the hisax module, which needs two parameters: type and protocol. You must set protocol to '1' if your country uses the 1TR6 standard, '2' if it uses EuroISDN (EDSS1), '3' if you're hooked to a so-called leased-line without D-channel, and '4' for US NI1.<br />
<br />
Details on all those settings and how to set them is included in the kernel documentation, more specifically in the isdn subdirectory, and available online. The type parameter depends on your card; a list of all possible types can be found in the README.HiSax kernel documentation. Choose your card and load the module with the appropriate options like this:<br />
<br />
modprobe hisax type=18 protocol=2<br />
<br />
This will load the hisax module for my ELSA Quickstep 1000PCI, being used in Germany with the EDSS1 protocol. You should find helpful debugging output in your /var/log/everything.log file, in which you should see your card being prepared for action. Please note that you will probably need to load some USB modules before you can work with an external USB ISDN Adapter.<br />
<br />
Once you have confirmed that your card works with certain settings, you can add the module options to your /etc/modprobe.conf:<br />
<br />
alias ippp0 hisax<br />
options hisax type=18 protocol=2<br />
<br />
Alternatively, you can add only the options line here, and add hisax to your MODULES array in the rc.conf. It's your choice, really, but this example has the advantage that the module will not be loaded until it's really needed.<br />
<br />
That being done, you should have working, supported hardware. Now you need the basic utilities to actually use it!<br />
<br />
Install the isdn4k-utils package, and read the manpage to isdnctrl; it'll get you started. Further down in the manpage you will find explanations on how to create a configuration file that can be parsed by isdnctrl, as well as some helpful setup examples. Please note that you have to add your SPID to your MSN setting separated by a colon if you use US NI1.<br />
<br />
After you have configured your ISDN card with the isdnctrl utility, you should be able to dial into the machine you specified with the PHONE_OUT parameter, but fail the username and password authentication. To make this work add your username and password to /etc/ppp/pap-secrets or /etc/ppp/chap-secrets as if you were configuring a normal analogous PPP link, depending on which protocol your ISP uses for authentication. If in doubt, put your data into both files.<br />
<br />
If you set up everything correctly, you should now be able to establish a dial-up connection with<br />
isdnctrl dial ippp0<br />
as root. If you have any problems, remember to check the logfiles!<br />
<br />
====DSL (PPPoE)====<br />
<br />
These instructions are relevant to you only if your PC itself is supposed to manage the connection to your ISP. You do not need to do anything but define a correct default gateway if you are using a separate router of some sort to do the grunt work.<br />
<br />
Before you can use your DSL online connection, you will have to physically install the network card that is supposed to be connected to the DSL-Modem into your computer. After adding your newly installed network card to the modules.conf/modprobe.conf or the MODULES array, you should install the rp-pppoe package and run the pppoe-setup script to configure your connection. After you have entered all the data, you can connect and disconnect your line with<br />
<br />
/etc/rc.d/adsl start<br />
<br />
and<br />
<br />
/etc/rc.d/adsl stop<br />
<br />
respectively. The setup usually is rather easy and straightforward, but feel free to read the manpages for hints. If you want to automatically dial in on boot-up, add adsl to your DAEMONS array.<br />
<br />
==Update, Sync and Upgrade the system with [[pacman]]==<br />
Now we will update the system using [[pacman]], the package manager of Arch Linux. Pacman is fast, simple, and extremely powerful. It manages your entire package system and allows installation, package removal, package downgrade (through cache), custom compiled package handling, automatic dependency resolution, and much more.<br />
<br />
Update, sync, and '''upgrade''' your entire new system with:<br />
pacman -Syu<br />
pacman will now fetch the latest information about available packages and perform all available upgrades. (You may be prompted to upgrade pacman itself at this point. If so, say yes, and then reissue the pacman -Syu command when finished.)<br />
<br />
=====''Take note as to whether a kernel upgrade is occurring!''=====<br />
<br />
If the kernel is upgraded, modules such as nvidia will be rendered inoperable, since the new, upgraded versions will be built against the newer kernel, and your system is currently using an older one. A reboot will be necessary.<br />
<br />
=====The beauty of the rolling release=====<br />
Keep in mind that Arch is a '''rolling release''' distribution. This means there is never a reason to reinstall or perform elaborate system rebuilds to upgrade to the newest version. Simply issuing '''pacman -Syu''' periodically keeps your entire system up-to-date and on the bleeding edge. At the end of this upgrade, your system is completely current.<br />
<br />
=====Get familiar with pacman=====<br />
Pacman is the Arch user's best friend. It is highly recommended to study and learn how to use the pacman tool. Try:<br />
man pacman<br />
Check out the bottom of this article, and look up the [[pacman]] wiki entries at your leisure.<br />
<br />
<br />
<br />
===Add a user and setup groups===<br />
You should not do your everyday work using the root account. It is more than poor practice; it is dangerous. Root is for administrative tasks. Instead, add a normal user account using:<br />
adduser<br />
While most default options are safe to use, you may want to add at least audio and wheel to your additional groups. <br />
Audio allows your user to use the audio card, while wheel allows switching to the root account with su. Other groups to be added, (separated by a comma) include:<br />
<br />
*disk - for managing disks, including USB flash drives and such<br />
<br />
*storage - for managing storage devices<br />
<br />
*video - for managing video tasks<br />
<br />
*optical - for managing tasks pertaining to the optical drive(s)<br />
<br />
*floppy - for access to a floppy if necessary<br />
<br />
*lp - for managing printing tasks<br />
<br />
You may also consider adding optical to your additional groups to enable CD/DVD recording from your user account.<br />
<br />
See the [http://wiki.archlinux.org/index.php/Groups Groups] article to understand what groups you need to be a member of. <br />
You may also add your user to the desired groups like so, (as root):<br />
usermod -aG audio,video,floppy,lp,optical,network,storage,wheel USERNAME<br />
<br />
==Installing and configuring Hardware==<br />
===Configure the audio card===<br />
Your audio card should already be working, but you can't hear anything because it is muted by default. Install the alsa-utils <br />
pacman -S alsa-utils<br />
and use alsamixer to adjust the channels: <br />
alsamixer<br />
Unmute the Master and PCM channels by scrolling to them with cursor left/right and pressing '''M'''. Increase the volume levels with the cursor-up key. (70-90 Should be a safe range.) Leave alsamixer by pressing ESC and store the settings with<br />
alsactl store<br />
If you plan on using a desktop environment such as GNOME or KDE and would prefer that alsa remember your settings when you change them, do not execute the above command--your volume settings will be remembered automatically.<br />
Add alsa to your DAEMONS section in /etc/rc.conf to automatically restore the mixer on boot-up.<br />
nano /etc/rc.conf<br />
<br />
DAEMONS=(syslog-ng network crond '''alsa''')<br />
<br />
===Configuring CPU frequency scaling===<br />
Modern processors can decrease their frequency and voltage to reduce heat and power consumption. Less heat leads to a quieter system; even a desktop system will benefit from it. Install cpufrequtils with<br />
pacman -S cpufrequtils<br />
and add cpufreq to your daemons in /etc/rc.conf. Edit the config file /etc/conf.d/cpufreq and change <br />
governor="conservative"<br />
which dynamically increases the CPU frequency if needed (which is a safe choice on desktop systems too). Alter min_freq and max_freq to match your system's CPU spec. If you don't know the frequencies, run ''cpufreq-info'' after loading one of the frequency scaling modules. Add the frequency scaling modules to your /etc/rc.conf modules line. Most modern notebooks and desktops can simply use the ''acpi-cpufreq'' driver, however other options include the ''p4-clockmod, powernow-k6, powernow-k7, powernow-k8, and speedstep-centrino'' drivers. Load the module with<br />
modprobe <modulname> <br />
and start cpufreq with<br />
/etc/rc.d/cpufreq start<br />
For more details, see [[Cpufrequtils]]<br />
<br />
===Additional tweaks for laptops===<br />
ACPI support is needed if you want to use some special functions on your notebook (e.g. sleep, sleep when lid is closed, special keys...). Install acpid <br />
pacman -S acpid<br />
and add it to the daemons in /etc/rc.conf (acpid). Start it with<br />
/etc/rc.d/acpid start<br />
<br />
More-specific information about Arch Linux on various Laptops can be found at [[:Category:Laptops (English)]]<br />
<br />
==Installing and configuring X==<br />
The X Window System (commonly X11, or just simply X) is a networking and display protocol which provides windowing on bitmap displays. It provides the standard toolkit and protocol to build graphical user interfaces (GUIs) on Unix-like operating systems.<br />
<br />
X provides the basic framework, or primitives, for building GUI environments: drawing and moving windows on the screen and interacting with a mouse and/or keyboard. X does not mandate the user interface — individual client programs handle this. <br />
-----<br />
Now we will install the base Xorg packages using pacman. <br />
<br />
As root, do:<br />
pacman -S xorg-server xorg-xkb-utils xorg-xauth xorg-server-utils xorg-xinit xf86-video-vesa xf86-input-mouse xf86-input-keyboard<br />
(The old xorg group package has been removed. If it reappears, the option to use it will be given here.)<br />
Now we have the base packages we need for running the X Server. You should add the driver for your graphics card now (e.g. xf86-video-<name>). If you need a list of all '''open-source''' video drivers, do: <br />
pacman -Ss xf86-video | less<br />
If you don't know what graphics card you are using, do:<br />
lspci | grep VGA<br />
Here is a list of '''open source''' drivers, and corresponding video chipsets.<br />
*'''xf86-video-apm''' Alliance ProMotion video driver<br />
*'''xf86-video-ark''' ark video driver<br />
*'''xf86-video-ati''' ati video driver<br />
*'''xf86-video-chips''' Chips and Technologies video driver<br />
*'''xf86-video-cirrus''' Cirrus Logic video driver<br />
*'''xf86-video-dummy''' dummy video driver<br />
*'''xf86-video-fbdev''' framebuffer video driver<br />
*'''xf86-video-glint''' GLINT/Permedia video driver<br />
*'''xf86-video-i128''' Number 0 i128 video driver<br />
*'''xf86-video-i740''' Intel i740 video driver<br />
*'''xf86-video-i810''' Intel i810/i830/i9xx video drivers<br />
*'''xf86-video-imstt''' Integrated Micro Solutions Twin Turbo vidoe driver<br />
*'''xf86-video-mga''' mga video driver (Matrox Graphics Adapter)<br />
*'''xf86-video-neomagic''' neomagic video driver<br />
*'''xf86-video-nv''' nvidia nv video driver<br />
*'''xf86-video-rendition''' Rendition video driver<br />
*'''xf86-video-s3''' S3 video driver<br />
*'''xf86-video-s3virge''' S3 Virge video driver<br />
*'''xf86-video-savage''' savage video driver<br />
*'''xf86-video-siliconmotion''' siliconmotion video driver<br />
*'''xf86-video-sis''' SiS video driver<br />
*'''xf86-video-sisusb''' SiS USB video driver<br />
*'''xf86-video-tdfx''' tdfx video driver<br />
*'''xf86-video-trident''' Trident video driver<br />
*'''xf86-video-tseng''' tseng video driver<br />
*'''xf86-video-unichrome''' Unichrome video drivers<br />
*'''xf86-video-v4l''' v4l video driver<br />
*'''xf86-video-vesa''' vesa video driver<br />
*'''xf86-video-vga''' VGA 16 color video driver<br />
*'''xf86-video-via''' via video driver<br />
*'''xf86-video-vmware ''' vmware video driver<br />
*'''xf86-video-voodoo ''' voodoo video driver<br />
<br />
* Note that the '''vesa''' driver is the most generic, and should work with almost any modern video chipset. If you cannot find a suitable driver for your video chipset, vesa '''should''' work.<br />
<br />
*If you have an nVIDIA or ATI video adapter, you may wish to install the proprietary nVIDIA or ATI drivers. '''Installing proprietary video drivers is covered below''' under "Using proprietary Graphics Driver (nVIDIA, ATI)"<br />
<br />
Install the appropriate video driver for your video card/onboard video. e.g.:<br />
pacman -S xf86-video-i810<br />
(for the intel 810 chipset driver.)<br />
<br />
==Create /etc/X11/xorg.conf==<br />
=====What is /etc/X11/xorg.conf?=====<br />
/etc/X11/xorg.conf is the '''main configuration file''' for your '''X''' Window System, the foundation of your '''G'''raphical '''U'''ser '''I'''nterface. It is a plain text file ordered into sections and subsections. Important sections are ''Files, InputDevice, Monitor, Modes, Screen, Device, and ServerLayout''. Sections can appear in any order and there may be more than one section of each kind, for example, if you have more than one monitor, say a video projector and an on board LCD of a notebook. <br />
------<br />
By default, you will not have an Xorg config file, and with the newest versions of Xorg, you don't need one ''if'' the autodetection ''works satisfactorily'' and you don't need to turn on features such as aiglx and so on. ''Most people will still find that they need to generate a config file, however.''<br />
<br />
There are several ways of creating /etc/X11/xorg.conf:<br />
<br />
*The Xorg way to make a basic config file is to run<br />
Xorg -configure<br />
which will create /root/xorg.conf. Move the generated config file as appropriate, e.g.<br />
mv /root/xorg.conf.new /etc/X11/xorg.conf<br />
<br />
*Another way of making an xorg.conf without getting your hands dirty is Arch Linux's own developer tpowa's tool:<br />
hwd -xa<br />
hwd (to see the various options)<br />
<br />
*The proprietary video drivers also have tools to edit xorg.conf to configure the drivers (see below). These are <br />
aticonfig<br />
and<br />
nvidia-xconfig<br />
<br />
However, you should not be a stranger to editing the config file by hand (as this is usually needed to fix various issues from time to time):<br />
<br />
nano /etc/X11/xorg.conf<br />
<br />
Edit your /etc/X11/xorg.conf to specify your video driver. e.g.:<br />
Section "Device"<br />
Driver "i810"<br />
<br />
=====Simple baseline X test=====<br />
<br />
At this point, you should have xorg installed, with a suitable video driver and an /etc/X11/xorg.conf configuration file. If you want to test your configuration quickly, before installing a complete desktop environment, install '''xterm'''. Xterm is a very simple terminal emulator which runs in the X Server environment. Xterm will allow us to effectively test if your video driver and /etc/X11/xorg.conf are properly configured. Alternatively, you may wish to test if the X autodetection works satisfactorily, in the absence of /etc/X11/xorg.conf.<br />
pacman -S xterm<br />
Edit your /home/username/.xinitrc file, '''as normal user''', to dictate which X Server event is called upon with the 'startx' command:<br />
<br />
su yourusername<br />
<br />
nano ~/.xinitrc<br />
<br />
and add (or uncomment)<br />
<br />
exec xterm<br />
<br />
So that it looks like this:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
exec xterm<br />
# exec wmaker<br />
# exec startkde<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
<br />
(Be sure to have only one uncommented line in your ~/.xinitrc ) If you do not have ~/.xinitrc, simply create one with the above information.<br />
<br />
Start X Server as normal user, with:<br />
<br />
startx<br />
You should have an xterm session open up. You can exit the X Server with Ctrl+Alt+Backspace, or by typing "exit". If you have problems starting X, you can look for errors in the /var/log/Xorg.0.log file and on the console output of the console you started X from.<br />
<br />
Now you might want to install a graphical login manager (to avoid having to type startx everytime you start the computer) like [[GDM]] or [[KDM]], but this ''could'' wait, and advanced instructions for Xorg configuration can be found in the [[Xorg]] article.<br />
<br />
===Adjusting Keyboard Layout===<br />
You may want to change your keyboard layout. To do this edit your /etc/X11/xorg.conf and add these lines in the Input Section (keyboard0) (the example shows a German keyboard layout with no dead keys; alter this to fit your needs).<br />
Option "XkbLayout" "de"<br />
Option "XkbVariant" "nodeadkeys"<br />
<br />
===Adjusting Mouse for scroll wheel===<br />
While your mouse should be working out of the box, you may want to use your scroll wheel. Add this to your Input Section (mouse0):<br />
Option "ZAxisMapping" "4 5 6 7"<br />
<br />
===evdev===<br />
If you have a modern USB mouse with several thumb buttons and/or functions, you will most likely want to install the evdev mouse driver, which will allow you to exploit the full functionality of your mouse:<br />
<br />
pacman -S xf86-input-evdev<br />
Load the driver:<br />
modprobe evdev<br />
Find your mouse name:<br />
cat /proc/bus/input/devices | egrep "Name"<br />
Using the mouse name, configure your /etc/X11/xorg.conf InputDevice section accordingly, e.g.:<br />
Section "InputDevice"<br />
Identifier "Evdev Mouse"<br />
Driver "evdev"<br />
Option "Name" "Logitech USB-PS/2 Optical Mouse"<br />
Option "CorePointer"<br />
EndSection<br />
You must have only '''one''' "CorePointer" device specified in /etc/X11/xorg.conf, so be sure to comment out any other mouse entries until you feel safe removing the old, unused entries.<br />
<br />
Also edit the ServerLayout section to include Evdev Mouse as the CorePointer, e.g.:<br />
Section "ServerLayout"<br />
Identifier "Layout0"<br />
Screen 0 "Screen0"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
InputDevice "Evdev Mouse" "CorePointer"<br />
<br />
===Using proprietary Graphics Driver (nVIDIA, ATI)===<br />
You may choose to use the proprietary video drivers from nVIDIA or ATI. <br />
====nVIDIA Graphic Cards====<br />
The nVIDIA proprietary drivers are generally considered to be of excellent quality, and offer superior 3D performance.<br />
<br />
Before you configure your Graphics Card you will need to know which driver fits. Arch currently has 3 different drivers that each match a certain subset of Cards: <br />
<br />
'''1. nvidia-71xx''' ''for very old Cards like TNT and TNT2''<br />
<br />
'''2. nvidia-96xx''' ''slightly newer cards up to the GF 4''<br />
<br />
'''3. nvidia''' ''newest GPUs after the GF 4''<br />
<br />
Consult the nVIDIA-Homepage to see which one is for you. The difference is only for the installation; Configuration works the same with every driver.<br />
<br />
Install the appropriate nvidia driver, e.g.: <br />
pacman -S nvidia <br />
At this point, you have 3 choices as to how to proceed.<br />
<br />
*'''1.''' If you have no xorg.conf at all, or if you have an existing xorg.conf and want to '''generate a completely new one''' with the nVIDIA utility, back up the old one:<br />
mv /etc/X11/xorg.conf /etc/X11/xorg.old<br />
Then create the new /etc/X11/xorg.conf with<br />
nvidia-xconfig<br />
The nvidia-xconfig utility will usually create a very short, streamlined, easy-to-read xorg.conf<br />
<br />
It also has several options which will further specify the contents and options of the xorg.conf file.<br />
For example,<br />
nvidia-xconfig --composite --add-argb-glx-visuals<br />
<br />
For more detailed information, see nvidia-xconfig(1).<br />
<br />
*'''2.''' '''Expert Option:''' If you have an existing xorg.conf and want to keep it, edit your xorg manually as needed, and at the very least, adjust your '''Device''' Section by changing Driver "<olddrivername>" to Driver "nvidia".<br />
Section "Device"<br />
<br />
Driver "nvidia" <br />
*'''3.''' Alternatively, you may choose to keep your existing /etc/X11/xorg.conf, and run:<br />
nvidia-xconfig<br />
which will automatically '''update''' your /etc/X11/xorg.conf for use with the nVIDIA proprietary driver.<br />
<br />
Some useful tweaking options in the device section are (beware that these may not work on your system):<br />
Option "RenderAccel" "true"<br />
Option "NoLogo" "true"<br />
Option "AGPFastWrite" "true"<br />
Option "EnablePageFlip" "true"<br />
<br />
The nvidia-xconfig utility will automatically place the glx option in your xorg. If you did not use nvidia-xconfig, then you should add this to your module section:<br />
<br />
Load "glx"<br />
Double check your /etc/X11/xorg.conf to make sure your default depth, horizontal refresh, vertical refresh, and resolutions are acceptable.<br />
<br />
Logout and login.<br />
<br />
Start X server as normal user, to test your configuration:<br />
startx<br />
<br />
Advanced instructions for nvidia configuration can be found in the [[NVIDIA]] article.<br />
<br />
====ATI Graphic Cards====<br />
ATI owners have two options for drivers. If you are unsure which driver to use, please try the open-source one first. The open-source driver will suit most needs along with being generally less problematic.<br />
<br />
Install the '''proprietary''' ATI Driver with<br />
pacman -S fglrx<br />
Use the aticonfig tool to modify the xorg.conf. Note: The proprietary driver does not support [[AIGLX]]. To use [[Compiz]] or [[Beryl]] with this driver you would need to use [[XGL]].<br />
<br />
Install the '''open-source''' ATI Driver with<br />
pacman -S xf86-video-ati<br />
Currently, the performance of the open-source driver is not on par with that of the proprietary one. It also lacks TV-out, dual-link DVI support, and possibly other features. On the other hand, it supports Aiglx and has better dual-head support.<br />
<br />
Advanced instructions for ATI configuration can be found in the [[ATI | ATI wiki]].<br />
<br />
==Installing and configuring a Desktop Environment ==<br />
If you ask two people what the best Desktop Environment or Window Manager is, you will get six different answers. <br />
* If you want something full-featured and similar to Windows and Mac OSX, '''KDE''' is a good choice<br />
* If you want something more minimalist, which follows the K.I.S.S. principle more closely, '''GNOME''' is a good choice<br />
* If you have an older machine or want something lighter, '''xfce4''' is a good choice, still giving you a complete environment<br />
* If you need something even lighter, '''openbox, fluxbox or fvwm2''' may be right (not to mention all other lightweight window managers like '''windowmaker and twm''').<br />
* If you need something completely different, try '''ion, wmii, or dwm'''.<br />
<br />
===Install Fonts===<br />
At this point, you may want to install some good-looking fonts, '''before''' installing a desktop environment/window manager. Dejavu and bitstream-vera are nice font sets. For websites, you may want to have the Microsoft fonts too. Install with:<br />
pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera<br />
<br />
===GNOME===<br />
====About GNOME====<br />
The '''G'''NU '''N'''etwork '''O'''bject '''M'''odel '''E'''nvironment. The GNOME project provides two things: The GNOME desktop environment, an intuitive and attractive desktop for end-users, and the GNOME development platform, an extensive framework for building applications that integrate into the rest of the desktop.<br />
<br />
====Installation====<br />
Install GNOME with<br />
pacman -S gnome<br />
If you want a more-than-complete GNOME distribution with a lot of extras, do:<br />
pacman -S gnome-extra<br />
It's safe to choose all packages shown. <br />
=====Useful DAEMONS for GNOME=====<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. The '''hal''' daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The '''fam''' daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system. Both '''hal''' and '''fam''' make life easier for the GNOME user.<br />
<br />
You may want to install a graphical login manager. For GNOME, the '''gdm''' daemon is a good choice. Install gdm with<br />
pacman -S gdm<br />
You will almost certainly want the '''hal''' and '''fam''' daemons.<br />
<br />
Start hal and fam:<br />
/etc/rc.d/hal start<br />
<br />
/etc/rc.d/fam start<br />
<br />
Add them to your /etc/rc.conf DAEMONS section, so they will start on bootup:<br />
nano /etc/rc.conf<br />
<br />
DAEMONS=(syslog-ng network crond alsa '''hal fam gdm''')<br />
(If you prefer to log into the console and manually start X in the 'Slackware tradition', leave out gdm.)<br />
<br />
====~/.xinitrc====<br />
<br />
This file controls what occurs when you type 'startx'.<br />
<br />
Edit your /home/username/.xinitrc to utilize GNOME:<br />
<br />
nano ~/.xinitrc<br />
<br />
Uncomment the 'exec gnome-session' line so that it looks like this:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
#exec xterm<br />
#exec wmaker<br />
# exec startkde<br />
exec gnome-session<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
<br />
If you do not have a ~/.xinitrc file, simply create it with the above information. Remember, you must have only one uncommented line in your ~/.xinitrc. <br />
<br />
Switch to normal user:<br />
su username<br />
<br />
And test it with:<br />
startx<br />
<br />
You may want to install a terminal and an editor. I would recommend gnome-terminal (part of the group gnome-extra) and geany:<br />
pacman -S geany gnome-terminal<br />
<br />
Advanced instructions for installing and configuring GNOME can be found in the [[Gnome]] article.<br />
<br />
====Eye Candy====<br />
You may find the default GNOME theme and icons not very attractive. A nice gtk theme is murrine. Install it with<br />
pacman -S gtk-engine-murrine<br />
and select it with System->Preferences->Theme. You can find more themes, icons, and wallpaper at [http://www.gnome-look.org Gnome Look].<br />
<br />
===KDE===<br />
====About KDE====<br />
The '''K''' '''D'''esktop '''E'''nvironment. KDE is a powerful Free Software graphical desktop environment for Linux and Unix workstations. It combines ease of use, contemporary functionality, and outstanding graphical design with the technological superiority of UNIX-like operating systems.<br />
<br />
====Installation====<br />
Arch offers several versions of kde: '''kde, kdebase, and KDEmod'''. Choose '''one''' of the following, and continue below with '''"Useful KDE DAEMONS"''': <br />
<br />
'''1.)''' Package '''kde''' is the complete, vanilla KDE, ~300MB.<br />
pacman -S kde<br />
'''2.)''' Package '''kdebase''' is a slimmed-down version with less applications, ~80MB.<br />
pacman -S kdebase<br />
'''3.)''' Lastly, '''KDEmod''' is an Arch Linux exclusive, community-driven system which is modified for extreme performance and modularity. The KDEmod project website can be found at [http://kdemod.ath.cx/ http://kdemod.ath.cx/]. KDEmod is extremely fast, lightweight and responsive, with a pleasing, customized theme. <br />
<br />
To install KDEmod in 5 easy steps, just follow these installation instructions...<br />
Note: Before you start, please remember to read all of the install messages. They are fairly comprehensive and should solve any upcoming questions after the installation. If you cant scroll back to see all messages, just take a look into /var/log/pacman.log<br />
<br />
*1. Add the kdemod repo to your /etc/pacman.conf:<br />
nano /etc/pacman.conf<br />
Add one of these entries at the top of your server list:<br />
[kdemod]<br />
Server = http://kdemod.ath.cx/repo/current/i686<br />
for 32 bit Arch, or<br />
[kdemod]<br />
Server = http://kdemod.ath.cx/repo/current/x86_64<br />
for 64 bit Arch.<br />
<br />
*2. You must also activate the [community] repository in /etc/pacman.conf because KDEmod needs some packages from this repository. Make sure the following lines are uncommented:<br />
[community]<br />
Include = /etc/pacman.d/community<br />
<br />
<br />
*3. Update your package database with pacman -Syu. Now you can choose between two installations:<br />
<br />
pacman -S kdemod ''- installs a light base system''<br />
pacman -S kdemod-complete ''- installs the full KDE desktop''<br />
<br />
If you encounter any errors or conflicts at this step, check pacmans output, and if there are some unsolvable problems, tell us about them at the forums.<br />
*4. Install your localization. Take a look at the list of packages or simply do a pacman -Ss kdemod-kde-i18n to see which of them are already included.<br />
<br />
*5. Install all the extra apps you want. You can check out all available KDEmod packages by entering pacman -Sl kdemod<br />
<br />
====Useful KDE DAEMONS====<br />
<br />
KDE will require the '''hal''' ('''H'''ardware '''A'''bstraction '''L'''ayer) and '''fam''' ('''F'''ile '''A'''lteration '''M'''onitor) daemons. The '''kdm''' daemon is the '''K''' '''D'''isplay '''M'''anager, which provides a '''graphical login''', if desired.<br />
<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services. The hal daemon, among other things, will automate the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The fam daemon will allow real-time representation of file alterations in the GUI, allowing instant access to recently installed programs, or changes in the file system.. Both '''hal''' and '''fam''' make life easier for the KDE user, and are installed when you install KDE.<br />
<br />
Start hal and fam:<br />
<br />
/etc/rc.d/hal start<br />
<br />
/etc/rc.d/fam start<br />
<br />
Edit your DAEMONS section in /etc/rc.conf:<br />
nano /etc/rc.conf<br />
Add '''hal''' and '''fam''' to your DAEMONS section, to start them on bootup. If you prefer a graphical login, add '''kdm''' as well: <br />
DAEMONS=(syslog-ng network crond alsa '''hal fam kdm''')<br />
(If you prefer to log into the '''console''' and manually start X in the 'Slackware tradition', leave out kdm.)<br />
<br />
=====~/.xinitrc=====<br />
This file controls what occurs when you type 'startx'.<br />
<br />
Edit your /home/username/.xinitrc to utilize KDE:<br />
nano ~/.xinitrc<br />
Uncomment the 'exec startkde' line so that it looks like this:<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
#exec xterm<br />
#exec wmaker<br />
exec startkde<br />
# exec gnome-session<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
If you do not have a ~/.xinitrc file, simply create it with the above information. Remember, you must have only '''one''' uncommented line in your ~/.xinitrc.<br />
<br />
Switch to your normal user:<br />
su username<br />
Now try starting your X Server:<br />
startx<br />
<br />
Congratulations! Welcome to your KDE desktop environment on your new Arch Linux system! You may wish to continue by viewing [[Post Installation Tips]], or the rest of the information below.<br />
Advanced instructions for installing and configuring KDE can be found in the [[KDE]] article.<br />
<br />
===Xfce===<br />
====About Xfce====<br />
Xfce is a Desktop Environment, like GNOME or KDE. It contains a suite of apps like a root window app, window manager, file manager, panel, etc. Xfce is written using the GTK2 toolkit and contains its own development environment (libraries, daemons, etc) similar to other big DEs. Unlike GNOME or KDE, Xfce is lightweight and designed more around CDE than Windows or Mac. It has a much slower development cycle, but is very stable and extremely fast. Xfce is great for older hardware.<br />
<br />
====Installation====<br />
Install xfce with<br />
pacman -S xfce4 xfce4-goodies <br />
<br />
If you use kdm or gdm a new xfce session should have appeared. Alternatively, you can use<br />
startxfce4<br />
<br />
Advanced instructions for installing and configuring Xfce can be found in the [[Xfce]] article.<br />
<br />
===*box===<br />
====Fluxbox====<br />
Fluxbox © is yet another windowmanager for X.<br />
It's based on the Blackbox 0.61.1 code. Fluxbox looks like blackbox and handles styles, colors, window placement and similar things exactly like blackbox (100% theme/style compability).<br />
<br />
Install Fluxbox using <br />
pacman -S fluxbox fluxconf<br />
<br />
If you use gdm/kdm a new fluxbox session will be automatically added. Otherwise, you should modify your user's .xinitrc and add this to it:<br />
exec startfluxbox <br />
<br />
More information is available in the [[Fluxbox]] article.<br />
<br />
====Openbox====<br />
Openbox is a standards compliant, fast, light-weight, extensible window manager.<br />
<br />
Openbox works with your applications, and makes your desktop easier to manage. This is because the approach to its development was the opposite of what seems to be the general case for window managers. Openbox was written first to comply with standards and to work properly. Only when that was in place did the team turn to the visual interface.<br />
<br />
Openbox is fully functional as a stand-alone working environment, or can be used as a drop-in replacement for the default window manager in the GNOME or KDE desktop environments. <br />
<br />
Install openbox using<br />
pacman -S openbox obconf obmenu<br />
<br />
Once openbox is installed you will get a message to move menu.xml & rc.xml to ~/.config/openbox/ in your home directory:<br />
<br />
mkdir -p ~/.config/openbox/<br />
cp /etc/xdg/openbox/rc.xml ~/.config/openbox/<br />
cp /etc/xdg/openbox/menu.xml ~/.config/openbox/<br />
<br />
In the file "rc.xml" you can change various settings for Openbox (or you can use OBconf). In "menu.xml" you can change your right-click menu.<br />
<br />
To be able to log into openbox you can either go via graphical login using KDM/GDM or startx, in which case you will need to edit your ~/.xinitrc (as user) and add the following:<br />
<br />
exec openbox<br />
<br />
For KDM there is nothing left to do; openbox is listed in the sessions menu in KDM.<br />
<br />
Useful programs for openbox are:<br />
* PyPanel or LXpanel if you want a panel<br />
* feh if you want to set the background<br />
* ROX if you want a simple file manager and desktop icons<br />
<br />
More information is available in the [[Openbox]] article.<br />
<br />
===fvwm2===<br />
FVWM is an extremely powerful ICCCM-compliant multiple virtual desktop window manager for the X Window system. Development is active, and support is excellent. <br />
<br />
Install fvwm2 with<br />
pacman -S fvwm <br />
<br />
fvwm will automatically be listed in kdm/gdm in the sessions menu. Otherwise, add <br />
exec fvwm <br />
<br />
to your user's .xinitrc.<br />
<br />
Note that this stable version of fvwm is a few years old. If you want a more recent version of fvwm, there is a fvwm-devel package in the unstable repo.<br />
<br />
==HAL==<br />
Since you have now installed a desktop environment now would be a good time to also install HAL. HAL allows plug-and-play for your mobile phone, your iPod, your external HD's, etc. It will mount the device and make a nice visual icon on your desktop and/or in 'My Computer', allowing you to access the device after you have plugged it in instead of having to manually configure the /etc/fstab file or udev rules for each and every new device.<br />
<br />
KDE, GNOME and XFCE uses HAL.<br />
<br />
Refer to this article to install: [http://wiki.archlinux.org/index.php/HAL HAL]<br />
wikipedia: [http://en.wikipedia.org/wiki/HAL_(software) 1]<br />
<br />
==Useful Applications==<br />
This section will never be complete. It just shows some good applications for the everyday user. <br />
===Internet===<br />
<br />
=====Firefox=====<br />
The ever-popular Firefox web browser is available through pacman. Install with:<br />
<br />
pacman -S firefox<br />
Be sure and install 'flashplugin', 'mplayer', 'mplayer-plugin', and the 'codecs' packages for a complete web experience:<br />
pacman -S flashplugin mplayer mplayer-plugin codecs<br />
(The codecs package contains codecs for Quicktime and Realplayer content.)<br />
<br />
Thunderbird is useful for managing your emails. If you are using GNOME you may want to take a look at Epiphany and Evolution; if you are using KDE Konqueror and KMail could be your choice. If you want something completely different you can still use Opera. Finally, if you are working on the system console - or in a terminal session - you could use various text-based browsers like ELinks, Links and Lynx, and manage your emails with [[Mutt]]. Pidgin (previously known as Gaim) and Kopete are good instant messengers for GNOME and KDE, respectively. PSI and Gajim are perfect if you are using only Jabber or Google Talk.<br />
<br />
===Office===<br />
OpenOffice is a complete office suite (similar to Microsoft Office). Abiword is a good, small alternative word processor, and Gnumeric an Excel replacement for the GNOME desktop. KOffice is a complete office suite for the KDE Desktop. GIMP (or GIMPShop) is a pixel-based graphics program (similar to Adobe Photoshop), while Inkscape is a vector-based graphics program (like Adobe Illustrator). And, of course, Arch comes with a full set of LaTeX Programs.<br />
<br />
==Multimedia ==<br />
<br />
<br />
===Video Player===<br />
====VLC====<br />
VLC Player is a multimedia player for Linux. To install it, simply type the code below.<br />
<br />
pacman -S vlc<br />
<br />
(TODO) Instructions for VLC mozilla plug-in<br />
<br />
====Mplayer====<br />
MPlayer is a multimedia player for Linux. To install it, simply type the code below.<br />
<br />
pacman -S mplayer<br />
<br />
It also has a Mozilla plug-in for videos and streams embedded in web pages. To install it, simply type the code below.<br />
<br />
pacman -S mplayer-plugin<br />
<br />
If you use KDE, KMplayer is a better choice. It comes with a plug-in for videos and streams embedded in web pages, which works with Konqueror. To install it, simply type the code below.<br />
<br />
pacman -S kmplayer<br />
<br />
(TODO) GMPlayer instructions<br />
<br />
====GNOME====<br />
=====Totem=====<br />
[http://www.gnome.org/projects/totem/ Totem] is the official movie player of the GNOME desktop environment based on xine-lib or GStreamer (gstreamer is the default which installs with the arch totem package). It features a playlist, a full-screen mode, seek and volume controls, as well as keyboard navigation.<br />
It comes with added functionality such as:<br />
<br />
* Video thumbnailer for the file manager<br />
* Nautilus properties tab<br />
* Epiphany / Mozilla (Firefox) plugin to view movies inside your browser <br />
* Webcam utility (in development)<br />
<br />
Totem-xine is still the better choice if you want to watch DVDs.<br />
<br />
Totem is part of the gnome-extra group; the Totem webbrowser plugin isn't.<br />
<br />
To install separately:<br />
pacman -S totem<br />
<br />
To install the Totem webbrowser plugin:<br />
pacman -S totem-plugin<br />
<br />
====KDE====<br />
=====Kaffeine=====<br />
Kaffeine is a good option for KDE users. To install it, simply type the code below.<br />
<br />
pacman -S kaffeine<br />
<br />
===Audio Player===<br />
====Gnome/Xfce====<br />
=====Exaile=====<br />
[[Exaile]] is a music player written in Python that makes use of the GTK+ toolkit.<br />
=====Rhythmbox=====<br />
[http://www.gnome.org/projects/rhythmbox/ Rhythmbox] is an integrated music management application, originally inspired by Apple's iTunes. It is free software, designed to work well under the GNOME Desktop, and based on the powerful GStreamer media framework.<br />
<br />
Rhythmbox has a number of features, including:<br />
<br />
* Easy-to-use music browser<br />
* Searching and sorting<br />
* Comprehensive audio format support through GStreamer<br />
* Internet radio support<br />
* Playlists<br />
<br />
To install rhythmbox:<br />
pacman -S rhythmbox<br />
<br />
Other good audio players are: Banshee, Quodlibet, and Listen. See [http://gnomefiles.org/ Gnomefiles] to compare them.<br />
<br />
====KDE====<br />
=====Amarok=====<br />
[http://amarok.kde.org/ Amarok] is one of the best audio players and music library systems available for KDE. To install it, simply type the code below.<br />
<br />
pacman -S amarok-base<br />
<br />
====Console====<br />
Moc is a ncurses-based audio player for the console; another good choice is mpd.<br />
<br />
Another excellent choice is cmus[http://freshmeat.net/projects/cmus/].<br />
<br />
====Other X-based====<br />
(TODO) Xmms, audacious, bmpx.<br />
<br />
===Codecs and other multimedia content types===<br />
====DVD====<br />
You can use totem-xine, mplayer or kaffeine (just to name three of the big ones) to watch DVDs. The only thing you may miss is libdvdcss. Beware that using it may be illegal in some countries.<br />
<br />
====Flash====<br />
Install the flash plugin using<br />
pacman -S flashplugin<br />
to enable Macromedia (now Adobe) Flash in your browser.<br />
<br />
====Quicktime====<br />
Quicktime codecs are contained in the codecs package. Just type<br />
pacman -S codecs<br />
to install them.<br />
====Realplayer====<br />
The codec for Realplayer 9 is contained in the codecs package. Just type<br />
pacman -S codecs<br />
to install them. Realplayer 10 is available as a binary package for Linux. You can get it from AUR [http://aur.archlinux.org/packages.php?do_Details=1&ID=1590&O=0&L=0&C=0&K=realplay&SB=&SO=&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd here].<br />
<br />
===CD and DVD Burning===<br />
====GNOME====<br />
=====Brasero=====<br />
[http://www.gnome.org/projects/brasero/ Brasero] is an application that burns CDs/DVDs for the GNOME Desktop. It is designed to be as simple as possible and has some unique features to enable users to create their discs easily and quickly.<br />
<br />
To install:<br />
pacman -S brasero<br />
<br />
====KDE====<br />
=====K3b=====<br />
K3b - '''B'''urn, '''B'''aby, '''B'''urn in '''K'''DE<br />
-----<br />
[http://k3b.plainblack.com/ K3B] - CD/DVD burning application for Linux - optimized for KDE - licensed under the GPL.<br />
To install:<br />
pacman -S k3b<br />
<br />
<br />
<br />
<br />
(Todo) cdrecord, graveman...<br />
<br />
<br />
<br />
<br />
Most CD burners are wrappers for cdrecord:<br />
<br />
pacman -S cdrkit<br />
<br />
If you install packages for CD/DVD burning applications like Brasero or K3B it also installs the CD/DVD burning library for it, like libburn or cdrkit.<br />
<br />
A good command-line DVD-burning tool is growisofs:<br />
<br />
pacman -S dvd+rw-tools<br />
<br />
===TV-Cards===<br />
There are several things to do if you want to watch TV under (Arch) Linux. The most important task is to find out which chip your tuner is using. However, quite a bunch is supported. Be sure to check at a Hardware Database to be sure (e.g. [http://en.opensuse.org/HCL/TV_Cards]). Once you know your Model, there are just a few steps ahead to get you going.<br />
<br />
In most cases, you will need to use the bttv-drivers (other drivers exist, see [http://linux.bytesex.org/v4l2/drivers.html]) together with the I2C-modules. Configuring those is the hardest task. If you are lucky, a<br />
modprobe bttv<br />
will autodetect the card (check dmesg for results). In that case, you need only to install an application to watch TV. We will look at that later, though.<br />
If the autodetection did not work, you will need to check the file CARDLIST, which is included in the tarball of bttv[http://dl.bytesex.org/releases/video4linux/] to find out the right parameters for your card. A PV951 without radio support would need this line:<br />
modprobe bttv card=42 radio=0<br />
Some cards need the following line to produce sound:<br />
modprobe tvaudio<br />
However, that varies. So just try it out. Some other cards demand the following line:<br />
modprobe tuner<br />
This is object to trial-and-error, too.<br />
<br />
TODO: clarify the installation-procedure<br />
<br />
To actually watch TV, install the xawtv-package with<br />
pacman -S xawtv <br />
and read its manpage.<br />
<br />
TODO: clarify some possible problems and procedures. Introduction to XAWTV on another page?<br />
<br />
===Digital Cameras===<br />
Most newer digital cameras are supported as USB mass storage devices, which means that you can simply plug it in and copy the images. Older cameras may use the PTP (Picture Transfer Protocol) which requires a "special driver". gPhoto2 provides this driver and allows a shell-based transfer of the images; digikam (for KDE) and gthumb (for GNOME, gtkam would be another choice) use this driver and offer a nice GUI.<br />
<br />
===USB Memory Sticks / Hard Disks===<br />
USB Memory Sticks and hard disks are supported out of the box with the USB mass storage device driver and will appear as a new SCSI device (/dev/sdX). If you are using KDE or GNOME you should use dbus and hal (add them to your daemons in /etc/rc.conf), and they will be automatically mounted. If you use a different Desktop Environment you may have a look at ivman.<br />
<br />
==Maintaining the system==<br />
===Pacman===<br />
[[Pacman]] is both a binary and source package manager which is able to download, install, and upgrade packages from both remote and local repositories with full dependency handling, and has easy-to-understand tools for crafting your own packages too.<br />
<br />
A more-detailed description of Pacman can be found in [[Pacman|its article]].<br />
<br />
==== Useful commands ====<br />
<br />
To synchronize and update the local packages database with the remote repositories (it is a good idea to do this before installing and upgrading packages):<br />
pacman -Sy<br />
<br />
To '''upgrade''' all packages on the system:<br />
pacman -Su<br />
<br />
To sync, update, and '''upgrade''' all the packages on the system with one command:<br />
pacman -Syu<br />
<br />
To install or upgrade a single package or list of packages (including dependencies):<br />
pacman -S packageA packageB<br />
<br />
You can also sync, update the package database, and install packages in one command:<br />
pacman -Sy packageA packageB<br />
<br />
To remove a single package, leaving all of its dependencies installed:<br />
pacman -R package<br />
<br />
To remove a package and all of the package's dependencies which aren't used by any other installed package:<br />
pacman -Rs package<br />
<br />
To remove all of the package's dependencies now unneeded and do not make any backup of settings:<br />
pacman -Rsn package<br />
<br />
To search the remote (repo) package database for a list of packages matching a given keyword:<br />
pacman -Ss keyword<br />
<br />
To list all packages on your system<br />
pacman -Q<br />
<br />
To search (query) the local (your machine) package database for a given package:<br />
pacman -Q package <br />
<br />
To search (query) the local (your machine) package database for a given package and list all pertinent information:<br />
pacman -Qi package<br />
<br />
To defragment pacman's cache database and optimize for speed:<br />
pacman-optimize<br />
<br />
To count how many packages are currently on your system:<br />
pacman -Q | wc -l<br />
<br />
To install a package compiled from source using ABS and makepkg:<br />
pacman -U packagename.pkg.tar.gz<br />
<br />
Note: There are countless additional pacman functions and commands. Try man pacman and consult the [[pacman]] wiki entries.<br />
<br />
==Polishing & Further information==<br />
If after you have read this you want to do a bit of polishing, head to [[Post Installation Tips]]. For further information and support you can go to the [http://www.archlinux.org homepage], search the wiki, the [http://bbs.archlinux.org forums], the [http://wiki.archlinux.org/index.php/ArchChannel IRC channel], and the [http://www.archlinux.org/mailman/listinfo/ mailing lists].</div>
Potamota
https://wiki.archlinux.org/index.php?title=Category:System_administration_(Bahasa_Indonesia)&diff=30271
Category:System administration (Bahasa Indonesia)
2007-10-03T23:17:29Z
<p>Potamota: New page: Anda sudah menginstal arch dan sekarang anda ingin mengkonfigurasinya sesuai kebutuhan.</p>
<hr />
<div>Anda sudah menginstal arch dan sekarang anda ingin mengkonfigurasinya sesuai kebutuhan.</div>
Potamota
https://wiki.archlinux.org/index.php?title=Allow_users_to_shutdown_(Bahasa_Indonesia)&diff=30269
Allow users to shutdown (Bahasa Indonesia)
2007-10-03T23:03:36Z
<p>Potamota: </p>
<hr />
<div>[[Category:Keamanan (Indonesia)]]<br />
[[Category:HOWTOs (Indonesia)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Allow_users_to_shutdown}}<br />
{{i18n_entry|Русский|Как разрешить пользователям выключать компьютер}}<br />
{{i18n_entry|Українська|Як дозволити користувачу вимкнути комп'ютер}}<br />
{{i18n_entry|Indonesia|Shutdown sebagai users(Indonesia)}}<br />
{{i18n_links_end}}<br />
Jika anda ingin mengijinkan penguna(user) untuk shutdown atau reboot sistem dan anda tidak menggunakan DE yang mendukung HAL ataupun karena memang tidak ingin mengunakan HAL ada beberapa cara yang dapat anda lakukan antara lain: <br />
<br />
-----<br />
Dengan merubah ijin permisi dari perintah halt, reboot tidak perlu diubah karena merupakan ''symlink'' ke halt. Sebagai root lakukan perintah di bawah ini:<br />
<br />
<pre><br />
chmod +s /sbin/halt<br />
</pre><br />
<br />
<b>Topic:</b> http://bbs.archlinux.org/viewtopic.php?t=2787<br />
-----<br />
Cara lain dengan menggunakan <code>sudo</code>. Pertama-tama install sudo:<br />
<br />
<pre><br />
# pacman -Sy sudo<br />
</pre><br />
<br />
Setelah itu sebagai root tambahkan baris dibawah ini di file <code>/etc/sudoers</code> dengan menggunakan <code>visudo</code> (ketikkan visudo lalu file akan terbuka, jangan mengedit secara manual!). Rubah ''pengguna'' dengan nama user yang ingin anda ijinkan dan ''hostname'' dengan nama hostname komputer anda.<br />
<br />
<pre><br />
pengguna hostname = NOPASSWD: /sbin/shutdown -h now<br />
pengguna hostname = NOPASSWD: /sbin/reboot<br />
<br />
contoh:<br />
dudung localhost = NOPASSWD: /sbin/shutdown -h now<br />
dudung localhost = NOPASSWD: /sbin/reboot<br />
</pre><br />
<br />
Atau apabila anda ingin memberikan ijin ini pada semua pengguna dalam group tertentu rubah format diatas menjadi seperti ini(sesuaikan ''namagroup'' dengan group yang anda inginkan).<br />
<br />
<pre><br />
%namagroup hostname = NOPASSWD: /sbin/shutdown -h now<br />
%namagroup hostname = NOPASSWD: /sbin/reboot<br />
</pre><br />
<br />
Sekarang penguna dapat shutdown dengan perintah <code>sudo shutdown -h now</code>, dan reboot dengan <code>reboot</code>.<br />
----<br />
Apabila anda menggunakan XFCE setelah install sudo. Tambahkan baris ini ke <code>/etc/sudoers</code> dengan perintah <code>visudo</code>. Untuk semua user dalam group users(sesuaikan bila group yang anda inginkan berbeda):<br />
<pre><br />
%users hostname=NOPASSWD:/usr/lib/xfce4/xfsm-shutdown-helper<br />
</pre><br />
Sesuaikan ''hostname'' dengan hostname anda.<br />
<br />
Untuk satu user saja(sesuikan user dengan user anda):<br />
<pre><br />
user hostname=NOPASSWD:/usr/lib/xfce4/xfsm-shutdown-helper<br />
</pre><br />
Sesuikan ''hostname'' dengan hostname anda.<br />
<br />
Hal diatas akan mengaktifkan pilihan "reboot" dan "turn off" pada dialog logout XFCE.</div>
Potamota
https://wiki.archlinux.org/index.php?title=Allow_users_to_shutdown_(Bahasa_Indonesia)&diff=30268
Allow users to shutdown (Bahasa Indonesia)
2007-10-03T22:59:55Z
<p>Potamota: New page: Category:Keamanan (Indonesia) Category:HOWTOs (Indonesia) {{i18n_links_start}} {{i18n_entry|English|Allow_users_to_shutdown}} {{i18n_entry|Русский|Как разрешить ...</p>
<hr />
<div>[[Category:Keamanan (Indonesia)]]<br />
[[Category:HOWTOs (Indonesia)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Allow_users_to_shutdown}}<br />
{{i18n_entry|Русский|Как разрешить пользователям выключать компьютер}}<br />
{{i18n_entry|Українська|Як дозволити користувачу вимкнути комп'ютер}}<br />
{{i18n_links_end}}<br />
Jika anda ingin mengijinkan penguna(user) untuk shutdown atau reboot sistem dan anda tidak menggunakan DE yang mendukung HAL ataupun karena memang tidak ingin mengunakan HAL ada beberapa cara yang dapat anda lakukan antara lain: <br />
<br />
-----<br />
Dengan merubah ijin permisi dari perintah halt, reboot tidak perlu diubah karena merupakan ''symlink'' ke halt. Sebagai root lakukan perintah di bawah ini:<br />
<br />
<pre><br />
chmod +s /sbin/halt<br />
</pre><br />
<br />
<b>Topic:</b> http://bbs.archlinux.org/viewtopic.php?t=2787<br />
-----<br />
Cara lain dengan menggunakan <code>sudo</code>. Pertama-tama install sudo:<br />
<br />
<pre><br />
# pacman -Sy sudo<br />
</pre><br />
<br />
Setelah itu sebagai root tambahkan baris dibawah ini di file <code>/etc/sudoers</code> dengan menggunakan <code>visudo</code> (ketikkan visudo lalu file akan terbuka, jangan mengedit secara manual!). Rubah ''pengguna'' dengan nama user yang ingin anda ijinkan dan ''hostname'' dengan nama hostname komputer anda.<br />
<br />
<pre><br />
pengguna hostname = NOPASSWD: /sbin/shutdown -h now<br />
pengguna hostname = NOPASSWD: /sbin/reboot<br />
<br />
contoh:<br />
dudung localhost = NOPASSWD: /sbin/shutdown -h now<br />
dudung localhost = NOPASSWD: /sbin/reboot<br />
</pre><br />
<br />
Atau apabila anda ingin memberikan ijin ini pada semua pengguna dalam group tertentu rubah format diatas menjadi seperti ini(sesuaikan ''namagroup'' dengan group yang anda inginkan).<br />
<br />
<pre><br />
%namagroup hostname = NOPASSWD: /sbin/shutdown -h now<br />
%namagroup hostname = NOPASSWD: /sbin/reboot<br />
</pre><br />
<br />
Sekarang penguna dapat shutdown dengan perintah <code>sudo shutdown -h now</code>, dan reboot dengan <code>reboot</code>.<br />
----<br />
Apabila anda menggunakan XFCE setelah install sudo. Tambahkan baris ini ke <code>/etc/sudoers</code> dengan perintah <code>visudo</code>. Untuk semua user dalam group users(sesuaikan bila group yang anda inginkan berbeda):<br />
<pre><br />
%users hostname=NOPASSWD:/usr/lib/xfce4/xfsm-shutdown-helper<br />
</pre><br />
Sesuaikan ''hostname'' dengan hostname anda.<br />
<br />
Untuk satu user saja(sesuikan user dengan user anda):<br />
<pre><br />
user hostname=NOPASSWD:/usr/lib/xfce4/xfsm-shutdown-helper<br />
</pre><br />
Sesuikan ''hostname'' dengan hostname anda.<br />
<br />
Hal diatas akan mengaktifkan pilihan "reboot" dan "turn off" pada dialog logout XFCE.</div>
Potamota
https://wiki.archlinux.org/index.php?title=Table_of_contents_(Bahasa_Indonesia)&diff=30245
Table of contents (Bahasa Indonesia)
2007-10-02T16:53:13Z
<p>Potamota: New page: Category:ArchWiki Tools (Indonesia) {{translateme}} {{i18n_links_start}} {{i18n_entry|Česky|Table of Contents (Česky)}} {{i18n_entry|Deutsch|Table of Contents (Deutsch)}} {{i18n_en...</p>
<hr />
<div>[[Category:ArchWiki Tools (Indonesia)]]<br />
<br />
{{translateme}}<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Česky|Table of Contents (Česky)}}<br />
{{i18n_entry|Deutsch|Table of Contents (Deutsch)}}<br />
{{i18n_entry|English|Table of Contents (English)}}<br />
{{i18n_entry|Français|Table of Contents (Français)}}<br />
{{i18n_entry|Italiano|Table of Contents (Italiano)}}<br />
{{i18n_entry|Lietuviškai|Table of Contents (Lietuviškai)}}<br />
{{i18n_entry|Indonesia|Daftar Isi (Indonesia)}}<br />
{{i18n_entry|Nederlands|Table of Contents (Nederlands)}}<br />
{{i18n_entry|Polski|Table of Contents (Polski)}}<br />
{{i18n_entry|Português do Brasil|Table of Contents (Português do Brasil)}}<br />
{{i18n_entry|Português|Table of Contents (Português)}}<br />
{{i18n_entry|Русский|Table of Contents (Русский)}}<br />
{{i18n_entry|Slovensky|Table of Contents (Slovensky)}}<br />
{{i18n_entry|ไทย|Table of Contents (ไทย)}}<br />
{{i18n_entry|Українська|Table of Contents (Українська)}}<br />
{{i18n_entry|简体中文|Table of Contents (简体中文)}}<br />
{{i18n_entry|繁體中文|Table of Contents (繁體中文)}}<br />
{{i18n_links_end}}<br />
<br />
*[[:Category: Tentang Arch (Indonesia)|Tentang Arch]]<br />
**[[:Category:Events (Indonesia)|Events]]<br />
*[[:Category: Mendapatkan dan Instalasi Arch (Indonesia)|Mendapatkan dan Instalasi Arch]]<br />
*[[:Category: Administrasi Sistem (Indonesia)|Administrasi Sistem]]<br />
**[[:Category:Kustomisasi (Indonesia)|Kustomisasi]]<br />
***[[:Category:kernel Arch (Indonesia)|Kernel Arch]]<br />
**[[:Category:Hardware (Indonesia)|Hardware]]<br />
***[[:Category:Arch64 (Indonesia)|Arch64]]<br />
***[[:Category:CPU (Indonesia)|CPU]]<br />
***[[:Category:Komunikasi dan jaringan (Indonesia)|Komunikasi dan jaringan]]<br />
***[[:Category:Grafik (Indonesia)|Grafik]]<br />
***[[:Category:Hardware detection and troubleshooting (Indonesia)|Deteksi dan pemecahan masalah hardware]]<br />
***[[:Category:I586 (Indonesia)|I586]]<br />
***[[:Category:Imaging (Indonesia)|Imaging]]<br />
***[[:Category:Alat input (Indonesia)|Alat input]]<br />
***[[:Category:Laptops (Indonesia)|Laptops]]<br />
***[[:Category:Mainboards dan BIOS (Indonesia)|Mainboards dan BIOS]]<br />
***[[:Category:Perangkat Optik (Indonesia)|Perangkat optik]]<br />
***[[:Category:Hardware lain (Indonesia)|Hardware lain]]<br />
***[[:Category:PowerPC (Indonesia)|PowerPC]]<br />
***[[:Category:Printers (Indonesia)|Printers]]<br />
***[[:Category:Suara (Indonesia)|Suara]]<br />
***[[:Category:Penyimpanan (Indonesia)|Penyimpanan]]<br />
**[[:Category:Jaringan (Indonesia)|Jaringan]]<br />
**[[:Category:Keamanan (Indonesia)|Keamanan]]<br />
**[[:Category:Software (Indonesia)|Software]]<br />
***[[:Category:Boot process (Indonesia)|Boot process]]<br />
***[[:Category:Command shells (Indonesia)|Command shells]]<br />
***[[:Category:Daemons dan system services (Indonesia)|Daemons dan system services]]<br />
***[[:Category:Desktop environments (Indonesia)|Desktop environments]]<br />
***[[:Category:Display managers (Indonesia)|Display managers]]<br />
***[[:Category:File systems (Indonesia)|File systems]]<br />
***[[:Category:Fonts (Indonesia)|Fonts]]<br />
***[[:Category:Hardware detection and troubleshooting (Indonesia)|Hardware detection and troubleshooting]]<br />
***[[:Category:Package management (Indonesia)|Package management]]<br />
***[[:Category:Power management (Indonesia)|Power management]]<br />
***[[:Category:X Server (Indonesia)|X Server]]<br />
*[[:Category: Desktop user's guide (Indonesia)|Desktop user's guide]]<br />
**[[:Category:Audio/Video (Indonesia)|Audio/Video]]<br />
**[[:Category:Development (Indonesia)|Development]]<br />
**[[:Category:Pendidikan (Indonesia)|Pendidikan]]<br />
**[[:Category:Emulators (Indonesia)|Emulators]]<br />
***[[:Category:Wine (Indonesia)|Wine]]<br />
**[[:Category:Eye candy (Indonesia)|Eye candy]]<br />
**[[:Category:Permainan dan hiburan (Indonesia)|Permainan and hiburan]]<br />
**[[:Category:Graphics and DTP (Indonesia)|Graphics and DTP]]<br />
**[[:Category:Internationalization (Indonesia)|Internationalization]]<br />
**[[:Category:Internet dan Email (Indonesia)|Internet dan Email]]<br />
**[[:Category:Office (Indonesia)|Office]]<br />
**[[:Category:Other desktop user's resources (Indonesia)|Other desktop user's resources]]<br />
**[[:Category:Scripts (Indonesia)|Scripts]]<br />
**[[:Category:Utilities (Indonesia)|Utilities]]<br />
*[[:Category:System recovery (Indonesia)|System recovery]]<br />
*[[:Category: Arch development (Indonesia)|Arch development]]<br />
**[[:Category:Package development (Indonesia)|Package development]]<br />
*[[:Category: Live Arch systems (Indonesia)|Live Arch systems]]</div>
Potamota