https://wiki.archlinux.org/api.php?action=feedcontributions&user=Synorgy&feedformat=atomArchWiki - User contributions [en]2024-03-29T02:12:58ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=AUR_helpers&diff=244218AUR helpers2013-01-17T01:58:44Z<p>Synorgy: /* Comparison Table */</p>
<hr />
<div>[[Category:Arch User Repository]]<br />
[[Category:Package management]]<br />
[[es:Aurbuild]]<br />
[[fr:Assistants AUR]]<br />
[[ja:AUR Helpers]]<br />
[[ru:AUR Helpers]]<br />
[[tr:AUR_Yardımcı_Uygulamaları]]<br />
[[zh-CN:AUR Helpers]]<br />
{{Warning|None of these tools are officially supported by Arch devs. See [https://bbs.archlinux.org/viewtopic.php?pid&#61;828254#p828254 this forum thread].}}<br />
<br />
'''AUR Helpers''' are written to make using the [[Arch User Repository]] more comfortable.<br />
<br />
== AUR uploader helpers ==<br />
<br />
* {{App|Aurploader|prompts the user for an AUR username and password and will then upload PKGBUILD tarballs to the AUR. Before uploading each package, the user is prompted to select a category. When the uploads have completed, the user is asked if the cookie file should be kept so that the script can be run again without needing the AUR username and password to be re-entered|http://xyne.archlinux.ca/projects/aurploader|{{AUR|aurploader}}}}<br />
<br />
* {{App|burp|fast and simple AUR uploader written in C. Supports persistent cookies for seamless logins|https://github.com/falconindy/burp|{{pkg|burp}}}}<br />
<br />
== AUR search/build helpers ==<br />
This is a list of helper utilities that search and/or build packages.<br />
<br />
* {{App|[[Aura]]|a multi-lingual package manager for Arch Linux written in Haskell. Has all pacman options, new ones for managing AUR packages, and a nifty logo.|https://github.com/fosskers/aura|{{AUR|aura}}}}<br />
<br />
* {{App|Aurnotify|a tool set to notify the status of your favorite packages from AUR.|http://adesklets.sourceforge.net/desklets.html|{{AUR|aurnotify}}}}<br />
<br />
* {{App|aurbuild|tool to download and build packages from the AUR.|http://aurbuild.berlios.de/|{{AUR|aurbuild}}}}<br />
<br />
* {{App|Aurget|aims to be a simple, pacman-like interface to the AUR. It tries to make the AUR convenient; whether the user wishes to find, download, build, install, or update AUR packages quickly. Aurget does not wrap any pure pacman commands, this is by design|http://pbrisbin.com/posts/aurget/|{{AUR|aurget}}}}<br />
<br />
* {{App|Aurora|very simple frontend for the AUR. It allows the user to install AUR packages, download the AUR packages (for manual installation) and also offers an AUR upgrade feature. By design, aurora does not wrap pacman|http://bitbucket.org/bbenne10/aurora|{{AUR|aurora-hg}}}}<br />
<br />
* {{App|aurpac|light'n'fast AUR and pacman frontend|http://3ed.jogger.pl/2009/02/15/aurpac/|{{AUR|aurpac}}}}<br />
<br />
* {{App|[[autoaur]]|script for automatic mass downloading, updating, building, and installing groups of AUR packages|https://github.com/stefanhusmann/autoaur|{{AUR|autoaur}}}}<br />
<br />
* {{App|1=Cower|2=fast and simple AUR search and download agent, which will also check for updates and download dependencies.<br />
:* [https://bbs.archlinux.org/viewtopic.php?id=97137 Forum page]|3=https://github.com/falconindy/cower|4={{AUR|cower}}}}<br />
<br />
* {{App|haskell-archlinux|library to programmatically access the AUR and package metadata from the Haskell programming language|http://hackage.haskell.org/package/archlinux|{{AUR|haskell-archlinux}}}}<br />
<br />
* {{App|Meat|front-end for cower ( see above ) and it is fully written in bash<br />
:{{Note|Meat is in actually under development/alpha state.}}|https://github.com/e36freak/meat|{{AUR|meat-git}}}}<br />
<br />
* {{App|owl|pacman and cower wrapper focused on simplicity|https://github.com/baskerville/owl<br />
:* [https://bbs.archlinux.org/viewtopic.php?id=129609 Forum page]|https://github.com/baskerville/owl|{{AUR|owl-git}}}}<br />
<br />
* {{App|1=[[Pacaur]]|2=fast workflow AUR wrapper, using cower as backend. It is aims at speed and simplicity, and is designed to minimize user prompt interaction and to use an uncluttered interface.<br />
:* [https://bbs.archlinux.org/viewtopic.php?pid=937423 Forum page]|3=https://github.com/Spyhawk/pacaur|4={{AUR|pacaur}}}}<br />
<br />
* {{App|1=Packer|2=wrapper for pacman and the AUR. It was designed to be a simple and very fast replacement for the basic functionality of Yaourt. It has commands to install, update, search, and show information for any package in the main repositories and in the AUR. Use pacman for other commands, such as removing a package<br />
:* [https://bbs.archlinux.org/viewtopic.php?id=88115 Forum page]<br />
:* [https://github.com/keenerd/packer/wiki Wiki]|3=https://github.com/keenerd/packer|4={{AUR|packer}}}}<br />
<br />
* {{App|1=Paktahn|2=yaourt replacement. It is under active development and already includes improvements such as a local cache for fast searches and interactive installation<br />
:* [https://bbs.archlinux.org/viewtopic.php?id=77674&p=1 Forum page]<br />
|3=https://github.com/skypher/paktahn|4={{AUR|paktahn}}}}<br />
<br />
* {{App|1=Pbfetch|2=script which can be used as a pacman-independent AUR helper or a pacman wrapper with additional AUR functionality. Pbfetch aims to be a simple and fast versus the well established yaourt. Pbfetch can be used as a shortcut to simply download PKGBUILDs from AUR or automatically build with dependency resolution among other things. The user can select which AUR packages to upgrade using a simple menu as well as update all AUR packages<br />
:* [https://bbs.archlinux.org/viewtopic.php?id=87789 Forum page]<br />
|3=https://github.com/dalingrin/pbfetch|4={{AUR|pbfetch-git}}}}<br />
<br />
* {{App|Pbget|simple command-line tool for retrieving PKGBUILDs and local source files for Arch Linux. It is able to retrieve files from the official SVN and CVS web interface, the AUR and the ABS rsync server|http://xyne.archlinux.ca/projects/pbget|{{AUR|pbget}}}}<br />
<br />
* {{App|1=PKGBUILDer|2=a python3 AUR helper with dependency support. It was (probably) the first helper supporting updates through multiinfo. Contains many useful features and is written to be fast and verbose, to eliminate long waiting times.|3=https://github.com/Kwpolska/pkgbuilder|4={{AUR|pkgbuilder}}}}<br />
<br />
* {{App|1=pkgman|2=script which helps to manage a local repository. It retrieves the PKGBUILD and related files for given name from ABS or AUR and lets you edit them, automatically generates checksums, backs up the source tarball, builds and adds the package to your local repository. Then you can install it as usual with pacman. It also has AUR support for submitting tarballs and leaving comments<br />
:* [https://bbs.archlinux.org/viewtopic.php?id=49023 Forum page]<br />
|3=http://sourceforge.net/apps/mediawiki/pkgman/index.php|4={{AUR|pkgman}}}}<br />
<br />
* {{App|Spinach|just another bash AUR helper|http://floft.net/wiki/Scripts/Spinach|{{AUR|spinach}}}}<br />
<br />
* {{App|1=srcman|2=pacman/makepkg wrapper written in Bash, which transparently handles pacman operations on 'source packages'. This means, for example, that packages can be specified for installation either explicitly (pacman's {{Ic|-U}} operation) or can be installed from a (source) repository (-S operation). The address of an AUR pacman database can be found in the corresponding forum thread, by the way. The primary goal of this project is to provide a complete pacman wrapper and therefore, srcman supports all current pacman operations for binary ''and'' source packages|3=https://bbs.archlinux.org/viewtopic.php?id=65501|4={{AUR|srcman}}}}<br />
<br />
* {{App|[[Yaourt]] (Yet Another User Repository Tool)|community-contributed wrapper for pacman which adds seamless access to the AUR, allowing and automating package compilation and installation from your choice of the thousands of PKGBUILDs in the AUR, in addition to the many thousands of available Arch binary packages. Yaourt uses the same exact syntax as pacman, which saves you from relearning an entirely new method of system maintenance, but also adds new options. Yaourt expands the power and simplicity of pacman by adding even more useful features and provides pleasing, colorized output, interactive search mode, and much more|http://archlinux.fr/yaourt-en|{{AUR|yaourt}}}}<br />
<br />
=== Comparison Table ===<br />
<br />
{| border="1" cellpadding="4" cellspacing="0" <br />
! Name !! Written in !! Handles Deps !! Official Repo support !! AUR Search !! Handles Upgrades !! Handles Downgrades !! Handles Backups !! Shell Tab Completion !! Manually Parses PKGBUILD* || Multilingual !! Active Project !! Usage <br />
|- <br />
! [[Aura]] <br />
| Haskell || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Bash/zsh || {{Yes}} || {{Yes}} || {{Yes}} || See {{Ic|man aura}} or {{Ic|aura -h}}<br />
|-<br />
! Aurget<br />
| Bash || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Bash || {{No}} || {{No}} || {{Yes}} || See {{Ic|aurget --help}}<br />
|-<br />
! Aurora<br />
| Python3 || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{No}} || {{No}} || {{No}} || {{Yes}} || See {{Ic|aurora --help}}<br />
|-<br />
! Cower<br />
| C|| {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Bash/zsh || {{Yes}} || {{No}} || {{Yes}} || See {{Ic|cower -h}}<br />
|-<br />
! Owl<br />
| Dash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Bash || {{Yes}} || {{No}} || {{Yes}} || See {{Ic|man owl}}<br />
|-<br />
! [[Pacaur]]<br />
| Bash/C || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Bash || {{Yes}} (optional)|| {{No}} || {{Yes}} || Identical to pacman, and/or AUR specific arguments . See also {{Ic|pacaur -h}}.<br />
|-<br />
! Packer<br />
| Bash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{No}} || {{No}} || {{No}} || {{Yes}} || Identical to pacman.<br />
|-<br />
! Paktahn<br />
| Lisp|| {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{No}} || {{No}} || {{No}} || {{Yes}} || Identical to pacman.<br />
|-<br />
! pbfetch<br />
| Bash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{No}} || {{No}} || {{No}} || {{Yes}} || Identical to pacman, and/or AUR specific arguments.<br />
|-<br />
! PKGBUILDer<br />
| Python3 || {{Yes}} || {{Yes}} ({{Ic|pb}} command) || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{No}} || {{No}} || {{Yes}} || {{Yes}} || Identical to pacman. <br />
|-<br />
! Spinach<br />
| Bash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{No}} || {{Yes}} || {{No}} || {{Yes}} || See {{Ic|man spinach}}<br />
|-<br />
! [[Yaourt]]<br />
| Bash/C || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || Bash/zsh/fish || {{No}} || {{Yes}} || {{Yes}} || Identical to pacman.<br />
|}<br />
<br />
{{Note|Scripts that do not parse PKGBUILDs manually opt instead to execute them directly for their variables. This is not considered secure, but is generally more accurate than manual parsing.}}<br />
<br />
== Testing and validation ==<br />
Helpers that check for errors in packages.<br />
<br />
* {{App|parched|pacman package and PKGBUILD parser module|http://hackage.haskell.org/package/archlinux|{{AUR|parched}}}}<br />
<br />
== See also ==<br />
* [[pacman GUI Frontends]]</div>Synorgyhttps://wiki.archlinux.org/index.php?title=AUR_helpers&diff=244217AUR helpers2013-01-17T01:58:00Z<p>Synorgy: Aurora is actively developed, and allows searching the AUR.</p>
<hr />
<div>[[Category:Arch User Repository]]<br />
[[Category:Package management]]<br />
[[es:Aurbuild]]<br />
[[fr:Assistants AUR]]<br />
[[ja:AUR Helpers]]<br />
[[ru:AUR Helpers]]<br />
[[tr:AUR_Yardımcı_Uygulamaları]]<br />
[[zh-CN:AUR Helpers]]<br />
{{Warning|None of these tools are officially supported by Arch devs. See [https://bbs.archlinux.org/viewtopic.php?pid&#61;828254#p828254 this forum thread].}}<br />
<br />
'''AUR Helpers''' are written to make using the [[Arch User Repository]] more comfortable.<br />
<br />
== AUR uploader helpers ==<br />
<br />
* {{App|Aurploader|prompts the user for an AUR username and password and will then upload PKGBUILD tarballs to the AUR. Before uploading each package, the user is prompted to select a category. When the uploads have completed, the user is asked if the cookie file should be kept so that the script can be run again without needing the AUR username and password to be re-entered|http://xyne.archlinux.ca/projects/aurploader|{{AUR|aurploader}}}}<br />
<br />
* {{App|burp|fast and simple AUR uploader written in C. Supports persistent cookies for seamless logins|https://github.com/falconindy/burp|{{pkg|burp}}}}<br />
<br />
== AUR search/build helpers ==<br />
This is a list of helper utilities that search and/or build packages.<br />
<br />
* {{App|[[Aura]]|a multi-lingual package manager for Arch Linux written in Haskell. Has all pacman options, new ones for managing AUR packages, and a nifty logo.|https://github.com/fosskers/aura|{{AUR|aura}}}}<br />
<br />
* {{App|Aurnotify|a tool set to notify the status of your favorite packages from AUR.|http://adesklets.sourceforge.net/desklets.html|{{AUR|aurnotify}}}}<br />
<br />
* {{App|aurbuild|tool to download and build packages from the AUR.|http://aurbuild.berlios.de/|{{AUR|aurbuild}}}}<br />
<br />
* {{App|Aurget|aims to be a simple, pacman-like interface to the AUR. It tries to make the AUR convenient; whether the user wishes to find, download, build, install, or update AUR packages quickly. Aurget does not wrap any pure pacman commands, this is by design|http://pbrisbin.com/posts/aurget/|{{AUR|aurget}}}}<br />
<br />
* {{App|Aurora|very simple frontend for the AUR. It allows the user to install AUR packages, download the AUR packages (for manual installation) and also offers an AUR upgrade feature. By design, aurora does not wrap pacman|http://bitbucket.org/bbenne10/aurora|{{AUR|aurora-hg}}}}<br />
<br />
* {{App|aurpac|light'n'fast AUR and pacman frontend|http://3ed.jogger.pl/2009/02/15/aurpac/|{{AUR|aurpac}}}}<br />
<br />
* {{App|[[autoaur]]|script for automatic mass downloading, updating, building, and installing groups of AUR packages|https://github.com/stefanhusmann/autoaur|{{AUR|autoaur}}}}<br />
<br />
* {{App|1=Cower|2=fast and simple AUR search and download agent, which will also check for updates and download dependencies.<br />
:* [https://bbs.archlinux.org/viewtopic.php?id=97137 Forum page]|3=https://github.com/falconindy/cower|4={{AUR|cower}}}}<br />
<br />
* {{App|haskell-archlinux|library to programmatically access the AUR and package metadata from the Haskell programming language|http://hackage.haskell.org/package/archlinux|{{AUR|haskell-archlinux}}}}<br />
<br />
* {{App|Meat|front-end for cower ( see above ) and it is fully written in bash<br />
:{{Note|Meat is in actually under development/alpha state.}}|https://github.com/e36freak/meat|{{AUR|meat-git}}}}<br />
<br />
* {{App|owl|pacman and cower wrapper focused on simplicity|https://github.com/baskerville/owl<br />
:* [https://bbs.archlinux.org/viewtopic.php?id=129609 Forum page]|https://github.com/baskerville/owl|{{AUR|owl-git}}}}<br />
<br />
* {{App|1=[[Pacaur]]|2=fast workflow AUR wrapper, using cower as backend. It is aims at speed and simplicity, and is designed to minimize user prompt interaction and to use an uncluttered interface.<br />
:* [https://bbs.archlinux.org/viewtopic.php?pid=937423 Forum page]|3=https://github.com/Spyhawk/pacaur|4={{AUR|pacaur}}}}<br />
<br />
* {{App|1=Packer|2=wrapper for pacman and the AUR. It was designed to be a simple and very fast replacement for the basic functionality of Yaourt. It has commands to install, update, search, and show information for any package in the main repositories and in the AUR. Use pacman for other commands, such as removing a package<br />
:* [https://bbs.archlinux.org/viewtopic.php?id=88115 Forum page]<br />
:* [https://github.com/keenerd/packer/wiki Wiki]|3=https://github.com/keenerd/packer|4={{AUR|packer}}}}<br />
<br />
* {{App|1=Paktahn|2=yaourt replacement. It is under active development and already includes improvements such as a local cache for fast searches and interactive installation<br />
:* [https://bbs.archlinux.org/viewtopic.php?id=77674&p=1 Forum page]<br />
|3=https://github.com/skypher/paktahn|4={{AUR|paktahn}}}}<br />
<br />
* {{App|1=Pbfetch|2=script which can be used as a pacman-independent AUR helper or a pacman wrapper with additional AUR functionality. Pbfetch aims to be a simple and fast versus the well established yaourt. Pbfetch can be used as a shortcut to simply download PKGBUILDs from AUR or automatically build with dependency resolution among other things. The user can select which AUR packages to upgrade using a simple menu as well as update all AUR packages<br />
:* [https://bbs.archlinux.org/viewtopic.php?id=87789 Forum page]<br />
|3=https://github.com/dalingrin/pbfetch|4={{AUR|pbfetch-git}}}}<br />
<br />
* {{App|Pbget|simple command-line tool for retrieving PKGBUILDs and local source files for Arch Linux. It is able to retrieve files from the official SVN and CVS web interface, the AUR and the ABS rsync server|http://xyne.archlinux.ca/projects/pbget|{{AUR|pbget}}}}<br />
<br />
* {{App|1=PKGBUILDer|2=a python3 AUR helper with dependency support. It was (probably) the first helper supporting updates through multiinfo. Contains many useful features and is written to be fast and verbose, to eliminate long waiting times.|3=https://github.com/Kwpolska/pkgbuilder|4={{AUR|pkgbuilder}}}}<br />
<br />
* {{App|1=pkgman|2=script which helps to manage a local repository. It retrieves the PKGBUILD and related files for given name from ABS or AUR and lets you edit them, automatically generates checksums, backs up the source tarball, builds and adds the package to your local repository. Then you can install it as usual with pacman. It also has AUR support for submitting tarballs and leaving comments<br />
:* [https://bbs.archlinux.org/viewtopic.php?id=49023 Forum page]<br />
|3=http://sourceforge.net/apps/mediawiki/pkgman/index.php|4={{AUR|pkgman}}}}<br />
<br />
* {{App|Spinach|just another bash AUR helper|http://floft.net/wiki/Scripts/Spinach|{{AUR|spinach}}}}<br />
<br />
* {{App|1=srcman|2=pacman/makepkg wrapper written in Bash, which transparently handles pacman operations on 'source packages'. This means, for example, that packages can be specified for installation either explicitly (pacman's {{Ic|-U}} operation) or can be installed from a (source) repository (-S operation). The address of an AUR pacman database can be found in the corresponding forum thread, by the way. The primary goal of this project is to provide a complete pacman wrapper and therefore, srcman supports all current pacman operations for binary ''and'' source packages|3=https://bbs.archlinux.org/viewtopic.php?id=65501|4={{AUR|srcman}}}}<br />
<br />
* {{App|[[Yaourt]] (Yet Another User Repository Tool)|community-contributed wrapper for pacman which adds seamless access to the AUR, allowing and automating package compilation and installation from your choice of the thousands of PKGBUILDs in the AUR, in addition to the many thousands of available Arch binary packages. Yaourt uses the same exact syntax as pacman, which saves you from relearning an entirely new method of system maintenance, but also adds new options. Yaourt expands the power and simplicity of pacman by adding even more useful features and provides pleasing, colorized output, interactive search mode, and much more|http://archlinux.fr/yaourt-en|{{AUR|yaourt}}}}<br />
<br />
=== Comparison Table ===<br />
<br />
{| border="1" cellpadding="4" cellspacing="0" <br />
! Name !! Written in !! Handles Deps !! Official Repo support !! AUR Search !! Handles Upgrades !! Handles Downgrades !! Handles Backups !! Shell Tab Completion !! Manually Parses PKGBUILD* || Multilingual !! Active Project !! Usage <br />
|- <br />
! [[Aura]] <br />
| Haskell || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Bash/zsh || {{Yes}} || {{Yes}} || {{Yes}} || See {{Ic|man aura}} or {{Ic|aura -h}}<br />
|-<br />
! Aurget<br />
| Bash || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Bash || {{No}} || {{No}} || {{Yes}} || See {{Ic|aurget --help}}<br />
|-<br />
! Aurora<br />
| Python3 || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{No}} || N/A || {{No}} || {{Yes}} || See {{Ic|aurora --help}}<br />
|-<br />
! Cower<br />
| C|| {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Bash/zsh || {{Yes}} || {{No}} || {{Yes}} || See {{Ic|cower -h}}<br />
|-<br />
! Owl<br />
| Dash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Bash || {{Yes}} || {{No}} || {{Yes}} || See {{Ic|man owl}}<br />
|-<br />
! [[Pacaur]]<br />
| Bash/C || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Bash || {{Yes}} (optional)|| {{No}} || {{Yes}} || Identical to pacman, and/or AUR specific arguments . See also {{Ic|pacaur -h}}.<br />
|-<br />
! Packer<br />
| Bash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{No}} || {{No}} || {{No}} || {{Yes}} || Identical to pacman.<br />
|-<br />
! Paktahn<br />
| Lisp|| {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{No}} || {{No}} || {{No}} || {{Yes}} || Identical to pacman.<br />
|-<br />
! pbfetch<br />
| Bash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{No}} || {{No}} || {{No}} || {{Yes}} || Identical to pacman, and/or AUR specific arguments.<br />
|-<br />
! PKGBUILDer<br />
| Python3 || {{Yes}} || {{Yes}} ({{Ic|pb}} command) || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{No}} || {{No}} || {{Yes}} || {{Yes}} || Identical to pacman. <br />
|-<br />
! Spinach<br />
| Bash || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{No}} || {{No}} || {{Yes}} || {{No}} || {{Yes}} || See {{Ic|man spinach}}<br />
|-<br />
! [[Yaourt]]<br />
| Bash/C || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || Bash/zsh/fish || {{No}} || {{Yes}} || {{Yes}} || Identical to pacman.<br />
|}<br />
<br />
{{Note|Scripts that do not parse PKGBUILDs manually opt instead to execute them directly for their variables. This is not considered secure, but is generally more accurate than manual parsing.}}<br />
<br />
== Testing and validation ==<br />
Helpers that check for errors in packages.<br />
<br />
* {{App|parched|pacman package and PKGBUILD parser module|http://hackage.haskell.org/package/archlinux|{{AUR|parched}}}}<br />
<br />
== See also ==<br />
* [[pacman GUI Frontends]]</div>Synorgyhttps://wiki.archlinux.org/index.php?title=Intel_GMA_500&diff=243282Intel GMA 5002013-01-09T02:06:59Z<p>Synorgy: /* Old fbdev driver (default) */</p>
<hr />
<div>[[Category:Graphics]]<br />
[[Category:X Server]]<br />
[[el:Poulsbo]]<br />
[[it:Poulsbo]]<br />
[[ru:Poulsbo]]<br />
{{Article summary start}}<br />
{{Article summary text|The current state of Intel GMA500/Poulsbo hardware support under Arch Linux.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Intel Graphics}}<br />
{{Article summary wiki|Xorg}}<br />
{{Article summary wiki|MPlayer}}<br />
{{Article summary heading|Resources}}<br />
{{Article summary link|Poulsbo Discussion in Arch BBS|https://bbs.archlinux.org/viewtopic.php?pid&#61;746439}}<br />
{{Article summary end}}<br />
<br />
The '''Intel GMA 500''' series, also known by it's codename '''Poulsbo''' or '''[http://ark.intel.com/Product.aspx?id=35444 Intel System Controller Hub US15W]''', is a family of integrated video adapters based on the PowerVR SGX 535 graphics core. It is typically found on boards for the Atom Z processor series. Features include hardware decoding capability of up to 720p/1080i video content in various state-of-the-art codecs, e.g. H.264.<br />
<br />
As the PowerVR SGX 535 graphics core was developed by Imagination Technologies and then licensed by Intel, the standard opensource [[Intel]] drivers do not work with this hardware. <br />
<br />
On this page you find comprehensive information about how to get the best out of your Poulsbo hardware using Arch Linux.<br />
<br />
== Kernel's gma500_gfx module ==<br />
<br />
With kernel 2.6.39, a new psb_gfx module appeared in the kernel developed by [http://en.wikipedia.org/wiki/Alan_Cox Alan Cox] to support Poulsbo hardware. As of kernel 3.3.rc1 the driver has left staging and been renamed gma500_gfx. ([http://blog.bodhizazen.net/linux/linux-gma500-poulsbo-driver-moved-out-of-staging/])<br />
<br />
'''Advantages'''<br />
<br />
* Native resolution (1366x768) with early KMS (tested on Asus Eee 1101HA)<br />
* Up to date kernel and Xorg<br />
* 2D acceleration<br />
* Works out of the box<br />
<br />
'''Disadvantages'''<br />
<br />
* Some are unable to get native resolution (e.g 1366x768)<br />
* No 3D acceleration possible<br />
* Poor multimedia performance (use mplayer with x11 or sdl so fullscreen video will be quite slow)<br />
<br />
To check if the driver is loaded, the output of <code>lsmod | grep gma</code> should look like this:<br />
<br />
gma500_gfx 131893 2 <br />
i2c_algo_bit 4615 1 gma500_gfx<br />
drm_kms_helper 29203 1 gma500_gfx<br />
drm 170883 2 drm_kms_helper,gma500_gfx<br />
i2c_core 16653 5 drm,drm_kms_helper,i2c_algo_bit,gma500_gfx,videodev<br />
<br />
== Modesetting driver and dual monitor Setup ==<br />
To setup different resolution for external monitor using [https://wiki.archlinux.org/index.php/Xrandr xrandr], {{Pkg|xf86-video-modesetting}} from official repo is needed. If you choose to use the git package ({{AUR| xf86-video-modesetting-git}}), remember to recompile it after a new version of [[Xorg]]. After installing, an [[Xorg]] file is needed to setup the driver. Use this for device section:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/20-gpudriver.conf|<br />
Section "Device"<br />
Identifier "gma500_gfx"<br />
Driver "modesetting"<br />
Option "SWCursor" "ON" <br />
EndSection<br />
}}<br />
{{Note|1= The above configuration file will replace the {{Pkg|xf86-video-fbdev}} driver. If you want to revert back, just replace {{ic|modesetting}} with {{ic|fbdev}}.}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Poor video performance ===<br />
<br />
If you have problems playing 720p and 1080i videos, yes, that's normal while there are not accelerated XV drivers. But you can improve it up to the point of going well and smoothly for most videos (even HD ones) with these tricks:<br />
<br />
# add <code>pm-powersave false</code> to <code>/etc/rc.local</code>. <code>man pm-powersave</code> for more info.<br />
# use {{AUR| xf86-video-modesetting-git}} as indicated above.<br />
# always use [[mplayer]] or any variant/gui. [[VLC]] and others are usually much more slower.<br />
# substitute the normal mplayer with {{AUR| mplayer-minimal-svn}}, and compile with aggressive optimizations: <code>-march=native -fomit-frame-pointer -O3 -ffast-math'</code>. ([[Makepkg|About makepkg]])<br />
# use {{AUR | linux-lqx}} as it is a very good performance kernel. Edit PKGBUILD so you can do <code>menuconfig</code> and make sure you select your processor and remove generic optimizations for other processors. ([[kernel |About kernels]])<br />
<br />
=== Fix suspend ===<br />
==== Old fbdev driver (default) ====<br />
<br />
If suspend does not work, there are various quirk options you can try. First, make sure that you have {{Pkg|pm-utils}} and {{Pkg|pm-quirks}} [[pacman|installed]]. See the manpage for pm-suspend for a list of them all. One that has been reported to help is <code>quirk-vbemode-restore</code>, which saves and restores the current VESA mode.<br />
<br />
To test it, open a terminal and use the following command<br />
<br />
# pm-suspend --quirk-vbemode-restore <br />
<br />
That should suspend your system. If you are able to resume, you'll want to use this option every time you suspend.<br />
<br />
# echo "ADD_PARAMETERS='--quirk-vbemode-restore'" > /etc/pm/config.d/gma500 <br />
<br />
If you are not able to resume and you get a black screen instead, try the above quirk command with only '''one dash'''<br />
<br />
# pm-suspend -quirk-vbemode-restore <br />
<br />
If this also fails, you might try removing pm-utils's video resume script, so that it's not run when you resume the machine. <br />
<br />
# cd /usr/lib/pm-utils/sleep.d<br />
# mv 99video ~<br />
<br />
{{Tip| If you stuck with a black screen after resume, be aware that besides the black screen, your system works fine. Instead of hard rebooting, you could try to blindly reboot your system, since the last thing you used before suspend was the terminal. Alternatively, if you have ssh enabled on your machine you could do it remotely.}}<br />
<br />
==== modesetting xorg driver ====<br />
<br />
On some machines, when using modesetting driver the screen gets messed up with random data. Although the computer still works, you must go to a console and kill X or reboot "blindly". This is not optimal, so here is a solution:<br />
<br />
First, see your available screens and modes running {{ic|xrandr}}:<br />
<br />
{{bc|<br />
# xrandr<br />
Screen 0: minimum 320 x 200, current 1280 x 720, maximum 2048 x 2048<br />
LVDS-0 connected 1280x720+0+0 222mm x 125mm<br />
1280x720 60.0*+<br />
HDMI-0 connected 1280x720+0+0 531mm x 298mm<br />
1920x1080 60.0 +<br />
1680x1050 59.9 <br />
1680x945 60.0 <br />
1400x1050 74.9 59.9 <br />
1600x900 60.0 <br />
1280x1024 75.0 60.0 <br />
1440x900 75.0 59.9 <br />
1280x960 60.0 <br />
1366x768 60.0 <br />
1360x768 60.0 <br />
1280x800 74.9 59.9 <br />
1152x864 75.0 <br />
1280x768 74.9 60.0 <br />
1280x720 60.0* <br />
1024x768 75.1 70.1 60.0 <br />
1024x576 60.0 <br />
832x624 74.6 <br />
800x600 72.2 75.0 60.3 56.2 <br />
848x480 60.0 <br />
640x480 72.8 75.0 60.0 <br />
720x400 70.1<br />
}}<br />
<br />
Edit or create (giving executive permissions) {{ic|/etc/pm/sleep.d/99xrandr}}, writing the correct names and modes for your solution:<br />
<br />
{{bc|<nowiki><br />
#!/bin/sh<br />
#<br />
# turn off and on the screens so we force to clean video data<br />
case "$1" in<br />
hibernate|||suspend)<br />
xrandr --output LVDS-0 --off<br />
xrandr --output HDMI-0 --off<br />
;;<br />
thaw|||resume)<br />
xrandr --output LVDS-0 --off<br />
xrandr --output HDMI-0 --off<br />
xrandr --output LVDS-0 --mode 1280x720<br />
/usr/local/bin/brillo-<br />
;;<br />
*) exit $NA<br />
;;<br />
esac<br />
</nowiki>}}<br />
<br />
In my case, I turn off both screens, and turn on only the main screen upon awakening. Feel free to customize to your needs.<br />
On some machines, the screen turns on by default even when the system was put to sleep with the screen turned off, so you need to turn it off twice.<br />
<br />
{{Note| This only works if you call {{ic|pm-suspend}} or {{ic|pm-hibernate}} inside [[X]]. If it is called from a daemon or a tty, it won't work.}}<br />
<br />
=== Set backlight brightness ===<br />
<br />
All that is needed to set the brightness is sending a number (0-100) to {{ic|/sys/class/backlight/psblvds/brightness}}. This obviously requires sysfs to be enabled in the kernel, as it is in the Arch Linux kernel. To set display to minimal brightness, issue this command as root:<br />
<br />
# echo 0 > /sys/class/backlight/psb-bl/brightness<br />
<br />
Or, for full luminosity:<br />
<br />
# echo 100 > /sys/class/backlight/psb-bl/brightness<br />
<br />
A very short script is available to do this with less typing written by [https://bbs.archlinux.org/viewtopic.php?pid=813074#p813074 mulenmar].<br />
<br />
#! /bin/sh<br />
sudo sh -c "echo $1 > /sys/class/backlight/psb-bl/brightness"<br />
<br />
Simply save it as brightness.sh, and give it executable permissions. Then you can use it like so:<br />
<br />
Set brightness to minimum:<br />
<br />
./brightness.sh 0<br />
<br />
Set brightness to half:<br />
<br />
./brightness.sh 50<br />
<br />
Sudo may obviously ask for your password, so you have to be in the sudoers file. A variation of this script can be found [https://bbs.archlinux.org/viewtopic.php?pid=1143245#p1143245 here].<br />
<br />
{{Note|If changing {{ic|/sys/class/backlight/psblvds/brightness}} does not work, you may need to add {{ic|acpi_osi&#61;Linux acpi_backlight&#61;vendor}} to your [[kernel parameters]]. After rebooting, a new folder will appear under {{ic|/sys/class/backlight/}}; making changes to the {{ic|brightness}} file in that folder should work. For example, in some Asus netbooks the backlight can be controlled by writing a value (0-10) to {{ic|/sys/class/backlight/eeepc-wmi/brightness}}.}}<br />
<br />
=== Memory allocation optimization ===<br />
<br />
You can often improve performance by limiting the amount of RAM used by the system so that there will be more available for the videocard. If you have 1GB RAM use <code>mem=896mb</code> or if you have 2GB RAM use <code>mem=1920mb</code>. Add the following parameters to your bootloader's configuration file.<br />
<br />
*[[Grub-legacy]]<br />
Edit {{ic|/boot/grub/menu.lst}}<br />
...<br />
kernel /vmlinuz-linux root=/dev/sda2 ro mem=896mb <br />
...<br />
<br />
*[[Grub]]<br />
Edit {{ic|/etc/default/grub}}<br />
...<br />
GRUB_CMDLINE_LINUX="mem=896mb"<br />
...<br />
<br />
*[[Syslinux]]<br />
Edit {{ic|/boot/syslinux/syslinux.cfg}}<br />
...<br />
APPEND root=/dev/sda2 ro mem=896mb <br />
...<br />
<br />
==See also==<br />
* [http://www.kriptopolis.org/arch-linux-03#comment-66066 An experience about configuring Poulsbo (Spanish)]<br />
* [https://wiki.ubuntu.com/HardwareSupportComponentsVideoCardsPoulsbo/ Ubuntu Wiki]<br />
* [http://ubuntuforums.org/showthread.php?t=1984236 Ubuntu Forums]<br />
* [http://blog.bodhizazen.net/linux/ubuntu-12-04-gma500-poulsbo-boot-options/ Ubuntu 12.04 gma500 (poulsbo) boot options (blog post)]</div>Synorgyhttps://wiki.archlinux.org/index.php?title=SLiM&diff=169744SLiM2011-11-12T16:01:23Z<p>Synorgy: Added the note to the beginning about the deprecation of SLiM.</p>
<hr />
<div>[[Category:Display managers (English)]]<br />
{{i18n|SLiM}}<br />
[[fr:SLiM]]<br />
{{Article summary start}}<br />
{{Article summary text|Provides an overview of the Simple Login Manager.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Display Manager}}<br />
{{Article summary end}}<br />
<br />
{{Box RED | Note: | SLiM is outdated and upstream development has ceased. Please consider using LXDM instead of SLiM. You can find information on setting up LXDM on the [[Display Manager]] page}}<br />
<br />
[http://slim.berlios.de/ SLiM] is an acronym for Simple Login Manager. SLiM is simple, lightweight and easily configurable. SLiM is used by some because it does not require the dependencies of [[GNOME]] or [[KDE]] and can help make a lighter system for users that like to use lightweight desktops like [[Xfce]], [[Openbox]], and [[Fluxbox]].<br />
<br />
== Installation ==<br />
<br />
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 />
Remember to make .xinitrc executable:<br />
<br />
chmod +x ~/.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 startfluxbox<br />
exec fvwm2<br />
exec gnome-session<br />
exec openbox-session<br />
exec startkde<br />
exec startlxde<br />
exec startxfce4<br />
exec enlightenment_start<br />
exec ck-launch-session $ONE_OF_THE_ABOVE<br />
</pre><br />
<br />
To get automount to work it might be necessary to use something like e.g.:<br />
<br />
exec ck-launch-session dbus-launch startxfce4<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 PolicyKit, use ConsoleKit's {{Codeline|ck-launch-session}} by changing the {{Codeline|login_cmd}} line of your {{filename|/etc/slim.conf}} to:<br />
<br />
login_cmd exec ck-launch-session /bin/bash -login ~/.xinitrc %session<br />
<br />
and leave your {{Filename|~/.xinitrc}} as plain as possible; for instance:<br />
<br />
#!/bin/sh<br />
exec startxfce4 # or the window manager of your choice<br />
<br />
=== Autologin ===<br />
<br />
To make SLiM automatically login as a specified user (without having to type a password) the following lines in {{Filename|/etc/slim.conf}} should be changed.<br />
# default_user simone<br />
<br />
Uncomment this line, and change "simone" to the user to be logged into automatically.<br />
<br />
# auto_login no<br />
<br />
Uncomment this line and change the 'no' to 'yes'. This enables the auto login feature.<br />
<br />
=== 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 />
Note that, in this script, the default option simply executes, e.g., exec icewm (if that is the default session), without icewmbg and icewmtray. You may want simply to repeat everything you've put under, e.g., icewm) again under *).<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 {{Codeline|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 {{Filename|/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 {{codeline|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 daemon ===<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 from initializing. 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 {{Codeline|1=DEFAULT_TTY=7}} same as {{Codeline|xserver_arguments vt07}}.<br />
<br />
=== Power-off tray icon fails ===<br />
<br />
If your power off tray icon fails, it could be due to not having root privileges. To start a tray icon with root privileges, be sure to have SLiM start the program. Edit {{Filename|/etc/slim.conf}} as follows:<br />
sessionstart_cmd /path/to/tray/icon/program &<br />
<br />
=== Login information with SLiM ===<br />
<br />
By default, SLiM fails to log logins to utmp and wtmp which causes who, last, etc. to misreport login information. To fix this edit your {{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 {{Filename|/etc/pam.d/slim}} (as discussed [http://bugs.archlinux.org/task/18637 here]).<br />
auth optional pam_gnome_keyring.so<br />
session optional pam_gnome_keyring.so auto_start<br />
<br />
You also have to add to {{Filename|/etc/pam.d/passwd}}:<br />
password optional pam_gnome_keyring.so<br />
<br />
If you use a screensaver you also have to add <br />
auth optional pam_gnome_keyring.so<br />
to {{Filename|/etc/pam.d/gnome-screensaver}} for example (replace gnome-screensaver with slimlock,slock,whatever you use). If you don't do that, your keyring is locked when screen is locked by your screensaver and not unlocked again after logging back in.<br />
<br />
However, this fix alone no longer works since Gnome 2.30. Further changes are necessary as described [http://bugs.archlinux.org/task/18930 here]. Modifying the {{Codeline|login_cmd}} line in {{Filename|/etc/slim.conf}}:<br />
login_cmd exec ck-launch-session dbus-launch /bin/bash -login ~/.xinitrc %session >~/.xsession-errors 2>&1<br />
<br />
As of GNOME 3, simply adding {{Codeline|dbus-launch}} after {{Codeline|ck-launch-session}} will work, without needing to edit {{Filename|/etc/pam.d/slim}}.<br />
<br />
As of GNOME 3.1, you need to add {{Codeline|dbus-launch}} after {{Codeline|ck-launch-session}} and edit {{Filename|/etc/pam.d/{slim,passwd} }}, otherwise the keyring will not be automatically unlocked. I never tried it on 3.0, so maybe the above information about GNOME 3 is wrong.<br />
<br />
The solutions mentioned here and also further information are found [http://live.gnome.org/GnomeKeyring/Pam here].<br />
<br />
=== SLiM and Environment Variables ===<br />
If you have trouble with environment variables changing after a session is started, one cause could be the module pam_env.so, by default, reads the file {{Filename|/etc/environment}} and sets up the environment accordingly.<br />
<br />
For example: I use SLiM, which fires up a XFCE4 session upon valid authentication. When this is done my terminal(xfterm4) can't print Unicode characters(LC_* environment variables has been defaulted/altered to "POSIX"). But when I start XFCE4 manually, like so: {{Codeline|startxfce4}}, Unicode characters on my terminal works fine.<br />
<br />
This can be fixed by adding this to {{Filename|/etc/environment}} or your user specific file: {{Filename|$HOME/.pam_environment}}:<br />
# You can change these to fit your preference, of course.<br />
LANG="en_US.UTF-8"<br />
LC_COLLATE="C"<br />
<br />
Alternatively, you can modify the line in {{Filename|/etc/pam.d/slim}} from:<br />
<pre><br />
session required pam_env.so<br />
</pre><br />
To:<br />
<pre><br />
session required pam_env.so envfile=<yourfile><br />
</pre><br />
Where <yourfile> is the name of the file you want PAM to recognize as your default environment file, when starting a new session from SLiM.<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 {{Codeline|current_theme}} variable as a comma separated list to specify a set from which to choose. Selection is random.<br />
<br />
===Move the whole session to another VT===<br />
Lets say you have commented out tty terminals 3-6 as you may not use them. (You may use screen and therefore only need one terminal)<br />
So, to move the X-Server you need to change one number in the {{Filename|/etc/slim.conf}} file. Just a few lines down you should see:<br />
xserver_arguments -nolisten tcp vt07<br />
<br />
Simply change the vt07 to lets say vt03 as there is no agetty started there.<br />
<br />
=== Automatically mount your encrypted /home on login ===<br />
<br />
You can use [[Pam_mount#Slim|pam_mount]].<br />
<br />
== All Slim Options ==<br />
Here is a list of all the slim configuration options and their default values.<br />
<br />
{{Note|welcome_msg allows 2 variables '''%host''' and '''%domain'''<br>sessionstart_cmd allows '''%user''' ''(execd right before login_cmd)'' and it is also allowed in sessionstop_cmd<br>login_cmd allows '''%session''' and '''%theme'''}}<br />
<br />
{| class="wikitable collapsible collapsable collapsed"<br />
|-<br />
! Option Name || Default Value<br />
|-<br />
| default_path ||{{Codeline|/bin:/usr/bin:/usr/local/bin}}<br />
|-<br />
| default_xserver ||{{Codeline|/usr/bin/X}}<br />
|-<br />
| xserver_arguments ||{{Codeline|vt07 -auth /var/run/slim.auth}}<br />
|-<br />
| numlock ||<br />
|-<br />
| daemon || {{Codeline|yes}}<br />
|-<br />
| xauth_path ||{{Codeline|/usr/bin/xauth}}<br />
|-<br />
| login_cmd ||{{Codeline|exec /bin/bash -login ~/.xinitrc %session}}<br />
|-<br />
| halt_cmd ||{{Codeline|/sbin/shutdown -h now}}<br />
|-<br />
| reboot_cmd ||{{Codeline|/sbin/shutdown -r now}}<br />
|-<br />
| suspend_cmd ||<br />
|-<br />
| sessionstart_cmd ||<br />
|-<br />
| sessionstop_cmd ||<br />
|-<br />
| console_cmd ||{{Codeline|/usr/bin/xterm -C -fg white -bg black +sb -g %dx%d+%d+%d -fn %dx%d -T }}<br />
|-<br />
| screenshot_cmd ||{{Codeline|import -window root /slim.png}}<br />
|-<br />
| welcome_msg ||{{Codeline|Welcome to %host}}<br />
|-<br />
| session_msg ||{{Codeline|Session:}}<br />
|-<br />
| default_user ||<br />
|-<br />
| focus_password ||{{Codeline|no}}<br />
|-<br />
| auto_login ||{{Codeline|no}}<br />
|-<br />
| current_theme ||{{Codeline|default}}<br />
|-<br />
| lockfile ||{{Codeline|/var/run/slim.lock}}<br />
|-<br />
| logfile ||{{Codeline|/var/log/slim.log}}<br />
|-<br />
| authfile ||{{Codeline|/var/run/slim.auth}}<br />
|-<br />
| shutdown_msg ||{{Codeline|The system is halting...}}<br />
|-<br />
| reboot_msg ||{{Codeline|The system is rebooting...}}<br />
|-<br />
| sessions ||{{Codeline|wmaker,blackbox,icewm}}<br />
|-<br />
| sessiondir ||<br />
|-<br />
| hidecursor ||{{Codeline|false}}<br />
|-<br />
| input_panel_x ||{{Codeline|50%}}<br />
|-<br />
| input_panel_y ||{{Codeline|40%}}<br />
|-<br />
| input_name_x ||{{Codeline|200}}<br />
|-<br />
| input_name_y ||{{Codeline|154}}<br />
|-<br />
| input_pass_x ||{{Codeline|-1}}<br />
|-<br />
| input_pass_y ||{{Codeline|-1}}<br />
|-<br />
| input_font ||{{Codeline|1=Verdana:size=11}}<br />
|-<br />
| input_color ||{{Codeline|#000000}}<br />
|-<br />
| input_cursor_height ||{{Codeline|20}}<br />
|-<br />
| input_maxlength_name ||{{Codeline|20}}<br />
|-<br />
| input_maxlength_passwd ||{{Codeline|20}}<br />
|-<br />
| input_shadow_xoffset ||{{Codeline|0}}<br />
|-<br />
| input_shadow_yoffset ||{{Codeline|0}}<br />
|-<br />
| input_shadow_color ||{{Codeline|#FFFFFF}}<br />
|-<br />
| welcome_font ||{{Codeline|1=Verdana:size=14}}<br />
|-<br />
| welcome_color ||{{Codeline|#FFFFFF}}<br />
|-<br />
| welcome_x ||{{Codeline|-1}}<br />
|-<br />
| welcome_y ||{{Codeline|-1}}<br />
|-<br />
| welcome_shadow_xoffset ||{{Codeline|0}}<br />
|-<br />
| welcome_shadow_yoffset ||{{Codeline|0}}<br />
|-<br />
| welcome_shadow_color ||{{Codeline|#FFFFFF}}<br />
|-<br />
| intro_msg ||<br />
|-<br />
| intro_font ||{{Codeline|1=Verdana:size=14}}<br />
|-<br />
| intro_color ||{{Codeline|#FFFFFF}}<br />
|-<br />
| intro_x ||{{Codeline|-1}}<br />
|-<br />
| intro_y ||{{Codeline|-1}}<br />
|-<br />
| background_style ||{{Codeline|stretch}}<br />
|-<br />
| background_color ||{{Codeline|#CCCCCC}}<br />
|-<br />
| username_font ||{{Codeline|1=Verdana:size=12}}<br />
|-<br />
| username_color ||{{Codeline|#FFFFFF}}<br />
|-<br />
| username_x ||{{Codeline|-1}}<br />
|-<br />
| username_y ||{{Codeline|-1}}<br />
|-<br />
| username_msg ||{{Codeline|Please enter your username}}<br />
|-<br />
| username_shadow_xoffset ||{{Codeline|0}}<br />
|-<br />
| username_shadow_yoffset ||{{Codeline|0}}<br />
|-<br />
| username_shadow_color ||{{Codeline|#FFFFFF}}<br />
|-<br />
| password_x ||{{Codeline|-1}}<br />
|-<br />
| password_y ||{{Codeline|-1}}<br />
|-<br />
| password_msg ||{{Codeline|Please enter your password}}<br />
|-<br />
| msg_color ||{{Codeline|#FFFFFF}}<br />
|-<br />
| msg_font ||{{Codeline|1=Verdana:size=16:bold}}<br />
|-<br />
| msg_x ||{{Codeline|40}}<br />
|-<br />
| msg_y ||{{Codeline|40}}<br />
|-<br />
| msg_shadow_xoffset ||{{Codeline|0}}<br />
|-<br />
| msg_shadow_yoffset ||{{Codeline|0}}<br />
|-<br />
| msg_shadow_color ||{{Codeline|#FFFFFF}}<br />
|-<br />
| session_color ||{{Codeline|#FFFFFF}}<br />
|-<br />
| session_font ||{{Codeline|1=Verdana:size=16:bold}}<br />
|-<br />
| session_x ||{{Codeline|50%}}<br />
|-<br />
| session_y ||{{Codeline|90%}}<br />
|-<br />
| session_shadow_xoffset ||{{Codeline|0}}<br />
|-<br />
| session_shadow_yoffset ||{{Codeline|0}}<br />
|-<br />
| session_shadow_color ||{{Codeline|#FFFFFF}}<br />
|}<br />
<br />
== Resources ==<br />
<br />
* [http://slim.berlios.de/ SLiM homepage]<br />
* [http://slim.berlios.de/manual.php SLiM documentation]</div>Synorgyhttps://wiki.archlinux.org/index.php?title=AUR_helpers&diff=125404AUR helpers2010-12-15T20:25:15Z<p>Synorgy: </p>
<hr />
<div>[[Category:Utilities (English)]]<br />
[[Category:AUR (English)]]<br />
[[Category:Package management (English)]]<br />
This is a list of helper utilities that search and/or build packages from the [[Arch User Repository]]. '''None of these tools are officially supported.'''<br />
<br />
A list of graphical pacman front-ends, some of which also work with the AUR, may be found at [[pacman GUI Frontends]].<br />
<br />
== List of Helpers ==<br />
=== arson ===<br />
<br />
Arson is an AUR searcher and downloader, written in Ruby. It allows you to search the AUR for a package you want, and download it. It does NOT automatically install the downloaded package. It can extract it, but not install. Searching for a package also searches through pacman's database cache (rather than going to each mirror and querying those).<br />
<br />
*Website: http://evaryont.github.com/arson<br />
*Package: http://aur.archlinux.org/packages.php?ID=16021<br />
<br />
=== aurbuild ===<br />
<br />
aurbuild is a tool to download and build packages from the AUR.<br />
<br />
*Website: http://aurbuild.berlios.de/<br />
*Package: http://aur.archlinux.org/packages.php?ID=1775<br />
<br />
=== aurget ===<br />
<br />
Aurget aims to be a simple, pacman-like interface to the AUR. It tries to make the AUR convenient; whether the user wishes to find, download, build, install, or update AUR packages quickly. Aurget does not wrap any pure pacman commands, this is by design.<br />
<br />
*Website: http://pbrisbin.com/posts/aurget/<br />
*Package: http://aur.archlinux.org/packages.php?ID=31933<br />
<br />
=== aurora ===<br />
<br />
Aurora is a very simple frontend for the AUR written in python3. It allows the user to install AUR packages, download the AUR packages (for manual installation) and also offers an AUR upgrade feature. By design, aurora does not wrap pacman.<br />
<br />
*Website: http://bitbucket.org/bbenne10/aurora<br />
*Package: http://aur.archlinux.org/packages.php?ID=41732<br />
<br />
=== aurpac ===<br />
<br />
Light'n'fast AUR and pacman frontend.<br />
<br />
*Website: http://3ed.jogger.pl/2009/02/15/aurpac/<br />
*Package: http://aur.archlinux.org/packages.php?ID=23919<br />
<br />
=== aurploader ===<br />
<br />
Aurploader prompts the user for an AUR username and password and will then upload PKGBUILD tarballs to the AUR. Before uploading each package, the user is prompted to select a category. When the uploads have completed, the user is asked if the cookie file should be kept so that the script can be run again without needing the AUR username and password to be re-entered.<br />
<br />
*Website: http://xyne.archlinux.ca/info/aurploader<br />
*Package: http://aur.archlinux.org/packages.php?ID=23393<br />
<br />
=== aursh ===<br />
<br />
AurShell is a shell like application written in Python. With plugins included, it's possible to build and install packages from AUR, ABS, and even wrap pacman.<br />
<br />
*Website: http://github.com/husio/aursh/<br />
*Package: http://aur.archlinux.org/packages.php?ID=33423<br />
<br />
=== autoaur ===<br />
<br />
autoaur is a script for automatic mass downloading, updating, building, and installing groups of AUR packages.<br />
<br />
*Website: http://wiki.archlinux.org/index.php/autoaur<br />
*Package: http://aur.archlinux.org/packages.php?ID=6390<br />
<br />
=== bauerbill ===<br />
<br />
Bauerbill is an extension of [http://xyne.archlinux.ca/info/powerpill Powerpill] that supports downloading and building packages from ABS, the AUR, CPAN and Hackage. It supports download acceleration via parallel and segmented downloads, including for source files when building packages.<br />
<br />
*Website: http://xyne.archlinux.ca/projects/bauerbill<br />
*Package: http://aur.archlinux.org/packages.php?ID=33511<br />
<br />
=== burp ===<br />
<br />
burp is a fast and simple AUR uploader written in C. Supports persistent cookies for seamless logins.<br />
<br />
*Website: http://github.com/falconindy/burp<br />
*Package: http://aur.archlinux.org/packages.php?ID=37216<br />
<br />
=== clyde ===<br />
<br />
Clyde is a next-generation libalpm/makepkg wrapper with AUR support, multithreaded downloading, and colorized output.<br />
<br />
*Website: http://clyde.archuser.com/ (Forum: http://bbs.archlinux.org/viewtopic.php?id=91860)<br />
*Package: http://aur.archlinux.org/packages.php?ID=34686<br />
<br />
=== cower ===<br />
<br />
Cower is a fast and simple AUR search and download agent, which will also check for updates and download dependencies. Written in C.<br />
<br />
*Website: http://github.com/falconindy/cower<br />
*Package: http://aur.archlinux.org/packages.php?ID=35822<br />
<br />
=== haskell-archlinux ===<br />
<br />
haskell-archlinux is a library to programmatically access the AUR and package metadata from the Haskell programming language.<br />
<br />
*Website: http://hackage.haskell.org/package/archlinux<br />
*Package: http://aur.archlinux.org/packages.php?ID=29267<br />
<br />
=== makeaur ===<br />
<br />
Makeaur is a wrapper for pacman and makepkg that allows users to easily install packages from the Arch User Repository.<br />
<br />
*Website: http://github.com/ghost1227/makeaur/<br />
*Package: http://aur.archlinux.org/packages.php?ID=23678<br />
<br />
=== makerepo ===<br />
<br />
Makerepo is a tool to simplify building and maintaining a repository. A simple configuration file is use to specify the basic arguments such as database name and directory, package lists, etc. Makerepo is able to build packages from the AUR and from local PKGBUILDs such as the ABS tree. It can even build packages from CPAN modules if pacpan is installed.<br />
<br />
*Website: http://xyne.archlinux.ca/info/makerepo<br />
*Package: http://aur.archlinux.org/packages.php?ID=23500<br />
<br />
=== packer ===<br />
<br />
Packer is a bash wrapper for pacman and the AUR. It was designed to be a simple and very fast replacement for the basic functionality of Yaourt. It has commands to install, update, search, and show information for any package in the main repositories and in the AUR. Use pacman for other commands, such as removing a package. It is fully functional.<br />
<br />
*Website: http://github.com/bruenig/packer (Forum: http://bbs.archlinux.org/viewtopic.php?id=88115)<br />
*Package: http://aur.archlinux.org/packages.php?ID=33378<br />
<br />
=== pacmoon ===<br />
<br />
pacmoon is a script for compiling arch linux packages from the AUR and repositories. It can automatically install make dependencies as binaries when necessary and update the entire system or just packages listed. It keeps track of which files have been compiled so that in the event of compiled packages getting replaced with a binary (like during an upgrade process) then pacmoon can recompile only the necessary packages.<br />
<br />
*Website: http://chilon.net/pacmoon<br />
*Package: http://aur.archlinux.org/packages.php?ID=41911<br />
<br />
=== paktahn ===<br />
<br />
Paktahn is a yaourt replacement written from the ground-up using Lisp. It is under active development and already includes improvements such as a local cache for fast searches and interactive installation.<br />
<br />
*Website: http://github.com/skypher/paktahn (Forum: http://bbs.archlinux.org/viewtopic.php?id=77674&p=1)<br />
*Package: http://aur.archlinux.org/packages.php?ID=30242<br />
<br />
=== pbfetch ===<br />
<br />
Pbfetch is a script which can be used as a pacman-independent AUR helper or a pacman wrapper with additional AUR functionality. Pbfetch aims to be a simple and fast versus the well established yaourt.<br />
Pbfetch can be used as a shortcut to simply download PKGBUILDs from AUR or automatically build with dependency resolution among other things. The user can select which AUR packages to upgrade using a simple menu as well as update all AUR packages.<br />
<br />
*Website/Source: https://github.com/dalingrin/pbfetch<br />
*Forum: https://bbs.archlinux.org/viewtopic.php?id=87789<br />
*Package: http://aur.archlinux.org/packages.php?ID=33256<br />
<br />
=== pbget ===<br />
<br />
Pbget is a simple command-line tool for retrieving PKGBUILDs and local source files for Arch Linux. It is able to retrieve files from the official SVN and CVS web interface, the AUR and the ABS rsync server.<br />
<br />
*Website: http://xyne.archlinux.ca/info/pbget<br />
*Package: http://aur.archlinux.org/packages.php?ID=23848<br />
<br />
=== pkgman ===<br />
<br />
pkgman is a bash script which helps to manage a local repository. It retrieves the PKGBUILD and related files for given name from ABS or AUR and lets you edit them, automatically generates checksums, backs up the source tarball, builds and adds the package to your local repository. Then you can install it as usual with pacman. It also has AUR support for submitting tarballs and leaving comments.<br />
<br />
*Website: http://sourceforge.net/apps/mediawiki/pkgman/index.php (Forum: http://bbs.archlinux.org/viewtopic.php?id=49023)<br />
*Package: http://aur.archlinux.org/packages.php?ID=17100<br />
<br />
=== qpkg ===<br />
<br />
qpkg is a tool written in python for searching in all known repositories and on AUR. It can install and automatically update packages from AUR and it also can install all needed dependencies of a package from AUR.<br />
<br />
*Website: http://qpkg.berlios.de/<br />
*Package: http://developer.berlios.de/project/showfiles.php?group_id=4501<br />
<br />
=== slurpy ===<br />
<br />
slurpy is an AUR helper written in python for searching AUR, downloading packages, showing information about packages, checking for updates and uploading a package to AUR. <br />
<br />
*Website: http://rsontech.net/projects/slurpy/<br />
*Package: http://aur.archlinux.org/packages.php?ID=28285<br />
<br />
=== srcman ===<br />
<br />
srcman is a pacman/makepkg wrapper written in Bash, which transparently handles pacman operations on 'source packages'. This means, for example, that packages can be specified for installation either explicitly (pacman's -U operation) or can be installed from a (source) repository (-S operation). The address of an AUR pacman database can be found in the corresponding forum thread, by the way.<br />
The primary goal of this project is to provide a complete pacman wrapper and therefore, srcman supports all current pacman operations for binary ''and'' source packages.<br />
<br />
*Website: http://bbs.archlinux.org/viewtopic.php?id=65501<br />
*Package: http://aur.archlinux.org/packages.php?ID=23945<br />
<br />
=== tupac ===<br />
<br />
tupac is a pacman/yaourt wrapper written in PHP. The main difference between tupac and the rest of tupac wrappers is that it caches the local package database, so it gives you really fast operatibility even in environments with low resources (low RAM, slow disks). It also gives you two advanced features: checking for missing installed files and checking for files that are not owned by any package.<br />
<br />
*Package: http://aur.archlinux.org/packages.php?ID=13322<br />
<br />
=== yaourt ===<br />
<br />
[[Yaourt]] (Yet Another User Repository Tool) is a community-contributed wrapper for pacman which adds seamless access to the AUR, allowing and automating package compilation and installation from your choice of the thousands of PKGBUILDs in the AUR, in addition to the many thousands of available Arch binary packages. Yaourt uses the same exact syntax as pacman, which saves you from relearning an entirely new method of system maintenance, but also adds new options. Yaourt expands the power and simplicity of pacman by adding even more useful features and provides pleasing, colorized output, interactive search mode, and much more.<br />
<br />
*Website: http://archlinux.fr/yaourt-en<br />
*Package: http://aur.archlinux.org/packages.php?ID=5863<br />
<br />
== Comparison Table ==<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
! Program !! Written in !! Dependency Support !! Core/extra/community support !! Actively Developed !! Usage <br />
|-<br />
! [[#aursh|AurShell]]<br />
| Python || No || No || Yes, as aursh || aursh (runs Aurshell program, wherein a number of different commands can be used)<br />
|-<br />
! [[#aurora|Aurora]]<br />
| Python3 || Basic (with makepkg) || No || Yes || see aurora --help<br />
|-<br />
! [[#bauerbill|Bauerbill]]<br />
| Perl || Yes || Yes || Yes || Identical to pacman (e.g., bauerbill -S <pkgname>)<br />
|-<br />
! [[#clyde|Clyde]]<br />
| Lua|| Yes || Yes || Yes || Identical to pacman (e.g., clyde -S <pkgname>)<br />
|-<br />
! [[#makeaur|Makeaur]]<br />
| Bash || No || No || Has been forked || makeaur <pkgname> <br />
|-<br />
! [[#packer|Packer]]<br />
| Bash || Yes || Yes || Yes || <tt>packer -Ss</tt> ''package'' (See <tt>packer -h</tt>)<br />
|-<br />
! [[#pacmoon|pacmoon]]<br />
| Zsh|| Yes || Yes || Yes || Similar to emerge from portage e.g. pacmoon -av <pkgname><br />
|-<br />
! [[#paktahn|Paktahn]]<br />
| Lisp|| Yes || Yes || Yes || Identical to pacman (e.g., pak -S <pkgname>)<br />
|-<br />
! [[#pbfetch|pbfetch]]<br />
| Bash || Yes || Yes || Yes || Identical to pacman, and/or AUR specifc arguments (additional arguments for PKGBUILD editing, etc)<br />
|-<br />
! [[#tupac|tupac]]<br />
| PHP || Yes || Yes || Yes || Identical to pacman (e.g., tupac -S <pkgname>)<br />
|-<br />
! [[#yaourt|Yaourt]]<br />
| Bash, back-end in C || Yes || Yes || Yes || Identical to pacman (e.g., yaourt -S <pkgname>)<br />
|-<br />
! [[#aurget|Aurget]]<br />
| Bash || Yes || No || Yes || see <tt>aurget --help</tt><br />
|}</div>Synorgyhttps://wiki.archlinux.org/index.php?title=DVD_Burning&diff=123163DVD Burning2010-11-30T23:42:49Z<p>Synorgy: </p>
<hr />
<div>[[Category:Utilities (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|DVD Burning}}<br />
{{Article summary start}}<br />
{{Article summary text|An overview of DVD writing tools and methods.}}<br />
{{Article summary heading|Series}}<br />
{{Article summary wiki|DVD Playing}}<br />
{{Article summary wiki|DVD Ripping}}<br />
{{Article summary wiki|DVD Burning}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|CD Burning Tips}}<br />
{{Article summary end}}<br />
<br />
Writing (or "burning") DVDs requires a different approach than burning CDs. DVDs offer much higher capacities, and the standard CD writing tools will not suffice.<br />
<br />
This HOWTO covers a narrow scope for now: writing data onto DVDs using the command line.<br />
<br />
==Required packages==<br />
# You still need the standard CD writing tools known as {{Package AUR|cdrtools}} (which can be replaced by {{Package Official|cdrkit}}, if desired).<br />
# You also need the new DVD writing tools known as [http://www.archlinux.org/packages/extra/i686/dvd+rw-tools/ <tt>dvd+rw-tools</tt>], found in the [extra] repository.<br />
<br />
{{Note|Do not install the package known as {{Package Official|dvdrtools}}. It conflicts with {{Package AUR|cdrtools}}, and [http://www.archlinux.org/packages/extra/i686/dvd+rw-tools/ <tt>dvd+rw-tools</tt>] is the superior DVD writing package.}}<br />
<br />
{{Tip|If you wish to use a graphical front-end, install {{Package Official|k3b}} or {{Package Official|brasero}} and you need to read no further.}}<br />
<br />
==Procedure==<br />
This HOWTO will use the command {{Codeline|growisofs}} from the [http://www.archlinux.org/packages/extra/i686/dvd+rw-tools/ <tt>dvd+rw-tools</tt>] package. If you've ever written CDs from the command line before, you'll know the process of first creating an iso9660 file ({{Codeline|mkisofs}}), and then burning it to CD ({{Codeline|cdrecord}}). {{Codeline|growisofs}} merges these steps, so you don't need extra storage space for the ISO file anymore. Another advantage is that multisession writing has been simplified.<br />
<br />
===Overview===<br />
Essentially, writing a '''new''' DVD follows this procedure:<br />
$ growisofs -Z /dev/cdrw -r -J /path/to/files<br />
<br />
where {{Filename|/dev/cdrw}} is your DVD writer device.<br />
<br />
To '''continue''' a DVD (write an additional session) you use:<br />
$ growisofs -M /dev/cdrw -r -J /path/to/files<br />
<br />
To burn an ISO '''image''' to disc use:<br />
$ growisofs -Z -dvd-compat /dev/cdrw=/path/to/iso<br />
{{Note|I actually had to reverse the order of the {{codeline|-Z}} and {{codeline|-dvd-compat}} arguments to get the above tip to work.}}<br />
<br />
To create a video dvd use the following (NOTE: rather than using /dev/srN directly, consider /dev/dvdN or even just plain /dev/dvd):<br />
$ growisofs -Z /dev/sr0 -dvd-video /path/to/video<br />
<br />
; {{Codeline|-Z}}: start at the beginning of the DVD using the following device<br />
; {{Codeline|-M}}: start after the last session on the disc using the following device<br />
; {{Codeline|-r}}: [[Wikipedia:Rock Ridge|Rock Ridge]] support with sane permission settings (recommended, extended UNIX info)<br />
; {{Codeline|-J}}: [[Wikipedia:Joliet (file system)|Joliet]] support (recommended, extended info for Windows NT and Windows 95)<br />
<br />
{{Note|{{Codeline|-r}} will choose different permissions than the real ones; to use the exact permissions use {{Codeline|-R}} instead. See the man page of {{Codeline|mkisofs}} for more information.}}<br />
<br />
{{Tip|1=If you want to copy an existing DVD, one way that works is to make an ISO using {{Codeline|readcd}}:<br />
$ readcd -v dev=/dev/cdrw -f image.iso<br />
<br />
as per [[CD Burning Tips]], then use the {{Codeline|growisofs}} example above to burn the ISO to a new blank disc.}}<br />
<br />
===Example===<br />
<br />
Although the above might suffice for you, some users require extra settings to successfully write DVDs.<br />
<br />
A simple DVD writing template:<br />
$ growisofs -Z /dev/cdrw -v -l -dry-run -iso-level 3 -R -J -speed=2 -joliet-long -graft-points /files/=/path/to/files/<br />
<br />
; {{Codeline|-Z}}: as seen above, this starts a new DVD; to continue a multisession DVD, use {{Codeline|-M}}<br />
; {{Codeline|-v}}: increase verbosity level (more output)<br />
; {{Codeline|-l}}: breaks DOS compatibility but allows for longer filenames<br />
; {{Codeline|-dry-run}}: simulate writing (remove this flag if you are sure that everything is set up correctly)<br />
; {{Codeline|-iso-level 3}}: defines how strict you want to adhere to the iso9660 standard ({{Codeline|-iso-level 1}} is very strict while {{Codeline|-iso-level 4}} is very loose)<br />
; {{Codeline|-R}}: see above<br />
; {{Codeline|-J}}: see above<br />
; {{Codeline|1=-speed=2}}: start burning at 2X speed<br />
; {{Codeline|-joliet-long}}: allows longer Joliet file names<br />
<br />
The final part needs more explanation:<br />
-graft-points /files/=/path/to/files/<br />
<br />
This specifies that files will be stored in the subdirectory {{Filename|/files}} rather than the DVD root. See the {{Codeline|mkisofs}} manual for details.<br />
<br />
{{Note|{{Codeline|growisofs}} is basically just a front-end to {{Codeline|mkisofs}}. That means that any option for {{Codeline|mkisofs}} also works with {{Codeline|growisofs}}. See the {{Codeline|mkisofs}} man page for details.}}<br />
<br />
==Re-writable DVDs==<br />
<br />
The process for burning re-writable discs is almost the same as for normal DVDs. However, keep in mind that virgin DVD+RW media needs to be initially formatted ("blanked") prior to usage. Blanking can be done using the program {{Codeline|dvd+rw-format}} like this:<br />
$ dvd+rw-format /dev/cdrw<br />
<br />
where {{Filename|/dev/cdrw}} is your DVD writer device.<br />
<br />
==Troubleshooting==<br />
<br />
===Permission denied===<br />
<br />
If you encounter the a permission error, ensure you are a member of the [[Groups|group]] "optical":<br />
# usermod -aG optical username<br />
<br />
after which you will have to logoff and -on. <br />
<br />
{{Note|{{Codeline|growisofs}} will not run via sudo.}}</div>Synorgyhttps://wiki.archlinux.org/index.php?title=DVD_Burning&diff=123162DVD Burning2010-11-30T23:41:03Z<p>Synorgy: </p>
<hr />
<div>[[Category:Utilities (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|DVD Burning}}<br />
{{Article summary start}}<br />
{{Article summary text|An overview of DVD writing tools and methods.}}<br />
{{Article summary heading|Series}}<br />
{{Article summary wiki|DVD Playing}}<br />
{{Article summary wiki|DVD Ripping}}<br />
{{Article summary wiki|DVD Burning}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|CD Burning Tips}}<br />
{{Article summary end}}<br />
<br />
Writing (or "burning") DVDs requires a different approach than burning CDs. DVDs offer much higher capacities, and the standard CD writing tools will not suffice.<br />
<br />
This HOWTO covers a narrow scope for now: writing data onto DVDs using the command line.<br />
<br />
==Required packages==<br />
# You still need the standard CD writing tools known as {{Package AUR|cdrtools}} (which can be replaced by {{Package Official|cdrkit}}, if desired).<br />
# You also need the new DVD writing tools known as [http://www.archlinux.org/packages/extra/i686/dvd+rw-tools/ <tt>dvd+rw-tools</tt>], found in the [extra] repository.<br />
<br />
{{Note|Do not install the package known as {{Package Official|dvdrtools}}. It conflicts with {{Package AUR|cdrtools}}, and [http://www.archlinux.org/packages/extra/i686/dvd+rw-tools/ <tt>dvd+rw-tools</tt>] is the superior DVD writing package.}}<br />
<br />
{{Tip|If you wish to use a graphical front-end, install {{Package Official|k3b}} or {{Package Official|brasero}} and you need to read no further.}}<br />
<br />
==Procedure==<br />
This HOWTO will use the command {{Codeline|growisofs}} from the [http://www.archlinux.org/packages/extra/i686/dvd+rw-tools/ <tt>dvd+rw-tools</tt>] package. If you've ever written CDs from the command line before, you'll know the process of first creating an iso9660 file ({{Codeline|mkisofs}}), and then burning it to CD ({{Codeline|cdrecord}}). {{Codeline|growisofs}} merges these steps, so you don't need extra storage space for the ISO file anymore. Another advantage is that multisession writing has been simplified.<br />
<br />
===Overview===<br />
Essentially, writing a '''new''' DVD follows this procedure:<br />
$ growisofs -Z /dev/cdrw -r -J /path/to/files<br />
<br />
where {{Filename|/dev/cdrw}} is your DVD writer device.<br />
<br />
To '''continue''' a DVD (write an additional session) you use:<br />
$ growisofs -M /dev/cdrw -r -J /path/to/files<br />
<br />
To burn an ISO '''image''' to disc use:<br />
$ growisofs -Z -dvd-compat /dev/cdrw=/path/to/iso<br />
{{Note|I actually had to reverse the order of the {{codeline|-Z}} and {{codeline|-dvd-compat}} arguments to get this to work}}<br />
<br />
To create a video dvd use the following (NOTE: rather than using /dev/srN directly, consider /dev/dvdN or even just plain /dev/dvd):<br />
$ growisofs -Z /dev/sr0 -dvd-video /path/to/video<br />
<br />
; {{Codeline|-Z}}: start at the beginning of the DVD using the following device<br />
; {{Codeline|-M}}: start after the last session on the disc using the following device<br />
; {{Codeline|-r}}: [[Wikipedia:Rock Ridge|Rock Ridge]] support with sane permission settings (recommended, extended UNIX info)<br />
; {{Codeline|-J}}: [[Wikipedia:Joliet (file system)|Joliet]] support (recommended, extended info for Windows NT and Windows 95)<br />
<br />
{{Note|{{Codeline|-r}} will choose different permissions than the real ones; to use the exact permissions use {{Codeline|-R}} instead. See the man page of {{Codeline|mkisofs}} for more information.}}<br />
<br />
{{Tip|1=If you want to copy an existing DVD, one way that works is to make an ISO using {{Codeline|readcd}}:<br />
$ readcd -v dev=/dev/cdrw -f image.iso<br />
<br />
as per [[CD Burning Tips]], then use the {{Codeline|growisofs}} example above to burn the ISO to a new blank disc.}}<br />
<br />
===Example===<br />
<br />
Although the above might suffice for you, some users require extra settings to successfully write DVDs.<br />
<br />
A simple DVD writing template:<br />
$ growisofs -Z /dev/cdrw -v -l -dry-run -iso-level 3 -R -J -speed=2 -joliet-long -graft-points /files/=/path/to/files/<br />
<br />
; {{Codeline|-Z}}: as seen above, this starts a new DVD; to continue a multisession DVD, use {{Codeline|-M}}<br />
; {{Codeline|-v}}: increase verbosity level (more output)<br />
; {{Codeline|-l}}: breaks DOS compatibility but allows for longer filenames<br />
; {{Codeline|-dry-run}}: simulate writing (remove this flag if you are sure that everything is set up correctly)<br />
; {{Codeline|-iso-level 3}}: defines how strict you want to adhere to the iso9660 standard ({{Codeline|-iso-level 1}} is very strict while {{Codeline|-iso-level 4}} is very loose)<br />
; {{Codeline|-R}}: see above<br />
; {{Codeline|-J}}: see above<br />
; {{Codeline|1=-speed=2}}: start burning at 2X speed<br />
; {{Codeline|-joliet-long}}: allows longer Joliet file names<br />
<br />
The final part needs more explanation:<br />
-graft-points /files/=/path/to/files/<br />
<br />
This specifies that files will be stored in the subdirectory {{Filename|/files}} rather than the DVD root. See the {{Codeline|mkisofs}} manual for details.<br />
<br />
{{Note|{{Codeline|growisofs}} is basically just a front-end to {{Codeline|mkisofs}}. That means that any option for {{Codeline|mkisofs}} also works with {{Codeline|growisofs}}. See the {{Codeline|mkisofs}} man page for details.}}<br />
<br />
==Re-writable DVDs==<br />
<br />
The process for burning re-writable discs is almost the same as for normal DVDs. However, keep in mind that virgin DVD+RW media needs to be initially formatted ("blanked") prior to usage. Blanking can be done using the program {{Codeline|dvd+rw-format}} like this:<br />
$ dvd+rw-format /dev/cdrw<br />
<br />
where {{Filename|/dev/cdrw}} is your DVD writer device.<br />
<br />
==Troubleshooting==<br />
<br />
===Permission denied===<br />
<br />
If you encounter the a permission error, ensure you are a member of the [[Groups|group]] "optical":<br />
# usermod -aG optical username<br />
<br />
after which you will have to logoff and -on. <br />
<br />
{{Note|{{Codeline|growisofs}} will not run via sudo.}}</div>Synorgyhttps://wiki.archlinux.org/index.php?title=AUR_Cleanup_Day/2010&diff=42853AUR Cleanup Day/20102008-06-10T23:03:45Z<p>Synorgy: /* Package List */</p>
<hr />
<div>'''NOTE: TU's are currently working through the list'''. You can still add packages but please check the whole page first.<br />
<br />
<br />
The AUR has a large number of obsolete packages which could use cleaning up. Examples of packages that may be cleaned up are:<br />
*packages that have been renamed or replaced<br />
*old and unmaintained developmental (cvs/svn/etc) packages<br />
<br />
Post suggestions of packages on this pages. Trusted Users will get together and go though the list in a couple of weeks and confirm which packages should be removed. '''Please DO NOT REMOVE suggestions from the wiki page but add a comment on why it should be kept instead.''' TUs will not delete any useful package.<br />
<br />
==Package List==<br />
'''Add new packages here''' - check for the package in the sorted lists below before adding<br />
<br />
* [http://aur.archlinux.org/packages.php?ID=13014 advi] - seems to be unmaintainable for the following reasons<br />
** The newest version 1.7.3 needs camlimages 3.0.0, which cannot be found on the net<br />
** camlimages' cvs-sources do not compile<br />
** package advi 1.6.0 has a patchfile of 102k size<br />
* [http://aur.archlinux.org/packages.php?ID=9026 audacious-docklet] - Doesnt work with latest audacious, not needed anymore either<br />
* [http://aur.archlinux.org/packages.php?ID=1731 ecamegapedal] - Do not to compile.<br />
* [http://aur.archlinux.org/packages.php?ID=4493 eclipse-kde] - Dead<br />
* [http://aur.archlinux.org/packages.php?ID=3698 galeon] - doesn't compile (not even the latest version)<br />
* [http://aur.archlinux.org/packages.php?ID=6069 gnuserv] - Deprecated in emacs-22+<br />
* [http://aur.archlinux.org/packages.php?ID=5207 gshare] - The package didn't function for me with the latest gnome. Furthermore it looks like this project is dead (website is down, source is no longer available)<br />
* [http://aur.archlinux.org/packages.php?ID=7942 gpsutil] - URL is not available, the link to gpsutil on the gpsbabel page is dead too.<br />
* [http://aur.archlinux.org/packages.php?ID=3689 ii-hg] - outdated, probably discontinued as the project website isn't available anymore (moved maybe?)<br />
** The project website is available at http://www.suckless.org/wiki/tools/irc/irc_it, so it's not dead. It only needs some changes to work again. --[[User:CuleX|CuleX]]<br />
* [http://aur.archlinux.org/packages.php?ID=7884 jfduke3d] - Is not updated by his author anymore, [http://aur.archlinux.org/packages.php?ID=15513 eduke32] was made to remplace it<br />
* [http://aur.archlinux.org/packages.php?ID=7037 kanola] - probably dead project, didn't went past the 0.0.1 release since 2006<br />
* [http://aur.archlinux.org/packages.php?ID=3429 lam 7.1.3-1] - Doesn't compile and is orphaned. The successor openmpi works.<br />
* [http://aur.archlinux.org/packages.php?ID=16889 libqglviewer-latest] - the same package as [http://aur.archlinux.org/packages.php?ID=7801 libqglviewer]<br />
* [http://aur.archlinux.org/packages.php?ID=14220 linuxdcpp-cvs] - Old, orphaned CVS version of a package in community<br />
* [http://aur.archlinux.org/packages.php?ID=7264 mencode] - outdated, tells aur is its homepage<br />
** The package is to install a perl script included in the AUR tarball so it doesn't really have a home page. So it could be kept if the script can still be useful or, at least, the script could be moved to the wiki if there is a page for scripts. --[[User:Snowman|Snowman]]<br />
* [http://aur.archlinux.org/packages.php?ID=5408 mlame] - just a small bash script, no project page, could be moved to the wiki maybe<br />
* [http://aur.archlinux.org/packages.php?ID=11581 mouseemu] - Project not updated since 2006; xautomation also allows mouse emulation.<br />
* [http://aur.archlinux.org/packages.php?ID=11498 mpd-pausemode] - "Website" is orig. contributor's email addr.; orphaned by this contributor, so presumably no longer developed.<br />
* [http://aur.archlinux.org/packages.php?ID=15401 org] - Out of date; also, included in Emacs 22+<br />
* [http://aur.archlinux.org/packages.php?ID=970 netwmpager] - I just orphaned this community package. Home page has disappeared. I think source can still be found on Debian mirrors though. See comments in AUR. It might be wise to move it to unsupported or remove completely unless a TU wants to adopt it. --[[User:Snowman|Snowman]]<br />
* [http://aur.archlinux.org/packages.php?ID=10514 rt61-cvs] - This driver is included in linus's tree and is therefore obsolete<br />
* [http://aur.archlinux.org/packages.php?ID=494 sonic-rainbow] - dead project, does not compile --[[User:Snowman|Snowman]]<br />
* [http://aur.archlinux.org/packages.php?ID=2612 stepmania-bin] - orphan, replaced by [http://aur.archlinux.org/packages.php?ID=5453 stepmania]<br />
* [http://aur.archlinux.org/packages.php?ID=15678 swt-devel] - I only created it to compile tuxguitar against it, but that's not needed. And it seems nobody is using it. <br />
* [http://aur.archlinux.org/packages.php?ID=3947 viki-svn] - old, pkgbuild is broken<br />
* [http://aur.archlinux.org/packages.php?ID=12067 pidgimpd-svn] - This package is orphaned and it doesn't build. There is mpd support in musictracker.<br />
* [http://aur.archlinux.org/packages.php?ID=6686 sizzle] - No upstream maintenance, does not compile.<br />
* [http://aur.archlinux.org/packages.php?ID=15973 weather-wallpaper] - orphaned and references as dep non-existing pymetar<br />
<br />
==TU Working Area==<br />
<br />
'''For editing by TUs only!''' The wiki has a history so do not think you can get away with ignoring this... --[[User:Allan|Allan]]<br />
<br />
===Packages to Remove===<br />
* [http://aur.archlinux.org/packages.php?ID=1926 fvwm-trans] last updated over 2 years ago and replaced with [http://aur.archlinux.org/packages.php?ID=7195 fvwm-patched] in AUR --[[User:pressh|pressh]] (I think one feature that is patched is in fvwm by default now, the other is in fvwm-patched too. If user does not want all the patched they can disable the ones they don't want from fvwm-patched)<br />
* [http://aur.archlinux.org/packages.php?ID=16166 jacman] - Jacman doesn't work correctly with pacman3. --[[User:Partition|Partition]]<br />
* [http://aur.archlinux.org/packages.php?ID=14992 slim-theme-darch] - in archlinux-themes-slim --[[User:Allan|Allan]]<br />
In community:<br />
* [http://aur.archlinux.org/packages.php?ID=12993 ion-modules] - ion3 is not part of official repos anymore, move to AUR --[[User:Allan|Allan]]<br />
* [http://aur.archlinux.org/packages.php?ID=9102 lmctl] - replaced by lomoco --[[User:Allan|Allan]]<br />
* [http://aur.archlinux.org/packages.php?ID=8958 wildfire] - Replaced by openfire. --[[User:pressh|pressh]]<br />
<br />
===Packages to Keep===<br />
* [http://aur.archlinux.org/packages.php?ID=14946 mplayer-w32codecs] - not duplicate package as has more codecs than the "codecs" package.<br />
** Should rename to "codecs-extra" and not provide same files as codecs package --[[User:Allan|Allan]]<br />
<br />
==Remove from Filesystem==<br />
<br />
This is a list of files on the AUR filesystem that have been created when poorly formed packages were uploaded. This is a secondary consideration.<br />
<br />
There are also directories in /packages/ for which the package no longer exists. These probably need to be removed as well. Examples are 4c, 1394commander and 8kingdoms. Also, all the packages that moved to community ALSO still exist here; for example 915resolution. A [http://archlinux.spider007.net/aur-invalid-directories.txt complete list of these directories can be found here]<br />
<br />
<pre><br />
/packages/0verkill-0.16.tar.gz/<br />
/packages/0verkill-0.16/<br />
/packages/2007.02.17-2/<br />
/packages/abakus-0.91-1/<br />
/packages/abakus-0.91.tar.gz/<br />
/packages/abakus-0.91/<br />
/packages/akgregator/<br />
/packages/akregator/<br />
/packages/akregator1.0.2/<br />
/packages/akregator_1.0.2/<br />
/packages/amsn-0.97ec1/<br />
/packages/amsn-0.97rc1/<br />
/packages/amsn-097rc1-1/<br />
/packages/amsn-097rc1/<br />
/packages/amsn-cvs/<br />
/packages/amsn-svn_update/<br />
/packages/amsn096/<br />
/packages/amsn096rc1/<br />
/packages/bashstyle-5.0<br />
/packages/bashstyle-5.0rc1.tar.gz/<br />
/packages/bashstyle-5.0rc1.tar.gz1/<br />
/packages/bashstyle-5.0rc1/<br />
/packages/bashstyle.tar.gz/<br />
/packages/bashstyle-ng/<br />
/packages/bashstyle1/<br />
/packages/braero-svn<br />
/packages/braser-cvs/<br />
/packages/brasero-cvs/<br />
/packages/brasero.svn/<br />
/packages/brlcad-cvs/<br />
/packages/ccd2iso-0.3/<br />
/packages/cdcollect-0.6.0/<br />
/packages/centerim-4.22.2/<br />
/packages/centerim/<br />
/packages/exiftool/exiftool-7.13.tar.gz (/packages/exiftool/exiftool.tar.gz has been uploaded & works)<br />
/packages/ploticus-test/<br />
/packages/test-louipc/<br />
/packages/test/<br />
/packages/test_pkg/<br />
/packages/yacas-1.1.17-2/<br />
/packages/yacas-1.2.2/<br />
/packages/yacas-1.17-2/<br />
/packages/yacas-new/<br />
/packages/yacasnew/<br />
/packages/zzztest/<br />
/packages/zzzztest/<br />
</pre><br />
<br />
==Remove from Filesystem (AUR Bugs)==<br />
<br />
This is a list of files that need to be removed due to AUR bugs as they hinder proper submission and maintenance of packages.<br />
<br />
AUR Bugs<br />
* FS#8672 - http://bugs.archlinux.org/task/8672<br />
<br />
<pre><br />
/packages/advanceutils<br />
/packages/isight-firmware-tools<br />
/packages/mlt-svn<br />
/packages/perl-devel-stacktrace<br />
/packages/psi-qt4<br />
/packages/xcursor-industrial<br />
/packages/zaptel<br />
</pre><br />
<br />
/packages/lib32-dbus is now in community - Allan</div>Synorgyhttps://wiki.archlinux.org/index.php?title=AUR_Cleanup_Day/2010&diff=42852AUR Cleanup Day/20102008-06-10T22:21:30Z<p>Synorgy: /* Package List */</p>
<hr />
<div>'''NOTE: TU's are currently working through the list'''. You can still add packages but please check the whole page first.<br />
<br />
<br />
The AUR has a large number of obsolete packages which could use cleaning up. Examples of packages that may be cleaned up are:<br />
*packages that have been renamed or replaced<br />
*old and unmaintained developmental (cvs/svn/etc) packages<br />
<br />
Post suggestions of packages on this pages. Trusted Users will get together and go though the list in a couple of weeks and confirm which packages should be removed. '''Please DO NOT REMOVE suggestions from the wiki page but add a comment on why it should be kept instead.''' TUs will not delete any useful package.<br />
<br />
==Package List==<br />
'''Add new packages here''' - check for the package in the sorted lists below before adding<br />
<br />
* [http://aur.archlinux.org/packages.php?ID=13014 advi] - seems to be unmaintainable for the following reasons<br />
** The newest version 1.7.3 needs camlimages 3.0.0, which cannot be found on the net<br />
** camlimages' cvs-sources do not compile<br />
** package advi 1.6.0 has a patchfile of 102k size<br />
* [http://aur.archlinux.org/packages.php?ID=9026 audacious-docklet] - Doesnt work with latest audacious, not needed anymore either<br />
* [http://aur.archlinux.org/packages.php?ID=1731 ecamegapedal] - Do not to compile.<br />
* [http://aur.archlinux.org/packages.php?ID=4493 eclipse-kde] - Dead<br />
* [http://aur.archlinux.org/packages.php?ID=3698 galeon] - doesn't compile (not even the latest version)<br />
* [http://aur.archlinux.org/packages.php?ID=6069 gnuserv] - Deprecated in emacs-22+<br />
* [http://aur.archlinux.org/packages.php?ID=5207 gshare] - The package didn't function for me with the latest gnome. Furthermore it looks like this project is dead (website is down, source is no longer available)<br />
* [http://aur.archlinux.org/packages.php?ID=7942 gpsutil] - URL is not available, the link to gpsutil on the gpsbabel page is dead too.<br />
* [http://aur.archlinux.org/packages.php?ID=3689 ii-hg] - outdated, probably discontinued as the project website isn't available anymore (moved maybe?)<br />
** The project website is available at http://www.suckless.org/wiki/tools/irc/irc_it, so it's not dead. It only needs some changes to work again. --[[User:CuleX|CuleX]]<br />
* [http://aur.archlinux.org/packages.php?ID=7884 jfduke3d] - Is not updated by his author anymore, [http://aur.archlinux.org/packages.php?ID=15513 eduke32] was made to remplace it<br />
* [http://aur.archlinux.org/packages.php?ID=7037 kanola] - probably dead project, didn't went past the 0.0.1 release since 2006<br />
* [http://aur.archlinux.org/packages.php?ID=3429 lam 7.1.3-1] - Doesn't compile and is orphaned. The successor openmpi works.<br />
* [http://aur.archlinux.org/packages.php?ID=16889 libqglviewer-latest] - the same package as [http://aur.archlinux.org/packages.php?ID=7801 libqglviewer]<br />
* [http://aur.archlinux.org/packages.php?ID=14220 linuxdcpp-cvs] - Old, orphaned CVS version of a package in community<br />
* [http://aur.archlinux.org/packages.php?ID=7264 mencode] - outdated, tells aur is its homepage<br />
** The package is to install a perl script included in the AUR tarball so it doesn't really have a home page. So it could be kept if the script can still be useful or, at least, the script could be moved to the wiki if there is a page for scripts. --[[User:Snowman|Snowman]]<br />
* [http://aur.archlinux.org/packages.php?ID=5408 mlame] - just a small bash script, no project page, could be moved to the wiki maybe<br />
* [http://aur.archlinux.org/packages.php?ID=11581 mouseemu] - Project not updated since 2006; xautomation also allows mouse emulation.<br />
* [http://aur.archlinux.org/packages.php?ID=11498 mpd-pausemode] - "Website" is orig. contributor's email addr.; orphaned by this contributor, so presumably no longer developed.<br />
* [http://aur.archlinux.org/packages.php?ID=15401 org] - Out of date; also, included in Emacs 22+<br />
* [http://aur.archlinux.org/packages.php?ID=970 netwmpager] - I just orphaned this community package. Home page has disappeared. I think source can still be found on Debian mirrors though. See comments in AUR. It might be wise to move it to unsupported or remove completely unless a TU wants to adopt it. --[[User:Snowman|Snowman]]<br />
* [http://aur.archlinux.org/packages.php?ID=1836 pyosd] - Source is no longer available from listed site, and a google search reveals very little. <br />
* [http://aur.archlinux.org/packages.php?ID=10514 rt61-cvs] - This driver is included in linus's tree and is therefore obsolete<br />
* [http://aur.archlinux.org/packages.php?ID=494 sonic-rainbow] - dead project, does not compile --[[User:Snowman|Snowman]]<br />
* [http://aur.archlinux.org/packages.php?ID=2612 stepmania-bin] - orphan, replaced by [http://aur.archlinux.org/packages.php?ID=5453 stepmania]<br />
* [http://aur.archlinux.org/packages.php?ID=15678 swt-devel] - I only created it to compile tuxguitar against it, but that's not needed. And it seems nobody is using it. <br />
* [http://aur.archlinux.org/packages.php?ID=3947 viki-svn] - old, pkgbuild is broken<br />
* [http://aur.archlinux.org/packages.php?ID=12067 pidgimpd-svn] - This package is orphaned and it doesn't build. There is mpd support in musictracker.<br />
* [http://aur.archlinux.org/packages.php?ID=6686 sizzle] - No upstream maintenance, does not compile.<br />
* [http://aur.archlinux.org/packages.php?ID=15973 weather-wallpaper] - orphaned and references as dep non-existing pymetar<br />
<br />
==TU Working Area==<br />
<br />
'''For editing by TUs only!''' The wiki has a history so do not think you can get away with ignoring this... --[[User:Allan|Allan]]<br />
<br />
===Packages to Remove===<br />
* [http://aur.archlinux.org/packages.php?ID=1926 fvwm-trans] last updated over 2 years ago and replaced with [http://aur.archlinux.org/packages.php?ID=7195 fvwm-patched] in AUR --[[User:pressh|pressh]] (I think one feature that is patched is in fvwm by default now, the other is in fvwm-patched too. If user does not want all the patched they can disable the ones they don't want from fvwm-patched)<br />
* [http://aur.archlinux.org/packages.php?ID=16166 jacman] - Jacman doesn't work correctly with pacman3. --[[User:Partition|Partition]]<br />
* [http://aur.archlinux.org/packages.php?ID=14992 slim-theme-darch] - in archlinux-themes-slim --[[User:Allan|Allan]]<br />
In community:<br />
* [http://aur.archlinux.org/packages.php?ID=12993 ion-modules] - ion3 is not part of official repos anymore, move to AUR --[[User:Allan|Allan]]<br />
* [http://aur.archlinux.org/packages.php?ID=9102 lmctl] - replaced by lomoco --[[User:Allan|Allan]]<br />
* [http://aur.archlinux.org/packages.php?ID=8958 wildfire] - Replaced by openfire. --[[User:pressh|pressh]]<br />
<br />
===Packages to Keep===<br />
* [http://aur.archlinux.org/packages.php?ID=14946 mplayer-w32codecs] - not duplicate package as has more codecs than the "codecs" package.<br />
** Should rename to "codecs-extra" and not provide same files as codecs package --[[User:Allan|Allan]]<br />
<br />
==Remove from Filesystem==<br />
<br />
This is a list of files on the AUR filesystem that have been created when poorly formed packages were uploaded. This is a secondary consideration.<br />
<br />
There are also directories in /packages/ for which the package no longer exists. These probably need to be removed as well. Examples are 4c, 1394commander and 8kingdoms. Also, all the packages that moved to community ALSO still exist here; for example 915resolution. A [http://archlinux.spider007.net/aur-invalid-directories.txt complete list of these directories can be found here]<br />
<br />
<pre><br />
/packages/0verkill-0.16.tar.gz/<br />
/packages/0verkill-0.16/<br />
/packages/2007.02.17-2/<br />
/packages/abakus-0.91-1/<br />
/packages/abakus-0.91.tar.gz/<br />
/packages/abakus-0.91/<br />
/packages/akgregator/<br />
/packages/akregator/<br />
/packages/akregator1.0.2/<br />
/packages/akregator_1.0.2/<br />
/packages/amsn-0.97ec1/<br />
/packages/amsn-0.97rc1/<br />
/packages/amsn-097rc1-1/<br />
/packages/amsn-097rc1/<br />
/packages/amsn-cvs/<br />
/packages/amsn-svn_update/<br />
/packages/amsn096/<br />
/packages/amsn096rc1/<br />
/packages/bashstyle-5.0<br />
/packages/bashstyle-5.0rc1.tar.gz/<br />
/packages/bashstyle-5.0rc1.tar.gz1/<br />
/packages/bashstyle-5.0rc1/<br />
/packages/bashstyle.tar.gz/<br />
/packages/bashstyle-ng/<br />
/packages/bashstyle1/<br />
/packages/braero-svn<br />
/packages/braser-cvs/<br />
/packages/brasero-cvs/<br />
/packages/brasero.svn/<br />
/packages/brlcad-cvs/<br />
/packages/ccd2iso-0.3/<br />
/packages/cdcollect-0.6.0/<br />
/packages/centerim-4.22.2/<br />
/packages/centerim/<br />
/packages/exiftool/exiftool-7.13.tar.gz (/packages/exiftool/exiftool.tar.gz has been uploaded & works)<br />
/packages/ploticus-test/<br />
/packages/test-louipc/<br />
/packages/test/<br />
/packages/test_pkg/<br />
/packages/yacas-1.1.17-2/<br />
/packages/yacas-1.2.2/<br />
/packages/yacas-1.17-2/<br />
/packages/yacas-new/<br />
/packages/yacasnew/<br />
/packages/zzztest/<br />
/packages/zzzztest/<br />
</pre><br />
<br />
==Remove from Filesystem (AUR Bugs)==<br />
<br />
This is a list of files that need to be removed due to AUR bugs as they hinder proper submission and maintenance of packages.<br />
<br />
AUR Bugs<br />
* FS#8672 - http://bugs.archlinux.org/task/8672<br />
<br />
<pre><br />
/packages/advanceutils<br />
/packages/isight-firmware-tools<br />
/packages/mlt-svn<br />
/packages/perl-devel-stacktrace<br />
/packages/psi-qt4<br />
/packages/xcursor-industrial<br />
/packages/zaptel<br />
</pre><br />
<br />
/packages/lib32-dbus is now in community - Allan</div>Synorgyhttps://wiki.archlinux.org/index.php?title=Desktop_environment&diff=13247Desktop environment2006-05-21T22:49:41Z<p>Synorgy: /* Under XFCE */</p>
<hr />
<div>[[Category:Desktop]]<br />
[[Category:Desktop Environment]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Desktop_Environment}}<br />
{{i18n_links_end}}<br />
A Desktop Environment (DE) is a complete Graphical User Interface (GUI) for a computer.<br />
<br />
Desktop Environments usually include, but are not limited to;<br />
* Widgets<br />
* Toolbars/Panels<br />
* Applets<br />
* Applications<br />
* Icons<br />
* Wallpapers<br />
* A Window Manager<br />
<br />
<br />
== The X server ==<br />
To install/use a DE, you require X(org). If you are accessing this wiki through a graphical browser like firefox or konqueror, then you likely already have X and a DE installed. However if you installed Arch using a base cd, and are reading this wiki from the terminal, in a browser like links2, you likely don't have X. To install X, type the following in a console:<br />
pacman -S xorg<br />
<br />
For more information on X, see the [[Xorg]] article.<br />
<br />
== Installing a Desktop Environment ==<br />
There are many DE's available for linux, here are just a few:<br />
* [[KDE]]<br />
* [[GNOME]]<br />
* [[XFCE]]<br />
* [[Enlightenment]]<br />
<br />
=== Installing KDE in a nutshell ===<br />
You can install KDE by simply typing the following in a root terminal:<br />
pacman -S kde<br />
<br />
This will ask you first, if you want to install the whole KDE group of packages. This is about 270mb of downloads <sub>(4-2006 estimate with kde 3.5.2)</sub>. If you don't want to install all of this, you can type 'n', and it will ask you which KDE packages you want. Below is a list of all the KDE packages and details about them.<br />
<br />
==== KDE Packages ====<br />
* arts - KDE Sound Engine<br />
* gwenview - KDE Image Viewer<br />
* kde-Common - Common KDE packages<br />
* kdeaccessibility - KDE Accessibility<br />
* kdeaddons - Plugins for konq, noatun, etc.<br />
* kdeadmin - Administration packages; includes user manager<br />
* kdeartwork - Artwork (Colours, themes, pictures, splash screens, etc.)<br />
* kdebase - Base of KDE. REQUIRED<br />
* kdebindings - KDE Key bindings<br />
* kdeedu - KDE Educational Applications<br />
* kdegames - Games for KDE<br />
* kdegraphics - Graphic-related Applications<br />
* kdelibs - KDE Libraries. REQUIRED<br />
* kdemultimedia - Includes Multimedia Applications for KDE<br />
* kdenetwork - KDE Network-related package, including kppp, etc.<br />
* kdepim - Personal Information Management; Korganiser, KMail, etc.<br />
* kdesdk - KDE Software Development Kit<br />
* kdetoys - Small Applications and toys for KDE; Eyes, Amusing Misuse of Resources (AMOR)<br />
* kdeutils - Little extra applications; ark, kcalc, etc.<br />
<br />
For more information, See [[KDE]]<br />
<br />
=== Installing GNOME in a nutshell ===<br />
You can install GNOME by simply typing the following in a root terminal:<br />
pacman -S gnome<br />
<br />
Like the KDE one, this will first ask whether you want the whole GNOME group. The total downloads for installing gnome is 95MB <sub>(As of 4-2006)</sub>. If no, you may select which packages to install. Below is a list of the GNOME packages, and explanations of what they are.<br />
<br />
==== GNOME Packages ====<br />
* gnome-icon-theme - An icon theme for GNOME<br />
* control-center - The GNOME Control Center<br />
* epiphany - GNOME web-browser<br />
* gnome-applets - *<br />
* gnome-backgrounds - *<br />
* gnome-common - *<br />
* gnome-desktop - *<br />
* gnome-media - *<br />
* gnome-mime-data - Mime Data for GNOME<br />
* gnome-panel - GNOME Panel<br />
* gnome-session - *<br />
* gnome-themes - Themes for GNOME<br />
* gnome2-user-docs - GNOME User Documentation<br />
* metacity - GNOME Window Manager<br />
* nautilus - GNOME Filebrowser<br />
* vte - *<br />
* yelp - *<br />
<br />
For more information, see [[GNOME]]<br />
<br />
=== Installing XFCE in a nutshell ===<br />
You can install XFCE by simply typing the following in a root terminal:<br />
pacman -S xfce4<br />
<br />
As with both the KDE and GNOME installs, it will first ask you if you want to install the whole XFCE group. The total downloads for XFCE is 44.9MB <sub>(As of 4-2006)</sub>. If you choose not to install the whole group, see below for each package and its details.<br />
<br />
==== XFCE packages ====<br />
* gtk-xfce-engine - The XFCE-GTK graphics engine<br />
* libxfce4mcs - *<br />
* libxfce4util - *<br />
* libxfcegui4 - *<br />
* xfcalendar - XFCE Calender<br />
* xfce-mcs-manager - *<br />
* xfce-mcs-plugins - *<br />
* xfce-utils - *<br />
* xfce4-appfinder - *<br />
* xfce4-icon-theme - *<br />
* xfce4-iconbox - *<br />
* xfce4-mixer - *<br />
* xfce4-panel - XFCE Panel<br />
* xfce4-session - *<br />
* xfce4-systray - *<br />
* xfce4-toys - Small toys for XFCE<br />
* xfce4-trigger-launcher - *<br />
* xfdesktop - *<br />
* xffm - *<br />
* xfprint - The XFCE Print package<br />
* xfwm4 - XFce Window Manager<br />
* xfwm4-themes - Themes for XFCE Window Manager<br />
<br />
For more information, see [[XFCE]]<br />
<br />
=== Installing Enlightenment in a nutshell ===<br />
Enlightenment has two versions:<br />
* DR16, the older code, originally released 2000, with most recent release 2003.<br />
* DR17, the newer code, still in pre-alpha (although quite stable).<br />
<br />
==== Enlightenment Development Release 16 ====<br />
You can install Enlightenment DR16 by simply typing the following in a root terminal:<br />
pacman -S enlightenment<br />
<br />
It seems that E16 is only the window manager, and not a whole Desktop Environment; See [[Window_Managers_and_Desktop_Environments_-_What_are_they%3F]] for more info.<br />
<br />
==== Enlightenment Development Release 17 ====<br />
You can install Enlightenment DR17 by [[enabling the community repositories]], then typing the following in a root terminal:<br />
pacman -S e17<br />
<br />
Enlightenment DR17 Has a similar group of packages to KDE, GNOME and XFCE. Total downloads for E17 is 31.8MB <sub>(As of 4-2006)</sub>. Below is a list of packages in the e17 group.<br />
<br />
==== E17 Packages ====<br />
* e - The window manager<br />
* ecore - Event Abstraction and Modular Convenience<br />
* edb-devel - E Database Development package<br />
* edje - Interface Abstraction Library & Tools<br />
* eet - Distribution Container Libraries & Tools<br />
* embryo - Embeddable scripting language for enlightenment<br />
* emotion - Video smart-object library for evas<br />
* entice - An Image Viewer<br />
* entrance - The E Display Manager<br />
* epeg - For thumbnailing JPEGs<br />
* epsilon - Freedesktop.org thumbnailing library<br />
* esmart - A collection of evas smart objects<br />
* etox - Text Layout and Manipulation<br />
* evas - Canvas Library<br />
* ewl - Enlightenment Widget Library<br />
* imlib2-devel - Image Rendering and Manipulation Library<br />
* imlib2_loaders - Loaders for the Image Rendering and Manipulation Library<br />
<br />
For more information, see [[Enlightenment]] and/or [[E17]]<br />
<br />
== Configuring the Desktop Environment ==<br />
<br />
=== Under KDE ===<br />
<br />
After installing kdeadmin, from the konsole, type 'kcontrol', or go K Menu --> Control Center<br />
<br />
=== Under GNOME ===<br />
<br />
Use the prefrences menu to drop down to whatever you'd like to change.<br />
<br />
=== Under XFCE ===<br />
<br />
Right click on the desktop and pull down to the settings menu. From there you can open the "settings manager".<br />
<br />
=== Under E17 ===<br />
<br />
Navigate from the E17 menu (or left click the desktop), go Configuration --> Configuration Panel<br />
<br />
== Other ==<br />
<br />
=== Links ===<br />
==== Internal Links ====<br />
* [[X]]<br />
* [[Xorg]]<br />
* [[KDE]]<br />
* [[GNOME]]<br />
* [[XFCE]]<br />
* [[GNOME]]<br />
* [[Enlightenment]]<br />
* [[E17]]<br />
<br />
==== External links ====<br />
* [http://en.wikipedia.org/wiki/Desktop_Environment Desktop Environment on Wikipedia]<br />
<br />
=== * ===<br />
In the package lists, those marked with a * require citation of package use.</div>Synorgyhttps://wiki.archlinux.org/index.php?title=Desktop_environment&diff=13246Desktop environment2006-05-21T22:42:59Z<p>Synorgy: /* Under GNOME */</p>
<hr />
<div>[[Category:Desktop]]<br />
[[Category:Desktop Environment]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Desktop_Environment}}<br />
{{i18n_links_end}}<br />
A Desktop Environment (DE) is a complete Graphical User Interface (GUI) for a computer.<br />
<br />
Desktop Environments usually include, but are not limited to;<br />
* Widgets<br />
* Toolbars/Panels<br />
* Applets<br />
* Applications<br />
* Icons<br />
* Wallpapers<br />
* A Window Manager<br />
<br />
<br />
== The X server ==<br />
To install/use a DE, you require X(org). If you are accessing this wiki through a graphical browser like firefox or konqueror, then you likely already have X and a DE installed. However if you installed Arch using a base cd, and are reading this wiki from the terminal, in a browser like links2, you likely don't have X. To install X, type the following in a console:<br />
pacman -S xorg<br />
<br />
For more information on X, see the [[Xorg]] article.<br />
<br />
== Installing a Desktop Environment ==<br />
There are many DE's available for linux, here are just a few:<br />
* [[KDE]]<br />
* [[GNOME]]<br />
* [[XFCE]]<br />
* [[Enlightenment]]<br />
<br />
=== Installing KDE in a nutshell ===<br />
You can install KDE by simply typing the following in a root terminal:<br />
pacman -S kde<br />
<br />
This will ask you first, if you want to install the whole KDE group of packages. This is about 270mb of downloads <sub>(4-2006 estimate with kde 3.5.2)</sub>. If you don't want to install all of this, you can type 'n', and it will ask you which KDE packages you want. Below is a list of all the KDE packages and details about them.<br />
<br />
==== KDE Packages ====<br />
* arts - KDE Sound Engine<br />
* gwenview - KDE Image Viewer<br />
* kde-Common - Common KDE packages<br />
* kdeaccessibility - KDE Accessibility<br />
* kdeaddons - Plugins for konq, noatun, etc.<br />
* kdeadmin - Administration packages; includes user manager<br />
* kdeartwork - Artwork (Colours, themes, pictures, splash screens, etc.)<br />
* kdebase - Base of KDE. REQUIRED<br />
* kdebindings - KDE Key bindings<br />
* kdeedu - KDE Educational Applications<br />
* kdegames - Games for KDE<br />
* kdegraphics - Graphic-related Applications<br />
* kdelibs - KDE Libraries. REQUIRED<br />
* kdemultimedia - Includes Multimedia Applications for KDE<br />
* kdenetwork - KDE Network-related package, including kppp, etc.<br />
* kdepim - Personal Information Management; Korganiser, KMail, etc.<br />
* kdesdk - KDE Software Development Kit<br />
* kdetoys - Small Applications and toys for KDE; Eyes, Amusing Misuse of Resources (AMOR)<br />
* kdeutils - Little extra applications; ark, kcalc, etc.<br />
<br />
For more information, See [[KDE]]<br />
<br />
=== Installing GNOME in a nutshell ===<br />
You can install GNOME by simply typing the following in a root terminal:<br />
pacman -S gnome<br />
<br />
Like the KDE one, this will first ask whether you want the whole GNOME group. The total downloads for installing gnome is 95MB <sub>(As of 4-2006)</sub>. If no, you may select which packages to install. Below is a list of the GNOME packages, and explanations of what they are.<br />
<br />
==== GNOME Packages ====<br />
* gnome-icon-theme - An icon theme for GNOME<br />
* control-center - The GNOME Control Center<br />
* epiphany - GNOME web-browser<br />
* gnome-applets - *<br />
* gnome-backgrounds - *<br />
* gnome-common - *<br />
* gnome-desktop - *<br />
* gnome-media - *<br />
* gnome-mime-data - Mime Data for GNOME<br />
* gnome-panel - GNOME Panel<br />
* gnome-session - *<br />
* gnome-themes - Themes for GNOME<br />
* gnome2-user-docs - GNOME User Documentation<br />
* metacity - GNOME Window Manager<br />
* nautilus - GNOME Filebrowser<br />
* vte - *<br />
* yelp - *<br />
<br />
For more information, see [[GNOME]]<br />
<br />
=== Installing XFCE in a nutshell ===<br />
You can install XFCE by simply typing the following in a root terminal:<br />
pacman -S xfce4<br />
<br />
As with both the KDE and GNOME installs, it will first ask you if you want to install the whole XFCE group. The total downloads for XFCE is 44.9MB <sub>(As of 4-2006)</sub>. If you choose not to install the whole group, see below for each package and its details.<br />
<br />
==== XFCE packages ====<br />
* gtk-xfce-engine - The XFCE-GTK graphics engine<br />
* libxfce4mcs - *<br />
* libxfce4util - *<br />
* libxfcegui4 - *<br />
* xfcalendar - XFCE Calender<br />
* xfce-mcs-manager - *<br />
* xfce-mcs-plugins - *<br />
* xfce-utils - *<br />
* xfce4-appfinder - *<br />
* xfce4-icon-theme - *<br />
* xfce4-iconbox - *<br />
* xfce4-mixer - *<br />
* xfce4-panel - XFCE Panel<br />
* xfce4-session - *<br />
* xfce4-systray - *<br />
* xfce4-toys - Small toys for XFCE<br />
* xfce4-trigger-launcher - *<br />
* xfdesktop - *<br />
* xffm - *<br />
* xfprint - The XFCE Print package<br />
* xfwm4 - XFce Window Manager<br />
* xfwm4-themes - Themes for XFCE Window Manager<br />
<br />
For more information, see [[XFCE]]<br />
<br />
=== Installing Enlightenment in a nutshell ===<br />
Enlightenment has two versions:<br />
* DR16, the older code, originally released 2000, with most recent release 2003.<br />
* DR17, the newer code, still in pre-alpha (although quite stable).<br />
<br />
==== Enlightenment Development Release 16 ====<br />
You can install Enlightenment DR16 by simply typing the following in a root terminal:<br />
pacman -S enlightenment<br />
<br />
It seems that E16 is only the window manager, and not a whole Desktop Environment; See [[Window_Managers_and_Desktop_Environments_-_What_are_they%3F]] for more info.<br />
<br />
==== Enlightenment Development Release 17 ====<br />
You can install Enlightenment DR17 by [[enabling the community repositories]], then typing the following in a root terminal:<br />
pacman -S e17<br />
<br />
Enlightenment DR17 Has a similar group of packages to KDE, GNOME and XFCE. Total downloads for E17 is 31.8MB <sub>(As of 4-2006)</sub>. Below is a list of packages in the e17 group.<br />
<br />
==== E17 Packages ====<br />
* e - The window manager<br />
* ecore - Event Abstraction and Modular Convenience<br />
* edb-devel - E Database Development package<br />
* edje - Interface Abstraction Library & Tools<br />
* eet - Distribution Container Libraries & Tools<br />
* embryo - Embeddable scripting language for enlightenment<br />
* emotion - Video smart-object library for evas<br />
* entice - An Image Viewer<br />
* entrance - The E Display Manager<br />
* epeg - For thumbnailing JPEGs<br />
* epsilon - Freedesktop.org thumbnailing library<br />
* esmart - A collection of evas smart objects<br />
* etox - Text Layout and Manipulation<br />
* evas - Canvas Library<br />
* ewl - Enlightenment Widget Library<br />
* imlib2-devel - Image Rendering and Manipulation Library<br />
* imlib2_loaders - Loaders for the Image Rendering and Manipulation Library<br />
<br />
For more information, see [[Enlightenment]] and/or [[E17]]<br />
<br />
== Configuring the Desktop Environment ==<br />
<br />
=== Under KDE ===<br />
<br />
After installing kdeadmin, from the konsole, type 'kcontrol', or go K Menu --> Control Center<br />
<br />
=== Under GNOME ===<br />
<br />
Use the prefrences menu to drop down to whatever you'd like to change.<br />
<br />
=== Under XFCE ===<br />
<br />
Navigate from the XFCE Start menu to custom settings <sub><Citation needed from an XFCE user></sub><br />
<br />
=== Under E17 ===<br />
<br />
Navigate from the E17 menu (or left click the desktop), go Configuration --> Configuration Panel<br />
<br />
== Other ==<br />
<br />
=== Links ===<br />
==== Internal Links ====<br />
* [[X]]<br />
* [[Xorg]]<br />
* [[KDE]]<br />
* [[GNOME]]<br />
* [[XFCE]]<br />
* [[GNOME]]<br />
* [[Enlightenment]]<br />
* [[E17]]<br />
<br />
==== External links ====<br />
* [http://en.wikipedia.org/wiki/Desktop_Environment Desktop Environment on Wikipedia]<br />
<br />
=== * ===<br />
In the package lists, those marked with a * require citation of package use.</div>Synorgyhttps://wiki.archlinux.org/index.php?title=Network_configuration/Wireless&diff=9943Network configuration/Wireless2006-03-22T16:43:15Z<p>Synorgy: </p>
<hr />
<div>[[Category:Wireless]]<br />
[[Category:Installation]]<br />
{{stub}}<br />
{{translateme}}<br />
==First steps==<br />
#Check to see if Linux supports your hardware<br />
#*[http://www.linux-wlan.org/docs/wlan_adapters.html.gz wlan-ng] supports quite a lot of chipsets, check here first.<br />
#*[http://madwifi.org madwifi] for Atheros chipsets (AR5210, AR5211, AR5212 and AR5213)<br />
#*[http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page rt2x00] for Ralink's rt2400, rt2500, and rt2570 chipsets.<br />
#*[http://ipw2100.sourceforge.net/ ipw2100] for Intel Pro/Wireless 2100 Mini PCI<br />
#*[http://ipw2200.sourceforge.net/ ipw2200] for Intel Pro/Wireless 2200 Mini PCI<br />
#*[http://www.nongnu.org/orinoco/devices/ orinoco] for some Prism 2 based cards<br />
#*[http://prism54.org/ prism54] for Prism 54 based cards<br />
#*The Linux Questions [http://www.linuxquestions.org/hcl/index.php?cat=10|hardware compatibility list] (HCL) has a good list of Linux friendly hardware <br />
#If the hardware is only supported under Windows<br />
#*[http://ndiswrapper.sourceforge.net/wiki/index.php/List ndiswrapper] for hardware only supported under Windows (Broadcom, 3com, etc)<br />
#*You will need the .inf and .sys files from your Windows driver - [http://ndiswrapper.sourceforge.net/mediawiki/index.php/List check here]<br />
#If the your hardware is not listed anywhere<br />
#*I think you may be screwed....<br />
#*Try a web search for the exact model name of your hardware with the word "linux" - and feel free to ask for help on [http://bbs.archlinux.org the forums]<br />
<br />
==Installation==<br />
First off, make sure you grab '''wireless-tools''' from pacman<br />
<pre>pacman -S wireless_tools</pre><br />
You cannot initialize wireless hardware without these tools<br />
===Drivers===<br />
Here are the details of how to get the drivers for your card. You may find that there are several options open to you so remember you can check the [http://www.linuxquestions.org/hcl/index.php?cat=10|LQ HCL] for help on selecting the best driver.<br />
====wlan-ng====<br />
<pre>pacman -S wlan-ng24</pre> or <pre>pacman -S wlan-ng26</pre><br />
====rt2x00====<br />
See the [[Using_the_new_rt2x00_beta_driver|rt2x00 wiki page]]<br />
<br />
====madwifi====<br />
[http://aur.archlinux.org/packages.php?do_Details=1&ID=785 AUR PKGBUILD]<br><br />
'''Note:'''Madwifi-ng is now included in unstable. You can enable the unstable repo in Pacman and install using pacman instead of the pkgbuild.<br />
'''Note:'''Using Madwifi drivers from before January 23, 2006 requires that you define which interface you would like to use (more recent versions do not require this step, go straight to ifconfig). This is an extra step that most other drivers do not require. Considering that you want your wifi0 interface to become ath0 the command would be:<pre>wlanconfig ath0 create wlandev wifi0 wlanmode sta</pre>Of course this is followed by these commands: <br />
<pre>ifconfig ath0 up<br />
iwconfig ath0 essid youressid key yourWEPkey<br />
dhclient ath0</pre> <br />
You can insert these into /etc/rc.local to have this occur everytime you boot up.<br />
<br />
Or enter this in /etc/rc.conf or /etc/conf.d/wireless, here's an example for rc.conf<br />
<pre><br />
ath0="ath0 192.168.100.1 netmask 255.255.255.0 broadcast 192.168.100.255" | ath0="dhcp"<br />
wlan_ath0="ath0 essid <your_essid> key <your_wep_key>"<br />
WLAN_INTERFACES=(ath0)<br />
</pre><br />
Don't forget to add or replace the interface name (ath0) for the INTERFACES keyword (this will bring ath0 up when booting):<br />
<pre><br />
Before:<br />
INTERFACES=(lo eth0)<br />
After:<br />
INTERFACES=(lo eth0 ath0)<br />
</pre><br />
<br />
* '''Note:''' You may need to use the countrycode option when loading the madwifi driver in order to use channels and transmit power settings that are legal in your country/region. So in The Netherlands, for example, you would load the module like this:<br />
<pre>modprobe ath_pci countrycode=528</pre><br />
* To make this happen during boot, add the following to /etc/modprobe.conf (for 2.6 kernels)<br />
<pre>#/etc/modprobe.conf<br />
options ath_pci countrycode=<your_countrycode><br />
</pre><br />
* You can verify the settings with the iwlist command, see man iwlist. See also the [http://madwifi.org/wiki/UserDocs/CountryCode CountryCode] page on the madwifi wiki.<br />
<br />
====ipw2100 or ipw2200====<br />
<pre>pacman -S ipw2100 or pacman -S ipw2200</pre><br />
====orinoco====<br />
This should be part of the kernel package and installed already<br />
====ndiswrapper====<br />
<pre>pacman -S community/ndiswrapper</pre><br />
<br />
NB: If you experience problems with ndiswrapper, I strongly suggest you download the latest stable version (1.10 as of 2006-02-23) [http://sourceforge.net/project/showfiles.php?group_id=93482&package_id=99148&release_id=392869], which appears to fix many issues with recent and/or optimized kernels. Follow these instructions [http://ndiswrapper.sourceforge.net/wiki/index.php/Installation] for installing. (In my experience versions 1.9.* and earlier made the 2-6-15-ARCH kernel freeze instantly, whereas with 1.10 it works just fine).<br />
<br />
====prism54====<br />
In dibble's [http://dtw.jiwe.org/primal/primal.php repo] - will add to AUR<br />
<br />
====ACX100/111====<br />
The ACX100/111 driver can be found at [http://acx100.sourceforge.net/]. This can be used for cards which are based on the Texas ACX100/111 chipset.<br />
<br />
Contrary to what people think, this is relatively easy to setup. There is a huge guide written by Craig [http://www.houseofcraig.net/acx100_howto.php here]. However, the README which comes with the driver is actually easier to follow.<br />
<br />
# Download the latest version of the driver. <br />
# Extract the archive in a directory of your choice. Beware, the archive does not have a directory inside, so if you don't extract within a directory, a lot of files will spill out everywhere.<br />
# Change to the directory containing the extracted files.<br />
# Execute <pre>make -C /lib/modules/`uname -r`/build M=`pwd`</pre><br />
# Change to root user.<br />
# Execute <pre>make -C /lib/modules/`uname -r`/build M=`pwd` modules_install</pre><br />
# Execute <pre>depmod -ae</pre> so the kernel detects the new module.<br />
# Insert your Driver CD which came with the card into the CD/DVD drive on your computer.<br />
# Mount the drive with <pre>mount &lt;device&gt;</pre><br />
# Copy the firmware from the CD to /lib/firmware.<br />
# Rename the firmware to 'tiacxNNNcMM' (NNN=100/111, MM=radio module ID (in uppercase hex)) for the PCI driver or tiacxNNNusbcMM for the USB driver. <br />
# Load the acx module with <pre>modprobe acx</pre><br />
# Add the acx module to the MODULES array in /etc/rc.conf so it gets loaded on startup.<br />
# Follow the instructions for connecting to your network with iwconfig.<br />
<br />
<br />
Note: It is also possible to compile the driver inside the kernel tree. This is documented in the README file with the driver.<br />
<br />
==Setup and Boot==<br />
Archlinux provides two methods for enabling wireless connections. The first method is based on the existing network script and is to be used for non-roaming wireless access. If you're only on 1 wireless network, this is the best setup to use. However, if you continually roam from network to network, the Network Profiles setup would be best, though slightly more complicated.<br />
<br />
===Using the Archlinux Wireless Network settings===<br />
* Typical Archlinux Wireless configuration is rather straight forward. The network itself is configured in the exact same way a non-wireless network is in /etc/rc.conf. For example:<br />
# /etc/rc.conf<br />
wlan0="dhcp"<br />
INTERFACES=(lo eth0 wlan0)<br />
* Beyond this, the networking scripts need some way to determine that wlan0 is a wireless interface (as not all wireless interfaces are wlan*). This is done in the /etc/conf.d/wireless file. The setup here is very simple. For each wireless interface, you simply declare a setting called wlan_<interface name>. If your wireless interface is "wlan0", it uses wlan_wlan0. If your wireless interface is "eth1", wlan_eth1 is what you need. The value for this setting is simply the parameters to iwconfig (see man iwconfig for details) ''including the interface name''.<br />
* A simply, non encrypted setup for the above would look like:<br />
# /etc/conf.d/wireless<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
* ''phrakture's trick''<br />
** My personal trick isn't much of a trick at all, it just simplifies alot of the process. While /etc/conf.d/wireless is sourced (included) in the network script, it is not a requirement for having a wireless interface. Therefore, the actual settings for the wireless interface can exist in anything sourced by the network script. For that reason, I put all my settings in /etc/rc.conf:<br />
# /etc/rc.conf<br />
eth0="dhcp"<br />
wlan0="dhcp"<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
#wlan_wlan0="wlan0 essid MyEssid key 12345678"<br />
#wlan_wlan0="wlan0 essid MyEssid key s:wirelesspassword"<br />
INTERFACES=(lo eth0 wlan0)<br />
<br />
If your wireless card is eth0 so you change wlan_wlan0 in wlan_eth0="eth0 essid ...."<br />
<br />
===Using the Archlinux Roaming Network Profiles - ''Work In Progress''===<br />
Please see Judd's explanation [http://www.archlinux.org/pipermail/arch/2005-June/004855.html here] (this need wikifying)<br />
<br />
'''Simple Wireless Autodetection'''<br />
iphitus created an autodetection patch for the official initscripts which has now been imported as standard. Please see [http://www.archlinux.org/pipermail/arch/2005-July/005251.html here] for an explanation of how it works.<br />
<br />
'''WPA support'''<br />
phydeaux created a great patch for WPA support which has been adopted straight into the main tree and will be in the next release (after 0.7.1)<br />
<br />
===Using phrakture's old scripts (very outdated)===<br />
* In order to use these scripts, place them where indicated. The main script is in /etc/rc.d and the profiles are in /etc/conf.d/wireless-profiles. Making a new profile involves copying the sample and renaming it. The script can be used in two ways. It can be added to the DAEMONS array, with an added WIRELESS_PROFILES collection in rc.conf that lists the profiles to start on boot. In addition, the script can be called manually: /etc/rc.d/wireless start/stop/restart will use the listed profiles in rc.conf, and /etc/rc.d/wireless profile sample up/down will use a named profile and bring it up or down.<br />
*[[Wireless Bootup Script]] - /etc/rc.d/wireless <br />
*[[Sample Wireless Profile]] - /etc/conf.d/wireless-profiles/sample/*<br />
<br />
==Misc Links==<br />
*[http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wireless.html An overly wordy howto that rarely helps]<br />
*[http://madwifi.org/wiki/UserDocs/FirstTimeHowTo The madwifi project's method of installing, good if you're having trouble doing it the Arch way]</div>Synorgyhttps://wiki.archlinux.org/index.php?title=Network_configuration/Wireless&diff=8217Network configuration/Wireless2006-01-11T16:06:01Z<p>Synorgy: </p>
<hr />
<div>[[Category:Wireless]]<br />
[[Category:Installation]]<br />
{{stub}}<br />
{{translateme}}<br />
==First steps==<br />
#Check to see if Linux supports your hardware<br />
#*[http://www.linux-wlan.org/docs/wlan_adapters.html.gz wlan-ng] supports quite a lot of chipsets, check here first.<br />
#*[http://www.mattfoster.clara.co.uk/madwifi-faq.htm madwifi] for Atheros chipsets (AR5210, AR5211, AR5212 and AR5213)<br />
#*[http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page rt2x00] for Ralink's rt2400, rt2500, and rt2570 chipsets.<br />
#*[http://ipw2100.sourceforge.net/ ipw2100] for Intel Pro/Wireless 2100 Mini PCI<br />
#*[http://ipw2200.sourceforge.net/ ipw2200] for Intel Pro/Wireless 2200 Mini PCI<br />
#*[http://www.nongnu.org/orinoco/devices/ orinoco] for some Prism 2 based cards<br />
#*[http://prism54.org/ prism54] for Prism 54 based cards<br />
#*The Linux Questions [http://www.linuxquestions.org/hcl/index.php?cat=10|hardware compatibility list] (HCL) has a good list of Linux friendly hardware <br />
#If the hardware is only supported under Windows<br />
#*[http://ndiswrapper.sourceforge.net/wiki/index.php/List ndiswrapper] for hardware only supported under Windows (Broadcom, 3com, etc)<br />
#*You will need the .inf and .sys files from your Windows driver - [http://ndiswrapper.sourceforge.net/mediawiki/index.php/List check here]<br />
#If the your hardware is not listed anywhere<br />
#*I think you may be screwed....<br />
#*Try a web search for the exact model name of your hardware with the word "linux" - and feel free to ask for help on [http://bbs.archlinux.org the forums]<br />
<br />
==Installation==<br />
First off, make sure you grab '''wireless-tools''' from pacman<br />
<pre>pacman -S wireless_tools</pre><br />
You cannot initialize wireless hardware without these tools<br />
===Drivers===<br />
Here are the details of how to get the drivers for your card. You may find that there are several options open to you so remember you can check the [http://www.linuxquestions.org/hcl/index.php?cat=10|LQ HCL] for help on selecting the best driver.<br />
====wlan-ng====<br />
<pre>pacman -S wlan-ng24</pre> or <pre>pacman -S wlan-ng26</pre><br />
====rt2x00====<br />
[http://aur.archlinux.org/packages.php?do_Details=1&ID=745 AUR PKGBUILD]<br />
====madwifi====<br />
[http://aur.archlinux.org/packages.php?do_Details=1&ID=785 AUR PKGBUILD]<br><br />
'''Note:'''Using the new Madwifi drivers requires that you define which interface you would like to use. This is an extra step that most other drivers do not require. Considering that you want your wifi0 interface to become ath0 the command would be:<pre>wlanconfig ath0 create wlandev wifi0 wlanmode sta</pre>Of course this is followed by these commands: <br />
<pre>ifconfig ath0 up<br />
iwconfig ath0 essid youressid key yourWEPkey<br />
dhclient ath0</pre> <br />
You can insert these into /etc/rc.local to have this occur everytime you boot up.<br />
====ipw2100 or ipw2200====<br />
<pre>pacman -S ipw2100 or pacman -S ipw2200</pre><br />
====orinoco====<br />
This should be part of the kernel package and installed already<br />
====ndiswrapper====<br />
<pre>pacman -S community/ndiswrapper</pre><br />
====prism54====<br />
In dibble's [http://dtw.jiwe.org/primal/primal.php repo] - will add to AUR<br />
<br />
==Setup and Boot==<br />
Archlinux provides two methods for enabling wireless connections. The first method is based on the existing network script and is to be used for non-roaming wireless access. If you're only on 1 wireless network, this is the best setup to use. However, if you continually roam from network to network, the Network Profiles setup would be best, though slightly more complicated.<br />
<br />
===Using the Archlinux Wireless Network settings===<br />
* Typical Archlinux Wireless configuration is rather straight forward. The network itself is configured in the exact same way a non-wireless network is in /etc/rc.conf. For example:<br />
# /etc/rc.conf<br />
wlan0="dhcp"<br />
INTERFACES=(lo eth0 wlan0)<br />
* Beyond this, the networking scripts need some way to determine that wlan0 is a wireless interface (as not all wireless interfaces are wlan*). This is done in the /etc/conf.d/wireless file. The setup here is very simple. For each wireless interface, you simply declare a setting called wlan_<interface name>. If your wireless interface is "wlan0", it uses wlan_wlan0. If your wireless interface is "eth1", wlan_eth1 is what you need. The value for this setting is simply the parameters to iwconfig (see man iwconfig for details) ''including the interface name''.<br />
* A simply, non encrypted setup for the above would look like:<br />
# /etc/conf.d/wireless<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
* ''phrakture's trick''<br />
** My personal trick isn't much of a trick at all, it just simplifies alot of the process. While /etc/conf.d/wireless is sourced (included) in the network script, it is not a requirement for having a wireless interface. Therefore, the actual settings for the wireless interface can exist in anything sourced by the network script. For that reason, I put all my settings in /etc/rc.conf:<br />
# /etc/rc.conf<br />
eth0="dhcp"<br />
wlan0="dhcp"<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
#wlan_wlan0="wlan0 essid MyEssid key 12345678"<br />
#wlan_wlan0="wlan0 essid MyEssid key s:wirelesspassword"<br />
INTERFACES=(lo eth0 wlan0)<br />
<br />
If your wireless card is eth0 so you change wlan_wlan0 in wlan_eth0="eth0 essid ...."<br />
<br />
===Using the Archlinux Roaming Network Profiles - ''Work In Progress''===<br />
Please see Judd's explanation [http://www.archlinux.org/pipermail/arch/2005-June/004855.html here] (this need wikifying)<br />
<br />
'''Simple Wireless Autodetection'''<br />
iphitus created an autodetection patch for the official initscripts which has now been imported as standard. Please see [http://www.archlinux.org/pipermail/arch/2005-July/005251.html here] for an explanation of how it works.<br />
<br />
'''WPA support'''<br />
phydeaux created a great patch for WPA support which has been adopted straight into the main tree and will be in the next release (after 0.7.1)<br />
<br />
===Using phrakture's old scripts (very outdated)===<br />
* In order to use these scripts, place them where indicated. The main script is in /etc/rc.d and the profiles are in /etc/conf.d/wireless-profiles. Making a new profile involves copying the sample and renaming it. The script can be used in two ways. It can be added to the DAEMONS array, with an added WIRELESS_PROFILES collection in rc.conf that lists the profiles to start on boot. In addition, the script can be called manually: /etc/rc.d/wireless start/stop/restart will use the listed profiles in rc.conf, and /etc/rc.d/wireless profile sample up/down will use a named profile and bring it up or down.<br />
*[[Wireless Bootup Script]] - /etc/rc.d/wireless <br />
*[[Sample Wireless Profile]] - /etc/conf.d/wireless-profiles/sample/*<br />
<br />
==Misc Links==<br />
*[http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wireless.html An overly wordy howto that rarely helps]</div>Synorgyhttps://wiki.archlinux.org/index.php?title=Network_configuration/Wireless&diff=8212Network configuration/Wireless2006-01-11T01:26:23Z<p>Synorgy: </p>
<hr />
<div>[[Category:Wireless]]<br />
[[Category:Installation]]<br />
{{stub}}<br />
{{translateme}}<br />
==First steps==<br />
#Check to see if Linux supports your hardware<br />
#*[http://www.linux-wlan.org/docs/wlan_adapters.html.gz wlan-ng] supports quite a lot of chipsets, check here first.<br />
#*[http://www.mattfoster.clara.co.uk/madwifi-faq.htm madwifi] for Atheros chipsets (AR5210, AR5211, AR5212 and AR5213)<br />
#*[http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page rt2x00] for Ralink's rt2400, rt2500, and rt2570 chipsets.<br />
#*[http://ipw2100.sourceforge.net/ ipw2100] for Intel Pro/Wireless 2100 Mini PCI<br />
#*[http://ipw2200.sourceforge.net/ ipw2200] for Intel Pro/Wireless 2200 Mini PCI<br />
#*[http://www.nongnu.org/orinoco/devices/ orinoco] for some Prism 2 based cards<br />
#*[http://prism54.org/ prism54] for Prism 54 based cards<br />
#*The Linux Questions [http://www.linuxquestions.org/hcl/index.php?cat=10|hardware compatibility list] (HCL) has a good list of Linux friendly hardware <br />
#If the hardware is only supported under Windows<br />
#*[http://ndiswrapper.sourceforge.net/wiki/index.php/List ndiswrapper] for hardware only supported under Windows (Broadcom, 3com, etc)<br />
#*You will need the .inf and .sys files from your Windows driver - [http://ndiswrapper.sourceforge.net/mediawiki/index.php/List check here]<br />
#If the your hardware is not listed anywhere<br />
#*I think you may be screwed....<br />
#*Try a web search for the exact model name of your hardware with the word "linux" - and feel free to ask for help on [http://bbs.archlinux.org the forums]<br />
<br />
==Installation==<br />
First off, make sure you grab '''wireless-tools''' from pacman<br />
<pre>pacman -S wireless_tools</pre><br />
You cannot initialize wireless hardware without these tools<br />
===Drivers===<br />
Here are the details of how to get the drivers for your card. You may find that there are several options open to you so remember you can check the [http://www.linuxquestions.org/hcl/index.php?cat=10|LQ HCL] for help on selecting the best driver.<br />
====wlan-ng====<br />
<pre>pacman -S wlan-ng24</pre> or <pre>pacman -S wlan-ng26</pre><br />
====rt2x00====<br />
[http://aur.archlinux.org/packages.php?do_Details=1&ID=745 AUR PKGBUILD]<br />
====madwifi====<br />
[http://aur.archlinux.org/packages.php?do_Details=1&ID=785 AUR PKGBUILD]<br><br />
'''Note:'''Using the new Madwifi drivers requires that you define which interface you would like to use. This is an extra step that most other drivers do not require. Considering that you want your wifi0 interface to become ath0 the command would be:<pre>wlanconfig ath0 create wlandev wifi0 wlanmode sta</pre>Of course this is followed by these commands: <pre>ifconfig ath0 up<br>iwconfig ath0 essid youressid key yourWEPkey<br>dhclient ath0</pre> You can insert these into /etc/rc.local to have this occur everytime you boot up.<br />
====ipw2100 or ipw2200====<br />
<pre>pacman -S ipw2100 or pacman -S ipw2200</pre><br />
====orinoco====<br />
This should be part of the kernel package and installed already<br />
====ndiswrapper====<br />
<pre>pacman -S community/ndiswrapper</pre><br />
====prism54====<br />
In dibble's [http://dtw.jiwe.org/primal/primal.php repo] - will add to AUR<br />
<br />
==Setup and Boot==<br />
Archlinux provides two methods for enabling wireless connections. The first method is based on the existing network script and is to be used for non-roaming wireless access. If you're only on 1 wireless network, this is the best setup to use. However, if you continually roam from network to network, the Network Profiles setup would be best, though slightly more complicated.<br />
<br />
===Using the Archlinux Wireless Network settings===<br />
* Typical Archlinux Wireless configuration is rather straight forward. The network itself is configured in the exact same way a non-wireless network is in /etc/rc.conf. For example:<br />
# /etc/rc.conf<br />
wlan0="dhcp"<br />
INTERFACES=(lo eth0 wlan0)<br />
* Beyond this, the networking scripts need some way to determine that wlan0 is a wireless interface (as not all wireless interfaces are wlan*). This is done in the /etc/conf.d/wireless file. The setup here is very simple. For each wireless interface, you simply declare a setting called wlan_<interface name>. If your wireless interface is "wlan0", it uses wlan_wlan0. If your wireless interface is "eth1", wlan_eth1 is what you need. The value for this setting is simply the parameters to iwconfig (see man iwconfig for details) ''including the interface name''.<br />
* A simply, non encrypted setup for the above would look like:<br />
# /etc/conf.d/wireless<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
* ''phrakture's trick''<br />
** My personal trick isn't much of a trick at all, it just simplifies alot of the process. While /etc/conf.d/wireless is sourced (included) in the network script, it is not a requirement for having a wireless interface. Therefore, the actual settings for the wireless interface can exist in anything sourced by the network script. For that reason, I put all my settings in /etc/rc.conf:<br />
# /etc/rc.conf<br />
eth0="dhcp"<br />
wlan0="dhcp"<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
#wlan_wlan0="wlan0 essid MyEssid key 12345678"<br />
#wlan_wlan0="wlan0 essid MyEssid key s:wirelesspassword"<br />
INTERFACES=(lo eth0 wlan0)<br />
<br />
If your wireless card is eth0 so you change wlan_wlan0 in wlan_eth0="eth0 essid ...."<br />
<br />
===Using the Archlinux Roaming Network Profiles - ''Work In Progress''===<br />
Please see Judd's explanation [http://www.archlinux.org/pipermail/arch/2005-June/004855.html here] (this need wikifying)<br />
<br />
'''Simple Wireless Autodetection'''<br />
iphitus created an autodetection patch for the official initscripts which has now been imported as standard. Please see [http://www.archlinux.org/pipermail/arch/2005-July/005251.html here] for an explanation of how it works.<br />
<br />
'''WPA support'''<br />
phydeaux created a great patch for WPA support which has been adopted straight into the main tree and will be in the next release (after 0.7.1)<br />
<br />
===Using phrakture's old scripts (very outdated)===<br />
* In order to use these scripts, place them where indicated. The main script is in /etc/rc.d and the profiles are in /etc/conf.d/wireless-profiles. Making a new profile involves copying the sample and renaming it. The script can be used in two ways. It can be added to the DAEMONS array, with an added WIRELESS_PROFILES collection in rc.conf that lists the profiles to start on boot. In addition, the script can be called manually: /etc/rc.d/wireless start/stop/restart will use the listed profiles in rc.conf, and /etc/rc.d/wireless profile sample up/down will use a named profile and bring it up or down.<br />
*[[Wireless Bootup Script]] - /etc/rc.d/wireless <br />
*[[Sample Wireless Profile]] - /etc/conf.d/wireless-profiles/sample/*<br />
<br />
==Misc Links==<br />
*[http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wireless.html An overly wordy howto that rarely helps]</div>Synorgy