https://wiki.archlinux.org/api.php?action=feedcontributions&user=Sargon&feedformat=atomArchWiki - User contributions [en]2024-03-28T16:18:49ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Install_Arch_i586&diff=56920Install Arch i5862009-01-04T15:28:13Z<p>Sargon: Some rewriting work</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:I586 (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{out of date}}<br />
= Preface =<br />
This document tries to describe the process which let me successfully build Arch Linux under other architectures.<br />
<br />
= Requirements =<br />
* A faster PC with Arch Linux already installed, we'll use it to build packages for i586.<br />
* free disk space about 2G bytes.<br />
<br />
= Step 1. Prepare build enviroment =<br />
Prepare your system for build tasks as described in [[Makepkg#Setting Things Up]] :<br />
pacman -Sy base-devel<br />
pacman -S abs<br />
Check /etc/abs.conf for activated repos, you should have at least core activated, check out or update <br />
your abs tree. Then create an work directory for your i586 PKGBUILDs and duplicate repos into it.<br />
# abs<br />
# mkdir -p /home/i586/abs<br />
# cd /home/i586/abs<br />
# cp -r /var/abs/core .<br />
You also should create an directory where you will put the packages. <br />
# mkdir -p /home/i586/pkg<br />
Edit the /etc/makepkg.conf or copy to ~/.makepkg.conf , modify the following lines, we'll use -mtune option for x86 can also use the binary packages.<br />
CARCH="i586"<br />
CHOST="i586-pc-linux-gnu"<br />
CFLAGS="-mtune=i586 -O2 -pipe"<br />
CXXFLAGS="-mtune=i586 -O2 -pipe"<br />
For faster compiling take a look on ccache and/or distcc.<br />
<br />
= Step 2. Build packages =<br />
After we have prepared our build enviroment now is the time to run some last commands and get some coffee. Change to your <br />
i586 abs directory and run makeworld. <br />
# cd /home/i586/abs<br />
# makeworld --clean --ignorearch --syncdeps --rmdeps --noconfirm /home/i586/pkg/ core<br />
When you didn't want to repeat typing your root pw for resolving dependencies you could<br />
allow your build user to use pacman without retyping pw. See [[Disable root password and gain su sudo with no password]] for more information.<br />
And don't forget to deactivate it after using for building process!<br />
<br />
= Step 3. Solve Problem during Compiling =<br />
After the build Process come to an end, we should check which packages have problems while building.<br />
# grep failed build.log<br />
Then you should change to the package directorys in your abs copy and retry building it.<br />
# cd core/<failed package><br />
# makepkg -Acrs <br />
For more information about building packages see in [[makepkg]]<br />
<br />
= Step 4. Share Built Packages for i586 =<br />
Set up a [[Custom local repository]] for sharing your packages with the target system.<br />
<br />
= Step 5. Install Arch Linux on i586 by bootable linux =<br />
See [[Install Arch from within another distro]], and use your custom repos as package source.<br />
More soon ....</div>Sargonhttps://wiki.archlinux.org/index.php?title=Install_Arch_i586&diff=56785Install Arch i5862009-01-03T11:30:04Z<p>Sargon: /* Step 1. Download PKGBUILD source */ typo</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:I586 (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{out of date}}<br />
= Preface =<br />
This document tries to describe the process which let me successfully build Arch Linux under other architectures.<br />
<br />
= Requirements =<br />
* A faster PC with Arch Linux already installed, we'll use it to build packages for i586.<br />
* free disk space about 2G bytes.<br />
<br />
= Step 1. Download PKGBUILD source =<br />
Prepare your system for build tasks as described in [[Makepkg#Setting Things Up]] :<br />
pacman -Sy base-devel<br />
pacman -S abs<br />
Check /etc/abs.conf for activated repos, you should have at least core activated, check out or update <br />
your abs tree. Then create an work directory for your i586 PKGBUILDs and duplicate repos into it.<br />
# abs<br />
# mkdir /var/abs/i586<br />
# cd /var/abs/i586<br />
# cp -a ../core .<br />
<br />
= Step 2. Compile Required Packages =<br />
prepare the destination directory where we'll put the packages. Here we use /home/i586/base, edit the /etc/makepkg.conf, modify the following lines, we'll use -mtune option for x86 can also use the binary packages.<br />
export CC="ccache gcc"<br />
export CPP="ccache cpp"<br />
export CXX="ccache g++"<br />
export CARCH="i586"<br />
export CHOST="i586-pc-linux-gnu"<br />
export CFLAGS="-mtune=i586 -O2 -pipe"<br />
export CXXFLAGS="-mtune=i586 -O2 -pipe"<br />
export PKGDEST=/home/i586/base<br />
There are two bugs in the gcc-4.0.2-1 package, do the following to fix them.<br />
* remove the compile backward compatible gcc-3.x dynamic library.<br />
* add a --host=$CHOST in compile gcc-4.0.2 line like following code<br />
./configure --host=$CHOST ...<br />
compile all base directory, the makeworld will call makepkg with --clean option to clean files after successful make package and with --ignorearch the core packages usually not have i586 in there arch parameter.<br />
mkdir -p /home/i586/base<br />
cd /var/abs/i586<br />
makeworld --clean --ignorearch /home/i586/base base<br />
we can view the process by build.log and makepkg.log under /var/abs/i586/.<br />
<br />
= Step 3. Solve Problem during Compiling =<br />
== find out which package build failed by grep ==<br />
grep failed build.log<br />
<br />
== build again by makepkg ==<br />
solve the failed package by manual run makepkg(eg. pacman failed)<br />
cd /var/abs/i586/base/pacman<br />
makepkg -w /home/i586/base<br />
== Solve Missing Dependencies ==<br />
You may found the error message like<br />
==> Missing Dependencies:<br />
requires: libtar<br />
get the missing library for your system<br />
pacman -S libtar<br />
or run the makeworld with additional options like --syncdeps and --rmdeps. You could also use --noconfirm if you want to run the process without waiting for your confirmation.<br />
<br />
== Solve validity check error ==<br />
You may found the error message like ( here I use syslog-ng as example)<br />
==> ERROR: One or more files did not pass the validity check!<br />
To make sure you get the full size package, remove the source cache and try again<br />
cd /var/abs/i586/base/syslog-ng<br />
makepkg -C ; makepkg<br />
If still failed, you should try to check the PKGBUILD, read the syslog-ng's web-site, try to found mirror which near your site, and download it to /var/cache/pacman/src/. If that file is really missing, report to bug system.<br />
<br />
== Solve cpp: too many input files ==<br />
Found following error message:<br />
ccache cpp -Wall -D_GNU_SOURCE -DLinux ...<br />
cpp: too many input files<br />
make: *** [depend] Error 1<br />
==> ERROR: Build Failed. Aborting...<br />
Comment off the ccache setting in /etc/makepkg.conf. Try again.<br />
<br />
= Step 4. Share Built Packages for i586 =<br />
generate current.db.tar.gz<br />
gensync /var/abs/i586 /home/i586/current.db.tar.gz /home/i586<br />
<br />
= Step 5. Install Arch Linux on i586 by bootable linux =<br />
# grep "^base" packages.txt | grep -v pacman \<br />
| grep -v glibc | grep -v iputils \<br />
| sed -e 's:base/::' -e 's:-[0-9].*::' > ~/i.txt<br />
# pacman -Syfw --noconfirm -r /mnt `cat ~/i.txt` kernel26 2>&1 &<br />
# pacman -S --noconfirm -r /mnt glibc iputils pacman | tee ~/i.log<br />
# pacman -Sf --noconfirm -r /mnt `cat ~/i.txt` kernel26</div>Sargonhttps://wiki.archlinux.org/index.php?title=Install_Arch_i586&diff=56765Install Arch i5862009-01-03T01:45:14Z<p>Sargon: /* Step 1. Download PKGBUILD source */ update</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:I586 (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{out of date}}<br />
= Preface =<br />
This document tries to describe the process which let me successfully build Arch Linux under other architectures.<br />
<br />
= Requirements =<br />
* A faster PC with Arch Linux already installed, we'll use it to build packages for i586.<br />
* free disk space about 2G bytes.<br />
<br />
= Step 1. Download PKGBUILD source =<br />
Prepare your system for build tasks as described in [[Makepkg#Setting Things Up]] :<br />
pacman -Sy base-devel<br />
pacman -S abs<br />
Check /etc/abs.conf for activated repos, you should have at lease core activated, check out or update <br />
your abs tree with. Then create an work directory for your i586 PKGBUILDs and duplicate repos into it.<br />
# abs<br />
# mkdir /var/abs/i586<br />
# cd /var/abs/i586<br />
# cp -a ../core .<br />
<br />
= Step 2. Compile Required Packages =<br />
prepare the destination directory where we'll put the packages. Here we use /home/i586/base, edit the /etc/makepkg.conf, modify the following lines, we'll use -mtune option for x86 can also use the binary packages.<br />
export CC="ccache gcc"<br />
export CPP="ccache cpp"<br />
export CXX="ccache g++"<br />
export CARCH="i586"<br />
export CHOST="i586-pc-linux-gnu"<br />
export CFLAGS="-mtune=i586 -O2 -pipe"<br />
export CXXFLAGS="-mtune=i586 -O2 -pipe"<br />
export PKGDEST=/home/i586/base<br />
There are two bugs in the gcc-4.0.2-1 package, do the following to fix them.<br />
* remove the compile backward compatible gcc-3.x dynamic library.<br />
* add a --host=$CHOST in compile gcc-4.0.2 line like following code<br />
./configure --host=$CHOST ...<br />
compile all base directory, the makeworld will call makepkg with --clean option to clean files after successful make package and with --ignorearch the core packages usually not have i586 in there arch parameter.<br />
mkdir -p /home/i586/base<br />
cd /var/abs/i586<br />
makeworld --clean --ignorearch /home/i586/base base<br />
we can view the process by build.log and makepkg.log under /var/abs/i586/.<br />
<br />
= Step 3. Solve Problem during Compiling =<br />
== find out which package build failed by grep ==<br />
grep failed build.log<br />
<br />
== build again by makepkg ==<br />
solve the failed package by manual run makepkg(eg. pacman failed)<br />
cd /var/abs/i586/base/pacman<br />
makepkg -w /home/i586/base<br />
== Solve Missing Dependencies ==<br />
You may found the error message like<br />
==> Missing Dependencies:<br />
requires: libtar<br />
get the missing library for your system<br />
pacman -S libtar<br />
or run the makeworld with additional options like --syncdeps and --rmdeps. You could also use --noconfirm if you want to run the process without waiting for your confirmation.<br />
<br />
== Solve validity check error ==<br />
You may found the error message like ( here I use syslog-ng as example)<br />
==> ERROR: One or more files did not pass the validity check!<br />
To make sure you get the full size package, remove the source cache and try again<br />
cd /var/abs/i586/base/syslog-ng<br />
makepkg -C ; makepkg<br />
If still failed, you should try to check the PKGBUILD, read the syslog-ng's web-site, try to found mirror which near your site, and download it to /var/cache/pacman/src/. If that file is really missing, report to bug system.<br />
<br />
== Solve cpp: too many input files ==<br />
Found following error message:<br />
ccache cpp -Wall -D_GNU_SOURCE -DLinux ...<br />
cpp: too many input files<br />
make: *** [depend] Error 1<br />
==> ERROR: Build Failed. Aborting...<br />
Comment off the ccache setting in /etc/makepkg.conf. Try again.<br />
<br />
= Step 4. Share Built Packages for i586 =<br />
generate current.db.tar.gz<br />
gensync /var/abs/i586 /home/i586/current.db.tar.gz /home/i586<br />
<br />
= Step 5. Install Arch Linux on i586 by bootable linux =<br />
# grep "^base" packages.txt | grep -v pacman \<br />
| grep -v glibc | grep -v iputils \<br />
| sed -e 's:base/::' -e 's:-[0-9].*::' > ~/i.txt<br />
# pacman -Syfw --noconfirm -r /mnt `cat ~/i.txt` kernel26 2>&1 &<br />
# pacman -S --noconfirm -r /mnt glibc iputils pacman | tee ~/i.log<br />
# pacman -Sf --noconfirm -r /mnt `cat ~/i.txt` kernel26</div>Sargonhttps://wiki.archlinux.org/index.php?title=Install_Arch_i586&diff=51683Install Arch i5862008-10-23T15:45:25Z<p>Sargon: /* Solve Missing Dependencies */ Add Info for auto dep resolving</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:I586 (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
= Preface =<br />
This document tries to describe the process which let me successfully build ArchLinux under other architectures.<br />
<br />
= Requirements =<br />
* A faster PC with ArchLinux already installed, we'll use it to build packages for i586.<br />
* free disk space about 2G bytes.<br />
<br />
= Step 1. Download PKGBUILD source =<br />
get required packages<br />
pacman -S cvsup ccache libtar libol<br />
edit the /etc/abs/abs.conf enable arch,extra.<br />
SUPFILES=(arch extra !unstable !community)<br />
Maybe you can also get the testing version by [[Getting_Testing_PKGBUILDs]].<br />
Execute abs to get PKGBUILDs in /var/abs, make a directory called i586, and copy base packages into it.<br />
# abs<br />
# mkdir /var/abs/i586<br />
# cd /var/abs/i586<br />
# cp -a ../base .<br />
= Step 2. Compile Required Packages =<br />
prepare the destination directory where we'll put the packages. Here we use /home/i586/base, edit the /etc/makepkg.conf, modify the following lines, we'll use -mtune option for x86 can also use the binary packages.<br />
export CC="ccache gcc"<br />
export CPP="ccache cpp"<br />
export CXX="ccache g++"<br />
export CARCH="i586"<br />
export CHOST="i586-pc-linux-gnu"<br />
export CFLAGS="-mtune=i586 -O2 -pipe"<br />
export CXXFLAGS="-mtune=i586 -O2 -pipe"<br />
export PKGDEST=/home/i586/base<br />
There are two bugs in the gcc-4.0.2-1 package, do the following to fix them.<br />
* remove the compile backward compatible gcc-3.x dynamic library.<br />
* add a --host=$CHOST in compile gcc-4.0.2 line like following code<br />
./configure --host=$CHOST ...<br />
compile all base directory, the makeworld will call makepkg with --clean option to clean files after successful make package and with --ignorearch the core packages usually not have i586 in there arch parameter.<br />
mkdir -p /home/i586/base<br />
cd /var/abs/i586<br />
makeworld --clean --ignorearch /home/i586/base base<br />
we can view the process by build.log and makepkg.log under /var/abs/i586/.<br />
<br />
= Step 3. Solve Problem during Compiling =<br />
== find out which package build failed by grep ==<br />
grep failed build.log<br />
<br />
== build again by makepkg ==<br />
solve the failed package by manual run makepkg(eg. pacman failed)<br />
cd /var/abs/i586/base/pacman<br />
makepkg -w /home/i586/base<br />
== Solve Missing Dependencies ==<br />
You may found the error message like<br />
==> Missing Dependencies:<br />
requires: libtar<br />
get the missing library for your system<br />
pacman -S libtar<br />
or run the makeworld with additional options like --syncdeps and --rmdeps. You could also use --noconfirm if you want to run the process without waiting for your confirmation.<br />
<br />
== Solve validity check error ==<br />
You may found the error message like ( here I use syslog-ng as example)<br />
==> ERROR: One or more files did not pass the validity check!<br />
To make sure you get the full size package, remove the source cache and try again<br />
cd /var/abs/i586/base/syslog-ng<br />
makepkg -C ; makepkg<br />
If still failed, you should try to check the PKGBUILD, read the syslog-ng's web-site, try to found mirror which near your site, and download it to /var/cache/pacman/src/. If that file is really missing, report to bug system.<br />
<br />
== Solve cpp: too many input files ==<br />
Found following error message:<br />
ccache cpp -Wall -D_GNU_SOURCE -DLinux ...<br />
cpp: too many input files<br />
make: *** [depend] Error 1<br />
==> ERROR: Build Failed. Aborting...<br />
Comment off the ccache setting in /etc/makepkg.conf. Try again.<br />
<br />
= Step 4. Share Built Packages for i586 =<br />
generate current.db.tar.gz<br />
gensync /var/abs/i586 /home/i586/current.db.tar.gz /home/i586<br />
<br />
= Step 5. Install ArchLinux on i586 by bootable linux =<br />
# grep "^base" packages.txt | grep -v pacman \<br />
| grep -v glibc | grep -v iputils \<br />
| sed -e 's:base/::' -e 's:-[0-9].*::' > ~/i.txt<br />
# pacman -Syfw --noconfirm -r /mnt `cat ~/i.txt` kernel26 2>&1 &<br />
# pacman -S --noconfirm -r /mnt glibc iputils pacman | tee ~/i.log<br />
# pacman -Sf --noconfirm -r /mnt `cat ~/i.txt` kernel26</div>Sargonhttps://wiki.archlinux.org/index.php?title=Install_Arch_i586&diff=51641Install Arch i5862008-10-22T23:40:32Z<p>Sargon: /* Step 2. Compile Required Packages */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:I586 (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
= Preface =<br />
This document tries to describe the process which let me successfully build ArchLinux under other architectures.<br />
<br />
= Requirements =<br />
* A faster PC with ArchLinux already installed, we'll use it to build packages for i586.<br />
* free disk space about 2G bytes.<br />
<br />
= Step 1. Download PKGBUILD source =<br />
get required packages<br />
pacman -S cvsup ccache libtar libol<br />
edit the /etc/abs/abs.conf enable arch,extra.<br />
SUPFILES=(arch extra !unstable !community)<br />
Maybe you can also get the testing version by [[Getting_Testing_PKGBUILDs]].<br />
Execute abs to get PKGBUILDs in /var/abs, make a directory called i586, and copy base packages into it.<br />
# abs<br />
# mkdir /var/abs/i586<br />
# cd /var/abs/i586<br />
# cp -a ../base .<br />
= Step 2. Compile Required Packages =<br />
prepare the destination directory where we'll put the packages. Here we use /home/i586/base, edit the /etc/makepkg.conf, modify the following lines, we'll use -mtune option for x86 can also use the binary packages.<br />
export CC="ccache gcc"<br />
export CPP="ccache cpp"<br />
export CXX="ccache g++"<br />
export CARCH="i586"<br />
export CHOST="i586-pc-linux-gnu"<br />
export CFLAGS="-mtune=i586 -O2 -pipe"<br />
export CXXFLAGS="-mtune=i586 -O2 -pipe"<br />
export PKGDEST=/home/i586/base<br />
There are two bugs in the gcc-4.0.2-1 package, do the following to fix them.<br />
* remove the compile backward compatible gcc-3.x dynamic library.<br />
* add a --host=$CHOST in compile gcc-4.0.2 line like following code<br />
./configure --host=$CHOST ...<br />
compile all base directory, the makeworld will call makepkg with --clean option to clean files after successful make package and with --ignorearch the core packages usually not have i586 in there arch parameter.<br />
mkdir -p /home/i586/base<br />
cd /var/abs/i586<br />
makeworld --clean --ignorearch /home/i586/base base<br />
we can view the process by build.log and makepkg.log under /var/abs/i586/.<br />
<br />
= Step 3. Solve Problem during Compiling =<br />
== find out which package build failed by grep ==<br />
grep failed build.log<br />
<br />
== build again by makepkg ==<br />
solve the failed package by manual run makepkg(eg. pacman failed)<br />
cd /var/abs/i586/base/pacman<br />
makepkg -w /home/i586/base<br />
== Solve Missing Dependencies ==<br />
You may found the error message like<br />
==> Missing Dependencies:<br />
requires: libtar<br />
get the missing library for your system<br />
pacman -S libtar<br />
== Solve validity check error ==<br />
You may found the error message like ( here I use syslog-ng as example)<br />
==> ERROR: One or more files did not pass the validity check!<br />
To make sure you get the full size package, remove the source cache and try again<br />
cd /var/abs/i586/base/syslog-ng<br />
makepkg -C ; makepkg<br />
If still failed, you should try to check the PKGBUILD, read the syslog-ng's web-site, try to found mirror which near your site, and download it to /var/cache/pacman/src/. If that file is really missing, report to bug system.<br />
<br />
== Solve cpp: too many input files ==<br />
Found following error message:<br />
ccache cpp -Wall -D_GNU_SOURCE -DLinux ...<br />
cpp: too many input files<br />
make: *** [depend] Error 1<br />
==> ERROR: Build Failed. Aborting...<br />
Comment off the ccache setting in /etc/makepkg.conf. Try again.<br />
<br />
= Step 4. Share Built Packages for i586 =<br />
generate current.db.tar.gz<br />
gensync /var/abs/i586 /home/i586/current.db.tar.gz /home/i586<br />
<br />
= Step 5. Install ArchLinux on i586 by bootable linux =<br />
# grep "^base" packages.txt | grep -v pacman \<br />
| grep -v glibc | grep -v iputils \<br />
| sed -e 's:base/::' -e 's:-[0-9].*::' > ~/i.txt<br />
# pacman -Syfw --noconfirm -r /mnt `cat ~/i.txt` kernel26 2>&1 &<br />
# pacman -S --noconfirm -r /mnt glibc iputils pacman | tee ~/i.log<br />
# pacman -Sf --noconfirm -r /mnt `cat ~/i.txt` kernel26</div>Sargonhttps://wiki.archlinux.org/index.php?title=Xmonad&diff=49682Xmonad2008-09-19T08:29:50Z<p>Sargon: Add run hint for stdinreader</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|Xmonad}}<br />
{{i18n_entry|Türkçe|Xmonad (Türkçe)}}<br />
{{i18n_links_end}}<br />
= Introduction =<br />
<br />
[http://xmonad.org/ xmonad] is a tiling window manager for X. Windows are arranged automatically to tile the screen without gaps or overlap, maximizing screen use. Window manager features are accessible from the keyboard: a mouse is optional. <br />
<br />
xmonad is written, configured and extensible in [http://haskell.org/ Haskell]. Custom layout algorithms, key bindings and other extensions may be written by the user in config files. <br />
<br />
Layouts are applied dynamically, and different layouts may be used on each workspace. Xinerama is fully supported, allowing windows to be tiled on several physical screens.<br />
<br />
For more information, please visit the xmonad website: http://xmonad.org/<br />
<br />
= Installation =<br />
<br />
xmonad is currently available in the community repo. A build for the current development snapshot (darcs) is in the [http://aur.archlinux.org/ aur]. The following instructions are for xmonad-darcs, the development snapshot.<br />
<br />
== Development Version (xmonad-darcs) ==<br />
<br />
The xmonad-darcs development release requires 3 separate packages available from AUR (install them in the following order):<br />
<br />
* [http://aur.archlinux.org/packages.php?do_Details=1&ID=13750&O=0&L=0&C=0&K=xmonad&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd haskell-x11-darcs] - haskell bindings to the X11 graphics library<br />
* [http://aur.archlinux.org/packages.php?ID=12483 xmonad-darcs] - the core window manager<br />
* [http://aur.archlinux.org/packages.php?do_Details=1&ID=13652&O=0&L=0&C=0&K=xmonad&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd xmonad-contrib-darcs] - contributed extensions providing custom layouts, configurations, etc.<br />
<br />
= Configuration =<br />
<br />
== Starting xmonad ==<br />
To start xmonad automatically, simply add the command '''xmonad''' to your startup script (e.g. ~/.xinitrc). GDM and KDM users can create a new session file and then select xmonad from the appropriate Session menu.<br />
<br />
== Configuring xmonad ==<br />
<br />
Xmonad users can modify, override or extend the default settings with the ~/.xmonad/xmonad.hs configuration file. Recompiling is done on the fly, with the Mod+q shortcut.<br />
<br />
Because the xmonad configuration file is written in Haskell, non-programmers may have a difficult time adjusting settings. For detailed HOWTO's and example configs, we refer you to the following resources:<br />
<br />
* [http://haskell.org/haskellwiki/Xmonad xmonad wiki]<br />
* [http://haskell.org/haskellwiki/Xmonad/Config_archive xmonad config archive]<br />
* [http://haskell.org/haskellwiki/Xmonad/Frequently_asked_questions xmonad FAQ]<br />
<br />
== Exiting xmonad ==<br />
To end the current xmonad session, press Mod+SHIFT+q (Mod being ALT by default).<br />
<br />
= Tips & Tricks =<br />
== Complementary Applications ==<br />
There are number of complementary utilities that work well with Xmonad. The most common of these include:<br />
<br />
* [http://www.suckless.org/wiki/tools/xlib dmenu]<br />
* [[Xmobar]]<br />
* [[Dzen]] <br />
* [[Conky]] and [http://aur.archlinux.org/packages.php?ID=11884 conky-cli]<br />
<br />
== Making room for conky or tray apps ==<br />
:''Note that 'defaultGaps' will be removed from XMonad in version 0.8, and replaced by something like 'avoidStruts' or an extension from XMonadContrib like XMonad.Hooks.ManageDocks.''<br />
<br />
xmonad can be configured to leave space at the top or bottom of your screen for background applications like Conky or trayer. To do so, open the Config.hs file in your favourite editor and change the ''defaultGaps'' value:<br />
defaultGaps = [(0,0,0,0)]<br />
The fields are: top, bottom, left, right. So, to leave a 15 pixel gap at the top and a 24 pixel gap along the bottom would look like this:<br />
defaultGaps = [(15,24,0,0)]<br />
<br />
Or, wrap your layouts with avoidStruts from XMonad.Hooks.ManageDocks for the fitting to happen automatically:<br />
layoutHook = avoidStruts (tiled Tall ||| ...<br />
manageHook = manageHook defaultConfig <+> manageDocks<br />
<br />
If you ever want to toggle the gaps the action is<br />
,((modMask x, xK_b ), sendMessage ToggleStruts)<br />
<br />
== Using [[xmobar]] with xmonad ==<br />
[[Xmobar]] is a light and minimalistic text based bar, designed to work with xmonad.<br><br />
To use xmobar with xmonad, you will need two packages in addition to the xmonad package, these are xmonad-contrib from [community] and xmobar or xmobar-darcs from [http://aur.archlinux.org aur]. You must also make room for the bar on screen, see [[Xmonad#Making room for conky or tray apps]]<br />
<br />
There are two ways of getting the output of xmonad into xmobar. You can either use a standard unix pipe when you start xmonad, or you can set up a pipe from within xmonad.hs. The later is generaly prefered since it's independent of the way you start xmonad. The following setup will use the later, starting xmobar and setting up the pipe from within xmonad.<br />
<br />
Open up <tt>~/.xmonad/xmonad.hs</tt> in your favorite editor.<br><br />
First, we need to import three modules, IO, the DynamicLog and the Run utility. The logger is used to format and print various information about xmonad, like the workspaces, the title of the current window, the current layout and more. The two others are neede to run xmobar with a pipe, and to print the output of the logger to it.<br />
import IO<br />
import XMonad.Hooks.DynamicLog<br />
import XMonad.Util.Run<br />
<br />
Now, on to the main function. There are several loggers you can use and you can also create your own. In this example, we will use xmobarPP, for details read the documentation on [http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-DynamicLog.html XMonad.Hooks.DynamicLog].<br><br />
The important thing here, is that we have to overide the ppOutput, else it will just print to stdout.<br />
main = do<br />
xmobar <- spawnPipe "xmobar" -- spawns xmobar and returns a handle<br />
xmonad $ defaultConfig <br />
{ ...<br />
, logHook = dynamicLogWithPP $ xmobarPP { ppOutput = hPutStrLn xmobar } -- print the output of xmobarPP to the handle<br />
, ...<br />
}<br />
<br />
At last, open up <tt>~/.xmobarrc</tt> and make sure you got StdinReader in the template and run the plugin. E.g.<br />
Config { ...<br />
, commands = [ Run StdinReader .... ] <br />
...<br />
, template = " %StdinReader% ... "<br />
}<br />
Now, all you should have to do is either to start, or restart xmonad.<br />
<br />
== Example Configurations ==<br />
Below are some example configurations from fellow Xmonad users. Feel free to add links to your own.<br />
* MrElendig :: Simple configuration, with xmobar :: [http://arch.har-ikkje.net/configs/home/dot.xmonad/xmonad.hs xmonad.hs], [http://arch.har-ikkje.net/configs/home/dot.xmobarrc .xmobarrc], [http://arch.har-ikkje.net/gfx/ss/2008-07-27-180602_1680x1050_scrot.png screenshot].<br />
* hsa2 :: Simple configuration, with xmobar :: [http://www.difuzyon.net/linked/configs/xmonad.hs xmonad.hs], [http://www.difuzyon.net/linked/configs/dot.xmobarrc .xmobarrc].<br />
<br />
= Other Resources =<br />
[http://xmonad.org/ xmonad] -- The official xmonad website<br />
<br />
[http://xmonad.org/tour.html xmonad: a guided tour]<br />
<br />
[[dzen]] -- A general purpose messaging and notification program<br />
<br />
[[dmenu]] -- A dynamic X menu for the quick launching of programs</div>Sargonhttps://wiki.archlinux.org/index.php?title=Hibernate-script&diff=34217Hibernate-script2007-12-28T13:06:11Z<p>Sargon: /* NVidia specific settings */ Fix typo</p>
<hr />
<div>[[Category:Power management (English)]]<br />
[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
This article will describe how to suspend a computer (usually a laptop) to disk. This means that all the running processes will be saved to the hard drive and power will completely shut down. This article discusses the two main maethods to accomplish this task, that is userspace suspension (uswsusp) and tuxonice (formerly known as suspend2). See the [http://suspend.sourceforge.net/ ususpend website] and the [http://www.tuxonice.net/ tuxonice website] for complete documentation. There is a third method: using the kernelspace functionalities of the vanilla kernel. However, this method is the least developed, the slowest and the less reliable. On the contrary, tuxonice and ususpend are competing in features and stability. The only method to decide which method is better for you is to try both of them. From a general point of view, we can say that uswsusp does not force you to patch, configure and compile a kernel, while tuxonice does. However, tuxonice can be used without an initrd/initramfs, while using ususpend without an initrd/initramfs is discouraged; moreover, tuxonice allows you to suspend on a regular file if you have not a swap partition, while uswsusp give this possibility only if you run an experimental and unstable mm kernel.<br />
<br />
It is important to distinguish the core method of suspension to disk from the userspace application which you use to hibernate concretely to disk your machine. A userspace application is required because the large majority of the laptops require some quirks in order to accomplish a proficient, successful hibernation cycle: unloading modules, restarting services, unmount windows partitions and usb keys, and so on.<br />
<br />
There are two widely used userspace applications for this purpose: [[pm-utils]] and hibernate-script. You can find both of them in the extra repo. However, since in this guide we need to describe two different, competing core methods, we will focus on the hibernate-script, since only this script allows the user to choose the core method he prefers. On the contrary, [[pm-utils]], at least in the version actually distributed by arch, forces you silently to use the old vanilla method. On the other side, the script, developed by the tuxonice development team, can be used nonetheless also to hibernate your machine with the ususpend method, and even to suspend the machine to ram (actually it is an excellent tool also for this task, but we are not going to discuss this aspect in this document, see [[Suspend to RAM]]).<br />
<br />
If you prefer to use pm-utils, refer to the specific [[pm-utils|wiki article]].<br />
<br />
Thus:<br />
<br />
# pacman -S hibernate-script<br />
<br />
The discussion will be articulated in four parts. First of all, we will discuss the userspace method, secondly the tuxonice one, thirdly we will see how to use the power of the hibernate-script in order to circumvent some problems which could impair your ability to accomplish successful suspend/resume cycles. These last tips can be used with both methods. On the contrary, the first two parts will include instructions to use the hibernate-script in order to accomplish the basic operations with the two methods. In the fourth and last part, we will see how to combine suspension to disk and [[Suspend to RAM]] . <br />
<br />
When there is the need to modify the configuration of the bootloader, we will be always under the assumption that you use grub, but it should not be difficult to act analogously on the configuration of lilo.<br />
<br />
=Uswsusp method=<br />
<br />
The userspace method lets you resort to some advanced suspension abilities included in vanilla kernels > 2.6.17. You need two userspace tools, called s2disk and resume, which do what their names say. They are both included in the uswsusp package (which includes also s2ram, see [[Suspend to RAM]] ). You can find uswsusp in the AUR. The package in the AUR includes also an initramfs hook which allows you to resume properly using an initramfs.<br />
<br />
==Obtaining uswsusp==<br />
The first thing to do is to download the tarball from the AUR page. Compile the source and create the package with makepkg and install it with pacman -U.<br />
<br />
==Recreate the intramfs==<br />
Now you need to recreate an initramfs with the new hook. So edit the /etc/mkinitcpio.conf file. In the HOOKS list add the uresume hook (it is different from the resume hook, which is on the contrary required by the tuxonice method). You should put it immediately before the filesystem hook. Now proceed to regenerate your initramfs:<br />
<br />
# mkinitcpio -k kernel26 -g /boot/kernel26.img<br />
<br />
You need to adjust this command according to the kernel you plan to use and the name of the initramfs in the grub configuration. Anyway you should not need to modify anything in the grub configuration.<br />
<br />
==Editing /etc/suspend.conf==<br />
On the contrary, you need to edit the s2disk configuration file, called /etc/suspend.conf. It is essential that you modify the resume device parameter:<br />
<br />
resume device = /dev/sda3<br />
<br />
It needs to point to your swap partition: in this case, the third partition of a primary pata-sata drive. It is also a good thing to enable compression, because this speeds up greatly your suspension/resume routine. Nothing else should be modified (in particular, please note that the AUR package does not provide support for splash screens: uswsusp would support libsplashy, but you need to modify the PKGBUILD in order to recompile uswsusp with libsplashy support: see the README in the source tarball for details; look there also if you want to encrypt your swap partition).<br />
<br />
Please note that uswsusp can also suspend to a file, but only if you use an experimental mm-patched kernel. If you want to suspend to file, tuxonice is probably the way to go. In the case you like experimental things, see the instructions in the README of the uswsusp source tarball.<br />
<br />
==Suspending==<br />
<br />
Now you could try to suspend directly calling s2disk from the command line:<br />
<br />
# s2disk<br />
<br />
However, this is highly likely to fail, because some services could need to be stopped, some modules unloaded, etc. Thus it is probably necessary to resort to a userspace tool which calls internally s2disk. The hibernate-script does this. See [[Suspend to Disk#Editing /etc/hibernate/hibernate.conf|below]] about details for defining the ususpend-disk method as default in /etc/hibernate/hibernate.conf. For the moment being, remember that you can define specific options in /etc/hibernate/ususpend-disk.conf and, after having configured also /etc/hibernate/common.conf, you can suspend to disk with the uswsusp method with the following command:<br />
<br />
# hibernate -F /etc/hibernate/ususpend-disk.conf <br />
<br />
=Tuxonice method=<br />
<br />
==Obtaining tuxonice==<br />
Tuxonice consists of a kernel patch, plus a user interface. Only the kernel patch is necessary, the user interface provides merely a semi-graphical interface displayed during the hibernation/resume cycle. Archlinux used to deliver a binary tuxonice-patched kernel, but none of the devs want currently to maintain it, thus you need to patch, configure and compile your own kernel. You can do this either with the ABS method (starting from the arch default kernel PKGBUILD and adding the tuxonice patchset, or with the plain, old, reliable, venerable routine of <br />
<br />
# make menuconfig<br />
# make<br />
# make modules_install<br />
# cp arch/i386/boot/bzImage /boot/kernel-tuxonice-2.6.*<br />
<br />
See [Kernel Compilation From Source] and [Kernel Compilation with ABS] for instructions.<br />
In both cases, you need to configure the options added by the patchset, which you can find in the ACPI section of make menuconfig. Anyway, the defaults should be suitable for the large majority of scenarios. You can also hardcode in the kernel the path of your swap partition. In this case you can skip the below [[Suspend to Disk#Editing the Grub menu.lst]] .<br />
<br />
Please note that, if you spend the time to reconfigure completely the kernel (and in particular if you compile into the kernel the stuff necessary to boot your machine), you can be dispensed by the necessity to generate and use an initramfs: tuxonice will be able to resume properly also without an initrd/initramfs.<br />
<br />
==Editing the Grub menu.lst==<br />
Before your can use the suspend function, you need to boot your computer with the "resume" parameter, unless you have hardcoded your swap partition during the kernel configuration. The resume parameter points to the swap partition or swap file. The parameter is a kernel boot parameter, that is it should be added, if you use GRUB, to the line of /boot/grub/menu.lst where the location of your kernel is specified. <br />
For example:<br />
<br />
# tuxonice kernel<br />
title ArchLinux<br />
kernel /boot/kernel-tuxonice-2.6 root=/dev/hda2 resume=swap:/dev/hda3<br />
initrd /boot/tuxonice.img<br />
<br />
This assumes that you installed Archlinux onto the second hard drive partition, that your swap partition is the third, that you have not a separate /boot partition and that you are using an initrd. Adjust accordingly to your case.<br />
<br />
==Recreating the initramfs==<br />
<br />
If you use an initramfs, you need to add the resume hook (which is different from the uresume used by uswsusp) in the HOOKS in /etc/mkinitcpio.conf and to regenerate your initramfs, with a command like the following:<br />
<br />
# mkinitcpio -k kernel-tuxonice-2.6 -g /boot/tuxonice.img<br />
<br />
==Using userui - a user interface for tuxonice==<br />
<br />
Optionally, you can use a text or fbsplash interface with a progress bar with tuxonice. To do this, install the userui package in the extra repo:<br />
<br />
# pacman -S userui<br />
<br />
In ''/etc/hibernate/suspend2.conf'', configure the user interface:<br />
<br />
## Specify a userui like this:<br />
# text interface<br />
ProcSetting user_interface/program /usr/sbin/tuxoniceui_text<br />
<br />
or<br />
<br />
## Specify a userui like this:<br />
# fbsplash interface interface<br />
ProcSetting user_interface/program /usr/sbin/tuxoniceui_fbsplash<br />
<br />
The ''fbsplash'' interface also needs a fbsplash theme in ''/etc/splash/suspend2/''.<br />
<br />
The text interface may be good for debugging suspend2, as it displays some messages.<br />
You won't see a user interface for the first few seconds of the resume process unless you add the ''userui'' hook to your mkinitcpio configuration and regenerate your initramfs, but this is also optional.<br />
<br />
==Suspending and Resuming==<br />
<br />
Now you need to tweak the hibernate script. See [[Suspend to Disk#Editing /etc/hibernate/hibernate.conf|below]] for instructions about defining the tuxonice method as the default hibernation method. <br />
The specific file is /etc/hibernate/suspend2.conf (the hibernate-script still uses the old name of tuxonice):<br />
<br />
Make sure that the following lines are uncommented and appropriately configured:<br />
UseSuspend2 yes<br />
Reboot no<br />
EnableEscape yes<br />
DefaultConsoleLevel 1<br />
Compressor lzf<br />
<br />
Encryptor none<br />
<br />
Once you have tweaked what you want/need (also in /etc/hibernate/common.conf), you can try tuxonice hibernation with the following method:<br />
<br />
# hibernate -F /etc/hibernate/suspend2.conf<br />
<br />
You can abort a suspend cycle if you press the escape key. If you press a capital r, you will force the system to reboot after hibernation.<br />
If all goes well, you should be able to resume using the same Grub menu selection. If you make that option the default for Grub, you will always default to resuming if a resume image is available. '''Do never use a different kernel to resume than you used to suspend! If pacman updates your kernel, don't suspend before you have rebooted properly.''' It is recommended that you test the suspend/hibernate from a text console first and then once you have confirmed that it works try it from within X.<br />
<br />
You can make this practice safer adding the hibernate-cleanup service to your SERVICES array in /etc/rc.conf. This script will make sure that any stale image is deleted from your swap partition at boot time. This should make your system safe also in the case that you have chosen the mistaken kernel at the grub prompt. The hibernate-cleanup service is included in the hibernate-script package.<br />
<br />
== References ==<br />
<br />
*The [http://www.tuxonice.net tuxonice website] and the [http://wiki.tuxonice.net/ tuxonice wiki] are excellent sources of documentation.<br />
*There is a good [http://gentoo-wiki.com/HOWTO_Software_Suspend_v2 Gentoo wiki article] that covers a lot of the same material.<br />
<br />
<br />
=Hibernate tricks with the hibernate.script=<br />
<br />
This is a brief overview of the hibernate script. If you want to tweak it further, examine the ''common.conf'' and ''suspend2.conf'' files further and read the excellent and exhaustive man pages for hibernate and hibernate.conf.<br />
<br />
==Editing /etc/hibernate/hibernate.conf==<br />
<br />
In order to call directly the hibernate command without the -F option, you need to define your preferred hibernation method. This should be done in this file. If you list several methods, the first one will be used. Note that ''hibernate'' can also be used with [[Suspend to RAM]] or vanilla swsusp, but this is not part of this HOWTO).<br />
<br />
Then either:<br />
<br />
TryMethod ususpend-disk.conf<br />
<br />
or: <br />
<br />
TryMethod suspend2.conf<br />
<br />
==Editing /etc/hibernate/common.conf==<br />
<br />
The options in this file are used with any hibernation method (actually, the file is sourced by the configuration files of each method) and also by [[Suspend to RAM]] when accomplished with the hibernate-script. This file is complex and well commented. The man page hibernate.conf describes adequately all the options. Here, we can only stress the most commonly useful parts.<br />
<br />
Uncomment the lines for any filesystems that have the potential to change while your computer is suspended (for example shared partitions with windows like vfat or ntfs ones). They will be remounted upon resume. Otherwise you would risk corrupting the filesystems.<br />
<br />
### filesystems<br />
# Unmount /nfsshare /windows /mnt/sambaserver<br />
# UnmountFSTypes smbfs nfs<br />
# UnmountGraceTime 1<br />
# Mount /windows<br />
<br />
If you don't explicitly restore the volume levels, ALSA may have the sound channels muted after resuming. If this happens, look for<br />
<br />
### services<br />
<br />
in /etc/hibernate/common.conf and change the line just below to<br />
<br />
RestartServices alsa<br />
<br />
The alsa service will be stopped before suspension and restarted after resuming: the sound channels and volumes will be as before.<br />
You may want to restart other problematic services here.<br />
<br />
A common issue is that some drivers do not support suspension, that is they do not work properly after a suspension cycle or even they prevent the system from suspending or resuming properly. <br />
In these cases (which should be reported - at least for modules in the vanilla kernel - to the suspend-devel@lists.sourceforge.net mailing list, so that they can be fixed upstream) you can unload the module before suspension and reload it after resuming: the hibernate-script can automatize this routine with the LoadModules and UnloadModules options. Actually, the hibernate-script already unload some problematic modules, listed in /etc/hibernate/blacklisted-modules, so you can also add the modules in that file.<br />
<br />
If you need/want to eject all PcCards before suspending and reinsert them after resuming, change the ''EjectCards'' setting in ''common.conf'':<br />
<br />
### pcmcia<br />
EjectCards yes<br />
<br />
This is necessary on some laptops, if the pccards stop working after resume.<br />
<br />
Finally, the most problematic aspect is constituted by the video card: its status needs often to be restored after resuming. In other cases, it is necessary to switch from X to the console.<br />
The following options in /etc/hibernate/common.conf will probably fix these issues (whose symptom could be a frozen machine or only a black display after resuming):<br />
<br />
### vbetool<br />
#EnableVbetool yes<br />
#RestoreVbeStateFrom /var/lib/vbetool/vbestate<br />
#VbetoolPost yes<br />
# RestoreVCSAData yes<br />
<br />
### xhacks<br />
#SwitchToTextMode yes<br />
#UseDummyXServer yes<br />
#DummyXServerConfig xorg-dummy.conf<br />
<br />
You can uncomment one or many of them in order to see if the problem is solved. In order to use the first block of options, you need to install the vbetool package from the extra repository. Each of the option is documented in man hibernate.conf. <br />
Please note that it is very important to try all the different combinations of these options before than anything else, becaause the problems with the display are the most common source of troubles in a suspension cycle.<br />
<br />
== NVidia specific settings ==<br />
If you have an NVidia graphics card and are using the binary driver by NVidia with an AGP card, you have to add the following line to your /etc/X11/xorg.conf:<br />
<br />
Option "NvAGP" "1"<br />
<br />
NVidia also suggest this setting for the hibernate script:<br />
<br />
ProcSetting extra_pages_allowance 0<br />
<br />
to the file /etc/hibernate/common.conf. This setting also seems to help with the binary ATI driver. At last, you need to uncomment the nvidia module in /etc/hibernate/blacklisted-modules.<br />
<br />
== Suspending with fglrx ==<br />
Following addition to /etc/hibernate/suspend2.conf is required:<br />
<br />
# For fglrx<br />
ProcSetting extra_pages_allowance 20000<br />
<br />
== Dropping Disk Caches ==<br />
<br />
As a way to speed up suspending, you can free the memory used for disk caches. so there will be less to write to the disk. The downside is the risk of crashing your system. but I have had no trouble with it so far, while reducing the size of the suspended image by half. Just run this before hibernating:<br />
<br />
sync; echo 3 > /proc/sys/vm/drop_caches<br />
[http://www.linuxinsight.com/proc_sys_vm_drop_caches.html drop_caches introduction]<br />
<br />
=Combining suspend to disk with suspend to RAM=<br />
<br />
If your motherboard or laptop supports [[Suspend to RAM]], you can combine it with suspend2. This will result in the following behavior:<br />
<br />
* When you call hibernate, your system will suspend to disk and after that suspend to RAM instead of powering down.<br />
* When you turn your system back on, it will resume directly from RAM (which only takes a few seconds)<br />
* If your battery fails in the meantime (and the image in your memory is therefore lost), you will be able to resumes from disk.<br />
<br />
This can be done both with uswsusp and with tuxonice. <br />
<br />
With uswsusp, you should use s2both. You can also call s2both from the hibernate script (with all its richness of options), resorting to the ususepnd-both.conf method. Please note that s2both works only if s2ram (see [[Suspend to RAM]] works in your system. There is no way to force it to work if your laptop model is not whitelisted in s2ram. See [[Suspend to RAM]] for instructions about how to whitelist your laptop in the local copy of s2ram and how to report that your laptop suspend to ram properly so that it is whitelisted in the next uswsusp release.<br />
<br />
To do it with tuxonice, edit ''/etc/hibernate/suspend2.conf'':<br />
<br />
## Powerdown method - 3 for suspend-to-RAM, 4 for ACPI S4 sleep, 5 for poweroff<br />
PowerdownMethod 3<br />
<br />
For this to work, your computer must be able to use suspend to RAM also without s2ram.</div>Sargonhttps://wiki.archlinux.org/index.php?title=ArchMap&diff=9051ArchMap2006-02-28T13:49:02Z<p>Sargon: Add myself to the map</p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__<br />
<center><br />
<b>We are ArchLinux</b><br />
<br />
http://www.taclug.org/~cmauch/media/maps/world.thumb.jpg<br />
</center><br />
<br />
=== Zoom In a Little ===<br />
<br />
* [http://www.taclug.org/~cmauch/media/maps/world.2048.png World Map]<br />
* [http://www.taclug.org/~cmauch/media/maps/namerica.1280.png North America]<br />
** [http://www.taclug.org/~cmauch/media/maps/usa.1024.png United States]<br />
* [http://www.taclug.org/~cmauch/media/maps/samerica.1024.png South America]<br />
* [http://www.taclug.org/~cmauch/media/maps/europe.1024.png Europe]<br />
** [http://www.taclug.org/~cmauch/media/maps/westerneurope.1024.png Western Europe]<br />
** [http://www.taclug.org/~cmauch/media/maps/centraleurope.1024.png Central Europe]<br />
** [http://www.taclug.org/~cmauch/media/maps/northeasterneurope.1024.png North Eastern Europe]<br />
** [http://www.taclug.org/~cmauch/media/maps/southeasterneurope.1024.png South Eastern Europe]<br />
* [http://www.taclug.org/~cmauch/media/maps/australia.1280.png Australia]<br />
* [http://www.taclug.org/~cmauch/media/maps/middleeast.1024.png Middle East]<br />
<br />
If you don't think your country belongs on map X, go duke it out in the [http://bbs.archlinux.org/viewtopic.php?p=126944 Forums] and blame it all on uneducated Americans. :)<br />
<br />
=== List yourself ===<br />
<br />
Use the '''Edit''' button at the top of this page to add yourself to the World Map run by [[User:Xterminus|xterminus]]. Use decimal coordinates; positive numbers mean north and east, negative numbers mean south and west, resp. The comment is optional.<br />
<br />
Find your coordinates at<br />
* [http://www.multimap.com/ multimap.com] (numbers are in brackets under the map)<br />
US Residents may also use<br />
* [http://tiger.census.gov/cgi-bin/mapbrowse-tbl census.gov] (go to bottom and enter zipcode)<br />
''Note: These maps are automatically generated at a random time during the day when [http://aur.archlinux.org/packages.php?do_Details=1&ID=916 fcron] decides I have a low CPU load. To speed things up, ask [[User:Xterminus|xterminus]] on '''[[ArchChannel|#archlinux]]'''.''<br />
<br />
Please add yourself to the '''end''' of the list.<br />
<br />
----<br />
<pre><br />
47.15655 -122.44884 "xterminus" # Tacoma, WA, USA<br />
41.94250 -87.67600 "phrakture" # Chicago, IL, USA <br />
59.3327 18.0645 "ZaxX" # Stockholm, Sweden<br />
37.2246323 -80.4198074 "codemac" # Blacksburg, VA, USA<br />
51.3412 12.3359 "neri" # Leipzig, Saxony, FRG<br />
59.3327 18.0645 "monotux" # Stockholm, Sweden<br />
53.2141 -6.1083 "tomk" # Bray, Ireland<br />
53.2615 -9.0128 "Civ247" # Galway, Ireland<br />
34.1435 -118.1266 "alturas" # Pasadena, CA, USA<br />
39.0106 -76.7016 "Maveric-i686-" # Crofton, MD, USA<br />
34.21245 -77.91129 "Penguin" # Wilmington, NC, USA<br />
38.0035 -122.1034 "WillySilly" # Martinez, CA, USA<br />
55.6892 12.5333 "FrankVaLi" # Frederiksberg, CPH, DK<br />
38.655408 -121.261065 "joe" # Fair Oaks, CA, USA<br />
59.7438 10.2159 "corky" # Drammen, Norway<br />
-33.3557 -70.4634 "MartinZ" # Santiago, Chile<br />
-23.4953 -46.7124 "Holskoiff" # São Paulo, Brazil<br />
-27.1732 152.9714 "Cam" # Burpengary, QLD, Australia<br />
42.975745 -90.44473 "LudoTheGreat" # Montfort, WI, USA <br />
52.1957 0.1004 "Panu" # Cambridge, UK<br />
29.9864 -90.1747 "Wolfman" # Metairie, LA, USA<br />
32.6605 -97.0886 "mailto" # Arlington, TX, USA<br />
50.7845 6.0765 "brain0" # Aachen, DE<br />
42.6495 -71.1564 "syamajala" # Andover, MA, USA<br />
36.174261 -85.49531 "jftaylor21" # Cookeville, TN, USA<br />
31.6421 -97.4783 "ozar" # Valley Mills, TX, USA<br />
40.5174 -111.9557 "Soloport" # Riverton, UT USA<br />
51.0429 -114.0547 "nirvanix" # Calgary, AB, Canada<br />
-31.9263 115.8786 "awalk" # Mount Lawley, WA, Australia<br />
57.704 18.8028 "CyberTron" # Slite, Gotland, Sweden<br />
40.535 -88.984 "rmbalfa" # Normal, IL (Currently)<br />
-33.3557 -70.4634 "kakabaratruskia" # Santiago, Chile<br />
55.8903 12.854 "N/A" # Landskrona SE<br />
49.0519 8.3958 "ise" # Karlsruhe, Germany <br />
50.3175 8.859 "stimpy" # Florstadt, Germany<br />
48.4168 8.6282 "madhatter" # Horb-Dettingen, Germany<br />
49.9897 17.4588 "Largon" # Bruntal, Czech Republic<br />
60.2301 25.0296 "murkus" # Helsinki, Finland<br />
45.8809 12.5188 "kasa" # Treviso, Italy<br />
48.1507 16.2849 "mercy" # Vienna, Austria<br />
47.2581 11.3217 "tezem" # Innsbruck, Austria<br />
32.1119 34.7803 "drakosha" # Israel, Herzelya<br />
27.12500 56.06300 "Oin" # Ramnicu Valcea, Romania<br />
-25.416 -49.266 "nadal" # Curitiba, Brazil<br />
46.677 -92.2271 "Shadowhand" # Duluth, MN, USA<br />
30.033 31.2166 "Explosivo" # Cairo, Egypt<br />
27.7772 -82.7061 "beniro" # St. Petersburg, FL, USA<br />
40.8248 -96.624 "diablo93" # Lincoln, NE, USA<br />
55.0037 12.3151 "Peque" # Moen, Denmark<br />
52.0361 11.8274 "AndyRTR" # Pretzien, Germany<br />
50.0334 14.2307 "Lejmr" # Rudna, Czech Republic<br />
59.3561 24.6365 "maitrix" # Tallinn, Estonia<br />
30.0351 -90.2446 "Lurch" # Kenner, LA, USA<br />
48.7179 21.2676 "pholie" # Kosice, Slovakia<br />
32.9122 -117.1401 "c14n" # San Diego, CA, USA<br />
-11.7223 -49.0581 "linfocito" # Gurupi, TO, Brazil<br />
-6486200 -4103900 "sgtpepper" # Quilmes, BA, Argentina<br />
42.6425 -95.2087 "medicated" # Storm Lake, IA, USA<br />
41.386209 -73.081745 "omgpro" # Seymour, CT, USA<br />
33.9998 -84.0139 "Frem" # Lawrenceville, GA, USA<br />
48.3674 -89.2698 "gp_aaron" # Thunder Bay, ON, Canada<br />
48.3214 -89.366 "swazo" # Thunder Bay, ON, Canada<br />
55.3471 9.4851 "timmy" # Christiansfeld, Denmark<br />
-6.1808 106.8239 "metromini" # Jakarta, Indonesia<br />
32.0823 34.811 "z4ziggy" # Ramat Gan, Israel<br />
32.2188 34.8447 "Greycloack" # Bnei-Zion, Israel<br />
52.271 10.4831 "yogi" # Braunschweig, Germany<br />
46.0424 14.4869 "iom" # Ljubljana, Slovenia<br />
45.4058 -75.6413 "ith140" # Ottawa, ON, Canada<br />
12.58 77.38 "shastry" # Bangalore, Karnataka, India<br />
63.1753 27.6287 "mclang" # Pöljä, Finland<br />
18.55 72.54 "priyank" # Mumbai, Maharashtra, India<br />
51.37 6.17 "Lone_Wolf" # Venlo, Netherlands<br />
45.0387 7.6698 "Arrakis" # Torino, Italy<br />
48.4286 -123.3655 "apeiro" # Victoria, BC, Canada<br />
40.058 -75.4008 "Andrewski" # Wayne, PA, USA<br />
35.484807 -80.601536 "jerrym" # Kannapolis, NC, USA<br />
40.715231 -73.987681 "darose" # New York City, NY, USA<br />
59.8574 10.6782 "nut543" # Nesodden, Norway<br />
35.6333 -77.4000 "iBertus" # Greenville, NC, USA<br />
33.6459 -112.0183 "celti" # Phoenix, AZ, USA<br />
56.0514 24.3529 "/dev/null" # Pasvalys, Lithuania<br />
59.3327 18.0645 "Lunke" # Stockholm, Sweden<br />
49.2358 12.6296 "hellwoofa" # Oberpfalz, Bavaria, Germany<br />
1.2988 103.825 "rasat" # Singapore, Singapore<br />
52.7106 4.6963 "Marco`" # Schoorl, The Netherlands<br />
51.1936 4.1788 "Pieter" # Sint-Niklaas, Belgium<br />
42.743348 -87.8053 "ovrclkr" # Racine, WI, USA<br />
50.5814 5.4207 "Michel" # Maasmechelen, Belgium<br />
39.991 -105.239 "stonecrest" # Boulder, CO, USA<br />
41.488 -87.343 "rayjgu3" # Merrillville, IN, USA<br />
13.9161 -89.3336 "rdoggsv" # San Salvador, El Salvador<br />
34.2205 -116.05 "jeebusroxors" # Twentynine Palms, CA, USA<br />
21.2748 157.819 "bosewicht" # Honolulu, HI, USA<br />
47.5583 7.5808 "dp" # Basel, Switzerland<br />
53.5805 9.7059 "baze" # Wedel, Germany<br />
50.877 4.705 "FUBAR" # Leuven, Belgium<br />
50.9661 20.6849 "zergu" # Zagnansk, Poland<br />
43.4829 -80.5284 "Cerebral" # Waterloo, ON, Canada<br />
36.2969 28.151 "stavrosg" # Afandou, Rhodes, Greece<br />
35.0828 -86.5753 "deficite" # Fayetteville, Tennessee, United States of America<br />
55.4073 -1.7023 "kern" # Northumberland, England, United Kingdom<br />
53.2094 6.5507 "iLLucionist" # Groningen, The Netherlands<br />
52.3411 -0.2023 "Sudman1" # Huntingdon, United Kingdom<br />
48.4132 2.7293 "MSeb" # Avon, France<br />
48.6889 6.1781 "wain" # Nancy, France<br />
39.0083 -94.6367 "bpisciot" # Prairie Village, KS, USA<br />
50.2355 8.7676 "mo_no" # Karben, Germany<br />
41.5058 -81.4653 "msg43" # Cleveland, Ohio<br />
40.3348 -3.8638 "kagan" # Mostoles, Madrid, Spain<br />
-28.2601 -52.3826 "BlackFenix" # Passo Fundo, RS, Brazil<br />
47.4824 -0.5126 "fouiny" # Angers, France<br />
49.0552 2.0455 "DesmoJ" # Cergy, France<br />
55.7465 37.6319 "nariall" # Moscow, Russia<br />
48.7092 2.2407 "oxman" # Palaiseau, France<br />
45.7317 4.8928 "rem" # Bron, France<br />
45.5088 -73.5541 "Snowman" # Montréal, QC, Canada<br />
46.8276 -71.3175 "SolarBear" # Québec, QC, Canada<br />
53.2459 -1.3771 "Renners" # Chesterfield, UK<br />
34.0703 -118.4533 "jbloom" # Los Angeles, CA<br />
47.2970 -122.1606 "biryoku" # Auburn, WA, USA<br />
55.9533 -3.1889 "samsara" # Edinburgh, United Kingdom<br />
59.9174 10.7624 "postlogic" # Oslo, Norway<br />
51.462 -2.6094 "al" # Bristol, England, UK<br />
19.0671 -72.7427 "hackmykack" # Bombay, Maharashtra, India<br />
47.1700 27.5699 "epo" # Iasi, Romania<br />
49.1848 -0.3578 "kozaki" # Caen, France<br />
48.5691 10.4299 "matsche" # Lauingen, Germany<br />
45.0555 24.4791 "Oin" # Ramnicu Valcea, Romania<br />
35.9134 139.4883 "huge" # Saitama, Japan<br />
51.898 4.5428 "Idovitz" # Rotterdam, Netherlands<br />
40.703613 73.896122 "shadrach" # Brooklyn, New York USA<br />
51.8015 10.3386 "rebel" # Clausthal, Lower Saxony, Germany <br />
-42.761 -65.0573 "Francisco" # Puerto Madryn, Argentina<br />
58.384 26.7061 "janwil" # Tartu, Estonia <br />
56.9611 24.1752 "Stalwart" # Riga, Latvia<br />
49.2178 18.7337 "kajn" # Zilina, Slovakia<br />
36.116534 80.083115 "Bysshe" # Kernersville, NC, USA<br />
52.542 13.3758 "dma147" # Berlin, Germany<br />
55.6757 12.3605 "Andarki" # Albertslund, Denmark<br />
49.3485 23.5165 "Romashka" # Drohobych, Ukraine<br />
45.049582 -93.246095 "jskier" # Minneapolis, MN, USA<br />
53.13 23.15 "Krzysiek_W" # Bialystok, Poland<br />
49.8688 8.9287 "Moo-Crumpus" # Groß-Umstadt, Germany<br />
34.529081 -117.2132 "jerryvb" # Apple Valley, CA, USA<br />
50.8594 4.6864 "xirus" # Leuven, Belgium<br />
47.2675 11.391 "MaceM" # Innbruck, Austria<br />
-34.6244 -58.4444 "sud_crow" # Capital Federal, Buenos Aires, Argentina<br />
51.5209 -0.0198 "arooaroo" # London, UK<br />
45.4595 9.1657 "rensel" # Milano, Italy<br />
-31.7811 115.7394 "B15HOP" # Mullaloo, WA, Australia<br />
50.8377 -0.7749 "dtw" # Chichester, UK<br />
44.6664 -74.9741 "starsoldier" # Potsdam, NY, USA<br />
48.4489 -123.3619 "bneate" # Victoria, BC, Canada<br />
48.5681 -123.4005 "Xentac" # Victoria, BC, Canada<br />
59.9266 10.7727 "bogomipz" # Oslo, Norway<br />
38.0321 23.7367 "osigen" # Athens, Greece<br />
51.3898 5.4431 "citral" # Waalre, The Netherlands<br />
22.2222 113.5343 "fallen" # Zhuhai, China<br />
27.4597 -82.6307 "whot" # Bradenton, Florida, USA<br />
47.2887 5.0607 "fogoh" # Longvic, France<br />
35.323 25.1081 "Phoinix" # Akis, Greece, Heraclion Crete<br />
40.1028 104.9309 "k-dub" # Frederick, CO, USA<br />
42.5802 -71.1635 "Arenium" # Massachusetts<br />
51.3843 -0.0973 "born1956" # Croydon, UK<br />
42.1554 -71.6505 "Freyrs" # Massachusetts<br />
57.6427 -3.5525 "Deggy" # Forres, UK<br />
51.2316 6.8558 "HerrSchmitt" # Duesseldorf, Germany<br />
45.5161 -122.6819 "lakanta" # Portland, OR, USA<br />
-33.7082 151.1035 "multixrulz" # Waitara, Sydney, NSW Australia<br />
42.716 -71.1562 "JesusFranco" # Lawrence, Massachusetts, USA<br />
61.4657 23.8388 "Gval" # Tampere, Finland<br />
50.7837 18.9657 "swiergot" # Blachownia, Poland<br />
49.3559 8.1523 "Silvio" # Neustadt/Wstr., Germany<br />
41.1547 -8.6204 "Alexo" # Porto, Portugal<br />
48.1362 17.1291 "no4" # Bratislava, Slovakia<br />
43.661 -79.4056 "BigBadPenguin" # Toronto, ON, Canada<br />
48.8984 14.5681 "myx" # Strážkovice, Czech Republic<br />
50.0282 14.4531 "havli" # Prague, Czech Republic<br />
49.5571 14.3521 "beda" # Vilasova Lhota, Czech Republic<br />
49.8284 18.1638 "apr01" # Ostrava, Czech Republic<br />
49.7939 18.1729 "KBBL" # Ostrava, Czech Republic<br />
48.1362 17.1291 "marek" # Bratislava, Slovakia<br />
50.078 14.4239 "Mikos" # Prague, Czech Republic<br />
60.1594 24.8885 "Sami" # Helsinki, Finland<br />
49.7424 13.6006 "wocas_0x1" # Mirošov, Czech Republic<br />
48.2848 17.7366 "Tatinko" # Sered, Slovakia<br />
43.4673 -80.519 "Chris_H-C" # Waterloo, Ontario, Canada<br />
48.4497 17.5172 "Junckritter" # Trnava, Slovakia<br />
49.949 15.25861 "appolito" # Kutná Hora, Czech Republic<br />
40.793 -77.8522 "vande198" # State College, PA, USA<br />
-22.8174 -47.0968 "Newton_C" # Campinas, SP, Brazil<br />
49.7926 18.2492 "twinsen" # Ostrava, Czech Republic<br />
48.1531 17.1297 "juice" # Bratislava, Slovakia<br />
35.6686 139.824 "bryce" # Tokyo, Japan<br />
34.101586 -118.053652 "Arch" # Temple City, CA, USA<br />
38.1598 13.3604 "JoeyrS" # Palermo, Italy<br />
63.4228 10.3939 "allanon" # Trondheim, Norway<br />
48.1097 17.1122 "PetrYk" # Bratislava, Slovakia<br />
50.9092 -1.3943 "AxelFendersson" # Southampton, UK<br />
49.4403 6.657 "Searinox" # Merzig, Germany<br />
60.4853 22.2386 "pxi" # Turku, Finland<br />
48.0382 17.2549 "cm" # Hamuliakovo, Slovakia<br />
59.8410 30.4238 "EugenePhilippov" # St. Petersburg, Russia<br />
51.1680 4.4441 "evdvelde" # Mortsel, Belgium<br />
48.4497 17.5172 "mimoto" # Trnava, Trebisov, Slovakia<br />
50.9306 11.6204 "matrixp" # Jena, Germany<br />
41.869647 -72.371789 "azdruid" # Tolland, CT, USA<br />
48.8605 2.3115 "Aer" # Paris, France<br />
45.6655 -122.574 "droog" # Vancouver, WA, USA<br />
39.5578 -104.7845 "Ethilien" # Parker, CO, USA<br />
45.6721 3.1126 "kylliox" # St Amant-tallende, France<br />
42.9966 -89.5597 "Farhan" # Verona, WI, USA<br />
68.0400 686.0300 "Blaasvis" # Zwolle, The Netherlands<br />
45.4411 11.0184 "Slippery" # Verona, Italy<br />
51.9646 5.6624 "surrounder" # Wageningen, The Netherlands<br />
43.8164 11.0559 "furibondox" # Poggio a Caiano, Prato, Italy<br />
50.9532 -0.1424 "BenedictWhite" # At Work in Burgess Hill Sussex, England<br />
51.0097 -0.1377 "BenedictWhite" # At home Cuckfield Sussex, England<br />
45.6161 -72.9777 "PouletFou" # St-Hyacinthe, Québec<br />
41.8928 12.5553 "Bobonov" # Roma, Italy<br />
48.1097 17.1122 "Jelkosz" # Bratislava, Slovakia<br />
55.3925 10.4071 "Godballe" # Odense, Denmark<br />
50.7309 -3.5082 "Bralkein" # Exeter, Devon, UK<br />
63.4207 10.3967 "lessthanjake" # Trondheim, Norway<br />
52.2158 5.9528 "Newjersey_nl" # Apeldoorn, The Netherlands<br />
19.0318 72.8487 "rohan" # Mumbai, India<br />
34.0004 -81.033418 "Infracephas" # Columbia, SC, USA<br />
49.8653 9.8998 "Legout" # Near Wuerzburg, Germany<br />
55.3917 10.3439 "Whargoul" # Odense, Denmark<br />
39.6692 20.8538 "Koukos" # Ioannina, Greece<br />
33.0041 -96.5394 "D1sc1pl3" # Wylie, TX, USA<br />
39.7876 -77.7012 "Rayzorblayde" # Greencastle, PA, USA<br />
48.3929 9.9808 "klapmuetz" # Ulm, Germany<br />
54.6012 25.1528 "Zolookas" # Vilnius, Lithuania<br />
50.8594 4.6864 "Lode" # Leuven, Belgium<br />
50.8594 4.6864 "eWoud" # Leuven, Belgium<br />
-43.5292 172.5592 "AlexW" # Christchurch, New Zealand<br />
45.5161 -122.6819 "cmhood" # Portland, OR, USA<br />
41.9714 12.437 "Bfg9000it" # Roma, Italy<br />
45.5619 9.2086 "alt-os" # Cinisello B., Italy<br />
45.435 12.141 "Pierluigi" # Mira, Italy<br />
34.3900 330100 "Antonis" # Lemesos, Cyprus<br />
39.8674 -83.0757 "JoeC" # Columbus, Oh, USA<br />
48.183 11.6093 "Dengar" # Munich, Germany<br />
50.9239 2.2336 "Helyo" # Bourbourg, France<br />
-29.9008 -71.2448 "failure" # La Serena, Chile<br />
-29.9438 -51.204 "yurijm" # Porto Alegre, Brazil<br />
33.0244 -117.2794 "android" # Cardiff by the Sea, CA, USA<br />
38.74740 -77.48537 "VLegacy" # Manassas, VA, USA<br />
56.7028 16.351 "nine" # Kalmar, Sweden<br />
38.7118 -9.3762 "tranquility" # Sao Joao do Estoril, Lisbon, Portugal<br />
50.0276 14.5248 "eqixat" # Prague, Czech Republic<br />
41.8526 12.5771 "Crow666" # Rome, Italy<br />
45.3624 10.3143 "nixxo" # Prevalle, Brescia, Italy<br />
45.7505 -122.8711 "marxom" # Scappoose, OR, USA<br />
39:54:25 116:19:55E "hongy19" # Beijing, China (unusable coordinates, fix)<br />
39.651426 -79.882429 "jp_fielding # Morgantown, WV, USA<br />
40.622493 73.9650074 "Mazaev" # Brooklyn, NY, USA<br />
51.5314 3.4419 "Michiel" # Westkapelle, Netherlands<br />
50.2917 18.6726 "TPJ" # Gliwice, Poland<br />
52.372 4.8534 "tehmaze" # Amsterdam, The Netherlands<br />
52.2906 4.9316 "MyZT" # Ouderkerk a/d Amstel, The Netherlands<br />
41.2598 1.7726 "josarn" # Sant Pere de Ribes, Barcelona, Spain<br />
27.7772 -82.7062 "thegnu" # St. Petersburg, FL, USA<br />
38.040628 84.543325 "mindtriggerz" # Lexington, KY, USA<br />
42.279379 83.783998 "iKevin" # Ann Arbor, MI, USA<br />
42.1384 24.7664 "iko" # Plovdiv, Bulgaria<br />
46.1024 14.44456 "Slav" # Ljubljana, Slovenia<br />
55.5841 13.0038 "Tor" # Malmö, Sweden<br />
45.3109 8.8648 "drizzt" # Vigevano (PV), Italia<br />
46 2502 121.38 "Beetlenut" # Taipei, Taiwan<br />
51.618 -87.8385 "waabimiigwan" # Eabametoong, ON, Canada<br />
51.985 9.5378 "querdenker" # Bodenwerder/Linse, Germany<br />
43.2932 -2.9906 "Dienadel" # Barakaldo, Basque Country, Spain<br />
28.1232 -15.443 "Finnberg" # Las Palmas de Gran Canaria, Spain<br />
53.5208 -113.513 "Kornhole" # Edmonton, AB, Canada<br />
59.9174 10.7624 "Egil.B" # Oslo, Norway<br />
48.3057 18.0851 "depi" # Nitra, Slovakia <br />
-42.9016 147.3773 "neonnds" "[(-.-)]" # Hobart, Tasmania, Australia<br />
-33.3557 -70.4634 "Celeron" # Santiago, Chile<br />
52.2475 21.2976 "Karc" # Sulejówek, Poland<br />
30.6568 -96.3354 "BroodingDogma" # Bryan, Texas, USA<br />
51.8203 0.746 "Stupidboy" # Tiptree, Essex, UK <br />
49.6037 11.0003 "Manji" # Erlangen, Bavaria, Germany<br />
38.2513 21.7422 "blackpit" # Patrai (or Patras), Greece<br />
45.3327 -93.1555 "kernel528" # Wyoming, Minnesota, USA<br />
40.212064 -74.822153 "phydeaux" # Morrisville, Pennsylvania, USA<br />
34.7086 33.0267 "neok" # Lemesos, Cyprus<br />
45.4058 -75.6413 "dadexter" # Ottawa, ON, Canada<br />
35.2147 -106.6623 "Linux Rocks" # Rio Rancgo, NM, USA<br />
-33.9332 18.406 "dave42" # Cape Town, South Africa<br />
-44.3899 171.2306 "hads" # Timaru, New Zealand<br />
-33.0383 -71.6133 "kronin" # Valparaiso, Chile<br />
45.4445 9.2643 "mOLOk" # Milano, Italy<br />
59.0515 9.7763 "Pappa" # Porsgrunn, Norway<br />
48.1791 16.3237 "jMCg" # Vienna, Austria<br />
51.2176 3.2721 "g_bertje" # Brugge, Belgium<br />
37.2076 -87.1806 "DEBuGRR" # Greenville, KY, USA<br />
-23.5348 -46.5606 "amb" # São Paulo, SP, Brazil<br />
25.6719 -100.2969 "oscarello" # Monterrey, NL, México<br />
45.569 -73.254 "drynish" # Montréal, QC, Canada<br />
41.9522 12.545 "rfilippone" # Roma, Lazio, Italy<br />
52.2374 6.8447 "Nrpil" # Enschede, The Netherlands<br />
38.7275 35.474 "yavuzselim" # Kayseri, Turkey<br />
48.6715 10.1679 "Leslie" # Giengen, Germany<br />
38.6804 -90.4343 "tribule" # St Louis, MO, USA<br />
37.9922 23.6796 "Mandos" # Athens, Greece<br />
52.5514 13.4135 "kth5" # Berlin, Germany<br />
38.6298 -121.2225 "Casey" # Sacramento, CA, USA<br />
28.0691 -80.6229 "ChrisX" # Melbourne, FL, USA<br />
40.7547874 -73.9869385 "Abhay" # New York, NY, USA<br />
53.9335 10.7065 "nagoola" # Bad Schwartau, Germany<br />
45.7542 4.8448 "barjo" # Lyon, France<br />
37.6006 15.1473 "gaiden" # Acireale, Italy<br />
44.5348 10.8262 "DaNiMoTh" # Modena, Italy<br />
38.0224 -121.3405 "mithus" # Stockton, Ca, USA<br />
53.63300 11.45400 "Pr0v4" # Livorno, Tuscany, Italy<br />
43.844 10.505 "Panther" # Lucca, Tuscany, Italy<br />
50.6278 3.0631 "p1pon" # Lille, France<br />
60.2993 5.31 "Solskogen" # Bergen, Norway<br />
19.01 72.50 "ravi" # Mumbai, Maharashtra, India<br />
47.1873 8.8288 "aamirtham" # Altendorf, Switzerland<br />
50.1164 14.4406 "otakar" # Prague, Czech Republic<br />
44.446 11.8332 "GeniE" # Massa Lombarda, Ravenna, Italia<br />
48.1044 -1.68 "Gandalf" # Rennes, France<br />
54.3375 10.0984 "s4rg.on" # Kronshagen, Germany<br />
</pre><br />
<br />
== Other Maps ==<br />
For the record, there is also a Frappr map: http://www.frappr.com/archlinux<br />
<br>Mindtriggerz also maintains a social networking map of the #archlinux IRC channel: <br />
<br />
http://mindtriggerz.net/images/archlinux/archlinux-current.png</div>Sargonhttps://wiki.archlinux.org/index.php?title=Mouse_buttons&diff=9031Mouse buttons2006-02-27T13:57:33Z<p>Sargon: /* Patching XOrg */</p>
<hr />
<div>[[Category:XServer]]<br />
<br />
=== About / Prerequisites ===<br />
<br />
This article is for users that have a mouse with more than 7 mouse buttons and want to be able to use all of them. Logitech makes several of these, and Microsoft makes a few as well. If you have one of these mice, read on!<br />
<br />
=== Patching XOrg ===<br />
<br />
The first thing you need to do is install Xorg evdev package. The [http://www.archlinux.org/packages.php?id=10240 package] could be found in current and is<br />
named [http://www.archlinux.org/packages.php?id=10240 xf86-input-evdev]. <br />
<br />
After it has been installed, modprobe the evdev module. <br />
<br />
modprobe evdev<br />
<br />
If everything is working, move on to the next section.<br />
<br />
=== Setting Up Your Mouse ===<br />
<br />
First we need to check to see which devices support the evdev protocol, so that we can configure XOrg properly.<br />
<br />
cat /proc/bus/input/devices<br />
<br />
This should return something like this:<br />
<br />
I: Bus=0003 Vendor=046d Product=c01d Version=2100<br />
N: Name="Logitech USB-PS/2 Optical Mouse"<br />
P: Phys=usb-0000:00:10.0-2/input0<br />
H: Handlers=mouse1 event3<br />
B: EV=7<br />
B: KEY=ff0000 0 0 0 0 0 0 0 0<br />
B: REL=103<br />
<br />
Note the event[X] in this line: <code>H: Handlers=mouse1 <strong>event3</strong></code>. We will be referring to that line when we change our xorg.conf.<br />
<br />
=== Setting Up XOrg ===<br />
<br />
Now we need to edit the XOrg configuration ( /etc/X11/xorg.conf ) and add a new mouse. Open /etc/X11/xorg.conf with whatever editor you want and look for the "InputDevice" section. Copy and paste the following below your existing mouse section.<br />
<br />
Section "InputDevice"<br />
Identifier "EvdevMouse"<br />
Driver "evdev"<br />
Option "Device" "/dev/input/event3"<br />
Option "Dev Name" "Logitech USB*"<br />
Option "Protocol" "IMPS/2" #for example ;-)<br />
Option "ZAxisMapping" "11 12"<br />
Option "Buttons" "12"<br />
EndSection<br />
<br />
You will have to edit this section accordingly. Change the "Device" line to match what you saw in the "Handlers" line. Chnage the "Dev Name" to match the "Name" line (use of wildcard (*) recommended). Change the "Buttons" to match what you have and change "ZAxisMapping" to match "Buttons" (ZAxisMapping refers to the last two buttons you have, so "4 5" for a 5 button mouse, "7 8" for a 8 button mouse, etc).<br />
<br />
The last thing we need to do here is add the new mouse to the XOrg "ServerLayout" at the top of xorg.conf. Comment out the other lines that end with "CorePointer" and add a new InputDevice. When you're done, it should look something like this:<br />
<br />
Section "ServerLayout"<br />
Identifier "XOrg Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
InputDevice "EvdevMouse" "CorePointer"<br />
#InputDevice "USB Mouse" "CorePointer"<br />
#InputDevice "PS/2 Mouse" "CorePointer"<br />
EndSection<br />
<br />
Now we are almost done! The last thing we have to do is tell X how to use the new mouse buttons and possibly set up some user tools.<br />
<br />
=== Post Configuration ===<br />
<br />
If you use .xinitrc to load X, then add this to .xinitrc (change for the number of buttons you have):<br />
<br />
xmodmap -e "pointer = 1 2 3 6 7 8 9 10 11 12 4 5" &<br />
<br />
Note that buttons 4 and 5 <strong>must go on the end</strong> or else your scroll wheel won't work.<br />
<br />
If you use GDM/XDM/KDM instead of .xinitrc, then create the file ~/.Xmodmap and add this to it (change for the number of buttons you have):<br />
<br />
pointer = 1 2 3 6 7 8 9 10 11 12 4 5<br />
<br />
You may have to play with these numbers a bit to get your desired behavior. Some mice use buttons 6 and 7 for the scroll wheel, in which case those buttons would have to be the last numbers. Keep playing with it until it works!<br />
<br />
You can also check to see which buttons are being read with a program called 'xev', which is part of XOrg. When xev is run, it will show a box on your desktop that you can put the cursor into and click buttons to find out what buttons have been mapped.<br />
<br />
=== User Tools ===<br />
<br />
If you use a Logitech mouse, there is a tool called lmctl which will help you set the proper resolution, enable or disable smart scroll, etc. This tool is available in the community repoisitory which is listed in the [[Unofficial user repositories]] .<br />
<br />
=== Credits ===<br />
<br />
[http://www.linux-gamers.net/modules/wfsection/article.php?articleid=46 linuX-gamers.net How-Tos: Getting all mouse buttons working in X]<br />
<br />
[http://www.bedroomlan.org/~alexios/coding_lmctl.html Alexios' LmCTL]</div>Sargonhttps://wiki.archlinux.org/index.php?title=NVIDIA&diff=9014NVIDIA2006-02-26T20:08:40Z<p>Sargon: /* Configuring X-Server */</p>
<hr />
<div>[[Category:Hardware]]<br />
[[Category:Kernel]]<br />
[[Category:XServer]]<br />
===How to install Nvidia Driver with pacman===<br />
<br />
====Info from Package Maintainer ''tpowa''====<br />
<br />
The package is for those people who run a stock arch kernel!<br />
I only test with kernel 2.6 and xorg.<br />
<br />
Multiple kernel users:<br />
You may need to install nvidia package for each extra!<br />
You may need to remove the kernel modules by hand after deinstall!<br />
<br />
<br />
====Installing drivers====<br />
<br />
You have to use extra repository, enable it for pacman.<br />
Leave X-Server, else pacman cannot finish installation and it will not work!<br />
run as root:<br />
pacman -Sy nvidia (for newer cards)<br />
pacman -Sy nvidia-legacy (for old cards)<br />
please look at the <code>README</code> from nvidia for information, which card is supported.<br />
<br />
If an error happens during install you can have a look at:<br />
/var/log/nvidia-installer.log<br />
<br />
====Configuring X-Server====<br />
<br />
Edit <code>/etc/X11/XF86Config</code> or your <code>/etc/X11/xorg.conf</code> config file:<br />
Disable in modules section:<br />
<code>GLcore</code> and <code>DRI</code><br />
<br />
Add to modules section:<br />
Load "glx"<br />
<br />
Disable <code>Section DRI</code> completely:<br />
#Section "DRI"<br />
# Mode 0666<br />
#EndSection<br />
<br />
Change <code>Driver "nv"</code> to <code>Driver "nvidia"</code><br />
If it exists disable <code>Chipset</code> option (only needed for nv driver).<br />
<br />
This was for basic setup, if you need more tweaking options<br />
have a look at <code>/usr/share/doc/NVIDIA_GLX-1.0/README.txt</code>.<br />
<br />
====Modifying Arch <code>rc.conf</code> file====<br />
<br />
Add <code>nvidia</code> to <code>/etc/rc.conf</code> MODULES section (not needed anymore if you run xorg and udev).<br />
Needed for nvidia-legacy and kernel >=2.6.13!<br />
<br />
If you would like to prevent having to reinstall the nvidia driver after kernel upgrades, add <code>nvidia</code> to your DAEMONS section as well.<br />
<br />
====Problems that might occur====<br />
<br />
=====Nvidia specific=====<br />
<br />
Having no Pictures in KDE/Xorg7:<br />
ln -s /usr/lib/libGL.so /usr/lib/libGLU.so<br />
<br />
<br />
<br />
If you experience slow 3D Performance have a look at<br />
<code>/usr/lib/libGL.so.1</code>, <code>/usr/lib/libGL.so</code>, <code>/usr/lib/GLcore.so.1</code><br />
Perhaps they are wrong linked to mesa or something else.<br />
Try reinstalling with <code>pacman -S nvidia</code>.<br />
<br />
If you experience errors like <code>/usr/bin/ld: cannot find -lGLU</code> when compiling applications, don't install mesa just use this command:<br />
ln -s /usr/X11R6/lib/libGLU.so /usr/lib/libGLU.so<br />
<br />
When you get this message when you try to start an openGL application (for example enemy-territory, or glxgears):<br />
Error: Could not open /dev/nvidiactl because the permissions are too restrictive. Please see the <code>FREQUENTLY ASKED QUESTIONS</code> section of <code>/usr/share/doc/NVIDIA_GLX-1.0/README</code> for steps to correct.<br />
<br />
Add yourself to the <code>video</code> group using <code>gpasswd -a ''yourusername'' video</code> (don't forget to log out and back in).<br />
<br />
=====Arch specific=====<br />
<br />
'''GCC update:'''<br />
You must compile the module with the compiler that was used for the kernel<br />
else it may fail.<br />
A simple <code>pacman -S nvidia</code> should do it, if not wait for a new kernel release and stay with old kernel and gcc.<br />
<br />
'''Kernel update:'''<br />
Kernel updates will require reinstalling the driver. A workaround is [http://wiki.archlinux.org/index.php/How_to_install_NVIDIA_driver#Modifying_Arch_rc.conf_file available].<br />
<br />
====Driver Config Tool====<br />
<br />
The new config tool for the nvidia-drivers is included called 'nvidia-settings'<br />
You don't have to use it it's only a add-on! <br><br />
For more information about the use, have a look at the following file:<br><br />
/usr/share/doc/NVIDIA_GLX-1.0/nvidia-settings-user-guide.txt<br><br />
Please install gtk2 with "pacman -S gtk2" in order to use this tool.<br />
<br />
'''NOTE:'''<br />
If you experience problems like crashing the X-Server while running the tool<br />
you have to delete your <code>.nvidia-settings-rc</code> file in your home directory.<br />
<br />
====Known Issues====<br />
<br />
If you experience crashes, try to disable <code>RenderAccel "true"</code> option.<br />
<br />
If you have nvidia installer complaining about different versions of gcc between the current one and the one used for compiling the kernel then see on how to install the traditional way but remember to <code>export IGNORE_CC_MISMATCH=1</code><br />
<br />
If you have comments on the package please post it here: http://bbs.archlinux.org/viewtopic.php?t=10692<br />
If you have a problem with the drivers have a look at the nvidia forum: http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14<br />
For a Changelog please look here: http://www.nvidia.com/object/linux_display_ia32_1.0-7676.html<br />
<br />
Note: please don't change the above part without notifying me.<br />
<br />
<br />
===How to install NVIDIA Driver the traditional way===<br />
<br />
* Download the latest NVIDIA driver from: http://www.nvidia.com/object/linux.html<br />
File name will look something like this: <code>NVIDIA-Linux-x86-1.0-7167-pkg0.run</code><br />
<br />
The Kernel Steps (the following 4 steps) can be left out if you use at least kernel 2.6.5 because the needed Includes are now in the Kernel package<br />
<br />
* Download the kernel source for the kernel version you are using<br />
<code>uname -r</code> will give you kernel version<br />
** http://www.kernel.org/pub/linux/kernel/v2.6/ - for the 2.6 series<br />
** http://www.kernel.org/pub/linux/kernel/v2.4/ - for the 2.4 series<br />
<br />
* Move the current incomplete kernel source tree to 2.x.x.old:<br />
mv /usr/src/2.x.x /usr/src/2.x.x.old<br />
<br />
* Uncompress and unpack your source code in <code>/usr/src</code>:<br />
mv /path/to/linux-2.x.x.tar.bz2 /usr/src<br />
cd /usr/src<br />
tar --bzip2 -xvf linux-2.x.x.tar.bz2<br />
<br />
* Copy the old include directory and <code>.config</code> file into new source tree:<br />
cp -rp linux-2.x.x.old/include/ linux-2.x.x/include/<br />
cp linux-2.x.x.old/.config linux-2.x.x/.config<br />
<br />
* Go to a non-graphical session<br />
** Use Control-Alt-F5 (or whatever F key you want)<br />
** Login as root<br />
** Go to runlevel 3<br />
init 3<br />
<br />
* Run NVIDIA installer<br />
sh /path/to/NVIDIA-Linux-x86-1.0-5336-pkg0.run<br />
You will be asked to accept their license, then hit OK a couple times on informational screens, the driver will then be built and installed<br />
<br />
* Edit XFree86Config file<br />
** Use the editor of choice to open <code>/etc/X11/XFree86Config</code> and go to the <code>Device</code> section<br />
** Change your driver from current (probably <code>nv</code> or <code>vesa</code>) to <code>nvidia</code>:<br />
*** <code>Driver "nv"</code> to <code>Driver "nvidia"</code><br />
** Uncomment the glx load line<br />
*** <code>#Load "glx"</code> to <code>Load "glx"</code><br />
** Comment or delete the Chipset line if exists<br />
<br />
* Edit modules loaded on boot<br />
** Open <code>/etc/rc.conf</code> in editor<br />
** Add <code>nvidia</code> to modules section<br />
MODULES=(''... some modules ...'' nvidia)<br />
<br />
* Reboot the machine and enjoy 3D acceleration...and a tainted kernel :)</div>Sargon