https://wiki.archlinux.org/api.php?action=feedcontributions&user=Foolishgrunt&feedformat=atom
ArchWiki - User contributions [en]
2024-03-29T12:19:40Z
User contributions
MediaWiki 1.41.0
https://wiki.archlinux.org/index.php?title=Talk:Firefox/Privacy&diff=516447
Talk:Firefox/Privacy
2018-04-08T03:52:06Z
<p>Foolishgrunt: /* Firefox 57+ incompatible extensions */ Vote</p>
<hr />
<div>Hey, I'm not an expert in privacy and browser security but I thought I'd get the ball rolling. If anyone could write some more detailed insights into cookies, scripts, etc that would be appreciated. Once/if more plugins are added we can begin to make sub catergories, eg: "Cookie Management", "Script/Plugin Management". <br />
<br />
Cheers,<br />
<br />
--[[User:MagickFox|MagickFox]] ([[User talk:MagickFox|talk]]) 13:52, 24 June 2012 (UTC)<br />
<br />
Check this site:<br />
https://panopticlick.eff.org<br />
Flash may track you using system fonts, to disable it:<br />
# echo DisableDeviceFontEnumeration = 1 >> /etc/adobe/mms.cfg<br />
The same problem should occur with Java<br />
another thing is to change the user agent to a more common one<br />
about:config -> general.useragent.override -> windows smth<br />
Are these suggestion worth in this page?<br />
[[User:Flu|Flu]] ([[User talk:Flu|talk]]) 19:22, 7 December 2012 (UTC)<br />
<br />
== Disable Geolocation ==<br />
<br />
Set {{ic|geo.enabled}} to {{ic|false}}. [[User:Pickfire|Pickfire]] ([[User talk:Pickfire|talk]]) 15:21, 25 November 2017 (UTC)<br />
<br />
== Firefox 57+ incompatible extensions ==<br />
<br />
Should we remove the legacy add-ons, wait for the release of 60 ESR, or for Firefox 52 EOL? I prefer to remove them now. Most users use the stable branch, which does not support these add-ons. Even ESR will be updated soon. And because all Firefox packages in the official repositories do not support WebExtensions, most Arch Linux users cannot use them, while they do clutter up this list.<br />
<br />
[[User:Aimilius|Aimilius]] ([[User talk:Aimilius|talk]]) 13:10, 5 April 2018 (UTC)<br />
<br />
:Those extensions will never get updated to support Firefox 57+, I vote for removing them. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 13:24, 5 April 2018 (UTC)<br />
<br />
:For the time being legacy addons are still usable on Waterfox and Palemoon, which are both available in AUR. Since neither of those browsers have their own Wiki pages, would it be worthwhile to keep the legacy addons here for the benefit of those users? --[[User:Foolishgrunt|Foolishgrunt]] ([[User talk:Foolishgrunt|talk]]) 03:52, 8 April 2018 (UTC)</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Firefox/Privacy&diff=507071
Firefox/Privacy
2018-01-12T22:54:07Z
<p>Foolishgrunt: /* RequestPolicy */ RequestPolicy -> RequestPolicy Continued</p>
<hr />
<div>[[Category:Web browser]]<br />
[[ja:Firefox プライバシー]]<br />
{{Related articles start}}<br />
{{Related|Firefox}}<br />
{{Related|Tor}}<br />
{{Related|Browser Plugins}}<br />
{{Related|Firefox/Tweaks}}<br />
{{Related|Firefox/Profile on RAM}}<br />
{{Related articles end}}<br />
<br />
This article overviews how to configure [[Firefox]] to enhance security and privacy.<br />
<br />
== Configuration tweaks ==<br />
<br />
The following are privacy-focused configuration tweaks to prevent [https://panopticlick.eff.org/ browser fingerprinting] and tracking.<br />
<br />
In addition, see the following links:<br />
<br />
* [https://support.mozilla.org/t5/Protect-your-privacy/How-to-stop-Firefox-from-making-automatic-connections/ta-p/1748 How to stop Firefox from making automatic connections] - Is an annotated list of corresponding Firefox functionality and settings to disable it case-by-case.<br />
* [https://ffprofile.com/ ffprofile.com] - You select which features you want to enable and disable and in the end you get a download link for a zip-file with your profile template. You can for example disable some functions, which send data to Mozilla and Google, or disable several annoying Firefox functions like Mozilla Hello or the Pocket integration. <br />
* [https://github.com/pyllyukko/user.js pyllyukko/user.js] - Firefox configuration hardening and documentation<br />
<br />
=== Enable Anti-Fingerprinting ===<br />
<br />
Mozilla has started an [https://wiki.mozilla.org/Security/Fingerprinting anti-fingerprinting project in Firefox], as part of a project to upstream features from [[Tor|Tor Browser]]. Many of these anti-fingerprinting features are enabled by setting {{ic|about:config}}:<br />
<br />
* {{ic|privacy.resistFingerprinting}} {{ic|true}}<br />
<br />
There is no user-facing documentation about this flag, and Mozilla doesn't recommend users enable it, since it will break a few websites (it exists mostly to make life easier for the Tor Browser developers). But it does automatically enable many of the features listed below (such as changing your reported timezone and user agent), as well as protection against other, lesser-known fingerprinting techniques. See the [https://bugzilla.mozilla.org/show_bug.cgi?id=1333933 tracking bug] that lists many of these features.<br />
<br />
=== Enable tracking protection ===<br />
<br />
Firefox gained an option for [https://support.mozilla.org/en-US/kb/tracking-protection-firefox tracking protection]. It can be enabled by setting {{ic|about:config}}:<br />
<br />
* {{ic|privacy.trackingprotection.enabled}} {{ic|true}}<br />
<br />
Apart from privacy benefits, enabling [http://venturebeat.com/2015/05/24/firefoxs-optional-tracking-protection-reduces-load-time-for-top-news-sites-by-44/ tracking protection] may also reduce load time by 44%.<br />
<br />
Note that this is not a replacement for ad blocking extensions such as [[#uBlock Origin]] and it may or may not work with [[List of applications/Internet#Firefox_spin-offs|Firefox forks]].<br />
<br />
=== Change browser time zone ===<br />
<br />
The time zone of your system can be used in browser fingerprinting. To set firefox's time zone to UTC launch it as:<br />
<br />
$ TZ=UTC firefox<br />
<br />
Or, set a script to launch the above (for example, at {{ic|/usr/local/bin/firefox}}).<br />
<br />
=== Change user agent and platform ===<br />
<br />
You can override Firefox's user agent with the {{ic|general.useragent.override}} preference in {{ic|about:config}}.<br />
<br />
The value for the key is your browser's user agent. Select a known common one.<br />
<br />
{{Tip|The value {{ic|Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0}} is used as the user agent for the Tor browser, thus being very common.}}<br />
<br />
{{Warning|Changing the user agent without changing to a corresponding platform will make your browser nearly unique.}}<br />
<br />
To change the platform for firefox, add the following {{ic|string}} key in {{ic|about:config}}:<br />
<br />
general.platform.override<br />
<br />
Select a known common platform that corresponds with your user agent.<br />
<br />
{{Tip|The value {{ic|Win32}} is used as the platform for the Tor browser, corresponding with the user agent provided above.}}<br />
<br />
=== WebRTC exposes LAN IP address ===<br />
<br />
To prevent websites from getting your local IP address via [[wikipedia:WebRTC|WebRTC]]'s peer-to-peer (and JavaScript), open {{ic|about:config}} and set:<br />
<br />
* {{ic|media.peerconnection.ice.default_address_only}} to {{ic|true}}<br />
* {{ic|media.peerconnection.enabled}} to {{ic|false}}. (only if you want to completely disable WebRTC)<br />
<br />
You can use this [http://net.ipcalf.com/ WebRTC test page] and [https://www.privacytools.io/webrtc.html WebRTC IP Leak VPN / Tor IP Test] to confirm that your internal/external IP address is no longer leaked.<br />
<br />
=== Disable 1024-bit Diffie-Hellman primes ===<br />
<br />
Following [https://freedom-to-tinker.com/blog/haldermanheninger/how-is-nsa-breaking-so-much-crypto/ recent research] it is likely that the NSA has been breaking 1024-bit Diffie-Hellman for some time now. To disable these switch the [https://www.eff.org/deeplinks/2015/10/how-to-protect-yourself-from-nsa-attacks-1024-bit-DH following] settings to {{ic|false}} in {{ic|about:config}}: <br />
<br />
security.ssl3.dhe_rsa_aes_128_sha<br />
security.ssl3.dhe_rsa_aes_256_sha<br />
<br />
Then consider checking your SSL configuration at https://www.howsmyssl.com/.<br />
<br />
=== Disable telemetry ===<br />
<br />
Set {{ic|toolkit.telemetry.enabled}} to {{ic|false}} and/or disable it under Preferences, Advanced, Data Choices.<br />
<br />
=== Enable Do Not Track Header (DNT) ===<br />
<br />
{{Note|The remote server may choose to not honour the Do Not Track request.}}<br />
<br />
Set {{ic|privacy.donottrackheader.enabled}} to {{ic|true}} or toggle it in ''Preferences > Privacy > Manage your Do Not Track settings''.<br />
<br />
=== Disable geolocation ===<br />
<br />
Set {{ic|geo.enabled}} to {{ic|false}} in {{ic|about:config}}.<br />
<br />
=== Disable Safe Browsing service ===<br />
<br />
Safe Browsing offers phishing protection and malware checks, however it may send user information (e.g. URL, file hashes, etc.) to third parties like Google.<br />
<br />
To disable the Safe Browsing service, in {{ic|about:config}} set: <br />
<br />
* {{ic|browser.safebrowsing.malware.enabled}} to {{ic|false}}<br />
* {{ic|browser.safebrowsing.phishing.enabled}} to {{ic|false}}<br />
<br />
In addition disable download checking, by setting {{ic|browser.safebrowsing.downloads.enabled}} to {{ic|false}}.<br />
<br />
=== Disable WebGL ===<br />
<br />
WebGL is a potential security risk.[http://security.stackexchange.com/questions/13799/is-webgl-a-security-concern] Set {{ic|webgl.disabled}} to {{ic|true}} in {{ic|about:config}} if you want to disable it.<br />
<br />
== Extensions ==<br />
<br />
=== HTTPS Everywhere ===<br />
<br />
[https://www.eff.org/https-everywhere HTTPS Everywhere] is an extension which encrypts your communication with a website. It forces a connection over HTTPS instead of HTTP wherever possible.<br />
<br />
HTTPS Everywhere will be automatically configured and enabled upon restarting Firefox. For information on how to set up your own rules for different websites please visit [https://www.eff.org/https-everywhere/rulesets the official website].<br />
<br />
{{Note|HTTPS Everywhere does not magically enable HTTPS for every site on the internet. The site needs to support HTTPS and HTTPS Everywhere should have a ruleset configured for that site.}}<br />
<br />
=== uBlock Origin ===<br />
<br />
uBlock Origin is a lightweight, efficient blocker which is easy on [https://github.com/gorhill/uBlock#performance memory and CPU]. It comes with several filter lists ready to use out-of-the-box (including EasyList, Peter Lowe's, several malware filter lists). <br />
<br />
The lead developer of uBlock forked the project and created uBlock Origin. As of July 2015, most of the development is being done on uBlock Origin and the codebases are deviating substantially.<br />
<br />
uBlock Origin: [https://github.com/gorhill/uBlock Github]; [https://addons.mozilla.org/firefox/addon/ublock-origin/ Firefox Add-ons].<br />
<br />
=== AdNauseam ===<br />
<br />
[https://adnauseam.io/ AdNauseam] is a lightweight browser extension that blends software tool and artware intervention to fight back against tracking by advertising networks. AdNauseam works like an ad-blocker (it is built atop uBlock-Origin) to silently simulate clicks on each blocked ad, confusing trackers as to one's real interests [https://github.com/dhowe/AdNauseam/].<br />
<br />
=== Adblock Plus ===<br />
<br />
[https://adblockplus.org/en/ Adblock Plus] was a popular extension to block ads. Now that it is not blocking some ads on purpose [https://adblockplus.org/acceptable-ads], it may be a better idea to use a different blocker like uBlock Origin.<br />
<br />
=== Privacy Badger ===<br />
<br />
[https://www.eff.org/privacybadger Privacy Badger] is an extension that monitors third-party trackers loaded with web content. It blocks trackers once they appear on different sites. It does not block advertisements in the first place, but since a lot of ads are served based on tracking information these are blocked as well. For more information on the mechanism, see its [https://www.eff.org/privacybadger#faq-How-is-Privacy-Badger-different-to-Disconnect,-Adblock-Plus,-Ghostery,-and-other-blocking-extensions? FAQ].<br />
<br />
=== Disconnect ===<br />
<br />
Disconnect is a open source project aimed at stopping 2,000 third-party sites from tracking a user. It encrypts data sent to popular sites and claims to loads web pages 27 percent faster. Disconnect shows its users, in real time, how many tracking attempts from Google, Twitter, Facebook, and more are stopped. It categorizes tracking attempts into advertising, analytical, social, and content, which makes it easy to monitor how one is being tracked.<br />
<br />
Disconnect can also stop side-jacking, which utilizes stolen cookies to steal personal data. It is easy to use and well supported. It can be added to Firefox at the [https://disconnect.me/ official website].<br />
<br />
{{Note|Firefox gained a feature based on the Disconnect list. See [[#Enable tracking protection]].}}<br />
<br />
=== NoScript ===<br />
<br />
[http://noscript.net/ NoScript] is an extension which disables JavaScript, Java, Flash and other plugins on any website not specifically whitelisted by the user. This extension will protect you from exploitation of security vulnerabilities by not letting anything but trusted sites (e.g: your bank, webmail) serve you executable content.<br />
<br />
Once installed you can configure settings for NoScript by either clicking its icon on the toolbar or right clicking a page and navigating to NoScript. You will then have the option to enable/disable scripts for the current page, as well as any third party scripts that the page is linking to. Alternatively you can choose to enable scripts temporarily for that session only.<br />
<br />
Be aware a lot of modern websites use scripts for layout purposes, hence content may look different. For example, failed rendering due to missing fonts might occur on websites that load fonts at runtime via scripts, which were blocked by NoScript.<br />
<br />
For more detailed configuration see the [http://noscript.net/faq NoScript FAQ].<br />
<br />
=== uMatrix ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/umatrix/ uMatrix] is forked and refactored from HTTP Switchboard. It allows you to selectively block Javascript, plugins or other resources and control third-party resources. It also features extensive privacy features like user-agent masquerading, referering blocking and so on. It effectively replaces NoScript and RequestPolicy. See the [https://github.com/gorhill/httpswitchboard/wiki/How-to-use-HTTP-Switchboard:-Two-opposing-views old HTTP Switchboard wiki] for different ways how to use it.<br />
<br />
For more Information visit the [https://github.com/gorhill/uMatrix project site].<br />
<br />
=== Cookie Monster ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/cookie-monster/ Cookie Monster] is a similar extension to NoScript but will the goal of managing cookies.<br />
<br />
From the preferences for Cookie Monster select "Block All Cookies". Once this is done, just as with NoScript, you can enable the use of cookies for specific pages from either the Cookie Monster icon on the toolbar or by right clicking the page and navigating to Cookie Monster. You have the option to accept cookies from the website in question or alternatively to only temporarily allow cookies for the current session.<br />
<br />
=== Cookie AutoDelete ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/cookie-autodelete/ Cookie AutoDelete] is an extension that deletes cookies as soon as the tab closes. Supports automatic and manual cookie cleaning modes. (Support for clearing LocalStorage was added in version 2.1, but only for Firefox versions 58+. The same release added support for first part isolation, but only for Firefox versions 59+).<br />
<br />
=== RefControl ===<br />
<br />
{{Remove|Not compatible with Firefox 57+}}<br />
<br />
[http://www.stardrifter.org/refcontrol/ RefControl] is an extension to control what gets sent as the HTTP Referer. Once installed RefControl can be configured so that no referer gets sent when navigating to a new webpage. This prevents the server from knowing which website you originated from.<br />
<br />
To do this open RefControl's preferences and change the setting for "Default for sites not listed:" to <Block>.<br />
<br />
{{Note|This extension has not been updated since 2014 and will not work with modern versions of Firefox. However Firefox now has native options to control emitted HTTP referers, possibly replacing plugins such as RefControl and Smart Referer. See [[Firefox tweaks#Referrer header control]].}}<br />
<br />
=== RequestPolicy ===<br />
<br />
[https://addons.mozilla.org/en-US/firefox/addon/requestpolicy-continued/ RequestPolicy Continued] (a successor to the original [https://addons.mozilla.org/en-US/firefox/addon/requestpolicy/ RequestPolicy]) is an extension for Mozilla browsers which lets you have control over cross-site requests. It also lets you blacklist or whitelist requests by default. Disabling unnecessary cross-site requests leads to better privacy, safety and faster browsing.<br />
<br />
{{Note|This addon is currently in the process of being updated for use on modern versions of Firefox (57+).}}<br />
<br />
=== Decentraleyes ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/decentraleyes/ Decentraleyes] protects you against tracking through "free", centralized, content delivery. It prevents a lot of requests from reaching networks like Google Hosted Libraries, and serves local files to keep sites from breaking. Complements regular content blockers.<br />
<br />
=== CanvasBlocker ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/canvasblocker/ CanvasBlocker] Blocks or fakes the JS-API for modifying <canvas> to prevent Canvas-Fingerprinting.</canvas><br />
<br />
{{Note|Mozilla is adding a built-in permission system to allow blocking of HTML5 canvas image track requests, [https://wiki.mozilla.org/Security/Fingerprinting targeted for release with verion 59].}}<br />
<br />
=== Random User Agent ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/random-agent-spoofer/ Random User Agent] rotates complete browser profiles (from real browsers/devices) at a user defined time interval. It includes many extra privacy enhancing options.<br />
<br />
=== Privacy Settings ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/privacy-settings/ Privacy Settings] provides a toolbar panel for easily altering Firefox's built-in privacy settings.<br />
<br />
=== Stop Fingerprinting ===<br />
<br />
{{Remove|Not compatible with Firefox 57+}}<br />
<br />
[https://addons.mozilla.org/firefox/addon/stop-fingerprinting/ Stop Fingerprinting] disables / modifies some browser APIs that would otherwise allow browser fingerprinting. However, this addon is not compatible with newer versions of Firefox (57+).<br />
<br />
== Remove system-wide hidden extensions ==<br />
<br />
Several extensions, hidden to the user, are installed by default in {{ic|/usr/lib/firefox/browser/features}}. Many can be safely removed via {{ic|rm ''extension-name''.xpi}} in order to completely remove unwanted features. Many of these extensions are not enabled by default and have a menu option for enabling or disabling. Note that any files removed will return upon update of the {{pkg|firefox}} package. Below are a few examples of these extensions and their features.<br />
<br />
* {{ic|activity-stream@mozilla.org.xpi}} - "Activity Stream" which replaces the new tab page. See [https://github.com/mozilla/activity-stream]<br />
<br />
* {{ic|firefox@getpocket.com.xpi}} - [https://getpocket.com/firefox/ Pocket]<br />
<br />
* {{ic|followonsearch@mozilla.com.xpi}} - Search telemetry. See also [[#Disable telemetry]].<br />
<br />
* {{ic|shield-recipe-client@mozilla.org.xpi}} [https://support.mozilla.org/en-US/kb/shield SHIELD studies]<br />
<br />
See also [https://dxr.mozilla.org/mozilla-release/source/browser/extensions/] for a full list of system extensions including README files describing their functions.</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Firefox/Privacy&diff=506884
Firefox/Privacy
2018-01-11T19:43:51Z
<p>Foolishgrunt: /* CanvasBlocker */ New native canvas blocking feature</p>
<hr />
<div>[[Category:Web browser]]<br />
[[ja:Firefox プライバシー]]<br />
{{Related articles start}}<br />
{{Related|Firefox}}<br />
{{Related|Tor}}<br />
{{Related|Browser Plugins}}<br />
{{Related|Firefox/Tweaks}}<br />
{{Related|Firefox/Profile on RAM}}<br />
{{Related articles end}}<br />
<br />
This article overviews configuration settings and some useful extensions which enhance security and privacy while using the [[Firefox]] web browser.<br />
<br />
== Configuration tweaks ==<br />
<br />
The following are privacy-focused configuration tweaks to prevent [https://panopticlick.eff.org/ browser fingerprinting] and tracking.<br />
<br />
In addition, see the following links:<br />
<br />
* [https://support.mozilla.org/t5/Protect-your-privacy/How-to-stop-Firefox-from-making-automatic-connections/ta-p/1748 How to stop Firefox from making automatic connections] - Is an annotated list of corresponding Firefox functionality and settings to disable it case-by-case.<br />
* [https://ffprofile.com/ ffprofile.com] - You select which features you want to enable and disable and in the end you get a download link for a zip-file with your profile template. You can for example disable some functions, which send data to Mozilla and Google, or disable several annoying Firefox functions like Mozilla Hello or the Pocket integration. <br />
* [https://github.com/pyllyukko/user.js pyllyukko/user.js] - Firefox configuration hardening and documentation<br />
<br />
=== Enable Anti-Fingerprinting ===<br />
<br />
Mozilla has started an [https://wiki.mozilla.org/Security/Fingerprinting anti-fingerprinting project in Firefox], as part of a project to upstream features from [[Tor|Tor Browser]]. Many of these anti-fingerprinting features are enabled by setting {{ic|about:config}}:<br />
<br />
* {{ic|privacy.resistFingerprinting}} {{ic|true}}<br />
<br />
There is no user-facing documentation about this flag, and Mozilla doesn't recommend users enable it, since it will break a few websites (it exists mostly to make life easier for the Tor Browser developers). But it does automatically enable many of the features listed below (such as changing your reported timezone and user agent), as well as protection against other, lesser-known fingerprinting techniques. See the [https://bugzilla.mozilla.org/show_bug.cgi?id=1333933 tracking bug] that lists many of these features.<br />
<br />
=== Enable tracking protection ===<br />
<br />
Firefox gained an option for [https://support.mozilla.org/en-US/kb/tracking-protection-firefox tracking protection]. It can be enabled by setting {{ic|about:config}}:<br />
<br />
* {{ic|privacy.trackingprotection.enabled}} {{ic|true}}<br />
<br />
Apart from privacy benefits, enabling [http://venturebeat.com/2015/05/24/firefoxs-optional-tracking-protection-reduces-load-time-for-top-news-sites-by-44/ tracking protection] may also reduce load time by 44%.<br />
<br />
Note that this is not a replacement for ad blocking extensions such as [[#uBlock Origin]] and it may or may not work with [[List of applications/Internet#Firefox_spin-offs|Firefox forks]].<br />
<br />
=== Change browser time zone ===<br />
<br />
The time zone of your system can be used in browser fingerprinting. To set firefox's time zone to UTC launch it as:<br />
<br />
$ TZ=UTC firefox<br />
<br />
Or, set a script to launch the above (for example, at {{ic|/usr/local/bin/firefox}}).<br />
<br />
=== Change user agent and platform ===<br />
<br />
You can override Firefox's user agent with the {{ic|general.useragent.override}} preference in {{ic|about:config}}.<br />
<br />
The value for the key is your browser's user agent. Select a known common one.<br />
<br />
{{Tip|The value {{ic|Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0}} is used as the user agent for the Tor browser, thus being very common.}}<br />
<br />
{{Warning|Changing the user agent without changing to a corresponding platform will make your browser nearly unique.}}<br />
<br />
To change the platform for firefox, add the following {{ic|string}} key in {{ic|about:config}}:<br />
<br />
general.platform.override<br />
<br />
Select a known common platform that corresponds with your user agent.<br />
<br />
{{Tip|The value {{ic|Win32}} is used as the platform for the Tor browser, corresponding with the user agent provided above.}}<br />
<br />
=== WebRTC exposes LAN IP address ===<br />
<br />
To prevent websites from getting your local IP address via [[wikipedia:WebRTC|WebRTC]]'s peer-to-peer (and JavaScript), open {{ic|about:config}} and set:<br />
<br />
* {{ic|media.peerconnection.ice.default_address_only}} to {{ic|true}}<br />
* {{ic|media.peerconnection.enabled}} to {{ic|false}}. (only if you want to completely disable WebRTC)<br />
<br />
You can use this [http://net.ipcalf.com/ WebRTC test page] and [https://www.privacytools.io/webrtc.html WebRTC IP Leak VPN / Tor IP Test] to confirm that your internal/external IP address is no longer leaked.<br />
<br />
=== Disable 1024-bit Diffie-Hellman primes ===<br />
<br />
Following [https://freedom-to-tinker.com/blog/haldermanheninger/how-is-nsa-breaking-so-much-crypto/ recent research] it is likely that the NSA has been breaking 1024-bit Diffie-Hellman for some time now. To disable these switch the [https://www.eff.org/deeplinks/2015/10/how-to-protect-yourself-from-nsa-attacks-1024-bit-DH following] settings to {{ic|false}} in {{ic|about:config}}: <br />
<br />
security.ssl3.dhe_rsa_aes_128_sha<br />
security.ssl3.dhe_rsa_aes_256_sha<br />
<br />
Then consider checking your SSL configuration at https://www.howsmyssl.com/.<br />
<br />
=== Disable telemetry ===<br />
<br />
Set {{ic|toolkit.telemetry.enabled}} to {{ic|false}} and/or disable it under Preferences, Advanced, Data Choices.<br />
<br />
=== Enable Do Not Track Header (DNT) ===<br />
<br />
{{Note|The remote server may choose to not honour the Do Not Track request.}}<br />
<br />
Set {{ic|privacy.donottrackheader.enabled}} to {{ic|true}} or toggle it in ''Preferences > Privacy > Manage your Do Not Track settings''.<br />
<br />
=== Disable geolocation ===<br />
<br />
Set {{ic|geo.enabled}} to {{ic|false}} in {{ic|about:config}}.<br />
<br />
=== Disable Safe Browsing service ===<br />
<br />
Safe Browsing offers phishing protection and malware checks, however it may send user information (e.g. URL, file hashes, etc.) to third parties like Google.<br />
<br />
To disable the Safe Browsing service, in {{ic|about:config}} set: <br />
<br />
* {{ic|browser.safebrowsing.malware.enabled}} to {{ic|false}}<br />
* {{ic|browser.safebrowsing.phishing.enabled}} to {{ic|false}}<br />
<br />
In addition disable download checking, by setting {{ic|browser.safebrowsing.downloads.enabled}} to {{ic|false}}.<br />
<br />
=== Disable WebGL ===<br />
<br />
WebGL is a potential security risk.[http://security.stackexchange.com/questions/13799/is-webgl-a-security-concern] Set {{ic|webgl.disabled}} to {{ic|true}} in {{ic|about:config}} if you want to disable it.<br />
<br />
== Extensions ==<br />
<br />
=== HTTPS Everywhere ===<br />
<br />
[https://www.eff.org/https-everywhere HTTPS Everywhere] is an extension which encrypts your communication with a website. It forces a connection over HTTPS instead of HTTP wherever possible.<br />
<br />
HTTPS Everywhere will be automatically configured and enabled upon restarting Firefox. For information on how to set up your own rules for different websites please visit [https://www.eff.org/https-everywhere/rulesets the official website].<br />
<br />
{{Note|HTTPS Everywhere does not magically enable HTTPS for every site on the internet. The site needs to support HTTPS and HTTPS Everywhere should have a ruleset configured for that site.}}<br />
<br />
=== uBlock Origin ===<br />
<br />
uBlock Origin is a lightweight, efficient blocker which is easy on [https://github.com/gorhill/uBlock#performance memory and CPU]. It comes with several filter lists ready to use out-of-the-box (including EasyList, Peter Lowe's, several malware filter lists). <br />
<br />
The lead developer of uBlock forked the project and created uBlock Origin. As of July 2015, most of the development is being done on uBlock Origin and the codebases are deviating substantially.<br />
<br />
uBlock Origin: [https://github.com/gorhill/uBlock Github]; [https://addons.mozilla.org/firefox/addon/ublock-origin/ Firefox Add-ons].<br />
<br />
=== AdNauseam ===<br />
<br />
[https://adnauseam.io/ AdNauseam] is a lightweight browser extension that blends software tool and artware intervention to fight back against tracking by advertising networks. AdNauseam works like an ad-blocker (it is built atop uBlock-Origin) to silently simulate clicks on each blocked ad, confusing trackers as to one's real interests [https://github.com/dhowe/AdNauseam/].<br />
<br />
=== Adblock Plus ===<br />
<br />
[https://adblockplus.org/en/ Adblock Plus] was a popular extension to block ads. Now that it is not blocking some ads on purpose [https://adblockplus.org/acceptable-ads], it may be a better idea to use a different blocker like uBlock Origin.<br />
<br />
=== Privacy Badger ===<br />
<br />
[https://www.eff.org/privacybadger Privacy Badger] is an extension that monitors third-party trackers loaded with web content. It blocks trackers once they appear on different sites. It does not block advertisements in the first place, but since a lot of ads are served based on tracking information these are blocked as well. For more information on the mechanism, see its [https://www.eff.org/privacybadger#faq-How-is-Privacy-Badger-different-to-Disconnect,-Adblock-Plus,-Ghostery,-and-other-blocking-extensions? FAQ].<br />
<br />
=== Disconnect ===<br />
<br />
Disconnect is a open source project aimed at stopping 2,000 third-party sites from tracking a user. It encrypts data sent to popular sites and claims to loads web pages 27 percent faster. Disconnect shows its users, in real time, how many tracking attempts from Google, Twitter, Facebook, and more are stopped. It categorizes tracking attempts into advertising, analytical, social, and content, which makes it easy to monitor how one is being tracked.<br />
<br />
Disconnect can also stop side-jacking, which utilizes stolen cookies to steal personal data. It is easy to use and well supported. It can be added to Firefox at the [https://disconnect.me/ official website].<br />
<br />
{{Note|Firefox gained a feature based on the Disconnect list. See [[#Enable tracking protection]].}}<br />
<br />
=== NoScript ===<br />
<br />
[http://noscript.net/ NoScript] is an extension which disables JavaScript, Java, Flash and other plugins on any website not specifically whitelisted by the user. This extension will protect you from exploitation of security vulnerabilities by not letting anything but trusted sites (e.g: your bank, webmail) serve you executable content.<br />
<br />
Once installed you can configure settings for NoScript by either clicking its icon on the toolbar or right clicking a page and navigating to NoScript. You will then have the option to enable/disable scripts for the current page, as well as any third party scripts that the page is linking to. Alternatively you can choose to enable scripts temporarily for that session only.<br />
<br />
Be aware a lot of modern websites use scripts for layout purposes, hence content may look different. For example, failed rendering due to missing fonts might occur on websites that load fonts at runtime via scripts, which were blocked by NoScript.<br />
<br />
For more detailed configuration see the [http://noscript.net/faq NoScript FAQ].<br />
<br />
=== uMatrix ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/umatrix/ uMatrix] is forked and refactored from HTTP Switchboard. It allows you to selectively block Javascript, plugins or other resources and control third-party resources. It also features extensive privacy features like user-agent masquerading, referering blocking and so on. It effectively replaces NoScript and RequestPolicy. See the [https://github.com/gorhill/httpswitchboard/wiki/How-to-use-HTTP-Switchboard:-Two-opposing-views old HTTP Switchboard wiki] for different ways how to use it.<br />
<br />
For more Information visit the [https://github.com/gorhill/uMatrix project site].<br />
<br />
=== Cookie Monster ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/cookie-monster/ Cookie Monster] is a similar extension to NoScript but will the goal of managing cookies.<br />
<br />
From the preferences for Cookie Monster select "Block All Cookies". Once this is done, just as with NoScript, you can enable the use of cookies for specific pages from either the Cookie Monster icon on the toolbar or by right clicking the page and navigating to Cookie Monster. You have the option to accept cookies from the website in question or alternatively to only temporarily allow cookies for the current session.<br />
<br />
=== Cookie AutoDelete ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/cookie-autodelete/ Cookie AutoDelete] is an extension that deletes cookies as soon as the tab closes. Supports automatic and manual cookie cleaning modes. (Support for clearing LocalStorage was added in version 2.1, [https://addons.mozilla.org/en-US/firefox/addon/cookie-autodelete/versions/ but only for Firefox versions 58+]. The same release added support for first part isolation, but only for Firefox versions 59+).<br />
<br />
=== RefControl ===<br />
<br />
[http://www.stardrifter.org/refcontrol/ RefControl] is an extension to control what gets sent as the HTTP Referer. Once installed RefControl can be configured so that no referer gets sent when navigating to a new webpage. This prevents the server from knowing which website you originated from.<br />
<br />
To do this open RefControl's preferences and change the setting for "Default for sites not listed:" to <Block>.<br />
<br />
{{Note|This extension has not been updated since 2014 and will not work with modern versions of Firefox. However Firefox now has native options to control emitted HTTP referers, possibly replacing plugins such as RefControl and Smart Referer. See [[Firefox tweaks#Referrer header control]].}}<br />
<br />
=== RequestPolicy ===<br />
<br />
[https://www.requestpolicy.com/ RequestPolicy] is an extension for Mozilla browsers which lets you have control over cross-site requests. The latest development version lets you blacklist or whitelist requests by default. Disabling unnecessary cross-site requests leads to better privacy, safety and faster browsing.<br />
<br />
For more information on cross-site requests and RequestPolicy visit [https://www.requestpolicy.com/faq.html here].<br />
<br />
=== Decentraleyes ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/decentraleyes/ Decentraleyes] protects you against tracking through "free", centralized, content delivery. It prevents a lot of requests from reaching networks like Google Hosted Libraries, and serves local files to keep sites from breaking. Complements regular content blockers.<br />
<br />
=== CanvasBlocker ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/canvasblocker/ CanvasBlocker] Blocks or fakes the JS-API for modifying <canvas> to prevent Canvas-Fingerprinting.</canvas><br />
<br />
{{Note|Mozilla is adding a built-in permission system to allow blocking of HTML5 canvas canvas image track requests, [https://wiki.mozilla.org/Security/Fingerprinting targeted for release with verion 59.]}}<br />
<br />
=== Random User Agent ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/random-agent-spoofer/ Random User Agent] rotates complete browser profiles (from real browsers/devices) at a user defined time interval. It includes many extra privacy enhancing options.<br />
<br />
=== Privacy Settings ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/privacy-settings/ Privacy Settings] provides a toolbar panel for easily altering Firefox's built-in privacy settings.<br />
<br />
=== Stop Fingerprinting ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/stop-fingerprinting/ Stop Fingerprinting] disables / modifies some browser APIs that would otherwise allow browser fingerprinting. However, this addon is not compatible with newer versions of Firefox (57+).<br />
<br />
== Remove system-wide hidden extensions ==<br />
<br />
Several extensions, hidden to the user, are installed by default in {{ic|/usr/lib/firefox/browser/features}}. Many can be safely removed via {{ic|rm ''extension-name''.xpi}} in order to completely remove unwanted features. Many of these extensions are not enabled by default and have a menu option for enabling or disabling. Note that any files removed will return upon update of the {{pkg|firefox}} package. Below are a few examples of these extensions and their features.<br />
<br />
* {{ic|activity-stream@mozilla.org.xpi}} - "Activity Stream" which replaces the new tab page. See [https://github.com/mozilla/activity-stream]<br />
<br />
* {{ic|firefox@getpocket.com.xpi}} - [https://getpocket.com/firefox/ Pocket]<br />
<br />
* {{ic|followonsearch@mozilla.com.xpi}} - Search telemetry. See also [[#Disable telemetry]].<br />
<br />
* {{ic|shield-recipe-client@mozilla.org.xpi}} [https://support.mozilla.org/en-US/kb/shield SHIELD studies]<br />
<br />
See also [https://dxr.mozilla.org/mozilla-release/source/browser/extensions/] for a full list of system extensions including README files describing their functions.</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Firefox/Privacy&diff=506882
Firefox/Privacy
2018-01-11T19:37:26Z
<p>Foolishgrunt: /* RefControl */ Plugin has apparently been abandoned.</p>
<hr />
<div>[[Category:Web browser]]<br />
[[ja:Firefox プライバシー]]<br />
{{Related articles start}}<br />
{{Related|Firefox}}<br />
{{Related|Tor}}<br />
{{Related|Browser Plugins}}<br />
{{Related|Firefox/Tweaks}}<br />
{{Related|Firefox/Profile on RAM}}<br />
{{Related articles end}}<br />
<br />
This article overviews configuration settings and some useful extensions which enhance security and privacy while using the [[Firefox]] web browser.<br />
<br />
== Configuration tweaks ==<br />
<br />
The following are privacy-focused configuration tweaks to prevent [https://panopticlick.eff.org/ browser fingerprinting] and tracking.<br />
<br />
In addition, see the following links:<br />
<br />
* [https://support.mozilla.org/t5/Protect-your-privacy/How-to-stop-Firefox-from-making-automatic-connections/ta-p/1748 How to stop Firefox from making automatic connections] - Is an annotated list of corresponding Firefox functionality and settings to disable it case-by-case.<br />
* [https://ffprofile.com/ ffprofile.com] - You select which features you want to enable and disable and in the end you get a download link for a zip-file with your profile template. You can for example disable some functions, which send data to Mozilla and Google, or disable several annoying Firefox functions like Mozilla Hello or the Pocket integration. <br />
* [https://github.com/pyllyukko/user.js pyllyukko/user.js] - Firefox configuration hardening and documentation<br />
<br />
=== Enable Anti-Fingerprinting ===<br />
<br />
Mozilla has started an [https://wiki.mozilla.org/Security/Fingerprinting anti-fingerprinting project in Firefox], as part of a project to upstream features from [[Tor|Tor Browser]]. Many of these anti-fingerprinting features are enabled by setting {{ic|about:config}}:<br />
<br />
* {{ic|privacy.resistFingerprinting}} {{ic|true}}<br />
<br />
There is no user-facing documentation about this flag, and Mozilla doesn't recommend users enable it, since it will break a few websites (it exists mostly to make life easier for the Tor Browser developers). But it does automatically enable many of the features listed below (such as changing your reported timezone and user agent), as well as protection against other, lesser-known fingerprinting techniques. See the [https://bugzilla.mozilla.org/show_bug.cgi?id=1333933 tracking bug] that lists many of these features.<br />
<br />
=== Enable tracking protection ===<br />
<br />
Firefox gained an option for [https://support.mozilla.org/en-US/kb/tracking-protection-firefox tracking protection]. It can be enabled by setting {{ic|about:config}}:<br />
<br />
* {{ic|privacy.trackingprotection.enabled}} {{ic|true}}<br />
<br />
Apart from privacy benefits, enabling [http://venturebeat.com/2015/05/24/firefoxs-optional-tracking-protection-reduces-load-time-for-top-news-sites-by-44/ tracking protection] may also reduce load time by 44%.<br />
<br />
Note that this is not a replacement for ad blocking extensions such as [[#uBlock Origin]] and it may or may not work with [[List of applications/Internet#Firefox_spin-offs|Firefox forks]].<br />
<br />
=== Change browser time zone ===<br />
<br />
The time zone of your system can be used in browser fingerprinting. To set firefox's time zone to UTC launch it as:<br />
<br />
$ TZ=UTC firefox<br />
<br />
Or, set a script to launch the above (for example, at {{ic|/usr/local/bin/firefox}}).<br />
<br />
=== Change user agent and platform ===<br />
<br />
You can override Firefox's user agent with the {{ic|general.useragent.override}} preference in {{ic|about:config}}.<br />
<br />
The value for the key is your browser's user agent. Select a known common one.<br />
<br />
{{Tip|The value {{ic|Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0}} is used as the user agent for the Tor browser, thus being very common.}}<br />
<br />
{{Warning|Changing the user agent without changing to a corresponding platform will make your browser nearly unique.}}<br />
<br />
To change the platform for firefox, add the following {{ic|string}} key in {{ic|about:config}}:<br />
<br />
general.platform.override<br />
<br />
Select a known common platform that corresponds with your user agent.<br />
<br />
{{Tip|The value {{ic|Win32}} is used as the platform for the Tor browser, corresponding with the user agent provided above.}}<br />
<br />
=== WebRTC exposes LAN IP address ===<br />
<br />
To prevent websites from getting your local IP address via [[wikipedia:WebRTC|WebRTC]]'s peer-to-peer (and JavaScript), open {{ic|about:config}} and set:<br />
<br />
* {{ic|media.peerconnection.ice.default_address_only}} to {{ic|true}}<br />
* {{ic|media.peerconnection.enabled}} to {{ic|false}}. (only if you want to completely disable WebRTC)<br />
<br />
You can use this [http://net.ipcalf.com/ WebRTC test page] and [https://www.privacytools.io/webrtc.html WebRTC IP Leak VPN / Tor IP Test] to confirm that your internal/external IP address is no longer leaked.<br />
<br />
=== Disable 1024-bit Diffie-Hellman primes ===<br />
<br />
Following [https://freedom-to-tinker.com/blog/haldermanheninger/how-is-nsa-breaking-so-much-crypto/ recent research] it is likely that the NSA has been breaking 1024-bit Diffie-Hellman for some time now. To disable these switch the [https://www.eff.org/deeplinks/2015/10/how-to-protect-yourself-from-nsa-attacks-1024-bit-DH following] settings to {{ic|false}} in {{ic|about:config}}: <br />
<br />
security.ssl3.dhe_rsa_aes_128_sha<br />
security.ssl3.dhe_rsa_aes_256_sha<br />
<br />
Then consider checking your SSL configuration at https://www.howsmyssl.com/.<br />
<br />
=== Disable telemetry ===<br />
<br />
Set {{ic|toolkit.telemetry.enabled}} to {{ic|false}} and/or disable it under Preferences, Advanced, Data Choices.<br />
<br />
=== Enable Do Not Track Header (DNT) ===<br />
<br />
{{Note|The remote server may choose to not honour the Do Not Track request.}}<br />
<br />
Set {{ic|privacy.donottrackheader.enabled}} to {{ic|true}} or toggle it in ''Preferences > Privacy > Manage your Do Not Track settings''.<br />
<br />
=== Disable geolocation ===<br />
<br />
Set {{ic|geo.enabled}} to {{ic|false}} in {{ic|about:config}}.<br />
<br />
=== Disable Safe Browsing service ===<br />
<br />
Safe Browsing offers phishing protection and malware checks, however it may send user information (e.g. URL, file hashes, etc.) to third parties like Google.<br />
<br />
To disable the Safe Browsing service, in {{ic|about:config}} set: <br />
<br />
* {{ic|browser.safebrowsing.malware.enabled}} to {{ic|false}}<br />
* {{ic|browser.safebrowsing.phishing.enabled}} to {{ic|false}}<br />
<br />
In addition disable download checking, by setting {{ic|browser.safebrowsing.downloads.enabled}} to {{ic|false}}.<br />
<br />
=== Disable WebGL ===<br />
<br />
WebGL is a potential security risk.[http://security.stackexchange.com/questions/13799/is-webgl-a-security-concern] Set {{ic|webgl.disabled}} to {{ic|true}} in {{ic|about:config}} if you want to disable it.<br />
<br />
== Extensions ==<br />
<br />
=== HTTPS Everywhere ===<br />
<br />
[https://www.eff.org/https-everywhere HTTPS Everywhere] is an extension which encrypts your communication with a website. It forces a connection over HTTPS instead of HTTP wherever possible.<br />
<br />
HTTPS Everywhere will be automatically configured and enabled upon restarting Firefox. For information on how to set up your own rules for different websites please visit [https://www.eff.org/https-everywhere/rulesets the official website].<br />
<br />
{{Note|HTTPS Everywhere does not magically enable HTTPS for every site on the internet. The site needs to support HTTPS and HTTPS Everywhere should have a ruleset configured for that site.}}<br />
<br />
=== uBlock Origin ===<br />
<br />
uBlock Origin is a lightweight, efficient blocker which is easy on [https://github.com/gorhill/uBlock#performance memory and CPU]. It comes with several filter lists ready to use out-of-the-box (including EasyList, Peter Lowe's, several malware filter lists). <br />
<br />
The lead developer of uBlock forked the project and created uBlock Origin. As of July 2015, most of the development is being done on uBlock Origin and the codebases are deviating substantially.<br />
<br />
uBlock Origin: [https://github.com/gorhill/uBlock Github]; [https://addons.mozilla.org/firefox/addon/ublock-origin/ Firefox Add-ons].<br />
<br />
=== AdNauseam ===<br />
<br />
[https://adnauseam.io/ AdNauseam] is a lightweight browser extension that blends software tool and artware intervention to fight back against tracking by advertising networks. AdNauseam works like an ad-blocker (it is built atop uBlock-Origin) to silently simulate clicks on each blocked ad, confusing trackers as to one's real interests [https://github.com/dhowe/AdNauseam/].<br />
<br />
=== Adblock Plus ===<br />
<br />
[https://adblockplus.org/en/ Adblock Plus] was a popular extension to block ads. Now that it is not blocking some ads on purpose [https://adblockplus.org/acceptable-ads], it may be a better idea to use a different blocker like uBlock Origin.<br />
<br />
=== Privacy Badger ===<br />
<br />
[https://www.eff.org/privacybadger Privacy Badger] is an extension that monitors third-party trackers loaded with web content. It blocks trackers once they appear on different sites. It does not block advertisements in the first place, but since a lot of ads are served based on tracking information these are blocked as well. For more information on the mechanism, see its [https://www.eff.org/privacybadger#faq-How-is-Privacy-Badger-different-to-Disconnect,-Adblock-Plus,-Ghostery,-and-other-blocking-extensions? FAQ].<br />
<br />
=== Disconnect ===<br />
<br />
Disconnect is a open source project aimed at stopping 2,000 third-party sites from tracking a user. It encrypts data sent to popular sites and claims to loads web pages 27 percent faster. Disconnect shows its users, in real time, how many tracking attempts from Google, Twitter, Facebook, and more are stopped. It categorizes tracking attempts into advertising, analytical, social, and content, which makes it easy to monitor how one is being tracked.<br />
<br />
Disconnect can also stop side-jacking, which utilizes stolen cookies to steal personal data. It is easy to use and well supported. It can be added to Firefox at the [https://disconnect.me/ official website].<br />
<br />
{{Note|Firefox gained a feature based on the Disconnect list. See [[#Enable tracking protection]].}}<br />
<br />
=== NoScript ===<br />
<br />
[http://noscript.net/ NoScript] is an extension which disables JavaScript, Java, Flash and other plugins on any website not specifically whitelisted by the user. This extension will protect you from exploitation of security vulnerabilities by not letting anything but trusted sites (e.g: your bank, webmail) serve you executable content.<br />
<br />
Once installed you can configure settings for NoScript by either clicking its icon on the toolbar or right clicking a page and navigating to NoScript. You will then have the option to enable/disable scripts for the current page, as well as any third party scripts that the page is linking to. Alternatively you can choose to enable scripts temporarily for that session only.<br />
<br />
Be aware a lot of modern websites use scripts for layout purposes, hence content may look different. For example, failed rendering due to missing fonts might occur on websites that load fonts at runtime via scripts, which were blocked by NoScript.<br />
<br />
For more detailed configuration see the [http://noscript.net/faq NoScript FAQ].<br />
<br />
=== uMatrix ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/umatrix/ uMatrix] is forked and refactored from HTTP Switchboard. It allows you to selectively block Javascript, plugins or other resources and control third-party resources. It also features extensive privacy features like user-agent masquerading, referering blocking and so on. It effectively replaces NoScript and RequestPolicy. See the [https://github.com/gorhill/httpswitchboard/wiki/How-to-use-HTTP-Switchboard:-Two-opposing-views old HTTP Switchboard wiki] for different ways how to use it.<br />
<br />
For more Information visit the [https://github.com/gorhill/uMatrix project site].<br />
<br />
=== Cookie Monster ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/cookie-monster/ Cookie Monster] is a similar extension to NoScript but will the goal of managing cookies.<br />
<br />
From the preferences for Cookie Monster select "Block All Cookies". Once this is done, just as with NoScript, you can enable the use of cookies for specific pages from either the Cookie Monster icon on the toolbar or by right clicking the page and navigating to Cookie Monster. You have the option to accept cookies from the website in question or alternatively to only temporarily allow cookies for the current session.<br />
<br />
=== Cookie AutoDelete ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/cookie-autodelete/ Cookie AutoDelete] is an extension that deletes cookies as soon as the tab closes. Supports automatic and manual cookie cleaning modes. (Support for clearing LocalStorage was added in version 2.1, [https://addons.mozilla.org/en-US/firefox/addon/cookie-autodelete/versions/ but only for Firefox versions 58+]. The same release added support for first part isolation, but only for Firefox versions 59+).<br />
<br />
=== RefControl ===<br />
<br />
[http://www.stardrifter.org/refcontrol/ RefControl] is an extension to control what gets sent as the HTTP Referer. Once installed RefControl can be configured so that no referer gets sent when navigating to a new webpage. This prevents the server from knowing which website you originated from.<br />
<br />
To do this open RefControl's preferences and change the setting for "Default for sites not listed:" to <Block>.<br />
<br />
{{Note|This extension has not been updated since 2014 and will not work with modern versions of Firefox. However Firefox now has native options to control emitted HTTP referers, possibly replacing plugins such as RefControl and Smart Referer. See [[Firefox tweaks#Referrer header control]].}}<br />
<br />
=== RequestPolicy ===<br />
<br />
[https://www.requestpolicy.com/ RequestPolicy] is an extension for Mozilla browsers which lets you have control over cross-site requests. The latest development version lets you blacklist or whitelist requests by default. Disabling unnecessary cross-site requests leads to better privacy, safety and faster browsing.<br />
<br />
For more information on cross-site requests and RequestPolicy visit [https://www.requestpolicy.com/faq.html here].<br />
<br />
=== Decentraleyes ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/decentraleyes/ Decentraleyes] protects you against tracking through "free", centralized, content delivery. It prevents a lot of requests from reaching networks like Google Hosted Libraries, and serves local files to keep sites from breaking. Complements regular content blockers.<br />
<br />
=== CanvasBlocker ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/canvasblocker/ CanvasBlocker] Blocks or fakes the JS-API for modifying <canvas> to prevent Canvas-Fingerprinting.</canvas><br />
<br />
=== Random User Agent ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/random-agent-spoofer/ Random User Agent] rotates complete browser profiles (from real browsers/devices) at a user defined time interval. It includes many extra privacy enhancing options.<br />
<br />
=== Privacy Settings ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/privacy-settings/ Privacy Settings] provides a toolbar panel for easily altering Firefox's built-in privacy settings.<br />
<br />
=== Stop Fingerprinting ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/stop-fingerprinting/ Stop Fingerprinting] disables / modifies some browser APIs that would otherwise allow browser fingerprinting. However, this addon is not compatible with newer versions of Firefox (57+).<br />
<br />
== Remove system-wide hidden extensions ==<br />
<br />
Several extensions, hidden to the user, are installed by default in {{ic|/usr/lib/firefox/browser/features}}. Many can be safely removed via {{ic|rm ''extension-name''.xpi}} in order to completely remove unwanted features. Many of these extensions are not enabled by default and have a menu option for enabling or disabling. Note that any files removed will return upon update of the {{pkg|firefox}} package. Below are a few examples of these extensions and their features.<br />
<br />
* {{ic|activity-stream@mozilla.org.xpi}} - "Activity Stream" which replaces the new tab page. See [https://github.com/mozilla/activity-stream]<br />
<br />
* {{ic|firefox@getpocket.com.xpi}} - [https://getpocket.com/firefox/ Pocket]<br />
<br />
* {{ic|followonsearch@mozilla.com.xpi}} - Search telemetry. See also [[#Disable telemetry]].<br />
<br />
* {{ic|shield-recipe-client@mozilla.org.xpi}} [https://support.mozilla.org/en-US/kb/shield SHIELD studies]<br />
<br />
See also [https://dxr.mozilla.org/mozilla-release/source/browser/extensions/] for a full list of system extensions including README files describing their functions.</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Firefox/Privacy&diff=506881
Firefox/Privacy
2018-01-11T19:33:44Z
<p>Foolishgrunt: /* Stop Fingerprinting */ Incompatible with WebExtensions.</p>
<hr />
<div>[[Category:Web browser]]<br />
[[ja:Firefox プライバシー]]<br />
{{Related articles start}}<br />
{{Related|Firefox}}<br />
{{Related|Tor}}<br />
{{Related|Browser Plugins}}<br />
{{Related|Firefox/Tweaks}}<br />
{{Related|Firefox/Profile on RAM}}<br />
{{Related articles end}}<br />
<br />
This article overviews configuration settings and some useful extensions which enhance security and privacy while using the [[Firefox]] web browser.<br />
<br />
== Configuration tweaks ==<br />
<br />
The following are privacy-focused configuration tweaks to prevent [https://panopticlick.eff.org/ browser fingerprinting] and tracking.<br />
<br />
In addition, see the following links:<br />
<br />
* [https://support.mozilla.org/t5/Protect-your-privacy/How-to-stop-Firefox-from-making-automatic-connections/ta-p/1748 How to stop Firefox from making automatic connections] - Is an annotated list of corresponding Firefox functionality and settings to disable it case-by-case.<br />
* [https://ffprofile.com/ ffprofile.com] - You select which features you want to enable and disable and in the end you get a download link for a zip-file with your profile template. You can for example disable some functions, which send data to Mozilla and Google, or disable several annoying Firefox functions like Mozilla Hello or the Pocket integration. <br />
* [https://github.com/pyllyukko/user.js pyllyukko/user.js] - Firefox configuration hardening and documentation<br />
<br />
=== Enable Anti-Fingerprinting ===<br />
<br />
Mozilla has started an [https://wiki.mozilla.org/Security/Fingerprinting anti-fingerprinting project in Firefox], as part of a project to upstream features from [[Tor|Tor Browser]]. Many of these anti-fingerprinting features are enabled by setting {{ic|about:config}}:<br />
<br />
* {{ic|privacy.resistFingerprinting}} {{ic|true}}<br />
<br />
There is no user-facing documentation about this flag, and Mozilla doesn't recommend users enable it, since it will break a few websites (it exists mostly to make life easier for the Tor Browser developers). But it does automatically enable many of the features listed below (such as changing your reported timezone and user agent), as well as protection against other, lesser-known fingerprinting techniques. See the [https://bugzilla.mozilla.org/show_bug.cgi?id=1333933 tracking bug] that lists many of these features.<br />
<br />
=== Enable tracking protection ===<br />
<br />
Firefox gained an option for [https://support.mozilla.org/en-US/kb/tracking-protection-firefox tracking protection]. It can be enabled by setting {{ic|about:config}}:<br />
<br />
* {{ic|privacy.trackingprotection.enabled}} {{ic|true}}<br />
<br />
Apart from privacy benefits, enabling [http://venturebeat.com/2015/05/24/firefoxs-optional-tracking-protection-reduces-load-time-for-top-news-sites-by-44/ tracking protection] may also reduce load time by 44%.<br />
<br />
Note that this is not a replacement for ad blocking extensions such as [[#uBlock Origin]] and it may or may not work with [[List of applications/Internet#Firefox_spin-offs|Firefox forks]].<br />
<br />
=== Change browser time zone ===<br />
<br />
The time zone of your system can be used in browser fingerprinting. To set firefox's time zone to UTC launch it as:<br />
<br />
$ TZ=UTC firefox<br />
<br />
Or, set a script to launch the above (for example, at {{ic|/usr/local/bin/firefox}}).<br />
<br />
=== Change user agent and platform ===<br />
<br />
You can override Firefox's user agent with the {{ic|general.useragent.override}} preference in {{ic|about:config}}.<br />
<br />
The value for the key is your browser's user agent. Select a known common one.<br />
<br />
{{Tip|The value {{ic|Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0}} is used as the user agent for the Tor browser, thus being very common.}}<br />
<br />
{{Warning|Changing the user agent without changing to a corresponding platform will make your browser nearly unique.}}<br />
<br />
To change the platform for firefox, add the following {{ic|string}} key in {{ic|about:config}}:<br />
<br />
general.platform.override<br />
<br />
Select a known common platform that corresponds with your user agent.<br />
<br />
{{Tip|The value {{ic|Win32}} is used as the platform for the Tor browser, corresponding with the user agent provided above.}}<br />
<br />
=== WebRTC exposes LAN IP address ===<br />
<br />
To prevent websites from getting your local IP address via [[wikipedia:WebRTC|WebRTC]]'s peer-to-peer (and JavaScript), open {{ic|about:config}} and set:<br />
<br />
* {{ic|media.peerconnection.ice.default_address_only}} to {{ic|true}}<br />
* {{ic|media.peerconnection.enabled}} to {{ic|false}}. (only if you want to completely disable WebRTC)<br />
<br />
You can use this [http://net.ipcalf.com/ WebRTC test page] and [https://www.privacytools.io/webrtc.html WebRTC IP Leak VPN / Tor IP Test] to confirm that your internal/external IP address is no longer leaked.<br />
<br />
=== Disable 1024-bit Diffie-Hellman primes ===<br />
<br />
Following [https://freedom-to-tinker.com/blog/haldermanheninger/how-is-nsa-breaking-so-much-crypto/ recent research] it is likely that the NSA has been breaking 1024-bit Diffie-Hellman for some time now. To disable these switch the [https://www.eff.org/deeplinks/2015/10/how-to-protect-yourself-from-nsa-attacks-1024-bit-DH following] settings to {{ic|false}} in {{ic|about:config}}: <br />
<br />
security.ssl3.dhe_rsa_aes_128_sha<br />
security.ssl3.dhe_rsa_aes_256_sha<br />
<br />
Then consider checking your SSL configuration at https://www.howsmyssl.com/.<br />
<br />
=== Disable telemetry ===<br />
<br />
Set {{ic|toolkit.telemetry.enabled}} to {{ic|false}} and/or disable it under Preferences, Advanced, Data Choices.<br />
<br />
=== Enable Do Not Track Header (DNT) ===<br />
<br />
{{Note|The remote server may choose to not honour the Do Not Track request.}}<br />
<br />
Set {{ic|privacy.donottrackheader.enabled}} to {{ic|true}} or toggle it in ''Preferences > Privacy > Manage your Do Not Track settings''.<br />
<br />
=== Disable geolocation ===<br />
<br />
Set {{ic|geo.enabled}} to {{ic|false}} in {{ic|about:config}}.<br />
<br />
=== Disable Safe Browsing service ===<br />
<br />
Safe Browsing offers phishing protection and malware checks, however it may send user information (e.g. URL, file hashes, etc.) to third parties like Google.<br />
<br />
To disable the Safe Browsing service, in {{ic|about:config}} set: <br />
<br />
* {{ic|browser.safebrowsing.malware.enabled}} to {{ic|false}}<br />
* {{ic|browser.safebrowsing.phishing.enabled}} to {{ic|false}}<br />
<br />
In addition disable download checking, by setting {{ic|browser.safebrowsing.downloads.enabled}} to {{ic|false}}.<br />
<br />
=== Disable WebGL ===<br />
<br />
WebGL is a potential security risk.[http://security.stackexchange.com/questions/13799/is-webgl-a-security-concern] Set {{ic|webgl.disabled}} to {{ic|true}} in {{ic|about:config}} if you want to disable it.<br />
<br />
== Extensions ==<br />
<br />
=== HTTPS Everywhere ===<br />
<br />
[https://www.eff.org/https-everywhere HTTPS Everywhere] is an extension which encrypts your communication with a website. It forces a connection over HTTPS instead of HTTP wherever possible.<br />
<br />
HTTPS Everywhere will be automatically configured and enabled upon restarting Firefox. For information on how to set up your own rules for different websites please visit [https://www.eff.org/https-everywhere/rulesets the official website].<br />
<br />
{{Note|HTTPS Everywhere does not magically enable HTTPS for every site on the internet. The site needs to support HTTPS and HTTPS Everywhere should have a ruleset configured for that site.}}<br />
<br />
=== uBlock Origin ===<br />
<br />
uBlock Origin is a lightweight, efficient blocker which is easy on [https://github.com/gorhill/uBlock#performance memory and CPU]. It comes with several filter lists ready to use out-of-the-box (including EasyList, Peter Lowe's, several malware filter lists). <br />
<br />
The lead developer of uBlock forked the project and created uBlock Origin. As of July 2015, most of the development is being done on uBlock Origin and the codebases are deviating substantially.<br />
<br />
uBlock Origin: [https://github.com/gorhill/uBlock Github]; [https://addons.mozilla.org/firefox/addon/ublock-origin/ Firefox Add-ons].<br />
<br />
=== AdNauseam ===<br />
<br />
[https://adnauseam.io/ AdNauseam] is a lightweight browser extension that blends software tool and artware intervention to fight back against tracking by advertising networks. AdNauseam works like an ad-blocker (it is built atop uBlock-Origin) to silently simulate clicks on each blocked ad, confusing trackers as to one's real interests [https://github.com/dhowe/AdNauseam/].<br />
<br />
=== Adblock Plus ===<br />
<br />
[https://adblockplus.org/en/ Adblock Plus] was a popular extension to block ads. Now that it is not blocking some ads on purpose [https://adblockplus.org/acceptable-ads], it may be a better idea to use a different blocker like uBlock Origin.<br />
<br />
=== Privacy Badger ===<br />
<br />
[https://www.eff.org/privacybadger Privacy Badger] is an extension that monitors third-party trackers loaded with web content. It blocks trackers once they appear on different sites. It does not block advertisements in the first place, but since a lot of ads are served based on tracking information these are blocked as well. For more information on the mechanism, see its [https://www.eff.org/privacybadger#faq-How-is-Privacy-Badger-different-to-Disconnect,-Adblock-Plus,-Ghostery,-and-other-blocking-extensions? FAQ].<br />
<br />
=== Disconnect ===<br />
<br />
Disconnect is a open source project aimed at stopping 2,000 third-party sites from tracking a user. It encrypts data sent to popular sites and claims to loads web pages 27 percent faster. Disconnect shows its users, in real time, how many tracking attempts from Google, Twitter, Facebook, and more are stopped. It categorizes tracking attempts into advertising, analytical, social, and content, which makes it easy to monitor how one is being tracked.<br />
<br />
Disconnect can also stop side-jacking, which utilizes stolen cookies to steal personal data. It is easy to use and well supported. It can be added to Firefox at the [https://disconnect.me/ official website].<br />
<br />
{{Note|Firefox gained a feature based on the Disconnect list. See [[#Enable tracking protection]].}}<br />
<br />
=== NoScript ===<br />
<br />
[http://noscript.net/ NoScript] is an extension which disables JavaScript, Java, Flash and other plugins on any website not specifically whitelisted by the user. This extension will protect you from exploitation of security vulnerabilities by not letting anything but trusted sites (e.g: your bank, webmail) serve you executable content.<br />
<br />
Once installed you can configure settings for NoScript by either clicking its icon on the toolbar or right clicking a page and navigating to NoScript. You will then have the option to enable/disable scripts for the current page, as well as any third party scripts that the page is linking to. Alternatively you can choose to enable scripts temporarily for that session only.<br />
<br />
Be aware a lot of modern websites use scripts for layout purposes, hence content may look different. For example, failed rendering due to missing fonts might occur on websites that load fonts at runtime via scripts, which were blocked by NoScript.<br />
<br />
For more detailed configuration see the [http://noscript.net/faq NoScript FAQ].<br />
<br />
=== uMatrix ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/umatrix/ uMatrix] is forked and refactored from HTTP Switchboard. It allows you to selectively block Javascript, plugins or other resources and control third-party resources. It also features extensive privacy features like user-agent masquerading, referering blocking and so on. It effectively replaces NoScript and RequestPolicy. See the [https://github.com/gorhill/httpswitchboard/wiki/How-to-use-HTTP-Switchboard:-Two-opposing-views old HTTP Switchboard wiki] for different ways how to use it.<br />
<br />
For more Information visit the [https://github.com/gorhill/uMatrix project site].<br />
<br />
=== Cookie Monster ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/cookie-monster/ Cookie Monster] is a similar extension to NoScript but will the goal of managing cookies.<br />
<br />
From the preferences for Cookie Monster select "Block All Cookies". Once this is done, just as with NoScript, you can enable the use of cookies for specific pages from either the Cookie Monster icon on the toolbar or by right clicking the page and navigating to Cookie Monster. You have the option to accept cookies from the website in question or alternatively to only temporarily allow cookies for the current session.<br />
<br />
=== Cookie AutoDelete ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/cookie-autodelete/ Cookie AutoDelete] is an extension that deletes cookies as soon as the tab closes. Supports automatic and manual cookie cleaning modes. (Support for clearing LocalStorage was added in version 2.1, [https://addons.mozilla.org/en-US/firefox/addon/cookie-autodelete/versions/ but only for Firefox versions 58+]. The same release added support for first part isolation, but only for Firefox versions 59+).<br />
<br />
=== RefControl ===<br />
<br />
[http://www.stardrifter.org/refcontrol/ RefControl] is an extension to control what gets sent as the HTTP Referer. Once installed RefControl can be configured so that no referer gets sent when navigating to a new webpage. This prevents the server from knowing which website you originated from.<br />
<br />
To do this open RefControl's preferences and change the setting for "Default for sites not listed:" to <Block>.<br />
<br />
{{Note|Firefox has options to control emitted HTTP referers, possibly replacing plugins such as RefControl and Smart Referer. See [[Firefox tweaks#Referrer header control]].}}<br />
<br />
=== RequestPolicy ===<br />
<br />
[https://www.requestpolicy.com/ RequestPolicy] is an extension for Mozilla browsers which lets you have control over cross-site requests. The latest development version lets you blacklist or whitelist requests by default. Disabling unnecessary cross-site requests leads to better privacy, safety and faster browsing.<br />
<br />
For more information on cross-site requests and RequestPolicy visit [https://www.requestpolicy.com/faq.html here].<br />
<br />
=== Decentraleyes ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/decentraleyes/ Decentraleyes] protects you against tracking through "free", centralized, content delivery. It prevents a lot of requests from reaching networks like Google Hosted Libraries, and serves local files to keep sites from breaking. Complements regular content blockers.<br />
<br />
=== CanvasBlocker ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/canvasblocker/ CanvasBlocker] Blocks or fakes the JS-API for modifying <canvas> to prevent Canvas-Fingerprinting.</canvas><br />
<br />
=== Random User Agent ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/random-agent-spoofer/ Random User Agent] rotates complete browser profiles (from real browsers/devices) at a user defined time interval. It includes many extra privacy enhancing options.<br />
<br />
=== Privacy Settings ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/privacy-settings/ Privacy Settings] provides a toolbar panel for easily altering Firefox's built-in privacy settings.<br />
<br />
=== Stop Fingerprinting ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/stop-fingerprinting/ Stop Fingerprinting] disables / modifies some browser APIs that would otherwise allow browser fingerprinting. However, this addon is not compatible with newer versions of Firefox (57+).<br />
<br />
== Remove system-wide hidden extensions ==<br />
<br />
Several extensions, hidden to the user, are installed by default in {{ic|/usr/lib/firefox/browser/features}}. Many can be safely removed via {{ic|rm ''extension-name''.xpi}} in order to completely remove unwanted features. Many of these extensions are not enabled by default and have a menu option for enabling or disabling. Note that any files removed will return upon update of the {{pkg|firefox}} package. Below are a few examples of these extensions and their features.<br />
<br />
* {{ic|activity-stream@mozilla.org.xpi}} - "Activity Stream" which replaces the new tab page. See [https://github.com/mozilla/activity-stream]<br />
<br />
* {{ic|firefox@getpocket.com.xpi}} - [https://getpocket.com/firefox/ Pocket]<br />
<br />
* {{ic|followonsearch@mozilla.com.xpi}} - Search telemetry. See also [[#Disable telemetry]].<br />
<br />
* {{ic|shield-recipe-client@mozilla.org.xpi}} [https://support.mozilla.org/en-US/kb/shield SHIELD studies]<br />
<br />
See also [https://dxr.mozilla.org/mozilla-release/source/browser/extensions/] for a full list of system extensions including README files describing their functions.</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Firefox/Privacy&diff=506878
Firefox/Privacy
2018-01-11T19:30:48Z
<p>Foolishgrunt: /* Cookie AutoDelete */ Updated new features</p>
<hr />
<div>[[Category:Web browser]]<br />
[[ja:Firefox プライバシー]]<br />
{{Related articles start}}<br />
{{Related|Firefox}}<br />
{{Related|Tor}}<br />
{{Related|Browser Plugins}}<br />
{{Related|Firefox/Tweaks}}<br />
{{Related|Firefox/Profile on RAM}}<br />
{{Related articles end}}<br />
<br />
This article overviews configuration settings and some useful extensions which enhance security and privacy while using the [[Firefox]] web browser.<br />
<br />
== Configuration tweaks ==<br />
<br />
The following are privacy-focused configuration tweaks to prevent [https://panopticlick.eff.org/ browser fingerprinting] and tracking.<br />
<br />
In addition, see the following links:<br />
<br />
* [https://support.mozilla.org/t5/Protect-your-privacy/How-to-stop-Firefox-from-making-automatic-connections/ta-p/1748 How to stop Firefox from making automatic connections] - Is an annotated list of corresponding Firefox functionality and settings to disable it case-by-case.<br />
* [https://ffprofile.com/ ffprofile.com] - You select which features you want to enable and disable and in the end you get a download link for a zip-file with your profile template. You can for example disable some functions, which send data to Mozilla and Google, or disable several annoying Firefox functions like Mozilla Hello or the Pocket integration. <br />
* [https://github.com/pyllyukko/user.js pyllyukko/user.js] - Firefox configuration hardening and documentation<br />
<br />
=== Enable Anti-Fingerprinting ===<br />
<br />
Mozilla has started an [https://wiki.mozilla.org/Security/Fingerprinting anti-fingerprinting project in Firefox], as part of a project to upstream features from [[Tor|Tor Browser]]. Many of these anti-fingerprinting features are enabled by setting {{ic|about:config}}:<br />
<br />
* {{ic|privacy.resistFingerprinting}} {{ic|true}}<br />
<br />
There is no user-facing documentation about this flag, and Mozilla doesn't recommend users enable it, since it will break a few websites (it exists mostly to make life easier for the Tor Browser developers). But it does automatically enable many of the features listed below (such as changing your reported timezone and user agent), as well as protection against other, lesser-known fingerprinting techniques. See the [https://bugzilla.mozilla.org/show_bug.cgi?id=1333933 tracking bug] that lists many of these features.<br />
<br />
=== Enable tracking protection ===<br />
<br />
Firefox gained an option for [https://support.mozilla.org/en-US/kb/tracking-protection-firefox tracking protection]. It can be enabled by setting {{ic|about:config}}:<br />
<br />
* {{ic|privacy.trackingprotection.enabled}} {{ic|true}}<br />
<br />
Apart from privacy benefits, enabling [http://venturebeat.com/2015/05/24/firefoxs-optional-tracking-protection-reduces-load-time-for-top-news-sites-by-44/ tracking protection] may also reduce load time by 44%.<br />
<br />
Note that this is not a replacement for ad blocking extensions such as [[#uBlock Origin]] and it may or may not work with [[List of applications/Internet#Firefox_spin-offs|Firefox forks]].<br />
<br />
=== Change browser time zone ===<br />
<br />
The time zone of your system can be used in browser fingerprinting. To set firefox's time zone to UTC launch it as:<br />
<br />
$ TZ=UTC firefox<br />
<br />
Or, set a script to launch the above (for example, at {{ic|/usr/local/bin/firefox}}).<br />
<br />
=== Change user agent and platform ===<br />
<br />
You can override Firefox's user agent with the {{ic|general.useragent.override}} preference in {{ic|about:config}}.<br />
<br />
The value for the key is your browser's user agent. Select a known common one.<br />
<br />
{{Tip|The value {{ic|Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0}} is used as the user agent for the Tor browser, thus being very common.}}<br />
<br />
{{Warning|Changing the user agent without changing to a corresponding platform will make your browser nearly unique.}}<br />
<br />
To change the platform for firefox, add the following {{ic|string}} key in {{ic|about:config}}:<br />
<br />
general.platform.override<br />
<br />
Select a known common platform that corresponds with your user agent.<br />
<br />
{{Tip|The value {{ic|Win32}} is used as the platform for the Tor browser, corresponding with the user agent provided above.}}<br />
<br />
=== WebRTC exposes LAN IP address ===<br />
<br />
To prevent websites from getting your local IP address via [[wikipedia:WebRTC|WebRTC]]'s peer-to-peer (and JavaScript), open {{ic|about:config}} and set:<br />
<br />
* {{ic|media.peerconnection.ice.default_address_only}} to {{ic|true}}<br />
* {{ic|media.peerconnection.enabled}} to {{ic|false}}. (only if you want to completely disable WebRTC)<br />
<br />
You can use this [http://net.ipcalf.com/ WebRTC test page] and [https://www.privacytools.io/webrtc.html WebRTC IP Leak VPN / Tor IP Test] to confirm that your internal/external IP address is no longer leaked.<br />
<br />
=== Disable 1024-bit Diffie-Hellman primes ===<br />
<br />
Following [https://freedom-to-tinker.com/blog/haldermanheninger/how-is-nsa-breaking-so-much-crypto/ recent research] it is likely that the NSA has been breaking 1024-bit Diffie-Hellman for some time now. To disable these switch the [https://www.eff.org/deeplinks/2015/10/how-to-protect-yourself-from-nsa-attacks-1024-bit-DH following] settings to {{ic|false}} in {{ic|about:config}}: <br />
<br />
security.ssl3.dhe_rsa_aes_128_sha<br />
security.ssl3.dhe_rsa_aes_256_sha<br />
<br />
Then consider checking your SSL configuration at https://www.howsmyssl.com/.<br />
<br />
=== Disable telemetry ===<br />
<br />
Set {{ic|toolkit.telemetry.enabled}} to {{ic|false}} and/or disable it under Preferences, Advanced, Data Choices.<br />
<br />
=== Enable Do Not Track Header (DNT) ===<br />
<br />
{{Note|The remote server may choose to not honour the Do Not Track request.}}<br />
<br />
Set {{ic|privacy.donottrackheader.enabled}} to {{ic|true}} or toggle it in ''Preferences > Privacy > Manage your Do Not Track settings''.<br />
<br />
=== Disable geolocation ===<br />
<br />
Set {{ic|geo.enabled}} to {{ic|false}} in {{ic|about:config}}.<br />
<br />
=== Disable Safe Browsing service ===<br />
<br />
Safe Browsing offers phishing protection and malware checks, however it may send user information (e.g. URL, file hashes, etc.) to third parties like Google.<br />
<br />
To disable the Safe Browsing service, in {{ic|about:config}} set: <br />
<br />
* {{ic|browser.safebrowsing.malware.enabled}} to {{ic|false}}<br />
* {{ic|browser.safebrowsing.phishing.enabled}} to {{ic|false}}<br />
<br />
In addition disable download checking, by setting {{ic|browser.safebrowsing.downloads.enabled}} to {{ic|false}}.<br />
<br />
=== Disable WebGL ===<br />
<br />
WebGL is a potential security risk.[http://security.stackexchange.com/questions/13799/is-webgl-a-security-concern] Set {{ic|webgl.disabled}} to {{ic|true}} in {{ic|about:config}} if you want to disable it.<br />
<br />
== Extensions ==<br />
<br />
=== HTTPS Everywhere ===<br />
<br />
[https://www.eff.org/https-everywhere HTTPS Everywhere] is an extension which encrypts your communication with a website. It forces a connection over HTTPS instead of HTTP wherever possible.<br />
<br />
HTTPS Everywhere will be automatically configured and enabled upon restarting Firefox. For information on how to set up your own rules for different websites please visit [https://www.eff.org/https-everywhere/rulesets the official website].<br />
<br />
{{Note|HTTPS Everywhere does not magically enable HTTPS for every site on the internet. The site needs to support HTTPS and HTTPS Everywhere should have a ruleset configured for that site.}}<br />
<br />
=== uBlock Origin ===<br />
<br />
uBlock Origin is a lightweight, efficient blocker which is easy on [https://github.com/gorhill/uBlock#performance memory and CPU]. It comes with several filter lists ready to use out-of-the-box (including EasyList, Peter Lowe's, several malware filter lists). <br />
<br />
The lead developer of uBlock forked the project and created uBlock Origin. As of July 2015, most of the development is being done on uBlock Origin and the codebases are deviating substantially.<br />
<br />
uBlock Origin: [https://github.com/gorhill/uBlock Github]; [https://addons.mozilla.org/firefox/addon/ublock-origin/ Firefox Add-ons].<br />
<br />
=== AdNauseam ===<br />
<br />
[https://adnauseam.io/ AdNauseam] is a lightweight browser extension that blends software tool and artware intervention to fight back against tracking by advertising networks. AdNauseam works like an ad-blocker (it is built atop uBlock-Origin) to silently simulate clicks on each blocked ad, confusing trackers as to one's real interests [https://github.com/dhowe/AdNauseam/].<br />
<br />
=== Adblock Plus ===<br />
<br />
[https://adblockplus.org/en/ Adblock Plus] was a popular extension to block ads. Now that it is not blocking some ads on purpose [https://adblockplus.org/acceptable-ads], it may be a better idea to use a different blocker like uBlock Origin.<br />
<br />
=== Privacy Badger ===<br />
<br />
[https://www.eff.org/privacybadger Privacy Badger] is an extension that monitors third-party trackers loaded with web content. It blocks trackers once they appear on different sites. It does not block advertisements in the first place, but since a lot of ads are served based on tracking information these are blocked as well. For more information on the mechanism, see its [https://www.eff.org/privacybadger#faq-How-is-Privacy-Badger-different-to-Disconnect,-Adblock-Plus,-Ghostery,-and-other-blocking-extensions? FAQ].<br />
<br />
=== Disconnect ===<br />
<br />
Disconnect is a open source project aimed at stopping 2,000 third-party sites from tracking a user. It encrypts data sent to popular sites and claims to loads web pages 27 percent faster. Disconnect shows its users, in real time, how many tracking attempts from Google, Twitter, Facebook, and more are stopped. It categorizes tracking attempts into advertising, analytical, social, and content, which makes it easy to monitor how one is being tracked.<br />
<br />
Disconnect can also stop side-jacking, which utilizes stolen cookies to steal personal data. It is easy to use and well supported. It can be added to Firefox at the [https://disconnect.me/ official website].<br />
<br />
{{Note|Firefox gained a feature based on the Disconnect list. See [[#Enable tracking protection]].}}<br />
<br />
=== NoScript ===<br />
<br />
[http://noscript.net/ NoScript] is an extension which disables JavaScript, Java, Flash and other plugins on any website not specifically whitelisted by the user. This extension will protect you from exploitation of security vulnerabilities by not letting anything but trusted sites (e.g: your bank, webmail) serve you executable content.<br />
<br />
Once installed you can configure settings for NoScript by either clicking its icon on the toolbar or right clicking a page and navigating to NoScript. You will then have the option to enable/disable scripts for the current page, as well as any third party scripts that the page is linking to. Alternatively you can choose to enable scripts temporarily for that session only.<br />
<br />
Be aware a lot of modern websites use scripts for layout purposes, hence content may look different. For example, failed rendering due to missing fonts might occur on websites that load fonts at runtime via scripts, which were blocked by NoScript.<br />
<br />
For more detailed configuration see the [http://noscript.net/faq NoScript FAQ].<br />
<br />
=== uMatrix ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/umatrix/ uMatrix] is forked and refactored from HTTP Switchboard. It allows you to selectively block Javascript, plugins or other resources and control third-party resources. It also features extensive privacy features like user-agent masquerading, referering blocking and so on. It effectively replaces NoScript and RequestPolicy. See the [https://github.com/gorhill/httpswitchboard/wiki/How-to-use-HTTP-Switchboard:-Two-opposing-views old HTTP Switchboard wiki] for different ways how to use it.<br />
<br />
For more Information visit the [https://github.com/gorhill/uMatrix project site].<br />
<br />
=== Cookie Monster ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/cookie-monster/ Cookie Monster] is a similar extension to NoScript but will the goal of managing cookies.<br />
<br />
From the preferences for Cookie Monster select "Block All Cookies". Once this is done, just as with NoScript, you can enable the use of cookies for specific pages from either the Cookie Monster icon on the toolbar or by right clicking the page and navigating to Cookie Monster. You have the option to accept cookies from the website in question or alternatively to only temporarily allow cookies for the current session.<br />
<br />
=== Cookie AutoDelete ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/cookie-autodelete/ Cookie AutoDelete] is an extension that deletes cookies as soon as the tab closes. Supports automatic and manual cookie cleaning modes. (Support for clearing LocalStorage was added in version 2.1, [https://addons.mozilla.org/en-US/firefox/addon/cookie-autodelete/versions/ but only for Firefox versions 58+]. The same release added support for first part isolation, but only for Firefox versions 59+).<br />
<br />
=== RefControl ===<br />
<br />
[http://www.stardrifter.org/refcontrol/ RefControl] is an extension to control what gets sent as the HTTP Referer. Once installed RefControl can be configured so that no referer gets sent when navigating to a new webpage. This prevents the server from knowing which website you originated from.<br />
<br />
To do this open RefControl's preferences and change the setting for "Default for sites not listed:" to <Block>.<br />
<br />
{{Note|Firefox has options to control emitted HTTP referers, possibly replacing plugins such as RefControl and Smart Referer. See [[Firefox tweaks#Referrer header control]].}}<br />
<br />
=== RequestPolicy ===<br />
<br />
[https://www.requestpolicy.com/ RequestPolicy] is an extension for Mozilla browsers which lets you have control over cross-site requests. The latest development version lets you blacklist or whitelist requests by default. Disabling unnecessary cross-site requests leads to better privacy, safety and faster browsing.<br />
<br />
For more information on cross-site requests and RequestPolicy visit [https://www.requestpolicy.com/faq.html here].<br />
<br />
=== Decentraleyes ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/decentraleyes/ Decentraleyes] protects you against tracking through "free", centralized, content delivery. It prevents a lot of requests from reaching networks like Google Hosted Libraries, and serves local files to keep sites from breaking. Complements regular content blockers.<br />
<br />
=== CanvasBlocker ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/canvasblocker/ CanvasBlocker] Blocks or fakes the JS-API for modifying <canvas> to prevent Canvas-Fingerprinting.</canvas><br />
<br />
=== Random User Agent ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/random-agent-spoofer/ Random User Agent] rotates complete browser profiles (from real browsers/devices) at a user defined time interval. It includes many extra privacy enhancing options.<br />
<br />
=== Privacy Settings ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/privacy-settings/ Privacy Settings] provides a toolbar panel for easily altering Firefox's built-in privacy settings.<br />
<br />
=== Stop Fingerprinting ===<br />
<br />
[https://addons.mozilla.org/firefox/addon/stop-fingerprinting/ Stop Fingerprinting] disables / modifies some browser APIs that would otherwise allow browser fingerprinting.<br />
<br />
== Remove system-wide hidden extensions ==<br />
<br />
Several extensions, hidden to the user, are installed by default in {{ic|/usr/lib/firefox/browser/features}}. Many can be safely removed via {{ic|rm ''extension-name''.xpi}} in order to completely remove unwanted features. Many of these extensions are not enabled by default and have a menu option for enabling or disabling. Note that any files removed will return upon update of the {{pkg|firefox}} package. Below are a few examples of these extensions and their features.<br />
<br />
* {{ic|activity-stream@mozilla.org.xpi}} - "Activity Stream" which replaces the new tab page. See [https://github.com/mozilla/activity-stream]<br />
<br />
* {{ic|firefox@getpocket.com.xpi}} - [https://getpocket.com/firefox/ Pocket]<br />
<br />
* {{ic|followonsearch@mozilla.com.xpi}} - Search telemetry. See also [[#Disable telemetry]].<br />
<br />
* {{ic|shield-recipe-client@mozilla.org.xpi}} [https://support.mozilla.org/en-US/kb/shield SHIELD studies]<br />
<br />
See also [https://dxr.mozilla.org/mozilla-release/source/browser/extensions/] for a full list of system extensions including README files describing their functions.</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Fonts&diff=381839
Fonts
2015-07-12T04:30:22Z
<p>Foolishgrunt: /* Burmese */</p>
<hr />
<div>[[Category:Fonts]]<br />
[[Category:Graphics and desktop publishing]]<br />
[[cs:Fonts]]<br />
[[de:Schriftarten]]<br />
[[es:Fonts]]<br />
[[it:Fonts]]<br />
[[ja:フォント]]<br />
[[ru:Fonts]]<br />
[[tr:Yazıtipleri]]<br />
[[zh-CN:Fonts]]<br />
[[zh-TW:Fonts]]<br />
{{Related articles start}}<br />
{{Related|Font configuration}}<br />
{{Related|Infinality}}<br />
{{Related|Java Runtime Environment Fonts}}<br />
{{Related|Microsoft fonts}}<br />
{{Related articles end}}<br />
From [[Wikipedia:Computer font|Wikipedia]]:<br />
:''A computer font (or font) is an electronic data file containing a set of glyphs, characters, or symbols such as dingbats.''<br />
<br />
Note that certain font licenses may impose some legal limitations.<br />
<br />
== Font formats ==<br />
<br />
Most computer fonts used today are in either ''bitmap'' or ''outline'' data formats. <br />
;Bitmap fonts: Consist of a matrix of dots or pixels representing the image of each glyph in each face and size.<br />
;Outline or ''vector'' fonts: Use Bézier curves, drawing instructions and mathematical formulae to describe each glyph, which make the character outlines scalable to any size.<br />
<br />
=== Common extensions ===<br />
<br />
* {{ic|bdf}} and {{ic|bdf.gz}} – bitmap fonts, ''b''itmap ''d''istribution ''f''ormat and gzip compressed {{ic|bdf}}<br />
* {{ic|pcf}} and {{ic|pcf.gz}} – bitmaps, ''p''ortable ''c''ompiled ''f''ont and gzip compressed {{ic|pcf}}<br />
* {{ic|psf}}, {{ic|psfu}}, {{ic|psf.gz}} and {{ic|psfu.gz}} – bitmaps, ''P''C ''s''creen ''f''ont, ''P''C ''s''creen ''f''ont ''U''nicode and the gzipped versions (not compatible with X.Org)<br />
* {{ic|pfa}} and {{ic|pfb}} – outline fonts, ''P''ostScript ''f''ont ''A''SCII and ''P''ostScript ''f''ont ''b''inary. PostScript fonts carry built-in printer instructions.<br />
* {{ic|ttf}} – outline, ''T''rue''T''ype ''f''ont. Originally designed as a replacement for the PostScript fonts.<br />
* {{ic|otf}} – outline, ''O''pen''T''ype ''f''ont. TrueType with PostScript typographic instructions.<br />
<br />
For most purposes, the technical differences between TrueType and OpenType can be ignored, some fonts with a {{ic|ttf}} extension are actually OpenType fonts.<br />
<br />
=== Other formats ===<br />
<br />
The typesetting application, ''TeX,'' and its companion font software, ''Metafont,'' render characters using their own methods. Some of the file extensions used for fonts by these two programs are {{ic|*pk}}, {{ic|*gf}}, {{ic|mf}} and {{ic|vf}}.<br />
<br />
''FontForge,'' a font editing application, can store fonts in its native text-based format, {{ic|sfd}}, ''s''pline ''f''ont ''d''atabase.<br />
<br />
The [http://www.w3.org/TR/SVG/fonts.html SVG] format also has its own font description method.<br />
<br />
== Installation ==<br />
<br />
There are various methods for installing fonts.<br />
<br />
=== Pacman ===<br />
<br />
Fonts and font collections in the enabled repositories can be installed using [[pacman]]. Available fonts may be found by using:<br />
$ pacman -Ss font<br />
Or to search for {{ic|ttf}} fonts only:<br />
$ pacman -Ss ttf<br />
<br />
=== Creating a package ===<br />
<br />
You should give pacman the ability to manage your fonts, which is done by creating an Arch package. These can also be shared with the community in the [[AUR]]. Here is an example of how to create a basic package. To learn more about building packages, read [[PKGBUILD]].<br />
<br />
{{bc|<nowiki><br />
pkgname=ttf-fontname<br />
pkgver=1.0<br />
pkgrel=1<br />
pkgdesc="custom fonts"<br />
arch=(any)<br />
depends=(fontconfig xorg-font-utils)<br />
source=("http://someurl.org/$pkgname.tar.bz2")<br />
install=$pkgname.install<br />
<br />
package() {<br />
install -d "$pkgdir/usr/share/fonts/TTF"<br />
install -m644 "$srcdir/$pkgname/"*.ttf "$pkgdir/usr/share/fonts/TTF/"<br />
}<br />
</nowiki>}}<br />
<br />
This PKGBUILD assumes the fonts are TrueType. An install file ({{ic|ttf-fontname.install}}) is also needed to update the font cache:<br />
<br />
{{bc|<nowiki><br />
post_install() {<br />
echo -n "Updating font cache... "<br />
fc-cache >/dev/null -f<br />
mkfontscale /usr/share/fonts/TTF<br />
mkfontdir /usr/share/fonts/TTF<br />
echo done<br />
}<br />
<br />
post_upgrade() {<br />
post_install<br />
}<br />
<br />
post_remove() {<br />
post_install<br />
}<br />
</nowiki>}}<br />
<br />
For a more convenient package creation from TTFs you can also use {{AUR|makefontpkg}} from the [[AUR]].<br />
<br />
=== Manual installation ===<br />
<br />
The recommended way of adding fonts that are not in the repositories to your system is described in [[#Creating a package]]. This gives pacman the ability to remove or update them at a later time. Fonts can alternately be installed manually as well.<br />
<br />
To install fonts system-wide (available for all users), move the folder to the {{ic|/usr/share/fonts/}} directory. The files need to be readable by every user, use [[chmod]] to set the correct permissions (i.e. at least {{ic|0444}} for files and {{ic|0555}} for directories). To install fonts for only a single user, use {{ic|~/.local/share/fonts}} ({{ic|~/.fonts/}} is now deprecated).<br />
<br />
For Xserver to load fonts directly (as opposed to the use of a ''font server'') the directory for your newly added font must be added with a FontPath entry. This entry is located in the ''Files'' section [[Xorg#Configuration|of your Xorg configuration file]] (e.g. {{ic|/etc/X11/xorg.conf}} or {{ic|/etc/xorg.conf}}). See [[#Older applications]] for more detail.<br />
<br />
Then update the fontconfig font cache:<br />
<br />
$ fc-cache -vf<br />
<br />
=== Manual installation: advanced method ===<br />
<br />
Manual installation and maintenance of your font resources may be especially useful if your collection is more specialized, e.g. if you use commercial fonts,<br />
if you use fonts in different formats, if you often install and remove font files, or if you just feel you need more control and better access than offered by<br />
the package manager. There are numerous benefits to such an approach:<br />
<br />
* You can avoid installation of multiple copies of the same family in different versions and formats (one of the most common reasons for rendering issues).<br />
* You can use multiple and non-standard physical sources of font files (e.g. an additional hard drive, a separate partition).<br />
* You can avoid relying on huge and cryptic local font sources which possibly contain 5 families you need and 55 you do not need (TeX Live & {{ic|09-texlive-fonts.conf}}, random font collections from the AUR, etc).<br />
* You can avoid rendering issues because your fontconfig settings were tuned to a different format but the one installed in your system.<br />
* You can quickly verify which families in which format(s) are present in the system and available for applications by visually inspecting the content of the main font directory (as a result, you do not need sophisticated and heavy-on-resources font management applications: {{Pkg|gtk2fontsel}} and basic CLI tools like {{ic|fc-query}} from {{Pkg|fontconfig}} package will do the job even better and faster).<br />
* When you install or upgrade a single font, the same version will be available for all applications, including LaTeX related software.<br />
* If necessary, you can quickly enable / disable a particular family because you know where exactly it can be found (useful for debugging).<br />
* You do not need to worry about redundant {{ic|/etc/fonts/conf.avail/nn-foo.conf}} fontconfig files, potentially conflicting with your rendering settings (especially when you are using a [[Font configuration#Patched_packages|customized font configuration and patched libraries]]).<br />
* In the long run, you save time needed to resolve issues and eliminate conflicts caused by careless use of the package manager.<br />
<br />
In practical terms, there are at least a few ways to achieve this, which, if necessary, can be adopted by any package manager. The one described below has<br />
proven to be very efficient and secure even with large font collections.<br />
<br />
* We are going to separate font source locations (e.g. {{ic|/usr/share/fonts.avail}}: this is where our fonts will be stored) from a directory containing symbolic links to the families in use ({{ic|/usr/share/fonts}}).<br />
<br />
* Each family is going to be located in a separate, clearly named subdirectory. The naming convention should be consistent and unambiguous, for instance:<br />
<br />
{{bc|<nowiki><br />
<ttf|otf|t1>-<optional_global_group_or_foundry_name>-<font_family_name><br />
</nowiki>}}<br />
<br />
This way the content of the source directory will look like this:<br />
<br />
{{bc|<nowiki><br />
$ ls /usr/share/fonts.avail<br />
<br />
/usr/share/fonts.avail/otf-heuristica<br />
/usr/share/fonts.avail/ttf-liberation<br />
/usr/share/fonts.avail/ttf-ms-arial<br />
...<br />
</nowiki>}}<br />
<br />
* We are not going to touch TeX Live font directories to avoid issues with LaTeX software. Instead, since we can use multiple locations, we will create symlinks in {{ic|/usr/share/fonts}}, giving applications access to particular families:<br />
<br />
{{bc|<nowiki><br />
# cd /usr/share/fonts<br />
# ln -s ../fonts.avail/otf-heuristica .<br />
# ln -s /opt/texlive/texmf-dist/fonts/truetype/public/opensans ttf-texlive-open.sans<br />
</nowiki>}}<br />
<br />
The result:<br />
<br />
{{bc|<nowiki><br />
$ ls /usr/share/fonts<br />
<br />
ttf-liberation -> ..fonts.avail/ttf-liberation<br />
ttf-ms-arial -> ..fonts.avail/ttf-ms-arial<br />
otf-heuristica -> ..fonts.avail/otf-heuristica<br />
otf-texlive-tex.gyre -> /opt/texlive/texmf-dist/fonts/opentype/public/tex-gyre<br />
ttf-texlive-open.sans -> /opt/texlive/texmf-dist/fonts/truetype/public/opensans<br />
...<br />
</nowiki>}}<br />
<br />
Finally, you may want to run the usual:<br />
<br />
{{bc|<nowiki><br />
# fc-cache && mkfontscale && mkfontdir<br />
</nowiki>}}<br />
<br />
A similar approach can be found in [[TeX Live]] Wiki article, but it is much simpler and describes a per-user scenario rather than a global implementation.<br />
<br />
=== Older applications ===<br />
<br />
With older applications that do not support fontconfig (e.g. GTK+ 1.x applications, and {{ic|xfontsel}}) the index will need to be created in the font directory:<br />
<br />
$ mkfontscale<br />
$ mkfontdir<br />
<br />
Or to include more than one folder with one command:<br />
<br />
$ for dir in /font/dir1/ /font/dir2/; do xset +fp $dir; done && xset fp rehash<br />
<br />
Or if fonts were installed in a different sub-folders under the e.g. {{ic|/usr/share/fonts}}:<br />
<br />
$ for dir in * ; do if [ -d "$dir" ]; then cd "$dir";xset +fp "$PWD" ;mkfontscale; mkfontdir;cd .. ;fi; done && xset fp rehash<br />
<br />
At times the X server may fail to load the fonts directory and you will need to rescan all the {{ic|fonts.dir}} files:<br />
<br />
# xset +fp /usr/share/fonts/misc # Inform the X server of new directories<br />
# xset fp rehash # Forces a new rescan<br />
<br />
To check that the font(s) is included:<br />
<br />
$ xlsfonts | grep fontname<br />
<br />
{{note|Many packages will automatically configure Xorg to use the font upon installation. If that is the case with your font, this step is not necessary.}}<br />
<br />
This can also be set globally in {{ic|/etc/X11/xorg.conf}} or {{ic|/etc/X11/xorg.conf.d}}.<br />
<br />
Here is an example of the section that must be added to {{ic|/etc/X11/xorg.conf}}. Add or remove paths based on your particular font requirements.<br />
<br />
# Let X.Org know about the custom font directories<br />
Section "Files"<br />
FontPath "/usr/share/fonts/100dpi"<br />
FontPath "/usr/share/fonts/75dpi"<br />
FontPath "/usr/share/fonts/cantarell"<br />
FontPath "/usr/share/fonts/cyrillic"<br />
FontPath "/usr/share/fonts/encodings"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/truetype"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/util"<br />
EndSection<br />
<br />
=== Pango Warnings ===<br />
When [http://www.pango.org/ Pango] is in use on your system it will read from [http://www.freedesktop.org/wiki/Software/fontconfig fontconfig] to sort out where to source fonts.<br />
<br />
(process:5741): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common'<br />
(process:5741): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='latin'<br />
<br />
If you are seeing errors similar to this and/or seeing blocks instead of characters in your application then you need to add fonts and update the font cache. This example uses the {{Pkg|ttf-liberation}} fonts to illustrate the solution (after successful installation of the package) and runs as root to enable them system-wide.<br />
<br />
# fc-cache -vfs<br />
/usr/share/fonts: caching, new cache contents: 0 fonts, 3 dirs<br />
/usr/share/fonts/TTF: caching, new cache contents: 16 fonts, 0 dirs<br />
/usr/share/fonts/encodings: caching, new cache contents: 0 fonts, 1 dirs<br />
/usr/share/fonts/encodings/large: caching, new cache contents: 0 fonts, 0 dirs<br />
/usr/share/fonts/util: caching, new cache contents: 0 fonts, 0 dirs<br />
/var/cache/fontconfig: cleaning cache directory<br />
fc-cache: succeeded<br />
<br />
You can test for a default font being set like so:<br />
<br />
# fc-match<br />
LiberationMono-Regular.ttf: "Liberation Mono" "Regular"<br />
<br />
== Console fonts ==<br />
<br />
{{Note|This section is about the [[Wikipedia:Linux console|Linux console]]. For an alternative console solutions offering more features (full Unicode fonts, modern graphics adapters etc.), see [[fbterm]], [[KMSCON]] or similar projects.}}<br />
<br />
By default, the [[Wikipedia:Virtual console|virtual console]] uses the kernel built-in font with a [[Wikipedia:CP437|CP437]] character set,<sup>[https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/tty/vt/Makefile#n4]</sup> but this can be easily changed.<br />
<br />
The [[Wikipedia:Linux console|Linux console]] uses UTF-8 encoding by default, but because the standard VGA-compatible framebuffer is used, a console font is limited to either a standard 256, or 512 glyphs. If the font has more than 256 glyphs, the number of colours is reduced from 16 to 8. In order to assign correct symbol to be displayed to the given Unicode value, a special translation map, often called ''unimap'', is needed. Nowadays most of the console fonts have the ''unimap'' built-in, historically it had to be loaded separately.<br />
<br />
The {{Pkg|kbd}} package provides tools to change virtual console font and font mapping. Available fonts are saved in the {{ic|/usr/share/kbd/consolefonts/}} directory, those ending with ''.psfu'' or ''.psfu.gz'' have a Unicode translation map built-in.<br />
<br />
Keymaps, the connection between the key pressed and the character used by the computer, are found in the subdirectories of {{ic|/usr/share/kbd/keymaps/}}, see [[Keyboard configuration in console]] for details.<br />
<br />
{{Note|Replacing the font can cause issues with programs that expect a standard VGA-style font, such as those using line drawing graphics.}}<br />
<br />
=== Previewing and testing ===<br />
<br />
{{Tip|An organized library of images for previewing is available: [http://alexandre.deverteuil.net/pages/consolefonts/ Linux console fonts screenshots].}}<br />
<br />
The available glyphs or letters in the font can also be viewed as a table with using ''showconsolefont'':<br />
<br />
$ showconsolefont<br />
<br />
The ''setfont'' utility may be used to temporarily change the font, so that the user can consider its permanent use. Just pass the name of the font (they are located in {{ic|/usr/share/kbd/consolefonts/}}). For example:<br />
<br />
$ setfont lat2-16 -m 8859-2<br />
<br />
Note that the font name is case-sensitive, so type it ''exactly'' as you see it. If the newly changed font is not suitable, a return to the default font with the following command (even if the console display is totally unreadable, this command will still work, just type the command "blindly"):<br />
<br />
$ setfont<br />
<br />
{{Note|''setfont'' only works on the console currently being used. Any other consoles, active or inactive, remain unaffected.}}<br />
<br />
=== Persistent configuration ===<br />
<br />
The {{ic|FONT}} variable in {{ic|/etc/vconsole.conf}} is used to set the font at boot, persistently for all consoles. See {{ic|man 5 vconsole.conf}} for details.<br />
<br />
For displaying characters such as ''Č, ž, đ, š'' or ''Ł, ę, ą, ś'' using the font {{ic|lat2-16.psfu.gz}}:<br />
<br />
{{hc|/etc/vconsole.conf|2=<br />
...<br />
FONT=lat2-16<br />
FONT_MAP=8859-2<br />
}}<br />
<br />
It means that second part of ISO/IEC 8859 characters are used with size 16. You can change font size using other values (e.g. {{ic|lat2-08}}). For the regions determined by 8859 specification, look at the [[wikipedia:ISO/IEC_8859#The_Parts_of_ISO.2FIEC_8859|Wikipedia table]].<br />
<br />
To use the specified font in early userspace, use the {{ic|consolefont}} hook in {{ic|/etc/mkinitcpio.conf}}. See [[Mkinitcpio#HOOKS]] for more information.<br />
<br />
If the fonts seems to not change on boot, or change only temporarily, it is most likely that they got reset when graphics driver was initialized and console was switched to framebuffer. To avoid this, load your graphics driver earlier. See for example [[Kernel mode setting#Early KMS start]], [https://bbs.archlinux.org/viewtopic.php?id=145765] or other ways to setup your framebuffer before {{ic|/etc/vconsole.conf}} is applied.<br />
<br />
== Font packages ==<br />
<br />
This is a selective list that includes many font packages from the [[AUR]] along with those in the official repositories. Fonts are tagged "Unicode" if they have wide Unicode support, see the project or Wikipedia pages for detail.<br />
<br />
Github user Ternstor has created a python script that generates HTML documents with PNG images of all the fonts in the AUR and the official repositories: [https://github.com/ternstor/distrofonts/blob/master/archfonts.py].<br />
<br />
=== Braille ===<br />
<br />
*{{Pkg|ttf-ubraille}} - Font containing Unicode symbols for ''braille''<br />
<br />
=== International users ===<br />
<br />
Applications and browsers select and display fonts depending upon fontconfig preferences and available font glyph for Unicode text. To list installed fonts for a particular language, issue a command {{ic|<nowiki>fc-list :lang="two letter language code"</nowiki>}}. For instance, to list installed Arabic fonts or fonts supporting Arabic glyph:<br />
{{hc|$ fc-list :lang&#61;ar &#124; cut -d: -f1|2=<br />
<nowiki><br />
/usr/share/fonts/TTF/FreeMono.ttf<br />
/usr/share/fonts/TTF/DejaVuSansCondensed.ttf<br />
/usr/share/fonts/truetype/custom/DroidKufi-Bold.ttf<br />
/usr/share/fonts/TTF/DejaVuSansMono.ttf<br />
/usr/share/fonts/TTF/FreeSerif.ttf<br />
</nowiki><br />
}}<br />
<br />
To properly render fonts for multilingual websites like Wikipedia or this Arch Linux wiki, install these packages: {{Pkg|ttf-freefont}}, {{Pkg|ttf-arphic-uming}}, {{Pkg|ttf-baekmuk}}<br />
<br />
==== Arabic & Urdu ====<br />
<br />
*{{AUR|ttf-qurancomplex-fonts}} - Fonts by King Fahd Glorious Quran Printing Complex in al-Madinah al-Munawwarah ''(AUR)''<br />
*{{AUR|ttf-amiri}} - A classical Arabic typeface in Naskh style poineered by Amiria Press ''(AUR)''<br />
*{{AUR|ttf-sil-lateef}} - Unicode Arabic font from SIL ''(AUR)''<br />
*{{AUR|ttf-sil-scheherazade}} - Unicode Arabic font from SIL ''(AUR)''<br />
*{{AUR|ttf-arabeyes-fonts}} - Collection of free Arabic fonts ''(AUR)''<br />
*{{AUR|ttf-urdufonts}} - Urdu fonts (Jameel Noori Nastaleeq (+kasheeda), Nafees Web Naskh, PDMS Saleem Quran Font) and font configuration to set Jameel Noori Nastaleeq as default font for Urdu ''(AUR)''<br />
<br />
==== Persian ====<br />
<br />
*{{AUR|ttf-irfonts}} - Official I.R. Iran Supreme Council of Information and Communication Technology (SCICT) standard persian fonts series ''(AUR)''<br />
*{{AUR|ttf-borna}} - Borna Rayaneh Persian B font series ''(AUR)''<br />
*{{AUR|ttf-x2}} - X Series 2 fonts are built on freely available fonts and extended to support Persian, Arabic, Urdu, Pashto, Dari, Uzbek, Kurdish, Uighur, old Turkish (Ottoman) and modern Turkish (Roman). ''(AUR)''<br />
*{{AUR|ttf-iran-nastaliq}} - An Unicode calligraphic font published by the High Council of Informatics of Iran ''(AUR)''<br />
<br />
==== Burmese ====<br />
<br />
*{{AUR|ttf-my-paduk}} - Padauk font for Myanmar/Birmania ''(AUR)''<br />
*{{AUR|ttf-myanmar3}} - Font for Myanmar/Burmese script ''(AUR)''<br />
*{{AUR|ttf-myanmar-fonts}} - 121 Fonts from myordbok.com ''(AUR)''<br />
<br />
==== Chinese, Japanese, Korean, Vietnamese ====<br />
<br />
===== Pan-CJK =====<br />
*{{Pkg|adobe-source-han-sans-otc-fonts}} - Large collection of fonts which comprehensively support Simplified Chinese, Traditional Chinese, Japanese, and Korean, with a consistent design and look.<br />
<br />
===== (Mainly) Chinese =====<br />
<br />
*{{Pkg|adobe-source-han-sans-cn-fonts}} - Simplified Chinese OpenType/CFF fonts<br />
*{{Pkg|adobe-source-han-sans-tw-fonts}} - Traditional Chinese OpenType/CFF fonts<br />
*{{AUR|ttf-tw}} - Kai and Song traditional Chinese font from the Ministry of Education of Taiwan ''(AUR)''.<br />
*{{Pkg|wqy-microhei}} - A Sans-Serif style high quality CJKV outline font.<br />
*{{Pkg|wqy-zenhei}} - Hei Ti Style (sans-serif) Chinese Outline font embedded with bitmapped Song Ti (also supporting Japanese (partial) and Korean characters).<br />
*{{Pkg|ttf-arphic-ukai}} - ''Kaiti'' (brush stroke) Unicode font (enabling anti-aliasing is suggested)<br />
*{{Pkg|ttf-arphic-uming}} - ''Mingti'' (printed) Unicode font<br />
*{{Pkg|opendesktop-fonts}} - ''New Sung'' font, previously is ttf-fireflysung package<br />
*{{Pkg|wqy-bitmapfont}} - Bitmapped Song Ti (serif) Chinese font<br />
*{{Pkg|ttf-hannom}} - Chinese and Vietnamese TrueType font<br />
<br />
===== Japanese =====<br />
<br />
*{{Pkg|adobe-source-han-sans-jp-fonts}} - Japanese OpenType/CFF fonts<br />
*{{Pkg|otf-ipafont}} - Formal style Japanese Gothic (sans-serif) and Mincho (serif) fonts set; one of the highest quality open source font. Default of openSUSE-ja.<br />
*{{AUR|ttf-vlgothic}} - Japanese Gothic fonts. Default of Debian/Fedora/Vine Linux ''(AUR)''<br />
*{{AUR|ttf-mplus}} - Modern Gothic style Japanese outline fonts. It includes all of Japanese Hiragana/Katakana, Basic Latin, Latin-1 Supplement, Latin Extended-A, IPA Extensions and most of Japanese Kanji, Greek, Cyrillic, Vietnamese with 7 weights (proportional) or 5 weights (monospace). ''(AUR)''<br />
*{{AUR|ttf-ipa-mona}}, {{AUR|ttf-monapo}} - Japanese fonts to show [[wikipedia:2channel_Shift_JIS_art|2channel Shift JIS art]] properly. ''(AUR)''<br />
*{{Pkg|ttf-sazanami}} - Japanese free TrueType font. This is outdated and not maintained any more, but may be defined as a fallback font on several environments.<br />
*{{Pkg|ttf-hanazono}} - A free Japanese kanji font, style Mincho (serif).<br />
<br />
===== Korean =====<br />
<br />
*{{Pkg|adobe-source-han-sans-kr-fonts}} - Korean OpenType/CFF fonts<br />
*{{Pkg|ttf-baekmuk}} - Collection of Korean TrueType fonts<br />
*{{AUR|ttf-alee}} - Set of free Hangul TrueType fonts (''AUR'')<br />
*{{AUR|ttf-unfonts-core}} - Un fonts (default Baekmuk fonts may be unsatisfactory) (''AUR'')<br />
*{{AUR|ttf-nanum}} - Nanum series TrueType fonts (''AUR'')<br />
*{{AUR|ttf-nanumgothic_coding}} - Nanum series fixed width TrueType fonts (''AUR'')<br />
<br />
==== Cyrillic ====<br />
<br />
''Also see [[#Monospaced]], [[#Sans-serif]] and [[#Serif]]''<br />
*{{AUR|ttf-paratype}} - Font family by ParaType: sans, serif, mono, extended cyrillic and latin, OFL license (''AUR'')<br />
*{{AUR|font-arhangai}} - Mongolian Cyrillic (''AUR'')<br />
*{{AUR|ttf-pingwi-typography}} - PingWi Typography (PWT) fonts (''AUR'')<br />
<br />
==== Greek ====<br />
<br />
Almost all Unicode fonts contain the Greek character set (polytonic included). Some additional font packages, which might not contain the complete Unicode set but utilize high quality Greek (and Latin, of course) typefaces are:<br />
*{{AUR|otf-gfs}} - Selection of OpenType fonts from the Greek Font Society ''(AUR)''<br />
*{{AUR|ttf-mgopen}} - Professional TrueType fonts from Magenta ''(AUR)''<br />
<br />
==== Hebrew ====<br />
<br />
*{{AUR|culmus}} - Nice collection of free Hebrew fonts ''(AUR)''<br />
<br />
==== Indic ====<br />
<br />
*{{Pkg|ttf-freebanglafont}} - Font for Bangla<br />
*{{Pkg|ttf-indic-otf}} - Indic OpenType Fonts collection (containing ttf-freebanglafont)<br />
:(This one contains a "look of disapproval" that might be more to your liking than the {{Pkg|bdf-unifont}} one mentioned elsewhere in this document)<br />
* {{AUR|lohit-fonts}} - Indic TrueType fonts from Fedora Project (containing Oriya Fonts and more) ''(AUR)''<br />
* {{AUR|ttf-devanagarifonts}} - Devanagari TrueType fonts (contains 283 fonts) ''(AUR)''<br />
* {{AUR|ttf-gujrati-fonts}} - TTF Gujarati fonts (Avantika,Gopika,Shree768) ''(AUR)''<br />
* {{AUR|ttf-gurmukhi-fonts_sikhnet}} - TrueType Gurmukhi fonts (gurbaniwebthick,prabhki) ''(AUR)''<br />
* {{AUR|ttf-gurmukhi_punjabi}} - TTF Gurmukhi / Punjabi (contains 252 fonts) ''(AUR)''<br />
* {{AUR|ttf-kannada-font}} - Kannada, the language of Karnataka state in India ''(AUR)''<br />
* {{AUR|ttf-tamil}} - Tamil Unicode fonts (''AUR'')<br />
<br />
==== Khmer ====<br />
<br />
*{{Pkg|ttf-khmer}} - Font covering glyphs for Khmer language<br />
*[https://www.google.com/fonts/specimen/Hanuman Hanuman] ({{AUR|ttf-google-fonts-hg}} or {{AUR|ttf-google-fonts-git}})<br />
<br />
==== Lao ====<br />
<br />
* {{AUR|ttf-lao}} - Lao TTF font (Phetsarath_OT) ''(AUR)''<br />
* {{AUR|ttf-lao-fonts}} - Lao TTF fonts, both Unicode and non-Unicode for Windows ''(AUR)''<br />
<br />
==== Meroitic (Egyptian Hieroglyphs) ====<br />
<br />
*{{AUR|ttf-aegyptus}} - Font for Egyptian Hieroglyphs (part of Unicode Fonts for Ancient Scripts) (''AUR'')<br />
<br />
==== Sinhala ====<br />
<br />
*{{AUR|ttf-lklug}} - Sinhala Unicode font (''AUR'')<br />
<br />
==== Thai ====<br />
<br />
*{{Pkg|ttf-tlwg}} - Collection of scalable Thai fonts<br />
<br />
==== Tibetan ====<br />
<br />
*{{Pkg|ttf-tibetan-machine}} - Tibetan Machine TTFont<br />
<br />
=== Math ===<br />
<br />
*{{Pkg|font-mathematica}} - Mathematica fonts by Wolfram Research, Inc.<br />
*{{AUR|ttf-mathtype}} - MathType fonts ''(AUR)''<br />
*{{AUR|ttf-computer-modern-fonts}} - ''(AUR)''<br />
<br />
=== Microsoft fonts ===<br />
<br />
See [[Microsoft fonts]].<br />
<br />
=== Apple OS X fonts ===<br />
<br />
* {{AUR|ttf-mac-fonts}} - Mac OS X TrueType fonts<br />
* {{AUR|ttf-mac}} - Mac OS X TrueType fonts (This package does not come with the ttf fonts (only the otf fonts), they have to be provided on their own.<br />
<br />
=== Monospaced ===<br />
<br />
Here are some suggestions. Every user has their own favorite, so experiment to find yours. <br />
If you are in a hurry, you read Dan Benjamin's blog post: [http://hivelogic.com/articles/top-10-programming-fonts ''Top 10 Programming Fonts''].<br />
<br />
Here is a long list of fonts by Trevor Lowing: http://www.lowing.org/fonts/.<br />
<br />
A comparison with images on Slant: [http://www.slant.co/topics/67/~what-are-the-best-programming-fonts What are the best programming fonts?]<br />
<br />
And a Stack Overflow question with some images: [http://stackoverflow.com/questions/4689/recommended-fonts-for-programming Recommended fonts for programming]<br />
<br />
==== TrueType ====<br />
<br />
* Agave ({{AUR|ttf-agave}})<br />
* [[Wikipedia:Andalé Mono|Andalé Mono]] ({{AUR|ttf-ms-fonts}})<br />
* Anka/Coder ({{AUR|ttf-anka-coder}})<br />
* [http://www.marksimonson.com/fonts/view/anonymous-pro Anonymous Pro] ({{pkg|ttf-anonymous-pro}}, included in {{AUR|ttf-google-fonts-hg}} and {{AUR|ttf-google-fonts-git}})<br />
* [[Wikipedia:Bitstream Vera|Bitstream Vera Mono]] ({{Pkg|ttf-bitstream-vera}})<br />
* [[Wikipedia:Consolas|Consolas]] ({{AUR|ttf-vista-fonts}}) - Windows programming font<br />
* [[Wikipedia:Courier New|Courier New]] ({{AUR|ttf-ms-fonts}})<br />
* Cousine ({{AUR|ttf-chromeos-fonts}} or {{AUR|ttf-google-fonts-hg}} or {{AUR|ttf-google-fonts-git}}) - Chrome/Chromium OS replacement for Courier New (metric-compatible)<br />
* [[Wikipedia:DejaVu fonts|DejaVu Sans Mono]] ({{Pkg|ttf-dejavu}}) - Unicode<br />
* [[Wikipedia:Droid (font)|Droid Sans Mono]] ({{Pkg|ttf-droid}}, included in {{AUR|ttf-google-fonts-hg}} and {{AUR|ttf-google-fonts-git}})<br />
* Envy Code R ({{AUR|ttf-envy-code-r}})<br />
* Fantasque Sans Mono ({{AUR|ttf-fantasque-sans}} or {{AUR|ttf-fantasque-sans-git}})<br />
* [[Wikipedia:GNU FreeFont|FreeMono]] ({{Pkg|ttf-freefont}}) - Unicode<br />
* [[Wikipedia:Inconsolata|Inconsolata]] ({{Pkg|ttf-inconsolata}}, included in {{AUR|ttf-google-fonts-hg}} and {{AUR|ttf-google-fonts-git}}) - Excellent programming font<br />
* [[Wikipedia:Inconsolata|Inconsolata-g]] ({{AUR|ttf-inconsolata-g}}) - adds some programmer-friendly modifications<br />
* [[Wikipedia:Liberation fonts|Liberation Mono]] ({{Pkg|ttf-liberation}}) - Replacement for Courier New, based on Cousine (metric-compatible)<br />
* [[Wikipedia:Lucida Typewriter|Lucida Typewriter]] (included in package {{AUR|jre}})<br />
* [[Wikipedia:Monaco (typeface)|Monaco]] ({{AUR|ttf-monaco}}) - Popular programming font on OSX/Textmate<br />
* Monofur ({{AUR|ttf-monofur}})<br />
* [[Wikipedia:Source_Code_Pro|Source Code Pro]] ({{pkg|adobe-source-code-pro-fonts}})<br />
<br />
==== Bitmap ====<br />
<br />
*Default 8x16<br />
*Dina ({{Pkg|dina-font}})<br />
*[http://font.gohu.org/ Gohu] ({{AUR|gohufont}})<br />
*Lime ({{Pkg|artwiz-fonts}})<br />
*[[Wikipedia:ProFont|ProFont]] ({{Pkg|profont}})<br />
*[[Wikipedia:Proggy Programming Fonts|Proggy Programming Fonts]] ({{AUR|proggyfonts}})<br />
*Proggy opti cyrillic ({{AUR|proggyopticyr-font}})<br />
*Tamsyn ({{Pkg|tamsyn-font}})<br />
*[http://terminus-font.sourceforge.net/ Terminus] ({{Pkg|terminus-font}})<br />
*Unifont (glyphs like (look of disapproval)) ({{Pkg|bdf-unifont}})<br />
<br />
=== Sans-serif ===<br />
<br />
*[http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=andika Andika] ({{AUR|ttf-andika}}, included in {{AUR|ttf-sil-fonts}})<br />
*[[Wikipedia:Arial|Arial]] ({{AUR|ttf-ms-fonts}})<br />
*[[Wikipedia:Arial Black|Arial Black]] ({{AUR|ttf-ms-fonts}})<br />
*Arimo ({{AUR|ttf-chromeos-fonts}} or {{AUR|ttf-google-fonts-hg}} or {{AUR|ttf-google-fonts-git}}) - Chrome/Chromium OS replacement for Arial (metric-compatible)<br />
*[[Wikipedia:Calibri|Calibri]] ({{AUR|ttf-vista-fonts}})<br />
*[[Wikipedia:Candara|Candara]] ({{AUR|ttf-vista-fonts}})<br />
*[[Wikipedia:Corbel (typeface)|Corbel]] ({{AUR|ttf-vista-fonts}})<br />
*[[Wikipedia:DejaVu fonts|DejaVu Sans]] ({{Pkg|ttf-dejavu}}) - Unicode<br />
*[[Wikipedia:Droid (font)|Droid Sans]] ({{Pkg|ttf-droid}}, included in {{AUR|ttf-google-fonts-hg}} and {{AUR|ttf-google-fonts-git}})<br />
*[[Wikipedia:GNU FreeFont|FreeSans]] ({{Pkg|ttf-freefont}}) - Unicode<br />
*[[Wikipedia:Impact (typeface)|Impact]] ({{AUR|ttf-ms-fonts}})<br />
*[[Wikipedia:Liberation fonts|Liberation Sans]] ({{Pkg|ttf-liberation}}) Replacement for Arial, based on Arimo (metric-compatible)<br />
*[[Wikipedia:Linux Libertine|Linux Biolinum]] ({{Pkg|ttf-linux-libertine}})<br />
*[[Wikipedia:Lucida Sans|Lucida Sans]] ({{AUR|ttf-ms-fonts}})<br />
*[[Wikipedia:Microsoft Sans Serif|Microsoft Sans Serif]] ({{AUR|ttf-ms-fonts}})<br />
*[[Wikipedia:PT Sans|PT Sans]] ({{AUR|ttf-google-fonts-hg}} or {{AUR|ttf-google-fonts-git}}) - 3 major variations: normal, narrow, and caption - Unicode: Latin, Cyrillic<br />
*[[Wikipedia:Source Sans Pro|Source Sans Pro]] ({{pkg|adobe-source-sans-pro-fonts}})<br />
*[[Wikipedia:Tahoma (typeface)|Tahoma]] ({{AUR|ttf-tahoma}})<br />
*[[Wikipedia:Trebuchet MS|Trebuchet]] ({{AUR|ttf-ms-fonts}})<br />
*[[Wikipedia:Ubuntu-Title|Ubuntu-Title]] ({{AUR|ttf-ubuntu-title}})<br />
*[[Wikipedia:Ubuntu Font Family|Ubuntu Font Family]] ({{Pkg|ttf-ubuntu-font-family}})<br />
*[[Wikipedia:Verdana|Verdana]] ({{AUR|ttf-ms-fonts}})<br />
<br />
=== Script ===<br />
<br />
*[[Wikipedia:Comic Sans|Comic Sans]] ({{AUR|ttf-ms-fonts}})<br />
<br />
=== Serif ===<br />
<br />
*[[Wikipedia:Cambria (typeface)|Cambria]] ({{AUR|ttf-vista-fonts}})<br />
*[[Wikipedia:Charis SIL|Charis]] ({{AUR|ttf-charis}}, included in {{AUR|ttf-sil-fonts}}) - Unicode: Latin, Cyrillic<br />
*[[Wikipedia:Constantia (typeface)|Constantia]] ({{AUR|ttf-vista-fonts}})<br />
*[[Wikipedia:DejaVu fonts|DejaVu Serif]] ({{Pkg|ttf-dejavu}}) - Unicode<br />
*[[Wikipedia:Doulos SIL|Doulos]] ({{AUR|ttf-sil-doulos}}, included in {{AUR|ttf-sil-fonts}}) - Unicode: Latin, Cyrillic<br />
*[[Wikipedia:Droid (font)|Droid Serif]] ({{Pkg|ttf-droid}}, included in {{AUR|ttf-google-fonts-hg}} and {{AUR|ttf-google-fonts-git}})<br />
*[[Wikipedia:GNU FreeFont|FreeSerif]] ({{Pkg|ttf-freefont}}) - Unicode<br />
*[[Wikipedia:Gentium|Gentium]] ({{Pkg|ttf-gentium}}, included in {{AUR|ttf-sil-fonts}}) - Unicode: Latin, Greek, Cyrillic, Phonetic Alphabet<br />
*[[Wikipedia:Georgia (typeface)|Georgia]] ({{AUR|ttf-ms-fonts}})<br />
*[[Wikipedia:Liberation fonts|Liberation Serif]] ({{Pkg|ttf-liberation}}) - Replacement for Times New Roman, based on Tinos (metric-compatible)<br />
*[[Wikipedia:Linux Libertine|Linux Libertine]] ({{Pkg|ttf-linux-libertine}}) - Unicode: Latin, Greek, Cyrillic, Hebrew<br />
*[[Wikipedia:Times New Roman|Times New Roman]] ({{AUR|ttf-ms-fonts}})<br />
*Tinos ({{AUR|ttf-chromeos-fonts}} or {{AUR|ttf-google-fonts-hg}} or {{AUR|ttf-google-fonts-git}}) - Chrome/Chromium OS replacement for Times New Roman (metric-compatible)<br />
<br />
=== Unsorted ===<br />
<br />
<!--This section should be absorbed into the Monospace/Serif/Sans-Serif structure--><br />
*{{AUR|ttf-google-fonts-git}} and {{AUR|ttf-google-fonts-hg}} — a huge collection of free fonts (including ubuntu, inconsolata, droid, etc.) - Note: Your font dialog might get very long as >100 fonts will be added. {{AUR|ttf-google-fonts-hg}} pulls down the entire Mercurial repository from the upstream Web Fonts project. {{AUR|ttf-google-fonts-git}} pulls from a much smaller and leaner unofficial repository hosted on GitHub. ''(AUR)''<br />
*{{Pkg|ttf-mph-2b-damase}} — Covers full plane 1 and several scripts<br />
*{{Pkg|ttf-symbola}} — Provides emoji and many many other symbols<br />
*{{AUR|ttf-sil-fonts}} — Gentium, Charis, Doulos, Andika and Abyssinica from SIL ''(AUR)''<br />
*{{Pkg|font-bh-ttf}} — X.Org Luxi fonts<br />
*{{Pkg|ttf-cheapskate}} — Font collection from ''dustismo.com''<br />
*{{AUR|ttf-isabella}} — Calligraphic font based on the ''Isabella Breviary'' of 1497<br />
*{{Pkg|ttf-junicode}} — Junius font containing almost complete medieval latin script glyphs<br />
*arkpandorafonts {{AUR|ttf-arkpandora}} — Alternative to Arial and Times New Roman fonts ''(AUR)''<br />
*{{Pkg|xorg-fonts-type1}} — IBM Courier and Adobe Utopia sets of [[Wikipedia:PostScript fonts|PostScript fonts]]<br />
<br />
== Fallback font order with X11 ==<br />
<br />
Fontconfig automatically chooses a font that matches the current requirement. That is to say, if one is looking at a window containing English and Chinese for example, it will switch to another font for the Chinese text if the default one does not support it.<br />
<br />
Fontconfig lets every user configure the order they want via {{ic|$XDG_CONFIG_HOME/fontconfig/fonts.conf}}.<br />
If you want a particular Chinese font to be selected after your favorite Serif font, your file would look like this:<br />
<?xml version="1.0"?><br />
<!DOCTYPE fontconfig SYSTEM "fonts.dtd"><br />
<fontconfig><br />
<alias><br />
<family>serif</family><br />
<prefer><br />
<family>Your favorite Latin Serif font name</family><br />
<family>Your Chinese font name</family><br />
</prefer><br />
</alias><br />
</fontconfig><br />
<br />
You can add a section for Sans-serif and monospace as well. For more informations, have a look at the fontconfig manual.<br />
<br />
== Font alias ==<br />
<br />
There are several font aliases which represent other fonts in order that applications may use similar fonts. The most common aliases are: {{ic|serif}} for a font of the serif type (e.g. DejaVu Serif); {{ic|sans-serif}} for a font of the sans-serif type (e.g. DejaVu Sans); and {{ic|monospace}} for a monospaced font (e.g. DejaVu Sans Mono). However, the fonts which these aliases represent may vary and the relationship is often not shown in font management tools, such as those found in [[KDE]] and other [[desktop environments]].<br />
<br />
To reverse an alias and find which font it is representing, run:<br />
$ fc-match monospace<br />
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"<br />
<br />
In this case, {{ic|DejaVuSansMono.ttf}} is the font represented by the monospace alias.<br />
<br />
== Tips and tricks ==<br />
<br />
=== List all installed fonts ===<br />
<br />
You can use the following command to list all installed fonts that are available on your system. <br />
<br />
$ fc-list<br />
<br />
=== Set terminal font on-the-fly ===<br />
<br />
{{Expansion|Which terminals specifically support this method? Where is the documentation for the escape codes?}}<br />
<br />
For terminal emulators that use {{ic|Xresources}}, fonts can be set by using escape sequences. Specifically, echo {{ic|\033]710;$font\007}} to change the normal font ({{ic|*font}} in {{ic|~/.Xresources}}), and replace {{ic|710}} with {{ic|711}}, {{ic|712}}, and {{ic|713}} to change the {{ic|*boldFont}}, {{ic|*italicFont}}, and {{ic|*boldItalicFont}}, respectively.<br />
<br />
<code>$font</code> can be anything the terminal emulator will support.<br />
<br />
=== Application-specific font cache ===<br />
<br />
Matplotlib ({{pkg|python-matplotlib}} or {{pkg|python2-matplotlib}}) uses its own font cache, so after updating fonts, be sure to remove {{ic|$HOME/.matplotlib/fontList.cache}}, <br />
{{ic|$HOME/.cache/matplotlib/fontList.cache}}, {{ic|$HOME/.sage/matplotlib-1.2.1/fontList.cache}}, etc. so it will regenerate its cache and find the new fonts [http://matplotlib.1069221.n5.nabble.com/getting-matplotlib-to-recognize-a-new-font-td40500.html].<br />
<br />
== See also ==<br />
<br />
* [http://behdad.org/text/ State of Text Rendering]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=LXQt&diff=378578
LXQt
2015-06-14T20:37:40Z
<p>Foolishgrunt: /* Installation */ Linked to release (rather than development) versions of obconf-qt and qterminal</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[ja:LXQt]]<br />
[[ru:Razor-qt]]<br />
[[zh-CN:Razor-qt]]<br />
{{Related articles start}}<br />
{{Related|LXDE}}<br />
{{Related|Desktop environment}}<br />
{{Related|Window manager}}<br />
{{Related articles end}}<br />
{{Stub|Little more than a list of applications}}<br />
In early 2013, Hong Jen Yee "PCMan" started porting [[LXDE]] components to [[Qt]]. The first [http://blog.lxde.org/?p=1013 preview of LXDE-Qt] was released on July 3rd, 2013. On July 21st, it was announced that Razor-qt (a desktop similar in design to LXDE) and LXDE were merging. <br />
<br />
The result is [http://lxqt.org LXQt], a desktop built on Qt which partly uses Razor-qt and LXDE components. While development is mainly focused on LXQt, the GTK+ 2 version of LXDE will see continued development. The final release of Razor-qt is 0.6.0.<br />
<br />
== Installation ==<br />
<br />
[[Install]] the {{Grp|lxqt}} group. Also install {{Pkg|openbox}} - the default [[window manager]] for LXQt.<br />
<br />
You may also wish to install the following:<br />
<br />
* {{AUR|qterminal}} - lightweight Qt terminal emulator.<br />
* {{AUR|obconf-qt}} - provides the Qt port of the openbox configuration tool ObConf.<br />
* {{Pkg|oxygen-icons}} - provides a compatible icon theme for the LXQt desktop.<br />
* {{AUR|qtcurve}} - provides a compatible Qt theme for the LXQt desktop.<br />
* [[SDDM]] - the recommended LXQt display manager<br />
<br />
=== Graphical login ===<br />
<br />
Choose ''LXQt Desktop'' from the menu in a [[display manager]] of choice.<br />
<br />
=== Using xinit ===<br />
<br />
Append the following line to [[Xinitrc]]:<br />
<br />
exec startlxqt<br />
<br />
== Configuration ==<br />
<br />
LXQt in general tries to provide GUI applications to change its settings. Configuration files are in {{ic|~/.config/lxqt}}. This directory is initialized automatically. The default configuration for new users is found in {{ic|/etc/xdg/lxqt}}.<br />
<br />
=== Replace the default window manager ===<br />
<br />
While [[Openbox]] is the default [[window manager]] for LXQt, you can specify a different window manager to use with LXQt via the ''Session Settings'', or by editing {{ic|~/.config/lxqt/session.conf}}. Change the following line:<br />
<br />
window_manager=openbox<br />
<br />
to a [[window manager]] of choice:<br />
<br />
window_manager=''your_window_manager''<br />
<br />
== Suggested applications ==<br />
<br />
As LXQt is a lightweight desktop, a plain install will not provide many desktop applications. It is left to the user to choose what applications they wish to install. The [https://github.com/Razor-qt/razor-qt/wiki/3rd-party-applications Razor-qt wiki] has a page which lists of number of useful Qt applications that you may wish to install. Also see the [[List of applications]] page for a comprehensive list of applications available in Arch.<br />
<br />
== Troubleshooting ==<br />
<br />
{{Merge|Qt|Not related to only LXQT}}<br />
<br />
=== Qt themes not respected ===<br />
<br />
If LXQt's applications do not stick with your Qt-theme (especially when using KDE's system settings to set your theme), then as of KDE 4.6.1 you'll probably need to tell Qt how to find KDE's styles (Oxygen, QtCurve etc.)<br />
<br />
You just need to set the environment variable QT_PLUGIN_PATH. E.g. put<br />
<br />
export QT_PLUGIN_PATH=$HOME/.kde4/lib/kde4/plugins/:/usr/lib/kde4/plugins/<br />
<br />
into your {{ic|/etc/profile}} (or {{ic|~/.profile}} if you do not have root access). {{ic|qtconfig-qt4}} should then be able to find your kde styles and everything should look nice again!<br />
<br />
Alternatively, you can symlink the Qt styles directory to the KDE styles one:<br />
# ln -s /usr/lib/kde4/plugins/styles/ /usr/lib/qt/plugins/styles<br />
<br />
=== Qt Configuration fails to start ===<br />
<br />
'Qt Configuration', in the LXQt Configuration Center and in the Preferences menu, is used to start {{ic|qtconfig}}. The following environmental variables are needed before qtconfig will run:<br />
<br />
export QTCHOOSER_RUNTOOL=qtconfig<br />
export QT_SELECT=4<br />
<br />
The above will enable qtconfig for qt4.<br />
<br />
=== LXQt Panel appears broken on first login ===<br />
<br />
After logging in to LXQt for the very first time, the panel will appear to have no start button, no clock, and will look odd.<br />
To fix this, you must go into the LXQt Appearance configuration and set an initial LXQt theme.<br />
<br />
Click on the bottom left of the panel (where the start button should be), and the menu will come up.<br />
Select '''Preferences->LXQt settings->Appearance''' Then click on the '''LXQt Theme''' icon. Select an initial theme.<br />
<br />
The panel will now look normal, and you should be able to customize from there.<br />
<br />
== See also ==<br />
<br />
* [http://lxqt.org LXQt homepage]<br />
* [https://github.com/lxde LXQt development]<br />
* [http://lxqt-de.deviantart.com/ LXQt on deviantART]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=237046
E17
2012-11-27T21:11:28Z
<p>Foolishgrunt: /* ConnMan */</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[cs:E17]]<br />
[[es:E17]]<br />
[[fr:E17]]<br />
[[it:E17]]<br />
[[lt:E17]]<br />
[[pl:E17]]<br />
[[ru:E17]]<br />
[[zh-CN:E17]]<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From the [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment wiki]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It comprises both the Enlightenment [[window manager]] and Enlightenment Foundation Libraries (EFL), which provide additional desktop environment features such as a toolkit, object canvas, and abstracted objects. E17 has been under development since 2005, but in February 2011 the core EFLs saw their first stable 1.0 release. Enlightenment the window manager is still in the beta stages, but is already quite usable. Many people currently use E17 as a day-to-day desktop environment without problems.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the extra repository ===<br />
<br />
To install e17:<br />
pacman -S enlightenment17<br />
<br />
You might also want to install additional [[Fonts]]. You need at least 1 True Type Font.<br />
<br />
If you need/want an e17 package which is not (yet) available in [extra], see if it is available in the [[AUR]].<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{ic|easy_e17.sh}} compiles E17 from source and installs it in {{ic|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{AUR|easy-e17}}.<br />
# Edit {{ic|/etc/easy_e17.conf}} if you want.<br />
# Run it as user, so it downloads to ~/e17_src and builds as user, to install E17 (the script will immediately ask for your password so it can install in the end): {{bc|# easy_e17.sh -i}}{{Warning|This will install the latest svn version. For a stable result add the <nowiki>--srcrev=</nowiki> parameter with the latest stable revision. For beta 3 use 55246 as argument. For the revision with the 1.0 release of the core libraries, use 56361, and for the 1.1 release use 65800 ([http://enlightenment.org/p.php?p&#61;news/show&l&#61;en&news_id&#61;37 2 Dec. 2011]).}}<br />
# Put {{ic|/opt/e17/bin}} in your {{ic|PATH}} by editing {{ic|/etc/profile}}. For example, you can add this line at the end of the file: {{bc|1=PATH="$PATH:/opt/e17/bin"}}<br />
# If, after completing the install, xinitrc complains that it cannot find enlightenment upon starting, you may need to add these lines to the end of /etc/profile as well:{{bc|1=PYTHONPATH=":$PYTHONPATH"}}{{bc|1=LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/e17/lib"}}<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it is not a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{ic|update_e17.sh}} is a zenity script which is made to accompany {{ic|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
=== startx ===<br />
If you use {{ic|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
=== Elsa ===<br />
Nowadays E17 has a new display manager called Elsa, you can download it from AUR {{AUR|elsa-svn-arch}}.<br />
Elsa is quite sophisticated and its configuration is controlled by {{ic|/etc/elsa.conf}}.<br />
To start Elsa add the following line to your {{ic|/etc/inittab}}<br />
x:5:respawn:/usr/sbin/elsa<br />
and change your default runlevel to 5.<br />
<br />
=== Other ===<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{ic|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{ic|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
=== ConnMan ===<br />
<br />
E17's preferred network manager is [[Connman|ConnMan]]. It is available from the [community] repository as the {{Pkg|connman}} package. To interface with E17's default Network module, you must also install EConmman (available in AUR as {{AUR|econnman-svn}}) and it's associated dependencies.<br />
<br />
Finally, configure systemd to start the ConnMan daemon at startup:<br />
<br />
systemctl enable connman.service<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you have installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
=== NetworkManager ===<br />
<br />
You can also use {{Pkg|networkmanager}} to manage your network connections.<br />
<br />
pacman -S networkmanager<br />
<br />
Follow the instructions on [[NetworkManager]] to do the configuration. You may also need {{Pkg|network-manager-applet}} to help with your settings.<br />
<br />
pacman -S network-manager-applet<br />
<br />
You may want to add it to the start up programs so every time your E17 starts it appears on systray.<br />
<br />
Settings -> Settings Panel -> Apps -> Startup Applications -> System -> Network<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog. During 2010 there was a change in how themes work, so for older themes you may need to do the following:<br />
edje_convert <theme>.edj<br />
<br />
{{Note|The edje_convert binary has been "dropped" by upstream developers... see: [http://trac.enlightenment.org/e/changeset/56156 trac.enlightenment.org]}}<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{ic|etk_prefs}}.<br />
<br />
== Modules and Gadgets ==<br />
;Module:Name used in enlightenment to refer to the "backing" code for a gadget. <br />
;Gadget:Front-end or user interface that should help the end users of [[E17]] do something.<br />
<br />
Many Modules provide Gadgets that can be added to your desktop or on a shelf. Some Modules (such as CPUFreq) only provide a single Gadget while others (such as Composite) provide additional features without any gadgets. Note that certain gadgets such as Systray can only be added to a shelf while others such as Moon can only be loaded on the desktop. <br />
<br />
=== Compositing ===<br />
E17 offers two modules for compositing, '''''Composite''''' and '''''Ecomorph''''', depending on your hardware and preference.<br />
<br />
==== Composite ====<br />
The ''Composite'' module is the standard compositing manager provided in enlightenment. It provides some minimal compositing effects such as transparency, fade and shadow. Composite provides the more stable module and is supported on a lot hardware through either OpenGL or compositing software rendering.<br />
<br />
==== Ecomorph ====<br />
The ''Ecomorph'' module is a full-featured compositing manager which was ported from [[Compiz]] for E17. It can be downloaded from AUR {{AUR|ecomorph-git}}. Some experience instability with Ecomorph while others use it without a problem. Ecomorph requires 3D acceleration, while Composite does not. <br />
<br />
=== Places ===<br />
From the current source code [http://trac.enlightenment.org/e/browser/trunk/E-MODULES-EXTRA/places/README README] for Places:<br />
;Places module:''This module manage the volumes device attached to the system.''<br />
<br />
In other words, Places is a gadget that will help you browse files on various devices you might plug into your computer, like phones, cameras, or other various storage devices you might plug into the usb port.<br />
<br />
=== Scale Windows ===<br />
The ''Scale Windows'' module, which requires compositing to be enabled, shrinks all open windows and brings them all into view. It can be added to the desktop as a gadget or set as a key binding. <br />
<br />
Some people like to change the standard window selection key binding {{ic|ALT + Tab}} to use Scale Windows to select windows. To change this setting, you navigate to {{ic|Menu > Settings > Settings Panel > Input > Keys}}. From here, you can set any key binding you would like. <br />
<br />
To replace the window selection key binding functionality with Scale Windows, scroll through the left panel until you find the "ALT" section and then find and select {{ic|ALT + Tab}}. Then, scroll through the right panel looking for the "Scale Windows" section and choose either {{ic|Select Next}} or {{ic|Select Next (All)}} depending on whether you would like to see windows from only the current desktop or from all desktops and click "Apply" to save the binding.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{ic|~/.e}} and remove it (e.g. {{ic|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream. http://trac.enlightenment.org/e/report<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Pkg|libxcursor}} package.<br />
<br />
=== Screen unlocking does not work ===<br />
<br />
If screenlock does not accept your password add the following to {{ic|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-dejavu ttf-bitstream-vera<br />
<br />
=== udisks vs. HAL ===<br />
Modules may need to use underlying libraries or daemons to interact with various devices connected to your computer. Currently there are at least two choices for these underlying libraries or daemons to interact with connected devices. The two that will be considered here are udisks and HAL. At the time of this entry the [[HAL]] page says:<br />
:''HAL (Hardware Abstraction Layer) is a daemon that allows desktop applications to readily access hardware information, to locate and use such hardware regardless of bus or device type. In this way a desktop GUI can present all resources to its user in a seamless and uniform manner. HAL has become deprecated in favor of udev, udisks, upower, etc. and is no longer developed. Currently, a small number of programs still rely on and use HAL, though development is heading toward utilizing udev as a replacement.''<br />
<br />
So, apparently [[E17]] now tries to use udisks instead of [[HAL]]. But some of the modules and gadgets, such as Places, have not been updated to use udisks yet.<br />
<br />
=== Places does not work ===<br />
If the Places gadget look something like a blank grey area with no Gadget in it and not detecting new device, it may because the Places is still trying to use [[HAL]]. Here is the procedure to get the HAL daemon running:<br />
<br />
Install {{AUR|hal-info}} and {{AUR|hal-git}} from the [[Arch User Repository]]. Note that {{AUR|hal-info}} is a dependency for {{AUR|hal-git}}, so you may want to install it with [[pacman]]'s {{ic|--asdeps}} flag.<br />
<br />
Start the hal daemon:<br />
<br />
{{bc|# systemctl start hal}}<br />
<br />
Now you must remove the "Places" gadget from my shelf, and unload the Places module from menu {{ic|settings -> modules -> Places -> unload}}<br />
<br />
Restart enlightenment, reload the Places module and add the Places gadget to my shelf. Then Places will work normally.<br />
<br />
=== Failure in mounting internal partitions ===<br />
Check if user is in storge group:<br />
{{bc|# groups <user>}}<br />
<br />
If user is not in storage group:<br />
{{bc|# groupadd storage <br />
# gpasswd -a <user> storage}}<br />
<br />
Then create this file as root:<br />
{{bc|# nano /etc/polkit-1/localauthority/50-local.d/10-storage-group-mount-override.pkla}}<br />
<br />
And write into the file:<br />
<br />
[storage group mount override]<br />
Identity=unix-group:storage<br />
Action=org.freedesktop.udisks2.filesystem-mount-system<br />
ResultAny=yes<br />
ResultInactive=yes<br />
ResultActive=yes<br />
<br />
For more information, see:<br />
http://bbs.archbang.org/viewtopic.php?id=2720<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]<br />
* [http://www.bodhilinux.com/e17guide/e17guideEN/ Bodhi Guide to Enlightenment]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=237040
E17
2012-11-27T19:07:28Z
<p>Foolishgrunt: /* Configuring the Network */</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[cs:E17]]<br />
[[es:E17]]<br />
[[fr:E17]]<br />
[[it:E17]]<br />
[[lt:E17]]<br />
[[pl:E17]]<br />
[[ru:E17]]<br />
[[zh-CN:E17]]<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From the [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment wiki]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It comprises both the Enlightenment [[window manager]] and Enlightenment Foundation Libraries (EFL), which provide additional desktop environment features such as a toolkit, object canvas, and abstracted objects. E17 has been under development since 2005, but in February 2011 the core EFLs saw their first stable 1.0 release. Enlightenment the window manager is still in the beta stages, but is already quite usable. Many people currently use E17 as a day-to-day desktop environment without problems.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the extra repository ===<br />
<br />
To install e17:<br />
pacman -S enlightenment17<br />
<br />
You might also want to install additional [[Fonts]]. You need at least 1 True Type Font.<br />
<br />
If you need/want an e17 package which is not (yet) available in [extra], see if it is available in the [[AUR]].<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{ic|easy_e17.sh}} compiles E17 from source and installs it in {{ic|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{AUR|easy-e17}}.<br />
# Edit {{ic|/etc/easy_e17.conf}} if you want.<br />
# Run it as user, so it downloads to ~/e17_src and builds as user, to install E17 (the script will immediately ask for your password so it can install in the end): {{bc|# easy_e17.sh -i}}{{Warning|This will install the latest svn version. For a stable result add the <nowiki>--srcrev=</nowiki> parameter with the latest stable revision. For beta 3 use 55246 as argument. For the revision with the 1.0 release of the core libraries, use 56361, and for the 1.1 release use 65800 ([http://enlightenment.org/p.php?p&#61;news/show&l&#61;en&news_id&#61;37 2 Dec. 2011]).}}<br />
# Put {{ic|/opt/e17/bin}} in your {{ic|PATH}} by editing {{ic|/etc/profile}}. For example, you can add this line at the end of the file: {{bc|1=PATH="$PATH:/opt/e17/bin"}}<br />
# If, after completing the install, xinitrc complains that it cannot find enlightenment upon starting, you may need to add these lines to the end of /etc/profile as well:{{bc|1=PYTHONPATH=":$PYTHONPATH"}}{{bc|1=LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/e17/lib"}}<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it is not a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{ic|update_e17.sh}} is a zenity script which is made to accompany {{ic|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
=== startx ===<br />
If you use {{ic|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
=== Elsa ===<br />
Nowadays E17 has a new display manager called Elsa, you can download it from AUR {{AUR|elsa-svn-arch}}.<br />
Elsa is quite sophisticated and its configuration is controlled by {{ic|/etc/elsa.conf}}.<br />
To start Elsa add the following line to your {{ic|/etc/inittab}}<br />
x:5:respawn:/usr/sbin/elsa<br />
and change your default runlevel to 5.<br />
<br />
=== Other ===<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{ic|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{ic|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
=== ConnMan ===<br />
<br />
E17's preferred network manager is [[Connman|ConnMan]]. It is available from the [community] repository as the {{Pkg|connman}} package. To interface with E17's default Network module, you must also download EConmman (available in AUR as {{AUR|econnman-svn}}) and it's associated dependencies.<br />
<br />
Finally, configure systemd to start the ConnMan daemon at startup:<br />
<br />
systemctl enable connman.service<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you have installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
=== NetworkManager ===<br />
<br />
You can also use {{Pkg|networkmanager}} to manage your network connections.<br />
<br />
pacman -S networkmanager<br />
<br />
Follow the instructions on [[NetworkManager]] to do the configuration. You may also need {{Pkg|network-manager-applet}} to help with your settings.<br />
<br />
pacman -S network-manager-applet<br />
<br />
You may want to add it to the start up programs so every time your E17 starts it appears on systray.<br />
<br />
Settings -> Settings Panel -> Apps -> Startup Applications -> System -> Network<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog. During 2010 there was a change in how themes work, so for older themes you may need to do the following:<br />
edje_convert <theme>.edj<br />
<br />
{{Note|The edje_convert binary has been "dropped" by upstream developers... see: [http://trac.enlightenment.org/e/changeset/56156 trac.enlightenment.org]}}<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{ic|etk_prefs}}.<br />
<br />
== Modules and Gadgets ==<br />
;Module:Name used in enlightenment to refer to the "backing" code for a gadget. <br />
;Gadget:Front-end or user interface that should help the end users of [[E17]] do something.<br />
<br />
Many Modules provide Gadgets that can be added to your desktop or on a shelf. Some Modules (such as CPUFreq) only provide a single Gadget while others (such as Composite) provide additional features without any gadgets. Note that certain gadgets such as Systray can only be added to a shelf while others such as Moon can only be loaded on the desktop. <br />
<br />
=== Compositing ===<br />
E17 offers two modules for compositing, '''''Composite''''' and '''''Ecomorph''''', depending on your hardware and preference.<br />
<br />
==== Composite ====<br />
The ''Composite'' module is the standard compositing manager provided in enlightenment. It provides some minimal compositing effects such as transparency, fade and shadow. Composite provides the more stable module and is supported on a lot hardware through either OpenGL or compositing software rendering.<br />
<br />
==== Ecomorph ====<br />
The ''Ecomorph'' module is a full-featured compositing manager which was ported from [[Compiz]] for E17. It can be downloaded from AUR {{AUR|ecomorph-git}}. Some experience instability with Ecomorph while others use it without a problem. Ecomorph requires 3D acceleration, while Composite does not. <br />
<br />
=== Places ===<br />
From the current source code [http://trac.enlightenment.org/e/browser/trunk/E-MODULES-EXTRA/places/README README] for Places:<br />
;Places module:''This module manage the volumes device attached to the system.''<br />
<br />
In other words, Places is a gadget that will help you browse files on various devices you might plug into your computer, like phones, cameras, or other various storage devices you might plug into the usb port.<br />
<br />
=== Scale Windows ===<br />
The ''Scale Windows'' module, which requires compositing to be enabled, shrinks all open windows and brings them all into view. It can be added to the desktop as a gadget or set as a key binding. <br />
<br />
Some people like to change the standard window selection key binding {{ic|ALT + Tab}} to use Scale Windows to select windows. To change this setting, you navigate to {{ic|Menu > Settings > Settings Panel > Input > Keys}}. From here, you can set any key binding you would like. <br />
<br />
To replace the window selection key binding functionality with Scale Windows, scroll through the left panel until you find the "ALT" section and then find and select {{ic|ALT + Tab}}. Then, scroll through the right panel looking for the "Scale Windows" section and choose either {{ic|Select Next}} or {{ic|Select Next (All)}} depending on whether you would like to see windows from only the current desktop or from all desktops and click "Apply" to save the binding.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{ic|~/.e}} and remove it (e.g. {{ic|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream. http://trac.enlightenment.org/e/report<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Pkg|libxcursor}} package.<br />
<br />
=== Screen unlocking does not work ===<br />
<br />
If screenlock does not accept your password add the following to {{ic|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-dejavu ttf-bitstream-vera<br />
<br />
=== udisks vs. HAL ===<br />
Modules may need to use underlying libraries or daemons to interact with various devices connected to your computer. Currently there are at least two choices for these underlying libraries or daemons to interact with connected devices. The two that will be considered here are udisks and HAL. At the time of this entry the [[HAL]] page says:<br />
:''HAL (Hardware Abstraction Layer) is a daemon that allows desktop applications to readily access hardware information, to locate and use such hardware regardless of bus or device type. In this way a desktop GUI can present all resources to its user in a seamless and uniform manner. HAL has become deprecated in favor of udev, udisks, upower, etc. and is no longer developed. Currently, a small number of programs still rely on and use HAL, though development is heading toward utilizing udev as a replacement.''<br />
<br />
So, apparently [[E17]] now tries to use udisks instead of [[HAL]]. But some of the modules and gadgets, such as Places, have not been updated to use udisks yet.<br />
<br />
=== Places does not work ===<br />
If the Places gadget look something like a blank grey area with no Gadget in it and not detecting new device, it may because the Places is still trying to use [[HAL]]. Here is the procedure to get the HAL daemon running:<br />
<br />
Install {{AUR|hal-info}} and {{AUR|hal-git}} from the [[Arch User Repository]]. Note that {{AUR|hal-info}} is a dependency for {{AUR|hal-git}}, so you may want to install it with [[pacman]]'s {{ic|--asdeps}} flag.<br />
<br />
Start the hal daemon:<br />
<br />
{{bc|# systemctl start hal}}<br />
<br />
Now you must remove the "Places" gadget from my shelf, and unload the Places module from menu {{ic|settings -> modules -> Places -> unload}}<br />
<br />
Restart enlightenment, reload the Places module and add the Places gadget to my shelf. Then Places will work normally.<br />
<br />
=== Failure in mounting internal partitions ===<br />
Check if user is in storge group:<br />
{{bc|# groups <user>}}<br />
<br />
If user is not in storage group:<br />
{{bc|# groupadd storage <br />
# gpasswd -a <user> storage}}<br />
<br />
Then create this file as root:<br />
{{bc|# nano /etc/polkit-1/localauthority/50-local.d/10-storage-group-mount-override.pkla}}<br />
<br />
And write into the file:<br />
<br />
[storage group mount override]<br />
Identity=unix-group:storage<br />
Action=org.freedesktop.udisks2.filesystem-mount-system<br />
ResultAny=yes<br />
ResultInactive=yes<br />
ResultActive=yes<br />
<br />
For more information, see:<br />
http://bbs.archbang.org/viewtopic.php?id=2720<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]<br />
* [http://www.bodhilinux.com/e17guide/e17guideEN/ Bodhi Guide to Enlightenment]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=237039
E17
2012-11-27T19:07:12Z
<p>Foolishgrunt: /* Configuring the Network */</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[cs:E17]]<br />
[[es:E17]]<br />
[[fr:E17]]<br />
[[it:E17]]<br />
[[lt:E17]]<br />
[[pl:E17]]<br />
[[ru:E17]]<br />
[[zh-CN:E17]]<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From the [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment wiki]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It comprises both the Enlightenment [[window manager]] and Enlightenment Foundation Libraries (EFL), which provide additional desktop environment features such as a toolkit, object canvas, and abstracted objects. E17 has been under development since 2005, but in February 2011 the core EFLs saw their first stable 1.0 release. Enlightenment the window manager is still in the beta stages, but is already quite usable. Many people currently use E17 as a day-to-day desktop environment without problems.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the extra repository ===<br />
<br />
To install e17:<br />
pacman -S enlightenment17<br />
<br />
You might also want to install additional [[Fonts]]. You need at least 1 True Type Font.<br />
<br />
If you need/want an e17 package which is not (yet) available in [extra], see if it is available in the [[AUR]].<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{ic|easy_e17.sh}} compiles E17 from source and installs it in {{ic|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{AUR|easy-e17}}.<br />
# Edit {{ic|/etc/easy_e17.conf}} if you want.<br />
# Run it as user, so it downloads to ~/e17_src and builds as user, to install E17 (the script will immediately ask for your password so it can install in the end): {{bc|# easy_e17.sh -i}}{{Warning|This will install the latest svn version. For a stable result add the <nowiki>--srcrev=</nowiki> parameter with the latest stable revision. For beta 3 use 55246 as argument. For the revision with the 1.0 release of the core libraries, use 56361, and for the 1.1 release use 65800 ([http://enlightenment.org/p.php?p&#61;news/show&l&#61;en&news_id&#61;37 2 Dec. 2011]).}}<br />
# Put {{ic|/opt/e17/bin}} in your {{ic|PATH}} by editing {{ic|/etc/profile}}. For example, you can add this line at the end of the file: {{bc|1=PATH="$PATH:/opt/e17/bin"}}<br />
# If, after completing the install, xinitrc complains that it cannot find enlightenment upon starting, you may need to add these lines to the end of /etc/profile as well:{{bc|1=PYTHONPATH=":$PYTHONPATH"}}{{bc|1=LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/e17/lib"}}<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it is not a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{ic|update_e17.sh}} is a zenity script which is made to accompany {{ic|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
=== startx ===<br />
If you use {{ic|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
=== Elsa ===<br />
Nowadays E17 has a new display manager called Elsa, you can download it from AUR {{AUR|elsa-svn-arch}}.<br />
Elsa is quite sophisticated and its configuration is controlled by {{ic|/etc/elsa.conf}}.<br />
To start Elsa add the following line to your {{ic|/etc/inittab}}<br />
x:5:respawn:/usr/sbin/elsa<br />
and change your default runlevel to 5.<br />
<br />
=== Other ===<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{ic|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{ic|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
=== ConnMan ===<br />
<br />
E17's preferred network manager is [[ConnMan|Connman]]. It is available from the [community] repository as the {{Pkg|connman}} package. To interface with E17's default Network module, you must also download EConmman (available in AUR as {{AUR|econnman-svn}}) and it's associated dependencies.<br />
<br />
Finally, configure systemd to start the ConnMan daemon at startup:<br />
<br />
systemctl enable connman.service<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you have installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
=== NetworkManager ===<br />
<br />
You can also use {{Pkg|networkmanager}} to manage your network connections.<br />
<br />
pacman -S networkmanager<br />
<br />
Follow the instructions on [[NetworkManager]] to do the configuration. You may also need {{Pkg|network-manager-applet}} to help with your settings.<br />
<br />
pacman -S network-manager-applet<br />
<br />
You may want to add it to the start up programs so every time your E17 starts it appears on systray.<br />
<br />
Settings -> Settings Panel -> Apps -> Startup Applications -> System -> Network<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog. During 2010 there was a change in how themes work, so for older themes you may need to do the following:<br />
edje_convert <theme>.edj<br />
<br />
{{Note|The edje_convert binary has been "dropped" by upstream developers... see: [http://trac.enlightenment.org/e/changeset/56156 trac.enlightenment.org]}}<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{ic|etk_prefs}}.<br />
<br />
== Modules and Gadgets ==<br />
;Module:Name used in enlightenment to refer to the "backing" code for a gadget. <br />
;Gadget:Front-end or user interface that should help the end users of [[E17]] do something.<br />
<br />
Many Modules provide Gadgets that can be added to your desktop or on a shelf. Some Modules (such as CPUFreq) only provide a single Gadget while others (such as Composite) provide additional features without any gadgets. Note that certain gadgets such as Systray can only be added to a shelf while others such as Moon can only be loaded on the desktop. <br />
<br />
=== Compositing ===<br />
E17 offers two modules for compositing, '''''Composite''''' and '''''Ecomorph''''', depending on your hardware and preference.<br />
<br />
==== Composite ====<br />
The ''Composite'' module is the standard compositing manager provided in enlightenment. It provides some minimal compositing effects such as transparency, fade and shadow. Composite provides the more stable module and is supported on a lot hardware through either OpenGL or compositing software rendering.<br />
<br />
==== Ecomorph ====<br />
The ''Ecomorph'' module is a full-featured compositing manager which was ported from [[Compiz]] for E17. It can be downloaded from AUR {{AUR|ecomorph-git}}. Some experience instability with Ecomorph while others use it without a problem. Ecomorph requires 3D acceleration, while Composite does not. <br />
<br />
=== Places ===<br />
From the current source code [http://trac.enlightenment.org/e/browser/trunk/E-MODULES-EXTRA/places/README README] for Places:<br />
;Places module:''This module manage the volumes device attached to the system.''<br />
<br />
In other words, Places is a gadget that will help you browse files on various devices you might plug into your computer, like phones, cameras, or other various storage devices you might plug into the usb port.<br />
<br />
=== Scale Windows ===<br />
The ''Scale Windows'' module, which requires compositing to be enabled, shrinks all open windows and brings them all into view. It can be added to the desktop as a gadget or set as a key binding. <br />
<br />
Some people like to change the standard window selection key binding {{ic|ALT + Tab}} to use Scale Windows to select windows. To change this setting, you navigate to {{ic|Menu > Settings > Settings Panel > Input > Keys}}. From here, you can set any key binding you would like. <br />
<br />
To replace the window selection key binding functionality with Scale Windows, scroll through the left panel until you find the "ALT" section and then find and select {{ic|ALT + Tab}}. Then, scroll through the right panel looking for the "Scale Windows" section and choose either {{ic|Select Next}} or {{ic|Select Next (All)}} depending on whether you would like to see windows from only the current desktop or from all desktops and click "Apply" to save the binding.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{ic|~/.e}} and remove it (e.g. {{ic|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream. http://trac.enlightenment.org/e/report<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Pkg|libxcursor}} package.<br />
<br />
=== Screen unlocking does not work ===<br />
<br />
If screenlock does not accept your password add the following to {{ic|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-dejavu ttf-bitstream-vera<br />
<br />
=== udisks vs. HAL ===<br />
Modules may need to use underlying libraries or daemons to interact with various devices connected to your computer. Currently there are at least two choices for these underlying libraries or daemons to interact with connected devices. The two that will be considered here are udisks and HAL. At the time of this entry the [[HAL]] page says:<br />
:''HAL (Hardware Abstraction Layer) is a daemon that allows desktop applications to readily access hardware information, to locate and use such hardware regardless of bus or device type. In this way a desktop GUI can present all resources to its user in a seamless and uniform manner. HAL has become deprecated in favor of udev, udisks, upower, etc. and is no longer developed. Currently, a small number of programs still rely on and use HAL, though development is heading toward utilizing udev as a replacement.''<br />
<br />
So, apparently [[E17]] now tries to use udisks instead of [[HAL]]. But some of the modules and gadgets, such as Places, have not been updated to use udisks yet.<br />
<br />
=== Places does not work ===<br />
If the Places gadget look something like a blank grey area with no Gadget in it and not detecting new device, it may because the Places is still trying to use [[HAL]]. Here is the procedure to get the HAL daemon running:<br />
<br />
Install {{AUR|hal-info}} and {{AUR|hal-git}} from the [[Arch User Repository]]. Note that {{AUR|hal-info}} is a dependency for {{AUR|hal-git}}, so you may want to install it with [[pacman]]'s {{ic|--asdeps}} flag.<br />
<br />
Start the hal daemon:<br />
<br />
{{bc|# systemctl start hal}}<br />
<br />
Now you must remove the "Places" gadget from my shelf, and unload the Places module from menu {{ic|settings -> modules -> Places -> unload}}<br />
<br />
Restart enlightenment, reload the Places module and add the Places gadget to my shelf. Then Places will work normally.<br />
<br />
=== Failure in mounting internal partitions ===<br />
Check if user is in storge group:<br />
{{bc|# groups <user>}}<br />
<br />
If user is not in storage group:<br />
{{bc|# groupadd storage <br />
# gpasswd -a <user> storage}}<br />
<br />
Then create this file as root:<br />
{{bc|# nano /etc/polkit-1/localauthority/50-local.d/10-storage-group-mount-override.pkla}}<br />
<br />
And write into the file:<br />
<br />
[storage group mount override]<br />
Identity=unix-group:storage<br />
Action=org.freedesktop.udisks2.filesystem-mount-system<br />
ResultAny=yes<br />
ResultInactive=yes<br />
ResultActive=yes<br />
<br />
For more information, see:<br />
http://bbs.archbang.org/viewtopic.php?id=2720<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]<br />
* [http://www.bodhilinux.com/e17guide/e17guideEN/ Bodhi Guide to Enlightenment]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=237038
E17
2012-11-27T19:06:43Z
<p>Foolishgrunt: /* Configuring the Network */</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[cs:E17]]<br />
[[es:E17]]<br />
[[fr:E17]]<br />
[[it:E17]]<br />
[[lt:E17]]<br />
[[pl:E17]]<br />
[[ru:E17]]<br />
[[zh-CN:E17]]<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From the [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment wiki]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It comprises both the Enlightenment [[window manager]] and Enlightenment Foundation Libraries (EFL), which provide additional desktop environment features such as a toolkit, object canvas, and abstracted objects. E17 has been under development since 2005, but in February 2011 the core EFLs saw their first stable 1.0 release. Enlightenment the window manager is still in the beta stages, but is already quite usable. Many people currently use E17 as a day-to-day desktop environment without problems.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the extra repository ===<br />
<br />
To install e17:<br />
pacman -S enlightenment17<br />
<br />
You might also want to install additional [[Fonts]]. You need at least 1 True Type Font.<br />
<br />
If you need/want an e17 package which is not (yet) available in [extra], see if it is available in the [[AUR]].<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{ic|easy_e17.sh}} compiles E17 from source and installs it in {{ic|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{AUR|easy-e17}}.<br />
# Edit {{ic|/etc/easy_e17.conf}} if you want.<br />
# Run it as user, so it downloads to ~/e17_src and builds as user, to install E17 (the script will immediately ask for your password so it can install in the end): {{bc|# easy_e17.sh -i}}{{Warning|This will install the latest svn version. For a stable result add the <nowiki>--srcrev=</nowiki> parameter with the latest stable revision. For beta 3 use 55246 as argument. For the revision with the 1.0 release of the core libraries, use 56361, and for the 1.1 release use 65800 ([http://enlightenment.org/p.php?p&#61;news/show&l&#61;en&news_id&#61;37 2 Dec. 2011]).}}<br />
# Put {{ic|/opt/e17/bin}} in your {{ic|PATH}} by editing {{ic|/etc/profile}}. For example, you can add this line at the end of the file: {{bc|1=PATH="$PATH:/opt/e17/bin"}}<br />
# If, after completing the install, xinitrc complains that it cannot find enlightenment upon starting, you may need to add these lines to the end of /etc/profile as well:{{bc|1=PYTHONPATH=":$PYTHONPATH"}}{{bc|1=LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/e17/lib"}}<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it is not a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{ic|update_e17.sh}} is a zenity script which is made to accompany {{ic|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
=== startx ===<br />
If you use {{ic|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
=== Elsa ===<br />
Nowadays E17 has a new display manager called Elsa, you can download it from AUR {{AUR|elsa-svn-arch}}.<br />
Elsa is quite sophisticated and its configuration is controlled by {{ic|/etc/elsa.conf}}.<br />
To start Elsa add the following line to your {{ic|/etc/inittab}}<br />
x:5:respawn:/usr/sbin/elsa<br />
and change your default runlevel to 5.<br />
<br />
=== Other ===<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{ic|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{ic|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
=== ConnMan ===<br />
<br />
E17's preferred network manager is [[Connman]]. It is available from the [community] repository as the {{Pkg|connman}} package. To interface with E17's default Network module, you must also download EConmman (available in AUR as {{AUR|econnman-svn}}) and it's associated dependencies.<br />
<br />
Finally, configure systemd to start the Connman daemon at startup:<br />
<br />
systemctl enable connman.service<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you have installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
=== NetworkManager ===<br />
<br />
You can also use {{Pkg|networkmanager}} to manage your network connections.<br />
<br />
pacman -S networkmanager<br />
<br />
Follow the instructions on [[NetworkManager]] to do the configuration. You may also need {{Pkg|network-manager-applet}} to help with your settings.<br />
<br />
pacman -S network-manager-applet<br />
<br />
You may want to add it to the start up programs so every time your E17 starts it appears on systray.<br />
<br />
Settings -> Settings Panel -> Apps -> Startup Applications -> System -> Network<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog. During 2010 there was a change in how themes work, so for older themes you may need to do the following:<br />
edje_convert <theme>.edj<br />
<br />
{{Note|The edje_convert binary has been "dropped" by upstream developers... see: [http://trac.enlightenment.org/e/changeset/56156 trac.enlightenment.org]}}<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{ic|etk_prefs}}.<br />
<br />
== Modules and Gadgets ==<br />
;Module:Name used in enlightenment to refer to the "backing" code for a gadget. <br />
;Gadget:Front-end or user interface that should help the end users of [[E17]] do something.<br />
<br />
Many Modules provide Gadgets that can be added to your desktop or on a shelf. Some Modules (such as CPUFreq) only provide a single Gadget while others (such as Composite) provide additional features without any gadgets. Note that certain gadgets such as Systray can only be added to a shelf while others such as Moon can only be loaded on the desktop. <br />
<br />
=== Compositing ===<br />
E17 offers two modules for compositing, '''''Composite''''' and '''''Ecomorph''''', depending on your hardware and preference.<br />
<br />
==== Composite ====<br />
The ''Composite'' module is the standard compositing manager provided in enlightenment. It provides some minimal compositing effects such as transparency, fade and shadow. Composite provides the more stable module and is supported on a lot hardware through either OpenGL or compositing software rendering.<br />
<br />
==== Ecomorph ====<br />
The ''Ecomorph'' module is a full-featured compositing manager which was ported from [[Compiz]] for E17. It can be downloaded from AUR {{AUR|ecomorph-git}}. Some experience instability with Ecomorph while others use it without a problem. Ecomorph requires 3D acceleration, while Composite does not. <br />
<br />
=== Places ===<br />
From the current source code [http://trac.enlightenment.org/e/browser/trunk/E-MODULES-EXTRA/places/README README] for Places:<br />
;Places module:''This module manage the volumes device attached to the system.''<br />
<br />
In other words, Places is a gadget that will help you browse files on various devices you might plug into your computer, like phones, cameras, or other various storage devices you might plug into the usb port.<br />
<br />
=== Scale Windows ===<br />
The ''Scale Windows'' module, which requires compositing to be enabled, shrinks all open windows and brings them all into view. It can be added to the desktop as a gadget or set as a key binding. <br />
<br />
Some people like to change the standard window selection key binding {{ic|ALT + Tab}} to use Scale Windows to select windows. To change this setting, you navigate to {{ic|Menu > Settings > Settings Panel > Input > Keys}}. From here, you can set any key binding you would like. <br />
<br />
To replace the window selection key binding functionality with Scale Windows, scroll through the left panel until you find the "ALT" section and then find and select {{ic|ALT + Tab}}. Then, scroll through the right panel looking for the "Scale Windows" section and choose either {{ic|Select Next}} or {{ic|Select Next (All)}} depending on whether you would like to see windows from only the current desktop or from all desktops and click "Apply" to save the binding.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{ic|~/.e}} and remove it (e.g. {{ic|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream. http://trac.enlightenment.org/e/report<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Pkg|libxcursor}} package.<br />
<br />
=== Screen unlocking does not work ===<br />
<br />
If screenlock does not accept your password add the following to {{ic|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-dejavu ttf-bitstream-vera<br />
<br />
=== udisks vs. HAL ===<br />
Modules may need to use underlying libraries or daemons to interact with various devices connected to your computer. Currently there are at least two choices for these underlying libraries or daemons to interact with connected devices. The two that will be considered here are udisks and HAL. At the time of this entry the [[HAL]] page says:<br />
:''HAL (Hardware Abstraction Layer) is a daemon that allows desktop applications to readily access hardware information, to locate and use such hardware regardless of bus or device type. In this way a desktop GUI can present all resources to its user in a seamless and uniform manner. HAL has become deprecated in favor of udev, udisks, upower, etc. and is no longer developed. Currently, a small number of programs still rely on and use HAL, though development is heading toward utilizing udev as a replacement.''<br />
<br />
So, apparently [[E17]] now tries to use udisks instead of [[HAL]]. But some of the modules and gadgets, such as Places, have not been updated to use udisks yet.<br />
<br />
=== Places does not work ===<br />
If the Places gadget look something like a blank grey area with no Gadget in it and not detecting new device, it may because the Places is still trying to use [[HAL]]. Here is the procedure to get the HAL daemon running:<br />
<br />
Install {{AUR|hal-info}} and {{AUR|hal-git}} from the [[Arch User Repository]]. Note that {{AUR|hal-info}} is a dependency for {{AUR|hal-git}}, so you may want to install it with [[pacman]]'s {{ic|--asdeps}} flag.<br />
<br />
Start the hal daemon:<br />
<br />
{{bc|# systemctl start hal}}<br />
<br />
Now you must remove the "Places" gadget from my shelf, and unload the Places module from menu {{ic|settings -> modules -> Places -> unload}}<br />
<br />
Restart enlightenment, reload the Places module and add the Places gadget to my shelf. Then Places will work normally.<br />
<br />
=== Failure in mounting internal partitions ===<br />
Check if user is in storge group:<br />
{{bc|# groups <user>}}<br />
<br />
If user is not in storage group:<br />
{{bc|# groupadd storage <br />
# gpasswd -a <user> storage}}<br />
<br />
Then create this file as root:<br />
{{bc|# nano /etc/polkit-1/localauthority/50-local.d/10-storage-group-mount-override.pkla}}<br />
<br />
And write into the file:<br />
<br />
[storage group mount override]<br />
Identity=unix-group:storage<br />
Action=org.freedesktop.udisks2.filesystem-mount-system<br />
ResultAny=yes<br />
ResultInactive=yes<br />
ResultActive=yes<br />
<br />
For more information, see:<br />
http://bbs.archbang.org/viewtopic.php?id=2720<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]<br />
* [http://www.bodhilinux.com/e17guide/e17guideEN/ Bodhi Guide to Enlightenment]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=237037
E17
2012-11-27T19:06:33Z
<p>Foolishgrunt: /* Configuring the Network */</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[cs:E17]]<br />
[[es:E17]]<br />
[[fr:E17]]<br />
[[it:E17]]<br />
[[lt:E17]]<br />
[[pl:E17]]<br />
[[ru:E17]]<br />
[[zh-CN:E17]]<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From the [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment wiki]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It comprises both the Enlightenment [[window manager]] and Enlightenment Foundation Libraries (EFL), which provide additional desktop environment features such as a toolkit, object canvas, and abstracted objects. E17 has been under development since 2005, but in February 2011 the core EFLs saw their first stable 1.0 release. Enlightenment the window manager is still in the beta stages, but is already quite usable. Many people currently use E17 as a day-to-day desktop environment without problems.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the extra repository ===<br />
<br />
To install e17:<br />
pacman -S enlightenment17<br />
<br />
You might also want to install additional [[Fonts]]. You need at least 1 True Type Font.<br />
<br />
If you need/want an e17 package which is not (yet) available in [extra], see if it is available in the [[AUR]].<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{ic|easy_e17.sh}} compiles E17 from source and installs it in {{ic|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{AUR|easy-e17}}.<br />
# Edit {{ic|/etc/easy_e17.conf}} if you want.<br />
# Run it as user, so it downloads to ~/e17_src and builds as user, to install E17 (the script will immediately ask for your password so it can install in the end): {{bc|# easy_e17.sh -i}}{{Warning|This will install the latest svn version. For a stable result add the <nowiki>--srcrev=</nowiki> parameter with the latest stable revision. For beta 3 use 55246 as argument. For the revision with the 1.0 release of the core libraries, use 56361, and for the 1.1 release use 65800 ([http://enlightenment.org/p.php?p&#61;news/show&l&#61;en&news_id&#61;37 2 Dec. 2011]).}}<br />
# Put {{ic|/opt/e17/bin}} in your {{ic|PATH}} by editing {{ic|/etc/profile}}. For example, you can add this line at the end of the file: {{bc|1=PATH="$PATH:/opt/e17/bin"}}<br />
# If, after completing the install, xinitrc complains that it cannot find enlightenment upon starting, you may need to add these lines to the end of /etc/profile as well:{{bc|1=PYTHONPATH=":$PYTHONPATH"}}{{bc|1=LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/e17/lib"}}<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it is not a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{ic|update_e17.sh}} is a zenity script which is made to accompany {{ic|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
=== startx ===<br />
If you use {{ic|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
=== Elsa ===<br />
Nowadays E17 has a new display manager called Elsa, you can download it from AUR {{AUR|elsa-svn-arch}}.<br />
Elsa is quite sophisticated and its configuration is controlled by {{ic|/etc/elsa.conf}}.<br />
To start Elsa add the following line to your {{ic|/etc/inittab}}<br />
x:5:respawn:/usr/sbin/elsa<br />
and change your default runlevel to 5.<br />
<br />
=== Other ===<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{ic|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{ic|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
=== ConnMan ===<br />
<br />
E17's preferred network manager is [[ConnMan]]. It is available from the [community] repository as the {{Pkg|connman}} package. To interface with E17's default Network module, you must also download EConmman (available in AUR as {{AUR|econnman-svn}}) and it's associated dependencies.<br />
<br />
Finally, configure systemd to start the Connman daemon at startup:<br />
<br />
systemctl enable connman.service<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you have installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
=== NetworkManager ===<br />
<br />
You can also use {{Pkg|networkmanager}} to manage your network connections.<br />
<br />
pacman -S networkmanager<br />
<br />
Follow the instructions on [[NetworkManager]] to do the configuration. You may also need {{Pkg|network-manager-applet}} to help with your settings.<br />
<br />
pacman -S network-manager-applet<br />
<br />
You may want to add it to the start up programs so every time your E17 starts it appears on systray.<br />
<br />
Settings -> Settings Panel -> Apps -> Startup Applications -> System -> Network<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog. During 2010 there was a change in how themes work, so for older themes you may need to do the following:<br />
edje_convert <theme>.edj<br />
<br />
{{Note|The edje_convert binary has been "dropped" by upstream developers... see: [http://trac.enlightenment.org/e/changeset/56156 trac.enlightenment.org]}}<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{ic|etk_prefs}}.<br />
<br />
== Modules and Gadgets ==<br />
;Module:Name used in enlightenment to refer to the "backing" code for a gadget. <br />
;Gadget:Front-end or user interface that should help the end users of [[E17]] do something.<br />
<br />
Many Modules provide Gadgets that can be added to your desktop or on a shelf. Some Modules (such as CPUFreq) only provide a single Gadget while others (such as Composite) provide additional features without any gadgets. Note that certain gadgets such as Systray can only be added to a shelf while others such as Moon can only be loaded on the desktop. <br />
<br />
=== Compositing ===<br />
E17 offers two modules for compositing, '''''Composite''''' and '''''Ecomorph''''', depending on your hardware and preference.<br />
<br />
==== Composite ====<br />
The ''Composite'' module is the standard compositing manager provided in enlightenment. It provides some minimal compositing effects such as transparency, fade and shadow. Composite provides the more stable module and is supported on a lot hardware through either OpenGL or compositing software rendering.<br />
<br />
==== Ecomorph ====<br />
The ''Ecomorph'' module is a full-featured compositing manager which was ported from [[Compiz]] for E17. It can be downloaded from AUR {{AUR|ecomorph-git}}. Some experience instability with Ecomorph while others use it without a problem. Ecomorph requires 3D acceleration, while Composite does not. <br />
<br />
=== Places ===<br />
From the current source code [http://trac.enlightenment.org/e/browser/trunk/E-MODULES-EXTRA/places/README README] for Places:<br />
;Places module:''This module manage the volumes device attached to the system.''<br />
<br />
In other words, Places is a gadget that will help you browse files on various devices you might plug into your computer, like phones, cameras, or other various storage devices you might plug into the usb port.<br />
<br />
=== Scale Windows ===<br />
The ''Scale Windows'' module, which requires compositing to be enabled, shrinks all open windows and brings them all into view. It can be added to the desktop as a gadget or set as a key binding. <br />
<br />
Some people like to change the standard window selection key binding {{ic|ALT + Tab}} to use Scale Windows to select windows. To change this setting, you navigate to {{ic|Menu > Settings > Settings Panel > Input > Keys}}. From here, you can set any key binding you would like. <br />
<br />
To replace the window selection key binding functionality with Scale Windows, scroll through the left panel until you find the "ALT" section and then find and select {{ic|ALT + Tab}}. Then, scroll through the right panel looking for the "Scale Windows" section and choose either {{ic|Select Next}} or {{ic|Select Next (All)}} depending on whether you would like to see windows from only the current desktop or from all desktops and click "Apply" to save the binding.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{ic|~/.e}} and remove it (e.g. {{ic|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream. http://trac.enlightenment.org/e/report<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Pkg|libxcursor}} package.<br />
<br />
=== Screen unlocking does not work ===<br />
<br />
If screenlock does not accept your password add the following to {{ic|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-dejavu ttf-bitstream-vera<br />
<br />
=== udisks vs. HAL ===<br />
Modules may need to use underlying libraries or daemons to interact with various devices connected to your computer. Currently there are at least two choices for these underlying libraries or daemons to interact with connected devices. The two that will be considered here are udisks and HAL. At the time of this entry the [[HAL]] page says:<br />
:''HAL (Hardware Abstraction Layer) is a daemon that allows desktop applications to readily access hardware information, to locate and use such hardware regardless of bus or device type. In this way a desktop GUI can present all resources to its user in a seamless and uniform manner. HAL has become deprecated in favor of udev, udisks, upower, etc. and is no longer developed. Currently, a small number of programs still rely on and use HAL, though development is heading toward utilizing udev as a replacement.''<br />
<br />
So, apparently [[E17]] now tries to use udisks instead of [[HAL]]. But some of the modules and gadgets, such as Places, have not been updated to use udisks yet.<br />
<br />
=== Places does not work ===<br />
If the Places gadget look something like a blank grey area with no Gadget in it and not detecting new device, it may because the Places is still trying to use [[HAL]]. Here is the procedure to get the HAL daemon running:<br />
<br />
Install {{AUR|hal-info}} and {{AUR|hal-git}} from the [[Arch User Repository]]. Note that {{AUR|hal-info}} is a dependency for {{AUR|hal-git}}, so you may want to install it with [[pacman]]'s {{ic|--asdeps}} flag.<br />
<br />
Start the hal daemon:<br />
<br />
{{bc|# systemctl start hal}}<br />
<br />
Now you must remove the "Places" gadget from my shelf, and unload the Places module from menu {{ic|settings -> modules -> Places -> unload}}<br />
<br />
Restart enlightenment, reload the Places module and add the Places gadget to my shelf. Then Places will work normally.<br />
<br />
=== Failure in mounting internal partitions ===<br />
Check if user is in storge group:<br />
{{bc|# groups <user>}}<br />
<br />
If user is not in storage group:<br />
{{bc|# groupadd storage <br />
# gpasswd -a <user> storage}}<br />
<br />
Then create this file as root:<br />
{{bc|# nano /etc/polkit-1/localauthority/50-local.d/10-storage-group-mount-override.pkla}}<br />
<br />
And write into the file:<br />
<br />
[storage group mount override]<br />
Identity=unix-group:storage<br />
Action=org.freedesktop.udisks2.filesystem-mount-system<br />
ResultAny=yes<br />
ResultInactive=yes<br />
ResultActive=yes<br />
<br />
For more information, see:<br />
http://bbs.archbang.org/viewtopic.php?id=2720<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]<br />
* [http://www.bodhilinux.com/e17guide/e17guideEN/ Bodhi Guide to Enlightenment]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=237036
E17
2012-11-27T19:01:21Z
<p>Foolishgrunt: /* Configuring the Network */</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[cs:E17]]<br />
[[es:E17]]<br />
[[fr:E17]]<br />
[[it:E17]]<br />
[[lt:E17]]<br />
[[pl:E17]]<br />
[[ru:E17]]<br />
[[zh-CN:E17]]<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From the [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment wiki]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It comprises both the Enlightenment [[window manager]] and Enlightenment Foundation Libraries (EFL), which provide additional desktop environment features such as a toolkit, object canvas, and abstracted objects. E17 has been under development since 2005, but in February 2011 the core EFLs saw their first stable 1.0 release. Enlightenment the window manager is still in the beta stages, but is already quite usable. Many people currently use E17 as a day-to-day desktop environment without problems.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the extra repository ===<br />
<br />
To install e17:<br />
pacman -S enlightenment17<br />
<br />
You might also want to install additional [[Fonts]]. You need at least 1 True Type Font.<br />
<br />
If you need/want an e17 package which is not (yet) available in [extra], see if it is available in the [[AUR]].<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{ic|easy_e17.sh}} compiles E17 from source and installs it in {{ic|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{AUR|easy-e17}}.<br />
# Edit {{ic|/etc/easy_e17.conf}} if you want.<br />
# Run it as user, so it downloads to ~/e17_src and builds as user, to install E17 (the script will immediately ask for your password so it can install in the end): {{bc|# easy_e17.sh -i}}{{Warning|This will install the latest svn version. For a stable result add the <nowiki>--srcrev=</nowiki> parameter with the latest stable revision. For beta 3 use 55246 as argument. For the revision with the 1.0 release of the core libraries, use 56361, and for the 1.1 release use 65800 ([http://enlightenment.org/p.php?p&#61;news/show&l&#61;en&news_id&#61;37 2 Dec. 2011]).}}<br />
# Put {{ic|/opt/e17/bin}} in your {{ic|PATH}} by editing {{ic|/etc/profile}}. For example, you can add this line at the end of the file: {{bc|1=PATH="$PATH:/opt/e17/bin"}}<br />
# If, after completing the install, xinitrc complains that it cannot find enlightenment upon starting, you may need to add these lines to the end of /etc/profile as well:{{bc|1=PYTHONPATH=":$PYTHONPATH"}}{{bc|1=LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/e17/lib"}}<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it is not a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{ic|update_e17.sh}} is a zenity script which is made to accompany {{ic|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
=== startx ===<br />
If you use {{ic|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
=== Elsa ===<br />
Nowadays E17 has a new display manager called Elsa, you can download it from AUR {{AUR|elsa-svn-arch}}.<br />
Elsa is quite sophisticated and its configuration is controlled by {{ic|/etc/elsa.conf}}.<br />
To start Elsa add the following line to your {{ic|/etc/inittab}}<br />
x:5:respawn:/usr/sbin/elsa<br />
and change your default runlevel to 5.<br />
<br />
=== Other ===<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{ic|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{ic|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
=== connman ===<br />
<br />
E17's preferred network manager is [[Connman]]. It is available from the [community] repository as the {{Pkg|connman}} package. To interface with E17's default Network module, you must also download EConmman (available in AUR as {{AUR|econnman-svn}}) and it's associated dependencies.<br />
<br />
Finally, configure systemd to start the Connman daemon at startup:<br />
<br />
systemctl enable connman.service<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you have installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
=== NetworkManager ===<br />
<br />
You can also use {{Pkg|networkmanager}} to manage your network connections.<br />
<br />
pacman -S networkmanager<br />
<br />
Follow the instructions on [[NetworkManager]] to do the configuration. You may also need {{Pkg|network-manager-applet}} to help with your settings.<br />
<br />
pacman -S network-manager-applet<br />
<br />
You may want to add it to the start up programs so every time your E17 starts it appears on systray.<br />
<br />
Settings -> Settings Panel -> Apps -> Startup Applications -> System -> Network<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog. During 2010 there was a change in how themes work, so for older themes you may need to do the following:<br />
edje_convert <theme>.edj<br />
<br />
{{Note|The edje_convert binary has been "dropped" by upstream developers... see: [http://trac.enlightenment.org/e/changeset/56156 trac.enlightenment.org]}}<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{ic|etk_prefs}}.<br />
<br />
== Modules and Gadgets ==<br />
;Module:Name used in enlightenment to refer to the "backing" code for a gadget. <br />
;Gadget:Front-end or user interface that should help the end users of [[E17]] do something.<br />
<br />
Many Modules provide Gadgets that can be added to your desktop or on a shelf. Some Modules (such as CPUFreq) only provide a single Gadget while others (such as Composite) provide additional features without any gadgets. Note that certain gadgets such as Systray can only be added to a shelf while others such as Moon can only be loaded on the desktop. <br />
<br />
=== Compositing ===<br />
E17 offers two modules for compositing, '''''Composite''''' and '''''Ecomorph''''', depending on your hardware and preference.<br />
<br />
==== Composite ====<br />
The ''Composite'' module is the standard compositing manager provided in enlightenment. It provides some minimal compositing effects such as transparency, fade and shadow. Composite provides the more stable module and is supported on a lot hardware through either OpenGL or compositing software rendering.<br />
<br />
==== Ecomorph ====<br />
The ''Ecomorph'' module is a full-featured compositing manager which was ported from [[Compiz]] for E17. It can be downloaded from AUR {{AUR|ecomorph-git}}. Some experience instability with Ecomorph while others use it without a problem. Ecomorph requires 3D acceleration, while Composite does not. <br />
<br />
=== Places ===<br />
From the current source code [http://trac.enlightenment.org/e/browser/trunk/E-MODULES-EXTRA/places/README README] for Places:<br />
;Places module:''This module manage the volumes device attached to the system.''<br />
<br />
In other words, Places is a gadget that will help you browse files on various devices you might plug into your computer, like phones, cameras, or other various storage devices you might plug into the usb port.<br />
<br />
=== Scale Windows ===<br />
The ''Scale Windows'' module, which requires compositing to be enabled, shrinks all open windows and brings them all into view. It can be added to the desktop as a gadget or set as a key binding. <br />
<br />
Some people like to change the standard window selection key binding {{ic|ALT + Tab}} to use Scale Windows to select windows. To change this setting, you navigate to {{ic|Menu > Settings > Settings Panel > Input > Keys}}. From here, you can set any key binding you would like. <br />
<br />
To replace the window selection key binding functionality with Scale Windows, scroll through the left panel until you find the "ALT" section and then find and select {{ic|ALT + Tab}}. Then, scroll through the right panel looking for the "Scale Windows" section and choose either {{ic|Select Next}} or {{ic|Select Next (All)}} depending on whether you would like to see windows from only the current desktop or from all desktops and click "Apply" to save the binding.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{ic|~/.e}} and remove it (e.g. {{ic|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream. http://trac.enlightenment.org/e/report<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Pkg|libxcursor}} package.<br />
<br />
=== Screen unlocking does not work ===<br />
<br />
If screenlock does not accept your password add the following to {{ic|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-dejavu ttf-bitstream-vera<br />
<br />
=== udisks vs. HAL ===<br />
Modules may need to use underlying libraries or daemons to interact with various devices connected to your computer. Currently there are at least two choices for these underlying libraries or daemons to interact with connected devices. The two that will be considered here are udisks and HAL. At the time of this entry the [[HAL]] page says:<br />
:''HAL (Hardware Abstraction Layer) is a daemon that allows desktop applications to readily access hardware information, to locate and use such hardware regardless of bus or device type. In this way a desktop GUI can present all resources to its user in a seamless and uniform manner. HAL has become deprecated in favor of udev, udisks, upower, etc. and is no longer developed. Currently, a small number of programs still rely on and use HAL, though development is heading toward utilizing udev as a replacement.''<br />
<br />
So, apparently [[E17]] now tries to use udisks instead of [[HAL]]. But some of the modules and gadgets, such as Places, have not been updated to use udisks yet.<br />
<br />
=== Places does not work ===<br />
If the Places gadget look something like a blank grey area with no Gadget in it and not detecting new device, it may because the Places is still trying to use [[HAL]]. Here is the procedure to get the HAL daemon running:<br />
<br />
Install {{AUR|hal-info}} and {{AUR|hal-git}} from the [[Arch User Repository]]. Note that {{AUR|hal-info}} is a dependency for {{AUR|hal-git}}, so you may want to install it with [[pacman]]'s {{ic|--asdeps}} flag.<br />
<br />
Start the hal daemon:<br />
<br />
{{bc|# systemctl start hal}}<br />
<br />
Now you must remove the "Places" gadget from my shelf, and unload the Places module from menu {{ic|settings -> modules -> Places -> unload}}<br />
<br />
Restart enlightenment, reload the Places module and add the Places gadget to my shelf. Then Places will work normally.<br />
<br />
=== Failure in mounting internal partitions ===<br />
Check if user is in storge group:<br />
{{bc|# groups <user>}}<br />
<br />
If user is not in storage group:<br />
{{bc|# groupadd storage <br />
# gpasswd -a <user> storage}}<br />
<br />
Then create this file as root:<br />
{{bc|# nano /etc/polkit-1/localauthority/50-local.d/10-storage-group-mount-override.pkla}}<br />
<br />
And write into the file:<br />
<br />
[storage group mount override]<br />
Identity=unix-group:storage<br />
Action=org.freedesktop.udisks2.filesystem-mount-system<br />
ResultAny=yes<br />
ResultInactive=yes<br />
ResultActive=yes<br />
<br />
For more information, see:<br />
http://bbs.archbang.org/viewtopic.php?id=2720<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]<br />
* [http://www.bodhilinux.com/e17guide/e17guideEN/ Bodhi Guide to Enlightenment]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Daemons_list&diff=237035
Daemons list
2012-11-27T19:00:46Z
<p>Foolishgrunt: </p>
<hr />
<div>[[Category:Boot process]]<br />
[[Category:Daemons and system services]]<br />
[[zh-cn:Daemons List]]<br />
Here is a list of daemons. Note that any package can provide a daemon, so this list will never be complete. Please feel free to add any missing daemons here, in alphabetical order.<br />
For each daemon the name of the script (for [[rc.conf|initscripts]]) and of the service (for [[systemd]]) is given.<br />
{| border="1"<br />
!initscripts!!systemd!!Description<br />
|-<br />
|[[acpid]]||acpid.service||Delivers ACPI events.<br />
|-<br />
|[[Advanced Linux Sound Architecture|alsa]]||alsa-store.service<br />
alsa-restore.service<br />
||Advanced Linux Sound Architecture; provides device drivers for sound cards.<br />
|-<br />
|atd||atd.service||Run jobs queued for later execution.<br />
|-<br />
|[[Avahi|avahi-daemon]]||avahi-daemon.service||Allows programs to automatically find local network services.<br />
|-<br />
|[[Avahi|avahi-dnsconfd]]||avahi-dnsconfd.service||<br />
|-<br />
|[[Bitlbee|bitlbee]]||bitlbee.service||BitlBee IRC/IM gateway.<br />
|-<br />
|[[Connman|connmand]]||connman.service||Alternative network manager.<br />
|-<br />
|[[Chrony|chrony]]||chrony.service||Alternative NTP client/server designed for systems not online all the time.<br />
|-<br />
|[[ClamAV|clamav]]||clamd.service<br />
freshclamd.service<br />
||Antivirus.<br />
|-<br />
|[[CPU_Frequency_Scaling|cpupower]]||cpupower.service||Userspace tools for the kernel cpufreq subsystem<br />
|-<br />
|craftbukkit||''not yet implemented''||CraftBukkit Minecraft server<br />
|-<br />
|[[Cron|crond]]||cronie.service||Daemon to schedule and time events. The daemon name ''crond'' is used by at least two packages, {{Pkg|cronie}} and {{Pkg|dcron}}.<br />
|-<br />
|[[CUPS|cupsd]]||cupsd.service<br />
''or'' cups.service<br />
||Common UNIX Printing System daemon.<br />
|-<br />
|[[D-Bus|dbus]]||dbus.service||Message bus system for software communication.<br />
|-<br />
|[[Cron|dcron]]||dcron.service||Daemon to schedule and time events. The daemon name ''crond'' is used by at least two packages, {{Pkg|cronie}} and {{Pkg|dcron}}. {{Pkg|cronie}} is the default cron implementation for Arch.<br />
|-<br />
|[[dante|sockd]]||sockd.service||A circuit-level SOCKS client/server.<br />
|-<br />
|[[Deluge|deluged]]||deluged.service||Cross-platform and full-featured BitTorrent client.<br />
|-<br />
|[[Deluge|deluge-web]]||deluge-web.service||Cross-platform and full-featured BitTorrent client web UI.<br />
|-<br />
|[[Dhcpcd|dhcpcd]]||dhcpcd@.service||DHCP daemon. Insert the network interface after @ ('dhcpcd@eth0.service'). <br />
|-<br />
|[[Dovecot|dovecot]]||dovecot.service||IMAP and POP3 server. <br />
|-<br />
|[[Dropbox|dropboxd]]||''not yet implemented''||Cross-platform file synchronisation with version control.<br />
|-<br />
|[[FAM|fam]]||''deprecated''||File Alteration Monitor. (deprecated)<br />
|-<br />
|fancontrol||fancontrol.service||Fan control daemon (part of lm_sensors)<br />
|-<br />
|[[Fbsplash|fbsplash]]||''not yet implemented''||Graphical boot splash screen for the user.<br />
|-<br />
|[[FluidSynth|fluidsynth]]||fluidsynth.service||Software synthesizer<br />
|-<br />
|ftpd||ftpd.service||Inetutils ftp daemon<br />
|-<br />
|[[GDM|gdm]]||gdm.service||Gnome Display Manager (Login Screen)<br />
|-<br />
|[[Git|git-daemon]]||git-daemon.socket||GIT daemon<br />
|-<br />
|[[Console Mouse Support|gpm]]||gpm.service||Console mouse support.<br />
|-<br />
|[[HAL|hal]]||''deprecated''||Hardware Abstraction Layer. (Deprecated)<br />
|-<br />
|hddtemp||hddtemp.service||Hard drive temperature monitor daemon<br />
|-<br />
|healthd||healthd.service||A daemon which can be used to alert you in the event of a hardware health monitoring alarm (part of lm_sensors).<br />
|-<br />
|-<br />
|[[LAMP|httpd]]||httpd.service||Apache HTTP Server (Web Server)<br />
|-<br />
|[[hwclock]]||||Not a daemon as such, but on shutdown, updates hwclock to compensate for drift. Only run this daemon if ntpd is not running as both daemons adjust the hardware clock.<br />
|-<br />
|iptables||iptables.service||Load firewall rules.<br />
|-<br />
|-<br />
|ip6tables||ip6tables.service||Load firewall rules for ipv6.<br />
|-<br />
|irqbalance||irqbalance.service||Irqbalance is the Linux utility tasked with making sure that interrupts from your hardware devices are handled in as efficient a manner as possible.<br />
|-<br />
|[[KDE|kdm]]||kdm.service||KDE Display Manager (Graphical Login)<br />
|-<br />
|krb5-kadmind||krb5-kadmind.service||Kerberos 5 administration server<br />
|-<br />
|krb5-kdc||krb5-kdc.service||Kerberos 5 KDC<br />
|-<br />
|krb5-kpropd||krb5-kpropd.service||Kerberos 5 propagation server<br />
|-<br />
|[[Laptop Mode Tools|laptop-mode]]||laptop-mode-tools.service||Laptop Power Saving Tools<br />
|-<br />
|[[lighttpd]]||lighttpd.service||Lighttpd HTTP Server (Web Server).<br />
|-<br />
|[[LXDE|lxdm]]||lxdm.service||LXDE Display Manager (Graphical Login)<br />
|-<br />
|mdadm||mdadm.service||MD Administration (Linux Software RAID).<br />
|-<br />
|[[miniDLNA]]||minidlna.service||simple DLNA/UPnP media server<br />
|-<br />
|[[Music Player Daemon|mpd]]||mpd.service||Music Player Daemon.<br />
|-<br />
|[[MySQL|mysqld]]||mysqld.service||MySQL database server.<br />
|-<br />
|[[MythTV|mythbackend]]||mythbackend.service||Backend for the MythTV digital video recording/home theater software.<br />
|-<br />
|[[BIND|named]]||named.service||The Berkeley Internet Name Daemon (BIND) DNS server.<br />
|-<br />
|netfs||''unused, handled automatically, see''<br />
remote-fs.target<br />
''to manually execute scripts''<br />
||Mounts network file systems.<br />
|-<br />
|[[Netcfg|net-auto-wired]]||net-auto-wired.service||Netcfg replacement for {{ic|network}} - connects to wired network<br />
|-<br />
|[[Netcfg|net-auto-wireless]]||net-auto-wireless.service||Netcfg replacement for {{ic|network}} - connects to wireless network<br />
|-<br />
|[[Netcfg|net-profiles]]||netcfg.service<br />
netcfg@<profile-name>.service<br />
||Netcfg replacement for {{ic|network}} - connects to profiles<br />
|-<br />
|[[Configuring_Network|network]]||''(dynamic Ethernet)'' dhcpcd@<interface>.service||To bring up the network connections.<br />
|-<br />
|[[NetworkManager|networkmanager]]||NetworkManager.service<br />
NetworkManager-wait-online.service<br />
||Replaces {{ic|network}}, and provides configuration and detection for automatic network connections.<br />
|-<br />
|[[Nginx|nginx]]||nginx.service||Nginx HTTP Server and IMAP/POP3 proxy server (Web Server)<br />
|-<br />
|nscd||nscd.service||Name service cache daemon<br />
|-<br />
|[[Network Time Protocol daemon|ntpd]]||ntpd.service||Network Time Protocol daemon (client and server).<br />
|-<br />
|[[Ntop|Ntop]]||ntop.service||Ntop is a network traffic probe based on libcap.<br />
|-<br />
|[[OpenNTPD|openntpd]]||openntpd.service||alternate Network Time Protocol daemon (client and server).<br />
|-<br />
|osspd||osspd.service||OSS Userspace Bridge.<br />
|-<br />
|[[OpenVPN|openvpn]]||openvpn@<profile-name>.service||One for each vpn conf file saved like /etc/openvpn/<profile-name>.conf<br />
|-<br />
|[[Pdnsd|pdnsd]]||pdnsd.service||Proxy DNS server with permanent caching.<br />
|-<br />
|[[Nginx#1st_Method_.22New.22_.28as_of_PHP_5.3.3.29|php-fpm]]||php-fpm.service||FastCGI Process Manager for PHP<br />
|-<br />
|[[OSS|oss]]||oss.service||Open Sound System. Alternative to ALSA.<br />
|-<br />
|[[PostgreSQL|postgresql]]||postgresql.service||PostgreSQL database server.<br />
|-<br />
|[[Postfix|postfix]]||postfix.service||<br />
|-<br />
|[[powernowd]]||''not yet implemented''||To adjust speed of CPU depending on system load. See also [[CPU Frequency Scaling]]<br />
|-<br />
|[[PPTP Server|pptpd]]||pptpd.service||A Virtual Private Network (VPN) server using the Point-to-Point Tunneling Protocol (PPTP).<br />
|-<br />
|[[Prosody|prosody]]||prosody.service||XMPP server.<br />
|-<br />
|[[pppd|Pppd]]||ppp@provider.service||A daemon which implements the Point-to-Point Protocol for dial-up networking.<br />
|-<br />
|[[preload]]||preload.service||Makes applications run faster by prefetching binaries and shared objects.<br />
|-<br />
|[[psd]]||psd.service||Manages your browser's profile in tmpfs and periodically sync it back to your physical disk.<br />
|-<br />
|pure-ftpd||''not yet implemented''||FTP server.<br />
|-<br />
|[[readahead]]||systemd-readahead-collect.service<br />
systemd-readahead-done.service<br />
<br />
systemd-readahead-drop.service<br />
<br />
systemd-readahead-replay.service<br />
||Readahead for faster boot<br />
|-<br />
||rfkill||rfkill-block@.service<br />
rfkill-unblock@.service<br />
||(Un)block radio devices. A block@all or unblock@all instance (not to be enabled simultaneously) is started before any unblock@device or block@device, respectively.<br />
|-<br />
|[[Rsync|rsyncd]]||rsyncd.service||Rsync daemon.<br />
|-<br />
|[[Rsyslog|rsyslogd]]||rsyslog.service||The latest version of a system logger.<br />
|-<br />
|[[samba]]||smbd.service<br />
nmbd.service<br />
<br />
winbindd.service<br />
||File and print services for Microsoft Windows clients.<br />
|-<br />
|[[USB_Scanner_Support|saned]]||saned@.service||To share the scanner system over network.<br />
|-<br />
|sensord||sensord.service||Sensor information logging daemon (part of lm_sensors)<br />
|-<br />
|[[Lm sensors|sensors]]||lm_sensors.service||Hardware (temperature, fans etc) monitoring.<br />
|-<br />
|[[SLiM|slim]]||slim.service||Simple Login Manager<br />
|-<br />
|[[SMART|smartd]]||smartd.service||Self-Monitoring, Analysis, and Reporting Technology (S.M.A.R.T) Hard Disk Monitoring<br />
|-<br />
|[[Samba#smbnetfs|smbnetfs]]||smbnetfs.service||To automatically mount Samba/Microsoft network shares.<br />
|-<br />
|snmpd||snmpd.service||A suite of applications used to implement SNMP<br />
|-<br />
|soundmodem||''not yet implemented''||Multiplatform Soundcard Packet Radio Modem<br />
|-<br />
|[[SOHO Postfix|spamd]]||spamassassin.service|| e-mail spam filtering service.<br />
|-<br />
|[[Secure Shell|sshd]]||sshd.service<br />
sshd@.service<br />
<br />
sshdgenkeys.service<br />
||OpenSSH (secure shell) daemon.<br />
|-<br />
|stbd||''deprecated''||This daemon was previously necessary for gnome-system-tools. However, as of gnome-tools 2.28, it is no longer needed.<br />
|-<br />
|[[stunnel]]||stunnel.service||Allows encrypting arbitrary TCP connections inside SSL.<br />
|-<br />
|svnserve||svnserve.service||Subversion server<br />
|-<br />
|syslogd||''deprecated''||This was the older and basic system logger.<br />
|-<br />
|[[syslog-ng]]||syslog-ng.service||System logger next generation.<br />
|-<br />
|[[Timidity|timidity++]]||timidity.service||Software synthesizer for MIDI.<br />
|-<br />
|[[Tor|tor]]||tor.service||Onion routing for anonymous communication.<br />
|-<br />
|[[Transmission|transmissiond]]||transmission.service||Bit Torrent Daemon.<br />
|-<br />
|[[Ufw|ufw]]||ufw.service||Uncomplicated FireWall.<br />
|-<br />
|[[VirtualBox|vboxservice]]||vboxservice.service||VirtualBox Guest Service<br />
|-<br />
|[[Very Secure FTP Daemon|vsftpd]]||vsftpd.service<br />
vsftpd@.service<br />
<br />
vsftpd-ssl.service<br />
||FTP server.<br />
|-<br />
|[[wicd]]||wicd.service||Combine with dbus to replace {{ic|network}}, a lightweight alternative to NetworkManager.<br />
|-<br />
|[[x11vnc]]||x11vnc.service||VNC remote desktop daemon <br />
|-<br />
|}</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Daemons_list&diff=237034
Daemons list
2012-11-27T19:00:07Z
<p>Foolishgrunt: </p>
<hr />
<div>[[Category:Boot process]]<br />
[[Category:Daemons and system services]]<br />
[[zh-cn:Daemons List]]<br />
Here is a list of daemons. Note that any package can provide a daemon, so this list will never be complete. Please feel free to add any missing daemons here, in alphabetical order.<br />
For each daemon the name of the script (for [[rc.conf|initscripts]]) and of the service (for [[systemd]]) is given.<br />
{| border="1"<br />
!initscripts!!systemd!!Description<br />
|-<br />
|[[acpid]]||acpid.service||Delivers ACPI events.<br />
|-<br />
|[[Advanced Linux Sound Architecture|alsa]]||alsa-store.service<br />
alsa-restore.service<br />
||Advanced Linux Sound Architecture; provides device drivers for sound cards.<br />
|-<br />
|atd||atd.service||Run jobs queued for later execution.<br />
|-<br />
|[[Avahi|avahi-daemon]]||avahi-daemon.service||Allows programs to automatically find local network services.<br />
|-<br />
|[[Avahi|avahi-dnsconfd]]||avahi-dnsconfd.service||<br />
|-<br />
|[[Bitlbee|bitlbee]]||bitlbee.service||BitlBee IRC/IM gateway.<br />
|-<br />
|[[Connman|connman]]||connman.service||Alternative network manager.<br />
|-<br />
|[[Chrony|chrony]]||chrony.service||Alternative NTP client/server designed for systems not online all the time.<br />
|-<br />
|[[ClamAV|clamav]]||clamd.service<br />
freshclamd.service<br />
||Antivirus.<br />
|-<br />
|[[CPU_Frequency_Scaling|cpupower]]||cpupower.service||Userspace tools for the kernel cpufreq subsystem<br />
|-<br />
|craftbukkit||''not yet implemented''||CraftBukkit Minecraft server<br />
|-<br />
|[[Cron|crond]]||cronie.service||Daemon to schedule and time events. The daemon name ''crond'' is used by at least two packages, {{Pkg|cronie}} and {{Pkg|dcron}}.<br />
|-<br />
|[[CUPS|cupsd]]||cupsd.service<br />
''or'' cups.service<br />
||Common UNIX Printing System daemon.<br />
|-<br />
|[[D-Bus|dbus]]||dbus.service||Message bus system for software communication.<br />
|-<br />
|[[Cron|dcron]]||dcron.service||Daemon to schedule and time events. The daemon name ''crond'' is used by at least two packages, {{Pkg|cronie}} and {{Pkg|dcron}}. {{Pkg|cronie}} is the default cron implementation for Arch.<br />
|-<br />
|[[dante|sockd]]||sockd.service||A circuit-level SOCKS client/server.<br />
|-<br />
|[[Deluge|deluged]]||deluged.service||Cross-platform and full-featured BitTorrent client.<br />
|-<br />
|[[Deluge|deluge-web]]||deluge-web.service||Cross-platform and full-featured BitTorrent client web UI.<br />
|-<br />
|[[Dhcpcd|dhcpcd]]||dhcpcd@.service||DHCP daemon. Insert the network interface after @ ('dhcpcd@eth0.service'). <br />
|-<br />
|[[Dovecot|dovecot]]||dovecot.service||IMAP and POP3 server. <br />
|-<br />
|[[Dropbox|dropboxd]]||''not yet implemented''||Cross-platform file synchronisation with version control.<br />
|-<br />
|[[FAM|fam]]||''deprecated''||File Alteration Monitor. (deprecated)<br />
|-<br />
|fancontrol||fancontrol.service||Fan control daemon (part of lm_sensors)<br />
|-<br />
|[[Fbsplash|fbsplash]]||''not yet implemented''||Graphical boot splash screen for the user.<br />
|-<br />
|[[FluidSynth|fluidsynth]]||fluidsynth.service||Software synthesizer<br />
|-<br />
|ftpd||ftpd.service||Inetutils ftp daemon<br />
|-<br />
|[[GDM|gdm]]||gdm.service||Gnome Display Manager (Login Screen)<br />
|-<br />
|[[Git|git-daemon]]||git-daemon.socket||GIT daemon<br />
|-<br />
|[[Console Mouse Support|gpm]]||gpm.service||Console mouse support.<br />
|-<br />
|[[HAL|hal]]||''deprecated''||Hardware Abstraction Layer. (Deprecated)<br />
|-<br />
|hddtemp||hddtemp.service||Hard drive temperature monitor daemon<br />
|-<br />
|healthd||healthd.service||A daemon which can be used to alert you in the event of a hardware health monitoring alarm (part of lm_sensors).<br />
|-<br />
|-<br />
|[[LAMP|httpd]]||httpd.service||Apache HTTP Server (Web Server)<br />
|-<br />
|[[hwclock]]||||Not a daemon as such, but on shutdown, updates hwclock to compensate for drift. Only run this daemon if ntpd is not running as both daemons adjust the hardware clock.<br />
|-<br />
|iptables||iptables.service||Load firewall rules.<br />
|-<br />
|-<br />
|ip6tables||ip6tables.service||Load firewall rules for ipv6.<br />
|-<br />
|irqbalance||irqbalance.service||Irqbalance is the Linux utility tasked with making sure that interrupts from your hardware devices are handled in as efficient a manner as possible.<br />
|-<br />
|[[KDE|kdm]]||kdm.service||KDE Display Manager (Graphical Login)<br />
|-<br />
|krb5-kadmind||krb5-kadmind.service||Kerberos 5 administration server<br />
|-<br />
|krb5-kdc||krb5-kdc.service||Kerberos 5 KDC<br />
|-<br />
|krb5-kpropd||krb5-kpropd.service||Kerberos 5 propagation server<br />
|-<br />
|[[Laptop Mode Tools|laptop-mode]]||laptop-mode-tools.service||Laptop Power Saving Tools<br />
|-<br />
|[[lighttpd]]||lighttpd.service||Lighttpd HTTP Server (Web Server).<br />
|-<br />
|[[LXDE|lxdm]]||lxdm.service||LXDE Display Manager (Graphical Login)<br />
|-<br />
|mdadm||mdadm.service||MD Administration (Linux Software RAID).<br />
|-<br />
|[[miniDLNA]]||minidlna.service||simple DLNA/UPnP media server<br />
|-<br />
|[[Music Player Daemon|mpd]]||mpd.service||Music Player Daemon.<br />
|-<br />
|[[MySQL|mysqld]]||mysqld.service||MySQL database server.<br />
|-<br />
|[[MythTV|mythbackend]]||mythbackend.service||Backend for the MythTV digital video recording/home theater software.<br />
|-<br />
|[[BIND|named]]||named.service||The Berkeley Internet Name Daemon (BIND) DNS server.<br />
|-<br />
|netfs||''unused, handled automatically, see''<br />
remote-fs.target<br />
''to manually execute scripts''<br />
||Mounts network file systems.<br />
|-<br />
|[[Netcfg|net-auto-wired]]||net-auto-wired.service||Netcfg replacement for {{ic|network}} - connects to wired network<br />
|-<br />
|[[Netcfg|net-auto-wireless]]||net-auto-wireless.service||Netcfg replacement for {{ic|network}} - connects to wireless network<br />
|-<br />
|[[Netcfg|net-profiles]]||netcfg.service<br />
netcfg@<profile-name>.service<br />
||Netcfg replacement for {{ic|network}} - connects to profiles<br />
|-<br />
|[[Configuring_Network|network]]||''(dynamic Ethernet)'' dhcpcd@<interface>.service||To bring up the network connections.<br />
|-<br />
|[[NetworkManager|networkmanager]]||NetworkManager.service<br />
NetworkManager-wait-online.service<br />
||Replaces {{ic|network}}, and provides configuration and detection for automatic network connections.<br />
|-<br />
|[[Nginx|nginx]]||nginx.service||Nginx HTTP Server and IMAP/POP3 proxy server (Web Server)<br />
|-<br />
|nscd||nscd.service||Name service cache daemon<br />
|-<br />
|[[Network Time Protocol daemon|ntpd]]||ntpd.service||Network Time Protocol daemon (client and server).<br />
|-<br />
|[[Ntop|Ntop]]||ntop.service||Ntop is a network traffic probe based on libcap.<br />
|-<br />
|[[OpenNTPD|openntpd]]||openntpd.service||alternate Network Time Protocol daemon (client and server).<br />
|-<br />
|osspd||osspd.service||OSS Userspace Bridge.<br />
|-<br />
|[[OpenVPN|openvpn]]||openvpn@<profile-name>.service||One for each vpn conf file saved like /etc/openvpn/<profile-name>.conf<br />
|-<br />
|[[Pdnsd|pdnsd]]||pdnsd.service||Proxy DNS server with permanent caching.<br />
|-<br />
|[[Nginx#1st_Method_.22New.22_.28as_of_PHP_5.3.3.29|php-fpm]]||php-fpm.service||FastCGI Process Manager for PHP<br />
|-<br />
|[[OSS|oss]]||oss.service||Open Sound System. Alternative to ALSA.<br />
|-<br />
|[[PostgreSQL|postgresql]]||postgresql.service||PostgreSQL database server.<br />
|-<br />
|[[Postfix|postfix]]||postfix.service||<br />
|-<br />
|[[powernowd]]||''not yet implemented''||To adjust speed of CPU depending on system load. See also [[CPU Frequency Scaling]]<br />
|-<br />
|[[PPTP Server|pptpd]]||pptpd.service||A Virtual Private Network (VPN) server using the Point-to-Point Tunneling Protocol (PPTP).<br />
|-<br />
|[[Prosody|prosody]]||prosody.service||XMPP server.<br />
|-<br />
|[[pppd|Pppd]]||ppp@provider.service||A daemon which implements the Point-to-Point Protocol for dial-up networking.<br />
|-<br />
|[[preload]]||preload.service||Makes applications run faster by prefetching binaries and shared objects.<br />
|-<br />
|[[psd]]||psd.service||Manages your browser's profile in tmpfs and periodically sync it back to your physical disk.<br />
|-<br />
|pure-ftpd||''not yet implemented''||FTP server.<br />
|-<br />
|[[readahead]]||systemd-readahead-collect.service<br />
systemd-readahead-done.service<br />
<br />
systemd-readahead-drop.service<br />
<br />
systemd-readahead-replay.service<br />
||Readahead for faster boot<br />
|-<br />
||rfkill||rfkill-block@.service<br />
rfkill-unblock@.service<br />
||(Un)block radio devices. A block@all or unblock@all instance (not to be enabled simultaneously) is started before any unblock@device or block@device, respectively.<br />
|-<br />
|[[Rsync|rsyncd]]||rsyncd.service||Rsync daemon.<br />
|-<br />
|[[Rsyslog|rsyslogd]]||rsyslog.service||The latest version of a system logger.<br />
|-<br />
|[[samba]]||smbd.service<br />
nmbd.service<br />
<br />
winbindd.service<br />
||File and print services for Microsoft Windows clients.<br />
|-<br />
|[[USB_Scanner_Support|saned]]||saned@.service||To share the scanner system over network.<br />
|-<br />
|sensord||sensord.service||Sensor information logging daemon (part of lm_sensors)<br />
|-<br />
|[[Lm sensors|sensors]]||lm_sensors.service||Hardware (temperature, fans etc) monitoring.<br />
|-<br />
|[[SLiM|slim]]||slim.service||Simple Login Manager<br />
|-<br />
|[[SMART|smartd]]||smartd.service||Self-Monitoring, Analysis, and Reporting Technology (S.M.A.R.T) Hard Disk Monitoring<br />
|-<br />
|[[Samba#smbnetfs|smbnetfs]]||smbnetfs.service||To automatically mount Samba/Microsoft network shares.<br />
|-<br />
|snmpd||snmpd.service||A suite of applications used to implement SNMP<br />
|-<br />
|soundmodem||''not yet implemented''||Multiplatform Soundcard Packet Radio Modem<br />
|-<br />
|[[SOHO Postfix|spamd]]||spamassassin.service|| e-mail spam filtering service.<br />
|-<br />
|[[Secure Shell|sshd]]||sshd.service<br />
sshd@.service<br />
<br />
sshdgenkeys.service<br />
||OpenSSH (secure shell) daemon.<br />
|-<br />
|stbd||''deprecated''||This daemon was previously necessary for gnome-system-tools. However, as of gnome-tools 2.28, it is no longer needed.<br />
|-<br />
|[[stunnel]]||stunnel.service||Allows encrypting arbitrary TCP connections inside SSL.<br />
|-<br />
|svnserve||svnserve.service||Subversion server<br />
|-<br />
|syslogd||''deprecated''||This was the older and basic system logger.<br />
|-<br />
|[[syslog-ng]]||syslog-ng.service||System logger next generation.<br />
|-<br />
|[[Timidity|timidity++]]||timidity.service||Software synthesizer for MIDI.<br />
|-<br />
|[[Tor|tor]]||tor.service||Onion routing for anonymous communication.<br />
|-<br />
|[[Transmission|transmissiond]]||transmission.service||Bit Torrent Daemon.<br />
|-<br />
|[[Ufw|ufw]]||ufw.service||Uncomplicated FireWall.<br />
|-<br />
|[[VirtualBox|vboxservice]]||vboxservice.service||VirtualBox Guest Service<br />
|-<br />
|[[Very Secure FTP Daemon|vsftpd]]||vsftpd.service<br />
vsftpd@.service<br />
<br />
vsftpd-ssl.service<br />
||FTP server.<br />
|-<br />
|[[wicd]]||wicd.service||Combine with dbus to replace {{ic|network}}, a lightweight alternative to NetworkManager.<br />
|-<br />
|[[x11vnc]]||x11vnc.service||VNC remote desktop daemon <br />
|-<br />
|}</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=237033
E17
2012-11-27T18:59:17Z
<p>Foolishgrunt: /* Configuring the Network */ Updated Connman section, + systemd instructions.</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[cs:E17]]<br />
[[es:E17]]<br />
[[fr:E17]]<br />
[[it:E17]]<br />
[[lt:E17]]<br />
[[pl:E17]]<br />
[[ru:E17]]<br />
[[zh-CN:E17]]<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From the [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment wiki]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It comprises both the Enlightenment [[window manager]] and Enlightenment Foundation Libraries (EFL), which provide additional desktop environment features such as a toolkit, object canvas, and abstracted objects. E17 has been under development since 2005, but in February 2011 the core EFLs saw their first stable 1.0 release. Enlightenment the window manager is still in the beta stages, but is already quite usable. Many people currently use E17 as a day-to-day desktop environment without problems.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the extra repository ===<br />
<br />
To install e17:<br />
pacman -S enlightenment17<br />
<br />
You might also want to install additional [[Fonts]]. You need at least 1 True Type Font.<br />
<br />
If you need/want an e17 package which is not (yet) available in [extra], see if it is available in the [[AUR]].<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{ic|easy_e17.sh}} compiles E17 from source and installs it in {{ic|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{AUR|easy-e17}}.<br />
# Edit {{ic|/etc/easy_e17.conf}} if you want.<br />
# Run it as user, so it downloads to ~/e17_src and builds as user, to install E17 (the script will immediately ask for your password so it can install in the end): {{bc|# easy_e17.sh -i}}{{Warning|This will install the latest svn version. For a stable result add the <nowiki>--srcrev=</nowiki> parameter with the latest stable revision. For beta 3 use 55246 as argument. For the revision with the 1.0 release of the core libraries, use 56361, and for the 1.1 release use 65800 ([http://enlightenment.org/p.php?p&#61;news/show&l&#61;en&news_id&#61;37 2 Dec. 2011]).}}<br />
# Put {{ic|/opt/e17/bin}} in your {{ic|PATH}} by editing {{ic|/etc/profile}}. For example, you can add this line at the end of the file: {{bc|1=PATH="$PATH:/opt/e17/bin"}}<br />
# If, after completing the install, xinitrc complains that it cannot find enlightenment upon starting, you may need to add these lines to the end of /etc/profile as well:{{bc|1=PYTHONPATH=":$PYTHONPATH"}}{{bc|1=LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/e17/lib"}}<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it is not a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{ic|update_e17.sh}} is a zenity script which is made to accompany {{ic|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
=== startx ===<br />
If you use {{ic|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
=== Elsa ===<br />
Nowadays E17 has a new display manager called Elsa, you can download it from AUR {{AUR|elsa-svn-arch}}.<br />
Elsa is quite sophisticated and its configuration is controlled by {{ic|/etc/elsa.conf}}.<br />
To start Elsa add the following line to your {{ic|/etc/inittab}}<br />
x:5:respawn:/usr/sbin/elsa<br />
and change your default runlevel to 5.<br />
<br />
=== Other ===<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{ic|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{ic|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
=== connman ===<br />
<br />
E17's preferred network manager is [[Connman]]. It is available from the [community] repository as the {{Pkg|connman}}) package. To interface with E17's default Network module, you must also download EConmman (available in AUR as {{AUR|econnman-svn}}) and it's associated dependencies.<br />
<br />
Finally, configure systemd to start the Connman daemon at startup:<br />
<br />
systemctl enable connman.service<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you have installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
=== NetworkManager ===<br />
<br />
You can also use {{Pkg|networkmanager}} to manage your network connections.<br />
<br />
pacman -S networkmanager<br />
<br />
Follow the instructions on [[NetworkManager]] to do the configuration. You may also need {{Pkg|network-manager-applet}} to help with your settings.<br />
<br />
pacman -S network-manager-applet<br />
<br />
You may want to add it to the start up programs so every time your E17 starts it appears on systray.<br />
<br />
Settings -> Settings Panel -> Apps -> Startup Applications -> System -> Network<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog. During 2010 there was a change in how themes work, so for older themes you may need to do the following:<br />
edje_convert <theme>.edj<br />
<br />
{{Note|The edje_convert binary has been "dropped" by upstream developers... see: [http://trac.enlightenment.org/e/changeset/56156 trac.enlightenment.org]}}<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{ic|etk_prefs}}.<br />
<br />
== Modules and Gadgets ==<br />
;Module:Name used in enlightenment to refer to the "backing" code for a gadget. <br />
;Gadget:Front-end or user interface that should help the end users of [[E17]] do something.<br />
<br />
Many Modules provide Gadgets that can be added to your desktop or on a shelf. Some Modules (such as CPUFreq) only provide a single Gadget while others (such as Composite) provide additional features without any gadgets. Note that certain gadgets such as Systray can only be added to a shelf while others such as Moon can only be loaded on the desktop. <br />
<br />
=== Compositing ===<br />
E17 offers two modules for compositing, '''''Composite''''' and '''''Ecomorph''''', depending on your hardware and preference.<br />
<br />
==== Composite ====<br />
The ''Composite'' module is the standard compositing manager provided in enlightenment. It provides some minimal compositing effects such as transparency, fade and shadow. Composite provides the more stable module and is supported on a lot hardware through either OpenGL or compositing software rendering.<br />
<br />
==== Ecomorph ====<br />
The ''Ecomorph'' module is a full-featured compositing manager which was ported from [[Compiz]] for E17. It can be downloaded from AUR {{AUR|ecomorph-git}}. Some experience instability with Ecomorph while others use it without a problem. Ecomorph requires 3D acceleration, while Composite does not. <br />
<br />
=== Places ===<br />
From the current source code [http://trac.enlightenment.org/e/browser/trunk/E-MODULES-EXTRA/places/README README] for Places:<br />
;Places module:''This module manage the volumes device attached to the system.''<br />
<br />
In other words, Places is a gadget that will help you browse files on various devices you might plug into your computer, like phones, cameras, or other various storage devices you might plug into the usb port.<br />
<br />
=== Scale Windows ===<br />
The ''Scale Windows'' module, which requires compositing to be enabled, shrinks all open windows and brings them all into view. It can be added to the desktop as a gadget or set as a key binding. <br />
<br />
Some people like to change the standard window selection key binding {{ic|ALT + Tab}} to use Scale Windows to select windows. To change this setting, you navigate to {{ic|Menu > Settings > Settings Panel > Input > Keys}}. From here, you can set any key binding you would like. <br />
<br />
To replace the window selection key binding functionality with Scale Windows, scroll through the left panel until you find the "ALT" section and then find and select {{ic|ALT + Tab}}. Then, scroll through the right panel looking for the "Scale Windows" section and choose either {{ic|Select Next}} or {{ic|Select Next (All)}} depending on whether you would like to see windows from only the current desktop or from all desktops and click "Apply" to save the binding.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{ic|~/.e}} and remove it (e.g. {{ic|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream. http://trac.enlightenment.org/e/report<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Pkg|libxcursor}} package.<br />
<br />
=== Screen unlocking does not work ===<br />
<br />
If screenlock does not accept your password add the following to {{ic|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-dejavu ttf-bitstream-vera<br />
<br />
=== udisks vs. HAL ===<br />
Modules may need to use underlying libraries or daemons to interact with various devices connected to your computer. Currently there are at least two choices for these underlying libraries or daemons to interact with connected devices. The two that will be considered here are udisks and HAL. At the time of this entry the [[HAL]] page says:<br />
:''HAL (Hardware Abstraction Layer) is a daemon that allows desktop applications to readily access hardware information, to locate and use such hardware regardless of bus or device type. In this way a desktop GUI can present all resources to its user in a seamless and uniform manner. HAL has become deprecated in favor of udev, udisks, upower, etc. and is no longer developed. Currently, a small number of programs still rely on and use HAL, though development is heading toward utilizing udev as a replacement.''<br />
<br />
So, apparently [[E17]] now tries to use udisks instead of [[HAL]]. But some of the modules and gadgets, such as Places, have not been updated to use udisks yet.<br />
<br />
=== Places does not work ===<br />
If the Places gadget look something like a blank grey area with no Gadget in it and not detecting new device, it may because the Places is still trying to use [[HAL]]. Here is the procedure to get the HAL daemon running:<br />
<br />
Install {{AUR|hal-info}} and {{AUR|hal-git}} from the [[Arch User Repository]]. Note that {{AUR|hal-info}} is a dependency for {{AUR|hal-git}}, so you may want to install it with [[pacman]]'s {{ic|--asdeps}} flag.<br />
<br />
Start the hal daemon:<br />
<br />
{{bc|# systemctl start hal}}<br />
<br />
Now you must remove the "Places" gadget from my shelf, and unload the Places module from menu {{ic|settings -> modules -> Places -> unload}}<br />
<br />
Restart enlightenment, reload the Places module and add the Places gadget to my shelf. Then Places will work normally.<br />
<br />
=== Failure in mounting internal partitions ===<br />
Check if user is in storge group:<br />
{{bc|# groups <user>}}<br />
<br />
If user is not in storage group:<br />
{{bc|# groupadd storage <br />
# gpasswd -a <user> storage}}<br />
<br />
Then create this file as root:<br />
{{bc|# nano /etc/polkit-1/localauthority/50-local.d/10-storage-group-mount-override.pkla}}<br />
<br />
And write into the file:<br />
<br />
[storage group mount override]<br />
Identity=unix-group:storage<br />
Action=org.freedesktop.udisks2.filesystem-mount-system<br />
ResultAny=yes<br />
ResultInactive=yes<br />
ResultActive=yes<br />
<br />
For more information, see:<br />
http://bbs.archbang.org/viewtopic.php?id=2720<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]<br />
* [http://www.bodhilinux.com/e17guide/e17guideEN/ Bodhi Guide to Enlightenment]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Desktop_environment&diff=236733
Desktop environment
2012-11-25T07:24:09Z
<p>Foolishgrunt: /* Comparison of desktop environments */ ETerm > Terminology</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[es:Desktop Environment]]<br />
[[it:Desktop Environment]]<br />
[[sv:Skrivbordsmiljö]]<br />
[[uk:Desktop Environment]]<br />
[[zh-CN:Desktop Environment]]<br />
{{Article summary start}}<br />
{{Article summary text|In graphical computing, a desktop environment (DE) commonly refers to a style of graphical user interface (GUI) derived from the desktop metaphor that is seen on most modern personal computers. This article provides a general overview of popular desktop environments.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Resources}}<br />
{{Article summary wiki|Wikipedia:Desktop environment}}<br />
{{Article summary wiki|Wikipedia:X Window System}}<br />
{{Article summary end}}<br />
<br />
'''Desktop environments''' provide a ''complete'' graphical user interface (GUI) for a system by bundling together a variety of X clients written using a common widget toolkit and set of libraries. <br />
<br />
== X Window System == <!-- please keep this section synchronized with [[Window Manager#X Window System]] --><br />
The [[Wikipedia:X Window System|X Window System]] provides the foundation for a graphical user interface. Prior to installing a desktop environment, a functional X server installation is required. See [[Xorg]] for detailed information.<br />
<br />
:''X provides the basic framework, or primitives, for building such GUI environments: drawing and moving windows on the screen and interacting with a mouse and keyboard. X does not mandate the user interface — individual client programs known as window managers handle this. As such, the visual styling of X-based environments varies greatly; different programs may present radically different interfaces. X is built as an additional (application) abstraction layer on top of the operating system kernel.''<br />
<br />
The user is free to configure their GUI environment in any number of ways. Desktop environments simply provide a complete and convenient means of accomplishing this task.<br />
<br />
== Desktop environments ==<br />
A desktop environment bundles together a variety of X clients to provide common graphical user interface elements such as icons, windows, toolbars, wallpapers, and desktop widgets. Additionally, most desktop environments include a set of integrated applications and utilities.<br />
<br />
Note that users are free to mix-and-match applications from multiple desktop environments. For example, a KDE user may install and run GNOME applications such as the Epiphany web browser, should he/she prefer it over KDE's Konqueror web browser. One drawback of this approach is that many applications provided by desktop environment projects rely heavily upon their DE's respective underlying libraries. As a result, installing applications from a range of desktop environments will require installation of a larger number of dependencies. Users seeking to conserve disk space and avoid [[Wikipedia:software bloat|software bloat]] often avoid such mixed environments, or look into lightweight alternatives.<br />
<br />
Furthermore, DE-provided applications tend to integrate better with their native environments. Superficially, mixing environments with different widget toolkits will result in visual discrepancies (that is, interfaces will use different icons and widget styles). In terms of user experience, mixed environments may not behave similarly (e.g. single-clicking versus double-clicking icons; drag-and-drop functionality) potentially causing confusion or unexpected behavior.<br />
<br />
=== List of desktop environments ===<br />
* {{App|[[GNOME]]|The GNOME project provides two things: The GNOME desktop environment, an attractive and intuitive desktop for users, and the GNOME development platform, an extensive framework for building applications that integrate into the rest of the desktop. GNOME is free, usable, accessible, international, developer-friendly, organized, supported, and a community.|http://www.gnome.org/about/|{{Pkg|gnome}}}}<br />
<br />
* {{App|[[Mate]]|Mate is a fork of Gnome 2. Mate provides an intuitive and attractive desktop to Linux users using traditional metaphors.|http://www.mate-desktop.org/|{{Pkg|mate}}}}<br />
<br />
* {{App|[[Cinnamon]]|Cinnamon is a fork of Gnome 3. Cinnamon strives to provide a traditional user experienc, similar to Gnome 2.|http://cinnamon.linuxmint.com/|{{AUR|cinnamon}} [unsupported]}}<br />
<br />
* {{App|[[KDE]]|KDE software consists of a large number of individual applications and a desktop workspace as a shell to run these applications. You can run KDE applications just fine on any desktop environment as they are built to integrate well with your system's components. By also using the KDE workspace, you get even better integration of your applications with the working environment while lowering system resource demands.|http://www.kde.org/|{{Pkg|kde}}}}<br />
<br />
* {{App|[[Xfce]]|Xfce embodies the traditional UNIX philosophy of modularity and re-usability. It consists of a number of components that provide the full functionality one can expect of a modern desktop environment, while remaining relatively light. They are packaged separately and you can pick among the available packages to create the optimal personal working environment.|http://www.xfce.org/|{{Pkg|xfce}}}}<br />
<br />
* {{App|[[E17]]|The [[Enlightenment]] desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.|http://www.enlightenment.org/|{{Pkg|enlightenment17}}}}<br />
<br />
* {{App|[[LXDE]]|The "Lightweight X11 Desktop Environment" is a fast and energy-saving desktop environment. Maintained by an international community of developers, it comes with a beautiful interface, multi-language support, standard keyboard short cuts and additional features like tabbed file browsing. Fundamentally designed to be lightweight, LXDE uses less CPU and RAM than other environments. It is especially beneficial for cloud computers with low hardware specifications, such as netbooks, mobile devices (e.g. MIDs) or older computers.|http://lxde.org/|{{Pkg|lxde}}}}<br />
<br />
* {{App|[[ROX]]|ROX is a fast, user friendly desktop which makes extensive use of drag-and-drop. The interface revolves around the file manager, following the traditional UNIX view that 'everything is a file' rather than trying to hide the filesystem beneath start menus, wizards, or druids. The aim is to make a system that is well designed and clearly presented. The ROX style favors using several small programs together instead of creating all-in-one mega-applications.|http://roscidus.com/desktop/|{{Pkg|rox}}}}<br />
<br />
* {{App|[[Sugar]]|The Sugar Learning Platform is a computer environment composed of Activities designed to help children from 5 to 12 years of age learn together through rich-media expression. Sugar is the core component of a worldwide effort to provide every child with the opportunity for a quality education &mdash; it is currently used by nearly one-million children worldwide speaking 25 languages in over 40 countries. Sugar provides the means to help people lead fulfilling lives through access to a quality education that is currently missed by so many.|http://wiki.sugarlabs.org/|{{AUR|sugar}} [unsupported]}}<br />
<br />
* {{App|[[Razor-qt]]|Razor-qt is an advanced, easy-to-use, and fast desktop environment based on Qt technologies. It has been tailored for users who value simplicity, speed, and an intuitive interface. While still a new project, Razor-qt already contains all the key DE components.|http://razor-qt.org/|{{AUR|razor-qt}} [unsupported]}}<br />
<br />
=== Comparison of desktop environments ===<br />
{{Expansion}}<br />
<br />
''This section attempts to draw a comparison between popular desktop environments. Note that first-hand experience is the only effective way to truly evaluate whether a desktop environment best suits your needs.''<br />
<br />
{{Wikipedia|Comparison of X Window System desktop environments}}<br />
<br />
{| border="1" cellpadding="2"<br />
|+ Overview of desktop environments <!-- PLEASE DO NOT OVER-CLUTTER THIS TABLE! --><br />
! Desktop environment !! Widget toolkit !! Window manager !! Terminal emulator !! File manager !! Text editor !! Web browser<br />
|-<br />
| [[E17]] || [http://trac.enlightenment.org/e/wiki/Elementary Elementary] || [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment] || [http://www.enlightenment.org/p.php?p=about/terminology Terminology] || [http://trac.enlightenment.org/e/wiki/EFM EFM] / Entropy / [http://evidence.sourceforge.net/ Evidence] || N/A || [http://trac.enlightenment.org/e/wiki/Eve Eve]<br />
|-<br />
| [[GNOME]] || [[GTK+]] || [[Wikipedia:Mutter_(window_manager)|Mutter]] || [[Wikipedia:GNOME Terminal|GNOME Terminal]] || [http://live.gnome.org/Nautilus Nautilus] || [http://projects.gnome.org/gedit/ gedit] || [[Epiphany]]<br />
|-<br />
| [[KDE]] || [[Qt]] || [[Wikipedia:KWin|KWin]] || [http://konsole.kde.org/ Konsole] || [http://dolphin.kde.org/ Dolphin] || [http://kate-editor.org/ Kate / KWrite] || [http://www.konqueror.org/ Konqueror]<br />
|-<br />
| [[LXDE]] || [[GTK+]] || [[Openbox]] || [http://wiki.lxde.org/en/LXTerminal LXTerminal] || [[PCManFM]] || [http://tarot.freeshell.org/leafpad/ Leafpad] || N/A<br />
|-<br />
| [[Razor-qt]] || [[Qt]] || N/A || N/A || N/A || N/A || N/A<br />
|-<br />
| [[ROX]] || [[GTK+]] || [http://roscidus.com/desktop/OroboROX OroboROX] || [http://roxterm.sourceforge.net/ ROXTerm] || [http://roscidus.com/desktop/ROX-Filer ROX-Filer] || [http://roscidus.com/desktop/Edit Edit] || N/A<br />
|-<br />
| [[Xfce]] || [[GTK+]] || [http://docs.xfce.org/xfce/xfwm4/start Xfwm] || [http://www.xfce.org/projects/terminal Terminal] || [[Thunar]] || N/A * || [[Midori]]<br />
|}<br />
<br />
{{Note|* Mousepad used to be XFCE's recommended text editor, but it is now discontinued. Many people recommend [http://tarot.freeshell.org/leafpad/ Leafpad] or [http://projects.gnome.org/gedit/ gEdit] instead. See http://forum.xfce.org/viewtopic.php?id&#61;7066 for more information.}}<br />
<br />
====Resource use====<br />
In terms of system resources, GNOME and KDE are ''expensive'' desktop environments. Not only do complete installations consume more disk space than lightweight alternatives (E17, LXDE, Razor-qt and Xfce) but also more CPU and memory resources while in use. This is because GNOME and KDE are relatively ''full-featured'': they provide the most complete and well-integrated environments.<br />
<br />
E17, LXDE, Razor-qt and Xfce, on the other hand, are ''lightweight'' desktop environments. They are designed to work well on older or lower-power hardware and generally consume fewer system resources while in use. This is achieved by cutting back on ''extra'' features (which some would term ''bloat'').<br />
<br />
====Environment familiarity====<br />
Many users describe KDE as more ''Windows-like'' and GNOME as more ''Mac-like''. This is a very subjective comparison, since either desktop environment can be customized to emulate the Windows or Mac operating systems. See [http://www.psychocats.net/ubuntucat/is-kde-more-windows-like-than-gnome/ Is KDE 'more Windows-like' than Gnome?] and [http://www.jeffwu.net/?p=71 KDE vs Gnome] for more information. ([http://linux.oneandoneis2.org/LNW.htm Linux is Not Windows] is also an excellent resource.)<br />
<br />
== Custom environments ==<br />
Desktop environments represent the simplest means of installing a ''complete'' graphical environment. However, users are free to build and customize their graphical environment in any number of ways should none of the popular desktop environments meet their requirements. Generally, building a custom environment involves selection of a suitable [[Window Manager]] and a number of [[Lightweight Applications]] (a minimalist selection usually includes a terminal emulator, file manager, and text editor).</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Desktop_environment&diff=236730
Desktop environment
2012-11-25T07:18:37Z
<p>Foolishgrunt: /* List of desktop environments */ New E17 pkg name.</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[es:Desktop Environment]]<br />
[[it:Desktop Environment]]<br />
[[sv:Skrivbordsmiljö]]<br />
[[uk:Desktop Environment]]<br />
[[zh-CN:Desktop Environment]]<br />
{{Article summary start}}<br />
{{Article summary text|In graphical computing, a desktop environment (DE) commonly refers to a style of graphical user interface (GUI) derived from the desktop metaphor that is seen on most modern personal computers. This article provides a general overview of popular desktop environments.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Resources}}<br />
{{Article summary wiki|Wikipedia:Desktop environment}}<br />
{{Article summary wiki|Wikipedia:X Window System}}<br />
{{Article summary end}}<br />
<br />
'''Desktop environments''' provide a ''complete'' graphical user interface (GUI) for a system by bundling together a variety of X clients written using a common widget toolkit and set of libraries. <br />
<br />
== X Window System == <!-- please keep this section synchronized with [[Window Manager#X Window System]] --><br />
The [[Wikipedia:X Window System|X Window System]] provides the foundation for a graphical user interface. Prior to installing a desktop environment, a functional X server installation is required. See [[Xorg]] for detailed information.<br />
<br />
:''X provides the basic framework, or primitives, for building such GUI environments: drawing and moving windows on the screen and interacting with a mouse and keyboard. X does not mandate the user interface — individual client programs known as window managers handle this. As such, the visual styling of X-based environments varies greatly; different programs may present radically different interfaces. X is built as an additional (application) abstraction layer on top of the operating system kernel.''<br />
<br />
The user is free to configure their GUI environment in any number of ways. Desktop environments simply provide a complete and convenient means of accomplishing this task.<br />
<br />
== Desktop environments ==<br />
A desktop environment bundles together a variety of X clients to provide common graphical user interface elements such as icons, windows, toolbars, wallpapers, and desktop widgets. Additionally, most desktop environments include a set of integrated applications and utilities.<br />
<br />
Note that users are free to mix-and-match applications from multiple desktop environments. For example, a KDE user may install and run GNOME applications such as the Epiphany web browser, should he/she prefer it over KDE's Konqueror web browser. One drawback of this approach is that many applications provided by desktop environment projects rely heavily upon their DE's respective underlying libraries. As a result, installing applications from a range of desktop environments will require installation of a larger number of dependencies. Users seeking to conserve disk space and avoid [[Wikipedia:software bloat|software bloat]] often avoid such mixed environments, or look into lightweight alternatives.<br />
<br />
Furthermore, DE-provided applications tend to integrate better with their native environments. Superficially, mixing environments with different widget toolkits will result in visual discrepancies (that is, interfaces will use different icons and widget styles). In terms of user experience, mixed environments may not behave similarly (e.g. single-clicking versus double-clicking icons; drag-and-drop functionality) potentially causing confusion or unexpected behavior.<br />
<br />
=== List of desktop environments ===<br />
* {{App|[[GNOME]]|The GNOME project provides two things: The GNOME desktop environment, an attractive and intuitive desktop for users, and the GNOME development platform, an extensive framework for building applications that integrate into the rest of the desktop. GNOME is free, usable, accessible, international, developer-friendly, organized, supported, and a community.|http://www.gnome.org/about/|{{Pkg|gnome}}}}<br />
<br />
* {{App|[[Mate]]|Mate is a fork of Gnome 2. Mate provides an intuitive and attractive desktop to Linux users using traditional metaphors.|http://www.mate-desktop.org/|{{Pkg|mate}}}}<br />
<br />
* {{App|[[Cinnamon]]|Cinnamon is a fork of Gnome 3. Cinnamon strives to provide a traditional user experienc, similar to Gnome 2.|http://cinnamon.linuxmint.com/|{{AUR|cinnamon}} [unsupported]}}<br />
<br />
* {{App|[[KDE]]|KDE software consists of a large number of individual applications and a desktop workspace as a shell to run these applications. You can run KDE applications just fine on any desktop environment as they are built to integrate well with your system's components. By also using the KDE workspace, you get even better integration of your applications with the working environment while lowering system resource demands.|http://www.kde.org/|{{Pkg|kde}}}}<br />
<br />
* {{App|[[Xfce]]|Xfce embodies the traditional UNIX philosophy of modularity and re-usability. It consists of a number of components that provide the full functionality one can expect of a modern desktop environment, while remaining relatively light. They are packaged separately and you can pick among the available packages to create the optimal personal working environment.|http://www.xfce.org/|{{Pkg|xfce}}}}<br />
<br />
* {{App|[[E17]]|The [[Enlightenment]] desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.|http://www.enlightenment.org/|{{Pkg|enlightenment17}}}}<br />
<br />
* {{App|[[LXDE]]|The "Lightweight X11 Desktop Environment" is a fast and energy-saving desktop environment. Maintained by an international community of developers, it comes with a beautiful interface, multi-language support, standard keyboard short cuts and additional features like tabbed file browsing. Fundamentally designed to be lightweight, LXDE uses less CPU and RAM than other environments. It is especially beneficial for cloud computers with low hardware specifications, such as netbooks, mobile devices (e.g. MIDs) or older computers.|http://lxde.org/|{{Pkg|lxde}}}}<br />
<br />
* {{App|[[ROX]]|ROX is a fast, user friendly desktop which makes extensive use of drag-and-drop. The interface revolves around the file manager, following the traditional UNIX view that 'everything is a file' rather than trying to hide the filesystem beneath start menus, wizards, or druids. The aim is to make a system that is well designed and clearly presented. The ROX style favors using several small programs together instead of creating all-in-one mega-applications.|http://roscidus.com/desktop/|{{Pkg|rox}}}}<br />
<br />
* {{App|[[Sugar]]|The Sugar Learning Platform is a computer environment composed of Activities designed to help children from 5 to 12 years of age learn together through rich-media expression. Sugar is the core component of a worldwide effort to provide every child with the opportunity for a quality education &mdash; it is currently used by nearly one-million children worldwide speaking 25 languages in over 40 countries. Sugar provides the means to help people lead fulfilling lives through access to a quality education that is currently missed by so many.|http://wiki.sugarlabs.org/|{{AUR|sugar}} [unsupported]}}<br />
<br />
* {{App|[[Razor-qt]]|Razor-qt is an advanced, easy-to-use, and fast desktop environment based on Qt technologies. It has been tailored for users who value simplicity, speed, and an intuitive interface. While still a new project, Razor-qt already contains all the key DE components.|http://razor-qt.org/|{{AUR|razor-qt}} [unsupported]}}<br />
<br />
=== Comparison of desktop environments ===<br />
{{Expansion}}<br />
<br />
''This section attempts to draw a comparison between popular desktop environments. Note that first-hand experience is the only effective way to truly evaluate whether a desktop environment best suits your needs.''<br />
<br />
{{Wikipedia|Comparison of X Window System desktop environments}}<br />
<br />
{| border="1" cellpadding="2"<br />
|+ Overview of desktop environments <!-- PLEASE DO NOT OVER-CLUTTER THIS TABLE! --><br />
! Desktop environment !! Widget toolkit !! Window manager !! Terminal emulator !! File manager !! Text editor !! Web browser<br />
|-<br />
| [[E17]] || [http://trac.enlightenment.org/e/wiki/Elementary Elementary] || [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment] || [http://www.eterm.org/ Eterm] || [http://trac.enlightenment.org/e/wiki/EFM EFM] / Entropy / [http://evidence.sourceforge.net/ Evidence] || N/A || [http://trac.enlightenment.org/e/wiki/Eve Eve]<br />
|-<br />
| [[GNOME]] || [[GTK+]] || [[Wikipedia:Mutter_(window_manager)|Mutter]] || [[Wikipedia:GNOME Terminal|GNOME Terminal]] || [http://live.gnome.org/Nautilus Nautilus] || [http://projects.gnome.org/gedit/ gedit] || [[Epiphany]]<br />
|-<br />
| [[KDE]] || [[Qt]] || [[Wikipedia:KWin|KWin]] || [http://konsole.kde.org/ Konsole] || [http://dolphin.kde.org/ Dolphin] || [http://kate-editor.org/ Kate / KWrite] || [http://www.konqueror.org/ Konqueror]<br />
|-<br />
| [[LXDE]] || [[GTK+]] || [[Openbox]] || [http://wiki.lxde.org/en/LXTerminal LXTerminal] || [[PCManFM]] || [http://tarot.freeshell.org/leafpad/ Leafpad] || N/A<br />
|-<br />
| [[Razor-qt]] || [[Qt]] || N/A || N/A || N/A || N/A || N/A<br />
|-<br />
| [[ROX]] || [[GTK+]] || [http://roscidus.com/desktop/OroboROX OroboROX] || [http://roxterm.sourceforge.net/ ROXTerm] || [http://roscidus.com/desktop/ROX-Filer ROX-Filer] || [http://roscidus.com/desktop/Edit Edit] || N/A<br />
|-<br />
| [[Xfce]] || [[GTK+]] || [http://docs.xfce.org/xfce/xfwm4/start Xfwm] || [http://www.xfce.org/projects/terminal Terminal] || [[Thunar]] || N/A * || [[Midori]]<br />
|}<br />
<br />
{{Note|* Mousepad used to be XFCE's recommended text editor, but it is now discontinued. Many people recommend [http://tarot.freeshell.org/leafpad/ Leafpad] or [http://projects.gnome.org/gedit/ gEdit] instead. See http://forum.xfce.org/viewtopic.php?id&#61;7066 for more information.}}<br />
<br />
====Resource use====<br />
In terms of system resources, GNOME and KDE are ''expensive'' desktop environments. Not only do complete installations consume more disk space than lightweight alternatives (E17, LXDE, Razor-qt and Xfce) but also more CPU and memory resources while in use. This is because GNOME and KDE are relatively ''full-featured'': they provide the most complete and well-integrated environments.<br />
<br />
E17, LXDE, Razor-qt and Xfce, on the other hand, are ''lightweight'' desktop environments. They are designed to work well on older or lower-power hardware and generally consume fewer system resources while in use. This is achieved by cutting back on ''extra'' features (which some would term ''bloat'').<br />
<br />
====Environment familiarity====<br />
Many users describe KDE as more ''Windows-like'' and GNOME as more ''Mac-like''. This is a very subjective comparison, since either desktop environment can be customized to emulate the Windows or Mac operating systems. See [http://www.psychocats.net/ubuntucat/is-kde-more-windows-like-than-gnome/ Is KDE 'more Windows-like' than Gnome?] and [http://www.jeffwu.net/?p=71 KDE vs Gnome] for more information. ([http://linux.oneandoneis2.org/LNW.htm Linux is Not Windows] is also an excellent resource.)<br />
<br />
== Custom environments ==<br />
Desktop environments represent the simplest means of installing a ''complete'' graphical environment. However, users are free to build and customize their graphical environment in any number of ways should none of the popular desktop environments meet their requirements. Generally, building a custom environment involves selection of a suitable [[Window Manager]] and a number of [[Lightweight Applications]] (a minimalist selection usually includes a terminal emulator, file manager, and text editor).</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Uniform_look_for_Qt_and_GTK_applications&diff=210879
Uniform look for Qt and GTK applications
2012-06-22T00:27:56Z
<p>Foolishgrunt: /* Making Qt apps use GTK+ themes */ Removed 'libgnomeui' suggestion, as it doesn't seem to be necessary. Made "Having trouble" section into subection.</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[Category:Eye candy]]<br />
[[es:Uniform Look for Qt and GTK Applications]]<br />
[[it:Uniform Look for Qt and GTK Applications]]<br />
[[ru:Uniform Look for Qt and GTK Applications]]<br />
[[uk:Uniform Look for Qt and GTK Applications]]<br />
[[zh-CN:Uniform Look for Qt and GTK Applications]]<br />
{{Article summary start}}<br />
{{Article summary text|This articles details theme configuration of GTK+ at QT applications to ensure a uniform style. This article will cover configuration, theme engines, tricks and troubleshooting.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|GTK+}}<br />
{{Article summary wiki|Qt}}<br />
{{Article summary end}}<br />
<br />
[[Qt]] and [[GTK+]] based programs both use a different widget toolkit to render the graphical user interface. Each come with different themes, styles and icon sets by default, among other things, so the "look and feel" differ significantly. This article will help you make your Qt and GTK+ applications look similar for a more streamlined and "integrated" desktop experience.<br />
<br />
*'''Theme''' - Collection of a style, an icon theme and a colour theme.<br />
*'''Style''' - Graphical layout; look.<br />
*'''Icon Theme''' - Set of global icons.<br />
*'''Colour Theme''' - Set of global colours that are used in conjunction with the style.<br />
<br />
You can choose various approaches:<br />
<br />
* Modify [[Uniform Look for QT and GTK Applications#Styles for both Qt and GTK+|GTK+ and Qt styles]] separately with the tools listed below for each toolkit and aim for choosing similarly looking themes (style, colours, icons, cursors, fonts).<br />
* Use a special [[Uniform Look for QT and GTK Applications#Theme Engines|theme engine]], which intermediates the modification of the other graphical toolkit to match your main toolkit:<br />
** if you work in KDE 4 desktop environment then there is available a GTK-Qt engine, which updates GTK+ configuration files automatically so that GTK+ appearance is similar to the Qt one;<br />
** if you work in other desktop environments, you can choose QGtkStyle engine (built in Qt), which forces Qt apps to use your GTK+ 2.x theme.<br />
<br />
Should you use also GTK+ 3.x toolkit, follow the [[GTK+#GTK+ 3.x|GTK+ 3.x]] wiki article to find out how to make it look similar to GTK+ 2.x themes.<br />
<br />
== Styles for both Qt and GTK+ ==<br />
<br />
There are widget style sets available for the purpose of integration, where builds are written and provided for both Qt and GTK+, all major versions included. With these, you can have one look for all applications regardless of the toolkit they had been written with.<br />
<br />
=== KDE4 Oxygen ===<br />
<br />
[http://www.oxygen-icons.org/ Oxygen] is the QT4 style that installs with KDE4.<br />
<br />
==== oxygen-gtk ====<br />
A couple of GTK+ ports are available in the {{Pkg|oxygen-gtk}} packages. Their primary goal is to ensure visual consistency between GTK2/GTK3 and qt-based applications running under kde. Secondary objectives are to also have stand-alone, nice looking gtk themes that behave well on other Desktop Environments. Unlike other attempts made to port the kde oxygen theme to gtk, these attempts do not depend on Qt (via some Qt to Gtk conversion engine), nor do they render widget appearances via hard coded pixmaps, which otherwise break everytime some setting is changed in kde. <br />
<br />
pacman -S oxygen-gtk2 oxygen-gtk3<br />
<br />
=====Automatic procedure=====<br />
To change the GTK theme a few applications are available:<br />
pacman -S gtk-kde4<br />
pacman -S gtk-chtheme<br />
pacman -S gtk-theme-switch2<br />
pacman -S lxappearance<br />
<br />
Then change the theme of your choice in the respective application:<br />
gtk-kde4 ("System Settings > Lost and Found > GTK style")<br />
gtk-chtheme<br />
gtk-theme-switch2<br />
lxappearance<br />
<br />
You can also install {{AUR|kde-gtk-config}} from [[AUR]]. After install it can be found in '''System Settings > Application Appearance > GTK Configuration'''. It allows you to configure the look and certain settings for both GTK2 and GTK3 applications. Integrating the usual addon installer of KDE you can also download and install other GTK themes.<br />
<br />
=====Manual procedure=====<br />
To manually change the GTK theme to {{Pkg|oxygen-gtk}} , you need to create the file {{ic|~/.kde4/share/config/gtkrc-2.0}} with the following content:<br />
<br />
include "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc"<br />
include "~/.themes/oxygen-gtk/gtk-2.0/gtkrc"<br />
style "user"<br />
{ <br />
fg[NORMAL] = "#1b1918"<br />
bg[NORMAL] = "#d5d1cf"<br />
text[NORMAL] = "#181615"<br />
base[NORMAL] = "#ffffff"<br />
fg[ACTIVE] = "#1b1918"<br />
bg[ACTIVE] = "#d5d1cf"<br />
text[ACTIVE] = "#181615"<br />
base[ACTIVE] = "#ffffff"<br />
fg[PRELIGHT] = "#1b1918"<br />
bg[PRELIGHT] = "#d5d1cf"<br />
text[PRELIGHT] = "#ffffff"<br />
base[PRELIGHT] = "#43ace8"<br />
fg[SELECTED] = "#1b1918"<br />
bg[SELECTED] = "#d5d1cf"<br />
text[SELECTED] = "#ffffff"<br />
base[SELECTED] = "#43ace8"<br />
fg[INSENSITIVE] = "#8d8a88"<br />
bg[INSENSITIVE] = "#ccc7c5"<br />
text[INSENSITIVE] = "#a6a5a5"<br />
base[INSENSITIVE] = "#f4f4f4"<br />
GtkTreeView::odd_row_color="#ffffff"<br />
GtkTreeView::even_row_color="#f8f7f6"<br />
}<br />
widget_class "*" style "user"<br />
style "tooltips"<br />
{ <br />
bg[NORMAL] = "#bedfff"<br />
fg[NORMAL] = "#252321"<br />
}<br />
widget "gtk-tooltips" style "tooltips"<br />
#gtk-theme-name="qt4"<br />
gtk-font-name="Sans Serif 9"<br />
gtk-icon-theme-name="gk4ico"<br />
gtk-icon-sizes = "panel-menu=16,16:panel=16,16:gtk-button=22,22:gtk-large-toolbar=22,22"<br />
<br />
Then you need to create the symbolic link {{ic|~/.kde4/share/config/gtkrc}}:<br />
ln -s ~/.kde4/share/config/gtkrc-2.0 ~/.kde4/share/config/gtkrc<br />
<br />
==== Oxygen Icons ====<br />
If you are using Oxygen icons and want a consistent look in GTK open/save dialogs, you can install an [https://aur.archlinux.org/packages.php?O=0&K=oxygenrefit2-icon-theme&do_Search=Go oxygenrefit2] icon theme from AUR and set it as your GTK icon theme. Add the theme to the {{ic|~/.gtkrc-2.0}} file or you can use lxappearance and set it.<br />
gtk-icon-theme-name="OxygenRefit2"<br />
There are also a couple GTK themes built on the [https://aur.archlinux.org/packages.php?ID=24329 gtk-kde42-oxygen-theme Oxygen style] that can also do this.<br />
<br />
=== QtCurve ===<br />
<br />
Available for ''qt4'' (kde4), ''qt3'' (kde3), and ''gtk2'' (gnome) in the '''[extra]''' repository, this highly-configurable style is the most popular all-rounder. It has many controls for various options, ranging from the appearance of buttons to the shape of sliders. You can install all of them using pacman.<br />
# pacman -S qtcurve-gtk2 qtcurve-kde3 qtcurve-kde4<br />
<br />
To manually change the GTK theme to '''QtCurve''', you need to create the file {{ic|~/.gtkrc-2.0-kde4}} with the following content:<br />
include "/usr/share/themes/QtCurve/gtk-2.0/gtkrc"<br />
include "/etc/gtk-2.0/gtkrc"<br />
<br />
style "user-font"<br />
{<br />
font_name="Sans Serif"<br />
}<br />
widget_class "*" style "user-font" <br />
gtk-theme-name="QtCurve"<br />
Then you need to create the symbolic link {{ic|~/.gtkrc-2.0}}:<br />
ln -s .gtkrc-2.0-kde4 .gtkrc-2.0<br />
If you want also specify a font, you can add (and adapt) the following line to the file:<br />
gtk-font-name="Sans Serif 9"<br />
<br />
=== Others ===<br />
<br />
Similar style sets are those that look like each other - written and provided for both Qt and GTK+ - but are not necessarily from the same developers. You may have to do some minor tweaking to make them look the same. Below is a list:<br />
<br />
*klearlooks (qt3); clearlooks (gtk2)<br />
<br />
== How do I set styles for each toolkit? ==<br />
<br />
You can use the following methods to change the theme used in each environment.<br />
<br />
=== QT3 styles ===<br />
* Using ''KDE3 Control Center'' (kcontrol):<br />
:--> Appearance & Themes --> Style --> Widget Style<br />
* kde-config --style [name of style]<br />
* ''Qt Configuration'' (qt3config | /opt/qt/bin/qtconfig)<br />
:--> Appearance --> Select GUI Style<br />
<br />
=== QT4 styles ===<br />
* Using ''KDE4 System Settings'' (/usr/bin/systemsettings)<br />
:--> Common Appearance and Behavior --> Application Appearance --> Style --> Widget Style''<br />
* ''Qt Configuration'' (/usr/bin/qtconfig)<br />
:--> Appearance --> Select GUI Style<br />
<br />
Note that while Qt Configuration allows you to choose the theme, font, etc. for the Qt apps, you can modify more settings with KDE 4 System Settings - e.g. font antialiasing and hinting.<br />
<br />
=== GTK2 styles ===<br />
* {{Pkg|gtk-kde4}} (allows you to change style and font of GTK applications in KDE4)<br />
* {{Pkg|lxappearance}} (a DE independent configuration tool from the LXDE project, which does not require any other parts of LXDE)<br />
* {{Pkg|gtk-chtheme}} (considered a better alternative to switch2)<br />
* {{Pkg|gtk2_prefs}}<br />
* {{Pkg|gtk-theme-switch2}}<br />
* [[GTK%2B#GTK.2B_2.x|Manual configuration]]<br />
<br />
=== GTK1 styles ===<br />
* [https://aur.archlinux.org/packages.php?K=gtk-theme-switch gtk-theme-switch package (AUR)]<br />
<br />
== Theme Engines ==<br />
<br />
A Theme Engine can be thought of as a thin layer API which translates themes (excluding icons) between one or more toolkits. These engines add some extra code in the process and it is arguable that this kind of a solution is not as elegant and optimal as using native styles.<br />
<br />
=== GTK-QT-Engine ===<br />
<br />
This one is for use by GTK+ applications running in KDE, which basically means this does not work in other desktop environments. It applies all Qt settings (styles, fonts, not icons though) to the GTK+ applications and uses the style plug-ins directly. Please note that there are rendering issues with some Qt styles.<br />
<br />
# pacman -S gtk-qt-engine<br />
<br />
You can access it from:<br />
:''Control Center (kcontrol) --> Appearance & Themes --> GTK Styles and Fonts''<br />
<br />
If you want to remove it entirely and every trace of it, you should delete the following files:<br />
<br />
*~/.gtkrc2.0-kde<br />
*~/.kde4/env/gtk-qt-engine.rc.sh<br />
*~/gtk-qt-engine.rc<br />
<br />
==== Make it work with OpenOffice ====<br />
Set (as root):<br />
export SAL_GTK_USE_PIXMAPPAINT=1<br />
into /etc/profile. In KDE4 systemsettings, make sure "use my KDE style in GTK applications" is selected in Appearance > GTK styles and fonts.<br />
<br />
=== Making Qt apps use GTK+ themes ===<br />
<br />
==== QGtkStyle ====<br />
<br />
This is a Qt style which intends to make applications blend perfectly into the GNOME desktop environment by using GTK to render all components. To use this style you must have at least GTK+ 2.0 and Qt 4.3, although Qt 4.4 or higher is preferred. To enable this style, use Qt Configuration or KDE 4 System Settings (see above) and choose "GTK+" style.<br />
<br />
{{Note|Beginning with version 4.5 this style is included in Qt and does not require a separate package anymore.}}<br />
<br />
=====Having trouble making your Qt applications use QGtkStyle?=====<br />
<br />
Qt will not apply QGtkStyle correctly if GTK is using the [[Uniform Look for QT and GTK Applications#GTK-QT-Engine|GTK-QT-Engine]]. Qt determines whether the [[Uniform Look for QT and GTK Applications#GTK-QT-Engine|GTK-QT-Engine]] is in use by reading the GTK configuration files listed in the environmental variable '''GTK2_RC_FILES'''. If the environmental variable is not set properly, Qt assumes you are using the [[Uniform Look for QT and GTK Applications#GTK-QT-Engine|GTK-QT-Engine]], sets QGtkStyle to use the style GTK style ''Clearlooks'', and outputs an error message:<br />
<br />
QGtkStyle cannot be used together with the GTK_Qt engine.<br />
<br />
Another error you may get after launching qtconfig from a shell and selecting the Gtk+ style is:<br />
<br />
QGtkStyle was unable to detect the current GTK+ theme.<br />
<br />
Users of [[Openbox]] and other non-GNOME environments may encounter this problem. Here is a solution:<br />
<br />
*Tell Qt where to look for your GTK configuration file by adding the following to your {{ic|.xinitrc}} file:<br />
**Add this line before invoking the window manager.<br />
**To add multiple paths, separate them with colons.<br />
**The $HOME part will expand to be path to your user's home directory. Using the ~ shortcut will not work.<br />
{{hc|.xinitrc|2=...<br />
export GTK2_RC_FILES="$HOME/.gtkrc-2.0"<br />
...}}<br />
<br />
*In {{ic|.gtkrc-2.0}} you must specify a GTK theme. For example:<br />
**This is usually done for you by an [[Uniform Look for QT and GTK Applications#GTK2_styles|application which sets GTK2 Styles]]<br />
**If {{ic|~/.gtkrc-2.0}} does not exist, simply create it and insert the following line.<br />
{{hc|.gtkrc-2.0|2=...<br />
gtk-theme-name="Crux"<br />
...}}<br />
However it seems in some cases those tools insert only an include directive like<br />
{{hc|.gtkrc-2.0|...<br />
include "/usr/share/themes/SomeTheme/gtk-2.0/gtkrc"<br />
...}} which apparently is not recognized by all versions of QGtkStyle. You can hotfix this problem by inserting the gtk-theme-name manually in your .gtkrc-2.0 like above, note however that Gtk2-style-change applications might overwrite that change when you use them.<br />
<br />
If these steps do not work, install gconf and run this command:<br />
<br />
gconftool-2 --set --type string /desktop/gnome/interface/gtk_theme '''your-theme-name'''<br />
<br />
To choose your GTK theme for QT apps you must run:<br />
<br />
qtconfig<br />
<br />
== Other Tricks ==<br />
=== KDE file dialogs for GTK2 apps ===<br />
KGtk is a wrapper script that LD_PRELOAD to force KDE file dialogs (open, save, etc) in GTK2 apps. If you use KDE and prefer its file dialogs over GTK's then you can install kgtk from AUR. Once installed you can run GTK2 applications with kgtk-wrapper in 2 ways (using gimp in the examples).<br />
<br />
Calling kgtk-wrapper directly and using the GTK2 binary as an arguement<br />
/usr/bin/kgtk-wrapper gimp<br />
<br />
OR<br />
<br />
Creating a symbolic link to kgtk using the name of the GTK2 binary. Then you can run /usr/bin/gimp when you want to run gimp with KDE dialogs.<br />
ln -s /usr/bin/kgtk-wrapper /usr/local/bin/gimp<br />
/usr/local/bin/gimp<br />
<br />
=== aMSN GTK or KDE dialogs ===<br />
aMSN's TK file dialogs are plain looking but no fear there is a plugin that will allow you to use GTK or KDE file dialogs to match your desktop. You can find the plugin on [http://www.amsn-project.net/plugins.php aMSN's Plugin Page]<br />
<br />
=== Using custom GTK style ===<br />
You can use custom styles for specific GTK2 applications. For this, use GTK2_RC_FILES=/path/to/theme/gtk-2.0/gtkrc appname<br />
<br />
For example:<br />
GTK2_RC_FILES=/usr/share/themes/QtCurve/gtk-2.0/gtkrc firefox<br />
It will launch firefox with QtCurve theme.<br />
<br />
=== Using gtk icon theme in Qt apps ===<br />
If you do not using Gnome run gconf-editor and edit that setting to your icon theme name<br />
/desktop/gnome/interface/icon_theme<br />
<br />
== Troubleshooting ==<br />
<br />
=== Themes not working in GTK apps ===<br />
<br />
If the style or theme engine you setup is not showing in your GTK apps then it's likely your GTK settings files are not being loaded for some reason. You can check where your system expects to find these files by doing the following..<br />
$ export | grep gtk<br />
<br />
Usually the expected files should be ~/.gtkrc for GTK1, ~/.gtkrc2.0 or ~/.gtkrc2.0-kde for GTK2<br />
<br />
Newer versions of gtk-qt-engine use ~/.gtkrc2.0-kde and set the export variable in ~/.kde/env/gtk-qt-engine.rc.sh<br />
If you recently removed gtk-qt-engine and are trying to set a GTK theme then you must remove ~/.kde/env/gtk-qt-engine.rc.sh and reboot. Doing this will ensure that GTK looks for it's settings in the standard ~/.gtkrc2.0 instead of ~/.gtkrc2.0-kde</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=184895
E17
2012-02-15T18:24:03Z
<p>Foolishgrunt: /* Installing Themes */</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
{{i18n|E17}}<br />
[[fr:E17]]<br />
<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From the [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment wiki]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It comprises both the Enlightenment [[window manager]] and Enlightenment Foundation Libraries (EFL), which provide additional desktop environment features such as a toolkit, object canvas, and abstracted objects. E17 has been under development since 2005, but in February 2011 the core EFLs saw their first stable 1.0 release. Enlightenment the window manager is still in the beta stages, but is already quite usable. Many people currently use E17 as a day-to-day desktop environment without problems.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the community repository (SVN snapshots) ===<br />
<br />
{{Note|Make sure the [[community repository]] is enabled in your {{ic|/etc/pacman.conf}}.}}<br />
<br />
To install e17:<br />
pacman -S e-svn<br />
<br />
To install additional e17 modules and applications:<br />
pacman -S e17-extra-svn<br />
<br />
You might also want to install additional [[Fonts]]. You need at least 1 True Type Font.<br />
<br />
If you need/want an e17 package which is not (yet) available in [community], see if it is available in the [[AUR]].<br />
<br />
{{Warning|As e17 is still beta software you are encouraged to keep packages of the previous version on your computer, allowing you to [[downgrade]] if needed.}}<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{ic|easy_e17.sh}} compiles E17 from source and installs it in {{ic|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{AUR|easy-e17}}.<br />
# Edit {{ic|/etc/easy_e17.conf}} if you want.<br />
# Run it as user, so it downloads to ~/e17_src and builds as user, to install E17 (the script will immediately ask for your password so it can install in the end): {{bc|# easy_e17.sh -i}}{{Warning|This will install the latest svn version. For a stable result add the <nowiki>--srcrev=</nowiki> parameter with the latest stable revision. For beta 3 use 55246 as argument. For the revision with the 1.0 release of the core libraries, use 56361.}}<br />
# Put {{ic|/opt/e17/bin}} in your {{ic|PATH}} by editing {{ic|/etc/profile}}. For example, you can add this line at the end of the file: {{bc|1=PATH="$PATH:/opt/e17/bin"}}<br />
# If, after completing the install, xinitrc complains that it cannot find enlightenment upon starting, you may need to add these lines to the end of /etc/profile as well:{{bc|1=PYTHONPATH=":$PYTHONPATH"}}{{bc|1=LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/e17/lib"}}<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it is not a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{ic|update_e17.sh}} is a zenity script which is made to accompany {{ic|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
=== startx ===<br />
If you use {{ic|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
=== Elsa ===<br />
Nowadays E17 has a new display manager called Elsa, you can download it from AUR {{AUR|elsa-svn-arch}}.<br />
Elsa is quite sophisticated and its configuration is controlled by {{ic|/etc/elsa.conf}}.<br />
To start Elsa add the following line to your {{ic|/etc/inittab}}<br />
x:5:respawn:/usr/sbin/elsa<br />
and change your default runlevel to 5.<br />
<br />
=== Other ===<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{ic|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{ic|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
=== NetworkManager ===<br />
<br />
You can use {{Pkg|networkmanager}} to manage your network connections.<br />
<br />
pacman -S networkmanager<br />
<br />
Then you need to follow the instructions on [[NetworkManager]] to do the configuration. You may also need {{Pkg|network-manager-applet}} to help with your settings.<br />
<br />
pacman -S network-manager-applet<br />
<br />
You may want to add it to the start up programs so every time your E17 starts it appears on systray.<br />
<br />
Settings -> Settings Panel -> Apps -> Startup Applications -> System -> Network<br />
<br />
=== connman ===<br />
<br />
Another available network manager is [[Connman]], you can download it from AUR {{AUR|connman}}. You do not need to follow any of the other instructions on the [[Connman|Connman wiki page]]. The current build of ConnMan already includes network policy group section (although with only one statement, not three).<br />
<br />
Next, edit your {{ic|/etc/rc.conf}}. Remove '''network''' from your DAEMONS line. Add '''connmand''' (do not forget the '''d''') ''after'' '''dbus''' and '''hal'''.<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you have installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog. During 2010 there was a change in how themes work, so for older themes you may need to do the following:<br />
edje_convert <theme>.edj<br />
<br />
{{Note|The edje_convert binary has been "dropped" by upstream developers... see: [http://trac.enlightenment.org/e/changeset/56156 trac.enlightenment.org]}}<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{ic|etk_prefs}}.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{ic|~/.e}} and remove it (e.g. {{ic|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream. http://trac.enlightenment.org/e/report<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Pkg|libxcursor}} package.<br />
<br />
=== Screen unlocking does not work ===<br />
<br />
If screenlock does not accept your password add the following to {{ic|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-dejavu ttf-bitstream-vera<br />
<br />
=== Modules and gadgets ===<br />
;Module:a name used in enlightenment to refer to the "backing" code for a gadget.<br />
;Gadget:a front-end or user interface that should help the end users of [[E17]] do something.<br />
<br />
=== udisks vs. HAL ===<br />
Often a gadget with the name "Places", for example, will use a corresponding module also named "Places". Also modules may need to use underlying libraries or daemons to interact with various devices connected to your computer. Currently there are at least two choices for these underlying libraries or daemons to interact with connected devices. The two that will be considered here are udisks and HAL. At the time of this entry the [[HAL]] page says:<br />
:''HAL (Hardware Abstraction Layer) is a daemon that allows desktop applications to readily access hardware information, to locate and use such hardware regardless of bus or device type. In this way a desktop GUI can present all resources to its user in a seamless and uniform manner. HAL has become deprecated in favor of udev, udisks, upower, etc. and is no longer developed. Currently, a small number of programs still rely on and use HAL, though development is heading toward utilizing udev as a replacement.''<br />
<br />
So, apparently [[E17]] now tries to use udisks instead of [[HAL]]. But some of the modules and gadgets, such as Places, have not been updated to use udisks yet.<br />
<br />
=== What is Places? ===<br />
From the current source code [http://trac.enlightenment.org/e/browser/trunk/E-MODULES-EXTRA/places/README README] for Places:<br />
;Places module:''This module manage the volumes device attached to the system.''<br />
<br />
In [http://www.urbandictionary.com/define.php?term=engrish other words], Places is a gadget that will help you browse files on various devices you might plug into your computer, like phones, cameras, or other various storage devices you might plug into the usb port.<br />
<br />
==== Why doesn't the Places work? ====<br />
So, if you load the "Places" module, and then add the Places gadget to, say, your bottom shelf in enlightenment, it may look something like a blank grey area with no Gadget in it because the Places module and Gadget are still trying to use [[HAL]]. Not to mention that if you plug a usb device in, the Places module will not detect it. So in order to fix this, here is a "solution":<br />
<br />
==== A workaround that gets Places working ====<br />
This procedure will attempt to help you get the HAL daemon running and the Places gadget working on your e17 desktop.<br />
<br />
Install {{AUR|hal-info}} and {{AUR|hal-git}} from the [[Arch User Repository]]. Note that {{AUR|hal-info}} is a dependency for {{AUR|hal-git}}, so you may want to install it with [[pacman]]'s {{ic|--asdeps}} flag.<br />
<br />
Start the hal daemon <br />
<br />
{{bc|# rc.d start hal}}<br />
<br />
Now you must remove the "Places" gadget from my shelf, and unload the Places module from menu {{ic|settings -> modules -> Places -> unload}}<br />
<br />
Restart enlightenment, reload the Places module and add the Places gadget to my shelf <br />
<br />
Try connecting a USB camera and watch it appear as a new device on the gadget bar in "places". If necessary, move it to the desktop, right click on the gadget {{ic|Gadget Places -> Move to -> Desktop}}.<br />
<br />
The Places gadget on the desktop should now look like an icon with a camera plugged into a usb port, and when you click on it, it opens a file manager, and shows you the files on your camera.<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=PulseAudio&diff=179235
PulseAudio
2012-01-20T00:58:07Z
<p>Foolishgrunt: /* No sound after install */</p>
<hr />
<div>[[Category:Audio/Video (English)]]<br />
{{i18n|PulseAudio}}<br />
[[fr:PulseAudio]]<br />
<br />
'''PulseAudio''' is a general purpose sound server. For a list of features, see [[Wikipedia:PulseAudio#Features]].<br />
<br />
{{Tip|If you want to play sound from multiple applications, [[ALSA]] already provides a basic software mixer named "dmix" which is enabled by default.}}<br />
<br />
==Installation==<br />
To install PulseAudio:<br />
# pacman -S pulseaudio<br />
<br />
Optionally you can install some GTK front-ends for PulseAudio:<br />
# pacman -S paprefs pavucontrol<br />
<br />
==Running==<br />
If the D-Bus system daemon is not already running, start it:<br />
<br />
# /etc/rc.d/dbus start<br />
<br />
PulseAudio can be started with:<br />
$ pulseaudio --start<br />
<br />
Or if you use X11:<br />
$ start-pulseaudio-x11<br />
<br />
If you use KDE 4:<br />
$ start-pulseaudio-x11; start-pulseaudio-kde<br />
<br />
PulseAudio can be stopped with:<br />
$ pulseaudio --kill<br />
<br />
Note that in the case of most X11 environments, PulseAudio will be automatically started together with the X11 session. See the section on Desktop Environments for details.<br />
<br />
==Backend Configuration==<br />
<br />
===ALSA===<br />
For the applications that do not support PulseAudio and support ALSA it is '''recommended''' to install the PulseAudio plugin for ALSA. The simplest way of doing this is installing the pulseaudio-alsa package:<br />
<br />
# pacman -S pulseaudio-alsa<br />
<br />
This package also contains the necessary {{ic|/etc/asound.conf}} for configuring ALSA to use PulseAudio.<br />
<br />
If you are on Arch x86_64 and want to have sound for 32 bit programs (like Wine), make sure to install lib32-libpulse and lib32-alsa-plugins as well.<br />
<br />
To prevent applications from using ALSA's OSS emulation and bypassing Pulseaudio (thereby preventing other applications from playing sound), make sure the module {{ic|snd_pcm_oss}} is not in the {{ic|MODULES}} array in [[rc.conf|{{ic|/etc/rc.conf}}]]. If it's currently loaded you can disable it by executing:<br />
# rmmod snd_pcm_oss<br />
<br />
===OSS===<br />
There are multiple ways of making OSS-only programs play to PulseAudio:<br />
<br />
====osspd====<br />
This is the simplest method.<br />
<br />
Install '''ossp''' and start oospd with:<br />
/etc/rc.d/osspd start<br />
<br />
Afterwards, add it to DAEMONS in rc.conf.<br />
<br />
====padsp wrapper====<br />
If you have a program that uses OSS you can make it work with PulseAudio by starting it with padsp:<br />
$ padsp OSSprogram<br />
A few examples:<br />
$ padsp aumix<br />
$ padsp sox foo.wav -t ossdsp /dev/dsp<br />
<br />
If you prefer you can rename the program OSSprogram-bin and replace it with a script like this: <br />
{{hc|/usr/bin/OSSProgram|<nowiki><br />
#!/bin/sh<br />
if test -x /usr/bin/padsp; then<br />
exec /usr/bin/padsp /usr/bin/OSSprogram-bin "$@"<br />
else<br />
exec /usr/bin/OSSprogram "$@"<br />
fi<br />
</nowiki>}}<br />
<br />
===GStreamer===<br />
To make [[GStreamer]] use PulseAudio, execute {{ic|gstreamer-properties}} (part of ''gnome-media'' package) and select ''PulseAudio Sound Server'' in both Audio Input and Output. Alternatively, this can be done by setting the gconf variables {{ic|/system/gstreamer/0.10/default/audiosink}} to ''pulsesink'' and {{ic|/system/gstreamer/0.10/default/audiosrc}} to ''pulsesrc'':<br />
$ gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosink pulsesink<br />
$ gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosrc pulsesrc<br />
<br />
Some applications (like Rhythmbox) ignore the ''audiosink'' property, but rely instead on ''musicaudiosink'', which can't be configured using {{ic|gstreamer-properties}} but needs to be manually set using {{ic|gconf-editor}} or the {{ic|gconftool-2}}:<br />
$ gconftool-2 -t string --set /system/gstreamer/0.10/default/musicaudiosink pulsesink<br />
<br />
===OpenAL===<br />
OpenAL Soft should use PulseAudio by default, but can be explicitly configured to do so: {{hc|/etc/openal/alsoft.conf|2=drivers=pulse,alsa}}<br />
<br />
===libao===<br />
Edit the libao configuration file:<br />
{{hc|/etc/libao.conf|2=default_driver=pulse}}<br />
<br />
===PortAudio===<br />
The current binary of PortAudio in the community repository does not support PulseAudio and non-mmap audio devices. This can be remedied by building PortAudio from ABS and applying [http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/portaudio/current/SOURCES/portaudio-19-alsa_pulse.patch?revision=313993 a patch]{{Linkrot|2011|09|05}} to the sources.<br />
There is an [http://aur.archlinux.org/packages.php?ID=51583 AUR] package for portaudio with pulse support.<br />
<br />
===ESD===<br />
PulseAudio is a drop-in replacement for the enlightened sound daemon (ESD). While PulseAudio is running, ESD clients should be able to output to it without configuration.<br />
<br />
==Desktop Environments==<br />
<br />
===General X11===<br />
Start Pulseaudio after the X session using:<br />
$ start-pulseaudio-x11<br />
<br />
This will start PulseAudio and load the X11 plugins.<br />
<br />
Note that PulseAudio may already launch automatically. This is handled by either {{ic|/etc/X11/xinit/xinitrc.d/pulseaudio}} or the files in {{ic|/etc/xdg/autostart/}}.<br />
<br />
====X11 bell====<br />
To make PulseAudio play a sample when an X11 bell event happens (e.g. to make your terminal go 'Ping!' instead of 'Beep!'), add the following to<br />
{{ic|/etc/pulse/default.pa}}:<br />
# Prevent pulseaudio --start from failing when following commands fail (eg. when X is not active)<br />
.nofail<br />
load-sample-lazy x11-bell /usr/share/sounds/freedesktop/stereo/dialog-error.oga<br />
load-module module-x11-bell sample=x11-bell<br />
.fail<br />
<br />
You can also use another sample. {{ic|dialog-error.oga}} is provided by ''sound-theme-freedesktop''.<br />
<br />
===GNOME===<br />
As of GNOME 3, GNOME fully integrates with PulseAudio and no extra configuration is needed.<br />
<br />
===KDE 3===<br />
PulseAudio is ''not'' a drop-in replacement for aRts. If you use KDE 3, it is not currently possible to use PulseAudio. However note, recent versions of puleaudio may have eliminated the prohibition:<br />
<br />
See: http://www.pulseaudio.org/wiki/PerfectSetup KDE 3 uses the artsd sound server by default. However, artsd itself can be configured to use an Esound backend. Edit kcmartsrc (either in /etc/kde or /usr/share/config for global configuration or .kde/share/config to configure only one user) like this:<br />
<br />
[Arts]<br />
Arguments=\s-F 10 -S 4096 -a esd -n -s 1 -m artsmessage -c drkonqi -l 3 -f<br />
NetworkTransparent=true<br />
SuspendTime=1<br />
<br />
===KDE 4 and Qt4===<br />
If you've installed PulseAudio, it will be used by KDE4/Qt4 applications. For more information see the [http://www.pulseaudio.org/wiki/KDE KDE pages in the PulseAudio wiki].<br />
<br />
Additionally, a minimal KDE alternative to pavucontrol, the [https://aur.archlinux.org/packages.php?ID=43848 veromix plasmoid] is available in the AUR.<br />
<br />
===XFCE4===<br />
<br />
Applications running under XFCE4 can take advantage of Pulseaudio. To manage Pulseaudio settings you can use pavucontrol.<br />
<br />
==Applications==<br />
===Audacious===<br />
[[Audacious]] natively supports PulseAudio. In order to use it, in Audacious you should set Audacious Preferences -> Audio -> Current output plugin to 'PulseAudio Output Plugin'.<br />
<br />
===Flashplugin (x86_64 only)===<br />
If you are using [[Browser Plugins#Adobe Flash Player|Adobe Flash Player]] browser plugin from the [[Multilib_Project|multilib repository]] you need to install lib32-alsa-plugins and lib32-libcanberra-pulse, otherwise you will not be able to use other audio applications while using flashplugin.<br />
{{bc|<br />
# pacman -S lib32-alsa-plugins lib32-libcanberra-pulse<br />
}}<br />
<br />
===Java/OpenJDK===<br />
Create a wrapper for the java executable using padsp as seen on the [[Java#Java_sound_with_Pulseaudio|Java sound with Pulseaudio]] page.<br />
<br />
===Music Player Daemon (MPD)===<br />
You will need to [http://mpd.wikia.com/wiki/PulseAudio configure] [[MPD]] to use PulseAudio.<br />
<br />
On a headless box, run PulseAudio as the ''mpd'' user.<br />
On a desktop, running mpd as yourself and not using the ''mpd'' user is preferred.<br />
<br />
===MPlayer===<br />
[[MPlayer]] natively supports PulseAudio output with the "{{ic|-ao pulse}}" option. It can also be configured to default to PulseAudio output, in {{ic|~/.mplayer/config}} for per-user, or {{ic|/etc/mplayer/mplayer.conf}} for system-wide:<br />
{{hc|/etc/mplayer/mplayer.conf|2=ao=pulse}}<br />
<br />
===Skype (x86_64 only)===<br />
Install lib32-libpulse from [[Multilib_Project|multilib repository]], otherwise you will get the Error "Problem with Audio Playback" when trying to initiate a call.<br />
<br />
===VLC media player===<br />
[[VLC]] supports PulseAudio through native plugin. In order to use it, in VLC you should open '''Tools -> Preferences''' (or Ctrl-P) and on '''Audio''' tab change '''Output Type''' to '''Pulseaudio audio output'''.<br />
<br />
Also consider increasing '''Caching''' to 1000-1500 ms.: (This could solve some freezings/lags) change '''Show options''' to '''All''' and go to '''Input / Codecs -> Access Modules -> File'''<br />
<br />
===volume control===<br />
Adapt the variable 'device' to your sink-device listed in {{bc|pactl list}} and you can change the volume using this script.<br />
{{bc|<nowiki><br />
#!/bin/bash<br />
device="alsa_output.pci-0000_00_14.2.analog-stereo"<br />
case "$1" in<br />
"up") # increase volume by 1000<br />
pacmd dump | awk --non-decimal-data '$1~/set-sink-volume/{if ($2~/'${device}'/) {if ($3+1000 > 65535) {system ("pactl "$1" '${device}' "65535)} else {system ("pactl "$1" '${device}' "$3+1000)}}}'<br />
;;<br />
"down") # decrease volume by 1000<br />
pacmd dump | awk --non-decimal-data '$1~/set-sink-volume/{if ($2~/'${device}'/) {if ($3-1000 < 0) {system ("pactl "$1" '${device}' "0)} else {system ("pactl "$1" '${device}' "$3-1000)}}}'<br />
;;<br />
"mute") # toggle mute<br />
pacmd dump|awk --non-decimal-data '$1~/set-sink-mute/{if ($2~/'${device}'/) {system ("pactl "$1" '${device}' "($3=="yes"?"no":"yes"))}}'<br />
;;<br />
esac<br />
</nowiki>}}<br />
<br />
*There is also a amixer like commandline mixer avaible {{AUR|pamixer-git}}.<br />
*For those wanting to map keyboard keys (such as volume up, volume down, mute, etc.), {{AUR|pulseaudio_ctl}} allows for this behavior.<br />
<br />
==Alternative configurations==<br />
===Surround sound systems===<br />
Many people have a surround card, but have speakers for just two channels, so PulseAudio cannot really default to a surround setup. To enable all the channels, edit {{ic|/etc/pulse/daemon.conf}}: uncomment the default-sample-channels line (i.e. remove the semicolon from the beginning of the line) and set the value to '''6''' if you have a ''5.1'' setup, or '''8''' if you have ''7.1'' setup etc.<br />
# Default<br />
default-sample-channels=2<br />
# For 5.1<br />
default-sample-channels=6<br />
# For 7.1<br />
default-sample-channels=8<br />
<br />
After doing the edit, you will need to restart Pulseaudio.<br />
<br />
====Splitting front/rear====<br />
<br />
You may want connect speakers to front analog output and headphones to rear output. It would be usefull to split front/rear to separate sinks. Add to default.pa:<br />
<br />
load-module module-remap-sink sink_name=speakers remix=no master=alsa_output.pci-0000_05_00.0.analog-surround-40 channels=2 master_channel_map=front-left,front-right channel_map=front-left,front-right<br />
load-module module-remap-sink sink_name=headphones remix=no master=alsa_output.pci-0000_05_00.0.analog-surround-40 channels=2 master_channel_map=rear-left,rear-right channel_map=front-left,front-right<br />
<br />
(replace alsa_output.pci-0000_05_00.0.analog-surround-40 to your sound card name that you got from 'pacmd list-sinks')<br />
<br />
After that you can switch player between speakers and headphones.<br />
<br />
====LFE remixing====<br />
By default Pulseaudio remixes the number of channels to the default-sample-channels, however it dose not do this for the LFE channel. To enable LFE remixing uncomment the line:<br />
<br />
; enable-lfe-remixing = no<br />
<br />
and replace no with yes:<br />
<br />
enable-lfe-remixing = yes<br />
<br />
then restart Pulseaudio.<br />
<br />
===Advanced ALSA Configuration===<br />
In order for ALSA to use PulseAudio it needs a special {{ic|/etc/asound.conf}} (system wide settings) (recommended) or {{ic|~/.asoundrc}} (settings on a per user basis):<br />
{{hc|/etc/asound.conf|<nowiki><br />
pcm.pulse {<br />
type pulse<br />
}<br />
ctl.pulse {<br />
type pulse<br />
}<br />
pcm.!default {<br />
type pulse<br />
}<br />
ctl.!default {<br />
type pulse<br />
}<br />
</nowiki>}}<br />
<br />
If you omit the last two groups, Pulseaudio will not be used by default. You will then need to change the ALSA device to "pulse" in the applications that you use to make it work.<br />
<br />
{{Note|You can also simply install the package 'pulseaudio-alsa'}}<br />
<br />
====ALSA Monitor source====<br />
To be able to record from a monitor source (a.k.a. "What-U-Hear", "Stereo Mix"), use {{ic|pactl list}} to find out the name of the source in Pulseaudio (e.g. {{ic|alsa_output.pci-0000_00_1b.0.analog-stereo.monitor}}). Then add lines like the following to {{ic|/etc/asound.conf}} or {{ic|~/.asoundrc}}:<br />
pcm.pulse_monitor {<br />
type pulse<br />
device alsa_output.pci-0000_00_1b.0.analog-stereo.monitor<br />
}<br />
<br />
ctl.pulse_monitor {<br />
type pulse<br />
device alsa_output.pci-0000_00_1b.0.analog-stereo.monitor<br />
}<br />
<br />
Now you can select {{ic|pulse_monitor}} as a recording source.<br />
<br />
Alternatively, you can use pavucontrol to do this : make sure you've set up the display to "All input Devices", then select "Monitor of [your soundcard]" as the recording source.<br />
<br />
===HDMI output configuration===<br />
As outlined in ftp://download.nvidia.com/XFree86/gpu-hdmi-audio-document/gpu-hdmi-audio.html#_issues_in_pulseaudio unless your hdmi port is the first<br />
output you will not be able to have any audio when using certain graphics cards with hdmi audio support. This is because of a bug in pulseaudio where it will only select the first HDMI output on a device. A work around posted further down is to first find which hdmi output is working by using the aplay utility from alsa you will need to install the alsa-utils package<br />
# pacman -S alsa-utils<br />
<br />
The original title for this section indicated the problem is specific to nVidia cards. As seen in [https://bbs.archlinux.org/viewtopic.php?id=133222 this forum thread] other cards are affected as well. The rest of the section will use an nVidia card as a case-study but the solution should carry over for people using other affected cards.<br />
<br />
====Finding HDMI output====<br />
Then find the working output by listing the available cards<br />
# aplay -l<br />
<br />
sample output:<br />
**** List of PLAYBACK Hardware Devices ****<br />
card 0: NVidia [HDA NVidia], device 0: ALC1200 Analog [ALC1200 Analog]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
card 0: NVidia [HDA NVidia], device 3: ALC1200 Digital [ALC1200 Digital]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
card 1: NVidia_1 [HDA NVidia], device 3: HDMI 0 [HDMI 0]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
card 1: NVidia_1 [HDA NVidia], device 7: HDMI 0 [HDMI 0]<br />
Subdevices: 0/1<br />
Subdevice #0: subdevice #0<br />
card 1: NVidia_1 [HDA NVidia], device 8: HDMI 0 [HDMI 0]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
card 1: NVidia_1 [HDA NVidia], device 9: HDMI 0 [HDMI 0]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
<br />
====Testing for the correct card====<br />
Now that you have a list of the detected cards you need to test for which one is outputing to the tv/monitor<br />
# aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Right.wav<br />
<br />
where 1 is the card and 3 is the device substitute in the values listed from the previous section. If there is no audio then try substituting a different device (on my card I had to use card 1 device 7)<br />
<br />
====Manually configuring pulseaudio to detect the Nvidia HDMI====<br />
Now that you know which HDMI device is working you can force pulseaudio to use it<br />
<br />
Edit /etc/pulse/default.pa<br />
add the follwing line to the file<br />
# load-module module-alsa-sink device=hw:1,7<br />
<br />
where the 1 is the card and the 7 is the deivce that you found to work in the previous section<br />
<br />
restart pulse audio<br />
# killall pulseaudio<br />
<br />
open the sound settings manager, make sure that under the hardware tab the graphics cards HDMI audio is set to "Digital Stereo (HDMI) Output" ( My graphics card audio is called "GF100 High Definition Audio Controller"<br />
<br />
Then open the output tab there should now be two HDMI outputs for the graphics card test which one works by selecting one of them and then using a program to play audio i.e use vlc to play a movie if it doesn't work the select the other.<br />
<br />
===PulseAudio over network===<br />
One of PulseAudio's magnificent features is the possibility to stream audio from clients over TCP to the server running the PulseAudio daemon, allowing sound to be streamed through your LAN.<br />
<br />
To accomplish this, one needs to enable module-native-protocol-tcp, and copy the pulse-cookie to the clients. <br />
<br />
====TCP support (networked sound)====<br />
To enable the TCP module, add this to (or uncomment, if already there) {{ic|/etc/pulse/default.pa}}:<br />
load-module module-native-protocol-tcp<br />
<br />
Note: If you are having trouble connecting, use (on server)<br />
pacmd>> list-modules<br />
(you can even load modules from here!)<br />
<br />
====TCP support with anonymous clients====<br />
<br />
If you do not want to copy the pulse-cookies from clients, you can allow anonymous clients, by giving these parameters to module-native-protocol-tcp (again in {{ic|/etc/pulse/default.pa}}):<br />
<br />
load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;192.168.0.0/24 auth-anonymous=1<br />
<br />
Remember to change your LAN ip prefix should it be different from 192.168.0.0.<br />
<br />
====Zeroconf (Avahi) publishing====<br />
For the remote Pulseaudio server to appear in the PulseAudio Device Chooser ({{ic|padevchooser}}) you need to load the appropriate zeroconf modules as well as to enable Avahi. On both machines add {{ic|avahi-daemon}} to the DAEMONS in rc.conf.<br />
On the server, add {{ic|load-module module-zeroconf-publish}} to /etc/pulse/default.pa, on the client, add {{ic|load-module module-zeroconf-discover}} to /etc/pulse/default.pa. You can then redirect any stream or complete audio output to the remote pulseaudio server by selecting the appropriate sink.<br />
<br />
====Switching the PulseAudio server used by local X clients====<br />
To switch between servers on the client from within X, the {{ic|pax11publish}} command can be used. For example, to switch from the default server to the server at hostname foo:<br />
$ pax11publish -e -S foo<br />
<br />
Or to switch back to the default:<br />
$ pax11publish -e -r<br />
<br />
Note that for the switch to become apparent, the programs using Pulse must be restarted.<br />
<br />
====When everything else seems to fail====<br />
The following is a quickfix and NOT a permanent solution<br />
<br />
On the Server: <br />
$ paprefs <br />
Go to Network Access -> Enable access to local sound devices (Also check both 'Allow discover' and 'Don't require authentication').<br />
<br />
On the Client: <br />
$ export PULSE_SERVER=server.ip && mplayer test.mp3<br />
<br />
===PulseAudio through JACK the new new way===<br />
This configuration only works with jackdbus (JACK2 compiled with D-Bus support).<br />
load-module module-jackdbus-detect<br />
As described on the [http://trac.jackaudio.org/wiki/JackDbusPackaging Jack-DBUS Packaging] page:<br />
<br />
''Server auto-launching is implemented as D-Bus call that auto-activates JACK D-Bus service, in case it is not already started, and starts the JACK server. Correct interaction with PulseAudio is done using a D-Bus based audio card "acquire/release" mechanism. When JACK server starts, it asks this D-Bus service to acquire the audio card and PulseAudio will unconditionally release it. When JACK server stops, it releases the audio card that can be grabbed again by PulseAudio.''<br />
<br />
{{ic|module-jackdbus-detect.so}} dynamically loads and unloads module-jack-sink and module-jack-source when jackdbus is started and stopped.<br />
<br />
===PulseAudio through JACK the new way===<br />
The basic idea is that killing PulseAudio is bad idea, it may crash any apps using PulseAudio, and disrupt any audio playing<br />
<br />
the flow of how this setup works:<br />
<br />
# PulseAudio releases the sound card<br />
# JACK grabs sound card and starts up<br />
# script redirects PulseAudio to JACK<br />
# manually send PulseAudio apps to JACK output (pavucontrol may come in helpful for this)<br />
# use JACK programs etc<br />
# via script, stop redirecting PulseAudio to JACK<br />
# stop JACK and release soundcard<br />
# PulseAudio grabs sound card and reroutes audio to it directly<br />
<br />
with QJackCTL setup these scripts:<br />
<br />
{{ic|pulse-jack-pre-start.sh}} set it up as the execute script on startup script<br />
#!/bin/bash<br />
pacmd suspend true<br />
<br />
{{ic|pulse-jack-post-start.sh}} set this one up as execute script after startup<br />
#!/bin/bash<br />
pactl load-module module-jack-sink channels=2<br />
pactl load-module module-jack-source channels=2<br />
pacmd set-default-sink jack_out<br />
pacmd set-default-source jack_in<br />
<br />
{{ic|pulse-jack-pre-stop.sh}} "execute script on shutdown"<br />
#!/bin/bash<br />
SINKID=$(pactl list | grep -B 1 "Name: module-jack-sink" | grep Module | sed 's/[^0-9]//g')<br />
SOURCEID=$(pactl list | grep -B 1 "Name: module-jack-source" | grep Module | sed 's/[^0-9]//g')<br />
pactl unload-module $SINKID<br />
pactl unload-module $SOURCEID<br />
sleep 5<br />
<br />
{{ic|pulse-jack-post-stop.sh}} "execute script after shutdown"<br />
#!/bin/bash<br />
pacmd suspend false<br />
<br />
===Pulseaudio through JACK the old way===<br />
The JACK-Audio-Connection-Kit is popular for audio work, and is widely supported by Linux audio applications. It fills a similar niche as Pulseaudio, but with more of an emphasis on professional audio work. In particular, audio applications such as Ardour and Audacity (recently) work well with Jack.<br />
<br />
Pulseaudio provides module-jack-source and module-jack-sink which allow Pulseaudio to be run as a sound server above the JACK daemon. This allows the usage of per-volume adjustments and the like for the apps which need it, play-back apps for movies and audio, while allowing low-latency and inter-app connectivity for sound-processing apps which connect to JACK. However, this will prevent Pulseaudio from directly writing to the sound card buffers, which will increase overall CPU usage.<br />
<br />
To just try PA on top of jack you can have PA load the necessary modules on start:<br />
pulseaudio -L module-jack-sink -L module-jack-source<br />
<br />
To use pulseaudio with JACK, JACK must be started up before Pulseaudio, using whichever method you prefer. Pulseaudio then needs to be started loading the 2 relevant modules. Edit {{ic|/etc/pulse/default.pa}}, and change the following region:<br />
### Load audio drivers statically (it is probably better to not load<br />
### these drivers manually, but instead use module-hal-detect --<br />
### see below -- for doing this automatically)<br />
#load-module module-alsa-sink<br />
#load-module module-alsa-source device=hw:1,0<br />
#load-module module-oss device="/dev/dsp" sink_name=output source_name=input<br />
#load-module module-oss-mmap device="/dev/dsp" sink_name=output source_name=input<br />
#load-module module-null-sink<br />
#load-module module-pipe-sink<br />
<br />
### Automatically load driver modules depending on the hardware available<br />
.ifexists module-udev-detect.so<br />
load-module module-udev-detect<br />
.else<br />
### Alternatively use the static hardware detection module (for systems that<br />
### lack udev support)<br />
load-module module-detect<br />
.endif<br />
<br />
to the following:<br />
### Load audio drivers statically (it is probably better to not load<br />
### these drivers manually, but instead use module-hal-detect --<br />
### see below -- for doing this automatically)<br />
#load-module module-alsa-sink<br />
#load-module module-alsa-source device=hw:1,0<br />
#load-module module-oss device="/dev/dsp" sink_name=output source_name=input<br />
#load-module module-oss-mmap device="/dev/dsp" sink_name=output source_name=input<br />
#load-module module-null-sink<br />
#load-module module-pipe-sink<br />
load-module module-jack-source<br />
load-module module-jack-sink<br />
<br />
### Automatically load driver modules depending on the hardware available<br />
#.ifexists module-udev-detect.so<br />
#load-module module-udev-detect<br />
#.else<br />
### Alternatively use the static hardware detection module (for systems that<br />
### lack udev support)<br />
#load-module module-detect<br />
#.endif<br />
<br />
Basically, this prevents module-udev-detect from loading. module-udev-detect will always try to grab your sound-card (JACK has already done that, so this will cause an error). Also, the jack source and sink must be explicitly loaded.<br />
<br />
====QjackCtl with Startup/Shutdown Scripts====<br />
Using the settings listed above you can use QjackCtl to execute a script upon startup and shutdown to load/unload PulseAudio. Part of the reason you may wish to do this is that the above changes disable PulseAudio's automatic hardware detection modules. This particular setup is for using PulseAudio in an exclusive fashion with JACK, though the scripts could be modified to unload and load an alternate non-JACK setup, but killing and starting PulseAudio while programs might be using it would become problematic.<br />
<br />
The following example could be used and modified as necessary as a startup script that daemonizes PulseAudio and loads the ''padevchooser'' program (optional, needs to be built from AUR) called {{ic|jack_startup}}:<br />
#!/bin/bash<br />
#Load PulseAudio and PulseAudio Device Chooser<br />
<br />
pulseaudio -D<br />
padevchooser&<br />
<br />
as well as a shutdown script to kill PulseAudio and the Pulse Audio Device Chooser, as another example called {{ic|jack_shutdown}} also in the home directory:<br />
#!/bin/bash<br />
#Kill PulseAudio and PulseAudio Device Chooser<br />
<br />
pulseaudio --kill<br />
killall padevchooser<br />
<br />
Both scripts need to be made executable:<br />
chmod +x jack_startup jack_shutdown<br />
<br />
then with QjackCtl loaded, click on the ''Setup'' button and then the ''Options'' tab and tick both "Execute Script after Startup:" And "Execute Script on Shutdown:" and put either use the ... button or type the path to the scripts (assuming the scripts are in the home directory) {{ic|~/jack_startup}} and {{ic|~/jack_shutdown}} making sure to save the changes you have made.<br />
<br />
===Pulseaudio through OSS===<br />
Add the following to {{ic|/etc/pulse/default.pa}}:<br />
load-module module-oss<br />
<br />
Then start Pulseaudio as usual. You should have sinks and sources for your OSS devices.<br />
<br />
===Pulseaudio from within a chroot (ex. 32-bit chroot in 64-bit install)===<br />
Since a chroot sets up an alternative root for the running/jailing of applications, pulseaudio must be installed within the chroot itself ({{ic|pacman -S pulseaudio}} within the chroot environment).<br />
<br />
Pulseaudio, if not set up to connect to any specific server (this can be done in {{ic|/etc/pulse/client.conf}}, through the PULSE_SERVER environment variable, or through publishing to the local X11 properties using module-x11-publish), will attempt to connect to the local pulse server, failing which it will spawn a new pulse server. Each pulse server has a unique ID based on the machine-id value in {{ic|/var/lib/dbus}}. To allow for chrooted apps to access the pulse server, the following directories must be mounted within the chroot:-<br />
/var/run<br />
/var/lib/dbus<br />
/tmp<br />
~/.pulse<br />
<br />
{{ic|/dev/shm}} should also be mounted for efficiency and good performance. Note that mounting /home would normally also allow sharing of the {{ic|~/.pulse}} folder.<br />
<br />
For specific direction on accomplishing the appropriate mounts, please refer to the wiki on installing a bundled 32-bit system, especially the [http://wiki.archlinux.org/index.php?title=Arch64_Install_bundled_32bit_system#Additional_mount_option_to_allow_32-bit_apps_to_access_the_64-bit_Pulseaudio_server additional section] specific to Pulseaudio.<br />
<br />
===Simultaneous Digital and Analog Output===<br />
As an example situation: you want to listen to music at your desktop, using the regular 3.5mm analog outputs into your desktop PC speakers. You also want to feed the same music to your hi-fi system in another room via your sound card's digital output. You would think this would be a simple matter, but for many sound chipsets, it requires some editing to get it set up since the default Pulseaudio profiles allow you to use either analog or digital, but not both simultaneously.<br />
<br />
The solution is as follows (with thanks for some useful pointers from: http://superuser.com/questions/267442/how-to-get-simultaneous-sound-from-pulseadio-on-two-outputs-analog-and-digital). Amarok is used in this example.<br />
<br />
* Install "pavucontrol" (pacman -S pavucontrol). You ''won't'' be needing the other useful pulse configuration utility "paprefs" for this task.<br />
* In a terminal, launch "pacmd" - a command line utility for loading pulse modules<br />
* Enter the following commands in pacmd in this order (where your numbers for "hw:0,0" are determined by entering "aplay -l" in terminal. One number is the hardware ID for the analog device, the other for the digital):<br />
load-module module-alsa-sink device="hw:0,0" sink_name=analog_output<br />
load-module module-alsa-sink device="hw:0,1" sink_name=digital_output<br />
load-module module-combine sink_name=analog_digital slaves=digital_output,analog_output<br />
<br />
* Open "pavucontrol" from a terminal<br />
* Under pavucontrol's "Playback Tab", for the running app Amarok, select "Simultaneous output to Internal Audio, Internal Audio" (you will need to have Amarok playing something to test this)<br />
* Under the "Configuration Tab" Select "Digital Stereo Duplex (IEC958)" for "Internal Audio" (your exact names may vary here, according to how ALSA has named your hardware). You should now be able to hear Amarok playing on both your analog and digital outputs!<br />
<br />
The above solution only holds to long as you have pacmd running, and is specific for the running app (in the above example, Amarok).<br />
<br />
To set the the sinks up every reboot and for all audio apps, add the above load-module commands to your '''/etc/pulse/default.pa''' file. You may need to add them at the start of the file, just above line "### Automatically restore the volume of streams and devices", or it may not work as expected.<br />
<br />
Finally, use the Gnome 3 sound preferences to set your system's default "Output" to "Simultaneous output to Internal Audio, Internal Audio".<br />
<br />
===System-wide Equalizer===<br />
Pulseaudio can be configured to sound much better through the use of a system-wide equalizer. There are a few tools to do this. Extra information on the cons of each [http://ubuntuforums.org/showthread.php?t=1378087 here] . Individual apps can be excluded via {{Filename|pavucontrol}} .<br />
<br />
====pulseaudio-equalizer====<br />
A simple, user-friendly gtk tool which you can grab from the AUR [https://aur.archlinux.org/packages.php?ID=48316 here]. <br />
<br />
{{Note| If you remove pulseaudio-equalizer, you should comment out the respective generated section in {{Filename | $HOME/.pulse/default.pa}} or you may have strange issues.}}<br />
{{Note|If you have trouble with the volume resetting to the maximum level or making harsh noise upon switching sound sources, do [https://wiki.archlinux.org/index.php/Pulseaudio#Volume_gets_louder_every_time_a_new_application_is_started this] and then find the "Equalized audio configuration" section in {{Filename | $HOME/.pulse/default.pa}} and comment out only the "set-sink-volume" line there.}}<br />
<br />
====qpaeq====<br />
A simple qt tool that comes with pulseaudio and includes support for more bands than pulseaudio-equalizer (just resize the window horizontally), but presently lacks easily accessible presets and may need to be set as the default manually. Located at {{Filename | /usr/bin/qpaeq}} and requires {{Filename|python2-pyqt}} to run. <br />
<br />
{{Note| If qpaeq crashes at startup, be sure you have {{Filename|load-module module-equalizer-sink}} in {{Filename|/etc/pulse/default.pa}} or {{Filename|$HOME/.pulse/default.pa}} }}<br />
<br />
{{Note| If the equalizer has no effect (e.g., setting the ''qpaeq'' preamp bar to zero doesn't mute all sound), you may need to link your applications' audio sinks to the equalizer. Do this by adding the line {{Filename|set-default-sink equalized}} to {{Filename|/etc/pulse/default.pa}} or {{Filename|$HOME/.pulse/default.pa}}.}}<br />
<br />
==Troubleshooting==<br />
===No sound after install===<br />
<br />
====Bad configuration files====<br />
If after starting pulseaudio your system outputs no sound, it may be necessary to delete the contents of {{ic|~/.pulse}}. Pulseaudio will automatically create new configuration files on its next start.<br />
<br />
====Flash Content====<br />
If after installing pulseaudio you get no sound from flash content, you can try installing [http://aur.archlinux.org/packages.php?ID=13384 libflashsupport-pulse] from the AUR. You can also try lib32-libpulse if on a 64-bit Arch and using [multilib]'s flashplugin:<br />
<br />
# pacman -S lib32-libcanberra-pulse lib32-alsa-plugins<br />
<br />
====No cards====<br />
If PulseAudio starts, run {{ic|pacmd list}}. If no cards are reported, make sure that your ALSA devices are not in use:<br />
$ fuser -v /dev/snd/*<br />
$ fuser -v /dev/dsp<br />
<br />
Make sure any applications using the pcm or dsp files are shut down before restarting PulseAudio.<br />
<br />
====The only device shown is "dummy output"====<br />
This may be caused by different reasons, one of them being the .asoundrc file in your home taking precedence over the systemwide /etc/asound.conf.<br />
<br />
The user file is modified also by the tool '''asoundconf''' or by its graphical variant '''asoundconf-gtk''' (the latter is named "Default sound card" in the menu) as soon as you run it.<br />
You can prevent the effects of .asoundrc altogether by commenting the last line like this:<br />
<br />
#</home/<yourusername>/.asoundrc.asoundconf><br />
<br />
====KDE4====<br />
It may be that you have another output device set as preferred in phonon. Make sure that every setting has your preferred output device at the top, and check the playback streams tab in kmix to make sure that applications are using the device for output.<br />
<br />
====Muted audio device====<br />
If you experience no audio output via any means while using ALSA as your default device, you may have to unmute your sound card. To do this, you will want to launch alsamixer and make sure each column has a green 00 under it (this can be toggled by pressing 'm')<br />
$ alsamixer -c 0<br />
<br />
===Bluetooth headset replay problems===<br />
Some user [https://bbs.archlinux.org/viewtopic.php?id=117420 report] huge delays or even no sound when the bluetooth connection does not send any data. This is due to an idle-suspend-module that puts the related sinks/sources automatically into suspend. As this can cause problems with headset, the responsible module can be deactivated. <br />
<br />
1. cp /etc/pulse/default.pa ~/.pulse/default.pa<br />
2. comment out the "load-module module-suspend-on-idle" line in ~/.pulse/default.pa<br />
3. pulseaudio -k && pulseaudio --start<br />
<br />
[http://robert.orzanna.de/2011/08/10/prevent-idle-suspend-with-a-bluetooth-headset-and-a2dp/ More information]<br />
<br />
===Pulse overwrites ALSA settings===<br />
Pulseaudio usually overwrites the ALSA settings- for example set with alsamixer- at start up, even when the alsa daemon is loaded. Since there seems to be no other way to restrict this behaviour, a workaround is to restore the alsa settings again after pulseaudio had started. Add the following command to {{ic|.xinitrc}} {{ic|.bash_login}} or any other autostart file and adjust the sleep, depending how long pulse needs to start on your system.<br />
<br />
(sleep 30 && alsactl -f /var/lib/alsa/asound.state restore) &<br />
<br />
===Daemon startup failed===<br />
Try resetting PulseAudio. To do that:<br />
$ pulseaudio --kill<br />
$ killall pulseaudio<br />
$ killall -9 pulseaudio<br />
$ rm -rf ~/.pulse*<br />
$ rm -rf /tmp/pulse*<br />
<br />
Afterwards, start PulseAudio again.<br />
<br />
===padevchooser===<br />
If you cannot launch the PulseAudio Device Chooser, first (re)start the Avahi daemon as follows:<br />
$ /etc/rc.d/avahi-daemon restart<br />
<br />
===Glitches, skips or crackling===<br />
The PulseAudio sound server uses a timer-based audio scheduling instead of the traditional interrupt-driven approach. Timer-based scheduling may expose issues in some ALSA drivers. To turn timer-based scheduling off, replace the line:<br />
load-module module-udev-detect <br />
in {{ic|/etc/pulse/default.pa}} by:<br />
load-module module-udev-detect tsched=0<br />
Then restart the PulseAudio server.<br />
<br />
===Choppy sound===<br />
Choppy sound in pulsaudio can result from wrong settings for the sample rate in /etc/pulse/daemon.conf. Try changing the line <br />
; default-sample-rate = 44100<br />
to <br />
default-sample-rate = 48000<br />
and restart the PulseAudio server.<br />
<br />
If you experience choppy sound in applications using openAL, you should also change the sample rate in /etc/openal/alsoft.conf:<br />
frequency = 48000<br />
<br />
===Volume adjustment doesn't work properly===<br />
You might want to check <br />
/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common<br />
<br />
If the volume does not appear to increment/decrement properly using {{ic|alsamixer}} or {{ic|amixer}}, it may be due to pulseaudio having a larger number of increments (65537 to be exact). Try using larger values when changing volume (e.g. {{ic|amixer set Master 655+}}).<br />
<br />
===Volume gets louder every time a new application is started===<br />
Per default, it seems as if changing the volume in an application sets the global system volume to that level instead of only affecting the respective application. Applications setting their volume on startup will therefore cause the system volume to "jump".<br />
If you encounter this issue, you can fix it by uncommenting <br />
flat-volumes = no<br />
in<br />
/etc/pulse/daemon.conf<br />
and then restarting PulseAudio by executing<br />
pulseaudio -k<br />
<br />
When Pulse comes back after a few seconds, applications will not alter the global system volume anymore but have their own volume level again.<br />
<br />
{{Note| If you've previously installed and removed pulseaudio-equalizer, remnants of it in {{Filename|$HOME/.pulse/default.pa}} can also cause maximized volume trouble. Comment that out as needed.}}<br />
<br />
===No mic on ThinkPad T400/T500===<br />
Run<br />
alsamixer -c 0<br />
and maximize the volume of/unmute the "Internal Mic". Please improve this documentation if you know the cause of this issue.<br />
<br />
===No mic input on Acer Aspire One===<br />
Install pavucontrol, unlink the microphone channels and turn down the left one to 0. You should now be able to use your microphone.<br />
Reference: http://getsatisfaction.com/jolicloud/topics/deaf_internal_mic_on_acer_aspire_one#reply_2108048<br />
<br />
===Sound output is only mono on M-Audio Audiophile 2496 sound card===<br />
Add the following to /etc/pulseaudio/default.pa:<br />
load-module module-alsa-sink sink_name=delta_out device=hw:M2496 format=s24le channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7<br />
load-module module-alsa-source source_name=delta_in device=hw:M2496 format=s24le channels=12 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9<br />
set-default-sink delta_out<br />
set-default-source delta_in<br />
<br />
===Static Noise in Microphone Recording===<br />
If we are getting static noise in skype, gnome-sound-recorder, arecord, etc.'s recordings then the sound card samplerate is incorrect. That's why there is static noise in linux microphone recordings. To fix this We need to set sample-rate in /etc/pulse/daemon.conf for the sound hardware.<br />
<br />
====1. Determine soundcards in the system====<br />
This requires alsa-utils and related packages to be installed:<br />
$ arecord --list-devices<br />
<br />
output:<br />
**** List of CAPTURE Hardware Devices ****<br />
card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
card 0: Intel [HDA Intel], device 2: ALC888 Analog [ALC888 Analog]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
<br />
soundcard is hw:0,0<br />
<br />
====2. Determine sampling-rate of the sound card====<br />
arecord -f dat -r 60000 -D hw:0,0 -d 5 test.wav<br />
<br />
output:<br />
"Recording WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 60000 Hz, Stereo<br />
Warning: rate is not accurate (requested = 60000Hz, '''got = 96000Hz''')<br />
please, try the plug plugin<br />
<br />
observe, the '''got = 96000Hz''', this is the max sample-rate of our card.<br />
<br />
====3. Setting the soundcard's sampling rate into pulse audio configuration====<br />
the default sample-rate in pulseaudio is<br />
grep "sample-rate" /etc/pulse/daemon.conf<br />
<br />
output:<br />
; default-sample-rate = 44100<br />
<br />
It is 44100 and is disabled. Let us set our sound card's settings into pulseaudio configuation file<br />
su -c "sed 's/; default-sample-rate = 44100/default-sample-rate = 96000/g' -i /etc/pulse/daemon.conf"<br />
<br />
Let's verify the changes to deamon.conf<br />
grep "sample-rate" /etc/pulse/daemon.conf <br />
output:<br />
default-sample-rate = 96000<br />
and it's done.<br />
<br />
====4. Restart pulseaudio to apply the new settings====<br />
pulseaudio --kill<br />
pulseaudio --start<br />
<br />
====5. Finally check by recording and playing it back====<br />
Let's record some voice using mic for say 10 seconds. Make sure the mic is not muted and all<br />
arecord -f cd -d 10 test-mic.wav<br />
<br />
After 10 seconds, let's play the recording...<br />
aplay test-mic.wav<br />
<br />
Now hopefully, there's no static noise in microphone recording anymore.<br />
<br />
=== My Bluetooth device is paired but doesn't play any sound ===<br />
[[Bluetooth#My_device_is_paired_but_no_sound_is_played_from_it|See the article in Bluetooth section]]<br />
<br />
==External links==<br />
*[http://www.pulseaudio.org/wiki/PerfectSetup http://www.pulseaudio.org/wiki/PerfectSetup] - A good guide to make your configuration perfect<br />
*[http://www.alsa-project.org/main/index.php/Asoundrc http://www.alsa-project.org/main/index.php/Asoundrc] - Alsa wiki on .asoundrc<br />
*[http://www.pulseaudio.org/ http://www.pulseaudio.org/] - PulseAudio official site<br />
*[http://www.pulseaudio.org/wiki/FAQ http://www.pulseaudio.org/wiki/FAQ] - PulseAudio FAQ</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Multilib&diff=176297
Multilib
2011-12-30T20:07:25Z
<p>Foolishgrunt: </p>
<hr />
<div>[[Category:Arch64 (English)]]<br />
[[Category:Package management (English)]]<br />
{{i18n|Multilib Project}}<br />
{{out of date|Multilib is here!}}<br />
Multilib support is coming to Arch, see: http://mailman.archlinux.org/pipermail/arch-dev-public/2010-August/017702.html<br />
<br />
The [multilib] repository can be found in multilib/os/x86_64 on your favorite mirror. It contains 32 bit libraries that can be used to run 32 bit applications like the flash plugin and skype in 64 bit installation.<br />
<br />
Add<br />
[multilib]<br />
Include = /etc/pacman.d/mirrorlist<br />
to your {{Filename|/etc/pacman.conf}} to use this repository.<br />
<br />
== TODO list ==<br />
<br />
* build [[Multilib_Project/Needed_Packages]] using the new toolchain (done)<br />
* clean up lib32 stuff from community (done)<br />
* arch-multilib mailing list (done)<br />
* infrastructure (folders) on sigurd for the new repository (done)<br />
* adjust dbscripts so cleanup doesn't kill our packages (done)<br />
* world domination (pending)<br />
<br />
== Developers and TUs interested in helping with multilib ==<br />
<br />
* Thomas Bächler<br />
* Jan Steffens<br />
* Sven-Hendrik Haase<br />
* Ionut Biru<br />
* Rémy Oudompheng<br />
* Laurent Carlier<br />
* Devin Cofer<br />
* Florian Pritz<br />
* ...</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=174813
E17
2011-12-18T05:51:29Z
<p>Foolishgrunt: /* From the community repository (SVN snapshots) */</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
{{i18n|E17}}<br />
[[fr:E17]]<br />
<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From the [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment wiki]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It comprises both the Enlightenment [[window manager]] and Enlightenment Foundation Libraries (EFL), which provide additional desktop environment features such as a toolkit, object canvas, and abstracted objects. E17 has been under development since 2005, but in February 2011 the core EFLs saw their first stable 1.0 release. Enlightenment the window manager is still in the beta stages, but is already quite usable. Many people currently use E17 as a day-to-day desktop environment without problems.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the community repository (SVN snapshots) ===<br />
<br />
{{Note|Make sure the [[community repository]] is enabled in your {{ic|/etc/pacman.conf}}.}}<br />
<br />
To install e17:<br />
pacman -S e-svn<br />
<br />
To install additional e17 modules and applications:<br />
pacman -S e17-extra-svn<br />
<br />
You might also want to install additional [[Fonts]]. You need at least 1 True Type Font.<br />
<br />
If you need/want an e17 package which is not (yet) available in [community], see if it is available in the [[AUR]].<br />
<br />
{{Warning|As e17 is still beta software you are encouraged to keep packages of the previous version on your computer, allowing you to [[downgrade]] if needed.}}<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{ic|easy_e17.sh}} compiles E17 from source and installs it in {{ic|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{AUR|easy-e17}}.<br />
# Edit {{ic|/etc/easy_e17.conf}} if you want.<br />
# Run it as user, so it downloads to ~/e17_src and builds as user, to install E17 (the script will immediately ask for your password so it can install in the end): {{bc|# easy_e17.sh -i}}{{Warning|This will install the latest svn version. For a stable result add the <nowiki>--srcrev=</nowiki> parameter with the latest stable revision. For beta 3 use 55246 as argument. For the revision with the 1.0 release of the core libraries, use 56361.}}<br />
# Put {{ic|/opt/e17/bin}} in your {{ic|PATH}} by editing {{ic|/etc/profile}}. For example, you can add this line at the end of the file: {{bc|1=PATH="$PATH:/opt/e17/bin"}}<br />
# If, after completing the install, xinitrc complains that it cannot find enlightenment upon starting, you may need to add these lines to the end of /etc/profile as well:{{bc|1=PYTHONPATH=":$PYTHONPATH"}}{{bc|1=LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/e17/lib"}}<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it is not a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{ic|update_e17.sh}} is a zenity script which is made to accompany {{ic|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
=== startx ===<br />
If you use {{ic|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
=== Elsa ===<br />
Nowadays E17 has a new display manager called Elsa, you can download it from AUR {{AUR|elsa-svn-arch}}.<br />
Elsa is quite sophisticated and its configuration is controlled by {{ic|/etc/elsa.conf}}.<br />
To start Elsa add the following line to your {{ic|/etc/inittab}}<br />
x:5:respawn:/usr/sbin/elsa<br />
and change your default runlevel to 5.<br />
<br />
=== Other ===<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{ic|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{ic|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
=== NetworkManager ===<br />
<br />
You can use {{Pkg|networkmanager}} to manage your network connections.<br />
<br />
pacman -S networkmanager<br />
<br />
Then you need to follow the instructions on [[NetworkManager]] to do the configuration. You may also need {{Pkg|network-manager-applet}} to help with your settings.<br />
<br />
pacman -S network-manager-applet<br />
<br />
You may want to add it to the start up programs so every time your E17 starts it appears on systray.<br />
<br />
Settings -> Settings Panel -> Apps -> Startup Applications -> System -> Network<br />
<br />
=== connman ===<br />
<br />
Another available network manager is [[Connman]], you can download it from AUR {{AUR|connman}}. You do not need to follow any of the other instructions on the [[Connman|Connman wiki page]]. The current build of ConnMan already includes network policy group section (although with only one statement, not three).<br />
<br />
Next, edit your {{ic|/etc/rc.conf}}. Remove '''network''' from your DAEMONS line. Add '''connmand''' (do not forget the '''d''') ''after'' '''dbus''' and '''hal'''.<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you have installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog. During 2010 there was a change in how themes work, so for older themes you may need to do the following:<br />
edje_convert <theme>.edj<br />
<br />
Note: the edje_convert binary has been "dropped" by upstream developers... see: [http://trac.enlightenment.org/e/changeset/56156 trac.enlightenment.org]<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{ic|etk_prefs}}.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{ic|~/.e}} and remove it (e.g. {{ic|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream. http://trac.enlightenment.org/e/report<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Pkg|libxcursor}} package.<br />
<br />
=== Screen unlocking does not work ===<br />
<br />
If screenlock does not accept your password add the following to {{ic|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-dejavu ttf-bitstream-vera<br />
<br />
=== Modules and gadgets ===<br />
;Module:a name used in enlightenment to refer to the "backing" code for a gadget.<br />
;Gadget:a front-end or user interface that should help the end users of [[E17]] do something.<br />
<br />
=== udisks vs. HAL ===<br />
Often a gadget with the name "Places", for example, will use a corresponding module also named "Places". Also modules may need to use underlying libraries or daemons to interact with various devices connected to your computer. Currently there are at least two choices for these underlying libraries or daemons to interact with connected devices. The two that will be considered here are udisks and HAL. At the time of this entry the [[HAL]] page says:<br />
:''HAL (Hardware Abstraction Layer) is a daemon that allows desktop applications to readily access hardware information, to locate and use such hardware regardless of bus or device type. In this way a desktop GUI can present all resources to its user in a seamless and uniform manner. HAL has become deprecated in favor of udev, udisks, upower, etc. and is no longer developed. Currently, a small number of programs still rely on and use HAL, though development is heading toward utilizing udev as a replacement.''<br />
<br />
So, apparently [[E17]] now tries to use udisks instead of [[HAL]]. But some of the modules and gadgets, such as Places, have not been updated to use udisks yet.<br />
<br />
=== What is Places? ===<br />
From the current source code [http://trac.enlightenment.org/e/browser/trunk/E-MODULES-EXTRA/places/README README] for Places:<br />
;Places module:''This module manage the volumes device attached to the system.''<br />
<br />
In [http://www.urbandictionary.com/define.php?term=engrish other words], Places is a gadget that will help you browse files on various devices you might plug into your computer, like phones, cameras, or other various storage devices you might plug into the usb port.<br />
<br />
==== Why doesn't the Places work? ====<br />
So, if you load the "Places" module, and then add the Places gadget to, say, your bottom shelf in enlightenment, it may look something like a blank grey area with no Gadget in it because the Places module and Gadget are still trying to use [[HAL]]. Not to mention that if you plug a usb device in, the Places module will not detect it. So in order to fix this, here is a "solution":<br />
<br />
==== A workaround that gets Places working ====<br />
This procedure will attempt to help you get the HAL daemon running and the Places gadget working on your e17 desktop.<br />
<br />
Install {{AUR|hal-info}} and {{AUR|hal-git}} from the [[Arch User Repository]]. Note that {{AUR|hal-info}} is a dependency for {{AUR|hal-git}}, so you may want to install it with [[pacman]]'s {{ic|--asdeps}} flag.<br />
<br />
Start the hal daemon <br />
<br />
{{bc|# rc.d start hal}}<br />
<br />
Now you must remove the "Places" gadget from my shelf, and unload the Places module from menu {{ic|settings -> modules -> Places -> unload}}<br />
<br />
Restart enlightenment, reload the Places module and add the Places gadget to my shelf <br />
<br />
Try connecting a USB camera and watch it appear as a new device on the gadget bar in "places". If necessary, move it to the desktop, right click on the gadget {{ic|Gadget Places -> Move to -> Desktop}}.<br />
<br />
The Places gadget on the desktop should now look like an icon with a camera plugged into a usb port, and when you click on it, it opens a file manager, and shows you the files on your camera.<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=LightDM&diff=165017
LightDM
2011-10-10T23:58:09Z
<p>Foolishgrunt: /* Enabling Lightdm */</p>
<hr />
<div>[[Category:Display managers (English)]]<br />
{{i18n|LightDM}}<br />
{{Article summary start}}<br />
{{Article summary text|Provides an overview of the Light Display Manager.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Display Manager}}<br />
{{Article summary end}}<br />
[http://www.freedesktop.org/wiki/Software/LightDM Lightdm] LightDM is a cross-desktop display manager that aims is to be the standard display manager for the X.org X server.<br />
== Installation ==<br />
You can install {{Package AUR|lightdm}} from the [[AUR]].<br />
<br />
== Enabling Lightdm ==<br />
Lightdm can be loaded on startup by entering it in your daemons array in {{Filename|rc.conf}}, or by appending the following line to {{Filename|inittab}}:<br />
x:5:respawn:/usr/sbin/lightdm >& /dev/null<br />
See [[Display Manager]] for detailed instructions.<br />
<br />
== Configuration ==<br />
In most cases further configuration will not be necessary. If needed, a well documented configuration file exists in <br />
/etc/lightdm/lightdm.conf<br />
<br />
It is possible to test lightdm with the following command:<br />
{{Cli|$ lightdm --test-mode -c /etc/lightdm/lightdm.conf}}<br />
<br />
Note that this requires [http://www.archlinux.org/packages/extra/i686/xorg-server-xephyr/ xorg-server-xephyr] to be installed, first.</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Display_manager&diff=165016
Display manager
2011-10-10T23:55:21Z
<p>Foolishgrunt: /* Modify default display manager */ Added LightDM.</p>
<hr />
<div>[[Category:Display managers (English)]]<br />
{{i18n|Display Manager}}<br />
[[de:Login-Manager]]<br />
[[fr:Gestionnaire de connexions]]<br />
<br />
{{Article summary start}}<br />
{{Article summary text|A display manager presents the user with a login screen which prompts for a user name and password. A session starts when the user successfully enters a valid combination of user name and password. This article covers installation, configuration, and troubleshooting of common display managers.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Start X at Boot}}<br />
{{Article summary end}}<br />
<br />
A [[Wikipedia:X display manager (program type)|display manager]], or login manager, is a graphical interface screen that is displayed at the end of the boot process in place of the default shell. There are various types of display managers, just as there are various types of window and desktop managers. There is usually a certain amount of customization and themeability available with these managers.<br />
<br />
==Installation==<br />
Choose and install a preferred display manager:<br />
<br />
{{Note|If you use a desktop environment, you should consider using the display manager that corresponds to it.}}<br />
<br />
'''[[XDM]]:''' X Display Manager<br />
# pacman -S xorg-xdm<br />
<br />
'''[[GDM]]:''' [[GNOME]] Display Manager<br />
# pacman -S gdm<br />
<br />
'''[[KDM]]:''' [[KDE]] Display Manager<br />
# pacman -S kdebase-workspace<br />
<br />
'''[[SLiM]]:''' Simple Login Manager<br />
# pacman -S slim<br />
<br />
'''[[Qingy]]:''' DirectFB [[getty]] replacement. The Arch theme package is optional.<br />
# pacman -S qingy qingy-theme-arch<br />
<br />
'''[[LXDM]]''' Part of the [[LXDE]] but it is independent of the desktop environment.<br />
# pacman -S lxdm<br />
<br />
'''[[wdm]]:''' WINGs Display Manager<br />
# pacman -S wdm<br />
<br />
'''[[CDM]]:''' Console Display Manager<br />
*package available in the [[AUR]]: {{Package AUR|cdm}}<br />
*latest development revision: {{Package AUR|cdm-git}}<br />
<br />
[[LightDM]]: Ubuntu replacement for GDM using webkit <br />
*package available in the [[AUR]]: {{Package AUR|lightdm}}<br />
*latest development revision: {{Package AUR|lightdm-bzr}}<br />
<br />
==Loading the display manager==<br />
You have two easy methods to make the system load the display manager:<br />
<br />
; {{Filename|inittab}} method : The display manager will load automatically after start-up and will respawn in the event of a crash.<br />
; [[Daemon]] method : The display manager will load automatically during the start-up as a daemon.<br />
<br />
The {{Filename|inittab}} method will allow you to boot directly into framebuffer mode from [[GRUB]]. This is an advantage should the graphics driver crash in X, for example, you would not be forced to fix your system from a live CD or through other needlessly complex means.<br />
<br />
With the {{Filename|inittab}} method all you would have to do is to press 'e' for edit at the GRUB prompt and just add the number of the run-level you prefer, such as run-level '''3''', to the end of the 'kernel' line to boot directly into framebuffer mode in order to fix your system/X (this described in detail below.)<br />
<br />
When using the daemon method you can simply boot into runlevel '''1/S''' which will prevent any daemons, including the login manager, from being started. Then you can fix your system/X and switch into the runlevel '''3'''. Both methods are equally easy.<br />
<br />
==={{Filename|inittab}} method===<br />
See [[inittab]] for additional information.<br />
<br />
{{Warning| You may get problems if you use [[KMS]] with your video driver. It can freeze your display output.}}<br />
<br />
The run-levels are:<br />
0 Halt<br />
1(S) Single-user<br />
2 Not used<br />
3 Multi-user (default)<br />
4 Not used<br />
5 X11<br />
6 Reboot<br />
<br />
====Modify default run-level====<br />
Edit {{Filename|/etc/inittab}} and find the line that looks like this:<br />
id:3:initdefault:<br />
<br />
Modify the '3' to '5' for X11:<br />
id:5:initdefault:<br />
<br />
The next time you reboot, the 'X display manager' should run. For other display managers see below:<br />
<br />
====Modify default display manager====<br />
Edit {{Filename|/etc/inittab}} and find the line that looks like similar to this one (near the end):<br />
x:5:respawn:/usr/bin/xdm -nodaemon<br />
<br />
Modify it so it points to the display manager of your choice:<br />
<br />
'''GDM:'''<br />
x:5:respawn:/usr/sbin/gdm -nodaemon<br />
<br />
'''KDM:'''<br />
x:5:respawn:/usr/bin/kdm -nodaemon<br />
<br />
'''SLiM:'''<br />
x:5:respawn:/usr/bin/slim >/dev/null 2>&1<br />
<br />
'''LXDM'''<br />
x:5:respawn:/usr/sbin/lxdm >/dev/null 2>&1<br />
<br />
'''LightDM'''<br />
x:5:respawn:/usr/sbin/lightdm >& /dev/null<br />
<br />
The next time you reboot, the display manager of your choice should run.<br />
<br />
===Daemon method===<br />
You simply need to add the daemon name to your daemons array in {{Filename|/etc/rc.conf}}<br />
<br />
Near the end of the file you will see a line that looks similar to the following:<br />
DAEMONS=(syslogd klogd !pcmcia network netfs crond) # this is the daemons array<br />
<br />
Append the daemon name for the display manager of your choice ({{Codeline|gdm}}, {{Codeline|kdm}}, or {{Codeline|slim}}):<br />
DAEMONS=(syslogd klogd !pcmcia network netfs crond '''slim''')<br />
<br />
Ensure you start the display manager '''last''' in the DAEMONS array, otherwise X will later allocate a tty device which was previously claimed by [[Getty]] (see {{Filename|/etc/inittab}}). Not placing the display manager at the end can cause X crashes, and is therefore unsupported.<br />
<br />
The next time you reboot, the display manager should run. In the event that it does not, be certain that you typed in the name correctly, and that the manager you selected is installed. It also helps to ensure that {{Codeline|startx}} is not stopping with errors.<br />
<br />
{{Note|If you use this method and your display manager hangs while loading, or X does not recognize any input device, you will need to boot into single user mode (run-level 1) using the examples above and remove the display manager daemon from {{Filename|rc.conf}}.}}<br />
<br />
==Troubleshooting==<br />
<br />
===Switching run-levels===<br />
<br />
====Command prompt====<br />
If you want to test out the display manager without rebooting, or you want to change the X configuration and that pesky display manager keeps respawning, use this command:<br />
/sbin/telinit <run-level><br />
<br />
To switch to run-level 3 (Multi-user):<br />
/sbin/telinit 3<br />
<br />
To switch to run-level 5 (X11):<br />
/sbin/telinit 5<br />
<br />
By switching you can avoid restarting the system during your testing.<br />
<br />
====GRUB====<br />
You can add a menu item in [[GRUB]] to allow you to boot with or without X11,<br />
<br />
In {{Filename|/boot/grub/menu.lst}} find the first kernel entry you have (the default is '# (0) Arch Linux')<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz-linux root=/dev/sda3 ro<br />
initrd /initramfs-linux.img<br />
<br />
You can duplicate it and modify both like so:<br />
# (0) Arch Linux Multi-user<br />
title Arch Linux Multi-user<br />
root (hd0,0)<br />
kernel /vmlinuz-linux root=/dev/sda3 ro '''3'''<br />
initrd /initramfs-linux.img<br />
<br />
# (1) Arch Linux X11<br />
title Arch Linux X11<br />
root (hd0,0)<br />
kernel /vmlinuz-linux root=/dev/sda3 ro '''5'''<br />
initrd /initramfs-linux.img<br />
<br />
The run-level was appended to the end so the kernel knows what run-level to start with.<br />
<br />
====LILO====<br />
You can start-up with the run-level of your choice by just selecting or typing in the kernel name and then appending the desired run-level in the [[LILO]] boot screen like so:<br />
: Arch 5</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Arch_based_distributions_(active)&diff=146788
Arch based distributions (active)
2011-06-20T16:38:44Z
<p>Foolishgrunt: /* ArchBang */ Updated screenshot link.</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
{{i18n|Arch Based Distributions (Active)}}<br />
<br />
=Specialty Distributions=<br />
== ArchBang ==<br />
ArchBang[http://wiki.archlinux.org/index.php/ArchBang] LIVE CD = Arch Linux w/ OpenBox (inspired from #!) so ArchBang!!!<br />
<br />
*Homepage: http://www.archbang.org/<br />
*Forums: http://bbs.archbang.org/<br />
*External Links: http://pdg86.wordpress.com/2010/02/02/release-archbang-1-03/<br />
*Screenshot: http://archbang.org/wp-content/uploads/2011/02/ss.png<br />
<br />
An installer is now available with version 2.00 onwards.<br />
<br />
== Arch Hurd ==<br />
Arch Hurd is a port of Arch Linux to the GNU/Hurd platform<br />
<br />
*Homepage: http://www.archhurd.org/<br />
*Forums: http://bbs.archhurd.org/<br />
*Wiki: http://wiki.archhurd.org<br />
*Mailing Lists: http://lists.archhurd.org/<br />
<br />
Most discussions happens in #archhurd on irc.freenode.net.<br />
<br />
== Arch Linux Mobile ==<br />
<br />
Arch Linux Mobile provides an ARM optimised port to run on the OpenMoko Freerunner, an open-source smartphone. It is currently undergoing early but active development.<br />
<br />
*Homepage: http://www.archmobile.org/<br />
*Forums: http://bbs.archlinux.org/viewforum.php?id=35<br />
*Documentation: http://www.archmobile.org/trac/wiki<br />
*Screenshots: http://www.archmobile.org/trac/wiki/AM/SuccessStories<br />
*DistroWatch Entry:<br />
<br />
== ArchLinux PPC ==<br />
<br />
''"The goal of the Archlinux PPC porting project is to make our favourite distribution, Arch Linux, available for the PPC architecture. Our strong community is diverse and helpful, and we pride ourselves on the range of skillsets and uses for Arch that stem from it. Please check out the forums and mailing list to get your feet wet. Also glance through the wiki if you want to learn more about Arch."''<br><br />
:<small>Source: [http://archlinuxppc.org/ Arch Linux PPC]</small><br />
<br />
*Homepage: http://archlinuxppc.org/<br />
*Forums: http://bbs.archlinux.org/<br />
*Documentation: http://wiki.archlinux.org/index.php/Main_Page<br />
*Screenshots: <br />
*DistroWatch Entry:<br />
<br />
== ArchPwn ==<br />
<br />
ArchPwn is a security based Linux Live CD/DVD system that aims to be a fully working swiss army knife for pentesting purpose. It is based on the Arch Linux distribution, and follows the Arch philosophy. It keeps the original system intact, and creates on top of it a package repository with all tools that a pentester needs.<br />
<br />
*Homepage: http://www.archpwn.org/index.php/Main_Page<br />
*Forums: <br />
*Documentation: http://www.archpwn.org/index.php/Main_Page<br />
*Screenshots: http://www.archpwn.org/index.php/Screenshots<br />
*DistroWatch Entry:<br />
<br />
== ArchServer ==<br />
<br />
ArchServer is a derivative work of Arch Linux designed to be more stable in order to be suitable for server use.<br />
<br />
*Homepage: http://www.archserver.org<br />
*Forums: http://bbs.archserver.org<br />
*Documentation: http://docs.archserver.org<br />
*Screenshots: TBA<br />
*DistroWatch Entry: TBA<br />
<br />
== archboot ==<br />
<br />
Archboot is designed for installation or rescue operations. It provides both the i686 and x86_64 architectures on one CD. It uses hwdetect and a different install script from the official Arch Linux install images. It runs in RAM using iniramfs, without any special filesystems like squashfs,<br />
thus it is limited to the RAM which is installed in your system.<br />
<br />
*Homepage: http://projects.archlinux.org/?p=archboot.git;a=summary<br />
*Forums: http://bbs.archlinux.org/<br />
*Documentation: ftp://ftp.archlinux.org/iso/archboot/Readme.txt<br />
*Screenshots: <br />
*DistroWatch Entry: <br />
<br />
== archlive ==<br />
<br />
Archlive is a Simple-Chinese live system based on Arch GNU/Linux. It is distinct from the Arch Live! distribution, adding Chinese language software and packages, but it is based upon Arch Live!<br />
<br />
*Homepage: http://code.google.com/p/archlive/<br />
*Forums: http://bbs.linuxeye.cn/forum-70-1.html<br />
*Documentation: http://code.google.com/p/archlive/w/list<br />
*Screenshots: <br />
*DistroWatch Entry: <br />
<br />
== CDN Linux ==<br />
<br />
CDN Linux is a system based on Arch GNU/Linux. CDN is designed to servers and routers. It is developed by Polish Freesco Group.<br />
<br />
*Homepage: http://cdn.freesco.pl<br />
*Forums: http://forum.freesco.pl<br />
*Documentation: http://cdn.freesco.pl<br />
*Screenshots: http://cdn.freesco.pl<br />
*DistroWatch Entry: <br />
<br />
== Chakra ==<br />
<br />
"''Our goal with Chakra is to provide an operating system for desktops that is easy to use, but still has all the functionality, clarity, power and speediness of a KISS operating system. In the long term, we want to build an operating system based on Arch Linux that meets most requirements desktop users have today, like easy installation of software, graphical system administration, configuring power management on mobile devices, or sharing an internet connection.''"<br><br />
:<small>Source: [http://chakra-project.org/about.html The Chakra Project - About]</small><br />
<br />
The creators of the [[KDEmod]] project have created Chakra, based on Arch and KDEMod (of course). Tools like [http://chakra-project.org/tools-shaman.html Shaman] and [http://chakra-project.org/tools-arxin.html Arxin] show the gradual shift towards a more graphical UI oriented Arch derivative. Nonetheless, the project maintains the KISS principle of Arch, even though the [http://chakra-project.org/tools-tribe.html Tribe installer] on the Live CD provides more of the 'you don't have to know what's inside' philosophy. The installed system however is a pure Arch Linux + KDE4 + Shaman, with some artistic touches.<br />
<br />
*Homepage: http://chakra-project.org/<br />
*Forums: http://chakra-project.org/bbs/<br />
*Documentation: http://chakra-project.org/wiki/index.php/Main_Page<br />
*Screenshots: http://chakra-project.org/about-screenshots.html<br />
*DistroWatch Entry: http://distrowatch.com/table.php?distribution=chakra<br />
<br />
== ConnochaetOS ==<br />
<br />
"''ConnochaetOS will be a free operating system for the desktop with old computers in mind but with modern software. ConnochaetOS will contain only free software, according to the GNU Guidelines for Free System Distributions, follow the KISS principle (Keep it small and simple), need as few resources as possible, be modern, but stable. We aim for minimal hardware requirements, as low as a Pentium I processor and 64 MB RAM for a graphical desktop. We decided to base ConnochaetOS on Arch Linux, but completely rebuild, since we want to support i586, and replace some packages with our own ones, because of footprint, stability or freedom.''"<br><br />
:<small>Source: [http://www.connochaetos.org/wiki/doku.php?id=connochaetos ConnochaetOS Website]</small><br />
<br />
*Homepage: http://www.connochaetos.org<br />
*Forums: http://www.connochaetos.org/forum<br />
*Documentation: http://www.connochaetos.org/wiki/doku.php?id=mainpage<br />
*Screenshots: http://www.connochaetos.org/wiki/doku.php?id=screenshots<br />
*DistroWatch Entry: http://distrowatch.com/table.php?distribution=connochaet<br />
<br />
== CTKArch (formerly CTKArchLive) ==<br />
A lightweight Arch-based liveCD using c²DE (openbox) that includes English and French locales.<br />
*Homepage: http://ctkarch.org/<br />
*Forums: http://ctkarch.org/forum/<br />
*Documentation: http://ctkarch.org/documentation/ <br />
*Screenshots: http://ctkarch.org/download/<br />
*DistroWatch Entry: http://distrowatch.com/table.php?distribution=ctkarch<br />
<br />
== Elegance ==<br />
<br />
Elegance is a Arch Linux spin-off that is heavily influenced by ArchBang[http://wiki.archlinux.org/index.php/ArchBang]. It comes with a small number of programs to start you off on building your own custom desktop.<br />
*Homepage: http://k2z.com<br />
*Forums: <br />
*Documentation:<br />
*Screenshots: <br />
*DistroWatch Entry:<br />
<br />
== Kahel OS ==<br />
<br />
''"Kahel OS is the first and remains to be the only Filipino Linux Distro with the rolling release model on Arch Linux + GNOME. In the community, it is the first to release (non-beta) such Linux OS on Arch Linux + GNOME."''<br><br />
:<small>Source: [http://www.kahelos.org/ Kahel OS]</small><br />
*Homepage: http://www.kahelos.org/<br />
*Forums: http://http://forum.kahelos.org/<br />
*Documentation: http://wiki.kahelos.org/index.php?title=Main_Page<br />
*Screenshots: http://www.kahelos.org/gallery.php<br />
*DistroWatch Entry: http://distrowatch.com/table.php?distribution=kahelos<br />
<br />
== LinHES ==<br />
<br />
LinHES ('''Lin'''ux '''H'''ome '''E'''ntertainment '''S'''ystem) is a distro based heavily on Arch and centered around [http://mythtv.org MythTV], with the expressed goal of being a HES-appliance. Utilizing open source software and off the shelf hardware, you'll be able to assemble a box that can serve as a PVR, Jukebox, Image Viewer, and Game Station. Users can go from a blank hard drive to fully functional MythTV system in literally 15-20 min. For more information, please see the [[LinHES]] wikipage.<br />
<br />
*Homepage: http://www.linhes.org/<br />
*Forums: http://www.linhes.org/phpBB2<br />
*Documentation: http://mysettopbox.tv/pamphlet.html<br />
*Screenshots: http://www.thecodingstudio.com/opensource/linux/screenshots/index.php?linux_distribution_sm=<br />
*DistroWatch Entry: http://distrowatch.com/table.php?distribution=knoppmyth<br />
<br />
== live.linuX-gamers.net ==<br />
<br />
The linuX-gamers Live DVD is a bootable medium with a collection of popular 3D games. It contains both the NVIDIA and ATI proprietary Linux drivers and includes the following games: BzFLag, Enemy Territory, Glest, Nexuiz, Sauerbraten, Torcs, Tremulous, True Combat: Elite, Warsow and World of Padman. Although the live DVD is based on Arch Linux, it does not offer any desktop Linux functionality except gaming.<br />
<br />
*Homepage: http://live.linux-gamers.net/<br />
*Forums: http://github.com/svenstaro/lglive<br />
*Documentation: http://github.com/svenstaro/lglive<br />
*Screenshots: http://live.linux-gamers.net/images/shot2.png<br />
*DistroWatch Entry: http://distrowatch.com/table.php?distribution=linuxgamers<br />
<br />
== Mesk Linux ==<br />
<br />
Mesk Linux is a project aiming at showcasing Arch to Arabic-speaking users . The project is also working on localizing Arch tools and documentation .<br />
<br />
*Homepage: http://www.mesklinux.org/<br />
*Forums: http://www.mesklinux.org/<br />
*Documentation: http://www.wiki.mesklinux.org/<br />
*Screenshots: http://www.mesklinux.org/shots.php<br />
*DistroWatch Entry:<br />
<br />
== PlugApps Linux ==<br />
PlugApps Linux is a light weight distro with packages natively compiled for a Sheevaplug (ARM-optimized).<br />
*Homepage: http://plugapps.com/index.php5?title=Portal:PlugApps_Linux<br />
<br />
= Meta Distributions =<br />
<br />
== archiso ==<br />
<br />
[[archiso]] is a very simple set of bash scripts that allow for building live bootable CD/DVD/USB images based on Arch Linux. It uses a small uncomplicated code base and is actively developed. archiso is the tool used by Arch Linux to generate the official CD/USB images. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, to install disks, to special interest live systems, and who knows what else. Simply put, if it involves Arch on a shiny coaster, it can do it. <br />
<br />
*Homepage: http://projects.archlinux.org/?p=archiso.git;a=summary<br />
*Forums http://bbs.archlinux.org/viewtopic.php?id=73878<br />
*Documentation: [[archiso|wiki article on archlinux.org]]<br />
*Screenshots:<br />
*DistroWatch Entry:<br />
<br />
== Archiso-live ==<br />
<br />
Archiso-live is a fork of archiso that has since gained a fair bit of complexity in its development. Archiso-live undergoes rapid development with fresh releases posted on the dev blog found on its homepage. It uses a modular design approach based on slax. It even uses the slax initrd as a base module to get the system going. This allows archiso-live to be used in an everyday fashion since it has a full xfce desktop. It can also be greatly customized since it uses modules.<br />
<br />
*Homepage: http://godane.wordpress.com/ (GIT: http://github.com/godane/archiso-live/tree/master)<br />
*Forums: http://arch-live.2kool4u.net/forum/index.php<br />
*Documentation: http://arch-live.2kool4u.net/articles.php<br />
*Screenshots: http://arch-live.2kool4u.net/photogallery.php?album_id=1<br />
*DistroWatch Entry:<br />
<br />
== larch ==<br />
<br />
[[larch]] is a collection of scripts used to create live CD/DVD/USB-stick versions of Arch Linux. One design aim is easy customization, so that even relatively inexperienced users can build personalized live CDs, containing whatever packages they want and with their own personal configurations. The resulting medium should also be usable for installation purposes, so that one has a customized Arch Linux installation/rescue medium. As the content can be chosen freely, a comfortable working environment is possible, in contrast to the rather Spartan standard Arch installation CD.<br />
<br />
*Homepage: http://larch.berlios.de/<br />
*Forums: <br />
*Documentation: http://larch.berlios.de/doc/index.html<br />
*Screenshots:<br />
*DistroWatch Entry:<br />
<br />
= Arch Influenced Distros =<br />
<br />
==Alpine Linux==<br />
<br />
Alpine Linux is a run-from-RAM linux distribution. Its original target was small appliances like routers, VPN gateways, or embedded x86 devices. However, it supports hosting other Linux guest OSes under VServer control, making it an attractive hosting solution as well. Though Alpine Linux may not actually be based on Arch, its [http://git.alpinelinux.org/cgit/aports/tree/main/abuild/APKBUILD build system] is undoubtably inspired by Arch. [http://lists.busybox.net/pipermail/busybox/2009-January/068280.html 2][http://wiki.alpinelinux.org/w/index.php?title=Creating_an_Alpine_package&oldid=2701#depends_.26_makedepends 3]<br />
<br />
*Homepage: http://alpinelinux.org<br />
*Documentation: http://wiki.alpinelinux.org/w/index.php?title=Documentation<br />
<br />
== Enlisy ==<br />
<br />
Enlisy is an i686 optimized Linux distribution for Pentium 2 based processors and higher. It is also as simple as possible when it comes to the construction of its underlying core. Enlisy uses its own package manager Apport, which is is based on Libpysrc and Libpypac, which are inspired by Arch's package manager Pacman. Enlisy also uses InitNG for the init system.<br />
<br />
*Homepage: http://enlisy.com/<br />
*Forums: http://enlisy.com/en/forum/<br />
*Documentation: http://enlisy.org/ewiki/Documentation<br />
*Screenshots: <br />
*DistroWatch Entry:<br />
<br />
== Frugalware ==<br />
<br />
''"Frugalware Linux is a general-purpose Linux distribution designed for intermediate users who are familiar with command-line operations. It is based on Slackware, but uses a different package management system, Pacman."''<br><br />
:<small>Source: [[Wikipedia:Frugalware|Wikipedia]]</small><br />
<br />
*Homepage: http://frugalware.org<br />
*Forums: http://forums.frugalware.org<br />
*Documentation: http://frugalware.org/docs<br />
*Screenshots: http://frugalware.org/screenshots<br />
*DistroWatch Entry: http://distrowatch.com/frugalware</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Arch_based_distributions_(active)&diff=146787
Arch based distributions (active)
2011-06-20T16:37:23Z
<p>Foolishgrunt: /* ArchBang */ Updated forum link.</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
{{i18n|Arch Based Distributions (Active)}}<br />
<br />
=Specialty Distributions=<br />
== ArchBang ==<br />
ArchBang[http://wiki.archlinux.org/index.php/ArchBang] LIVE CD = Arch Linux w/ OpenBox (inspired from #!) so ArchBang!!!<br />
<br />
*Homepage: http://www.archbang.org/<br />
*Forums: http://bbs.archbang.org/<br />
*External Links: http://pdg86.wordpress.com/2010/02/02/release-archbang-1-03/<br />
*Screenshot: http://omploader.org/vM2g3ZA<br />
<br />
An installer is now available with version 2.00 onwards.<br />
<br />
== Arch Hurd ==<br />
Arch Hurd is a port of Arch Linux to the GNU/Hurd platform<br />
<br />
*Homepage: http://www.archhurd.org/<br />
*Forums: http://bbs.archhurd.org/<br />
*Wiki: http://wiki.archhurd.org<br />
*Mailing Lists: http://lists.archhurd.org/<br />
<br />
Most discussions happens in #archhurd on irc.freenode.net.<br />
<br />
== Arch Linux Mobile ==<br />
<br />
Arch Linux Mobile provides an ARM optimised port to run on the OpenMoko Freerunner, an open-source smartphone. It is currently undergoing early but active development.<br />
<br />
*Homepage: http://www.archmobile.org/<br />
*Forums: http://bbs.archlinux.org/viewforum.php?id=35<br />
*Documentation: http://www.archmobile.org/trac/wiki<br />
*Screenshots: http://www.archmobile.org/trac/wiki/AM/SuccessStories<br />
*DistroWatch Entry:<br />
<br />
== ArchLinux PPC ==<br />
<br />
''"The goal of the Archlinux PPC porting project is to make our favourite distribution, Arch Linux, available for the PPC architecture. Our strong community is diverse and helpful, and we pride ourselves on the range of skillsets and uses for Arch that stem from it. Please check out the forums and mailing list to get your feet wet. Also glance through the wiki if you want to learn more about Arch."''<br><br />
:<small>Source: [http://archlinuxppc.org/ Arch Linux PPC]</small><br />
<br />
*Homepage: http://archlinuxppc.org/<br />
*Forums: http://bbs.archlinux.org/<br />
*Documentation: http://wiki.archlinux.org/index.php/Main_Page<br />
*Screenshots: <br />
*DistroWatch Entry:<br />
<br />
== ArchPwn ==<br />
<br />
ArchPwn is a security based Linux Live CD/DVD system that aims to be a fully working swiss army knife for pentesting purpose. It is based on the Arch Linux distribution, and follows the Arch philosophy. It keeps the original system intact, and creates on top of it a package repository with all tools that a pentester needs.<br />
<br />
*Homepage: http://www.archpwn.org/index.php/Main_Page<br />
*Forums: <br />
*Documentation: http://www.archpwn.org/index.php/Main_Page<br />
*Screenshots: http://www.archpwn.org/index.php/Screenshots<br />
*DistroWatch Entry:<br />
<br />
== ArchServer ==<br />
<br />
ArchServer is a derivative work of Arch Linux designed to be more stable in order to be suitable for server use.<br />
<br />
*Homepage: http://www.archserver.org<br />
*Forums: http://bbs.archserver.org<br />
*Documentation: http://docs.archserver.org<br />
*Screenshots: TBA<br />
*DistroWatch Entry: TBA<br />
<br />
== archboot ==<br />
<br />
Archboot is designed for installation or rescue operations. It provides both the i686 and x86_64 architectures on one CD. It uses hwdetect and a different install script from the official Arch Linux install images. It runs in RAM using iniramfs, without any special filesystems like squashfs,<br />
thus it is limited to the RAM which is installed in your system.<br />
<br />
*Homepage: http://projects.archlinux.org/?p=archboot.git;a=summary<br />
*Forums: http://bbs.archlinux.org/<br />
*Documentation: ftp://ftp.archlinux.org/iso/archboot/Readme.txt<br />
*Screenshots: <br />
*DistroWatch Entry: <br />
<br />
== archlive ==<br />
<br />
Archlive is a Simple-Chinese live system based on Arch GNU/Linux. It is distinct from the Arch Live! distribution, adding Chinese language software and packages, but it is based upon Arch Live!<br />
<br />
*Homepage: http://code.google.com/p/archlive/<br />
*Forums: http://bbs.linuxeye.cn/forum-70-1.html<br />
*Documentation: http://code.google.com/p/archlive/w/list<br />
*Screenshots: <br />
*DistroWatch Entry: <br />
<br />
== CDN Linux ==<br />
<br />
CDN Linux is a system based on Arch GNU/Linux. CDN is designed to servers and routers. It is developed by Polish Freesco Group.<br />
<br />
*Homepage: http://cdn.freesco.pl<br />
*Forums: http://forum.freesco.pl<br />
*Documentation: http://cdn.freesco.pl<br />
*Screenshots: http://cdn.freesco.pl<br />
*DistroWatch Entry: <br />
<br />
== Chakra ==<br />
<br />
"''Our goal with Chakra is to provide an operating system for desktops that is easy to use, but still has all the functionality, clarity, power and speediness of a KISS operating system. In the long term, we want to build an operating system based on Arch Linux that meets most requirements desktop users have today, like easy installation of software, graphical system administration, configuring power management on mobile devices, or sharing an internet connection.''"<br><br />
:<small>Source: [http://chakra-project.org/about.html The Chakra Project - About]</small><br />
<br />
The creators of the [[KDEmod]] project have created Chakra, based on Arch and KDEMod (of course). Tools like [http://chakra-project.org/tools-shaman.html Shaman] and [http://chakra-project.org/tools-arxin.html Arxin] show the gradual shift towards a more graphical UI oriented Arch derivative. Nonetheless, the project maintains the KISS principle of Arch, even though the [http://chakra-project.org/tools-tribe.html Tribe installer] on the Live CD provides more of the 'you don't have to know what's inside' philosophy. The installed system however is a pure Arch Linux + KDE4 + Shaman, with some artistic touches.<br />
<br />
*Homepage: http://chakra-project.org/<br />
*Forums: http://chakra-project.org/bbs/<br />
*Documentation: http://chakra-project.org/wiki/index.php/Main_Page<br />
*Screenshots: http://chakra-project.org/about-screenshots.html<br />
*DistroWatch Entry: http://distrowatch.com/table.php?distribution=chakra<br />
<br />
== ConnochaetOS ==<br />
<br />
"''ConnochaetOS will be a free operating system for the desktop with old computers in mind but with modern software. ConnochaetOS will contain only free software, according to the GNU Guidelines for Free System Distributions, follow the KISS principle (Keep it small and simple), need as few resources as possible, be modern, but stable. We aim for minimal hardware requirements, as low as a Pentium I processor and 64 MB RAM for a graphical desktop. We decided to base ConnochaetOS on Arch Linux, but completely rebuild, since we want to support i586, and replace some packages with our own ones, because of footprint, stability or freedom.''"<br><br />
:<small>Source: [http://www.connochaetos.org/wiki/doku.php?id=connochaetos ConnochaetOS Website]</small><br />
<br />
*Homepage: http://www.connochaetos.org<br />
*Forums: http://www.connochaetos.org/forum<br />
*Documentation: http://www.connochaetos.org/wiki/doku.php?id=mainpage<br />
*Screenshots: http://www.connochaetos.org/wiki/doku.php?id=screenshots<br />
*DistroWatch Entry: http://distrowatch.com/table.php?distribution=connochaet<br />
<br />
== CTKArch (formerly CTKArchLive) ==<br />
A lightweight Arch-based liveCD using c²DE (openbox) that includes English and French locales.<br />
*Homepage: http://ctkarch.org/<br />
*Forums: http://ctkarch.org/forum/<br />
*Documentation: http://ctkarch.org/documentation/ <br />
*Screenshots: http://ctkarch.org/download/<br />
*DistroWatch Entry: http://distrowatch.com/table.php?distribution=ctkarch<br />
<br />
== Elegance ==<br />
<br />
Elegance is a Arch Linux spin-off that is heavily influenced by ArchBang[http://wiki.archlinux.org/index.php/ArchBang]. It comes with a small number of programs to start you off on building your own custom desktop.<br />
*Homepage: http://k2z.com<br />
*Forums: <br />
*Documentation:<br />
*Screenshots: <br />
*DistroWatch Entry:<br />
<br />
== Kahel OS ==<br />
<br />
''"Kahel OS is the first and remains to be the only Filipino Linux Distro with the rolling release model on Arch Linux + GNOME. In the community, it is the first to release (non-beta) such Linux OS on Arch Linux + GNOME."''<br><br />
:<small>Source: [http://www.kahelos.org/ Kahel OS]</small><br />
*Homepage: http://www.kahelos.org/<br />
*Forums: http://http://forum.kahelos.org/<br />
*Documentation: http://wiki.kahelos.org/index.php?title=Main_Page<br />
*Screenshots: http://www.kahelos.org/gallery.php<br />
*DistroWatch Entry: http://distrowatch.com/table.php?distribution=kahelos<br />
<br />
== LinHES ==<br />
<br />
LinHES ('''Lin'''ux '''H'''ome '''E'''ntertainment '''S'''ystem) is a distro based heavily on Arch and centered around [http://mythtv.org MythTV], with the expressed goal of being a HES-appliance. Utilizing open source software and off the shelf hardware, you'll be able to assemble a box that can serve as a PVR, Jukebox, Image Viewer, and Game Station. Users can go from a blank hard drive to fully functional MythTV system in literally 15-20 min. For more information, please see the [[LinHES]] wikipage.<br />
<br />
*Homepage: http://www.linhes.org/<br />
*Forums: http://www.linhes.org/phpBB2<br />
*Documentation: http://mysettopbox.tv/pamphlet.html<br />
*Screenshots: http://www.thecodingstudio.com/opensource/linux/screenshots/index.php?linux_distribution_sm=<br />
*DistroWatch Entry: http://distrowatch.com/table.php?distribution=knoppmyth<br />
<br />
== live.linuX-gamers.net ==<br />
<br />
The linuX-gamers Live DVD is a bootable medium with a collection of popular 3D games. It contains both the NVIDIA and ATI proprietary Linux drivers and includes the following games: BzFLag, Enemy Territory, Glest, Nexuiz, Sauerbraten, Torcs, Tremulous, True Combat: Elite, Warsow and World of Padman. Although the live DVD is based on Arch Linux, it does not offer any desktop Linux functionality except gaming.<br />
<br />
*Homepage: http://live.linux-gamers.net/<br />
*Forums: http://github.com/svenstaro/lglive<br />
*Documentation: http://github.com/svenstaro/lglive<br />
*Screenshots: http://live.linux-gamers.net/images/shot2.png<br />
*DistroWatch Entry: http://distrowatch.com/table.php?distribution=linuxgamers<br />
<br />
== Mesk Linux ==<br />
<br />
Mesk Linux is a project aiming at showcasing Arch to Arabic-speaking users . The project is also working on localizing Arch tools and documentation .<br />
<br />
*Homepage: http://www.mesklinux.org/<br />
*Forums: http://www.mesklinux.org/<br />
*Documentation: http://www.wiki.mesklinux.org/<br />
*Screenshots: http://www.mesklinux.org/shots.php<br />
*DistroWatch Entry:<br />
<br />
== PlugApps Linux ==<br />
PlugApps Linux is a light weight distro with packages natively compiled for a Sheevaplug (ARM-optimized).<br />
*Homepage: http://plugapps.com/index.php5?title=Portal:PlugApps_Linux<br />
<br />
= Meta Distributions =<br />
<br />
== archiso ==<br />
<br />
[[archiso]] is a very simple set of bash scripts that allow for building live bootable CD/DVD/USB images based on Arch Linux. It uses a small uncomplicated code base and is actively developed. archiso is the tool used by Arch Linux to generate the official CD/USB images. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, to install disks, to special interest live systems, and who knows what else. Simply put, if it involves Arch on a shiny coaster, it can do it. <br />
<br />
*Homepage: http://projects.archlinux.org/?p=archiso.git;a=summary<br />
*Forums http://bbs.archlinux.org/viewtopic.php?id=73878<br />
*Documentation: [[archiso|wiki article on archlinux.org]]<br />
*Screenshots:<br />
*DistroWatch Entry:<br />
<br />
== Archiso-live ==<br />
<br />
Archiso-live is a fork of archiso that has since gained a fair bit of complexity in its development. Archiso-live undergoes rapid development with fresh releases posted on the dev blog found on its homepage. It uses a modular design approach based on slax. It even uses the slax initrd as a base module to get the system going. This allows archiso-live to be used in an everyday fashion since it has a full xfce desktop. It can also be greatly customized since it uses modules.<br />
<br />
*Homepage: http://godane.wordpress.com/ (GIT: http://github.com/godane/archiso-live/tree/master)<br />
*Forums: http://arch-live.2kool4u.net/forum/index.php<br />
*Documentation: http://arch-live.2kool4u.net/articles.php<br />
*Screenshots: http://arch-live.2kool4u.net/photogallery.php?album_id=1<br />
*DistroWatch Entry:<br />
<br />
== larch ==<br />
<br />
[[larch]] is a collection of scripts used to create live CD/DVD/USB-stick versions of Arch Linux. One design aim is easy customization, so that even relatively inexperienced users can build personalized live CDs, containing whatever packages they want and with their own personal configurations. The resulting medium should also be usable for installation purposes, so that one has a customized Arch Linux installation/rescue medium. As the content can be chosen freely, a comfortable working environment is possible, in contrast to the rather Spartan standard Arch installation CD.<br />
<br />
*Homepage: http://larch.berlios.de/<br />
*Forums: <br />
*Documentation: http://larch.berlios.de/doc/index.html<br />
*Screenshots:<br />
*DistroWatch Entry:<br />
<br />
= Arch Influenced Distros =<br />
<br />
==Alpine Linux==<br />
<br />
Alpine Linux is a run-from-RAM linux distribution. Its original target was small appliances like routers, VPN gateways, or embedded x86 devices. However, it supports hosting other Linux guest OSes under VServer control, making it an attractive hosting solution as well. Though Alpine Linux may not actually be based on Arch, its [http://git.alpinelinux.org/cgit/aports/tree/main/abuild/APKBUILD build system] is undoubtably inspired by Arch. [http://lists.busybox.net/pipermail/busybox/2009-January/068280.html 2][http://wiki.alpinelinux.org/w/index.php?title=Creating_an_Alpine_package&oldid=2701#depends_.26_makedepends 3]<br />
<br />
*Homepage: http://alpinelinux.org<br />
*Documentation: http://wiki.alpinelinux.org/w/index.php?title=Documentation<br />
<br />
== Enlisy ==<br />
<br />
Enlisy is an i686 optimized Linux distribution for Pentium 2 based processors and higher. It is also as simple as possible when it comes to the construction of its underlying core. Enlisy uses its own package manager Apport, which is is based on Libpysrc and Libpypac, which are inspired by Arch's package manager Pacman. Enlisy also uses InitNG for the init system.<br />
<br />
*Homepage: http://enlisy.com/<br />
*Forums: http://enlisy.com/en/forum/<br />
*Documentation: http://enlisy.org/ewiki/Documentation<br />
*Screenshots: <br />
*DistroWatch Entry:<br />
<br />
== Frugalware ==<br />
<br />
''"Frugalware Linux is a general-purpose Linux distribution designed for intermediate users who are familiar with command-line operations. It is based on Slackware, but uses a different package management system, Pacman."''<br><br />
:<small>Source: [[Wikipedia:Frugalware|Wikipedia]]</small><br />
<br />
*Homepage: http://frugalware.org<br />
*Forums: http://forums.frugalware.org<br />
*Documentation: http://frugalware.org/docs<br />
*Screenshots: http://frugalware.org/screenshots<br />
*DistroWatch Entry: http://distrowatch.com/frugalware</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=130448
E17
2011-02-11T04:16:25Z
<p>Foolishgrunt: Stable release info for EFL.</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|E17}}<br />
<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment - Enlightenment]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It comprises both the Enlightenment [[window manager]] and Enlightenment Foundation Libraries (EFL), which provide additional desktop environment features such as a toolkit, object canvas, and abstracted objects. E17 has been under development since 2005, but in February 2011 the core EFLs saw their first stable 1.0 release. Enlightenment the window manager is still in the beta stages, but is already quite usable. Many people currently use E17 as a day-to-day desktop environment without problems.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the community repository (SVN snapshots) ===<br />
<br />
{{Note|Make sure the [[community repository]] is enabled in your {{Filename|/etc/pacman.conf}}.}}<br />
<br />
To install e17:<br />
pacman -S e-svn<br />
<br />
To install additional e17 modules and applications:<br />
pacman -S e17-extra-svn<br />
<br />
You might also want to install additional [[Fonts]], see [[Fonts#Desktop environments|recommended fonts for Desktop Environments]] in particular.<br />
<br />
If you need/want an e17 package which is not (yet) available in [community], see if it is available in the [[AUR]].<br />
<br />
{{Warning|As e17 is still alpha software you are encouraged to keep packages of the previous version on your computer, allowing you to [[downgrade]] if needed.}}<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{Codeline|easy_e17.sh}} compiles E17 from source and installs it in {{Filename|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{Package AUR|easy-e17}}.<br />
# Edit {{Filename|/etc/easy_e17.conf}} if you want.<br />
# Run it as root to install E17: <pre># easy_e17.sh -i</pre><br />
# Put {{Filename|/opt/e17/bin}} in your {{Codeline|PATH}} by editing {{Filename|/etc/profile}}. For example, you can add this line at the end of the file: <pre>PATH="$PATH:/opt/e17/bin"</pre><br />
# If, after completing the install, xinitrc complains that it cannot find enlightenment upon starting, you may need to add these lines to the end of /etc/profile as well:<br />
PYTHONPATH=":$PYTHONPATH"<br />
LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/e17/lib"<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it isn't a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{Codeline|update_e17.sh}} is a zenity script which is made to accompany {{Codeline|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{Package AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
<br />
If you use {{Codeline|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{Filename|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{Codeline|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
Enlightenment's preferred network manager is [[Connman]], so the you'll want to download [http://aur.archlinux.org/packages.php?ID=25181 connman] from the [[AUR]]. You don't need to follow any of the other instructions on the [[Connman|Connman wiki page]] -- at least that's my assumption; the current build of ConnMan already includes network policy group section (although with only one statement, not three).<br />
<br />
Next, edit your {{Codeline|/etc/rc.conf}}. Remove '''network''' from your DAEMONS line. Add '''connmand''' (don't forget the '''d''') ''after'' '''dbus''' and '''hal'''.<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you've installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{Package AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog.<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{Codeline|etk_prefs}}.<br />
<br />
== FAQs ==<br />
<br />
=== What happened to Entrance ? ===<br />
<br />
{{Codeline|entrance}}, a [[Display Manager]] based on the EFLs, is no longer maintained thus packages for it have been dropped. Elsa, a new display manager is now available {{Package AUR|elsa-svn}} [[AUR]].<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{Filename|~/.e}} and remove it (e.g. {{Codeline|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream.<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Package Official|libxcursor}} package.<br />
<br />
=== Screen unlocking doesn't work ===<br />
<br />
If screenlock does not accept your password add the following to {{Filename|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-dejavu ttf-bitstream-vera<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=SLiM&diff=129370
SLiM
2011-01-30T04:29:41Z
<p>Foolishgrunt: /* Single environments */ Added Enlightenment.</p>
<hr />
<div>[[Category:Display managers (English)]]<br />
{{i18n|SLiM}}<br />
{{Article summary start}}<br />
{{Article summary text|Provides an overview of the Simple Login Manager.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Display Manager}}<br />
{{Article summary end}}<br />
[http://slim.berlios.de/ SLiM] is an acronym for Simple Login Manager. SLiM is simple, lightweight and easily configurable. SLiM is used by some because it does not require the dependencies of [[GNOME]] or [[KDE]] and can help make a lighter system for users that like to use lightweight desktops like [[Xfce]], [[Openbox]], and [[Fluxbox]].<br />
<br />
== Installation ==<br />
<br />
Install SLiM from the '''extra''' repository:<br />
<br />
# pacman -S slim<br />
<br />
== Configuration ==<br />
<br />
=== Enabling SLiM ===<br />
<br />
SLiM can be loaded on startup by entering it in your daemons array in {{Filename|rc.conf}} or by modifying {{Filename|inittab}}. See [[Display Manager]] for detailed instructions.<br />
<br />
=== Single environments ===<br />
<br />
To configure SLiM to load a particular environment, edit your {{Filename|~/.xinitrc}} to load your desktop environment:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
exec [session-command]<br />
</pre><br />
<br />
SLiM reads the local {{Filename|~/.xinitrc}} configuration and then launches the desktop according to what is in that file. If you do not have a {{Filename|~/.xinitrc}} file, you can use the skeleton file by:<br />
<br />
$ cp /etc/skel/.xinitrc ~<br />
<br />
Replace {{Codeline|[session-command]}} with the appropriate session command. Some examples of different desktop start commands:<br />
<br />
<pre><br />
exec awesome<br />
exec dwm<br />
exec fluxbox<br />
exec fvwm2<br />
exec gnome-session<br />
exec openbox-session<br />
exec startkde<br />
exec startlxde<br />
exec startxfce4<br />
exec enlightenment_start<br />
</pre><br />
<br />
If your environment is not listed here, refer to the appropriate wiki page.<br />
<br />
=== PolicyKit ===<br />
<br />
If you have problems with the PolicyKit, use ConsoleKit's {{Codeline|ck-launch-session}}:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
exec ck-launch-session [session-command]<br />
</pre><br />
<br />
=== Autologin ===<br />
<br />
To make SLiM automatically login as a specified user (without having to type a password) the following lines in /etc/slim.conf should be changed.<br />
<br />
<pre><br />
# default_user simone<br />
</pre><br />
<br />
Uncomment this line, and change "simone" to the user to be logged into automatically.<br />
<br />
<pre><br />
# auto_login no<br />
</pre><br />
<br />
Uncomment this line and change the 'no' to 'yes'. This enables the auto login feature.<br />
<br />
=== Multiple environments ===<br />
<br />
To be able to choose from multiple desktop environments, SLiM can be setup to log you into whichever you choose.<br />
<br />
Put a case statement similar to this one in your {{Filename|~/.xinitrc}} file and edit the sessions variable in {{Filename|/etc/slim.conf}} to match the names that trigger the case statement. You can choose the session at login time by pressing F1. Note that this feature is experimental.<br />
<br />
<pre><br />
# The following variable defines the session which is started if the user doesn't explicitly select a session<br />
# Source: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample<br />
<br />
DEFAULT_SESSION=twm<br />
<br />
case $1 in<br />
kde)<br />
exec startkde<br />
;;<br />
xfce4)<br />
exec startxfce4<br />
;;<br />
icewm)<br />
icewmbg &<br />
icewmtray &<br />
exec icewm<br />
;;<br />
wmaker)<br />
exec wmaker<br />
;;<br />
blackbox)<br />
exec blackbox<br />
;;<br />
*)<br />
exec $DEFAULT_SESSION<br />
;;<br />
esac<br />
</pre><br />
<br />
=== Themes ===<br />
<br />
Install the {{Package Official|slim-themes}} package:<br />
<br />
# pacman -S slim-themes archlinux-themes-slim<br />
<br />
The {{Package Official|archlinux-themes-slim}} packages contains several different themes. Look in the directory of {{Filename|/usr/share/slim/themes}} to see the themes available. Enter the theme name on the 'current_theme' line in {{Filename|/etc/slim.conf}}:<br />
<br />
#current_theme default<br />
current_theme archlinux-simplyblack<br />
<br />
To preview a theme run while an instance of the Xorg server is running by:<br />
<br />
$ slim -p /usr/share/slim/themes/<theme name><br />
<br />
To close, type "exit" in the Login line and press Enter.<br />
<br />
Additional theme packages can be found in the [[AUR]].<br />
<br />
==== Dual screen setup ====<br />
<br />
You can customize the slim theme in /usr/share/slim/themes/<your-theme>/slim.theme to turn these percents values. The box itself is 450 pixels by 250 pixels:<br />
<br />
input_panel_x 50%<br />
input_panel_y 50%<br />
<br />
into pixels values:<br />
<br />
# These settings set the "archlinux-simplyblack" panel in the center of a 1440x900 screen<br />
input_panel_x 495<br />
input_panel_y 325<br />
<br />
# These settings set the "archlinux-retro" panel in the center of a 1680x1050 screen<br />
input_panel_x 615<br />
input_panel_y 400<br />
<br />
If your theme has a background picture you should use the background_style setting ('stretch', 'tile', 'center' or 'color') to get it correctly displayed. Have a look at the [http://slim.berlios.de/themes_howto.php very simple and clear official documentation about slim themes] for further details.<br />
<br />
== Other options ==<br />
<br />
A few things you might like to try.<br />
<br />
=== Changing the cursor ===<br />
<br />
If you want to change the default X cursor to a newer design, the {{Package AUR|slim-cursor}} package is available.<br />
<br />
After installing, edit {{Filename|/etc/slim.conf}} and uncomment the line:<br />
<br />
cursor left_ptr<br />
<br />
This will give you a normal arrow instead. This setting is forwarded to {{Codeline|xsetroot -cursor_name}}. You can look up the possible cursor names [http://cvsweb.xfree86.org/cvsweb/*checkout*/xc/lib/X11/cursorfont.h?rev=HEAD&content-type=text/plain here] or in {{Filename|/usr/share/icons/<your-cursor-theme>/cursors/}}.<br />
<br />
To change the cursor theme being used at the login screen, make a file named {{Filename|/usr/share/icons/default/index.theme}} with this content:<br />
<br />
[Icon Theme]<br />
Inherits=<your-cursor-theme><br />
<br />
Replace <your-cursor-theme> with the name of the cursor theme you want to use (e.g. whiteglass).<br />
<br />
=== Match SLiM and Desktop Wallpaper ===<br />
<br />
To share a wallpaper between SLiM and your desktop, rename the used theme background, then create a link from your desktop wallpaper file to the default SLiM theme:<br />
<br />
# mv /usr/share/slim/themes/default/background.jpg{,.bck}<br />
# ln -s /path/to/mywallpaper.jpg /usr/share/slim/themes/default/background.jpg<br />
<br />
=== Shutdown, reboot, suspend, exit, launch terminal from SLiM ===<br />
<br />
You may shutdown, reboot, suspend, exit or even launch a terminal from the SLiM login screen. To do so, use the values in the username field, and the root password in the password field:<br />
<br />
* To launch a terminal, enter '''console''' as the username (defaults to xterm which must be installed separately... edit {{Filename|/etc/slim.conf}} to change terminal preference)<br />
* For shutdown, enter '''halt''' as the username<br />
* For reboot, enter '''reboot''' as the username<br />
* To exit to bash, enter '''exit''' as the username<br />
* For suspend, enter '''suspend''' as the username (suspend is disabled by default, edit {{Filename|/etc/slim.conf}} as root to uncomment the {{Filename|suspend_cmd}} line and, if necessary modify the suspend command itself (e.g. change {{Codeline|/usr/sbin/suspend}} to {{Codeline|sudo /usr/sbin/pm-suspend}}))<br />
<br />
=== SLiM init error with rc.d deamon ===<br />
<br />
If you initialize SLiM with {{Filename|/etc/rc.conf}} inside the DAEMONS array and it fails to initialize it's most likely a lock file issue. SLiM creates a lock file in {{Filename|/var/lock}} on each initialization however in most cases the lock folder in /var does not exist preventing SLiM for initliazing. Check to make sure {{Filename|/var/lock}} exists if it does not you can create it by typing the following.<br />
<br />
# mkdir /var/lock/<br />
<br />
=== Power-off error with Splashy ===<br />
<br />
If you use Splashy and SLiM, sometimes you can't power-off or reboot from menu in GNOME, Xfce, LXDE or others. Check your {{Filename|/etc/slim.conf}} and {{Filename|/etc/splash.conf}}; set the DEFAULT_TTY=7 same as xserver_arguments vt07.<br />
<br />
=== Login information with SLiM ===<br />
<br />
By default, SLiM fails to log logins to utmp and wtmp which causes who, last, etc. to misreport login information. To fix this edit your {{Filename|slim.conf}} as follows:<br />
<br />
sessionstart_cmd /usr/bin/sessreg -a -l $DISPLAY %user<br />
sessionstop_cmd /usr/bin/sessreg -d -l $DISPLAY %user<br />
<br />
=== SLiM and Gnome Keyring ===<br />
If you are using SLiM to launch a Gnome session and have trouble accessing your keyring, for example not being automatically authenticated on login, add the following lines to /etc/pam.d/slim (as discussed [http://bugs.archlinux.org/task/18637 here]).<br />
<pre><br />
auth optional pam_gnome_keyring.so<br />
session optional pam_gnome_keyring.so auto_start<br />
</pre><br />
<br />
However, this fix no longer works for Gnome 2.30. An alternate workaround is described [http://bugs.archlinux.org/task/18930 here]. Modifying the login_cmd line in /etc/slim.conf:<br />
<pre><br />
login_cmd exec ck-launch-session dbus-launch /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1<br />
</pre><br />
<br />
=== Setting DPI with SLiM ===<br />
<br />
The Xorg server generally picks up the DPI but if it doesn't you can specify it to SLiM. If you set the DPI with the argument -dpi 96 in {{Filename|/etc/X11/xinit/xserverrc}} it will not work with SLiM. To fix this change your {{Filename|slim.conf}} from:<br />
<br />
xserver_arguments -nolisten tcp vt07 <br />
<br />
to<br />
<br />
xserver_arguments -nolisten tcp vt07 -dpi 96<br />
<br />
=== Use a random theme ===<br />
<br />
Use the current_theme variable as a comma separated list to specify a set to randomly choose from.<br />
<br />
== All Slim Options ==<br />
Here is a list of all the slim configuration options and their default values.<br />
<br />
{{Note|welcome_msg allows 2 variables '''%host''' and '''%domain'''<br>sessionstart_cmd allows '''%user''' ''(execd right before login_cmd)'' and it is also allowed in sessionstop_cmd<br>login_cmd allows '''%session''' and '''%theme'''}}<br />
<br />
<br />
{| class="wikitable collapsible collapsable collapsed"<br />
|-<br />
! Option Name || Default Value<br />
|-<br />
| default_path ||<tt>/bin:/usr/bin:/usr/local/bin</tt><br />
|-<br />
| default_xserver ||<tt>/usr/bin/X</tt><br />
|-<br />
| xserver_arguments ||<tt>vt07 -auth /var/run/slim.auth</tt><br />
|-<br />
| numlock ||<br />
|-<br />
| daemon || <tt>yes</tt><br />
|-<br />
| xauth_path ||<tt>/usr/bin/xauth</tt><br />
|-<br />
| login_cmd ||<tt>exec /bin/bash -login ~/.xinitrc %session</tt><br />
|-<br />
| halt_cmd ||<tt>/sbin/shutdown -h now</tt><br />
|-<br />
| reboot_cmd ||<tt>/sbin/shutdown -r now</tt><br />
|-<br />
| suspend_cmd ||<br />
|-<br />
| sessionstart_cmd ||<br />
|-<br />
| sessionstop_cmd ||<br />
|-<br />
| console_cmd ||<tt>/usr/bin/xterm -C -fg white -bg black +sb -g %dx%d+%d+%d -fn %dx%d -T </tt><br />
|-<br />
| screenshot_cmd ||<tt>import -window root /slim.png</tt><br />
|-<br />
| welcome_msg ||<tt>Welcome to %host</tt><br />
|-<br />
| session_msg ||<tt>Session:</tt><br />
|-<br />
| default_user ||<br />
|-<br />
| focus_password ||<tt>no</tt><br />
|-<br />
| auto_login ||<tt>no</tt><br />
|-<br />
| current_theme ||<tt>default</tt><br />
|-<br />
| lockfile ||<tt>/var/run/slim.lock</tt><br />
|-<br />
| logfile ||<tt>/var/log/slim.log</tt><br />
|-<br />
| authfile ||<tt>/var/run/slim.auth</tt><br />
|-<br />
| shutdown_msg ||<tt>The system is halting...</tt><br />
|-<br />
| reboot_msg ||<tt>The system is rebooting...</tt><br />
|-<br />
| sessions ||<tt>wmaker,blackbox,icewm</tt><br />
|-<br />
| sessiondir ||<br />
|-<br />
| hidecursor ||<tt>false</tt><br />
|-<br />
| input_panel_x ||<tt>50%</tt><br />
|-<br />
| input_panel_y ||<tt>40%</tt><br />
|-<br />
| input_name_x ||<tt>200</tt><br />
|-<br />
| input_name_y ||<tt>154</tt><br />
|-<br />
| input_pass_x ||<tt>-1</tt><br />
|-<br />
| input_pass_y ||<tt>-1</tt><br />
|-<br />
| input_font ||<tt>Verdana:size=11</tt><br />
|-<br />
| input_color ||<tt>#000000</tt><br />
|-<br />
| input_cursor_height ||<tt>20</tt><br />
|-<br />
| input_maxlength_name ||<tt>20</tt><br />
|-<br />
| input_maxlength_passwd ||<tt>20</tt><br />
|-<br />
| input_shadow_xoffset ||<tt>0</tt><br />
|-<br />
| input_shadow_yoffset ||<tt>0</tt><br />
|-<br />
| input_shadow_color ||<tt>#FFFFFF</tt><br />
|-<br />
| welcome_font ||<tt>Verdana:size=14</tt><br />
|-<br />
| welcome_color ||<tt>#FFFFFF</tt><br />
|-<br />
| welcome_x ||<tt>-1</tt><br />
|-<br />
| welcome_y ||<tt>-1</tt><br />
|-<br />
| welcome_shadow_xoffset ||<tt>0</tt><br />
|-<br />
| welcome_shadow_yoffset ||<tt>0</tt><br />
|-<br />
| welcome_shadow_color ||<tt>#FFFFFF</tt><br />
|-<br />
| intro_msg ||<br />
|-<br />
| intro_font ||<tt>Verdana:size=14</tt><br />
|-<br />
| intro_color ||<tt>#FFFFFF</tt><br />
|-<br />
| intro_x ||<tt>-1</tt><br />
|-<br />
| intro_y ||<tt>-1</tt><br />
|-<br />
| background_style ||<tt>stretch</tt><br />
|-<br />
| background_color ||<tt>#CCCCCC</tt><br />
|-<br />
| username_font ||<tt>Verdana:size=12</tt><br />
|-<br />
| username_color ||<tt>#FFFFFF</tt><br />
|-<br />
| username_x ||<tt>-1</tt><br />
|-<br />
| username_y ||<tt>-1</tt><br />
|-<br />
| username_msg ||<tt>Please enter your username</tt><br />
|-<br />
| username_shadow_xoffset ||<tt>0</tt><br />
|-<br />
| username_shadow_yoffset ||<tt>0</tt><br />
|-<br />
| username_shadow_color ||<tt>#FFFFFF</tt><br />
|-<br />
| password_x ||<tt>-1</tt><br />
|-<br />
| password_y ||<tt>-1</tt><br />
|-<br />
| password_msg ||<tt>Please enter your password</tt><br />
|-<br />
| msg_color ||<tt>#FFFFFF</tt><br />
|-<br />
| msg_font ||<tt>Verdana:size=16:bold</tt><br />
|-<br />
| msg_x ||<tt>40</tt><br />
|-<br />
| msg_y ||<tt>40</tt><br />
|-<br />
| msg_shadow_xoffset ||<tt>0</tt><br />
|-<br />
| msg_shadow_yoffset ||<tt>0</tt><br />
|-<br />
| msg_shadow_color ||<tt>#FFFFFF</tt><br />
|-<br />
| session_color ||<tt>#FFFFFF</tt><br />
|-<br />
| session_font ||<tt>Verdana:size=16:bold</tt><br />
|-<br />
| session_x ||<tt>50%</tt><br />
|-<br />
| session_y ||<tt>90%</tt><br />
|-<br />
| session_shadow_xoffset ||<tt>0</tt><br />
|-<br />
| session_shadow_yoffset ||<tt>0</tt><br />
|-<br />
| session_shadow_color ||<tt>#FFFFFF</tt><br />
|}<br />
<br />
== Resources ==<br />
<br />
* [http://slim.berlios.de/ SLiM homepage]<br />
* [http://slim.berlios.de/manual.php SLiM documentation]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Qingy&diff=129127
Qingy
2011-01-27T02:33:58Z
<p>Foolishgrunt: /* ConsoleKit locks tty */ Specified rc.local directory.</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:Display managers (English)]]<br />
[[Category:Eye candy (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|Qingy}}<br />
[http://qingy.sourceforge.net/ Qingy] is a replacement for getty and login-managers like slim, kdm gdm and so on, using [http://www.directfb.org DirectFB] to provide a fast, nice GUI without the overhead of the X Window System. It allows users to log in and start the session of their choice (text console, gnome, kde, wmaker, etc.). Running several X sessions is also possible.<br />
<br />
==How to get qingy?==<br />
First you need a working DirectFB.<br />
I'm recommending [http://wiki.archlinux.org/index.php/Uvesafb Uvesafb] but if you have some graphical issues with it use vesafb. Qingy may not work with [[KMS]].<br />
<br />
A package is available in the [community] repo. To install:<br />
# pacman -S qingy <br />
<br />
Several extra themes are also available. In [community] repo, there is an Arch specific theme:<br />
# pacman -S qingy-theme-arch<br />
<br />
A package of several various themes is available in AUR:<br />
<br />
*[http://aur.archlinux.org/packages.php?do_Details=1&ID=5501 qingy-themes]<br />
<br />
==Replace *getty with qingy==<br />
To use qingy, you'll need to edit /etc/inittab.<br />
<br />
Replace:<br />
c1:2345:respawn:/sbin/agetty -8 38400 vc/1 linux<br />
c2:2345:respawn:/sbin/agetty -8 38400 vc/2 linux<br />
c3:2345:respawn:/sbin/agetty -8 38400 vc/3 linux<br />
c4:2345:respawn:/sbin/agetty -8 38400 vc/4 linux<br />
c5:2345:respawn:/sbin/agetty -8 38400 vc/5 linux<br />
c6:2345:respawn:/sbin/agetty -8 38400 vc/6 linux<br />
<br />
with:<br />
c1:2345:respawn:/sbin/qingy tty1<br />
c2:2345:respawn:/sbin/qingy tty2<br />
c3:2345:respawn:/sbin/qingy tty3<br />
c4:2345:respawn:/sbin/qingy tty4<br />
c5:2345:respawn:/sbin/qingy tty5<br />
c6:2345:respawn:/sbin/agetty -8 38400 vc/6 linux<br />
<br />
Qingy's author suggest to keep agetty on a console (here on console 6) as a safety measure as qingy is still beta software.<br />
<br />
Because qingy uses tty0-9 insead of vc/1-6 so you need add tty to /etc/securetty (NOTE : this should no longer be necessary since vc/1-6 have been replaced by tty0-9 with the new version of agetty): <br />
#<br />
# /etc/securetty<br />
#<br />
console<br />
vc/1<br />
vc/2<br />
vc/3<br />
vc/4<br />
vc/5<br />
vc/6<br />
tty0<br />
tty1<br />
tty2<br />
tty3<br />
tty4<br />
tty5<br />
tty6<br />
tty7<br />
<br />
==Configuring qingy==<br />
<br />
You can configure qingy by editing /etc/qingy/settings.<br />
<br />
The default settings for X are fine so only edit them if you really know what you are doing.<br />
# Full path to the X server<br />
#x_server = "/usr/bin/Xorg"<br />
# Full path to the 'xinit' executable<br />
xinit = "/usr/bin/xinit"<br />
# Parameter we should pass to the X server<br />
x_args = "-nolisten tcp -br"<br />
<br />
I recommend to set <br />
log_facilities = console, file<br />
so you can look for errors in /var/log/qingy.log, too.<br />
<br />
All other options are well explained.<br />
<br />
You may need to set the path to the X server e.g.<br />
# Full path to the X server<br />
x_server = "/usr/bin/X"<br />
<br />
==Starting X==<br />
<br />
Please do note that .xinitrc is different from .xsession. The default login script, .xinitrc, works with startx, but graphical login managers generally do not look for .xinitrc. Instead, they look for a file named .xsession in your home directory.<br />
<br />
If you want to start X with qingy you need to edit your .xsession.<br />
<br />
Here a default .xsession for qingy.<br />
#!/bin/sh<br />
exec <login-shell command> <window manager starter><br />
An example:<br />
#!/bin/sh<br />
exec bash --login -c 'openbox-session'<br />
<br />
The start of the window manager using a login shell is needed because qingy starts the X-session directly without the help of a shell.<br />
This causes issues like no umlauts in xterm and malfunction of control keys like "Home", "End", "Del" and so on in the terminal.<br />
<br />
For more details, visit the Ubuntu CustomXSession wiki at [https://wiki.ubuntu.com/CustomXSession]<br />
<br />
==Adding a session entry==<br />
<br />
If you've changed the variable x_sessions or text_session in the config file of qingy replace the following paths with the path you've set.<br />
<br />
===Text mode session===<br />
<br />
Create a file /etc/qingy/sessions/<sessionname>.<br />
<br />
The file name is shown as entry in the session list.<br />
<br />
The file should be a shell script. For an example have a look into /etc/qingy/sessions/emacs.<br />
<br />
===X mode session===<br />
<br />
Create the folder /etc/X11/Sessions/ and save a new script file into it. (see Text mode session)<br />
<br />
The name of the file is shown in the session list.<br />
<br />
==Troubleshooting==<br />
<br />
=== Synaptic touchpad and keyboard issue ===<br />
<br />
Qingy (and quite possibly other DirectFB applicationss) has some issues using Synaptics touchpad. Also the keyboard can behave strangely (like if each keys were pressed twice).<br />
<br />
This can be solved by adding:<br />
disable-module=linux_input<br />
to /etc/directfbrc. If the file does not exist, create it. This will enable you to use your touchpad, however some extra functionality like tapping or tap-dragging might not work.<br />
<br />
=== ConsoleKit locks tty ===<br />
<br />
If you use ck-launch-session to start your session, then console-kit-daemon will lock currently active tty on it's first start. This is especially nasty if you use x_server_tty=qingy_tty parameter: tty you've logged in first becomes disposable.<br />
<br />
There is a bug about this behavior [https://bugs.freedesktop.org/show_bug.cgi?id=29920] and a workaround: start console-kit-daemon on some useless tty, i.e. 63 by adding this to /etc/rc.local:<br />
<br />
openvt -c 63 -f -- console-kit-daemon --no-daemon &</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=128624
E17
2011-01-20T22:26:01Z
<p>Foolishgrunt: Acknowledging beta status.</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|E17}}<br />
<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment - Enlightenment]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It is currently under heavy development, but it recently reached the beta stage and is already quite stable. Many people use it as a day-to-day environment.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the community repository (SVN snapshots) ===<br />
<br />
{{Note|Make sure the [[community repository]] is enabled in your {{Filename|/etc/pacman.conf}}.}}<br />
<br />
To install e17:<br />
pacman -S e-svn<br />
<br />
To install additional e17 modules and applications:<br />
pacman -S e17-extra-svn<br />
<br />
You might also want to install additional [[Fonts]], see [[Fonts#Desktop environments|recommended fonts for Desktop Environments]] in particular.<br />
<br />
If you need/want an e17 package which is not (yet) available in [community], see if it is available in the [[AUR]].<br />
<br />
{{Warning|As e17 is still alpha software you are encouraged to keep packages of the previous version on your computer, allowing you to [[downgrade]] if needed.}}<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{Codeline|easy_e17.sh}} compiles E17 from source and installs it in {{Filename|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{Package AUR|easy-e17}}.<br />
# Edit {{Filename|/etc/easy_e17.conf}} if you want.<br />
# Run it as root to install E17: <pre># easy_e17.sh -i</pre><br />
# Put {{Filename|/opt/e17/bin}} in your {{Codeline|PATH}} by editing {{Filename|/etc/profile}}. For example, you can add this line at the end of the file: <pre>PATH="$PATH:/opt/e17/bin"</pre><br />
# If, after completing the install, xinitrc complains that it cannot find enlightenment upon starting, you may need to add these lines to the end of /etc/profile as well:<br />
PYTHONPATH=":$PYTHONPATH"<br />
LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/e17/lib"<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it isn't a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{Codeline|update_e17.sh}} is a zenity script which is made to accompany {{Codeline|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{Package AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
<br />
If you use {{Codeline|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{Filename|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{Codeline|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
Enlightenment's preferred network manager is [[Connman]], so the you'll want to download [http://aur.archlinux.org/packages.php?ID=25181 connman] from the [[AUR]]. You don't need to follow any of the other instructions on the [[Connman|Connman wiki page]] -- at least that's my assumption; the current build of ConnMan already includes network policy group section (although with only one statement, not three).<br />
<br />
Next, edit your {{Codeline|/etc/rc.conf}}. Remove '''network''' from your DAEMONS line. Add '''connmand''' (don't forget the '''d''') ''after'' '''dbus''' and '''hal'''.<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you've installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{Package AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog.<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{Codeline|etk_prefs}}.<br />
<br />
== FAQs ==<br />
<br />
=== What happened to Entrance ? ===<br />
<br />
{{Codeline|entrance}}, a [[Display Manager]] based on the EFLs, is no longer maintained thus packages for it have been dropped.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{Filename|~/.e}} and remove it (e.g. {{Codeline|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream.<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Package Official|libxcursor}} package.<br />
<br />
=== Screen unlocking doesn't work ===<br />
<br />
If screenlock does not accept your password add the following to {{Filename|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Arch_compared_to_other_distributions&diff=128022
Arch compared to other distributions
2011-01-13T19:26:52Z
<p>Foolishgrunt: /* The *BSDs */</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:FAQs (English)]]<br />
{{i18n|Arch Compared to Other Distributions}}<br />
{{Article summary start}}<br />
{{Article summary text|A brief comparison of Arch Linux with other popular GNU/Linux distributions and BSDs.}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|Arch Linux}}<br />
{{Article summary wiki|The Arch Way}}<br />
{{Article summary heading|External links}}<br />
{{Article summary link|DistroWatch.com|http://distrowatch.com/}}<br />
{{Article summary end}}<br />
<br />
This page attempts to draw a comparison between Arch Linux and other popular GNU/Linux distributions and <tt>UNIX</tt>-like operating systems. The summaries that follow are brief descriptions that may help a person decide if Arch Linux will suit their needs. Although reviews and descriptions can be useful, first-hand experience is invariably the best way to compare distributions.<br />
<br />
== Source-based ==<br />
<br />
Source-based distros are highly portable, giving the advantage of controlling and compiling the entire OS and applications for a particular machine architecture and usage scheme, with the disadvantage of the time-consuming nature of source compilation. The Arch base and all packages are compiled for i686 and x86-64 architectures, offering a potential performance boost over i386/i486/i586 binary distros, with the added advantage of expedient installation.<br />
<br />
=== Gentoo Linux ===<br />
<br />
Both Arch Linux and Gentoo Linux are rolling release systems, making packages available to the distribution a short time after they are released upstream. The Gentoo packages and base system are built directly from source code according to user-specified 'USE flags'. Arch provides a ports-like system for building packages from source, though the Arch base system is designed to be installed as pre-built i686/x86_64 binary. This generally makes Arch quicker to build and update, and allows Gentoo to be more systemically customizable. Arch supports i686 and x86_64 while Gentoo officially supports x86, ppc, sparc, alpha, amd64, arm, mips, hppa, s390, sh, and itanium architectures. Because both the Gentoo and Arch installations only include a base system, both are considered to be highly customizable. Gentoo users will generally feel quite comfortable with most aspects of Arch.<br />
<br />
=== Sorcerer/Lunar-Linux/Source Mage ===<br />
<br />
Sorcerer/Lunar-Linux/Source Mage (SLS) are all source-based distros originally related to one another. SLS distros use a rather simple set of script files to create package descriptions, and use a global configuration file to configure the compilation process, much like the [[Arch Build System]]. The SLS tools do full dependency checking, including handling optional features, package tracking, removal and upgrading. There are no binary packages for any of the SLS family, although they all provide the ability to roll back to earlier installed packages easily.<br />
<br />
The installation process involves configuring a simple base system from the shell and ncurses menus, then optionally recompiling the base system afterward. Like Arch, there is no default WM/DE/DM, and Xorg is not included in the base installation. Several X server alternatives are available (X.Org 6.8 or 7, XFree86).<br />
<br />
SLS has a very complicated history. Perhaps the best write-up about it can be found at [http://wiki.sourcemage.org/SourceMage/History the SourceMage wiki].<br />
<br />
== Minimalist ==<br />
<br />
The minimalist distros are quite comparable to Arch, sharing several similarities. All are considered 'simple' from a technical standpoint.<br />
<br />
=== LFS ===<br />
<br />
LFS, (or Linux From Scratch) exists simply as documentation. The book instructs the user on how to obtain the minimal base package set for a functional GNU/Linux system, and how to manually compile, patch and configure it from scratch. LFS is as minimal as it gets, and offers an excellent and educational process of building and customizing a base system. Arch provides these very same packages, plus a BSD-style init, a few extra tools and the powerful [[pacman]] package manager as its base system, already compiled for i686/x86-64. LFS provides no online repositories; sources are manually obtained, compiled and installed with '''make'''. (Several manual methods of package management exist, and are mentioned in LFS Hints) Along with the minimal Arch base system, the Arch community and developers provide and maintain many thousands of binary packages installable via pacman as well as [[PKGBUILD]] build scripts for use with the [[Arch Build System]]. Arch also includes the [[makepkg]] tool for expediently building or customizing {{Filename|.pkg.tar.xz}} packages, readily installable by pacman. Judd Vinet built Arch from scratch, and then wrote pacman in C. Historically, Arch was sometimes humorously described simply as "Linux, with a nice package manager."<br />
<br />
=== CRUX ===<br />
<br />
Arch is independently developed, was built from scratch and is not based on any other GNU/Linux distribution. Before creating Arch, Judd Vinet admired and used CRUX; a minimalist distro created by Per Lidén. Originally inspired by ideas in common with CRUX, Arch was built from scratch, and [[pacman]] was then coded in C. The two share some guiding principles: for instance, both are architecture-optimized, minimalist and K.I.S.S.-oriented. Both ship with ports-like systems, use *BSD-style init systems and, like *BSD, both provide a minimal base environment to build upon. Arch features pacman, which handles binary system package management and works seamlessly with the [[Arch Build System]]. CRUX uses a community contributed system called prt-get, which, in combination with its own ports system, handles dependency resolution, but builds all packages from source (though the CRUX base installation is i686 binary). Arch officially supports x86-64 and i686, whereas CRUX is i686-only.<br />
<br />
Arch uses a rolling-release system and features a large array of binary package repositories as well as the [[Arch User Repository]]. CRUX provides a more slimmed-down officially supported ports system in addition to a modest community repository.<br />
<br />
=== Slackware ===<br />
<br />
Slackware and Arch are quite similar in that both are simple distributions focused on elegance and minimalism. Slackware is famous for its lack of branding and completely vanilla packages, from the kernel up. Arch typically applies patching only to avoid severe breakage or to ensure packages will compile cleanly. Both use BSD-style init scripts. Arch supplies a package management system in [[pacman]] which, unlike Slackware's standard tools, offers automatic dependency resolution and allows for more automated system upgrades. Slackware users typically prefer their method of manual dependency resolution, citing the level of system control it grants them, as well as Slackware's excellent supply of pre-installed libraries and dependencies. Arch is a rolling-release system. Slackware is seen as more conservative in its release cycle, preferring proven stable packages. Arch is more 'bleeding-edge' in this respect. Arch Linux provides many thousands of binary packages within its official repositories whereas Slackware official repositories are more modest. Arch offers the [[Arch Build System]], an actual ports-like system and also the [[AUR]], a very large collection of PKGBUILDs contributed by users. Slackware offers a similar, though slimmer system at [http://www.slackbuilds.org slackbuilds.org] which is a semi-official repository of Slackbuilds, which are analogous to Arch PKGBUILDs. Slackware users will generally be quite comfortable with most aspects of Arch.<br />
<br />
== Graphical ==<br />
<br />
Sometimes called "newbie" distros, the graphical distros share a lot of similarities, though Arch is quite different from them. Arch may be a better choice if you want to learn about GNU/Linux by building up from a very minimal base, as an installation of Arch installs very few packages in comparison. Graphical distros tend to ship with GUI installers (like Fedora's Anaconda) and GUI system-configuration tools (like SUSE's YaST). Specific differences between distros are described below.<br />
<br />
=== Ubuntu ===<br />
<br />
Ubuntu is an immensely popular Debian-based distro commercially sponsored by Canonical Ltd., while Arch is an independently developed system built from scratch. Both projects have very different goals and are targeted at a different user base. Arch is designed for users who desire a do-it-yourself approach, whereas Ubuntu provides an autoconfigured system which is meant to be more of a distribution for 'all'. If you want to get up and running quickly and not fiddle around with the guts of the system as much, Ubuntu is better suited. Arch is presented as a much more minimalist design from the base installation onward, relying heavily on the user to customize it to their own specific needs. In general, developers and tinkerers will probably like Arch better than Ubuntu, though many Arch users have started on Ubuntu and eventually migrated to Arch. Ubuntu moves between discrete releases every 6 months, whereas Arch is a rolling-release system. Arch offers a ports-like package build system, the [[Arch Build System]], while Ubuntu does not. The two communities differ in some ways as well. The Arch community is much smaller and is strongly encouraged to be proactive; a large percentage contribute to the distro. In contrast, the Ubuntu community is relatively large and can therefore tolerate a much larger percentage of users who do not actively contribute to development, packaging, or repository maintenance.<br />
<br />
=== Fedora ===<br />
<br />
Fedora is a spin-off from the Red Hat distribution and has continually been one of the most popular distributions to date. It is often presented as a bleeding edge testbed release system, and many Fedora packages and projects eventually migrate to RHEL and become adopted by other distributions. Arch too is considered relatively bleeding edge, although it is a rolling-release and does not serve as a testing branch for another distribution. Fedora boasts a massive community, lots of pre-built packages and excellent support. Fedora packages are RPMs, using YUM as its package manager. Arch uses [[pacman]] to manage simple tarball packages. Fedora famously refuses to support the MP3 media format due to perceived patent issues. Arch is more lenient in its disposition toward MP3 and other media. Fedora offers both a graphical and a text installer. Arch does not offer a graphical installer, but rather, uses an ncurses-based installer, relying more on the user for manual configuration. Fedora has a scheduled release cycle. Arch is a rolling-release system. The Arch design approach is geared more toward lightweight elegance and minimalism rather than automation/auto-configuration. Fedora does innovate and has earned much community recognition for integration of SELinux, GCJ compiled packages to remove the need for Sun's JRE, and the pioneering of many other free software projects. Fedora supports neither JFS nor ReiserFS out of the box whereas Arch does.<br />
<br />
=== Mandriva ===<br />
<br />
Mandriva Linux (formerly Mandrake Linux) was created in 1998 with the goal of making GNU/Linux easy to use for everyone. It is RPM-based and uses the urpmi package manager. Again, Arch takes a simpler approach, being text-based and relying on more manual configuration and is aimed at intermediate to advanced users.<br />
<br />
=== openSUSE ===<br />
<br />
openSUSE is centered around the RPM package format and its well-regarded YaST2 gui-driven configuration tool, which is a one-stop shop for most users' system configuration needs, including package management. Arch does not offer such a facility as it goes against [[The Arch Way]]. openSUSE, therefore, is widely regarded as more appropriate for less-experienced users, or those who want a more GUI-driven environment, auto-configuration and expected functionality out of the box.<br />
<br />
=== PCLinuxOS ===<br />
<br />
PCLinuxOS is a popular Mandriva-based distro providing a complete DE, designed for user-friendliness and is described as "simple", though its definition of simple is quite different than the Arch definition. Arch is designed as a simple base system to be customized from the ground up and is aimed more toward advanced users. PCLOS uses the apt package manager as a wrapper for RPM packages. Arch uses its own independently-developed [[pacman]] package manager with {{Filename|.pkg.tar.xz}} packages. PCLOS is very GUI-driven, provides GUI hardware configuration tools and the Synaptic package management front-end, and claims to have little or no reliance on the shell. Arch is command-line oriented and designed for more simple approaches to system configuration, management and maintenance. PCLOS recommends 256MB RAM as part of its minimum system requirements. Being more lightweight, Arch can run on systems with much less system memory, requiring only 64MB of RAM for a base i686 install, and will run flawlessly on more modern systems.<br />
<br />
== The *BSDs ==<br />
<br />
<nowiki>*</nowiki>BSDs share a common origin and descend directly from the work done at UC Berkeley to produce a freely redistributable, free of cost, <tt>UNIX</tt> system. They are not GNU/Linux distributions, but rather, <tt>UNIX</tt>-like operating systems. Therefore, although Arch and the *BSDs share the concept of a tightly-integrated base and ports system, along with a similar init framework, they are absolutely not related from a code standpoint. *BSDs were derived from the original AT&T <tt>UNIX</tt> code and have a true <tt>UNIX</tt> heritage. To learn more about the *BSD variants visit the vendor's site.<br />
<br />
=== FreeBSD ===<br />
<br />
Both Arch and [http://www.freebsd.org/about.html FreeBSD] offer software which can be obtained using binaries or compiled using 'ports' systems. Both share a very similar init system. Like other *BSDs, the FreeBSD base is developed fundamentally as a system designed as a whole, with each application 'ported' over to FreeBSD and made sure to work in the process. In contrast, GNU/Linux distributions such as Arch exist as amalgams combined from many separate sources. Both Arch and FreeBSD use {{Filename|/etc/rc.conf}} as a major configuration file. The FreeBSD license is generally more protective of the ''coder'', compared to the GPL, which in contrast favors protection of the ''code'' itself. Arch is released under the GPL. In FreeBSD, like Arch, decisions are delegated to you, the power user. This may be the most interesting comparison to Arch since it goes head-to-head in package modernity and has a somewhat sizable, smart, active, no-nonsense community. Both systems share many similarities and FreeBSD users will generally feel quite comfortable with most aspects of Arch.<br />
<br />
=== NetBSD ===<br />
<br />
NetBSD is a free, secure, and highly portable <tt>UNIX</tt>-like open-source operating system available for over 50 platforms, from 64-bit Opteron machines and desktop systems to hand-held and embedded devices. Its clean design and advanced features make it excellent in both production and research environments, and it is user-supported with complete source. Many applications are easily available through pkgsrc, the NetBSD Packages Collection. Arch may not operate on the vast number of devices NetBSD operates on, but for an i686 system it may offer more applications. Also, the default installation method in pkgsrc is to pull and compile sources whereas Arch offers binary packages. Arch does share similarities with NetBSD; both use {{Filename|/etc/rc.conf}} as the primary configuration file, both require manual configuration, they are minimalist and lightweight, both offer ports systems as well as binaries and both have active, no-nonsense developers and communities. Arch also borrows from *BSD for its init system concepts.<br />
<br />
=== OpenBSD ===<br />
<br />
The OpenBSD project produces a free, multi-platform 4.4BSD-based <tt>UNIX</tt>-like operating system. Efforts focus on portability, standardization, code correctness, proactive security, and integrated cryptography. In contrast, Arch focuses more on simplicity, elegance, minimalism and bleeding edge software. OpenBSD supports binary emulation of most programs from SVR4 (Solaris), FreeBSD, GNU/Linux, BSD/OS, SunOS and HP-UX. OpenBSD is self-described as 'perhaps the #1 security OS'.<br />
<br />
In common with Arch, OpenBSD offers a small, elegant, base install and uses a ports system and packaging systems to allow for easy installation and management of programs which are not part of the base operating system. In contrast to a GNU/Linux system like Arch, but in common with most other BSD-based operating systems, the OpenBSD kernel and userland programs, such as the shell and common tools (like ls, cp, cat and ps), are developed together in a single source repository.<br />
<br />
== Other ==<br />
<br />
These OS's fall into the 'other' category.<br />
<br />
=== Debian GNU/Linux ===<br />
<br />
Debian is a much larger project and community and features stable, testing, and unstable branches, offering over 20,000 binary packages. Arch does not 'split' their packages into "-dev" and "-common" as Debian does, therefore, Arch repositories will seem much smaller. Debian has a more vehement stance on free software. Arch is more lenient when it comes to 'non-free' packages as defined by GNU. Debian's design approach focuses more on stability and stringent testing. Arch is focused more on the philosophy of simplicity, minimalism, and offering bleeding edge software. Arch packages are more current than Debian Stable and Testing, typically being about equal with Debian unstable. Both Debian and Arch offer well-regarded package management systems. Arch is a rolling release, whereas Debian Stable is released with "frozen" packages. Debian is available for many architectures, including alpha, arm, hppa, i386, x86_64, ia64, m68k, mips, mipsel, powerpc, s390, and sparc, whereas Arch is i686 and x86_64 only. Arch provides more expedient support for building custom, installable packages from outside sources, with a ports-like package build system. Debian does not offer a ports system, relying instead on its huge binary repositories. The Arch installation system only offers a minimal base, transparently exposed during system configuration, whereas Debian's methods offer a more automatically configured approach as well as several alternative methods of installation. Debian utilizes the SysVinit, whereas Arch uses a simpler *BSD-style init. Arch keeps patching to a minimum, thus avoiding problems that upstream are unable to review.<br />
<br />
=== Frugalware ===<br />
<br />
Arch is text-based and command-line oriented. Frugalware has adopted Arch's [[pacman]] as its package manager, but uses bzipped tarballs. In contrast, Arch uses xz compressed (lzma) tarballs, for the purpose of expedience of installation. Frugalware doesn't support the JFS filesystem by default. Frugalware is no longer based on Slackware but is rather a distro of its own, and is promoted as an i686 distro. Arch is a fundamentally different system, being installed as a minimal base environment and expanded with pacman according to the user's choices and needs. Frugalware is installed from a DVD, with default software choices and desktop environment chosen for the user already. Frugalware has a scheduled release cycle. Again, Arch is more focused on simplicity, minimalism, code-correctness and bleeding edge packages within a rolling-release model.</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=AbiWord&diff=127654
AbiWord
2011-01-11T16:29:56Z
<p>Foolishgrunt: /* Installation */ ttf-ms-fonts is no longer in repos.</p>
<hr />
<div>[[Category:Office (English)]]<br />
{{i18n|Abiword}}<br />
{{stub}}<br />
<br />
== Introduction ==<br />
'''Abiword''' is a word processor that provides a lighter alternative for [[OpenOffice]] Writer, while at the same time providing great functionality. Abiword supports many standard document types, such as OpenOffice.org documents, Microsoft Word documents, WordPerfect documents, Rich Text Format documents and HTML web pages.<br />
<br />
== Installation ==<br />
Before you install, you'll want to install dictionaries if you want spell check.<br />
# pacman -S aspell-en<br />
<br />
To install, run:<br />
# pacman -S abiword<br />
<br />
For additional plugins:<br />
# pacman -S abiword-plugins<br />
<br />
To fix tiny cursor and misaligned text issues, install [https://aur.archlinux.org/packages.php?ID=13030 ttf-ms-fonts] from [[AUR]] and:<br />
# pacman -S ttf-freefont<br />
<br />
== Fix for Print dialog crash ==<br />
{{Note|This bug has been reported as non-existent for version 2.8.1 or higher. However, this section will remain for legacy versions or if it crops up again,}}<br />
For some reason, the current versions of Abiword and libgnomeprint are not playing nice together. The .abw default template causes the program to crash when the user attempts to print. The solution is to force abiword to work with the .rtf format instead. By following the steps below, you will set the default save format to .rtf and trick Abiword into using a .rtf file as its default template.<br />
<br />
Open {{Filename|~/.AbiSuite/AbiWord.Profile}} and insert the following line into the second <scheme> section.<br />
DefaultSaveFormat=".rtf"<br />
It should look similar to the following<br />
<Scheme<br />
name="_custom_"<br />
ZoomPercentage="64"<br />
DefaultSaveFormat=".rtf"<br />
/><br />
It is then neccessary to change the default template. You must follow these steps exactly.<br />
<br />
1) open Abiword and save a blank document titled {{Filename|normal.rtf}} in {{Filename|~/.AbiSuite/templates/}}. If the directory does not exist, create it.<br />
<br />
2) Rename the file to {{Filename|normal.awt}} <br />
<br />
Do not just save a blank .awt file!! You must trick Abiword into using a .rtf template in order for this to work.<br />
<br />
As soon as the conflict between Abiword and libgnomeprint is resovled, these instructions will no longer be neccessary and should be removed.<br />
<br />
== Change Keybindings ==<br />
See [http://www.abisource.com/wiki/Keyboard_bindings this wiki post] on how to change the default key bindings in Abiword.<br />
<br />
== LaTeX Fonts ==<br />
The package "abiword-plugins" comes with a function which allows user to insert LaTeX codes in a document. To display mathematics symbols properly, one needs to download [http://movementarian.org/latex-xft-fonts-0.1.tar.gz latex-xft-fonts] and save it to the directory {{Filename|/usr/share/fonts}}. To install the font, unzip the file by<br />
# tar -xzf (name of the tar.gz file)<br />
and then run<br />
# fc-cache -fv<br />
<br />
== External links ==<br />
*[http://www.abisource.com/ Official homepage]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Beginners%27_guide_old&diff=127221
Beginners' guide old
2011-01-08T07:29:35Z
<p>Foolishgrunt: /* Mirrorcheck for up-to-date packages */</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|Install from SSH}}<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-2011 by Aaron Griffin and are licensed under the [http://www.gnu.org/licenses/old-licenses/gpl-2.0.html 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. Also, be sure to check out the <code>man</code> pages for any command you are unfamiliar with; this can usually be invoked with <code>man ''command''</code>.<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 6 main components:<br />
<br />
*[[#Part I: Prepare the Installation|Part I: Prepare the Installation]]<br />
*[[#Part II: Install the Base System|Part II: Install the Base system]]<br />
*[[#Part III: Update|Part III: Update]]<br />
*[[#Part IV: Add a user|Part IV: Add a user]]<br />
*[[#Part V: Sound|Part V: Sound]]<br />
*[[#Part VI: Graphical User Interface|Part VI: Graphical User Interface]]<br />
<br />
==Part I: Prepare the Installation==<br />
<br />
{{Note|If you wish to install to another partition from within an existing GNU/Linux distro or LiveCD, please 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. The following assumes installation by conventional means.}}<br />
<br />
===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 />
<br />
<code>cd</code> to the directory where the downloaded files have been placed, and invoke <code>sha1sum</code>:<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 Over a Network====<br />
<br />
Instead of writing the boot media to a disc or USB drive, you may alternatively boot the .iso image over the network. This works well when you already have a server set up. Please see [[Install Arch from network (via PXE)|this article]] for more information, and then continue to [[#Boot Arch Linux Installer|Boot Arch Linux Installer]]<br />
<br />
====CD installer====<br />
<br />
Burn the .iso image file to a CD or DVD media with your preferred CD/DVD burner drive and software, and continue with [[#Boot Arch Linux Installer | 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 <code>dd</code> 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>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 .iso 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 />
To verify that the image was successfully written to the flash device, 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 (2010.05)]; 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 #Write .iso to drive</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 #Verify integrety</nowiki>| 4850d533ddd343b80507543536258229 -<br />
744973+0 records in<br />
744973+0 records out}}<br />
<br />
Continue with [[#Boot Arch Linux Installer | 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 [[#Boot Arch Linux Installer | Boot Arch Linux Installer]]<br />
<br />
===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. Menus vary slightly among the different ISOs.<br />
<br />
{{Note|Users seeking to preform the Arch Linux installation remotely via an ssh connection are encouraged to make a few tweaks at this point to enable ssh connections directly to the live CD environment. If interested, see the [[Install from SSH]] article.}}<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 />
where ''layout'' is 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 />
==Part II: Install the Base System==<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 />
===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. If using a Netinstall image, relative speed and update status of source repository mirrors may be checked [https://www.archlinux.de/?page=MirrorStatus here].<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 of the installation media''. These steps (or some other form of wireless management) must be repeated from the actual installed system after booting into it.<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 output 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 />
===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 />
===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 />
{{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.''<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 />
===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 />
===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 />
===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 usually fine for US English users. However if you experience any problems such as some characters not printing right and being replaced by squares you may want to go back and replace &quot;en_US.utf8&quot; with just &quot;en_US&quot;.<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 !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).<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 />
===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 />
===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 III: 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]. If you don't know how to downgrade a package or chroot into an install, don't use it.}}<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 />
<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. Tools 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 />
Since <code>rankmirrors</code> does not take into account how up-to-date a mirror's package list is, it's important to note that one or more of the mirrors it selects as fastest may still be 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. 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 />
Alternatively, the [http://www.archlinux.org/mirrorlist/ Mirrorlist Generator] can automatically rank mirrors close to your location by how up-to-date they are.<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, or check out the [[pacman rosetta]] entry for a comparison to other popular package managers.<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 IV: 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,scanner -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 />
==Part V: Sound==<br />
<!--Sound is out of the scope of the Beginners' Guide and this section will soon be replaced with a link to [[Sound]] or [[ALSA]], improve those articles rather than working on this section--><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}}. Use the {{keypress|↑}} key to increase the volume and obtain a value of zero dB gain. The gain may be found in the upper left next to the 'Item:' field. Higher values of gain will produce distorted sound.<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 of approximately 75 produces a gain of zero. 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 VI: '''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 />
<!--This whole section probably belongs elsewhere.--><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 />
<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:<br />
# 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 />
<br />
{{Note | ''Be sure to have only '''one''' uncommented '''exec''' line in ~/.xinitrc''.}}<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. See [[Display Manager]] for instructions on using a login manager or [[Start X at Boot]] for two lightweight methods that don't rely on a display manager.<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>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=Beginners%27_guide_old&diff=127220
Beginners' guide old
2011-01-08T07:28:49Z
<p>Foolishgrunt: /* Mirrorcheck for up-to-date packages */</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|Install from SSH}}<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-2011 by Aaron Griffin and are licensed under the [http://www.gnu.org/licenses/old-licenses/gpl-2.0.html 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. Also, be sure to check out the <code>man</code> pages for any command you are unfamiliar with; this can usually be invoked with <code>man ''command''</code>.<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 6 main components:<br />
<br />
*[[#Part I: Prepare the Installation|Part I: Prepare the Installation]]<br />
*[[#Part II: Install the Base System|Part II: Install the Base system]]<br />
*[[#Part III: Update|Part III: Update]]<br />
*[[#Part IV: Add a user|Part IV: Add a user]]<br />
*[[#Part V: Sound|Part V: Sound]]<br />
*[[#Part VI: Graphical User Interface|Part VI: Graphical User Interface]]<br />
<br />
==Part I: Prepare the Installation==<br />
<br />
{{Note|If you wish to install to another partition from within an existing GNU/Linux distro or LiveCD, please 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. The following assumes installation by conventional means.}}<br />
<br />
===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 />
<br />
<code>cd</code> to the directory where the downloaded files have been placed, and invoke <code>sha1sum</code>:<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 Over a Network====<br />
<br />
Instead of writing the boot media to a disc or USB drive, you may alternatively boot the .iso image over the network. This works well when you already have a server set up. Please see [[Install Arch from network (via PXE)|this article]] for more information, and then continue to [[#Boot Arch Linux Installer|Boot Arch Linux Installer]]<br />
<br />
====CD installer====<br />
<br />
Burn the .iso image file to a CD or DVD media with your preferred CD/DVD burner drive and software, and continue with [[#Boot Arch Linux Installer | 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 <code>dd</code> 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>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 .iso 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 />
To verify that the image was successfully written to the flash device, 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 (2010.05)]; 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 #Write .iso to drive</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 #Verify integrety</nowiki>| 4850d533ddd343b80507543536258229 -<br />
744973+0 records in<br />
744973+0 records out}}<br />
<br />
Continue with [[#Boot Arch Linux Installer | 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 [[#Boot Arch Linux Installer | Boot Arch Linux Installer]]<br />
<br />
===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. Menus vary slightly among the different ISOs.<br />
<br />
{{Note|Users seeking to preform the Arch Linux installation remotely via an ssh connection are encouraged to make a few tweaks at this point to enable ssh connections directly to the live CD environment. If interested, see the [[Install from SSH]] article.}}<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 />
where ''layout'' is 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 />
==Part II: Install the Base System==<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 />
===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. If using a Netinstall image, relative speed and update status of source repository mirrors may be checked [https://www.archlinux.de/?page=MirrorStatus here].<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 of the installation media''. These steps (or some other form of wireless management) must be repeated from the actual installed system after booting into it.<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 output 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 />
===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 />
===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 />
{{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.''<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 />
===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 />
===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 />
===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 usually fine for US English users. However if you experience any problems such as some characters not printing right and being replaced by squares you may want to go back and replace &quot;en_US.utf8&quot; with just &quot;en_US&quot;.<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 !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).<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 />
===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 />
===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 III: 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]. If you don't know how to downgrade a package or chroot into an install, don't use it.}}<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 />
<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. Tools 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 />
Since <code>rankmirrors</code> does not take into account how up-to-date a mirror's package list is, it's important to not that one or more of the mirrors it selects as fastest may still be 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. 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 />
Alternatively, the {http://www.archlinux.org/mirrorlist/ Mirrorlist Generator] can automatically rank mirrors close to your location by how up-to-date they are.<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, or check out the [[pacman rosetta]] entry for a comparison to other popular package managers.<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 IV: 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,scanner -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 />
==Part V: Sound==<br />
<!--Sound is out of the scope of the Beginners' Guide and this section will soon be replaced with a link to [[Sound]] or [[ALSA]], improve those articles rather than working on this section--><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}}. Use the {{keypress|↑}} key to increase the volume and obtain a value of zero dB gain. The gain may be found in the upper left next to the 'Item:' field. Higher values of gain will produce distorted sound.<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 of approximately 75 produces a gain of zero. 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 VI: '''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 />
<!--This whole section probably belongs elsewhere.--><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 />
<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:<br />
# 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 />
<br />
{{Note | ''Be sure to have only '''one''' uncommented '''exec''' line in ~/.xinitrc''.}}<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. See [[Display Manager]] for instructions on using a login manager or [[Start X at Boot]] for two lightweight methods that don't rely on a display manager.<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>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=127195
E17
2011-01-08T01:07:57Z
<p>Foolishgrunt: /* Configuring the Network */</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|E17}}<br />
<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment - Enlightenment]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It is currently under heavy development, and is in the pre-alpha stages, but is still quite stable. Many people use it as a day-to-day environment.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the community repository (SVN snapshots) ===<br />
<br />
{{Note|Make sure the [[community repository]] is enabled in your {{Filename|/etc/pacman.conf}}.}}<br />
<br />
To install e17:<br />
pacman -S e-svn<br />
<br />
To install additional e17 modules and applications:<br />
pacman -S e17-extra-svn<br />
<br />
You might also want to install additional [[Fonts]], see [[Fonts#Desktop environments|recommended fonts for Desktop Environments]] in particular.<br />
<br />
If you need/want an e17 package which is not (yet) available in [community], see if it is available in the [[AUR]].<br />
<br />
{{Warning|As e17 is still alpha software you are encouraged to keep packages of the previous version on your computer, allowing you to [[downgrade]] if needed.}}<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{Codeline|easy_e17.sh}} compiles E17 from source and installs it in {{Filename|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{Package AUR|easy-e17}}.<br />
# Edit {{Filename|/etc/easy_e17.conf}} if you want.<br />
# Run it as root to install E17: <pre># easy_e17.sh -i</pre><br />
# Put {{Filename|/opt/e17/bin}} in your {{Codeline|PATH}} by editing {{Filename|/etc/profile}}. For example, you can add this line at the end of the file: <pre>PATH="$PATH:/opt/e17/bin"</pre><br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it isn't a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{Codeline|update_e17.sh}} is a zenity script which is made to accompany {{Codeline|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{Package AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
<br />
If you use {{Codeline|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{Filename|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{Codeline|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
Enlightenment's preferred network manager is [[Connman]], so the you'll want to download [http://aur.archlinux.org/packages.php?ID=25181 connman] from the [[AUR]]. You don't need to follow any of the other instructions on the [[Connman|Connman wiki page]] -- at least that's my assumption; the current build of ConnMan already includes network policy group section (although with only one statement, not three).<br />
<br />
Next, edit your {{Codeline|/etc/rc.conf}}. Remove '''network''' from your DAEMONS line. Add '''connmand''' (don't forget the '''d''') ''after'' '''dbus''' and '''hal'''.<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you've installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{Package AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog.<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{Codeline|etk_prefs}}.<br />
<br />
== FAQs ==<br />
<br />
=== What happened to Entrance ? ===<br />
<br />
{{Codeline|entrance}}, a [[Display Manager]] based on the EFLs, is no longer maintained thus packages for it have been dropped.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{Filename|~/.e}} and remove it (e.g. {{Codeline|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream.<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Package Official|libxcursor}} package.<br />
<br />
=== Screen unlocking doesn't work ===<br />
<br />
If screenlock does not accept your password add the following to {{Filename|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=127194
E17
2011-01-08T01:04:37Z
<p>Foolishgrunt: /* Configuring the Network */</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|E17}}<br />
<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment - Enlightenment]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It is currently under heavy development, and is in the pre-alpha stages, but is still quite stable. Many people use it as a day-to-day environment.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the community repository (SVN snapshots) ===<br />
<br />
{{Note|Make sure the [[community repository]] is enabled in your {{Filename|/etc/pacman.conf}}.}}<br />
<br />
To install e17:<br />
pacman -S e-svn<br />
<br />
To install additional e17 modules and applications:<br />
pacman -S e17-extra-svn<br />
<br />
You might also want to install additional [[Fonts]], see [[Fonts#Desktop environments|recommended fonts for Desktop Environments]] in particular.<br />
<br />
If you need/want an e17 package which is not (yet) available in [community], see if it is available in the [[AUR]].<br />
<br />
{{Warning|As e17 is still alpha software you are encouraged to keep packages of the previous version on your computer, allowing you to [[downgrade]] if needed.}}<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{Codeline|easy_e17.sh}} compiles E17 from source and installs it in {{Filename|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{Package AUR|easy-e17}}.<br />
# Edit {{Filename|/etc/easy_e17.conf}} if you want.<br />
# Run it as root to install E17: <pre># easy_e17.sh -i</pre><br />
# Put {{Filename|/opt/e17/bin}} in your {{Codeline|PATH}} by editing {{Filename|/etc/profile}}. For example, you can add this line at the end of the file: <pre>PATH="$PATH:/opt/e17/bin"</pre><br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it isn't a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{Codeline|update_e17.sh}} is a zenity script which is made to accompany {{Codeline|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{Package AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
<br />
If you use {{Codeline|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{Filename|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{Codeline|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
Enlightenment's preferred network manager is [[Connman]], so the you'll want to download [http://aur.archlinux.org/packages.php?ID=25181|connman] from the [[AUR]]. You don't need to follow any of the other instructions on the [[Connman|Connman wiki page]] -- at least that's my assumption; the current build of ConnMan already includes network policy group section (although with only one statement, not three).<br />
<br />
Next, edit your {{Codeline|/etc/rc.conf}}. Remove '''network''' from your DAEMONS line. Add '''connmand''' (don't forget the '''d''') ''after'' '''dbus''' and '''hal'''.<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you've installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{Package AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog.<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{Codeline|etk_prefs}}.<br />
<br />
== FAQs ==<br />
<br />
=== What happened to Entrance ? ===<br />
<br />
{{Codeline|entrance}}, a [[Display Manager]] based on the EFLs, is no longer maintained thus packages for it have been dropped.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{Filename|~/.e}} and remove it (e.g. {{Codeline|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream.<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Package Official|libxcursor}} package.<br />
<br />
=== Screen unlocking doesn't work ===<br />
<br />
If screenlock does not accept your password add the following to {{Filename|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=127193
E17
2011-01-08T01:04:11Z
<p>Foolishgrunt: /* Configuring the Network */</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|E17}}<br />
<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment - Enlightenment]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It is currently under heavy development, and is in the pre-alpha stages, but is still quite stable. Many people use it as a day-to-day environment.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the community repository (SVN snapshots) ===<br />
<br />
{{Note|Make sure the [[community repository]] is enabled in your {{Filename|/etc/pacman.conf}}.}}<br />
<br />
To install e17:<br />
pacman -S e-svn<br />
<br />
To install additional e17 modules and applications:<br />
pacman -S e17-extra-svn<br />
<br />
You might also want to install additional [[Fonts]], see [[Fonts#Desktop environments|recommended fonts for Desktop Environments]] in particular.<br />
<br />
If you need/want an e17 package which is not (yet) available in [community], see if it is available in the [[AUR]].<br />
<br />
{{Warning|As e17 is still alpha software you are encouraged to keep packages of the previous version on your computer, allowing you to [[downgrade]] if needed.}}<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{Codeline|easy_e17.sh}} compiles E17 from source and installs it in {{Filename|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{Package AUR|easy-e17}}.<br />
# Edit {{Filename|/etc/easy_e17.conf}} if you want.<br />
# Run it as root to install E17: <pre># easy_e17.sh -i</pre><br />
# Put {{Filename|/opt/e17/bin}} in your {{Codeline|PATH}} by editing {{Filename|/etc/profile}}. For example, you can add this line at the end of the file: <pre>PATH="$PATH:/opt/e17/bin"</pre><br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it isn't a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{Codeline|update_e17.sh}} is a zenity script which is made to accompany {{Codeline|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{Package AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
<br />
If you use {{Codeline|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{Filename|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{Codeline|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
Enlightenment's preferred network manager is [[Connman]], so the you'll want to download [http://aur.archlinux.org/packages.php?ID=25181|connman] from the [[AUR]]. You don't need to follow any of the other instructions on the [[Conncan|Connman wiki page]] -- at least that's my assumption; the current build of ConnMan already includes network policy group section (although with only one statement, not three).<br />
<br />
Next, edit your {{Codeline|/etc/rc.conf}}. Remove '''network''' from your DAEMONS line. Add '''connmand''' (don't forget the '''d''') ''after'' '''dbus''' and '''hal'''.<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you've installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{Package AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog.<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{Codeline|etk_prefs}}.<br />
<br />
== FAQs ==<br />
<br />
=== What happened to Entrance ? ===<br />
<br />
{{Codeline|entrance}}, a [[Display Manager]] based on the EFLs, is no longer maintained thus packages for it have been dropped.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{Filename|~/.e}} and remove it (e.g. {{Codeline|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream.<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Package Official|libxcursor}} package.<br />
<br />
=== Screen unlocking doesn't work ===<br />
<br />
If screenlock does not accept your password add the following to {{Filename|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]</div>
Foolishgrunt
https://wiki.archlinux.org/index.php?title=E17&diff=127192
E17
2011-01-08T01:03:28Z
<p>Foolishgrunt: /* Configuring the Network */ Reworded, redirected links.</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|E17}}<br />
<br />
{{Article summary start}}<br />
{{Article summary text|The Enlightenment project provides useful libraries, a graphical environment and other applications as well as development tools for creating such applications. This article covers its installation, configuration, and troubleshooting.}}<br />
{{Article summary text|E17 uses the [[Elementary]] toolkit.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Enlightenment}}<br />
{{Article summary end}}<br />
<br />
From [http://trac.enlightenment.org/e/wiki/Enlightenment Enlightenment - Enlightenment]:<br />
<br />
:''The Enlightenment desktop shell provides an efficient yet breathtaking window manager based on the Enlightenment Foundation Libraries along with other essential desktop components like a file manager, desktop icons and widgets. It boasts a unprecedented level of theme-ability while still being capable of performing on older hardware or embedded devices.''<br />
<br />
E17 is the development release 17 (DR17) of the [[Enlightenment]] [[Desktop Environment]]. It is currently under heavy development, and is in the pre-alpha stages, but is still quite stable. Many people use it as a day-to-day environment.<br />
<br />
== Installing E17 ==<br />
<br />
=== From the community repository (SVN snapshots) ===<br />
<br />
{{Note|Make sure the [[community repository]] is enabled in your {{Filename|/etc/pacman.conf}}.}}<br />
<br />
To install e17:<br />
pacman -S e-svn<br />
<br />
To install additional e17 modules and applications:<br />
pacman -S e17-extra-svn<br />
<br />
You might also want to install additional [[Fonts]], see [[Fonts#Desktop environments|recommended fonts for Desktop Environments]] in particular.<br />
<br />
If you need/want an e17 package which is not (yet) available in [community], see if it is available in the [[AUR]].<br />
<br />
{{Warning|As e17 is still alpha software you are encouraged to keep packages of the previous version on your computer, allowing you to [[downgrade]] if needed.}}<br />
<br />
=== Compiling and packaging with ArchE17 script ===<br />
<br />
You can build your own Arch Linux e17 packages with a small python script called [http://dev.archlinux.org/~ronald/e17.html ArchE17].<br />
<br />
=== Compiling with easy_e17.sh ===<br />
<br />
{{Codeline|easy_e17.sh}} compiles E17 from source and installs it in {{Filename|/opt/e17}}. It does not create packages and therefore does not install dependencies automatically.<br />
<br />
# Get it from the [[AUR]]: {{Package AUR|easy-e17}}.<br />
# Edit {{Filename|/etc/easy_e17.conf}} if you want.<br />
# Run it as root to install E17: <pre># easy_e17.sh -i</pre><br />
# Put {{Filename|/opt/e17/bin}} in your {{Codeline|PATH}} by editing {{Filename|/etc/profile}}. For example, you can add this line at the end of the file: <pre>PATH="$PATH:/opt/e17/bin"</pre><br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it isn't a dependency problem. If it is, install the dependency and continue installing e17.<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
# easy_e17.sh -u<br />
<br />
==== Update_e17.sh ====<br />
<br />
{{Codeline|update_e17.sh}} is a zenity script which is made to accompany {{Codeline|easy_e17.sh}}. It makes several aspects of updating e17 easier as it can backup and restore your E17 svn tree (in case there is breakage), as well as roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. You can get it from the [[AUR]]: {{Package AUR|oz-e17-tools}}.<br />
<br />
== Starting E17 ==<br />
<br />
If you use {{Codeline|startx}} or a simple [[Display Manager]] like XDM or [[SLiM]], add or uncomment the following command in [[xinitrc]]:<br />
exec enlightenment_start<br />
<br />
More advanced display managers like [[GDM]] and [[KDM]] will automatically detect E17 thanks to the {{Filename|/usr/share/xsessions/enlightenment.desktop}} file provided by the {{Codeline|e-svn}} package.<br />
<br />
== Configuring the Network ==<br />
<br />
Enlightenment's preferred network manager is [[ConnMan]], so the you'll want to download [http://aur.archlinux.org/packages.php?ID=25181|connman] from the [[AUR]]. You don't need to follow any of the other instructions on the [[ConnMan|ConnMan wiki page]] -- at least that's my assumption; the current build of ConnMan already includes network policy group section (although with only one statement, not three).<br />
<br />
Next, edit your {{Codeline|/etc/rc.conf}}. Remove '''network''' from your DAEMONS line. Add '''connmand''' (don't forget the '''d''') ''after'' '''dbus''' and '''hal'''.<br />
<br />
ConnMan loads very quickly and appears to handle DHCP quite nicely. If you've installed [[Wpa_supplicant]], ConnMan latches onto that shows all available wireless connections.<br />
<br />
== Installing Themes ==<br />
<br />
More themes to customize the look of e17 are available from:<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org], for which you can use the {{Package AUR|e17-themes}} [[AUR]] package<br />
* [http://www.e17-stuff.org e17-stuff.org]<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog.<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting {{Codeline|etk_prefs}}.<br />
<br />
== FAQs ==<br />
<br />
=== What happened to Entrance ? ===<br />
<br />
{{Codeline|entrance}}, a [[Display Manager]] based on the EFLs, is no longer maintained thus packages for it have been dropped.<br />
<br />
== Troubleshooting ==<br />
<br />
If you find some unexpected behavior, there are a few things you can do:<br />
# try to see if the same behavior exists with the default theme<br />
# backup {{Filename|~/.e}} and remove it (e.g. {{Codeline|mv ~/.e ~/.e.back}}).<br />
<br />
If you are sure you found a bug please report it directly upstream.<br />
<br />
=== Cursors ===<br />
<br />
If X complains about X cursors not being available, install the {{Package Official|libxcursor}} package.<br />
<br />
=== Screen unlocking doesn't work ===<br />
<br />
If screenlock does not accept your password add the following to {{Filename|/etc/pam.d/enlightenment}}:<br />
auth required pam_unix_auth.so<br />
<br />
=== Unreadable fonts ===<br />
<br />
If fonts are too small and your screen is unreadable, be sure the right font packages are installed:<br />
pacman -S ttf-ms-fonts ttf-dejavu ttf-bitstream-vera<br />
<br />
== External Links ==<br />
<br />
* [http://exchange.enlightenment.org/ exchange.enlightenment.org]<br />
* [http://e17-stuff.org/ e17-stuff.org]</div>
Foolishgrunt