https://wiki.archlinux.org/api.php?action=feedcontributions&user=Cantabile&feedformat=atom
ArchWiki - User contributions [en]
2024-03-29T06:10:39Z
User contributions
MediaWiki 1.41.0
https://wiki.archlinux.org/index.php?title=Talk:USB_flash_installation_medium&diff=291330
Talk:USB flash installation medium
2014-01-02T09:47:19Z
<p>Cantabile: /* Does `sync` have any effect? */ new section</p>
<hr />
<div>== About making the installation media without overwriting ==<br />
I'm not totally sure if I misunderstood something, but I had to change the path of the entries of the *.cfg files. For instance:<br />
<br />
INCLUDE boot/syslinux/archiso_sys.cfg<br />
<br />
became:<br />
<br />
INCLUDE syslinux/archiso_sys.cfg<br />
<br />
It was the only way it worked with the unofficial ISO x86_64 image of march 13th, 2012. Looks like the syslinux command described in the page doesn't get the path as it should. <br />
<br />
I edited all of the .cfg files, but probably only editing this ones should have been enough:<br />
<br />
archiso.cfg<br />
archiso_head.cfg<br />
archiso_sys_inc.cfg<br />
<br />
I hope it could be useful to somebody, because I spend some time with this (I even thought that was a problem with the hardware). I think it could be possible to make a simple script (or give some command lines) to patch the files once they are copied into the USB and run syslinux.<br />
<br />
Thanks !!<br />
:I cannot find that this is still relevant to the article as it now exists. I am striking it out as it looks like it could be good to remove. [[User:AdamT|AdamT]] ([[User talk:AdamT|talk]]) 10:33, 8 August 2013 (UTC)<br />
<br />
::Just lunched from USB drive without UUID(don't have any idea why it didn't have one). Solution was to change label to appropriate in loader/entries/archiso-x86_64.conf. Not sure weither this should be added to article.<br />
--[[User:Versusvoid|Versusvoid]] ([[User talk:Versusvoid|talk]]) 16:00, 18 August 2013 (UTC)<br />
::Versusvoid, I would love to adapt the article but I cannot follow your description above. Looking at that section, it may be out dated. If you are watching this please elaborate when you have time. Thanks, [[User:AdamT|AdamT]] ([[User_talk:AdamT|Talk]]) 08:32, 23 August 2013 (UTC)<br />
<br />
:::Ok. For some reason ubuntu did not see USB UUID. So ''blkid -o value -s UUID /dev/sdx1'' were returning empty string. The solution was:<br />
<br />
:::''$ sed -i "s|label=ARCH_.*|label=$(blkid -o value -s LABEL /dev/sdx1)|" loader/entries/archiso-x86_64.conf''<br />
<br />
:::in the USB mounting directory. --[[User:Versusvoid|Versusvoid]] ([[User talk:Versusvoid|talk]]) 08:05, 31 August 2013 (UTC)<br />
<br />
:::It seems that sometimes you have to get the UUID by running the command as root. --[[User:Rongmu|Rongmu]] ([[User talk:Rongmu|talk]]) 11:23, 3 October 2013 (UTC)<br />
::::Thank you for the follow-up. My semester started so I have not had much of a chance to help with the Arch Wiki of late. I am removing the strike from this section until I can take a closer look and update the article. [[User:AdamT|AdamT]] ([[User_talk:AdamT|Talk]]) 02:02, 16 November 2013 (UTC)<br />
<br />
== BIOS and UEFI bootable USB in Windows ==<br />
<br />
Maybe this applies also for Linux...<br />
<br />
In section 1.2, where one reads:<br />
<br />
X:\boot\syslinux\<br><br />
/boot/syslinux<br />
<br />
It should be <br />
<br />
X:'''\arch'''\boot\syslinux<br><br />
'''/arch'''/boot/syslinux<br />
<br />
At least with the ARCH_201311 iso...<br />
<br />
Cheers.<br><br />
[[User:Jauch|Jauch]] ([[User talk:Jauch|talk]]) 16:54, 26 November 2013 (UTC)<br />
<br />
<br />
== Making an UEFI/BIOS ISO should be KISS ==<br />
Following up on the discussion in the [https://bbs.archlinux.org/viewtopic.php?id=173559 the bbs], I disagree that [https://wiki.archlinux.org/index.php?title=Talk:USB_Flash_Installation_Media&oldid=284705 this edit] should be kept as the first thing users see when hitting this page. I based this opinion on my feeling that the instructions are too many steps and, arguably too vague. Example, this method is 7 steps (depending on how you count) and requires that user read linked articles (i.e syslinux install and modifying master boot records). In contrast, the dd method is simple (KISS principal) and is both [https://projects.archlinux.org/archiso.git/commit/?id=f19f6173c8650ebc43dc166ee2a2f3f92a753afe implemented] and [https://projects.archlinux.org/archiso.git/commit/?id=ce9c853292e0d37e3931634f43ce697ccd33ad11 documented] as pointed out by one of our developers in the aforementioned bbs thread.<br />
<br />
I think we should at least start the article with the KISS method and this edit down the page. [[User:Graysky|Graysky]] ([[User talk:Graysky|talk]]) 10:30, 29 November 2013 (UTC)<br />
<br />
: Well, I have been keeping an eye on this since the.ridikulus.rat's extensive edits on and after 2013-11-20. I have kept quiet because the maintainers and admins seemed to accept the changes. However, from the start, I disagreed along lines similar to what Graysky has mentioned above.<br />
<br />
: I did not, and do not, understand why the Arch Wiki should be recommending a specific method without any references or firm reasoning. Instead the.ridikulus.rat seemed to be prescribing a method that was believed was superior based on their own preferences. ''This method is slightly more complicated than writing the image directly with {{ic|dd}}, but it does keep the drive usable for data storage.''<br />
<br />
: <s>Please note this quote from the [https://bbs.archlinux.org/viewtopic.php?pid=1354844#p1354844 BBS thread] Graysky linked above (emphasis mine): ''It took me some time to read through the syslinux docs and other blog [sic] to understand the syslinux installation process under Windows, and '''I don't appreciate you simply removing the entire part that I thought out and typed for the sake of the community.'''''</s> I just realized I completely mistook what the.ridikulus.rat meant to say here. Please disregard.<br />
<br />
: While I do think the technical information that the.ridikulus.rat provided was needed in general, and I had in fact [[Talk:Unified_Extensible_Firmware_Interface#Migrate_UEFI_Bootable_Media_to_USB_Flash_Installation_Media.3F|proposed something similar]] shortly before, the extensive reordering of the page and the subjective recommendations does not seem in keeping with the [[ArchWiki:About|ideals]] and [[Help:Editing|established processes]] of the Arch Wiki as I understand them. <br />
<br />
: <s>Further, referencing the quote above, egos definitely seem to be coming into play in a place where they should not matter. The sake of the community is what matters here, not individual investments. See also [[The Arch Way]].</s><br />
<br />
: Moving forward, as of this writing, the changes that Teateawhy has been making seem to be in keeping with the practices put forth in the Arch Wiki's documentation while also mitigating the subjective recommendation that was put forth during the.ridikulus.rat's changes.<br />
<br />
: As a fairly new contributor, one aspect I have not been able to determine from reading over the Arch Wiki's documentation is when and how to make recommendations. As such, and keeping an eye on the bigger picture here, I would like to take this opportunity to suggest something be added to [[Help:Style]] or elsewhere regarding when and how recommendations and suggestions are justified. There seems to be a willingness for some contributors to make claims without references or supporting statements. Similar to Wikipedia's "reference needed" template, a flag or at least cohesive policy may be warranted for the Arch Wiki and it may help prevent situations like this in the future! : )<br />
<br />
: Cheers all, [[User:AdamT|AdamT]] ([[User_talk:AdamT|Talk]]) 03:17, 30 November 2013 (UTC)<br />
<br />
=== Side notes ===<br />
I don't want to hijack the main discussion, but I'd like to answer a couple of AdamT's observations:<br />
<br />
* please do not assume that admins and maintainers can follow everything that happens on the wiki; if you have something to say about somebody else's edits just do it ;)<br />
* I'd be glad to add some guidelines about recommendations to the style guide; the problem is that it's still very subjective to distinguish between what is a ''justified'' recommendation and what is a ''personal'' recommendation... Technically The.ridikulus.rat did justify his suggestion. If you have an idea for the wording of an effective style guide, please propose it here or in [[Help talk:Style]], but I think that most of these cases will have to be solved in discussion pages like it's happened here.<br />
<br />
-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 01:34, 1 December 2013 (UTC)<br />
<br />
== <s>Magic numbers</s> ==<br />
<br />
I know this is not the place to ask questions, but believe me, i spent the last hour searching where the 4Mb info cames from... why do i have to write 4Mb, not 5, not 3 to the beginig of the ISO to the begining of the partition? i was not able to find any information, but it is relevant here. if anyone knows how to explain, or where to link to more info, please do.<br />
<br />
:I don't see how this is relevant to this article, it uses {{ic|4M}} only as a ''block size'' (see {{ic|man dd}}) and IMO this should not matter. So yes, please, use [https://bbs.archlinux.org/ the forums] to ask this kind of questions or if you have a problem. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 11:58, 25 December 2013 (UTC)<br />
<br />
== Does `sync` have any effect? ==<br />
<br />
The line in question is:<br />
# dd bs=4M if=/path/to/archlinux.iso of=/dev/sd'''x''' && sync<br />
<br />
The manual says "sync - flush file system buffers" and "Force changed blocks to disk, update the super block."<br />
<br />
So the question is: does sync have any use when you're writing straight to a block device? There is no filesystem, therefore no buffers to flush and no superblock.<br />
--[[User:Cantabile|Cantabile]] ([[User talk:Cantabile|talk]]) 09:47, 2 January 2014 (UTC)</div>
Cantabile
https://wiki.archlinux.org/index.php?title=List_of_applications/Internet&diff=189922
List of applications/Internet
2012-03-18T15:35:00Z
<p>Cantabile: /* BitTorrent Clients */ Moved deluge and transmission to their own section, since they have both graphical and console interfaces</p>
<hr />
<div><noinclude><br />
[[Category:Software (English)]]<br />
[[Category:Networking (English)]]<br />
{{i18n|Common Applications/Internet}}<br />
{{Common Applications navigation}}<br />
<br />
</noinclude><br />
== Internet ==<br />
{{Note|1=For possibly more up to date selection of applications, try checking the [https://aur.archlinux.org/packages.php?O=0&K=&do_Search=Go&detail=1&C=13&SeB=nd&SB=n&SO=a&PP=50 AUR 'network' category]}}<br />
<br />
=== BitTorrent Clients ===<br />
{{Wikipedia|Comparison of BitTorrent clients}}<br />
<br />
==== Console ====<br />
* {{App|[[aria2]]|lightweight download utility that supports simultaneous adaptive downloading via HTTP(S), FTP, BitTorrent (DHT, PEX, MSE/PE) protocols and MetaLink. Can run as daemon controlled via JSON-RPC & XML-RPC interfaces|http://aria2.sourceforge.net/|{{Pkg|aria2}}}}<br />
* {{App|[[Wikipedia:MLDonkey|MLDonkey]]|multi-protocol P2P client supporting BitTorrent|http://mldonkey.sourceforge.net/|{{Pkg|mldonkey}}}}<br />
* {{App|[[rTorrent]]|simple and lightweight ncurses BitTorrent client|http://libtorrent.rakshasa.no/|{{Pkg|rtorrent}}}}<br />
<br />
==== Graphical ====<br />
* {{App|[[Wikipedia:Vuze|Vuze]]|Feature-rich BitTorrent client written in Java (formerly Azureus)|https://www.vuze.com/|{{AUR|vuze}}}}<br />
* {{App|[[Wikipedia:KTorrent|KTorrent]]|Feature-rich BitTorrent client developed using Qt|http://ktorrent.org/|{{Pkg|ktorrent}}}}<br />
* {{App|[[Wikipedia:qBittorrent|qBittorrent]]|The closest open source (GNU GPL v2 license) equivalent to µtorrent|http://qbittorrent.sourceforge.net/|{{AUR|qbittorrent}}}}<br />
<br />
==== Mixed ====<br />
* {{App|[[Deluge]]|user-friendly BitTorrent client written in Python, with PyGTK, console and web interfaces|http://deluge-torrent.org/|{{Pkg|deluge}}}}<br />
* {{App|[[Wikipedia:Transmission (BitTorrent client)|Transmission]]|simple and easy-to-use BitTorrent client with daemon, GTK+, Qt, web and CLI front-ends|http://transmissionbt.com/|{{Pkg|transmission}}}}<br />
<br />
=== eDonkey Clients ===<br />
eDonkey is still the second-largest p2p network (see [http://ipoque.com/en/resources/internet-studies Internet Study 2008/2009]).<br />
* {{App|[[aMule]]|Well-known eDonkey/Kad client with daemon version and GTK, web, and CLI front-ends|http://www.amule.org/|{{Pkg|amule}}}}<br />
<br />
=== eMoney ===<br />
{{Stub}}<br />
<br />
==== Bitcoin ====<br />
* {{App|[[Bitcoin]]|A tool to manage bitcoins, a p2p currency.|Official website : http://bitcoin.org/|{{AUR|bitcoin}}}}<br />
* [[Bitcoin#Mining|List of mining applications]]<br />
<br />
=== Chat Clients ===<br />
{{Wikipedia|Comparison of instant messaging clients}}<br />
<br />
==== Multi-Protocol Clients ====<br />
{{Wikipedia|Comparison of instant messaging clients#Multiprotocol clients}}<br />
<br />
{{Box||All messengers, that support several networks by means of direct connections to them, belong to this section|#E5E5FF|#FCFCFC}}<br />
<br />
Many clients listed here (including Pidgin and all it's forks) support multiple IM networks via [[Wikipedia:libpurple|libpurple]]. Number of networks is huge but they (like any multiprotocol clients) usually have very limited/none support of network-specific features.<br />
===== Console =====<br />
* {{App|Finch|ncurses-based Jabber/aim/etc/etc chat client based on libpurple|http://developer.pidgin.im/wiki/Using%20Finch|{{Pkg|finch}}}}<br />
* {{App|BarnOwl|chat client for the AIM, IRC, Jabber, and Zephyr protocols|http://barnowl.mit.edu/|{{AUR|barnowl}}}}<br />
* {{App|[[Bitlbee]]|way to use other IM to your [[Wikipedia:IRC|IRC]] client|http://bitlbee.org/|{{Pkg|bitlbee}}}}<br />
* {{App|[[Wikipedia:Centericq|CenterIM]]|Fork of CenterICQ, text mode menu- and window-driven IM interface|http://centerim.org/|{{Pkg|centerim}}}}<br />
<br />
===== Graphical =====<br />
* {{App|[[Pidgin]]|multi-protocol instant messaging client|http://pidgin.im/|{{Pkg|pidgin}}}}<br />
* {{App|Pidgin Light|light Pidgin version without gstreamer, tcl, tk, xscreensaver support|http://pidgin.im/|{{AUR|pidgin-light}}}}<br />
* {{App|Carrier|Pidgin fork providing minor GUI enhancements (formerly funpidgin)|http://funpidgin.sourceforge.net/{{Linkrot|2012|03|09}}|{{AUR|carrier}}}}<br />
* {{App|[[Wikipedia:Instantbird|Instantbird]]|multiprotocol chat client using Mozilla's XUL and libpurple.|http://instantbird.com/|{{AUR|instantbird}}}}<br />
* {{App|[[Wikipedia:Emesene|Emesene]]|Python/GTK+ instant messenger for the Windows Live Messenger network, compatible also with Jabber, Facebook and Google Talk|http://emesene.org/|{{Pkg|emesene}}}}<br />
* {{App|[[Wikipedia:Empathy (software)|Empathy]]|GNOME instant messaging client using the [[Wikipedia:Telepathy (software)|Telepathy]] framework|http://live.gnome.org/Empathy|{{Pkg|empathy}}}}<br />
* {{App|[[Wikipedia:Kopete|Kopete]]|user-friendly IM supporting AIM, ICQ, Windows Live Messenger, Yahoo, Jabber, Gadu-Gadu, Novell GroupWise Messenger, and more IM networks|http://kopete.kde.org/|{{Pkg|kdenetwork-kopete}}}}<br />
* {{App|qutIM|simple user-friendly IM supporting ICQ, Jabber, Mail.Ru, IRC and VKontakte messaging|http://qutim.org/|{{AUR|qutim}}}}<br />
* {{App|Galaxium Messenger|messenger application designed for the GNOME desktop|https://code.google.com/p/galaxium/|{{AUR|galaxium}}}}<br />
<br />
==== IRC Clients ====<br />
{{Wikipedia|Comparison of Internet Relay Chat clients}}<br />
<br />
===== Console =====<br />
* {{App|[[Irssi]]|Highly-configurable ncurses-based IRC client|http://irssi.org/|{{Pkg|irssi}}}}<br />
* {{App|[[Wikipedia:WeeChat|WeeChat]]|Modular, lightweight ncurses-based IRC client|http://weechat.org/|{{Pkg|weechat}}}}<br />
* {{App|[[Wikipedia:Ii (IRC client)|ii]]|featherweight IRC client, literally `tail -f` the convo and `echo` back your replies|http://tools.suckless.org/ii|{{AUR|ii}}}}<br />
* {{App|ERC|powerful, modular, and extensible IRC client for [[Emacs]]|http://savannah.gnu.org/projects/erc/|{{AUR|erc-git}}}}<br />
* {{App|Ircfs|file system interface to irc written in [http://limbo.cat-v.org Limbo]|http://www.ueber.net/code/r/ircfs|not available}}<br />
* {{App|[[Wikipedia:IrcII|IrcII]]|console-based IRC client - AKA BitchX|http://eterna.com.au/ircii/|{{Pkg|ircii-pana}}}}<br />
* {{App|sic|extremely simple IRC client|http://tools.suckless.org/sic|{{AUR|sic}}}}<br />
* {{App|ScrollZ|An advanced IRC client based on ircII|http://scrollz.com {{Linkrot|2012|03|09}}|{{AUR|scrollz}}}}<br />
<br />
===== Graphical =====<br />
* {{App|[[Wikipedia:Konversation|Konversation]]|Qt-based IRC client for the KDE4 desktop|http://konversation.kde.org/|{{Pkg|konversation}}}}<br />
* {{App|[[Wikipedia:KVIrc|KVIrc]]|Qt-based IRC client featuring extensive themes support|http://kvirc.net/|{{Pkg|kvirc}}}}<br />
* {{App|Loqui|A GTK IRC client with only one dependency|https://launchpad.net/loqui|{{AUR|loqui}}}}<br />
* {{App|LostIRC|A simple GTK+ IRC client|http://lostirc.sourceforge.net|{{AUR|lostirc}}}}<br />
* {{App|[[Wikipedia:Smuxi|Smuxi]]|A cross-platform IRC client for the GNOME desktop inspired by Irssi|http://smuxi.org/|{{AUR|smuxi}}}}<br />
* {{App|[[Wikipedia:XChat|XChat]]|GTK-based IRC client|http://xchat.org/|{{Pkg|xchat}}}}<br />
* {{App|pcw|A frontend for [http://tools.suckless.org/ii ii] that opens a new terminal for each channel (depends on [https://bitbucket.org/emg/srw srw] by default)|https://bitbucket.org/emg/pcw|{{AUR|pcw-hg}}}}<br />
<br />
==== Jabber/XMPP Clients ====<br />
{{Wikipedia|Comparison of instant messaging clients#XMPP clients}}<br />
<br />
===== Console =====<br />
* {{App|Freetalk|A console based Jabber client|https://gnu.org/s/freetalk/|{{Pkg|freetalk}}}}<br />
* {{App|jabber.el|A minimal jabber client for emacs|http://emacs-jabber.sourceforge.net/|{{AUR|emacs-jabber}}}}<br />
* {{App|[[Wikipedia:MCabber|MCabber]]|small Jabber console client, includes features: SSL, PGP, MUC, and UTF8|http://mcabber.com/|{{Pkg|mcabber}}}}<br />
<br />
===== Graphical =====<br />
* {{App|[[Wikipedia:Gajim|Gajim]]|Jabber client written in PyGTK|https://gajim.org/|{{Pkg|gajim}}}}<br />
* {{App|[[Wikipedia:Psi (instant messaging client)|Psi]]|A Qt based Jabber client|http://psi-im.org/|{{Pkg|psi}}}}<br />
* {{App|Psi+|enhanced version of Psi Jabber client|https://code.google.com/p/psi-dev/|{{AUR|psi-plus}}}}<br />
<br />
==== MSN Clients ====<br />
* {{App|[[Wikipedia:AMSN|aMSN]]|MSN client written in Tcl/Tk|http://amsn-project.net/|{{Pkg|amsn}}}}<br />
* {{App|[[Wikipedia:Emesene|Emesene]]|A pygtk MSN Messenger client|http://blog.emesene.org/|{{Pkg|emesene}}}}<br />
* {{App|[[Wikipedia:Kmess|KMess]]|KMess is a MSN Messenger client for Linux|http://kmess.org/|{{Pkg|kmess}}}}<br />
* {{App|Mercury|Java Based MSN client|http://mercury.im{{Linkrot|2012|02|19}}|{{AUR|mercury}}}}<br />
<br />
=== Email clients ===<br />
{{Wikipedia|Comparison of e-mail clients}}<br />
<br />
==== Console ====<br />
* {{App|[[Alpine]]|The Apache-licensed [[Wikipedia:PINE|PINE]] (a tool for reading, sending, and managing electronic messages)|https://washington.edu/alpine|{{Pkg|alpine}}}}<br />
* {{App|[[Wikipedia:Gnus|Gnus]]|mail, nntp, rss client for Emacs.|http://gnus.org/|{{AUR|emacs-gnus-git}}}}<br />
* {{App|[[Wikipedia:mailx|heirloom-mailx]]|A full-featured command-line MUA derived from Berkeley Mail.|http://heirloom.sourceforge.net/mailx.html|{{Pkg|heirloom-mailx}}}}<br />
* {{App|[[Mutt]]|Small but very powerful text-based mail client.|http://mutt.org/|{{Pkg|mutt}}}}<br />
* {{App|[[Sup]]|A CLI mail client with very fast searching, tagging, threading and gmail like operation.|http://sup.rubyforge.org/|{{AUR|sup}}}}<br />
<br />
==== Graphical ====<br />
* {{App|[[Balsa]]|A simple light email client. Part of the Gnome project|http://balsa.gnome.org/|{{Pkg|balsa}}}}<br />
* {{App|[[Wikipedia:Claws Mail|Claws Mail]]|A GTK+ based e-mail client|http://claws-mail.org/|{{Pkg|claws-mail}}}}<br />
* {{App|[[Evolution]]|A mature and feature-rich e-mail client used in GNOME by default|http://projects.gnome.org/evolution/|{{Pkg|evolution}}}}<br />
* {{App|[[Wikipedia:Kmail|Kmail]]|A mature and feature-rich e-mail client part of the KDE project|http://kde.org/applications/internet/kmail/|{{Pkg|kmail}}}}<br />
* {{App|Postler|simple desktop mail client built in vala.|http://git.xfce.org/apps/postler|{{AUR|postler}}}}<br />
* {{App|[[Wikipedia:Sylpheed|Sylpheed]]|Lightweight and user-friendly e-mail client (GTK)|http://sylpheed.sraoss.jp/en/|{{AUR|sylpheed}}}}<br />
* {{App|[[Thunderbird]]|Mozilla's GTK2-based client|https://mozillamessaging.com|{{Pkg|thunderbird}}}}<br />
<br />
=== Network Managers ===<br />
* {{App|[[netcfg]]|Network configuration and profile scripts|http://projects.archlinux.org/netcfg.git/|{{Pkg|netcfg}}}}<br />
* {{App|[[Wicd]]|Manages wireless and wired interfaces, requiring fewer dependencies than other network managers. In addition to GUI interfaces, a curses version is also available.|http://wicd.sourceforge.net/|{{Pkg|wicd}}}}<br />
* {{App|[[NetworkManager]]|provides wired, wireless, mobile broadband and OpenVPN detection and configuration allowing automatic connection to a network.|http://projects.gnome.org/NetworkManager/|{{Pkg|networkmanager}}}}<br />
<br />
=== News Aggregators ===<br />
{{Wikipedia|Comparison of feed aggregators}}<br />
<br />
==== Console ====<br />
* {{App|Newsbeuter|A ncurses RSS aggregator with layout and keybinding similar to mutt. Does not use the traditional 3 panes setup|http://newsbeuter.org|{{Pkg|newsbeuter}}}}<br />
* {{App|Snownews|Text mode RSS newsreader|http://kiza.kcore.de/software/snownews/|{{Pkg|snownews}}}}<br />
* {{App|Rawdog|A "RSS Aggregator Without Delusions Of Grandeur" that parses RSS/CDF/Atom feeds into a static HTML page of articles in date order|http://offog.org/code/rawdog.html|{{AUR|rawdog}}}}<br />
* {{App|[[Wikipedia:Gnus|Gnus]]|A mail, nntp, rss client for Emacs|http://gnus.org/|{{AUR|emacs-gnus-git}}}}<br />
* {{App|[[Wikipedia:Canto (news aggregator)|Canto]]|A ncurses RSS aggregator|http://codezen.org/canto/|{{AUR|canto}}}}<br />
<br />
==== Graphical ====<br />
* {{App|Akregator|KDE's news aggregator|http://akregator.kde.org/|{{Pkg|kdepim-akregator}}}}<br />
* {{App|[[Wikipedia:Liferea|Liferea]]|GTK desktop news aggregator for online news feeds and weblogs| http://liferea.sourceforge.net|{{Pkg|liferea}}}}<br />
* {{App|RSS Guard|A (very) tiny RSS & ATOM reader developed using Qt framework|https://code.google.com/p/rss-guard/|{{AUR|rss-guard}}}}<br />
* {{App|[[Wikipedia:RSSOwl|Rssowl]]|powerful aggregator for RSS and Atom feeds, written in Java using Eclipse Rich Client Platform and SWT as a widget toolkit|http://boreal.rssowl.org|{{AUR|rssowl}}}}<br />
* {{App|[[Wikipedia:BlogBridge|BlogBridge]]|excellent java-based aggregator, which gives users the option to synchronize their feeds across multiple computers|http://blogbridge.com|{{AUR|blogbridge}}}}<br />
* {{App|[[Thunderbird]]|A mail client from Mozilla which also functions as a pretty nice news aggregator|https://mozillamessaging.com|{{Pkg|thunderbird}}}}<br />
* {{App|Tickr (formerly News)|GTK-based RSS Reader that displays feeds as a smooth scrolling line on your Desktop, as known from TV stations.|http://newsrssticker.com/|{{AUR|tickr}}}}<br />
<br />
=== Web Browsers ===<br />
{{Wikipedia|Comparison of web browsers}}<br />
<br />
==== Console ====<br />
* {{App|[[Wikipedia:W3m|W3m]]|pager/text-based WWW browser|http://w3m.sourceforge.net/|{{Pkg|w3m}}}}<br />
* {{App|[[Wikipedia:Lynx (web browser)|Lynx]]|text browser for the World Wide Web|http://lynx.isc.org|{{Pkg|lynx}}}}<br />
* {{App|[[Wikipedia:Links (web browser)|Links]]|text WWW browser, similar to Lynx, but with CSS-based rendering|http://links.twibright.com/|{{Pkg|links}}}}<br />
* {{App|[[Wikipedia:ELinks|ELinks]]|advanced and well-established feature-rich text mode web browser (links fork, barely supported since 2009)|http://elinks.or.cz/|{{Pkg|elinks}}}}<br />
<br />
==== Graphical ====<br />
* {{App|[[Wikipedia:Abaco (web browser)|Abaco]]|A multi-page graphical web browser|http://lab-fgb.com/abaco/|{{AUR|abaco}}}}<br />
* {{App|[[Wikipedia:Arora (browser)|Arora]]|A cross platform web browser built using Qt and WebKit|https://code.google.com/p/arora/|{{Pkg|arora}}}}<br />
* {{App|[[Wikipedia:Conkeror|Conkeror]]|A highly programmable web browser based on Mozilla XULRunner|http://conkeror.org/|{{AUR|conkeror-git}}}}<br />
* {{App|[[Chromium]]|The open-source project behind Google Chrome, a web browser developed by Google that uses the WebKit layout engine and application framework|https://code.google.com/chromium/|{{Pkg|chromium}}}}<br />
* {{App|[[Wikipedia:Dillo|Dillo]]|A small, fast graphical web browser built on FLTK|http://dillo.org/|{{Pkg|dillo}}}}<br />
* {{App|[[Epiphany]]|The default GNOME browser, which uses the webkit rendering engine|http://projects.gnome.org/epiphany/|{{Pkg|epiphany}}}}<br />
* {{App|[[Firefox]]|[https://addons.mozilla.org/firefox/ Extensible] GTK2 browser based on Gecko with fast rendering|https://mozilla.com/firefox|{{Pkg|firefox}}}}<br />
* {{App|Hv3|A minimalist web browser based on tkhtml3|http://tkhtml.tcl.tk/hv3.html|{{AUR|hv3}}}}<br />
* {{App|[[Jumanji]]|A highly customizable and functional web browser|http://pwmt.org/projects/jumanji|{{AUR|jumanji}}}}<br />
* {{App|[[Wikipedia:Kazehakase|Kazehakase]]|A much lighter, but rather feature-lacking alternative to other browsers (GTK2 and Gecko)|http://kazehakase.sourceforge.jp/|{{AUR|kazehakase}}}}<br />
* {{App|dwb| A lightweight web browser based on the webkit engine. Highly customizable, with vi-like shortcuts and tiling layouts. |http://portix.bitbucket.org/dwb|{{AUR|dwb}}}}<br />
* {{App|[[Wikipedia:Konqueror|Konqueror]]|Qt- and KHTML-based browser. A part of the KDE desktop|http://konqueror.org/|{{Pkg|kdebase-konqueror}}}}<br />
* {{App|Luakit| A highly configurable, micro-browser framework based on the WebKit web content engine and the GTK+ toolkit. It is very fast, extensible by Lua and licensed under the GNU GPLv3 license|http://luakit.org/projects/luakit/|{{Pkg|luakit}}}}<br />
* {{App|[[Wikipedia:Midori (web browser)|Midori]]| A lightweight web browser based on Gtk and WebKit. Passes the ACID3 test|http://twotoasts.de/index.php?/pages/midori_summary.html|{{Pkg|midori}}}}<br />
* {{App|[[Wikipedia:NetSurf|NetSurf]]| A featherweight browser written in C. Notable is its lack of JavaScript support and fast rendering through its own custom rendering engine|http://netsurf-browser.org|{{Pkg|netsurf}}}}<br />
* {{App|[[Opera]]|Highly customizable browser with focuses on an adherence to web rendering standards|http://opera.com|{{Pkg|opera}}}}<br />
* {{App|[[wikipedia:Rekonq|Rekonq]]| A WebKit based web browser for KDE|http://rekonq.kde.org/|{{Pkg|rekonq}}}}<br />
* {{App|Sb|A very lightweight webkit-based browser that uses keybindings to perform most things the URL bar would usually do|https://github.com/mutantturkey/sb/|{{AUR|sb-git}}}} <br />
* {{App|Surf|Another lightweight WebKit-based browser, which follows the [http://suckless.org/manifest/ suckless ideology]. Which means, the software is even more lightweight (basically, the browser itself is a single C source file)|http://surf.suckless.org|{{AUR|surf-hg}}}}<br />
* {{App|[[Wikipedia:Uzbl|Uzbl]]|Web interface tools which adhere to the unix philosophy|http://uzbl.org/|{{Pkg|uzbl-browser}}}}<br />
* {{App|[[Vimprobable]]|A browser that behaves like the Vimperator plugin available for Mozilla Firefox. It is based on the WebKit engine (using GTK bindings)|http://vimprobable.org/|{{AUR|vimprobable-git}}}}<br />
<br />
=== Microblogging Clients ===<br />
* {{App|Pino|simple and fast X11 client for Twitter and Identi.ca. It is compiled to native code, which assures small size and speed, and thanks to use of Vala language it can perfectly integrate into your Gnome or XFCE desktop|http://pino-app.appspot.com/|{{AUR|pino}}}}<br />
* {{App|[[Wikipedia:Gwibber|Gwibber]]|open source microblogging client for Linux. It brings the most popular social networking web services to your desktop and gives you the ability to control how you communicate|http://gwibber.com/|{{AUR|gwibber}}}}<br />
* {{App|[[Wikipedia:Hotot (program)|Hotot]]|lightweight & open source Microblogging Client, coding using Python language and designed for Linux|http://hotot.org|{{AUR|hotot}}}}<br />
* {{App|tyrs|simple client for for Twitter and Identi.ca supporting virtually all its' features with nice console UI|http://tyrs.nicosphere.net/|{{AUR|tyrs}}}}<br />
<br />
=== FTP Clients ===<br />
{{Wikipedia|Comparison of FTP client software}}<br />
<br />
* {{App|Filezilla|Fast and reliable FTP, FTPS and SFTP client|http://filezilla-project.org/|{{Pkg|filezilla}}}}<br />
* {{App|curlftp|A filesystem for acessing FTP hosts based on FUSE and libcurl. |http://curlftpfs.sourceforge.net/|{{Pkg|curlftpfs}}}}<br />
* {{App|fuseftp|FTP filesystem written in Perl, using FUSE|http://freshmeat.net/projects/fuseftp/|{{AUR|fuseftp}}}}<br />
* {{App|lftp|Sophisticated command line based FTP client|http://lftp.yar.ru/|{{Pkg|lftp}}}}<br />
* {{App|gftp|A multithreaded ftp client for X|http://gftp.seul.org/|{{Pkg|gftp}}}}<br />
* {{App|tnftp|[[Wikipedia:NetBSD|NetBSD]] FTP client with several advanced features|http://freecode.com/projects/tnftp|{{Pkg|tnftp}}}}<br />
Some file managers like [[Dolphin]], [[Nautilus]] and [[Thunar]] also provide FTP functionality.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=List_of_applications/Internet&diff=189902
List of applications/Internet
2012-03-18T15:20:56Z
<p>Cantabile: /* Console */ Search for "transmission" so that all relevant packages are found, not just the cli client.</p>
<hr />
<div><noinclude><br />
[[Category:Software (English)]]<br />
[[Category:Networking (English)]]<br />
{{i18n|Common Applications/Internet}}<br />
{{Common Applications navigation}}<br />
<br />
</noinclude><br />
== Internet ==<br />
{{Note|1=For possibly more up to date selection of applications, try checking the [https://aur.archlinux.org/packages.php?O=0&K=&do_Search=Go&detail=1&C=13&SeB=nd&SB=n&SO=a&PP=50 AUR 'network' category]}}<br />
<br />
=== BitTorrent Clients ===<br />
{{Wikipedia|Comparison of BitTorrent clients}}<br />
<br />
==== Console ====<br />
* {{App|[[aria2]]|lightweight download utility that supports simultaneous adaptive downloading via HTTP(S), FTP, BitTorrent (DHT, PEX, MSE/PE) protocols and MetaLink. Can run as daemon controlled via JSON-RPC & XML-RPC interfaces|http://aria2.sourceforge.net/|{{Pkg|aria2}}}}<br />
* {{App|[[Wikipedia:MLDonkey|MLDonkey]]|multi-protocol P2P client supporting BitTorrent|http://mldonkey.sourceforge.net/|{{Pkg|mldonkey}}}}<br />
* {{App|[[Deluge]]|user-friendly BitTorrent client written in Python and wrapped with PyGTK|http://deluge-torrent.org/|{{Pkg|deluge}}}}<br />
* {{App|[[rTorrent]]|simple and lightweight ncurses BitTorrent client|http://libtorrent.rakshasa.no/|{{Pkg|rtorrent}}}}<br />
* {{App|[[Wikipedia:Transmission (BitTorrent client)|Transmission]]|simple and easy-to-use BitTorrent client with daemon version, GTK+, Qt GUI, web and CLI front-ends|http://transmissionbt.com/|{{Pkg|transmission}}}}<br />
<br />
==== Graphical ====<br />
* {{App|[[Wikipedia:Vuze|Vuze]]|Feature-rich BitTorrent client written in Java (formerly Azureus)|https://www.vuze.com/|{{AUR|vuze}}}}<br />
* {{App|[[Wikipedia:KTorrent|KTorrent]]|Feature-rich BitTorrent client developed using Qt|http://ktorrent.org/|{{Pkg|ktorrent}}}}<br />
* {{App|[[Wikipedia:qBittorrent|qBittorrent]]|The closest open source (GNU GPL v2 license) equivalent to µtorrent|http://qbittorrent.sourceforge.net/|{{AUR|qbittorrent}}}}<br />
<br />
=== eDonkey Clients ===<br />
eDonkey is still the second-largest p2p network (see [http://ipoque.com/en/resources/internet-studies Internet Study 2008/2009]).<br />
* {{App|[[aMule]]|Well-known eDonkey/Kad client with daemon version and GTK, web, and CLI front-ends|http://www.amule.org/|{{Pkg|amule}}}}<br />
<br />
=== eMoney ===<br />
{{Stub}}<br />
<br />
==== Bitcoin ====<br />
* {{App|[[Bitcoin]]|A tool to manage bitcoins, a p2p currency.|Official website : http://bitcoin.org/|{{AUR|bitcoin}}}}<br />
* [[Bitcoin#Mining|List of mining applications]]<br />
<br />
=== Chat Clients ===<br />
{{Wikipedia|Comparison of instant messaging clients}}<br />
<br />
==== Multi-Protocol Clients ====<br />
{{Wikipedia|Comparison of instant messaging clients#Multiprotocol clients}}<br />
<br />
{{Box||All messengers, that support several networks by means of direct connections to them, belong to this section|#E5E5FF|#FCFCFC}}<br />
<br />
Many clients listed here (including Pidgin and all it's forks) support multiple IM networks via [[Wikipedia:libpurple|libpurple]]. Number of networks is huge but they (like any multiprotocol clients) usually have very limited/none support of network-specific features.<br />
===== Console =====<br />
* {{App|Finch|ncurses-based Jabber/aim/etc/etc chat client based on libpurple|http://developer.pidgin.im/wiki/Using%20Finch|{{Pkg|finch}}}}<br />
* {{App|BarnOwl|chat client for the AIM, IRC, Jabber, and Zephyr protocols|http://barnowl.mit.edu/|{{AUR|barnowl}}}}<br />
* {{App|[[Bitlbee]]|way to use other IM to your [[Wikipedia:IRC|IRC]] client|http://bitlbee.org/|{{Pkg|bitlbee}}}}<br />
* {{App|[[Wikipedia:Centericq|CenterIM]]|Fork of CenterICQ, text mode menu- and window-driven IM interface|http://centerim.org/|{{Pkg|centerim}}}}<br />
<br />
===== Graphical =====<br />
* {{App|[[Pidgin]]|multi-protocol instant messaging client|http://pidgin.im/|{{Pkg|pidgin}}}}<br />
* {{App|Pidgin Light|light Pidgin version without gstreamer, tcl, tk, xscreensaver support|http://pidgin.im/|{{AUR|pidgin-light}}}}<br />
* {{App|Carrier|Pidgin fork providing minor GUI enhancements (formerly funpidgin)|http://funpidgin.sourceforge.net/{{Linkrot|2012|03|09}}|{{AUR|carrier}}}}<br />
* {{App|[[Wikipedia:Instantbird|Instantbird]]|multiprotocol chat client using Mozilla's XUL and libpurple.|http://instantbird.com/|{{AUR|instantbird}}}}<br />
* {{App|[[Wikipedia:Emesene|Emesene]]|Python/GTK+ instant messenger for the Windows Live Messenger network, compatible also with Jabber, Facebook and Google Talk|http://emesene.org/|{{Pkg|emesene}}}}<br />
* {{App|[[Wikipedia:Empathy (software)|Empathy]]|GNOME instant messaging client using the [[Wikipedia:Telepathy (software)|Telepathy]] framework|http://live.gnome.org/Empathy|{{Pkg|empathy}}}}<br />
* {{App|[[Wikipedia:Kopete|Kopete]]|user-friendly IM supporting AIM, ICQ, Windows Live Messenger, Yahoo, Jabber, Gadu-Gadu, Novell GroupWise Messenger, and more IM networks|http://kopete.kde.org/|{{Pkg|kdenetwork-kopete}}}}<br />
* {{App|qutIM|simple user-friendly IM supporting ICQ, Jabber, Mail.Ru, IRC and VKontakte messaging|http://qutim.org/|{{AUR|qutim}}}}<br />
* {{App|Galaxium Messenger|messenger application designed for the GNOME desktop|https://code.google.com/p/galaxium/|{{AUR|galaxium}}}}<br />
<br />
==== IRC Clients ====<br />
{{Wikipedia|Comparison of Internet Relay Chat clients}}<br />
<br />
===== Console =====<br />
* {{App|[[Irssi]]|Highly-configurable ncurses-based IRC client|http://irssi.org/|{{Pkg|irssi}}}}<br />
* {{App|[[Wikipedia:WeeChat|WeeChat]]|Modular, lightweight ncurses-based IRC client|http://weechat.org/|{{Pkg|weechat}}}}<br />
* {{App|[[Wikipedia:Ii (IRC client)|ii]]|featherweight IRC client, literally `tail -f` the convo and `echo` back your replies|http://tools.suckless.org/ii|{{AUR|ii}}}}<br />
* {{App|ERC|powerful, modular, and extensible IRC client for [[Emacs]]|http://savannah.gnu.org/projects/erc/|{{AUR|erc-git}}}}<br />
* {{App|Ircfs|file system interface to irc written in [http://limbo.cat-v.org Limbo]|http://www.ueber.net/code/r/ircfs|not available}}<br />
* {{App|[[Wikipedia:IrcII|IrcII]]|console-based IRC client - AKA BitchX|http://eterna.com.au/ircii/|{{Pkg|ircii-pana}}}}<br />
* {{App|sic|extremely simple IRC client|http://tools.suckless.org/sic|{{AUR|sic}}}}<br />
* {{App|ScrollZ|An advanced IRC client based on ircII|http://scrollz.com {{Linkrot|2012|03|09}}|{{AUR|scrollz}}}}<br />
<br />
===== Graphical =====<br />
* {{App|[[Wikipedia:Konversation|Konversation]]|Qt-based IRC client for the KDE4 desktop|http://konversation.kde.org/|{{Pkg|konversation}}}}<br />
* {{App|[[Wikipedia:KVIrc|KVIrc]]|Qt-based IRC client featuring extensive themes support|http://kvirc.net/|{{Pkg|kvirc}}}}<br />
* {{App|Loqui|A GTK IRC client with only one dependency|https://launchpad.net/loqui|{{AUR|loqui}}}}<br />
* {{App|LostIRC|A simple GTK+ IRC client|http://lostirc.sourceforge.net|{{AUR|lostirc}}}}<br />
* {{App|[[Wikipedia:Smuxi|Smuxi]]|A cross-platform IRC client for the GNOME desktop inspired by Irssi|http://smuxi.org/|{{AUR|smuxi}}}}<br />
* {{App|[[Wikipedia:XChat|XChat]]|GTK-based IRC client|http://xchat.org/|{{Pkg|xchat}}}}<br />
* {{App|pcw|A frontend for [http://tools.suckless.org/ii ii] that opens a new terminal for each channel (depends on [https://bitbucket.org/emg/srw srw] by default)|https://bitbucket.org/emg/pcw|{{AUR|pcw-hg}}}}<br />
<br />
==== Jabber/XMPP Clients ====<br />
{{Wikipedia|Comparison of instant messaging clients#XMPP clients}}<br />
<br />
===== Console =====<br />
* {{App|Freetalk|A console based Jabber client|https://gnu.org/s/freetalk/|{{Pkg|freetalk}}}}<br />
* {{App|jabber.el|A minimal jabber client for emacs|http://emacs-jabber.sourceforge.net/|{{AUR|emacs-jabber}}}}<br />
* {{App|[[Wikipedia:MCabber|MCabber]]|small Jabber console client, includes features: SSL, PGP, MUC, and UTF8|http://mcabber.com/|{{Pkg|mcabber}}}}<br />
<br />
===== Graphical =====<br />
* {{App|[[Wikipedia:Gajim|Gajim]]|Jabber client written in PyGTK|https://gajim.org/|{{Pkg|gajim}}}}<br />
* {{App|[[Wikipedia:Psi (instant messaging client)|Psi]]|A Qt based Jabber client|http://psi-im.org/|{{Pkg|psi}}}}<br />
* {{App|Psi+|enhanced version of Psi Jabber client|https://code.google.com/p/psi-dev/|{{AUR|psi-plus}}}}<br />
<br />
==== MSN Clients ====<br />
* {{App|[[Wikipedia:AMSN|aMSN]]|MSN client written in Tcl/Tk|http://amsn-project.net/|{{Pkg|amsn}}}}<br />
* {{App|[[Wikipedia:Emesene|Emesene]]|A pygtk MSN Messenger client|http://blog.emesene.org/|{{Pkg|emesene}}}}<br />
* {{App|[[Wikipedia:Kmess|KMess]]|KMess is a MSN Messenger client for Linux|http://kmess.org/|{{Pkg|kmess}}}}<br />
* {{App|Mercury|Java Based MSN client|http://mercury.im{{Linkrot|2012|02|19}}|{{AUR|mercury}}}}<br />
<br />
=== Email clients ===<br />
{{Wikipedia|Comparison of e-mail clients}}<br />
<br />
==== Console ====<br />
* {{App|[[Alpine]]|The Apache-licensed [[Wikipedia:PINE|PINE]] (a tool for reading, sending, and managing electronic messages)|https://washington.edu/alpine|{{Pkg|alpine}}}}<br />
* {{App|[[Wikipedia:Gnus|Gnus]]|mail, nntp, rss client for Emacs.|http://gnus.org/|{{AUR|emacs-gnus-git}}}}<br />
* {{App|[[Wikipedia:mailx|heirloom-mailx]]|A full-featured command-line MUA derived from Berkeley Mail.|http://heirloom.sourceforge.net/mailx.html|{{Pkg|heirloom-mailx}}}}<br />
* {{App|[[Mutt]]|Small but very powerful text-based mail client.|http://mutt.org/|{{Pkg|mutt}}}}<br />
* {{App|[[Sup]]|A CLI mail client with very fast searching, tagging, threading and gmail like operation.|http://sup.rubyforge.org/|{{AUR|sup}}}}<br />
<br />
==== Graphical ====<br />
* {{App|[[Balsa]]|A simple light email client. Part of the Gnome project|http://balsa.gnome.org/|{{Pkg|balsa}}}}<br />
* {{App|[[Wikipedia:Claws Mail|Claws Mail]]|A GTK+ based e-mail client|http://claws-mail.org/|{{Pkg|claws-mail}}}}<br />
* {{App|[[Evolution]]|A mature and feature-rich e-mail client used in GNOME by default|http://projects.gnome.org/evolution/|{{Pkg|evolution}}}}<br />
* {{App|[[Wikipedia:Kmail|Kmail]]|A mature and feature-rich e-mail client part of the KDE project|http://kde.org/applications/internet/kmail/|{{Pkg|kmail}}}}<br />
* {{App|Postler|simple desktop mail client built in vala.|http://git.xfce.org/apps/postler|{{AUR|postler}}}}<br />
* {{App|[[Wikipedia:Sylpheed|Sylpheed]]|Lightweight and user-friendly e-mail client (GTK)|http://sylpheed.sraoss.jp/en/|{{AUR|sylpheed}}}}<br />
* {{App|[[Thunderbird]]|Mozilla's GTK2-based client|https://mozillamessaging.com|{{Pkg|thunderbird}}}}<br />
<br />
=== Network Managers ===<br />
* {{App|[[netcfg]]|Network configuration and profile scripts|http://projects.archlinux.org/netcfg.git/|{{Pkg|netcfg}}}}<br />
* {{App|[[Wicd]]|Manages wireless and wired interfaces, requiring fewer dependencies than other network managers. In addition to GUI interfaces, a curses version is also available.|http://wicd.sourceforge.net/|{{Pkg|wicd}}}}<br />
* {{App|[[NetworkManager]]|provides wired, wireless, mobile broadband and OpenVPN detection and configuration allowing automatic connection to a network.|http://projects.gnome.org/NetworkManager/|{{Pkg|networkmanager}}}}<br />
<br />
=== News Aggregators ===<br />
{{Wikipedia|Comparison of feed aggregators}}<br />
<br />
==== Console ====<br />
* {{App|Newsbeuter|A ncurses RSS aggregator with layout and keybinding similar to mutt. Does not use the traditional 3 panes setup|http://newsbeuter.org|{{Pkg|newsbeuter}}}}<br />
* {{App|Snownews|Text mode RSS newsreader|http://kiza.kcore.de/software/snownews/|{{Pkg|snownews}}}}<br />
* {{App|Rawdog|A "RSS Aggregator Without Delusions Of Grandeur" that parses RSS/CDF/Atom feeds into a static HTML page of articles in date order|http://offog.org/code/rawdog.html|{{AUR|rawdog}}}}<br />
* {{App|[[Wikipedia:Gnus|Gnus]]|A mail, nntp, rss client for Emacs|http://gnus.org/|{{AUR|emacs-gnus-git}}}}<br />
* {{App|[[Wikipedia:Canto (news aggregator)|Canto]]|A ncurses RSS aggregator|http://codezen.org/canto/|{{AUR|canto}}}}<br />
<br />
==== Graphical ====<br />
* {{App|Akregator|KDE's news aggregator|http://akregator.kde.org/|{{Pkg|kdepim-akregator}}}}<br />
* {{App|[[Wikipedia:Liferea|Liferea]]|GTK desktop news aggregator for online news feeds and weblogs| http://liferea.sourceforge.net|{{Pkg|liferea}}}}<br />
* {{App|RSS Guard|A (very) tiny RSS & ATOM reader developed using Qt framework|https://code.google.com/p/rss-guard/|{{AUR|rss-guard}}}}<br />
* {{App|[[Wikipedia:RSSOwl|Rssowl]]|powerful aggregator for RSS and Atom feeds, written in Java using Eclipse Rich Client Platform and SWT as a widget toolkit|http://boreal.rssowl.org|{{AUR|rssowl}}}}<br />
* {{App|[[Wikipedia:BlogBridge|BlogBridge]]|excellent java-based aggregator, which gives users the option to synchronize their feeds across multiple computers|http://blogbridge.com|{{AUR|blogbridge}}}}<br />
* {{App|[[Thunderbird]]|A mail client from Mozilla which also functions as a pretty nice news aggregator|https://mozillamessaging.com|{{Pkg|thunderbird}}}}<br />
* {{App|Tickr (formerly News)|GTK-based RSS Reader that displays feeds as a smooth scrolling line on your Desktop, as known from TV stations.|http://newsrssticker.com/|{{AUR|tickr}}}}<br />
<br />
=== Web Browsers ===<br />
{{Wikipedia|Comparison of web browsers}}<br />
<br />
==== Console ====<br />
* {{App|[[Wikipedia:W3m|W3m]]|pager/text-based WWW browser|http://w3m.sourceforge.net/|{{Pkg|w3m}}}}<br />
* {{App|[[Wikipedia:Lynx (web browser)|Lynx]]|text browser for the World Wide Web|http://lynx.isc.org|{{Pkg|lynx}}}}<br />
* {{App|[[Wikipedia:Links (web browser)|Links]]|text WWW browser, similar to Lynx, but with CSS-based rendering|http://links.twibright.com/|{{Pkg|links}}}}<br />
* {{App|[[Wikipedia:ELinks|ELinks]]|advanced and well-established feature-rich text mode web browser (links fork, barely supported since 2009)|http://elinks.or.cz/|{{Pkg|elinks}}}}<br />
<br />
==== Graphical ====<br />
* {{App|[[Wikipedia:Abaco (web browser)|Abaco]]|A multi-page graphical web browser|http://lab-fgb.com/abaco/|{{AUR|abaco}}}}<br />
* {{App|[[Wikipedia:Arora (browser)|Arora]]|A cross platform web browser built using Qt and WebKit|https://code.google.com/p/arora/|{{Pkg|arora}}}}<br />
* {{App|[[Wikipedia:Conkeror|Conkeror]]|A highly programmable web browser based on Mozilla XULRunner|http://conkeror.org/|{{AUR|conkeror-git}}}}<br />
* {{App|[[Chromium]]|The open-source project behind Google Chrome, a web browser developed by Google that uses the WebKit layout engine and application framework|https://code.google.com/chromium/|{{Pkg|chromium}}}}<br />
* {{App|[[Wikipedia:Dillo|Dillo]]|A small, fast graphical web browser built on FLTK|http://dillo.org/|{{Pkg|dillo}}}}<br />
* {{App|[[Epiphany]]|The default GNOME browser, which uses the webkit rendering engine|http://projects.gnome.org/epiphany/|{{Pkg|epiphany}}}}<br />
* {{App|[[Firefox]]|[https://addons.mozilla.org/firefox/ Extensible] GTK2 browser based on Gecko with fast rendering|https://mozilla.com/firefox|{{Pkg|firefox}}}}<br />
* {{App|Hv3|A minimalist web browser based on tkhtml3|http://tkhtml.tcl.tk/hv3.html|{{AUR|hv3}}}}<br />
* {{App|[[Jumanji]]|A highly customizable and functional web browser|http://pwmt.org/projects/jumanji|{{AUR|jumanji}}}}<br />
* {{App|[[Wikipedia:Kazehakase|Kazehakase]]|A much lighter, but rather feature-lacking alternative to other browsers (GTK2 and Gecko)|http://kazehakase.sourceforge.jp/|{{AUR|kazehakase}}}}<br />
* {{App|dwb| A lightweight web browser based on the webkit engine. Highly customizable, with vi-like shortcuts and tiling layouts. |http://portix.bitbucket.org/dwb|{{AUR|dwb}}}}<br />
* {{App|[[Wikipedia:Konqueror|Konqueror]]|Qt- and KHTML-based browser. A part of the KDE desktop|http://konqueror.org/|{{Pkg|kdebase-konqueror}}}}<br />
* {{App|Luakit| A highly configurable, micro-browser framework based on the WebKit web content engine and the GTK+ toolkit. It is very fast, extensible by Lua and licensed under the GNU GPLv3 license|http://luakit.org/projects/luakit/|{{Pkg|luakit}}}}<br />
* {{App|[[Wikipedia:Midori (web browser)|Midori]]| A lightweight web browser based on Gtk and WebKit. Passes the ACID3 test|http://twotoasts.de/index.php?/pages/midori_summary.html|{{Pkg|midori}}}}<br />
* {{App|[[Wikipedia:NetSurf|NetSurf]]| A featherweight browser written in C. Notable is its lack of JavaScript support and fast rendering through its own custom rendering engine|http://netsurf-browser.org|{{Pkg|netsurf}}}}<br />
* {{App|[[Opera]]|Highly customizable browser with focuses on an adherence to web rendering standards|http://opera.com|{{Pkg|opera}}}}<br />
* {{App|[[wikipedia:Rekonq|Rekonq]]| A WebKit based web browser for KDE|http://rekonq.kde.org/|{{Pkg|rekonq}}}}<br />
* {{App|Sb|A very lightweight webkit-based browser that uses keybindings to perform most things the URL bar would usually do|https://github.com/mutantturkey/sb/|{{AUR|sb-git}}}} <br />
* {{App|Surf|Another lightweight WebKit-based browser, which follows the [http://suckless.org/manifest/ suckless ideology]. Which means, the software is even more lightweight (basically, the browser itself is a single C source file)|http://surf.suckless.org|{{AUR|surf-hg}}}}<br />
* {{App|[[Wikipedia:Uzbl|Uzbl]]|Web interface tools which adhere to the unix philosophy|http://uzbl.org/|{{Pkg|uzbl-browser}}}}<br />
* {{App|[[Vimprobable]]|A browser that behaves like the Vimperator plugin available for Mozilla Firefox. It is based on the WebKit engine (using GTK bindings)|http://vimprobable.org/|{{AUR|vimprobable-git}}}}<br />
<br />
=== Microblogging Clients ===<br />
* {{App|Pino|simple and fast X11 client for Twitter and Identi.ca. It is compiled to native code, which assures small size and speed, and thanks to use of Vala language it can perfectly integrate into your Gnome or XFCE desktop|http://pino-app.appspot.com/|{{AUR|pino}}}}<br />
* {{App|[[Wikipedia:Gwibber|Gwibber]]|open source microblogging client for Linux. It brings the most popular social networking web services to your desktop and gives you the ability to control how you communicate|http://gwibber.com/|{{AUR|gwibber}}}}<br />
* {{App|[[Wikipedia:Hotot (program)|Hotot]]|lightweight & open source Microblogging Client, coding using Python language and designed for Linux|http://hotot.org|{{AUR|hotot}}}}<br />
* {{App|tyrs|simple client for for Twitter and Identi.ca supporting virtually all its' features with nice console UI|http://tyrs.nicosphere.net/|{{AUR|tyrs}}}}<br />
<br />
=== FTP Clients ===<br />
{{Wikipedia|Comparison of FTP client software}}<br />
<br />
* {{App|Filezilla|Fast and reliable FTP, FTPS and SFTP client|http://filezilla-project.org/|{{Pkg|filezilla}}}}<br />
* {{App|curlftp|A filesystem for acessing FTP hosts based on FUSE and libcurl. |http://curlftpfs.sourceforge.net/|{{Pkg|curlftpfs}}}}<br />
* {{App|fuseftp|FTP filesystem written in Perl, using FUSE|http://freshmeat.net/projects/fuseftp/|{{AUR|fuseftp}}}}<br />
* {{App|lftp|Sophisticated command line based FTP client|http://lftp.yar.ru/|{{Pkg|lftp}}}}<br />
* {{App|gftp|A multithreaded ftp client for X|http://gftp.seul.org/|{{Pkg|gftp}}}}<br />
* {{App|tnftp|[[Wikipedia:NetBSD|NetBSD]] FTP client with several advanced features|http://freecode.com/projects/tnftp|{{Pkg|tnftp}}}}<br />
Some file managers like [[Dolphin]], [[Nautilus]] and [[Thunar]] also provide FTP functionality.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Disable_clearing_of_boot_messages&diff=162619
Disable clearing of boot messages
2011-09-27T10:35:54Z
<p>Cantabile: /* Restoring /etc/issue */</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
{{i18n|Disable Clearing of Boot Messages}}<br />
[[fr:Messages au demarrage]]<br />
{{Article summary start|Summary}}<br />
{{Article summary text|Preventing the boot sequence printout from disappearing.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Arch Boot Process}}<br />
{{Article summary end}}<br />
<br />
After the boot process, the screen is cleared and the login prompt appears, leaving users unable to read init output and error messages. This default behavior may be modified using methods outlined in this article.<br />
<br />
Note that regardless of the chosen option, kernel messages can be displayed for inspection after booting by using {{Codeline|dmesg}}.<br />
<br />
{{Note|'''Given the recent change in agetty, the mandatory change is:'''<br />
add a {{Codeline|--noclear}} option to the call of agetty in {{Filename|/etc/inittab}} and also remove {{Filename|/etc/issue}} first line. See below}}<br />
<br />
==Using flow control==<br />
This is basic management that applies to most terminal emulators, including virtual consoles (vc):<br />
* Press {{Keypress|Ctrl}} + {{Keypress|S}} to pause the output<br />
* And {{Keypress|Ctrl}} + {{Keypress|Q}} to resume it<br />
<br />
==More permanent solution==<br />
For a more permanent change, the following can be used to add a pause or wait for keypress while boot messages are still on the screen:<br />
<br />
* Wait for a keypress before clearing the screen:<br />
read -n1<br />
* Wait for at most 5 seconds or until a keypress occurs:<br />
read -t5 -n1<br />
<br />
Add one of these to either the bottom of {{Filename|/etc/rc.local}} to pause when booting is finished, or the stat_fail() function in {{Filename|/etc/rc.d/functions}} to pause when a boot script in {{{Filename|/etc/rc.d}}} fails with an explicit error code. Note that the latter is a system script and may be overwritten when that file is updated. If you are unsure what this means, use {{Filename|/etc/rc.local}}.<br />
<br />
==Have boot messages stay on tty1==<br />
<br />
'''Normal behaviour:'''<br />
Boot messages shoot past, screen is cleared, contents of {{Filename|/etc/issue}} are displayed, login (either CLI or login manager) is displayed.<br />
<br />
'''Desired behaviour:'''<br />
Boot messages shoot past, login (either CLI or login manager) is displayed without clearing of tty1.<br />
<br />
First you should know that screen may be cleared:<br />
* by [[getty]];<br />
* due to control characters in {{Filename|/etc/issue}} because '''getty''' displays this file.<br />
I.e. to force desired behavior you should eliminate one/all of the above factors.<br />
<br />
===Disable clearing by getty===<br />
<br />
In {{Filename|/etc/inittab}}, you will find a list of numbered consoles which look something like the following; just scroll down in the file to find it. If you are using '''agetty''' or '''mingetty''' as '''getty''', add the {{Codeline|--noclear}} option for the first virtual console (the c1 line) only:<br />
c1:2345:respawn:/sbin/agetty '''--noclear''' -8 38400 tty1 linux<br />
c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux<br />
.<br />
.<br />
.<br />
<br />
===Disable clearing in /etc/issue===<br />
<br />
====Disable displaying of /etc/issue====<br />
<br />
Add the {{Codeline|--noissue}} option in {{Filename|/etc/inittab}}:<br />
c1:2345:respawn:/sbin/agetty '''--noissue''' -8 38400 tty1 linux<br />
<br />
Alternatively simply comment out the above line. <br />
{{Note|this way the login prompt does not appear, i.e. tty1 is locked.}}<br />
<br />
====Give tty1 a custom /etc/issue====<br />
<br />
Copy the existing {{Filename|/etc/issue}} file to {{Filename|/etc/issue.tty1}} (without the first line):<br />
sed 1d /etc/issue > /etc/issue.tty1<br />
<br />
Find this in {{Filename|/etc/inittab}}:<br />
c1:2345:respawn:/sbin/agetty -8 38400 tty1 linux<br />
<br />
Replace it with:<br />
c1:2345:respawn:/sbin/agetty -8 38400 tty1 linux -f /etc/issue.tty1<br />
<br />
====Edit /etc/issue directly====<br />
Simply cut the contents of the first line in {{Filename|/etc/issue}} so it looks like this:<br />
<br />
Arch Linux \r (\n) (\l)<br />
<br />
{{Warning|Read below how to restore the file before attempting this.}}<br />
<br />
=====Restoring /etc/issue=====<br />
The characters cannot be just typed again into the file because they are special characters '''not''' available on your keyboard!<br />
<br />
After you cut the contents from line 1 in {{Filename|/etc/issue}}, paste it into a temporary file somewhere on you computer so you can copy and paste it back into {{Filename|/etc/issue}} later when you wish to restore original functionality. You can also backup the whole {{Filename|/etc/issue}} somewhere safe and restore it when needed.<br />
<br />
Optionally, if you are more advanced, you can follow special procedures for typing in these special characters:<br />
<br />
Methods of placing literal escape characters are editor dependent. In [[Vim]]:<br />
<pre><br />
ESC (exit insert mode)<br />
:r !clear<br />
:x (Save and Exit)<br />
</pre><br />
This will insert the literal characters equivalent to the shell {{Codeline|clear}} command. Optionally you can also insert the characters manually: <br />
<pre><br />
i (insert)<br />
ctrl-v (insert literal character)<br />
ESC (insert escape character)<br />
c<br />
ESC (exit insert mode)<br />
ZZ (Save and Exit)<br />
</pre><br />
<br />
In [[Emacs]]:<br />
C-q ESC (to insert literal escape)<br />
<br />
Or you could just extract it from core/filesystem.<br />
<br />
== See Also ==<br />
*[[Inittab]]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Lightweight_Applications&diff=159597
Lightweight Applications
2011-09-13T16:27:33Z
<p>Cantabile: /* CD/DVD Burning Tools */ added cdw</p>
<hr />
<div>[[Category:Software (English)]]<br />
{{i18n|Lightweight Applications}}<br />
{{merge|List of Applications}}<br />
<br />
Provides a list of lightweight software for those who wish to use programs that require less computer resources.<br />
<br />
==Internet==<br />
===BitTorrent Clients===<br />
<!--Keep in sync with [[Common Applications]] and use the App template.--><br />
{{Wikipedia|Comparison of BitTorrent clients}}<br />
*{{App|[[aria2]]|Command-line download manager that supports HTTP/HTTPS, FTP, BitTorrent and MetaLink protocols|http://aria2.sourceforge.net/|{{Package Official|aria2}}}}<br />
*{{App|[[Wikipedia:QBittorrent|qBittorrent]]|The closest open source (GNU GPL v2 license) equivalent to µtorrent|http://qbittorrent.sourceforge.net/|{{Package Official|qbittorrent}}}}<br />
*{{App|[[rTorrent]]|Simple and lightweight ncurses BitTorrent client|http://libtorrent.rakshasa.no/|{{Package Official|rtorrent}}}}<br />
*{{App|[[Wikipedia:Transmission (BitTorrent client)|Transmission]]|Simple and easy-to-use BitTorrent client with (GTK+) GUI and CLI front-ends|http://www.transmissionbt.com/|{{Package Official|transmission}}}}<br />
<br />
===Email clients===<br />
<!--Keep in sync with [[Common Applications]] and use the App template.--><br />
{{Wikipedia|Comparison of e-mail clients}}<br />
====Console====<br />
*{{App|[[Alpine]]|The Apache-licensed PINE (a tool for reading, sending, and managing electronic messages)|http://www.washington.edu/alpine|{{Package Official|alpine}}}}<br />
*{{App|[[Wikipedia:Gnus|Gnus]]|mail, nntp, rss client for Emacs.|http://www.gnus.org/|[[package]]}}<br />
*{{App|[[Wikipedia:mailx|heirloom-mailx]]|A full-featured command-line MUA derived from Berkeley Mail.|http://heirloom.sourceforge.net/mailx.html|{{Package Official|mailx-heirloom}}}}<br />
*{{App|[[mutt]]|Small but very powerful text-based mail client.|http://www.mutt.org/|{{Package Official|mutt}}}}<br />
*{{App|[[Sup]]|A CLI mail client with very fast searching, tagging, threading and gmail like operation.|http://sup.rubyforge.org/|{{Package AUR|sup}}}}<br />
<br />
====X11====<br />
*{{App|[[Wikipedia:Claws Mail|Claws Mail]]|A GTK+ based e-mail client|http://www.claws-mail.org/|{{Package Official|claws-mail}}}}<br />
*{{App|[[Wikipedia:Gnus|Gnus]]|mail, nntp, rss client for Emacs.|http://www.gnus.org/|[[package]]}}<br />
*{{App|[[Wikipedia:Sylpheed|Sylpheed]]|Lightweight and user-friendly e-mail client (GTK)|http://sylpheed.sraoss.jp/en/|{{Package AUR|sylpheed}}}}<br />
*{{App|Postler|simple desktop mail client built in vala.|http://git.xfce.org/apps/postler|[[postler]]}}<br />
<br />
===Instant Messengers===<br />
<!--Use the App template.--><br />
{{Wikipedia|Comparison of instant messaging clients}}<br />
*{{App|[[Bitlbee]]|A way to use other IM to your [[#IRC]] client|http://www.bitlbee.org/|{{Package Official|bitlbee}}}}<br />
*{{App|Carrier|A fork of Pidgin with more options|http://funpidgin.sourceforge.net|{{Package AUR|carrier}}}}<br />
*{{App|[[Wikipedia:CenterIM|CenterIM]]|A curses based fork of Centericq which supports several protocols|http://www.centerim.org/|{{Package Official|centerim}}}}<br />
*{{App|[[Wikipedia:Emesene|Emesene]]|A Python/GTK+ instant messenger for the Windows Live Messenger network|http://www.emesene.org/|{{Package Official|emesene}}}}<br />
*{{App|Finch|A curses based version of Pidgin|http://developer.pidgin.im/wiki/Using%20Finch|{{Package Official|finch}}}}<br />
*{{App|[[Pidgin]]|A multiprotocol instant messenger|http://www.pidgin.im/|{{Package Official|pidgin}}}}<br />
*{{App|Pidgin Light|A light Pidgin version without gstreamer, tcl, tk, xscreensaver support|http://www.pidgin.im/|{{Package AUR|pidgin-light}}}}<br />
<br />
===IRC===<br />
<!--Use the App template.--><br />
{{Wikipedia|Comparison of Internet_Relay_Chat_clients}}<br />
*{{App|Conspire|Lightweight, simple, and powerful|http://nenolod.net/|{{Package AUR|conspire-client}}}}<br />
*{{App|[[Irssi]]|A modular text mode IRC client with Perl scripting|http://irssi.org/|{{Package Official|irssi}}}}<br />
*{{App|ERC|A powerful, modular, and extensible IRC client for [[Emacs]]|http://erc.sourceforge.net/|{{Package AUR|erc-git}}}}<br />
*{{App|II|A featherweight IRC client, literally `tail -f` the convo and `echo` back your replies|http://tools.suckless.org/ii|}}<br />
*{{App|Ircfs|A file system interface to irc written in [http://limbo.cat-v.org Limbo]|http://www.ueber.net/code/r/ircfs|}}<br />
*{{App|LostIRC|A simple IRC client|http://lostirc.sourceforge.net|{{Package AUR|lostirc}}}}<br />
*{{App|ScrollZ|An advanced IRC client based on ircII|http://www.scrollz.com|{{Package AUR|scrollz}}}}<br />
*{{App|[[WeeChat]]|A fast, light & extensible curses-based IRC client|http://weechat.org/|{{Package Official|weechat}}}}<br />
*{{App|[[Wikipedia:XChat|XChat]]|A GTK+ X client with Perl and Python scripting support|http://xchat.org|{{Package Official|xchat}}}}<br />
*{{App|pcw|A frontend for [http://tools.suckless.org/ii ii] that opens a new terminal for each channel (depends on [http://bitbucket.org/emg/srw srw] by default)|http://bitbucket.org/emg/pcw|}}<br />
*{{App|Loqui|A GTK IRC client with only one dependency|https://launchpad.net/loqui|{{Package AUR|loqui}}}}<br />
<br />
===News Aggregators===<br />
<!--Use the App template.--><br />
{{Wikipedia|Comparison of feed aggregators}}<br />
*{{App|[[Wikipedia:Canto_(news_aggregator)|Canto]]|A ncurses RSS aggregator|http://codezen.org/canto/|{{Package AUR|canto}}}}<br />
*{{App|[[Wikipedia:Gnus|Gnus]]|A mail, nntp, rss client for Emacs|http://www.gnus.org/|{{Package AUR|emacs-gnus-git}}}}<br />
*{{App|Newsbeuter|A ncurses RSS aggregator with layout and keybinding similar to mutt. Does not use the traditional 3 panes setup|http://www.newsbeuter.org/|{{Package Official|newsbeuter}}}}<br />
*{{App|Rawdog|A "RSS Aggregator Without Delusions Of Grandeur" that parses RSS/CDF/Atom feeds into a static HTML page of articles in date order|http://offog.org/code/rawdog.html|{{Package AUR|rawdog}}}}<br />
*{{App|Snownews|Text mode RSS newsreader|http://kiza.kcore.de/software/snownews/|{{Package Official|snownews}}}}<br />
<br />
===Web Browsers===<br />
<!--Use the App template.--><br />
{{Wikipedia|Comparison of web browsers}}<br />
*{{App|[[Wikipedia:Abaco (web browser)|Abaco]]|A multi-page graphical web browser|http://lab-fgb.com/abaco/|{{Package AUR|abaco}}}}<br />
*{{App|[[Wikipedia:Arora (browser)|Arora]]|A cross platform web browser built using Qt and WebKit|http://code.google.com/p/arora/|{{Package Official|arora}}}}<br />
*{{App|[[Wikipedia:Conkeror|Conkeror]]|A highly programmable web browser based on Mozilla XULRunner|http://conkeror.org/|{{Package Official|conkeror}}}}<br />
*{{App|[[Wikipedia:Dillo|Dillo]]|A small, fast graphical web browser built on FLTK|http://www.dillo.org/|{{Package Official|dillo}}}}<br />
*{{App|[[Wikipedia:ELinks|ELinks]]|An advanced and well-established feature-rich text mode web browser|http://elinks.or.cz/|{{Package Official|elinks}}}}<br />
*{{App|Hv3|A minimalist web browser based on tkhtml3|http://tkhtml.tcl.tk/hv3.html|{{Package AUR|hv3}}}}<br />
*{{App|[[Jumanji]]|A highly customizable and functional web browser|http://pwmt.org/projects/jumanji|{{Package AUR|jumanji}}}}<br />
*{{App|[[Wikipedia:Links (web browser)|Links]]|A text WWW browser, similar to Lynx|http://links.twibright.com/|{{Package Official|links}}}}<br />
*{{App|Luakit| A highly configurable, micro-browser framework based on the WebKit web content engine and the GTK+ toolkit. It is very fast, extensible by Lua and licensed under the GNU GPLv3 license|http://luakit.org/projects/luakit/|{{Package Official|luakit}}}}<br />
*{{App|[[Wikipedia:Midori (web browser)|Midori]]| A lightweight web browser based on Gtk and WebKit. It passes the ACID3 test|http://www.twotoasts.de/index.php?/pages/midori_summary.html|{{Package Official|midori}}}}<br />
*{{App|[[Wikipedia:NetSurf|NetSurf]]| A featherweight browser written in C. Notable is its lack of JavaScript support and fast rendering through its own custom rendering engine|http://www.netsurf-browser.org Netsurf|{{Package Official|netsurf}}}}<br />
*{{App|Sb|A very lightweight webkit-based browser that uses keybindings to perform most things the URL bar would usually do|https://github.com/mutantturkey/sb/|{{Package AUR|sb-git}}}} <br />
*{{App|Surf|Another lightweight WebKit-based browser, which follows the [[suck less philosophy|suckless ideology]]. Which means, the software is even more lightweight (basically, the browser itself is a single C source file)|http://surf.suckless.org|{{Package AUR|surf-hg}}}}<br />
*{{App|[[Wikipedia:Uzbl|Uzbl]]|Web interface tools which adhere to the unix philosophy|http://www.uzbl.org/|{{Package Official|uzbl-browser}}}}<br />
*{{App|[[Vimprobable]]|A browser that behaves like the Vimperator plugin available for Mozilla Firefox. It is based on the WebKit engine (using GTK bindings)|http://vimprobable.org/|{{Package AUR|vimprobable}}}}<br />
<br />
==Multimedia==<br />
===Audio Players===<br />
<!--Use the App template.--><br />
{{Wikipedia|Comparison of audio player software}}<br />
*{{App|[[Wikipedia:cmus|cmus]]|A very feature-rich ncurses-based music player|http://cmus.sourceforge.net/|{{Package Official|cmus}}}}<br />
*{{App|DeaDBeeF|A light and fast music player with many features, no GNOME or KDE dependencies, supports console-only and as well GTK2-gui, comes with many plugins, and has a metadata editor|http://deadbeef.sourceforge.net/|{{Package Official|deadbeef}}}}<br />
*{{App|cplay|A curses front-end for various audio players|http://sourceforge.net/projects/cplay/{{Linkrot|2011|09|04}}|{{Package AUR|cplay}}}}<br />
*{{App|[[Goggles Music Manager]]|A music collection manager and player that automatically categorizes your music, supports gapless playback, features easy tag editing, and internet radio support|http://code.google.com/p/gogglesmm/|{{Package Official|gogglesmm}}}}<br />
*{{App|Herrie|A minimalistic console-based music player with native AudioScrobbler support|http://herrie.info/|{{Package AUR|herrie}}}}<br />
*{{App|[[Moc]]|A ncurses console audio player with support for the MP3, Ogg, and WAV formats|http://moc.daper.net/|{{Package Official|moc}}}}<br />
*{{App|Potamus|A lightweight, intuitive GTK+ audio player with an emphasis on high audio quality|http://offog.org/code/potamus.html|{{Package AUR|potamus}}}}<br />
*{{App|Pragha|A GTK+ music manager that was a fork of Consonance Music Manager|http://pragha.wikispaces.com/|{{Package Official|pragha}}}}<br />
*{{App|[[Wikipedia:Mpg123|Mpg123]]|A fast free MP3 console audio player for Linux, FreeBSD, Solaris, Hpux and near all other UNIX systems. Also decodes mp1 and mp2 files|http://www.mpg123.de/|{{Package Official|mpg123}}}}<br />
<br />
[[mpd|MPD]] clients:<br />
<br />
*{{App|Ario|A very feature-rich GTK2 client for [[mpd]], inspired by Rhythmbox|http://ario-player.sourceforge.net/|{{Package Official|ario}}}}<br />
*{{App|ncmpc|A curses client for [[mpd]]|http://mpd.wikia.com/wiki/Client:Ncmpc|{{Package Official|ncmpc}}}}<br />
*{{App|ncmpcpp|An almost exact clone of ncmpc with some new features|http://unkart.ovh.org/ncmpcpp/|{{Package Official|ncmpcpp}}}}<br />
*{{App|QmpdClient|A Qt4 based mpd client|http://bitcheese.net/wiki/QMPDClient|{{Package Official|qmpdclient}}}}<br />
*{{App|Sonata|An elegant GTK+ music client for [[mpd]]|http://sonata.berlios.de/|{{Package Official|sonata}}}}<br />
<br />
===Image Editors===<br />
<!--Use the App template.--><br />
*{{App|mtPaint|A a graphic editing program geared towards creating indexed palette images and pixel art|http://mtpaint.sourceforge.net/|{{Package Official|mtpaint}}}}<br />
<br />
===Image Viewers===<br />
<!--Keep in sync with [[Common Applications]] and use the App template.--><br />
{{Wikipedia|Comparison of image viewers}}<br />
*{{App|[[Feh]]|A fast, lightweight image viewer that uses imlib2|http://feh.finalrewind.org/|{{Package Official|feh}}}}<br />
*{{App|GpicView|A simple and fast image viewer for X. Made by the developers of [[LXDE]]|http://lxde.sourceforge.net/gpicview/|{{Package Official|gpicview}}}}<br />
*{{App|[[Wikipedia:GQview|GQview]]|An image browser that features single click access to view images and move around the directory tree|http://gqview.sourceforge.net/|{{Package Official|gqview}}}}<br />
*{{App|Geeqie|An image browser/viewer fork of GQview. Adds additional functionality such as support for RAW files|http://geeqie.sourceforge.net/|{{Package Official|geeqie}}}}<br />
*{{App|Mirage|PyGTK image viewer featuring support for crop and resize, custom actions and a thumbnail panel|http://mirageiv.berlios.de|{{Package Official|mirage}}}}<br />
*{{App|Ristretto|A fast and lightweight picture-viewer for the Xfce desktop environment|http://goodies.xfce.org/projects/applications/ristretto|{{Package Official|ristretto}}}}<br />
*{{App|QIV|A very small and fast gdk/Imlib image viewer|http://spiegl.de/qiv/|{{Package Official|qiv}}}}<br />
*{{App|Viewnior|Minimalistic GTK2 viewer featuring support for flip, rotate, animations and configurable mouse actions|http://xsisqox.github.com/Viewnior/about.html|{{Package Official|viewnior}}}}<br />
*{{App|Xloadimage|The classic X image viewer|http://web.archive.org/web/19981207030422/http://world.std.com/~jimf/xloadimage.html|{{Package Official|xloadimage}}}}<br />
*{{App|SXIV|Simple X Image Viewer; works well with tiling window managers, uses imlib2|http://github.com/muennich/sxiv|{{Package AUR|sxiv}}}}<br />
<br />
===Video Players===<br />
<!--Use the App template.--><br />
{{Wikipedia|Comparison of video player software}}<br />
*{{App|Gnome-Mplayer|A simple GTK-based GUI for [[mplayer]]|http://kdekorte.googlepages.com/gnomemplayer|{{Package Official|gnome-mplayer}}}}<br />
*{{App|[[mplayer]]|Support a complete and versatile array of video/audio formats|http://www.mplayerhq.hu/design7/news.html|{{Package Official|mplayer}}}}<br />
*{{App|[[Wikipedia:SMPlayer|SMPlayer]]|A middleweight QT frontend for mplayer with additional patches|http://smplayer.sourceforge.net/|{{Package Official|smplayer}}}}<br />
*{{App|[[Wikipedia:VLC media player|VLC media player]]|A middleweight video player with support for a wide variety of audio/video formats|http://www.videolan.org/vlc/|{{Package Official|vlc}}}}<br />
*{{App|Xnoise|A GTK+ media player for both audio and video with "a slick GUI, great speed and lots of features.". Uses gstreamer.|http://www.xnoise-media-player.com/|{{Package AUR|xnoise}}}}<br />
<br />
==Office==<br />
===Calendars===<br />
<!--Use the App template.--><br />
*{{App|Pal|A very lightweight calendar with both interactive and non-interactive interfaces|http://palcal.sourceforge.net/|{{Package AUR|pal}}}}<br />
*{{App|Calcurse|A text-based curses calendar and scheduling system|http://calcurse.org/|{{Package Official|calcurse}}}}<br />
*{{App|Remind|A highly sophisticated text-based calendaring and notification system|http://www.roaringpenguin.com/products/remind|{{Package Official|remind}}}}<br />
*{{App|Wyrd|A curses front-end to Remind|http://pessimization.com/software/wyrd/|{{Package Official|wyrd}}}}<br />
*{{App|wxRewind|A Python text and graphical frontend to Remind|http://www.duke.edu/~dgraham/wxRemind/|{{Package AUR|wxremind}}}}<br />
*{{App|etm|Event and Task Manager. A "Getting Things Done" approach handling events, tasks, activities, reminders and projects|http://www.duke.edu/~dgraham/ETM/|{{Package AUR|etm}}}}<br />
<br />
===PDF Tools===<br />
<!--Use the App template.--><br />
*{{App|apvlv|A lightweight PDF viewer with VIM key bindings|http://code.google.com/p/apvlv/|{{Package Official|apvlv}}}}<br />
*{{App|ePDFView|A free lightweight PDF document viewer using Poppler and GTK+ libraries|http://www.emma-soft.com/projects/epdfview/|{{Package Official|epdfview}}}}<br />
*{{App|llpp|A very fast PDF reader based off of MuPDF, that supports continuous page scrolling, bookmarking, and text search through the whole document|http://repo.or.cz/w/llpp.git|{{Package AUR|llpp}}}}<br />
*{{App|MuPDF|A very fast PDF viewer and toolkit written in portable C. Features CJK font support|http://ccxvii.net/mupdf|{{Package Official|mupdf}}}}<br />
*{{App|Xpdf|A viewer for Portable Document Format (PDF) files|http://www.foolabs.com/xpdf/|{{Package Official|xpdf}}}}<br />
*{{App|zathura|Another lightweight PDF viewer similar to apvlv, only lighter|http://zathura.pwmt.org/projects/zathura|{{Package Official|zathura}}}}<br />
<br />
===Text Editors===<br />
<!--Use the App template.--><br />
{{Wikipedia|Comparison of text editors}}<br />
*{{App|[[Wikipedia:Acme (text editor)|Acme]]|A minimalist and flexible programming environment by Rob Pike|http://acme.cat-v.org|}}<br />
*{{App|[[Beaver]]|An Early AdVanced EditoR|http://www.nongnu.org/beaver/|{{Package Official|beaver}}}}<br />
*{{App|[[Wikipedia:Geany|Geany]]|A text editor using the GTK+ 2 toolkit with basic features of an integrated development environment|http://www.geany.org|{{Package Official|geany}}}}<br />
*{{App|Edile|A PyGTK code/scripting editor implemented in one file|http://edile.googlecode.com|{{Package AUR|edile}}}}<br />
*{{App|Leafpad|A notepad clone for GTK+ 2.x that emphasizes simplicity|http://tarot.freeshell.org/leafpad/|{{Package Official|leafpad}}}}<br />
*{{App|medit|A lightweight IDE text editor featuring support for tabs, sessions, plugins and syntax highlighting|http://mooedit.sourceforge.net/|{{Package Official|medit}}}}<br />
*{{App|[[nano]]|A console text editor with on-screen key binding help, a free clone of pico|http://www.nano-editor.org/|{{Package Official|nano}}}}<br />
*{{App|[[Wikipedia:PyRoom|PyRoom]]|A great distractionless PyGTK text editor, a clone of the infamous WriteRoom|http://pyroom.org/|{{Package AUR|pyroom}}}}<br />
*{{App|[[Wikipedia:Sam (text editor)|Sam]]|A graphical text editor by Rob Pike (still used by Ken Thompson and others)|http://sam.cat-v.org|}}<br />
*{{App|[[Vim]]|The improved classic vi text editor|http://www.vim.org/|{{Package Official|vim}}}}<br />
<br />
===Word processors===<br />
<!--Use the App template.--><br />
{{Wikipedia|Comparison of word processors}}<br />
*{{App|[[Abiword]]|A full-featured word processor|http://www.abisource.com/|{{Package Official|abiword}}}}<br />
*{{App|Abiword Light|A lighter version of Abiword|http://www.abisource.com/|{{Package AUR|abiword-light}}}}<br />
*{{App|[[Wikipedia:Markdown|Markdown]]|A text-to-HTML conversion tool that allows you to write using a simple plain text format|http://daringfireball.net/projects/markdown|{{Package AUR|markdown}}}}<br />
*{{App|pandoc|A swiss-army knife for converting one markup format into another (supports Markdown)|http://johnmacfarlane.net/pandoc|{{Package AUR|pandoc}}}}<br />
*{{App|[[Wikipedia:Txt2tags|txt2tags]]|A dead-simple, KISS-compliant lightweight, human-readable markup language to produce rich format content out of plain text files|http://txt2tags.sourceforge.net|{{Package AUR|txt2tags}}}}<br />
<br />
===Todo List Managers===<br />
<!--Use the App template.--><br />
*{{App|[[Wikipedia:Org-mode|org-mode]]|An [[Emacs]] Mode for Notes, Project Planning, and Authoring|http://orgmode.org|{{Package AUR|emacs-org-mode}}}}<br />
*{{App|todo.txt|Manages your Todo list from the command line|http://ginatrapani.github.com/todo.txt-cli/|{{Package AUR|todotxt}}}}<br />
*{{App|Taskwarrior|Another cli todo list application with support for lua customization and more|http://taskwarrior.org|Available in the community repository as "tasks".}}<br />
<br />
==System==<br />
===File Managers===<br />
<!--Use the App template.--><br />
{{Wikipedia|Comparison of file managers}}<br />
*{{App|[[Wikipedia:Emelfm2|emelFM2]]|A file manager that implements the popular two-panel design|http://emelfm2.net/|{{Package Official|emelfm2}}}}<br />
*{{App|[[Wikipedia:Midnight commander|Midnight Commander]]|A console-based, dual-paned, file manager|http://www.midnight-commander.org|{{Package Official|mc}}}}<br />
*{{App|[[PCManFM]]|A lightweight file manager which features tabbed browsing and can optionally manage the desktop background|http://pcmanfm.sourceforge.net/|{{Package Official|pcmanfm}}}}<br />
*{{App|[[Ranger]]|A console based file manager with vi bindings, customizability, and lots of features|http://nongnu.org/ranger|{{Package Official|ranger}}}}<br />
*{{App|ROX-Filer|A small and fast file manager which can optionally manage the desktop background and panels|http://rox.sourceforge.net|{{Package Official|rox}}}}<br />
*{{App|[[Thunar]]|Can be run as a daemon with excellent start up and directory load times. Features support for customizable actions|http://thunar.xfce.org/index.html|{{Package Official|thunar}}}}<br />
*{{App|[[Vifm]]|A ncurses based two-pane file manager with vi like keybindings|http://vifm.sourceforge.net/|{{Package Official|vifm}}}}<br />
*{{App|[[Wikipedia:Xfe|Xfe]]|A MS-Explorer or Commander like file manager for X|http://roland65.free.fr/xfe/index.php/|{{Package Official|xfe}}}}<br />
*{{App|qtfm|A small, lightweight filemanager for Linux desktops based on pure Qt and works great with minimal desktop environments like Openbox|http://www.qtfm.org/|{{Package Official|qtfm}}}}<br />
<br />
===GUI Data Compression Tools===<br />
<!--Use the App template.--><br />
{{Wikipedia|Comparison of file archivers}}<br />
*{{App|Xarchive|A GTK+ 2 front-end for various command line archiving tools|http://xarchive.sourceforge.net|{{Package AUR|xarchive}}}}<br />
*{{App|[[Wikipedia:Xarchiver|Xarchiver]]|A lightweight desktop independent archive manager built with GTK+ 2. At the time of writing, it appears to be the most functional and up to date of the three tools listed here|http://xarchiver.sourceforge.net/|{{Package Official|xarchiver}}}}<br />
<br />
===CD/DVD Burning Tools===<br />
<!--Use the App template.--><br />
{{Wikipedia|Comparison of disc authoring software}}<br />
*{{App|recorder|Simple frontend to cdrkit/cdrtools, cdrdao, mkisofs and growisofs with limited options and preferences|http://code.google.com/p/recorder/|{{Package Official|recorder}}}}<br />
*{{App|Xfburn|Simple frontend to the libburnia libraries with support for CD/DVD(-RW), ISO images and BurnFree|http://www.xfce.org/projects/xfburn/|{{Package Official|xfburn}}}}<br />
*{{App|cdw|Ncurses frontend to cdrecord, mkisofs, growisofs, dvd+rw-mediainfo, dvd+rw-format, xorriso.|http://cdw.sourceforge.net/|{{Package AUR|cdw}}}}<br />
<br />
===Login managers===<br />
<!--Use the App template.--><br />
*{{App|[[CDM]]|An ultra-minimalistic, yet full-featured login manager written in bash|http://cdm.ghost1227.com/|{{Package AUR|cdm}}}}<br />
*{{App|[[SLiM]]|A lightweight and elegant graphical login solution|http://slim.berlios.de/|{{Package Official|slim}}}}<br />
*{{App|[[Qingy]]|An ultralight and very configurable graphical login independent on X Windows|http://qingy.sourceforge.net/|{{Package Official|qingy}}}}<br />
<br />
===Monitors===<br />
<!--Use the App template.--><br />
*{{App|[[Conky]]|A lightweight, scriptable system monitor|http://conky.sourceforge.net/|{{Package Official|conky}}}}<br />
*{{App|[[Wikipedia:Htop|Htop]]|A simple, ncurses interactive process viewer|http://htop.sourceforge.net/|{{Package Official|htop}}}}<br />
*{{App|LXTask|A lightweight task manager for [[LXDE]]|http://wiki.lxde.org/en/LXTask|{{Package Official|lxtask}}}}<br />
<br />
===Panels===<br />
<!--Use the App template.--><br />
*{{App|[[Bmpanel]]|A lightweight, NETWM compliant panel for the X11 system|http://nsf.110mb.com/bmpanel/|{{Package Official|bmpanel}}}}<br />
*{{App|fbpanel|A lightweight, NETWM compliant desktop panel|http://fbpanel.sourceforge.net|{{Package Official|fbpanel}}}}<br />
*{{App|LXPanel|A lightweight X11 desktop panel (part of [[LXDE]])|http://lxde.org/|{{Package Official|lxpanel}}}}<br />
*{{App|[[PyPanel]]|A lightweight panel/taskbar written in Python and C|http://pypanel.sourceforge.net/|{{Package Official|pypanel}}}}<br />
*{{App|[[Tint2]]|A simple panel/taskbar intentionally made for openbox3, but should also work with other window managers|http://code.google.com/p/tint2/|{{Package Official|tint}}}}<br />
*{{App|pancake|A highly configurable, modular panel for X|http://www.failedprojects.de/pancake/|{{Package AUR|pancake}}}}<br />
*{{App|qtpanel|A project to create useful and beautiful panel in Qt|https://bbs.archlinux.org/viewtopic.php?id&#61;117528|{{Package AUR|qtpanel-git}}}}<br />
<br />
===Terminals===<br />
<!--Use the App template.--><br />
*{{App|[[LilyTerm]]|A light and easy to use libvte based X Terminal Emulator|http://lilyterm.luna.com.tw/|{{Package Official|lilyterm}}}}<br />
*{{App|ROXTerm|A tabbed, VTE-based terminal emulator with a small footprint|http://rox.sourceforge.net|{{Package Official|roxterm}}}}<br />
*{{App|[[urxvt]]|A highly extendable unicode enabled rxvt-clone terminal emulator featuring tabbing, url launching, quake-style dropdown, pseudo-transparency, and is extensible with perl|http://software.schmorp.de/pkg/rxvt-unicode|{{Package Official|rxvt-unicode}}}}<br />
*{{App|Sakura|A terminal emulator based on GTK+ and VTE|http://www.pleyades.net/david/sakura.php|{{Package Official|sakura}}}}<br />
*{{App|[[Xterm]]|A terminal emulator for the X Window System|http://invisible-island.net/xterm/|{{Package Official|xterm}}}}<br />
*{{App|[[Wikipedia:Tilda (software)|Tilda]]|A Linux terminal taking after the likeness of many classic terminals from first person shooter games, Quake, Doom and Half-Life (to name a few), where the terminal has no border and is hidden from the desktop until a key is pressed|http://sourceforge.net/projects/tilda/files/|{{Package Official|tilda}}}}<br />
*{{App|[[Stjerm]]|is a GTK+-based drop-down terminal emulator. Stjerm sets itself apart from similar programs by providing a minimalistic interface combined with a small file size, lightweight memory usage and easy integration with composite window managers such as Compiz. |http://code.google.com/p/stjerm-terminal-emulator/downloads/list|}}<br />
<br />
===Trays===<br />
<!--Use the App template.--><br />
*{{App|Docker|A docking application which acts as a system tray|http://icculus.org/openbox/2/docker/|{{Package Official|docker}}}}<br />
*{{App|[[Stalonetray]]|A stand-alone system tray|http://stalonetray.sourceforge.net|{{Package Official|stalonetray}}}}<br />
*{{App|Trayer|Swallows GTK+ 1.2/2.x application docklets, and KDE docklets|http://gna.org/projects/fvwm-crystal/|{{Package Official|trayer}}}}<br />
<br />
==Links==<br />
*[https://bbs.archlinux.org/viewtopic.php?id=88515 Arch Linux Forums / LnF Awards 2010] - The best Light & Fast apps of 2010.<br />
*[https://bbs.archlinux.org/viewtopic.php?id=111878 Arch Linux Forums / LnF Awards 2011] - The best Light & Fast apps of 2011.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Systemd&diff=142539
Systemd
2011-05-23T18:45:54Z
<p>Cantabile: /* FAQ */ removed two questions about syslog messages showing up in dmesg - systemd support in syslog-ng >=3.2.3 should make those questions obsolete</p>
<hr />
<div>{{i18n|Systemd}}<br />
[[fr:Systemd]]<br />
<br />
[[Category: Daemons and system services (English)]]<br />
systemd is a system and service manager for Linux, compatible with SysV and LSB init scripts. systemd provides aggressive parallelization capabilities, uses socket and [[D-Bus]] activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux [[cgroups]], supports snapshotting and restoring of the system state, maintains mount and automount points and implements an elaborate transactional dependency-based service control logic. It can work as a drop-in replacement for sysvinit.<br />
<br />
See [http://0pointer.de/blog/projects/systemd.html Lennart's blog story] for a longer introduction, the two [http://0pointer.de/blog/projects/systemd-update.html status] [http://0pointer.de/blog/projects/systemd-update-2.html updates] since then, and the [http://0pointer.de/blog/projects/why.html most recent summary]. Also see the [http://en.wikipedia.org/wiki/Systemd Wikipedia article] and the [http://freedesktop.org/wiki/Software/systemd project web page].<br />
<br />
== Installation ==<br />
<br />
To try out systemd on Arch you need to<br />
<br />
* install initscripts-systemd (and its dependencies) from community<br />
* append init=/bin/systemd to the end of your kernel line in GRUB.<br />
<br />
Note that systemd can be installed side-by-side with the regular Arch initscripts, and they can be toggled by adding/removing the init=/bin/systemd kernel parameter.<br />
<br />
* To take advantage of the systemd way of starting services, you might also want the systemd-arch-units package.<br />
<br />
{{Warning|systemd does not support /usr on a separate partition. You will not be able to boot without libdbus accessible on the root partition.}}<br />
<br />
== Using systemd ==<br />
<br />
*systemctl: used to introspect and control the state of the systemd system and service manager<br />
*systemd-cgls: recursively shows the contents of the selected Linux control group hierarchy in a tree<br />
*systemadm: a graphical frontend for the systemd system and service manager that allows introspection and control of systemd.<br />
<br />
View the man pages for more details. <br />
<br />
Listing running services<br />
<br />
{{cli|$ systemctl}}<br />
<br />
or<br />
<br />
{{cli|$ systemctl list-units}}<br />
<br />
The available services or units can be seen in /lib/systemd/system and /etc/systemd/system (the latter takes precedence).<br />
<br />
Activates a service immediately:<br />
<br />
{{cli|# systemctl start <service>}}<br />
<br />
Deactivates a service immediately:<br />
<br />
{{cli|# systemctl stop <service>}}<br />
<br />
Restarts a service:<br />
<br />
{{cli|# systemctl restart <service>}}<br />
<br />
Reloads a service:<br />
<br />
{{cli|# systemctl reload <service>}}<br />
<br />
Shows status of a service including whether it is running or not:<br />
<br />
{{cli|# systemctl status <service>}}<br />
<br />
Enables a service to be started on bootup:<br />
<br />
{{cli|# systemctl enable <service>}}<br />
<br />
Disables a service to not start during bootup:<br />
<br />
{{cli|# systemctl disable <service>}}<br />
<br />
Refer to man systemctl for more details. <br />
<br />
Notice that you need to use the full name of a service file. E.g., in order to restart the avahi daemon, issue:<br />
<br />
{{cli|# systemctl restart avahi-daemon.service}}<br />
<br />
Shut down and reboot the system <br />
<br />
{{cli|# systemctl reboot}}<br />
<br />
=== Runlevels/targets ===<br />
<br />
Systemd has a concept of ''targets'' which serve a similar purpose as runlevels but act a little different. Each ''target'' is named instead of numbered and is intended to serve a specific purpose. Some ''targets'' are implemented by inheriting all of the services of another ''target'' and adding additional services to it. There are systemd ''target''s that mimic the common SystemVinit runlevels so you can still switch ''target''s using the familiar <code>telinit RUNLEVEL</code> command. The runlevels that are assigned a specific purpose on vanilla Fedora installs; 0, 1, 3, 5, and 6; have a 1:1 mapping with a specific systemd ''target''. Unfortunately, there's no good way to do the same for the user-defined runlevels like 2 and 4. If you make use of those it is suggested that you make a new named systemd ''target'' as <code>/etc/systemd/system/$YOURTARGET</code> that takes one of the existing runlevels as a base (you can look at <code>/lib/systemd/system/graphical.target</code> as an example), make a directory <code>/etc/systemd/system/$YOURTARGET.wants</code>, and then symlink the additional services that you want to enable into that directory. (The service unit files that you symlink live in <code>/lib/systemd/system</code>).<br />
<br />
{| border="1"<br />
!SystemVinit Runlevel!!Systemd Target!!Notes<br />
|-<br />
| 0 || runlevel0.target, poweroff.target || Halt the system.<br />
|-<br />
| 1, s, single || runlevel1.target, rescue.target || Single user mode.<br />
|-<br />
| 2, 4 || runlevel2.target, runlevel4.target, multi-user.target || User-defined/Site-specific runlevels. By default, identical to 3.<br />
|-<br />
| 3 || runlevel3.target, multi-user.target || Multi-user, non-graphical. Users can usually login via multiple consoles or via the network.<br />
|-<br />
| 5 || runlevel5.target, graphical.target || Multi-user, graphical. Usually has all the services of runlevel 3 plus a graphical login.<br />
|-<br />
| 6 || runlevel6.target, reboot.target || Reboot<br />
|-<br />
| emergency || emergency.target || Emergency shell<br />
|-<br />
|}<br />
<br />
Changing runlevels:<br />
<br />
{| border="1"<br />
!SystemVinit Command!!Systemd Command!!Notes<br />
|-<br />
| telinit 3 || systemctl isolate multi-user.target (OR systemctl isolate runlevel3.target OR telinit 3) || Change to multi-user run level.<br />
|-<br />
| sed s/^id:.*:initdefault:/id:3:initdefault:/ || ln -sf /lib/systemd/system/multi-user.target /etc/systemd/system/default.target || Set to use multi-user runlevel on next reboot.<br />
|}<br />
<br />
=== Running DEs under systemd ===<br />
<br />
To enable graphical login run your preferred [[Display Manager]] daemon (e.g. [[KDM]]). At the moment service files exist for gdm, kdm and slim, but there isn't one for xdm.<br />
<br />
{{cli|# systemctl enable kdm.service}}<br />
<br />
This should work out of the box. If not, you might have a default.target set manually or from a older install:<br />
<br />
{{Command|command=ls -l /etc/systemd/system/default.target|output=/etc/systemd/system/default.target -> /lib/systemd/system/graphical.target|prompt=#}}<br />
<br />
simply delete the symlink and systemd will use its stock default.target i.e. graphical.target.<br />
<br />
{{cli|# rm /etc/systemd/system/default.target}}<br />
<br />
On KDE start an error message will appear saying "console-kit-daemon.unit" could not be found. To solve this problem install systemd-arch-units.<br />
<br />
== Arch integration ==<br />
<br />
Integration with Arch's classic configuration is accomplished via the initscripts-systemd package. This is an optional package which can be used to ease the transition from sysVinit to systemd.<br />
<br />
/etc/inittab is not used at all.<br />
<br />
/etc/rc.local and /etc/rc.local.shutdown can be run at startup and shutdown by enabling rc-local.service.<br />
<br />
Some variables in /etc/rc.conf are respected by this glue work. For a pure systemd setup it is recommended to use the native systemd configuration files (such as /etc/locale.conf, /etc/vconsole.conf, /etc/hostname, /etc/modules-load.d/*.conf) which will take precedence over /etc/rc.conf.<br />
<br />
=== Supported ===<br />
<br />
* LOCALE<br />
* KEYMAP<br />
* CONSOLEFONT<br />
* CONSOLEMAP<br />
* HOSTNAME (this and all above is parsed at boot-time, the native systemd configuration takes presedence) <br />
* TIMEZONE (set at shutdown)<br />
* MODULES (blacklisting is respected)<br />
* DAEMONS (ordering and blacklisting is respected, if a native systemd service file by the same name as a daemon exists, it will take precedence, this logic can be disabled by 'systemctl disable arch-daemons.target')<br />
<br />
=== Not supported ===<br />
<br />
* HARDWARECLOCK (use 'hwclock --systohc --utc' to set your hardware clock to utc, localtime is not supported, see [[Systemd#Why_does_systemd_not_support_the_RTC_being_in_localtime.3F|FAQ]])<br />
* USELVM (use lvm.service provided by initscripts-systemd instead)<br />
* USECOLOR<br />
<br />
== The initscripts-systemd package ==<br />
<br />
This package contains unit files and scripts that are needed to emulate Arch's initscripts. Most people will not need all (if any) of these units, and they can be easily disabled by doing<br />
{{cli|# systemctl disable <unitfile>}}<br />
if you determine that you don't want a particular unit.<br />
<br />
The plan is to remove most of the functionality from this package as soon as it is handled elsewhere (mostly in udev/systemd/kernel).<br />
<br />
The following is a brief description of the functionality of each of them.<br />
<br />
* '''lvm.service'''<br />
:Copies Arch's handling of LVM. Only needed if you use non-root LVM. In the future systemd will probably deal with this natively (in a much cleaner and more robust way).<br />
* '''rc-local.service'''<br />
:Runs /etc/rc-local (resp., /etc/rc-local.shutdown) on boot (resp., shutdown).<br />
* '''arch-daemons.target'''<br />
:Parses the DAEMONS array in rc.conf and starts the services. If a native systemd unit exists (by the same name) for a given daemon, this is used, otherwise the script in /etc/rc.d/ is used to control the unit.<br />
* '''arch-persistent-settings.service'''<br />
:This is run at shutdown, it's aim is to make sure that any Arch settings is applied on next boot. In particular:<br />
:* sets the timezone based on rc.conf<br />
:* updates module blacklists based on rc.conf (see /etc/modprobe.d/rc.conf)<br />
:* updates list of modules to be loaded based on rc.conf (see /etc/modules-load.d/rc.conf)<br />
<br />
== Native systemd configuration files ==<br />
<br />
*Add a hostname<br />
{{File|name=/etc/hostname|content=myhostname}}<br />
*Console and keymap settings<br />
:The /etc/vconsole.conf file configures the virtual console, i.e. keyboard mapping and console font.<br />
{{File|name=/etc/vconsole.conf|content=<br />
<nowiki><br />
KEYMAP=us<br />
FONT=lat9w-16<br />
FONT_MAP=8859-1_to_uni</nowiki><br />
}}<br />
*OS info<br />
:/etc/os-release contains data that is defined by the operating system vendor and should not be changed by the administrator.<br />
{{File|name=/etc/os-release|content=<br />
<nowiki><br />
NAME=Archlinux<br />
ID=arch<br />
PRETTY_NAME=Arch GNU/Linux<br />
ANSI_COLOR=1;34</nowiki><br />
}}<br />
* Locale settings (read man locale.conf for more options) <br />
{{File|name=/etc/locale.conf|content=<br />
<nowiki><br />
LANG=en_US.utf8<br />
LC_COLLATE=C<br />
</nowiki><br />
}}<br />
* Configure kernel modules to load during boot<br />
:systemd uses /etc/modules-load.d/ to configure kernel modules to load during boot in a static list. Each configuration file is named in the style of /etc/modules-load.d/<program>.conf. The configuration files should simply contain a list of kernel module names to load, separated by newlines. Empty lines and lines whose first non-whitespace character is # or ; are ignored. Example:<br />
{{File|name=/etc/modules-load.d/virtio-net.conf|content=<br />
<nowiki><br />
# Load virtio-net.ko at boot<br />
virtio-net<br />
</nowiki><br />
}}<br />
* Configure kernel modules blacklist<br />
:systemd uses /etc/modprobe.d/ to configure kernel modules blacklist. Each configuration file is named in the style of //etc/modprobe.d/<program>.conf. Empty lines and lines whose first non-whitespace character is # or ; are ignored. Example:<br />
{{File|name=/etc/modprobe.d/snd_hda_intel|content=<br />
<nowiki><br />
blacklist snd_hda_intel<br />
</nowiki><br />
}}<br />
or<br />
{{File|name=/etc/modprobe.d/snd_hda_intel|content=<br />
<nowiki><br />
install snd_hda_intel /bin/false<br />
</nowiki><br />
}}<br />
* Describe temporary files<br />
:systemd-tmpfiles uses the configuration files in /etc/tmpfiles.d/ to describe the creation, cleaning and removal of volatile and temporary files and directories which usually reside in directories such as /run or /tmp. Each configuration file is named in the style of /etc/tmpfiles.d/<program>.conf.<br />
<br />
== Helping out ==<br />
<br />
Currently, systemd is mostly at feature parity with Arch's initscripts. However, a lot more testing is needed. If you'd like to help out, you can fork the [http://github.com/falconindy/initscripts-systemd initscripts-systemd] or [http://github.com/falconindy/systemd-arch-units systemd-arch-units] git repos and submit pull requests for your additions.<br />
<br />
If you have any questions, ask in the [https://bbs.archlinux.org/viewtopic.php?id=96316&p=1 thread] in the Arch forums. falconindy is also somewhat available on IRC in #archlinux (please, no private messages).<br />
<br />
== FAQ ==<br />
<br />
For an up-to-date list of known issues, look at the upstream [http://cgit.freedesktop.org/systemd/tree/TODO TODO].<br />
<br />
=== Why are my console fonts ugly? ===<br />
<br />
A: If no font is set in /etc/vconsole.conf (or alternatively /etc/rc.conf), then a standard font will be used. The standard font is chosen due to it supporting a wide range of character sets. Set your preferred font to fix the issue.<br />
<br />
=== Why are there duplicates in the output of df/mount? ===<br />
<br />
A: Systemd expects /etc/mtab to be a symlink to /proc/self/mounts. This is going to be the recommended setup by upstream (util-linux) in the near future, but for the time being there are still some regressions related to fuse. For that reason we leave /etc/mtab as it is until the last kinks have been worked out upstream. You can manually create the symlink if you think you are not affected by the regressions.<br />
<br />
=== Why does systemd not support the RTC being in localtime? ===<br />
<br />
A: In principle, there is nothing stopping you from adding some unit files that will allow the RTC to be in localtime, but there are a few reasons why we have not (and probably will not) implement it by default:<br />
<br />
* The reason for allowing the RTC to be in localtime was to allow dualboot with Windows ([http://blogs.msdn.com/b/oldnewthing/archive/2004/09/02/224672.aspx who uses localtime]). However, for some time now, Windows has been able to deal with the RTC being in UTC by setting the following registry key<br />
HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\RealTimeIsUniversal<br />
This needs to be a DWORD key with a value of 1.<br />
<br />
* Dealing with daylight saving time is messy. If the DST changes when your computer is off, your clock will be wrong on next boot ([http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html there is a lot more to it]).<br />
* Recent kernels set the system time from the RTC directly on boot without using 'hwclock', the kernel will always assume that the RTC is in UTC. This means that if the RTC is in localtime, then the system time will first be set up wrongly and then corrected shortly afterwards on every boot. It is not clear that this will not introduce weird bugs (time going backwards is rarely a good thing).<br />
<br />
=== How do I change the current runlevel? ===<br />
<br />
A: In systemd runlevels are exposed via "target units". You can change them like this:<br />
{{cli|# systemctl isolate runlevel5.target}}<br />
or<br />
{{cli|# systemctl isolate runlevel3.target}}<br />
Note however, that the concept of runlevels is a bit out of date, and it is usually nicer to use modern names for this. e.g.:<br />
{{cli|# systemctl isolate graphical.target}}<br />
This will only change the current runlevel, and has no effect on the next boot.<br />
<br />
=== How do I boot into a different "runlevel"? ===<br />
<br />
A: The standard target (which is what runlevels are called in a systemd world) is graphical.target (which roughly corresponds to the old runlevel 5). To change the default target at boot-time, append one of the following kernel parameters to your GRUB kernel line:<br />
* systemd.unit=multi-user.target (which roughly corresponds to the old runlevel 3),<br />
* systemd.unit=rescue.target (which roughly corresponds to the old runlevel 1).<br />
<br />
=== How do I change the default runlevel/target to boot into? ===<br />
<br />
A: The symlink /etc/systemd/system/default.target controls where we boot into by default. Link it to the target unit of your choice. For example, like this:<br />
{{cli|# systemctl -f enable multi-user.target}}<br />
or<br />
{{cli|# systemctl -f enable graphical.target}}<br />
<br />
=== How do I know the current run level? ===<br />
<br />
A: runlevel command still works with systemd. You can continue using that however runlevels is a legacy concept in systemd and is emulated via 'targets' and multiple targets can be active at the same time. So the equivalent in systemd terms is<br />
{{cli|<nowiki># systemctl list-units --type=target</nowiki>}}<br />
<br />
=== How do I make a custom unit file? ===<br />
<br />
A: The unit files in /etc/systemd/system take precedence over the ones in /lib/systemd/system. To make your own version of a unit (which will not be destroyed by an upgrade), copy the old unit file from /lib to /etc and make your changes there.<br />
<br />
=== How do I change the number of gettys running by default? ===<br />
<br />
To add another getty:<br />
<br />
Simply place another symlink for instantiating another getty in the getty.target.wants/ directory:<br />
<br />
{{cli|<nowiki># ln -sf /lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty9.service<br />
# systemctl daemon-reload<br />
# systemctl start getty@tty9.service</nowiki>}}<br />
<br />
To remove a getty:<br />
<br />
Simply remove the getty symlinks you want to get rid of in the getty.target.wants/ directory:<br />
<br />
{{cli|<nowiki># rm /etc/systemd/system/getty.target.wants/getty@tty5.service /etc/systemd/system/getty.target.wants/getty@tty6.service<br />
# systemctl daemon-reload<br />
# systemctl stop getty@tty5.service getty@tty6.service</nowiki>}}<br />
<br />
systemd does not use /etc/inittab file.<br />
<br />
=== How do I get more verbose output during boot? ===<br />
<br />
A: By default systemd does not give much (if any) output during boot. Firstly, lots of output from services running in parallel would be very messy, and secondly, boot is supposed to be so fast that status messages would slow it down.<br />
<br />
If you append the kernel parameter "verbose" to your kernel line in GRUB, you will get lots of output during boot. However, this is only really meant as a debugging tool as it is not very useful during normal use. Any messages are logged to the system log and if you want to find out about the status of your system<br />
{{cli|$ systemctl}}<br />
is your friend.<br />
<br />
=== What kernel options do I need to enable in my kernel in case I don't use the official Arch kernel? ===<br />
<br />
A: kernels prior to 2.6.36 are unsupported.<br />
<br />
This is a partial list of required/recommended options, there might be more:<br />
<br />
CONFIG_DEVTMPFS=y<br />
CONFIG_CGROUPS=y<br />
CONFIG_AUTOFS4_FS=[y|m]<br />
CONFIG_IPV6=[y|m], optional, but highly recommended<br />
CONFIG_RTC_DRV_CMOS=y, optional, but highly recommended<br />
CONFIG_FANOTIFY=y, optional, required for systemd readahed. Availabe in Linux kernel >= 2.6.37-rcX.<br />
CONFIG_UEVENT_HELPER_PATH should be empty, if you want to use systemd without initramfs<br />
<br />
=== What other units does a unit depend on? ===<br />
<br />
For example, if you want to figure out which services a target like multi-user.target pulls in, use something like this: <br />
{{Command|command=systemctl show -p "Wants" multi-user.target|output=Wants=rc-local.service avahi-daemon.service rpcbind.service NetworkManager.service acpid.service dbus.service atd.service crond.service auditd.service ntpd.service udisks.service bluetooth.service cups.service wpa_supplicant.service getty.target modem-manager.service portreserve.service abrtd.service yum-updatesd.service upowerd.service test-first.service pcscd.service rsyslog.service haldaemon.service remote-fs.target plymouth-quit.service systemd-update-utmp-runlevel.service sendmail.service lvm2-monitor.service cpuspeed.service udev-post.service mdmonitor.service iscsid.service livesys.service livesys-late.service irqbalance.service iscsi.service netfs.service}}<br />
<br />
Instead of "Wants" you might also try "WantedBy", "Requires", "RequiredBy", "Conflicts", "ConflictedBy", "Before", "After" for the respective types of dependencies and their inverse.<br />
<br />
== Optimization ==<br />
<br />
=== Less output ===<br />
<br />
Change 'verbose' to 'quiet' on the kernel line in GRUB. For some systems, particularly those with an SSD, the slow performance of the TTY is actually a bottleneck, and so less output means faster booting.<br />
<br />
=== Early start ===<br />
<br />
One central feature of systemd is dbus and socket activation, this causes services to be started when they are first accessed, and is generally a good thing. However, if you know that a service (like console-kit) will always be started during boot, then the overall boot time might be reduced by starting it as early as possible. This can be acheived (if the service file is set up for it, which in most cases it is) by issuing:<br />
<br />
{{cli|# systemctl enable console-kit-daemon.service}}<br />
<br />
This will cause systemd to start console-kit as soon as possible, without causing races with the socket or dbus activation.<br />
<br />
=== Automount ===<br />
<br />
The default setup will fsck and mount all filesystems before starting most daemons and services. If you have a large /home partition, it might be better to allow services that do not depend on /home to start while /home is being fsck'ed. This can be acheived by adding the following options to the fstab entry of your /home partition<br />
<br />
comment=systemd.automount<br />
<br />
This will fsck and mount /home when it is first accessed, and the kernel will buffer all file access to /home until it is ready.<br />
<br />
=== /etc/mtab ===<br />
<br />
systemd requires that /etc/mtab is a symlink to /proc/self/mounts, or the following warning will be printed:<br />
<br />
''/etc/mtab is not a symlink or not pointing to /proc/self/mounts. This is not supported anymore. Please make sure to replace this file by a symlink to avoid incorrect or misleading mount(8) output.''<br />
<br />
Replace the file with a symlink with ln:<br />
<br />
{{cli|# ln -fs /proc/self/mounts /etc/mtab}}<br />
<br />
Without doing this, features such as automounting through /etc/fstab will be unavailable.<br />
<br />
{{warning|If you use FUSE mounts or filesystem specific options such as user or users, it's required to recompile util-linux with --enable-libmount-mount.}}<br />
<br />
=== Disabling native mount ===<br />
<br />
With v12 or later you can disable the native mount and fsck facility in /etc/systemd/system.conf.<br />
MountAuto=no<br />
SwapAuto=no<br />
{{Note|These options are enabled by default.}}<br />
<br />
=== Remote filesystem mounts ===<br />
<br />
If you have NFS mounts listed in /etc/fstab then systemd will attempt to mount them but will typically do so too early, before networking has been configured. To get the timing correct we need to tell systemd explicitly that the mount depends on networking and on rpc.statd. To do this, create a file under /lib/systemd/system named <mount-unit-name>.mount with contents as follows.<br />
<br />
[Unit]<br />
Description=<mountpoint><br />
Wants=network.target statd.service<br />
After=network.target statd.service <br />
<br />
[Mount]<br />
What=<server>:<share><br />
Where=<mountpoint><br />
Type=nfs<br />
StandardOutput=syslog<br />
StandardError=syslog<br />
<br />
In the above<br />
*mount-unit-name is the full path to the mountpoint in an escaped format. For example, a mount unit for /usr/local must be named usr-local.mount.<br />
*mountpoint is the local mountpoint<br />
*server:share specify the remote filesystem in the same manner as for /etc/fstab <br />
<br />
See systemd.unit(5) and systemd.mount(5) for further details.<br />
<br />
A similar approach will probably be required for other remote filesystem types such as nfs4 and cifs.<br />
<br />
Alternatively, you can mark these entries in /etc/fstab with the option 'comment=systemd.automount'. Make sure that if you also include 'defaults' as a mount option that you override the implicit 'auto' with 'noauto'. This will cause the device to be mounted on first access, similar to [[Autofs]].<br />
<br />
=== Readahead ===<br />
<br />
systemd comes with its own readahead implementation, this should in principle improve boot time. However, depending on your kernel version and your the type of your hard drive, your milage might vary (i.e. it might make boot slower). To enable do:<br />
<br />
{{cli|<nowiki># systemctl enable systemd-readahead-collect.service<br />
# systemctl enable systemd-readahead-replay.service</nowiki>}}<br />
<br />
Remember that in order for the readahead to work its magic you should reboot a couple of times.<br />
<br />
=== User sessions ===<br />
<br />
systemd can divide user sessions into cgroups. Add "session optional pam_systemd.so" to your relevant /etc/pam.d files (e.g., login for tty logins, sshd for remote access, kde for password kdm logins, kde-np for automatic kdm logins).<br />
<br />
Before:<br />
{{Command|systemd-cgls systemd:/system/getty@.service|<br />
systemd:/system/getty@.service:<br />
├ tty5<br />
│ └ 904 /sbin/agetty tty5 38400<br />
├ tty2<br />
│ ├ 13312 /bin/login --<br />
│ └ 15765 -zsh<br />
[…]}}<br />
After:<br />
{{Command|systemd-cgls systemd:/user/example/|<br />
systemd:/user/example/:<br />
├ 4<br />
│ ├ 902 /bin/login --<br />
│ └ 16016 -zsh<br />
[…]}}<br />
<br />
== See also==<br />
<br />
*[http://www.freedesktop.org/wiki/Software/systemd Official Web Site]<br />
*[http://0pointer.de/public/systemd-man/ Manual Pages]<br />
*[http://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions FAQ]<br />
*[http://www.freedesktop.org/wiki/Software/systemd/TipsAndTricks Tips And Tricks]<br />
*[https://bbs.archlinux.org/viewtopic.php?pid=792280 Discussion on the bbs.archlinux.org]<br />
*[http://en.gentoo-wiki.com/wiki/Systemd About systemd in Gentoo Wiki]<br />
*[http://fedoraproject.org/wiki/Systemd About systemd on Fedora Project]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=NVIDIA&diff=135697
NVIDIA
2011-04-02T18:33:19Z
<p>Cantabile: /* Installing */ mention the conflict with libgl; a reboot is necessary; (the previous revision was not supposed to happen - pressed wrong button</p>
<hr />
<div>[[Category: Graphics (English)]]<br />
[[Category: X Server (English)]]<br />
[[Category: HOWTOs (English)]]<br />
{{i18n|NVIDIA}}<br />
[[de:Nvidia]]<br />
{{Article summary start}}<br />
{{Article summary text|Information on installing, configuring and troubleshooting the proprietary NVIDIA Drivers.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|ATI}}<br />
{{Article summary wiki|Intel}}<br />
{{Article summary wiki|Nouveau}}<br />
{{Article summary wiki|Xorg}}<br />
{{Article summary end}}<br />
<br />
This article covers installing and configuring [http://www.nvidia.com NVIDIA]'s ''proprietary'' graphic card driver. For information about the open-source drivers, see [[Nouveau]].<br />
<br />
==Installing==<br />
These instructions are for those using the stock kernel26 package. For custom kernel setup, skip to the [[#Alternate install: custom kernel|next]] subsection.<br />
<br />
{{Tip|It is usually beneficial to install the NVIDIA driver through pacman rather than through the package provided by the NVIDIA site, this allows the driver to be updated when upgrading the system.}}<br />
<br />
1. Visit NVIDIA's [http://www.nvidia.com/Download/index.aspx?lang=en-us driver download site] to find out the appropiate driver for a given card.<br />
<br />
2. Install the driver for newer cards (newest GPUs after the GF FX):<br />
:<pre># pacman -S nvidia nvidia-utils</pre><br />
<br />
:Whereas users with older cards should install (Geforce FX series cards):<br />
:<pre># pacman -S nvidia-173xx nvidia-173xx-utils</pre><br />
<br />
:or (cards up to the GF 4):<br />
<br />
:<pre># pacman -S nvidia-96xx nvidia-96xx-utils</pre><br />
<br />
:The nvidia{,-173xx,-96xx}-utils packages conflict with the libgl package. This is normal. pacman will ask if it should remove libgl &mdash; answer "yes".<br />
<br />
:{{Note|For the latest card models, it may be required to install {{Package AUR|nvidia-beta}} and {{Package AUR|nvidia-utils-beta}} from the [[AUR]] since the stable drivers may not support the newly introduced features.}}<br />
:On 64 bit systems, for 32 bit programs to take advantage of nvidia-utils you must also install the equivalent lib32 package (for example lib32-nvidia-utils).<br />
<br />
3. '''Reboot'''. The nvidia{,-173xx,-96xx} packages contain a file which blacklists the nouveau module. A reboot is necessary for this blacklist to take effect.<br />
<br />
Once the driver has been installed, continue to: [[#Configuring]].<br />
<br />
===Alternate install: custom kernel===<br />
First of all, it is of advantage to know how the ABS system works by reading some of the other articles about it:<br />
* Main article for [[ABS]]<br />
* Article on [[makepkg]]<br />
* Article on [[Creating Packages]]<br />
<br />
{{Note|There is the {{Package AUR|nvidia-all}} package on [[AUR]] which turns out to make it easier to install the nvidia driver for custom kernels and multiple kernels}}<br />
<br />
The following is a short tutorial for making a custom nvidia driver package using ABS:<br />
<br />
Install ABS and generate the tree:<br />
# pacman -S abs<br />
# abs<br />
As a standard user, make a temporary directory for creating the new package:<br />
$ mkdir -p ~/devel/abs<br />
Make a copy of the nvidia package directory:<br />
$ cp -r /var/abs/extra/nvidia/ ~/devel/abs/<br />
Go into the temporary nvidia build directory:<br />
$ cd ~/devel/abs/nvidia<br />
It is required to edit the files {{Filename|nvidia.install}} and {{Filename|PKGBUILD}} file so that they contain the right kernel version variables.<br />
<br />
While running the custom kernel, get the appropiate kernel and local version names:<br />
$ uname -r<br />
# In nvidia.install, replace the <code>KERNEL_VERSION="2.6.xx-ARCH"</code> variable with the custom kernel version, such as <code>KERNEL_VERSION="2.6.22.6"</code> or <code>KERNEL_VERSION"2.6.22.6-custom"</code> depending on what the kernel's version is and the local version's text/numbers. Do this for all instances of the version number within this file.<br />
# In PKGBUILD, change the <code>_kernver='2.6.xx-ARCH'</code> variable to match the appropiate version, as above.<br />
# If there are more than one kernels in the system installed in parallel, (such as a custom kernel alongside the default -ARCH kernel) change the <code>"pkgname=nvidia"</code> variable in the PKGBUILD to a unique identifier, such as nvidia-2622 or nvidia-custom. This will allow both kernels to use the nvidia module, since the custom nvidia module has a different package name and will not overwrite the original.<br />
<br />
Then do:<br />
$ makepkg -ci<br />
The {{Codeline|-c}} operand tells makepkg to clean left over files after building the nvidia driver, whereas {{Codeline|-i}} specifies that makepkg should automatically run pacman to install the resulting package.<br />
<br />
==Configuring==<br />
It is possible that after installing the driver it may not be needed to create an Xorg server configuration file. You can run [[Xorg#Running Xorg| a test]] to see if the Xorg server will function correctly without a configuration file. However, it may be required to create a {{Filename|/etc/X11/xorg.conf}} configuration file in order to adjust various settings. This configuration can be generated by the NVIDIA Xorg configuration tool, or it can be created manually. If created manually, it can be a minimal configuration (in the sense that it will only pass the basic options to the [[Xorg]] server), or it can include a [[Xorg#Manual configuration|number of settings]] that can bypass Xorg's auto-discovered or pre-configured options.<br />
<br />
===Automatic configuration===<br />
The NVIDIA package includes an automatic configuration tool to create an Xorg server configuration file ({{Filename|xorg.conf}}) and can be run by:<br />
# nvidia-xconfig<br />
<br />
This command will auto-detect and create (or edit, if already present) the {{Filename|/etc/X11/xorg.conf}} configuration according to present hardware.<br />
<br />
If there are instances of DRI, ensure they are commented out:<br />
# Load "dri"<br />
Double check your {{filename | /etc/X11/xorg.conf}} to make sure your default depth, horizontal sync, vertical refresh, and resolutions are acceptable.<br />
<br />
{{Warning| That may still not work properly with Xorg-server 1.8 }}<br />
<br />
===Automatic configuration with multiple monitors===<br />
The NVIDIA package provides Twinview. This tool will help by automatically configuring all the monitors connected to your video card. This only works for multiple monitors on a single card.<br />
To configure Xorg Server with Twinview run:<br />
# nvidia-xconfig --twinview<br />
<br />
===Minimal configuration===<br />
To create a basic {{Filename|/etc/X11/xorg.conf}}, as root:<br />
# vi /etc/X11/xorg.conf<br />
<br />
And add the driver:<br />
<pre><br />
Section "Device"<br />
Identifier "Device0"<br />
Driver "nvidia"<br />
VendorName "NVIDIA Corporation"<br />
EndSection<br />
</pre><br />
<br />
{{Tip|Make sure, in order to have full multimedia functionality, to have '''xorg-input-drivers''' installed.}}<br />
<br />
==Tweaking==<br />
<br />
===GUI: nvidia-settings===<br />
The NVIDIA package includes the {{Codeline|nvidia-settings}} program that allows adjustment of several additional settings.<br />
<br />
For the settings to be loaded on login, run this command from the terminal:<br />
$ nvidia-settings --load-config-only<br />
<br />
Or add it to the the desktop environment's auto-startup method.<br />
<br />
{{Tip | On rare occasions the {{Filename|~/.nvidia-settings-rc}} may become corrupt. If this happens, the Xorg server may crash and the file will have to be deleted to fix the issue.}}<br />
<br />
===Advanced: xorg.conf===<br />
Edit {{Filename|/etc/X11/xorg.conf}}, and add the option to the correct section. NVIDIA tests and ships the drivers with the recommended setting so note that some edits may cause instability, tearing, among other problems. Since not all options may work for a given system, consider backing up {{Filename|xorg.conf}} before making any edits. The Xorg server will need to be restarted before any changes are applied.<br />
<br />
* See [http://us.download.nvidia.com/XFree86/Linux-x86_64/256.53/README/index.html NVIDIA Accelerated Linux Graphics Driver README and Installation Guide] for additional details and options.]<br />
====Enabling desktop composition====<br />
As of NVIDIA driver version 180.44, support for GLX with the Damage and Composite X extensions is enabled by default. Refer to [[Composite]] for detailed instructions.<br />
<br />
====Disabling the logo on startup====<br />
Add the {{Codeline|"NoLogo"}} option under section {{Codeline|Device}}:<br />
Option "NoLogo" "1"<br />
<br />
====Enabling hardware acceleration====<br />
{{Note|RenderAccel is enabled by default since drivers version 97.46.xx}}<br />
Add the {{Codeline|"RenderAccel"}} option under section {{Codeline|Device}}:<br />
Option "RenderAccel" "1"<br />
<br />
====Overriding monitor detection====<br />
The {{Codeline|"ConnectedMonitor"}} option under section {{Codeline|Device}} allows to override monitor detection when X server starts, which may save a significant amount of time at start up. The available options are: {{Codeline|"CRT"}} for analog connections, {{Codeline|"DFP"}} for digital monitors and {{Codeline|"TV"}} for televisions.<br />
<br />
The following statement forces the NVIDIA driver to bypass startup checks and recognize the monitor as DFP:<br />
Option "ConnectedMonitor" "DFP"<br />
{{Note| Use "CRT" for all analog 15 pin VGA connections, even if the display is a flat panel. "DFP" is intended for DVI digital connections only.}}<br />
<br />
====Enabling triple buffering====<br />
Enable the use of triple buffering by adding the {{Codeline|"TripleBuffer"}} Option under section {{Codeline|Device}}:<br />
Option "TripleBuffer" "1"<br />
<br />
Use this option if the graphics card has plenty of ram (equal or greater than 128MB). The setting only takes effect when syncing to vblank is enabled, one of the options featured in nvidia-settings.<br />
<br />
{{Note|This option may introduce full-screen tearing and reduce performance.}}<br />
<br />
====Using OS-level events====<br />
Taken from the NVIDIA driver's [http://http.download.nvidia.com/XFree86/Linux-x86/1.0-7182/README/readme.txt README] file: ''"[...] Use OS-level events to efficiently notify X when a client has performed direct rendering to a window that needs to be composited."'' It may help improving performance, but it is currently incompatible with SLI and Multi-GPU modes.<br />
<br />
Add under section {{Codeline|Device}}:<br />
Option "DamageEvents" "1"<br />
{{Note|This option is enabled by default in newer driver versions.}}<br />
<br />
====Enabling power saving====<br />
Add under section <code>Monitor</code>:<br />
Option "DPMS" "1"<br />
<br />
====Forcing Powermizer performance level (for laptops)====<br />
Add under section {{Codeline|Device}}:<br />
# Force Powermizer to a certain level at all times<br />
# level 0x1=highest<br />
# level 0x2=med<br />
# level 0x3=lowest<br />
<br />
# AC settings:<br />
Option "RegistryDwords" "PowerMizerLevelAC=0x3"<br />
# Battery settings:<br />
Option "RegistryDwords" "PowerMizerLevel=0x3"<br />
Settings are better explained in [http://tutanhamon.com.ua/technovodstvo/NVIDIA-UNIX-driver/ NVIDIA Driver for X.org:Performance and Power Saving Hints].<br />
<br />
=====Letting the GPU set its own performance level based on temperature=====<br />
Add under section {{Codeline|Device}}:<br />
Option "RegistryDwords" "PerfLevelSrc=0x3333"<br />
<br />
====Disable vblank interrupts (for laptops)====<br />
When running the interrupt detection utility {{Codeline|powertop}}, it can be observed that the Nvidia driver will generate an interrupt for every vblank. To disable, place in the {{Codeline|Device}} section:<br />
Option "OnDemandVBlankInterrupts" "1"<br />
This will reduce interrupts to about one or two per second.<br />
<br />
====Enabling overclocking====<br />
{{Warning|Please note that overclocking may damage hardware and that no responsibility may be placed on the authors of this page due to any damage to any information technology equipment from operating products out of specifications set by the manufacturer.}}<br />
To enable GPU and memory overclocking, place the following line in the {{Codeline|Device}} section:<br />
Option "Coolbits" "1"<br />
<br />
This will enable on-the-fly overclocking within an X session by running:<br />
$ nvidia-settings<br />
{{Note|GTX 4xx/5xx series Fermi cores cannot currently be overclocked using <br />
the Coolbits method. The alternative is to edit and reflash the GPU BIOS either under DOS (preferred), or within a Win32 environment by way of [http://www.mvktech.net/component/option,com_remository/Itemid,26/func,select/id,127/orderby,2/page,1/ nvflash] and [http://www.mvktech.net/component/option,com_remository/Itemid,26/func,select/id,135/orderby,2/page,1/ NiBiTor 6.0]. The advantage of BIOS flashing is that not only can voltage limits be raised, but stability is generally improved over software overclocking methods such as Coolbits.}}<br />
<br />
===== Setting static 2D/3D clocks =====<br />
Set the following string in the {{Codeline|Device}} section to enable PowerMizer at its maximum performance level:<br />
Option "RegistryDwords" "PerfLevelSrc=0x2222"<br />
Set one of the following two strings in the {{Codeline|Device}} section to enable manual GPU fan control within {{codeline|nvidia-settings}}:<br />
Option "Coolbits" "4"<br />
<br />
Option "Coolbits" "5"<br />
<br />
====Enable screen rotation through XRandR====<br />
Place the following line in the {{Codeline|Device}} section:<br />
Option "RandRRotation" "True"<br />
After restarting Xorg:<br />
$ xrandr -o left<br />
The Screen should be rotated. To restore:<br />
$ xrandr -o normal<br />
{{Note| Editing xorg.conf may be unnecessary since screen rotation should be enabled by default, ideally by using the respective DE tools, such as SystemSettings in KDE.}}<br />
<br />
==Tips and tricks==<br />
===Enabling Pure Video HD (VDPAU/VAAPI)===<br />
'''Hardware Required:''' <br />
<br />
At least a video card with second generation PureVideo HD [http://en.wikipedia.org/wiki/PureVideo_HD#Table_of_PureVideo_.28HD.29_GPUs]<br />
<br />
'''Software Required:'''<br />
<br />
Nvidia video cards with the proprietary driver installed will provide video decoding capabilities with the VDPAU interface at different levels according to PureVideo generation.<br />
<br />
You can also add support for the VA-API interface with:<br />
# pacman -S vdpau-video<br />
<br />
Check VA-API support with:<br />
$ vainfo<br />
<br />
To take full advantage of the hardware decoding capability of your video card you will need a media player that supports VDPAU or VA-API.<br />
<br />
To enable hardware acceleration in '''MPlayer''' edit ~/.mplayer/config<br />
<br />
vo=vdpau<br />
vc=ffmpeg12vdpau,ffwmv3vdpau,ffvc1vdpau,ffh264vdpau,ffodivxvdpau,<br />
<br />
<br />
To enable hardware acceleration in '''VLC''' go:<br />
<br />
Tools -> Settings -> Videos and codec -> check "Use GPU acceleration"<br />
<br />
To enable hardware acceleration in '''smplayer''' go:<br />
<br />
Options -> Preferences -> General -> Video Tab -> select vdpau as output driver<br />
<br />
To enable hardware acceleration in '''gnome-mplayer''' go:<br />
<br />
Edit -> Preferences -> set video output to vdpau<br />
<br />
'''Playing HD movies on cards with low memory:'''<br />
<br />
If your graphic card doesn't have a lot of memory(>521MB?), you can experience glitches when watching 1080p or even 720p movies.<br />
To avoid that start simple window manager like TWM or MWM.<br />
<br />
Additionally increasing the MPlayer's cache size in ~/.mplayer/config can help, when your hard drive is spinning down when watching HD movies.<br />
<br />
===Using TV-out===<br />
A good article on the subject can be found [http://en.wikibooks.org/wiki/NVidia/TV-OUT here]<br />
<br />
===X with a TV (DFP) as the only display===<br />
The X server falls back to CRT-0 if no monitor is automatically detected. This can be a problem when using a DVI connected TV as the main display, and X is started while the TV is turned off or otherwise disconnected.<br />
<br />
To force nvidia to use DFP, store a copy of the EDID somewhere in the filesystem so that X can parse the file instead of reading EDID from the TV/DFP.<br />
<br />
To acquire the EDID, start nvidia-settings. It will show some information in tree format, ignore the rest of the settings for now and select the GPU (the corresponding entry should be titled "GPU-0" or similar), click the "DFP" section (again, "DFP-0" or similar), click on the "Acquire Edid" Button and store it somewhere, for example, {{Filename|/etc/X11/dfp0.edid}}.<br />
<br />
Edit xorg.conf by adding to the "Device" section:<br />
Option "ConnectedMonitor" "DFP"<br />
Option "CustomEDID" "DFP-0:/etc/X11/dfp0.edid"<br />
The "ConnectedMonitor" option forces the driver to recognize the DFP as if it were connected. The "CustomEDID" provides EDID data for the device, meaning that it will start up just as if the TV/DFP was connected during X the process.<br />
<br />
This way, one can automatically start a display manager at boot time and still have a working and properly configured X screen by the time the TV gets powered on.<br />
<br />
===Displaying GPU temperature in the shell===<br />
====Method 1 - nvidia-settings====<br />
{{Note|This method requires that you're using X. Use Method 2 or Method 3 if you are not. Also note that Method 3 currently does not not work with newer nvidia cards such as the G210/220 as well as embedded GPUs such as the Zotac IONITX's 8800GS.}}<br />
<br />
To display the GPU temp in the shell, use nvidia-settings as follows:<br />
$ nvidia-settings -q gpucoretemp<br />
<br />
This will output something similar to the following:<br />
Attribute 'GPUCoreTemp' (hostname:0.0): 41.<br />
'GPUCoreTemp' is an integer attribute.<br />
'GPUCoreTemp' is a read-only attribute.<br />
'GPUCoreTemp' can use the following target types: X Screen, GPU.<br />
<br />
The GPU temps of this board is 41 C.<br />
<br />
In order to get just the temperature for use in utils such as rrdtool or conky, among others:<br />
$ nvidia-settings -q gpucoretemp -t<br />
41<br />
<br />
====Method 2 - nvidia-smi====<br />
<br />
Use nvidia-smi which can read temps directly from the GPU without the need to use X at all. This is important for a small group of users who do not have X running on their boxes, perhaps because the box is headless running server apps. <br />
To display the GPU temp in the shell, use nvidia-smi as follows:<br />
<br />
$ nvidia-smi -a<br />
<br />
This should output something similar to the following:<br />
<pre><br />
$ nvidia-smi -a<br />
<br />
==============NVSMI LOG==============<br />
<br />
<br />
Timestamp : Mon Dec 13 20:11:28 2010<br />
<br />
Driver Version : 260.19.29<br />
<br />
<br />
GPU 0:<br />
Product Name : GeForce 8400 GS<br />
PCI Device/Vendor ID : 6e410de<br />
PCI Location ID : 0:1:0<br />
Board Serial : 2648101198649<br />
Display : Connected<br />
Temperature : 40 C<br />
Utilization<br />
GPU : 1%<br />
Memory : 8%<br />
<br />
</pre><br />
<br />
In order to get just the temperature for use in utils such as rrdtool or conky, among others:<br />
<br />
$ nvidia-smi -a | grep Temp | cut -c17-18<br />
40<br />
<br />
Reference: http://www.question-defense.com/2010/03/22/gpu-linux-shell-temp-get-nvidia-gpu-temperatures-via-linux-cli<br />
<br />
====Method 3 - nvclock====<br />
Use nvclock which is available from the [extra] repo. Note that nvclock cannot access thermal sensors on newer nvidia cards such as the G210/220.<br />
<br />
There can be significant differences between the temperatures reported by nvclock and nvidia-settings/nv-control. According to [http://sourceforge.net/projects/nvclock/forums/forum/67426/topic/1906899 this post] by the author (thunderbird) of nvclock, the nvclock values should be more accurate.<br />
<br />
===Set Fan Speed at Login===<br />
You can adjust the fan speed on your graphics card with {{Codeline|nvidia-settings}}'s console interface. First ensure that your Xorg configuration sets the Coolbits option to 4 or 5 in your {{Codeline|Device}} section to enable fan control.<br />
<br />
Option "Coolbits" "4"<br />
<br />
{{Note|GTX 4xx/5xx series cards cannot currently set fan speeds at login using this method. This method only allows for the setting of fan speeds within the current X session by way of nvidia-settings.}}<br />
<br />
Place the following line in your [[xinitrc|{{filename|~/.xinitrc}}]] file to adjust the fan when you launch Xorg. Replace <n> with the fan speed percentage you want to set.<br />
<br />
nvidia-settings -a "[gpu:0]/GPUFanControlState=1" -a "[fan:0]/GPUCurrentFanSpeed=<n>"<br />
<br />
You can also configure a second GPU by incrementing the GPU and fan number.<br />
<br />
nvidia-settings -a "[gpu:0]/GPUFanControlState=1" \ <br />
-a "[gpu:1]/GPUFanControlState=1" \<br />
-a "[fan:0]/GPUCurrentFanSpeed=<n>" \<br />
-a [fan:1]/GPUCurrentFanSpeed=<n>" &<br />
<br />
If you use a login manager such as GDM or KDM, you can create a desktop entry file to process this setting. Create {{filename|~/.config/autostart/nvidia-fan-speed.desktop}} and place this text inside it. Again, change <n> to the speed percentage you want.<br />
<br />
[Desktop Entry]<br />
Type=Application<br />
Exec=nvidia-settings -a "[gpu:0]/GPUFanControlState=1" -a "[fan:0]/GPUCurrentFanSpeed=<n>"<br />
X-GNOME-Autostart-enabled=true<br />
Name=nvidia-fan-speed<br />
<br />
===Order of install/deinstall for changing drivers===<br />
Where the old driver is nvidiaO and the new driver is nvidiaN.<br />
remove nvidiaO<br />
install nvidia-utilsN<br />
install nvidiaN<br />
install lib32-nvidia-utils-N (if required)<br />
<br />
==Troubleshooting==<br />
<br />
===Gaming using Twinview===<br />
In case you want to play fullscreen games when using Twinview, you will notice that games recognize the two screens as being one big screen. While this is technically correct (the virtual X screen really is the size of your screens combined), you probably don't want to play on both screens at the same time. <br />
<br />
To correct this behavior for SDL, try:<br />
export SDL_VIDEO_FULLSCREEN_HEAD=1<br />
<br />
For OpenGL, add the appropiate Metamodes to your xorg.conf in section {{Codeline|Device}} and restart X:<br />
Option "Metamodes" "1680x1050,1680x1050; 1280x1024,1280x1024; 1680x1050,NULL; 1280x1024,NULL;"<br />
<br />
Another method that may either work alone or in conjunction with those mentioned above is [[Gaming#Starting_games_in_a_separate_X_server|starting games in a separate X server]].<br />
<br />
===Old Xorg Settings===<br />
If upgrading from an old installation, please remove old {{Filename|/usr/X11R6}} paths as it can cause trouble during installation.<br />
<br />
===Corrupted screen: "Six screens" issue===<br />
For some users using Geforce GT 100M's, the screen turns out corrupted after X starts; divided into 6 sections with a resolution limited to 640x480.<br />
<br />
To solve this problem, enable the Validation Mode {{Codeline|NoTotalSizeCheck}} in section {{Codeline|Device}}:<br />
Section "Device"<br />
...<br />
Option "ModeValidation" "NoTotalSizeCheck"<br />
...<br />
EndSection<br />
==='/dev/nvidia0' Input/Output error===<br />
This error can occur for several different reasons, and the most common solution given for this error is to check for group/file permissions, which in almost every case is ''not'' the issue. The Nvidia documentation does not talk in detail on what you should<br />
do to correct this problem but there are a few things that have worked for some people. The problem can be a IRQ conflict with another device or bad routing by either the kernel or your BIOS.<br />
<br />
First thing to try is to remove other video devices such as video capture cards and see if the problem goes away. If there are too many video processors on the same system it can lead into the kernel being unable to start them because of memory allocation problems with the video controller. In particular on systems with low video memory this can occur even if there's only one video processor. In such case you should find out the amount of your system's video memory (e.g. with ''lspci -v'') and pass allocation parameters to the kernel, e.g.:<br />
vmalloc=64M<br />
or<br />
vmalloc=256M<br />
<br />
Another thing to try is to change your BIOS IRQ routing from ''Operating system controlled'' to ''BIOS controlled'' or the other way around. The first one can be passed as a kernel parameter:<br />
PCI=biosirq<br />
<br />
The ''noacpi'' kernel parameter has also been suggested as a solution but since it disables ACPI completely it should be used with caution. Some hardware are easily damaged by overheating.<br />
<br />
{{Note|The kernel parameters can be passed either through the kernel command line or the bootloader configuration file. See your bootloader Wiki page for more information.}}<br />
<br />
==='/dev/nvidiactl' errors===<br />
Trying to start an opengl application might result in errors such as:<br />
Error: Could not open /dev/nvidiactl because the permissions are too<br />
restrictive. Please see the <code>FREQUENTLY ASKED QUESTIONS</code> <br />
section of <code>/usr/share/doc/NVIDIA_GLX-1.0/README</code> <br />
for steps to correct.<br />
<br />
Solve by adding the appropiate user to the "video" group and relogin:<br />
# gpasswd -a username video<br />
<br />
===32 bit applications do not start===<br />
Under 64 bit systems, installing {{Codeline|lib32-nvidia-utils}} that corresponds to the same version installed for the 64 bit driver fixes the issue.<br />
<br />
===Errors after updating the kernel===<br />
If a custom build of nvidia's module is used instead of the package from [extra], a recompile is required every time the kernel is updated. Rebooting is generally recommended after updating kernel and graphic drivers.<br />
<br />
===Crashing in general===<br />
* Try disabling {{Codeline|RenderAccel}} in xorg.conf.<br />
* If Xorg outputs an error about "conflicting memory type" or "failed to allocate primary buffer: out of memory", add {{Codeline|nopat}} at the end of the {{Codeline|kernel}} line in {{Codeline|/boot/grub/menu.lst}}.<br />
* If the NVIDIA compiler complains about different versions of GCC between the current one and the one used for compiling the kernel, add in {{Codeline|/etc/profile}}:<br />
export IGNORE_CC_MISMATCH=1<br />
* If Xorg is crashing with a "Signal 11" while using nvidia-96xx drivers, try disabling PAT. Pass the argument {{Codeline|nopat}} to the {{Codeline|kernel}} line in {{Codeline|menu.lst}}.<br />
More information about trouble-shooting the driver can be found in the [http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14 NVIDIA forums.]<br />
<br />
===Bad performance after installing a new driver version===<br />
If FPS have dropped in comparison with older drivers, first check if direct rendering is turned on: <br />
$ glxinfo | grep direct<br />
If the command prints:<br />
direct rendering: No <br />
then that could be an indication for the sudden FPS drop.<br />
<br />
A possible solution could be to regress to the previously installed driver version and rebooting afterwards.<br />
<br />
===CPU spikes with 400 series cards===<br />
If you're experiencing intermittent CPU spikes with a 400 series card, it may be caused by PowerMizer constantly changing the GPU's clock frequency. Switching PowerMizer's setting from Adaptive to Performance, add the following to the Device section of your Xorg configuration:<br />
<br />
Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x3322; PowerMizerDefaultAC=0x1"<br />
<br />
===Laptops: X hangs on login/out, worked around with Ctrl+Alt+Backspace===<br />
If while using the legacy nvidia drivers Xorg hangs on login and logout (particularly with an odd screen split into two black and white/gray pieces), but logging in is still possible via Ctrl-Alt-Backspace (or whatever the new "kill X" keybind is), try adding this in {{Filename|/etc/modprobe.d/modprobe.conf}}:<br />
options nvidia NVreg_Mobile=1<br />
<br />
One user had luck with this instead, but it makes performance drop significantly for others:<br />
options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660 NVreg_SoftEDIDs=0 NVreg_Mobile=1<br />
<br />
Note that {{Codeline|NVreg_Mobile}} needs to be changed according to the laptop:<br />
* 1 for Dell laptops.<br />
* 2 for non-Compal Toshiba laptops.<br />
* 3 for other laptops.<br />
* 4 for Compal Toshiba laptops.<br />
* 5 for Gateway laptops.<br />
<br />
See [http://http.download.nvidia.com/XFree86/Linux-x86/1.0-7182/README/readme.txt NVIDIA Driver's Readme:Appendix K] for more information.<br />
<br />
===Refresh rate not detected properly by XRandR dependant utilities===<br />
The XRandR X extension is not presently aware of multiple display devices on a single X screen; it only sees the {{Codeline|MetaMode}} bounding box, which may contain one or more actual modes. This means that if multiple MetaModes have the same bounding box, XRandR will not be able to distinguish between them.<br />
<br />
In order to support {{Codeline|DynamicTwinView}}, the NVIDIA driver must make each MetaMode appear to be unique to XRandR. Presently, the Nvidia driver accomplishes this by using the refresh rate as a unique identifier.<br />
<br />
Use {{Codeline|nvidia-settings -q RefreshRate}} to query the actual refresh rate on each display device.<br />
<br />
The XRandR extension is currently being redesigned by the X.Org community, so the refresh rate workaround may be removed at some point in the future.<br />
<br />
This workaround can also be disabled by setting the "DynamicTwinView" X configuration option to "false", which will disable NV-CONTROL support for manipulating MetaModes, but will cause the XRandR and XF86VidMode visible refresh rate to be accurate.<br />
<br />
==External links==<br />
* [http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14 NVIDIA forums]<br />
* [http://http.download.nvidia.com/XFree86/Linux-x86/1.0-7182/README/readme.txt Official readme for NVIDIA drivers]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=NVIDIA&diff=135696
NVIDIA
2011-04-02T18:20:42Z
<p>Cantabile: /* Installing */</p>
<hr />
<div>[[Category: Graphics (English)]]<br />
[[Category: X Server (English)]]<br />
[[Category: HOWTOs (English)]]<br />
{{i18n|NVIDIA}}<br />
[[de:Nvidia]]<br />
{{Article summary start}}<br />
{{Article summary text|Information on installing, configuring and troubleshooting the proprietary NVIDIA Drivers.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|ATI}}<br />
{{Article summary wiki|Intel}}<br />
{{Article summary wiki|Nouveau}}<br />
{{Article summary wiki|Xorg}}<br />
{{Article summary end}}<br />
<br />
This article covers installing and configuring [http://www.nvidia.com NVIDIA]'s ''proprietary'' graphic card driver. For information about the open-source drivers, see [[Nouveau]].<br />
<br />
==Installing==<br />
These instructions are for those using the stock kernel26 package. For custom kernel setup, skip to the [[#Alternate install: custom kernel|next]] subsection.<br />
<br />
{{Tip|It is usually beneficial to install the NVIDIA driver through pacman rather than through the package provided by the NVIDIA site, this allows the driver to be updated when upgrading the system.}}<br />
<br />
:1. Visit NVIDIA's [http://www.nvidia.com/Download/index.aspx?lang=en-us driver download site] to find out the appropiate driver for a given card.<br />
:2. Install the driver for newer cards (newest GPUs after the GF FX):<br />
: # pacman -S nvidia nvidia-utils<br />
<br />
Whereas users with older cards should install (Geforce FX series cards):<br />
# pacman -S nvidia-173xx nvidia-173xx-utils<br />
<br />
or (cards up to the GF 4):<br />
<br />
# pacman -S nvidia-96xx nvidia-96xx-utils<br />
<br />
{{Note|The nvidia{,-173xx,-96xx}-utils packages conflict with the libgl package. This is normal. pacman will ask if it should remove libgl - answer "yes".}}<br />
<br />
{{Note|For the latest card models, it may be required to install {{Package AUR|nvidia-beta}} and {{Package AUR|nvidia-utils-beta}} from the [[AUR]] since the stable drivers may not support the newly introduced features.}}<br />
On 64 bit systems, for 32 bit programs to take advantage of nvidia-utils you must also install the equivalent lib32 package (for example lib32-nvidia-utils).<br />
<br />
:3. Reboot. The nvidia{,-173xx,-96xx} packages contain a file which blacklists the nouveau module. A reboot is necessary for this blacklist to take effect.<br />
<br />
Once the driver has been installed, continue to: [[#Configuring]].<br />
<br />
===Alternate install: custom kernel===<br />
First of all, it is of advantage to know how the ABS system works by reading some of the other articles about it:<br />
* Main article for [[ABS]]<br />
* Article on [[makepkg]]<br />
* Article on [[Creating Packages]]<br />
<br />
{{Note|There is the {{Package AUR|nvidia-all}} package on [[AUR]] which turns out to make it easier to install the nvidia driver for custom kernels and multiple kernels}}<br />
<br />
The following is a short tutorial for making a custom nvidia driver package using ABS:<br />
<br />
Install ABS and generate the tree:<br />
# pacman -S abs<br />
# abs<br />
As a standard user, make a temporary directory for creating the new package:<br />
$ mkdir -p ~/devel/abs<br />
Make a copy of the nvidia package directory:<br />
$ cp -r /var/abs/extra/nvidia/ ~/devel/abs/<br />
Go into the temporary nvidia build directory:<br />
$ cd ~/devel/abs/nvidia<br />
It is required to edit the files {{Filename|nvidia.install}} and {{Filename|PKGBUILD}} file so that they contain the right kernel version variables.<br />
<br />
While running the custom kernel, get the appropiate kernel and local version names:<br />
$ uname -r<br />
# In nvidia.install, replace the <code>KERNEL_VERSION="2.6.xx-ARCH"</code> variable with the custom kernel version, such as <code>KERNEL_VERSION="2.6.22.6"</code> or <code>KERNEL_VERSION"2.6.22.6-custom"</code> depending on what the kernel's version is and the local version's text/numbers. Do this for all instances of the version number within this file.<br />
# In PKGBUILD, change the <code>_kernver='2.6.xx-ARCH'</code> variable to match the appropiate version, as above.<br />
# If there are more than one kernels in the system installed in parallel, (such as a custom kernel alongside the default -ARCH kernel) change the <code>"pkgname=nvidia"</code> variable in the PKGBUILD to a unique identifier, such as nvidia-2622 or nvidia-custom. This will allow both kernels to use the nvidia module, since the custom nvidia module has a different package name and will not overwrite the original.<br />
<br />
Then do:<br />
$ makepkg -ci<br />
The {{Codeline|-c}} operand tells makepkg to clean left over files after building the nvidia driver, whereas {{Codeline|-i}} specifies that makepkg should automatically run pacman to install the resulting package.<br />
<br />
==Configuring==<br />
It is possible that after installing the driver it may not be needed to create an Xorg server configuration file. You can run [[Xorg#Running Xorg| a test]] to see if the Xorg server will function correctly without a configuration file. However, it may be required to create a {{Filename|/etc/X11/xorg.conf}} configuration file in order to adjust various settings. This configuration can be generated by the NVIDIA Xorg configuration tool, or it can be created manually. If created manually, it can be a minimal configuration (in the sense that it will only pass the basic options to the [[Xorg]] server), or it can include a [[Xorg#Manual configuration|number of settings]] that can bypass Xorg's auto-discovered or pre-configured options.<br />
<br />
===Automatic configuration===<br />
The NVIDIA package includes an automatic configuration tool to create an Xorg server configuration file ({{Filename|xorg.conf}}) and can be run by:<br />
# nvidia-xconfig<br />
<br />
This command will auto-detect and create (or edit, if already present) the {{Filename|/etc/X11/xorg.conf}} configuration according to present hardware.<br />
<br />
If there are instances of DRI, ensure they are commented out:<br />
# Load "dri"<br />
Double check your {{filename | /etc/X11/xorg.conf}} to make sure your default depth, horizontal sync, vertical refresh, and resolutions are acceptable.<br />
<br />
{{Warning| That may still not work properly with Xorg-server 1.8 }}<br />
<br />
===Automatic configuration with multiple monitors===<br />
The NVIDIA package provides Twinview. This tool will help by automatically configuring all the monitors connected to your video card. This only works for multiple monitors on a single card.<br />
To configure Xorg Server with Twinview run:<br />
# nvidia-xconfig --twinview<br />
<br />
===Minimal configuration===<br />
To create a basic {{Filename|/etc/X11/xorg.conf}}, as root:<br />
# vi /etc/X11/xorg.conf<br />
<br />
And add the driver:<br />
<pre><br />
Section "Device"<br />
Identifier "Device0"<br />
Driver "nvidia"<br />
VendorName "NVIDIA Corporation"<br />
EndSection<br />
</pre><br />
<br />
{{Tip|Make sure, in order to have full multimedia functionality, to have '''xorg-input-drivers''' installed.}}<br />
<br />
==Tweaking==<br />
<br />
===GUI: nvidia-settings===<br />
The NVIDIA package includes the {{Codeline|nvidia-settings}} program that allows adjustment of several additional settings.<br />
<br />
For the settings to be loaded on login, run this command from the terminal:<br />
$ nvidia-settings --load-config-only<br />
<br />
Or add it to the the desktop environment's auto-startup method.<br />
<br />
{{Tip | On rare occasions the {{Filename|~/.nvidia-settings-rc}} may become corrupt. If this happens, the Xorg server may crash and the file will have to be deleted to fix the issue.}}<br />
<br />
===Advanced: xorg.conf===<br />
Edit {{Filename|/etc/X11/xorg.conf}}, and add the option to the correct section. NVIDIA tests and ships the drivers with the recommended setting so note that some edits may cause instability, tearing, among other problems. Since not all options may work for a given system, consider backing up {{Filename|xorg.conf}} before making any edits. The Xorg server will need to be restarted before any changes are applied.<br />
<br />
* See [http://us.download.nvidia.com/XFree86/Linux-x86_64/256.53/README/index.html NVIDIA Accelerated Linux Graphics Driver README and Installation Guide] for additional details and options.]<br />
====Enabling desktop composition====<br />
As of NVIDIA driver version 180.44, support for GLX with the Damage and Composite X extensions is enabled by default. Refer to [[Composite]] for detailed instructions.<br />
<br />
====Disabling the logo on startup====<br />
Add the {{Codeline|"NoLogo"}} option under section {{Codeline|Device}}:<br />
Option "NoLogo" "1"<br />
<br />
====Enabling hardware acceleration====<br />
{{Note|RenderAccel is enabled by default since drivers version 97.46.xx}}<br />
Add the {{Codeline|"RenderAccel"}} option under section {{Codeline|Device}}:<br />
Option "RenderAccel" "1"<br />
<br />
====Overriding monitor detection====<br />
The {{Codeline|"ConnectedMonitor"}} option under section {{Codeline|Device}} allows to override monitor detection when X server starts, which may save a significant amount of time at start up. The available options are: {{Codeline|"CRT"}} for analog connections, {{Codeline|"DFP"}} for digital monitors and {{Codeline|"TV"}} for televisions.<br />
<br />
The following statement forces the NVIDIA driver to bypass startup checks and recognize the monitor as DFP:<br />
Option "ConnectedMonitor" "DFP"<br />
{{Note| Use "CRT" for all analog 15 pin VGA connections, even if the display is a flat panel. "DFP" is intended for DVI digital connections only.}}<br />
<br />
====Enabling triple buffering====<br />
Enable the use of triple buffering by adding the {{Codeline|"TripleBuffer"}} Option under section {{Codeline|Device}}:<br />
Option "TripleBuffer" "1"<br />
<br />
Use this option if the graphics card has plenty of ram (equal or greater than 128MB). The setting only takes effect when syncing to vblank is enabled, one of the options featured in nvidia-settings.<br />
<br />
{{Note|This option may introduce full-screen tearing and reduce performance.}}<br />
<br />
====Using OS-level events====<br />
Taken from the NVIDIA driver's [http://http.download.nvidia.com/XFree86/Linux-x86/1.0-7182/README/readme.txt README] file: ''"[...] Use OS-level events to efficiently notify X when a client has performed direct rendering to a window that needs to be composited."'' It may help improving performance, but it is currently incompatible with SLI and Multi-GPU modes.<br />
<br />
Add under section {{Codeline|Device}}:<br />
Option "DamageEvents" "1"<br />
{{Note|This option is enabled by default in newer driver versions.}}<br />
<br />
====Enabling power saving====<br />
Add under section <code>Monitor</code>:<br />
Option "DPMS" "1"<br />
<br />
====Forcing Powermizer performance level (for laptops)====<br />
Add under section {{Codeline|Device}}:<br />
# Force Powermizer to a certain level at all times<br />
# level 0x1=highest<br />
# level 0x2=med<br />
# level 0x3=lowest<br />
<br />
# AC settings:<br />
Option "RegistryDwords" "PowerMizerLevelAC=0x3"<br />
# Battery settings:<br />
Option "RegistryDwords" "PowerMizerLevel=0x3"<br />
Settings are better explained in [http://tutanhamon.com.ua/technovodstvo/NVIDIA-UNIX-driver/ NVIDIA Driver for X.org:Performance and Power Saving Hints].<br />
<br />
=====Letting the GPU set its own performance level based on temperature=====<br />
Add under section {{Codeline|Device}}:<br />
Option "RegistryDwords" "PerfLevelSrc=0x3333"<br />
<br />
====Disable vblank interrupts (for laptops)====<br />
When running the interrupt detection utility {{Codeline|powertop}}, it can be observed that the Nvidia driver will generate an interrupt for every vblank. To disable, place in the {{Codeline|Device}} section:<br />
Option "OnDemandVBlankInterrupts" "1"<br />
This will reduce interrupts to about one or two per second.<br />
<br />
====Enabling overclocking====<br />
{{Warning|Please note that overclocking may damage hardware and that no responsibility may be placed on the authors of this page due to any damage to any information technology equipment from operating products out of specifications set by the manufacturer.}}<br />
To enable GPU and memory overclocking, place the following line in the {{Codeline|Device}} section:<br />
Option "Coolbits" "1"<br />
<br />
This will enable on-the-fly overclocking within an X session by running:<br />
$ nvidia-settings<br />
{{Note|GTX 4xx/5xx series Fermi cores cannot currently be overclocked using <br />
the Coolbits method. The alternative is to edit and reflash the GPU BIOS either under DOS (preferred), or within a Win32 environment by way of [http://www.mvktech.net/component/option,com_remository/Itemid,26/func,select/id,127/orderby,2/page,1/ nvflash] and [http://www.mvktech.net/component/option,com_remository/Itemid,26/func,select/id,135/orderby,2/page,1/ NiBiTor 6.0]. The advantage of BIOS flashing is that not only can voltage limits be raised, but stability is generally improved over software overclocking methods such as Coolbits.}}<br />
<br />
===== Setting static 2D/3D clocks =====<br />
Set the following string in the {{Codeline|Device}} section to enable PowerMizer at its maximum performance level:<br />
Option "RegistryDwords" "PerfLevelSrc=0x2222"<br />
Set one of the following two strings in the {{Codeline|Device}} section to enable manual GPU fan control within {{codeline|nvidia-settings}}:<br />
Option "Coolbits" "4"<br />
<br />
Option "Coolbits" "5"<br />
<br />
====Enable screen rotation through XRandR====<br />
Place the following line in the {{Codeline|Device}} section:<br />
Option "RandRRotation" "True"<br />
After restarting Xorg:<br />
$ xrandr -o left<br />
The Screen should be rotated. To restore:<br />
$ xrandr -o normal<br />
{{Note| Editing xorg.conf may be unnecessary since screen rotation should be enabled by default, ideally by using the respective DE tools, such as SystemSettings in KDE.}}<br />
<br />
==Tips and tricks==<br />
===Enabling Pure Video HD (VDPAU/VAAPI)===<br />
'''Hardware Required:''' <br />
<br />
At least a video card with second generation PureVideo HD [http://en.wikipedia.org/wiki/PureVideo_HD#Table_of_PureVideo_.28HD.29_GPUs]<br />
<br />
'''Software Required:'''<br />
<br />
Nvidia video cards with the proprietary driver installed will provide video decoding capabilities with the VDPAU interface at different levels according to PureVideo generation.<br />
<br />
You can also add support for the VA-API interface with:<br />
# pacman -S vdpau-video<br />
<br />
Check VA-API support with:<br />
$ vainfo<br />
<br />
To take full advantage of the hardware decoding capability of your video card you will need a media player that supports VDPAU or VA-API.<br />
<br />
To enable hardware acceleration in '''MPlayer''' edit ~/.mplayer/config<br />
<br />
vo=vdpau<br />
vc=ffmpeg12vdpau,ffwmv3vdpau,ffvc1vdpau,ffh264vdpau,ffodivxvdpau,<br />
<br />
<br />
To enable hardware acceleration in '''VLC''' go:<br />
<br />
Tools -> Settings -> Videos and codec -> check "Use GPU acceleration"<br />
<br />
To enable hardware acceleration in '''smplayer''' go:<br />
<br />
Options -> Preferences -> General -> Video Tab -> select vdpau as output driver<br />
<br />
To enable hardware acceleration in '''gnome-mplayer''' go:<br />
<br />
Edit -> Preferences -> set video output to vdpau<br />
<br />
'''Playing HD movies on cards with low memory:'''<br />
<br />
If your graphic card doesn't have a lot of memory(>521MB?), you can experience glitches when watching 1080p or even 720p movies.<br />
To avoid that start simple window manager like TWM or MWM.<br />
<br />
Additionally increasing the MPlayer's cache size in ~/.mplayer/config can help, when your hard drive is spinning down when watching HD movies.<br />
<br />
===Using TV-out===<br />
A good article on the subject can be found [http://en.wikibooks.org/wiki/NVidia/TV-OUT here]<br />
<br />
===X with a TV (DFP) as the only display===<br />
The X server falls back to CRT-0 if no monitor is automatically detected. This can be a problem when using a DVI connected TV as the main display, and X is started while the TV is turned off or otherwise disconnected.<br />
<br />
To force nvidia to use DFP, store a copy of the EDID somewhere in the filesystem so that X can parse the file instead of reading EDID from the TV/DFP.<br />
<br />
To acquire the EDID, start nvidia-settings. It will show some information in tree format, ignore the rest of the settings for now and select the GPU (the corresponding entry should be titled "GPU-0" or similar), click the "DFP" section (again, "DFP-0" or similar), click on the "Acquire Edid" Button and store it somewhere, for example, {{Filename|/etc/X11/dfp0.edid}}.<br />
<br />
Edit xorg.conf by adding to the "Device" section:<br />
Option "ConnectedMonitor" "DFP"<br />
Option "CustomEDID" "DFP-0:/etc/X11/dfp0.edid"<br />
The "ConnectedMonitor" option forces the driver to recognize the DFP as if it were connected. The "CustomEDID" provides EDID data for the device, meaning that it will start up just as if the TV/DFP was connected during X the process.<br />
<br />
This way, one can automatically start a display manager at boot time and still have a working and properly configured X screen by the time the TV gets powered on.<br />
<br />
===Displaying GPU temperature in the shell===<br />
====Method 1 - nvidia-settings====<br />
{{Note|This method requires that you're using X. Use Method 2 or Method 3 if you are not. Also note that Method 3 currently does not not work with newer nvidia cards such as the G210/220 as well as embedded GPUs such as the Zotac IONITX's 8800GS.}}<br />
<br />
To display the GPU temp in the shell, use nvidia-settings as follows:<br />
$ nvidia-settings -q gpucoretemp<br />
<br />
This will output something similar to the following:<br />
Attribute 'GPUCoreTemp' (hostname:0.0): 41.<br />
'GPUCoreTemp' is an integer attribute.<br />
'GPUCoreTemp' is a read-only attribute.<br />
'GPUCoreTemp' can use the following target types: X Screen, GPU.<br />
<br />
The GPU temps of this board is 41 C.<br />
<br />
In order to get just the temperature for use in utils such as rrdtool or conky, among others:<br />
$ nvidia-settings -q gpucoretemp -t<br />
41<br />
<br />
====Method 2 - nvidia-smi====<br />
<br />
Use nvidia-smi which can read temps directly from the GPU without the need to use X at all. This is important for a small group of users who do not have X running on their boxes, perhaps because the box is headless running server apps. <br />
To display the GPU temp in the shell, use nvidia-smi as follows:<br />
<br />
$ nvidia-smi -a<br />
<br />
This should output something similar to the following:<br />
<pre><br />
$ nvidia-smi -a<br />
<br />
==============NVSMI LOG==============<br />
<br />
<br />
Timestamp : Mon Dec 13 20:11:28 2010<br />
<br />
Driver Version : 260.19.29<br />
<br />
<br />
GPU 0:<br />
Product Name : GeForce 8400 GS<br />
PCI Device/Vendor ID : 6e410de<br />
PCI Location ID : 0:1:0<br />
Board Serial : 2648101198649<br />
Display : Connected<br />
Temperature : 40 C<br />
Utilization<br />
GPU : 1%<br />
Memory : 8%<br />
<br />
</pre><br />
<br />
In order to get just the temperature for use in utils such as rrdtool or conky, among others:<br />
<br />
$ nvidia-smi -a | grep Temp | cut -c17-18<br />
40<br />
<br />
Reference: http://www.question-defense.com/2010/03/22/gpu-linux-shell-temp-get-nvidia-gpu-temperatures-via-linux-cli<br />
<br />
====Method 3 - nvclock====<br />
Use nvclock which is available from the [extra] repo. Note that nvclock cannot access thermal sensors on newer nvidia cards such as the G210/220.<br />
<br />
There can be significant differences between the temperatures reported by nvclock and nvidia-settings/nv-control. According to [http://sourceforge.net/projects/nvclock/forums/forum/67426/topic/1906899 this post] by the author (thunderbird) of nvclock, the nvclock values should be more accurate.<br />
<br />
===Set Fan Speed at Login===<br />
You can adjust the fan speed on your graphics card with {{Codeline|nvidia-settings}}'s console interface. First ensure that your Xorg configuration sets the Coolbits option to 4 or 5 in your {{Codeline|Device}} section to enable fan control.<br />
<br />
Option "Coolbits" "4"<br />
<br />
{{Note|GTX 4xx/5xx series cards cannot currently set fan speeds at login using this method. This method only allows for the setting of fan speeds within the current X session by way of nvidia-settings.}}<br />
<br />
Place the following line in your [[xinitrc|{{filename|~/.xinitrc}}]] file to adjust the fan when you launch Xorg. Replace <n> with the fan speed percentage you want to set.<br />
<br />
nvidia-settings -a "[gpu:0]/GPUFanControlState=1" -a "[fan:0]/GPUCurrentFanSpeed=<n>"<br />
<br />
You can also configure a second GPU by incrementing the GPU and fan number.<br />
<br />
nvidia-settings -a "[gpu:0]/GPUFanControlState=1" \ <br />
-a "[gpu:1]/GPUFanControlState=1" \<br />
-a "[fan:0]/GPUCurrentFanSpeed=<n>" \<br />
-a [fan:1]/GPUCurrentFanSpeed=<n>" &<br />
<br />
If you use a login manager such as GDM or KDM, you can create a desktop entry file to process this setting. Create {{filename|~/.config/autostart/nvidia-fan-speed.desktop}} and place this text inside it. Again, change <n> to the speed percentage you want.<br />
<br />
[Desktop Entry]<br />
Type=Application<br />
Exec=nvidia-settings -a "[gpu:0]/GPUFanControlState=1" -a "[fan:0]/GPUCurrentFanSpeed=<n>"<br />
X-GNOME-Autostart-enabled=true<br />
Name=nvidia-fan-speed<br />
<br />
===Order of install/deinstall for changing drivers===<br />
Where the old driver is nvidiaO and the new driver is nvidiaN.<br />
remove nvidiaO<br />
install nvidia-utilsN<br />
install nvidiaN<br />
install lib32-nvidia-utils-N (if required)<br />
<br />
==Troubleshooting==<br />
<br />
===Gaming using Twinview===<br />
In case you want to play fullscreen games when using Twinview, you will notice that games recognize the two screens as being one big screen. While this is technically correct (the virtual X screen really is the size of your screens combined), you probably don't want to play on both screens at the same time. <br />
<br />
To correct this behavior for SDL, try:<br />
export SDL_VIDEO_FULLSCREEN_HEAD=1<br />
<br />
For OpenGL, add the appropiate Metamodes to your xorg.conf in section {{Codeline|Device}} and restart X:<br />
Option "Metamodes" "1680x1050,1680x1050; 1280x1024,1280x1024; 1680x1050,NULL; 1280x1024,NULL;"<br />
<br />
Another method that may either work alone or in conjunction with those mentioned above is [[Gaming#Starting_games_in_a_separate_X_server|starting games in a separate X server]].<br />
<br />
===Old Xorg Settings===<br />
If upgrading from an old installation, please remove old {{Filename|/usr/X11R6}} paths as it can cause trouble during installation.<br />
<br />
===Corrupted screen: "Six screens" issue===<br />
For some users using Geforce GT 100M's, the screen turns out corrupted after X starts; divided into 6 sections with a resolution limited to 640x480.<br />
<br />
To solve this problem, enable the Validation Mode {{Codeline|NoTotalSizeCheck}} in section {{Codeline|Device}}:<br />
Section "Device"<br />
...<br />
Option "ModeValidation" "NoTotalSizeCheck"<br />
...<br />
EndSection<br />
==='/dev/nvidia0' Input/Output error===<br />
This error can occur for several different reasons, and the most common solution given for this error is to check for group/file permissions, which in almost every case is ''not'' the issue. The Nvidia documentation does not talk in detail on what you should<br />
do to correct this problem but there are a few things that have worked for some people. The problem can be a IRQ conflict with another device or bad routing by either the kernel or your BIOS.<br />
<br />
First thing to try is to remove other video devices such as video capture cards and see if the problem goes away. If there are too many video processors on the same system it can lead into the kernel being unable to start them because of memory allocation problems with the video controller. In particular on systems with low video memory this can occur even if there's only one video processor. In such case you should find out the amount of your system's video memory (e.g. with ''lspci -v'') and pass allocation parameters to the kernel, e.g.:<br />
vmalloc=64M<br />
or<br />
vmalloc=256M<br />
<br />
Another thing to try is to change your BIOS IRQ routing from ''Operating system controlled'' to ''BIOS controlled'' or the other way around. The first one can be passed as a kernel parameter:<br />
PCI=biosirq<br />
<br />
The ''noacpi'' kernel parameter has also been suggested as a solution but since it disables ACPI completely it should be used with caution. Some hardware are easily damaged by overheating.<br />
<br />
{{Note|The kernel parameters can be passed either through the kernel command line or the bootloader configuration file. See your bootloader Wiki page for more information.}}<br />
<br />
==='/dev/nvidiactl' errors===<br />
Trying to start an opengl application might result in errors such as:<br />
Error: Could not open /dev/nvidiactl because the permissions are too<br />
restrictive. Please see the <code>FREQUENTLY ASKED QUESTIONS</code> <br />
section of <code>/usr/share/doc/NVIDIA_GLX-1.0/README</code> <br />
for steps to correct.<br />
<br />
Solve by adding the appropiate user to the "video" group and relogin:<br />
# gpasswd -a username video<br />
<br />
===32 bit applications do not start===<br />
Under 64 bit systems, installing {{Codeline|lib32-nvidia-utils}} that corresponds to the same version installed for the 64 bit driver fixes the issue.<br />
<br />
===Errors after updating the kernel===<br />
If a custom build of nvidia's module is used instead of the package from [extra], a recompile is required every time the kernel is updated. Rebooting is generally recommended after updating kernel and graphic drivers.<br />
<br />
===Crashing in general===<br />
* Try disabling {{Codeline|RenderAccel}} in xorg.conf.<br />
* If Xorg outputs an error about "conflicting memory type" or "failed to allocate primary buffer: out of memory", add {{Codeline|nopat}} at the end of the {{Codeline|kernel}} line in {{Codeline|/boot/grub/menu.lst}}.<br />
* If the NVIDIA compiler complains about different versions of GCC between the current one and the one used for compiling the kernel, add in {{Codeline|/etc/profile}}:<br />
export IGNORE_CC_MISMATCH=1<br />
* If Xorg is crashing with a "Signal 11" while using nvidia-96xx drivers, try disabling PAT. Pass the argument {{Codeline|nopat}} to the {{Codeline|kernel}} line in {{Codeline|menu.lst}}.<br />
More information about trouble-shooting the driver can be found in the [http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14 NVIDIA forums.]<br />
<br />
===Bad performance after installing a new driver version===<br />
If FPS have dropped in comparison with older drivers, first check if direct rendering is turned on: <br />
$ glxinfo | grep direct<br />
If the command prints:<br />
direct rendering: No <br />
then that could be an indication for the sudden FPS drop.<br />
<br />
A possible solution could be to regress to the previously installed driver version and rebooting afterwards.<br />
<br />
===CPU spikes with 400 series cards===<br />
If you're experiencing intermittent CPU spikes with a 400 series card, it may be caused by PowerMizer constantly changing the GPU's clock frequency. Switching PowerMizer's setting from Adaptive to Performance, add the following to the Device section of your Xorg configuration:<br />
<br />
Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x3322; PowerMizerDefaultAC=0x1"<br />
<br />
===Laptops: X hangs on login/out, worked around with Ctrl+Alt+Backspace===<br />
If while using the legacy nvidia drivers Xorg hangs on login and logout (particularly with an odd screen split into two black and white/gray pieces), but logging in is still possible via Ctrl-Alt-Backspace (or whatever the new "kill X" keybind is), try adding this in {{Filename|/etc/modprobe.d/modprobe.conf}}:<br />
options nvidia NVreg_Mobile=1<br />
<br />
One user had luck with this instead, but it makes performance drop significantly for others:<br />
options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660 NVreg_SoftEDIDs=0 NVreg_Mobile=1<br />
<br />
Note that {{Codeline|NVreg_Mobile}} needs to be changed according to the laptop:<br />
* 1 for Dell laptops.<br />
* 2 for non-Compal Toshiba laptops.<br />
* 3 for other laptops.<br />
* 4 for Compal Toshiba laptops.<br />
* 5 for Gateway laptops.<br />
<br />
See [http://http.download.nvidia.com/XFree86/Linux-x86/1.0-7182/README/readme.txt NVIDIA Driver's Readme:Appendix K] for more information.<br />
<br />
===Refresh rate not detected properly by XRandR dependant utilities===<br />
The XRandR X extension is not presently aware of multiple display devices on a single X screen; it only sees the {{Codeline|MetaMode}} bounding box, which may contain one or more actual modes. This means that if multiple MetaModes have the same bounding box, XRandR will not be able to distinguish between them.<br />
<br />
In order to support {{Codeline|DynamicTwinView}}, the NVIDIA driver must make each MetaMode appear to be unique to XRandR. Presently, the Nvidia driver accomplishes this by using the refresh rate as a unique identifier.<br />
<br />
Use {{Codeline|nvidia-settings -q RefreshRate}} to query the actual refresh rate on each display device.<br />
<br />
The XRandR extension is currently being redesigned by the X.Org community, so the refresh rate workaround may be removed at some point in the future.<br />
<br />
This workaround can also be disabled by setting the "DynamicTwinView" X configuration option to "false", which will disable NV-CONTROL support for manipulating MetaModes, but will cause the XRandR and XF86VidMode visible refresh rate to be accurate.<br />
<br />
==External links==<br />
* [http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14 NVIDIA forums]<br />
* [http://http.download.nvidia.com/XFree86/Linux-x86/1.0-7182/README/readme.txt Official readme for NVIDIA drivers]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Suspend2&diff=135682
Suspend2
2011-04-02T15:23:20Z
<p>Cantabile: Why are page titles case sensitive?</p>
<hr />
<div>#REDIRECT [[TuxOnIce]]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Suspend2&diff=135681
Suspend2
2011-04-02T15:22:32Z
<p>Cantabile: Suspend2 was renamed to Tuxonice a while ago - redirect to the that page</p>
<hr />
<div>#REDIRECT [[Tuxonice]]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Arch_Linux_VirtualBox_Guest&diff=135041
Arch Linux VirtualBox Guest
2011-03-27T17:04:10Z
<p>Cantabile: /* virtualbox-ext-oracle */ install base-devel rather than make and gcc; don't install the entire xorg group, it now contains *a lot* of unnecessary packages</p>
<hr />
<div>{{out of date}}<br />
Installing Arch under [[VirtualBox]] is straightforward. Once the install is done, if you want the guest additions under X, you have two choices:<br />
The GPL virtual box additions which are in the ArchLinux repositories, or the additions provided by Oracle.<br />
<br />
Follow these instructions after doing a basic install following the [[Beginners' Guide]].<br />
<br />
The file locations and script names are slightly different between the GPL and PUEL versions of Virtualbox (See below). For both versions, the install of VBoxLinuxAdditions will build and install the kernel modules, install the Xorg drivers and create init scripts. It will most probably print out errors about init scripts and run levels, which can (in most cases) be ignored.<br />
Among the files created, {{Filename|/etc/rc.d/rc.vboxadd}} will load the Guest Additions on demand. <br />
<br />
==virtualbox - GPL Version==<br />
Install the required package and kernel headers:<br />
# pacman -S virtualbox-additions kernel26-headers xorg-server base-devel<br />
Now, mount the installed ISO containing the additions:<br />
# modprobe loop<br />
# mount /usr/lib/virtualbox/additions/VBoxGuestAdditions.iso /mnt -o loop<br />
Run the installer:<br />
# sh /mnt/VBoxLinuxAdditions.run<br />
Add it to the {{Codeline|DAEMONS}} array to load on boot:<br />
DAEMONS=(... '''rc.vboxadd''')<br />
<br />
==virtualbox-ext-oracle==<br />
Install the kernel headers, xorg (if it's not already installed), and the build tools :<br />
# pacman -S kernel26-headers xorg-server base-devel<br />
Make the guest additions "CD" available to the guest OS by clicking Devices->Install Guest Additions.<br />
<br />
Now, mount the installed ISO containing the additions from the host, this connects a disk to /dev/cdrom:<br />
# mkdir /mnt/cdrom<br />
# mount /dev/cdrom /mnt/cdrom<br />
Run the installer script which tests the proper architecture and installs the additions:<br />
# /mnt/cdrom/VBoxLinuxAdditions.run<br />
{{Note|'''rc.vboxadd''' is automatically run from /etc/rc.local}}<br />
<br />
==Enabling OpenGL acceleration in Arch Linux guests==<br />
<br />
*Make sure the user starting X in the guest is in the '''video''' group.<br />
*Make sure you have checked '3D acceleration' under the VirtualBox settings on the host.<br />
*Make sure you have installed drivers for your graphics card. Nvidia, ATI or Intel (xf86-video-fbdev)<br />
<br />
{{Note | Don't compare before-after performance using glxgears! You may get a lot less FPS due to now-working vsync support. Compare performance using a real, heavy 3D application (like a game).}}<br />
<br />
<br />
----<br />
<br />
{{Note|If you upgrade the kernel in the Virtual Machine you will need to re-install the Guest Additions in order for some features to work properly.}}<br />
<br />
If you need to rebuild the Virtual Box Additions in a guest installation of Arch Linux, use this command:<br />
# /etc/rc.d/rc.vboxadd setup<br />
<br />
===Copy and paste is not working in Arch guests!===<br />
You forgot to start VBoxclient-all. See above.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Arch_Linux_VirtualBox_Guest&diff=135040
Arch Linux VirtualBox Guest
2011-03-27T17:01:13Z
<p>Cantabile: /* virtualbox - GPL Version */ don't install the entire xorg group, it contains now *a lot* of unnecessary packages</p>
<hr />
<div>{{out of date}}<br />
Installing Arch under [[VirtualBox]] is straightforward. Once the install is done, if you want the guest additions under X, you have two choices:<br />
The GPL virtual box additions which are in the ArchLinux repositories, or the additions provided by Oracle.<br />
<br />
Follow these instructions after doing a basic install following the [[Beginners' Guide]].<br />
<br />
The file locations and script names are slightly different between the GPL and PUEL versions of Virtualbox (See below). For both versions, the install of VBoxLinuxAdditions will build and install the kernel modules, install the Xorg drivers and create init scripts. It will most probably print out errors about init scripts and run levels, which can (in most cases) be ignored.<br />
Among the files created, {{Filename|/etc/rc.d/rc.vboxadd}} will load the Guest Additions on demand. <br />
<br />
==virtualbox - GPL Version==<br />
Install the required package and kernel headers:<br />
# pacman -S virtualbox-additions kernel26-headers xorg-server base-devel<br />
Now, mount the installed ISO containing the additions:<br />
# modprobe loop<br />
# mount /usr/lib/virtualbox/additions/VBoxGuestAdditions.iso /mnt -o loop<br />
Run the installer:<br />
# sh /mnt/VBoxLinuxAdditions.run<br />
Add it to the {{Codeline|DAEMONS}} array to load on boot:<br />
DAEMONS=(... '''rc.vboxadd''')<br />
<br />
==virtualbox-ext-oracle==<br />
Install the kernel headers, xorg (if it's not already installed), and the build tools :<br />
# pacman -S kernel26-headers xorg gcc make<br />
Make the guest additions "CD" available to the guest OS by clicking Devices->Install Guest Additions.<br />
<br />
Now, mount the installed ISO containing the additions from the host, this connects a disk to /dev/cdrom:<br />
# mkdir /mnt/cdrom<br />
# mount /dev/cdrom /mnt/cdrom<br />
Run the installer script which tests the proper architecture and installs the additions:<br />
# /mnt/cdrom/VBoxLinuxAdditions.run<br />
{{Note|'''rc.vboxadd''' is automatically run from /etc/rc.local}}<br />
<br />
==Enabling OpenGL acceleration in Arch Linux guests==<br />
<br />
*Make sure the user starting X in the guest is in the '''video''' group.<br />
*Make sure you have checked '3D acceleration' under the VirtualBox settings on the host.<br />
*Make sure you have installed drivers for your graphics card. Nvidia, ATI or Intel (xf86-video-fbdev)<br />
<br />
{{Note | Don't compare before-after performance using glxgears! You may get a lot less FPS due to now-working vsync support. Compare performance using a real, heavy 3D application (like a game).}}<br />
<br />
<br />
----<br />
<br />
{{Note|If you upgrade the kernel in the Virtual Machine you will need to re-install the Guest Additions in order for some features to work properly.}}<br />
<br />
If you need to rebuild the Virtual Box Additions in a guest installation of Arch Linux, use this command:<br />
# /etc/rc.d/rc.vboxadd setup<br />
<br />
===Copy and paste is not working in Arch guests!===<br />
You forgot to start VBoxclient-all. See above.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Arch_Linux_VirtualBox_Guest&diff=135038
Arch Linux VirtualBox Guest
2011-03-27T16:47:06Z
<p>Cantabile: /* virtualbox - GPL Version */ install base-devel rather than gcc and make</p>
<hr />
<div>{{out of date}}<br />
Installing Arch under [[VirtualBox]] is straightforward. Once the install is done, if you want the guest additions under X, you have two choices:<br />
The GPL virtual box additions which are in the ArchLinux repositories, or the additions provided by Oracle.<br />
<br />
Follow these instructions after doing a basic install following the [[Beginners' Guide]].<br />
<br />
The file locations and script names are slightly different between the GPL and PUEL versions of Virtualbox (See below). For both versions, the install of VBoxLinuxAdditions will build and install the kernel modules, install the Xorg drivers and create init scripts. It will most probably print out errors about init scripts and run levels, which can (in most cases) be ignored.<br />
Among the files created, {{Filename|/etc/rc.d/rc.vboxadd}} will load the Guest Additions on demand. <br />
<br />
==virtualbox - GPL Version==<br />
Install the required package and kernel headers:<br />
# pacman -S virtualbox-additions kernel26-headers xorg base-devel<br />
Now, mount the installed ISO containing the additions:<br />
# modprobe loop<br />
# mount /usr/lib/virtualbox/additions/VBoxGuestAdditions.iso /mnt -o loop<br />
Run the installer:<br />
# sh /mnt/VBoxLinuxAdditions.run<br />
Add it to the {{Codeline|DAEMONS}} array to load on boot:<br />
DAEMONS=(... '''rc.vboxadd''')<br />
<br />
==virtualbox-ext-oracle==<br />
Install the kernel headers, xorg (if it's not already installed), and the build tools :<br />
# pacman -S kernel26-headers xorg gcc make<br />
Make the guest additions "CD" available to the guest OS by clicking Devices->Install Guest Additions.<br />
<br />
Now, mount the installed ISO containing the additions from the host, this connects a disk to /dev/cdrom:<br />
# mkdir /mnt/cdrom<br />
# mount /dev/cdrom /mnt/cdrom<br />
Run the installer script which tests the proper architecture and installs the additions:<br />
# /mnt/cdrom/VBoxLinuxAdditions.run<br />
{{Note|'''rc.vboxadd''' is automatically run from /etc/rc.local}}<br />
<br />
==Enabling OpenGL acceleration in Arch Linux guests==<br />
<br />
*Make sure the user starting X in the guest is in the '''video''' group.<br />
*Make sure you have checked '3D acceleration' under the VirtualBox settings on the host.<br />
*Make sure you have installed drivers for your graphics card. Nvidia, ATI or Intel (xf86-video-fbdev)<br />
<br />
{{Note | Don't compare before-after performance using glxgears! You may get a lot less FPS due to now-working vsync support. Compare performance using a real, heavy 3D application (like a game).}}<br />
<br />
<br />
----<br />
<br />
{{Note|If you upgrade the kernel in the Virtual Machine you will need to re-install the Guest Additions in order for some features to work properly.}}<br />
<br />
If you need to rebuild the Virtual Box Additions in a guest installation of Arch Linux, use this command:<br />
# /etc/rc.d/rc.vboxadd setup<br />
<br />
===Copy and paste is not working in Arch guests!===<br />
You forgot to start VBoxclient-all. See above.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Laptop/HP&diff=134288
Laptop/HP
2011-03-19T14:54:27Z
<p>Cantabile: /* */ updated info about 6720s</p>
<hr />
<div>{| style="background-color: #f3f9ff; margin: 1em 2.5% 0 2.5%; padding: 3px 3px; border: 1px solid #aaa;"<br />
|-<br />
|align="center"|'''[[HCL|Hardware Compatibility List]] - [[HCL/Laptops|Laptops main page]]''' <br> [[HCL/Laptops/Acer|Acer]] - [[HCL/Laptops/Apple|Apple]] - [[HCL/Laptops/Asus|Asus]] - [[HCL/Laptops/Compaq|Compaq]] - [[HCL/Laptops/Dell|Dell]] - [[HCL/Laptops/Digital|Digital]] - [[HCL/Laptops/ECS|ECS]] - [[HCL/Laptops/Siemens-Fujitsu|Siemens-Fujitsu]] - [[HCL/Laptops/Gateway|Gateway]] - [[HCL/Laptops/Hitachi|Hitachi]] - [[HCL/Laptops/Higrade|Higrade]] - [[HCL/Laptops/HP|HP]] - [[HCL/Laptops/IBM|IBM/Lenovo]] - [[HCL/Laptops/Medion|Medion]] - [[HCL/Laptops/Micron|Micron]] - [[HCL/Laptops/Mitac|Mitac]] - [[HCL/Laptops/Mitsubishi|Mitsubishi]] - [[HCL/Laptops/NEC|NEC]] - [[HCL/Laptops/Panasonic|Panasonic]] - [[HCL/Laptops/Samsung|Samsung]] - [[HCL/Laptops/Sony|Sony]] - [[HCL/Laptops/Toshiba|Toshiba]] - [[HCL/Laptops/Zenith|Zenith]] - [[HCL/Laptops/Other|Other]]<br />
|}<br />
<br />
<br />
[[Category:Hardware Compatibility List (English)]]<br />
<br />
<br />
<br />
{| align="right" width="300px" style="background-color: #f3f9ff; margin: 1em 2.5% 0 2.5%; padding: 3px; border: 1px solid #aaa;"<br />
| style="background-color:white" | <small>'''[[HCL|Hardware Compatibility List (HCL)]]'''</small><br />
|-<br />
|<small> ''Full Systems'' </small><br />
|-<br />
|<small>[[HCL/Laptops|Laptops]] - [[HCL/Desktops|Desktops]] - [[HCL/Servers|Servers]] - [[HCL/Virtual Machines|Virtual Machines]]</small><br />
|-<br />
|<small>''Components''</small><br />
|-<br />
|<small>[[HCL/Video Cards|Video Cards]] - [[HCL/Sound Cards|Sound Cards]] - [[HCL/Network Adapters (Wired)|Wired Net Adapters]] - [[HCL/Modems|Modems]] - [[HCL/Network Adapters (Wireless)|Wireless Adapters]] - [[HCL/Monitors|Monitors]] - [[HCL/Bluetooth Adapters|Bluetooth Adapters]] - [[HCL/Printers|Printers]] - [[HCL/Scanners|Scanners]] - [[HCL/TV Cards|TV Cards]] - [[HCL/Digital Cameras|Digital Cameras]] - [[HCL/Web Cameras|Web Cameras]] - [[HCL/UPS|UPS]] - [[HCL/Floppy Drives|Floppy Drives]] - [[HCL/CD and DVD Writer/Readers|CD and DVD Writer/Readers]] - [[HCL/SCSI Adapters|SCSI Adapters]] - [[HCL/Gadgets|Gadgets]] - [[HCL/SATA IDE Cards|SATA IDE Cards]] - [[HCL/Keyboards|Keyboards]] - [[HCL/Main Boards|Main Boards]] - [[HCL/RAID Controllers|RAID Controllers]]</small><br />
|}<br />
<br />
= Model Version =<br />
<br />
== ==<br />
<br />
<br><br><br><br><br><br><br><br><br><br />
{| border="1" cellpadding="2" cellspacing="0"<br />
! rowspan=2 | Model Version:<br />
! rowspan=2 | Arch Linux <br>Install CD Version:<br> <br />
! colspan=8 | Hardware Support:<br />
! rowspan=2 | Remark:<br />
|- <br />
! Video: || Sound: || Ethernet: || Wireless: || Bluetooth: || Power<br>Management:<br> || Modem: || Other:<br />
|-<br />
|HP Compaq Mini 730|| 2009.02 || Intel GMA 950<br/>driver: <em>intel</em> || Intel HDA <br/>driver: <em>snd_hda_intel</em> || Broadcom<br/>driver: <em>tg3</em> || Broadcom 4312<br/>driver: <em>wl</em> || Yes ||Suspend to<br/>RAM: Yes<br>Disk: Yes<br/>Battery: Yes<br/>Dimming of display: Yes<br/>Frequency scaling of CPU: Yes|| <br/> || <br/><br />
||<br />
|-<br />
|-<br />
|HP Compaq 6715S||0.8 Voodoo|| ATI Radeon X1250<br/>driver: <em>catalyst</em> || AD1981 <br/>driver: <em>snd_hda_intel</em> || Broadcom<br/>driver: <em>tg3</em> || Broadcom 4312<br/>driver: <em>ndiswrapper</em> <br /> (Problematic with 64-bit arch) || Yes ||Suspend to<br/>RAM: Yes<br>Disk: Yes<br/>Battery: Yes<br/>Dimming of display: Yes<br/>Frequency scaling of CPU: Yes|| not tested || Hotkeys: Yes <br /> Lightscribe: untested <br/><br />
||<br />
|-<br />
|HP Compaq 6720S|| 2009.2 || Intel X3100<br/>driver: <em>xf86-video-intel</em> || Intel HDA<br/>driver: <em>snd_hda_intel</em> || Intel 10/100<br/>driver: <em>e1000e</em> || Intel 3945<br/>driver: <em>iwl3945</em> <br /> Broadcom 4312<br/>driver: <em>wl</em> [http://aur.archlinux.org/packages.php?ID=19514 AUR] || Yes, <em>bluez-utils</em> ||ACPI: Yes<br/>Suspend to<br/>RAM: Yes<br>Disk: Yes<br/>Battery: Yes<br/>Dimming of display: Yes<br/>Frequency scaling of CPU: Yes, cpudyn|| not tested || Hotkeys: Configurable<br /> Lightscribe: Yes [http://aur.archlinux.org/packages.php?ID=7779 AUR] <br/><br />
||<br />
|-<br />
|Pavilion DV2172EA||Duke 2007.05|| Nvidia Go7200<br/>driver <em>nvidia</em> || Intel 82801G<br/>with internal microphones<br/>driver <em>snd_hda_intel</em> || Yes<br/>driver <em>e100</em> || Intel 3945<br/>driver <em>ipw3945</em> || Yes ||Suspend to<br/>RAM: Yes<br>Disk: Yes<br/>Battery: Yes<br/>Dimming of display: Yes<br/>Frequency scaling of CPU: Yes || Yes || Hotkeys: Yes<br/>Remote: Yes<br/>Webcam: Yes<br/>(<em>uvcvideo</em>)<br/>IRDA: Yes<br/>Lightscribe: untested<br />
||<br />
|-<br />
|Pavilion DM1-1150SL||2009.02|| Intel X4500MHD<br/>driver <br><em>xf86-video-intel</em><br/> || Intel 82801G<br/>with internal microphones<br/>driver <em>snd_hda_intel</em> || Yes(RTL8101E)<br/>driver <em>r8169</em> || Atheros AR9285<br/>driver <em>ath9k</em> || Yes ||Suspend to<br/>RAM: Yes<br>Disk: Yes<br/>Battery: Yes<br/>Dimming of display: Yes<br/>Frequency scaling of CPU: n/a || Yes || Hotkeys: Yes<br/>Webcam: Yes<br/>(<em>uvcvideo</em>)<br/><br />
||<br />
|-<br />
|HP Pavilion dv5055ea || 2009.06 || ATI Radeon XPRESS 200M || ATI IXP SB400 AC'97 Audio Controller (rev 02) || Realtek RTL-8139/8139C/8139C+ (rev 10) || Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02) || N/A || Suspend to RAM: not tested<br />Suspend to Disk: not tested<br />Battery: Yes<br />Dimming of display: Yes<br />Frequency scaling of CPU: Odd on battery, Yes on AC || not tested || Hotkeys: Yes for Sound and WLAN. and no for DVD and Multimedia button ||<br />
|-<br />
|HP Pavilion dv6605ed || 2007.08-2 || Intel X3100 ''(xf86-video-intel)'' || Intel 82801H ''(snd-hda-intel)'' || RTL8101e ''(r8139)'' || Broadcom BCM94311MCG<br />''b43'': No (may need different firmware)<br />''ndiswrapper'': Yes || N/A || ACPI: Yes<br />Suspend to RAM: Yes<br />Suspend to Disk: No<br />Battery: Yes<br />Display dimming: Yes<br />CPU frequency scaling: Yes ''(p4-clockmod)'' || not tested || Hotkeys: Yes ''(HP keymap)''<br />Remote: Yes, ''except for DVD, Quickplay and Windows MCE buttons''<br />Lightscribe: not tested ||<br />
|-<br />
|HP Pavilion dv9530em || 2009.06 || nVidia GeForce 8400M GS || Realtek ALC268 || RTL8168b/8111b || Intel 3945 ''(iwl3945)'' || yes || Suspend to RAM: Yes<br />Suspend to Disk: Yes<br />Battery: Yes<br />Dimming of display: Yes<br />Frequency scaling of CPU: Yes || not tested || Hotkeys: Yes<br />Lightscribe: not tested ||<br />
|-<br />
|HP Pavilion TX1220US(GA647UA) || Overlord || nVidia Gefore Go 6150 (works with '''nvidia''') || nVidia Corporation MCP51 High Definition Audio (works with '''snd-hda-intel''') || nVidia Corporation MCP51 Ethernet Controller (works with '''forcedeth''') || Broadcom 4321 card (works with '''ndiswrapper''' and Broadcom released linux drivers: [http://aur.archlinux.org/packages.php?ID=19514 pkg]) || not tested || not tested || not tested || Touch Screen (appears to work, have not calibrated)<br />Remote (not working)<br />Hotkeys (not tested)<br /> Lightscribe (not tested)|| People with this same laptop have gotten the hotkeys and touch screen to work on other distros. I'm sure you can figure it out with some work :-)<br />
|-<br />
|HP 8510W || 2008 || NVIDIA FX570M ''(nvidia driver'' || Intel soundcard ''(snd-hda-intel)'' || Ethernet Port ''(e1000)'' || Intel Wireless ''(iwl4965)'' || || ACPI: Yes<br />Suspend to RAM: Yes<br/> Suspend to Disk: Yes <br/>Battery: Yes<br />Display Dimming: Yes (using nvclock)<br /> CPU frequency scaling:Yes ''(acpi-cpufreq)'' || not tested || Hotkey: Yes <br /> DVD/CD: Yes<br /> SD-Slot: Yes<br />Touchkeys: Yes<br /> Firewire: Untested<br />||<br />
|-<br />
|[[HP tx2z]] || 2009.08 || Radeon HD 3200<br/>driver: ''radeon'' || Intel HDA<br/>driver: ''snd-hda-intel'' || RTL8111/8168B<br/>driver: ''r8169'' || Broadcom 4322<br/>driver: ''wl'' [http://aur.archlinux.org/packages.php?ID=19514 AUR] || not tested || not tested || not tested || hotkeys: yes<br/>litescribe: not tested<br/>webcam: yes<br/>touchscreen: works<br/>stylus: still working on<br/>Media reader: works || some known successes with touchscreen and stylus in ubuntu<br />
|-<br />
|[[HP Pavilion DV3-2155MX]] || 2010.05 || --<br/>-- || --<br/>-- || -- || --<br/>-- || -- || --<br/>--<br/>--<br/>--<br/>--<br/>--<br/>-- || -- || --<br/>--<br/>--<br/>||--||<br />
|-<br />
|HP Pavilion dv6-2115sa || 2010.05 || Radeon HD 4200 series<br/>Works well with open source radeon driver || Intel HDA<br/>driver: ''snd-hda-intel'' || unknown || Broadcom Wireless<br/>works OOTB || not tested || ACPI: Yes<br/>Suspend to RAM: No<br/>Suspend to Disk: Yes, with TuxOnIce<br/>Battery: Yes<br/>Remote: Some buttons don't work<br/>Display Dimming: Yes<br/> CPU Freq Scaling: Yes, with K8 Driver || not tested || hotkeys: yes<br/>Lightscribe: not tested<br/>Webcam: yes<br/>||To prevent output to both headphones and speakers simultaneously, add ''options snd-hda-intel model=hp-dv5'' to /etc/modprobe.d/modprobe.conf||</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Syslinux&diff=130917
Syslinux
2011-02-14T16:47:05Z
<p>Cantabile: /* MBR Partition Table */ mention a few apps which can set the bootable flag</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
{{i18n|Syslinux}}<br />
<br />
{{Article summary start}}<br />
{{Article summary text|Describes installing and configuring Syslinux, a collection of bootloaders.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Boot process overview}}}}<br />
{{Article summary end}}<br />
<br />
Syslinux is a collection of boot loaders capable of booting from hard drives, CDs and over the network via PXE. It supports the fat, ext2, ext3, ext4 and btrfs file systems.<br />
<br />
{{Note|Since Syslinux 4, Extlinux and Syslinux are the same thing.}} <br />
<br />
== Syslinux Boot Process ==<br />
<br />
At boot, the computer loads the [[MBR]] ({{Filename|/usr/lib/syslinux/mbr.bin}}). Then the MBR looks for the partition that is marked as active (boot flag). Once found, the volume boot record (VBR) will be executed. In the case of ext2/3/4 and fat12/16/32, the starting sector of {{Filename|ldlinux.sys}} is hard-coded into the VBR. The VBR will execute ({{Filename|ldlinux.sys}}). Therefore, if the location of {{Filename|ldlinux.sys}} changes, syslinux will no longer boot. In the case of btrfs, the above method will not work since files move around resulting in the sector location of {{Filename|ldlinux.sys}} changing. Therefore, the entire Syslinux code needs to be stored outside the filesystem. The code is stored in the sectors following the VBR. Once Syslinux is fully loaded, it looks for a configuration file, either {{Filename|extlinux.conf}} or {{Filename|syslinux.cfg}}. If one is found, the configuration file is loaded. If no configuration file is found you will be given a syslinux prompt.<br />
<br />
== Installing syslinux ==<br />
{{Note| If you are unsure of which partition table you are using (MBR or GPT), you are likely using the MBR partition table.}}<br />
<br />
{{Note| If you are trying to rescue an installed system with a live CD, be sure to [[Change_Root|chroot]] into it before executing these commands.}}<br />
<br />
Make sure you have the ''syslinux'' package installed. Then install Syslinux onto your boot partition, which must contain a fat, ext2, ext3, ext4, or btrfs file system.<br />
# mkdir /boot/syslinux<br />
# extlinux --install /boot/syslinux #run on a mounted directory (not /dev/sdXY)<br />
/boot/syslinux/ is device /dev/sda1<br />
<br />
===MBR Partition Table===<br />
Next, you need mark your boot partition active in your partition table. Applications capable of doing this include fdisk, cfdisk, sfdisk, (g)parted. It should look like this:<br />
# fdisk -l /dev/sda<br />
[...]<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 * 2048 104447 51200 83 Linux<br />
/dev/sda2 104448 625142447 312519000 83 Linux<br />
<br />
Install the master boot record:<br />
# cat /usr/lib/syslinux/mbr.bin > /dev/sda<br />
<br />
===GUID Partition Table aka GPT===<br />
<br />
Main article [[GUID_Partition_Table]]<br />
<br />
Bit 2 of the attributes for the /boot partition need to be set.<br />
<br />
# sgdisk /dev/hda --attributes=1:set:2<br />
<br />
This would toggle the attribute legacy bios bootable on partition 1 <br />
<br />
Verify:<br />
# sgdisk /dev/sda --attributes=1:show<br />
1:2:1 (legacy BIOS bootable)<br />
<br />
Install the master boot record:<br />
# cat /usr/lib/syslinux/gptmbr.bin > /dev/sda<br />
<br />
===Rebooting===<br />
When you reboot your system now, you will have a syslinux prompt. To automatically boot your system or get a boot menu, you still need to create a configuration file.<br />
<br />
== Configuring syslinux ==<br />
<br />
The syslinux configuration file, {{Filename|syslinux.cfg}} should be created in the same directory where you installed syslinux. In our case '/boot/syslinux/'<br />
<br />
The bootloader will look for either {{Filename|syslinux.cfg}} (preferred) or {{Filename| extlinux.conf}}<br />
<br />
'''Tips''':<br />
*Instead of LINUX, the keyword KERNEL can also be used. KERNEL tries to detect the type of the file, while LINUX always expects a Linux kernel.<br />
*TIMEOUT value is in units of 1/10 of a second.<br />
<br />
=== Examples ===<br />
{{Note| All examples will assumes that /boot is a separate mount point. If /boot is the same partition as /, you have to replace ''/vmlinuz26'' by ''/boot/vmlinuz26'' and so on.}}<br />
<br />
==== Basic Syslinux Config ====<br />
<br />
This is a simple configuration file that will show a boot: prompt and automatically boot after 5 seconds.<br />
<br />
Config:<br />
PROMPT 1<br />
TIMEOUT 50<br />
DEFAULT arch<br />
<br />
LABEL arch<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
LABEL archfallback<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26-fallback.img<br />
<br />
If you want to boot directly without seeing a prompt, set PROMPT to 0. <br />
<br />
==== Text Boot menu ====<br />
<br />
Syslinux also allows you to use a boot menu. To use it, copy the menu COM32 module to your syslinux folder:<br />
# cp /usr/lib/syslinux/menu.c32 /boot/syslinux/<br />
If /boot is the same partition as /, a symlink will also work:<br />
# ln -s /usr/lib/syslinux/menu.c32 /boot/syslinux/<br />
<br />
Config:<br />
UI menu.c32<br />
PROMPT 0<br />
<br />
MENU TITLE Boot Menu<br />
TIMEOUT 50<br />
DEFAULT arch<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
LABEL archfallback<br />
MENU LABEL Arch Linux Fallback<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26-fallback.img<br />
<br />
For more details about the menu system, see http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=doc/menu.txt.<br />
<br />
==== Graphical Boot menu ====<br />
<br />
Syslinux also allows you to use a graphical boot menu. To use it, copy the vesamenu COM32 module to your syslinux folder:<br />
# cp /usr/lib/syslinux/vesamenu.c32 /boot/syslinux/<br />
If /boot is the same partition as /, a symlink will also work:<br />
# ln -s /usr/lib/syslinux/vesamenu.c32 /boot/syslinux/<br />
<br />
This config uses the same menu design as the Arch Install CD: [http://projects.archlinux.org/archiso.git/tree/configs/syslinux-iso/boot-files/syslinux/syslinux.cfg syslinux.cfg]<br />
<br />
The background file can be found here: [http://projects.archlinux.org/archiso.git/plain/configs/syslinux-iso/boot-files/splash.png splash.png]<br />
<br />
Config:<br />
UI vesamenu.c32<br />
DEFAULT arch<br />
PROMPT 0<br />
MENU TITLE Boot Menu<br />
MENU BACKGROUND splash.png<br />
TIMEOUT 50<br />
<br />
MENU WIDTH 78<br />
MENU MARGIN 4<br />
MENU ROWS 5<br />
MENU VSHIFT 10<br />
MENU TIMEOUTROW 13<br />
MENU TABMSGROW 11<br />
MENU CMDLINEROW 11<br />
MENU HELPMSGROW 16<br />
MENU HELPMSGENDROW 29<br />
<br />
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu<br />
<br />
MENU COLOR border 30;44 #40ffffff #a0000000 std<br />
MENU COLOR title 1;36;44 #9033ccff #a0000000 std<br />
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all<br />
MENU COLOR unsel 37;44 #50ffffff #a0000000 std<br />
MENU COLOR help 37;40 #c0ffffff #a0000000 std<br />
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std<br />
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std<br />
MENU COLOR msg07 37;40 #90ffffff #a0000000 std<br />
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std<br />
<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
<br />
LABEL archfallback<br />
MENU LABEL Arch Linux Fallback<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26-fallback.img<br />
<br />
=== Chainloading ===<br />
<br />
If you want to chainload other operating systems (such as Windows) or boot loaders, copy (or symlink) the ''chain.c32'' module to the syslinux folder (for details, see the instructions in the previous section). Then, create a section in the configuration file:<br />
<br />
LABEL windows<br />
MENU LABEL Windows<br />
COM32 chain.c32<br />
APPEND hd0 3<br />
<br />
''hd0 3'' is the third partition on the first BIOS drive - drives are counted from zero, but partitions are counted from one. For more details about chainloading, see [http://syslinux.zytor.com/wiki/index.php/Comboot/chain.c32].<br />
<br />
=== Using memtest ===<br />
<br />
Use this LABEL section to launch memtest (install the ''memtest86'' package):<br />
<br />
LABEL memtest<br />
MENU LABEL Memtest86+<br />
LINUX /memtest86+/memtest.bin<br />
<br />
=== HDT ===<br />
<br />
HDT (Hardware Detection Tool) displays hardware information. Like before, the .c32 file has to be copied or symlinked from /boot/syslinux/.<br />
<br />
LABEL hdt<br />
MENU LABEL Hardware Info<br />
COM32 hdt.c32<br />
<br />
=== Reboot and power off ===<br />
<br />
Use the following sections to reboot or power off your machine.<br />
<br />
LABEL reboot<br />
MENU LABEL Reboot<br />
COM32 reboot.c32<br />
<br />
LABEL poweroff<br />
MENU LABEL Power Off<br />
COMBOOT poweroff.com<br />
<br />
==Troubeshooting==<br />
===I have a Syslinux Prompt - Yikes!===<br />
You can type in the LABEL name of the entry that you want to boot (as per your syslinux.cfg). If you used the example configs just type<br />
boot: arch<br />
<br />
If you get an error that the config file could not be loaded you can pass your needed boot parameters<br />
boot: vmlinuz26 root=/dev/sda2 ro initrd=/kernel26.img<br />
<br />
===Windows boots up! No Syslinux!===<br />
'''Solution:''' Make sure the partition that contains /boot has the boot flag enabled. Also, make sure the boot flag is not enabled on the windows partition. See the installation section above.<br />
<br />
The MBR that comes with syslinux looks for the first active partition that has the boot flag set. The windows partition was likely found first and had the boot flag set. If you wanted you could use the MBR that windows or msdos fdisk provides.<br />
<br />
===Menu Entries do nothing===<br />
You select a menu entry and it does nothing. It "refreshes" the menu<br/><br />
This usually means that you have an error in your configuration. Hit {{Keypress| TAB }} to edit your boot parameters. Alternatively, press {{Keypress| ESC}} and type in the LABEL of your boot entry (Example: arch)<br />
<br />
<br />
===Can't remove ldlinux.sys===<br />
ldlinux.sys has the immutable attribute set which prevents the file from being deleted or overwritten. This is because the sector location of the file must not change or else syslinux has to be reinstalled.<br />
To remove: <br />
chattr -i /boot/syslinux/ldlinux.sys<br />
rm /boot/syslinux/ldlinux.sys</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Netcfg&diff=127561
Netcfg
2011-01-10T11:16:49Z
<p>Cantabile: /* Tips and tricks */ using dhclient</p>
<hr />
<div>[[Category:Networking (English)]]<br />
{{i18n|Netcfg}}<br />
{{Article summary start}}<br />
{{Article summary text|A guide to installing and configuring netcfg &ndash; network configuration and profile scripts.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Network}}<br />
{{Article summary wiki|Wireless Setup}}<br />
{{Article summary heading|Resources}}<br />
{{Article summary link|netcfg network scripts repository|http://projects.archlinux.org/netcfg.git/}}<br />
{{Article summary end}}<br />
<br />
From the [http://projects.archlinux.org/netcfg.git/tree/man/netcfg.8 netcfg man page]:<br />
<br />
:'''''netcfg''' is used to configure and manage network connections via profiles. It has pluggable support for a range of connection types, such as wireless, ethernet, ppp. It is also capable of starting/stopping many to one connections, that is, multiple connections within the same profile, optionally with bonding.''<br />
<br />
netcfg is useful for users seeking a simple and robust means of managing multiple network configurations (e.g. laptop users). For systems connecting to a single network, the [[network]] daemon may be more appropriate.<br />
<br />
==Preparation==<br />
In the simplest cases, users must at least know the name of their network interface(s) (e.g. '''eth0''', '''wlan0'''). If configuring a static IP address, gateway and name server addresses must also be known.<br />
<br />
If connecting to a wireless network, have some basic information ready. For a wireless network this includes what type of security is used, the network name (ESSID), and any password or encryption keys. Additionally, ensure the proper drivers and firmware are installed for the wireless device, as described in [[Wireless Setup]].<br />
<br />
==Installation==<br />
Ensure you have the latest version of netcfg installed. Older versions have more bugs and may not work well with the latest drivers. The {{Package Official|netcfg}} package is available in '''core''':<br />
<br />
# pacman -S netcfg<br />
<br />
As of version 2.5.x, optional dependencies include {{Package Official|wpa_actiond}} &ndash; required for automatic/roaming wireless connection &ndash; and {{Package Official|ifplugd}} &ndash; required for automatic ethernet configuration. ([http://www.archlinux.org/news/487/ More information].)<br />
<br />
# pacman -S wpa_actiond ifplugd<br />
<br />
==Configuration==<br />
Network profiles are stored in the {{Filename|/etc/network.d}} directory. To minimize the potential for errors, copy an example configuration from {{Filename|/etc/network.d/examples}} to {{Filename|/etc/network.d/mynetwork}}. The file name is the name of the network profile ("mynetwork" is used as an example throughout this article). The name is not a network setting and does not need to match the wireless network name (SSID).<br />
<br />
Depending on the connection type and security, use one of the following examples from {{Filename|/etc/network.d/examples}} as a base. Be wary of examples found on the Internet as they often contain deprecated options that may cause problems.<br />
<br />
{| border="1"<br />
! Connection type/security !! Example profile<br />
|-<br />
| Wireless; WEP hex key || {{Filename|wireless-wep}}<br />
|-<br />
| Wireless; WEP string key || {{Filename|wireless-wep-string-key}}<br />
|-<br />
| Wireless; WPA personal (passphrase) || {{Filename|wireless-wpa}}<br />
|-<br />
| Wireless; WPA enterprise || {{Filename|wireless-wpa-config}} (wpa_supplicant configuration is external) <br /> {{Filename|wireless-wpa-configsection}} (wpa_supplicant configuration stored as string)<br />
|-<br />
| Wired; DHCP || {{Filename|ethernet-dhcp}}<br />
|-<br />
| Wired; static IP || {{Filename|ethernet-static}}<br />
|-<br />
| Wired; iproute configuration || {{Filename|ethernet-iproute}}<br />
|}<br />
<br />
Next, modify the new configuration file, {{Filename|/etc/network.d/mynetwork}}:<br />
<br />
* Set {{Codeline|INTERFACE}} to the correct wireless or ethernet interface. This can be checked with {{Codeline|ifconfig}} and {{Codeline|iwconfig}}.<br />
* Ensure the {{Codeline|ESSID}} and {{Codeline|KEY}} (passphrase) are set correctly for wireless connections. Typos in these fields are common errors.<br />
** Note that WEP ''string'' keys (not ''hex'' keys) must be specified with a leading {{Codeline|s:}} (e.g. {{Codeline|<nowiki>KEY="s:somepasskey"</nowiki>}}).<br />
<br />
{{Note | Netcfg configurations are valid Bash scripts. Any configuration involving special characters such as $ or \ needs to be quoted correctly otherwise it will be interpreted by Bash. To avoid interpretation, use single quotes or backslash escape characters where appropriate. }}<br />
<br />
{{Note | Network information (e.g. wireless passkey) will be stored in plain text format, so users may want to change the permissions on the newly created profile (e.g. {{Codeline|chmod 0600 /etc/network.d/mynetwork}} to make it readable by root only).}}<br />
<br />
==Usage==<br />
To connect a profile:<br />
# netcfg mynetwork<br />
<br />
To disconnect a profile:<br />
# netcfg down <profile-name><br />
<br />
If successful, users can configure netcfg to connect automatically or during boot. If the connection fails, see [[#Troubleshooting]] for solutions and how to get help.<br />
<br />
For other functions, see:<br />
$ netcfg help<br />
<br />
==Connecting automatically==<br />
Several methods are available to users wanting to automatically connect network profiles (e.g. during boot or whilst roaming). Note that a network profile must be properly configured within the {{Filename|/etc/network.d}} directory ''first'' (see [[#Configuration]]).<br />
<br />
{{Tip|If enabling one of the following daemons and nothing is configured within the {{Codeline|INTERFACES}} array in {{Filename|rc.conf}}, you may remove the {{Codeline|network}} daemon from the {{Codeline|DAEMONS}} array. If you mount NFS shares during boot, ensure the {{Codeline|netfs}} daemon remains listed, though (otherwise the network will be dropped before unmounting shares during shutdown).}}<br />
<br />
===net-profiles===<br />
'''{{Codeline|net-profiles}} allows users to connect profiles during boot.'''<br />
<br />
To enable this feature, users must add {{Codeline|net-profiles}} to the {{Codeline|DAEMONS}} array in [[rc.conf]] and specify profiles to try in the {{Codeline|NETWORKS}} array:<br />
<br />
{{File<br />
|name=/etc/rc.conf<br />
|content=<nowiki><br />
NETWORKS=(mynetwork yournetwork)<br />
<br />
...<br />
<br />
DAEMONS=(... net-profiles ...)<br />
</nowiki>}}<br />
<br />
Alternatively, {{Codeline|net-profiles}} can be configured to display a menu &ndash; allowing users to choose a desired profile &ndash; by setting the contents of the {{Codeline|NETWORKS}} array to {{Codeline|menu}}:<br />
<br />
{{File<br />
|name=/etc/rc.conf<br />
|content=<nowiki><br />
NETWORKS=(menu)<br />
<br />
...<br />
<br />
DAEMONS=(... net-profiles ...)<br />
</nowiki>}}<br />
<br />
Additionally, the {{Package Official|dialog}} package is required.<br />
<br />
{{Tip|Access the menu at any time by running {{Codeline|netcfg-menu}} in a terminal.}}<br />
<br />
===net-auto-wireless===<br />
'''{{Codeline|net-auto-wireless}} allows users to automatically connect to wireless networks with proper roaming support.'''<br />
<br />
To enable this feature, users must add {{Codeline|net-auto-wireless}} to the {{Codeline|DAEMONS}} array in [[rc.conf]] and specify the desired wireless interface with the {{Codeline|WIRELESS_INTERFACE}} variable:<br />
<br />
{{File<br />
|name=/etc/rc.conf<br />
|content=<nowiki><br />
WIRELESS_INTERFACE="wlan0"<br />
<br />
...<br />
<br />
DAEMONS=(... net-auto-wireless ...)<br />
</nowiki>}}<br />
<br />
Additionally, the {{Package Official|wpa_actiond}} package is required. Note that wpa-config profiles does not work with net-auto-wireless. Convert them to wpa-configsection instead.<br />
<br />
===net-auto-wired===<br />
'''{{Codeline|net-auto-wired}} allows users to automatically connect to wired networks.'''<br />
<br />
To enable this feature, users must install ifplugd <br />
<br />
# pacman -S ifplugd<br />
<br />
and add {{Codeline|net-auto-wired}} to the {{Codeline|DAEMONS}} array in [[rc.conf]] and specify the desired wired interface with the {{Codeline|WIRED_INTERFACE}} variable:<br />
<br />
{{File<br />
|name=/etc/rc.conf<br />
|content=<nowiki><br />
WIRED_INTERFACE="eth0"<br />
<br />
...<br />
<br />
DAEMONS=(... net-auto-wired ...)<br />
</nowiki>}}<br />
<br />
The daemon starts an ifplugd process which runs {{Filename|/etc/ifplugd/netcfg.action}} when the status of the wired interface changes (e.g. a cable is plugged in or unplugged). On plugging in a cable, attempts are made to start any profiles with CONNECTION = "ethernet" or "ethernet-iproute" and INTERFACE = WIRED_INTERFACE until one of them succeeds.<br />
<br />
Note: DHCP profiles are tried before static ones, which could lead to undesired results in some cases.<br />
<br />
Note2: The net-auto-wired daemon cannot start multiple ifplugd processes for multiple interfaces (unlike ifplugd's own /etc/rc.d/ifplugd which can).<br />
<br />
==Tips and tricks==<br />
<br />
===Passing arguments to iwconfig before connecting===<br />
Simply add the following to a profile:<br />
<br />
IWCONFIG="<arguments>"<br />
<br />
Where {{Codeline|<arguments>}} can be any valid {{Codeline|iwconfig}} argument. The script then runs {{Codeline|iwconfig $INTERFACE $IWCONFIG}}.<br />
<br />
For example, force the card to register to a specific access point given by MAC address:<br />
IWCONFIG="ap 12:34:56:78:90:12"<br />
<br />
This supersedes the {{Codeline|IWOPTS}} and {{Codeline|WEP_OPTS}} options which were incompletely implemented.<br />
<br />
===rfkill (enable/disable radio power)===<br />
netcfg can enable/disable radio for wireless cards equipped with software control of radio. For wireless cards with hardware switches, netcfg can detect disabled hardware switches and fail accordingly.<br />
<br />
To enable rfkill support, you need to specify what sort of switch the wireless interface has; hardware or software. This can be set within a profile or at the interface level ({{Filename|/etc/network.d/interfaces/$INTERFACE}}; see [[#Per-interface configuration]]). <br />
<br />
RFKILL=soft # can be either 'hard' or 'soft'<br />
<br />
For some kill switches the rfkill entry in {{Filename|/sys}} is not linked to the interface and the {{Codeline|RFKILL_NAME}} variable needs to be set to the contents of the matching {{Filename|/sys/class/rfkill/rfkill#/name}}.<br />
<br />
For example, on an Eee PC:<br />
<br />
RFKILL=soft<br />
RFKILL_NAME='eeepc-wlan'<br />
<br />
===Execute commands before/after interface up/down===<br />
If your interface requires special actions prior/after the establishment/closure of a connection, you may use the {{Codeline|PRE_UP}}, {{Codeline|POST_UP}}, {{Codeline|PRE_DOWN}}, and {{Codeline|POST_DOWN}} variables.<br />
<br />
For example, if you want to configure your wireless card to operate in ad-hoc mode but you can only change modes when the interface is down, you could use something like this:<br />
<br />
PRE_UP="ifconfig wlan0 down; iwconfig wlan0 mode ad-hoc"<br />
<br />
Or if you want to mount your network shares after a successful connection, you could use:<br />
<br />
POST_UP="sleep 5; mount /mnt/shares/nexus/utorrent 2>/dev/null"<br />
<br />
Sometimes you may want to run something from netcfg with another user:<br />
<br />
POST_UP="su -c '/you/own/command' username"<br />
<br />
{{Note|If the commands specified in these properties return anything other than 0 (success), netcfg aborts the current operation. So if you want to mount a certain network share that might not be available at the time of connection (thus returning an error), you could create a separate Bash script with the mount commands and a {{Codeline|exit 0}} at the end. Alternatively you can add {{Codeline|<nowiki>|| true</nowiki>}} to the end of the command that may fail.}}<br />
<br />
===Intermittent Connection Failure===<br />
Some driver+hardware combinations drop associations sometimes. Use the pre and post<br />
commands to add/remove the driver and use a script like the following <br />
to fix the current connection:<br />
<br />
{{File<br />
|name=/usr/local/bin/netcfgd<br />
|content=<nowiki><br />
#!/bin/bash<br />
log() { logger -t "$( basename $0 )" "$*" ; }<br />
<br />
main() {<br />
local host<br />
while sleep 1; do<br />
[[ "$( netcfg current )" = "" ]] && continue<br />
<br />
host=$( route -n | awk '/^0.0.0.0/ { print $2 }' )<br />
ping -c 1 $host && continue<br />
<br />
log "trying to reassociate"<br />
wpa_cli reassociate<br />
ping -c 1 $host && continue<br />
<br />
log "reassociate failed, reconfiguring network"<br />
netcfg -r $( netcfg current )<br />
done<br />
}<br />
<br />
exec 1>/dev/null<br />
[[ $EUID != 0 ]] && { log "must be root"; exit 1; }<br />
<br />
for cmd in wpa_cli ping netcfg; do<br />
! which $cmd && {<br />
log "can't find command ${cmd}, exiting..."<br />
exit 1<br />
}<br />
done<br />
<br />
log 'starting...'<br />
main <br />
<br />
</nowiki>}}<br />
<br />
===Per-interface configuration===<br />
Configuration options that apply to all profiles using an interface can be set using {{Filename|/etc/network.d/interfaces/$INTERFACE}}. For example:<br />
<br />
/etc/network.d/interfaces/wlan0<br />
<br />
This is useful for {{Codeline|wpa_supplicant}} options, rfkill switch support, pre/post up/down scripts and {{Codeline|net-auto-wireless}}. These options are loaded ''before'' profiles so that any profile-based options will take priority.<br />
<br />
{{Filename|/etc/network.d/interfaces/$INTERFACE}} may contain any valid profile option, though you are likely to use {{Codeline|PRE_UP}}/{{Codeline|DOWN}} and {{Codeline|POST_UP}}/{{Codeline|DOWN}} (described in the previous section) or one of the options listed below. Remember that these options are set for ''all'' profiles using the interface; you probably do not want to connect to your work VPN here, for instance, as it will try to connect on ''every'' wireless network!<br />
<br />
WPA_GROUP - Setting the group of the wpa_ctrl interface<br />
WPA_COUNTRY - Enforces local regulatory limitations and allows use of more channels<br />
WPA_DRIVER - Defaults to wext, may want nl80211 for mac80211 devices<br />
<br />
{{Note|{{Codeline|POST_UP}}/{{Codeline|POST_DOWN}} require the {{Package Official|wpa_actiond}} package.}}<br />
<br />
===Output hooks===<br />
netcfg has limited support to load hooks that handle output. By default it loads the {{Filename|arch}} hook which provides the familiar output that you see. A syslog logging hook is also included. These can be found at {{Filename|/usr/lib/network/hooks}}.<br />
<br />
===ArchAssistant (GUI)===<br />
<br />
A Qt-based netcfg front-end called ArchAssistant exists. It proposes to manage and connect/disconnect profiles from a systray icon. Automatic wireless detection is also available. This tool is particularly useful for laptop users.<br />
<br />
Links:<br />
<br />
* [http://aur.archlinux.org/packages.php?ID=15655 archassistant in the AUR] <br />
* [http://www.kde-apps.org/content/show.php/ArchAssistant?content=76760 archassistant on kde-apps.org] <br />
* archassistant package on archlinux.fr: [http://repo.archlinux.fr/i686/archassistant/ i686] and [http://repo.archlinux.fr/x86_64/archassistant/ x86_64]<br />
<br />
There is also a relatively new GUI for netcfg2 on qt-apps.org that does only network configuration. You can find it [http://www.qt-apps.org/content/show.php/netcfgGUI?content=99523 here].<br />
<br />
===wifi-select===<br />
<br />
There is a console tool for selecting wireless networks in "real-time" (in NetworkManager manner) called <tt>wifi-select</tt>. The tool is convenient for use in Internet cafés or other places you are visiting for the first (and maybe the last) time. With this tool, you do not need to create a profile for a new network, just type {{Codeline|sudo wifi-select wlan0}} and choose the network you need. <br />
<br />
The tool is currently packaged and available in [community] repository. To install:<br />
<br />
# pacman -S wifi-select<br />
<br />
<tt>wifi-select</tt> does the following:<br />
* parses <tt>iwlist scan</tt> results and presents list of networks along with its security settings (WPA/WEP/none) using <tt>dialog</tt><br />
* if user selects network with existing profile -- just use this profile to connect with <tt>netcfg</tt><br />
* if user selects a new network (for example, WiFi hotspot), <tt>wifi-select</tt> automatically generates new profile with corresponding <tt>$SECURITY</tt> and asks for the key (if needed). It uses DHCP as <tt>$IP</tt> by default<br />
* then, if connection succeeds, profile is saved for later usage<br />
* if connection fails, user is asked if he/she wants to keep generated profile for further usage (for example to change <tt>$IP</tt> to static or adjust some additional options)<br />
<br />
Links: <br />
<br />
* [http://bbs.archlinux.org/viewtopic.php?id=63973 Forum thread] related to development of <tt>wifi-select</tt><br />
* [http://aur.archlinux.org/packages.php?ID=23471 wifi-select in the AUR] <br />
* [http://hg.horna.org.ua/wifi-select/ wifi-select Mercurial repository]<br />
<br />
===Using dhclient instead of dhcpcd===<br />
<br />
Simply add<br />
DHCLIENT=yes<br />
in the desired profile.<br />
<br />
==Troubleshooting==<br />
<br />
===Debugging===<br />
To run netcfg with debugging output, set the {{Codeline|NETCFG_DEBUG}} environment variable to {{Codeline|"yes"}}, for example:<br />
<br />
# NETCFG_DEBUG="yes" netcfg <arguments><br />
<br />
Debugging information for wpa_supplicant can be logged using {{Codeline|WPA_OPTS}} within a profile, for example:<br />
<br />
WPA_OPTS="-f/path/to/log"<br />
<br />
Whatever is entered here will be added to the command when wpa_supplicant is called.<br />
<br />
===Network unavailable===<br />
This error is typically due to:<br />
* Out of range; or<br />
* Driver issue.<br />
<br />
===Wireless association failed===<br />
This error is typically due to:<br />
* Out of range/reception;<br />
* Incorrect configuration;<br />
* Invalid key;<br />
* Driver problem; or<br />
* Trying to connect to a hidden network.<br />
<br />
If the connection problem is due to poor reception, increase the {{Codeline|TIMEOUT}} variable in {{Filename|/etc/network.d/mynetwork}}, such as:<br />
TIMEOUT=60<br />
<br />
If an AP with a hidden SSID is used, try:<br />
PRE_UP='iwconfig $INTERFACE essid $ESSID'<br />
<br />
===Unable to get IP address with DHCP===<br />
This error is typically due to:<br />
* Out of range/reception<br />
<br />
Try increasing {{Codeline|DHCP_TIMEOUT}} variable in your network {{Filename|/etc/network.d/profile}}.<br />
<br />
===Not a valid connection, check spelling or look at examples===<br />
You must set {{Codeline|CONNECTION}} to one of the connection types listed in the {{Filename|/usr/lib/network/connections}} directory. Alternatively, use one of the provided configuration examples in {{Filename|/etc/network.d/examples}}.<br />
<br />
===Driver quirks===<br />
{{Note|You most likely do '''not''' need quirks; ensure your configuration is correct before considering them. Quirks are intended for a small range of drivers with unusual issues, many of them older versions. These are workarounds, not solutions.}}<br />
<br />
Some drivers behave oddly and need workarounds to connect. Quirks must be enabled manually. They are best determined by reading the forums, seeing what others have used, and, if that fails, trial and error. Quirks can be combined.<br />
<br />
; {{Codeline|prescan}}: Run {{Codeline|iwlist $INTERFACE scan}} before attempting to connect (broadcom)<br />
; {{Codeline|preessid}}: Run {{Codeline|iwconfig $INTERFACE essid $ESSID}} before attempting to connect (ipw3945, broadcom and Intel PRO/Wireless 4965AGN)<br />
; {{Codeline|wpaessid}}: Same as previous, run before starting {{Codeline|wpa_supplicant}}. Not supported anymore - use <pre>IWCONFIG="essid $ESSID"</pre> instead. (ath9k)<br />
; {{Codeline|predown}}: Take interface down before association and then restore it after (madwifi)<br />
; {{Codeline|postsleep}}: Sleep one second before checking if the association was successful<br />
; {{Codeline|postscan}}: Run {{Codeline|iwlist scan}} after associating <br />
<br />
Add the required quirks to the netcfg configuration file {{Filename|/etc/network.d/mynetwork}}, for example:<br />
QUIRKS=(prescan preessid)<br />
<br />
If you receive "Wireless network not found", "Association failed" errors and have tried the above, or if an AP with a hidden SSID is used, see the above section [[#Wireless association failed]].<br />
<br />
===Ralink legacy drivers rt2500, rt2400 that use iwpriv===<br />
There is no plans to add WPA support to these drivers. rt2x00 is supported, however, and will replace these.<br />
<br />
If you must use them, create a shell script that runs the needed {{Codeline|iwpriv}} commands and put its path in {{Codeline|PRE_UP}}.<br />
<br />
===find: "/var/run/network//suspend/": No such file or directory===<br />
If you get this error message then don't bother because it is a known bug. Create the directory by hand.<br />
<br />
===It still doesn't work, what do I do?===<br />
If this article did not help solve your problem, the next best place to ask for help is the forums or the mailing list. <br />
<br />
To be able to determine the problem, we need information. When you ask, provide the following output:<br />
* '''ALL OUTPUT FROM netcfg''' <br />
* '''ALL OUTPUT FROM netcfg''' <br />
* '''ALL OUTPUT FROM netcfg'''<br />
** This is absolutely crucial to be able determine what went wrong. The message might be short or non-existent, but it can mean a great deal. <br />
* '''{{Filename|/etc/network.d}} network profiles'''<br />
** This is also crucial as many problems are simple configuration issues. Feel free to censor your wireless key.<br />
* '''netcfg version'''<br />
* {{Codeline|lsmod}}<br />
* {{Codeline|iwconfig}}<br />
<br />
==FAQ==<br />
{{FAQ<br />
|question=Why doesn't netcfg do ''(some feature)''?<br />
|answer=netcfg doesn't need to; it connects to networks. netcfg is modular and re-usable; see {{Filename|/usr/lib/networks}} for reusable functions for custom scripts.}}<br />
<br />
{{FAQ<br />
|question=Why doesn't netcfg behave in ''this'' way?<br />
|answer=netcfg doesn't enforce any rules; it connects to networks. It doesn't impose any heuristics, like "disconnect from wireless if ethernet is connected". If you want behaviour like that, it should be simple to write a separate tool over netcfg. See the question above.}}<br />
<br />
{{FAQ<br />
|question=Do I still need ''(some thing)'' if I'm using netcfg?<br />
|answer=This question usually references {{Filename|/etc/hosts}} and the {{Codeline|HOSTNAME}} variable in {{Filename|/etc/rc.conf}}, which are both still required. You may remove {{Codeline|network}} from the {{Codeline|DAEMONS}} array if you've configured all your networks with netcfg, though.}}</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Arch_User_Repository&diff=125809
Arch User Repository
2010-12-23T10:44:56Z
<p>Cantabile: /* Installing packages */ acquire the tarball, not the pkgbuild</p>
<hr />
<div>[[Category:AUR (English)]]<br />
[[Category:About Arch (English)]]<br />
[[Category:Package development (English)]]<br />
[[Category:Package management (English)]]<br />
[[Category:Arch development (English)]]<br />
{{i18n|Arch User Repository}}<br />
<br />
{{Article summary start}}<br />
{{Article summary text|The Arch User Repository is a collection of user-submitted PKGBUILDs that supplement software available from the official repositories. This article describes how to build ''unsupported'' software packages from the AUR.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Package management overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|AUR Helpers}}<br />
{{Article summary wiki|AUR Trusted User Guidelines}}<br />
{{Article summary heading|Resources}}<br />
{{Article summary link|AUR Web Interface|http://aur.archlinux.org}}<br />
{{Article summary link|AUR Mailing List|http://www.archlinux.org/mailman/listinfo/aur-general}}<br />
{{Article summary end}}<br />
<br />
The [[Arch User Repository]] (AUR) is a community-driven repository for Arch users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]]. The AUR was created to organize and share new packages from the community and to help expedite popular packages' inclusion into the [[#.5Bcommunity.5D|[community]]] repository. This document explains how users can access and utilize the AUR.<br />
<br />
A good number of new packages that enter the official repositories start in the AUR. In the AUR, users are able to contribute their own package builds (PKGBUILD and related files). The AUR community has the ability to vote for or against packages in the AUR. If a package becomes popular enough -- provided it has a compatible license and good packaging technique -- it may be entered into the [community] repository (directly accessible by <tt>pacman</tt> or <tt>abs</tt>).<br />
<br />
==Getting started==<br />
<br />
Users can search and download [[PKGBUILD]]s from the [http://aur.archlinux.org AUR Web Interface]. These PKGBUILDs can be built into installable packages using [[makepkg]], then installed using [[pacman]]. <br />
<br />
* Read the remainder of this article for more info and a short tutorial on installing AUR packages.<br />
* Visit the [http://aur.archlinux.org AUR Web Interface] to inform yourself on updates and happenings. There you will also find statistics and an up-to-date list of newest available packages available in AUR.<br />
* Glance over the [[#FAQ]] for answers to the most common questions.<br />
* You may wish to adjust {{Filename|/etc/makepkg.conf}} to better optimize for your processor prior to building packages from the AUR. A significant improvement in compile times can be realized on systems with multi-core processors by adjusting the MAKEFLAGS variable. Users can also enable hardware-specific optimizations in GCC via the CFLAGS variable. See [[makepkg.conf]] for more information.<br />
* Install "base-devel" ({{Codeline|pacman -S base-devel}}), because members of this group are not explicitly required by AUR packages which may not build without them (more info in [http://bbs.archlinux.org/viewtopic.php?pid=632355 this thread]).<br />
<br />
==History==<br />
The following items are listed for historical purposes only. They have since been superseded by the AUR and are no longer available.<br />
<br />
At the beginning, there was <tt><nowiki>ftp://ftp.archlinux.org/incoming</nowiki></tt>, and people contributed by simply uploading the [[PKGBUILD]], the needed supplementary files, and the built package itself to the server. The package and associated files remained there until a [[Package Maintainer]] saw the program and adopted it.<br />
<br />
Then the Trusted User Repositories were born. Certain individuals in the community were allowed to host their own repositories for anyone to use. The AUR expanded on this basis, with the aim of making it both more flexible and more usable. In fact, the AUR maintainers are still referred to as TUs (Trusted Users).<br />
<br />
==Searching==<br />
The AUR web interface can be found [http://aur.archlinux.org/ here], and an interface suitable for accessing the AUR from a script (for example) can be found [http://aur.archlinux.org/rpc.php here]<br />
<br />
Queries search package names and descriptions via a MySQL LIKE comparison. This allows for more flexible search criteria (e.g. try searching for 'tool%like%grep' instead of 'tool like grep'). If you need to search for a description that contains '%', escape it with '\%'.<br />
<br />
==Installing packages==<br />
Installing packages from the AUR (aka the [unsupported] repository) is a relatively simple process. Essentially:<br />
# Acquire the tarball which contains the [[PKGBUILD]] and possibly other required files<br />
# Extract the tarball (preferably in a folder set aside just for builds from the AUR)<br />
# Run [[makepkg]] in the directory where the files are saved ("makepkg -s" will auto-resolve dependencies with [[pacman]])<br />
# Install the resulting package with [[pacman]]<br />
<br />
# pacman -U /path/to/pkg.tar.xz<br />
<br />
[[AUR Helpers]] add seamless access to the AUR. They vary in their features, but can ease in searching, fetching, building, and installing from PKGBUILDs found in AUR. All of these scripts can be found in UNSUPPORTED. <br />
<br />
{{Note|There is not and will never be an ''official'' mechanism for installing build material from UNSUPPORTED. All users should be familiar with the build process.}}<br />
<br />
What follows is a detailed example of installation of a package called "foo".<br />
<br />
===Prerequisites===<br />
First ensure that the necessary tools are installed. The package group "base-devel" should be sufficient; it includes ''make'' and other tools needed for compiling from source.<br />
<br />
{{Warning|Packages in the AUR assume "base-devel" is installed, and will not list members of this group as dependencies even if the package cannot be built without them. Please ensure this group is installed before complaining about failed builds.}}<br />
<br />
# pacman -S base-devel<br />
<br />
Next choose an appropriate build directory. A build directory is simply a directory where the package will be made or "built" and can be any directory. Examples of commonly used directories are:<br />
<br />
~/builds<br />
<br />
or if using ABS (the [[Arch Build System]]):<br />
<br />
/var/abs/local<br />
<br />
For more information on ABS read the [[Arch Build System]] article. The example will use {{Filename|~/builds}} as the build directory.<br />
<br />
===Acquire build files===<br />
Locate the package in the AUR. This is done using the search feature (text field at the top of the [http://aur.archlinux.org/ AUR home page]). Clicking the application's name in the search list brings up an information page on the package. Read through the description to confirm that this is the desired package, note when the package was last updated, and read any comments.<br />
<br />
Download the necessary build files. From the package's information page download the build files by clicking the "Tarball" link on the left-hand side near the end of the package details. This file should be saved to the build directory or otherwise copied to the directory after downloading. In this example, the file is called "foo.tar.gz" (standard format is <pkgname>.tar.gz, if it has been properly submitted).<br />
<br />
===Build the package===<br />
Extract the tarball. Change directories to the build directory if not already there and extract the build files.<br />
<br />
$ cd ~/builds<br />
$ tar -xvzf foo.tar.gz<br />
<br />
This should create a new directory called "foo" in the build directory.<br />
<br />
{{Warning|'''Carefully check all files.''' Change directories to the newly created directory and carefully check the {{Filename|PKGBUILD}} and any {{Filename|.install}} file for malicious commands. If in doubt, do NOT build the package and seek advice on the forums or mailing list.}}<br />
<br />
$ cd foo<br />
$ nano PKGBUILD<br />
$ nano foo.install<br />
<br />
Make the package. After manually confirming the integrity of the files, run [[makepkg]] as a normal user in the build directory.<br />
<br />
$ makepkg -s<br />
<br />
The {{Codeline|-s}} switch will use [[sudo]] to install any needed dependencies. If the use of sudo is undesirable, manually install required dependencies beforehand and exclude the {{Codeline|-s}} in the above command.<br />
<br />
===Install the package===<br />
Install the package using [[pacman]]. A tarball should have been created named:<br />
<br />
<application name>-<version number>-<architecture>.pkg.tar.xz<br />
<br />
This package can be installed using [[pacman]]'s "upgrade" command:<br />
<br />
# pacman -U foo-0.1-i686.pkg.tar.xz <br />
<br />
{{Note|The above example is only a brief summary of the package building process. A visit to the [[makepkg]] and [[ABS]] pages will provide more detail and is highly recommended (particularly for first-time users).}}<br />
<br />
==Sharing packages==<br />
The user plays an essential role in the AUR, which cannot fulfill its potential without the support, involvement, and contribution of the wider user community. The life-cycle of an AUR package starts and ends with the user and requires the user to contribute in several ways.<br />
<br />
Users can '''share''' [[PKGBUILD]]s using the UNSUPPORTED area in the AUR. UNSUPPORTED does not contain any binary packages but allows users to upload PKGBUILDs that can be downloaded by others. These PKGBUILDs are completely unofficial and have not been thoroughly vetted, so they should be used at your own risk.<br />
<br />
===Feedback===<br />
A comments facility allows users to provide suggestions and feedback on improvements to the PKGBUILD contributor. Avoid pasting patches or PKGBUILDs into the comments section. They quickly become obsolete and just end up needlessly taking up lots of space. Instead email those files to the maintainer, or even use a [[pastebin Clients|pastebin]] like http://aur.pastebin.com.<br />
<br />
One of the easiest activities for '''all''' Arch users is to browse the AUR and '''vote''' for their favorite packages using the online interface. All packages are eligible for adoption by a TU for inclusion in [community], and the vote count is one of the considerations in that process; it is in everyone's interest to vote!<br />
<br />
===Submitting packages===<br />
After logging in to the AUR web interface, a user can [http://aur.archlinux.org/pkgsubmit.php submit] a gzipped tarball ({{Filename|.tar.gz}}) of a directory containing build files for a package. The directory inside the tarball should contain a {{Filename|PKGBUILD}}, any {{Filename|.install}} files, patches, etc. (ABSOLUTELY no binaries). Examples of what such a directory should look like can be seen inside {{Filename|/var/abs}} if [[ABS]] was installed.<br />
<br />
The tarball can be created with the following command:<br />
$ makepkg --source <br />
<br />
Note that this is a gzipped tarball; assuming you are uploading a package called ''libfoo'', when you create the file it should look similar to this:<br />
<br />
# List contents of tarball.<br />
$ tar tf libfoo-0.1-1.src.tar.gz<br />
libfoo/<br />
libfoo/PKGBUILD<br />
libfoo/libfoo.install<br />
<br />
When submitting a package, observe the following rules: <br />
* Check [core], [extra], and [community] for the package. If it is inside any of those repositories in ANY form, DO NOT submit the package (if the current package is broken or is lacking an included feature then please file a bug report in [http://bugs.archlinux.org/ FlySpray]).<br />
* Check AUR for the package. If it is currently maintained, changes can be submitted in a comment for the maintainer's attention. If it is unmaintained, the package can be adopted and updated as required.<br />
* Verify carefully that what you are uploading is correct. All contributors must read and adhere to the [[Arch Packaging Standards]] when writing PKGBUILDs. This is essential to the smooth running and general success of the AUR. Remember you are not going to earn any credit or respect from your peers by wasting their time with a bad PKGBUILD.<br />
* Packages that contain binaries or that are very poorly written may be deleted without warning.<br />
* If you are unsure about the package (or the build/submission process) in any way, submit the PKGBUILD to the AUR Mailing List or the AUR boards on the forum for public review before adding it to the AUR.<br />
* Make sure the package is useful. Will anyone else want to use this package? Is it extremely specialized? If more than a few people would find this package useful, it is appropriate for submission.<br />
* Gain some experience before submitting packages. Build a few packages to learn the process and then submit.<br />
* If you submit a {{Filename|package.tar.gz}} with a file named '{{Filename|package}}' in it you'll get a an error: 'Could not change to directory {{Filename|/home/aur/unsupported/package/package}}'. To resolve this, rename the file named '{{Filename|package}}' to something else, for example, '{{Filename|package.rc}}'. When it is installed in the {{Filename|pkg}} directory you may rename it back to '{{Filename|package}}'.<br />
<br />
===Maintaining packages===<br />
* If you maintain a package and want to update the PKGBUILD for your package just resubmit it.<br />
* Check for feedback and comments from other users and try to incorporate any improvements they suggest; consider it a learning process!<br />
* Please DO NOT just submit and forget about packages! While in UNSUPPORTED, it is the user's job to maintain the package by checking for updates and improving the PKGBUILD.<br />
* If you do not want to continue to maintain the package for some reason, <tt>disown</tt> the package using the AUR web interface and/or post a message to the AUR Mailing List.<br />
<br />
==[community]==<br />
The [community] repository, maintained by [[Trusted Users]], contains the most popular packages from AUR. It is enabled by default in {{Filename|pacman.conf}}. If disabled/removed, it can be enabled by uncommenting/adding these two lines: <br />
<br />
{{File<br />
|name=/etc/pacman.conf<br />
|content=<nowiki><br />
...<br />
[community]<br />
Include = /etc/pacman.d/mirrorlist<br />
...<br />
</nowiki>}}<br />
<br />
[community], unlike AUR, contains binary packages that can be installed directly with [[pacman]] and the build files can also be accessed with [[ABS]]. Some of these packages may eventually make the transition to the [core] or [extra] repositories as the developers consider them crucial to the distribution.<br />
<br />
Users can also access the [community] build files by editing {{Filename|/etc/abs.conf}} and enabling the community repository in the {{Codeline|REPOS}} array.<br />
<br />
==FAQ==<br />
<br />
{{FAQ<br />
|question=What is the AUR?<br />
|answer=The AUR (Arch User Repository) is a place where the Arch Linux community can upload [[PKGBUILD]]s of applications, libraries, etc., and share them with the entire community. Fellow users can then vote for their favorites to be moved into the [community] repository to be shared with Arch Linux users in binary form.}}<br />
<br />
{{FAQ<br />
|question=What is a TU?<br />
|answer=A [[AUR Trusted User Guidelines|TU (Trusted User)]] is a person who is chosen to oversee AUR and the [community] repository. They're the ones who maintain popular PKGBUILDs in [community], and overall keep the AUR running.}}<br />
<br />
{{FAQ<br />
|question=What's the difference between [unsupported] and [community]?<br />
|answer=[unsupported] is where all PKGBUILDs that users submit are stored, and must be built manually with [makepkg]. When PKGBUILDs receive enough votes, they are moved into the [community] repository, where the TUs maintain binary packages that can be installed with [[pacman]].}}<br />
<br />
{{FAQ<br />
|question=How many votes does it take to get a PKGBUILD into [community]?<br />
|answer=Usually, at least 10 votes are required for something to move into [community]. However, if a TU wants to support an package, it will often be found in the repository.}}<br />
<br />
{{FAQ<br />
|question=How do I make a PKGBUILD?<br />
|answer=The best resource is [[Creating Packages]]. Remember to look in AUR before creating the PKGBUILD as to not duplicate efforts.}}<br />
<br />
{{FAQ<br />
|question=I'm trying to do {{Codeline|pacman -S foo}}; it isn't working but I know it's in [community]<br />
|answer=You probably haven't enabled [community] in your {{Filename|/etc/pacman.conf}}. Just uncomment the relevant lines.<br />
If [community] is enabled in your {{Filename|/etc/pacman.conf}} try running {{Codeline|pacman -S -y}} first to synchronize the pkgcache before trying your package again.}}<br />
<br />
{{FAQ<br />
|question=Foo in AUR is outdated; what do I do?<br />
|answer=For starters, you can flag packages out-of-date. If it stays out-of-date for an extended amount of time, the best thing to do is email the maintainer. If there is no response from the maintainer, you could mail to the aur-general mailing list to have a TU orphan the PKGBUILD if you're willing to maintain it yourself.}}<br />
<br />
{{FAQ<br />
|question=I have a PKGBUILD I would like to submit; can someone check it to see if there are any errors?<br />
|answer=If you would like to have your PKGBUILD critiqued, post it on the aur-general mailing list to get feedback from the TUs and fellow AUR members. You could also get help from the [[ArchChannel|IRC channel]], #archlinux on irc.freenode.net. You can also<br />
use [[namcap]] to check your PKGBUILD and the resulting package for errors.}}<br />
<br />
{{FAQ<br />
|question=Foo in AUR doesn't compile when I do {{Codeline|makepkg}}; what should I do?<br />
|answer=You are probably missing something trivial.<br />
<br />
# Run {{Codeline|pacman -Syyu}} before compiling anything with {{Codeline|makepkg}} as the problem may be that your system is not up-to-date.<br />
# Ensure you have both "base" and "base-devel" groups installed.<br />
# Try using the "{{Codeline|-s}}" option with {{Codeline|makepkg}} to check and install all the dependencies needed before starting the build process.<br />
<br />
The reason might not be trivial after all. Custom CFLAGS, LDFLAGS and MAKEFLAGS can cause failures. It's also possible that the PKGBUILD is broken for everyone. If you can't figure it out on your own, just report it to the maintainer.}}<br />
<br />
{{FAQ<br />
|question=How can I speed up repeated build processes?<br />
|answer=If you frequently compile code that uses gcc - say, a git or SVN package - you may find [[ccache]], short for "compiler cache", useful.}}<br />
<br />
{{FAQ<br />
|question=How do I access unsupported packages?<br />
|answer=See [[#Installing Packages from the AUR]]}}<br />
<br />
{{FAQ<br />
|question=How can I upload to AUR without using the web interface?<br />
|answer=You can use [http://aur.archlinux.org/packages.php?ID=23393 aurploader] or [http://aur.archlinux.org/packages.php?ID=37216 burp] -- both with command-line interfaces.}}</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Beginners%27_guide_old&diff=125627
Beginners' guide old
2010-12-20T08:02:45Z
<p>Cantabile: /* OS System Start */ add another workaround for the blank screen issue</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]] [[Category:About Arch (English)]]<br />
[[Category:HOWTOs (English)]] [[Category:Website Resources]]<br />
{{i18n|Beginners' Guide}}<br />
[[de:Anleitung für Einsteiger]]<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|Related}}<br />
{{Article summary wiki|:Category:Accessibility (English)}}<br />
{{Article summary wiki|Official Arch Linux Install Guide}}<br />
{{Article summary wiki|General Recommendations}}<br />
{{Article summary end}}<br />
==Preface==<br />
=====Introduction=====<br />
Welcome. This document will guide you through the process of installing and configuring [[Arch Linux]]; a simple, lightweight GNU/Linux distribution targeted at competent users. 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 />
* [http://www.archlinux.org/packages/?q= All packages] compiled for i686 and x86_64 architectures<br />
* [[Arch Boot Process|BSD style]] init scripts, featuring one centralized configuration file<br />
* [[mkinitcpio]]: A simple and dynamic initramfs creator<br />
* [[Pacman]] package manager is lightweight and agile, with a very modest memory footprint<br />
* The [[Arch Build System]]: A ports-like package building system, providing a simple framework to create installable Arch packages from source<br />
* The [[Arch User Repository]]: offering many thousands of user contributed build scripts and the opportunity to share your own<br />
<br />
=====License=====<br />
<br />
Arch Linux, pacman, documentation, and scripts are copyright<br />
©2002-2007 by Judd Vinet, ©2007-2010 by Aaron Griffin and are licensed under the GNU General Public License Version 2.<br />
<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 as you consider simplicity:'''<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..The height of cultivation always runs to simplicity.&quot;'' - Bruce Lee<br />
<br />
=====About This Guide=====<br />
<br />
The Arch wiki is an excellent resource and should be consulted for issues [[Main Page|first]]. The IRC room (at freenode #archlinux), and the [http://bbs.archlinux.org/ forums] are also available if the answer cannot be found elsewhere.<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 <u>before</u> carrying out the tasks contained.}}<br />
<br />
The guide is divided into 5 main components:<br />
<br />
*[[#Part I: Install the Base System|Part I: Install the Base system]]<br />
*[[#Part II: Update|Part II: Update]]<br />
*[[#Part III: Add a user|Part III: Add a user]]<br />
*[[#Part IV: Sound|Part IV: Sound]]<br />
*[[#Part V: Graphical User Interface|Part V: Graphical User Interface]]<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 installation media from [http://archlinux.org/download/ here]. The latest version is 2010.05<br />
<br />
* Both the Core and the Netinstall images 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 utilities), the Linux kernel, and a few extra libraries and modules.''<br />
* Core images facilitate both installing from CD and Net.<br />
* Netinstall images are smaller and provide no packages themselves; the entire system is retrieved via internet.<br />
* [[Arch64_FAQ|The Arch64 FAQ]] can help you choose between the 32-, 64-bit and dual versions.<br />
* Don't forget to download the checksum txt files along with your chosen ISO.<br />
<br />
====Check the Integrity of the Downloaded File====<br />
Open a terminal, change to the directory where the downloaded files have been placed, and type at the CLI (Command Line Interface):<br />
$ sha1sum --check name_of_checksum_file.txt name_of_selected_iso_file.iso<br />
This should give you an "OK" for the one you have. (Simply ignore other lines.) If not, download all files again.<br />
The md5sum check works the same way.<br />
<br />
====Install from an Existing GNU/Linux Distro====<br />
Arch is flexible enough to be installed to another partition ''from within'' an existing distro or Live CD. See [[Install from Existing Linux|this wiki article]] for steps to do this. This can be useful particularly if you plan to install Arch via vnc or ssh remotely.<br />
<br />
====CD installer====<br />
Burn the .iso image file to a CD or DVD media with your preferred CD/DVD burner drive and software, and continue with [[#Step 2: Boot Arch Linux Installer | Step 2: Boot Arch Linux Installer]]<br />
{{Note| The quality of optical drives, as well as the CD media itself, vary greatly. 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 />
====Flash Memory Device or USB stick====<br />
<br />
See [[Install_from_a_USB_flash_drive|Install from a USB flash drive]] for more detailed instructions.<br />
<br />
This method will work for any type of flash media from which your BIOS will let you boot, be it a card reader or USB port.<br />
<br />
{{Warning|This procedure will irrevocably destroy all data on your media! Also, be very careful where you send the image iso, as dd will obediently write to any target you point to, even if that is your hard disk.}}<br />
<br />
'''*nix Method:'''<br />
<br />
Insert an empty or expendable flash device, determine its path, and write the .iso to the device with the <code>/bin/dd</code> program:<br />
# dd if=archlinux-2010.05-''{core|netinstall}''-''{i686|x86_64|dual}''.iso of=/dev/sd''x''<br />
where <code>if=</code> is the path to the img file and <code>of=</code> is your flash device. Make sure to use {{Filename|/dev/sd'''x'''}} and not {{Filename|/dev/sd'''x1'''}}. You will need a flash memory device large enough to accomodate the image.<br />
<br />
'''Check md5sum:'''<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 [ftp://ftp.archlinux.org/iso/2010.05/md5sums.txt 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. A typical run will look like this: <br />
{{Command|<nowiki>[sudo] dd if=archlinux-2010.05-core-i686.iso of=/dev/sdc</nowiki>|<nowiki> 744973+0 records in<br />
744973+0 records out<br />
381426176 bytes (381 MB) copied, 106.611 s, 3.6 MB/s<br />
</nowiki>}}<br />
<br />
{{Command|<nowiki>[sudo] dd if=/dev/sdc count=744973 status=noxfer | md5sum</nowiki>| 4850d533ddd343b80507543536258229 -<br />
744973+0 records in<br />
744973+0 records out}}<br />
<br />
Continue with [[#Step 2: Boot Arch Linux Installer | Step 2: Boot Arch Linux Installer]]<br />
<br />
'''Microsoft Windows Method:'''<br />
<br />
Download Disk Imager from https://launchpad.net/win32-image-writer/+download. Insert flash media. Start the Disk Imager and select the image file (Disk Imager accepts only *.IMG files, so you'll have to put "*.iso" in file open dialog to select Arch snapshot). Select the drive letter associated with the flash drive. Click "write".<br />
<br />
There are also other solutions to [[Install_from_a_USB_flash_drive#On_Windows|writing bootable ISO images to USB sticks]]. If you have problems with USB sticks disconnecting, try using different USB port and/or cable.<br />
<br />
Continue with [[#Step 2: Boot Arch Linux Installer | Step 2: Boot Arch Linux Installer]]<br />
<br />
===Step 2: Boot Arch Linux Installer===<br />
{{Tip|The memory requirement for a basic install is 64 MB of RAM.}}<br />
<br />
{{Tip|During the process, the automatic screen blanker may come on. If so, one can press the Alt key to safely obtain the normal display.}}<br />
<br />
====Boot from the Media====<br />
Insert the CD or Flash media you prepared, 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 (Power On Self-Test) phase.<br />
<br />
'''Main Menu:''' The main menu should be displayed at this point. Select the preferred choice by using the arrow keys to highlight your choice, and then by pressing Enter.<br />
<br />
Menus vary on different iso's. The 2010.05 Netinstall menu has "Boot Arch Linux (i686)", "Boot Arch Linux (x86-64)", "Boot Existing OS", "Run Memtest86+ (RAM test)", "Run x86test (CPU test)", and "Reboot"<br />
<br />
For Netinstall, choose the first or second item according to your CPU type. For Core, usually the first item, Boot Archlive, is the preferred selection. However, choose Boot Archlive [legacy IDE] if you have trouble with libata/PATA, or have no SATA (Serial ATA) drives.<br />
<br />
It is strongly recommended that you run the memory test; just to be sure. The CPU test can also provide detailed and useful specs. It may be wise to remember or record any system details of which you were unaware.<br />
<br />
====OS System Start====<br />
The system will now load and present a login prompt. Login as 'root', without the quotes.<br />
<br />
If using an Intel video chipset and the screen goes blank during the boot process, the problem is likely an issue with kernel mode setting. A possible workaround may be achieved by rebooting and pressing <Tab> at the GRUB menu to enter kernel options. At the end of the kernel line, add a space and then:<br />
i915.modeset=0<br />
Alternatively, add:<br />
video=SVIDEO-1:d<br />
which (if it works) will not disable kernel mode setting.<br />
<br />
When done making any changes to any menu command, simply press "Enter" to boot with that setup.<br />
<br />
See [[Intel| the Intel article]] for more information.<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 conveniently available right on the live system! To access it, change to tty2 (virtual console #2) with <ALT>+F2, log in as "root" and then invoke <code>/usr/bin/less</code> by typing in the following at the # prompt:<br />
# less /usr/share/aif/docs/official_installation_guide_en<br />
<code>less</code> will allow you to page through the document.<br />
<br />
Change back to tty1 with <ALT>+F1 to follow the rest of the install process. (Change back to tty2 at any time if you need to reference the Official Guide as you progress through the installation process.)<br />
<br />
{{tip|Please note that the official guide only covers installation and configuration of the base system. Once that is installed, it is strongly recommended that you come back here to the wiki to find out more about post-installation considerations and other related issues.}}<br />
<br />
===Step 3: Start the Installation===<br />
As root, run the installer script from tty1:<br />
# /arch/setup<br />
You should next see the displayed Arch Linux Installation Framework screen.<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. A good place to check for relative speed of source repositories is [https://www.archlinux.de/?page=MirrorStatus Mirror Status]. Choose one that matches one from the installer list.<br />
<br />
* If you chose the CORE installer, continue below with [[#B: Set Clock|B: Set Clock]].<br />
* Netinstall 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 tty3. (Select OK to continue.)<br />
<br />
====Configure Network (Netinstall)====<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 />
=====(A)DSL Quickstart for the Live Environment=====<br />
(If you have a modem or router in bridge mode to connect to your ISP)<br />
<br />
Switch to another virtual console (<Alt> + F2), login as root and invoke<br />
# pppoe-setup<br />
If everything is well configured in the end you can connect to your ISP with<br />
# pppoe-start<br />
<br />
Return to first virtual console with <ALT>+F1. Continue with [[#B: Set Clock|B: Set Clock]]<br />
<br />
=====Wireless Quickstart For the Live Environment=====<br />
(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. Note that the following quickstart procedure ''executed at this point in the installation'' will initialize your wireless hardware for use ''in the live environment''. These steps (or some other form of wireless management) must be repeated from the actual installed system after booting into it.<br />
<br />
Also note that these steps are optional if wireless connectivity is unnecessary at this point in the installation; wireless functionality may always be established later.<br />
<br />
;Does the Wireless Chipset require Firmware?<br />
A small percentage of wireless chipsets also require firmware, in addition to a corresponding driver. If the wireless chipset requires firmware, you are likely to receive this error:<br />
<br />
{{Command|ifconfig wlan0 up|SIOCSIFFLAGS: No such file or directory|prompt=#}}<br />
<br />
If unsure, invoke <code>/usr/bin/dmesg</code> to query the kernel log for a firmware request from the wireless chipset.<br />
<br />
Example from an Intel chipset which requires and has requested firmware from the kernel at boot:<br />
<br />
{{Command|<nowiki>dmesg | grep firmware</nowiki>|firmware: requesting iwlwifi-5000-1.ucode}}<br />
<br />
If there is no output, it may be concluded that the system's wireless chipset does not require firmware.<br />
<br />
{{Note | '''Wireless chipset firmware packages (for cards which require them) are pre-installed under /lib/firmware in the live environment, (on CD/USB stick) ''but must be explicitly installed to your actual system to provide wireless functionality after you reboot into it!'' Package 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 installed system.<br />
<br />
The basic procedure will be:<br />
* Switch to a free virtual console, e.g.: <ALT>+F3<br />
* Login as root<br />
* (Optional) Identify the wireless interface:<br />
# lspci | grep -i net<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 />
<br />
Example: <br />
{{Command|iwconfig|<nowiki> lo no wireless extensions.<br />
eth0 no wireless extensions.<br />
wlan0 unassociated ESSID:""<br />
Mode:Managed Channel=0 Access Point: Not-Associated<br />
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0<br />
Retry limit:7 RTS thr:off Fragment thr:off<br />
Power Management:off<br />
Link Quality:0 Signal level:0 Noise level:0<br />
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0<br />
Tx excessive retries:0 Invalid misc:0 Missed beacon:0<br />
</nowiki>|prompt=#}}<br />
<code>wlan0</code> is the available wireless interface in the example.<br />
* Bring the interface up with <code>/sbin/ifconfig <interface> up</code>.<br />
An example using the wlan0 interface:<br />
# ifconfig wlan0 up<br />
(Remember, your interface may be named something else, depending on your module (driver) and chipset: wlan0, eth1, etc.)<br />
<br />
* If the essid has been forgotten or is unknown, use <code>/sbin/iwlist <interface> scan</code> to scan for nearby networks.<br />
# iwlist wlan0 scan<br />
<br />
* Associate your wireless device with the access point you want to use. Depending on the encryption (none, WEP, or WPA), the procedure may differ. You need to know the name of the chosen wireless network (ESSID), e.g. 'linksys' in the following examples:<br />
* An example using a ''non-encrypted'' network:<br />
# iwconfig wlan0 essid &quot;linksys&quot;<br />
* An example using ''WEP and a hexadecimal key'':<br />
# iwconfig wlan0 essid &quot;linksys&quot; key 0241baf34c<br />
* An example using ''WEP and an ASCII passphrase'':<br />
# iwconfig wlan0 essid "linksys" key s:pass1<br />
* Using ''WPA'' requires extra steps:<br />
<br />
Step 1: The default /etc/wpa_supplicant.conf is rather obtuse. For the purpose of simplifying, rename the default wpa_supplicant.conf file:<br />
# mv /etc/wpa_supplicant.conf /etc/wpa_supplicant.conf.original<br />
<br />
Step 2: Using wpa_passphrase, provide your wireless network name and wpa key to be encrypted and written to /etc/wpa_supplicant.conf<br />
<br />
The following example encrypts the key 'my_secret_passkey' of the 'linksys' wireless network, generates a new configuration file (/etc/wpa_supplicant.conf), and subsequently redirects the encrypted key, writing it to the file:<br />
# wpa_passphrase linksys "my_secret_passkey" > /etc/wpa_supplicant.conf<br />
(Substitute the actual SSID and passkey)<br />
<br />
Step 3: Using the wpa_supplicant command, attempt to associate to the wireless network specified in /etc/wpa_supplicant.conf and the now encrypted key contained therein:<br />
# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf<br />
Check [[WPA_Supplicant|WPA supplicant]] for more information and troubleshooting.<br />
<br />
{{Note | The network connection process may be automated later by using the default Arch network daemon, [[netcfg]], [[wicd]], or another network manager of your choice.}}<br />
<br />
'''Verify Association and IP routing'''<br />
<br />
* After utilizing the appropriate association method outlined above, wait a few moments and confirm you have successfully associated to the access point before continuing. e.g.:<br />
# iwconfig wlan0<br />
Output should indicate the wireless network is associated with the interface. Again, your interface may be named something besides wlan0.<br />
* Request an IP address with <code>/sbin/dhcpcd <interface> </code>. e.g.:<br />
# dhcpcd wlan0<br />
* Lastly, ensure you can route using <code>/bin/ping</code>:<br />
# ping -c 3 www.google.com<br />
<br />
You should have a working network connection. For troubleshooting, check the detailed [[Wireless_Setup|Wireless Setup]] page.<br />
<br />
Return to tty1 with <ALT>+F1. Continue with [[#B: Set Clock|B: Set Clock]]<br />
<br />
===B: Set Clock===<br />
* UTC - Choose UTC if running only <tt>UNIX</tt>-like operating system(s).<br />
<br />
* localtime - Choose local if multi-booting with a Microsoft Windows OS.<br />
<br />
===C: 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 />
{{Warning|Choosing the Cancel button in the Prepare Hard Drive menu will not cancel the operations you have selected - see {{Bug|19805}}. If you must cancel the installation from this menu, press <Control>+C to exit the installer completely and immediately.}}<br />
<br />
{{Note|Partitioning may be performed before initiating the Arch installation if desired, by utilizing [http://gparted.sourceforge.net/download.php GParted] or other available tools. If the installation drive has already been partitioned to the required specifications, continue with [[#Set Filesystem Mountpoints| Set Filesystem Mountpoints]]}}<br />
<br />
Verify 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) to utilize for the 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 (Erases an ENTIRE hard drive and sets up partitions)<br />
Auto-Prepare divides the disk into the following configuration:<br />
<br />
* ext2 /boot partition, default size 32MB. ''You will be prompted to modify the size to your requirement.''<br />
* swap partition, default size 256MB. ''You will be prompted to modify the size to your requirement.''<br />
* A Separate / and /home partition, (sizes can also be specified). Available filesystems include ext2, ext3, ext4, reiserfs, xfs and jfs, but note that ''both / and /home shall share the same fs type'' if choosing the Auto Prepare option.<br />
<br />
Be warned that Auto-prepare will completely erase the chosen hard drive. Read the <font color="red">warning</font> presented by the installer very carefully, and make sure the correct device is about to be partitioned.<br />
<br />
* Option 2: Manually Partition Hard Drives (with cfdisk)- recommended.<br />
<br />
This option will allow for the most robust and customized partitioning solution for your personal needs.<br />
<br />
* Option 3: Manually Configure block devices, filesystems and mountpoints<br />
If this is selected, the system will list what filesystems and mountpoints it has found and ask you if you wish to use these. If selecting "Yes", you will be given a choice to select the desired method of identification, ie. by dev, label or uuid.<br />
<br />
* Option 4: Rollback last filesystem changes<br />
<br />
''At this point, more advanced GNU/Linux users who are familiar and comfortable with manually partitioning may wish to skip down to '''[[#D: Select Packages|D: Select Packages]]''' below.''<br />
<br />
{{Note|If you are installing to 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 are 3 types of disk partitions:<br />
#Primary<br />
#Extended<br />
#Logical<br />
'''Primary''' partitions can be bootable, and are limited to 4 partitions per disk or raid volume. If a partitioning scheme requires more than 4 partitions, an '''extended''' partition which will contain '''logical''' partitions will be required.<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 through sda3 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 the 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. If the installation machine provides gratuitous amounts of RAM (more than 1024 MB) it may be possible to completely forget a swap partition altogether, since the option to create a [[HOW TO: Create swap file|swap file]] is always available later. A 1 GB swap partition will be used in this example.<br />
{{Note|If using suspend-to-disk, (hibernate) a swap partition at least '''equal''' in size to the amount of physical RAM is required. 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. If you would like to dual boot Arch Linux and a Windows operating system please see [[Windows and Arch Dual Boot]].<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. Therefore, certain directories under / are not themselves candidates for separate partitions. (See warning below).''<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. /boot is essential for booting, but is unique in that it may still be kept on its own separate partition (if required).''<br />
<br />
'''/home''' ''Provides subdirectories, each named for a system user, for miscellaneous personal data storage as well as user-specific configuration files for applications.''<br />
<br />
'''/usr''' ''While root is the primary filesystem, /usr is the secondary hierarchy for all system users' data, including the majority of multi-user utilities and applications. /usr is shareable, read-only data. This means that /usr shall be shareable between various hosts and must not be written to, except in the case of system update/upgrade. Any information that is host-specific or varies with time is stored elsewhere.''<br />
<br />
'''/tmp''' ''directory for programs that require temporary files such as '.lck' files, which can be used to prevent multiple instances of their respective program until a task is completed, at which point the '.lck' file will be removed. Programs must not assume that any files or directories in /tmp are preserved between invocations of the program and files and directories located under /tmp will typically be deleted whenever the system is booted.''<br />
<br />
'''/var''' ''contains variable data; spool directories and files, administrative and logging data, pacman's cache, the ABS tree, etc. /var exists in order to make it possible to mount /usr as read-only. Everything that historically went into /usr that is written to during system operation (as opposed to installation and software maintenance) must reside under /var.''<br />
{{Warning | Besides /boot, directories essential for booting are: ''''''/bin', '/etc', '/lib', 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 />
{{Note | /var contains many small files. This should be taken into consideration when choosing a filesystem type for it, (if creating its own separate partition).}}<br />
<br />
=====How big should my partitions be?=====<br />
This question is best answered based upon individual needs.<br />
You may wish to simply create '''one partition for root and one partition for swap or only one root partition without swap''' or refer to the following examples and consider these guidelines to provide a frame of reference:<br />
* The root filesystem (/) in the example will contain the /usr directory, which can become moderately large, depending upon how much software is installed. 15-20 GB should be sufficient for most users.<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. If you are using an SSD, you may wish to locate your /var on an HDD and keep the / and /home partitions on your SSD to avoid needless read/writes to the SSD. 8-12 Gigs on a desktop system should be sufficient for /var, depending largely upon how much software you intend to install. Servers tend to have relatively larger /var filesystems.<br />
<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. Remember that if you chose to reinstall Arch, all the data on your /home partition will be untouched (so long as you have a separate /home partition).<br />
<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, ~10GB /var, 1GB swap, and a /home containing the remaining disk space.'''''<br />
<br />
=====Create Partitions with 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 10256 #/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 />
{{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 />
Specify each partition and corresponding mountpoint to your requirements. (Recall that partitions end in a number. Therefore, '''sda''' is not itself a partition, but rather, signifies an entire drive)<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. [[Wikipedia:ext2|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. [[Wikipedia:ext3|ext3]] ''Third Extended Filesystem''- Essentially the ext2 system, but with journaling support. ext3 is backward compatible with ext2. Extremely stable, mature, and by far the most widely used, supported and developed GNU/Linux FS.<br />
<br />
3. [[Wikipedia:ext4|ext4]] ''Fourth Extended Filesystem''- Backward compatible with ext2 and ext3. Introduces support for volumes with sizes up to 1 exabyte and files with sizes up to 16 terabytes. Increases the 32,000 subdirectory limit in ext3 to 64,000. Offers online defragmentation ability.<br />
<br />
4. [[Wikipedia:ReiserFS|ReiserFS]] (V3)- Hans Reiser's high-performance journaling FS uses a very interesting method of data throughput based on an unconventional and creative algorithm. ReiserFS is touted as very fast, especially when dealing with many small files. ReiserFS is fast at formatting, yet comparatively slow at mounting. Quite mature and stable. ReiserFS is not actively developed at this time (Reiser4 is the new Reiser filesystem). Generally regarded as a good choice for /var/.<br />
<br />
5. [[Wikipedia:JFS (file system)|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 GNU/Linux. JFS currently uses the least CPU resources of any GNU/Linux filesystem. Very fast at formatting, mounting and fsck's, and very good all-around performance, especially in conjunction with the deadline I/O scheduler. (See [[JFS]].) Not as widely supported as ext or ReiserFS, but very mature and stable.<br />
<br />
6. [[Wikipedia:XFS|XFS]] - Another early journaling filesystem originally developed by Silicon Graphics for the IRIX OS and ported to GNU/Linux. XFS offers very fast throughput on large files and large filesystems. Very fast at formatting and mounting. Generally benchmarked as slower with many small files, in comparison to other filesystems. XFS is very mature and offers online defragmentation ability.<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, utilize [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 are committed to the file system to avoid metadata corruption in the event of a crash. Note that not all journaling techniques are alike; specifically, only ext3 and ext4 offer ''data-mode journaling'', (though, not by default), which journals ''both'' data ''and'' meta-data (but with a significant speed penalty). The others only offer ''ordered-mode journaling'', which journals meta-data only. While all will return your filesystem to a valid state after recovering from a crash, ''data-mode journaling'' offers the greatest protection against file system corruption and data loss but can suffer from performance degradation, as all data is written twice (first to the journal, then to the disk). Depending upon how important your data is, this may be a consideration in choosing your filesystem type.<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.<br />
{{Box Note |If you have not created and do not need a separate /boot partition, you may safely ignore the warning that it does not exist.}} Return to the main menu.<br />
<br />
===D: Select Packages===<br />
<br />
*Core ISO: Choose CD as source and select the appropriate CD drive if more than one exist on the installation machine.<br />
*Netinstall: Select an FTP/HTTP [https://www.archlinux.de/?page=MirrorStatus mirror]. ''Note that archlinux.org is throttled to 50KB/s''.<br />
*All packages during installation are from the [core] repository. They are further divided into '''Base''', and '''Base-devel'''.<br />
*Package information and brief descriptions are available [http://www.archlinux.org/packages/?repo=Core&arch=i686&limit=all&sort=pkgname here].<br />
<br />
Package selection is split into two stages. First, select the package category:<br />
{{Note | For expedience, all packages in '''base''' are selected by default. Use the space-bar to select and de-select packages.}}<br />
* '''Base''': Packages from the [core] repo to provide the minimal base environment. ''Always select it and only remove packages that will not be used.''<br />
* '''Base-devel''': Extra tools from [core] such as '''make''', and '''automake'''. ''Most beginners should choose to install it, and will probably need it later.<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 />
{{Note | If connection to a wireless network is required, remember to select and install the '''wireless_tools''' package. Some wireless interfaces also need [[Wireless_Setup#ndiswrapper|'''ndiswrapper''']] and/or a specific [[Wireless_Setup#Drivers_and_firmware|'''firmware''']]. If you plan to use WPA encryption, you will need [[WPA_Supplicant|'''wpa_supplicant''']]. The [[Wireless_Setup|Wireless Setup page]] will help you choose the correct packages for your wireless device. Also strongly consider installing [[Netcfg|'''netcfg''']], which will help you set up your network connection and profiles.}}<br />
<br />
After selecting the needed packages, leave the selection<br />
screen and continue to the next step, Install Packages.<br />
<br />
===E: Install Packages===<br />
Next, choose 'Install Packages'.<br />
*Netinstall: The [[Pacman]] package manager will now download and install your selected packages. (See tty5 for output, tty1 to return to the installer)<br />
*Core image: The packages will be installed from the CD/USB stick.<br />
<br />
In some installers, 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 />
<br />
After the packages have been downloaded, the installer will check their integrity. Next it will create the kernel from the packages downloaded.<br />
<br />
===F: 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|udev]]''' should handle most module loading automatically at boot.<br />
<br />
Now you will be asked which text editor you want to use; choose [[Nano|nano]], [http://joe-editor.sourceforge.net/ joe] or [[Vim|vi]], ('''nano''' is generally considered easiest of the 3). You will be presented with a menu including the main configuration files for your system.<br />
<br />
{{Note | ''It is very important at this point to edit, or at least 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 />
'''''Moving on...'''''<br />
<br />
====/etc/rc.conf====<br />
Arch Linux uses the file {{Filename|/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 />
<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 {{Codeline|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 '''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 {{Filename|/dev/rtc}} for hwclock<br />
* '''TIMEZONE'''=: Specify your TIMEZONE. (All available zones are under {{Filename|/usr/share/zoneinfo/}}).<br />
* '''KEYMAP'''=: The available keymaps are in {{Filename|/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 {{Filename|/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 {{Filename|/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 />
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, (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 will be using loopback filesystems, add "loop". Also specify any blacklisted modules by prefixing them with a bang (!). Udev will be forced NOT to load blacklisted modules. In the example, the IPv6 module as well as the annoying pcspeaker are blacklisted.<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=(!net-pf-10 !snd_pcsp !pcspkr loop)<br />
<br />
=====NETWORKING Section=====<br />
* '''HOSTNAME'''=:Set your HOSTNAME to your liking. This is the name of your computer. Whatever you put here, also put it in {{filename|/etc/hosts}}<br />
* '''eth0'''=: 'Ethernet, card 0'. ''If'' you are using '''static IP''', adjust the interface IP address, netmask and broadcast address. Set eth0=&quot;dhcp&quot; if you want to use '''DHCP''' for dynamic/automatic configuration.<br />
* '''INTERFACES'''=: Specify all interfaces here. Multiple interfaces should be separated with a space as in:<br />
(eth0 wlan0)<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 a dynamically assigned IP address ('''DHCP'''):<br />
<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 />
<br />
Example, using a '''static''' IP address:<br />
<br />
HOSTNAME=&quot;arch&quot;<br />
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"<br />
INTERFACES=(eth0)<br />
gateway="default gw 192.168.0.1"<br />
ROUTES=(gateway)<br />
<br />
Modify {{Filename|/etc/resolv.conf}} to specify the DNS servers of choice. Example:<br />
<br />
search my.isp.net.<br />
nameserver 4.2.2.1<br />
nameserver 4.2.2.2<br />
nameserver 4.2.2.3<br />
<br />
Various processes can overwrite the contents of {{filename|/etc/resolv.conf}}. For example, by default Arch Linux uses the '''dhcpcd''' DHCP client, which will overwrite the file when it starts. [[Resolv.conf|Various methods]] may be used to preserve the nameserver settings in {{filename|/etc/resolv.conf}}. For example, dhcpcd's configurations file may be edited to prevent the dhcpcd daemon from overwriting the file. To do this, you will need to append this to the end of {{Filename|/etc/dhcpcd.conf}}:<br />
<br />
nohook resolv.conf<br />
<br />
{{tip|If using a non-standard MTU size (a.k.a. jumbo frames) is desired AND the installation machine hardware supports them, see the [[Jumbo Frames]] wiki article for further configuration.}}<br />
<br />
=====DAEMONS Section=====<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. Asynchronous initialization by backgrounding is also supported and useful for speeding up boot.<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 (@), it shall be executed in the background; the startup sequence will not wait for successful completion of each daemon before continuing to the next. (Useful for speeding up system boot). Do not background daemons that are needed by other daemons. For example "mpd" depends on "network", therefore backgrounding network may cause mpd to break.<br />
*Edit this array whenever new system services are installed, if starting them automatically during boot is desired.<br />
<br />
{{Note | This 'BSD-style' init, is the Arch way of handling what other distributions handle with various symlinks to an /etc/init.d directory.}}<br />
<br />
;About DAEMONS<br />
<br />
The [[daemons]] line need not be changed at this time, but it is useful to explain what daemons are, as they will be addressed later in this guide.<br />
<br />
A ''daemon'' is a program that runs in the background, waiting for events to occur and offering services. A good example is a web server that waits for a request to deliver a page (e.g.:httpd) or an SSH server waiting for a user login (e.g.:sshd). While these are full-featured applications, there are also daemons whose work is not that visible. Examples are a daemon which writes messages into a log file (e.g. syslog, metalog), and a daemon which provides a graphical login (e.g.: gdm, kdm). All these programs can be added to the daemons line and will be started when the system boots. Useful daemons will be presented during this guide.<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. *nix 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/sda1 / jfs defaults,noatime 0 1<br />
/dev/sda2 /var reiserfs defaults,noatime,notail 0 2<br />
/dev/sda3 swap swap defaults 0 0<br />
/dev/sda4 /home jfs defaults,noatime 0 2<br />
{{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 (see [http://kerneltrap.org/node/14148 here] for more). 'notail' disables the ReiserFS tailpacking feature, for added performance at the cost of slightly less efficient disk usage.}}<br />
<br />
* '''<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'.<br />
<br />
{{Note | If your system has more than one hard drive, the installer will default to using UUID rather than the sd''x'' naming scheme, for consistent device mapping. '''[[Persistent block device naming| Utilizing UUID]] has several advantages and may also be preferred to avoid issues if hard disks are added to the system in the future.''' Due to active developments in the kernel and also udev, the ordering in which drivers for storage controllers are loaded may change randomly, yielding an unbootable system/kernel panic. Nearly every motherboard has several controllers (onboard SATA, onboard IDE), and due to the aforementioned development updates, /dev/sda may become /dev/sdb on the next reboot. (See [[Persistent block device naming| this wiki article]] for more information on persistent block device naming. )}}<br />
<br />
* '''<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 />
* '''<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 />
* '''<options>''': describes the mount options associated with the filesystem. It is formatted as a comma-separated list of options with no intervening spaces. It contains at least the type of mount plus any additional options appropriate to the filesystem type. For documentation on the available options for non-nfs file systems, see mount(8).<br />
<br />
* '''<dump>''': used by the dump(8) command to determine which filesystems are to be dumped. dump is a backup utility. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be backed up. ''Note that dump is not installed by default.''<br />
<br />
* '''<pass>''': 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 />
Expanded information available in the [[Fstab]] wiki entry.<br />
<br />
===='''[[Configuring mkinitcpio | /etc/mkinitcpio]].conf'''====<br />
''Most users will not need to modify this file at this time, but please read the following explanatory information.''<br />
<br />
This file allows further fine-tuning of the initial ram filesystem, or initramfs, (also historically referred to as the initial ramdisk or &quot;initrd&quot;) for your system. The initramfs is a gzipped image that is read by the kernel during boot. The purpose of the initramfs is to bootstrap the system to the point where it can access the root filesystem. This means it has to load any modules that are required for devices like IDE, SCSI, or SATA drives (or USB/FW, if you are booting from a USB/FW drive). Once the initrramfs loads the proper modules, either manually or through udev, it passes control to the kernel and your boot continues. For this reason, the initramfs only needs to contain the modules necessary to access the root filesystem. It does not need to contain every module you would ever want to use. The majority of common kernel modules will be loaded later on by udev, during the init process.<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 '''glibc''' and '''busybox''' to provide a small and lightweight base for early userspace.<br />
* It can use '''udev''' for hardware autodetection at runtime, thus preventing numerous unnecessary modules from being 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 />
<br />
If using RAID or LVM on the root filesystem, the appropriate HOOKS must be configured. See the wiki pages for [[Installing with Software RAID or LVM| RAID]] and [[Configuring mkinitcpio | /etc/mkinitcpio]] for more info. If using a non-US keyboard. add the "<code>keymap</code>" hook to load your local keymap during boot. Add the "<code>usbinput</code>" hook if using a USB keyboard. Don't forget to add the "<code>usb</code>" hook when installing arch on an external hard drive which is connected via usb, e.g.:<br />
HOOKS="base udev autodetect pata scsi sata usb filesystems keymap usbinput"<br />
(Otherwise, if boot fails for some reason you will be asked to enter root's password for system maintenance but will be unable to do so.)<br />
<br />
If you need support for booting from USB devices, FireWire devices, PCMCIA devices, NFS shares, software RAID arrays, LVM2 volumes, encrypted volumes, or DSDT support, configure your HOOKS accordingly.<br />
<br />
If doing a CF or SD card install, you may need to add the <code>usb</code> HOOK for your system to boot properly.<br />
<br />
''If you are using a US keyboard, and have no need for any of the above HOOKS, editing this configuration should be unnecessary at this point.''<br />
<br />
'''mkinitcpio''' is an Arch innovation developed by Aaron Griffin and Tobias Powalowski with some help from the community.<br />
<br />
==== /etc/modprobe.d/modprobe.conf====<br />
<br />
This file can be used to set special configuration options for the kernel modules. It is unnecessary to configure this file in the example.<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 [[Network#For DHCP IP]]).''<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 />
{{Note |''This format, '''including the 'localhost' and your actual host name''', is required for program compatibility! So, if you have named your computer "arch", then that line above should look like this:<br />
127.0.0.1 localhost.localdomain localhost arch<br />
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 />
* restrict it to your local LAN network (range 192.168.0.0 to 192.168.0.255)<br />
sshd: 192.168.0.<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 text, correctly displaying regional monetary values, time and date formats, alphabetic idiosyncrasies, and other locale-specific standards.<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 />
{{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 />
====Pacman-Mirror====<br />
Choose a mirror repository for '''pacman'''.<br />
*''archlinux.org is throttled, limiting downloads to 50KB/s''<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 />
====Done====<br />
When you select "Done", the system will rebuild the images and put you back to the Main Menu. This may take some time.<br />
<br />
===G: 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.alioth.debian.org/ LILO] or [[Syslinux]].<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/sda1 ro<br />
initrd /boot/kernel26.img<br />
{{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 />
Example for /boot on the separate partition:<br />
title Arch Linux (Main)<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 ro<br />
initrd /kernel26.img<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''').<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, (usually a safe default; you may wish to change this in case it causes problems booting).<br />
<br />
Note: Depending on hardware, 'rootdelay=8' may need to be added to the kernel options in order to be able to boot from an external usb hard drive.<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 />
{{tip|For more details, see the [[GRUB]] wiki page.}}<br />
<br />
===H: 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: Update==<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 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.<br />
<br />
{{Note |Virtual consoles 1-6 are available. You may switch between them with ALT+F1...F6}}<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, an &quot;unknown host&quot; error is received, you may conclude that your network is not properly configured. You may choose to double-check the following files for integrity and proper settings:<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 />
{{Tip|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 wlan0 up<br />
<br />
{{Note|If you get this error message: <code>SIOCSIFFLAGS: No such file or directory</code> it most certainly means your wireless chipset requires a firmware to function, which you forgot to install during package selection. See [[Beginners'_Guide#Does_the_Wireless_Chipset_require_Firmware.3F|Does the Wireless Chipset require Firmware?]] and [[Beginners'_Guide#D:_Select_Packages|Select Packages]].}}<br />
<br />
* Associate your wireless device with the access point you want to use. Depending on the encryption (none, WEP, or WPA), the procedure may differ. You need to know the name of the chosen wireless network (ESSID), e.g. 'linksys' in the following examples:<br />
* An example using a ''non-encrypted'' network:<br />
# iwconfig wlan0 essid &quot;linksys&quot;<br />
* An example using ''WEP and a hexadecimal key'':<br />
# iwconfig wlan0 essid &quot;linksys&quot; key 0241baf34c<br />
* An example using ''WEP and an ASCII passphrase'':<br />
# iwconfig wlan0 essid "linksys" key s:pass1<br />
* Using ''WPA'', the procedure requires a bit more work. Check [[WPA_Supplicant|WPA supplicant]] for more information and troubleshooting:<br />
# wpa_passphrase linksys "secretpassphrase" > /etc/wpa_supplicant.conf<br />
# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf<br />
<br />
* Check you have successfully associated to the access point before continuing:<br />
# iwconfig wlan0<br />
<br />
* Request an IP address with <code>/sbin/dhcpcd <interface> </code>. e.g.:<br />
# dhcpcd wlan0<br />
* Ensure you can route using <code>/bin/ping</code>:<br />
# ping -c 3 www.google.com<br />
<br />
You should have a working network connection. For troubleshooting, check the detailed [[Wireless_Setup|Wireless Setup]] page.<br />
<br />
====Proxy Server====<br />
If you are behind a proxy server, edit /etc/wgetrc and set http_proxy and ftp_proxy in it.<br />
<br />
====Analog Modem, ISDN, and DSL (PPPoE)====<br />
See [[Internet Access]] for detailed instructions.<br />
<br />
===Step 2: Update, Sync, and Upgrade the system with [[pacman]]===<br />
Now we will update the system using [[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, to occupy a very modest memory footprint, and to be 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. Pacman's output is streamlined, very readable and provides ETA for each package download. Arch uses pkg.tar.gz tarballs and is in the process of moving to the pkg.tar.xz format.<br />
<br />
Pacman will now be used to download software packages from remote repositories and install them onto your system.<br />
<br />
====Package Repositories====<br />
Arch currently offers the following 5 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 ensure the system remains in a usable state. These are the absolute system-critical packages.<br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<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.<br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<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 />
<br />
<nowiki>*</nowiki> they are expected to break something on update and need to be tested first.<br />
<br />
<nowiki>*</nowiki> 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.<br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<br />
{{Note|[testing] is the only repository that can have name collisions with any of the other official repositories. Therefore, if enabled, [testing] must be the first repo listed in <code>pacman.conf</code>.}}<br />
<br />
{{Warning|Only experienced users should use [testing].}}<br />
<br />
=====[community]=====<br />
<br />
The [community] repository is maintained by the ''Trusted Users (TUs)'' and is simply the binary branch of the ''Arch User Repository ([[AUR]])''. It contains binary packages which originated as PKGBUILDs from ''AUR'' [unsupported] that have acquired enough votes and were adopted by a ''TU''. Like all repos listed above, [community] may be readily accessed by pacman.<br />
* TU maintained<br />
* All binary packages<br />
* pacman accessible<br />
<br />
=====[multilib]=====<br />
<br />
Users running 64 bit arch linux may want to install and use applications that are not available in 64 bit (and most desktop or laptop users probably will). The 32 bit versions of these applications can be used, but require that certain 32 bit libraries are installed. These libraries are available in the [multilib] repository.<br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<br />
<br />
{{Note | If you want to use this repository, you should add the lines below to <code>/etc/pacman.conf</code> }}<br />
[multilib]<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
=====AUR (unsupported)=====<br />
<br />
The '''[[AUR]]''' also contains the '''unsupported''' branch, which cannot be accessed directly by pacman*. '''AUR''' [unsupported] does not contain binary packages. Rather, it provides more than sixteen thousand PKGBUILD scripts for building packages from source, that may be unavailable through the other repos. When an AUR unsupported package acquires enough popular votes, it may be moved to the AUR [community] binary repo, if a TU is willing to adopt and maintain it there.<br />
* TU maintained<br />
* All PKGBUILD bash build scripts<br />
* '''''Not''''' pacman accessible by default<br />
<br />
<nowiki>*</nowiki> pacman wrappers ('''''[[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 />
<br />
Note that the defaults should work, so modifying at this point may be unnecessary, but verification is always recommended. Further info available in the [[Mirrors]] article.<br />
# nano /etc/pacman.conf<br />
Example:<br />
{{File|name=/etc/pacman.conf|content=<nowiki>#<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 />
</nowiki>}}<br />
<br />
Enable all desired repositories (remove the # in front of the 'Include =' and '[repository]' lines).<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 />
Defines pacman repository mirrors and priorities.<br />
<br />
'''Build a mirrorlist using the rankmirrors script''' (Optional)<br />
<br />
<code>/usr/bin/rankmirrors</code> is a bash script which will attempt to detect uncommented mirrors specified in /etc/pacman.d/mirrorlist which are closest to the installation machine based on latency. Faster mirrors will dramatically improve pacman performance, and the overall Arch Linux experience. This script may be run periodically, especially if the chosen mirrors provide inconsistent throughput and/or updates. Note that <code>rankmirrors</code> does not test for throughput. Too/ls such as <code>wget</code> or <code>rsync</code> may be used to effectively test for mirror throughput after a new <code>/etc/pacman.d/mirrorlist</code> has been generated.<br />
<br />
'''Initially force pacman to refresh the package lists'''<br />
<br />
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 />
Use pacman to install curl:<br />
# pacman -S curl<br />
<br />
*'''''If you get an error at this step, use the command "nano /etc/pacman.d/mirrorlist" and uncomment a server that suits you.'' ''<br />
<br />
'''cd''' to the /etc/pacman.d/ directory:<br />
# cd /etc/pacman.d<br />
Backup the existing /etc/pacman.d/mirrorlist:<br />
# cp mirrorlist mirrorlist.backup<br />
Edit mirrorlist.backup and uncomment all mirrors on the same continent or within geographical proximity to test with rankmirrors.<br />
# nano mirrorlist.backup<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 closest mirrors<br />
<br />
Force pacman to refresh all package lists with the new mirrorlist in place:<br />
# pacman -Syy<br />
<br />
If you want to get help from the IRC channel, you will find it easier if you install and use curlpaste:<br />
# pacman -S curlpaste<br />
<br />
====Mirrorcheck for up-to-date packages====<br />
Some of the official mirrors may contain packages that are out-of-date. [https://www.archlinux.de/?page=MirrorStatus;orderby=lastsync;sort=1 ArchLinux Mirrorcheck] reports various aspects about the mirrors such as network problems with mirrors, data collection problems, the last time mirrors have been synced, etc.<br />
<br />
One may wish to manually inspect /etc/pacman.d/mirrorlist, ensuring that the file contains only up-to-date mirrors if having the latest package versions is a priority.<br />
<br />
====Ignoring packages====<br />
After executing the command &quot;pacman -Syu&quot;, the entire system will be updated. It is possible to prevent a package from being upgraded. A typical scenario would be a package for which an upgrade may prove problematic for the system. In this case, there are two options; indicate the package(s) to skip in the pacman command line using the --ignore switch (do pacman -S --help for details) or permanently indicate the package(s) to skip in the /etc/pacman.conf file in the IgnorePkg array. List each package, with one intervening space :<br />
IgnorePkg = wine<br />
The typical way to use Arch is to use pacman to install all packages unless there is no package available, in which case [[ABS]] may be used. Many user-contributed package build scripts are also available in the [[AUR]] and can be installed manually with [[makepkg]], or with an [[AUR helper]].<br />
<br />
The power user is expected to keep the system up to date with pacman -Syu, rather than selectively upgrading packages. You may diverge from this typical usage as you wish; just be warned that there is a greater chance that things will not work as intended and that it could break your system. The majority of complaints happen when selective upgrading, unusual compilation or improper software installation is performed. Use of '''IgnorePkg''' in /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, have a look at the [[pacman]] wiki entry at your own leisure.<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 required configurations and modifications 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 />
or:<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 />
{{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 />
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 />
==Part III: Add a user==<br />
<br />
Linux is a multi-user environment. You should not do your everyday work using the root account. It is more than poor practice; it is dangerous. Root is for administrative tasks. Instead, add a normal, non-root, user account using the <code>/usr/sbin/useradd</code> program.<br />
<br />
useradd -m -g [initial_group] -G [additional_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''' The group name or number of the user's initial login group. The group name must exist. If a group number is provided, it must refer to an already existing group. If not specified, the behavior of useradd will depend on the USERGROUPS_ENAB variable contained in /etc/login.defs.<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.<br />
* '''-s''' The path and filename of the user´s default login shell. Arch Linux init scripts use Bash. After the boot process is complete, the default login shell is user-specified. (Ensure the chosen shell package is installed if choosing something other than Bash).<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 hardware acceleration<br />
*'''wheel''' - for using sudo<br />
*'''games''' - needed for write permission for games in the games group<br />
*'''power''' - used w/ power options (e.g.: shutdown with power button)<br />
*'''scanner''' - for using a scanner<br />
A typical desktop system example, adding a user named "archie" specifying bash as the login shell:<br />
useradd -m -g users -G audio,lp,optical,storage,video,wheel,games,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 password.)<br />
<br />
Your new non-root user has now been created, complete with a home directory and a login password.<br />
<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 />
If you want to change the name of your user or any existing user, see the [[Change username]] page of the Arch wiki and/or 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 />
===Install and setup Sudo (Optional)===<br />
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.<br />
<br />
By default, the visudo command uses the editor [[vi]]. If you do not know how to use vi, you may set the EDITOR environment variable to the editor of your choice, such as in this example with the editor "nano":<br />
# EDITOR=nano visudo<br />
{{Note|Please note that you are setting the variable and starting visudo on the same line at the same time. This will not work properly as two separated commands.}}<br />
<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 />
In the previous section we added your user to the "wheel" group. To give users in the wheel group full root privileges when they precede a command with &quot;sudo&quot;, uncomment the following line:<br />
%wheel ALL=(ALL) ALL<br />
Now you can give any user access to the sudo command by simply adding them to the wheel group.<br />
<br />
For more information, such as sudoer <TAB> completion, see [[Sudo]]<br />
<br />
Further, for security purposes, it is good practice to restrict access to the "su" command to users in the "wheel" group only. This can be accomplished by editing /etc/pam.d/su:<br />
# nano /etc/pam.d/su<br />
Uncomment the following line:<br />
auth required pam_wheel.so use_uid<br />
<br />
==Part IV: Sound==<br />
<br />
The [[Wikipedia:Advanced Linux Sound Architecture|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 />
{{Note| Alsa is included in the Arch mainline kernel and udev will automatically probe your hardware at boot, loading the corresponding kernel module for your audio card. Therefore, your sound should already be working, but upstream sources mute all channels by default.}}<br />
{{Note| [[Wikipedia:Open Sound System|OSS4.2]] 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.2 instead. Instructions can be found in the [[OSS|OSS article]].}}<br />
<br />
The alsa-utils package contains the alsamixer userspace tool, which allows configuration of the sound device from the console or terminal.<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, 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 />
You must log out to activate this change. 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 {{keypress|M}}. With the key {{keypress|↑}} increased the volume to obtain a value of zero dB gain, this wording is found in the upper left. Higher values of gain produce distorted sounds and crackling.<br />
<br />
Card: NVidia CK804<br />
Chip: Realtek ALC658D<br />
View: F3:[Playback] F4: Capture F5: All<br />
Item: PCM ['''dB gain: 0,00, 0,00''']<br />
<br />
Usually a value around 75 produces a gain of zero, but some cards to a maximum value do not add any gain. Some machines, (like the Thinkpad T61), have a '''Speaker''' channel which must be unmuted and adjusted as well. Leave alsamixer by pressing ESC.<br />
<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 woman's voice saying, &quot;Front, center.&quot;<br />
<br />
====Saving the sound settings====<br />
Switch back to root user and store these settings using <code>/usr/sbin/alsactl</code> :<br />
# alsactl -f /var/lib/alsa/asound.state store<br />
This will create the file {{Filename|/var/lib/alsa/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 at boot.<br />
# nano /etc/rc.conf<br />
DAEMONS=(syslog-ng network crond '''alsa''')<br />
{{Note| The alsa daemon merely restores your volume mixer levels on boot up by reading {{Filename|/var/lib/alsa/asound.state}}. It is separate from the alsa audio library (and kernel level API).''}}<br />
<br />
{{Tip|For advanced information and troubleshooting, see [[ALSA]].}}<br />
<br />
==Part V: '''G'''raphical '''U'''ser '''I'''nterface==<br />
<br />
===Step 1: Install X===<br />
<br />
The '''X''' Window System version 11 (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).<br />
<br />
'''X''' provides the basic framework, or primitives, for building GUI environments: spaces for interaction with a mouse, keyboard, or other input to windows on the screen. '''X''' does not mandate the user interface per application, the individual client programs handle this. '''X''' does add that graphic splendor at the cost of an extra layer.<br />
<br />
'''X''' is so named because it was preceded by the '''W''' Window System, originally developed at Stanford University.<br />
<br />
{{Warning|If you're installing Arch in a Virtualbox guest, you need a different way to complete X installation. See [[Virtualbox#Running Arch Linux as a guest|Running Arch Linux as a guest]], then skip the A,B,C steps below.<br />
}}<br />
<br />
====A: Install Xorg====<br />
Now we will install the base '''[[Xorg]]''' packages using pacman. This is the first step in building a GUI.<br />
<br />
Install the base packages:<br />
# pacman -S xorg<br />
<br />
Install mesa for 3D support:<br />
<br />
# pacman -S mesa<br />
<br />
The 3D utilities glxgears and glxinfo are included in the '''mesa-demos''' package, install if needed:<br />
<br />
# pacman -S mesa-demos<br />
<br />
====B: Install video driver====<br />
<br />
Next, you should install a driver for your graphics card.<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<br />
<br />
{{Note| The '''vesa''' driver is the most generic, and should work with almost any modern video chipset. If you cannot find a suitable driver for your video chipset, vesa ''should'' work with any video card, but it offers only slow 2D.}}<br />
<br />
If you need a list of all open-source video drivers, do:<br />
$ pacman -Ss xf86-video | less<br />
Or use this list of open-source drivers, and the corresponding video chipsets:<br />
<br />
*'''xf86-video-apm''' — Alliance ProMotion video driver<br />
*'''xf86-video-ark''' — ark video driver<br />
*'''xf86-video-ast''' — ASPEED AST Graphics video driver<br />
*'''xf86-video-ati''' — ATI(AMD) radeon video driver<br />
**'''xf86-video-r128''' — ATI(AMD) video driver for X.org ati Rage128 video<br />
**'''xf86-video-mach64''' — ATI(AMD) video driver for X.org mach64 video<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-intel''' — Intel i810/i830/i915/945G/G965+ video drivers<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-nouveau''' — Open Source 3D acceleration driver for nVidia cards<br />
*'''xf86-video-openchrome''' — VIA/S3G UniChrome, UniChrome Pro and Chrome9 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-vmware''' — vmware video driver<br />
*'''xf86-video-voodoo''' — voodoo video driver<br />
*'''xf86-video-xgi''' — XGI video driver<br />
*'''xf86-video-xgixp''' — XGIXP video driver<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 />
{{Tip|For some Intel graphics cards, configuration may be necessary to get proper 2D or 3D performance, see [[Intel]] for more information.}}<br />
<br />
=====NVIDIA Graphics Cards=====<br />
NVIDIA users have three options for drivers (in addition to the vesa driver):<br />
* The open source nouveau driver, which offers fast 2d acceleration and experimental 3d support which is good enough for basic compositing (note: does not support powersaving yet). [http://nouveau.freedesktop.org/wiki/FeatureMatrix Feature Matrix.]<br />
* The open source (but obfuscated) nv driver, which is very slow and only has 2d support.<br />
* The proprietary nvidia drivers, which offer good 3d performance and powersaving. See [[NVIDIA]] for more information. Even if you plan on using the proprietary drivers, it's recommended to start with nouveau and then switch to the binary driver, because nouveau will almost always work out-of-the-box, while nvidia will require configuration and likely some troubleshooting.<br />
<br />
The open-source nouveau driver should be good enough for most users and is recommended:<br />
<br />
# pacman -S xf86-video-nouveau<br />
<br />
For 3D support (highly experimental):<br />
<br />
# pacman -S nouveau-dri<br />
<br />
Create the file {{Filename|/etc/X11/xorg.conf.d/20-nouveau.conf}}, and input the following contents:<br />
<br />
Section "Device"<br />
Identifier "n"<br />
Driver "nouveau"<br />
EndSection<br />
<br />
This is required to ensure that nouveau driver is loaded. Xorg is not yet smart enough to do this by itself.<br />
<br />
{{Tip|For advanced instructions, see [[Nouveau]].}}<br />
<br />
=====ATI Graphics Cards=====<br />
ATI owners have two options for drivers (in addition to the vesa driver):<br />
* The open source '''''radeon''''' driver provided by the '''xf86-video-ati''' package. It fully supports Radeon chipsets up to X1950 (latest R500 chipsets). Cards up to the 9200 series are fully supported, stable, and provide full 2D and 3D acceleration. Cards from 9500 to HD4000 feature full 2D acceleration, and stable/partly implemented 3D acceleration, but lack certain features provided by the proprietary driver; power management is under development and in an advanced stage, but not on par with catalyst. HD5000 support is currently a work in progress. Supports KMS and HDMI with audio output since kernel 2.6.33. [http://wiki.x.org/wiki/RadeonFeature Feature Matrix.]<br />
* The proprietary '''''fglrx''''' driver provided by the [http://aur.archlinux.org/packages.php?O=0&K=catalyst&do_Search=Go catalyst] package located in the [[AUR]]. It supports only newer devices (HD2xxx and newer). It was once a package offered by Arch in the <code>extra</code> repository, but as of March 2009, official support has been dropped because of dissatisfaction with the quality and speed of development of the proprietary driver. See [[ATI Catalyst]] for more information.<br />
<br />
The open-source driver is the recommended choice:<br />
<br />
Install the '''''radeon''''' ATI Driver:<br />
# pacman -S xf86-video-ati<br />
<br />
{{Tip|For advanced instructions, see [[ATI]].}}<br />
<br />
====C: Install input drivers====<br />
<br />
Udev should be capable of detecting your hardware without problems and evdev (xf86-input-evdev) is the modern, hotplugging input driver for almost all devices so in most cases, installing input drivers is not needed. At this point, evdev has already been installed as a dependency of Xorg.<br />
<br />
If evdev does not support your device, install the needed driver from the xorg-input-drivers group.<br />
<br />
For a complete list of available input drivers, invoke a pacman search:<br />
# pacman -Ss xf86-input | less<br />
<br />
{{Note|You only need xf86-input-keyboard or xf86-input-mouse if you plan on disabling hotplugging, otherwise, evdev will act as the input driver.}}<br />
<br />
Laptop users (or users with a touchscreen) will also need the synaptics package to allow X to configure the touchpad/touchscreen:<br />
# pacman -S xf86-input-synaptics<br />
{{Tip|For instructions on fine tuning or troubleshooting touchpad settings, see the [[Touchpad Synaptics]] article.}}<br />
<br />
===Step 2: Configure X (Optional)===<br />
<br />
{{Warning|Proprietary drivers usually require a reboot after installation along with configuration. See [[NVIDIA]] or [[ATI Catalyst]] for details.}}<br />
<br />
X.Org X Server features auto-configuration. Therefore, it can function without an xorg.conf.<br />
<br />
{{Note|If you want to configure something like horizontal/vertical refresh or monitor dimensions if your monitor's EDID is incorrect, see [[Xorg]].}}<br />
<br />
The current arrangement of configuration files is found in /etc/X11. Within that directory, there is the subdirectory /etc/X11/xorg.conf.d. This is the directory which contains the default configuration files for the X server. These are supplied by your distribution, automatically-created or may also be added to for your personal configuration and editing. However, it is also possible to simply create and edit {{filename|/etc/X11/xorg.conf}}, since that file is read last after those in the /xorg.conf.d directory.<br />
<br />
====Non-US keyboard====<br />
<br />
If you do not use a standard US keyboard you need to set the keyboard layout in {{Filename|/etc/X11/xorg.conf.d/10-evdev.conf}}:<br />
<br />
Section "InputClass"<br />
Identifier "evdev keyboard catchall"<br />
MatchIsKeyboard "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Driver "evdev"<br />
'''Option "XkbLayout" "be"'''<br />
EndSection<br />
<br />
{{Note|The '''XkbLayout''' key may differ from the keymap code you used with the km or loadkeys command. For instance, the uk layout corresponds to the key: '''gb'''.}}<br />
<br />
===Step 3: Starting a basic graphical environment===<br />
<br />
This section will explain how to start the very basic graphical environment included with in the xorg group. This uses the simple default X window manager, twm.<br />
<br />
The default X environment is rather bare, and step 5 will deal with installing a desktop environment or window manager of your choice to supplement X.<br />
<br />
If you just installed Xorg, there is an empty .xinitrc file in your $HOME that you need to either delete or edit in order for X to start properly. If you do not do this X will show a blank screen with what appears to be no errors in your Xorg.0.log. Simply deleting it will get it running with a default X environment.<br />
<br />
$ rm ~/.xinitrc<br />
<br />
====Message bus====<br />
<br />
dbus is likely required for many of your applications to work properly, if you know you don't need it, skip this section.<br />
<br />
=====Installation=====<br />
<br />
Install dbus:<br />
<br />
# pacman -S dbus<br />
<br />
=====Starting the daemon=====<br />
<br />
You should add dbus to your DAEMONS array in {{filename|/etc/rc.conf}}:<br />
<br />
DAEMONS=(syslog-ng '''dbus''' network crond)<br />
<br />
If you need to start dbus without rebooting, run<br />
<br />
# /etc/rc.d/dbus start<br />
<br />
====Starting X====<br />
<br />
{{Note|The Ctrl-Alt-Backspace shortcut traditionally used to kill X has been deprecated and will not work to exit out of this test. You can enable Ctrl-Alt-Backspace by editing xorg.conf, as described at [[Xorg#Ctrl-Alt-Backspace doesn't work|here]].}}<br />
<br />
Finally, start Xorg:<br />
$ startx<br />
or<br />
$ xinit -- /usr/bin/X -nolisten tcp<br />
<br />
If the screen goes black, you may still attempt to switch to a different virtual console (CTRL-Alt-F2, for example), and login blindly as root, followed by <Enter>, followed by root's password followed by <Enter>.<br />
<br />
You can attempt to kill the X server with <code>/usr/bin/pkill</code> (note the capital letter '''X'''):<br />
# pkill X<br />
<br />
If pkill does not work, reboot blindly with:<br />
# reboot<br />
or<br />
# init 6<br />
<br />
====In case of errors====<br />
If a problem occurs, then look for errors in {{Filename|/var/log/Xorg.0.log}}. Be on the lookout for any lines beginning with {{Codeline|(EE)}} which represent errors, and also {{Codeline|(WW)}} which are warnings that could indicate other issues.<br />
<br />
$ grep EE /var/log/Xorg.0.log<br />
<br />
Errors may also be searched for in the console output of the virtual console from which '''X''' was started.<br />
<br />
See the [[Xorg]] article for detailed instructions and troubleshooting.<br />
<br />
=====Need Help?=====<br />
<br />
If you are still having trouble after consulting the [[Xorg]] article and need assistance via the Arch forums, be sure to install and use wgetpaste:<br />
<br />
# pacman -S wgetpaste<br />
Use wgetpaste and provide links for the following files when asking for help in your forum post:<br />
* ~/.xinitrc<br />
* /etc/X11/xorg.conf<br />
* /var/log/Xorg.0.log<br />
* /var/log/Xorg.0.log.old<br />
Use wgetpaste like so:<br />
$ wgetpaste </path/to/file><br />
Post the corresponding links given within your forum post. Be sure to provide appropriate hardware and driver information as well.<br />
{{Warning| '''''It is very important to provide detail when troubleshooting X. Please provide all pertinent information as detailed above when asking for assistance on the Arch forums. '''''}}<br />
<br />
===Step 4: 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 is a set of high quality, general-purpose fonts.<br />
<br />
Install with:<br />
# pacman -S ttf-dejavu<br />
<br />
Refer to [[Font Configuration]] for how to configure font rendering and [[Fonts]] for font suggestions and installation instructions.<br />
<br />
===Step 5: Choose and install a graphical interface===<br />
<br />
The X Window System provides the basic framework for building a graphical user interface (GUI).<br />
<br />
A Window Manager controls the placement and appearance of application windows in conjunction with the X Window System.<br />
<br />
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.<br />
<br />
Alternatively, you can build your own DE by using a WM and the applications of your choice.<br />
<br />
{{Note|Unlike lots of other distributions, Arch won't decide what graphical environment you want to use. Choosing your DE or WM is a very subjective and personal decision. Choose the best environment for ''your'' needs. It's worth trying out a bunch of the environments listed here before you make your choice as pacman can completely remove anything you install.}}<br />
<br />
After installing a graphical interface, you'll probably want to continue with [[General Recommendations]] for post-installation instructions.<br />
<br />
====Desktop Environments====<br />
<br />
See [[Desktop Environment#Desktop environments|Desktop environments]] for more information.<br />
<br />
====Window Managers====<br />
<br />
See [[Window Manager#Window managers|Window managers]] for more information.<br />
<br />
===Methods for starting your Graphical Environment===<br />
<br />
====A: Manually====<br />
You might prefer to start X manually from your terminal rather than booting straight into the desktop (if not, skip to [[Beginner's Guide#B: Automatically|B: Automatically]]). There are three methods for starting X manually. Choose the one that suits you best:<br />
<br />
=====Method 1: DE-specific commands=====<br />
For some users, this method might be the easiest since you need only enter a command without any configuring.<br />
Simply use a command to launch your WM/DE.<br />
You may always start your desktop environment with '''xinit''' or '''startx''', followed by the path to your DE's script:<br />
<br />
$ xinit /usr/bin/gnome-session<br />
or<br />
$ startx /usr/bin/startkde<br />
<br />
from the shell prompt. Note that such a command does not finish until you logout of the DE.<br />
{{Note|If you do '''xinit gnome-session''' instead of '''xinit /usr/bin/gnome-session''', then you will have problems on your desktop. Always include the complete path (/usr/bin/)}}<br />
<br />
Optionally, you can make an [[Bashrc#Aliases|alias]] in /etc/bash.bashrc so you don't have to type the whole command.<br />
...<br />
alias gnome="xinit /usr/bin/gnome-session"<br />
...<br />
<br />
Alternatively, if you wish to launch a Display Manager (AKA login manager) rather than go directly into your desktop, you can use the command for your installed Display Manager. For example, for gnome:<br />
$ gdm<br />
or KDE:<br />
$ kdm<br />
etc.<br />
<br />
=====Method 2: using runlevels=====<br />
By default, Linux is set up to have different [[runlevels]]. Arch boots into runlevel 3 by default. Runlevel 5 is typically used in Linux for loading X server.<br />
Edit the file /etc/inittab. In the last section at the bottom of the file, uncomment the appropriate line for your desktop environment's display manager. For example, for gnome it would look like this:<br />
# Example lines for starting a login manager<br />
#x:5:respawn:/usr/bin/xdm -nodaemon<br />
x:5:respawn:/usr/sbin/gdm -nodaemon<br />
#x:5:respawn:/usr/bin/kdm -nodaemon<br />
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1<br />
<br />
Now, simply start your desktop environment, as root, with<br />
# init 5<br />
or, as a normal user, with<br />
$ sudo init 5<br />
<br />
=====Method 3: using .xinitrc=====<br />
This method involves the most configuring.<br />
<br />
First we need to configure ~/.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 />
<br />
{{Note | '''[[.xinitrc]]''' is a so-called 'dot' (.) file. Files in a *nix 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 />
The '''startx''' and '''xinit''' commands 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 />
<br />
# su - ''yourusername''<br />
<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 />
{{Note | This template file '''[[.xinitrc]]''' is available in the /etc/skel directory when the package '''xorg-xinit''' is installed.}}<br />
<br />
* Sample .xinitrc 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 uncomment the line that corresponds to your Desktop Environment. For example, if you use Gnome, it will look something like this:<br />
<br />
<pre><br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
<br />
exec gnome-session<br />
# exec startkde<br />
# exec startxfce4<br />
# exec wmaker<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
# exec openbox-session<br />
# ...or the Window Manager of your choice<br />
# exec xterm<br />
</pre><br />
For KDE uncomment:<br />
exec startkde<br />
For fluxbox:<br />
exec fluxbox<br />
etc...<br />
<br />
{{Note | ''Be sure to have only '''one''' uncommented '''exec''' line in ~/.xinitrc'' for now.}}<br />
<br />
Now we're ready to launch X. Start '''X''' as a '''normal, non-root''' user, with:<br />
<br />
$ startx<br />
or<br />
$ xinit<br />
<br />
Your desktop should open up now. You can test your keyboard and its layout in it. Try moving your mouse around and enjoy the view.<br />
<br />
If trouble with automounting is experienced, try using the following command in ~/.xinitrc instead. (Replace "startxfce4" with the command that is appropriate for your window manager/DE.)<br />
exec ck-launch-session startxfce4<br />
This will ensure the various environment variables are set correctly by starting a clean consolekit session. ConsoleKit is a framework for keeping track of the various users, sessions, and seats present on a system. It provides a mechanism for software to react to changes of any of these items or of any of the metadata associated with them. It works in conjunction with dbus, and other tools.<br />
<br />
====B: Automatically====<br />
Most users might prefer to have their desktop start automatically during boot instead of starting X manually. There are two methods for starting X automatically. Choose the one that suits you best:<br />
<br />
=====Method 1: using runlevels=====<br />
This method expands on Method 2 from the section above on starting X manually.<br />
<br />
By default, Linux is set up to have different [[runlevels]]. Arch boots into runlevel 3 by default. Runlevel 5 is typically used for loading X server.<br />
Edit the file /etc/inittab.<br />
In the first section, uncomment '''id:5:initdefault:''' so it looks like this:<br />
## Only one of the following two lines can be uncommented!<br />
# Boot to console<br />
#id:3:initdefault:<br />
# Boot to X11<br />
id:5:initdefault:<br />
This tells Arch to boot to runlevel 5 when you start your computer.<br />
<br />
In the last section at the bottom of the file, uncomment the appropriate line for your desktop environment's display manager. For example, for gnome it would look like this:<br />
# Example lines for starting a login manager<br />
#x:5:respawn:/usr/bin/xdm -nodaemon<br />
x:5:respawn:/usr/sbin/gdm -nodaemon<br />
#x:5:respawn:/usr/bin/kdm -nodaemon<br />
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1<br />
<br />
=====Method 2: using a daemon=====<br />
Simply add your display manager to your daemons array in /etc/rc.conf. For example, it would look like this for gnome:<br />
DAEMONS=(syslog-ng dbus network '''gdm''' ...)<br />
You might try backgrounding your display manager so that other daemons continue loading while the display manager loads:<br />
DAEMONS=(syslog-ng dbus hal network '''@kdm''' ...)<br />
<br />
==Appendix==<br />
For a list of [[Common Applications]] and [[Lightweight Applications]], visit their respective articles.<br />
<br />
See [[General Recommendations]] for post-installation tutorials like setting up CPU frequency scaling or font rendering.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Beginners%27_guide_old&diff=125626
Beginners' guide old
2010-12-20T07:49:29Z
<p>Cantabile: /* Flash Memory Device or USB stick */ run dd as root; don't mention the size of the install media</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]] [[Category:About Arch (English)]]<br />
[[Category:HOWTOs (English)]] [[Category:Website Resources]]<br />
{{i18n|Beginners' Guide}}<br />
[[de:Anleitung für Einsteiger]]<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|Related}}<br />
{{Article summary wiki|:Category:Accessibility (English)}}<br />
{{Article summary wiki|Official Arch Linux Install Guide}}<br />
{{Article summary wiki|General Recommendations}}<br />
{{Article summary end}}<br />
==Preface==<br />
=====Introduction=====<br />
Welcome. This document will guide you through the process of installing and configuring [[Arch Linux]]; a simple, lightweight GNU/Linux distribution targeted at competent users. 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 />
* [http://www.archlinux.org/packages/?q= All packages] compiled for i686 and x86_64 architectures<br />
* [[Arch Boot Process|BSD style]] init scripts, featuring one centralized configuration file<br />
* [[mkinitcpio]]: A simple and dynamic initramfs creator<br />
* [[Pacman]] package manager is lightweight and agile, with a very modest memory footprint<br />
* The [[Arch Build System]]: A ports-like package building system, providing a simple framework to create installable Arch packages from source<br />
* The [[Arch User Repository]]: offering many thousands of user contributed build scripts and the opportunity to share your own<br />
<br />
=====License=====<br />
<br />
Arch Linux, pacman, documentation, and scripts are copyright<br />
©2002-2007 by Judd Vinet, ©2007-2010 by Aaron Griffin and are licensed under the GNU General Public License Version 2.<br />
<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 as you consider simplicity:'''<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..The height of cultivation always runs to simplicity.&quot;'' - Bruce Lee<br />
<br />
=====About This Guide=====<br />
<br />
The Arch wiki is an excellent resource and should be consulted for issues [[Main Page|first]]. The IRC room (at freenode #archlinux), and the [http://bbs.archlinux.org/ forums] are also available if the answer cannot be found elsewhere.<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 <u>before</u> carrying out the tasks contained.}}<br />
<br />
The guide is divided into 5 main components:<br />
<br />
*[[#Part I: Install the Base System|Part I: Install the Base system]]<br />
*[[#Part II: Update|Part II: Update]]<br />
*[[#Part III: Add a user|Part III: Add a user]]<br />
*[[#Part IV: Sound|Part IV: Sound]]<br />
*[[#Part V: Graphical User Interface|Part V: Graphical User Interface]]<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 installation media from [http://archlinux.org/download/ here]. The latest version is 2010.05<br />
<br />
* Both the Core and the Netinstall images 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 utilities), the Linux kernel, and a few extra libraries and modules.''<br />
* Core images facilitate both installing from CD and Net.<br />
* Netinstall images are smaller and provide no packages themselves; the entire system is retrieved via internet.<br />
* [[Arch64_FAQ|The Arch64 FAQ]] can help you choose between the 32-, 64-bit and dual versions.<br />
* Don't forget to download the checksum txt files along with your chosen ISO.<br />
<br />
====Check the Integrity of the Downloaded File====<br />
Open a terminal, change to the directory where the downloaded files have been placed, and type at the CLI (Command Line Interface):<br />
$ sha1sum --check name_of_checksum_file.txt name_of_selected_iso_file.iso<br />
This should give you an "OK" for the one you have. (Simply ignore other lines.) If not, download all files again.<br />
The md5sum check works the same way.<br />
<br />
====Install from an Existing GNU/Linux Distro====<br />
Arch is flexible enough to be installed to another partition ''from within'' an existing distro or Live CD. See [[Install from Existing Linux|this wiki article]] for steps to do this. This can be useful particularly if you plan to install Arch via vnc or ssh remotely.<br />
<br />
====CD installer====<br />
Burn the .iso image file to a CD or DVD media with your preferred CD/DVD burner drive and software, and continue with [[#Step 2: Boot Arch Linux Installer | Step 2: Boot Arch Linux Installer]]<br />
{{Note| The quality of optical drives, as well as the CD media itself, vary greatly. 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 />
====Flash Memory Device or USB stick====<br />
<br />
See [[Install_from_a_USB_flash_drive|Install from a USB flash drive]] for more detailed instructions.<br />
<br />
This method will work for any type of flash media from which your BIOS will let you boot, be it a card reader or USB port.<br />
<br />
{{Warning|This procedure will irrevocably destroy all data on your media! Also, be very careful where you send the image iso, as dd will obediently write to any target you point to, even if that is your hard disk.}}<br />
<br />
'''*nix Method:'''<br />
<br />
Insert an empty or expendable flash device, determine its path, and write the .iso to the device with the <code>/bin/dd</code> program:<br />
# dd if=archlinux-2010.05-''{core|netinstall}''-''{i686|x86_64|dual}''.iso of=/dev/sd''x''<br />
where <code>if=</code> is the path to the img file and <code>of=</code> is your flash device. Make sure to use {{Filename|/dev/sd'''x'''}} and not {{Filename|/dev/sd'''x1'''}}. You will need a flash memory device large enough to accomodate the image.<br />
<br />
'''Check md5sum:'''<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 [ftp://ftp.archlinux.org/iso/2010.05/md5sums.txt 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. A typical run will look like this: <br />
{{Command|<nowiki>[sudo] dd if=archlinux-2010.05-core-i686.iso of=/dev/sdc</nowiki>|<nowiki> 744973+0 records in<br />
744973+0 records out<br />
381426176 bytes (381 MB) copied, 106.611 s, 3.6 MB/s<br />
</nowiki>}}<br />
<br />
{{Command|<nowiki>[sudo] dd if=/dev/sdc count=744973 status=noxfer | md5sum</nowiki>| 4850d533ddd343b80507543536258229 -<br />
744973+0 records in<br />
744973+0 records out}}<br />
<br />
Continue with [[#Step 2: Boot Arch Linux Installer | Step 2: Boot Arch Linux Installer]]<br />
<br />
'''Microsoft Windows Method:'''<br />
<br />
Download Disk Imager from https://launchpad.net/win32-image-writer/+download. Insert flash media. Start the Disk Imager and select the image file (Disk Imager accepts only *.IMG files, so you'll have to put "*.iso" in file open dialog to select Arch snapshot). Select the drive letter associated with the flash drive. Click "write".<br />
<br />
There are also other solutions to [[Install_from_a_USB_flash_drive#On_Windows|writing bootable ISO images to USB sticks]]. If you have problems with USB sticks disconnecting, try using different USB port and/or cable.<br />
<br />
Continue with [[#Step 2: Boot Arch Linux Installer | Step 2: Boot Arch Linux Installer]]<br />
<br />
===Step 2: Boot Arch Linux Installer===<br />
{{Tip|The memory requirement for a basic install is 64 MB of RAM.}}<br />
<br />
{{Tip|During the process, the automatic screen blanker may come on. If so, one can press the Alt key to safely obtain the normal display.}}<br />
<br />
====Boot from the Media====<br />
Insert the CD or Flash media you prepared, 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 (Power On Self-Test) phase.<br />
<br />
'''Main Menu:''' The main menu should be displayed at this point. Select the preferred choice by using the arrow keys to highlight your choice, and then by pressing Enter.<br />
<br />
Menus vary on different iso's. The 2010.05 Netinstall menu has "Boot Arch Linux (i686)", "Boot Arch Linux (x86-64)", "Boot Existing OS", "Run Memtest86+ (RAM test)", "Run x86test (CPU test)", and "Reboot"<br />
<br />
For Netinstall, choose the first or second item according to your CPU type. For Core, usually the first item, Boot Archlive, is the preferred selection. However, choose Boot Archlive [legacy IDE] if you have trouble with libata/PATA, or have no SATA (Serial ATA) drives.<br />
<br />
It is strongly recommended that you run the memory test; just to be sure. The CPU test can also provide detailed and useful specs. It may be wise to remember or record any system details of which you were unaware.<br />
<br />
====OS System Start====<br />
The system will now load and present a login prompt. Login as 'root', without the quotes.<br />
<br />
If using an Intel video chipset and the screen goes blank during the boot process, the problem is likely an issue with kernel mode setting. A possible workaround may be achieved by rebooting and pressing <Tab> at the GRUB menu to enter kernel options. At the end of the kernel line, add a space and then:<br />
i915.modeset=0<br />
<br />
When done making any changes to any menu command, simply press "Enter" to boot with that setup.<br />
<br />
See [[Intel| the Intel article]] for more information.<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 conveniently available right on the live system! To access it, change to tty2 (virtual console #2) with <ALT>+F2, log in as "root" and then invoke <code>/usr/bin/less</code> by typing in the following at the # prompt:<br />
# less /usr/share/aif/docs/official_installation_guide_en<br />
<code>less</code> will allow you to page through the document.<br />
<br />
Change back to tty1 with <ALT>+F1 to follow the rest of the install process. (Change back to tty2 at any time if you need to reference the Official Guide as you progress through the installation process.)<br />
<br />
{{tip|Please note that the official guide only covers installation and configuration of the base system. Once that is installed, it is strongly recommended that you come back here to the wiki to find out more about post-installation considerations and other related issues.}}<br />
<br />
===Step 3: Start the Installation===<br />
As root, run the installer script from tty1:<br />
# /arch/setup<br />
You should next see the displayed Arch Linux Installation Framework screen.<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. A good place to check for relative speed of source repositories is [https://www.archlinux.de/?page=MirrorStatus Mirror Status]. Choose one that matches one from the installer list.<br />
<br />
* If you chose the CORE installer, continue below with [[#B: Set Clock|B: Set Clock]].<br />
* Netinstall 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 tty3. (Select OK to continue.)<br />
<br />
====Configure Network (Netinstall)====<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 />
=====(A)DSL Quickstart for the Live Environment=====<br />
(If you have a modem or router in bridge mode to connect to your ISP)<br />
<br />
Switch to another virtual console (<Alt> + F2), login as root and invoke<br />
# pppoe-setup<br />
If everything is well configured in the end you can connect to your ISP with<br />
# pppoe-start<br />
<br />
Return to first virtual console with <ALT>+F1. Continue with [[#B: Set Clock|B: Set Clock]]<br />
<br />
=====Wireless Quickstart For the Live Environment=====<br />
(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. Note that the following quickstart procedure ''executed at this point in the installation'' will initialize your wireless hardware for use ''in the live environment''. These steps (or some other form of wireless management) must be repeated from the actual installed system after booting into it.<br />
<br />
Also note that these steps are optional if wireless connectivity is unnecessary at this point in the installation; wireless functionality may always be established later.<br />
<br />
;Does the Wireless Chipset require Firmware?<br />
A small percentage of wireless chipsets also require firmware, in addition to a corresponding driver. If the wireless chipset requires firmware, you are likely to receive this error:<br />
<br />
{{Command|ifconfig wlan0 up|SIOCSIFFLAGS: No such file or directory|prompt=#}}<br />
<br />
If unsure, invoke <code>/usr/bin/dmesg</code> to query the kernel log for a firmware request from the wireless chipset.<br />
<br />
Example from an Intel chipset which requires and has requested firmware from the kernel at boot:<br />
<br />
{{Command|<nowiki>dmesg | grep firmware</nowiki>|firmware: requesting iwlwifi-5000-1.ucode}}<br />
<br />
If there is no output, it may be concluded that the system's wireless chipset does not require firmware.<br />
<br />
{{Note | '''Wireless chipset firmware packages (for cards which require them) are pre-installed under /lib/firmware in the live environment, (on CD/USB stick) ''but must be explicitly installed to your actual system to provide wireless functionality after you reboot into it!'' Package 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 installed system.<br />
<br />
The basic procedure will be:<br />
* Switch to a free virtual console, e.g.: <ALT>+F3<br />
* Login as root<br />
* (Optional) Identify the wireless interface:<br />
# lspci | grep -i net<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 />
<br />
Example: <br />
{{Command|iwconfig|<nowiki> lo no wireless extensions.<br />
eth0 no wireless extensions.<br />
wlan0 unassociated ESSID:""<br />
Mode:Managed Channel=0 Access Point: Not-Associated<br />
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0<br />
Retry limit:7 RTS thr:off Fragment thr:off<br />
Power Management:off<br />
Link Quality:0 Signal level:0 Noise level:0<br />
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0<br />
Tx excessive retries:0 Invalid misc:0 Missed beacon:0<br />
</nowiki>|prompt=#}}<br />
<code>wlan0</code> is the available wireless interface in the example.<br />
* Bring the interface up with <code>/sbin/ifconfig <interface> up</code>.<br />
An example using the wlan0 interface:<br />
# ifconfig wlan0 up<br />
(Remember, your interface may be named something else, depending on your module (driver) and chipset: wlan0, eth1, etc.)<br />
<br />
* If the essid has been forgotten or is unknown, use <code>/sbin/iwlist <interface> scan</code> to scan for nearby networks.<br />
# iwlist wlan0 scan<br />
<br />
* Associate your wireless device with the access point you want to use. Depending on the encryption (none, WEP, or WPA), the procedure may differ. You need to know the name of the chosen wireless network (ESSID), e.g. 'linksys' in the following examples:<br />
* An example using a ''non-encrypted'' network:<br />
# iwconfig wlan0 essid &quot;linksys&quot;<br />
* An example using ''WEP and a hexadecimal key'':<br />
# iwconfig wlan0 essid &quot;linksys&quot; key 0241baf34c<br />
* An example using ''WEP and an ASCII passphrase'':<br />
# iwconfig wlan0 essid "linksys" key s:pass1<br />
* Using ''WPA'' requires extra steps:<br />
<br />
Step 1: The default /etc/wpa_supplicant.conf is rather obtuse. For the purpose of simplifying, rename the default wpa_supplicant.conf file:<br />
# mv /etc/wpa_supplicant.conf /etc/wpa_supplicant.conf.original<br />
<br />
Step 2: Using wpa_passphrase, provide your wireless network name and wpa key to be encrypted and written to /etc/wpa_supplicant.conf<br />
<br />
The following example encrypts the key 'my_secret_passkey' of the 'linksys' wireless network, generates a new configuration file (/etc/wpa_supplicant.conf), and subsequently redirects the encrypted key, writing it to the file:<br />
# wpa_passphrase linksys "my_secret_passkey" > /etc/wpa_supplicant.conf<br />
(Substitute the actual SSID and passkey)<br />
<br />
Step 3: Using the wpa_supplicant command, attempt to associate to the wireless network specified in /etc/wpa_supplicant.conf and the now encrypted key contained therein:<br />
# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf<br />
Check [[WPA_Supplicant|WPA supplicant]] for more information and troubleshooting.<br />
<br />
{{Note | The network connection process may be automated later by using the default Arch network daemon, [[netcfg]], [[wicd]], or another network manager of your choice.}}<br />
<br />
'''Verify Association and IP routing'''<br />
<br />
* After utilizing the appropriate association method outlined above, wait a few moments and confirm you have successfully associated to the access point before continuing. e.g.:<br />
# iwconfig wlan0<br />
Output should indicate the wireless network is associated with the interface. Again, your interface may be named something besides wlan0.<br />
* Request an IP address with <code>/sbin/dhcpcd <interface> </code>. e.g.:<br />
# dhcpcd wlan0<br />
* Lastly, ensure you can route using <code>/bin/ping</code>:<br />
# ping -c 3 www.google.com<br />
<br />
You should have a working network connection. For troubleshooting, check the detailed [[Wireless_Setup|Wireless Setup]] page.<br />
<br />
Return to tty1 with <ALT>+F1. Continue with [[#B: Set Clock|B: Set Clock]]<br />
<br />
===B: Set Clock===<br />
* UTC - Choose UTC if running only <tt>UNIX</tt>-like operating system(s).<br />
<br />
* localtime - Choose local if multi-booting with a Microsoft Windows OS.<br />
<br />
===C: 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 />
{{Warning|Choosing the Cancel button in the Prepare Hard Drive menu will not cancel the operations you have selected - see {{Bug|19805}}. If you must cancel the installation from this menu, press <Control>+C to exit the installer completely and immediately.}}<br />
<br />
{{Note|Partitioning may be performed before initiating the Arch installation if desired, by utilizing [http://gparted.sourceforge.net/download.php GParted] or other available tools. If the installation drive has already been partitioned to the required specifications, continue with [[#Set Filesystem Mountpoints| Set Filesystem Mountpoints]]}}<br />
<br />
Verify 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) to utilize for the 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 (Erases an ENTIRE hard drive and sets up partitions)<br />
Auto-Prepare divides the disk into the following configuration:<br />
<br />
* ext2 /boot partition, default size 32MB. ''You will be prompted to modify the size to your requirement.''<br />
* swap partition, default size 256MB. ''You will be prompted to modify the size to your requirement.''<br />
* A Separate / and /home partition, (sizes can also be specified). Available filesystems include ext2, ext3, ext4, reiserfs, xfs and jfs, but note that ''both / and /home shall share the same fs type'' if choosing the Auto Prepare option.<br />
<br />
Be warned that Auto-prepare will completely erase the chosen hard drive. Read the <font color="red">warning</font> presented by the installer very carefully, and make sure the correct device is about to be partitioned.<br />
<br />
* Option 2: Manually Partition Hard Drives (with cfdisk)- recommended.<br />
<br />
This option will allow for the most robust and customized partitioning solution for your personal needs.<br />
<br />
* Option 3: Manually Configure block devices, filesystems and mountpoints<br />
If this is selected, the system will list what filesystems and mountpoints it has found and ask you if you wish to use these. If selecting "Yes", you will be given a choice to select the desired method of identification, ie. by dev, label or uuid.<br />
<br />
* Option 4: Rollback last filesystem changes<br />
<br />
''At this point, more advanced GNU/Linux users who are familiar and comfortable with manually partitioning may wish to skip down to '''[[#D: Select Packages|D: Select Packages]]''' below.''<br />
<br />
{{Note|If you are installing to 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 are 3 types of disk partitions:<br />
#Primary<br />
#Extended<br />
#Logical<br />
'''Primary''' partitions can be bootable, and are limited to 4 partitions per disk or raid volume. If a partitioning scheme requires more than 4 partitions, an '''extended''' partition which will contain '''logical''' partitions will be required.<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 through sda3 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 the 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. If the installation machine provides gratuitous amounts of RAM (more than 1024 MB) it may be possible to completely forget a swap partition altogether, since the option to create a [[HOW TO: Create swap file|swap file]] is always available later. A 1 GB swap partition will be used in this example.<br />
{{Note|If using suspend-to-disk, (hibernate) a swap partition at least '''equal''' in size to the amount of physical RAM is required. 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. If you would like to dual boot Arch Linux and a Windows operating system please see [[Windows and Arch Dual Boot]].<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. Therefore, certain directories under / are not themselves candidates for separate partitions. (See warning below).''<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. /boot is essential for booting, but is unique in that it may still be kept on its own separate partition (if required).''<br />
<br />
'''/home''' ''Provides subdirectories, each named for a system user, for miscellaneous personal data storage as well as user-specific configuration files for applications.''<br />
<br />
'''/usr''' ''While root is the primary filesystem, /usr is the secondary hierarchy for all system users' data, including the majority of multi-user utilities and applications. /usr is shareable, read-only data. This means that /usr shall be shareable between various hosts and must not be written to, except in the case of system update/upgrade. Any information that is host-specific or varies with time is stored elsewhere.''<br />
<br />
'''/tmp''' ''directory for programs that require temporary files such as '.lck' files, which can be used to prevent multiple instances of their respective program until a task is completed, at which point the '.lck' file will be removed. Programs must not assume that any files or directories in /tmp are preserved between invocations of the program and files and directories located under /tmp will typically be deleted whenever the system is booted.''<br />
<br />
'''/var''' ''contains variable data; spool directories and files, administrative and logging data, pacman's cache, the ABS tree, etc. /var exists in order to make it possible to mount /usr as read-only. Everything that historically went into /usr that is written to during system operation (as opposed to installation and software maintenance) must reside under /var.''<br />
{{Warning | Besides /boot, directories essential for booting are: ''''''/bin', '/etc', '/lib', 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 />
{{Note | /var contains many small files. This should be taken into consideration when choosing a filesystem type for it, (if creating its own separate partition).}}<br />
<br />
=====How big should my partitions be?=====<br />
This question is best answered based upon individual needs.<br />
You may wish to simply create '''one partition for root and one partition for swap or only one root partition without swap''' or refer to the following examples and consider these guidelines to provide a frame of reference:<br />
* The root filesystem (/) in the example will contain the /usr directory, which can become moderately large, depending upon how much software is installed. 15-20 GB should be sufficient for most users.<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. If you are using an SSD, you may wish to locate your /var on an HDD and keep the / and /home partitions on your SSD to avoid needless read/writes to the SSD. 8-12 Gigs on a desktop system should be sufficient for /var, depending largely upon how much software you intend to install. Servers tend to have relatively larger /var filesystems.<br />
<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. Remember that if you chose to reinstall Arch, all the data on your /home partition will be untouched (so long as you have a separate /home partition).<br />
<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, ~10GB /var, 1GB swap, and a /home containing the remaining disk space.'''''<br />
<br />
=====Create Partitions with 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 10256 #/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 />
{{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 />
Specify each partition and corresponding mountpoint to your requirements. (Recall that partitions end in a number. Therefore, '''sda''' is not itself a partition, but rather, signifies an entire drive)<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. [[Wikipedia:ext2|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. [[Wikipedia:ext3|ext3]] ''Third Extended Filesystem''- Essentially the ext2 system, but with journaling support. ext3 is backward compatible with ext2. Extremely stable, mature, and by far the most widely used, supported and developed GNU/Linux FS.<br />
<br />
3. [[Wikipedia:ext4|ext4]] ''Fourth Extended Filesystem''- Backward compatible with ext2 and ext3. Introduces support for volumes with sizes up to 1 exabyte and files with sizes up to 16 terabytes. Increases the 32,000 subdirectory limit in ext3 to 64,000. Offers online defragmentation ability.<br />
<br />
4. [[Wikipedia:ReiserFS|ReiserFS]] (V3)- Hans Reiser's high-performance journaling FS uses a very interesting method of data throughput based on an unconventional and creative algorithm. ReiserFS is touted as very fast, especially when dealing with many small files. ReiserFS is fast at formatting, yet comparatively slow at mounting. Quite mature and stable. ReiserFS is not actively developed at this time (Reiser4 is the new Reiser filesystem). Generally regarded as a good choice for /var/.<br />
<br />
5. [[Wikipedia:JFS (file system)|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 GNU/Linux. JFS currently uses the least CPU resources of any GNU/Linux filesystem. Very fast at formatting, mounting and fsck's, and very good all-around performance, especially in conjunction with the deadline I/O scheduler. (See [[JFS]].) Not as widely supported as ext or ReiserFS, but very mature and stable.<br />
<br />
6. [[Wikipedia:XFS|XFS]] - Another early journaling filesystem originally developed by Silicon Graphics for the IRIX OS and ported to GNU/Linux. XFS offers very fast throughput on large files and large filesystems. Very fast at formatting and mounting. Generally benchmarked as slower with many small files, in comparison to other filesystems. XFS is very mature and offers online defragmentation ability.<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, utilize [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 are committed to the file system to avoid metadata corruption in the event of a crash. Note that not all journaling techniques are alike; specifically, only ext3 and ext4 offer ''data-mode journaling'', (though, not by default), which journals ''both'' data ''and'' meta-data (but with a significant speed penalty). The others only offer ''ordered-mode journaling'', which journals meta-data only. While all will return your filesystem to a valid state after recovering from a crash, ''data-mode journaling'' offers the greatest protection against file system corruption and data loss but can suffer from performance degradation, as all data is written twice (first to the journal, then to the disk). Depending upon how important your data is, this may be a consideration in choosing your filesystem type.<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.<br />
{{Box Note |If you have not created and do not need a separate /boot partition, you may safely ignore the warning that it does not exist.}} Return to the main menu.<br />
<br />
===D: Select Packages===<br />
<br />
*Core ISO: Choose CD as source and select the appropriate CD drive if more than one exist on the installation machine.<br />
*Netinstall: Select an FTP/HTTP [https://www.archlinux.de/?page=MirrorStatus mirror]. ''Note that archlinux.org is throttled to 50KB/s''.<br />
*All packages during installation are from the [core] repository. They are further divided into '''Base''', and '''Base-devel'''.<br />
*Package information and brief descriptions are available [http://www.archlinux.org/packages/?repo=Core&arch=i686&limit=all&sort=pkgname here].<br />
<br />
Package selection is split into two stages. First, select the package category:<br />
{{Note | For expedience, all packages in '''base''' are selected by default. Use the space-bar to select and de-select packages.}}<br />
* '''Base''': Packages from the [core] repo to provide the minimal base environment. ''Always select it and only remove packages that will not be used.''<br />
* '''Base-devel''': Extra tools from [core] such as '''make''', and '''automake'''. ''Most beginners should choose to install it, and will probably need it later.<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 />
{{Note | If connection to a wireless network is required, remember to select and install the '''wireless_tools''' package. Some wireless interfaces also need [[Wireless_Setup#ndiswrapper|'''ndiswrapper''']] and/or a specific [[Wireless_Setup#Drivers_and_firmware|'''firmware''']]. If you plan to use WPA encryption, you will need [[WPA_Supplicant|'''wpa_supplicant''']]. The [[Wireless_Setup|Wireless Setup page]] will help you choose the correct packages for your wireless device. Also strongly consider installing [[Netcfg|'''netcfg''']], which will help you set up your network connection and profiles.}}<br />
<br />
After selecting the needed packages, leave the selection<br />
screen and continue to the next step, Install Packages.<br />
<br />
===E: Install Packages===<br />
Next, choose 'Install Packages'.<br />
*Netinstall: The [[Pacman]] package manager will now download and install your selected packages. (See tty5 for output, tty1 to return to the installer)<br />
*Core image: The packages will be installed from the CD/USB stick.<br />
<br />
In some installers, 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 />
<br />
After the packages have been downloaded, the installer will check their integrity. Next it will create the kernel from the packages downloaded.<br />
<br />
===F: 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|udev]]''' should handle most module loading automatically at boot.<br />
<br />
Now you will be asked which text editor you want to use; choose [[Nano|nano]], [http://joe-editor.sourceforge.net/ joe] or [[Vim|vi]], ('''nano''' is generally considered easiest of the 3). You will be presented with a menu including the main configuration files for your system.<br />
<br />
{{Note | ''It is very important at this point to edit, or at least 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 />
'''''Moving on...'''''<br />
<br />
====/etc/rc.conf====<br />
Arch Linux uses the file {{Filename|/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 />
<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 {{Codeline|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 '''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 {{Filename|/dev/rtc}} for hwclock<br />
* '''TIMEZONE'''=: Specify your TIMEZONE. (All available zones are under {{Filename|/usr/share/zoneinfo/}}).<br />
* '''KEYMAP'''=: The available keymaps are in {{Filename|/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 {{Filename|/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 {{Filename|/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 />
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, (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 will be using loopback filesystems, add "loop". Also specify any blacklisted modules by prefixing them with a bang (!). Udev will be forced NOT to load blacklisted modules. In the example, the IPv6 module as well as the annoying pcspeaker are blacklisted.<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=(!net-pf-10 !snd_pcsp !pcspkr loop)<br />
<br />
=====NETWORKING Section=====<br />
* '''HOSTNAME'''=:Set your HOSTNAME to your liking. This is the name of your computer. Whatever you put here, also put it in {{filename|/etc/hosts}}<br />
* '''eth0'''=: 'Ethernet, card 0'. ''If'' you are using '''static IP''', adjust the interface IP address, netmask and broadcast address. Set eth0=&quot;dhcp&quot; if you want to use '''DHCP''' for dynamic/automatic configuration.<br />
* '''INTERFACES'''=: Specify all interfaces here. Multiple interfaces should be separated with a space as in:<br />
(eth0 wlan0)<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 a dynamically assigned IP address ('''DHCP'''):<br />
<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 />
<br />
Example, using a '''static''' IP address:<br />
<br />
HOSTNAME=&quot;arch&quot;<br />
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"<br />
INTERFACES=(eth0)<br />
gateway="default gw 192.168.0.1"<br />
ROUTES=(gateway)<br />
<br />
Modify {{Filename|/etc/resolv.conf}} to specify the DNS servers of choice. Example:<br />
<br />
search my.isp.net.<br />
nameserver 4.2.2.1<br />
nameserver 4.2.2.2<br />
nameserver 4.2.2.3<br />
<br />
Various processes can overwrite the contents of {{filename|/etc/resolv.conf}}. For example, by default Arch Linux uses the '''dhcpcd''' DHCP client, which will overwrite the file when it starts. [[Resolv.conf|Various methods]] may be used to preserve the nameserver settings in {{filename|/etc/resolv.conf}}. For example, dhcpcd's configurations file may be edited to prevent the dhcpcd daemon from overwriting the file. To do this, you will need to append this to the end of {{Filename|/etc/dhcpcd.conf}}:<br />
<br />
nohook resolv.conf<br />
<br />
{{tip|If using a non-standard MTU size (a.k.a. jumbo frames) is desired AND the installation machine hardware supports them, see the [[Jumbo Frames]] wiki article for further configuration.}}<br />
<br />
=====DAEMONS Section=====<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. Asynchronous initialization by backgrounding is also supported and useful for speeding up boot.<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 (@), it shall be executed in the background; the startup sequence will not wait for successful completion of each daemon before continuing to the next. (Useful for speeding up system boot). Do not background daemons that are needed by other daemons. For example "mpd" depends on "network", therefore backgrounding network may cause mpd to break.<br />
*Edit this array whenever new system services are installed, if starting them automatically during boot is desired.<br />
<br />
{{Note | This 'BSD-style' init, is the Arch way of handling what other distributions handle with various symlinks to an /etc/init.d directory.}}<br />
<br />
;About DAEMONS<br />
<br />
The [[daemons]] line need not be changed at this time, but it is useful to explain what daemons are, as they will be addressed later in this guide.<br />
<br />
A ''daemon'' is a program that runs in the background, waiting for events to occur and offering services. A good example is a web server that waits for a request to deliver a page (e.g.:httpd) or an SSH server waiting for a user login (e.g.:sshd). While these are full-featured applications, there are also daemons whose work is not that visible. Examples are a daemon which writes messages into a log file (e.g. syslog, metalog), and a daemon which provides a graphical login (e.g.: gdm, kdm). All these programs can be added to the daemons line and will be started when the system boots. Useful daemons will be presented during this guide.<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. *nix 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/sda1 / jfs defaults,noatime 0 1<br />
/dev/sda2 /var reiserfs defaults,noatime,notail 0 2<br />
/dev/sda3 swap swap defaults 0 0<br />
/dev/sda4 /home jfs defaults,noatime 0 2<br />
{{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 (see [http://kerneltrap.org/node/14148 here] for more). 'notail' disables the ReiserFS tailpacking feature, for added performance at the cost of slightly less efficient disk usage.}}<br />
<br />
* '''<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'.<br />
<br />
{{Note | If your system has more than one hard drive, the installer will default to using UUID rather than the sd''x'' naming scheme, for consistent device mapping. '''[[Persistent block device naming| Utilizing UUID]] has several advantages and may also be preferred to avoid issues if hard disks are added to the system in the future.''' Due to active developments in the kernel and also udev, the ordering in which drivers for storage controllers are loaded may change randomly, yielding an unbootable system/kernel panic. Nearly every motherboard has several controllers (onboard SATA, onboard IDE), and due to the aforementioned development updates, /dev/sda may become /dev/sdb on the next reboot. (See [[Persistent block device naming| this wiki article]] for more information on persistent block device naming. )}}<br />
<br />
* '''<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 />
* '''<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 />
* '''<options>''': describes the mount options associated with the filesystem. It is formatted as a comma-separated list of options with no intervening spaces. It contains at least the type of mount plus any additional options appropriate to the filesystem type. For documentation on the available options for non-nfs file systems, see mount(8).<br />
<br />
* '''<dump>''': used by the dump(8) command to determine which filesystems are to be dumped. dump is a backup utility. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be backed up. ''Note that dump is not installed by default.''<br />
<br />
* '''<pass>''': 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 />
Expanded information available in the [[Fstab]] wiki entry.<br />
<br />
===='''[[Configuring mkinitcpio | /etc/mkinitcpio]].conf'''====<br />
''Most users will not need to modify this file at this time, but please read the following explanatory information.''<br />
<br />
This file allows further fine-tuning of the initial ram filesystem, or initramfs, (also historically referred to as the initial ramdisk or &quot;initrd&quot;) for your system. The initramfs is a gzipped image that is read by the kernel during boot. The purpose of the initramfs is to bootstrap the system to the point where it can access the root filesystem. This means it has to load any modules that are required for devices like IDE, SCSI, or SATA drives (or USB/FW, if you are booting from a USB/FW drive). Once the initrramfs loads the proper modules, either manually or through udev, it passes control to the kernel and your boot continues. For this reason, the initramfs only needs to contain the modules necessary to access the root filesystem. It does not need to contain every module you would ever want to use. The majority of common kernel modules will be loaded later on by udev, during the init process.<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 '''glibc''' and '''busybox''' to provide a small and lightweight base for early userspace.<br />
* It can use '''udev''' for hardware autodetection at runtime, thus preventing numerous unnecessary modules from being 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 />
<br />
If using RAID or LVM on the root filesystem, the appropriate HOOKS must be configured. See the wiki pages for [[Installing with Software RAID or LVM| RAID]] and [[Configuring mkinitcpio | /etc/mkinitcpio]] for more info. If using a non-US keyboard. add the "<code>keymap</code>" hook to load your local keymap during boot. Add the "<code>usbinput</code>" hook if using a USB keyboard. Don't forget to add the "<code>usb</code>" hook when installing arch on an external hard drive which is connected via usb, e.g.:<br />
HOOKS="base udev autodetect pata scsi sata usb filesystems keymap usbinput"<br />
(Otherwise, if boot fails for some reason you will be asked to enter root's password for system maintenance but will be unable to do so.)<br />
<br />
If you need support for booting from USB devices, FireWire devices, PCMCIA devices, NFS shares, software RAID arrays, LVM2 volumes, encrypted volumes, or DSDT support, configure your HOOKS accordingly.<br />
<br />
If doing a CF or SD card install, you may need to add the <code>usb</code> HOOK for your system to boot properly.<br />
<br />
''If you are using a US keyboard, and have no need for any of the above HOOKS, editing this configuration should be unnecessary at this point.''<br />
<br />
'''mkinitcpio''' is an Arch innovation developed by Aaron Griffin and Tobias Powalowski with some help from the community.<br />
<br />
==== /etc/modprobe.d/modprobe.conf====<br />
<br />
This file can be used to set special configuration options for the kernel modules. It is unnecessary to configure this file in the example.<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 [[Network#For DHCP IP]]).''<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 />
{{Note |''This format, '''including the 'localhost' and your actual host name''', is required for program compatibility! So, if you have named your computer "arch", then that line above should look like this:<br />
127.0.0.1 localhost.localdomain localhost arch<br />
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 />
* restrict it to your local LAN network (range 192.168.0.0 to 192.168.0.255)<br />
sshd: 192.168.0.<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 text, correctly displaying regional monetary values, time and date formats, alphabetic idiosyncrasies, and other locale-specific standards.<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 />
{{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 />
====Pacman-Mirror====<br />
Choose a mirror repository for '''pacman'''.<br />
*''archlinux.org is throttled, limiting downloads to 50KB/s''<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 />
====Done====<br />
When you select "Done", the system will rebuild the images and put you back to the Main Menu. This may take some time.<br />
<br />
===G: 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.alioth.debian.org/ LILO] or [[Syslinux]].<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/sda1 ro<br />
initrd /boot/kernel26.img<br />
{{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 />
Example for /boot on the separate partition:<br />
title Arch Linux (Main)<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 ro<br />
initrd /kernel26.img<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''').<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, (usually a safe default; you may wish to change this in case it causes problems booting).<br />
<br />
Note: Depending on hardware, 'rootdelay=8' may need to be added to the kernel options in order to be able to boot from an external usb hard drive.<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 />
{{tip|For more details, see the [[GRUB]] wiki page.}}<br />
<br />
===H: 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: Update==<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 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.<br />
<br />
{{Note |Virtual consoles 1-6 are available. You may switch between them with ALT+F1...F6}}<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, an &quot;unknown host&quot; error is received, you may conclude that your network is not properly configured. You may choose to double-check the following files for integrity and proper settings:<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 />
{{Tip|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 wlan0 up<br />
<br />
{{Note|If you get this error message: <code>SIOCSIFFLAGS: No such file or directory</code> it most certainly means your wireless chipset requires a firmware to function, which you forgot to install during package selection. See [[Beginners'_Guide#Does_the_Wireless_Chipset_require_Firmware.3F|Does the Wireless Chipset require Firmware?]] and [[Beginners'_Guide#D:_Select_Packages|Select Packages]].}}<br />
<br />
* Associate your wireless device with the access point you want to use. Depending on the encryption (none, WEP, or WPA), the procedure may differ. You need to know the name of the chosen wireless network (ESSID), e.g. 'linksys' in the following examples:<br />
* An example using a ''non-encrypted'' network:<br />
# iwconfig wlan0 essid &quot;linksys&quot;<br />
* An example using ''WEP and a hexadecimal key'':<br />
# iwconfig wlan0 essid &quot;linksys&quot; key 0241baf34c<br />
* An example using ''WEP and an ASCII passphrase'':<br />
# iwconfig wlan0 essid "linksys" key s:pass1<br />
* Using ''WPA'', the procedure requires a bit more work. Check [[WPA_Supplicant|WPA supplicant]] for more information and troubleshooting:<br />
# wpa_passphrase linksys "secretpassphrase" > /etc/wpa_supplicant.conf<br />
# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf<br />
<br />
* Check you have successfully associated to the access point before continuing:<br />
# iwconfig wlan0<br />
<br />
* Request an IP address with <code>/sbin/dhcpcd <interface> </code>. e.g.:<br />
# dhcpcd wlan0<br />
* Ensure you can route using <code>/bin/ping</code>:<br />
# ping -c 3 www.google.com<br />
<br />
You should have a working network connection. For troubleshooting, check the detailed [[Wireless_Setup|Wireless Setup]] page.<br />
<br />
====Proxy Server====<br />
If you are behind a proxy server, edit /etc/wgetrc and set http_proxy and ftp_proxy in it.<br />
<br />
====Analog Modem, ISDN, and DSL (PPPoE)====<br />
See [[Internet Access]] for detailed instructions.<br />
<br />
===Step 2: Update, Sync, and Upgrade the system with [[pacman]]===<br />
Now we will update the system using [[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, to occupy a very modest memory footprint, and to be 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. Pacman's output is streamlined, very readable and provides ETA for each package download. Arch uses pkg.tar.gz tarballs and is in the process of moving to the pkg.tar.xz format.<br />
<br />
Pacman will now be used to download software packages from remote repositories and install them onto your system.<br />
<br />
====Package Repositories====<br />
Arch currently offers the following 5 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 ensure the system remains in a usable state. These are the absolute system-critical packages.<br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<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.<br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<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 />
<br />
<nowiki>*</nowiki> they are expected to break something on update and need to be tested first.<br />
<br />
<nowiki>*</nowiki> 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.<br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<br />
{{Note|[testing] is the only repository that can have name collisions with any of the other official repositories. Therefore, if enabled, [testing] must be the first repo listed in <code>pacman.conf</code>.}}<br />
<br />
{{Warning|Only experienced users should use [testing].}}<br />
<br />
=====[community]=====<br />
<br />
The [community] repository is maintained by the ''Trusted Users (TUs)'' and is simply the binary branch of the ''Arch User Repository ([[AUR]])''. It contains binary packages which originated as PKGBUILDs from ''AUR'' [unsupported] that have acquired enough votes and were adopted by a ''TU''. Like all repos listed above, [community] may be readily accessed by pacman.<br />
* TU maintained<br />
* All binary packages<br />
* pacman accessible<br />
<br />
=====[multilib]=====<br />
<br />
Users running 64 bit arch linux may want to install and use applications that are not available in 64 bit (and most desktop or laptop users probably will). The 32 bit versions of these applications can be used, but require that certain 32 bit libraries are installed. These libraries are available in the [multilib] repository.<br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<br />
<br />
{{Note | If you want to use this repository, you should add the lines below to <code>/etc/pacman.conf</code> }}<br />
[multilib]<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
=====AUR (unsupported)=====<br />
<br />
The '''[[AUR]]''' also contains the '''unsupported''' branch, which cannot be accessed directly by pacman*. '''AUR''' [unsupported] does not contain binary packages. Rather, it provides more than sixteen thousand PKGBUILD scripts for building packages from source, that may be unavailable through the other repos. When an AUR unsupported package acquires enough popular votes, it may be moved to the AUR [community] binary repo, if a TU is willing to adopt and maintain it there.<br />
* TU maintained<br />
* All PKGBUILD bash build scripts<br />
* '''''Not''''' pacman accessible by default<br />
<br />
<nowiki>*</nowiki> pacman wrappers ('''''[[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 />
<br />
Note that the defaults should work, so modifying at this point may be unnecessary, but verification is always recommended. Further info available in the [[Mirrors]] article.<br />
# nano /etc/pacman.conf<br />
Example:<br />
{{File|name=/etc/pacman.conf|content=<nowiki>#<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 />
</nowiki>}}<br />
<br />
Enable all desired repositories (remove the # in front of the 'Include =' and '[repository]' lines).<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 />
Defines pacman repository mirrors and priorities.<br />
<br />
'''Build a mirrorlist using the rankmirrors script''' (Optional)<br />
<br />
<code>/usr/bin/rankmirrors</code> is a bash script which will attempt to detect uncommented mirrors specified in /etc/pacman.d/mirrorlist which are closest to the installation machine based on latency. Faster mirrors will dramatically improve pacman performance, and the overall Arch Linux experience. This script may be run periodically, especially if the chosen mirrors provide inconsistent throughput and/or updates. Note that <code>rankmirrors</code> does not test for throughput. Too/ls such as <code>wget</code> or <code>rsync</code> may be used to effectively test for mirror throughput after a new <code>/etc/pacman.d/mirrorlist</code> has been generated.<br />
<br />
'''Initially force pacman to refresh the package lists'''<br />
<br />
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 />
Use pacman to install curl:<br />
# pacman -S curl<br />
<br />
*'''''If you get an error at this step, use the command "nano /etc/pacman.d/mirrorlist" and uncomment a server that suits you.'' ''<br />
<br />
'''cd''' to the /etc/pacman.d/ directory:<br />
# cd /etc/pacman.d<br />
Backup the existing /etc/pacman.d/mirrorlist:<br />
# cp mirrorlist mirrorlist.backup<br />
Edit mirrorlist.backup and uncomment all mirrors on the same continent or within geographical proximity to test with rankmirrors.<br />
# nano mirrorlist.backup<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 closest mirrors<br />
<br />
Force pacman to refresh all package lists with the new mirrorlist in place:<br />
# pacman -Syy<br />
<br />
If you want to get help from the IRC channel, you will find it easier if you install and use curlpaste:<br />
# pacman -S curlpaste<br />
<br />
====Mirrorcheck for up-to-date packages====<br />
Some of the official mirrors may contain packages that are out-of-date. [https://www.archlinux.de/?page=MirrorStatus;orderby=lastsync;sort=1 ArchLinux Mirrorcheck] reports various aspects about the mirrors such as network problems with mirrors, data collection problems, the last time mirrors have been synced, etc.<br />
<br />
One may wish to manually inspect /etc/pacman.d/mirrorlist, ensuring that the file contains only up-to-date mirrors if having the latest package versions is a priority.<br />
<br />
====Ignoring packages====<br />
After executing the command &quot;pacman -Syu&quot;, the entire system will be updated. It is possible to prevent a package from being upgraded. A typical scenario would be a package for which an upgrade may prove problematic for the system. In this case, there are two options; indicate the package(s) to skip in the pacman command line using the --ignore switch (do pacman -S --help for details) or permanently indicate the package(s) to skip in the /etc/pacman.conf file in the IgnorePkg array. List each package, with one intervening space :<br />
IgnorePkg = wine<br />
The typical way to use Arch is to use pacman to install all packages unless there is no package available, in which case [[ABS]] may be used. Many user-contributed package build scripts are also available in the [[AUR]] and can be installed manually with [[makepkg]], or with an [[AUR helper]].<br />
<br />
The power user is expected to keep the system up to date with pacman -Syu, rather than selectively upgrading packages. You may diverge from this typical usage as you wish; just be warned that there is a greater chance that things will not work as intended and that it could break your system. The majority of complaints happen when selective upgrading, unusual compilation or improper software installation is performed. Use of '''IgnorePkg''' in /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, have a look at the [[pacman]] wiki entry at your own leisure.<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 required configurations and modifications 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 />
or:<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 />
{{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 />
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 />
==Part III: Add a user==<br />
<br />
Linux is a multi-user environment. You should not do your everyday work using the root account. It is more than poor practice; it is dangerous. Root is for administrative tasks. Instead, add a normal, non-root, user account using the <code>/usr/sbin/useradd</code> program.<br />
<br />
useradd -m -g [initial_group] -G [additional_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''' The group name or number of the user's initial login group. The group name must exist. If a group number is provided, it must refer to an already existing group. If not specified, the behavior of useradd will depend on the USERGROUPS_ENAB variable contained in /etc/login.defs.<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.<br />
* '''-s''' The path and filename of the user´s default login shell. Arch Linux init scripts use Bash. After the boot process is complete, the default login shell is user-specified. (Ensure the chosen shell package is installed if choosing something other than Bash).<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 hardware acceleration<br />
*'''wheel''' - for using sudo<br />
*'''games''' - needed for write permission for games in the games group<br />
*'''power''' - used w/ power options (e.g.: shutdown with power button)<br />
*'''scanner''' - for using a scanner<br />
A typical desktop system example, adding a user named "archie" specifying bash as the login shell:<br />
useradd -m -g users -G audio,lp,optical,storage,video,wheel,games,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 password.)<br />
<br />
Your new non-root user has now been created, complete with a home directory and a login password.<br />
<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 />
If you want to change the name of your user or any existing user, see the [[Change username]] page of the Arch wiki and/or 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 />
===Install and setup Sudo (Optional)===<br />
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.<br />
<br />
By default, the visudo command uses the editor [[vi]]. If you do not know how to use vi, you may set the EDITOR environment variable to the editor of your choice, such as in this example with the editor "nano":<br />
# EDITOR=nano visudo<br />
{{Note|Please note that you are setting the variable and starting visudo on the same line at the same time. This will not work properly as two separated commands.}}<br />
<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 />
In the previous section we added your user to the "wheel" group. To give users in the wheel group full root privileges when they precede a command with &quot;sudo&quot;, uncomment the following line:<br />
%wheel ALL=(ALL) ALL<br />
Now you can give any user access to the sudo command by simply adding them to the wheel group.<br />
<br />
For more information, such as sudoer <TAB> completion, see [[Sudo]]<br />
<br />
Further, for security purposes, it is good practice to restrict access to the "su" command to users in the "wheel" group only. This can be accomplished by editing /etc/pam.d/su:<br />
# nano /etc/pam.d/su<br />
Uncomment the following line:<br />
auth required pam_wheel.so use_uid<br />
<br />
==Part IV: Sound==<br />
<br />
The [[Wikipedia:Advanced Linux Sound Architecture|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 />
{{Note| Alsa is included in the Arch mainline kernel and udev will automatically probe your hardware at boot, loading the corresponding kernel module for your audio card. Therefore, your sound should already be working, but upstream sources mute all channels by default.}}<br />
{{Note| [[Wikipedia:Open Sound System|OSS4.2]] 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.2 instead. Instructions can be found in the [[OSS|OSS article]].}}<br />
<br />
The alsa-utils package contains the alsamixer userspace tool, which allows configuration of the sound device from the console or terminal.<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, 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 />
You must log out to activate this change. 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 {{keypress|M}}. With the key {{keypress|↑}} increased the volume to obtain a value of zero dB gain, this wording is found in the upper left. Higher values of gain produce distorted sounds and crackling.<br />
<br />
Card: NVidia CK804<br />
Chip: Realtek ALC658D<br />
View: F3:[Playback] F4: Capture F5: All<br />
Item: PCM ['''dB gain: 0,00, 0,00''']<br />
<br />
Usually a value around 75 produces a gain of zero, but some cards to a maximum value do not add any gain. Some machines, (like the Thinkpad T61), have a '''Speaker''' channel which must be unmuted and adjusted as well. Leave alsamixer by pressing ESC.<br />
<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 woman's voice saying, &quot;Front, center.&quot;<br />
<br />
====Saving the sound settings====<br />
Switch back to root user and store these settings using <code>/usr/sbin/alsactl</code> :<br />
# alsactl -f /var/lib/alsa/asound.state store<br />
This will create the file {{Filename|/var/lib/alsa/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 at boot.<br />
# nano /etc/rc.conf<br />
DAEMONS=(syslog-ng network crond '''alsa''')<br />
{{Note| The alsa daemon merely restores your volume mixer levels on boot up by reading {{Filename|/var/lib/alsa/asound.state}}. It is separate from the alsa audio library (and kernel level API).''}}<br />
<br />
{{Tip|For advanced information and troubleshooting, see [[ALSA]].}}<br />
<br />
==Part V: '''G'''raphical '''U'''ser '''I'''nterface==<br />
<br />
===Step 1: Install X===<br />
<br />
The '''X''' Window System version 11 (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).<br />
<br />
'''X''' provides the basic framework, or primitives, for building GUI environments: spaces for interaction with a mouse, keyboard, or other input to windows on the screen. '''X''' does not mandate the user interface per application, the individual client programs handle this. '''X''' does add that graphic splendor at the cost of an extra layer.<br />
<br />
'''X''' is so named because it was preceded by the '''W''' Window System, originally developed at Stanford University.<br />
<br />
{{Warning|If you're installing Arch in a Virtualbox guest, you need a different way to complete X installation. See [[Virtualbox#Running Arch Linux as a guest|Running Arch Linux as a guest]], then skip the A,B,C steps below.<br />
}}<br />
<br />
====A: Install Xorg====<br />
Now we will install the base '''[[Xorg]]''' packages using pacman. This is the first step in building a GUI.<br />
<br />
Install the base packages:<br />
# pacman -S xorg<br />
<br />
Install mesa for 3D support:<br />
<br />
# pacman -S mesa<br />
<br />
The 3D utilities glxgears and glxinfo are included in the '''mesa-demos''' package, install if needed:<br />
<br />
# pacman -S mesa-demos<br />
<br />
====B: Install video driver====<br />
<br />
Next, you should install a driver for your graphics card.<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<br />
<br />
{{Note| The '''vesa''' driver is the most generic, and should work with almost any modern video chipset. If you cannot find a suitable driver for your video chipset, vesa ''should'' work with any video card, but it offers only slow 2D.}}<br />
<br />
If you need a list of all open-source video drivers, do:<br />
$ pacman -Ss xf86-video | less<br />
Or use this list of open-source drivers, and the corresponding video chipsets:<br />
<br />
*'''xf86-video-apm''' — Alliance ProMotion video driver<br />
*'''xf86-video-ark''' — ark video driver<br />
*'''xf86-video-ast''' — ASPEED AST Graphics video driver<br />
*'''xf86-video-ati''' — ATI(AMD) radeon video driver<br />
**'''xf86-video-r128''' — ATI(AMD) video driver for X.org ati Rage128 video<br />
**'''xf86-video-mach64''' — ATI(AMD) video driver for X.org mach64 video<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-intel''' — Intel i810/i830/i915/945G/G965+ video drivers<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-nouveau''' — Open Source 3D acceleration driver for nVidia cards<br />
*'''xf86-video-openchrome''' — VIA/S3G UniChrome, UniChrome Pro and Chrome9 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-vmware''' — vmware video driver<br />
*'''xf86-video-voodoo''' — voodoo video driver<br />
*'''xf86-video-xgi''' — XGI video driver<br />
*'''xf86-video-xgixp''' — XGIXP video driver<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 />
{{Tip|For some Intel graphics cards, configuration may be necessary to get proper 2D or 3D performance, see [[Intel]] for more information.}}<br />
<br />
=====NVIDIA Graphics Cards=====<br />
NVIDIA users have three options for drivers (in addition to the vesa driver):<br />
* The open source nouveau driver, which offers fast 2d acceleration and experimental 3d support which is good enough for basic compositing (note: does not support powersaving yet). [http://nouveau.freedesktop.org/wiki/FeatureMatrix Feature Matrix.]<br />
* The open source (but obfuscated) nv driver, which is very slow and only has 2d support.<br />
* The proprietary nvidia drivers, which offer good 3d performance and powersaving. See [[NVIDIA]] for more information. Even if you plan on using the proprietary drivers, it's recommended to start with nouveau and then switch to the binary driver, because nouveau will almost always work out-of-the-box, while nvidia will require configuration and likely some troubleshooting.<br />
<br />
The open-source nouveau driver should be good enough for most users and is recommended:<br />
<br />
# pacman -S xf86-video-nouveau<br />
<br />
For 3D support (highly experimental):<br />
<br />
# pacman -S nouveau-dri<br />
<br />
Create the file {{Filename|/etc/X11/xorg.conf.d/20-nouveau.conf}}, and input the following contents:<br />
<br />
Section "Device"<br />
Identifier "n"<br />
Driver "nouveau"<br />
EndSection<br />
<br />
This is required to ensure that nouveau driver is loaded. Xorg is not yet smart enough to do this by itself.<br />
<br />
{{Tip|For advanced instructions, see [[Nouveau]].}}<br />
<br />
=====ATI Graphics Cards=====<br />
ATI owners have two options for drivers (in addition to the vesa driver):<br />
* The open source '''''radeon''''' driver provided by the '''xf86-video-ati''' package. It fully supports Radeon chipsets up to X1950 (latest R500 chipsets). Cards up to the 9200 series are fully supported, stable, and provide full 2D and 3D acceleration. Cards from 9500 to HD4000 feature full 2D acceleration, and stable/partly implemented 3D acceleration, but lack certain features provided by the proprietary driver; power management is under development and in an advanced stage, but not on par with catalyst. HD5000 support is currently a work in progress. Supports KMS and HDMI with audio output since kernel 2.6.33. [http://wiki.x.org/wiki/RadeonFeature Feature Matrix.]<br />
* The proprietary '''''fglrx''''' driver provided by the [http://aur.archlinux.org/packages.php?O=0&K=catalyst&do_Search=Go catalyst] package located in the [[AUR]]. It supports only newer devices (HD2xxx and newer). It was once a package offered by Arch in the <code>extra</code> repository, but as of March 2009, official support has been dropped because of dissatisfaction with the quality and speed of development of the proprietary driver. See [[ATI Catalyst]] for more information.<br />
<br />
The open-source driver is the recommended choice:<br />
<br />
Install the '''''radeon''''' ATI Driver:<br />
# pacman -S xf86-video-ati<br />
<br />
{{Tip|For advanced instructions, see [[ATI]].}}<br />
<br />
====C: Install input drivers====<br />
<br />
Udev should be capable of detecting your hardware without problems and evdev (xf86-input-evdev) is the modern, hotplugging input driver for almost all devices so in most cases, installing input drivers is not needed. At this point, evdev has already been installed as a dependency of Xorg.<br />
<br />
If evdev does not support your device, install the needed driver from the xorg-input-drivers group.<br />
<br />
For a complete list of available input drivers, invoke a pacman search:<br />
# pacman -Ss xf86-input | less<br />
<br />
{{Note|You only need xf86-input-keyboard or xf86-input-mouse if you plan on disabling hotplugging, otherwise, evdev will act as the input driver.}}<br />
<br />
Laptop users (or users with a touchscreen) will also need the synaptics package to allow X to configure the touchpad/touchscreen:<br />
# pacman -S xf86-input-synaptics<br />
{{Tip|For instructions on fine tuning or troubleshooting touchpad settings, see the [[Touchpad Synaptics]] article.}}<br />
<br />
===Step 2: Configure X (Optional)===<br />
<br />
{{Warning|Proprietary drivers usually require a reboot after installation along with configuration. See [[NVIDIA]] or [[ATI Catalyst]] for details.}}<br />
<br />
X.Org X Server features auto-configuration. Therefore, it can function without an xorg.conf.<br />
<br />
{{Note|If you want to configure something like horizontal/vertical refresh or monitor dimensions if your monitor's EDID is incorrect, see [[Xorg]].}}<br />
<br />
The current arrangement of configuration files is found in /etc/X11. Within that directory, there is the subdirectory /etc/X11/xorg.conf.d. This is the directory which contains the default configuration files for the X server. These are supplied by your distribution, automatically-created or may also be added to for your personal configuration and editing. However, it is also possible to simply create and edit {{filename|/etc/X11/xorg.conf}}, since that file is read last after those in the /xorg.conf.d directory.<br />
<br />
====Non-US keyboard====<br />
<br />
If you do not use a standard US keyboard you need to set the keyboard layout in {{Filename|/etc/X11/xorg.conf.d/10-evdev.conf}}:<br />
<br />
Section "InputClass"<br />
Identifier "evdev keyboard catchall"<br />
MatchIsKeyboard "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Driver "evdev"<br />
'''Option "XkbLayout" "be"'''<br />
EndSection<br />
<br />
{{Note|The '''XkbLayout''' key may differ from the keymap code you used with the km or loadkeys command. For instance, the uk layout corresponds to the key: '''gb'''.}}<br />
<br />
===Step 3: Starting a basic graphical environment===<br />
<br />
This section will explain how to start the very basic graphical environment included with in the xorg group. This uses the simple default X window manager, twm.<br />
<br />
The default X environment is rather bare, and step 5 will deal with installing a desktop environment or window manager of your choice to supplement X.<br />
<br />
If you just installed Xorg, there is an empty .xinitrc file in your $HOME that you need to either delete or edit in order for X to start properly. If you do not do this X will show a blank screen with what appears to be no errors in your Xorg.0.log. Simply deleting it will get it running with a default X environment.<br />
<br />
$ rm ~/.xinitrc<br />
<br />
====Message bus====<br />
<br />
dbus is likely required for many of your applications to work properly, if you know you don't need it, skip this section.<br />
<br />
=====Installation=====<br />
<br />
Install dbus:<br />
<br />
# pacman -S dbus<br />
<br />
=====Starting the daemon=====<br />
<br />
You should add dbus to your DAEMONS array in {{filename|/etc/rc.conf}}:<br />
<br />
DAEMONS=(syslog-ng '''dbus''' network crond)<br />
<br />
If you need to start dbus without rebooting, run<br />
<br />
# /etc/rc.d/dbus start<br />
<br />
====Starting X====<br />
<br />
{{Note|The Ctrl-Alt-Backspace shortcut traditionally used to kill X has been deprecated and will not work to exit out of this test. You can enable Ctrl-Alt-Backspace by editing xorg.conf, as described at [[Xorg#Ctrl-Alt-Backspace doesn't work|here]].}}<br />
<br />
Finally, start Xorg:<br />
$ startx<br />
or<br />
$ xinit -- /usr/bin/X -nolisten tcp<br />
<br />
If the screen goes black, you may still attempt to switch to a different virtual console (CTRL-Alt-F2, for example), and login blindly as root, followed by <Enter>, followed by root's password followed by <Enter>.<br />
<br />
You can attempt to kill the X server with <code>/usr/bin/pkill</code> (note the capital letter '''X'''):<br />
# pkill X<br />
<br />
If pkill does not work, reboot blindly with:<br />
# reboot<br />
or<br />
# init 6<br />
<br />
====In case of errors====<br />
If a problem occurs, then look for errors in {{Filename|/var/log/Xorg.0.log}}. Be on the lookout for any lines beginning with {{Codeline|(EE)}} which represent errors, and also {{Codeline|(WW)}} which are warnings that could indicate other issues.<br />
<br />
$ grep EE /var/log/Xorg.0.log<br />
<br />
Errors may also be searched for in the console output of the virtual console from which '''X''' was started.<br />
<br />
See the [[Xorg]] article for detailed instructions and troubleshooting.<br />
<br />
=====Need Help?=====<br />
<br />
If you are still having trouble after consulting the [[Xorg]] article and need assistance via the Arch forums, be sure to install and use wgetpaste:<br />
<br />
# pacman -S wgetpaste<br />
Use wgetpaste and provide links for the following files when asking for help in your forum post:<br />
* ~/.xinitrc<br />
* /etc/X11/xorg.conf<br />
* /var/log/Xorg.0.log<br />
* /var/log/Xorg.0.log.old<br />
Use wgetpaste like so:<br />
$ wgetpaste </path/to/file><br />
Post the corresponding links given within your forum post. Be sure to provide appropriate hardware and driver information as well.<br />
{{Warning| '''''It is very important to provide detail when troubleshooting X. Please provide all pertinent information as detailed above when asking for assistance on the Arch forums. '''''}}<br />
<br />
===Step 4: 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 is a set of high quality, general-purpose fonts.<br />
<br />
Install with:<br />
# pacman -S ttf-dejavu<br />
<br />
Refer to [[Font Configuration]] for how to configure font rendering and [[Fonts]] for font suggestions and installation instructions.<br />
<br />
===Step 5: Choose and install a graphical interface===<br />
<br />
The X Window System provides the basic framework for building a graphical user interface (GUI).<br />
<br />
A Window Manager controls the placement and appearance of application windows in conjunction with the X Window System.<br />
<br />
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.<br />
<br />
Alternatively, you can build your own DE by using a WM and the applications of your choice.<br />
<br />
{{Note|Unlike lots of other distributions, Arch won't decide what graphical environment you want to use. Choosing your DE or WM is a very subjective and personal decision. Choose the best environment for ''your'' needs. It's worth trying out a bunch of the environments listed here before you make your choice as pacman can completely remove anything you install.}}<br />
<br />
After installing a graphical interface, you'll probably want to continue with [[General Recommendations]] for post-installation instructions.<br />
<br />
====Desktop Environments====<br />
<br />
See [[Desktop Environment#Desktop environments|Desktop environments]] for more information.<br />
<br />
====Window Managers====<br />
<br />
See [[Window Manager#Window managers|Window managers]] for more information.<br />
<br />
===Methods for starting your Graphical Environment===<br />
<br />
====A: Manually====<br />
You might prefer to start X manually from your terminal rather than booting straight into the desktop (if not, skip to [[Beginner's Guide#B: Automatically|B: Automatically]]). There are three methods for starting X manually. Choose the one that suits you best:<br />
<br />
=====Method 1: DE-specific commands=====<br />
For some users, this method might be the easiest since you need only enter a command without any configuring.<br />
Simply use a command to launch your WM/DE.<br />
You may always start your desktop environment with '''xinit''' or '''startx''', followed by the path to your DE's script:<br />
<br />
$ xinit /usr/bin/gnome-session<br />
or<br />
$ startx /usr/bin/startkde<br />
<br />
from the shell prompt. Note that such a command does not finish until you logout of the DE.<br />
{{Note|If you do '''xinit gnome-session''' instead of '''xinit /usr/bin/gnome-session''', then you will have problems on your desktop. Always include the complete path (/usr/bin/)}}<br />
<br />
Optionally, you can make an [[Bashrc#Aliases|alias]] in /etc/bash.bashrc so you don't have to type the whole command.<br />
...<br />
alias gnome="xinit /usr/bin/gnome-session"<br />
...<br />
<br />
Alternatively, if you wish to launch a Display Manager (AKA login manager) rather than go directly into your desktop, you can use the command for your installed Display Manager. For example, for gnome:<br />
$ gdm<br />
or KDE:<br />
$ kdm<br />
etc.<br />
<br />
=====Method 2: using runlevels=====<br />
By default, Linux is set up to have different [[runlevels]]. Arch boots into runlevel 3 by default. Runlevel 5 is typically used in Linux for loading X server.<br />
Edit the file /etc/inittab. In the last section at the bottom of the file, uncomment the appropriate line for your desktop environment's display manager. For example, for gnome it would look like this:<br />
# Example lines for starting a login manager<br />
#x:5:respawn:/usr/bin/xdm -nodaemon<br />
x:5:respawn:/usr/sbin/gdm -nodaemon<br />
#x:5:respawn:/usr/bin/kdm -nodaemon<br />
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1<br />
<br />
Now, simply start your desktop environment, as root, with<br />
# init 5<br />
or, as a normal user, with<br />
$ sudo init 5<br />
<br />
=====Method 3: using .xinitrc=====<br />
This method involves the most configuring.<br />
<br />
First we need to configure ~/.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 />
<br />
{{Note | '''[[.xinitrc]]''' is a so-called 'dot' (.) file. Files in a *nix 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 />
The '''startx''' and '''xinit''' commands 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 />
<br />
# su - ''yourusername''<br />
<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 />
{{Note | This template file '''[[.xinitrc]]''' is available in the /etc/skel directory when the package '''xorg-xinit''' is installed.}}<br />
<br />
* Sample .xinitrc 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 uncomment the line that corresponds to your Desktop Environment. For example, if you use Gnome, it will look something like this:<br />
<br />
<pre><br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
<br />
exec gnome-session<br />
# exec startkde<br />
# exec startxfce4<br />
# exec wmaker<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
# exec openbox-session<br />
# ...or the Window Manager of your choice<br />
# exec xterm<br />
</pre><br />
For KDE uncomment:<br />
exec startkde<br />
For fluxbox:<br />
exec fluxbox<br />
etc...<br />
<br />
{{Note | ''Be sure to have only '''one''' uncommented '''exec''' line in ~/.xinitrc'' for now.}}<br />
<br />
Now we're ready to launch X. Start '''X''' as a '''normal, non-root''' user, with:<br />
<br />
$ startx<br />
or<br />
$ xinit<br />
<br />
Your desktop should open up now. You can test your keyboard and its layout in it. Try moving your mouse around and enjoy the view.<br />
<br />
If trouble with automounting is experienced, try using the following command in ~/.xinitrc instead. (Replace "startxfce4" with the command that is appropriate for your window manager/DE.)<br />
exec ck-launch-session startxfce4<br />
This will ensure the various environment variables are set correctly by starting a clean consolekit session. ConsoleKit is a framework for keeping track of the various users, sessions, and seats present on a system. It provides a mechanism for software to react to changes of any of these items or of any of the metadata associated with them. It works in conjunction with dbus, and other tools.<br />
<br />
====B: Automatically====<br />
Most users might prefer to have their desktop start automatically during boot instead of starting X manually. There are two methods for starting X automatically. Choose the one that suits you best:<br />
<br />
=====Method 1: using runlevels=====<br />
This method expands on Method 2 from the section above on starting X manually.<br />
<br />
By default, Linux is set up to have different [[runlevels]]. Arch boots into runlevel 3 by default. Runlevel 5 is typically used for loading X server.<br />
Edit the file /etc/inittab.<br />
In the first section, uncomment '''id:5:initdefault:''' so it looks like this:<br />
## Only one of the following two lines can be uncommented!<br />
# Boot to console<br />
#id:3:initdefault:<br />
# Boot to X11<br />
id:5:initdefault:<br />
This tells Arch to boot to runlevel 5 when you start your computer.<br />
<br />
In the last section at the bottom of the file, uncomment the appropriate line for your desktop environment's display manager. For example, for gnome it would look like this:<br />
# Example lines for starting a login manager<br />
#x:5:respawn:/usr/bin/xdm -nodaemon<br />
x:5:respawn:/usr/sbin/gdm -nodaemon<br />
#x:5:respawn:/usr/bin/kdm -nodaemon<br />
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1<br />
<br />
=====Method 2: using a daemon=====<br />
Simply add your display manager to your daemons array in /etc/rc.conf. For example, it would look like this for gnome:<br />
DAEMONS=(syslog-ng dbus network '''gdm''' ...)<br />
You might try backgrounding your display manager so that other daemons continue loading while the display manager loads:<br />
DAEMONS=(syslog-ng dbus hal network '''@kdm''' ...)<br />
<br />
==Appendix==<br />
For a list of [[Common Applications]] and [[Lightweight Applications]], visit their respective articles.<br />
<br />
See [[General Recommendations]] for post-installation tutorials like setting up CPU frequency scaling or font rendering.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Beginners%27_guide_old&diff=125625
Beginners' guide old
2010-12-20T07:40:42Z
<p>Cantabile: /* Check the Integrity of the Downloaded File */ no need to run sha1sum from a root shell</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]] [[Category:About Arch (English)]]<br />
[[Category:HOWTOs (English)]] [[Category:Website Resources]]<br />
{{i18n|Beginners' Guide}}<br />
[[de:Anleitung für Einsteiger]]<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|Related}}<br />
{{Article summary wiki|:Category:Accessibility (English)}}<br />
{{Article summary wiki|Official Arch Linux Install Guide}}<br />
{{Article summary wiki|General Recommendations}}<br />
{{Article summary end}}<br />
==Preface==<br />
=====Introduction=====<br />
Welcome. This document will guide you through the process of installing and configuring [[Arch Linux]]; a simple, lightweight GNU/Linux distribution targeted at competent users. 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 />
* [http://www.archlinux.org/packages/?q= All packages] compiled for i686 and x86_64 architectures<br />
* [[Arch Boot Process|BSD style]] init scripts, featuring one centralized configuration file<br />
* [[mkinitcpio]]: A simple and dynamic initramfs creator<br />
* [[Pacman]] package manager is lightweight and agile, with a very modest memory footprint<br />
* The [[Arch Build System]]: A ports-like package building system, providing a simple framework to create installable Arch packages from source<br />
* The [[Arch User Repository]]: offering many thousands of user contributed build scripts and the opportunity to share your own<br />
<br />
=====License=====<br />
<br />
Arch Linux, pacman, documentation, and scripts are copyright<br />
©2002-2007 by Judd Vinet, ©2007-2010 by Aaron Griffin and are licensed under the GNU General Public License Version 2.<br />
<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 as you consider simplicity:'''<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..The height of cultivation always runs to simplicity.&quot;'' - Bruce Lee<br />
<br />
=====About This Guide=====<br />
<br />
The Arch wiki is an excellent resource and should be consulted for issues [[Main Page|first]]. The IRC room (at freenode #archlinux), and the [http://bbs.archlinux.org/ forums] are also available if the answer cannot be found elsewhere.<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 <u>before</u> carrying out the tasks contained.}}<br />
<br />
The guide is divided into 5 main components:<br />
<br />
*[[#Part I: Install the Base System|Part I: Install the Base system]]<br />
*[[#Part II: Update|Part II: Update]]<br />
*[[#Part III: Add a user|Part III: Add a user]]<br />
*[[#Part IV: Sound|Part IV: Sound]]<br />
*[[#Part V: Graphical User Interface|Part V: Graphical User Interface]]<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 installation media from [http://archlinux.org/download/ here]. The latest version is 2010.05<br />
<br />
* Both the Core and the Netinstall images 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 utilities), the Linux kernel, and a few extra libraries and modules.''<br />
* Core images facilitate both installing from CD and Net.<br />
* Netinstall images are smaller and provide no packages themselves; the entire system is retrieved via internet.<br />
* [[Arch64_FAQ|The Arch64 FAQ]] can help you choose between the 32-, 64-bit and dual versions.<br />
* Don't forget to download the checksum txt files along with your chosen ISO.<br />
<br />
====Check the Integrity of the Downloaded File====<br />
Open a terminal, change to the directory where the downloaded files have been placed, and type at the CLI (Command Line Interface):<br />
$ sha1sum --check name_of_checksum_file.txt name_of_selected_iso_file.iso<br />
This should give you an "OK" for the one you have. (Simply ignore other lines.) If not, download all files again.<br />
The md5sum check works the same way.<br />
<br />
====Install from an Existing GNU/Linux Distro====<br />
Arch is flexible enough to be installed to another partition ''from within'' an existing distro or Live CD. See [[Install from Existing Linux|this wiki article]] for steps to do this. This can be useful particularly if you plan to install Arch via vnc or ssh remotely.<br />
<br />
====CD installer====<br />
Burn the .iso image file to a CD or DVD media with your preferred CD/DVD burner drive and software, and continue with [[#Step 2: Boot Arch Linux Installer | Step 2: Boot Arch Linux Installer]]<br />
{{Note| The quality of optical drives, as well as the CD media itself, vary greatly. 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 />
====Flash Memory Device or USB stick====<br />
<br />
See [[Install_from_a_USB_flash_drive|Install from a USB flash drive]] for more detailed instructions.<br />
<br />
This method will work for any type of flash media from which your BIOS will let you boot, be it a card reader or USB port.<br />
<br />
{{Warning|This procedure will irrevocably destroy all data on your media! Also, be very careful where you send the image iso, as dd will obediently write to any target you point to, even if that is your hard disk.}}<br />
<br />
'''*nix Method:'''<br />
<br />
Insert an empty or expendable flash device, determine its path, and write the .iso to the device with the <code>/bin/dd</code> program:<br />
dd if=archlinux-2010.05-''{core|netinstall}''-''{i686|x86_64|dual}''.iso of=/dev/sd''x''<br />
where <code>if=</code> is the path to the img file and <code>of=</code> is your flash device. Make sure to use {{Filename|/dev/sd'''x'''}} and not {{Filename|/dev/sd'''x1'''}}. You will need a flash memory device large enough to accomodate the image which, at the time of this writing is 381MB.<br />
<br />
'''Check md5sum:'''<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 [ftp://ftp.archlinux.org/iso/2010.05/md5sums.txt 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. A typical run will look like this: <br />
{{Command|<nowiki>[sudo] dd if=archlinux-2010.05-core-i686.iso of=/dev/sdc</nowiki>|<nowiki> 744973+0 records in<br />
744973+0 records out<br />
381426176 bytes (381 MB) copied, 106.611 s, 3.6 MB/s<br />
</nowiki>}}<br />
<br />
{{Command|<nowiki>[sudo] dd if=/dev/sdc count=744973 status=noxfer | md5sum</nowiki>| 4850d533ddd343b80507543536258229 -<br />
744973+0 records in<br />
744973+0 records out}}<br />
<br />
Continue with [[#Step 2: Boot Arch Linux Installer | Step 2: Boot Arch Linux Installer]]<br />
<br />
'''Microsoft Windows Method:'''<br />
<br />
Download Disk Imager from https://launchpad.net/win32-image-writer/+download. Insert flash media. Start the Disk Imager and select the image file (Disk Imager accepts only *.IMG files, so you'll have to put "*.iso" in file open dialog to select Arch snapshot). Select the Drive letter associated with the flash drive. Click "write".<br />
<br />
There are also other solutions to [[Install_from_a_USB_flash_drive#On_Windows|writing bootable ISO images to USB sticks]]. If you have problems with USB sticks disconnecting, try using different USB port and/or cable.<br />
<br />
Continue with [[#Step 2: Boot Arch Linux Installer | Step 2: Boot Arch Linux Installer]]<br />
<br />
===Step 2: Boot Arch Linux Installer===<br />
{{Tip|The memory requirement for a basic install is 64 MB of RAM.}}<br />
<br />
{{Tip|During the process, the automatic screen blanker may come on. If so, one can press the Alt key to safely obtain the normal display.}}<br />
<br />
====Boot from the Media====<br />
Insert the CD or Flash media you prepared, 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 (Power On Self-Test) phase.<br />
<br />
'''Main Menu:''' The main menu should be displayed at this point. Select the preferred choice by using the arrow keys to highlight your choice, and then by pressing Enter.<br />
<br />
Menus vary on different iso's. The 2010.05 Netinstall menu has "Boot Arch Linux (i686)", "Boot Arch Linux (x86-64)", "Boot Existing OS", "Run Memtest86+ (RAM test)", "Run x86test (CPU test)", and "Reboot"<br />
<br />
For Netinstall, choose the first or second item according to your CPU type. For Core, usually the first item, Boot Archlive, is the preferred selection. However, choose Boot Archlive [legacy IDE] if you have trouble with libata/PATA, or have no SATA (Serial ATA) drives.<br />
<br />
It is strongly recommended that you run the memory test; just to be sure. The CPU test can also provide detailed and useful specs. It may be wise to remember or record any system details of which you were unaware.<br />
<br />
====OS System Start====<br />
The system will now load and present a login prompt. Login as 'root', without the quotes.<br />
<br />
If using an Intel video chipset and the screen goes blank during the boot process, the problem is likely an issue with kernel mode setting. A possible workaround may be achieved by rebooting and pressing <Tab> at the GRUB menu to enter kernel options. At the end of the kernel line, add a space and then:<br />
i915.modeset=0<br />
<br />
When done making any changes to any menu command, simply press "Enter" to boot with that setup.<br />
<br />
See [[Intel| the Intel article]] for more information.<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 conveniently available right on the live system! To access it, change to tty2 (virtual console #2) with <ALT>+F2, log in as "root" and then invoke <code>/usr/bin/less</code> by typing in the following at the # prompt:<br />
# less /usr/share/aif/docs/official_installation_guide_en<br />
<code>less</code> will allow you to page through the document.<br />
<br />
Change back to tty1 with <ALT>+F1 to follow the rest of the install process. (Change back to tty2 at any time if you need to reference the Official Guide as you progress through the installation process.)<br />
<br />
{{tip|Please note that the official guide only covers installation and configuration of the base system. Once that is installed, it is strongly recommended that you come back here to the wiki to find out more about post-installation considerations and other related issues.}}<br />
<br />
===Step 3: Start the Installation===<br />
As root, run the installer script from tty1:<br />
# /arch/setup<br />
You should next see the displayed Arch Linux Installation Framework screen.<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. A good place to check for relative speed of source repositories is [https://www.archlinux.de/?page=MirrorStatus Mirror Status]. Choose one that matches one from the installer list.<br />
<br />
* If you chose the CORE installer, continue below with [[#B: Set Clock|B: Set Clock]].<br />
* Netinstall 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 tty3. (Select OK to continue.)<br />
<br />
====Configure Network (Netinstall)====<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 />
=====(A)DSL Quickstart for the Live Environment=====<br />
(If you have a modem or router in bridge mode to connect to your ISP)<br />
<br />
Switch to another virtual console (<Alt> + F2), login as root and invoke<br />
# pppoe-setup<br />
If everything is well configured in the end you can connect to your ISP with<br />
# pppoe-start<br />
<br />
Return to first virtual console with <ALT>+F1. Continue with [[#B: Set Clock|B: Set Clock]]<br />
<br />
=====Wireless Quickstart For the Live Environment=====<br />
(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. Note that the following quickstart procedure ''executed at this point in the installation'' will initialize your wireless hardware for use ''in the live environment''. These steps (or some other form of wireless management) must be repeated from the actual installed system after booting into it.<br />
<br />
Also note that these steps are optional if wireless connectivity is unnecessary at this point in the installation; wireless functionality may always be established later.<br />
<br />
;Does the Wireless Chipset require Firmware?<br />
A small percentage of wireless chipsets also require firmware, in addition to a corresponding driver. If the wireless chipset requires firmware, you are likely to receive this error:<br />
<br />
{{Command|ifconfig wlan0 up|SIOCSIFFLAGS: No such file or directory|prompt=#}}<br />
<br />
If unsure, invoke <code>/usr/bin/dmesg</code> to query the kernel log for a firmware request from the wireless chipset.<br />
<br />
Example from an Intel chipset which requires and has requested firmware from the kernel at boot:<br />
<br />
{{Command|<nowiki>dmesg | grep firmware</nowiki>|firmware: requesting iwlwifi-5000-1.ucode}}<br />
<br />
If there is no output, it may be concluded that the system's wireless chipset does not require firmware.<br />
<br />
{{Note | '''Wireless chipset firmware packages (for cards which require them) are pre-installed under /lib/firmware in the live environment, (on CD/USB stick) ''but must be explicitly installed to your actual system to provide wireless functionality after you reboot into it!'' Package 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 installed system.<br />
<br />
The basic procedure will be:<br />
* Switch to a free virtual console, e.g.: <ALT>+F3<br />
* Login as root<br />
* (Optional) Identify the wireless interface:<br />
# lspci | grep -i net<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 />
<br />
Example: <br />
{{Command|iwconfig|<nowiki> lo no wireless extensions.<br />
eth0 no wireless extensions.<br />
wlan0 unassociated ESSID:""<br />
Mode:Managed Channel=0 Access Point: Not-Associated<br />
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0<br />
Retry limit:7 RTS thr:off Fragment thr:off<br />
Power Management:off<br />
Link Quality:0 Signal level:0 Noise level:0<br />
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0<br />
Tx excessive retries:0 Invalid misc:0 Missed beacon:0<br />
</nowiki>|prompt=#}}<br />
<code>wlan0</code> is the available wireless interface in the example.<br />
* Bring the interface up with <code>/sbin/ifconfig <interface> up</code>.<br />
An example using the wlan0 interface:<br />
# ifconfig wlan0 up<br />
(Remember, your interface may be named something else, depending on your module (driver) and chipset: wlan0, eth1, etc.)<br />
<br />
* If the essid has been forgotten or is unknown, use <code>/sbin/iwlist <interface> scan</code> to scan for nearby networks.<br />
# iwlist wlan0 scan<br />
<br />
* Associate your wireless device with the access point you want to use. Depending on the encryption (none, WEP, or WPA), the procedure may differ. You need to know the name of the chosen wireless network (ESSID), e.g. 'linksys' in the following examples:<br />
* An example using a ''non-encrypted'' network:<br />
# iwconfig wlan0 essid &quot;linksys&quot;<br />
* An example using ''WEP and a hexadecimal key'':<br />
# iwconfig wlan0 essid &quot;linksys&quot; key 0241baf34c<br />
* An example using ''WEP and an ASCII passphrase'':<br />
# iwconfig wlan0 essid "linksys" key s:pass1<br />
* Using ''WPA'' requires extra steps:<br />
<br />
Step 1: The default /etc/wpa_supplicant.conf is rather obtuse. For the purpose of simplifying, rename the default wpa_supplicant.conf file:<br />
# mv /etc/wpa_supplicant.conf /etc/wpa_supplicant.conf.original<br />
<br />
Step 2: Using wpa_passphrase, provide your wireless network name and wpa key to be encrypted and written to /etc/wpa_supplicant.conf<br />
<br />
The following example encrypts the key 'my_secret_passkey' of the 'linksys' wireless network, generates a new configuration file (/etc/wpa_supplicant.conf), and subsequently redirects the encrypted key, writing it to the file:<br />
# wpa_passphrase linksys "my_secret_passkey" > /etc/wpa_supplicant.conf<br />
(Substitute the actual SSID and passkey)<br />
<br />
Step 3: Using the wpa_supplicant command, attempt to associate to the wireless network specified in /etc/wpa_supplicant.conf and the now encrypted key contained therein:<br />
# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf<br />
Check [[WPA_Supplicant|WPA supplicant]] for more information and troubleshooting.<br />
<br />
{{Note | The network connection process may be automated later by using the default Arch network daemon, [[netcfg]], [[wicd]], or another network manager of your choice.}}<br />
<br />
'''Verify Association and IP routing'''<br />
<br />
* After utilizing the appropriate association method outlined above, wait a few moments and confirm you have successfully associated to the access point before continuing. e.g.:<br />
# iwconfig wlan0<br />
Output should indicate the wireless network is associated with the interface. Again, your interface may be named something besides wlan0.<br />
* Request an IP address with <code>/sbin/dhcpcd <interface> </code>. e.g.:<br />
# dhcpcd wlan0<br />
* Lastly, ensure you can route using <code>/bin/ping</code>:<br />
# ping -c 3 www.google.com<br />
<br />
You should have a working network connection. For troubleshooting, check the detailed [[Wireless_Setup|Wireless Setup]] page.<br />
<br />
Return to tty1 with <ALT>+F1. Continue with [[#B: Set Clock|B: Set Clock]]<br />
<br />
===B: Set Clock===<br />
* UTC - Choose UTC if running only <tt>UNIX</tt>-like operating system(s).<br />
<br />
* localtime - Choose local if multi-booting with a Microsoft Windows OS.<br />
<br />
===C: 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 />
{{Warning|Choosing the Cancel button in the Prepare Hard Drive menu will not cancel the operations you have selected - see {{Bug|19805}}. If you must cancel the installation from this menu, press <Control>+C to exit the installer completely and immediately.}}<br />
<br />
{{Note|Partitioning may be performed before initiating the Arch installation if desired, by utilizing [http://gparted.sourceforge.net/download.php GParted] or other available tools. If the installation drive has already been partitioned to the required specifications, continue with [[#Set Filesystem Mountpoints| Set Filesystem Mountpoints]]}}<br />
<br />
Verify 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) to utilize for the 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 (Erases an ENTIRE hard drive and sets up partitions)<br />
Auto-Prepare divides the disk into the following configuration:<br />
<br />
* ext2 /boot partition, default size 32MB. ''You will be prompted to modify the size to your requirement.''<br />
* swap partition, default size 256MB. ''You will be prompted to modify the size to your requirement.''<br />
* A Separate / and /home partition, (sizes can also be specified). Available filesystems include ext2, ext3, ext4, reiserfs, xfs and jfs, but note that ''both / and /home shall share the same fs type'' if choosing the Auto Prepare option.<br />
<br />
Be warned that Auto-prepare will completely erase the chosen hard drive. Read the <font color="red">warning</font> presented by the installer very carefully, and make sure the correct device is about to be partitioned.<br />
<br />
* Option 2: Manually Partition Hard Drives (with cfdisk)- recommended.<br />
<br />
This option will allow for the most robust and customized partitioning solution for your personal needs.<br />
<br />
* Option 3: Manually Configure block devices, filesystems and mountpoints<br />
If this is selected, the system will list what filesystems and mountpoints it has found and ask you if you wish to use these. If selecting "Yes", you will be given a choice to select the desired method of identification, ie. by dev, label or uuid.<br />
<br />
* Option 4: Rollback last filesystem changes<br />
<br />
''At this point, more advanced GNU/Linux users who are familiar and comfortable with manually partitioning may wish to skip down to '''[[#D: Select Packages|D: Select Packages]]''' below.''<br />
<br />
{{Note|If you are installing to 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 are 3 types of disk partitions:<br />
#Primary<br />
#Extended<br />
#Logical<br />
'''Primary''' partitions can be bootable, and are limited to 4 partitions per disk or raid volume. If a partitioning scheme requires more than 4 partitions, an '''extended''' partition which will contain '''logical''' partitions will be required.<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 through sda3 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 the 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. If the installation machine provides gratuitous amounts of RAM (more than 1024 MB) it may be possible to completely forget a swap partition altogether, since the option to create a [[HOW TO: Create swap file|swap file]] is always available later. A 1 GB swap partition will be used in this example.<br />
{{Note|If using suspend-to-disk, (hibernate) a swap partition at least '''equal''' in size to the amount of physical RAM is required. 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. If you would like to dual boot Arch Linux and a Windows operating system please see [[Windows and Arch Dual Boot]].<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. Therefore, certain directories under / are not themselves candidates for separate partitions. (See warning below).''<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. /boot is essential for booting, but is unique in that it may still be kept on its own separate partition (if required).''<br />
<br />
'''/home''' ''Provides subdirectories, each named for a system user, for miscellaneous personal data storage as well as user-specific configuration files for applications.''<br />
<br />
'''/usr''' ''While root is the primary filesystem, /usr is the secondary hierarchy for all system users' data, including the majority of multi-user utilities and applications. /usr is shareable, read-only data. This means that /usr shall be shareable between various hosts and must not be written to, except in the case of system update/upgrade. Any information that is host-specific or varies with time is stored elsewhere.''<br />
<br />
'''/tmp''' ''directory for programs that require temporary files such as '.lck' files, which can be used to prevent multiple instances of their respective program until a task is completed, at which point the '.lck' file will be removed. Programs must not assume that any files or directories in /tmp are preserved between invocations of the program and files and directories located under /tmp will typically be deleted whenever the system is booted.''<br />
<br />
'''/var''' ''contains variable data; spool directories and files, administrative and logging data, pacman's cache, the ABS tree, etc. /var exists in order to make it possible to mount /usr as read-only. Everything that historically went into /usr that is written to during system operation (as opposed to installation and software maintenance) must reside under /var.''<br />
{{Warning | Besides /boot, directories essential for booting are: ''''''/bin', '/etc', '/lib', 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 />
{{Note | /var contains many small files. This should be taken into consideration when choosing a filesystem type for it, (if creating its own separate partition).}}<br />
<br />
=====How big should my partitions be?=====<br />
This question is best answered based upon individual needs.<br />
You may wish to simply create '''one partition for root and one partition for swap or only one root partition without swap''' or refer to the following examples and consider these guidelines to provide a frame of reference:<br />
* The root filesystem (/) in the example will contain the /usr directory, which can become moderately large, depending upon how much software is installed. 15-20 GB should be sufficient for most users.<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. If you are using an SSD, you may wish to locate your /var on an HDD and keep the / and /home partitions on your SSD to avoid needless read/writes to the SSD. 8-12 Gigs on a desktop system should be sufficient for /var, depending largely upon how much software you intend to install. Servers tend to have relatively larger /var filesystems.<br />
<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. Remember that if you chose to reinstall Arch, all the data on your /home partition will be untouched (so long as you have a separate /home partition).<br />
<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, ~10GB /var, 1GB swap, and a /home containing the remaining disk space.'''''<br />
<br />
=====Create Partitions with 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 10256 #/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 />
{{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 />
Specify each partition and corresponding mountpoint to your requirements. (Recall that partitions end in a number. Therefore, '''sda''' is not itself a partition, but rather, signifies an entire drive)<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. [[Wikipedia:ext2|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. [[Wikipedia:ext3|ext3]] ''Third Extended Filesystem''- Essentially the ext2 system, but with journaling support. ext3 is backward compatible with ext2. Extremely stable, mature, and by far the most widely used, supported and developed GNU/Linux FS.<br />
<br />
3. [[Wikipedia:ext4|ext4]] ''Fourth Extended Filesystem''- Backward compatible with ext2 and ext3. Introduces support for volumes with sizes up to 1 exabyte and files with sizes up to 16 terabytes. Increases the 32,000 subdirectory limit in ext3 to 64,000. Offers online defragmentation ability.<br />
<br />
4. [[Wikipedia:ReiserFS|ReiserFS]] (V3)- Hans Reiser's high-performance journaling FS uses a very interesting method of data throughput based on an unconventional and creative algorithm. ReiserFS is touted as very fast, especially when dealing with many small files. ReiserFS is fast at formatting, yet comparatively slow at mounting. Quite mature and stable. ReiserFS is not actively developed at this time (Reiser4 is the new Reiser filesystem). Generally regarded as a good choice for /var/.<br />
<br />
5. [[Wikipedia:JFS (file system)|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 GNU/Linux. JFS currently uses the least CPU resources of any GNU/Linux filesystem. Very fast at formatting, mounting and fsck's, and very good all-around performance, especially in conjunction with the deadline I/O scheduler. (See [[JFS]].) Not as widely supported as ext or ReiserFS, but very mature and stable.<br />
<br />
6. [[Wikipedia:XFS|XFS]] - Another early journaling filesystem originally developed by Silicon Graphics for the IRIX OS and ported to GNU/Linux. XFS offers very fast throughput on large files and large filesystems. Very fast at formatting and mounting. Generally benchmarked as slower with many small files, in comparison to other filesystems. XFS is very mature and offers online defragmentation ability.<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, utilize [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 are committed to the file system to avoid metadata corruption in the event of a crash. Note that not all journaling techniques are alike; specifically, only ext3 and ext4 offer ''data-mode journaling'', (though, not by default), which journals ''both'' data ''and'' meta-data (but with a significant speed penalty). The others only offer ''ordered-mode journaling'', which journals meta-data only. While all will return your filesystem to a valid state after recovering from a crash, ''data-mode journaling'' offers the greatest protection against file system corruption and data loss but can suffer from performance degradation, as all data is written twice (first to the journal, then to the disk). Depending upon how important your data is, this may be a consideration in choosing your filesystem type.<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.<br />
{{Box Note |If you have not created and do not need a separate /boot partition, you may safely ignore the warning that it does not exist.}} Return to the main menu.<br />
<br />
===D: Select Packages===<br />
<br />
*Core ISO: Choose CD as source and select the appropriate CD drive if more than one exist on the installation machine.<br />
*Netinstall: Select an FTP/HTTP [https://www.archlinux.de/?page=MirrorStatus mirror]. ''Note that archlinux.org is throttled to 50KB/s''.<br />
*All packages during installation are from the [core] repository. They are further divided into '''Base''', and '''Base-devel'''.<br />
*Package information and brief descriptions are available [http://www.archlinux.org/packages/?repo=Core&arch=i686&limit=all&sort=pkgname here].<br />
<br />
Package selection is split into two stages. First, select the package category:<br />
{{Note | For expedience, all packages in '''base''' are selected by default. Use the space-bar to select and de-select packages.}}<br />
* '''Base''': Packages from the [core] repo to provide the minimal base environment. ''Always select it and only remove packages that will not be used.''<br />
* '''Base-devel''': Extra tools from [core] such as '''make''', and '''automake'''. ''Most beginners should choose to install it, and will probably need it later.<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 />
{{Note | If connection to a wireless network is required, remember to select and install the '''wireless_tools''' package. Some wireless interfaces also need [[Wireless_Setup#ndiswrapper|'''ndiswrapper''']] and/or a specific [[Wireless_Setup#Drivers_and_firmware|'''firmware''']]. If you plan to use WPA encryption, you will need [[WPA_Supplicant|'''wpa_supplicant''']]. The [[Wireless_Setup|Wireless Setup page]] will help you choose the correct packages for your wireless device. Also strongly consider installing [[Netcfg|'''netcfg''']], which will help you set up your network connection and profiles.}}<br />
<br />
After selecting the needed packages, leave the selection<br />
screen and continue to the next step, Install Packages.<br />
<br />
===E: Install Packages===<br />
Next, choose 'Install Packages'.<br />
*Netinstall: The [[Pacman]] package manager will now download and install your selected packages. (See tty5 for output, tty1 to return to the installer)<br />
*Core image: The packages will be installed from the CD/USB stick.<br />
<br />
In some installers, 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 />
<br />
After the packages have been downloaded, the installer will check their integrity. Next it will create the kernel from the packages downloaded.<br />
<br />
===F: 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|udev]]''' should handle most module loading automatically at boot.<br />
<br />
Now you will be asked which text editor you want to use; choose [[Nano|nano]], [http://joe-editor.sourceforge.net/ joe] or [[Vim|vi]], ('''nano''' is generally considered easiest of the 3). You will be presented with a menu including the main configuration files for your system.<br />
<br />
{{Note | ''It is very important at this point to edit, or at least 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 />
'''''Moving on...'''''<br />
<br />
====/etc/rc.conf====<br />
Arch Linux uses the file {{Filename|/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 />
<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 {{Codeline|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 '''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 {{Filename|/dev/rtc}} for hwclock<br />
* '''TIMEZONE'''=: Specify your TIMEZONE. (All available zones are under {{Filename|/usr/share/zoneinfo/}}).<br />
* '''KEYMAP'''=: The available keymaps are in {{Filename|/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 {{Filename|/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 {{Filename|/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 />
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, (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 will be using loopback filesystems, add "loop". Also specify any blacklisted modules by prefixing them with a bang (!). Udev will be forced NOT to load blacklisted modules. In the example, the IPv6 module as well as the annoying pcspeaker are blacklisted.<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=(!net-pf-10 !snd_pcsp !pcspkr loop)<br />
<br />
=====NETWORKING Section=====<br />
* '''HOSTNAME'''=:Set your HOSTNAME to your liking. This is the name of your computer. Whatever you put here, also put it in {{filename|/etc/hosts}}<br />
* '''eth0'''=: 'Ethernet, card 0'. ''If'' you are using '''static IP''', adjust the interface IP address, netmask and broadcast address. Set eth0=&quot;dhcp&quot; if you want to use '''DHCP''' for dynamic/automatic configuration.<br />
* '''INTERFACES'''=: Specify all interfaces here. Multiple interfaces should be separated with a space as in:<br />
(eth0 wlan0)<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 a dynamically assigned IP address ('''DHCP'''):<br />
<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 />
<br />
Example, using a '''static''' IP address:<br />
<br />
HOSTNAME=&quot;arch&quot;<br />
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"<br />
INTERFACES=(eth0)<br />
gateway="default gw 192.168.0.1"<br />
ROUTES=(gateway)<br />
<br />
Modify {{Filename|/etc/resolv.conf}} to specify the DNS servers of choice. Example:<br />
<br />
search my.isp.net.<br />
nameserver 4.2.2.1<br />
nameserver 4.2.2.2<br />
nameserver 4.2.2.3<br />
<br />
Various processes can overwrite the contents of {{filename|/etc/resolv.conf}}. For example, by default Arch Linux uses the '''dhcpcd''' DHCP client, which will overwrite the file when it starts. [[Resolv.conf|Various methods]] may be used to preserve the nameserver settings in {{filename|/etc/resolv.conf}}. For example, dhcpcd's configurations file may be edited to prevent the dhcpcd daemon from overwriting the file. To do this, you will need to append this to the end of {{Filename|/etc/dhcpcd.conf}}:<br />
<br />
nohook resolv.conf<br />
<br />
{{tip|If using a non-standard MTU size (a.k.a. jumbo frames) is desired AND the installation machine hardware supports them, see the [[Jumbo Frames]] wiki article for further configuration.}}<br />
<br />
=====DAEMONS Section=====<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. Asynchronous initialization by backgrounding is also supported and useful for speeding up boot.<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 (@), it shall be executed in the background; the startup sequence will not wait for successful completion of each daemon before continuing to the next. (Useful for speeding up system boot). Do not background daemons that are needed by other daemons. For example "mpd" depends on "network", therefore backgrounding network may cause mpd to break.<br />
*Edit this array whenever new system services are installed, if starting them automatically during boot is desired.<br />
<br />
{{Note | This 'BSD-style' init, is the Arch way of handling what other distributions handle with various symlinks to an /etc/init.d directory.}}<br />
<br />
;About DAEMONS<br />
<br />
The [[daemons]] line need not be changed at this time, but it is useful to explain what daemons are, as they will be addressed later in this guide.<br />
<br />
A ''daemon'' is a program that runs in the background, waiting for events to occur and offering services. A good example is a web server that waits for a request to deliver a page (e.g.:httpd) or an SSH server waiting for a user login (e.g.:sshd). While these are full-featured applications, there are also daemons whose work is not that visible. Examples are a daemon which writes messages into a log file (e.g. syslog, metalog), and a daemon which provides a graphical login (e.g.: gdm, kdm). All these programs can be added to the daemons line and will be started when the system boots. Useful daemons will be presented during this guide.<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. *nix 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/sda1 / jfs defaults,noatime 0 1<br />
/dev/sda2 /var reiserfs defaults,noatime,notail 0 2<br />
/dev/sda3 swap swap defaults 0 0<br />
/dev/sda4 /home jfs defaults,noatime 0 2<br />
{{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 (see [http://kerneltrap.org/node/14148 here] for more). 'notail' disables the ReiserFS tailpacking feature, for added performance at the cost of slightly less efficient disk usage.}}<br />
<br />
* '''<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'.<br />
<br />
{{Note | If your system has more than one hard drive, the installer will default to using UUID rather than the sd''x'' naming scheme, for consistent device mapping. '''[[Persistent block device naming| Utilizing UUID]] has several advantages and may also be preferred to avoid issues if hard disks are added to the system in the future.''' Due to active developments in the kernel and also udev, the ordering in which drivers for storage controllers are loaded may change randomly, yielding an unbootable system/kernel panic. Nearly every motherboard has several controllers (onboard SATA, onboard IDE), and due to the aforementioned development updates, /dev/sda may become /dev/sdb on the next reboot. (See [[Persistent block device naming| this wiki article]] for more information on persistent block device naming. )}}<br />
<br />
* '''<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 />
* '''<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 />
* '''<options>''': describes the mount options associated with the filesystem. It is formatted as a comma-separated list of options with no intervening spaces. It contains at least the type of mount plus any additional options appropriate to the filesystem type. For documentation on the available options for non-nfs file systems, see mount(8).<br />
<br />
* '''<dump>''': used by the dump(8) command to determine which filesystems are to be dumped. dump is a backup utility. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be backed up. ''Note that dump is not installed by default.''<br />
<br />
* '''<pass>''': 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 />
Expanded information available in the [[Fstab]] wiki entry.<br />
<br />
===='''[[Configuring mkinitcpio | /etc/mkinitcpio]].conf'''====<br />
''Most users will not need to modify this file at this time, but please read the following explanatory information.''<br />
<br />
This file allows further fine-tuning of the initial ram filesystem, or initramfs, (also historically referred to as the initial ramdisk or &quot;initrd&quot;) for your system. The initramfs is a gzipped image that is read by the kernel during boot. The purpose of the initramfs is to bootstrap the system to the point where it can access the root filesystem. This means it has to load any modules that are required for devices like IDE, SCSI, or SATA drives (or USB/FW, if you are booting from a USB/FW drive). Once the initrramfs loads the proper modules, either manually or through udev, it passes control to the kernel and your boot continues. For this reason, the initramfs only needs to contain the modules necessary to access the root filesystem. It does not need to contain every module you would ever want to use. The majority of common kernel modules will be loaded later on by udev, during the init process.<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 '''glibc''' and '''busybox''' to provide a small and lightweight base for early userspace.<br />
* It can use '''udev''' for hardware autodetection at runtime, thus preventing numerous unnecessary modules from being 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 />
<br />
If using RAID or LVM on the root filesystem, the appropriate HOOKS must be configured. See the wiki pages for [[Installing with Software RAID or LVM| RAID]] and [[Configuring mkinitcpio | /etc/mkinitcpio]] for more info. If using a non-US keyboard. add the "<code>keymap</code>" hook to load your local keymap during boot. Add the "<code>usbinput</code>" hook if using a USB keyboard. Don't forget to add the "<code>usb</code>" hook when installing arch on an external hard drive which is connected via usb, e.g.:<br />
HOOKS="base udev autodetect pata scsi sata usb filesystems keymap usbinput"<br />
(Otherwise, if boot fails for some reason you will be asked to enter root's password for system maintenance but will be unable to do so.)<br />
<br />
If you need support for booting from USB devices, FireWire devices, PCMCIA devices, NFS shares, software RAID arrays, LVM2 volumes, encrypted volumes, or DSDT support, configure your HOOKS accordingly.<br />
<br />
If doing a CF or SD card install, you may need to add the <code>usb</code> HOOK for your system to boot properly.<br />
<br />
''If you are using a US keyboard, and have no need for any of the above HOOKS, editing this configuration should be unnecessary at this point.''<br />
<br />
'''mkinitcpio''' is an Arch innovation developed by Aaron Griffin and Tobias Powalowski with some help from the community.<br />
<br />
==== /etc/modprobe.d/modprobe.conf====<br />
<br />
This file can be used to set special configuration options for the kernel modules. It is unnecessary to configure this file in the example.<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 [[Network#For DHCP IP]]).''<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 />
{{Note |''This format, '''including the 'localhost' and your actual host name''', is required for program compatibility! So, if you have named your computer "arch", then that line above should look like this:<br />
127.0.0.1 localhost.localdomain localhost arch<br />
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 />
* restrict it to your local LAN network (range 192.168.0.0 to 192.168.0.255)<br />
sshd: 192.168.0.<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 text, correctly displaying regional monetary values, time and date formats, alphabetic idiosyncrasies, and other locale-specific standards.<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 />
{{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 />
====Pacman-Mirror====<br />
Choose a mirror repository for '''pacman'''.<br />
*''archlinux.org is throttled, limiting downloads to 50KB/s''<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 />
====Done====<br />
When you select "Done", the system will rebuild the images and put you back to the Main Menu. This may take some time.<br />
<br />
===G: 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.alioth.debian.org/ LILO] or [[Syslinux]].<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/sda1 ro<br />
initrd /boot/kernel26.img<br />
{{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 />
Example for /boot on the separate partition:<br />
title Arch Linux (Main)<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 ro<br />
initrd /kernel26.img<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''').<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, (usually a safe default; you may wish to change this in case it causes problems booting).<br />
<br />
Note: Depending on hardware, 'rootdelay=8' may need to be added to the kernel options in order to be able to boot from an external usb hard drive.<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 />
{{tip|For more details, see the [[GRUB]] wiki page.}}<br />
<br />
===H: 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: Update==<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 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.<br />
<br />
{{Note |Virtual consoles 1-6 are available. You may switch between them with ALT+F1...F6}}<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, an &quot;unknown host&quot; error is received, you may conclude that your network is not properly configured. You may choose to double-check the following files for integrity and proper settings:<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 />
{{Tip|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 wlan0 up<br />
<br />
{{Note|If you get this error message: <code>SIOCSIFFLAGS: No such file or directory</code> it most certainly means your wireless chipset requires a firmware to function, which you forgot to install during package selection. See [[Beginners'_Guide#Does_the_Wireless_Chipset_require_Firmware.3F|Does the Wireless Chipset require Firmware?]] and [[Beginners'_Guide#D:_Select_Packages|Select Packages]].}}<br />
<br />
* Associate your wireless device with the access point you want to use. Depending on the encryption (none, WEP, or WPA), the procedure may differ. You need to know the name of the chosen wireless network (ESSID), e.g. 'linksys' in the following examples:<br />
* An example using a ''non-encrypted'' network:<br />
# iwconfig wlan0 essid &quot;linksys&quot;<br />
* An example using ''WEP and a hexadecimal key'':<br />
# iwconfig wlan0 essid &quot;linksys&quot; key 0241baf34c<br />
* An example using ''WEP and an ASCII passphrase'':<br />
# iwconfig wlan0 essid "linksys" key s:pass1<br />
* Using ''WPA'', the procedure requires a bit more work. Check [[WPA_Supplicant|WPA supplicant]] for more information and troubleshooting:<br />
# wpa_passphrase linksys "secretpassphrase" > /etc/wpa_supplicant.conf<br />
# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf<br />
<br />
* Check you have successfully associated to the access point before continuing:<br />
# iwconfig wlan0<br />
<br />
* Request an IP address with <code>/sbin/dhcpcd <interface> </code>. e.g.:<br />
# dhcpcd wlan0<br />
* Ensure you can route using <code>/bin/ping</code>:<br />
# ping -c 3 www.google.com<br />
<br />
You should have a working network connection. For troubleshooting, check the detailed [[Wireless_Setup|Wireless Setup]] page.<br />
<br />
====Proxy Server====<br />
If you are behind a proxy server, edit /etc/wgetrc and set http_proxy and ftp_proxy in it.<br />
<br />
====Analog Modem, ISDN, and DSL (PPPoE)====<br />
See [[Internet Access]] for detailed instructions.<br />
<br />
===Step 2: Update, Sync, and Upgrade the system with [[pacman]]===<br />
Now we will update the system using [[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, to occupy a very modest memory footprint, and to be 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. Pacman's output is streamlined, very readable and provides ETA for each package download. Arch uses pkg.tar.gz tarballs and is in the process of moving to the pkg.tar.xz format.<br />
<br />
Pacman will now be used to download software packages from remote repositories and install them onto your system.<br />
<br />
====Package Repositories====<br />
Arch currently offers the following 5 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 ensure the system remains in a usable state. These are the absolute system-critical packages.<br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<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.<br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<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 />
<br />
<nowiki>*</nowiki> they are expected to break something on update and need to be tested first.<br />
<br />
<nowiki>*</nowiki> 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.<br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<br />
{{Note|[testing] is the only repository that can have name collisions with any of the other official repositories. Therefore, if enabled, [testing] must be the first repo listed in <code>pacman.conf</code>.}}<br />
<br />
{{Warning|Only experienced users should use [testing].}}<br />
<br />
=====[community]=====<br />
<br />
The [community] repository is maintained by the ''Trusted Users (TUs)'' and is simply the binary branch of the ''Arch User Repository ([[AUR]])''. It contains binary packages which originated as PKGBUILDs from ''AUR'' [unsupported] that have acquired enough votes and were adopted by a ''TU''. Like all repos listed above, [community] may be readily accessed by pacman.<br />
* TU maintained<br />
* All binary packages<br />
* pacman accessible<br />
<br />
=====[multilib]=====<br />
<br />
Users running 64 bit arch linux may want to install and use applications that are not available in 64 bit (and most desktop or laptop users probably will). The 32 bit versions of these applications can be used, but require that certain 32 bit libraries are installed. These libraries are available in the [multilib] repository.<br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<br />
<br />
{{Note | If you want to use this repository, you should add the lines below to <code>/etc/pacman.conf</code> }}<br />
[multilib]<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
=====AUR (unsupported)=====<br />
<br />
The '''[[AUR]]''' also contains the '''unsupported''' branch, which cannot be accessed directly by pacman*. '''AUR''' [unsupported] does not contain binary packages. Rather, it provides more than sixteen thousand PKGBUILD scripts for building packages from source, that may be unavailable through the other repos. When an AUR unsupported package acquires enough popular votes, it may be moved to the AUR [community] binary repo, if a TU is willing to adopt and maintain it there.<br />
* TU maintained<br />
* All PKGBUILD bash build scripts<br />
* '''''Not''''' pacman accessible by default<br />
<br />
<nowiki>*</nowiki> pacman wrappers ('''''[[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 />
<br />
Note that the defaults should work, so modifying at this point may be unnecessary, but verification is always recommended. Further info available in the [[Mirrors]] article.<br />
# nano /etc/pacman.conf<br />
Example:<br />
{{File|name=/etc/pacman.conf|content=<nowiki>#<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 />
</nowiki>}}<br />
<br />
Enable all desired repositories (remove the # in front of the 'Include =' and '[repository]' lines).<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 />
Defines pacman repository mirrors and priorities.<br />
<br />
'''Build a mirrorlist using the rankmirrors script''' (Optional)<br />
<br />
<code>/usr/bin/rankmirrors</code> is a bash script which will attempt to detect uncommented mirrors specified in /etc/pacman.d/mirrorlist which are closest to the installation machine based on latency. Faster mirrors will dramatically improve pacman performance, and the overall Arch Linux experience. This script may be run periodically, especially if the chosen mirrors provide inconsistent throughput and/or updates. Note that <code>rankmirrors</code> does not test for throughput. Too/ls such as <code>wget</code> or <code>rsync</code> may be used to effectively test for mirror throughput after a new <code>/etc/pacman.d/mirrorlist</code> has been generated.<br />
<br />
'''Initially force pacman to refresh the package lists'''<br />
<br />
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 />
Use pacman to install curl:<br />
# pacman -S curl<br />
<br />
*'''''If you get an error at this step, use the command "nano /etc/pacman.d/mirrorlist" and uncomment a server that suits you.'' ''<br />
<br />
'''cd''' to the /etc/pacman.d/ directory:<br />
# cd /etc/pacman.d<br />
Backup the existing /etc/pacman.d/mirrorlist:<br />
# cp mirrorlist mirrorlist.backup<br />
Edit mirrorlist.backup and uncomment all mirrors on the same continent or within geographical proximity to test with rankmirrors.<br />
# nano mirrorlist.backup<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 closest mirrors<br />
<br />
Force pacman to refresh all package lists with the new mirrorlist in place:<br />
# pacman -Syy<br />
<br />
If you want to get help from the IRC channel, you will find it easier if you install and use curlpaste:<br />
# pacman -S curlpaste<br />
<br />
====Mirrorcheck for up-to-date packages====<br />
Some of the official mirrors may contain packages that are out-of-date. [https://www.archlinux.de/?page=MirrorStatus;orderby=lastsync;sort=1 ArchLinux Mirrorcheck] reports various aspects about the mirrors such as network problems with mirrors, data collection problems, the last time mirrors have been synced, etc.<br />
<br />
One may wish to manually inspect /etc/pacman.d/mirrorlist, ensuring that the file contains only up-to-date mirrors if having the latest package versions is a priority.<br />
<br />
====Ignoring packages====<br />
After executing the command &quot;pacman -Syu&quot;, the entire system will be updated. It is possible to prevent a package from being upgraded. A typical scenario would be a package for which an upgrade may prove problematic for the system. In this case, there are two options; indicate the package(s) to skip in the pacman command line using the --ignore switch (do pacman -S --help for details) or permanently indicate the package(s) to skip in the /etc/pacman.conf file in the IgnorePkg array. List each package, with one intervening space :<br />
IgnorePkg = wine<br />
The typical way to use Arch is to use pacman to install all packages unless there is no package available, in which case [[ABS]] may be used. Many user-contributed package build scripts are also available in the [[AUR]] and can be installed manually with [[makepkg]], or with an [[AUR helper]].<br />
<br />
The power user is expected to keep the system up to date with pacman -Syu, rather than selectively upgrading packages. You may diverge from this typical usage as you wish; just be warned that there is a greater chance that things will not work as intended and that it could break your system. The majority of complaints happen when selective upgrading, unusual compilation or improper software installation is performed. Use of '''IgnorePkg''' in /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, have a look at the [[pacman]] wiki entry at your own leisure.<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 required configurations and modifications 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 />
or:<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 />
{{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 />
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 />
==Part III: Add a user==<br />
<br />
Linux is a multi-user environment. You should not do your everyday work using the root account. It is more than poor practice; it is dangerous. Root is for administrative tasks. Instead, add a normal, non-root, user account using the <code>/usr/sbin/useradd</code> program.<br />
<br />
useradd -m -g [initial_group] -G [additional_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''' The group name or number of the user's initial login group. The group name must exist. If a group number is provided, it must refer to an already existing group. If not specified, the behavior of useradd will depend on the USERGROUPS_ENAB variable contained in /etc/login.defs.<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.<br />
* '''-s''' The path and filename of the user´s default login shell. Arch Linux init scripts use Bash. After the boot process is complete, the default login shell is user-specified. (Ensure the chosen shell package is installed if choosing something other than Bash).<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 hardware acceleration<br />
*'''wheel''' - for using sudo<br />
*'''games''' - needed for write permission for games in the games group<br />
*'''power''' - used w/ power options (e.g.: shutdown with power button)<br />
*'''scanner''' - for using a scanner<br />
A typical desktop system example, adding a user named "archie" specifying bash as the login shell:<br />
useradd -m -g users -G audio,lp,optical,storage,video,wheel,games,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 password.)<br />
<br />
Your new non-root user has now been created, complete with a home directory and a login password.<br />
<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 />
If you want to change the name of your user or any existing user, see the [[Change username]] page of the Arch wiki and/or 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 />
===Install and setup Sudo (Optional)===<br />
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.<br />
<br />
By default, the visudo command uses the editor [[vi]]. If you do not know how to use vi, you may set the EDITOR environment variable to the editor of your choice, such as in this example with the editor "nano":<br />
# EDITOR=nano visudo<br />
{{Note|Please note that you are setting the variable and starting visudo on the same line at the same time. This will not work properly as two separated commands.}}<br />
<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 />
In the previous section we added your user to the "wheel" group. To give users in the wheel group full root privileges when they precede a command with &quot;sudo&quot;, uncomment the following line:<br />
%wheel ALL=(ALL) ALL<br />
Now you can give any user access to the sudo command by simply adding them to the wheel group.<br />
<br />
For more information, such as sudoer <TAB> completion, see [[Sudo]]<br />
<br />
Further, for security purposes, it is good practice to restrict access to the "su" command to users in the "wheel" group only. This can be accomplished by editing /etc/pam.d/su:<br />
# nano /etc/pam.d/su<br />
Uncomment the following line:<br />
auth required pam_wheel.so use_uid<br />
<br />
==Part IV: Sound==<br />
<br />
The [[Wikipedia:Advanced Linux Sound Architecture|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 />
{{Note| Alsa is included in the Arch mainline kernel and udev will automatically probe your hardware at boot, loading the corresponding kernel module for your audio card. Therefore, your sound should already be working, but upstream sources mute all channels by default.}}<br />
{{Note| [[Wikipedia:Open Sound System|OSS4.2]] 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.2 instead. Instructions can be found in the [[OSS|OSS article]].}}<br />
<br />
The alsa-utils package contains the alsamixer userspace tool, which allows configuration of the sound device from the console or terminal.<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, 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 />
You must log out to activate this change. 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 {{keypress|M}}. With the key {{keypress|↑}} increased the volume to obtain a value of zero dB gain, this wording is found in the upper left. Higher values of gain produce distorted sounds and crackling.<br />
<br />
Card: NVidia CK804<br />
Chip: Realtek ALC658D<br />
View: F3:[Playback] F4: Capture F5: All<br />
Item: PCM ['''dB gain: 0,00, 0,00''']<br />
<br />
Usually a value around 75 produces a gain of zero, but some cards to a maximum value do not add any gain. Some machines, (like the Thinkpad T61), have a '''Speaker''' channel which must be unmuted and adjusted as well. Leave alsamixer by pressing ESC.<br />
<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 woman's voice saying, &quot;Front, center.&quot;<br />
<br />
====Saving the sound settings====<br />
Switch back to root user and store these settings using <code>/usr/sbin/alsactl</code> :<br />
# alsactl -f /var/lib/alsa/asound.state store<br />
This will create the file {{Filename|/var/lib/alsa/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 at boot.<br />
# nano /etc/rc.conf<br />
DAEMONS=(syslog-ng network crond '''alsa''')<br />
{{Note| The alsa daemon merely restores your volume mixer levels on boot up by reading {{Filename|/var/lib/alsa/asound.state}}. It is separate from the alsa audio library (and kernel level API).''}}<br />
<br />
{{Tip|For advanced information and troubleshooting, see [[ALSA]].}}<br />
<br />
==Part V: '''G'''raphical '''U'''ser '''I'''nterface==<br />
<br />
===Step 1: Install X===<br />
<br />
The '''X''' Window System version 11 (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).<br />
<br />
'''X''' provides the basic framework, or primitives, for building GUI environments: spaces for interaction with a mouse, keyboard, or other input to windows on the screen. '''X''' does not mandate the user interface per application, the individual client programs handle this. '''X''' does add that graphic splendor at the cost of an extra layer.<br />
<br />
'''X''' is so named because it was preceded by the '''W''' Window System, originally developed at Stanford University.<br />
<br />
{{Warning|If you're installing Arch in a Virtualbox guest, you need a different way to complete X installation. See [[Virtualbox#Running Arch Linux as a guest|Running Arch Linux as a guest]], then skip the A,B,C steps below.<br />
}}<br />
<br />
====A: Install Xorg====<br />
Now we will install the base '''[[Xorg]]''' packages using pacman. This is the first step in building a GUI.<br />
<br />
Install the base packages:<br />
# pacman -S xorg<br />
<br />
Install mesa for 3D support:<br />
<br />
# pacman -S mesa<br />
<br />
The 3D utilities glxgears and glxinfo are included in the '''mesa-demos''' package, install if needed:<br />
<br />
# pacman -S mesa-demos<br />
<br />
====B: Install video driver====<br />
<br />
Next, you should install a driver for your graphics card.<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<br />
<br />
{{Note| The '''vesa''' driver is the most generic, and should work with almost any modern video chipset. If you cannot find a suitable driver for your video chipset, vesa ''should'' work with any video card, but it offers only slow 2D.}}<br />
<br />
If you need a list of all open-source video drivers, do:<br />
$ pacman -Ss xf86-video | less<br />
Or use this list of open-source drivers, and the corresponding video chipsets:<br />
<br />
*'''xf86-video-apm''' — Alliance ProMotion video driver<br />
*'''xf86-video-ark''' — ark video driver<br />
*'''xf86-video-ast''' — ASPEED AST Graphics video driver<br />
*'''xf86-video-ati''' — ATI(AMD) radeon video driver<br />
**'''xf86-video-r128''' — ATI(AMD) video driver for X.org ati Rage128 video<br />
**'''xf86-video-mach64''' — ATI(AMD) video driver for X.org mach64 video<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-intel''' — Intel i810/i830/i915/945G/G965+ video drivers<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-nouveau''' — Open Source 3D acceleration driver for nVidia cards<br />
*'''xf86-video-openchrome''' — VIA/S3G UniChrome, UniChrome Pro and Chrome9 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-vmware''' — vmware video driver<br />
*'''xf86-video-voodoo''' — voodoo video driver<br />
*'''xf86-video-xgi''' — XGI video driver<br />
*'''xf86-video-xgixp''' — XGIXP video driver<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 />
{{Tip|For some Intel graphics cards, configuration may be necessary to get proper 2D or 3D performance, see [[Intel]] for more information.}}<br />
<br />
=====NVIDIA Graphics Cards=====<br />
NVIDIA users have three options for drivers (in addition to the vesa driver):<br />
* The open source nouveau driver, which offers fast 2d acceleration and experimental 3d support which is good enough for basic compositing (note: does not support powersaving yet). [http://nouveau.freedesktop.org/wiki/FeatureMatrix Feature Matrix.]<br />
* The open source (but obfuscated) nv driver, which is very slow and only has 2d support.<br />
* The proprietary nvidia drivers, which offer good 3d performance and powersaving. See [[NVIDIA]] for more information. Even if you plan on using the proprietary drivers, it's recommended to start with nouveau and then switch to the binary driver, because nouveau will almost always work out-of-the-box, while nvidia will require configuration and likely some troubleshooting.<br />
<br />
The open-source nouveau driver should be good enough for most users and is recommended:<br />
<br />
# pacman -S xf86-video-nouveau<br />
<br />
For 3D support (highly experimental):<br />
<br />
# pacman -S nouveau-dri<br />
<br />
Create the file {{Filename|/etc/X11/xorg.conf.d/20-nouveau.conf}}, and input the following contents:<br />
<br />
Section "Device"<br />
Identifier "n"<br />
Driver "nouveau"<br />
EndSection<br />
<br />
This is required to ensure that nouveau driver is loaded. Xorg is not yet smart enough to do this by itself.<br />
<br />
{{Tip|For advanced instructions, see [[Nouveau]].}}<br />
<br />
=====ATI Graphics Cards=====<br />
ATI owners have two options for drivers (in addition to the vesa driver):<br />
* The open source '''''radeon''''' driver provided by the '''xf86-video-ati''' package. It fully supports Radeon chipsets up to X1950 (latest R500 chipsets). Cards up to the 9200 series are fully supported, stable, and provide full 2D and 3D acceleration. Cards from 9500 to HD4000 feature full 2D acceleration, and stable/partly implemented 3D acceleration, but lack certain features provided by the proprietary driver; power management is under development and in an advanced stage, but not on par with catalyst. HD5000 support is currently a work in progress. Supports KMS and HDMI with audio output since kernel 2.6.33. [http://wiki.x.org/wiki/RadeonFeature Feature Matrix.]<br />
* The proprietary '''''fglrx''''' driver provided by the [http://aur.archlinux.org/packages.php?O=0&K=catalyst&do_Search=Go catalyst] package located in the [[AUR]]. It supports only newer devices (HD2xxx and newer). It was once a package offered by Arch in the <code>extra</code> repository, but as of March 2009, official support has been dropped because of dissatisfaction with the quality and speed of development of the proprietary driver. See [[ATI Catalyst]] for more information.<br />
<br />
The open-source driver is the recommended choice:<br />
<br />
Install the '''''radeon''''' ATI Driver:<br />
# pacman -S xf86-video-ati<br />
<br />
{{Tip|For advanced instructions, see [[ATI]].}}<br />
<br />
====C: Install input drivers====<br />
<br />
Udev should be capable of detecting your hardware without problems and evdev (xf86-input-evdev) is the modern, hotplugging input driver for almost all devices so in most cases, installing input drivers is not needed. At this point, evdev has already been installed as a dependency of Xorg.<br />
<br />
If evdev does not support your device, install the needed driver from the xorg-input-drivers group.<br />
<br />
For a complete list of available input drivers, invoke a pacman search:<br />
# pacman -Ss xf86-input | less<br />
<br />
{{Note|You only need xf86-input-keyboard or xf86-input-mouse if you plan on disabling hotplugging, otherwise, evdev will act as the input driver.}}<br />
<br />
Laptop users (or users with a touchscreen) will also need the synaptics package to allow X to configure the touchpad/touchscreen:<br />
# pacman -S xf86-input-synaptics<br />
{{Tip|For instructions on fine tuning or troubleshooting touchpad settings, see the [[Touchpad Synaptics]] article.}}<br />
<br />
===Step 2: Configure X (Optional)===<br />
<br />
{{Warning|Proprietary drivers usually require a reboot after installation along with configuration. See [[NVIDIA]] or [[ATI Catalyst]] for details.}}<br />
<br />
X.Org X Server features auto-configuration. Therefore, it can function without an xorg.conf.<br />
<br />
{{Note|If you want to configure something like horizontal/vertical refresh or monitor dimensions if your monitor's EDID is incorrect, see [[Xorg]].}}<br />
<br />
The current arrangement of configuration files is found in /etc/X11. Within that directory, there is the subdirectory /etc/X11/xorg.conf.d. This is the directory which contains the default configuration files for the X server. These are supplied by your distribution, automatically-created or may also be added to for your personal configuration and editing. However, it is also possible to simply create and edit {{filename|/etc/X11/xorg.conf}}, since that file is read last after those in the /xorg.conf.d directory.<br />
<br />
====Non-US keyboard====<br />
<br />
If you do not use a standard US keyboard you need to set the keyboard layout in {{Filename|/etc/X11/xorg.conf.d/10-evdev.conf}}:<br />
<br />
Section "InputClass"<br />
Identifier "evdev keyboard catchall"<br />
MatchIsKeyboard "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Driver "evdev"<br />
'''Option "XkbLayout" "be"'''<br />
EndSection<br />
<br />
{{Note|The '''XkbLayout''' key may differ from the keymap code you used with the km or loadkeys command. For instance, the uk layout corresponds to the key: '''gb'''.}}<br />
<br />
===Step 3: Starting a basic graphical environment===<br />
<br />
This section will explain how to start the very basic graphical environment included with in the xorg group. This uses the simple default X window manager, twm.<br />
<br />
The default X environment is rather bare, and step 5 will deal with installing a desktop environment or window manager of your choice to supplement X.<br />
<br />
If you just installed Xorg, there is an empty .xinitrc file in your $HOME that you need to either delete or edit in order for X to start properly. If you do not do this X will show a blank screen with what appears to be no errors in your Xorg.0.log. Simply deleting it will get it running with a default X environment.<br />
<br />
$ rm ~/.xinitrc<br />
<br />
====Message bus====<br />
<br />
dbus is likely required for many of your applications to work properly, if you know you don't need it, skip this section.<br />
<br />
=====Installation=====<br />
<br />
Install dbus:<br />
<br />
# pacman -S dbus<br />
<br />
=====Starting the daemon=====<br />
<br />
You should add dbus to your DAEMONS array in {{filename|/etc/rc.conf}}:<br />
<br />
DAEMONS=(syslog-ng '''dbus''' network crond)<br />
<br />
If you need to start dbus without rebooting, run<br />
<br />
# /etc/rc.d/dbus start<br />
<br />
====Starting X====<br />
<br />
{{Note|The Ctrl-Alt-Backspace shortcut traditionally used to kill X has been deprecated and will not work to exit out of this test. You can enable Ctrl-Alt-Backspace by editing xorg.conf, as described at [[Xorg#Ctrl-Alt-Backspace doesn't work|here]].}}<br />
<br />
Finally, start Xorg:<br />
$ startx<br />
or<br />
$ xinit -- /usr/bin/X -nolisten tcp<br />
<br />
If the screen goes black, you may still attempt to switch to a different virtual console (CTRL-Alt-F2, for example), and login blindly as root, followed by <Enter>, followed by root's password followed by <Enter>.<br />
<br />
You can attempt to kill the X server with <code>/usr/bin/pkill</code> (note the capital letter '''X'''):<br />
# pkill X<br />
<br />
If pkill does not work, reboot blindly with:<br />
# reboot<br />
or<br />
# init 6<br />
<br />
====In case of errors====<br />
If a problem occurs, then look for errors in {{Filename|/var/log/Xorg.0.log}}. Be on the lookout for any lines beginning with {{Codeline|(EE)}} which represent errors, and also {{Codeline|(WW)}} which are warnings that could indicate other issues.<br />
<br />
$ grep EE /var/log/Xorg.0.log<br />
<br />
Errors may also be searched for in the console output of the virtual console from which '''X''' was started.<br />
<br />
See the [[Xorg]] article for detailed instructions and troubleshooting.<br />
<br />
=====Need Help?=====<br />
<br />
If you are still having trouble after consulting the [[Xorg]] article and need assistance via the Arch forums, be sure to install and use wgetpaste:<br />
<br />
# pacman -S wgetpaste<br />
Use wgetpaste and provide links for the following files when asking for help in your forum post:<br />
* ~/.xinitrc<br />
* /etc/X11/xorg.conf<br />
* /var/log/Xorg.0.log<br />
* /var/log/Xorg.0.log.old<br />
Use wgetpaste like so:<br />
$ wgetpaste </path/to/file><br />
Post the corresponding links given within your forum post. Be sure to provide appropriate hardware and driver information as well.<br />
{{Warning| '''''It is very important to provide detail when troubleshooting X. Please provide all pertinent information as detailed above when asking for assistance on the Arch forums. '''''}}<br />
<br />
===Step 4: 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 is a set of high quality, general-purpose fonts.<br />
<br />
Install with:<br />
# pacman -S ttf-dejavu<br />
<br />
Refer to [[Font Configuration]] for how to configure font rendering and [[Fonts]] for font suggestions and installation instructions.<br />
<br />
===Step 5: Choose and install a graphical interface===<br />
<br />
The X Window System provides the basic framework for building a graphical user interface (GUI).<br />
<br />
A Window Manager controls the placement and appearance of application windows in conjunction with the X Window System.<br />
<br />
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.<br />
<br />
Alternatively, you can build your own DE by using a WM and the applications of your choice.<br />
<br />
{{Note|Unlike lots of other distributions, Arch won't decide what graphical environment you want to use. Choosing your DE or WM is a very subjective and personal decision. Choose the best environment for ''your'' needs. It's worth trying out a bunch of the environments listed here before you make your choice as pacman can completely remove anything you install.}}<br />
<br />
After installing a graphical interface, you'll probably want to continue with [[General Recommendations]] for post-installation instructions.<br />
<br />
====Desktop Environments====<br />
<br />
See [[Desktop Environment#Desktop environments|Desktop environments]] for more information.<br />
<br />
====Window Managers====<br />
<br />
See [[Window Manager#Window managers|Window managers]] for more information.<br />
<br />
===Methods for starting your Graphical Environment===<br />
<br />
====A: Manually====<br />
You might prefer to start X manually from your terminal rather than booting straight into the desktop (if not, skip to [[Beginner's Guide#B: Automatically|B: Automatically]]). There are three methods for starting X manually. Choose the one that suits you best:<br />
<br />
=====Method 1: DE-specific commands=====<br />
For some users, this method might be the easiest since you need only enter a command without any configuring.<br />
Simply use a command to launch your WM/DE.<br />
You may always start your desktop environment with '''xinit''' or '''startx''', followed by the path to your DE's script:<br />
<br />
$ xinit /usr/bin/gnome-session<br />
or<br />
$ startx /usr/bin/startkde<br />
<br />
from the shell prompt. Note that such a command does not finish until you logout of the DE.<br />
{{Note|If you do '''xinit gnome-session''' instead of '''xinit /usr/bin/gnome-session''', then you will have problems on your desktop. Always include the complete path (/usr/bin/)}}<br />
<br />
Optionally, you can make an [[Bashrc#Aliases|alias]] in /etc/bash.bashrc so you don't have to type the whole command.<br />
...<br />
alias gnome="xinit /usr/bin/gnome-session"<br />
...<br />
<br />
Alternatively, if you wish to launch a Display Manager (AKA login manager) rather than go directly into your desktop, you can use the command for your installed Display Manager. For example, for gnome:<br />
$ gdm<br />
or KDE:<br />
$ kdm<br />
etc.<br />
<br />
=====Method 2: using runlevels=====<br />
By default, Linux is set up to have different [[runlevels]]. Arch boots into runlevel 3 by default. Runlevel 5 is typically used in Linux for loading X server.<br />
Edit the file /etc/inittab. In the last section at the bottom of the file, uncomment the appropriate line for your desktop environment's display manager. For example, for gnome it would look like this:<br />
# Example lines for starting a login manager<br />
#x:5:respawn:/usr/bin/xdm -nodaemon<br />
x:5:respawn:/usr/sbin/gdm -nodaemon<br />
#x:5:respawn:/usr/bin/kdm -nodaemon<br />
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1<br />
<br />
Now, simply start your desktop environment, as root, with<br />
# init 5<br />
or, as a normal user, with<br />
$ sudo init 5<br />
<br />
=====Method 3: using .xinitrc=====<br />
This method involves the most configuring.<br />
<br />
First we need to configure ~/.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 />
<br />
{{Note | '''[[.xinitrc]]''' is a so-called 'dot' (.) file. Files in a *nix 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 />
The '''startx''' and '''xinit''' commands 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 />
<br />
# su - ''yourusername''<br />
<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 />
{{Note | This template file '''[[.xinitrc]]''' is available in the /etc/skel directory when the package '''xorg-xinit''' is installed.}}<br />
<br />
* Sample .xinitrc 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 uncomment the line that corresponds to your Desktop Environment. For example, if you use Gnome, it will look something like this:<br />
<br />
<pre><br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
<br />
exec gnome-session<br />
# exec startkde<br />
# exec startxfce4<br />
# exec wmaker<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
# exec openbox-session<br />
# ...or the Window Manager of your choice<br />
# exec xterm<br />
</pre><br />
For KDE uncomment:<br />
exec startkde<br />
For fluxbox:<br />
exec fluxbox<br />
etc...<br />
<br />
{{Note | ''Be sure to have only '''one''' uncommented '''exec''' line in ~/.xinitrc'' for now.}}<br />
<br />
Now we're ready to launch X. Start '''X''' as a '''normal, non-root''' user, with:<br />
<br />
$ startx<br />
or<br />
$ xinit<br />
<br />
Your desktop should open up now. You can test your keyboard and its layout in it. Try moving your mouse around and enjoy the view.<br />
<br />
If trouble with automounting is experienced, try using the following command in ~/.xinitrc instead. (Replace "startxfce4" with the command that is appropriate for your window manager/DE.)<br />
exec ck-launch-session startxfce4<br />
This will ensure the various environment variables are set correctly by starting a clean consolekit session. ConsoleKit is a framework for keeping track of the various users, sessions, and seats present on a system. It provides a mechanism for software to react to changes of any of these items or of any of the metadata associated with them. It works in conjunction with dbus, and other tools.<br />
<br />
====B: Automatically====<br />
Most users might prefer to have their desktop start automatically during boot instead of starting X manually. There are two methods for starting X automatically. Choose the one that suits you best:<br />
<br />
=====Method 1: using runlevels=====<br />
This method expands on Method 2 from the section above on starting X manually.<br />
<br />
By default, Linux is set up to have different [[runlevels]]. Arch boots into runlevel 3 by default. Runlevel 5 is typically used for loading X server.<br />
Edit the file /etc/inittab.<br />
In the first section, uncomment '''id:5:initdefault:''' so it looks like this:<br />
## Only one of the following two lines can be uncommented!<br />
# Boot to console<br />
#id:3:initdefault:<br />
# Boot to X11<br />
id:5:initdefault:<br />
This tells Arch to boot to runlevel 5 when you start your computer.<br />
<br />
In the last section at the bottom of the file, uncomment the appropriate line for your desktop environment's display manager. For example, for gnome it would look like this:<br />
# Example lines for starting a login manager<br />
#x:5:respawn:/usr/bin/xdm -nodaemon<br />
x:5:respawn:/usr/sbin/gdm -nodaemon<br />
#x:5:respawn:/usr/bin/kdm -nodaemon<br />
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1<br />
<br />
=====Method 2: using a daemon=====<br />
Simply add your display manager to your daemons array in /etc/rc.conf. For example, it would look like this for gnome:<br />
DAEMONS=(syslog-ng dbus network '''gdm''' ...)<br />
You might try backgrounding your display manager so that other daemons continue loading while the display manager loads:<br />
DAEMONS=(syslog-ng dbus hal network '''@kdm''' ...)<br />
<br />
==Appendix==<br />
For a list of [[Common Applications]] and [[Lightweight Applications]], visit their respective articles.<br />
<br />
See [[General Recommendations]] for post-installation tutorials like setting up CPU frequency scaling or font rendering.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Pm-utils&diff=125536
Pm-utils
2010-12-18T17:56:45Z
<p>Cantabile: Added box with summary + related articles</p>
<hr />
<div>[[Category:Power management (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|pm-utils}} {{DISPLAYTITLE:pm-utils}}<br />
{{Article summary start}}<br />
{{Article summary text|Describes installing, configuring, using and troubleshooting pm-utils, the new suspend and powerstate setting framework.}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|Uswsusp}}<br />
{{Article summary wiki|Tuxonice}}<br />
{{Article summary end}}<br />
'''pm-utils''' is the new suspend and powerstate setting framework. It is designed to replace such scripts as those provided by the <tt>powersave</tt> package.<br />
<br />
It is usually used by HAL to execute the various hacks needed to work around bugs in drivers and subsystems that are not yet aware of suspend. It is easily extensible by putting custom hooks into a directory, which can either be done by the system administrator or those hooks can be part of a package, especially if this package needs special attention during a system suspend or power state transition.<br />
<br />
A lesser known feature is one that mimmicks toggling done by [[Laptop Mode Tools]].<br />
<br />
Used in conjunction with the [[cpufrequtils]] package, notebook (and desktop) owners are provided with a complete power management suite.<br />
<br />
== Installation ==<br />
<br />
The <tt>pm-utils</tt> package is now available from the [http://www.archlinux.org/packages/search/?q=pm-utils Extra] repository:<br />
# pacman -S pm-utils<br />
<br />
{{note|If you run into issues when resuming video, it might be necessary to also sync <tt>vbetool</tt> from [extra].}}<br />
<br />
{{note|If you are starting from a clean install, make sure that you have <tt>acpi</tt> installed.}}<br />
<br />
== Basic Configuration ==<br />
=== Hibernation (suspend2disk) ===<br />
In order for suspend2disk (hibernate) to work, we need to edit ''/boot/grub/menu.lst'' as root and add '''resume=/path/to/swap/drive''' (e.g. /dev/sda2) to the kernel options, for example:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 '''resume=/dev/sda2''' ro vga=0<br />
initrd /kernel26.img<br />
<br />
Raid swap example:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/md2 resume=/dev/md0 ro md=0,/dev/sda2,/dev/sdb2 md=2,/dev/sda5,/dev/sdb5 vga=773<br />
initrd /kernel26.img<br />
<br />
If you want to use the UUID of the device instead then use the following example. The UUID itself can by find out by using the blkid command as root.<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 cryptdevice=/dev/sda2:main root=/dev/mapper/main-root resume=/dev/disk/by-uuid/1d893194-b151-43cd-a89e-6f89bd8b9f99 ro<br />
initrd /kernel26.img<br />
<br />
When the machine is placed into hibernation, it will now move all data from RAM to the swap partition... you ''did'' make your swap partition large enough to hold your RAM data, right?<br />
<br />
Even if your swap partition is smaller than RAM, you still have a big chance in hibernating successfully. According to [http://www.mjmwired.net/kernel/Documentation/power/interface.txt kernel documentation], ''/sys/power/image_size controls the size of the image created by the suspend-to-disk mechanism'', which has a default value of 500M. ''The suspend-to-disk mechanism will do its best to ensure the image size will not exceed that number.'' You may either decrease it due to a small swap partition or increase it in purpose of possible hibernation speed up.<br />
<br />
{{Box Note|'''''You may have to add the resume hook to mkinitcpio, see [[Pm-utils#Resume_Hook|below]]!'''''}}<br />
<br />
=== Suspend/Hibernate as regular user ===<br />
<br />
Three methods are available to suspend without the need for a root password: using HAL, using UPower, and giving the user permissions with visudo.<br />
<br />
==== UPower method ====<br />
<br />
To suspend to RAM:<br />
<br />
<pre><br />
$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" \<br />
/org/freedesktop/UPower org.freedesktop.UPower.Suspend<br />
</pre><br />
<br />
To suspend to disk (hibernate):<br />
<br />
<pre><br />
$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" \<br />
/org/freedesktop/UPower org.freedesktop.UPower.Hibernate<br />
</pre><br />
<br />
==== HAL Method ====<br />
<br />
HAL can be invoked as regular user to suspend by:<br />
<br />
<pre>$ dbus-send --system --print-reply --dest=org.freedesktop.Hal \<br />
/org/freedesktop/Hal/devices/computer \<br />
org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0</pre><br />
<br />
and Hibernate by:<br />
<br />
<pre>$ dbus-send --system --print-reply --dest=org.freedesktop.Hal \<br />
/org/freedesktop/Hal/devices/computer \<br />
org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate</pre><br />
<br />
==== User Permission Method ====<br />
<br />
Because the <tt>pm-utils</tt> scripts must be run as root, you may want to make the scripts accessible to normal users by running sudo without the root password. To do so, edit the {{Filename|/etc/sudoers}} file with {{Codeline|visudo}}, for example:<br />
<br />
# visudo<br />
<br />
add the following lines, replacing ''username'' with your own:<br />
<br />
''username'' ALL = NOPASSWD: /usr/sbin/pm-hibernate<br />
''username'' ALL = NOPASSWD: /usr/sbin/pm-suspend<br />
<br />
save and exit visudo<br />
<br />
Or you can enable it for a group, using the following lines, of course replacing ''group'':<br />
<br />
''%group'' ALL = NOPASSWD: /usr/sbin/pm-hibernate<br />
''%group'' ALL = NOPASSWD: /usr/sbin/pm-suspend<br />
<br />
Note: These must come after any user privilege specifications, e.g., "username ALL=(ALL) ALL", or they won't work.<br />
<br />
You can now run the scripts without a password by simply typing:<br />
<br />
$ sudo pm-hibernate<br />
<br />
or <br />
<br />
$ sudo pm-suspend<br />
<br />
Also, add yourself to the ''power'' group so that way using things like applets to do suspend will work. If you do not do this, when you try to use suspend though things like the gnome shutdown applet to suspend/hibernate your computer will just play a very annoying loud triple beep and lock the screen.<br />
<br />
# gpasswd -a ''username'' power<br />
<br />
You should now be able to use gnome power management tools (and kpowersave?) to automatically suspend/hibernate when doing things like closing the laptop lid, running low on battery power etc...<br />
<br />
=== Power Management ===<br />
Write a custom [[acpid]] event:<br />
{{File|name=/etc/acpi/events/ac|content=<br />
event=ac_adapter.*<br />
action=/etc/acpi/actions/ac.sh %e<br />
}}<br />
<br />
Write a custom acpid action:<br />
{{File|name=/etc/acpi/actions/ac.sh|content=<br />
#!/bin/sh<br />
case "$4" in<br />
*0) /usr/sbin/pm-powersave true;;<br />
*1) /usr/sbin/pm-powersave false;;<br />
esac<br />
}}<br />
<br />
Be sure not to install {{Package Official|laptop-mode-tools}} since the rules may conflict.<br />
<br />
== Advanced Configuration ==<br />
The main configuration file is '''<tt>/usr/lib/pm-utils/defaults</tt>'''. You ''should not edit this file'', since after a package update it might be overwritten with the default settings. Put your config file into '''<tt>/etc/pm/config.d/</tt>''' instead.<br />
You can just put a simple text file with<br />
SUSPEND_MODULES="button uhci_hcd"<br />
named "modules" or "config" into <tt>/etc/pm/config.d</tt> and it will override the settings in the system wide configuration file.<br />
<br />
=== Available Variables for use in config files ===<br />
SUSPEND_MODULES="button" # the list of modules to be unloaded before suspend<br />
SLEEP_MODULE="tuxonice uswsusp kernel" # The default sleep/wake systems to try<br />
HIBERNATE_MODE="shutdown" # forces the system to shutdown rather than reboot<br />
<br />
=== Disabling a hook ===<br />
If a hook is run which you do not like or which you think is not useful or even harmful, we'd appreciate a bugreport for that.<br />
You can however easily disable hooks by just creating an empty file corresponding to the hook in <tt>/etc/pm/sleep.d/</tt>. Say you want to disable the hook <tt>/usr/lib/pm-utils/sleep.d/45pcmcia</tt>, you can do this easily by calling<br />
# touch /etc/pm/sleep.d/45pcmcia<br />
Do not set the executable bit on that dummy-hook.<br />
<br />
=== Creating your own hooks ===<br />
If you want to do something specific to your setup during suspend / hibernate, then you can easily put your own hook into <tt>/etc/pm/sleep.d</tt>. The hooks in this directory will be called in alphabetic order during suspend (that's the reason their names all start with 2 digits, to make the ordering explicit) and in the reverse order during resume.<br />
<br />
I'm showing a pretty useless demonstration hook here, that will just put some informative lines into your logfile:<br />
<br />
#!/bin/bash<br />
case $1 in<br />
hibernate)<br />
echo "Hey guy, we are going to suspend to disk!"<br />
;;<br />
suspend)<br />
echo "Oh, this time we're doing a suspend to RAM. Cool!"<br />
;;<br />
thaw)<br />
echo "oh, suspend to disk is over, we are resuming..."<br />
;;<br />
resume)<br />
echo "hey, the suspend to RAM seems to be over..."<br />
;;<br />
*) echo "somebody is calling me totally wrong."<br />
;;<br />
esac<br />
<br />
Put this into /etc/pm/sleep.d/66dummy, do a <tt>chmod +x /etc/pm/sleep.d/66dummy</tt> and it will spew some useless lines during suspend / resume.<br />
<br />
'''''Warning:''' All the hooks run as user root. This means that you need to be careful when creating temporary files, check that the PATH variable is set correctly etc. to avoid security problems.''<br />
<br />
== How it Works ==<br />
The concept is quite easy: the main script (<tt>pm-action</tt>, called via symlinks as either <tt>pm-suspend</tt>, <tt>pm-hibernate</tt> or <tt>pm-suspend-hybrid</tt>) executes so-called "hooks", executable scripts, in the alphabetical sorted order with the parameter <tt>suspend</tt> (suspend to RAM) or <tt>hibernate</tt> (suspend to disk).<br />
Once all hooks are done, it puts the machine to sleep. After the machine has woken up again, all those hooks are executed in reverse order with the parameter <tt>resume</tt> (resume from RAM) or <tt>thaw</tt> (resume from disk).<br />
The hooks do various stuff, for example preparing the bootloader, stopping the bluetooth subsystem or unloading of critical modules.<br />
<br />
Both pm-suspend and pm-hibernate are usually called from HAL, initiated by desktop applets as gnome-power-manager or kpowersave.<br />
<br />
{{Box Note|<tt>suspend-hybrid</tt> is a placeholder right now, it is not completely implemented.}}<br />
<br />
There is also the possibility to set the machine into high-power and low-power mode, the command <tt>pm-powersave</tt> is used with an additional parameter of <tt>true</tt> or <tt>false</tt>. It works basically the same as the suspend framework.<br />
<br />
The hooks for suspend are placed in<br />
* <tt>/usr/lib/pm-utils/sleep.d</tt> (distribution / package provided hooks)<br />
* <tt>/etc/pm/sleep.d</tt> (hooks added by the system administrator)<br />
<br />
The hooks for the power state are placed in <br />
* <tt>/usr/lib/pm-utils/power.d</tt> (distribution / package provided hooks)<br />
* <tt>/etc/pm/power.d</tt> (hooks added by the system administrator)<br />
<br />
Hooks in <tt>/etc/pm/</tt> take precedence over those in <tt>/usr/lib/pm-utils/</tt>, so the system administrator can override the defaults provided by the distribution.<br />
<br />
== Troubleshooting ==<br />
If suspend or hibernate did not work correctly, you will probably find some information in the logfile '''<tt>/var/log/pm-suspend.log</tt>''', for example which hooks were run and what the output of them was.<br />
<br />
=== Resume Hook ===<br />
<br />
It has been suggested that some systems, including those using [[LVM]], require the <tt>resume</tt> hook be added to the initrd image, otherwise the kernel will '''not''' resume. To do so, edit <tt>/etc/mkinitcpio.conf</tt> as root and add <tt>resume</tt> to the HOOKS array:<br />
HOOKS="base udev autodetect ide scsi sata lvm2 '''''resume''''' filesystems "<br />
<br />
Note that this is an example, and your HOOKS array may look different.<br />
<br />
<tt>resume</tt> must be placed ''after'' 'ide', 'scsi', 'sata' and/or 'lvm2', but before 'filesystems'. Of course there has to be an appropriate 'resume' file in /lib/initcpio/hooks, it should already be there, as it is part of the package 'mkinitcpio'.<br />
<br />
Finally, you must rebuild the initrd image for these changes to take effect:<br />
<br />
# mkinitcpio -p kernel26<br />
<br />
{{Box Note|If you use a custom kernel then you might have to change the value of the '-p' option.}}<br />
<br />
=== Set UUID === <br />
<br />
If you experience segmentation faults that might result in an unresponsive system and missing keys then try to set the UUID in the resume-path in '''/boot/grub/menu.lst''' as explained [[http://wiki.archlinux.org/index.php/Pm-utils#Hibernation_.28suspend2disk.29 above]].<br />
<br />
=== Intel Audio Powersave ===<br />
<br />
There's an error in {{Filename|/usr/lib/pm-utils/power.d/intel-audio-powersave}}. The <tt>for dev</tt> and <tt>printf</tt> lines are incorrect. Instead, they should be:<br />
<br />
for dev in /sys/module/snd_*; do<br />
<br />
and<br />
<br />
printf "Setting power savings for %s to %s..." "${dev##*/}" "$1"<br />
<br />
Now when all the hooks run on a <tt>pm-powersave</tt> run, Intel HDA audio components will be included.<br />
<br />
=== Reboot instead of resume from suspend ===<br />
<br />
This problem started when was introduced (in 2.6.35-rc4) saving NVS area during suspend (http://www.spinics.net/lists/linux-acpi/msg29521.html). However, it is known that this mechanism does not work on all machines, so the kernel developers allow the user to disable it with the help of the 'acpi_sleep=nonvs' kernel command line option. This option could be pass to the kernel through grub options editing the file /boot/grub/menu.lst (grub 0.97) on kernel line.<br />
<br />
== Tips and Tricks / FAQ ==<br />
=== Triggering suspend manually ===<br />
If you want to trigger suspend manually for debugging, without using HAL and other frameworks, call '''<tt>pm-suspend</tt>''' or '''<tt>pm-hibernate</tt>''' as root.<br />
=== Automatically deactivate kwin compositing before suspend===<br />
<br />
at the moment pm-suspend fails to resume with garbled screen when you resume from suspend with active AIGLX clients, such as kwin compositing (only ati-catalyst?).<br />
To automatically deactivate kwin compositing add a new hook under /etc/pm/sleep.d/00togglecompositing with this content:<br />
<br />
#!/bin/bash<br />
USER=`finger|grep '*:0'|grep -o '^\w*'`<br />
DBUS_SESSION_BUS_ADDRESS=`grep -o 'DBUS_SESSION_BUS_ADDRESS=.*' /home/$USER/.dbus/session-bus/*|sed s/DBUS_SESSION_BUS_ADDRESS=//`<br />
case $1 in<br />
hibernate)<br />
;;<br />
suspend)<br />
if `sudo -u $USER -i DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS qdbus org.kde.kwin /KWin compositingActive`;<br />
then<br />
sudo -u $USER -i DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS qdbus org.kde.kwin /KWin toggleCompositing;<br />
sleep 1<br />
fi<br />
;;<br />
thaw)<br />
;;<br />
resume)<br />
sudo -u $USER -i DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS qdbus org.kde.kwin /KWin toggleCompositing;<br />
;;<br />
*) echo "somebody is calling me totally wrong."<br />
;;<br />
esac<br />
<br />
I don't know if it's very secure or if it can be done simpler. Feel free to add better versions.<br />
<br />
If you are having trouble getting the above script to work, you can try my version. This version removes the use of finger, and fixes the DBUS_SESSION_BUS_ADDRESS resolution which did not work for me (though my solution is admittedly quite dirty). Simply replace the first three lines with:<br />
<br />
#!/bin/bash<br />
USER=`who | grep ':0' | grep -o '^\w*' | head -n1`<br />
. /home/$USER/.dbus/session-bus/*<br />
<br />
=== Using another sleep backend (like uswsusp) ===<br />
Create a file with a SLEEP_MODULE variable, like this:<br />
$ cat /etc/pm/config.d/module <br />
SLEEP_MODULE=uswsusp<br />
To list available modules, use:<br />
$ pacman -Ql pm-utils | grep module.d<br />
<br />
=== Having the hd power management level automatically set again on resume ===<br />
Do it like this:<br />
$ cat /etc/pm/sleep.d/50-hdparm_pm <br />
#!/bin/dash<br />
<br />
if [ -n "$1" ] && ([ "$1" = "resume" ] || [ "$1" = "thaw" ]); then<br />
hdparm -B 254 /dev/sda > /dev/null<br />
fi<br />
<br />
=== Restarting the mouse ===<br />
On some laptops the mouse will hang after an otherwise successful suspend. One way to remedy this is to force a reinit of the PS/2 driver (here <tt>i8042</tt>) through a hook in <tt>/etc/pm/hooks</tt> (see [[#Creating_your_own_hooks|hooks]])<br />
<br />
#!/bin/sh <br />
echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind<br />
echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind<br />
<br />
=== It seems to not do anything / where is the logfile ===<br />
If it seem to not do anything when called via the desktop applets, then try to call <tt>pm-suspend</tt> or <tt>pm-hibernate</tt> [[#Triggering_suspend_manually|manually from a root shell in a terminal]]. Maybe you'll already get some output that will point you to the problem.<br />
The suspend scripts also write a [[#Troubleshooting|logfile at '''<tt>/var/log/pm-suspend.log</tt>''']].<br />
<br />
=== Add sleep modes to Openbox menu ===<br />
Openbox users can add the new scripts as additional shutdown options within the Openbox menu by adding the items to a new or existing sub-menu in <tt>~/.config/openbox/menu.xml</tt>, for example:<br />
<menu id="64" label="Shutdown"><br />
<item label="Lock"> <action name="Execute"> <execute>xscreensaver-command -lock</execute> </action> </item><br />
<item label="Logout"> <action name="Exit"/> </item><br />
<item label="Reboot"> <action name="Execute"> <execute>sudo shutdown -r now</execute> </action> </item><br />
<item label="Poweroff"> <action name="Execute"> <execute>sudo shutdown -h now </execute> </action> </item><br />
'''''<item label="Hibernate"> <action name="Execute"> <execute>sudo pm-hibernate</execute> </action> </item>'''''<br />
'''''<item label="Suspend"> <action name="Execute"> <execute>sudo pm-suspend</execute> </action> </item>'''''<br />
</menu><br />
<br />
=== Blank screen issue ===<br />
Some users have reported having issues with their laptops not resuming after a suspend or hibernate. This is due to the autodetect HOOK. This can be disabled using the same method for adding the resume HOOK. Just remove autodetect from the list and follow the steps to build the new image. See [http://wiki.archlinux.org/index.php/Pm-utils#Resume_Hook Resume Hook] for more details on building the new image.<br />
<br />
=== Handling "sleep" and "power" buttons ===<br />
"Sleep" and "power" buttons are handled by acpid in /etc/acpi/handler.sh (see "button/power" and "power/sleep" entries). You may want to substitute the default actions with calls to pm-suspend and pm-hibernate.<br />
<br />
=== [[HAL]] will not recognize new devices on resume ===<br />
With the 2.6.30 kernel, HAL will on some systems bug on resume, not recognizing new USB devices. Adding the following bash script with a name like "02hal" to /etc/pm/sleep.d works around the problem by stopping HAL and starting it again after resuming.<br />
<br />
#!/bin/bash<br />
case $1 in<br />
hibernate)<br />
;;<br />
suspend)<br />
/etc/rc.d/hal stop<br />
;;<br />
thaw)<br />
;;<br />
resume)<br />
/etc/rc.d/hal start<br />
;;<br />
*)<br />
;;<br />
esac<br />
<br />
Remember to mark it executable with "chmod +x 02hal".<br />
<br />
== Other Resources ==<br />
* [https://wiki.ubuntu.com/UnderstandingSuspend Understanding Suspend] - Ubuntu article explaining how suspend-to-ram works<br />
*[[Cpufrequtils]] - CPU Frequency Scaling and CPU Power schemes<br />
*[[Acpid]] - daemon for delivering ACPI events.<br />
<br />
== Credits ==<br />
''This wiki entry was originally sourced from the [http://en.opensuse.org/Pm-utils OpenSUSE Wiki] (Licensed under GPL). A big thank you goes to the <tt>pm-utils</tt> developers and documenters for their time.''</div>
Cantabile
https://wiki.archlinux.org/index.php?title=TuxOnIce&diff=125535
TuxOnIce
2010-12-18T17:53:46Z
<p>Cantabile: Added box with summary + related articles</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|Tuxonice}}<br />
{{i18n_entry|Italiano|Tuxonice (Italiano)}}<br />
{{i18n_links_end}}<br />
[[Category:Power management (English)]]<br />
[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{Article summary start}}<br />
{{Article summary text|Describes installing, configuring and using tuxonice, an advanced suspend/hibernate framework.}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|Pm-utils}}<br />
{{Article summary wiki|Uswsusp}}<br />
{{Article summary end}}<br />
This is a quick start guide for installing [http://www.tuxonice.net Tuxonice] (formerly suspend2), an advanced suspend/hibernate framework which supports suspending to a swap-disk or a regular file with fast LZO-compression. Visit the Tuxonice website for a full list of [http://www.tuxonice.net/features features].<br />
<br />
=Preparing the kernel=<br />
<br />
Tuxonice consists of a kernel patch, plus an optional user interface. Only the kernel patch is necessary, the user interface merely provides a graphical interface displayed during the hibernation/resume cycle. <br />
<br />
You can use the [http://aur.archlinux.org/packages.php?ID=15224 kernel26-ice] package in the [[AUR]]. It automatizes all the patch routines, the compilation and installation of the kernel, the regeneration of the initramfs with an appropriate hook.<br />
<br />
You can build the package manually, see [[AUR_User_Guidelines#Installing_Packages_from_the_AUR | Installing packages from the AUR]] for more information. This is better as you maintain more control over the install process, plus its easier to make changes if you want to repeat the process. Alternatively, you can use [[Yaourt]]:<br />
<br />
# yaourt -S kernel26-ice<br />
<br />
Otherwise, you need to patch, configure and compile your own kernel, visit [[Kernel Compilation From Source]] and [[Kernel Compilation with ABS]] for instructions. The required patch can be obtained from the Tuxonice website mentioned above.<br />
<br />
Next, you may need to run [[mkinitcpio]], which create the ram disk for you:<br />
<br />
# mkinitcpio -p kernel26-ice<br />
<br />
Next, install the hibernate-script package from the Extra repository which we will use to call Tuxonice. Hibernate-script is the default script developed by the Tuxonice development team:<br />
<br />
# pacman -S hibernate-script<br />
<br />
The configuration files for hibernate-script are in /etc/hibernate, we will get back to them shortly.<br />
<br />
=Setting up the bootmanager=<br />
Before your can use the suspend function, you need to add the "resume" parameter in your bootmanager, unless you have hardcoded your swap partition during the kernel configuration. The resume parameter points to the swap partition or swap file, below are the steps involved for both methods.<br />
<br />
==Suspend to swap partition==<br />
{{Note|As of the latest version of TuxOnIce (3.0.99.44), adding the kernel resume parameter is no longer necessary, it will autodetect if your swap drive contains a bootable image. You only need to set the swap method appropriately. For more details, check out http://www.tuxonice.net/<br />
}}<br />
<br />
Set the swap method (make sure the right partition is indicated) in /etc/hibernate/tuxonice.conf:<br />
<br />
SuspendDevice swap:/dev/sda3<br />
<br />
==Suspend to file==<br />
For the file allocator, you will have to prepare a hibernation file. First configure the /etc/hibernate/tuxonice.conf file, uncomment the "FilewriterLocation" option:<br />
<br />
FilewriterLocation /suspend_file 1000<br />
<br />
1000 is the amount of diskspace reserved for the hibernation file, in this case 1000 Megabytes. Usually an amount of 50% - 75% of your total amount of RAM will suffice.<br />
<br />
Next, run the following command to create the hibernation file:<br />
<br />
# hibernate --no-suspend<br />
<br />
Take a look in /sys/power/tuxonice/resume for what to pass to your kernel. You should see something like file:/dev/hda7:0x10011f, in which case you should append "resume=file:/dev/hda7:0x10011f" as a kernel parameter in your lilo.conf file or GRUB's menu.lst.<br />
<br />
=Recreating the initramfs=<br />
{{Note|Resuming doesn't work with mkinitcpio 0.5.25 (this is still true as of version 0.5.28) due to a bug in /lib/initcpio/hooks/resume.<br />
As a workaround downgrade to version 0.5.24 or replace the 6th line in /lib/initcpio/hooks/resume by<br />
resumedevice&#61;${resume#*:}<br />
resumedevice&#61;${resumedevice%:*}<br />
if [ -n "${resumedevice}" ] && poll_device "${resumedevice}" ${rootdelay}; then<br />
('''Note:''' there must be a space between the opening bracket and the '-n' in the last line above.)<br />
}}<br />
If you use an initramfs, you need to add the resume hook in the HOOKS in the configuration of mkinitcpio. Additionally, if you want to speed things up by using LZO compression, add the lzo module to the MODULES array in the same file.<br />
<br />
/etc/mkinitcpio.conf example:<br />
<br />
MODULES="lzo"<br />
HOOKS="base udev autodetect pata scsi sata resume filesystems"<br />
<br />
Rebuild the initramfs:<br />
<br />
# mkinitcpio -p kernel26-ice<br />
<br />
=Suspending and resuming=<br />
With hibernate-script, your preferred hibernation method can be set in the file /etc/hibernate/hibernate.conf. If you list several methods, the first one will be used. Note that ''hibernate'' can also be used with [[Suspend to RAM]] or vanilla swsusp, but this is not part of this guide.<br />
<br />
For Tuxonice use: <br />
<br />
TryMethod tuxonice.conf<br />
<br />
Specific settings for Tuxonice are in /etc/hibernate/tuxonice.conf. Make sure that the following lines are uncommented and appropriately configured:<br />
<br />
UseTuxOnIce yes<br />
Compressor lzo<br />
<br />
There are a number of additional settings and tweaks which you can set in /etc/hibernate/tuxonice.conf and /etc/hibernate/common.conf, more information about these can be found on the [http://www.tuxonice.net/HOWTO-4.html Tuxonice] website and on the [[Suspend_to_Disk | Suspend to Disk]] page of this wiki.<br />
<br />
Now try Tuxonice hibernation with the following method:<br />
<br />
# hibernate -F /etc/hibernate/tuxonice.conf<br />
<br />
You can abort a suspend cycle if you press the escape key. If you press a capital R, you will force the system to reboot after hibernation.<br />
<br />
If all goes well, you should be able to resume using the same Grub menu selection. If you make that option the default for Grub, you will always default to resuming if a resume image is available. '''Do never use a different kernel to resume than you used to suspend! If pacman updates your kernel, don't suspend before you have rebooted properly.''' It is recommended that you test the suspend/hibernate from a text console first and then once you have confirmed that it works try it from within X.<br />
<br />
You can make this practice safer adding the hibernate-cleanup daemon to your DAEMONS array in /etc/rc.conf. This script will make sure that any stale image is deleted from your swap partition at boot time. This should make your system safe also in the case that you have chosen the mistaken kernel at the grub prompt. The hibernate-cleanup service is included in the hibernate-script package.<br />
<br />
=Using userui - a user interface for Tuxonice (optional)=<br />
<br />
Optionally, you can use a text or graphical (fbsplash) interface with a progress bar with tuxonice. To do this, install the tuxonice-userui package from the AUR. This package depends on the static freetype2 library that is provided by freetype2-static (also in the AUR).<br />
<br />
In /etc/hibernate/tuxonice.conf, set the desired user interface:<br />
<br />
ProcSetting user_interface/program /usr/sbin/tuxoniceui_text # Text interface<br />
<br />
or<br />
<br />
ProcSetting user_interface/program /usr/sbin/tuxoniceui_fbsplash # Graphical fbsplash interface<br />
<br />
The fbsplash interface also needs a symlink to the fbsplash theme, like so:<br />
# ln -s /etc/splash/arch-banner-noicons/ /etc/splash/tuxonice<br />
Without this symlink, there will be no progress indicators during suspend/resume.<br />
<br />
It is probably necessary to regenerate the initramfs after changing the symlink above.<br />
<br />
The text interface may be good for debugging tuxonice, as it displays some messages.<br />
You won't see a user interface for the first few seconds of the resume process unless you add the ''userui'' hook to your mkinitcpio (before the ''resume'' hook) configuration and regenerate your initramfs, but this is also optional. <br />
<br />
Generate initramfs:<br />
<br />
# mkinitcpio -p kernel26-ice<br />
<br />
To test if userui works, switch to a text console and run:<br />
<br />
# tuxoniceui_text --test<br />
<br />
For the graphical interface run:<br />
<br />
# tuxoniceui_fbsplash --test<br />
<br />
=References=<br />
<br />
*The [http://www.tuxonice.net Tuxonice website] and [http://wiki.tuxonice.net/ Tuxonice wiki] are excellent sources of documentation.<br />
*More general information about suspend/hibernate with hibernate-script can be found on the [[Suspend_to_Disk | Suspend to Disk]] page of this wiki. This also covers some advanced topics like problems with specific hardware and configurations.<br />
*Another good source of information is the [http://en.gentoo-wiki.com/wiki/TuxOnIce Gentoo wiki]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Uswsusp&diff=125530
Uswsusp
2010-12-18T16:44:57Z
<p>Cantabile: Created page with "Category:Power management (English) Category:HOWTOs (English) {{i18n|uswsusp}} {{Article summary start}} {{Article summary text|Describes installing, configuring and usin..."</p>
<hr />
<div>[[Category:Power management (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|uswsusp}}<br />
{{Article summary start}}<br />
{{Article summary text|Describes installing, configuring and using uswsusp, a set of userspace tools used for suspending to disk and/or to RAM.}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|Pm-utils}}<br />
{{Article summary wiki|Tuxonice}}<br />
{{Article summary end}}<br />
<br />
uswsusp (userspace software suspend) is a set of user space tools used for hibernation (suspend-to-disk) and suspend (suspend-to-RAM or standby) on Linux systems.<br />
It consists of:<br />
* '''s2ram''' - a wrapper around the kernel's suspend-to-RAM mechanism allowing the user to perform some graphics adapter manipulations from the user land before suspending and after resuming that may help to bring the graphics (and the entire system) back to life after the resume. Incorporates the functionality of vbetool and radeontool as well as some tricks of its own. Includes a list of working hardware configurations along with the appropriate sets of operations to be performed to resume them successfully.<br />
<br />
* '''s2disk''' - the reference implementation of the userspace software suspend (µswsusp); it coordinates the steps necessary to suspend the system (such as freezing the processes, preparing the swap space, etc.) and handles image writing and reading. s2disk already supports compression and encryption of the image and other features (e.g. a nice progress bar, saving the image on a remote disk, playing tetris while resuming, etc.) can be easily added.<br />
<br />
* '''s2both''' - combines the funtionalities of s2ram and s2disk and it's very useful when the battery is almost depleted. s2both writes the system snapshot to the swap (just like s2disk) but then puts the machine into STR (just like s2ram). If the battery has enough power left you can quickly resume from STR, otherwise you can still resume from disk without losing your work. <br />
<br />
<br />
== Installation ==<br />
<br />
uswsusp is available in the [[AUR]] under the name [https://aur.archlinux.org/packages.php?ID=44473 uswsusp-git].<br />
<br />
== Configuration ==<br />
<br />
You must edit {{Filename|/etc/suspend.conf}} before attempting to suspend to disk.<br />
<br />
* If using a swap partition:<br />
resume device = /dev/disk/by-label/swap<br />
<br />
where {{Filename|/dev/disk/by-label/swap}} must be replaced with the correct block device containing the swap partition.<br />
<br />
* If using a [[Swap#swap_file|swap file]]:<br />
resume device = /partition/containing/swap/file<br />
resume offset = 123456<br />
<br />
where 123456 is the offset from the beginning of the resume device where the swap file's header is located.<br />
The resume offset can be obtained by running<br />
<br />
# swap-offset your-swap-file<br />
<br />
* The <code>image size</code> parameter (optional) can be used to limit the size of the system snapshot image created by s2disk. If it's not possible to create an image of the desired size, s2disk will suspend anyway, using a bigger image. If image size is set to 0, the image will be as small as possible.<br />
<br />
* The <code>shutdown method</code> parameter (optional) specifies the operation that will be carried out when the machine is ready to be powered off. If set to "reboot" the machine will be rebooted immediately. If set to "platform" the machine will be shut down using special power management operations available from the kernel that may be necessary for the hardware to be properly reinitialized after the resume, and may cause the system to resume faster.<br />
<br />
* If the <code>compute checksum</code> parameter is set to 'y', the s2disk and resume tools will use the MD5 algorithm to verify the image integrity.<br />
<br />
* If the <code>compress</code> parameter is set to 'y', the s2disk and resume tools will use the LZF compression algorithm to compress/decompress the image.<br />
<br />
* If <code>splash</code> is set to 'y', s2disk and/or resume will use a splash system. Currently splashy and fbsplash are supported. {{Note|This requires additional <code>configure</code> flags for uswsusp (<code>--enable-splashy</code> and <code>--enable-fbsplash</code>, respectively).}}<br />
<br />
* The <code>resume pause</code> option will introduce a delay after successfully resuming from hibernation, in order to allow the user to read the stats (read and write speed, image size, etc.)<br />
<br />
* If <code>threads</code> is enabled, s2disk will use several threads for compressing, encrypting and writing the image. This is supposed to speed things up. For details, read the comments in [http://git.kernel.org/?p=linux/kernel/git/rafael/suspend-utils.git;a=blob;f=suspend.c;h=166a62f03ea9daaba271e7cebf94c76881d4266f;hb=HEAD suspend.c]<br />
<br />
=== Sample config ===<br />
<br />
{{File|name=/etc/suspend.conf|content=<br />
snapshot device = /dev/snapshot<br />
<br />
resume device = /dev/disk/by-label/swap<br />
<br />
# image size is in bytes<br />
image size = 1468006400<br />
<br />
#suspend loglevel = 2<br />
<br />
compute checksum = y<br />
<br />
compress = y<br />
<br />
#encrypt = y<br />
<br />
#early writeout = y<br />
<br />
#splash = y<br />
<br />
# up to 60 (seconds)<br />
#resume pause = 30 <br />
<br />
threads = y<br />
}}<br />
<br />
== Usage ==<br />
<br />
=== Standalone ===<br />
<br />
To suspend to disk, run:<br />
<br />
# s2disk<br />
<br />
To suspend to ram, first run:<br />
<br />
# s2ram --test<br />
<br />
to see if your machine is in the database of machines known to work. If it returns something like "Machine matched entry xyz" then go ahead and run:<br />
<br />
# s2ram<br />
<br />
Otherwise, the --force parameter will be necessary, possibly combined with other parameters (see {{Codeline|s2ram --help}}). It may fail.<br />
<br />
=== With pm-utils ===<br />
<br />
[[Pm-utils]] can utilise several [[Pm-utils#Using_another_sleep_backend_.28like_uswsusp.29|sleep back-ends]], including uswsusp. Create or edit {{Filename|/etc/pm/config.d/module}}:<br />
SLEEP_MODULE=uswsusp<br />
<br />
This way, pm-suspend and pm-hibernate will use uswsusp.<br />
There is an advantage to this: regular users can use these commands to suspend with uswsusp:<br />
<br />
$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend<br />
<br />
$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate<br />
{{Note|The user's [[Window Manager|window manager]] or [[Desktop Environment|desktop environment]] needs to be started either with a [[Display Manager|login manager]] like gdm or kdm, or with <code>exec ck-launch-session <window-manager></code>. Also, upower needs to be installed.}}<br />
<br />
== Further reading ==<br />
<br />
Most of this page is adapted/copied from the [http://git.kernel.org/?p=linux/kernel/git/rafael/suspend-utils.git;a=blob;f=HOWTO;h=116cddaa76cbdec69eb8b1e87b7df8931d3a73da;hb=HEAD HOWTO file] included with the source code. <br /><br />
The introduction is from http://suspend.sourceforge.net/intro.shtml</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Pm-utils&diff=125527
Pm-utils
2010-12-18T14:59:10Z
<p>Cantabile: /* Using another sleep backend (like uswsusp) */ /etc/pm/config.d/module doesn't need to be executable</p>
<hr />
<div>[[Category:Power management (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|pm-utils}} {{DISPLAYTITLE:pm-utils}}<br />
<br />
'''pm-utils''' is the new suspend and powerstate setting framework. It is designed to replace such scripts as those provided by the <tt>powersave</tt> package.<br />
<br />
It is usually used by HAL to execute the various hacks needed to work around bugs in drivers and subsystems that are not yet aware of suspend. It is easily extensible by putting custom hooks into a directory, which can either be done by the system administrator or those hooks can be part of a package, especially if this package needs special attention during a system suspend or power state transition.<br />
<br />
A lesser known feature is one that mimmicks toggling done by [[Laptop Mode Tools]].<br />
<br />
Used in conjunction with the [[cpufrequtils]] package, notebook (and desktop) owners are provided with a complete power management suite.<br />
<br />
== Installation ==<br />
<br />
The <tt>pm-utils</tt> package is now available from the [http://www.archlinux.org/packages/search/?q=pm-utils Extra] repository:<br />
# pacman -S pm-utils<br />
<br />
{{note|If you run into issues when resuming video, it might be necessary to also sync <tt>vbetool</tt> from [extra].}}<br />
<br />
{{note|If you are starting from a clean install, make sure that you have <tt>acpi</tt> installed.}}<br />
<br />
== Basic Configuration ==<br />
=== Hibernation (suspend2disk) ===<br />
In order for suspend2disk (hibernate) to work, we need to edit ''/boot/grub/menu.lst'' as root and add '''resume=/path/to/swap/drive''' (e.g. /dev/sda2) to the kernel options, for example:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 '''resume=/dev/sda2''' ro vga=0<br />
initrd /kernel26.img<br />
<br />
Raid swap example:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/md2 resume=/dev/md0 ro md=0,/dev/sda2,/dev/sdb2 md=2,/dev/sda5,/dev/sdb5 vga=773<br />
initrd /kernel26.img<br />
<br />
If you want to use the UUID of the device instead then use the following example. The UUID itself can by find out by using the blkid command as root.<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 cryptdevice=/dev/sda2:main root=/dev/mapper/main-root resume=/dev/disk/by-uuid/1d893194-b151-43cd-a89e-6f89bd8b9f99 ro<br />
initrd /kernel26.img<br />
<br />
When the machine is placed into hibernation, it will now move all data from RAM to the swap partition... you ''did'' make your swap partition large enough to hold your RAM data, right?<br />
<br />
Even if your swap partition is smaller than RAM, you still have a big chance in hibernating successfully. According to [http://www.mjmwired.net/kernel/Documentation/power/interface.txt kernel documentation], ''/sys/power/image_size controls the size of the image created by the suspend-to-disk mechanism'', which has a default value of 500M. ''The suspend-to-disk mechanism will do its best to ensure the image size will not exceed that number.'' You may either decrease it due to a small swap partition or increase it in purpose of possible hibernation speed up.<br />
<br />
{{Box Note|'''''You may have to add the resume hook to mkinitcpio, see [[Pm-utils#Resume_Hook|below]]!'''''}}<br />
<br />
=== Suspend/Hibernate as regular user ===<br />
<br />
Three methods are available to suspend without the need for a root password: using HAL, using UPower, and giving the user permissions with visudo.<br />
<br />
==== UPower method ====<br />
<br />
To suspend to RAM:<br />
<br />
<pre><br />
$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" \<br />
/org/freedesktop/UPower org.freedesktop.UPower.Suspend<br />
</pre><br />
<br />
To suspend to disk (hibernate):<br />
<br />
<pre><br />
$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" \<br />
/org/freedesktop/UPower org.freedesktop.UPower.Hibernate<br />
</pre><br />
<br />
==== HAL Method ====<br />
<br />
HAL can be invoked as regular user to suspend by:<br />
<br />
<pre>$ dbus-send --system --print-reply --dest=org.freedesktop.Hal \<br />
/org/freedesktop/Hal/devices/computer \<br />
org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0</pre><br />
<br />
and Hibernate by:<br />
<br />
<pre>$ dbus-send --system --print-reply --dest=org.freedesktop.Hal \<br />
/org/freedesktop/Hal/devices/computer \<br />
org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate</pre><br />
<br />
==== User Permission Method ====<br />
<br />
Because the <tt>pm-utils</tt> scripts must be run as root, you may want to make the scripts accessible to normal users by running sudo without the root password. To do so, edit the {{Filename|/etc/sudoers}} file with {{Codeline|visudo}}, for example:<br />
<br />
# visudo<br />
<br />
add the following lines, replacing ''username'' with your own:<br />
<br />
''username'' ALL = NOPASSWD: /usr/sbin/pm-hibernate<br />
''username'' ALL = NOPASSWD: /usr/sbin/pm-suspend<br />
<br />
save and exit visudo<br />
<br />
Or you can enable it for a group, using the following lines, of course replacing ''group'':<br />
<br />
''%group'' ALL = NOPASSWD: /usr/sbin/pm-hibernate<br />
''%group'' ALL = NOPASSWD: /usr/sbin/pm-suspend<br />
<br />
Note: These must come after any user privilege specifications, e.g., "username ALL=(ALL) ALL", or they won't work.<br />
<br />
You can now run the scripts without a password by simply typing:<br />
<br />
$ sudo pm-hibernate<br />
<br />
or <br />
<br />
$ sudo pm-suspend<br />
<br />
Also, add yourself to the ''power'' group so that way using things like applets to do suspend will work. If you do not do this, when you try to use suspend though things like the gnome shutdown applet to suspend/hibernate your computer will just play a very annoying loud triple beep and lock the screen.<br />
<br />
# gpasswd -a ''username'' power<br />
<br />
You should now be able to use gnome power management tools (and kpowersave?) to automatically suspend/hibernate when doing things like closing the laptop lid, running low on battery power etc...<br />
<br />
=== Power Management ===<br />
Write a custom [[acpid]] event:<br />
{{File|name=/etc/acpi/events/ac|content=<br />
event=ac_adapter.*<br />
action=/etc/acpi/actions/ac.sh %e<br />
}}<br />
<br />
Write a custom acpid action:<br />
{{File|name=/etc/acpi/actions/ac.sh|content=<br />
#!/bin/sh<br />
case "$4" in<br />
*0) /usr/sbin/pm-powersave true;;<br />
*1) /usr/sbin/pm-powersave false;;<br />
esac<br />
}}<br />
<br />
Be sure not to install {{Package Official|laptop-mode-tools}} since the rules may conflict.<br />
<br />
== Advanced Configuration ==<br />
The main configuration file is '''<tt>/usr/lib/pm-utils/defaults</tt>'''. You ''should not edit this file'', since after a package update it might be overwritten with the default settings. Put your config file into '''<tt>/etc/pm/config.d/</tt>''' instead.<br />
You can just put a simple text file with<br />
SUSPEND_MODULES="button uhci_hcd"<br />
named "modules" or "config" into <tt>/etc/pm/config.d</tt> and it will override the settings in the system wide configuration file.<br />
<br />
=== Available Variables for use in config files ===<br />
SUSPEND_MODULES="button" # the list of modules to be unloaded before suspend<br />
SLEEP_MODULE="tuxonice uswsusp kernel" # The default sleep/wake systems to try<br />
HIBERNATE_MODE="shutdown" # forces the system to shutdown rather than reboot<br />
<br />
=== Disabling a hook ===<br />
If a hook is run which you do not like or which you think is not useful or even harmful, we'd appreciate a bugreport for that.<br />
You can however easily disable hooks by just creating an empty file corresponding to the hook in <tt>/etc/pm/sleep.d/</tt>. Say you want to disable the hook <tt>/usr/lib/pm-utils/sleep.d/45pcmcia</tt>, you can do this easily by calling<br />
# touch /etc/pm/sleep.d/45pcmcia<br />
Do not set the executable bit on that dummy-hook.<br />
<br />
=== Creating your own hooks ===<br />
If you want to do something specific to your setup during suspend / hibernate, then you can easily put your own hook into <tt>/etc/pm/sleep.d</tt>. The hooks in this directory will be called in alphabetic order during suspend (that's the reason their names all start with 2 digits, to make the ordering explicit) and in the reverse order during resume.<br />
<br />
I'm showing a pretty useless demonstration hook here, that will just put some informative lines into your logfile:<br />
<br />
#!/bin/bash<br />
case $1 in<br />
hibernate)<br />
echo "Hey guy, we are going to suspend to disk!"<br />
;;<br />
suspend)<br />
echo "Oh, this time we're doing a suspend to RAM. Cool!"<br />
;;<br />
thaw)<br />
echo "oh, suspend to disk is over, we are resuming..."<br />
;;<br />
resume)<br />
echo "hey, the suspend to RAM seems to be over..."<br />
;;<br />
*) echo "somebody is calling me totally wrong."<br />
;;<br />
esac<br />
<br />
Put this into /etc/pm/sleep.d/66dummy, do a <tt>chmod +x /etc/pm/sleep.d/66dummy</tt> and it will spew some useless lines during suspend / resume.<br />
<br />
'''''Warning:''' All the hooks run as user root. This means that you need to be careful when creating temporary files, check that the PATH variable is set correctly etc. to avoid security problems.''<br />
<br />
== How it Works ==<br />
The concept is quite easy: the main script (<tt>pm-action</tt>, called via symlinks as either <tt>pm-suspend</tt>, <tt>pm-hibernate</tt> or <tt>pm-suspend-hybrid</tt>) executes so-called "hooks", executable scripts, in the alphabetical sorted order with the parameter <tt>suspend</tt> (suspend to RAM) or <tt>hibernate</tt> (suspend to disk).<br />
Once all hooks are done, it puts the machine to sleep. After the machine has woken up again, all those hooks are executed in reverse order with the parameter <tt>resume</tt> (resume from RAM) or <tt>thaw</tt> (resume from disk).<br />
The hooks do various stuff, for example preparing the bootloader, stopping the bluetooth subsystem or unloading of critical modules.<br />
<br />
Both pm-suspend and pm-hibernate are usually called from HAL, initiated by desktop applets as gnome-power-manager or kpowersave.<br />
<br />
{{Box Note|<tt>suspend-hybrid</tt> is a placeholder right now, it is not completely implemented.}}<br />
<br />
There is also the possibility to set the machine into high-power and low-power mode, the command <tt>pm-powersave</tt> is used with an additional parameter of <tt>true</tt> or <tt>false</tt>. It works basically the same as the suspend framework.<br />
<br />
The hooks for suspend are placed in<br />
* <tt>/usr/lib/pm-utils/sleep.d</tt> (distribution / package provided hooks)<br />
* <tt>/etc/pm/sleep.d</tt> (hooks added by the system administrator)<br />
<br />
The hooks for the power state are placed in <br />
* <tt>/usr/lib/pm-utils/power.d</tt> (distribution / package provided hooks)<br />
* <tt>/etc/pm/power.d</tt> (hooks added by the system administrator)<br />
<br />
Hooks in <tt>/etc/pm/</tt> take precedence over those in <tt>/usr/lib/pm-utils/</tt>, so the system administrator can override the defaults provided by the distribution.<br />
<br />
== Troubleshooting ==<br />
If suspend or hibernate did not work correctly, you will probably find some information in the logfile '''<tt>/var/log/pm-suspend.log</tt>''', for example which hooks were run and what the output of them was.<br />
<br />
=== Resume Hook ===<br />
<br />
It has been suggested that some systems, including those using [[LVM]], require the <tt>resume</tt> hook be added to the initrd image, otherwise the kernel will '''not''' resume. To do so, edit <tt>/etc/mkinitcpio.conf</tt> as root and add <tt>resume</tt> to the HOOKS array:<br />
HOOKS="base udev autodetect ide scsi sata lvm2 '''''resume''''' filesystems "<br />
<br />
Note that this is an example, and your HOOKS array may look different.<br />
<br />
<tt>resume</tt> must be placed ''after'' 'ide', 'scsi', 'sata' and/or 'lvm2', but before 'filesystems'. Of course there has to be an appropriate 'resume' file in /lib/initcpio/hooks, it should already be there, as it is part of the package 'mkinitcpio'.<br />
<br />
Finally, you must rebuild the initrd image for these changes to take effect:<br />
<br />
# mkinitcpio -p kernel26<br />
<br />
{{Box Note|If you use a custom kernel then you might have to change the value of the '-p' option.}}<br />
<br />
=== Set UUID === <br />
<br />
If you experience segmentation faults that might result in an unresponsive system and missing keys then try to set the UUID in the resume-path in '''/boot/grub/menu.lst''' as explained [[http://wiki.archlinux.org/index.php/Pm-utils#Hibernation_.28suspend2disk.29 above]].<br />
<br />
=== Intel Audio Powersave ===<br />
<br />
There's an error in {{Filename|/usr/lib/pm-utils/power.d/intel-audio-powersave}}. The <tt>for dev</tt> and <tt>printf</tt> lines are incorrect. Instead, they should be:<br />
<br />
for dev in /sys/module/snd_*; do<br />
<br />
and<br />
<br />
printf "Setting power savings for %s to %s..." "${dev##*/}" "$1"<br />
<br />
Now when all the hooks run on a <tt>pm-powersave</tt> run, Intel HDA audio components will be included.<br />
<br />
=== Reboot instead of resume from suspend ===<br />
<br />
This problem started when was introduced (in 2.6.35-rc4) saving NVS area during suspend (http://www.spinics.net/lists/linux-acpi/msg29521.html). However, it is known that this mechanism does not work on all machines, so the kernel developers allow the user to disable it with the help of the 'acpi_sleep=nonvs' kernel command line option. This option could be pass to the kernel through grub options editing the file /boot/grub/menu.lst (grub 0.97) on kernel line.<br />
<br />
== Tips and Tricks / FAQ ==<br />
=== Triggering suspend manually ===<br />
If you want to trigger suspend manually for debugging, without using HAL and other frameworks, call '''<tt>pm-suspend</tt>''' or '''<tt>pm-hibernate</tt>''' as root.<br />
=== Automatically deactivate kwin compositing before suspend===<br />
<br />
at the moment pm-suspend fails to resume with garbled screen when you resume from suspend with active AIGLX clients, such as kwin compositing (only ati-catalyst?).<br />
To automatically deactivate kwin compositing add a new hook under /etc/pm/sleep.d/00togglecompositing with this content:<br />
<br />
#!/bin/bash<br />
USER=`finger|grep '*:0'|grep -o '^\w*'`<br />
DBUS_SESSION_BUS_ADDRESS=`grep -o 'DBUS_SESSION_BUS_ADDRESS=.*' /home/$USER/.dbus/session-bus/*|sed s/DBUS_SESSION_BUS_ADDRESS=//`<br />
case $1 in<br />
hibernate)<br />
;;<br />
suspend)<br />
if `sudo -u $USER -i DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS qdbus org.kde.kwin /KWin compositingActive`;<br />
then<br />
sudo -u $USER -i DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS qdbus org.kde.kwin /KWin toggleCompositing;<br />
sleep 1<br />
fi<br />
;;<br />
thaw)<br />
;;<br />
resume)<br />
sudo -u $USER -i DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS qdbus org.kde.kwin /KWin toggleCompositing;<br />
;;<br />
*) echo "somebody is calling me totally wrong."<br />
;;<br />
esac<br />
<br />
I don't know if it's very secure or if it can be done simpler. Feel free to add better versions.<br />
<br />
If you are having trouble getting the above script to work, you can try my version. This version removes the use of finger, and fixes the DBUS_SESSION_BUS_ADDRESS resolution which did not work for me (though my solution is admittedly quite dirty). Simply replace the first three lines with:<br />
<br />
#!/bin/bash<br />
USER=`who | grep ':0' | grep -o '^\w*' | head -n1`<br />
. /home/$USER/.dbus/session-bus/*<br />
<br />
=== Using another sleep backend (like uswsusp) ===<br />
Create a file with a SLEEP_MODULE variable, like this:<br />
$ cat /etc/pm/config.d/module <br />
SLEEP_MODULE=uswsusp<br />
To list available modules, use:<br />
$ pacman -Ql pm-utils | grep module.d<br />
<br />
=== Having the hd power management level automatically set again on resume ===<br />
Do it like this:<br />
$ cat /etc/pm/sleep.d/50-hdparm_pm <br />
#!/bin/dash<br />
<br />
if [ -n "$1" ] && ([ "$1" = "resume" ] || [ "$1" = "thaw" ]); then<br />
hdparm -B 254 /dev/sda > /dev/null<br />
fi<br />
<br />
=== Restarting the mouse ===<br />
On some laptops the mouse will hang after an otherwise successful suspend. One way to remedy this is to force a reinit of the PS/2 driver (here <tt>i8042</tt>) through a hook in <tt>/etc/pm/hooks</tt> (see [[#Creating_your_own_hooks|hooks]])<br />
<br />
#!/bin/sh <br />
echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind<br />
echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind<br />
<br />
=== It seems to not do anything / where is the logfile ===<br />
If it seem to not do anything when called via the desktop applets, then try to call <tt>pm-suspend</tt> or <tt>pm-hibernate</tt> [[#Triggering_suspend_manually|manually from a root shell in a terminal]]. Maybe you'll already get some output that will point you to the problem.<br />
The suspend scripts also write a [[#Troubleshooting|logfile at '''<tt>/var/log/pm-suspend.log</tt>''']].<br />
<br />
=== Add sleep modes to Openbox menu ===<br />
Openbox users can add the new scripts as additional shutdown options within the Openbox menu by adding the items to a new or existing sub-menu in <tt>~/.config/openbox/menu.xml</tt>, for example:<br />
<menu id="64" label="Shutdown"><br />
<item label="Lock"> <action name="Execute"> <execute>xscreensaver-command -lock</execute> </action> </item><br />
<item label="Logout"> <action name="Exit"/> </item><br />
<item label="Reboot"> <action name="Execute"> <execute>sudo shutdown -r now</execute> </action> </item><br />
<item label="Poweroff"> <action name="Execute"> <execute>sudo shutdown -h now </execute> </action> </item><br />
'''''<item label="Hibernate"> <action name="Execute"> <execute>sudo pm-hibernate</execute> </action> </item>'''''<br />
'''''<item label="Suspend"> <action name="Execute"> <execute>sudo pm-suspend</execute> </action> </item>'''''<br />
</menu><br />
<br />
=== Blank screen issue ===<br />
Some users have reported having issues with their laptops not resuming after a suspend or hibernate. This is due to the autodetect HOOK. This can be disabled using the same method for adding the resume HOOK. Just remove autodetect from the list and follow the steps to build the new image. See [http://wiki.archlinux.org/index.php/Pm-utils#Resume_Hook Resume Hook] for more details on building the new image.<br />
<br />
=== Handling "sleep" and "power" buttons ===<br />
"Sleep" and "power" buttons are handled by acpid in /etc/acpi/handler.sh (see "button/power" and "power/sleep" entries). You may want to substitute the default actions with calls to pm-suspend and pm-hibernate.<br />
<br />
=== [[HAL]] will not recognize new devices on resume ===<br />
With the 2.6.30 kernel, HAL will on some systems bug on resume, not recognizing new USB devices. Adding the following bash script with a name like "02hal" to /etc/pm/sleep.d works around the problem by stopping HAL and starting it again after resuming.<br />
<br />
#!/bin/bash<br />
case $1 in<br />
hibernate)<br />
;;<br />
suspend)<br />
/etc/rc.d/hal stop<br />
;;<br />
thaw)<br />
;;<br />
resume)<br />
/etc/rc.d/hal start<br />
;;<br />
*)<br />
;;<br />
esac<br />
<br />
Remember to mark it executable with "chmod +x 02hal".<br />
<br />
== Other Resources ==<br />
* [https://wiki.ubuntu.com/UnderstandingSuspend Understanding Suspend] - Ubuntu article explaining how suspend-to-ram works<br />
*[[Cpufrequtils]] - CPU Frequency Scaling and CPU Power schemes<br />
*[[Acpid]] - daemon for delivering ACPI events.<br />
<br />
== Credits ==<br />
''This wiki entry was originally sourced from the [http://en.opensuse.org/Pm-utils OpenSUSE Wiki] (Licensed under GPL). A big thank you goes to the <tt>pm-utils</tt> developers and documenters for their time.''</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Xcompmgr&diff=122893
Xcompmgr
2010-11-28T19:07:40Z
<p>Cantabile: added 'related articles' box + various small corrections</p>
<hr />
<div>[[Category:X Server (English)]]<br />
[[Category:Eye candy (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|Xcompmgr}}<br />
{{Article summary start}}<br />
{{Article summary text|Describes the installation and usage of xcompmgr.}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|Cairo Compmgr}}<br />
{{Article summary wiki|Composite}}<br />
{{Article summary wiki|AIGLX}}<br />
{{Article summary wiki|Xgl}}<br />
{{Article summary wiki|Xorg}}<br />
{{Article summary wiki|Window Manager}}<br />
{{Article summary wiki|Openbox}}<br />
{{Article summary wiki|Fluxbox}}<br />
{{Article summary wiki|Awesome}}<br />
{{Article summary end}}<br />
Xcompmgr is a simple composite manager, capable of rendering drop shadows and, with the use of the {{Codeline|transset}} utility, primitive window transparency. Designed solely as a proof-of-concept, xcompmgr is a lightweight alternative to Compiz Fusion and similar composite managers.<br />
<br />
Because it does not replace any existing window manager, it is an ideal solution for [[Openbox]] and [[Fluxbox]] users seeking a more elegant desktop.<br />
<br />
== Prerequisites ==<br />
<br />
Xcompmgr requires the following:<br />
* [[Xorg]] must be installed, configured and running<br />
* [[Composite]] must be enabled via graphics drivers, [[AIGLX]], or [[Xgl]]<br />
<br />
== Installation ==<br />
<br />
Both {{Codeline|xcompmgr}} and the transparency tool {{Codeline|transset-df}}, are available from the standard repositories:<br />
# pacman -Syu xcompmgr transset-df<br />
<br />
== Configuration ==<br />
<br />
To load xcompmgr, simply run:<br />
$ xcompmgr -c<br />
<br />
To have it load at session start, add the following to [[xprofile]]:<br />
xcompmgr -c &<br />
<br />
Instead of {{Codeline|-c}} you can experiment with the other switches to modify the drop-shadows or even enable fading. Below is a common example:<br />
xcompmgr -c -t-5 -l-5 -r4.2 -o.55 &<br />
<br />
For a full list of options, run:<br />
$ xcompmgr --help<br />
<br />
=== Window Transparency ===<br />
<br />
Although its practical use is limited, due to its slow performance, the {{Codeline|transset}} utility can be used to set the transparency of individual windows.<br />
<br />
To set the transparency of a program window, make sure the desired program is already running, then execute:<br />
transset n<br />
.. where {{Codeline|n}} is a number from 0 to 1, zero being transparent and 1 being opaque.<br />
<br />
Once executed, the mouse cursor will transform to a crosshair. Simply click the desired window and the transparency will change to the value specified. For example, {{Codeline|transset .25}} will set the target window to 75% transparency.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Fluxbox windows won't raise ===<br />
<br />
This is fixed in fluxbox CVS after 0.9.10. See [http://freedesktop.org/bugzilla/show_bug.cgi?id=1264] for more info.<br />
<br />
A workaround in 0.9.10 is to set the layer of the Slit to "Desktop" (flux menu -> Configure -> Slit -> Layer -> Desktop).<br />
<br />
=== Mozilla Firefox crashes when entering a Flash site ===<br />
<br />
You can fix it by creating an executable file named {{Filename|/etc/profile.d/flash.sh}} containing this line:<br />
export XLIB_SKIP_ARGB_VISUALS=1<br />
<br />
=== Background turns light gray briefly after logging in (e.g. in Openbox) ===<br />
<br />
This is fixed by installing hsetroot (it's in AUR) and setting the background color by executing {{Codeline|hsetroot -solid "#000000"}} (just type the code of the colour you want instead of 000000) before xcompmgr.<br />
<br />
== Tips ==<br />
<br />
=== Starting/Stopping xcompmgr on Demand ===<br />
<br />
This script (e.g. in ~/bin) allows easy (re)starting and stopping of the compositing manager.<br />
#!/bin/bash<br />
#<br />
# Start a composition manager.<br />
# (xcompmgr in this case)<br />
<br />
function comphelp () {<br />
echo "Composition Manager:"<br />
echo " (re)start: COMP"<br />
echo " stop: COMP -s"<br />
echo " query: COMP -q"<br />
echo " returns 1 if composition manager is running, else 0"<br />
exit<br />
}<br />
<br />
function checkcomp () {<br />
( ps nc -C xcompmgr &>/dev/null ) && exit 1<br />
exit 0<br />
}<br />
<br />
function stopcomp () {<br />
( ps nc -C xcompmgr &>/dev/null ) && killall xcompmgr<br />
}<br />
<br />
function startcomp () {<br />
stopcomp<br />
# Example settings only. Replace with your own.<br />
xcompmgr -CcfF -I-.015 -O-.03 -D6 -t-1 -l-3 -r4.2 -o.5 &<br />
exit<br />
}<br />
<br />
case "$1x" in<br />
"x") startcomp;;<br />
"-qx") checkcomp;;<br />
"-sx") stopcomp; exit;;<br />
*) comphelp;;<br />
esac<br />
<br />
I bound COMP and COMP -s to two hot keys in IceWM because there are a few glitches using xcompmgr in this WM. This allows for fast restart or temporary composition removal if needed without interrupting other work.<br />
<br />
== Additional Resources ==<br />
*[[AIGLX]]<br />
*[[Xgl]]<br />
*[[Composite]] -- A Xorg extension required by composite managers<br />
*[[Compiz Fusion]] -- A composite and window manager offering a rich 3D accelerated desktop environment<br />
*[[Compiz]] -- The original composite/window manager from Novell<br />
*[[Xcompmgr]] -- A simple composite manager capable of drop shadows and primitive transparency<br />
*[[Cairo Compmgr | Cairo Composite Manager]] -- A versatile and extensible composite manager which uses cairo for rendering.<br />
*Wikipedia: [http://en.wikipedia.org/wiki/Compositing_window_manager Compositing Window Managers]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Hdparm&diff=122758
Hdparm
2010-11-27T10:45:42Z
<p>Cantabile: /* KDE => 4.4.4 and hdparm */ # or sudo, not both</p>
<hr />
<div>[[Category:File systems (English)]]<br />
Hdparm is a performance tool for your Hard Disk (SATA/IDE). Be careful, it's easy to destroy your HDD with hdparm!<br />
<br />
== Information ==<br />
<br />
hdparm is available in the [core] repository. For SCSI devices, take sdparm.<br />
<br />
To get information about your disk, just do:<br />
# hdparm -I /dev/sda<br />
<br />
== Reading speed MB/s ==<br />
<br />
To measure how many MB/s your Hard Disk (IDE/SATA) can read:<br />
# hdparm -t --direct /dev/sda<br />
<br />
=== Writing speed MB/s ===<br />
<br />
$ sync;time bash -c "(dd if=/dev/zero of=bf bs=8k count=500000; sync)"<br />
Don't forget to ctrl+c and rm bf after that.<br />
<br />
== Parking your HDD ==<br />
<br />
If your HDD is clicking many times, the kernel is parking the reading head of the HDD. This happens often on laptops (2.5" IDE HDDs). If it happens too often, it could damage your HDD.<br />
<br />
This will just park the reading head when you shutdown:<br />
# hdparm -B254 /dev/sd<br />
<br />
Default value is -B128. An average value could be -B199 if it's parking too often.<br />
<br />
== KDE => 4.4.4 and hdparm ==<br />
<br />
To stop KDE version 4.4.4 or greater from messing around with your (manually) set hdparm values, enter:<br />
<br />
# touch /etc/pm/power.d/harddrive<br />
<br />
and you should be done.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Hdparm&diff=122757
Hdparm
2010-11-27T10:45:13Z
<p>Cantabile: /* Parking your HDD */</p>
<hr />
<div>[[Category:File systems (English)]]<br />
Hdparm is a performance tool for your Hard Disk (SATA/IDE). Be careful, it's easy to destroy your HDD with hdparm!<br />
<br />
== Information ==<br />
<br />
hdparm is available in the [core] repository. For SCSI devices, take sdparm.<br />
<br />
To get information about your disk, just do:<br />
# hdparm -I /dev/sda<br />
<br />
== Reading speed MB/s ==<br />
<br />
To measure how many MB/s your Hard Disk (IDE/SATA) can read:<br />
# hdparm -t --direct /dev/sda<br />
<br />
=== Writing speed MB/s ===<br />
<br />
$ sync;time bash -c "(dd if=/dev/zero of=bf bs=8k count=500000; sync)"<br />
Don't forget to ctrl+c and rm bf after that.<br />
<br />
== Parking your HDD ==<br />
<br />
If your HDD is clicking many times, the kernel is parking the reading head of the HDD. This happens often on laptops (2.5" IDE HDDs). If it happens too often, it could damage your HDD.<br />
<br />
This will just park the reading head when you shutdown:<br />
# hdparm -B254 /dev/sd<br />
<br />
Default value is -B128. An average value could be -B199 if it's parking too often.<br />
<br />
== KDE => 4.4.4 and hdparm ==<br />
<br />
To stop KDE version 4.4.4 or greater from messing around with your (manually) set hdparm values, enter:<br />
<br />
# sudo touch /etc/pm/power.d/harddrive<br />
<br />
and you should be done.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Hdparm&diff=122755
Hdparm
2010-11-27T10:43:42Z
<p>Cantabile: /* Reading speed MB/s */</p>
<hr />
<div>[[Category:File systems (English)]]<br />
Hdparm is a performance tool for your Hard Disk (SATA/IDE). Be careful, it's easy to destroy your HDD with hdparm!<br />
<br />
== Information ==<br />
<br />
hdparm is available in the [core] repository. For SCSI devices, take sdparm.<br />
<br />
To get information about your disk, just do:<br />
# hdparm -I /dev/sda<br />
<br />
== Reading speed MB/s ==<br />
<br />
To measure how many MB/s your Hard Disk (IDE/SATA) can read:<br />
# hdparm -t --direct /dev/sda<br />
<br />
=== Writing speed MB/s ===<br />
<br />
$ sync;time bash -c "(dd if=/dev/zero of=bf bs=8k count=500000; sync)"<br />
Don't forget to ctrl+c and rm bf after that.<br />
<br />
== Parking your HDD ==<br />
<br />
If your HDD is clicking many times, the kernel is parking the reading head of the HDD. This happened often on Laptops (2.5" IDE HDDs). If it happend to often, it could damage your HDD.<br />
<br />
This will just parking the reading head when you shutdown.<br />
# hdparm -B254 /dev/sd<br />
<br />
Default value is -B128. A average value could be -B199 if it's parking to often.<br />
<br />
== KDE => 4.4.4 and hdparm ==<br />
<br />
To stop KDE version 4.4.4 or greater from messing around with your (manually) set hdparm values, enter:<br />
<br />
# sudo touch /etc/pm/power.d/harddrive<br />
<br />
and you should be done.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Hdparm&diff=122754
Hdparm
2010-11-27T10:42:23Z
<p>Cantabile: /* Information */ core repo, not base</p>
<hr />
<div>[[Category:File systems (English)]]<br />
Hdparm is a performance tool for your Hard Disk (SATA/IDE). Be careful, it's easy to destroy your HDD with hdparm!<br />
<br />
== Information ==<br />
<br />
hdparm is available in the [core] repository. For SCSI devices, take sdparm.<br />
<br />
To get information about your disk, just do:<br />
# hdparm -I /dev/sda<br />
<br />
== Reading speed MB/s ==<br />
<br />
To measure how many MB/s your Hard Disk (IDE/SATA) can read.<br />
# hdparm -t --direct /dev/sda<br />
<br />
=== Writing speed MB/s ===<br />
<br />
$ sync;time bash -c "(dd if=/dev/zero of=bf bs=8k count=500000; sync)"<br />
Don't forget to ctrl+c and rm bf after that.<br />
<br />
== Parking your HDD ==<br />
<br />
If your HDD is clicking many times, the kernel is parking the reading head of the HDD. This happened often on Laptops (2.5" IDE HDDs). If it happend to often, it could damage your HDD.<br />
<br />
This will just parking the reading head when you shutdown.<br />
# hdparm -B254 /dev/sd<br />
<br />
Default value is -B128. A average value could be -B199 if it's parking to often.<br />
<br />
== KDE => 4.4.4 and hdparm ==<br />
<br />
To stop KDE version 4.4.4 or greater from messing around with your (manually) set hdparm values, enter:<br />
<br />
# sudo touch /etc/pm/power.d/harddrive<br />
<br />
and you should be done.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Cairo_Compmgr&diff=122398
Cairo Compmgr
2010-11-24T19:10:30Z
<p>Cantabile: Added i18n thingy and summary+related articles box</p>
<hr />
<div>[[Category:X Server (English)]]<br />
[[Category:Eye candy (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|Cairo Compmgr}}<br />
{{Article summary start}}<br />
{{Article summary text|Describes the installation and usage of Cairo Composite Manager.}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|Xcompmgr}}<br />
{{Article summary wiki|Composite}}<br />
{{Article summary wiki|AIGLX}}<br />
{{Article summary wiki|Xgl}}<br />
{{Article summary wiki|Xorg}}<br />
{{Article summary wiki|Window Manager}}<br />
{{Article summary wiki|Openbox}}<br />
{{Article summary wiki|Fluxbox}}<br />
{{Article summary end}}<br />
Cairo Composite Manager is a versatile and extensible [http://en.wikipedia.org/wiki/Compositing_window_manager composite manager] which uses cairo for rendering. Plugins can be used to add some cool effects to your desktop. It's capable of, but not limited to, rendering of drop shadows, setting window transparency, menu and window animations, and applying decorations.<br />
<br />
Like [[Xcompmgr]] it does not replace an existing window manager, which makes it ideal for users of lightweight window managers like [[Openbox]] and [[Fluxbox]] that seek a more elegant desktop.<br />
<br />
== Prerequisites ==<br />
<br />
To make use of Cairo Composite Manager, it requires the following:<br />
<br />
* [[Xorg]] must be installed, configured and running<br />
* [[Composite]] must be enabled via graphics drivers, [[AIGLX]], or [[Xgl]]<br />
<br />
== Installation ==<br />
<br />
Install cairo-compmgr from [community] or the newer [http://aur.archlinux.org/packages.php?ID=30042 cairo-compmgr-git] development version from the [[AUR]].<br />
<br />
There are no errors on compile with removed <tt>gconf</tt>, and it runs fine. However, it is not posible to remove dependency on <tt>vala</tt> as it will not compile in that case. If you remove gconf, you need to remove the last 3 lines in PKGBUILD, the ones mentioning gconf.<br />
<br />
== Configuration ==<br />
<br />
To start Cairo Composite Manager, simply run:<br />
<br />
$ cairo-compmgr <br />
<br />
To have it load every time you start X, you can add it to your <tt>~/.xinitrc</tt> :<br />
<br />
cairo-compmgr &<br />
<br />
Once started, Cairo Composite Manager installs itself in your systray and you can configure it by by right-clicking the systray icon.<br />
<br />
If you just want Xcompmgr's behaviour, you can disable a lot of the plugins straightaway. Be patient while Cairo Composite Manager unloads a plugin, it might stall your screen for a moment. <br />
<br />
== Additional Resources ==<br />
<br />
*[[AIGLX]]<br />
*[[Xgl]]<br />
*[[Composite]] -- A Xorg extension required by composite managers<br />
*[[Xcompmgr]] -- A simple composite manager capable of drop shadows and primitive transparency<br />
*[[Compiz Fusion]] -- A composite and window manager offering a rich 3D accelerated desktop environment<br />
*Wikipedia: [http://en.wikipedia.org/wiki/Compositing_window_manager Compositing Window Managers]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Syslinux&diff=121924
Syslinux
2010-11-21T07:27:51Z
<p>Cantabile: /* Configuring syslinux */ cleanup; hard tabs are yuck</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
{{i18n|Syslinux}}<br />
{{Article summary start}}<br />
{{Article summary text|Describes installing and configuring Syslinux, a collection of bootloaders.}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|GRUB}}<br />
{{Article summary wiki|grub-gfx}}<br />
{{Article summary wiki|GRUB2}}<br />
{{Article summary wiki|LILO}}<br />
{{Article summary wiki|MBR}}<br />
{{Article summary end}}<br />
Syslinux is a collection of boot loaders capable of booting from hard drives, CDs and over the network via PXE. It supports the fat, ext2, ext3, ext4 and btrfs file systems.<br />
<br />
== Syslinux Boot Process ==<br />
<br />
At boot, the computer loads the [[MBR]] ({{Filename|/usr/lib/syslinux/mbr.bin}}). The MBR looks for the active partition that is marked with the boot flag, reads the partition boot sector and executes it. At this point, part of the boot loader (syslinux/extlinux) is loaded. This is known as the early-bootstrap code. The early-bootstrap code will load the rest of syslinux. There are two locations where the rest of syslinux is loaded from, depending on the filesystem used. In the case of ext2/3/4 and fat12/16/32, the starting sector of {{Filename|ldlinux.sys}} is hard-coded into the partition boot-sector. The early-bootstrap code executes the code on the starting sector ({{Filename|ldlinux.sys}}). Therefore, if the location of {{Filename|ldlinux.sys}} changes, syslinux will no longer boot. Since btrfs can move every file to another location (changing sector locations), the whole syslinux code needs to be stored outside of the filesystem. Therefore, with btrfs the rest of the syslinux code is in the sectors following the partition boot sector. Once syslinux is fully loaded, it looks for a configuration file, either {{Filename|extlinux.conf}}, {{Filename|syslinux.conf}}, or {{Filename|syslinux.cfg}} (FAT). If one is found, the configuration is loaded, otherwise you will be given a syslinux prompt.<br />
<br />
== Installing syslinux ==<br />
<br />
Make sure you have the ''syslinux'' package installed. Then install syslinux onto your boot partition, which must contain a fat, ext2, ext3, ext4, or btrfs file system.<br />
# mkdir /boot/syslinux<br />
# extlinux --install /boot/syslinux #run on a mounted directory (not /dev/sdXY)<br />
/boot/syslinux/ is device /dev/sda1<br />
<br />
Next, you need mark your boot partition active in your partition table:<br />
# fdisk -l /dev/sda<br />
[...]<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 * 2048 104447 51200 83 Linux<br />
/dev/sda2 104448 625142447 312519000 83 Linux<br />
Once that is the case, install a master boot record:<br />
# cat /usr/lib/syslinux/mbr.bin > /dev/sda<br />
When you reboot your system now, you will have a syslinux prompt. To automatically boot your system or get a boot menu, you still need to create a configuration file.<br />
<br />
== Configuring syslinux ==<br />
<br />
The syslinux configuration file, ''extlinux.conf'' or ''syslinux.conf'' should be created in the same directory where you installed syslinux. In our case '/boot/syslinux/'<br />
<br />
The bootloader will look for either ''extlinux.conf'' or ''syslinux.conf''<br />
<br />
'''Tips''':<br />
*Instead of LINUX, the keyword KERNEL can also be used. KERNEL tries to detect the type of the file, while LINUX always expects a Linux kernel.<br />
*TIMEOUT value is in units of 1/10 of a second.<br />
<br />
=== Examples ===<br />
{{Note| All examples will assumes that /boot is a separate mount point. If /boot is the same partition as /, you have to replace ''/vmlinuz26'' by ''/boot/vmlinuz26'' and so on.}}<br />
<br />
==== Basic Syslinux Config ====<br />
<br />
This is a simple configuration file that will show a boot: prompt and automatically boot after 5 seconds.<br />
<br />
Config:<br />
PROMPT 1<br />
TIMEOUT 50<br />
DEFAULT arch<br />
<br />
LABEL arch<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
LABEL archfallback<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro nomodeset<br />
INITRD /kernel26-fallback.img<br />
<br />
If you want to boot directly without seeing a prompt, set PROMPT to 0. <br />
<br />
==== Text Boot menu ====<br />
<br />
Syslinux also allows you to use a boot menu. To use it, copy the menu COM32 module to your syslinux folder:<br />
# cp /usr/lib/syslinux/menu.c32 /boot/syslinux/<br />
If /boot is the same partition as /, a symlink will also work:<br />
# ln -s /usr/lib/syslinux/menu.c32 /boot/syslinux/<br />
<br />
Config:<br />
UI menu.c32<br />
PROMPT 0<br />
<br />
MENU TITLE Boot Menu<br />
TIMEOUT 50<br />
DEFAULT arch<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
LABEL archfallback<br />
MENU LABEL Arch Linux Fallback<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro nomodeset<br />
INITRD /kernel26-fallback.img<br />
<br />
For more details about the menu system, see [http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=doc/menu.txt].<br />
<br />
==== Graphical Boot menu ====<br />
<br />
Syslinux also allows you to use a graphical boot menu. To use it, copy the vesamenu COM32 module to your syslinux folder:<br />
# cp /usr/lib/syslinux/vesamenu.c32 /boot/syslinux/<br />
If /boot is the same partition as /, a symlink will also work:<br />
# ln -s /usr/lib/syslinux/vesamenu.c32 /boot/syslinux/<br />
<br />
This config uses the same menu design as the Arch Install CD: [http://projects.archlinux.org/archiso.git/tree/configs/syslinux-iso/boot-files/syslinux/syslinux.cfg syslinux.cfg]<br />
<br />
The background file can be found here: [http://projects.archlinux.org/archiso.git/plain/configs/syslinux-iso/boot-files/splash.png splash.png]<br />
<br />
Config:<br />
UI vesamenu.c32<br />
DEFAULT arch<br />
PROMPT 0<br />
MENU TITLE Boot Menu<br />
MENU BACKGROUND splash.png<br />
TIMEOUT 50<br />
<br />
MENU WIDTH 78<br />
MENU MARGIN 4<br />
MENU ROWS 5<br />
MENU VSHIFT 10<br />
MENU TIMEOUTROW 13<br />
MENU TABMSGROW 11<br />
MENU CMDLINEROW 11<br />
MENU HELPMSGROW 16<br />
MENU HELPMSGENDROW 29<br />
<br />
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu<br />
<br />
MENU COLOR border 30;44 #40ffffff #a0000000 std<br />
MENU COLOR title 1;36;44 #9033ccff #a0000000 std<br />
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all<br />
MENU COLOR unsel 37;44 #50ffffff #a0000000 std<br />
MENU COLOR help 37;40 #c0ffffff #a0000000 std<br />
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std<br />
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std<br />
MENU COLOR msg07 37;40 #90ffffff #a0000000 std<br />
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std<br />
<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro nomodeset<br />
INITRD /kernel26.img<br />
<br />
<br />
LABEL archfallback<br />
MENU LABEL Arch Linux Fallback<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro nomodeset<br />
INITRD /kernel26-fallback.img<br />
<br />
=== Chainloading ===<br />
<br />
If you want to chainload other operating systems (such as Windows) or boot loaders, copy (or symlink) the ''chain.c32'' module to the syslinux folder (for details, see the instructions in the previous section). Then, create a section in the configuration file:<br />
<br />
LABEL windows<br />
MENU LABEL Windows<br />
COM32 chain.c32<br />
APPEND hd0 3<br />
<br />
''hd0 3'' is the third partition on the first BIOS drive - drives are counted from zero, but partitions are counted from one. For more details about chainloading, see [http://syslinux.zytor.com/wiki/index.php/Comboot/chain.c32].<br />
<br />
=== Using memtest ===<br />
<br />
Use this LABEL section to launch memtest (install the ''memtest86'' package):<br />
<br />
LABEL memtest<br />
MENU LABEL Memtest86+<br />
LINUX /memtest86+/memtest.bin<br />
<br />
=== HDT ===<br />
<br />
HDT (Hardware Detection Tool) displays hardware information. Like before, the .c32 file has to be copied or symlinked from /boot/syslinux/.<br />
<br />
LABEL hdt<br />
MENU LABEL Hardware Info<br />
COM32 hdt.c32<br />
<br />
=== Reboot and power off ===<br />
<br />
Use the following sections to reboot or power off your machine.<br />
<br />
LABEL reboot<br />
MENU LABEL Reboot<br />
COM32 reboot.c32<br />
<br />
LABEL poweroff<br />
MENU LABEL Power Off<br />
COMBOOT poweroff.com</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Syslinux&diff=121923
Syslinux
2010-11-21T07:16:10Z
<p>Cantabile: /* Syslinux Boot Process */ cleanup</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
{{i18n|Syslinux}}<br />
{{Article summary start}}<br />
{{Article summary text|Describes installing and configuring Syslinux, a collection of bootloaders.}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|GRUB}}<br />
{{Article summary wiki|grub-gfx}}<br />
{{Article summary wiki|GRUB2}}<br />
{{Article summary wiki|LILO}}<br />
{{Article summary wiki|MBR}}<br />
{{Article summary end}}<br />
Syslinux is a collection of boot loaders capable of booting from hard drives, CDs and over the network via PXE. It supports the fat, ext2, ext3, ext4 and btrfs file systems.<br />
<br />
== Syslinux Boot Process ==<br />
<br />
At boot, the computer loads the [[MBR]] ({{Filename|/usr/lib/syslinux/mbr.bin}}). The MBR looks for the active partition that is marked with the boot flag, reads the partition boot sector and executes it. At this point, part of the boot loader (syslinux/extlinux) is loaded. This is known as the early-bootstrap code. The early-bootstrap code will load the rest of syslinux. There are two locations where the rest of syslinux is loaded from, depending on the filesystem used. In the case of ext2/3/4 and fat12/16/32, the starting sector of {{Filename|ldlinux.sys}} is hard-coded into the partition boot-sector. The early-bootstrap code executes the code on the starting sector ({{Filename|ldlinux.sys}}). Therefore, if the location of {{Filename|ldlinux.sys}} changes, syslinux will no longer boot. Since btrfs can move every file to another location (changing sector locations), the whole syslinux code needs to be stored outside of the filesystem. Therefore, with btrfs the rest of the syslinux code is in the sectors following the partition boot sector. Once syslinux is fully loaded, it looks for a configuration file, either {{Filename|extlinux.conf}}, {{Filename|syslinux.conf}}, or {{Filename|syslinux.cfg}} (FAT). If one is found, the configuration is loaded, otherwise you will be given a syslinux prompt.<br />
<br />
== Installing syslinux ==<br />
<br />
Make sure you have the ''syslinux'' package installed. Then install syslinux onto your boot partition, which must contain a fat, ext2, ext3, ext4, or btrfs file system.<br />
# mkdir /boot/syslinux<br />
# extlinux --install /boot/syslinux #run on a mounted directory (not /dev/sdXY)<br />
/boot/syslinux/ is device /dev/sda1<br />
<br />
Next, you need mark your boot partition active in your partition table:<br />
# fdisk -l /dev/sda<br />
[...]<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 * 2048 104447 51200 83 Linux<br />
/dev/sda2 104448 625142447 312519000 83 Linux<br />
Once that is the case, install a master boot record:<br />
# cat /usr/lib/syslinux/mbr.bin > /dev/sda<br />
When you reboot your system now, you will have a syslinux prompt. To automatically boot your system or get a boot menu, you still need to create a configuration file.<br />
<br />
== Configuring syslinux ==<br />
<br />
The syslinux configuration file, ''extlinux.conf'' or ''syslinux.conf'' should be created in the same directory were you installed syslinux. In our case '/boot/syslinux/'<br />
<br />
The bootloader will look for either ''extlinux.conf'' or ''syslinux.conf''<br />
<br />
'''Tips''':<br />
*Instead of LINUX, the keyword KERNEL can also be used. KERNEL tries to detect the file type of the file, while LINUX always expects a Linux kernel.<br />
*TIMEOUT value is in units of 1/10 second<br />
<br />
=== Examples ===<br />
{{Note| All examples will assumes that /boot is a separate mount point. If /boot is the same partition as /, you have to replace ''/vmlinuz26'' by ''/boot/vmlinuz26'' and so on.}}<br />
<br />
==== Basic Syslinux Config ====<br />
<br />
This is a simple configuration file that will show a boot: prompt and automatically boot after 5 seconds.<br />
<br />
Config:<br />
PROMPT 1<br />
TIMEOUT 50<br />
DEFAULT arch<br />
<br />
LABEL arch<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
LABEL archfallback<br />
MENU LABEL Arch Linux Fallback<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro nomodeset<br />
INITRD /kernel26-fallback.img<br />
<br />
If you want to boot directly without seeing a prompt, set PROMPT to 0. <br />
<br />
==== Text Boot menu ====<br />
<br />
Syslinux also allows you to use a boot menu. To use it, copy the menu COM32 module to your syslinux folder:<br />
# cp /usr/lib/syslinux/menu.c32 /boot/syslinux/<br />
If /boot is the same partition as /, a symlink will also work<br />
# ln -s /usr/lib/syslinux/menu.c32 /boot/syslinux/<br />
<br />
Config:<br />
UI menu.c32<br />
PROMPT 0<br />
<br />
MENU TITLE Boot Menu<br />
TIMEOUT 50<br />
DEFAULT arch<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
LABEL archfallback<br />
MENU LABEL Arch Linux Fallback<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro nomodeset<br />
INITRD /kernel26-fallback.img<br />
<br />
For more details about the menu system, see [http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=doc/menu.txt].<br />
<br />
==== Graphical Boot menu ====<br />
<br />
Syslinux also allows you to use a graphical boot menu. To use it, copy the vesamenu COM32 module to your syslinux folder:<br />
# cp /usr/lib/syslinux/vesamenu.c32 /boot/syslinux/<br />
If /boot is the same partition as /, a symlink will also work<br />
# ln -s /usr/lib/syslinux/vesamenu.c32 /boot/syslinux/<br />
<br />
This config uses the same menu design as the Arch Install CD: [http://projects.archlinux.org/archiso.git/tree/configs/syslinux-iso/boot-files/syslinux/syslinux.cfg syslinux.cfg]<br />
<br />
The background file can be found here: [http://projects.archlinux.org/archiso.git/plain/configs/syslinux-iso/boot-files/splash.png splash.png]<br />
<br />
Config:<br />
UI vesamenu.c32<br />
DEFAULT arch<br />
PROMPT 0<br />
MENU TITLE Boot Menu<br />
MENU BACKGROUND splash.png<br />
TIMEOUT 50<br />
<br />
MENU WIDTH 78<br />
MENU MARGIN 4<br />
MENU ROWS 5<br />
MENU VSHIFT 10<br />
MENU TIMEOUTROW 13<br />
MENU TABMSGROW 11<br />
MENU CMDLINEROW 11<br />
MENU HELPMSGROW 16<br />
MENU HELPMSGENDROW 29<br />
<br />
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu<br />
<br />
MENU COLOR border 30;44 #40ffffff #a0000000 std<br />
MENU COLOR title 1;36;44 #9033ccff #a0000000 std<br />
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all<br />
MENU COLOR unsel 37;44 #50ffffff #a0000000 std<br />
MENU COLOR help 37;40 #c0ffffff #a0000000 std<br />
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std<br />
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std<br />
MENU COLOR msg07 37;40 #90ffffff #a0000000 std<br />
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std<br />
<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro nomodeset<br />
INITRD /kernel26.img<br />
<br />
<br />
LABEL archfallback<br />
MENU LABEL Arch Linux Fallback<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro nomodeset<br />
INITRD /kernel26-fallback.img<br />
<br />
=== Chainloading ===<br />
<br />
If you want to chainload other operating systems (such as Windows) or boot loaders, copy (or symlink) the ''chain.c32'' module to the syslinux folder (for details, see the instructions in the previous section). Then, create a section in the configuration file:<br />
<br />
LABEL windows<br />
MENU LABEL Windows<br />
COM32 chain.c32<br />
APPEND hd0 3<br />
<br />
''hd0 3'' is the third partition on the first BIOS drive - drives are counted from zero, but partitions are counted from one. For more details about chainloading, see [http://syslinux.zytor.com/wiki/index.php/Comboot/chain.c32].<br />
<br />
=== Using memtest ===<br />
<br />
Use this LABEL section to launch memtest (install the ''memtest86'' package):<br />
<br />
LABEL memtest<br />
MENU LABEL Memtest86+<br />
LINUX /memtest86+/memtest.bin<br />
<br />
=== HDT ===<br />
<br />
HDT (Hardware Detection Tool) displays hardware information. Like before, the .c32 file has to be copied or symlinked from /boot/syslinux/.<br />
<br />
LABEL hdt<br />
MENU LABEL Hardware Info<br />
COM32 hdt.c32<br />
<br />
=== Reboot and power off ===<br />
<br />
Use the following sections to reboot or power off your machine.<br />
<br />
LABEL reboot<br />
MENU LABEL Reboot<br />
COM32 reboot.c32<br />
<br />
LABEL poweroff<br />
MENU LABEL Power Off<br />
COMBOOT poweroff.com</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Syslinux&diff=121922
Syslinux
2010-11-21T07:05:05Z
<p>Cantabile: /* Graphical Boot menu */ fixed small mistake</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
{{i18n|Syslinux}}<br />
{{Article summary start}}<br />
{{Article summary text|Describes installing and configuring Syslinux, a collection of bootloaders.}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|GRUB}}<br />
{{Article summary wiki|grub-gfx}}<br />
{{Article summary wiki|GRUB2}}<br />
{{Article summary wiki|LILO}}<br />
{{Article summary wiki|MBR}}<br />
{{Article summary end}}<br />
Syslinux is a collection of boot loaders capable of booting from hard drives, CDs and over the network via PXE. It supports the fat, ext2, ext3, ext4 and btrfs file systems.<br />
<br />
== Syslinux Boot Process ==<br />
<br />
At boot, the computer loads the MBR (/usr/lib/syslinux/mbr.bin). The MBR looks for the active partition that is marked with the boot flag, reads the partition boot sector, and executes it. At this point, part of the boot loader (syslinux/extlinux) is loaded. This is known as the early-bootstrap code. The early-bootstrap code, will load the rest of syslinux. There are two locations where the rest of syslinux is loaded from depending on the filesystem used. In the case of ext2/3/4 and fat12/16/32, the starting sector of ldlinux.sys is hard-coded into the partition boot-sector. The early-bootstrap code, executes the code on the starting sector (ldlinux.sys). Therefore, if the location of ldlinux.sys changes, syslinux will no longer boot. Since btrfs can move every file to another location (changing sector locations), the whole syslinux code needs to stored outside of the filesystem. Therefore, with btrfs the rest of the syslinux code is in the sectors following the partition boot sector. Once syslinux is fully loaded, it looks for a configuration file, either extlinux.conf, syslinux.conf, or syslinux.cfg (FAT). If one is found, the configuration is loaded, otherwise you will be given a syslinux prompt.<br />
<br />
<br />
== Installing syslinux ==<br />
<br />
Make sure you have the ''syslinux'' package installed. Then install syslinux onto your boot partition, which must contain a fat, ext2, ext3, ext4, or btrfs file system.<br />
# mkdir /boot/syslinux<br />
# extlinux --install /boot/syslinux #run on a mounted directory (not /dev/sdXY)<br />
/boot/syslinux/ is device /dev/sda1<br />
<br />
Next, you need mark your boot partition active in your partition table:<br />
# fdisk -l /dev/sda<br />
[...]<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 * 2048 104447 51200 83 Linux<br />
/dev/sda2 104448 625142447 312519000 83 Linux<br />
Once that is the case, install a master boot record:<br />
# cat /usr/lib/syslinux/mbr.bin > /dev/sda<br />
When you reboot your system now, you will have a syslinux prompt. To automatically boot your system or get a boot menu, you still need to create a configuration file.<br />
<br />
== Configuring syslinux ==<br />
<br />
The syslinux configuration file, ''extlinux.conf'' or ''syslinux.conf'' should be created in the same directory were you installed syslinux. In our case '/boot/syslinux/'<br />
<br />
The bootloader will look for either ''extlinux.conf'' or ''syslinux.conf''<br />
<br />
'''Tips''':<br />
*Instead of LINUX, the keyword KERNEL can also be used. KERNEL tries to detect the file type of the file, while LINUX always expects a Linux kernel.<br />
*TIMEOUT value is in units of 1/10 second<br />
<br />
=== Examples ===<br />
{{Note| All examples will assumes that /boot is a separate mount point. If /boot is the same partition as /, you have to replace ''/vmlinuz26'' by ''/boot/vmlinuz26'' and so on.}}<br />
<br />
==== Basic Syslinux Config ====<br />
<br />
This is a simple configuration file that will show a boot: prompt and automatically boot after 5 seconds.<br />
<br />
Config:<br />
PROMPT 1<br />
TIMEOUT 50<br />
DEFAULT arch<br />
<br />
LABEL arch<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
LABEL archfallback<br />
MENU LABEL Arch Linux Fallback<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro nomodeset<br />
INITRD /kernel26-fallback.img<br />
<br />
If you want to boot directly without seeing a prompt, set PROMPT to 0. <br />
<br />
==== Text Boot menu ====<br />
<br />
Syslinux also allows you to use a boot menu. To use it, copy the menu COM32 module to your syslinux folder:<br />
# cp /usr/lib/syslinux/menu.c32 /boot/syslinux/<br />
If /boot is the same partition as /, a symlink will also work<br />
# ln -s /usr/lib/syslinux/menu.c32 /boot/syslinux/<br />
<br />
Config:<br />
UI menu.c32<br />
PROMPT 0<br />
<br />
MENU TITLE Boot Menu<br />
TIMEOUT 50<br />
DEFAULT arch<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
LABEL archfallback<br />
MENU LABEL Arch Linux Fallback<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro nomodeset<br />
INITRD /kernel26-fallback.img<br />
<br />
For more details about the menu system, see [http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=doc/menu.txt].<br />
<br />
==== Graphical Boot menu ====<br />
<br />
Syslinux also allows you to use a graphical boot menu. To use it, copy the vesamenu COM32 module to your syslinux folder:<br />
# cp /usr/lib/syslinux/vesamenu.c32 /boot/syslinux/<br />
If /boot is the same partition as /, a symlink will also work<br />
# ln -s /usr/lib/syslinux/vesamenu.c32 /boot/syslinux/<br />
<br />
This config uses the same menu design as the Arch Install CD: [http://projects.archlinux.org/archiso.git/tree/configs/syslinux-iso/boot-files/syslinux/syslinux.cfg syslinux.cfg]<br />
<br />
The background file can be found here: [http://projects.archlinux.org/archiso.git/plain/configs/syslinux-iso/boot-files/splash.png splash.png]<br />
<br />
Config:<br />
UI vesamenu.c32<br />
DEFAULT arch<br />
PROMPT 0<br />
MENU TITLE Boot Menu<br />
MENU BACKGROUND splash.png<br />
TIMEOUT 50<br />
<br />
MENU WIDTH 78<br />
MENU MARGIN 4<br />
MENU ROWS 5<br />
MENU VSHIFT 10<br />
MENU TIMEOUTROW 13<br />
MENU TABMSGROW 11<br />
MENU CMDLINEROW 11<br />
MENU HELPMSGROW 16<br />
MENU HELPMSGENDROW 29<br />
<br />
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu<br />
<br />
MENU COLOR border 30;44 #40ffffff #a0000000 std<br />
MENU COLOR title 1;36;44 #9033ccff #a0000000 std<br />
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all<br />
MENU COLOR unsel 37;44 #50ffffff #a0000000 std<br />
MENU COLOR help 37;40 #c0ffffff #a0000000 std<br />
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std<br />
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std<br />
MENU COLOR msg07 37;40 #90ffffff #a0000000 std<br />
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std<br />
<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro nomodeset<br />
INITRD /kernel26.img<br />
<br />
<br />
LABEL archfallback<br />
MENU LABEL Arch Linux Fallback<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro nomodeset<br />
INITRD /kernel26-fallback.img<br />
<br />
=== Chainloading ===<br />
<br />
If you want to chainload other operating systems (such as Windows) or boot loaders, copy (or symlink) the ''chain.c32'' module to the syslinux folder (for details, see the instructions in the previous section). Then, create a section in the configuration file:<br />
<br />
LABEL windows<br />
MENU LABEL Windows<br />
COM32 chain.c32<br />
APPEND hd0 3<br />
<br />
''hd0 3'' is the third partition on the first BIOS drive - drives are counted from zero, but partitions are counted from one. For more details about chainloading, see [http://syslinux.zytor.com/wiki/index.php/Comboot/chain.c32].<br />
<br />
=== Using memtest ===<br />
<br />
Use this LABEL section to launch memtest (install the ''memtest86'' package):<br />
<br />
LABEL memtest<br />
MENU LABEL Memtest86+<br />
LINUX /memtest86+/memtest.bin<br />
<br />
=== HDT ===<br />
<br />
HDT (Hardware Detection Tool) displays hardware information. Like before, the .c32 file has to be copied or symlinked from /boot/syslinux/.<br />
<br />
LABEL hdt<br />
MENU LABEL Hardware Info<br />
COM32 hdt.c32<br />
<br />
=== Reboot and power off ===<br />
<br />
Use the following sections to reboot or power off your machine.<br />
<br />
LABEL reboot<br />
MENU LABEL Reboot<br />
COM32 reboot.c32<br />
<br />
LABEL poweroff<br />
MENU LABEL Power Off<br />
COMBOOT poweroff.com</div>
Cantabile
https://wiki.archlinux.org/index.php?title=List_of_applications&diff=121343
List of applications
2010-11-14T17:41:33Z
<p>Cantabile: /* Audio */ replaced red links with links to project pages, replaced "gtk" with "gtk2" where appropriate, added line about Clementine</p>
<hr />
<div>[[Category:Other desktop user's resources (English)]] [[Category:General (English)]]<br />
{{i18n|Common Applications}}<br />
{{Article summary start}}<br />
{{Article summary text|Provides a list of common software that may be useful in day-to-day computer use, categorized by task.}}<br />
<!--{{Article summary heading|Languages}}--><br />
<!--{{i18n_entry|English|Common Applications}}--><br />
{{Article summary heading|Related}}<br />
{{Article summary text|[[Lightweight Applications]]}}<br />
{{Article summary end}}<br />
<br />
== [[Backup programs]] ==<br />
* [[Wikipedia:DAR (Disk Archiver)|DAR]] - A full-featured command-line backup tool, short for Disk ARchive<br />
** Architecture(s): i686, x86_64<br />
** Repository: Community<br />
** Description: A full-featured command-line backup tool, short for Disk ARchive<br />
** Upstream URL: http://dar.linux.free.fr/<br />
** License: GPL<br />
** Package name: {{Package Official|dar}}<br />
<br />
* [[Wikipedia:Duplicity (software)|Duplicity]] - A utility for encrypted, bandwidth-efficient backups using the rsync algorithm<br />
** Architecture(s): i686, x86_64<br />
** Repository: Community<br />
** Description: A utility for encrypted, bandwidth-efficient backups using the rsync algorithm<br />
** Upstream URL: http://www.nongnu.org/duplicity/<br />
** License: GPL<br />
** Package name: {{Package Official|duplicity}}<br />
<br />
* Packrat - A simple, modular backup system that uses dar to take full/incremental backups of files and can store them locally, on a remote system via SSH, or on Amazon S3<br />
** Architecture(s): i686, x86_64<br />
** Repository: AUR<br />
** Description: A simple backup system with included modules for SSH, Amazon S3, and MySQL<br />
** Upstream URL: http://www.zeroflux.org/projects<br />
** License: MIT<br />
** Package name: {{Package AUR|packrat}}<br />
<br />
* [[wikipedia:Rsync#Variations|rdiff-backup]] - A utility for local/remote mirroring and incremental backups<br />
** Architecture(s): i686, x86_64<br />
** Repository: Community<br />
** Description: A utility for local/remote mirroring and incremental backups<br />
** Upstream URL: http://www.nongnu.org/rdiff-backup/<br />
** License: GPL<br />
** Package name: {{Package Official|rdiff-backup}}<br />
<br />
* rsnapshot - A remote filesystem snapshot utility<br />
** Architecture(s): i686, x86_64<br />
** Repository: Community<br />
** Description: A remote filesystem snapshot utility<br />
** Upstream URL: http://www.rsnapshot.org/<br />
** License: GPL<br />
** Package name: {{Package Official|rsnapshot}}<br />
<br />
* [[Rsync|rsync]] - A file transfer program to keep remote files in sync<br />
** Architecture(s): i686, x86_64<br />
** Repository: Extra<br />
** Description: A file transfer program to keep remote files in sync<br />
** Upstream URL: http://rsync.samba.org/<br />
** License: GPL3<br />
** Package name: {{Package Official|rsync}}<br />
<br />
* Safekeep - A client/server backup system which enhances the power of rdiff-backup<br />
** Architecture(s): i686, x86_64<br />
** Repository: AUR<br />
** Description: A client/server backup system which enhances the power of rdiff-backup<br />
** Upstream URL: http://safekeep.sourceforge.net/<br />
** License: GPL<br />
** Package name: {{Package AUR|safekeep}}<br />
<br />
== Internet ==<br />
=== BitTorrent Clients ===<br />
{{Wikipedia|Comparison of BitTorrent clients}}<br />
<br />
* {{App|aria2|Fast command-line download utility with support for multiple protocols, including BitTorrent|http://aria2.sourceforge.net/|{{Package Official|aria2}}}}<br />
* {{App|[[Wikipedia:Deluge (software)|Deluge]]|User-friendly BitTorrent client written in Python and wrapped with PyGTK|http://deluge-torrent.org/|{{Package Official|deluge}}}}<br />
* {{App|[[Wikipedia:KTorrent|KTorrent]]|Feature-rich BitTorrent client developed using Qt|http://ktorrent.org/|{{Package Official|ktorrent}}}}<br />
* {{App|[[Wikipedia:MLDonkey|MLDonkey]]|Multi-protocol P2P client supporting BitTorrent|http://mldonkey.sourceforge.net/|{{Package Official|mldonkey}}}}<br />
* {{App|[[Wikipedia:QBittorrent|qBittorrent]]|The closest open source (GNU GPL v2 license) equivalent to µtorrent|http://qbittorrent.sourceforge.net/|{{Package Official|qbittorrent}}}}<br />
* {{App|[[Wikipedia:RTorrent|rTorrent]]|Simple and lightweight ncurses BitTorrent client|http://libtorrent.rakshasa.no/|{{Package Official|rtorrent}}}}<br />
* {{App|[[Wikipedia:Transmission (BitTorrent client)|Transmission]]|Simple and easy-to-use BitTorrent client with (GTK+) GUI and CLI front-ends|http://www.transmissionbt.com/|{{Package Official|transmission}}}}<br />
* {{App|[[Wikipedia:Vuze|Vuze]]|Feature-rich BitTorrent client written in Java (formerly Azureus)|http://www.vuze.com/|{{Package Official|vuze}}}}<br />
<br />
=== Chat Clients ===<br />
==== IRC Clients ====<br />
* {{App|[[Irssi]]|Highly-configurable ncurses-based IRC client|http://www.irssi.org/|{{Package Official|irssi}}}}<br />
* {{App|[[Wikipedia:Konversation|Konversation]]|Qt-based IRC client for the KDE4 desktop|http://konversation.kde.org/|{{Package Official|konversation}}}}<br />
* {{App|[[Wikipedia:KVIrc|KVIrc]]|Qt-based IRC client featuring extensive themes support|http://www.kvirc.net/|{{Package Official|kvirc}}}}<br />
* {{App|[[Wikipedia:WeeChat|WeeChat]]|Modular, lightweight ncurses-based IRC client|http://www.weechat.org/|{{Package Official|weechat}}}}<br />
* {{App|[[Wikipedia:XChat|XChat]]|GTK-based IRC client|http://xchat.org/|{{Package Official|xchat}}}}<br />
<br />
==== Jabber/XMPP Clients ====<br />
* {{App|Freetalk|A console based Jabber client|http://www.gnu.org/software/freetalk/|{{Package Official|freetalk}}}}<br />
* {{App|[[Wikipedia:Gajim|Gajim]]|Jabber client written in PyGTK|http://www.gajim.org/|{{Package Official|gajim}}}}<br />
* {{App|jabber.el|A minimal jabber client for emacs|http://emacs-jabber.sourceforge.net/|{{Package AUR|emacs-jabber}}}}<br />
* {{App|[[Wikipedia:MCabber|MCabber]]|A small Jabber console client, includes features: SSL, PGP, MUC, and UTF8|http://mcabber.com/|{{Package Official|mcabber}}}}<br />
* {{App|[[Wikipedia:Psi (instant messaging client)|Psi]]|A Qt based Jabber client|http://psi-im.org/|{{Package Official|psi}}}}<br />
* [http://code.google.com/p/psi-dev/ Psi+] is an enhanced version of Psi Jabber client. Not in AUR<br />
<br />
==== MSN Clients ====<br />
* {{App|[[Wikipedia:AMSN|aMSN]]|MSN client written in Tcl/Tk|http://www.amsn-project.net/|{{Package Official|amsn}}}}<br />
* {{App|[[Wikipedia:Emesene|Emesene]]|A pygtk MSN Messenger client|http://www.emesene.org/|{{Package Official|emesene}}}}<br />
* {{App|Galaxium Messenger|A multi-protocol instant messenger application designed for the GNOME desktop|http://code.google.com/p/galaxium/|{{Package AUR|galaxium}}}}<br />
* {{App|[[Wikipedia:Kmess|KMess]]|KMess is a MSN Messenger client for Linux|http://kmess.org/|{{Package Official|kmess}}}}<br />
* {{App|[[Wikipedia:Mercury Messenger|Mercury]]|Java Based MSN client|http://www.mercury.im/|{{Package Official|mercury}}}}<br />
<br />
==== Multi-Protocol Clients ====<br />
{{Wikipedia|Comparison of instant messaging clients}}<br />
<br />
* {{App|BarnOwl|A console chat client for the AIM, IRC, Jabber, and Zephyr protocols|http://barnowl.mit.edu/|{{Package AUR|barnowl}}}}<br />
* {{App|Carrier|Pidgin fork providing minor GUI enhancements (formerly funpidgin)|http://funpidgin.sourceforge.net/|{{Package AUR|carrier}}}}<br />
* {{App|[[Wikipedia:Centericq|CenterIM]]|Fork of CenterICQ - A text mode menu- and window-driven IM interface|http://www.centerim.org/index.php/Main_Page|{{Package Official|centerim}}}}<br />
* {{App|[[Wikipedia:Empathy (software)|Empathy]]|A GNOME instant messaging client using the Telepathy framework|http://live.gnome.org/Empathy|{{Package Official|empathy}}}}<br />
* {{App|Finch|A ncurses-based messaging client|http://pidgin.im/|{{Package Official|finch}}}}<br />
* {{App|[[Wikipedia:Kopete|Kopete]]|Instant Messenger|http://www.kde.org/|{{Package Official|kopete}}}}<br />
* {{App|[[Pidgin]]|Multi-protocol instant messaging client|http://pidgin.im/|{{Package Official|pidgin}}}}<br />
* {{App|[[Wikipedia:QutIM|qutIM]]|Multiplatform instant messenger|http://qutim.org/|{{Package AUR|qutim}}}}<br />
<br />
=== Mail Clients ===<br />
* [[Alpine]] The Apache-licensed PINE (a tool for reading, sending, and managing electronic messages) http://www.washington.edu/alpine<br />
* [[Claws-mail]] - A GTK+ based e-mail client http://www.claws-mail.org<br />
* [[Evolution]] - A mature and feature-rich e-mail client used in GNOME by default.<br />
* [[Gnus]] - mail, nntp, rss client for Emacs.<br />
* [[Kmail]] - A mature and feature-rich e-mail client part of the kde project. http://kontact.kde.org/kmail/<br />
* [[mutt]] - The famous, mature old command-line client http://www.mutt.org/<br />
* [[Sup]] - A CLI mail client with very fast searching, tagging, threading and gmail like operation. http://sup.rubyforge.org/<br />
* [[Sylpheed]] - Lightweight and user-friendly e-mail client http://sylpheed.sraoss.jp/en/<br />
* [[Thunderbird]] - Mozilla's GTK2-based client.<br />
<br />
=== News Aggregators ===<br />
* [[Akregator]] - KDE's news aggregator (in kdepim package)<br />
* [[Canto]] - A ncurses RSS aggregator http://codezen.org/canto/<br />
* [[Gnus]] - mail, nntp, rss client for Emacs.<br />
* [[Liferea]] - A GTK desktop news aggregator for online news feeds and weblogs http://liferea.sourceforge.net<br />
* [[Newsbeuter]] - A ncurses RSS aggregator with layout and keybinding similar to mutt. Does not use the traditional 3 panes setup.<br />
* [[Rawdog]] - An "RSS Aggregator Without Delusions Of Grandeur" that parses RSS/CDF/Atom feeds into a static HTML page of articles in date order http://offog.org/code/rawdog.html<br />
* [[Rssowl]] - A powerful java-based RSS reader http://boreal.rssowl.org<br />
* [[BlogBridge]] - Another excellent java-based aggregator http://www.blogbridge.com<br />
* [[Snownews]] - Text mode RSS newsreader.<br />
* [[Thunderbird]] - A mail client from Mozilla which also functions as a pretty nice news aggregator<br />
<br />
=== Web Browsers ===<br />
==== Graphical ====<br />
* [[Arora]] - Cross-platform open source web browser using the [http://webkit.org/ WebKit] rendering engine, built on top of Qt. http://www.arora-browser.org/<br />
* [[Chromium]] - The open-source project behind Google Chrome, a web browser developed by Google that uses the WebKit layout engine and application framework. http://code.google.com/chromium/<br />
* [[Dillo]] - A small, fast graphical web browser built on FLTK http://www.dillo.org/<br />
* [[Epiphany]] - The default GNOME browser, which uses the webkit rendering engine. http://projects.gnome.org/epiphany/<br />
* [[Firefox]] - [https://addons.mozilla.org/firefox/ Extensible] GTK2 browser based on Gecko with fast rendering. http://www.mozilla.com/firefox/<br />
* [[Kazehakase]] - A much lighter, but rather feature-lacking alternative to other browsers (GTK2 and Gecko). http://kazehakase.sourceforge.jp/<br />
* [[Konqueror]] - Qt- and KHTML-based browser. A part of the KDE desktop. http://www.konqueror.org/<br />
* [[Midori]] - Young but promising GTK2/WebKit browser, featherweight with very fast rendering http://www.twotoasts.de/index.php?/pages/midori_summary.html<br />
* [[Opera]] - Highly customizable browser with focuses on an adherence to web rendering standards http://www.opera.com/<br />
* [[uzbl]] - A lightweight webkit browser following the UNIX philosophy - to do one thing and do it well. http://www.uzbl.org/<br />
* [http://aur.archlinux.org/packages.php?ID=6524 Hv3] - A minimalist web browser based on tkhtml3 http://tkhtml.tcl.tk/hv3.html<br />
* [http://aur.archlinux.org/packages.php?O=0&K=vimprobable&do_Search=Go Vimprobable] - A webkit-based web browser which behaves like Vimperator, but without Firefox. http://www.vimprobable.org/<br />
* [http://aur.archlinux.org/packages.php?ID=38684 jumanji] - jumanji provides a minimalistic and space saving interface with vimperator-like keyboard-focused interaction http://pwmt.org/jumanji<br />
<br />
==== Text Based ====<br />
* [[Elinks]] - An advanced and well-established feature-rich text mode web browser. http://elinks.or.cz<br />
* [[links-g]] A text WWW browser, similar to Lynx, with framebuffer and X graphics enabled http://links.twibright.com/<br />
* [[Lynx]] A text browser for the World Wide Web http://lynx.isc.org<br />
* [[w3m]] A pager/text-based WWW browser http://w3m.sourceforge.net/<br />
<br />
== Document Indexers ==<br />
* [[pinot]] - Personal search and metasearch tool http://pinot.berlios.de/<br />
* [[recoll]] - Full text search tool based on Xapian backend http://www.lesbonscomptes.com/recoll/<br />
<br />
== Document Readers ==<br />
*[[ePDFView ]] - A free lightweight PDF document viewer using Poppler and GTK+ libraries. http://trac.emma-soft.com/epdfview/<br />
*[[Evince]] - Document viewer for multiple document formats. Supports pdf, postscript, djvu, tiff and dvi http://projects.gnome.org/evince/<br />
*[[Foxit Reader]] - A small, fast PDF viewer http://www.foxitsoftware.com/pdf/desklinux/<br />
*[[MuPDF]] - lightweight PDF viewer and toolkit written in portable C http://ccxvii.net/mupdf/<br />
*[[Okular]] - PDF viewer for KDE. http://okular.kde.org/<br />
*[[xpdf]] - A viewer for Portable Document Format (PDF) files http://www.foolabs.com/xpdf/<br />
*[[apvlv]] - apvlv is a PDF Viewer Under Linux and its behaviour like Vim. http://code.google.com/p/apvlv/<br />
<br />
== Multimedia ==<br />
=== Audio ===<br />
* [[Amarok]] - A mature Qt-based player known for its plethora of features<br />
* [http://ario-player.sourceforge.net/ Ario] - A GTK2 client for MPD (Music player daemon) inspired by Rhythmbox but much lighter and faster<br />
* [http://www.atunes.org/ aTunes] - An audio-player written in Java<br />
* [[Audacious]] - A Winamp clone like Beep and old XMMS versions<br />
* [http://banshee.fm/ Banshee] - yet another GTK2 iTunes clone, yet more feature-rich and more actively developed.<br />
* [http://www.clementine-player.org/ Clementine] - Amarok 1.4 ported to QT4<br />
* [http://cmus.sourceforge.net/ Cmus] is a very feature-rich ncurses-based music player.<br />
* [http://web.archive.org/web/20080221195932/http://mask.tf.hut.fi/~flu/cplay/ Cplay] is a curses front-end for various audio players.<br />
* [http://deadbeef.sourceforge.net/ DeaDBeeF] - Lightweight and powerful music player made with C and GTK2. [http://bbs.archlinux.org/viewtopic.php?id=96968]<br />
* [[Exaile]] - A GTK2 clone of Amarok<br />
* [[Goggles Music Manager]] - A lightweight music manager and player that automatically categorizes your music files.<br />
* [[Moc]] - A ncurses-based daemon/client style player, designed to be flexible and easy to use.<br />
* [[Music Player Daemon]] - Music player daemon, a lightweight and scalable choice for music management<br />
* [http://www.mpg123.org/ mpg123] - command line audio player.<br />
* [http://mpd.wikia.com/wiki/Client:Ncmpc ncmpc] - An ncurses-based front-end to mpd<br />
* [http://unkart.ovh.org/ncmpcpp/ ncmpcpp] - A clone of ncmpc with some new features written in C++<br />
* [http://www.luga.de/pytone/ PyTone] - An advanced music jukebox with a console interface<br />
* [http://code.google.com/p/quodlibet/ Quod Libet] - an audio player written with pygtk and gstreamer<br />
* [[Rhythmbox]] - A GTK2 clone of iTunes, used by default in GNOME<br />
* [http://sonata.berlios.de/ Sonata] - A pygtk-based client for mpd<br />
* [http://getnightingale.com/ Nightingale] - ([http://getsongbird.com/ Songbird] for linux) an open source clone of iTunes that uses Mozilla technologies as well as Gstreamer and is being developed by the team that made WinAMP<br />
* [http://legacy.xmms2.org/ XMMS] - A skinnable GTK+1 standalone media player similar to winamp<br />
<br />
==== Visualization ====<br />
* [http://projectm.sourceforge.net/ projectM]<br />
<br />
==== Editing ====<br />
* [http://audacity.sourceforge.net/ Audacity]<br />
<br />
=== Graphics and Image Manipulation ===<br />
* [[Blender]]<br />
* [[Dia]]<br />
* [[Gimp]]<br />
* [[imagemagick]]<br />
* [[Inkscape]]<br />
* [[Krita]]<br />
* [[mtpaint]]<br />
* [[Nathive]]<br />
* [[Shotwell]]<br />
* [[Xara]]<br />
* [[mypaint]]<br />
<br />
=== Image Viewers ===<br />
* [[Background Setter]]<br />
* [[eog]]<br />
* [[feh]]<br />
* [[GPicView]]<br />
* [[Geeqie]]<br />
* [[GQview]]<br />
* [[gThumb]]<br />
* [[Mirage]]<br />
* [[Quick Image Viewer]]<br />
* [[Ristretto]]<br />
* [[XnView]]<br />
* [[xv]]<br />
* [[Picasa]]<br />
<br />
=== Phone ===<br />
* [[moto4lin]]<br />
<br />
=== Video Players===<br />
* [[mplayer]]<br />
* [[Parole]] A modern media player based on the GStreamer framework http://goodies.xfce.org/projects/applications/parole/<br />
* [[SMPlayer]] is a complete frontend for [[MPlayer]].<br />
* [[VLC]] - A simple multi-platform media player, streamer, and encoder, that handles huge numbers of media formats.<br />
* [[Whaaw! Media Player]] is a lightweight Gstreamer-based audio/video player that can serve as a good alternative to Totem for those who don't like all those GNOME dependencies. http://home.gna.org/whaawmp/<br />
* [[Dragon player]] is a simple video player for KDE 4 developed by Ian Monroe. http://www.dragonplayer.net/<br />
<br />
=== Video Editors ===<br />
* http://www.pitivi.org/ {{Package AUR|pitivi}}<br />
* http://lives.sourceforge.net/ {{Package AUR|lives}}<br />
* http://www.openmovieeditor.org/ {{Package Official|openmovieeditor}}<br />
* http://www.openshotvideo.com/<br />
* http://www.avidemux.org/ {{Package Official|avidemux}}<br />
* http://kdenlive.org/ {{Package Official|kdenlive}}<br />
* http://www.kinodv.org/<br />
* http://cinelerra.org/ {{Package Official|cinelerra-cv}}<br />
<br />
== Note Taking Organizers ==<br />
* [http://aur.archlinux.org/packages.php?ID=19388 glista] with notes support [http://prematureoptimization.org/glista/downloads.php Home page]<br />
* [[hnb]] - A program to organize many kinds of data in one place [http://hnb.sourceforge.net/ Home page] [http://aur.archlinux.org/packages.php?ID=16630 Package]<br />
* [[NoteCase]] - A portable hierarchical note manager, coded in C++ using the GTK+ toolkit [http://notecase.sourceforge.net Home page]<br />
* [[Task]] - A command-line TODO list manager [http://www.beckingham.net/task.html Home page]<br />
* [[tomboy]] - Desktop note-taking application for Linux and Unix [http://www.gnome.org/projects/tomboy/ Home page]<br />
* [[zim]] - A WYSIWYG text editor that aims at bringing the concept of a wiki to the desktop [http://zim-wiki.org/ Home page]<br />
* [[Gnote]] - Gnote is an experimental port of Tomboy to C++ [http://live.gnome.org/Gnote Home page]<br />
<br />
== Office ==<br />
=== Suites ===<br />
* [[Koffice]] - KOffice is a free, integrated office suite for KDE, the K Desktop Environment. http://www.koffice.org/<br />
* [[OpenOffice.org]] - An office suite http://www.OpenOffice.org/<br />
<br />
=== Word Processors ===<br />
* [[Abiword]] - A lightweight fast word processor http://www.abisource.com/<br />
* [[OpenOffice.org Writer]] - A full-featured word processor included in the OpenOffice.org suite<br />
* [http://www.archlinux.org/packages/community/i686/ted/ Ted] - An easy GTK-based rich text processor (with footnote support) http://www.nllgg.nl/Ted/<br />
<br />
== Spreadsheets ==<br />
* [[gnumeric]] - A GNOME Spreadsheet Program http://www.gnome.org/projects/gnumeric<br />
* [[OpenOffice.org Calc]] - A full-featured spreadsheet included in OpenOffice.org suite<br />
<br />
== Security ==<br />
* [[arpwatch]] - arpwatch and arpsnmp network monitoring tools ftp://ftp.ee.lbl.gov/<br />
* [[DenyHosts]] - a script to help thwart ssh server attacks http://denyhosts.sourceforge.net/<br />
* [[fail2ban]] - bans IP that makes too many password failures http://www.fail2ban.org/<br />
* [[etherape]] - A graphical network monitor for various OSI layers and protocols http://etherape.sourceforge.net/<br />
* [[iptraf]] - An IP network monitor http://iptraf.seul.org/<br />
* [[logwatch]] - Logwatch is a customizable log analysis system http://www.logwatch.org/<br />
* [[nessus]] - Vulnerability scanner http://www.nessus.org<br />
* [[nmap]] - A command line network exploration tool and security/port scanner http://nmap.org<br />
* [[ntop]] - A network traffic probe based on libcap http://ntop.org<br />
* [[portbunny]] - Extremly fast CLI portscanner http://www.recurity-labs.com/portbunny/index.shtml<br />
* [[snort]] - A lightweight network intrusion detection system http://www.snort.org<br />
* [[swatch]] - The active log file monitoring tool http://swatch.sourceforge.net/<br />
* [[tcpdump]] - A tool for network monitoring and data acquisition http://www.tcpdump.org<br />
* [[wireshark]] - A free network protocol analyzer for Unix/Linux and Windows http://www.wireshark.org/<br />
<br />
== Time Management ==<br />
* [[Calcurse]] - An ncurses calendar and task manager [http://culot.org/calcurse/ Home page]<br />
* [[Orage]] - A GTK+ calendar and task manager often seen integrated with Xfce [http://www.xfce.org/projects/orage/ Home page]<br />
* [[Osmo]] - A GTK+ personal organizer, which includes calendar, tasks manager and address book modules. [http://clayo.org/osmo/ Home page]<br />
* [http://aur.archlinux.org/packages.php?ID=21675 Rachota] - A portable time tracker for personal projects [http://rachota.sourceforge.net/en/ Home page]<br />
* [[Remind]] - A sophisticated calendar and alarm program [http://www.roaringpenguin.com/penguin/open_source_remind.php Home page]<br />
* [[Sunbird]] - The standalone Mozilla calendar application [http://www.mozilla.org/projects/calendar/sunbird/ Home page]<br />
* [[taskcoach]] - A simple open source todo manager to manage personal tasks and todo lists [http://taskcoach.sourceforge.net/ Home page] [http://aur.archlinux.org/packages.php?ID=6005 Package]<br />
* [[When]] - A simple command line personal calendar program [http://www.lightandmatter.com/when/when.html Home page]<br />
* [[Wyrd]] - A text-based front-end to Remind. [http://pessimization.com/software/wyrd/ Home page]<br />
<br />
== Translation and Localisation ==<br />
<br />
* [[Lokalize]] - the standard [[KDE]] tool for software translation. Available in Extra. [http://userbase.kde.org/Lokalize Home page]<br />
* [[virtaal]] - an editor for translation of both software and other text, based on Translate Toolkit. [http://aur.archlinux.org/packages.php?ID=21709 Available in AUR]. [http://translate.sourceforge.net/wiki/virtaal/index Home page]<br />
** Supported formats: Gettext (.po and .mo), XLIFF (.xlf), TMX, TBX, WordFast TM (.txt), Qt Linguist (.ts), Qt Phrase Book (.qph), OmegaT glossary (.tab and .utf8), ...<br />
** Shows suggestions from [[Apertium]], Google Translate, Microsoft Translator, [[Moses]], http://open-tran.eu, Translation Memories or TM servers<br />
* [[poedit]] - a simple Gettext/po-file translation tool. Available in Community. [http://www.poedit.net/ Home page]<br />
* [[OmegaT]] - "the translation memory tool", a general translators tool which contains a lot of translation memory features<br />
** Supported formats: html, MS Office 2007 XML, OpenDocument format, XLIFF/Okapi, MediaWiki, plain text, TMX, ...<br />
** Shows suggestions from Google Translate<br />
<br />
* [[pology]] - a set of Python tools for dealing with Gettext/po-files. See the [http://techbase.kde.org/Localization/Tools/Pology#About home page] for simple installation instructions.<br />
** May be used to translate po-files with [[Apertium]], see http://wiki.apertium.org/wiki/Translating_gettext for instructions. <br />
<br />
<br />
* [[Apertium]] - a free and open source rule-based machine translation platform. All released language data is [http://aur.archlinux.org/packages.php?K=apertium available in AUR]. [http://apertium.org/ Home page]<br />
** Supported formats: html, MS Office 2007 XML, OpenDocument format, TMX, some MediaWiki support, ... (use [[Pology]] or [[Virtaal]] for po-files)<br />
** See [http://wiki.apertium.org/wiki/Main_Page the wiki] for supported languages<br />
* [[Moses]] - a statistical machine translation tool (language data not included). [http://www.statmt.org/moses/ Home page]<br />
<br />
== Utilities ==<br />
=== Arch Package Management ===<br />
* {{App|Aurnotify|A tool set to notify the status of your favorite packages from AUR.|To use the aurnotify desklet visit: http://adesklets.sourceforge.net/desklets.html|{{Package AUR|aurnotify}}}}<br />
* {{App|[http://wiki.archlinux.org/index.php/AUR_Helpers#aurshell Aurshell]|Shell for Arch Linux AUR and ABS repository management.|http://github.com/husio/aursh|{{Package AUR|aurshell}}}}<br />
* {{App|[http://wiki.archlinux.org/index.php/AUR_Helpers#makeaur Makeaur]|A simple AUR wrapper.|http://ghost1227.com/makeaur|{{Package AUR|makeaur}}}}<br />
* {{App|[http://wiki.archlinux.org/index.php/Pacman_Tips#Color_output Pacman-color]|Command-line frontend for libalpm aka pacman with color patch.|http://www.archlinux.org/pacman/|{{Package AUR|pacman-color}}}}<br />
* {{App|Pacman-contrib|Utilities for use with the pacman package manager.|http://www.archlinux.org/pacman/|{{Package Official|pacman-contrib}}}}<br />
* {{App|Pkgtools|A collection of scripts for Arch Linux packages.|Which includes '''pkgfile'''; find what package owns a file. [[http://bbs.archlinux.org/viewtopic.php?pid=384196 Forum topic]]|{{Package Official|pkgtools}}}}<br />
* {{App|[[Powerpill]]|A wrapper for pacman that speeds up package retrieval by using aria2c for concurrent/segmented downloads.|http://xyne.archlinux.ca/info/powerpill|{{Package Official|powerpill}}}}<br />
* {{App|[http://wiki.archlinux.org/index.php/AUR_Helpers#slurpy Slurpy]|An AUR search/download/update helper in Python.|http://rsontech.net/projects/slurpy/|{{Package AUR|slurpy}}}}<br />
* {{App|[[TuPac]]|A cached pacman implementation that boosts some pacman operations: faster searches, AND searches, aur support, colored output, system sanity check, frontend friendly and more...|http://sourceforge.net/projects/tupac|{{Package AUR|tupac}}}} <br />
* {{App|[[Yaourt]]|A Pacman frontend with more features and AUR support.|http://www.archlinux.fr/yaourt-en/|{{Package AUR|yaourt}}}}<br />
<br><br />
See also: [[Comparison of AUR frontends]] and [[AUR Helpers]].<br />
<br />
=== Disk Usage Display Programs===<br />
* {{App|[[ncdu]]|A simple ncurses disk usage analyzer.|http://dev.yorhel.nl/ncdu|{{Package Official|ncdu}}}}<br />
* {{App|[[gt5]]|A diff-capable 'du-browser'.|http://gt5.sourceforge.net|{{Package AUR|gt5}}}}<br />
* {{App|[[Baobab]]|Baobab is a C/gtk+ application to analyse disk usage in any Gnome environment.|http://www.marzocca.net/linux/baobab|{{Package AUR|Baobab}}}}<br />
* {{App|[[Filelight]]|Filelight creates an interactive map of concentric, segmented rings that help visualise disk usage on your computer.|http://www.methylblue.com/filelight|{{Package Official|Filelight}}}}<br />
<br />
=== CD/DVD Burning Tools===<br />
* [[bashburn]] - A lightweight terminal based menu frontend for CD/DVD burning tools.<br />
* [[brasero]] - An application to burn CDs/DVDs for the Gnome Desktop.<br />
* [[gnomebaker]] - A GTK based CD/DVD burning application.<br />
* [[graveman]] - A GTK based CD/DVD burning application.<br />
* [[k3b]] - A feature-rich and easy to handle CD burning application for KDE.<br />
* [[nerolinux]] - A commercial CD/DVD burning tool (requires a valid key).<br />
* [[xcdroast]] - A lightweight CD/DVD burning tool.<br />
* [[xfburn]] - Xfburn is a simple CD/DVD burning tool based on libburnia libraries (xfce).<br />
<br />
===Clipboard Managers===<br />
* [[Parcellite]] - a lightweight yet feature-rich clipboard manager [http://parcellite.sourceforge.net/ Home page]<br />
* [[Glipper]] - Glipper is a clipboardmanager for GNOME with more features and plugin support [http://glipper.sourceforge.net/ Home page]<br />
<br />
=== Compression Tools ===<br />
* [[File Roller]] The default archive manager for GNOME.<br />
* [[p7zip]] - A command line port of 7-Zip for POSIX systems, including Linux. http://p7zip.sourceforge.net/ http://www.7-zip.org/<br />
* [[pbzip2]] - A threaded version of the bzip2 utility, can automatically scale up to as many cores as it finds in the system.<br />
* [[Squeeze]] - A featherweight front-end for command line archiving tools. Passworded archives are currently unsupported. http://squeeze.xfce.org/<br />
* [[XArchive]] - A GTK+ front-end for command line archiving tools.<br />
* [[Xarchiver]] - A lightweight, desktop independent front-end for command line archiving tools built with GTK2. http://xarchiver.sourceforge.net/<br />
<br />
=== File Managers ===<br />
* [[Dolphin]] - Default file manager for KDE 4 - http://dolphin.kde.org/<br />
* [[emelFM2]] - File manager that implements a three-pane design - http://emelfm2.net<br />
* [[Konqueror]] - Default file manager for KDE 2 and KDE 3 - http://www.konqueror.org/<br />
* [[Krusader]] - Advanced twin panel (commander style) file manager for KDE - http://www.krusader.org/<br />
* [[Midnight Commander]] - Terminal filemanager/shell that emulates Norton Commander - http://www.midnight-commander.org/<br />
* [[Nautilus]] - Extensible, heavyweight file manager used by default in GNOME with support for custom scripts - http://projects.gnome.org/nautilus/<br />
* [[PCManFM | PCMan File Manager]] - Part of the standard [[LXDE]] DE, a small and efficient graphical file manager - http://pcmanfm.sourceforge.net/<br />
* [[ROX-Filer]] - Small and fast file manager which can optionally manage desktop backgrounds and panels - http://roscidus.com/desktop/ROX-Filer<br />
* [[Thunar]] - [http://goodies.xfce.org/projects/thunar-plugins/start Extensible], medium weight file manager used by default in Xfce with support for plugins - http://thunar.xfce.org/<br />
* [[tuxcmd]] - Windowed file manager with 2 panels side by side similar to popular Total Commander or Midnight Commander file managers - http://tuxcmd.sourceforge.net/description.php<br />
* [[Vifm]] - Ncurses based file manager with vi-like keybindings - http://vifm.sourceforge.net/<br />
* [[Xfe]] - Small and very fast Commander like file manager - http://roland65.free.fr/xfe/<br />
<br />
=== Panels ===<br />
* [[fbpanel]] Lightweight, NETWM compliant desktop panel. [http://fbpanel.sourceforge.net/ Home page] [http://aur.archlinux.org/packages.php?ID=5255 Package]<br />
* [[LXPanel]] Lightweight X11 desktop panel and part of the LXDE DE. [http://lxde.org/ Home page] [http://aur.archlinux.org/packages.php?ID=17813 Package]<br />
* [[PyPanel]] Lightweight panel/taskbar written in Python and C. [http://pypanel.sourceforge.net/ Home page] [http://aur.archlinux.org/packages.php?ID=9118 Package]<br />
* [[Tint]] Simple panel/taskbar developed specifically for Openbox. [http://code.google.com/p/tint2/ Home page] [http://aur.archlinux.org/packages.php?ID=17082 Package]<br />
* [[BMPanel]] Lightweight, NETWM compliant desktop panel. [http://nsf.110mb.com/bmpanel/ Home page] [http://aur.archlinux.org/packages.php?ID=15165 Package]<br />
* [[Xfce4panel]] Default [[Xfce]] panel [http://www.xfce.org/projects/xfce4-panel/ Home page]<br />
<br />
=== System Monitoring ===<br />
*[[adesklet-systemmonitor]] - Modular stackable system monitors for adesklets http://adesklets.sourceforge.net/desklets.html<br />
*[[conky]] - advanced, highly configurable system monitor for X based on torsmo http://conky.sourceforge.net/<br />
*[[gkrellm]] - Simple, flexible system monitor package for GTK2; many plug-ins are available on AUR. http://members.dslextreme.com/users/billw/gkrellm/gkrellm.html<br />
<br />
=== Terminals ===<br />
* [[Aterm]] - An xterm replacement with transparency support http://aterm.sourceforge.net/ <br />
* [[Gnome-Terminal]] - GNOME default (standalone) terminal with support for Unicode and pseudo-transparency<br />
* [[Konsole]] - KDE's default terminal<br />
* [[lxterminal]] - VTE-based terminal emulator and c part of the LXDE DE. http://lxde.org/<br />
* [[Lilyterm]] — Lightweight and plain terminal emulator<br />
* [[mrxvt]] - Tabbed X terminal emulator based on rxvt code http://materm.sourceforge.net/index.html<br />
* [[roxterm]] - Tabbed, VTE-based terminal emulator http://roxterm.sourceforge.net/<br />
* [[rxvt-unicode]] (or urxvt) - A small, fast and customizable terminal which uses ~/.Xdefaults http://software.schmorp.de/pkg/rxvt-unicode.html<br />
* [[sakura]] - terminal emulator based on GTK and VTE. http://www.pleyades.net/david/sakura.php<br />
* [[terminator]] - A terminal emulator supporting multiple resizable terminal panes<br />
* [[xterm]] - The default of defaults, requires only X<br />
* [[Terminal]] - Xfce default terminal with support for a colorized prompt and a tabbed interface http://www.xfce.org/projects/terminal/<br />
<br />
=== Text Editors ===<br />
* [[Beaver]] - Early AdVanced EditoR.<br />
* [[Bluefish]] - GTK editor/IDE with an MDI interface, syntax highlighting and support for Python plugins http://bluefish.openoffice.nl/<br />
* [[Cssed]] - GTK2 based Cascading Style Sheets (CSS) editor http://cssed.sourceforge.net/<br />
* [[Emacs]] - The somewhat intimidating but famously extensible text editor with hundreds of tricks and add-ons <br />
* [[Geany]] is a text editor using the GTK2 toolkit with basic features of an integrated development environment.<br />
* [[Gedit]] - Part of the GNOME desktop, but has minimal dependencies: a GTK2 editor with syntax highlighting, automatic indentation, matching brackets, etc., and a number of add-ons to increase functionality<br />
* [[Kate]] The KDE Advanced Text Editor. A full-featured programmer's editor, with MDI and a filesystem browser.<br />
* [[KWrite]] (part of the KDE desktop) A lightweight text editor with syntax highlighting.<br />
* [[Tea]] a QT based feature rich text editor [http://www.archlinux.org/packages/community/x86_64/tea/ in AUR]<br />
* [[LeafPad]] - GTK+ based simple text editor http://tarot.freeshell.org/leafpad/<br />
* [[medit]] is intended to be a useful programming and around-programming text editor.<br />
* [[Mousepad]] - Lightweight text editor with support for word wrapping, line numbering and printing http://www.xfce.org/projects/mousepad/<br />
* [[Nano]] - A console based editor, similar to vim with a more intuitive interface, a good choice for newbies and casual users.<br />
* [[Scite]] - A generally useful editor with facilities for building and running programs http://www.scintilla.org/SciTE.html<br />
* [[Vim]] - "Vi improved," its many shortcuts and utilities may take a while to master but are a huge asset to programmers<br />
<br />
=== OCR tools ===<br />
There are several steps to the whole OCR process, the actual OCR engine is only part of this:<br />
# scanning<br />
# document layout analysis<br />
# optical character recognition<br />
# post-processing (formatting, PDF creation)<br />
<br />
* [[cuneiform]] is a command line OCR system originally developed and open sourced by Cognitive technologies. Supported languages: eng, ger, fra, rus, swe, spa, ita, ruseng, ukr, srp, hrv, pol, dan, por, dut, cze, rum, hun, bul, slo, lav, lit, est, tur. Available from [[pacman]]/community. https://launchpad.net/cuneiform-linux <br />
** [[YAGF]] is a graphical interface for the cuneiform text recognition program on the Linux platform. Available from [[AUR]]. http://symmetrica.net/cuneiform-linux/yagf-en.html<br />
<br />
* [[Tesseract]] is "probably one of the most accurate open source OCR engines available". Available from [[pacman]]/community. http://code.google.com/p/tesseract-ocr/<br />
* [[OCRopus]] is an OCR ''platform'', modules exist for document layout analysis, OCR engines (it can use Tesseract or its own engine), natural language modelling, etc. Available from [[AUR]]. http://code.google.com/p/ocropus/<br />
* [[gscan2pdf]] scans, runs Tesseract and creates a PDF all in one go<br />
<br />
* [[GOCR]]/JOCR (http://jocr.sourceforge.net/) is an OCR engine which also supports barcode recognition. Available from [[pacman]]/extra as "gocr". http://www.gnu.org/software/ocrad/<br />
* [[Ocrad]] is an OCR (Optical Character Recognition) program based on a feature extraction method. Available from [[pacman]]/extra. http://www.gnu.org/software/ocrad/<br />
* [[Kooka]] is a scanner GUI for KDE which supports the OCR engines [[GOCR]], [[Ocrad]] or [[KADMOS]]. Used to be part of kdegraphics4, but dropped out due to lack of development. http://kooka.kde.org/<br />
<br />
=== Trays ===<br />
* [[Docker]] is a docking application which acts as a system tray.<br />
* [[Stalonetray]] is a stand-alone system tray.<br />
* [[Trayer]] swallows GTK 1.2/2.x application docklets, and KDE docklets.<br />
<br />
== Desktop Environments (DE) ==<br />
* [[GNOME]] - Heavyweight DE that focuses on usability by offering simple controls and options http://www.gnome.org/<br />
* [[KDE]] - Heavyweight DE that focuses on customizeable options and integrated applications http://www.kde.org/<br />
* [[LXDE]] - Fully modular, lightweight DE based on Openbox offered with a suite of lightweight tools http://www.lxde.org/<br />
* [[ROX Desktop]] - Lightweight DE with excellent drag-and-drop support http://roscidus.com/desktop/<br />
* [[Xfce]] - Partially modular, medium weight DE which attempts to emulate the usability of GNOME http://www.xfce.org/<br />
<br />
== Window Managers (WM) ==<br />
=== Stacking Window Managers ===<br />
* [[Compiz]] - Compositing WM, similar to GNOME's Metacity http://freedesktop.org/wiki/Software/Compiz<br />
* [[Enlightenment]] - WM which attempts to provide minimal DE features with a native image viewer and file manager, amongst others http://www.enlightenment.org/<br />
* [[Fluxbox]] - Lightweight, easily configurable WM with support for panels and a tabbed interface http://www.fluxbox.org<br />
* [[JWM]] - Simple, stable and featherweight WM with native support for panels and buttons. XML-based configuration http://joewing.net/programs/jwm/<br />
* [[Openbox]] - Lightweight WM with numerous customization options and a mature code base. XML-based configuration http://icculus.org/openbox<br />
* [[pekwm]] - Lightweight, themeable WM configured with an intuitive Perl-like syntax http://pekwm.org/projects/pekwm<br />
* [[Sawfish]] - Medium weight WM, formerly the default WM in GNOME (subsequently substituted by Metacity) http://sawfish.wikia.com<br />
* [[Twm]] - Classic, customizable and very lightweight window manager; possibly the first designed for X11.<br />
* [[Xfwm4]] - Middleweight Compositing WM, [[Xfce]] default WM http://www.xfce.org/documentation/4.2/manuals/xfwm4<br />
<br />
=== Tiling Window Managers ===<br />
Window managers that tile work by partitioning off areas of the screen and are designed to maximize the usage of the screen without forcing the user to muck around with window positions and frames. See also [[Comparison of Tiling Window Managers]].<br />
* [[awesome]]<br />
* [[dwm]]<br />
* [[i3]]<br />
* [[Ion3]]<br />
* [[Musca]]<br />
* [[ratpoison]]<br />
* [[scrotwm]]<br />
* [[Stumpwm]]<br />
* [[subtle]]<br />
* [[wmii]]<br />
* [[Xmonad]]<br />
<br />
== See also ==<br />
* http://linuxappfinder.com/<br />
* http://www.linuxlinks.com/<br />
* http://en.wikipedia.org/wiki/List_of_open_source_software_packages<br />
<br />
* http://linuxappfinder.com/alternatives - Windows and OS X Software Alternatives<br />
* http://alternativeto.net/ - find alternatives to popular programs<br />
* http://www.linuxalt.com/ - Linux equivalents of Windows software</div>
Cantabile
https://wiki.archlinux.org/index.php?title=MOC&diff=121172
MOC
2010-11-12T13:41:07Z
<p>Cantabile: /* Configuration */ added info about the config and keymap files</p>
<hr />
<div>{{i18n|moc}}<br />
[[Category:Audio/Video (English)]]<br />
=Description=<br />
<br />
'''M'''usic '''O'''n '''C'''onsole is a lightweight music player. It consists of 2 parts, a server (Moc) and the player/interface (Mocp). <br />
This is similar to [[mpd]], but unlike mpd, Moc comes with a interface.<br />
<br />
=Installation=<br />
<br />
Sync and install with pacman:<br />
# pacman -S moc<br />
<br />
=Configuration=<br />
The package includes a sample configuration file at {{Filename|/usr/share/doc/moc/config.example}}. To configure moc, copy this file to {{Filename|~/.moc/config}} and edit it.<br />
<br />
For instructions about customising the keybindings, read {{Filename|/usr/share/doc/moc/keymap.example}}.<br />
<br />
If you want to use Moc with OSS v4.1 go to that [http://wiki.archlinux.org/index.php/OSS article].<br />
<br />
=Usage=<br />
<br />
To start moc:<br />
<br />
$ mocp<br />
<br />
This will start the server and interface. You will enter player interface. Some useful shortcuts to use mocp (case sensitive):<br />
<br />
{| class="wikitable"<br />
|-<br />
| Start playing a track<br />
| Enter<br />
|-<br />
| Pause track <br />
| Space or p<br />
|- <br />
| Play next track<br />
| n<br />
|-<br />
| Play previous track<br />
| b<br />
|-<br />
| Switch from playlist browsing to filesystem browsing (and vice versa)<br />
| tab<br />
|-<br />
| Add one track to the playlist<br />
| a<br />
|-<br />
| Add a folder recursively to playlist<br />
| A<br />
|-<br />
| Clear playlist<br />
| C<br />
|-<br />
| Increase volume 5%<br />
| . (dot)<br />
|-<br />
| Decrease volume 5%<br />
| , (comma)<br />
|-<br />
| Increase volume 1%<br />
| ><br />
|-<br />
| Decrease volume 1%<br />
| <<br />
|-<br />
| Change volume to 10%<br />
| meta + 1<br />
|-<br />
| Change volume to 20%<br />
| meta + 2<br />
|-<br />
| etc, etc...<br />
|-<br />
| Quit player<br />
| q<br />
|}<br />
<br />
NOTE: To shut down the server:<br />
$ mocp -x<br />
<br />
=Frontends=<br />
[http://aur.archlinux.org/packages.php?ID=39708 dmenu_mocp] is a dmenu frontend for moc<br />
<br />
[http://aur.archlinux.org/packages.php?ID=24338 moc-tray] is a perl gtk dock that gives you access to moc functions</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Lightweight_Applications&diff=121120
Lightweight Applications
2010-11-11T17:07:37Z
<p>Cantabile: /* Audio Players */ grouped the mpd clients together</p>
<hr />
<div>[[Category:Other desktop user's resources (English)]][[Category:General (English)]]<br />
{{i18n|Lightweight Applications}}<br />
<br />
Provides a list of lightweight software for those who wish to use programs that require less computer resources.<br />
<br />
==Internet==<br />
===Browsers===<br />
<br />
{{App|[[Wikipedia:Abaco (web browser)|Abaco]]|A multi-page graphical web browser|http://lab-fgb.com/abaco/|{{Package AUR|abaco}}}}<br />
{{App|[[Wikipedia:Arora (browser)|Arora]]|A cross platform web browser built using Qt and WebKit|http://code.google.com/p/arora/|{{Package Official|arora}}}}<br />
{{App|[[Wikipedia:Chromium (web browser)|Chromium]]|The middleweight, open-source project behind Google Chrome|http://code.google.com/chromium/|{{Package Official|chromium}}}}<br />
{{App|[[Wikipedia:Conkeror|Conkeror]]|A highly programmable web browser based on Mozilla XULRunner|http://conkeror.org/|{{Package Official|conkeror}}}}<br />
{{App|[[Wikipedia:Dillo|Dillo]]|A small, fast graphical web browser built on FLTK|http://www.dillo.org/|{{Package Official|dillo}}}}<br />
{{App|[[Wikipedia:ELinks|ELinks]]|An advanced and well-established feature-rich text mode web browser|http://elinks.or.cz/|{{Package Official|elinks}}}}<br />
{{App|Hv3|A minimalist web browser based on tkhtml3|http://tkhtml.tcl.tk/hv3.html|{{Package AUR|hv3}}}}<br />
[http://pwmt.org/projects/jumanji jumanji] - "a highly customizable and functional web browser"<br />
<br />
{{App|[[Wikipedia:Kazehakase|Kazehakase]]|GTK+ web browser that uses the Gecko rendering engine|http://kazehakase.sourceforge.jp/|{{Package Official|kazehakase}}}}<br />
{{App|[[Wikipedia:Links (web browser)|Links]]|A text WWW browser, similar to Lynx|http://links.twibright.com/|{{Package Official|links}}}}<br />
<br />
[http://luakit.org/projects/luakit/ Luakit] is a highly configurable, micro-browser framework based on the WebKit web content engine and the GTK+ toolkit. It is very fast, extensible by Lua and licensed under the GNU GPLv3 license.<br />
<br />
[http://www.twotoasts.de/index.php?/pages/midori_summary.html Midori] is a lightweight web browser based on Gtk and WebKit. It passes the ACID3 test (midori-git/AUR).<br />
<br />
[http://www.netsurf-browser.org Netsurf] is a featherweight browser written in C. Notable is its lack of JavaScript support and fast rendering through its own custom rendering engine.<br />
<br />
[http://aur.archlinux.org/packages.php?ID=37037 Sb] - A very lightweight webkit-based browser that uses keybindings to perform most things the URL bar would usually do.<br />
<br />
[http://surf.suckless.org surf] is another lightweight WebKit-based browser, which follows the [[suck less philosophy|suckless ideology]]. Which means, the software is even more lightweight (basically, the browser itself is a single C source file).<br />
<br />
[[Uzbl]] - "web interface tools which adhere to the unix philosophy."<br />
<br />
===Email Clients===<br />
<br />
[[alpine]] is another powerful, and user-friendly text-based mail and news client.<br />
<br />
[[mutt]] is a small but very powerful text-based mail client.<br />
<br />
[http://sylpheed.sraoss.jp/en/ Sylpheed] is a simple, lightweight but featureful, and easy-to-use GTK based e-mail client.<br />
<br />
[http://www.claws-mail.org/ Claws] is a user-friendly, lightweight, and fast GTK based email client.<br />
<br />
[[sup]] is yet another powerful, text-based mail client; it is still under development.<br />
<br />
===Instant Messengers===<br />
<br />
[[Bitlbee]] is a way to use other IM to your [[#IRC]] client.<br />
<br />
[http://funpidgin.sourceforge.net/ Carrier] is a fork of Pidgin with more options.<br />
<br />
[http://www.centerim.org Centerim] is a curses based fork of Centericq which supports several protocols.<br />
<br />
[http://www.emesene.org/ emesene] is a Python/GTK+ instant messenger for the Windows Live Messenger network.<br />
<br />
[http://developer.pidgin.im/wiki/Using%20Finch Finch] is a curses based version of Pidgin.<br />
<br />
[[Pidgin]] is a multiprotocol instant messenger.<br />
<br />
[http://pidgin.im Pidgin Light] is a light Pidgin version without gstreamer, tcl, tk, xscreensaver support.<br />
<br />
===IRC===<br />
<br />
[http://nenolod.net/ Conspire] Lightweight, simple, and powerful.<br />
<br />
[[Irssi]] is a modular text mode IRC client with Perl scripting.<br />
<br />
[[ERC]] is a powerful, modular, and extensible IRC client for [[Emacs]].<br />
<br />
[http://tools.suckless.org/ii II] Ultimate lightweight, literally `tail -f` the convo and `echo` back your replies.<br />
<br />
[http://www.ueber.net/code/r/ircfs ircfs] is a file system interface to irc written in [http://limbo.cat-v.org Limbo].<br />
<br />
[http://lostirc.sourceforge.net LostIRC] is a simple IRC client.<br />
<br />
[http://www.scrollz.com ScrollZ] is an advanced IRC client based on ircII.<br />
<br />
[http://weechat.org/ WeeChat] is a fast, light & extensible curses-based IRC client.<br />
<br />
[http://xchat.org XChat] is a GTK+ X client with Perl and Python scripting support.<br />
<br />
[http://bitbucket.org/emg/pcw pcw] is a frontend for [http://tools.suckless.org/ii ii] that opens a new terminal for each channel (depends on [http://bitbucket.org/emg/srw srw] by default)<br />
<br />
===Torrents===<br />
{{App|[[aria2]]|Command-line download manager that supports HTTP/HTTPS, FTP, BitTorrent and MetaLink protocols|http://aria2.sourceforge.net/|{{Package Official|aria2}}}}<br />
{{App|[[Wikipedia:Deluge_(software)|Deluge]]|PyGTK torrent client with daemon, webgui, and many other functionalities. I recommend Deluge-GIT from the AUR as it has many vital bugfixes.|http://deluge-torrent.org/|{{Package Official|deluge}}}}<br />
{{App|[[Wikipedia:QBittorrent|qBittorrent]]|The closest open source (GNU GPL v2 license) equivalent to µtorrent|http://qbittorrent.sourceforge.net/|{{Package Official|qbittorrent}}}}<br />
{{App|[[Wikipedia:RTorrent|rTorrent]]|Simple and lightweight ncurses BitTorrent client|http://libtorrent.rakshasa.no/|{{Package Official|rtorrent}}}}<br />
{{App|[[Wikipedia:Transmission (BitTorrent client)|Transmission]]|Simple and easy-to-use BitTorrent client with GTK+ and Qt GUI and CLI front-ends|http://www.transmissionbt.com/|{{Package Official|transmission}}}}<br />
<br />
===News Aggregators===<br />
[[Canto]] - A ncurses RSS aggregator http://codezen.org/canto/<br />
<br />
[[Gnus]] - mail, nntp, rss client for Emacs.<br />
<br />
[[Newsbeuter]] - A ncurses RSS aggregator with layout and keybinding similar to mutt. Does not use the traditional 3 panes setup.<br />
<br />
[[Rawdog]] - An "RSS Aggregator Without Delusions Of Grandeur" that parses RSS/CDF/Atom feeds into a static HTML page of articles in date order http://offog.org/code/rawdog.html<br />
<br />
[[Snownews]] - Text mode RSS newsreader.<br />
<br />
==Multimedia==<br />
<br />
===Audio Players===<br />
<br />
[http://cmus.sourceforge.net/ C* Music Player] is a very feature-rich ncurses-based music player.<br />
<br />
[http://deadbeef.sourceforge.net/ Deadbeef] is a light and fast music player with many features, no GNOME or KDE dependencies, supports console-only and as well GTK2-gui, comes with many plugins, and has a metadata editor. <br />
<br />
[http://sourceforge.net/projects/cplay/ cplay] is a curses front-end for various audio players.<br />
<br />
[http://code.google.com/p/gogglesmm/ Goggles Music Manager] is a music collection manager and player that automatically categorizes your music, supports gapless playback, features easy tag editing, and internet radio support.<br />
<br />
[http://aur.archlinux.org/packages.php?ID=11623 Herrie] is a minimalistic console-based music player with native AudioScrobbler support.<br />
<br />
[http://moc.daper.net/ MOC (Music On Console)] is an ncurses console audio player with support for the MP3, Ogg, and WAV formats.<br />
<br />
[http://pragha.wikispaces.com/ Pragha] is a GTK+ music manager that was a fork of Consonance Music Manager.<br />
<br />
[http://www.mpg123.de/ mpg123] A fast free MP3 console audio player for Linux, FreeBSD, Solaris, Hpux and near all other UNIX systems. Also decodes mp1 and mp2 files.<br />
<br />
[[mpd|MPD]] clients:<br />
<br />
[http://ario-player.sourceforge.net/ Ario] is very feature-rich GTK2 client for [[mpd]], inspired by Rhythmbox<br />
<br />
[http://hem.bredband.net/kaw/ncmpc/ ncmpc] is a curses client for [[mpd]].<br />
<br />
[http://unkart.ovh.org/ncmpcpp/ ncmpcpp] is an almost exact clone of ncmpc with some new features.<br />
<br />
[http://www.archlinux.org/packages/community/i686/qmpdclient/ QmpdClient] is Qt4 based mpd client.<br />
<br />
[http://sonata.berlios.de/ Sonata] is an elegant GTK+ music client for [[mpd]].<br />
<br />
===Image Editors===<br />
<br />
[http://mtpaint.sourceforge.net/ mtPaint] is a graphic editing program geared towards creating indexed palette images and pixel art.<br />
<br />
===Image Viewers===<br />
<br />
[http://linuxbrit.co.uk/feh/ Feh] is a fast, lightweight image viewer that uses imlib2.<br />
<br />
[http://lxde.sourceforge.net/gpicview/ GPicView] is a simple and fast image viewer for X. Made by the developers of [[LXDE]]<br />
<br />
[http://gqview.sourceforge.net/ GQview] is an image browser that features single click access to view images and move around the directory tree.<br />
<br />
[http://geeqie.sourceforge.net/ Geeqie] is an image browser/viewer fork of GQview. Adds additional functionality such as support for RAW files.<br />
<br />
{{App|Mirage|PyGTK image viewer featuring support for crop and resize, custom actions and a thumbnail pane.|http://mirageiv.berlios.de|{{Package Official|mirage}}}}<br />
<br />
[http://goodies.xfce.org/projects/applications/ristretto Ristretto] is a fast and lightweight picture-viewer for the Xfce desktop environment.<br />
<br />
[http://spiegl.de/qiv/ QIV] (Quick Image Viewer) is a very small and fast gdk/Imlib image viewer.<br />
<br />
{{App|Viewnior|Minimalistic GTK2 viewer featuring support for flip, rotate, animations and configurable mouse actions|http://xsisqox.github.com/Viewnior/about.html|{{Package Official|viewnior}}}}<br />
<br />
[http://web.archive.org/web/19981207030422/http://world.std.com/~jimf/xloadimage.html Xloadimage] is the classic X image viewer.<br />
<br />
===Video Players===<br />
<br />
[http://kdekorte.googlepages.com/gnomemplayer Gnome-Mplayer] is a simple GTK-based GUI for [[mplayer]] without GNOME dependencies<br />
<br />
[[mplayer]] and [[mencoder]] support a complete and versatile array of video/audio formats.<br />
<br />
[http://smplayer.sourceforge.net/ SMPlayer] is a middleweight QT frontend for mplayer with additional patches.<br />
<br />
[http://www.videolan.org/vlc/ VLC] is a a middleweight video player with support for a wide variety of audio/video formats.<br />
<br />
==Office==<br />
<br />
===Calendars===<br />
<br />
[http://palcal.sourceforge.net/ Pal] is a very lightweight calendar with both interactive and non-interactive interfaces.<br />
<br />
[http://culot.org/calcurse/ Calcurse] is a text-based curses calendar and scheduling system.<br />
<br />
[http://www.roaringpenguin.com/products/remind Remind] is a highly sophisticated text-based calendaring and notification system.<br />
<br />
[http://pessimization.com/software/wyrd/ Wyrd] is an curses front-end to Remind.<br />
<br />
[http://www.duke.edu/~dgraham/wxRemind/ wxRemind] is a Python text and graphical frontend to Remind.<br />
<br />
===PDF Tools===<br />
<br />
[http://code.google.com/p/apvlv/ apvlv] is a lightweight PDF viewer with VIM key bindings.<br />
<br />
[http://www.emma-soft.com/projects/epdfview/ ePDFView] is a free lightweight PDF document viewer using Poppler and GTK+ libraries.<br />
<br />
[http://ccxvii.net/mupdf/ MuPDF] is very fast PDF viewer and toolkit written in portable C. Features CJK font support.<br />
<br />
[http://www.foolabs.com/xpdf/ Xpdf] is a viewer for Portable Document Format (PDF) files.<br />
<br />
[http://zathura.pwmt.org/projects/zathura zathura] is another lightweight PDF viewer similar to apvlv, only lighter<br />
<br />
===Text Editors===<br />
<br />
[http://acme.cat-v.org Acme] a minimalist and flexible programming environment by Rob Pike.<br />
<br />
[http://www.nongnu.org/beaver/ Beaver] is an Early AdVanced EditoR.<br />
<br />
[http://www.geany.org Geany] is a text editor using the GTK+ 2 toolkit with basic features of an integrated development environment.<br />
<br />
[http://edile.googlecode.com Edile] is a PyGTK code/scripting editor implemented in one file.<br />
<br />
[http://tarot.freeshell.org/leafpad/ Leafpad] is a notepad clone for GTK+ 2.x that emphasizes simplicity.<br />
<br />
[http://mooedit.sourceforge.net/ medit] is a lightweight IDE text editor featuring support for tabs, sessions, plugins and syntax highlighting.<br />
<br />
[http://www.xfce.org/projects/mousepad/ Mousepad] is a simple text editor for Xfce based on Leafpad.<br />
<br />
[[nano]] is a console text editor based on pico with on-screen key binding help.<br />
<br />
[http://pyroom.org/ PyRoom] is a great distractionless PyGTK text editor, a clone of the infamous WriteRoom<br />
<br />
[http://sam.cat-v.org Sam] a graphical text editor by Rob Pike (still used by Ken Thompson and others).<br />
<br />
Vi, [[Vim]], gVim, the classic vi text editor.<br />
<br />
===Word Processors===<br />
<br />
[[Abiword]] is a full-featured word processor, there is also an even lighter version in the AUR, [http://aur.archlinux.org/packages.php?ID=25601/ Abiword-light].<br />
<br />
[http://txt2tags.sourceforge.net txt2tags] is a dead-simple, KISS-compliant lightweight, human-readable markup language to produce rich format content out of plain text files<br />
<br />
===Todo List Managers===<br />
[http://aur.archlinux.org/packages.php?ID=7673 Todo.txt] manages your Todo list from the command line.<br />
<br />
[http://orgmode.org org-mode] - an [[Emacs]] Mode for Notes, Project Planning, and Authoring.<br />
<br />
==System==<br />
<br />
===File Managers===<br />
<br />
[http://emelfm2.net/ emelFM2] is file manager that implements the popular two-pane design.<br />
<br />
[http://www.midnight-commander.org Midnight Commander] is a console-based, dual-paned, file manager.<br />
<br />
[http://pcmanfm.sourceforge.net/ PCManFM] is a lightweight file manager which features tabbed browsing and can optionally manage the desktop background.<br />
<br />
[[Ranger]] is a console based file manager with vi bindings, customizability, and lots of features.<br />
<br />
[http://rox.sourceforge.net ROX] is a small and fast file manager which can optionally manage the desktop background and panels.<br />
<br />
[[Thunar]] can be run as a daemon with excellent start up and directory load times. Features support for customizable actions.<br />
<br />
[[Vifm]] is a ncurses based two-pane file manager with vi like keybindings.<br />
<br />
[http://roland65.free.fr/xfe/index.php/ Xfe] X File Explorer (Xfe) is an MS-Explorer or Commander like file manager for X.<br />
<br />
===GUI Compression Tools===<br />
<br />
[http://squeeze.xfce.org/ Squeeze] is a modern and advanced archive manager.<br />
<br />
[http://xarchive.sourceforge.net Xarchive] is a GTK+ 2 front-end for various command line archiving tools.<br />
<br />
[http://xarchiver.sourceforge.net/ Xarchiver] is a lightweight desktop independent archive manager built with GTK+ 2. At the time of writing, it appears to be the most functional and up to date of the three tools listed here.<br />
<br />
===CD/DVD Burning Tools===<br />
<br />
{{App|recorder|Simple frontend to cdrkit/cdrtools, cdrdao, mkisofs and growisofs with limited options and preferences|http://code.google.com/p/recorder/|{{Package Official|recorder}}}}<br />
{{App|Xfburn|Simple frontend to the libburnia libraries with support for CD/DVD(-RW), ISO images and BurnFree.|http://www.xfce.org/projects/xfburn/|{{Package Official|xfburn}}}}<br />
<br />
===Login managers===<br />
<br />
[[CDM]] provides an ultra-minimalistic, yet full-featured login manager written in bash.<br />
<br />
[[SLiM]] provides a lightweight and elegant graphical login solution.<br />
<br />
[[Qingy]] is ultralight and very configurable graphical login independent on X Windows.<br />
<br />
===Monitors===<br />
<br />
[[Conky]] is a lightweight, scriptable system monitor.<br />
<br />
[http://htop.sourceforge.net/ htop] is a simple, ncurses interactive process viewer.<br />
<br />
[http://wiki.lxde.org/en/LXTask LXTask] is a lightweight task manager for [[LXDE]].<br />
<br />
===Panels===<br />
<br />
[http://nsf.110mb.com/bmpanel/ BMPanel] (BitMap Panel) is a lightweight, NETWM compliant panel for the X11 system.<br />
<br />
[http://fbpanel.sourceforge.net fbpanel] is a lightweight, NETWM compliant desktop panel.<br />
<br />
[http://lxde.org LXPanel] is a lightweight X11 desktop panel (part of LXDE).<br />
<br />
[http://pypanel.sourceforge.net/ PyPanel] is a lightweight panel/taskbar written in Python and C ([[PyPanel|HOWTO]]).<br />
<br />
[http://code.google.com/p/tint2/ Tint] is a simple panel/taskbar intentionally made for openbox3, but should also work with other window managers ([[Tint|HOWTO]]).<br />
<br />
[http://www.failedprojects.de/pancake/ pancake] is a highly configurable, modular panel for X.<br />
<br />
===Terminals===<br />
<br />
[http://lilyterm.luna.com.tw/index_en.html Lilyterm] is a light and easy to use libvte based X Terminal Emulator.<br />
<br />
[http://rox.sourceforge.net ROXTerm] is a tabbed, VTE-based terminal emulator with a small footprint.<br />
<br />
[[urxvt]] is a highly extendable unicode enabled rxvt-clone terminal emulator featuring tabbing, url launching, quake-style dropdown, pseudo-transparency, and is extensible with perl.<br />
<br />
[http://www.pleyades.net/david/sakura.php Sakura] is a terminal emulator based on GTK+ and VTE.<br />
<br />
[http://invisible-island.net/xterm/ xterm] is a terminal emulator for the X Window System.<br />
<br />
===Trays===<br />
<br />
[http://icculus.org/openbox/2/docker/ Docker] is a docking application which acts as a system tray.<br />
<br />
[http://stalonetray.sourceforge.net Stalonetray] is a stand-alone system tray.<br />
<br />
[http://gna.org/projects/fvwm-crystal/ Trayer] swallows GTK+ 1.2/2.x application docklets, and KDE docklets.<br />
<br />
===Window managers===<br />
<br />
[[Awesome]] is a floating and tiling window manager initially based on a [[dwm]] code rewriting.<br />
<br />
[[Dwm]] is a featherweight dynamic window manager configured by editing the source itself. <br />
<br />
[[Evilwm]] is a minimalist floating window manager with an installed size of only 0.07 MB.<br />
<br />
[[Fluxbox]] is a lightweight and highly configurable window manager.<br />
<br />
[http://www.fvwm.org/ FVWM] is a lightweight, flexible and highly-configurable Window Manager.<br />
<br />
[[i3]] is a manual tiling window manager which places client into containers.Containers can be stacked (like wmii) or tabbed (like ion3). i3 also supports floating windows. <br />
<br />
[[JWM]] is a small and fast stacking window manager featuring native support for customizable panels/buttons and a system tray dock.<br />
<br />
[[Musca]] is a very lightweight window manager which has features from dwm and ratpoison. Uses about 350-400KB of memory.<br />
<br />
[[Openbox]] is another lightweight and highly configurable window manager.<br />
<br />
[[PekWM]] is small and easily configurable window manager.<br />
<br />
[[Ratpoison]] is a keyboard-oriented, customizable lightweight window manager, modelled after GNU Screen.<br />
<br />
[[Scrotwm]] is a small dynamic tiling window manager for X11. It is written in C and configured with a text configuration file.<br />
<br />
[[Subtle]] is a semi-automatic tiling window manager with a strong focus on easy but customizable handling and look and feel.<br />
<br />
[http://incise.org/tinywm.html TinyWM] is a tiny window manager that was created as an exercise in minimalism, and it is also helpful in learning some of the very basics of creating a window manager. It is around 50 lines of C, and there is a Python version using python-xlib.<br />
<br />
[[Twm]] is a classic, customizable and very lightweight window manager; possibly the first designed for X11.<br />
<br />
[[Window Maker]] is an elegant and fast floating window manager. It is an implementation NeXTSTEP, the precursor to Mac OS X. It includes functionality to launch applications and manage iconified windows. It is easy to configure both with the included GUI application and by editing simple text files.<br />
<br />
[[Xfce]] is a desktop environment much lighter but similar to GNOME. It includes the xfwm4 window manager.<br />
<br />
[[Xmonad]] is a tiling window manager for X, written and configured in Haskell.<br />
<br />
[[Wmfs]] (Window Manager From Scratch) is a lightweight and highly configurable tiling window manager for X.<br />
<br />
[[Wmii]] is a small, dynamic window manager for X11. It is scriptable, has a 9p filesystem interface and supports classic and tiling (acme-like) window management. It aims to maintain a small and clean (read hackable and beautiful) codebase.<br />
<br />
==Games==<br />
[[Chromium-BSU]] is a top scrolling shooter with very low OpenGL requirements.<br />
<br />
[[Lbreakout2]] is a very efficient arkanoid clone. Let's break the bricks!<br />
<br />
[[Ltris]] is a very nice Tetris clone.<br />
<br />
== Links ==<br />
<br />
[http://bbs.archlinux.org/viewtopic.php?id=88515 Arch Linux Forums / LnF Awards 2010] - The best Light & Fast apps of 2010.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Master_Boot_Record&diff=120461
Master Boot Record
2010-11-01T14:28:43Z
<p>Cantabile: added Syslinux to "Related"</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:Mainboards and BIOS (English)]]<br />
[[Category:System recovery (English)]]<br />
{{i18n|Master Boot Record}}<br />
{{Article summary start}}<br />
{{Article summary text|An overview of the Master Boot Record; the first sector of a partitioned data storage device.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Arch Boot Process}}<br />
{{Article summary wiki|GRUB}}<br />
{{Article summary wiki|GRUB2}}<br />
{{Article summary wiki|LILO}}<br />
{{Article summary wiki|Syslinux}}<br />
{{Article summary end}}<br />
<br />
The Master Boot Record (MBR) is the first 512 bytes of a storage device. The MBR is not a partition; it is reserved for the operating system's bootloader and the storage device's partition table.<br />
<br />
== Boot process ==<br />
<br />
Booting is a multi-stage process. Most PCs today initialize system devices with firmware called the [http://en.wikipedia.org/wiki/BIOS BIOS] (Basic Input/Output System), which is typically stored in a dedicated ROM chip on the system board. After system devices have been initialized, the BIOS looks for the bootloader on the MBR of the first recognized storage device (hard disk drive, solid state drive, CD/DVD drive, USB drive...) or the first partition of the device. It then executes that program. The bootloader reads the partition table, and is then capable of loading the operating system(s). Common GNU/Linux bootloaders include [[GRUB]] and [[LILO]].<br />
<br />
== History == <br />
<br />
The MBR consists of a short piece of assembly code (the initial bootloader &ndash; 446 bytes), a partition table for the 4 primary partitions (16 bytes each) and a ''sentinel'' (0xAA55).<br />
<br />
The "Conventional" Windows/DOS MBR bootloader code will check the partition table for one and only one ''active'' partition, read X sectors from this partition and then transfer control to the operating system. The Windows/DOS bootloader can ''not'' boot an Arch Linux partition because it is not designed to load the Linux kernel, and it can only cater for an ''active'', ''primary'' partition (which GRUB safely ignores).<br />
<br />
The [[GRUB|GRand Unified Bootloader (GRUB)]] is the de facto standard bootloader for GNU/Linux, and users are recommended to install it on the MBR to allow booting from ''any'' partition, whether it be primary or logical.<br />
<br />
== Backup and restoration ==<br />
<br />
Because the MBR is located on the disk it can be backed up and later recovered.<br />
<br />
To backup the MBR:<br />
<br />
dd if=/dev/hda of=/path/mbr-backup bs=512 count=1<br />
<br />
Restore the MBR:<br />
<br />
dd if=/path/mbr-backup of=/dev/hda bs=512 count=1<br />
<br />
{{Warning|Restoring the MBR with a mismatching partition table will make your data unreadable and nearly impossible to recover. If you simply need to reinstall the bootloader see [[GRUB]] or [[LILO]].}}<br />
<br />
To erase the MBR (may be useful if you have to do a full reinstall of another operating system) only the first 446 bits are zeroed because the rest of the data contains the partition table:<br />
<br />
dd if=/dev/zero of=/dev/hda bs=446 count=1<br />
<br />
== Restoring a Windows boot record ==<br />
<br />
Windows by convention (and for ease of installation) is usually installed on the first partition and installs its partition table and reference to its bootloader to the first sector of that partition. If you accidentally install a bootloader like GRUB to the Windows partition or damage the boot record in some other way, you will need to use a utility to repair it. Microsoft includes an boot sector fix utility {{Codeline|FIXBOOT}} and MBR fix utility called {{Codeline|FIXMBR}} on their recovery CDs or sometimes the install CD. Using this method you can fix the reference on the boot sector of the first partition to the bootloader file and fix the reference on the MBR to the first partition respectively. After doing this you will have to [[GRUB#Bootloader installation|reinstall GRUB]] to the MBR as is intended to in the first place (the GRUB bootloader can be assigned to load the Windows bootloader when defined to).<br />
<br />
If you wish to revert back to using Windows, you can use the {{Codeline|FIXBOOT}} command which chains from the MBR to the boot sector of the first partition to restore you normal automatic loading of the Windows operating system.<br />
<br />
Of note, there is a Linux utility called {{Codeline|ms-sys}} that can install MBR's. However this utility is only currently capable of writing new MBR's (all OS's and file systems supported) and boot sectors (a.k.a. boot record i.e. equivalent to using {{Codeline|FIXBOOT}}) for FAT file systems. Most LiveCDs don't have this utility by default so it will need to be installed first, or you can look at a rescue CD that does have it like [http://partedmagic.com/ Parted Magic].<br />
<br />
First, write the partition info (table) again by:<br />
<br />
ms-sys --partition /dev/sda1<br />
<br />
Next write a Windows 2000/XP/2003 MBR:<br />
<br />
ms-sys --mbr /dev/sda # Read options for different versions<br />
<br />
Then write the new boot sector (boot record)<br />
<br />
ms-sys -(1-6) # Read options to discover the correct FAT record type<br />
<br />
{{Codeline|ms-sys}} can also write Windows 98, ME, Vista, and 7 MBRs as well, see {{Codeline|ms-sys -h}}.<br />
<br />
== Resources ==<br />
<br />
* [http://kb.iu.edu/data/aijw.html What is a Master Boot Record (MBR)?]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Syslinux&diff=120460
Syslinux
2010-11-01T14:21:30Z
<p>Cantabile: Added i18n thingy and summary+related articles box</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
{{i18n|Syslinux}}<br />
{{Article summary start}}<br />
{{Article summary text|Describes installing and configuring Syslinux, a collection of bootloaders.}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|GRUB}}<br />
{{Article summary wiki|grub-gfx}}<br />
{{Article summary wiki|GRUB2}}<br />
{{Article summary wiki|LILO}}<br />
{{Article summary wiki|MBR}}<br />
{{Article summary end}}<br />
Syslinux is a collection of boot loaders capable of booting from hard drives, CDs and over the network via PXE. It supports the fat, ext2, ext3, ext4 and btrfs file systems.<br />
<br />
= Using syslinux to boot your Arch Linux system =<br />
<br />
== Installing syslinux ==<br />
<br />
Make sure you have the ''syslinux'' package installed. Then install syslinux onto your boot partition, which must contain a ext2, ext3, ext4 or btrfs file system.<br />
# mkdir /boot/syslinux<br />
# extlinux --install /boot/syslinux<br />
/boot/syslinux/ is device /dev/sda1<br />
Next, you need mark your boot partition active in your partition table:<br />
# fdisk -l /dev/sda<br />
[...]<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 * 2048 104447 51200 83 Linux<br />
/dev/sda2 104448 625142447 312519000 83 Linux<br />
Once that is the case, install a master boot record:<br />
# cat /usr/lib/syslinux/mbr.bin > /dev/sda<br />
When you reboot your system now, you will have a syslinux prompt. To automatically boot your system, you still need to create a configuration file.<br />
<br />
== Configuring syslinux ==<br />
<br />
The syslinux configuration file is ''syslinux.cfg'' in the syslinux folder, in our case ''/boot/syslinux/syslinux.cfg''.<br />
<br />
=== Booting Arch Linux ===<br />
<br />
This is a simple configuration file that will show a boot: prompt and automatically boot after 5 seconds.<br />
<br />
PROMPT 1<br />
TIMEOUT 50<br />
DEFAULT arch<br />
<br />
LABEL arch<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
This example assumes that /boot is a separate mount point. If /boot is the same partition as /, you have to replace ''/vmlinuz26'' by ''/boot/vmlinuz26'' and so on.<br />
<br />
If you want to boot directly without seeing a prompt, set PROMPT to 0 above. Instead of LINUX, the keyword KERNEL can also be used. KERNEL tries to detect the file type of the file, while LINUX always expects a Linux kernel.<br />
<br />
=== Boot menu ===<br />
<br />
Syslinux also allows you to use a boot menu. To use it, copy the menu COM32 module to your syslinux folder:<br />
# cp /usr/lib/syslinux/menu.c32 /boot/syslinux/<br />
If /boot is the same partition as /, a symlink will also work<br />
# ln -s /usr/lib/syslinux/menu.c32 /boot/syslinux/<br />
Now, adjust the configuration file:<br />
UI menu.c32<br />
PROMPT 0<br />
<br />
MENU TITLE Boot Menu<br />
TIMEOUT 50<br />
DEFAULT arch<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
For more details about the menu system, see [http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=doc/menu.txt].<br />
<br />
=== Chainloading ===<br />
<br />
If you want to chainload other operating systems (such as Windows) or boot loaders, copy (or symlink) the ''chain.c32'' module to the syslinux folder (for details, see the instructions in the previous section). Then, create a section in the configuration file:<br />
<br />
LABEL windows<br />
MENU LABEL Windows<br />
COM32 chain.c32<br />
APPEND hd0 3<br />
<br />
''hd0 3'' is the third partition on the first BIOS drive - drives are counted from zero, but partitions are counted from one. For more details about chainloading, see [http://syslinux.zytor.com/wiki/index.php/Comboot/chain.c32].<br />
<br />
=== Using memtest ===<br />
<br />
Use this LABEL section to launch memtest (install the ''memtest86'' package):<br />
<br />
LABEL memtest<br />
MENU LABEL Memtest86+<br />
LINUX /memtest86+/memtest.bin<br />
<br />
=== HDT ===<br />
<br />
HDT (Hardware Detection Tool) displays hardware information. Like before, the .c32 file has to be copied or symlinked from /boot/syslinux/.<br />
<br />
LABEL hdt<br />
MENU LABEL Hardware Info<br />
COM32 hdt.c32<br />
<br />
=== Reboot and power off ===<br />
<br />
Use the following sections to reboot or power off your machine.<br />
<br />
LABEL reboot<br />
MENU LABEL Reboot<br />
COM32 reboot.c32<br />
<br />
LABEL poweroff<br />
MENU LABEL Power Off<br />
COMBOOT poweroff.com</div>
Cantabile
https://wiki.archlinux.org/index.php?title=GRUB_Legacy&diff=120387
GRUB Legacy
2010-10-31T12:21:49Z
<p>Cantabile: added Syslinux to "related articles"</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:System recovery (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|GRUB}}<br />
{{Article summary start}}<br />
{{Article summary text|Covers various aspects of Arch Linux's default bootloader, the GRand Unified Bootloader (GRUB).}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|GRUB2}}<br />
{{Article summary wiki|grub-gfx}}<br />
{{Article summary wiki|LILO}}<br />
{{Article summary wiki|Syslinux}}<br />
{{Article summary wiki|MBR}}<br />
{{Article summary end}}<br />
<br />
[http://www.gnu.org/software/grub/ GNU GRUB] is a [http://www.gnu.org/software/grub/manual/multiboot/ multiboot] bootloader. It was derived from GRUB, the GRand Unified Bootloader, which was originally designed and implemented by Erich Stefan Boleyn. <br />
<br />
Briefly, the ''bootloader'' is the first software program that runs when a computer starts. It is responsible for loading and transferring control to the Linux kernel. The kernel, in turn, initializes the rest of the operating system.<br />
<br />
Currently, GRUB is the de facto standard bootloader of Linux, and is expected to be superseded by [[GRUB2]] in the near future. When this happens, "GRUB" will become "GRUB Legacy".<br />
<br />
== Installation ==<br />
<br />
The GRUB package is installed by default when you install Arch Linux. If you previously selected not to install this package, you can install now via:<br />
<br />
# pacman -S grub<br />
<br />
Additionally, GRUB must be installed to the boot sector of a drive or partition to serve as a bootloader. This is covered in the [[#Bootloader installation]] section.<br />
<br />
== Configuration ==<br />
<br />
The configuration file is located at {{Filename|/boot/grub/menu.lst}}. Edit this file to suit your needs.<br />
<br />
* {{Codeline|timeout #}} -- time to wait (in seconds) before the {{Codeline|default}} operating system is automatically loaded.<br />
* {{Codeline|default #}} -- the default boot entry that is chosen when the {{Codeline|timeout}} has expired.<br />
<br />
An example configuration ({{Filename|/boot}} is on a separate partition):<br />
<br />
{{File<br />
|name=/boot/grub/menu.lst<br />
|content=<nowiki><br />
# Config file for GRUB - The GNU GRand Unified Bootloader<br />
# /boot/grub/menu.lst<br />
<br />
# DEVICE NAME CONVERSIONS<br />
#<br />
# Linux Grub<br />
# -------------------------<br />
# /dev/fd0 (fd0)<br />
# /dev/sda (hd0)<br />
# /dev/sdb2 (hd1,1)<br />
# /dev/sda3 (hd0,2)<br />
#<br />
<br />
# FRAMEBUFFER RESOLUTION SETTINGS<br />
# +-------------------------------------------------+<br />
# | 640x480 800x600 1024x768 1280x1024<br />
# ----+--------------------------------------------<br />
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775<br />
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793<br />
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794<br />
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795<br />
# +-------------------------------------------------+<br />
# for more details and different resolutions see<br />
# http://wiki.archlinux.org/index.php/GRUB#Framebuffer_Resolution<br />
<br />
# general configuration:<br />
timeout 5<br />
default 0<br />
color light-blue/black light-cyan/blue<br />
<br />
# boot sections follow<br />
# each is implicitly numbered from 0 in the order of appearance below<br />
#<br />
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.<br />
#<br />
#-*<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 ro<br />
initrd /kernel26.img<br />
<br />
# (1) Windows<br />
#title Windows<br />
#rootnoverify (hd0,0)<br />
#makeactive<br />
#chainloader +1<br />
</nowiki>}}<br />
<br />
=== Finding GRUB's root ===<br />
<br />
GRUB must be told where its files reside on the system, since multiple instances may exist (i.e., in multi-boot environments). GRUB files always reside under {{Filename|/boot}}, which may be on a dedicated partition.<br />
<br />
{{Note|GRUB defines storage devices differently than conventional kernel naming does.<br />
<br />
* Hard disks are defined as '''(hdX)'''; this also refers to any USB storage devices.<br />
* Device and partitioning numbering begin at zero. For example, the first hard disk recognized in the BIOS will be defined as '''(hd0)'''. The second device will be called '''(hd1)'''. This also applies to partitions. So, the second partition on the first hard disk will be defined as '''(hd0,1)'''.}}<br />
<br />
If you are unaware of the the location of {{Filename|/boot}}, use the GRUB shell {{Codeline|find}} command to locate the GRUB files. Enter the GRUB shell as root by:<br />
<br />
# grub<br />
<br />
The following example is for systems ''without'' a separate {{Filename|/boot}} partition, wherein {{Filename|/boot}} is merely a directory under {{Filename|/}}:<br />
<br />
grub> find /boot/grub/stage1<br />
<br />
The following example is for systems ''with'' a separate {{Filename|/boot}} partition:<br />
<br />
grub> find /grub/stage1<br />
<br />
GRUB will find the file, and output the location of the stage1 file. For example:<br />
<br />
(hd1,0)<br />
<br />
This value should be entered on the {{Codeline|root}} line in your configuration file. Type {{Codeline|quit}} to exit the shell.<br />
<br />
=== Dual booting with Windows ===<br />
<br />
Add the following to the end of your {{Filename|/boot/grub/menu.lst}} (assuming that your Windows partition is on the first partition of the first drive):<br />
<br />
title Windows<br />
rootnoverify (hd0,0)<br />
makeactive #if you use Windows7 this line should be commented out<br />
chainloader +1<br />
<br />
{{Note|Windows 2000 and later versions do NOT need to be on the first partition to boot (contrary to popular belief). If the Windows partition changes (i.e. if you add a partition before the Windows partition), you will need to edit the Windows {{Filename|boot.ini}} file to reflect the change (see [http://vlaurie.com/computers2/Articles/bootini.htm this article] for details on how to do that).}}<br />
<br />
If Windows is located on another hard disk, the map command must be used. This will make your Windows install think it is actually on the first drive. Assuming that your Windows partition is on the first partition of the second drive:<br />
<br />
title Windows<br />
map (hd0) (hd1)<br />
map (hd1) (hd0)<br />
rootnoverify (hd1,0)<br />
makeactive #if you use Windows7 this line should be commented out<br />
chainloader +1<br />
<br />
=== Dual booting with GNU/Linux ===<br />
<br />
This can be done the same way that an Arch Linux install is defined. For example:<br />
<br />
title Other Linux<br />
root (hd0,2)<br />
kernel /path/to/kernel root=/dev/sda3 ro<br />
initrd /path/to/initrd<br />
<br />
However, there may be other options that are required, and an initial RAM disk may not be used. Examine the other distribution's {{Filename|/boot/grub/menu.lst}} to match boot options, or see [[#chainloader and configfile]] (recommended).<br />
<br />
=== {{Codeline|chainloader}} and {{Codeline|configfile}} ===<br />
<br />
To facilitate system maintenance, the {{Codeline|chainloader}} or {{Codeline|configfile}} command should be used to boot another Linux distribution that provides an "automagic" GRUB configuration mechanism (e.g. Debian, Ubuntu, openSUSE). This allows the distribution to manage its own {{Filename|menu.lst}} and boot options.<br />
<br />
* The {{Codeline|chainloader}} command will load another bootloader (rather than a kernel image); useful if another bootloader is installed in a partition's boot sector (GRUB, for example). This allows one to install a "main" instance of GRUB to the [[MBR]] and distribution-specific instances of GRUB to each partition boot record (PBR).<br />
<br />
* The {{Codeline|configfile}} command will instruct the currently running GRUB instance to load the specified configuration file. This can be used to load another distribution's {{Filename|menu.lst}} without a separate GRUB installation. The caveat of this approach is that other {{Filename|menu.lst}} may not be compatible with the installed version of GRUB; some distributions heavily patch their versions of GRUB.<br />
<br />
For example, GRUB is to be installed to the [[MBR]] and some other bootloader (be it GRUB or [[LILO]]) is already installed to the boot sector of {{Codeline|(hd0,2)}}.<br />
<br />
---------------------------------------------<br />
| | | | % |<br />
| M | | | B % |<br />
| B | (hd0,0) | (hd0,1) | L % (hd0,2) |<br />
| R | | | % |<br />
| | | | % |<br />
---------------------------------------------<br />
| ^<br />
| chainloading |<br />
-----------------------------<br />
<br />
One can simply include in {{Filename|menu.lst}}:<br />
<br />
title Other Linux<br />
root (hd0,2)<br />
chainloader +1<br />
<br />
Or, if the bootloader on {{Codeline|(hd0,2)}} is GRUB:<br />
<br />
title Other Linux<br />
root (hd0,2)<br />
configfile /boot/grub/menu.lst<br />
<br />
The {{Codeline|chainloader}} command can also be used to load the MBR of a second drive:<br />
<br />
title Other drive<br />
rootnoverify (hd1)<br />
chainloader +1<br />
<br />
=== Dual booting with GNU/Linux (Grub2) ===<br />
<br />
If the other Linux distribution uses Grub2 (e.g. Ubuntu 9.10+), and you installed its boot loader to its root partition, you can add an entry like this one to your {{Filename|/boot/grub/menu.lst}}:<br />
<br />
# other Linux using Grub2<br />
title Ubuntu<br />
root (hd0,2)<br />
kernel /boot/grub/core.img<br />
<br />
Selecting this entry at boot will load the other distribution's Grub2 menu.<br />
<br />
== Bootloader installation ==<br />
<br />
=== Manual recovery of GRUB libs ===<br />
<br />
The {{Filename|*stage*}} files are expected to be in {{Filename|/boot/grub}}, which may not be the case if the bootloader was not installed during system installation or if the partition/filesystem was damaged, accidentally deleted, etc. <br />
<br />
Manually copy the grub libs like so:<br />
# cp -a /usr/lib/grub/i386-pc/* /boot/grub<br />
<br />
{{Note|Don't forget to mount the system's boot partition if your setup uses a separate one! The above assumes that either the boot partition resides on the root filesystem or is mounted to /boot on the root file system!}}<br />
<br />
=== General notes about bootloader installation === <br />
GRUB may be installed from a separate medium (e.g. a LiveCD), or directly from a running Arch install. The GRUB bootloader is ''seldom'' required to be reinstalled and installation is ''not'' necessary when:<br />
<br />
* The configuration file is updated.<br />
* The GRUB package is updated.<br />
<br />
Installation is ''necessary'' when:<br />
<br />
* A bootloader is not already installed.<br />
* Another operating system overwrites the a Linux bootloader.<br />
* The bootloader fails for some unknown reason.<br />
<br />
Before continuing, a few notes:<br />
<br />
* Be sure that your GRUB configuration is correct ({{Filename|/boot/grub/menu.lst}}) before proceeding. Refer to [[#Finding GRUB's root]] to ensure your devices are defined correctly.<br />
* GRUB must be installed on the [[MBR]] (first sector of the hard disk), or the first partition of the first storage device to be recognized by most BIOS's. To allow individual distributions the ability to manage their own GRUB menus, multiple instances of GRUB can be used, see [[#chainloader and configfile]].<br />
* Installing the GRUB bootloader may need to be done from within a {{Codeline|chroot}}ed environment (i.e. from installed environment via a separate medium) for cases like RAID configurations or if you forgot/broke your GRUB installation. You will need to [[Change Root]] from a LiveCD or another Linux installation to do so.<br />
<br />
First, enter the GRUB shell:<br />
<br />
# grub<br />
<br />
Use the {{Codeline|root}} command with the output from the {{Codeline|find}} command (see [[#Finding GRUB's root]]) to instruct GRUB which partition contains stage1 (and therefore, {{Filename|/boot}}):<br />
<br />
grub> root (hd1,0)<br />
<br />
{{Tip|The GRUB shell also supports tab-completion. If you type 'root (hd' then press '''Tab''' twice you will see the available storage devices, this can also be done for partitions. Tab-completion also works from the GRUB boot menu. If there is an error in your configuration file you can edit in the boot menu and use tab-completion to help find devices and partitions. See [[#Edit GRUB entries in the boot menu]].}}<br />
<br />
=== Installing to the MBR ===<br />
<br />
The following example installs GRUB to the [[MBR]] of the first drive:<br />
<br />
grub> setup (hd0)<br />
<br />
=== Installing to a partition ===<br />
<br />
The following example installs GRUB to the first partition of the first drive:<br />
<br />
grub> setup (hd0,0)<br />
<br />
After running {{Codeline|setup}}, enter {{Codeline|quit}} to exit the shell. If you chrooted, [[Change Root|exit your chroot and unmount partitions]]. Now reboot to test.<br />
<br />
=== Alternate method (grub-install) ===<br />
<br />
{{Tip|This procedure is known to be less reliable, the recommended method is to use the GRUB shell.}}<br />
<br />
Use the {{Codeline|grub-install}} command followed by the location to install the bootloader. For example to install the GRUB bootloader to the MBR of the first drive:<br />
<br />
# grub-install /dev/sda<br />
<br />
GRUB will indicate whether it successfully installs. If it does not, you will have to use the GRUB shell method.<br />
<br />
== Tips and tricks ==<br />
<br />
Additional configuration notes.<br />
<br />
=== Graphical boot ===<br />
<br />
For those desiring eye candy, see [[grub-gfx]]. [[GRUB2]] also offers enhanced graphical capabilities, such as background images and bitmap fonts.<br />
<br />
=== Framebuffer resolution ===<br />
<br />
One can use the resolution given in the {{Filename|menu.lst}}, but you might want to use your LCD wide-screen at its full native resolution. Here is what you can do to achieve this:<br />
<br />
On [[Wikipedia:VESA BIOS Extensions#Linux video mode numbers|Wikipedia]], there is a list of extended framebuffer resolutions (i.e. beyond the ones in the VBE standard). But, for example, the one I want to use for 1440x900 ({{Codeline|1=vga=867}}) does not work. This is because the graphic card manufacturers are free to choose any number they wish, as this is not part of the VBE 3 standard. This is why these codes change from one card to the other (possibly even for the same manufacturer).<br />
<br />
So instead of using that table, you can use one of the tools mentioned below to get the correct code:<br />
<br />
==== vbetest ====<br />
<br />
# Install {{Package Official|lrmi}} package from '''[community]''' that contains the '''vbetest''' tool (x86_64 users will need to use [[#hwinfo]] below).<br />
# Run {{Codeline|vbetest}} as root <br />
# Then note the number in [ ] corresponding to your desired resolution.<br />
# Press 'q' to quit '''vbetest''' interactive prompt. <br />
## As an option, in a console as root, you can test the mode you just picked up by running {{Codeline|vbetest -m <yourcode>}} and see a pattern like [http://www.phoronix.net/image.php?id=803&image=x_vbespy_5 this one]<br />
# Add '''512''' to the discovered value picked up above and use the total value to define the {{Codeline|1=vga=}} parameter in the kernel options of {{Filename|menu.lst}}.<br />
# Reboot to enjoy the result<br />
<br />
For example '''vbetest''' on one computer:<br />
<br />
[356] 1440x900 (256 color palette)<br />
[357] 1440x900 (8:8:8)<br />
<br />
So here the number you want is 357. Then, 357 + 512 = 869, so you will use '''vga=869'''. Add your value to the end of the kernel line in {{Filename|menu.lst}} as shown below:<br />
<br />
kernel /vmlinuz26 root=/dev/sda1 ro '''vga=869'''<br />
<br />
{{Note|<br />
* (8:8:8) is for 24-bit color (24bit is 32bit)<br />
* (5:6:5) is for 16-bit color<br />
* (5:5:5) is for 15-bit color<br />
}}<br />
<br />
==== hwinfo ====<br />
<br />
# Install {{Package AUR|hwinfo}} from [AUR].<br />
# Run {{Codeline|hwinfo --framebuffer}} as root.<br />
# Pick up the code corresponding to the desired resolution.<br />
# Use the 6 digit code with 0x prefix in {{Codeline|1=vga=}} kernel option in {{Filename|menu.lst}}. Or convert it to decimal to avoid the use of 0x prefix.<br />
<br />
Example output of '''hwinfo''':<br />
<br />
Mode 0x0364: 1440x900 (+1440), 8 bits<br />
Mode 0x0365: 1440x900 (+5760), 24 bits<br />
<br />
And the kernel line:<br />
<br />
kernel /vmlinuz26 root=/dev/sda1 ro '''vga=0x0365'''<br />
<br />
{{Note|''vbetest'' gives you VESA mode to which we need to add 512 to get the correct value to use in kernel option line. While ''hwinfo'' gives you directly the correct value needed by the kernel.}}<br />
<br />
==== GRUB recognized value ====<br />
<br />
This is an easy way to find the resolution code using only GRUB itself.<br />
<br />
On the kernel line, specify that the kernel should ask you which mode to use.<br />
<br />
kernel /vmlinuz26 root=/dev/sda1 ro '''vga=ask'''<br />
<br />
Now reboot. GRUB will now present a list of suitable codes to use and the option to scan for even more.<br />
<br />
You can pick the code you would like to use (don't forget it, it is needed for the next step) and boot using it.<br />
<br />
The number you have picked here is the '''hexadecimal''' number, in order to use it at the kernel line you can transform it into a '''decimal''' number.<br />
<br />
Now replace '''ask''' in the kernel line with the correct one you have picked.<br />
<br />
e.g. the kernel line for '''[369] 1680x1050x32''' would be:<br />
<br />
kernel /vmlinuz26 root=/dev/sda1 ro '''vga=873'''<br />
<br />
=== Naming by label ===<br />
<br />
If you alter (or plan to alter) partition sizes from time to time, you might want to consider defining your drive/partitions by a label. You can label ext2, ext3, ext4 partitions by:<br />
<br />
e2label </dev/drive|partition> label<br />
<br />
The label name can be up to 16 characters long but cannot have spaces for GRUB to understand it. Then define it in your {{Filename|menu.lst}}:<br />
<br />
kernel /boot/vmlinuz26 root=/dev/disk/by-label/Arch_Linux ro<br />
<br />
=== Password protection ===<br />
<br />
You can enable password protection in the GRUB configuration file for operating systems you wish to have protected. Bootloader password protection may be desired if your BIOS lacks such functionality and you need the extra security.<br />
<br />
First, choose a password you can remember and then encrypt it:<br />
<br />
# grub-md5-crypt<br />
Password:<br />
Retype password:<br />
$1$ZOGor$GABXUQ/hnzns/d5JYqqjw<br />
<br />
Then add your password to the beginning of the GRUB configuration file (the password must be at the beginning of the configuration file for GRUB to be able to recognize it):<br />
<br />
<pre><br />
# general configuration<br />
timeout 5<br />
default 0<br />
color light-blue/black light-cyan/blue<br />
<br />
password --md5 $1$ZOGor$GABXUQ/hnzns/d5JYqqjw<br />
</pre><br />
<br />
Then for each operating system you wish to protect, add the {{Codeline|lock}} command:<br />
<br />
<pre><br />
# (0) Arch Linux<br />
title Arch Linux<br />
lock<br />
root (hd0,1)<br />
kernel /boot/vmlinuz26 root=/dev/disk/by-label/Arch_Linux ro<br />
initrd /boot/kernel26.img<br />
</pre><br />
<br />
{{Warning|If you disable booting from other boot devices (like a CD drive) in the BIOS's settings and then password protect all your operating system entries, it could be difficult to re-enable booting back into the operating systems if the password is forgotten.}}<br />
<br />
=== Restart with named boot choice ===<br />
<br />
If you realize that you often need to switch to some other non-default OS (e.g. Windows) having to reboot and wait for the GRUB menu to appear is tedious. GRUB offers a way to record your OS choice when restarting instead of waiting for the menu, by designating a temporary new default which will be reset as soon as it has been used.<br />
<br />
Supposing a simple {{Filename|menu.lst}} setup like this:<br />
<br />
{{File<br />
|name=/boot/grub/menu.lst<br />
|content=<nowiki><br />
# general configuration:<br />
timeout 10<br />
default 0<br />
color light-blue/black light-cyan/blue<br />
<br />
# (0) Arch<br />
title Arch Linux<br />
root (hd0,1)<br />
kernel /boot/vmlinuz26 root=/dev/disk/by-label/ARCH ro<br />
initrd /boot/kernel26.img<br />
<br />
# (1) Windows<br />
title Windows XP<br />
rootnoverify (hd0,0)<br />
makeactive<br />
chainloader +1<br />
</nowiki>}}<br />
<br />
Arch is the default (0). We want to restart in to Windows. Change {{Codeline|default 0}} to {{Codeline|default saved}} -- this will record the current default in a {{Filename|default}} file in the GRUB directory whenever the '''savedefault''' command is used. Now add the line {{Codeline|savedefault 0}} to the bottom of the Windows entry. Whenever Windows is booted, it will reset the default to Arch, thus making changing the default to Windows temporary. <br />
<br />
Now all that is needed is a way to easily change the default manually. This can be accomplished using the command {{Codeline|grub-set-default}}. So, to reboot into Windows, enter the following command:<br />
<br />
sudo grub-set-default 1 && sudo shutdown -r now<br />
<br />
For ease of use, you might to wish to implement the "[[Allow users to shutdown]] fix" (including {{Filename|/sbin/grub-set-default}} amongst the commands the user is allowed to issue without supplying a password).<br />
<br />
=== LILO and GRUB interaction ===<br />
<br />
If the [[LILO]] package is installed on your system, remove it with<br />
<br />
pacman -R lilo<br />
<br />
as some tasks (e.g. kernel compilation using {{Codeline|make all}}) will make a LILO call, and LILO will then be installed over GRUB. LILO may have been included in your base system, depending on your installer media version and whether you selected/deselected it during the package selection stage.<br />
<br />
{{Note|pacman -R lilo will not remove LILO from the MBR if it has been installed there; it will merely remove the lilo package. The LILO bootloader installed to the MBR will be overwritten when GRUB (or another bootloader) is installed over it.}}<br />
<br />
=== GRUB boot disk ===<br />
<br />
First, format a floppy disk:<br />
<br />
fdformat /dev/fd0<br />
mke2fs /dev/fd0<br />
<br />
Now mount the disk:<br />
<br />
mount -t ext2 /dev/fd0 /mnt/fl<br />
<br />
Install GRUB to the disk:<br />
<br />
grub-install --root-directory=/mnt/fl '(fd0)'<br />
<br />
Copy your {{Filename|menu.lst}} file to the disk:<br />
<br />
cp /boot/grub/menu.lst /mnt/fl/boot/grub/menu.lst<br />
<br />
Now unmount your floppy:<br />
<br />
umount /mnt/fl<br />
<br />
Now you should be able to restart your computer with the disk in the drive and it should boot to GRUB. Make sure that your floppy disk is set to have higher priority than your hard drive when booting in your BIOS first, of course.<br />
<br />
See also: [http://www.supergrubdisk.org/ Super GRUB Disk]<br />
<br />
== Troubleshooting ==<br />
<br />
=== GRUB Error 17 ===<br />
<br />
If your partition table gets messed up, an unpleasant "GRUB error 17" message might be the only thing that greets you on your next reboot. There are a number of reasons why the partition table could get messed up. Commonly, users who manipulate their partitions with [[GParted]] -- particularly logical drives -- can cause the order of the partitions to change. For example, you delete {{Filename|/dev/sda6}} and resize {{Filename|/dev/sda7}}, then finally re-create what used to be {{Filename|/dev/sda6}} only now it appears at the bottom of the list, {{Filename|/dev/sda9}} for example. Although the physical order of the partitions/logical drives has not changed, the order in which they are recognized has changed.<br />
<br />
Fixing the partition table is easy. Boot from your Arch CD/DVD/USB, login as root and fix the partition table:<br />
<br />
# fdisk /dev/sda<br />
<br />
Once in disk, enter e[x]tra/expert mode, [f]ix the partition order, then [w]rite the table and exit.<br />
<br />
You can verify that the partition table was indeed fixed by issuing an {{Codeline|fdisk -l}}. Now you just need to fix GRUB. See the [[#Bootloader installation]] section above.<br />
<br />
Basically you need to tell GRUB the correct location of your {{Filename|/boot}} then re-write grub to the [[MBR]] on the disk.<br />
<br />
For example:<br />
<br />
# grub<br />
<br />
grub> root (hd0,6)<br />
grub> setup (hd0)<br />
grub> quit<br />
<br />
See [[http://stringofthoughts.wordpress.com/2009/05/24/grub-error-17-debianubuntu this page]] for a more in-depth summary of this section.<br />
<br />
=== /boot/grub/stage1 not read correctly ===<br />
If you see this error message while trying to setup grub and you are not using a fresh partition table, it's worth checking it.<br />
<br />
# fdisk -l /dev/sda<br />
<br />
This will show you the partition table for /dev/sda. So check here, whether the "Id" values of your partitions are correct. <br />
The "System" column will show you the description of the "Id" values.<br />
<br />
If your boot partition is marked as being "HPFS/NTFS", for example, then you have to change it to "Linux". To do this, go to fdisk,<br />
<br />
# fdisk /dev/sda<br />
<br />
change a partition's system id with [t], select you partition number and type in the new system id (Linux = 83). <br />
You can also list all available system ids by typing "L" instead of a system id.<br />
<br />
If you have changed a partitions system id, you should [v]erify your partition table and then [w]rite it.<br />
<br />
Now try to setup grub again.<br />
<br />
[[http://bbs.archlinux.org/viewtopic.php?pid=799930 Here]] is the forum post reporting this problem.<br />
<br />
=== Accidental install to a Windows partition ===<br />
<br />
If you accidentally install GRUB to a Windows partition, GRUB will write some information to the boot sector of the partition, erasing the reference to the Windows bootloader. (This is true for NTLDR the bootloader for Windows XP and earlier, unsure about later versions).<br />
<br />
To fix this you'll need to use the Windows Recovery Console for your Windows release. Because many computer manufacturers do not include this with their product (many choose to use a recovery partition) Microsoft has made them available for download. If you use XP, look at [http://tips.vlaurie.com/2006/05/recovery-console-for-those-without-an-xp-disk/ this page] to be able to turn the floppy disks to a Recovery CD. Boot the Recovery CD (or enable Windows Recovery mode) and run {{Codeline|fixboot}} to repair the partition boot sector. After this, you will have to install GRUB again---this time, to the MBR, not to the Windows partition---to boot Linux.<br />
<br />
See [[MBR#Restoring a Windows boot record|further discussion here]].<br />
<br />
=== Edit GRUB entries in the boot menu ===<br />
<br />
Once you have selected and entry in the boot menu, you can edit it by pressing key '''e'''. Use tab-completion if you need to to discover devices then '''Esc''' to exit. Then you can try to boot by pressing '''b'''. Note: these settings '''will not be saved'''.<br />
<br />
=== device.map error ===<br />
<br />
If an error is raised mentioning {{Filename|/boot/grub/device.map}} during installation or boot, run:<br />
<br />
# grub-install --recheck /dev/sda<br />
<br />
to force GRUB to recheck the device map, even if it already exists. This may be necessary after resizing partitions or adding/removing drives.<br />
<br />
=== KDE reboot pull-down menu fails ===<br />
<br />
If you've opened a sub-menu with the list of all operating systems configured in GRUB, selected one, and upon restart, you still booted your default OS, then you might want to check if you have the line:<br />
<br />
default saved<br />
<br />
in {{Filename|/boot/grub/menu.lst}}.<br />
<br />
=== GRUB fails to find or install to any virtio ''/dev/vd*'' or other non-BIOS devices ===<br />
I had trouble installing GRUB while installing ArchLinux in an virtual KVM machine using a virtio device for hard drive. To install GRUB, I figured out the following:<br />
Enter a virtual console by typing ctrl+alt+f2 or any other f-key for a free virtual console.<br />
Assuming your root file system is mounted in the folder /mnt and boot file system is either mounted or stored in the folder /mnt/boot<br />
<br />
1. Assure that all needed GRUB files is present in your boot directory(assuming mounted in /mnt/boot folder), by issuing the command:<br />
<br />
# ls /mnt/boot/grub<br />
<br />
2. If the grub folder allready contains all the needed files, jump to step 3. Otherwise, do the following commands(replacing /mnt, your_kernel and your_initrd with the real paths and file names). You should also have the menu.lst file written to this folder:<br />
<br />
# mkdir -p /mnt/boot/grub # if the folder is not yet present<br />
# cp -r /boot/grub/stage1 /boot/grub/stage2 /mnt/boot/grub<br />
# cp -r your_kernel your_initrd /mnt/boot<br />
<br />
3. Start the GRUB shell with the following command:<br />
<br />
# grub --device-map=/dev/null<br />
<br />
4. Enter the following commands, replace /dev/vda, (hd0,0) with the correct device and partition corresponding to your setup.<br />
<br />
device (hd0) /dev/vda<br />
root (hd0,0)<br />
setup (hd0)<br />
quit<br />
<br />
5. If GRUB reports no error messages you probably are done.<br />
<br />
== External resources ==<br />
* [http://www.gnu.org/software/grub/ GNU GRUB]<br />
* [http://www.troubleshooters.com/linux/grub/index.htm GRUB Grotto]<br />
* [http://www.mjmwired.net/kernel/Documentation/kernel-parameters.txt Linux Kernel Documentation :: kernel-parameters.txt]<br />
* [http://www.kernel.org/pub/linux/kernel/people/gregkh/lkn/lkn_pdf/ch09.pdf List of kernel paramaters with further explanation and grouped by similar options]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Chromium&diff=120054
Chromium
2010-10-26T18:17:34Z
<p>Cantabile: /* Displaying various non-latin scripts */</p>
<hr />
<div>[[Category:Internet and Email (English)]]<br />
Chromium is an open source graphical web browser from Google, based on the [[Wikipedia: WebKit|WebKit]] rendering engine.<br />
<br />
== Installation ==<br />
The stable version of chromium can be installed from the official repository by:<br />
# pacman -S chromium<br />
<br />
There are also beta and dev versions, which can be found in [[Arch User Repository]] under the name of [http://aur.archlinux.org/packages.php?ID=40059 chromium-beta] and [http://aur.archlinux.org/packages.php?ID=37244 chromium-dev].<br />
{{Note|Compiling chromium-beta or chromium-dev takes at least as long as compiling the linux kernel.}}<br />
<br />
There are also some packages in the AUR which provide the binary version of Google Chrome.<br />
<br />
See [http://news.softpedia.com/news/Google-Chrome-vs-Chromium-Understanding-Stable-Beta-Dev-Releases-and-Version-No-140060.shtml this article] for an explanation of the differences between the three flavours, Chromium vs. Chrome, and the version numbers.<br />
<br />
== Configuration ==<br />
=== Displaying various non-latin scripts ===<br />
To correctly display Chinese, Japanese, Korean... etc characters, see [[Fonts#Font_packages|here]] for detailed instructions to install various TrueType fonts.<br />
<br />
=== Using chromium with no desktop environment ===<br />
<br />
Unlike [[Firefox]], chromium does not maintain its own database of mimetype-to-application associations. Instead, it relies on {{Filename|xdg-open}} (part of extra/xdg-utils) to open files and, for example, [[Wikipedia: Magnet_URI_scheme|magnet links]].<br />
<br />
Inside a [[Desktop Environment|desktop environment]] (e.g. [[GNOME|Gnome]], or [[KDE|Kde]], or [[Xfce]]), {{Filename|xdg-open}} simply passes the arguments to that desktop environment's file-opener application ({{Filename|gnome-open}}, {{Filename|kde-open}}, or {{Filename|exo-open}}, respectively), which means that the associations are left up to the desktop environment.<br />
<br />
However, when no desktop environment is detected (for example when one runs a standalone [[Window Manager|window manager]], e.g. [[Openbox]]), {{Filename|xdg-open}}'s behaviour becomes rather strange and annoying: many filetypes opened in firefox or chromium itself, no support for magnet links, etc.<br />
<br />
There are a number of possible solutions to this problem, outlined below.<br />
<br />
* Improve xdg-open, make it smarter (aka "patches welcome" :P )<br />
* Use part of a desktop environment, specifically, the part which includes the file opener; for gnome, that would be 'libgnome' (and its dependencies), for xfce, 'exo'. The $DE environment variable needs to be exported before starting the window manager. For example:<br />
<blockquote>{{File|name=~/.xinitrc|content=<br />
export DE=gnome<br />
exec ck-launch-session openbox<br />
}}</blockquote><br />
* Use [http://aur.archlinux.org/packages.php?ID=32911 mimeo] (written by an arch (trusted) user) and [http://aur.archlinux.org/packages.php?ID=32912 xdg-utils-mimeo], which replaces extra/xdg-utils and contains a {{Filename|xdg-open}} script patched to make use of {{Filename|mimeo}} the same way {{Filename|gnome-open}} would be used. Mimetype<->application associations can then be customised easily in {{Filename|/etc/mime.types}} or {{Filename|~/.mime.types}}<br />
<br />
* When using openbox and no Desktop Environment (=DE) like KDE, GNOME or XFCE do following:<br />
<blockquote>{{File|name=~/.config/openbox/autostart.sh|content=<br />
export BROWSER=chromium<br />
}}</blockquote><br />
Attention: Do not export any DE environment variable !<br />
Then issue the command:<br />
> xdg-mime default xpdf.desktop application/pdf<br />
This should create an entry in your local mime database:<br />
<blockquote>{{File|name=~/.local/share/applications/defaults.list|content=<br />
[Default Applications]<br />
text/html=chromium.desktop<br />
application/pdf=xpdf.desktop<br />
}}</blockquote><br />
Restart chromium and your pdf files should be opened with xpdf now.<br />
For me it only worked as normal user - as root I had problems cause no directories for the local mime times were created.<br />
See also this thread [https://bbs.archlinux.org/viewtopic.php?id=93956].<br />
<br />
=== Font Rendering ===<br />
Chromium is now supposed to use the settings in {{Filename|~/.fonts.conf}}, though you may have to edit it manually (see [[Font_Configuration#Basic_settings|Font Configuration]]). If the fonts are still rendered badly you can use xft settings [[Xdefaults|as suggested here]]. Just create {{Filename|~/.Xdefaults}} if it doesn't exist and add in:<br />
<pre><br />
! Xft settings ---------------------------------------------------------------<br />
<br />
Xft.dpi: 96<br />
Xft.antialias: true<br />
Xft.rgba: rgb<br />
Xft.hinting: true<br />
Xft.hintstyle: hintslight<br />
</pre><br />
<br />
{{Note|these settings will affect any application that reads {{Filename|~/.Xdefaults}}, not just chromium; one example is [[Rxvt-unicode|rxvt-unicode]].}}<br />
<br />
=== Default browser ===<br />
The simpliest way to make chromium the default browser is to set variable $BROWSER=chromium in ~/.bashrc (depends on your shell, e.g. ~/.zshrc for zsh)<br />
if [ -n "$DISPLAY" ]; then<br />
BROWSER=chromium<br />
fi<br />
<br />
The other way is to edit the ''xdg-open'' script.<br />
$ sudo $YOUR_EDITOR /usr/bin/xdg-open<br />
At almost the bottom on the file, is a long horizontal list of browsers:<br />
if [ x"$DE" = x"" ]; then<br />
# if BROWSER variable is not set, check some well known browsers instead<br />
if [ x"$BROWSER" = x"" ]; then<br />
BROWSER=links2:links:lynx:w3m<br />
if [ -n "$DISPLAY" ]; then<br />
BROWSER=firefox:mozilla:epiphany:konqueror:chromium-browser:google-chrome:$BROWSER<br />
fi<br />
fi<br />
DE=generic<br />
fi<br />
Add '''chromium:''' ''(mind the colon which separates the entries)'' before '''firefox:mozilla:''' ... and save. To test if this were conducted successfully, type this into your terminal:<br />
<pre>$ xdg-open http://google.com</pre><br />
If everything went perfect, either a new tab inside Chromium, or a new window would open and display the Google homepage, depending on your settings.<br />
<br />
Another option, when using '''mimeo''', is to associate "http://" links with chromium:<br />
{{File|name=~/.mime.types|content=<nowiki><br />
/usr/bin/chromium<br />
^http://<br />
</nowiki>}}<br />
<br />
=== Flash Player ===<br />
<br />
If running i686 Arch Linux, all one needs to do is to install the flash plugin and restart chromium:<br />
# pacman -S flashplugin<br />
<br />
For x86_64, one [http://www.archlinux.org/news/508/ needs to enable] the new [multilib] repository.<br />
# pacman -S flashplugin<br />
<br />
=== Open PDF files inside Chromium ===<br />
<br />
There are two ways to do this: The first one by using Google Chrome's own PDF rendering plugin, the second by allowing Chromium access to e. g. Adobe Reader via the mozplugger plugin.<br />
<br />
==== libpdf.so ====<br />
<br />
libpdf is Google's own implementation of a PDF renderer. While compatible, it is currently only part of Chrome releases, not Chromium ones. The easiest way to add it to the latter is:<br />
<br />
Download a Google Chrome release that corresponds to the version of Chromium you use.<br />
<br />
$ wget http://dl.google.com/linux/direct/google-chrome-unstable_current_i386.deb<br />
<br />
$ wget http://dl.google.com/linux/direct/google-chrome-unstable_current_amd64.deb<br />
<br />
Extract and fetch {{Filename|libpdf.so}} from {{Filename|/opt/google/chrome/}} in {{Filename|data.tar.lzma}}.<br />
<br />
Move the file to {{Filename|/opt/chromium-browser}}. A change of its file permissions may be necessary.<br />
<br />
Start Chromium and open about:plugins. "Chrome PDF Viewer" should now view; it may need to be enabled.<br />
<br />
==== mozplugger ====<br />
<br />
To use mozplugger, a small edit to its sources is required: Grab its [http://aur.archlinux.org/packages.php?ID=9458 PKGBUILD] from AUR and download the sources with: <br />
<br />
$ makepkg -o<br />
<br />
Next open up {{Filename|mozplugger.c}} and search for "NPPVpluginNeedsXEmbed". Change the line directly below from:<br />
<br />
$ *((NPBool *)value) = …;<br />
<br />
to:<br />
<br />
$ *((NPBool *)value) = 1;"<br />
<br />
After the change execute:<br />
<br />
$ makepkg -ei<br />
<br />
to build and install without overwriting the source.<br />
<br />
=== Certificates ===<br />
<br />
Chromium uses [[Nss | NSS]] for the certificate management. Actually there is no graphical user interface for NSS therefore you can use the CLI.<br />
<br />
== Tips and tricks ==<br />
=== Profile in tmpfs ===<br />
The default Chromium profile is typically located in {{filename|$HOME/.config/chromium}}. This profile can be relocated to an available [http://en.wikipedia.org/wiki/Tmpfs tmpfs] filesystem, including <tt>/tmp</tt>, or <tt>/dev/shm</tt> for improvements in application response as the the entire profile is now stored in RAM. Another benefit is a reduction in disk read and write operations, of which SSD drives benefit the most.<br />
<br />
* At system startup, call [http://en.wikipedia.org/wiki/Rsync rsync] to recursively copy the folder {{filename|/home/USER/.config/chromium}} to {{filename|/dev/shm/.chromium}}:<br />
#!/bin/bash<br />
#<br />
# /etc/rc.local<br />
#<br />
rsync -a /home/USER/.config/chromium /dev/shm/.chromium<br />
<br />
* At system shutdown, call [http://en.wikipedia.org/wiki/Rsync rsync] to recursively copy the folder {{filename|/dev/shm/.chromium}} to {{filename|/home/USER/.config/chromium}}:<br />
#!/bin/bash<br />
#<br />
# /etc/rc.local.shutdown<br />
#<br />
rsync -a --delete /dev/shm/.chromium home/USER/.config/chromium<br />
<br />
* To copy only bookmarks and the preferences file back to the disk profile:<br />
<br />
#!/bin/bash<br />
#<br />
# /etc/rc.local.shutdown<br />
#<br />
rsync -a /dev/shm/.chromium/Default/Bookmarks home/USER/.config/chromium/Bookmarks &<br />
rsync -a /dev/shm/.chromium/Default/Preferences home/USER/.config/chromium/Preferences<br />
<br />
* Specify the user data directory where the browser will look for all of its state:<br />
<br />
$ chromium --user-data-dir=/dev/shm/.chromium<br />
<br />
* Any number of command-line options may be included in the string:<br />
<br />
$ chromium --block-nonsandboxed-plugins --incognito --disable-java --safe-plugins --start-maximized --user-data-dir=/dev/shm/.chromium<br />
<br />
== Troubleshooting ==<br />
=== Default profile ===<br />
If you cannot get your default profile when you try to run chromium:<br />
<pre><br />
$ chromium<br />
[2630:2630:485325611:FATAL:chrome/browser/browser_main.cc(755)] Check failed: profile. <br />
Cannot get default profile. Trace/breakpoint trap<br />
</pre><br />
<br />
Just correct the owner of the directory {{Filename|~/.config/chromium}}, and it will work.<br />
<pre><br />
$ chown -R yourusername: ~/.config/chromium<br />
</pre><br />
<br />
== Resources ==<br />
* [http://www.chromium.org/Home Chromium homepage]<br />
* [[Wikipedia: Chromium_(web_browser)#Differences_between_Chromium_and_Google_Chrome|Differences between Chromium and Google Chrome]]<br />
* [http://googlechromereleases.blogspot.com/ Announcements and release notes for the Google Chrome browser]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Syslinux&diff=119310
Syslinux
2010-10-16T05:59:17Z
<p>Cantabile: Added to category "Boot Process (English)"</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
Syslinux is a collection of boot loaders capable of booting from hard drives, CDs and over the network via PXE. It supports the fat, ext2, ext3, ext4 and btrfs file systems.<br />
<br />
= Using syslinux to boot your Arch Linux system =<br />
<br />
== Installing syslinux ==<br />
<br />
Make sure you have the ''syslinux'' package installed. Then install syslinux onto your boot partition, which must contain a ext2, ext3, ext4 or btrfs file system.<br />
# mkdir /boot/syslinux<br />
# extlinux --install /boot/syslinux<br />
/boot/syslinux/ is device /dev/sda1<br />
Next, you need mark your boot partition active in your partition table:<br />
# fdisk -l /dev/sda<br />
[...]<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 * 2048 104447 51200 83 Linux<br />
/dev/sda2 104448 625142447 312519000 83 Linux<br />
Once that is the case, install a master boot record:<br />
# cat /usr/lib/syslinux/mbr.bin > /dev/sda<br />
When you reboot your system now, you will have a syslinux prompt. To automatically boot your system, you still need to create a configuration file.<br />
<br />
== Configuring syslinux ==<br />
<br />
The syslinux configuration file is ''syslinux.cfg'' in the syslinux folder, in our case ''/boot/syslinux/syslinux.cfg''.<br />
<br />
=== Booting Arch Linux ===<br />
<br />
This is a simple configuration file that will show a boot: prompt and automatically boot after 5 seconds.<br />
<br />
PROMPT 1<br />
TIMEOUT 50<br />
DEFAULT arch<br />
<br />
LABEL arch<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
This example assumes that /boot is a separate mount point. If /boot is the same partition as /, you have to replace ''/vmlinuz26'' by ''/boot/vmlinuz26'' and so on.<br />
<br />
If you want to boot directly without seeing a prompt, set PROMPT to 0 above. Instead of LINUX, the keyword KERNEL can also be used. KERNEL tries to detect the file type of the file, while LINUX always expects a Linux kernel.<br />
<br />
=== Boot menu ===<br />
<br />
Syslinux also allows you to use a boot menu. To use it, copy the menu COM32 module to your syslinux folder:<br />
# cp /usr/lib/syslinux/menu.c32 /boot/syslinux/<br />
If /boot is the same partition as /, a symlink will also work<br />
# ln -s /usr/lib/syslinux/menu.c32 /boot/syslinux/<br />
Now, adjust the configuration file:<br />
UI menu.c32<br />
PROMPT 0<br />
<br />
MENU TITLE Boot Menu<br />
TIMEOUT 50<br />
DEFAULT arch<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /vmlinuz26<br />
APPEND root=/dev/sda2 ro<br />
INITRD /kernel26.img<br />
<br />
For more details about the menu system, see [http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=doc/menu.txt].<br />
<br />
=== Chainloading ===<br />
<br />
If you want to chainload other operating systems (such as Windows) or boot loaders, copy (or symlink) the ''chain.c32'' module to the syslinux folder (for details, see the instructions in the previous section). Then, create a section in the configuration file:<br />
<br />
LABEL windows<br />
MENU LABEL Windows<br />
COM32 chain.c32<br />
APPEND hd0 3<br />
<br />
''hd0 3'' is the third partition on the first BIOS drive - drives are counted from zero, but partitions are counted from one. For more details about chainloading, see [http://syslinux.zytor.com/wiki/index.php/Comboot/chain.c32].<br />
<br />
=== Using memtest ===<br />
<br />
Use this LABEL section to launch memtest (install the ''memtest86'' package):<br />
<br />
LABEL memtest<br />
MENU LABEL Memtest86+<br />
LINUX /memtest86+/memtest.bin<br />
<br />
=== HDT ===<br />
<br />
HDT (Hardware Detection Tool) displays hardware information. Like before, the .c32 file has to be copied or symlinked from /boot/syslinux/.<br />
<br />
LABEL hdt<br />
MENU LABEL Hardware Info<br />
COM32 hdt.c32<br />
<br />
=== Reboot and power off ===<br />
<br />
Use the following sections to reboot or power off your machine.<br />
<br />
LABEL reboot<br />
MENU LABEL Reboot<br />
COM32 reboot.c32<br />
<br />
LABEL poweroff<br />
MENU LABEL Power Off<br />
COMBOOT poweroff.com</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Beginners%27_guide_old&diff=119309
Beginners' guide old
2010-10-16T05:53:24Z
<p>Cantabile: /* G: Install Bootloader */ mention Syslinux</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]] [[Category:About Arch (English)]]<br />
[[Category:HOWTOs (English)]] [[Category:Website Resources]]<br />
{{i18n|Beginners' Guide}}<br />
[[de:Anleitung für Einsteiger]]<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|Related}}<br />
{{Article summary wiki|:Category:Accessibility (English)}}<br />
{{Article summary wiki|Official Arch Linux Install Guide}}<br />
{{Article summary wiki|General Recommendations}}<br />
{{Article summary end}}<br />
==Preface==<br />
=====Introduction=====<br />
Welcome. This document will guide you through the process of installing and configuring [[Arch Linux]]; a simple, lightweight GNU/Linux distribution targeted at competent users. 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 />
* [http://www.archlinux.org/packages/?q= All packages] compiled for i686 and x86_64 architectures<br />
* [[Arch Boot Process|BSD style]] init scripts, featuring one centralized configuration file<br />
* [[mkinitcpio]]: A simple and dynamic initramfs creator<br />
* [[Pacman]] package manager is lightweight and agile, with a very modest memory footprint<br />
* The [[Arch Build System]]: A ports-like package building system, providing a simple framework to create installable Arch packages from source<br />
* The [[Arch User Repository]]: offering many thousands of user contributed build scripts and the opportunity to share your own<br />
<br />
=====License=====<br />
<br />
Arch Linux, pacman, documentation, and scripts are copyright<br />
©2002-2007 by Judd Vinet, ©2007-2010 by Aaron Griffin and are licensed under the GNU General Public License Version 2.<br />
<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 as you consider simplicity:'''<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..The height of cultivation always runs to simplicity.&quot;'' - Bruce Lee<br />
<br />
=====About This Guide=====<br />
<br />
The Arch wiki is an excellent resource and should be consulted for issues [[Main Page|first]]. The IRC room (at freenode #archlinux), and the [http://bbs.archlinux.org/ forums] are also available if the answer cannot be found elsewhere.<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 <u>before</u> carrying out the tasks contained.}}<br />
<br />
Since GNU/Linux Distributions are fundamentally 'modular' by design, the guide is logically divided into 4 main components of a desktop <tt>UNIX</tt>-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 installation media from [http://archlinux.org/download/ here]. The latest version is 2010.05 <br />
<br />
* Both the Core and the Netinstall images 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 utilities), the Linux kernel, and a few extra libraries and modules.''<br />
* Core images facilitate both installing from CD and Net. <br />
* Netinstall images are smaller and provide no packages themselves; the entire system is retrieved via internet.<br />
* [[Arch64_FAQ|The Arch64 FAQ]] can help you choose between the 32- and 64-bit versions.<br />
<br />
====Install from an Existing GNU/Linux Distro====<br />
Arch is flexible enough to be installed to another partition ''from within'' an existing distro or Live CD. See [http://wiki.archlinux.org/index.php/Install_from_Existing_Linux this wiki article] for steps to do this. This can be useful particularly if you plan to install Arch via vnc or ssh remotely.<br />
<br />
====CD installer====<br />
Burn the .iso image file to a CD or DVD media with your preferred CD/DVD burner drive and software, and continue with [[#Step 2: Boot Arch Linux Installer | Step 2: Boot Arch Linux Installer]]<br />
{{Note| The quality of optical drives, as well as the CD media itself, vary greatly. 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 />
====Flash Memory Device or USB stick====<br />
<br />
See [[Install_from_a_USB_flash_drive|Install from a USB flash drive]] for more detailed instructions.<br />
<br />
This method will work for any type of flash media from which your BIOS will let you boot, be it a card reader or USB port.<br />
<br />
{{Warning|This procedure will irrevocably destroy all data on your media! Also, be very careful where you send the image iso, as dd will obediently write to any target you point to, even if that is your hard disk.}}<br />
<br />
'''<tt>UNIX</tt> Method:'''<br />
<br />
Insert an empty or expendable flash device, determine its path, and write the .iso to the device with the <code>/bin/dd</code> program:<br />
dd if=archlinux-2010.05-''{core|netinstall}''-''{i686|x86_64|dual}''.iso of=/dev/sd''x''<br />
where <code>if=</code> is the path to the img file and <code>of=</code> is your flash device. Make sure to use {{Filename|/dev/sd'''x'''}} and not {{Filename|/dev/sd'''x1'''}}. You will need a flash memory device large enough to accomodate the image which, at the time of this writing is 381MB.<br />
<br />
'''Check md5sum:'''<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 [ftp://ftp.archlinux.org/iso/2010.05/md5sums.txt 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. A typical run will look like this:<br />
$ [sudo] dd if=archlinux-2010.05-core-i686.iso of=/dev/sdc<br />
744973+0 records in<br />
744973+0 records out<br />
381426176 bytes (381 MB) copied, 106.611 s, 3.6 MB/s<br />
$ [sudo] dd if=/dev/sdc count=744973 status=noxfer | md5sum<br />
4850d533ddd343b80507543536258229 -<br />
744973+0 records in<br />
744973+0 records out<br />
<br />
'''Microsoft Windows Method:'''<br />
<br />
Download Disk Imager from https://launchpad.net/win32-image-writer/+download. Insert flash media. Start the Disk Imager and select the image file. Select the Drive letter associated with the flash drive. Click "write".<br />
<br />
<b>Note:</b><br />
<i>The Windows instructions don't work for .iso images. Disk Imager only works with .img files. I couldn't find any .img files for Arch Linux, but the instructions on [[Install_from_a_USB_flash_drive|Install from a USB flash drive]] worked for me. [[User:Chuzzum|Chuzzum]] 21:53, 11 August 2010 (EDT)</i> <br />
<br />
Continue with [[#Step 2: Boot Arch Linux Installer | Step 2: Boot Arch Linux Installer]]<br />
<br />
===Step 2: Boot Arch Linux Installer===<br />
Insert the CD or Flash media you prepared, 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 (Power On Self-Test) phase.<br />
<br />
{{Tip|The memory requirements for a basic install are:<br />
* Core : 128 MB RAM x86_64/i686 (all packages selected, with swap partition)<br />
* Netinstall : 128 MB RAM x86_64/i686 (all packages selected, with swap partition)}}<br />
<br />
The main menu should be displayed at this point. Select the preferred choice by using the arrow keys to highlight your choice, and then by pressing Enter.<br />
<br />
Usually, the first item, Boot Archlive, is the preferred selection. However, choose Boot Archlive [legacy IDE] if you have trouble with libata/PATA, or have no SATA (Serial ATA) drives.<br />
<br />
To change GRUB boot options, press '''e'''. 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. When done, press '''b''' to boot into that selection.<br />
<br />
The system will now boot and present a login prompt. Login as 'root', without the quotes.<br />
<br />
If your screen goes blank during the boot process, the problem is likely kernel mode setting, see [[Intel]]. When the Arch logo appears, press <Tab> to enter kernel options. At the end of the line, put a space and then i915.modeset=0<br />
<br />
{{Tip|Error Boot device didn't show up after 30 seconds:<br />
* At the ramfs$ prompt:<br />
* [ramfs /]# udevadm trigger<br />
* [ramfs /]# exit }}<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 conveniently available right on the live system! To access it, change to vc/2 (virtual console #2) with <ALT>+F2, and then invoke <code>/usr/bin/less</code> by typing in the following at the # prompt:<br />
# less /usr/share/aif/docs/official_installation_guide_en<br />
<code>less</code> will allow you to page through the document. Change back to vc/1 with <ALT>+F1 to follow the rest of the install process.<br />
<br />
Change back to vc/2 at any time if you need to reference the Official Guide as you progress through the installation process.<br />
<br />
{{tip|Please note that the official guide only covers installation and configuration of the base system. Once that is installed, it is strongly recommended that you come back here to the wiki to find out more about post-installation considerations and other related issues.}}<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 [[#B: Set Clock|B: Set Clock]].<br />
* Netinstall 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 (Netinstall)====<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 />
=====(A)DSL Quickstart for the Live Environment=====<br />
(If you have a modem or router in bridge mode to connect to your ISP)<br />
<br />
Switch to another virtual console (<Alt> + F2), login as root and invoke <br />
# pppoe-setup<br />
If everything is well configured in the end you can connect to your ISP with <br />
# pppoe-start<br />
<br />
Return to first virtual console with <ALT>+F1. Continue with [[#B: Set Clock|B: Set Clock]]<br />
<br />
=====Wireless Quickstart For the Live Environment=====<br />
(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. Note that the following quickstart procedure ''executed at this point in the installation'' will initialize your wireless hardware for use ''in the live environment''. These steps (or some other form of wireless management) must be repeated from the actual installed system after booting into it. <br />
<br />
Also note that these steps are optional if wireless connectivity is unnecessary at this point in the installation; wireless functionality may always be established later.<br />
<br />
The basic procedure will be:<br />
* Switch to a free virtual console, e.g.: <ALT>+F3<br />
* Login as root<br />
* (Optional) Identify the wireless interface:<br />
# lspci | grep -i net<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 />
Example output:<br />
lo no wireless extensions.<br />
eth0 no wireless extensions.<br />
wlan0 unassociated ESSID:""<br />
Mode:Managed Channel=0 Access Point: Not-Associated <br />
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0 <br />
Retry limit:7 RTS thr:off Fragment thr:off<br />
Power Management:off<br />
Link Quality:0 Signal level:0 Noise level:0<br />
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0<br />
Tx excessive retries:0 Invalid misc:0 Missed beacon:0<br />
<code>wlan0</code> is the available wireless interface in the example.<br />
* Bring the interface up with <code>/sbin/ifconfig <interface> up</code>.<br />
An example using the wlan0 interface:<br />
# ifconfig wlan0 up<br />
(Remember, your interface may be named something else, depending on your module (driver) and chipset: wlan0, eth1, etc.)<br />
<br />
* If the essid has been forgotten or is unknown, use <code>/sbin/iwlist <interface> scan</code> to scan for nearby networks.<br />
# iwlist wlan0 scan<br />
<br />
* Associate your wireless device with the access point you want to use. Depending on the encryption (none, WEP, or WPA), the procedure may differ. You need to know the name of the chosen wireless network (ESSID), e.g. 'linksys' in the following examples:<br />
* An example using a ''non-encrypted'' network:<br />
# iwconfig wlan0 essid &quot;linksys&quot;<br />
* An example using ''WEP and a hexadecimal key'':<br />
# iwconfig wlan0 essid &quot;linksys&quot; key 0241baf34c<br />
* An example using ''WEP and an ASCII passphrase'':<br />
# iwconfig wlan0 essid "linksys" key s:pass1<br />
* Using ''WPA'', the procedure requires a bit more work. Check [[WPA_Supplicant|WPA supplicant]] for more information and troubleshooting. Later on you can automate the process by using [[netcfg]] instead. The following commands generates a configuration file for the network and attempts to connect to that network.<br />
# wpa_passphrase linksys "secretpassphrase" > /etc/wpa_supplicant.conf<br />
# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf<br />
<br />
* Confirm you have successfully associated to the access point before continuing:<br />
# iwconfig wlan0<br />
<br />
* Request an IP address with <code>/sbin/dhcpcd <interface> </code>. e.g.:<br />
# dhcpcd wlan0<br />
* Ensure you can route using <code>/bin/ping</code>:<br />
# ping -c 3 www.google.com<br />
<br />
You should have a working network connection. For troubleshooting, check the detailed [[Wireless_Setup|Wireless Setup]] page.<br />
<br />
======Does the Wireless Chipset require Firmware?======<br />
A small percentage of wireless chipsets also require firmware, in addition to a corresponding driver. If unsure, invoke <code>/usr/bin/dmesg</code> to query the kernel log for a firmware request from the wireless chipset:<br />
# dmesg | grep firmware<br />
Example output from an Intel chipset which requires and has requested firmware from the kernel at boot:<br />
firmware: requesting iwlwifi-5000-1.ucode<br />
If there is no output, it may be concluded that the system's wireless chipset does not require firmware.<br />
<br />
{{Note | '''Wireless chipset firmware packages (for cards which require them) are pre-installed under /lib/firmware in the live environment, (on CD/USB stick) ''but must be explicitly installed to your actual system to provide wireless functionality after you reboot into it!'' Package 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 installed system.<br />
<br />
Return to vc/1 with <ALT>+F1. Continue with [[#B: Set Clock|B: Set Clock]]<br />
<br />
===B: Set Clock===<br />
* UTC - Choose UTC if running only <tt>UNIX</tt>-like operating system(s).<br />
<br />
* localtime - Choose local if multi-booting with a Microsoft Windows OS.<br />
<br />
===C: 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 />
{{Warning|Choosing the Cancel button in the Prepare Hard Drive menu will not cancel the operations you have selected - see {{Bug|19805}}. If you must cancel the installation from this menu, press <Control>+C to exit the installer completely and immediately.}}<br />
<br />
{{Note|Partitioning may be performed before initiating the Arch installation if desired, by utilizing [http://gparted.sourceforge.net/download.php GParted] or other available tools. If the installation drive has already been partitioned to the required specifications, continue with [[#Set Filesystem Mountpoints| Set Filesystem Mountpoints]]}}<br />
<br />
Verify 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) to utilize for the 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 the disk into the following configuration:<br />
<br />
* ext2 /boot partition, default size 32MB. ''You will be prompted to modify the size to your requirement.''<br />
* swap partition, default size 256MB. ''You will be prompted to modify the size to your requirement.''<br />
* A Separate / and /home partition, (sizes can also be specified). Available filesystems include ext2, ext3, ext4, reiserfs, xfs and jfs, but note that ''both / and /home shall share the same fs type'' if choosing the Auto Prepare option.<br />
<br />
Be warned that Auto-prepare will completely erase the chosen hard drive. Read the <font color="red">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 '''[[#D: Select Packages|D: Select Packages]]''' below.''<br />
<br />
{{Note|If you are installing to 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 are 3 types of disk partitions:<br />
#Primary<br />
#Extended<br />
#Logical<br />
'''Primary''' partitions can be bootable, and are limited to 4 partitions per disk or raid volume. If a partitioning scheme requires more than 4 partitions, an '''extended''' partition which will contain '''logical''' partitions will be required.<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 through sda3 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 the 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. If the installation machine provides gratuitous amounts of RAM (more than 1024 MB) it may be possible to completely forget a swap partition altogether, since the option to create a [[HOW TO: Create swap file|swap file]] is always available later. A 1 GB swap partition will be used in this example.<br />
{{Note|If using suspend-to-disk, (hibernate) a swap partition at least '''equal''' in size to the amount of physical RAM is required. 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. If you would like to dual boot Arch Linux and a Windows operating system please see [[Windows and Arch Dual Boot]].<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. Therefore, certain directories under / are not themselves candidates for separate partitions. (See warning below).''<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. /boot is essential for booting, but is unique in that it may still be kept on its own separate partition (if required).''<br />
<br />
'''/home''' ''Provides subdirectories, each named for a system user, for miscellaneous personal data storage as well as user-specific configuration files for applications.''<br />
<br />
'''/usr''' ''While root is the primary filesystem, /usr is the secondary hierarchy for all system users' data, including the majority of multi-user utilities and applications. /usr is shareable, read-only data. This means that /usr shall be shareable between various hosts and must not be written to, except in the case of system update/upgrade. Any information that is host-specific or varies with time is stored elsewhere.''<br />
<br />
'''/tmp''' ''directory for programs that require temporary files such as '.lck' files, which can be used to prevent multiple instances of their respective program until a task is completed, at which point the '.lck' file will be removed. Programs must not assume that any files or directories in /tmp are preserved between invocations of the program and files and directories located under /tmp will typically be deleted whenever the system is booted.''<br />
<br />
'''/var''' ''contains variable data; spool directories and files, administrative and logging data, pacman's cache, the ABS tree, etc. /var exists in order to make it possible to mount /usr as read-only. Everything that historically went into /usr that is written to during system operation (as opposed to installation and software maintenance) must reside under /var.''<br />
{{Warning | Besides /boot, directories essential for booting are: ''''''/bin', '/etc', '/lib', 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 />
{{Note | /var contains many small files. This should be taken into consideration when choosing a filesystem type for it, (if creating its own separate partition).}}<br />
<br />
=====How big should my partitions be?=====<br />
This question is best answered based upon individual needs.<br />
You may wish to simply create '''one partition for root and one partition for swap or only one root partition without swap''' or refer to the following examples and consider these guidelines to provide a frame of reference:<br />
* The root filesystem (/) in the example will contain the /usr directory, which can become moderately large, depending upon how much software is installed. 15-20 GB should be sufficient for most users.<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. If you are using an SSD, you may wish to locate your /var on an HDD and keep the / and /home partitions on your SSD to avoid needless read/writes to the SSD. 8-12 Gigs on a desktop system should be sufficient for /var, depending largely upon how much software you intend to install. Servers tend to have relatively larger /var filesystems.<br />
<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. Remember that if you chose to reinstall Arch, all the data on your /home partition will be untouched (so long as you have a separate /home partition). <br />
<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, ~10GB /var, 1GB swap, and a /home containing the remaining disk space.'''''<br />
<br />
=====Create Partition: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 10256 #/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 />
{{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 />
Specify each partition and corresponding mountpoint to your requirements. (Recall that partitions end in a number. Therefore, '''sda''' is not itself a partition, but rather, signifies an entire drive)<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 backward 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 terabytes. Increases the 32,000 subdirectory limit in ext3 to 64,000. Offers online defragmentation ability. <br />
<br />
4. '''ReiserFS''' (V3)- Hans Reiser's high-performance journaling FS uses a very interesting method of data throughput based on an unconventional and creative algorithm. ReiserFS is touted as very fast, especially when dealing with many small files. ReiserFS is fast at formatting, yet comparatively slow at mounting. Quite mature and stable. ReiserFS is not actively developed at this time (Reiser4 is the new Reiser filesystem). Generally regarded as a good choice for /var/.<br />
<br />
5. '''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 GNU/Linux. JFS currently uses the least CPU resources of any GNU/Linux filesystem. Very fast at formatting, mounting and fsck's, and very good all-around performance, especially in conjunction with the deadline I/O scheduler. (See [[JFS]].) Not as widely supported as ext or ReiserFS, but very mature and stable.<br />
<br />
6. '''XFS''' - Another early journaling filesystem originally developed by Silicon Graphics for the IRIX OS and ported to GNU/Linux. XFS offers very fast throughput on large files and large filesystems. Very fast at formatting and mounting. Generally benchmarked as slower with many small files, in comparison to other filesystems. XFS is very mature and offers online defragmentation ability.<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, utilize [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 are committed to the file system to avoid metadata corruption in the event of a crash. Note that not all journaling techniques are alike; specifically, only ext3 and ext4 offer ''data-mode journaling'', (though, not by default), which journals ''both'' data ''and'' meta-data (but with a significant speed penalty). The others only offer ''ordered-mode journaling'', which journals meta-data only. While all will return your filesystem to a valid state after recovering from a crash, ''data-mode journaling'' offers the greatest protection against file system corruption and data loss but can suffer from performance degradation, as all data is written twice (first to the journal, then to the disk). Depending upon how important your data is, this may be a consideration in choosing your filesystem type.<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. <br />
{{Box Note |If you have not created and do not need a separate /boot partition, you may safely ignore the warning that it does not exist.}} Return to the main menu.<br />
<br />
===D: Select Packages===<br />
<br />
*Core ISO: Choose CD as source and select the appropriate CD drive if more than one exist on the installation machine.<br />
*Netinstall: Select an FTP/HTTP [https://www.archlinux.de/?page=MirrorStatus mirror]. ''Note that archlinux.org is throttled to 50KB/s''.<br />
*All packages during installation are from the [core] repository. They are further divided into '''Base''', and '''Base-devel'''. <br />
*Package information and brief descriptions are available [http://www.archlinux.org/packages/?repo=Core&arch=i686&limit=all&sort=pkgname here].<br />
<br />
Package selection is split into two stages. First, select the package category:<br />
{{Note | For expedience, all packages in '''base''' are selected by default. Use the space-bar to select and de-select packages.}}<br />
* '''Base''': Packages from the [core] repo to provide the minimal base environment. ''Always select it and only remove packages that will not be used.''<br />
* '''Base-devel''': Extra tools from [core] such as '''make''', and '''automake'''. ''Most beginners should choose to install it, and will probably need it later.<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 />
{{Note | If connection to a wireless network is required, remember to select and install the '''wireless_tools''' package. Some wireless interfaces also need [[Wireless_Setup#ndiswrapper|'''ndiswrapper''']] and/or a specific [[Wireless_Setup#Drivers_and_firmware|'''firmware''']]. If you plan to use WPA encryption, you will need [[WPA_Supplicant|'''wpa_supplicant''']]. The [[Wireless_Setup|Wireless Setup page]] will help you choose the correct packages for your wireless device. Also strongly consider installing [[Netcfg|'''netcfg''']], which will help you set up your network connection and profiles.}}<br />
<br />
After selecting the needed packages, leave the selection<br />
screen and continue to the next step, Install Packages.<br />
<br />
===E: 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 />
*Netinstall: 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 image: The packages will be installed from the CD/USB stick.<br />
<br />
===F: 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|udev]]''' should handle most module loading automatically at boot.<br />
<br />
Now you will be asked which text editor you want to use; choose [[Nano|nano]], [http://joe-editor.sourceforge.net/ joe] or [[Vim|vi]], ('''nano''' is generally considered easiest of the 3). You will be presented with a menu including the main configuration files for your system. <br />
<br />
{{Note | ''It is very important at this point to edit, or at least 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 />
'''''Moving on...'''''<br />
<br />
====/etc/rc.conf====<br />
Arch Linux uses the file {{Filename|/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 />
<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 {{Codeline|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 '''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 {{Filename|/dev/rtc}} for hwclock<br />
* '''TIMEZONE'''=: Specify your TIMEZONE. (All available zones are under {{Filename|/usr/share/zoneinfo/}}).<br />
* '''KEYMAP'''=: The available keymaps are in {{Filename|/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 {{Filename|/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 {{Filename|/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 />
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, (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 will be using loopback filesystems, add "loop". Also specify any blacklisted modules by prefixing them with a bang (!). Udev will be forced NOT to load blacklisted modules. In the example, the IPv6 module as well as the annoying pcspeaker are blacklisted.<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=(!net-pf-10 !snd_pcsp !pcspkr loop)<br />
<br />
=====NETWORKING Section=====<br />
* '''HOSTNAME'''=:Set your HOSTNAME to your liking. This is the name of your computer. Whatever you put here, also put it in {{filename|/etc/hosts}}<br />
* '''eth0'''=: 'Ethernet, card 0'. ''If'' you are using '''static IP''', adjust the interface IP address, netmask and broadcast address. Set eth0=&quot;dhcp&quot; if you want to use '''DHCP''' for dynamic/automatic configuration.<br />
* '''INTERFACES'''=: Specify all interfaces here. Multiple interfaces should be separated with a space as in: <br />
(eth0 wlan0)<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 a dynamically assigned IP address ('''DHCP''') ======<br />
<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 />
<br />
======Example, using a '''static''' IP address======<br />
<br />
HOSTNAME=&quot;arch&quot;<br />
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"<br />
INTERFACES=(eth0)<br />
gateway="default gw 192.168.0.1"<br />
ROUTES=(gateway)<br />
<br />
Modify {{Filename|/etc/resolv.conf}} to specify the DNS servers of choice. Example:<br />
<br />
search my.isp.net.<br />
nameserver 4.2.2.1<br />
nameserver 4.2.2.2<br />
nameserver 4.2.2.3<br />
<br />
Various processes can overwrite the contents of {{filename|/etc/resolv.conf}}. For example, by default Arch Linux uses the '''dhcpcd''' DHCP client, which will overwrite the file when it starts. [[Resolv.conf|Various methods]] may be used to preserve the nameserver settings in {{filename|/etc/resolv.conf}}. For example, dhcpcd's configurations file may be edited to prevent the dhcpcd daemon from overwriting the file. To do this, you will need to append this to the end of {{Filename|/etc/dhcpcd.conf}}:<br />
<br />
nohook resolv.conf<br />
<br />
{{tip|If using a non-standard MTU size (a.k.a. jumbo frames) is desired AND the installation machine hardware supports them, see the [[Jumbo Frames]] wiki article for further configuration.}}<br />
<br />
=====DAEMONS Section=====<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. Asynchronous initialization by backgrounding is also supported and useful for speeding up boot. <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 (@), it shall be executed in the background; the startup sequence will not wait for successful completion of each daemon before continuing to the next. (Useful for speeding up system boot). Do not background daemons that are needed by other daemons. For example "mpd" depends on "network", therefore backgrounding network may cause mpd to break.<br />
*Edit this array whenever new system services are installed, if starting them automatically during boot is desired.<br />
<br />
{{Note | This 'BSD-style' init, is the Arch way of handling what other distributions handle with various symlinks to an /etc/init.d directory.}}<br />
<br />
======About DAEMONS======<br />
The [[daemons]] line need not be changed at this time, but it is useful to explain what daemons are, as they will be addressed later in this guide.<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 (e.g.:httpd) or an SSH server waiting for a user login (e.g.:sshd). While these are full-featured applications, there are also daemons whose work is not that visible. Examples are a daemon which writes messages into a log file (e.g. syslog, metalog), a daemon which lowers the CPU frequency if the system has nothing to do (e.g.:cpufreq), and a daemon which provides a graphical login (e.g.: gdm, kdm). All these programs can be added to the daemons line and will be started when the system boots. Useful daemons will be presented during this guide.<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. <tt>UNIX</tt> 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/sda1 / jfs defaults,noatime 0 1<br />
/dev/sda2 /var reiserfs defaults,noatime,notail 0 2<br />
/dev/sda3 swap swap defaults 0 0<br />
/dev/sda4 /home jfs defaults,noatime 0 2<br />
{{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 (see [http://kerneltrap.org/node/14148 here] for more). 'notail' disables the ReiserFS tailpacking feature, for added performance at the cost of slightly less efficient disk usage.}}<br />
<br />
* '''<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'. <br />
<br />
{{Note | If your system has more than one hard drive, the installer will default to using UUID rather than the sd''x'' naming scheme, for consistent device mapping. '''[[Persistent block device naming| Utilizing UUID]] has several advantages and may also be preferred to avoid issues if hard disks are added to the system in the future.''' Due to active developments in the kernel and also udev, the ordering in which drivers for storage controllers are loaded may change randomly, yielding an unbootable system/kernel panic. Nearly every motherboard has several controllers (onboard SATA, onboard IDE), and due to the aforementioned development updates, /dev/sda may become /dev/sdb on the next reboot. (See [[Persistent block device naming| this wiki article]] for more information on persistent block device naming. )}}<br />
<br />
* '''<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 />
* '''<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 />
* '''<options>''': describes the mount options associated with the filesystem. It is formatted as a comma-separated list of options with no intervening spaces. It contains at least the type of mount plus any additional options appropriate to the filesystem type. For documentation on the available options for non-nfs file systems, see mount(8).<br />
<br />
* '''<dump>''': used by the dump(8) command to determine which filesystems are to be dumped. dump is a backup utility. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be backed up. ''Note that dump is not installed by default.''<br />
<br />
* '''<pass>''': 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 />
Expanded information available in the [[Fstab]] wiki entry.<br />
<br />
===='''[[Configuring mkinitcpio | /etc/mkinitcpio]].conf'''====<br />
''Most users will not need to modify this file at this time, but please read the following explanatory information.''<br />
<br />
This file allows further fine-tuning of the initial ram filesystem, or initramfs, (also historically referred to as the initial ramdisk or &quot;initrd&quot;) for your system. The initramfs is a gzipped image that is read by the kernel during boot. The purpose of the initramfs is to bootstrap the system to the point where it can access the root filesystem. This means it has to load any modules that are required for devices like IDE, SCSI, or SATA drives (or USB/FW, if you are booting from a USB/FW drive). Once the initrramfs loads the proper modules, either manually or through udev, it passes control to the kernel and your boot continues. For this reason, the initramfs only needs to contain the modules necessary to access the root filesystem. It does not need to contain every module you would ever want to use. The majority of common kernel modules will be loaded later on by udev, during the init process.<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 '''glibc''' and '''busybox''' 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 />
<br />
If using RAID or LVM on the root filesystem, the appropriate HOOKS must be configured. See the wiki pages for [[Installing with Software RAID or LVM| RAID]] and [[Configuring mkinitcpio | /etc/mkinitcpio]] for more info. If using a non-US keyboard. add the "<code>keymap</code>" hook to load your local keymap during boot. Add the "<code>usbinput</code>" hook if using a USB keyboard. Don't forget to add the "<code>usb</code>" hook when installing arch on an external hard drive which is connected via usb, e.g.:<br />
HOOKS="base udev autodetect pata scsi sata usb filesystems keymap usbinput"<br />
(Otherwise, if boot fails for some reason you will be asked to enter root's password for system maintenance but will be unable to do so.)<br />
<br />
If you need support for booting from USB devices, FireWire devices, PCMCIA devices, NFS shares, software RAID arrays, LVM2 volumes, encrypted volumes, or DSDT support, configure your HOOKS accordingly. <br />
<br />
If doing a CF or SD card install, you may need to add the <code>usb</code> HOOK for your system to boot properly. <br />
<br />
''If you are using a US keyboard, and have no need for any of the above HOOKS, editing this configuration should be unnecessary at this point.''<br />
<br />
'''mkinitcpio''' is an Arch innovation developed by Aaron Griffin and Tobias Powalowski with some help from the community.<br />
<br />
==== /etc/modprobe.d/modprobe.conf====<br />
<br />
This file can be used to set special configuration options for the kernel modules. It is unnecessary to configure this file in the example.<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 />
{{Note |''This format, '''including the 'localhost' and your actual host name''', is required for program compatibility! So, if you have named your computer "arch", then that line above should look like this:<br />
127.0.0.1 localhost.localdomain localhost arch<br />
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 />
* restrict it to your local LAN network (range 192.168.0.0 to 192.168.0.255)<br />
sshd: 192.168.0.<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 text, correctly displaying regional monetary values, time and date formats, alphabetic idiosyncrasies, and other locale-specific standards.<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 />
{{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 />
====Pacman-Mirror====<br />
Choose a mirror repository for '''pacman'''. <br />
*''archlinux.org is throttled, limiting downloads to 50KB/s''<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 />
===G: 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] or [[Syslinux]].<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/sda1 ro vga=773<br />
initrd /boot/kernel26.img<br />
{{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 />
Example for /boot on the separate partition:<br />
title Arch Linux (Main)<br />
root (hd0,0) <br />
kernel /vmlinuz26 root=/dev/sda3 ro vga=773<br />
initrd /kernel26.img<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'''). <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, (usually a safe default; you may wish to change this in case it causes problems booting) and the '''&quot;vga=773&quot;''' argument will give a 1024x768 framebuffer with 256 color depth.<br />
<br />
Please note: You may have to add rootdelay=8 to the kernel options in order to be able to boot from an external usb hard drive.<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 />
{{tip|For more details, see the [[GRUB]] wiki page.}}<br />
<br />
===H: 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 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 />
{{Note |Virtual consoles 1-6 are available. You may switch between them with ALT+F1...F6}}<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, an &quot;unknown host&quot; error is received, you may conclude that your network is not properly configured. You may choose to double-check the following files for integrity and proper settings:<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 />
{{Tip|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 wlan0 up<br />
<br />
{{Note|If you get this error message: <code>SIOCSIFFLAGS: No such file or directory</code> it most certainly means your wireless chipset requires a firmware to function, which you forgot to install during package selection. See [[Beginners'_Guide#Does_the_Wireless_Chipset_require_Firmware.3F|Does the Wireless Chipset require Firmware?]] and [[Beginners'_Guide#D:_Select_Packages|Select Packages]].}}<br />
<br />
* Associate your wireless device with the access point you want to use. Depending on the encryption (none, WEP, or WPA), the procedure may differ. You need to know the name of the chosen wireless network (ESSID), e.g. 'linksys' in the following examples:<br />
* An example using a ''non-encrypted'' network:<br />
# iwconfig wlan0 essid &quot;linksys&quot;<br />
* An example using ''WEP and a hexadecimal key'':<br />
# iwconfig wlan0 essid &quot;linksys&quot; key 0241baf34c<br />
* An example using ''WEP and an ASCII passphrase'':<br />
# iwconfig wlan0 essid "linksys" key s:pass1<br />
* Using ''WPA'', the procedure requires a bit more work. Check [[WPA_Supplicant|WPA supplicant]] for more information and troubleshooting:<br />
# wpa_passphrase linksys "secretpassphrase" > /etc/wpa_supplicant.conf<br />
# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf<br />
<br />
* Check you have successfully associated to the access point before continuing:<br />
# iwconfig wlan0<br />
<br />
* Request an IP address with <code>/sbin/dhcpcd <interface> </code>. e.g.:<br />
# dhcpcd wlan0<br />
* Ensure you can route using <code>/bin/ping</code>:<br />
# ping -c 3 www.google.com<br />
<br />
You should have a working network connection. For troubleshooting, check the detailed [[Wireless_Setup|Wireless Setup]] page.<br />
<br />
====Proxy Server====<br />
If you are behind a proxy server, edit /etc/wgetrc and set http_proxy and ftp_proxy in it.<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' at boot, 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 />
====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, to occupy a very modest memory footprint, and to be 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. Pacman's output is streamlined, very readable and provides ETA for each package download. Arch uses pkg.tar.gz tarballs and is in the process of moving to the pkg.tar.xz format. <br />
<br />
Pacman will now be used to download software packages from remote repositories and install them onto your system.<br />
<br />
====Package Repositories====<br />
Arch currently offers the following 5 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 ensure the system remains in a usable state. These are the absolute system-critical packages. <br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<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. <br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<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 />
<br />
<nowiki>*</nowiki> they are expected to break something on update and need to be tested first.<br />
<br />
<nowiki>*</nowiki> 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. <br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<br />
{{Note|[testing] is the only repository that can have name collisions with any of the other official repositories. Therefore, if enabled, [testing] must be the first repo listed in <code>pacman.conf</code>.}}<br />
<br />
{{Warning|Only experienced users should use [testing].}}<br />
<br />
'''[community]'''<br />
<br />
The [community] repository is maintained by the ''Trusted Users (TUs)'' and is simply the binary branch of the ''Arch User Repository ([[AUR]])''. It contains binary packages which originated as PKGBUILDs from ''AUR'' [unsupported] that have acquired enough votes and were adopted by a ''TU''. Like all repos listed above, [community] may be readily accessed by pacman.<br />
* TU maintained<br />
* All binary packages<br />
* pacman accessible<br />
<br />
'''[multilib]'''<br />
<br />
Users running 64 bit arch linux may want to install and use applications that are not available in 64 bit (and most desktop or laptop users probably will). The 32 bit versions of these applications can be used, but require that certain 32 bit libraries are installed. These libraries are available in the [multilib] repository. <br />
* Developer maintained<br />
* All binary packages<br />
* pacman accessible<br />
<br />
{{Note | If you want to use this repository, you should add the lines below to <code>/etc/pacman.conf</code> }}<br />
[multilib]<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
'''AUR (unsupported)'''<br />
<br />
The '''[[AUR]]''' also contains the '''unsupported''' branch, which cannot be accessed directly by pacman*. '''AUR''' [unsupported] does not contain binary packages. Rather, it provides more than sixteen thousand PKGBUILD scripts for building packages from source, that may be unavailable through the other repos. When an AUR unsupported package acquires enough popular votes, it may be moved to the AUR [community] binary repo, if a TU is willing to adopt and maintain it there.<br />
* TU maintained<br />
* All PKGBUILD bash build scripts<br />
* '''''Not''''' pacman accessible by default<br />
<br />
<nowiki>*</nowiki> pacman wrappers ('''''[[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 />
<br />
Note that the defaults should work, so modifying at this point may be unnecessary, but verification is always recommended. Further info available in the [[Mirrors]] article.<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 />
*'''''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 />
Defines pacman repository mirrors and priorities.<br />
<br />
'''Build a mirrorlist using the rankmirrors script''' (Optional)<br />
<br />
<code>/usr/bin/rankmirrors</code> is a bash script which will attempt to detect uncommented mirrors specified in /etc/pacman.d/mirrorlist which are closest to the installation machine based on latency. Faster mirrors will dramatically improve pacman performance, and the overall Arch Linux experience. This script may be run periodically, especially if the chosen mirrors provide inconsistent throughput and/or updates. Note that <code>rankmirrors</code> does not test for throughput. Too/ls such as <code>wget</code> or <code>rsync</code> may be used to effectively test for mirror throughput after a new <code>/etc/pacman.d/mirrorlist</code> has been generated. <br />
<br />
'''Initially force pacman to refresh the package lists'''<br />
<br />
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 />
Use pacman to install curl:<br />
# pacman -S curl<br />
<br />
*'''''If you get an error at this step, use the command "nano /etc/pacman.d/mirrorlist" and uncomment a server that suits you.'' ''<br />
<br />
'''cd''' to the /etc/pacman.d/ directory:<br />
# cd /etc/pacman.d<br />
Backup the existing /etc/pacman.d/mirrorlist:<br />
# cp mirrorlist mirrorlist.backup<br />
Edit mirrorlist.backup and uncomment all mirrors on the same continent or within geographical proximity to test with rankmirrors.<br />
# nano mirrorlist.backup<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 closest mirrors<br />
<br />
Force pacman to refresh all package lists with the new mirrorlist in place:<br />
# pacman -Syy<br />
<br />
If you want to get help from the IRC channel, you will find it easier if you install and use curlpaste:<br />
# pacman -S curlpaste<br />
<br />
====Mirrorcheck for up-to-date packages====<br />
Some of the official mirrors may contain packages that are out-of-date. [https://www.archlinux.de/?page=MirrorStatus;orderby=lastsync;sort=1 ArchLinux Mirrorcheck] reports various aspects about the mirrors such as network problems with mirrors, data collection problems, the last time mirrors have been synced, etc.<br />
<br />
One may wish to manually inspect /etc/pacman.d/mirrorlist, ensuring that the file contains only up-to-date mirrors if having the latest package versions is a priority.<br />
<br />
====Ignoring packages====<br />
After executing the command &quot;pacman -Syu&quot;, the entire system will be updated. It is possible to prevent a package from being upgraded. A typical scenario would be a package for which an upgrade may prove problematic for the system. In this case, there are two options; indicate the package(s) to skip in the pacman command line using the --ignore switch (do pacman -S --help for details) or permanently indicate the package(s) to skip in the /etc/pacman.conf file in the IgnorePkg array. List each package, with one intervening space :<br />
IgnorePkg = wine <br />
The typical way to use Arch is to use pacman to install all packages unless there is no package available, in which case [[ABS]] may be used. Many user-contributed package build scripts are also available in the [[AUR]] and can be installed manually with [[makepkg]], or with an [[AUR helper]].<br />
<br />
The power user is expected to keep the system up to date with pacman -Syu, rather than selectively upgrading packages. You may diverge from this typical usage as you wish; just be warned that there is a greater chance that things will not work as intended and that it could break your system. The majority of complaints happen when selective upgrading, unusual compilation or improper software installation is performed. Use of '''IgnorePkg''' in /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, have a look at the [[pacman]] wiki entry at your own leisure.<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 required configurations and modifications 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 />
or:<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 />
{{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 />
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 />
=====Network Time Protocol=====<br />
You may wish to set the system time using NTP to sync the local clock to remote NTP servers.<br />
<br />
For more information and setup instructions, see the [[Network Time Protocol]] article.<br />
<br />
===Step 4: Add a user and setup groups===<br />
<tt>UNIX</tt> 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 />
<br />
useradd -m -g [initial_group] -G [additional_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''' The group name or number of the user's initial login group. The group name must exist. If a group number is provided, it must refer to an already existing group. If not specified, the behavior of useradd will depend on the USERGROUPS_ENAB variable contained in /etc/login.defs.<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. <br />
* '''-s''' The path and filename of the user´s default login shell. Arch Linux init scripts use Bash. After the boot process is complete, the default login shell is user-specified. (Ensure the chosen shell package is installed if choosing something other than Bash). <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 hardware acceleration<br />
*'''wheel''' - for using sudo<br />
*'''games''' - needed for write permission for games in the games group<br />
*'''power''' - used w/ power options (e.g.: shutdown with power button)<br />
*'''scanner''' - for using a scanner<br />
A typical desktop system example, adding a user named "archie" specifying bash as the login shell:<br />
useradd -m -g users -G audio,lp,optical,storage,video,wheel,games,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 <tt>UNIX</tt> password.)<br />
<br />
Your new non-root user has now been created, complete with a home directory and a login password.<br />
<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 />
If you want to change the name of your user or any existing user, see the [[Change username]] page of the Arch wiki and/or 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 />
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.<br />
<br />
By default, the visudo command uses the editor [[vi]]. If you do not know how to use vi, you may set the EDITOR environment variable to the editor of your choice, such as in this example with the editor "nano":<br />
# EDITOR=nano visudo<br />
{{Note|Please note that you are setting the variable and starting visudo on the same line at the same time. This will not work properly as two separated commands.}}<br />
<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 />
In the previous section we added your user to the "wheel" group. To give users in the wheel group full root privileges when they precede a command with &quot;sudo&quot;, uncomment the following line:<br />
%wheel ALL=(ALL) ALL<br />
Now you can give any user access to the sudo command by simply adding them to the wheel group.<br />
<br />
For more information, such as sudoer <TAB> completion, see [[Sudo]]<br />
<br />
To give '''only''' users in the "wheel" group access to the "su" command, open up /etc/pam.d/su and uncomment the following line:<br />
auth required pam_wheel.so use_uid<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 />
{{Note| Alsa is included in the Arch mainline kernel and udev will automatically probe your hardware at boot, loading the corresponding kernel module for your audio card. Therefore, your sound should already be working, but upstream sources mute all channels by default.}}<br />
{{Note| OSS4.2 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.2 instead. Instructions can be found in [[OSS]]}} <br />
<br />
The alsa-utils package contains the alsamixer userspace tool, which allows configuration of the sound device from the console or terminal.<br />
<br />
By default the upstream kernel sources ship 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.d/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 />
{{Note | You will need to unload all your sound modules and reload them for the changes to take effect. 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, 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 {{keypress|M}}. With the key {{keypress|↑}} increased the volume to obtain a value of zero dB gain, this wording is found in the upper left. Higher values of gain produce distorted sounds and crackling.<br />
<br />
Card: NVidia CK804<br />
Chip: Realtek ALC658D<br />
View: F3:[Playback] F4: Capture F5: All<br />
Item: PCM ['''dB gain: 0,00, 0,00''']<br />
<br />
Usually a value around 75 produces a gain of zero, but some cards to a maximum value do not add any gain. Some machines, (like the Thinkpad T61), have a '''Speaker''' channel which must be unmuted and adjusted as well. Leave alsamixer by pressing ESC. <br />
<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 woman's voice saying, &quot;Front, center.&quot;<br />
<br />
==== Saving the Sound Settings ====<br />
Switch back to root user and store these settings using <code>/usr/sbin/alsactl</code> :<br />
# alsactl store<br />
This will create the file '/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 at boot.<br />
# nano /etc/rc.conf<br />
DAEMONS=(syslog-ng network crond '''alsa''')<br />
{{Note| 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 />
<br />
{{warning|Since v. 1.8, xorg-server uses multiple configuration files within /etc/X11/xorg.conf.d, instead of the singular xorg.conf. xorg.conf is mostly deprecated, even though it is parsed by Xorg-server during its initialization. It is '''highly recommended''' to follow the instructions given in the '''[[Xorg]]''' wiki page to set up '''X'''. This in particular applies to all configuration tools that generate a {{filename|xorg.conf}} file instead of the multiple configuration files in {{filename|/etc/xorg.conf.d}}.}}<br />
<br />
The '''X''' Window System version 11 (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 <tt>UNIX</tt>-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 />
{{Warning|If you'er installing Arch in a Virtualbox guest , you need a different way to complete X installation. See this [[Virtualbox#Running_Arch_Linux_as_a_guest|Running_Arch_Linux_as_a_guest]],then skip All ABC steps.<br />
}}<br />
<br />
====A: The <code>X-Files</code>====<br />
Now we will install the base '''[[Xorg]]''' packages using pacman. This is the first step in building a GUI.<br />
<br />
Install the base packages:<br />
# pacman -S xorg<br />
The 3d utilities glxgears and glxinfo are included in the '''mesa''' package:<br />
# pacman -S mesa<br />
<br />
====B: Install Video Driver Package====<br />
<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 {{filename | /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 />
If you plan on using an '''open-source''' video driver, and need 3d acceleration, install the libgl library (if you use a proprietary driver, don't install this):<br />
# pacman -S libgl<br />
{{Note|The open source packages (in most cases) will automatically install libgl. Proprietary packages (in most cases) will remove libgl automatically.}}<br />
''(Proprietary video drivers provide their own gl library implementations.)''<br />
Here is a list of '''open source''' drivers, and the corresponding video chipsets:<br />
*'''xf86-video-apm''' &mdash; Alliance ProMotion video driver<br />
*'''xf86-video-ark''' &mdash; ark video driver<br />
*'''xf86-video-ati''' &mdash; ATI(AMD) radeon video driver<br />
**'''xf86-video-r128''' &mdash; ATI(AMD) video driver for X.org ati Rage128 video<br />
**'''xf86-video-mach64''' &mdash; ATI(AMD) video driver for X.org mach64 video<br />
**'''xf86-video-radeonhd''' &mdash; ATI(AMD) radeonhd video driver<br />
*'''xf86-video-chips''' &mdash; Chips and Technologies video driver<br />
*'''xf86-video-cirrus''' &mdash; Cirrus Logic video driver<br />
*'''xf86-video-dummy''' &mdash; dummy video driver<br />
*'''xf86-video-fbdev''' &mdash; framebuffer video driver<br />
*'''xf86-video-glint''' &mdash; GLINT/Permedia video driver<br />
*'''xf86-video-i128''' &mdash; Number 0 i128 video driver<br />
*'''xf86-video-i740''' &mdash; Intel i740 video driver<br />
*'''xf86-video-i810''' &mdash; Intel i810/i830/i9xx video drivers (deprecated - use -intel)<br />
*'''xf86-video-intel''' &mdash; Newer Version of Intel i810/i830/i9xx video drivers (xf86-video-intel-legacy merged into this)<br />
*'''xf86-video-imstt''' &mdash; Integrated Micro Solutions Twin Turbo video driver<br />
*'''xf86-video-mga''' &mdash; mga video driver (Matrox Graphics Adapter)<br />
*'''xf86-video-neomagic''' &mdash; neomagic video driver<br />
*'''xf86-video-nv''' &mdash; Nvidia nv video driver<br />
*'''xf86-video-nouveau''' &mdash; Open Source 3D acceleration driver for nVidia cards (experimental), check: [http://nouveau.freedesktop.org/wiki/] for Current Status<br />
*'''xf86-video-openchrome''' &mdash; VIA/S3G UniChrome, UniChrome Pro and Chrome9 video driver<br />
*'''xf86-video-rendition''' &mdash; Rendition video driver<br />
*'''xf86-video-s3''' &mdash; S3 video driver<br />
*'''xf86-video-s3virge''' &mdash; S3 Virge video driver<br />
*'''xf86-video-savage''' &mdash; savage video driver<br />
*'''xf86-video-siliconmotion''' &mdash; siliconmotion video driver<br />
*'''xf86-video-sis''' &mdash; SiS video driver<br />
*'''xf86-video-sisusb''' &mdash; SiS USB video driver<br />
*'''xf86-video-tdfx''' &mdash; tdfx video driver<br />
*'''xf86-video-trident''' &mdash; Trident video driver<br />
*'''xf86-video-tseng''' &mdash; tseng video driver<br />
*'''xf86-video-unichrome''' &mdash; VIA S3 Unichrome video drivers<br />
*'''xf86-video-v4l''' &mdash; v4l video driver<br />
*'''xf86-video-vesa''' &mdash; vesa video driver<br />
*'''xf86-video-vga''' &mdash; VGA 16 color video driver<br />
*'''xf86-video-vmware''' &mdash; vmware video driver<br />
*'''xf86-video-voodoo''' &mdash; voodoo video driver<br />
<br />
'''''Note''''': The '''vesa''' driver is the most generic, and should work with almost any modern video chipset. If you cannot find a suitable driver for your video chipset, vesa ''should'' work, but offers only 2D acceleration.<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 graphics card you may wish to install the proprietary NVIDIA or ATI drivers. '''Installing proprietary video drivers is covered below.'''.<br />
*If you do not want to install the proprietary drivers or do not have an NVIDIA or ATI graphics card, you should skip down to '''[[#C: Install Input Driver Packages|C: Install Input Driver Packages]]'''.<br />
<br />
=====NVIDIA Graphics Cards=====<br />
The NVIDIA proprietary drivers are generally considered to be of good quality, and offer good 3D performance, whereas the open source '''nv''' driver offers only 2d support at this time and the new '''nouveau''' driver offers only experimental 3D acceleration. <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 />
'''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 />
{{Note | 1=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.}}<br />
<br />
{{Note | 1=Currently Nvidia-96.xx drivers do not support Xorg release 1.8. Please see the news post here: [http://www.archlinux.org/news/502/]. This is not the case if you get the latest binary driver directly from the nVidia site.}}<br />
<br />
Consult the [http://www.nvidia.com/Download/index.aspx NVIDIA website] 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 />
{{Note | 1=At this point, with the 'nvidia' driver, you may be told there is a fatal error when trying to load the driver. If this happens, rebooting should fix the problem. }}<br />
{{Note | 1=It is best to install the binary driver directly from the nVidia website for newer cards (newer than 3 years). If you find that you upgraded your kernel and you can't install your nVidia drivers because nouveau is running and nouveau can't be removed via the rmmod command then edit /etc/modprobe.d/modprobe.conf and append "blacklist nouveau". Reboot and try installing the nVidia driver again. Configure your nVidia proprietary driver by either running nvidia-xconfig and/or nvidia-settings (GUI). See man pages of associated commands for configuration options.}}<br />
<br />
Continue with '''[[#C: Install Input Driver Packages|C: Install Input Driver Packages]]'''.<br />
<br />
=====ATI Graphics Cards=====<br />
ATI owners have multiple options for drivers. <br />
* The open source '''''radeon''''' driver provided by the '''xf86-video-ati''' package.<br />
** This is the original, reverse-engineered open source driver which fully supports Radeon chipsets up to X1950 (latest R500 chipsets). Cards up to the 9200 series are fully supported, stable, and provide full 2D and 3D acceleration. Cards from 9500 to HD4000 feature full 2D acceleration, and stable/partly implemented 3D acceleration, but lack certain features provided by the proprietary driver; power management is under development and in an advanced stage, but not on par with catalyst. HD5000 support is currently a work in progress. Supports KMS and HDMI with audio output since kernel 2.6.33.<br />
* The open source '''''radeonhd''''' driver provided by the '''xf86-video-radeonhd''' package.<br />
** This driver supports ATI R500 chipsets (Radeon X1000 series) and newer. It is written by Novell with specifications provided to the public by AMD. It supports RandR 1.2. Development is currently as good as dead and functionality may be inconsistent across the spectrum of cards supported. Supports HDMI with audio.<br />
* The proprietary '''''fglrx''''' driver provided by the Catalyst package located in the AUR. The proprietary driver is covered below.<br />
The open-source drivers will usually suit most needs and are generally less problematic.<br />
<br />
Install the '''''radeon''''' ATI Driver with<br />
# pacman -S xf86-video-ati libgl ati-dri<br />
Install the '''''radeonhd''''' ATi Driver with<br />
# pacman -S xf86-video-radeonhd libgl ati-dri<br />
<br />
The proprietary ATI driver '''Catalyst''' was once a precompiled package offered by Arch in the <code>extra</code> repository, but as of March 2009, official support has been dropped because of dissatisfaction with the quality and speed of development of the proprietary driver. The catalyst driver is now available in [http://aur.archlinux.org/packages.php?ID=29111 AUR]. Installation information for Catalyst driver is available [[ATI_Catalyst | here]]<br />
<br />
{{Warning| The proprietary ATI driver supports only R600 and newer devices (that means, HD2xxx and newer). Older series cards (X1xxx and older) are not supported.}}<br />
<br />
{{Tip|Advanced instructions for ATI configuration can be found in the [[ATI | ATI wiki article]].}}<br />
<br />
====C: Install Input Driver Packages====<br />
The latest X requires you to install drivers for your input devices, keyboard and mouse included. For a complete list of available input drivers, invoke a pacman search:<br />
# pacman -Ss xf86-input | less<br />
<br />
For most users, xf86-input-keyboard and xf86-input-mouse should be sufficient for a basic setup. Use pacman to install your desired drivers for your input devices. e.g.:<br />
# pacman -S xf86-input-keyboard xf86-input-mouse<br />
Laptop users (or users with a touchscreen) will also need the synaptics package to allow X to configure the touchpad/touchscreen:<br />
# pacman -S xf86-input-synaptics<br />
{{Tip|For instructions on fine tuning or troubleshooting touchpad settings, see the [[Touchpad Synaptics]] article.}}<br />
{{Warning|Some users had some problems with xf86-input-keyboard and xf86-input mouse. If your mouse and keyboard doesn't work and X seems freezed try uninstalling. For more information read the following forum post [[http://bbs.archlinux.org/viewtopic.php?id=89352]] }}<br />
<br />
===Step 3: Configure X (Optional)===<br />
At this point, reboot so that your system has the proper video drivers loaded, then proceed.<br />
====A: Introduction to the config file :xorg.conf====<br />
<br />
{{Warning | 1=Since v. 1.8, xorg-server uses multiple configuration files within /etc/X11/xorg.conf.d, instead of the singular xorg.conf. xorg.conf is mostly deprecated, even though it is parsed by Xorg-server during its initialisation. It is '''highly recommended''' to follow the instructions given in the '''[[Xorg]]''' wiki page to set up '''X''' until this section is updated. This in particular applies to all configuration tools that generate a {{filename|xorg.conf}} file instead of the multiple configuration files in {{filename|/etc/xorg.conf.d}}.}}<br />
<br />
{{Note | Since X11R7.2 the X.Org X Server features autoconfiguration. Therefore, it can function without an xorg.conf file in many cases. ''If'' the autoconfiguration ''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 and continue below with [[#B: Input hotplugging| Input hotplugging]].}}<br />
<br />
{{filename | /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 />
=====Standard xorg.conf generation=====<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 />
<br />
Newer versions of the Xorg Server(>1.6) do not include the /usr/bin/xorgconfig or /usr/bin/xorgcfg scripts. If you run into problems generating/using an xorg.conf file, you might want to consider using this guide.<br />
<br />
See the [[Xorg#Without_xorg.conf|article on X.Org, section "Without xorg.conf"]].<br />
<br />
* Note that if you are in possession of a properly 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 />
<br />
{{Tip | For Intel graphics card, specific configuration may be necessary to get proper 2D or 3D performance, as stated in the [[Intel]] wiki article.}}<br />
<br />
If you have a nvidia graphics card and chose to install the proprietary nvidia driver, you should configure it now. Otherwise jump to '''[[#B: Input hotplugging|B: Input hotplugging]]'''<br />
<br />
The NVIDIA package has a utility for creating (or updating an existing) {{filename | /etc/X11/xorg.conf}} for use with the NVIDIA driver:<br />
# nvidia-xconfig<br />
{{Note |The script output will inform you of a method of testing the created file. }}<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 />
If there are instances of DRI, ensure they are commented out:<br />
# Load &quot;dri&quot;<br />
Double check your {{filename | /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 />
{{Tip|Advanced instructions for NVIDIA configuration can be found in the [[NVIDIA]] article.}}<br />
<br />
====B: Input hotplugging====<br />
<br />
[[Xorg input hotplugging|Input hotplugging]] is supported since the 1.4 version of the X.Org X Server and enabled by default. When enabled, X will now utilize udev to allow for the hotplugging and removal of human interface devices without having to restart X. <br />
<br />
{{Note | As of X.Org X Server 1.8, the hal daemon is no longer utilized for input hotplugging. Rather, udev is used. (Installed by default) }}<br />
<br />
You must decide whether you will use input hotplugging (enabled by default), or disable it. Input hotplugging is convenient for many users, especially those with mobile machines like laptops and netbooks. Other users may wish to disable it in favor of manual or more static device configuration within /etc/xorg.conf.<br />
<br />
{{Tip | See the article on [[Xorg input hotplugging]] for full details.}}<br />
<br />
=====Using input hotplugging=====<br />
<br />
Install the evdev input driver:<br />
# pacman -S xf86-input-evdev<br />
<br />
If you do not use a standard US keyboard you need to set the keyboard layout in the file /etc/X11/xorg.conf.d/10-evdev.conf like this:<br />
Section "InputClass"<br />
Identifier "evdev keyboard catchall"<br />
MatchIsKeyboard "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Driver "evdev"<br />
'''Option "XkbLayout" "be"'''<br />
EndSection<br />
<br />
{{Note|The '''XkbLayout''' key may differ from the keymap code you used with the km or loadkeys command. For instance, the uk layout corresponds to the key: '''gb'''.}}<br />
<br />
=====Disable input hotplugging=====<br />
Disabling input hotplugging will skip devices detected by udev and will use the keyboard/mouse configuration from {{filename | /etc/X11/xorg.conf}}:<br />
# nano /etc/X11/xorg.conf<br />
add the following:<br />
Section &quot;ServerFlags&quot;<br />
Option &quot;AutoAddDevices&quot; &quot;False&quot;<br />
EndSection<br />
<br />
=====Set the keyboard layout if not using a standard US keyboard=====<br />
Add option lines in the &quot;InputDevice&quot; section of the {{filename | /etc/X11/xorg.conf}} file specifying the keyboard layout and variant. <br />
<br />
Example:<br />
Option &quot;XkbLayout&quot; &quot;be&quot;<br />
Option &quot;XkbVariant&quot; &quot;&quot;<br />
<br />
Alternative method using the setxkbmap command:<br />
# setxkbmap pl <br />
(with the proper keyboard layout instead of <code>pl</code> of course) should switch your keyboard layout in x.<br />
To make this permanent, add this command to <code>/home/<youruser>/.xinitrc</code> before starting the window manager (before command like <code>exec startxfce4</code>).<br />
<br />
==== C: Test X ====<br />
<br />
First, read the warning about input hotplugging in the previous section. At this point, you should have xorg installed, with a suitable video driver and an {{filename | /etc/X11/xorg.conf}} configuration file, (unless you chose to attempt to use '''X''' without it which is perfectly acceptable).<br />
<br />
If you want to test your configuration quickly, to ensure your ability to successfully start '''X''' from the command line and before installing a complete desktop environment, you can do so by starting X, which will in turn invoke '''xterm'''. Xterm is a simple [[Terminal Emulator|terminal emulator]] which runs in the '''X''' Server environment; it is installed as part of the base xorg packages.<br />
<br />
To start X, use<br />
# startx<br />
or<br />
# xinit -- /usr/bin/X -nolisten tcp<br />
<br />
To exit:<br />
# exit<br />
<br />
If you prove a properly configured {{filename | /etc/X11/xorg.conf}} by successfully running the test, you can be assured that your DE/WM of choice will work smoothly.<br />
{{Tip|Advanced instructions for Xorg configuration can be found in the [[Xorg]] article.}}<br />
<br />
{{Note| As of Xorg 1.6, CTRL-Alt-Backspace has been deprecated and will not work to exit out of this test. A possible workaround is to switch to a different virtual console (CTRL-Alt-F2, for example) and then switch back to the console the test is running in (probably CTRL-Alt-F1). You will then be able to use CTRL-C to kill the X test. You can enable CTRL-Alt-Backspace by editing xorg.conf, as described [http://wiki.archlinux.org/index.php/Xorg#Ctrl-Alt-Backspace_doesn.27t_work here].}}<br />
If the screen goes black, you may still attempt to switch to a different virtual console (CTRL-Alt-F2, for example), and login blindly as root, followed by <Enter>, followed by root's password followed by <Enter>. <br />
<br />
You can attempt to kill the X server with <code>/usr/bin/pkill</code>:<br />
# pkill X<br />
If pkill does not work, reboot blindly with:<br />
# reboot<br />
or <br />
# init 6<br />
<br />
======In case of errors======<br />
If you have problems starting '''X''', you can look for errors in the /var/log/Xorg.0.log file, as well as in the console output of the virtual console from which '''X''' was started. <br />
<br />
Also, if using {{filename | /etc/X11/xorg.conf}}, inspect the config file:<br />
<br />
# nano /etc/X11/xorg.conf<br />
<br />
for the following issues:<br />
<br />
*The video driver may need to be specified. e.g.:<br />
Section &quot;Device&quot;<br />
<br />
...<br />
Driver &quot;savage&quot;<br />
...<br />
<br />
EndSection<br />
<br />
*Horizontal sync and vertical refresh specs under section &quot;Monitor&quot; may need to be added:<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 these specs are unknown, consult the documentation of the computer monitor.)<br />
<br />
*Color depth can be specified 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 desired Modes to the &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 />
<br />
*Add the following section, if eye candy which requires the composite extension is desired: <br />
Section &quot;Extensions&quot;<br />
Option &quot;Composite&quot; &quot;Enable&quot;<br />
EndSection<br />
<br />
Try the config again, after modifying, by running:<br />
# startx<br />
or<br />
# xinit -- /usr/bin/X -nolisten tcp<br />
'''''Still having trouble? Detailed instructions are in the [[Xorg]] article.'''''<br />
<br />
======Need Help?======<br />
<br />
If you are still having trouble after consulting the [[Xorg]] article and need assistance via the Arch forums, be sure to install and use wgetpaste:<br />
<br />
# pacman -S wgetpaste<br />
Use wgetpaste and provide links for the following files when asking for help in your forum post:<br />
* ~/.xinitrc<br />
* /etc/X11/xorg.conf<br />
* /var/log/Xorg.0.log<br />
* /var/log/Xorg.0.log.old<br />
Use wgetpaste like so:<br />
$ wgetpaste </path/to/file><br />
Post the corresponding links given within your forum post. Be sure to provide appropriate hardware and driver information as well.<br />
{{Warning| '''''It is very important to provide detail when troubleshooting X. Please provide all pertinent information as detailed above when asking for assistance on the Arch forums. '''''}}<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 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 WMs include: [[#Openbox|'''Openbox''']], [[#Fluxbox|'''Fluxbox''']], [[#FVWM2|'''FVWM2''']], [[PekWM|'''pekwm''']], [[Evilwm|'''evilwm''']], '''Windowmaker, and TWM'''.<br />
* If you need something completely different, try a tiling WM like [[Awesome|'''awesome''']], [[Ion3|'''ion3''']], [[Wmii|'''wmii''']], [[Dwm|'''dwm''']], [[Xmonad|'''xmonad''']], or [[Ratpoison|'''ratpoison''']].<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 is a set of high quality, general-purpose fonts. You may also want to install the Microsoft font sets, which are especially popular on websites, and may be required for the proper function of Flash animations which feature text.<br />
<br />
Install with:<br />
# pacman -S ttf-dejavu ttf-ms-fonts<br />
<br />
Refer to [[Font Configuration]] for how to configure fonts.<br />
<br />
===Step 2: Install a Desktop Environment===<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 />
* [[#Tiling WMs|'''Tiling WMs''']]<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 the base GNOME environment with:<br />
# pacman -S gnome<br />
<br />
Additionally, you can install the extras and system tools:<br />
# pacman -S gnome-extra gnome-system-tools<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. <br />
<br />
Some users prefer to use the '''hal''' daemon. The '''hal''' daemon, among other things, will assist in automating the mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The hal package is installed as a dependency along with GNOME, but must be invoked to become useful.<br />
<br />
{{Warning|The FAM (File Alteration Monitor) daemon is obsolete; use [[Gamin]] instead, if possible. Gamin is a re-implementation of the FAM specification. It is newer, more actively maintained, and simpler to utilize:<br />
<br />
# pacman -S gamin<br />
Go ahead and remove fam when prompted.<br />
}}<br />
<br />
You may want to install a graphical login manager. For GNOME, '''gdm''' is a good choice. <br />
{{Note|'''gdm''' is in the gnome-extra group; if you have installed that already, this step is not necessary.}}<br />
<br />
As root:<br />
# pacman -S gdm<br />
<br />
Start hal:<br />
# /etc/rc.d/hal start<br />
Add the desired daemons to your /etc/rc.conf DAEMONS section, so they will be invoked at boot (Note that gamin is ''not'' to be added to the DAEMONS array):<br />
# nano /etc/rc.conf<br />
<br />
DAEMONS=(syslog-ng '''dbus hal gdm''' network crond alsa)<br />
{{Note|dbus and hal '''must''' precede network daemons (e.g. network or networkmanager) to avoid seeing harmless errors during boot or shutdown.}}<br />
{{Tip|If you prefer to log into the console and manually start X, exclude the gdm daemon.}}<br />
{{Note | HAL relies on and will automatically start dbus. However, some users have reported a failure with networkmanager unless dbus is implicitly specified in the DAEMONS array. When adding dbus to the array, ensure it directly precedes HAL. }}<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 />
{{Tip|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 '''[[General Recommendations]]''', or the rest of the information below.<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 />
Optional for more themes:<br />
# pacman -S murrine-themes-collection <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 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 />
But how do i get those really cool desktop effects I've been seeing on youtube? See [[Compiz]]. :)<br />
<br />
===== Further Customization=====<br />
See the [http://wiki.archlinux.org/index.php/Gnome Gnome ArchWiki page] for useful details like adding [http://wiki.archlinux.org/index.php/Gnome#If_you_want_to_enable_passwordless_login_in_gnome_.28bypass_the_password_promp_in_GDM.29: passwordless login] features for selected users and other useful information.<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 <tt>UNIX</tt> workstations. It combines ease of use, contemporary functionality, and outstanding graphical design with the technological superiority of <tt>UNIX</tt>-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.x residing under the Arch [extra] repo.<br />
<br />
Install base kde:<br />
# pacman -S kdebase-workspace<br />
Install the whole Desktop Environment: <br />
# pacman -S kde<br />
''or'' <br />
# pacman -S kde-meta<br />
<br />
{{note | Learn about the difference between '''kde''' and '''kde-meta''' packages in the [[KDE_Packages|KDE Packages]] article.}} <br />
<br />
2. Alternatively, another KDE project exists called '''KDEmod''', part of the Chakra distribution. It is an Arch Linux (and spinoff) exclusive, community-driven package set 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 repositories to /etc/pacman.conf. The project website, including complete installation instructions, can be found at [http://www.chakra-project.org/ http://www.chakra-project.org/]. <br />
{{Note|[http://chakra-project.org/news/index.php?/archives/79-End-of-the-road-in-sight-for-KDEmod.html Support to KDEmod will end soon].}}<br />
<br />
[[Gamin]], an extension of the file alteration monitor (fam) project, is more actively developed than '''fam''', and will be useful for reflecting real-time changes in the filesystem. <br />
<br />
Install with:<br />
<br />
# pacman -S gamin<br />
<br />
=====Useful KDE DAEMONS=====<br />
<br />
Recall from above that a daemon is a program that runs in the background, waiting for events to occur and offering services.<br />
<br />
KDE will require the '''hal''' ('''H'''ardware '''A'''bstraction '''L'''ayer) daemon for optimal functionality. The hal daemon, among other things, will facilitate the automatic mounting of disks, optical drives, and USB drives/thumbdrives for use in the GUI. The hal package is installed as a dependency along with KDE, but must be invoked to become useful.<br />
<br />
The '''kdm''' daemon is the '''K''' '''D'''isplay '''M'''anager, which provides a '''graphical login''', if desired.<br />
<br />
-----<br />
<br />
Start hal:<br />
# /etc/rc.d/hal start<br />
<br />
{{Note|HAL relies on and will automatically start dbus. However, some users have reported a failure with NetworkManager unless dbus is implicitly specified in the DAEMONS array. When adding dbus to the array, ensure it directly precedes HAL.}}<br />
Edit your DAEMONS array in /etc/rc.conf:<br />
# nano /etc/rc.conf<br />
Add '''dbus''' and '''hal''' to your DAEMONS array, to invoke it on boot. If you prefer a graphical login, add '''kdm''' as well:<br />
DAEMONS=(syslog-ng '''dbus hal''' networkmanager alsa crond '''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 [[Display Manager]] 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 />
{{Tip|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 '''[[General Recommendations]]''', or the rest of the information below.<br />
<br />
=====Eye candy=====<br />
Arch KDE themes can be installed:<br />
# pacman -S archlinux-themes-kde<br />
<br />
But how do i get those really cool desktop effects I've been seeing on youtube? See [[Compiz]]. :)<br />
<br />
====Xfce====<br />
=====About Xfce=====<br />
Xfce is another free software desktop environment for Linux. It aims to be fast and lightweight, while still being visually appealing and easy to use. Xfce is modular and reusable. It consists of separately packaged components that together provide the full functionality of the desktop environment, but which can be selected in subsets to create the user's preferred personal working environment. Xfce is mainly used for its ability to run a modern desktop environment on relatively modest hardware. It is based on the GTK+ 2 toolkit (the same as GNOME). It uses the Xfwm window manager, described below. Its configuration is entirely mouse-driven, and the configuration files are hidden from the casual user.<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 murrine-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. If you don't want '''xfce4-xfapplet-plugin''' to be installed, install xfce4-goodies this way:<br />
# pacman -S murrine-themes-collection $(pacman -Sgq xfce4-goodies | egrep -v xfce4-xfapplet-plugin) <br />
To install the standard menu icons:<br />
# pacman -S gnome-icon-theme<br />
<br />
If you get errors about dbus-launch then you need to install dbus aswell:<br />
# pacman -S dbus<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 hal package is installed when you install Xfce, but must be invoked to become useful.<br />
<br />
{{Note|'''fam''' (the file alteration monitor) is now obsolete. Install the [[gamin]] package but do not add gamin to rc.conf. gamin is automatically configured to run in the background by default.}}<br />
# pacman -S gamin<br />
Ensure hal is installed:<br />
# pacman -Q hal<br />
Start the hal daemon:<br />
<br />
# /etc/rc.d/hal start<br />
<br />
{{Note|HAL relies on and will automatically start dbus. However, some users have reported a failure with NetworkManager unless dbus is implicitly specified in the DAEMONS array. When adding dbus to the array, ensure it directly precedes HAL.}}<br />
Edit your DAEMONS array in /etc/rc.conf:<br />
# nano /etc/rc.conf<br />
Add '''hal''' to your DAEMONS array, to invoke at boot.<br />
<br />
{{Tip|Advanced instructions for installing and configuring Xfce can be found in the [[Xfce]] article.}}<br />
<br />
If you wish to install one, see [[Display Manager]]. 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 wish to continue by viewing '''[[General Recommendations]]''', or the rest of the information below.<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 />
=====Installation=====<br />
Install LXDE with: <br />
# pacman -S lxde gamin<br />
<br />
[[Gamin]] is a file and directory monitoring tool designed to be a subset of the [[FAM]]. It runs on demand for programs that have support for it so does not require a daemon like fam does.<br />
<br />
Add:<br />
exec startlxde<br />
to your ~/.xinitrc and start with ''startx'' or ''xinit''<br />
*If you experience problems with Policykit or plan on running '''nm-applet''', the following command should be used instead<br />
exec ck-launch-session startlxde<br />
<br />
{{Tip | Further information available at the [[LXDE]] wiki article.}}<br />
<br />
Congratulations! Welcome to your LXDE desktop environment on your new Arch Linux system! You may wish to continue by viewing '''[[General Recommendations]]''', or the rest of the information below.<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 />
<br />
NOTE: If you plan on running dbus (which is required by hal) then make sure your ~/.xinitrc reads:<br />
<br />
exec dbus-launch --exit-with-session openbox-session<br />
<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, Tint2, 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 />
{{Tip | More information is available in the [[Openbox]] article.}}<br />
<br />
====FVWM2====<br />
FVWM (F Virtual Window Manager) 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 />
It will install the official version of the WM. However, if you want/need to use some more features than it provides, you can install the patched version from the [[AUR]] (see package [http://aur.archlinux.org/packages.php?ID=7195 fvwm-patched]) or from archlinuxfr (see [[Unofficial user repositories]]) using pacman:<br />
# pacman -S fvwm-patched<br />
<br />
fvwm will automatically be listed in kdm/gdm in the sessions menu. Otherwise, add <br />
exec fvwm2 <br />
<br />
to your user's .xinitrc.<br />
<br />
When you start [[FVWM2]], you will get into the blank configuration. However, when you left-click on the desktop, you will be able to select to configure FVWM. chose wanted modules and you are ready to go. Check out the configs in the http://www.box-look.org. One should also consider checking FVWM forums at http://www.fvwmforums.org<br />
<br />
[[SLiM]] is a very good login manager, that does not have many dependencies and acts well with FVWM. Common Applications are similar to those suggested for [[Openbox]] or [[Fluxbox]].<br />
<br />
====Tiling WMs====<br />
<br />
In addition to floating window managers, there are also several tiling window managers available. This type of window manager may be described as making more extensive usage of the keyboard, less (or no) reliance on the mouse, and window control via predefined layouts. Windows are usually resized and positioned so that they would not overlap, potentially maximizing space.<br />
<br />
Here are some of the more popular tiling WMs, in alphabetical order:<br />
* [[Awesome]]<br />
* [[dwm]]<br />
* [[Musca]]<br />
* [[wmii]]<br />
* [[Xmonad]]<br />
<br />
More information can be found in the [[Comparison of Tiling Window Managers]] article.<br />
<br />
===Step 3: Methods for starting your Desktop Environment===<br />
<br />
====A: Manually====<br />
You might prefer to start X manually from your terminal rather than booting straight into the desktop (if not, skip to [[Beginner's Guide#B: Automatically|B: Automatically]]). There are three methods for starting X manually. Choose the one that suits you best:<br />
<br />
=====Method 1: DE-specific commands=====<br />
For some users, this method might be the easiest since you need only enter a command without any configuring.<br />
Simply use a command to launch your WM/DE.<br />
You may always start your desktop environment with '''xinit''' or '''startx''', followed by the path to your DE's script:<br />
<br />
$ xinit /usr/bin/gnome-session<br />
or<br />
$ startx /usr/bin/startkde<br />
<br />
from the shell prompt. Note that such a command does not finish until you logout of the DE.<br />
{{Note|If you do '''xinit gnome-session''' instead of '''xinit /usr/bin/gnome-session''', then you will have problems on your desktop. Always include the complete path (/usr/bin/)}}<br />
<br />
Optionally, you can make an [[Bashrc#Aliases|alias]] in /etc/bash.bashrc so you don't have to type the whole command.<br />
...<br />
alias gnome="xinit /usr/bin/gnome-session"<br />
...<br />
<br />
Alternatively, if you wish to launch a Display Manager (AKA login manager) rather than go directly into your desktop, you can use the command for your installed Display Manager. For example, for gnome:<br />
$ gdm<br />
or KDE:<br />
$ kdm<br />
etc...<br />
Have fun.<br />
<br />
=====Method 2: using runlevels=====<br />
By default, Linux is set up to have different [[runlevels]]. Arch boots into runlevel 3 by default. Runlevel 5 is typically used in Linux for loading X server.<br />
Edit the file /etc/inittab. In the last section at the bottom of the file, uncomment the appropriate line for your desktop environment's display manager. For example, for gnome it would look like this:<br />
# Example lines for starting a login manager<br />
#x:5:respawn:/usr/bin/xdm -nodaemon<br />
x:5:respawn:/usr/sbin/gdm -nodaemon<br />
#x:5:respawn:/usr/bin/kdm -nodaemon<br />
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1<br />
<br />
Now, simply start your desktop environment, as root, with<br />
# init 5<br />
or, as a normal user, with<br />
$ sudo init 5<br />
<br />
Enjoy.<br />
<br />
=====Method 3: using .xinitrc=====<br />
This method involves the most configuring.<br />
<br />
First we need to configure ~/.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 />
<br />
{{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 />
The '''startx''' and '''xinit''' commands 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 />
<br />
# su - ''yourusername''<br />
<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 />
{{Note | This template file '''[[.xinitrc]]''' is available in the /etc/skel directory when the package '''xorg-xinit''' is installed.}}<br />
<br />
* Sample .xinitrc 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 uncomment the line that corresponds to your Desktop Environment. For example, if you use Gnome, it will look something like this:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
<br />
exec gnome-session<br />
# exec startkde<br />
# exec startxfce4<br />
# exec wmaker<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
# exec openbox-session<br />
# ...or the Window Manager of your choice<br />
# exec xterm<br />
For KDE uncomment:<br />
exec startkde<br />
For fluxbox:<br />
exec fluxbox<br />
etc...<br />
<br />
{{Note | ''Be sure to have only '''one''' uncommented '''exec''' line in ~/.xinitrc'' for now.}}<br />
<br />
Now we're ready to launch X. Start '''X''' as a '''normal, non-root''' user, with:<br />
<br />
$ startx<br />
or<br />
$ xinit<br />
<br />
Your desktop should open up now. You can test your keyboard and its layout in it. Try moving your mouse around and enjoy the view.<br />
<br />
If trouble with automounting is experienced, try using the following command in ~/.xinitrc instead. (Replace "startxfce4" with the command that is appropriate for your window manager/DE.)<br />
exec ck-launch-session startxfce4<br />
This will ensure the various environment variables are set correctly by starting a clean consolekit session. ConsoleKit is a framework for keeping track of the various users, sessions, and seats present on a system. It provides a mechanism for software to react to changes of any of these items or of any of the metadata associated with them. It works in conjunction with dbus, and other tools.<br />
<br />
====B: Automatically====<br />
Most users might prefer to have their desktop start automatically during boot instead of starting X manually. There are two methods for starting X automatically. Choose the one that suits you best:<br />
<br />
=====Method 1: using runlevels=====<br />
This method expands on Method 2 from the section above on starting X manually.<br />
<br />
By default, Linux is set up to have different [[runlevels]]. Arch boots into runlevel 3 by default. Runlevel 5 is typically used for loading X server.<br />
Edit the file /etc/inittab.<br />
In the first section, uncomment '''id:5:initdefault:''' so it looks like this:<br />
## Only one of the following two lines can be uncommented!<br />
# Boot to console<br />
#id:3:initdefault:<br />
# Boot to X11<br />
id:5:initdefault:<br />
This tells Arch to boot to runlevel 5 when you start your computer.<br />
<br />
In the last section at the bottom of the file, uncomment the appropriate line for your desktop environment's display manager. For example, for gnome it would look like this:<br />
# Example lines for starting a login manager<br />
#x:5:respawn:/usr/bin/xdm -nodaemon<br />
x:5:respawn:/usr/sbin/gdm -nodaemon<br />
#x:5:respawn:/usr/bin/kdm -nodaemon<br />
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1<br />
<br />
Now sit back and relax while your computer boots directly into your desktop environment when you turn it on.<br />
<br />
=====Method 2: using a daemon=====<br />
Simply add your display manager to your daemons array in /etc/rc.conf. For example, it would look like this for gnome:<br />
DAEMONS=(syslog-ng dbus hal '''gdm''' ...)<br />
You might try backgrounding your display manager so that other daemons continue loading while the display manager loads:<br />
DAEMONS=(syslog-ng dbus hal '''@kdm''' ...)<br />
Now sit back and relax while your computer boots directly into your desktop environment when you turn it on.<br />
<br />
==Multimedia==<br />
<br />
===Use 32bit programs on 64bit systems===<br />
<br />
On a 64bit system (Arch x86_64), some programs such as Skype do not exist for this architecture, but they can be installed by using the appropriate lib32. For this purpose has been created a repository that contains all the lib32 necessary for many programs to run on a 64-bit system. This deposit also contains programs such as '''wine''', '''skype''' and '''flashplugin'''.<br />
<br />
Edit the file {{filename|/etc/pacman.conf}} and adding the following string to the list of repositories:<br />
<br />
[multilib]<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
Then update the list with the command:<br />
<br />
# pacman -Syy<br />
<br />
{{note|The package ''flashplugins'' content in this repository is not native 64-bit systems, but is its 32bit version that uses ''nspluginwrapper'' to work. If you do not use this method you should consider the installation of open solutions like '''gnash''' or '''lightspark'''. The package lightspark be found on [[http://aur.archlinux.org/packages.php?O=0&K=lightspark AUR]].}}<br />
<br />
===Codecs, plugins and Java===<br />
Multimedia codecs, plugins and Java can be installed with the following:<br />
<br />
# pacman -S mplayer gecko-mediaplayer xine-lib xine-ui libdvdread libdvdcss alsa-oss flashplugin jre<br />
Ensure the legality of using libdvdcss in your region before installing.<br />
<br />
=Appendix=<br />
For a list of [[Common Applications]] and [[Lightweight Applications]], visit their respective articles. Also see [[General Recommendations]] for post installation tips.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Pm-utils&diff=119218
Pm-utils
2010-10-14T10:04:47Z
<p>Cantabile: /* Suspend/Hibernate as regular user */ Added UPower method</p>
<hr />
<div>[[Category:Power management (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|pm-utils}} {{DISPLAYTITLE:pm-utils}}<br />
<br />
'''pm-utils''' is the new suspend and powerstate setting framework. It is designed to replace such scripts as those provided by the <tt>powersave</tt> package.<br />
<br />
It is usually used by HAL to execute the various hacks needed to work around bugs in drivers and subsystems that are not yet aware of suspend. It is easily extensible by putting custom hooks into a directory, which can either be done by the system administrator or those hooks can be part of a package, especially if this package needs special attention during a system suspend or power state transition.<br />
<br />
A lesser known feature is one that mimmicks toggling done by [[Laptop Mode Tools]].<br />
<br />
Used in conjunction with the [[cpufrequtils]] package, notebook (and desktop) owners are provided with a complete power management suite.<br />
<br />
== Installation ==<br />
<br />
The <tt>pm-utils</tt> package is now available from the [http://www.archlinux.org/packages/search/?q=pm-utils Extra] repository:<br />
# pacman -S pm-utils<br />
<br />
{{note|If you run into issues when resuming video, it might be necessary to also sync <tt>vbetool</tt> from [extra].}}<br />
<br />
== Basic Configuration ==<br />
=== Hibernation (suspend2disk) ===<br />
In order for suspend2disk (hibernate) to work, we need to edit ''/boot/grub/menu.lst'' as root and add '''resume=/path/to/swap/drive''' (e.g. /dev/sda2) to the kernel options, for example:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 '''resume=/dev/sda2''' ro vga=0<br />
initrd /kernel26.img<br />
<br />
Raid swap example:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/md2 resume=/dev/md0 ro md=0,/dev/sda2,/dev/sdb2 md=2,/dev/sda5,/dev/sdb5 vga=773<br />
initrd /kernel26.img<br />
<br />
If you want to use the UUID of the device instead then use the following example. The UUID itself can by find out by using the blkid command as root.<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 cryptdevice=/dev/sda2:main root=/dev/mapper/main-root resume=/dev/disk/by-uuid/1d893194-b151-43cd-a89e-6f89bd8b9f99 ro<br />
initrd /kernel26.img<br />
<br />
<br />
When the machine is placed into hibernation, it will now move all data from RAM to the swap partition... you ''did'' make your swap partition large enough to hold your RAM data, right?<br />
<br />
Even if your swap partition is smaller than RAM, you still have a big chance in hibernating successfully. According to [http://www.mjmwired.net/kernel/Documentation/power/interface.txt kernel documentation], ''/sys/power/image_size controls the size of the image created by the suspend-to-disk mechanism'', which has a default value of 500M. ''The suspend-to-disk mechanism will do its best to ensure the image size will not exceed that number.'' You may either decrease it due to a small swap partition or increase it in purpose of possible hibernation speed up.<br />
<br />
'''Note: you may have to add the resume hook to mkinitcpio, see [[Pm-utils#Resume_Hook|below]]'''<br />
<br />
=== Suspend/Hibernate as regular user ===<br />
<br />
Three methods are available to suspend without the need for a root password: using HAL, using UPower, and giving the user permissions with visudo.<br />
<br />
==== UPower method ====<br />
<br />
To suspend to RAM:<br />
<br />
<pre><br />
$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" \<br />
/org/freedesktop/UPower org.freedesktop.UPower.Suspend<br />
</pre><br />
<br />
To suspend to disk (hibernate):<br />
<br />
<pre><br />
$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" \<br />
/org/freedesktop/UPower org.freedesktop.UPower.Hibernate<br />
</pre><br />
<br />
==== HAL Method ====<br />
<br />
HAL can be invoked as regular user to suspend by:<br />
<br />
<pre>$ dbus-send --system --print-reply --dest=org.freedesktop.Hal \<br />
/org/freedesktop/Hal/devices/computer \<br />
org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0</pre><br />
<br />
and Hibernate by:<br />
<br />
<pre>$ dbus-send --system --print-reply --dest=org.freedesktop.Hal \<br />
/org/freedesktop/Hal/devices/computer \<br />
org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate</pre><br />
<br />
==== User Permission Method ====<br />
<br />
Because the <tt>pm-utils</tt> scripts must be run as root, you may want to make the scripts accessible to normal users by running sudo without the root password. To do so, edit the {{Filename|/etc/sudoers}} file with {{Codeline|visudo}}, for example:<br />
<br />
# visudo<br />
<br />
add the following lines, replacing ''username'' with your own:<br />
<br />
''username'' ALL = NOPASSWD: /usr/sbin/pm-hibernate<br />
''username'' ALL = NOPASSWD: /usr/sbin/pm-suspend<br />
<br />
save and exit visudo<br />
<br />
Or you can enable it for a group, using the following lines, of course replacing ''group'':<br />
<br />
''%group'' ALL = NOPASSWD: /usr/sbin/pm-hibernate<br />
''%group'' ALL = NOPASSWD: /usr/sbin/pm-suspend<br />
<br />
Note: These must come after any user privilege specifications, e.g., "username ALL=(ALL) ALL", or they won't work.<br />
<br />
You can now run the scripts without a password by simply typing:<br />
<br />
$ sudo pm-hibernate<br />
<br />
or <br />
<br />
$ sudo pm-suspend<br />
<br />
Also, add yourself to the ''power'' group so that way using things like applets to do suspend will work. If you do not do this, when you try to use suspend though things like the gnome shutdown applet to suspend/hibernate your computer will just play a very annoying loud triple beep and lock the screen.<br />
<br />
# gpasswd -a ''username'' power<br />
<br />
You should now be able to use gnome power management tools (and kpowersave?) to automatically suspend/hibernate when doing things like closing the laptop lid, running low on battery power etc...<br />
<br />
=== Power Management ===<br />
Write a custom [[acpid]] event:<br />
{{File|name=/etc/acpi/events/ac|content=<br />
event=ac_adapter.*<br />
action=/etc/acpi/actions/ac.sh %e<br />
}}<br />
<br />
Write a custom acpid action:<br />
{{File|name=/etc/acpi/actions/ac.sh|content=<br />
#!/bin/sh<br />
case "$4" in<br />
*0) /usr/sbin/pm-powersave true;;<br />
*1) /usr/sbin/pm-powersave false;;<br />
esac<br />
}}<br />
<br />
Be sure not to install {{Package Official|laptop-mode-tools}} since the rules may conflict.<br />
<br />
== Advanced Configuration ==<br />
The main configuration file is '''<tt>/usr/lib/pm-utils/defaults</tt>'''. You ''should not edit this file'', since after a package update it might be overwritten with the default settings. Put your config file into '''<tt>/etc/pm/config.d/</tt>''' instead.<br />
You can just put a simple text file with<br />
SUSPEND_MODULES="button uhci_hcd"<br />
named "modules" or "config" into <tt>/etc/pm/config.d</tt> and it will override the settings in the system wide configuration file.<br />
<br />
=== Available Variables for use in config files ===<br />
SUSPEND_MODULES="button" # the list of modules to be unloaded before suspend<br />
SLEEP_MODULE="tuxonice uswsusp kernel" # The default sleep/wake systems to try<br />
HIBERNATE_MODE="shutdown" # forces the system to shutdown rather than reboot<br />
<br />
=== Disabling a hook ===<br />
If a hook is run which you do not like or which you think is not useful or even harmful, we'd appreciate a bugreport for that.<br />
You can however easily disable hooks by just creating an empty file corresponding to the hook in <tt>/etc/pm/sleep.d/</tt>. Say you want to disable the hook <tt>/usr/lib/pm-utils/sleep.d/45pcmcia</tt>, you can do this easily by calling<br />
# touch /etc/pm/sleep.d/45pcmcia<br />
Do not set the executable bit on that dummy-hook.<br />
<br />
=== Creating your own hooks ===<br />
If you want to do something specific to your setup during suspend / hibernate, then you can easily put your own hook into <tt>/etc/pm/sleep.d</tt>. The hooks in this directory will be called in alphabetic order during suspend (that's the reason their names all start with 2 digits, to make the ordering explicit) and in the reverse order during resume.<br />
<br />
I'm showing a pretty useless demonstration hook here, that will just put some informative lines into your logfile:<br />
<br />
#!/bin/bash<br />
case $1 in<br />
hibernate)<br />
echo "Hey guy, we are going to suspend to disk!"<br />
;;<br />
suspend)<br />
echo "Oh, this time we're doing a suspend to RAM. Cool!"<br />
;;<br />
thaw)<br />
echo "oh, suspend to disk is over, we are resuming..."<br />
;;<br />
resume)<br />
echo "hey, the suspend to RAM seems to be over..."<br />
;;<br />
*) echo "somebody is calling me totally wrong."<br />
;;<br />
esac<br />
<br />
Put this into /etc/pm/sleep.d/66dummy, do a <tt>chmod +x /etc/pm/sleep.d/66dummy</tt> and it will spew some useless lines during suspend / resume.<br />
<br />
'''''Warning:''' All the hooks run as user root. This means that you need to be careful when creating temporary files, check that the PATH variable is set correctly etc. to avoid security problems.''<br />
<br />
== How it Works ==<br />
The concept is quite easy: the main script (<tt>pm-action</tt>, called via symlinks as either <tt>pm-suspend</tt>, <tt>pm-hibernate</tt> or <tt>pm-suspend-hybrid</tt>) executes so-called "hooks", executable scripts, in the alphabetical sorted order with the parameter <tt>suspend</tt> (suspend to RAM) or <tt>hibernate</tt> (suspend to disk).<br />
Once all hooks are done, it puts the machine to sleep. After the machine has woken up again, all those hooks are executed in reverse order with the parameter <tt>resume</tt> (resume from RAM) or <tt>thaw</tt> (resume from disk).<br />
The hooks do various stuff, for example preparing the bootloader, stopping the bluetooth subsystem or unloading of critical modules.<br />
<br />
Both pm-suspend and pm-hibernate are usually called from HAL, initiated by desktop applets as gnome-power-manager or kpowersave.<br />
<br />
{{Box Note|<tt>suspend-hybrid</tt> is a placeholder right now, it is not completely implemented.}}<br />
<br />
There is also the possibility to set the machine into high-power and low-power mode, the command <tt>pm-powersave</tt> is used with an additional parameter of <tt>true</tt> or <tt>false</tt>. It works basically the same as the suspend framework.<br />
<br />
The hooks for suspend are placed in<br />
* <tt>/usr/lib/pm-utils/sleep.d</tt> (distribution / package provided hooks)<br />
* <tt>/etc/pm/sleep.d</tt> (hooks added by the system administrator)<br />
<br />
The hooks for the power state are placed in <br />
* <tt>/usr/lib/pm-utils/power.d</tt> (distribution / package provided hooks)<br />
* <tt>/etc/pm/power.d</tt> (hooks added by the system administrator)<br />
<br />
Hooks in <tt>/etc/pm/</tt> take precedence over those in <tt>/usr/lib/pm-utils/</tt>, so the system administrator can override the defaults provided by the distribution.<br />
<br />
== Troubleshooting ==<br />
If suspend or hibernate did not work correctly, you will probably find some information in the logfile '''<tt>/var/log/pm-suspend.log</tt>''', for example which hooks were run and what the output of them was.<br />
<br />
=== Resume Hook ===<br />
<br />
It has been suggested that some systems, including those using [[LVM]], require the <tt>resume</tt> hook be added to the initrd image, otherwise the kernel will '''not''' resume. To do so, edit <tt>/etc/mkinitcpio.conf</tt> as root and add <tt>resume</tt> to the HOOKS array:<br />
HOOKS="base udev autodetect ide scsi sata lvm2 '''''resume''''' filesystems "<br />
<br />
Note that this is an example, and your HOOKS array may look different.<br />
<br />
<tt>resume</tt> must be placed ''after'' 'ide', 'scsi', 'sata' and/or 'lvm2', but before 'filesystems'. Of course there has to be an appropriate 'resume' file in /lib/initcpio/hooks, it should already be there, as it is part of the package 'mkinitcpio'.<br />
<br />
Finally, you must rebuild the initrd image for these changes to take effect:<br />
<br />
# mkinitcpio -p kernel26<br />
<br />
{{Box Note|If you use a custom kernel then you might have to change the value of the '-p' option.}}<br />
<br />
=== Set UUID === <br />
<br />
If you experience segmentation faults that might result in an unresponsive system and missing keys then try to set the UUID in the resume-path in '''/boot/grub/menu.lst''' as explained [[http://wiki.archlinux.org/index.php/Pm-utils#Hibernation_.28suspend2disk.29 above]].<br />
<br />
== Tips and Tricks / FAQ ==<br />
=== Triggering suspend manually ===<br />
If you want to trigger suspend manually for debugging, without using HAL and other frameworks, call '''<tt>pm-suspend</tt>''' or '''<tt>pm-hibernate</tt>''' as root.<br />
=== Automatically deactivate kwin compositing before suspend===<br />
<br />
at the moment pm-suspend fails to resume with garbled screen when you resume from suspend with active AIGLX clients, such as kwin compositing (only ati-catalyst?).<br />
To automatically deactivate kwin compositing add a new hook under /etc/pm/sleep.d/00togglecompositing with this content:<br />
<br />
#!/bin/bash<br />
USER=`finger|grep '*:0'|grep -o '^\w*'`<br />
DBUS_SESSION_BUS_ADDRESS=`grep -o 'DBUS_SESSION_BUS_ADDRESS=.*' /home/$USER/.dbus/session-bus/*|sed s/DBUS_SESSION_BUS_ADDRESS=//`<br />
case $1 in<br />
hibernate)<br />
;;<br />
suspend)<br />
if `sudo -u $USER -i DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS qdbus org.kde.kwin /KWin compositingActive`;<br />
then<br />
sudo -u $USER -i DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS qdbus org.kde.kwin /KWin toggleCompositing;<br />
sleep 1<br />
fi<br />
;;<br />
thaw)<br />
;;<br />
resume)<br />
sudo -u $USER -i DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS qdbus org.kde.kwin /KWin toggleCompositing;<br />
;;<br />
*) echo "somebody is calling me totally wrong."<br />
;;<br />
esac<br />
<br />
I don't know if it's very secure or if it can be done simpler. Feel free to add better versions.<br />
<br />
If you are having trouble getting the above script to work, you can try my version. This version removes the use of finger, and fixes the DBUS_SESSION_BUS_ADDRESS resolution which did not work for me (though my solution is admittedly quite dirty). Simply replace the first three lines with:<br />
<br />
#!/bin/bash<br />
USER=`who | grep ':0' | grep -o '^\w*' | head -n1`<br />
. /home/$USER/.dbus/session-bus/*<br />
<br />
=== Using another sleep backend (like uswsusp) ===<br />
Create a file with a SLEEP_MODULE variable, like this:<br />
$ cat /etc/pm/config.d/module <br />
SLEEP_MODULE=uswsusp<br />
I don't know but you may have to <code>chmod +x</code> it. To list available modules, use:<br />
$ pacman -Ql pm-utils | grep module.d<br />
<br />
=== Having the hd power management level automatically set again on resume ===<br />
Do it like this:<br />
$ cat /etc/pm/sleep.d/50-hdparm_pm <br />
#!/bin/dash<br />
<br />
if [ -n "$1" ] && ([ "$1" = "resume" ] || [ "$1" = "thaw" ]); then<br />
hdparm -B 254 /dev/sda > /dev/null<br />
fi<br />
<br />
=== Restarting the mouse ===<br />
On some laptops the mouse will hang after an otherwise successful suspend. One way to remedy this is to force a reinit of the PS/2 driver (here <tt>i8042</tt>) through a hook in <tt>/etc/pm/hooks</tt> (see [[#Creating_your_own_hooks|hooks]])<br />
<br />
#!/bin/sh <br />
echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind<br />
echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind<br />
<br />
=== It seems to not do anything / where is the logfile ===<br />
If it seem to not do anything when called via the desktop applets, then try to call <tt>pm-suspend</tt> or <tt>pm-hibernate</tt> [[#Triggering_suspend_manually|manually from a root shell in a terminal]]. Maybe you'll already get some output that will point you to the problem.<br />
The suspend scripts also write a [[#Troubleshooting|logfile at '''<tt>/var/log/pm-suspend.log</tt>''']].<br />
<br />
=== Add sleep modes to Openbox menu ===<br />
Openbox users can add the new scripts as additional shutdown options within the Openbox menu by adding the items to a new or existing sub-menu in <tt>~/.config/openbox/menu.xml</tt>, for example:<br />
<menu id="64" label="Shutdown"><br />
<item label="Lock"> <action name="Execute"> <execute>xscreensaver-command -lock</execute> </action> </item><br />
<item label="Logout"> <action name="Exit"/> </item><br />
<item label="Reboot"> <action name="Execute"> <execute>sudo shutdown -r now</execute> </action> </item><br />
<item label="Poweroff"> <action name="Execute"> <execute>sudo shutdown -h now </execute> </action> </item><br />
'''''<item label="Hibernate"> <action name="Execute"> <execute>sudo pm-hibernate</execute> </action> </item>'''''<br />
'''''<item label="Suspend"> <action name="Execute"> <execute>sudo pm-suspend</execute> </action> </item>'''''<br />
</menu><br />
<br />
=== Blank screen issue ===<br />
Some users have reported having issues with their laptops not resuming after a suspend or hibernate. This is due to the autodetect HOOK. This can be disabled using the same method for adding the resume HOOK. Just remove autodetect from the list and follow the steps to build the new image. See [http://wiki.archlinux.org/index.php/Pm-utils#Resume_Hook Resume Hook] for more details on building the new image.<br />
<br />
=== Handling "sleep" and "power" buttons ===<br />
"Sleep" and "power" buttons are handled by acpid in /etc/acpi/handler.sh (see "button/power" and "power/sleep" entries). You may want to substitute the default actions with calls to pm-suspend and pm-hibernate.<br />
<br />
=== [[HAL]] will not recognize new devices on resume ===<br />
With the 2.6.30 kernel, HAL will on some systems bug on resume, not recognizing new USB devices. Adding the following bash script with a name like "02hal" to /etc/pm/sleep.d works around the problem by stopping HAL and starting it again after resuming.<br />
<br />
#!/bin/bash<br />
case $1 in<br />
hibernate)<br />
;;<br />
suspend)<br />
/etc/rc.d/hal stop<br />
;;<br />
thaw)<br />
;;<br />
resume)<br />
/etc/rc.d/hal start<br />
;;<br />
*)<br />
;;<br />
esac<br />
<br />
Remember to mark it executable with "chmod +x 02hal".<br />
<br />
== Other Resources ==<br />
* [https://wiki.ubuntu.com/UnderstandingSuspend Understanding Suspend] - Ubuntu article explaining how suspend-to-ram works<br />
*[[Cpufrequtils]] - CPU Frequency Scaling and CPU Power schemes<br/><br />
*[[SpeedStep]] - More information on CPU frequency scaling (some of which is obsolete)<br/><br />
*[[Acpid]] - daemon for delivering ACPI events.<br />
<br />
== Credits ==<br />
''This wiki entry was originally sourced from the [http://en.opensuse.org/Pm-utils OpenSUSE Wiki] (Licensed under GPL). A big thank you goes to the <tt>pm-utils</tt> developers and documenters for their time.''</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Lightweight_Applications&diff=118752
Lightweight Applications
2010-10-06T12:10:34Z
<p>Cantabile: /* Audio Players */ removed duplicate deadbeef entry</p>
<hr />
<div>[[Category:Other desktop user's resources (English)]][[Category:General (English)]]<br />
{{i18n|Lightweight Applications}}<br />
<br />
Provides a list of lightweight software for those who wish to use programs that require less computer resources.<br />
<br />
==Internet==<br />
===Browsers===<br />
<br />
{{App|[[Wikipedia:Abaco (web browser)|Abaco]]|A multi-page graphical web browser|http://lab-fgb.com/abaco/|{{Package AUR|abaco}}}}<br />
{{App|[[Wikipedia:Arora (browser)|Arora]]|A cross platform web browser built using Qt and WebKit|http://code.google.com/p/arora/|{{Package Official|arora}}}}<br />
{{App|[[Wikipedia:Chromium (web browser)|Chromium]]|The middleweight, open-source project behind Google Chrome|http://code.google.com/chromium/|{{Package Official|chromium}}}}<br />
{{App|[[Wikipedia:Conkeror|Conkeror]]|A highly programmable web browser based on Mozilla XULRunner|http://conkeror.org/|{{Package Official|conkeror}}}}<br />
{{App|[[Wikipedia:Dillo|Dillo]]|A small, fast graphical web browser built on FLTK|http://www.dillo.org/|{{Package Official|dillo}}}}<br />
{{App|[[Wikipedia:ELinks|ELinks]]|An advanced and well-established feature-rich text mode web browser|http://elinks.or.cz/|{{Package Official|elinks}}}}<br />
{{App|Hv3|A minimalist web browser based on tkhtml3|http://tkhtml.tcl.tk/hv3.html|{{Package AUR|hv3}}}}<br />
[http://pwmt.org/projects/jumanji jumanji] - "a highly customizable and functional web browser"<br />
<br />
{{App|[[Wikipedia:Kazehakase|Kazehakase]]|GTK+ web browser that uses the Gecko rendering engine|http://kazehakase.sourceforge.jp/|{{Package Official|kazehakase}}}}<br />
{{App|[[Wikipedia:Links (web browser)|Links]]|A text WWW browser, similar to Lynx|http://links.twibright.com/|{{Package Official|links}}}}<br />
<br />
[http://luakit.org/projects/luakit/ Luakit] is a highly configurable, micro-browser framework based on the WebKit web content engine and the GTK+ toolkit. It is very fast, extensible by Lua and licensed under the GNU GPLv3 license.<br />
<br />
[http://www.twotoasts.de/index.php?/pages/midori_summary.html Midori] is a lightweight web browser based on Gtk and WebKit. It passes the ACID3 test (midori-git/AUR).<br />
<br />
[http://www.netsurf-browser.org Netsurf] is a featherweight browser written in C. Notable is its lack of JavaScript support and fast rendering through its own custom rendering engine.<br />
<br />
[http://aur.archlinux.org/packages.php?ID=37037 Sb] - A very lightweight webkit-based browser that uses keybindings to perform most things the URL bar would usually do.<br />
<br />
[http://surf.suckless.org surf] is another lightweight WebKit-based browser, which follows the [[suck less philosophy|suckless ideology]]. Which means, the software is even more lightweight (basically, the browser itself is a single C source file).<br />
<br />
[[Uzbl]] - "web interface tools which adhere to the unix philosophy."<br />
<br />
===Email Clients===<br />
<br />
[[alpine]] is another powerful, and user-friendly text-based mail and news client.<br />
<br />
[[mutt]] is a small but very powerful text-based mail client.<br />
<br />
[http://sylpheed.sraoss.jp/en/ Sylpheed] is a simple, lightweight but featureful, and easy-to-use GTK based e-mail client.<br />
<br />
[http://www.claws-mail.org/ Claws] is a user-friendly, lightweight, and fast GTK based email client.<br />
<br />
[[sup]] is yet another powerful, text-based mail client; it is still under development.<br />
<br />
===Instant Messengers===<br />
<br />
[[Bitlbee]] is a way to use other IM to your [[#IRC]] client.<br />
<br />
[http://funpidgin.sourceforge.net/ Carrier] is a fork of Pidgin with more options.<br />
<br />
[http://www.centerim.org Centerim] is a curses based fork of Centericq which supports several protocols.<br />
<br />
[http://www.emesene.org/ emesene] is a Python/GTK+ instant messenger for the Windows Live Messenger network.<br />
<br />
[http://developer.pidgin.im/wiki/Using%20Finch Finch] is a curses based version of Pidgin.<br />
<br />
[[Pidgin]] is a multiprotocol instant messenger.<br />
<br />
[http://pidgin.im Pidgin Light] is a light Pidgin version without gstreamer, tcl, tk, xscreensaver support.<br />
<br />
===IRC===<br />
<br />
[http://nenolod.net/ Conspire] Lightweight, simple, and powerful.<br />
<br />
[[Irssi]] is a modular text mode IRC client with Perl scripting.<br />
<br />
[http://tools.suckless.org/ii II] Ultimate lightweight, literally `tail -f` the convo and `echo` back your replies.<br />
<br />
[http://www.ueber.net/code/r/ircfs ircfs] is a file system interface to irc written in [http://limbo.cat-v.org Limbo].<br />
<br />
[http://lostirc.sourceforge.net LostIRC] is a simple IRC client.<br />
<br />
[http://www.scrollz.com ScrollZ] is an advanced IRC client based on ircII.<br />
<br />
[http://weechat.org/ WeeChat] is a fast, light & extensible curses-based IRC client.<br />
<br />
[http://xchat.org XChat] is a GTK+ X client with Perl and Python scripting support.<br />
<br />
[http://bitbucket.org/emg/pcw pcw] is a frontend for [http://tools.suckless.org/ii ii] that opens a new terminal for each channel (depends on [http://bitbucket.org/emg/srw srw] by default)<br />
<br />
===Torrents===<br />
{{App|[[aria2]]|Command-line download manager that supports HTTP/HTTPS, FTP, BitTorrent and MetaLink protocols|http://aria2.sourceforge.net/|{{Package Official|aria2}}}}<br />
{{App|[[Wikipedia:Deluge_(software)|Deluge]]|PyGTK torrent client with daemon, webgui, and many other functionalities. I recommend Deluge-GIT from the AUR as it has many vital bugfixes.|http://deluge-torrent.org/|{{Package Official|deluge}}}}<br />
{{App|[[Wikipedia:QBittorrent|qBittorrent]]|The closest open source (GNU GPL v2 license) equivalent to µtorrent|http://qbittorrent.sourceforge.net/|{{Package Official|qbittorrent}}}}<br />
{{App|[[Wikipedia:RTorrent|rTorrent]]|Simple and lightweight ncurses BitTorrent client|http://libtorrent.rakshasa.no/|{{Package Official|rtorrent}}}}<br />
{{App|[[Wikipedia:Transmission (BitTorrent client)|Transmission]]|Simple and easy-to-use BitTorrent client with (GTK+) GUI and CLI front-ends|http://www.transmissionbt.com/|{{Package Official|transmission}}}}<br />
<br />
===News Aggregators===<br />
[[Canto]] - A ncurses RSS aggregator http://codezen.org/canto/<br />
<br />
[[Gnus]] - mail, nntp, rss client for Emacs.<br />
<br />
[[Newsbeuter]] - A ncurses RSS aggregator with layout and keybinding similar to mutt. Does not use the traditional 3 panes setup.<br />
<br />
[[Rawdog]] - An "RSS Aggregator Without Delusions Of Grandeur" that parses RSS/CDF/Atom feeds into a static HTML page of articles in date order http://offog.org/code/rawdog.html<br />
<br />
[[Snownews]] - Text mode RSS newsreader.<br />
<br />
==Multimedia==<br />
<br />
===Audio Players===<br />
<br />
[http://ario-player.sourceforge.net/ Ario] is very feature-rich GTK2 client for [[mpd]], inspired by Rhythmbox<br />
<br />
[http://cmus.sourceforge.net/ C* Music Player] is a very feature-rich ncurses-based music player.<br />
<br />
[http://deadbeef.sourceforge.net/ Deadbeef] is a light and fast music player with many features, no GNOME or KDE dependencies, supports console-only and as well GTK2-gui, comes with many plugins, and has a metadata editor. <br />
<br />
[http://sourceforge.net/projects/cplay/ cplay] is a curses front-end for various audio players.<br />
<br />
[http://code.google.com/p/gogglesmm/ Goggles Music Manager] is a music collection manager and player that automatically categorizes your music, supports gapless playback, features easy tag editing, and internet radio support.<br />
<br />
[http://aur.archlinux.org/packages.php?ID=11623 Herrie] is a minimalistic console-based music player with native AudioScrobbler support.<br />
<br />
[http://moc.daper.net/ MOC (Music On Console)] is an ncurses console audio player with support for the MP3, Ogg, and WAV formats.<br />
<br />
[http://hem.bredband.net/kaw/ncmpc/ ncmpc] is a curses client for [[mpd]].<br />
<br />
[http://unkart.ovh.org/ncmpcpp/ ncmpcpp] is an almost exact clone of ncmpc with some new features.<br />
<br />
[http://pragha.wikispaces.com/ Pragha] is a GTK+ music manager that was a fork of Consonance Music Manager.<br />
<br />
[http://www.archlinux.org/packages/community/i686/qmpdclient/ QmpdClient] is Qt4 based mpd client.<br />
<br />
[http://sonata.berlios.de/ Sonata] is an elegant GTK+ music client for [[mpd]].<br />
<br />
[http://www.mpg123.de/ mpg123] A fast free MP3 console audio player for Linux, FreeBSD, Solaris, Hpux and near all other UNIX systems. Also decodes mp1 and mp2 files.<br />
<br />
===Image Editors===<br />
<br />
[http://mtpaint.sourceforge.net/ mtPaint] is a graphic editing program geared towards creating indexed palette images and pixel art.<br />
<br />
===Image Viewers===<br />
<br />
[http://linuxbrit.co.uk/feh/ Feh] is a fast, lightweight image viewer that uses imlib2.<br />
<br />
[http://lxde.sourceforge.net/gpicview/ GPicView] is a simple and fast image viewer for X. Made by the developers of [[LXDE]]<br />
<br />
[http://gqview.sourceforge.net/ GQview] is an image browser that features single click access to view images and move around the directory tree.<br />
<br />
[http://geeqie.sourceforge.net/ Geeqie] is an image browser/viewer fork of GQview. Adds additional functionality such as support for RAW files.<br />
<br />
{{App|Mirage|PyGTK image viewer featuring support for crop and resize, custom actions and a thumbnail pane.|http://mirageiv.berlios.de|{{Package Official|mirage}}}}<br />
<br />
[http://goodies.xfce.org/projects/applications/ristretto Ristretto] is a fast and lightweight picture-viewer for the Xfce desktop environment.<br />
<br />
[http://spiegl.de/qiv/ QIV] (Quick Image Viewer) is a very small and fast gdk/Imlib image viewer.<br />
<br />
{{App|Viewnior|Minimalistic GTK2 viewer featuring support for flip, rotate, animations and configurable mouse actions|http://xsisqox.github.com/Viewnior/about.html|{{Package Official|viewnior}}}}<br />
<br />
[http://web.archive.org/web/19981207030422/http://world.std.com/~jimf/xloadimage.html Xloadimage] is the classic X image viewer.<br />
<br />
===Video Players===<br />
<br />
[http://kdekorte.googlepages.com/gnomemplayer Gnome-Mplayer] is a simple GTK-based GUI for [[mplayer]] without GNOME dependencies<br />
<br />
[[mplayer]] and [[mencoder]] support a complete and versatile array of video/audio formats.<br />
<br />
[http://smplayer.sourceforge.net/ SMPlayer] is a middleweight QT frontend for mplayer with additional patches.<br />
<br />
[http://www.videolan.org/vlc/ VLC] is a a middleweight video player with support for a wide variety of audio/video formats.<br />
<br />
==Office==<br />
<br />
===Calendars===<br />
<br />
[http://palcal.sourceforge.net/ Pal] is a very lightweight calendar with both interactive and non-interactive interfaces.<br />
<br />
[http://culot.org/calcurse/ Calcurse] is a text-based curses calendar and scheduling system.<br />
<br />
[http://www.roaringpenguin.com/products/remind Remind] is a highly sophisticated text-based calendaring and notification system.<br />
<br />
[http://pessimization.com/software/wyrd/ Wyrd] is an curses front-end to Remind.<br />
<br />
[http://www.duke.edu/~dgraham/wxRemind/ wxRemind] is a Python text and graphical frontend to Remind.<br />
<br />
===PDF Tools===<br />
<br />
[http://code.google.com/p/apvlv/ apvlv] is a lightweight PDF viewer with VIM key bindings.<br />
<br />
[http://www.emma-soft.com/projects/epdfview/ ePDFView] is a free lightweight PDF document viewer using Poppler and GTK+ libraries.<br />
<br />
[http://ccxvii.net/mupdf/ MuPDF] is very fast PDF viewer and toolkit written in portable C. Features CJK font support.<br />
<br />
[http://www.foolabs.com/xpdf/ Xpdf] is a viewer for Portable Document Format (PDF) files.<br />
<br />
[http://zathura.pwmt.org/projects/zathura zathura] is another lightweight PDF viewer similar to apvlv, only lighter<br />
<br />
===Text Editors===<br />
<br />
[http://acme.cat-v.org Acme] a minimalist and flexible programming environment by Rob Pike.<br />
<br />
[http://www.nongnu.org/beaver/ Beaver] is an Early AdVanced EditoR.<br />
<br />
[http://www.geany.org Geany] is a text editor using the GTK+ 2 toolkit with basic features of an integrated development environment.<br />
<br />
[http://tarot.freeshell.org/leafpad/ Leafpad] is a notepad clone for GTK+ 2.x that emphasizes simplicity.<br />
<br />
[http://mooedit.sourceforge.net/ medit] is a lightweight IDE text editor featuring support for tabs, sessions, plugins and syntax highlighting.<br />
<br />
[http://www.xfce.org/projects/mousepad/ Mousepad] is a simple text editor for Xfce based on Leafpad.<br />
<br />
[[nano]] is a console text editor based on pico with on-screen key binding help.<br />
<br />
[http://pyroom.org/ PyRoom] is a great distractionless PyGTK text editor, a clone of the infamous WriteRoom<br />
<br />
[http://sam.cat-v.org Sam] a graphical text editor by Rob Pike (still used by Ken Thompson and others).<br />
<br />
Vi, [[Vim]], gVim, the classic vi text editor.<br />
<br />
===Word Processors===<br />
<br />
[[Abiword]] is a full-featured word processor, there is also an even lighter version in the AUR, [http://aur.archlinux.org/packages.php?ID=25601/ Abiword-light].<br />
<br />
[http://txt2tags.sourceforge.net txt2tags] is a dead-simple, KISS-compliant lightweight, human-readable markup language to produce rich format content out of plain text files<br />
<br />
===Todo List Managers===<br />
[http://aur.archlinux.org/packages.php?ID=7673 Todo.txt] manages your Todo list from the command line.<br />
<br />
==System==<br />
<br />
===File Managers===<br />
<br />
[http://emelfm2.net/ emelFM2] is file manager that implements the popular two-pane design.<br />
<br />
[http://www.midnight-commander.org Midnight Commander] is a console-based, dual-paned, file manager.<br />
<br />
[http://pcmanfm.sourceforge.net/ PCManFM] is a lightweight file manager which features tabbed browsing and can optionally manage the desktop background.<br />
<br />
[[Ranger]] is a console based file manager with vi bindings, customizability, and lots of features.<br />
<br />
[http://rox.sourceforge.net ROX] is a small and fast file manager which can optionally manage the desktop background and panels.<br />
<br />
[[Thunar]] can be run as a daemon with excellent start up and directory load times. Features support for customizable actions.<br />
<br />
[[Vifm]] is a ncurses based two-pane file manager with vi like keybindings.<br />
<br />
[http://roland65.free.fr/xfe/index.php/ Xfe] X File Explorer (Xfe) is an MS-Explorer or Commander like file manager for X.<br />
<br />
===GUI Compression Tools===<br />
<br />
[http://squeeze.xfce.org/ Squeeze] is a modern and advanced archive manager.<br />
<br />
[http://xarchive.sourceforge.net Xarchive] is a GTK+ 2 front-end for various command line archiving tools.<br />
<br />
[http://xarchiver.xfce.org/ Xarchiver] is a lightweight desktop independent archive manager built with GTK+ 2. At the time of writing, it appears to be the most functional and up to date of the three tools listed here.<br />
<br />
===CD/DVD Burning Tools===<br />
<br />
{{App|recorder|Simple frontend to cdrkit/cdrtools, cdrdao, mkisofs and growisofs with limited options and preferences|http://code.google.com/p/recorder/|{{Package Official|recorder}}}}<br />
{{App|Xfburn|Simple frontend to the libburnia libraries with support for CD/DVD(-RW), ISO images and BurnFree.|http://www.xfce.org/projects/xfburn/|{{Package Official|xfburn}}}}<br />
<br />
===Login managers===<br />
<br />
[[CDM]] provides an ultra-minimalistic, yet full-featured login manager written in bash.<br />
<br />
[[SLiM]] provides a lightweight and elegant graphical login solution.<br />
<br />
[[Qingy]] is ultralight and very configurable graphical login independent on X Windows.<br />
<br />
===Monitors===<br />
<br />
[[Conky]] is a lightweight, scriptable system monitor.<br />
<br />
[http://htop.sourceforge.net/ htop] is a simple, ncurses interactive process viewer.<br />
<br />
===Panels===<br />
<br />
[http://nsf.110mb.com/bmpanel/ BMPanel] (BitMap Panel) is a lightweight, NETWM compliant panel for the X11 system.<br />
<br />
[http://fbpanel.sourceforge.net fbpanel] is a lightweight, NETWM compliant desktop panel.<br />
<br />
[http://lxde.org LXPanel] is a lightweight X11 desktop panel (part of LXDE).<br />
<br />
[http://pypanel.sourceforge.net/ PyPanel] is a lightweight panel/taskbar written in Python and C ([[PyPanel|HOWTO]]).<br />
<br />
[http://code.google.com/p/tint2/ Tint] is a simple panel/taskbar intentionally made for openbox3, but should also work with other window managers ([[Tint|HOWTO]]).<br />
<br />
[http://www.failedprojects.de/pancake/ pancake] is a highly configurable, modular panel for X.<br />
<br />
===Terminals===<br />
<br />
[http://lilyterm.luna.com.tw/index_en.html Lilyterm] is a light and easy to use libvte based X Terminal Emulator.<br />
<br />
[http://rox.sourceforge.net ROXTerm] is a tabbed, VTE-based terminal emulator with a small footprint.<br />
<br />
[[urxvt]] is a highly extendable unicode enabled rxvt-clone terminal emulator featuring tabbing, url launching, quake-style dropdown, pseudo-transparency, and is extensible with perl.<br />
<br />
[http://www.pleyades.net/david/sakura.php Sakura] is a terminal emulator based on GTK+ and VTE.<br />
<br />
[http://invisible-island.net/xterm/ xterm] is a terminal emulator for the X Window System.<br />
<br />
===Trays===<br />
<br />
[http://icculus.org/openbox/2/docker/ Docker] is a docking application which acts as a system tray.<br />
<br />
[http://stalonetray.sourceforge.net Stalonetray] is a stand-alone system tray.<br />
<br />
[http://gna.org/projects/fvwm-crystal/ Trayer] swallows GTK+ 1.2/2.x application docklets, and KDE docklets.<br />
<br />
===Window managers===<br />
<br />
[[Awesome]] is a floating and tiling window manager initially based on a [[dwm]] code rewriting.<br />
<br />
[[Dwm]] is a featherweight dynamic window manager configured by editing the source itself. <br />
<br />
[[Evilwm]] is a minimalist floating window manager with an installed size of only 0.07 MB.<br />
<br />
[[Fluxbox]] is a lightweight and highly configurable window manager.<br />
<br />
[http://www.fvwm.org/ FVWM] is a lightweight, flexible and highly-configurable Window Manager.<br />
<br />
[[i3]] is a manual tiling window manager which places client into containers.Containers can be stacked (like wmii) or tabbed (like ion3). i3 also supports floating windows. <br />
<br />
[[JWM]] is a small and fast stacking window manager featuring native support for customizable panels/buttons and a system tray dock.<br />
<br />
[[Musca]] is a very lightweight window manager which has features from dwm and ratpoison. Uses about 350-400KB of memory.<br />
<br />
[[Openbox]] is another lightweight and highly configurable window manager.<br />
<br />
[[PekWM]] is small and easily configurable window manager.<br />
<br />
[[Ratpoison]] is a keyboard-oriented, customizable lightweight window manager, modelled after GNU Screen.<br />
<br />
[[Scrotwm]] is a small dynamic tiling window manager for X11. It is written in C and configured with a text configuration file.<br />
<br />
[[Subtle]] is a semi-automatic tiling window manager with a strong focus on easy but customizable handling and look and feel.<br />
<br />
[http://incise.org/tinywm.html TinyWM] is a tiny window manager that was created as an exercise in minimalism, and it is also helpful in learning some of the very basics of creating a window manager. It is around 50 lines of C, and there is a Python version using python-xlib.<br />
<br />
[[Twm]] is a classic, customizable and very lightweight window manager; possibly the first designed for X11.<br />
<br />
[[Window Maker]] is an elegant and fast floating window manager. It is an implementation NeXTSTEP, the precursor to Mac OS X. It includes functionality to launch applications and manage iconified windows. It is easy to configure both with the included GUI application and by editing simple text files.<br />
<br />
[[Xfce]] is a desktop environment much lighter but similar to GNOME. It includes the xfwm4 window manager.<br />
<br />
[[Xmonad]] is a tiling window manager for X, written and configured in Haskell.<br />
<br />
[[Wmfs]] (Window Manager From Scratch) is a lightweight and highly configurable tiling window manager for X.<br />
<br />
[[Wmii]] is a small, dynamic window manager for X11. It is scriptable, has a 9p filesystem interface and supports classic and tiling (acme-like) window management. It aims to maintain a small and clean (read hackable and beautiful) codebase.<br />
<br />
== Links ==<br />
<br />
[http://bbs.archlinux.org/viewtopic.php?id=88515 Arch Linux Forums / LnF Awards 2010] - The best Light & Fast apps of 2010.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=USB_flash_installation_medium&diff=118564
USB flash installation medium
2010-10-02T20:09:59Z
<p>Cantabile: /* Arch USB images */ made the warning about sdx/sdx1 hopefully a bit more prominent</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|Install from a USB flash drive}}<br />
[[de:Installation von einem USB-Stick]]<br />
<br />
This page discusses how to put Arch installation media onto a USB key (or "flash drive"). The result will be a LiveCD-like system that will discard all changes when it's shut down. Consider whether you're instead interested in [[Installing Arch Linux on a USB key]].<br />
<br />
== On GNU/Linux ==<br />
<br />
=== Arch USB images ===<br />
<br />
Beginning from release 2010.05, all iso files can be directly written to usb media. Download them from your [http://archlinux.org/download/ local mirror]. To install, first ensure the USB device is '''unmounted''' and then issue the following command:<br />
<br />
$ dd if=image.iso of=/dev/sd[x]<br />
<br />
where ''image.iso'' is the path to the iso file and ''/dev/sd[x]'' is your USB device.<br />
{{Warning|'''''Make sure to use /dev/sdx and NOT /dev/sdx1.''''' '''This is a very common error!'''}}<br />
<br />
{{Warning|This will irrevocably destroy all data on your USB stick.}}<br />
<br />
brain0 made a nice post on his blog on [http://archlinux.me/brain0/2010/05/29/arch-linux-usb-install-and-resuce-media/ Arch Linux USB Install and Rescue Media] where he explains how to have several partitions on the USB stick with some accessible from windows.<br />
<br />
=== UNetBootin ===<br />
<br />
Another way to make a USB drive bootable, is by using [http://unetbootin.sourceforge.net/ UNetBootin]. This application can download most distributions for you and write them to your flash drive. UNetBootin is not using the most recent Arch ISO version, but you can supply your own iso file. <br />
<br />
After Unetbootin finishes, you have to adjust syslinux.cfg on the root of your flash drive before rebooting. Correct the "archisolabel=" parameter to reflect the label of the USB drive you used, i.e.:<br />
<br />
append initrd=/ubninit archisolabel=<label> tmpfs_size=75% locale=en_US.UTF-8<br />
<br />
=== Gujin ===<br />
<br />
A third method is to follow the instructions about [http://psychoticspoon.blogspot.com/2009/01/booting-multiple-livecds-from-single.html Booting multiple LiveCD's from a single USB stick]. In a nutshell, you create 2 partitions on your USB drive, copy the [http://gujin.sourceforge.net/ Gujin] boot loader image to the first partition, and copy Arch's ISO to the second.<br />
<br />
== On Mac OS X ==<br />
<br />
To be able to use dd on your usb device on a Mac you have to do some special maneuvers. First of all insert your usb device, OS X will automount it, and run<br />
<br />
diskutil list<br />
<br />
in Terminal.app. Figure out what your usb device is called - mine was called /dev/disk1. (Just use the `mount` command or `sudo dmesg | tail`.) Now you run<br />
<br />
diskutil unmountDisk /dev/disk1<br />
<br />
to unmount the partitions on the device (i.e., /dev/disk1s1) while keeping the device proper (i.e., /dev/disk1). Now we can continue in accordance with the Linux instructions above (but use bs=8192 if you're using the OS X dd, the number comes from 1024*8).<br />
<br />
dd if=image.iso of=/dev/disk1 bs=8192<br />
20480+0 records in<br />
20480+0 records out<br />
167772160 bytes transferred in 220.016918 secs (762542 bytes/sec)<br />
<br />
== On Windows ==<br />
<br />
To write the USB image on Windows, you will need [http://shounen.ru/soft/flashnul/ flashnul] ([http://translate.google.com/translate?u=http%3A%2F%2Fshounen.ru%2Fsoft%2Fflashnul%2F&hl=en&ie=UTF8&sl=ru&tl=en English version of the page]) or [http://www.cygwin.com/ Cygwin].<br />
<br />
=== The Flashnul Way ===<br />
<br />
From a command prompt, invoke flashnul with -p, and determine which device index is your USB drive. For example, my output looks like this:<br />
<br />
C:\>flashnul -p<br />
<br />
Avaible [sic] physical drives:<br />
0 size = 200048565760 (186 Gb)<br />
1 size = 400088457216 (372 Gb)<br />
2 size = 400088457216 (372 Gb)<br />
3 size = 4060086272 (3872 Mb)<br />
<br />
In my case, with a 4 GB USB drive, it is device index 3.<br />
<br />
When you have determined which device is the correct one, you can write the image to your drive, by invoking flashnul with the device index, -L, and the path to your image. In my case, it would be<br />
<br />
C:\>flashnul 3 -L path\to\arch\usb.iso<br />
<br />
As long as you are really sure you want to write the data, type yes, then wait a bit for it to write. If you get an access denied error, unplugging and re-attaching the drive worked for me.<br />
<br />
If under Vista or Win7, you should open the console as administrator, or else flashnul will fail to open the stick as a block device and will only be able to write via the drive handle windows provides<br />
<br />
<b>Note:</b><br />
<i>I had to do "C:\flashnul\flashnul.exe <b>H:</b> -L c:\archlinux-2008.06-core-i686.img" for it to work. I kept getting access denied if i just used the number. -gejr </i> <br />
<br />
<b>Note:</b><br />
<i>The output of flashnul -p was considerably different for me. No numbers were returned or block information, just a list of logical drive mappings (C:, D:, etc..) so I just did flashnul -L archlinux.img E: --[[User:Kahrn|Kahrn]] 18:12, 28 April 2010 (EDT)</i><br />
<br />
=== The Cygwin Way ===<br />
<br />
Make sure your cygwin installation contains the dd package.<br />
Or if you don't want to install Cygwin, you can simply download dd for windows from http://www.chrysocome.net/dd.<br />
<br />
Place your image file in your home directory, in my case it is:<br />
<br />
C:\cygwin\home\John\<br />
<br />
Run cygwin as administrator (required for cygwin to access hardware). To write to your USB drive use the following command:<br />
<br />
dd if=image.iso of=\\.\[x]:<br />
<br />
where image.iso is the path to the iso-image file within the cygwin directory and \\.\[x]: is your USB device where x is the windows designated letter, in my case "\\.\d:".<br />
<br />
'''Note:''' This will irrevocably delete all files on your USB stick, so make sure you don't have any important files on the stick before doing this.<br />
<br />
=== win32 disk imager ===<br />
Download win32 disk imager from http://launchpad.net/win32-image-writer. Run the program. Select the arch image-file and usb stick. The Win32 Disk Imager's file browser assumes image files end with .img, so if the image-file you've selected ends with .iso, you will have to type its name in manually; this difference in suffixes is simply cosmetic however, the image will be written fine regardless. Click on the write button. Now you should be able to boot from the usb stick and install Arch Linux from it.<br />
<br />
===UNetBootin===<br />
<br />
Another way to make a USB drive bootable, is by using UNetBootin ([[#UNetBootin|see above]])<br />
<br />
==Old Method from ISO, deprecated==<br />
*Prepare USB stick:<br />
The arch-ftp.img is about 150 MB, so it should fit on a 256 MB USB stick. The arch-core.img is ~300 MB and should fit on a 512 MB stick.<br />
<br />
1. Partition the USB stick.<br />
Create one partition with FAT16 type, make it bootable. Remember its name, such as /dev/sd[x]1.<br />
<br />
cfdisk /dev/sd[x]<br />
<br />
2. Make a FAT16 filesystem (you need dosfstools)<br />
<br />
mkdosfs /dev/sd[x]1<br />
<br />
3. Get the arch-base install ISO from www.archlinux.org<br />
<br />
4. Mount the iso to an temporary directory<br />
<br />
mkdir -p /mnt/archcd<br />
mount -o loop /Path/to/iso /mnt/archcd<br />
<br />
5. Mount the USB Stick<br />
<br />
mkdir -p /mnt/usb/<br />
mount /dev/sd[x]1 /mnt/usb/<br />
<br />
6. Copy the .iso to the USB Stick<br />
<br />
cp -ra /mnt/archcd/* /mnt/usb/<br />
<br />
<br />
7. Copy the boot data<br />
<br />
cd /mnt/usb/isolinux/<br />
cp vmlinuz /mnt/usb/<br />
cp initrd.img /mnt/usb/<br />
cp boot.* /mnt/usb/<br />
cp isolinux.cfg /mnt/usb/syslinux.cfg<br />
<br />
8. Install MBR and syslinux<sup>(1)</sup><br />
<br />
lilo -M /dev/sd[x] mbr<br />
syslinux -s /dev/sd[x]1<br />
<br />
===After booting from the USB stick:===<br />
<br />
Start the installation by logging in as root and invoke the command "/arch/setup".<br />
<br />
The installer should mount the source media automatically. If it fails you can manually mount the source media on the stick to the /src directory with the following command:<br />
<br />
mount /dev/sd[x] /src<br />
<br />
===Notes and Troubleshooting:===<br />
<br />
<sup>(1)</sup> Using lilo is not really needed because syslinux does the "floppy" loading stuff. But if you get some error like "Can't load operating system" you have to perform the lilo command.<br />
<br />
<sup>(2)</sup> If you get "Cluster sizes larger than 16K not supported" error when booting this means you need to install more recent version of syslinux.<br />
<br />
<sup>(3)</sup> Space not used on the USB stick can still be used for storing files... Use a utility like gparted and add a partition to the unused space.</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Broadcom_wireless&diff=116462
Broadcom wireless
2010-09-05T11:53:35Z
<p>Cantabile: Updated list of supported cards</p>
<hr />
<div>[[Category:Communication and network (English)]]<br />
[[Category:HOWTOs (English)]]<br />
= Introduction =<br />
<br />
Finally Broadcom has released a linux driver for most of its wireless chipsets. See the [http://ubuntuforums.org/showthread.php?t=914697 Ubuntu forums] and the [http://forums.debian.net/viewtopic.php?p=174719&sid=801a8f97aa7112c8c1c4f9294ad5d3e9 Debian forums]. It seems to work with all modern 43xx Broadcom cards. Up until recently the only way to get some of these working, such as 4328, was via [[ndiswrapper|ndiswrapper]]. Broadcom chipsets are used in most Dell laptops, among others.<br />
<br />
Unfortunately, the driver does not work with hidden ESSID's.<br />
<br />
= Determine whether you actually have one of these cards =<br />
<br />
Type in console (mind the letter case):<br />
$ lspci -nn | grep 14e4<br />
Look at the numbers at the end, in square brackets.<br />
<br />
Here is a list of cards which work with this driver:<br />
<br />
<pre><br />
[14e4:4311]<br />
[14e4:4312]<br />
[14e4:4313]<br />
[14e4:4315]<br />
[14e4:4727]<br />
[14e4:4328]<br />
[14e4:4328]<br />
[14e4:4329]<br />
[14e4:432a]<br />
[14e4:432b]<br />
[14e4:432c]<br />
[14e4:432d]<br />
[14e4:4353]<br />
[14e4:4357]<br />
</pre><br />
<br />
[http://www.broadcom.com/docs/linux_sta/README.txt This document] should have more up-to-date information.<br />
<br />
If you have some other Broadcom model you might try the [[Wireless#b43|b43]] driver. List of cards supported by b43 is [http://wireless.kernel.org/en/users/Drivers/b43 here].<br />
<br />
= Driver installation =<br />
== Get the driver == <br />
There's a PKGBUILD in [http://aur.archlinux.org/packages.php?ID=19514 AUR].<br />
Or, you can download the driver from [http://www.broadcom.com/support/802.11/linux_sta.php here],<br />
where you will also find a README file.<br />
<br />
It is better to use the PKGBUILD, that way pacman will track all the files.<br />
<br />
== Load the kernel module ==<br />
Before loading the module, remove b43, or any other module you are using for your wireless card:<br />
# rmmod b43<br />
Load the module:<br />
# modprobe lib80211_crypt_tkip<br />
# modprobe wl<br />
<br />
You might also need to generate modules.dep and map file again by:<br />
# depmod -a<br />
<br />
Now you can make the change permanent by including lib80211_crypt_tkip in your MODULES array in {{Filename|/etc/rc.conf}}.<br />
<br />
MODULES=(lib80211_crypt_tkip ...<br />
<br />
Or if you installed module via AUR package you just need:<br />
# rmmod b43 # (or any other module you are using for your wireless card)<br />
# modprobe wl<br />
<br />
Now in iwconfig you should see a wireless device (for example eth1). You might need to restart your computer to see the device in iwconfig.<br />
<br />
To make the module load at boot just add in {{Filename|[[rc.conf]]}}:<br />
MODULES=(lib80211_crypt_tkip wl !b43 !ssb ...<br />
By blacklisting the 'b43' and 'ssb' modules, you will prevent the kernel from autoloading them instead of the desired modules.<br />
<br />
==Note on using multiple Broadcom kernel modules==<br />
<br />
In my Dell Inspiron Laptop, i have a Broadcom BCM4401 Ethernet card and a Broadcom BCM4328 Wireless card. If I just remove b43, I can load the wl driver, but no wireless card shows up. However, if i first remove the b44 (and ssb) driver for my ethernet card, and then load the wl driver, I get a wireless eth0. Afterwards, I can load b44 again, to have an ethernet eth1.<br />
<br />
Short version:<br />
* Put "lib80211_crypt_tkip" and "wl" at the BEFORE b44 (if you have it) position in MODULES= in /etc/rc.conf<br />
* Don't forget to blacklist b43<br />
* Your wireless card will be eth0<br />
* Your ethernet card will be eth1<br />
* Both will work fine<br />
<br />
<br />
= Troubleshooting =<br />
== Interfaces swapped every time == <br />
This is a common problem with this driver. And the next process works for me with the BCM4312 following the [http://wiki.archlinux.org/index.php/Udev#Mixed_Up_Devices.2C_Sound.2FNetwork_Cards_Changing_Order_Each_Boot udev post]:<br />
<br />
Create a file called <code>/etc/udev/rules.d/10-network.rules</code> and bind the MAC address of each of your cards to a certain interface name:<br />
<br />
<pre>SUBSYSTEM=="net", ATTR{address}=="aa:bb:cc:dd:ee:ff", NAME="eth0"<br />
SUBSYSTEM=="net", ATTR{address}=="ff:ee:dd:cc:bb:aa", NAME="eth1"</pre><br />
<br />
'''Where:'''<br />
* NAME="eth0" is the name of the interface that you want, for example the same name "eth0". You can use other names, for example "lan0" for eth0 or "wlan0" for eth1. <br />
* To get the MAC address of each card, use this command: <code>udevadm info -a -p /sys/class/net/<yourdevice> | grep address</code>. Please, note that this is case sensitive and you must use '''lower-case'''.<br />
But first you need know if eth0 isn't eth1 or vice versa, you can perform a scan: <code>iwlist scan</code> <br />
So if eth0 is really eth1 then the MAC of eth1 is that of eth0.<br />
<br />
Don't forget to update your /etc/rc.conf and other config files using the old ethX notation!<br />
<br />
== Module wl does not work after a kernel upgrade ==<br />
This is because the driver is compiled with the current kernel, you need recompile the driver with the new kernel for the module to function properly. Bear this in mind when doing kernel updates.<br />
<br />
== Device not showing up ==<br />
Be sure of trying "ifconfig -a", "ifconfig" only shows interfaces that are active.<br />
<br />
Here is one short script that helped me out, because I was loading modules incorrectly:<br />
<pre>#!/bin/bash<br />
<br />
rmmod b43 ssb wl lib80211_crypt_tkip lib80211<br />
<br />
modprobe lib80211_crypt_tkip<br />
modprobe wl<br />
<br />
depmod -a</pre><br />
<br />
This helped me when sometimes I couldn't get the interface to show up. Else, I recommend adding the modules in rc.conf:<br />
<pre>MODULES=([...] !b43 !ssb !lib80211 lib80211_crypt_tkip wl)</pre><br />
<br />
Worked for me in a Dell Latitude 2100 with Broadcom BCM5764M (eth) and BCM4312 (wifi). Also works in a HP Compaq 6715s with Broadcom BCM4311 (wifi).<br />
<br />
Also works on the HP Mini 110-1020LA netbook using BCM4312 chipset</div>
Cantabile
https://wiki.archlinux.org/index.php?title=User:Cantabile&diff=116290
User:Cantabile
2010-09-02T11:16:56Z
<p>Cantabile: Created page with "The only reason this page exists is because I like blue more than red :) ..."</p>
<hr />
<div>The only reason this page exists is because I like blue more than red :) ...</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Chromium&diff=116282
Chromium
2010-09-02T10:41:03Z
<p>Cantabile: Added info about the various channels, non-latin scripts, xdg-open; corrected spelling here and there</p>
<hr />
<div>[[Category:Internet and Email (English)]]<br />
Chromium is an open source graphical web browser from Google, based on the [[Wikipedia: WebKit|WebKit]] rendering engine.<br />
<br />
== Available flavours ==<br />
<br />
There are three flavours of chromium:<br />
* stable, which can be found in [extra], under the name of '''chromium'''<br />
* beta, which lives in the aur, under the name of [http://aur.archlinux.org/packages.php?ID=40059 chromium-beta]<br />
* dev, which also lives in the aur, under the name of [http://aur.archlinux.org/packages.php?ID=37244 chromium-dev]<br />
<br />
{{Note|Compiling chromium-beta or chromium-dev takes at least as long as compiling the linux kernel.}}<br />
<br />
There are also some packages in the aur which provide the binary Google Chrome.<br />
<br />
See [http://news.softpedia.com/news/Google-Chrome-vs-Chromium-Understanding-Stable-Beta-Dev-Releases-and-Version-No-140060.shtml this article] for an explanation of the differences between the three flavours, Chromium vs. Chrome, and the version numbers.<br />
<br />
== Displaying various non-latin scripts ==<br />
<br />
If you encounter empty square boxes instead of Chinese/Japanese/Korean/etc characters, you need to install some ttf fonts.<br />
<br />
* for Chinese:<br />
** ttf-arphic-uming<br />
** ttf-arphic-ukai<br />
** ttf-fireflysung<br />
* for Japanese:<br />
** ttf-fireflysung<br />
** ttf-vlgothic<br />
* for Korean (Hangul):<br />
** ttf-unfonts-core<br />
* for Khmer:<br />
** ttf-khmer<br />
<br />
[[Wikipedia: Help:Multilingual_support|This page]] has some useful tables.<br />
<br />
== Using chromium with no desktop environment ==<br />
<br />
Unlike [[Firefox]], chromium does not maintain its own database of mimetype<->application associations. Instead, it relies on {{Filename|xdg-open}} (part of extra/xdg-utils) to open files and, for example, [[Wikipedia: Magnet_URI_scheme|magnet links]].<br />
<br />
Inside a [[Desktop Environment|desktop environment]] ([[GNOME|Gnome]], or [[KDE|Kde]], or [[Xfce]]), {{Filename|xdg-open}} simply passes the arguments to that DE's file-opener application ({{Filename|gnome-open}}, {{Filename|kde-open}}, or {{Filename|exo-open}}, respectively), which means that the associations are left up to the DE.<br />
<br />
However, when no desktop environment is detected (for example when one runs a standalone [[Window Manager|window manager]], like [[Openbox]]), {{Filename|xdg-open}}'s behaviour becomes rather strange and annoying: many filetypes opened in firefox or chromium itself, no support for magnet links, etc.<br />
<br />
There are a number of possible solutions to this problem, outlined below.<br />
<br />
* Improve xdg-open, make it smarter (aka "patches welcome" :P )<br />
* Use part of a desktop environment, specifically, the part which includes the file opener; for gnome, that would be 'libgnome' (and its dependencies), for xfce, 'exo'. The $DE environment variable needs to be exported before starting the window manager. For example:<br />
<blockquote>{{File|name=~/.xinitrc|content=<br />
export DE=gnome<br />
exec ck-launch-session openbox<br />
}}</blockquote><br />
* Use [http://aur.archlinux.org/packages.php?ID=32911 mimeo] (written by an arch (trusted) user) and [http://aur.archlinux.org/packages.php?ID=32912 xdg-utils-mimeo], which replaces extra/xdg-utils and contains a {{Filename|xdg-open}} script patched to make use of {{Filename|mimeo}} the same way {{Filename|gnome-open}} would be used. Mimetype<->application associations can then be customised easily in {{Filename|/etc/mime.types}} or {{Filename|~/.mime.types}}<br />
<br />
== Font Rendering ==<br />
<br />
Chromium doesn't use the settings in {{Filename|~/.fonts.conf}}. If the fonts are rendered badly you can use xft settings [[Xdefaults|as suggested here]]. Just create {{Filename|~/.Xdefaults}} if it doesn't exist and add in:<br />
<br />
<pre><br />
! Xft settings ---------------------------------------------------------------<br />
<br />
Xft.dpi: 96<br />
Xft.antialias: true<br />
Xft.rgba: rgb<br />
Xft.hinting: true<br />
Xft.hintstyle: hintslight<br />
</pre><br />
<br />
{{Note|these settings will affect any application that reads {{Filename|~/.Xdefaults}}, not just chromium; one example is [[Rxvt-unicode|rxvt-unicode]].}}<br />
<br />
== Default browser ==<br />
<br />
Want to make Chromium the default browser? An option is to edit the ''xdg-open'' script.<br />
$ sudo $YOUR_EDITOR /usr/bin/xdg-open<br />
Almost at the bottom on the file, is a long horizontal list of browsers:<br />
if [ x"$DE" = x"" ]; then<br />
# if BROWSER variable is not set, check some well known browsers instead<br />
if [ x"$BROWSER" = x"" ]; then<br />
BROWSER=links2:links:lynx:w3m<br />
if [ -n "$DISPLAY" ]; then<br />
BROWSER=firefox:mozilla:epiphany:konqueror:chromium-browser:google-chrome:$BROWSER<br />
fi<br />
fi<br />
DE=generic<br />
fi<br />
Add '''chromium:''' ''(mind the colon which separates the entries)'' before '''firefox:mozilla:''' ... and save. To test if this were conducted successfully, type this into your terminal:<br />
<pre>$ xdg-open http://google.com</pre><br />
If everything went perfect, either a new tab inside Chromium, or a new window would open and display the Google homepage, depending on your settings.<br />
<br />
<br />
Another option, when using '''mimeo''', is to associate "http://" links with chromium:<br />
{{File|name=~/.mime.types|content=<nowiki><br />
/usr/bin/chromium<br />
^http://<br />
</nowiki>}}<br />
<br />
== Flash Player ==<br />
<br />
If running the 32 bit Archlinux, all one needs to do is install the flash plugin and restart chromium:<br />
# pacman -S flashplugin<br />
On the 64 bit port however, it's not so simple.<br />
<br />
Before installing the flash plugin, one [http://www.archlinux.org/news/508/ needs to enable] the new [multilib] repository.<br />
<br />
Now add a directory {{Filename|plugins}} in {{Filename|/usr/lib/chromium}}<br />
<br />
Next, add in that directory a symbolic link to the flash plugin:<br />
$ cd /usr/lib/chromium/plugins/<br />
# ln -s ../../nspluginwrapper/i386/plugins/libflashplayer.so<br />
<br />
== Open PDF files inside Chromium ==<br />
<br />
To open PDF files directly inside Chromium you will need a fixed version of [http://aur.archlinux.org/packages.php?ID=9458 mozplugger].<br />
<br />
Grab the PKGBUILD from AUR and do a <br />
<br />
$ makepkg -o<br />
<br />
to extract the sources. Next open {{Filename|mozplugger.c}} and go to line 2097 (for version 1.14.1; otherwise search for NPPVpluginNeedsXEmbed) and change <br />
<br />
$ (2097): *((NPBool *)value) = 0;"<br />
<br />
to:<br />
<br />
$ (2097): *((NPBool *)value) = 1;"<br />
<br />
After the change do<br />
<br />
$ makepkg -ei<br />
<br />
to build and install without overriding the source.<br />
<br />
Create a patch and PKGBUILD for lazy people...<br />
<br />
== Certificates ==<br />
<br />
Chromium uses [[Nss | NSS]] for the certificate management. Actually there is no graphical user interface for NSS therefore you can use the CLI.<br />
<br />
== Problems ==<br />
<br />
If when you try to run chromium you cannot get your default profile as below:<br />
<br />
<pre><br />
$ chromium<br />
[2630:2630:485325611:FATAL:chrome/browser/browser_main.cc(755)] Check failed: profile. <br />
Cannot get default profile. Trace/breakpoint trap<br />
</pre><br />
<br />
Just correct the owner of the directory {{Filename|~/.config/chromium}}, and it will work.<br />
<pre><br />
$ chown -R yourusername: ~/.config/chromium<br />
</pre><br />
<br />
== Resources ==<br />
<br />
* [http://www.chromium.org/Home Chromium homepage]<br />
* [[Wikipedia: Chromium_(web_browser)#Differences_between_Chromium_and_Google_Chrome|Differences between Chromium and Google Chrome]]<br />
* [http://googlechromereleases.blogspot.com/ Announcements and release notes for the Google Chrome browser]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=TuxOnIce&diff=112749
TuxOnIce
2010-07-28T18:36:53Z
<p>Cantabile: replaced all occurences of suspend2.conf with tuxonice.conf</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|Tuxonice}}<br />
{{i18n_entry|Italiano|Tuxonice (Italiano)}}<br />
{{i18n_links_end}}<br />
[[Category:Power management (English)]]<br />
[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
This is a quick start guide for installing [http://www.tuxonice.net Tuxonice] (formerly suspend2), an advanced suspend/hibernate framework which supports suspending to a swap-disk or a regular file with fast LZO-compression. Visit the Tuxonice website for a full list of [http://www.tuxonice.net/features features].<br />
<br />
=Preparing the kernel=<br />
<br />
Tuxonice consists of a kernel patch, plus an optional user interface. Only the kernel patch is necessary, the user interface merely provides a graphical interface displayed during the hibernation/resume cycle. <br />
<br />
You can use the [http://aur.archlinux.org/packages.php?ID=15224 kernel26-ice] package in the [[AUR]]. It automatizes all the patch routines, the compilation and installation of the kernel, the regeneration of the initramfs with an appropriate hook.<br />
<br />
You can build the package manually, see [[AUR_User_Guidelines#Installing_Packages_from_the_AUR | Installing packages from the AUR]] for more information. This is better as you maintain more control over the install process, plus its easier to make changes if you want to repeat the process. Alternatively, you can use [[Yaourt]]:<br />
<br />
# yaourt -S kernel26-ice<br />
<br />
Otherwise, you need to patch, configure and compile your own kernel, visit [[Kernel Compilation From Source]] and [[Kernel Compilation with ABS]] for instructions. The required patch can be obtained from the Tuxonice website mentioned above.<br />
<br />
<br />
Next, install the hibernate-script package from the Extra repository which we will use to call Tuxonice. Hibernate-script is the default script developed by the Tuxonice development team:<br />
<br />
# pacman -S hibernate-script<br />
<br />
The configuration files for hibernate-script are in /etc/hibernate, we will get back to them shortly.<br />
<br />
=Setting up the bootmanager=<br />
Before your can use the suspend function, you need to add the "resume" parameter in your bootmanager, unless you have hardcoded your swap partition during the kernel configuration. The resume parameter points to the swap partition or swap file, below are the steps involved for both methods.<br />
<br />
==Suspend to swap partition==<br />
{{Note|As of the latest version of TuxOnIce (3.0.99.44), adding the kernel resume parameter is no longer necessary, it will autodetect if your swap drive contains a bootable image. You only need to set the swap method appropriately. For more details, check out http://www.tuxonice.net/<br />
}}<br />
<br />
Set the swap method (make sure the right partition is indicated) in /etc/hibernate/tuxonice.conf:<br />
<br />
SuspendDevice swap:/dev/sda3<br />
<br />
==Suspend to file==<br />
For the file allocator, you will have to prepare a hibernation file. First configure the /etc/hibernate/tuxonice.conf file, uncomment the "FilewriterLocation" option:<br />
<br />
FilewriterLocation /suspend_file 1000<br />
<br />
1000 is the amount of diskspace reserved for the hibernation file, in this case 1000 Megabytes. Usually an amount of 50% - 75% of your total amount of RAM will suffice.<br />
<br />
Next, run the following command to create the hibernation file:<br />
<br />
# hibernate --no-suspend<br />
<br />
Take a look in /sys/power/tuxonice/resume for what to pass to your kernel. You should see something like file:/dev/hda7:0x10011f, in which case you should append "resume=file:/dev/hda7:0x10011f" as a kernel parameter in your lilo.conf file or GRUB's menu.lst.<br />
<br />
=Recreating the initramfs=<br />
{{Note|Resuming doesn't work with mkinitcpio 0.5.25 (this is still true as of version 0.5.28) due to a bug in /lib/initcpio/hooks/resume.<br />
As a workaround downgrade to version 0.5.24 or replace the 6th line in /lib/initcpio/hooks/resume by<br />
resumedevice&#61;${resume#*:}<br />
resumedevice&#61;${resumedevice%:*}<br />
if [ -n "${resumedevice}" ] && poll_device "${resumedevice}" ${rootdelay}; then<br />
('''Note:''' there must be a space between the opening bracket and the '-n' in the last line above.)<br />
}}<br />
If you use an initramfs, you need to add the resume hook in the HOOKS in the configuration of mkinitcpio. Additionally, if you want to speed things up by using LZO compression, add the lzo module to the MODULES array in the same file.<br />
<br />
/etc/mkinitcpio.conf example:<br />
<br />
MODULES="lzo"<br />
HOOKS="base udev autodetect pata scsi sata resume filesystems"<br />
<br />
Rebuild the initramfs:<br />
<br />
# mkinitcpio -p kernel26-ice<br />
<br />
=Suspending and resuming=<br />
With hibernate-script, your preferred hibernation method can be set in the file /etc/hibernate/hibernate.conf. If you list several methods, the first one will be used. Note that ''hibernate'' can also be used with [[Suspend to RAM]] or vanilla swsusp, but this is not part of this guide.<br />
<br />
For Tuxonice use: <br />
<br />
TryMethod tuxonice.conf<br />
<br />
Specific settings for Tuxonice are in /etc/hibernate/tuxonice.conf. Make sure that the following lines are uncommented and appropriately configured:<br />
<br />
UseTuxOnIce yes<br />
Compressor lzo<br />
<br />
There are a number of additional settings and tweaks which you can set in /etc/hibernate/tuxonice.conf and /etc/hibernate/common.conf, more information about these can be found on the [http://www.tuxonice.net/HOWTO-4.html Tuxonice] website and on the [[Suspend_to_Disk | Suspend to Disk]] page of this wiki.<br />
<br />
Now try Tuxonice hibernation with the following method:<br />
<br />
# hibernate -F /etc/hibernate/tuxonice.conf<br />
<br />
You can abort a suspend cycle if you press the escape key. If you press a capital R, you will force the system to reboot after hibernation.<br />
<br />
If all goes well, you should be able to resume using the same Grub menu selection. If you make that option the default for Grub, you will always default to resuming if a resume image is available. '''Do never use a different kernel to resume than you used to suspend! If pacman updates your kernel, don't suspend before you have rebooted properly.''' It is recommended that you test the suspend/hibernate from a text console first and then once you have confirmed that it works try it from within X.<br />
<br />
You can make this practice safer adding the hibernate-cleanup daemon to your DAEMONS array in /etc/rc.conf. This script will make sure that any stale image is deleted from your swap partition at boot time. This should make your system safe also in the case that you have chosen the mistaken kernel at the grub prompt. The hibernate-cleanup service is included in the hibernate-script package.<br />
<br />
=Using userui - a user interface for Tuxonice (optional)=<br />
<br />
Optionally, you can use a text or graphical (fbsplash) interface with a progress bar with tuxonice. To do this, install the tuxonice-userui package from the AUR. This package depends on the static freetype2 library that is provided by freetype2-static (also in the AUR).<br />
<br />
In /etc/hibernate/tuxonice.conf, set the desired user interface:<br />
<br />
ProcSetting user_interface/program /usr/sbin/tuxoniceui_text # Text interface<br />
<br />
or<br />
<br />
ProcSetting user_interface/program /usr/sbin/tuxoniceui_fbsplash # Graphical fbsplash interface<br />
<br />
The fbsplash interface also needs a symlink to the fbsplash theme, like so:<br />
# ln -s /etc/splash/arch-banner-noicons/ /etc/splash/tuxonice<br />
Without this symlink, there will be no progress indicators during suspend/resume.<br />
<br />
It is probably necessary to regenerate the initramfs after changing the symlink above.<br />
<br />
The text interface may be good for debugging tuxonice, as it displays some messages.<br />
You won't see a user interface for the first few seconds of the resume process unless you add the ''userui'' hook to your mkinitcpio (before the ''resume'' hook) configuration and regenerate your initramfs, but this is also optional. <br />
<br />
Generate initramfs:<br />
<br />
# mkinitcpio -p kernel26-ice<br />
<br />
To test if userui works, switch to a text console and run:<br />
<br />
# tuxoniceui_text --test<br />
<br />
For the graphical interface run:<br />
<br />
# tuxoniceui_fbsplash --test<br />
<br />
=References=<br />
<br />
*The [http://www.tuxonice.net Tuxonice website] and [http://wiki.tuxonice.net/ Tuxonice wiki] are excellent sources of documentation.<br />
*More general information about suspend/hibernate with hibernate-script can be found on the [[Suspend_to_Disk | Suspend to Disk]] page of this wiki. This also covers some advanced topics like problems with specific hardware and configurations.<br />
*Another good source of information is the [http://en.gentoo-wiki.com/wiki/TuxOnIce Gentoo wiki]</div>
Cantabile
https://wiki.archlinux.org/index.php?title=Allow_users_to_shutdown&diff=112615
Allow users to shutdown
2010-07-25T07:52:16Z
<p>Cantabile: added dbus-send commands</p>
<hr />
<div>[[Category:Security (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|Allow Users to Shutdown}}<br />
<br />
== The first way: sudo ==<br />
First install sudo:<br />
# pacman -S sudo<br />
<br />
Then, as root, add the following to the end of {{Filename|/etc/sudoers}} using the {{Codeline|visudo}} command. Substitute {{Codeline|'''user'''}} for your username and {{Codeline|'''hostname'''}} for the machine's hostname.<br />
<br />
'''user''' '''hostname'''=NOPASSWD: /sbin/shutdown -h now,/sbin/reboot<br />
<br />
Now your user can shutdown with {{Codeline|sudo shutdown -h now}}, and reboot with {{Codeline|sudo reboot}}. Users wishing to power down a system can also use {{Codeline|poweroff}} or {{Codeline|halt}}.<br />
<br />
== The second way: Xfce ==<br />
A third option under XFCE, if you don't want to use shutting down using Hal, is to install sudo. Then add the following line to {{Filename|/etc/sudoers}} using the {{Codeline|visudo -f}} 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 {{Codeline|'''user'''}} for your username and {{Codeline|'''hostname'''}} for the machine's hostname (you can use the {{Codeline|hostname}} 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.<br />
== The Modern Way: PolicyKit ==<br />
Start your X session by prepending {{Codeline|ck-launch-session}} to your session-start line in ~/.xinitrc<br />
exec ck-launch-session startxfce4<br />
Note that if you are using a display manager (KDM, GDM..) PolicyKit/ConsoleKit will be utilized automatically.<br />
<br />
The computer can now be shut down with:<br />
dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop<br />
and restarted with:<br />
dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart</div>
Cantabile