https://wiki.archlinux.org/api.php?action=feedcontributions&user=Taylorchu&feedformat=atomArchWiki - User contributions [en]2024-03-29T00:35:53ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Plymouth&diff=274300Plymouth2013-09-04T02:24:27Z<p>Taylorchu: /* Changing the Theme */</p>
<hr />
<div>[[Category:Bootsplash]]<br />
[[cs:Plymouth]]<br />
[[es:Plymouth]]<br />
[[it:Plymouth]]<br />
[[ja:Plymouth]]<br />
[[ru:Plymouth]]<br />
[[zh-CN:Plymouth]]<br />
[http://www.freedesktop.org/wiki/Software/Plymouth Plymouth] is a project from Fedora providing a flicker-free graphical boot process. It relies on [[kernel mode setting]] (KMS) to set the native resolution of the display as early as possible, then provides an eye-candy splash screen leading all the way up to the login manager.<br />
<br />
== Preparation ==<br />
{{Warning|Plymouth is currently under heavy development and may contain bugs.}}<br />
Plymouth primarily uses [[KMS]] (Kernel Mode Setting) to display graphics. If you can't use KMS (e.g. because you are using a proprietary driver) you will need to use [[Framebuffer#Framebuffer_Resolution|framebuffer]] instead. Uvesafb is recommended as it can function with widescreen resolutions.<br />
<br />
If you have neither KMS nor a framebuffer, Plymouth will fall back to text-mode.<br />
<br />
==Installation==<br />
Plymouth is not presently available in the [[Official Repositories]], and will need to be installed from the [[AUR]].<br />
<br />
The stable one is called {{AUR|plymouth}} and the git version {{AUR|plymouth-git}}.<br />
<br />
==Configuration==<br />
<br />
===Including Plymouth in the Initcpio===<br />
<br />
Add Plymouth to the HOOKS array in {{ic|/etc/[[mkinitcpio.conf]]}}. It '''must''' be added ''after'' '''base''' and '''udev''' for it to work:<br />
{{hc|/etc/mkinitcpio.conf|2=HOOKS="base udev plymouth [...] "}}<br />
<br />
{{Warning|If you use [[System Encryption with LUKS for dm-crypt|hard drive encryption]] with the '''encrypt''' hook, you ''must'' replace the '''encrypt''' hook with '''plymouth-encrypt''' in order to get to the TTY password prompts.}}<br />
<br />
For early KMS start add the module [[radeon]] (for radeon cards), [[Intel|i915]] (for intel cards) or [[nouveau]] (for nvidia cards) to the MODULES line in {{ic|/etc/mkinitcpio.conf}}:<br />
<br />
{{hc|/etc/mkinitcpio.conf|2=MODULES="i915"<br />
'''or'''<br />
MODULES="radeon"<br />
'''or'''<br />
MODULES="nouveau"}}<br />
<br />
Rebuild your initrd image (refer to the [[mkinitcpio]] article for more info):<br />
{{bc|# mkinitcpio -p [name of your kernel preset]}}<br />
<br />
===The kernel command line===<br />
<br />
You now need to set {{ic|quiet splash}} as you kernel command line parameters in your bootloader. See [[Kernel parameters]] for more info.<br />
<br />
===Changing the Theme===<br />
<br />
Plymouth comes with a selection of themes:<br />
#'''Fade-in''': "Simple theme that fades in and out with shimmering stars"<br />
#'''Glow''': "Corporate theme with pie chart boot progress followed by a glowing emerging logo"<br />
#'''Script''': "Script example plugin" (Despite the description seems to be a quite nice Arch logo theme)<br />
#'''Solar''': "Space theme with violent flaring blue star"<br />
#'''Spinner''': "Simple theme with a loading spinner" ''(default)''<br />
#'''Spinfinity''': "Simple theme that shows a rotating infinity sign in the center of the screen"<br />
#''('''Text''': "Text mode theme with tricolor progress bar")''<br />
#''('''Details''': "Verbose fallback theme")''<br />
<br />
To show the current theme:<br />
<br />
{{hc|$ plymouth-set-default-theme|<br />
spinner}}<br />
<br />
To list all currently installed themes:<br />
<br />
{{bc|$ plymouth-set-default-theme -l}}<br />
<br />
To preview the themes without rebooting, hit {{ic|Ctrl+Alt+F2}} to change to console, log in as root and type:<br />
<br />
{{bc|# plymouthd<br># plymouth --show-splash}}<br />
<br />
To quit the preview hit {{ic|Ctrl+Alt+F2}} again and type:<br />
<br />
{{bc|# plymouth --quit}}<br />
<br />
To set your desired theme and rebuild your kernel image:<br />
{{bc|# plymouth-set-default-theme -R <theme name>}}<br />
<br />
And reboot.<br />
<br />
==See also==<br />
[http://fedoraproject.org/wiki/Releases/FeatureBetterStartup Original Spec]<br />
<br />
[https://bbs.archlinux.org/viewtopic.php?id=81406 A related forum thread]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Plymouth&diff=274299Plymouth2013-09-04T02:22:28Z<p>Taylorchu: /* Including Plymouth in the Initcpio */</p>
<hr />
<div>[[Category:Bootsplash]]<br />
[[cs:Plymouth]]<br />
[[es:Plymouth]]<br />
[[it:Plymouth]]<br />
[[ja:Plymouth]]<br />
[[ru:Plymouth]]<br />
[[zh-CN:Plymouth]]<br />
[http://www.freedesktop.org/wiki/Software/Plymouth Plymouth] is a project from Fedora providing a flicker-free graphical boot process. It relies on [[kernel mode setting]] (KMS) to set the native resolution of the display as early as possible, then provides an eye-candy splash screen leading all the way up to the login manager.<br />
<br />
== Preparation ==<br />
{{Warning|Plymouth is currently under heavy development and may contain bugs.}}<br />
Plymouth primarily uses [[KMS]] (Kernel Mode Setting) to display graphics. If you can't use KMS (e.g. because you are using a proprietary driver) you will need to use [[Framebuffer#Framebuffer_Resolution|framebuffer]] instead. Uvesafb is recommended as it can function with widescreen resolutions.<br />
<br />
If you have neither KMS nor a framebuffer, Plymouth will fall back to text-mode.<br />
<br />
==Installation==<br />
Plymouth is not presently available in the [[Official Repositories]], and will need to be installed from the [[AUR]].<br />
<br />
The stable one is called {{AUR|plymouth}} and the git version {{AUR|plymouth-git}}.<br />
<br />
==Configuration==<br />
<br />
===Including Plymouth in the Initcpio===<br />
<br />
Add Plymouth to the HOOKS array in {{ic|/etc/[[mkinitcpio.conf]]}}. It '''must''' be added ''after'' '''base''' and '''udev''' for it to work:<br />
{{hc|/etc/mkinitcpio.conf|2=HOOKS="base udev plymouth [...] "}}<br />
<br />
{{Warning|If you use [[System Encryption with LUKS for dm-crypt|hard drive encryption]] with the '''encrypt''' hook, you ''must'' replace the '''encrypt''' hook with '''plymouth-encrypt''' in order to get to the TTY password prompts.}}<br />
<br />
For early KMS start add the module [[radeon]] (for radeon cards), [[Intel|i915]] (for intel cards) or [[nouveau]] (for nvidia cards) to the MODULES line in {{ic|/etc/mkinitcpio.conf}}:<br />
<br />
{{hc|/etc/mkinitcpio.conf|2=MODULES="i915"<br />
'''or'''<br />
MODULES="radeon"<br />
'''or'''<br />
MODULES="nouveau"}}<br />
<br />
Rebuild your initrd image (refer to the [[mkinitcpio]] article for more info):<br />
{{bc|# mkinitcpio -p [name of your kernel preset]}}<br />
<br />
===The kernel command line===<br />
<br />
You now need to set {{ic|quiet splash}} as you kernel command line parameters in your bootloader. See [[Kernel parameters]] for more info.<br />
<br />
===Changing the Theme===<br />
<br />
Plymouth comes with a selection of themes:<br />
#'''Fade-in''': "Simple theme that fades in and out with shimmering stars"<br />
#'''Glow''': "Corporate theme with pie chart boot progress followed by a glowing emerging logo"<br />
#'''Script''': "Script example plugin" (Despite the description seems to be a quite nice Arch logo theme)<br />
#'''Solar''': "Space theme with violent flaring blue star" and <br />
#'''Spinfinity''': "Simple theme that shows a rotating infinity sign in the center of the screen" ''(default)''<br />
#''('''Text''': "Text mode theme with tricolor progress bar")''<br />
#''('''Details''': "Verbose fallback theme")''<br />
<br />
To show the current theme:<br />
<br />
{{hc|$ plymouth-set-default-theme|<br />
spinfinity}}<br />
<br />
To list all currently installed themes:<br />
<br />
{{bc|$ plymouth-set-default-theme -l}}<br />
<br />
To preview the themes without rebooting, hit {{ic|Ctrl+Alt+F2}} to change to console, log in as root and type:<br />
<br />
{{bc|# plymouthd<br># plymouth --show-splash}}<br />
<br />
To quit the preview hit {{ic|Ctrl+Alt+F2}} again and type:<br />
<br />
{{bc|# plymouth --quit}}<br />
<br />
To set your desired theme and rebuild your kernel image:<br />
{{bc|# plymouth-set-default-theme -R <theme name>}}<br />
<br />
And reboot.<br />
<br />
==See also==<br />
[http://fedoraproject.org/wiki/Releases/FeatureBetterStartup Original Spec]<br />
<br />
[https://bbs.archlinux.org/viewtopic.php?id=81406 A related forum thread]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Pacman/Package_signing&diff=170700Pacman/Package signing2011-11-21T05:04:44Z<p>Taylorchu: /* Setup */</p>
<hr />
<div>[[Category:Pacman development (English)]]<br />
{{i18n|Pacman-key}}<br />
[[fr:pacman-key]]<br />
<br />
pacman-key is a new tool available with pacman 4. It allows the user to manage pacman's list of trusted keys in the new package signing implementation. For some background on this issue, see [http://allanmcrae.com/2011/08/pacman-package-signing-2-pacman-key/ this] blog entry and the [https://wiki.archlinux.org/index.php/Package_Signing_Proposal_for_Pacman package signing proposal] wiki page.<br />
<br />
==Overview of keys and fingerprints==<br />
A PGP key allows developers to uniquely sign their package, ensuring they made the package and the file did not come from someone impersonating them.<br />
<br />
===Fingerprint or keyid===<br />
* A fingerprint is a short version of the key that can be used to identify the key without needing the entire (sometime rather long) key. It's the "name" of the key. In the pacman documentation these are what are referred to as keyids.<br />
* Fingerprint formats<br />
** Fingerprints such as "6645 B0A8 C700 5E78 DB1D 7864 F99F FE0F EAE9 99BD" need to be compressed to "6645B0A8C7005E78DB1D7864F99FFE0FEAE999BD" (spaces removed)<br />
** The "0x" bit in front of the key is optional. It can be added/dropped and still work.<br />
<br />
===Keyservers===<br />
* PGP key servers store key files and allow you to look up keys based on fingerprints. One can be specified with the {{ic|--keyserver}} option.<br />
* hkp://pgp.mit.edu is one PGP key server that it seems the Archlinux developers like using.<br />
* The default keyserver can be changed in {{ic|/etc/pacman.d/gnupg/gpg.conf}}.<br />
<br />
==Setup==<br />
To disable PGP key checking completely, add the following line to {{ic|/etc/pacman.conf}}:<br />
SigLevel = Never<br />
<br />
To set up the pacman-key gpg key storage use:<br />
# pacman-key --init<br />
<br />
<br />
The SigLevel directive takes three main values: Required, which forces signature checking to be performed; Optional (default), which will check signatures if present but unsigned packages and databases will be accepted; and Never, which sets no signature checking to be preformed.<br />
<br />
==Adding keys==<br />
When pacman encounters unknown keys on packages, it will ask the user whether to add them. Keys can also be added by downloading the PGP key file yourself and running '{{ic|pacman-key -a key-file}}' or by retrieving the key file from a key server based on the fingerprint. The latter is simpler and explained below.<br />
* Find the fingerprint of a developer's key: visit the [https://www.archlinux.org/developers/ developers page] and find a PGP Key link. The link text is the fingerprint.<br />
* Run the command {{ic|pacman-key -r <fingerprint> --keyserver <key server>}}. For the <key server> use "hkp://pgp.mit.edu".<br />
* {{ic|pacman-key -l}} will list the keys you added<br />
* This adds the keys to the keyring but leaves the trust level as "unknown". <br />
<br />
==Key signing==<br />
For the key to work the trust level needs to be changed.<br />
<br />
To sign the key locally, use:<br />
<br />
# pacman-key --lsign-key <keyid><br />
<br />
This can also be done using the gpg tsign command or equivalently {{ic|pacman-key --edit-key "<fingerprint>"}} and then {{ic|tsign}} <br />
<br />
Or pacman can be told to trust any key in its keyring. For the latter, add ONE of the following to {{ic|/etc/pacman.conf}}<br />
SigLevel = Required TrustAll<br />
SigLevel = Optional TrustAll<br />
<br />
==Script to add all the developer PGP keys from the [https://www.archlinux.org/developers/ developers page]==<br />
This script uses elinks to download the developer page, extracts PGP key fingerprints and uses {{ic|pacman -r --keyserver pgp.mit.edu}} to add them to the pacman key store.<br />
<br />
Use with caution. It is possible that someone will hack the developer page and insert a malicious PGP key, making the whole signing process useless.<br />
<br />
This has to be run as root to add keys or add a sudo before the pacman-key command.<br />
<br />
elinks -no-numbering -dump <nowiki>https://www.archlinux.org/developers/</nowiki> | \<br />
awk '$1 $2 == "PGPKey:" && $3 != "Unknown"{$1="";$2="";print}' | \<br />
tr -dc '\n[:alnum:]' | while read fingerprint ; do <br />
pacman-key -r "$fingerprint" --keyserver pgp.mit.edu ; done<br />
<br />
==Script to add all the trusted user PGP keys from the [https://www.archlinux.org/trustedusers/ trustedusers page]==<br />
This script uses elinks to download the trustedusers page, extracts PGP key fingerprints and uses {{ic|pacman -r --keyserver pgp.mit.edu}} to add them to the pacman key store.<br />
<br />
Use with caution. It is possible that someone will hack the trustedusers page and insert a malicious PGP key, making the whole signing process useless.<br />
<br />
This has to be run as root to add keys or add a sudo before the pacman-key command.<br />
<br />
elinks -no-numbering -dump <nowiki>https://www.archlinux.org/trustedusers/</nowiki> | \<br />
awk '$1 $2 == "PGPKey:" && $3 != "Unknown"{$1="";$2="";print}' | \<br />
tr -dc '\n[:alnum:]' | while read fingerprint ; do <br />
pacman-key -r "$fingerprint" --keyserver pgp.mit.edu ; done</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=MPlayer&diff=165030MPlayer2011-10-11T02:19:24Z<p>Taylorchu: /* Installation */</p>
<hr />
<div>[[Category:Audio/Video (English)]]<br />
{{i18n|MPlayer}}<br />
[[fr:MPlayer]]<br />
<br />
'''MPlayer''' is a popular movie player for GNU/Linux. It has support for pretty much every video and audio format out there and is hence very versatile, even though most people use it for viewing videos.<br />
<br />
==Installation==<br />
The {{Package Official|mplayer}} package is available in [extra]:<br />
# pacman -S mplayer<br />
<br />
Alternatively, the latest development version can be install from the [[AUR]] ({{Package AUR|mplayer-svn}}).<br />
<br />
You may also want to try [http://www.mplayer2.org/ mplayer2], a fork of mplayer:<br />
<br />
# pacman -S mplayer2<br />
<br />
mplayer2 has several improvements over mplayer. see [http://www.mplayer2.org/comparison.html mplayer2 vs mplayer]<br />
<br />
==Additional installation tips==<br />
<br />
===Frontends/GUIs===<br />
There are several GUIs for MPlayer.<br />
* Qt: {{Package Official|smplayer}} is in the extra repository. The smplayer-themes package provides themes for it.<br />
* Gtk+: {{Package AUR|pymp}} and {{Package Official|gnome-mplayer}} are in the AUR and community repos, respectively.<br />
* gmplayer: this gui is no longer included in the mplayer package. There is an alternative mplayer package (mplayer-x) in AUR in which the gmplayer gui is enabled.<br />
<br />
===Browser integration===<br />
<br />
If you want to let MPlayer control video viewing in your favorite web browser, install the following:<br />
<br />
====Firefox====<br />
<br />
# pacman -S gecko-mediaplayer<br />
<br />
{{Note| Depends on gnome-mplayer, which provides a complete frontend to MPlayer.}}<br />
<br />
====Konqueror====<br />
<br />
# pacman -S kmplayer<br />
<br />
{{Note| Also provides a complete frontend to MPlayer.}}<br />
<br />
==Usage==<br />
<br />
===Configuration===<br />
System-wide configuration is located in {{Filename|/etc/mplayer/mplayer.conf}}, whereas the user-local settings are stored in {{Filename|~/.mplayer/config}}. The file {{Filename|/etc/mplayer/example.conf}} is a good starting point.<br />
<br />
An example configuration: <br />
<br />
{{File|name=/etc/mplayer/example.conf|content=<br />
<br />
# default configuration that applies to every file<br />
[default]<br />
# use X11 for video output<br />
vo=xv<br />
# use also for audio output<br />
ao=alsa<br />
# ao=oss # Use OSS4<br />
# prefer using six channels audio<br />
channels = 6<br />
# scale the subtitles to the 3% of the screen size<br />
subfont-text-scale = 3<br />
# never use font config<br />
nofontconfig = 1<br />
# add black borders so the movies have the same aspect ratio of the monitor<br />
# for wide screen monitors<br />
vf-add=expand=::::1:16/9:16<br />
# for non wide screen traditional monitors<br />
#vf-add=expand=::::1:4/3:16<br />
<br />
#profile for up-mixing two channels audio to six channels<br />
# use -profile 2chto6ch to activate<br />
[2chto6ch]<br />
af-add=pan=6:1:0:.4:0:.6:2:0:1:0:.4:.6:2<br />
<br />
#profile to down-mixing six channels audio to two channels<br />
# use -profile 6chto2ch to activate<br />
[6chto2ch]<br />
af-add=pan=2:0.7:0:0:0.7:0.5:0:0:0.5:0.6:0.6:0:0<br />
<br />
# Disable screensaver.<br />
heartbeat-cmd="xscreensaver-command -deactivate &" # stop xscreensaver<br />
stop-xscreensaver="yes" # stop gnome-screensaver<br />
}}<br />
<br />
===Enabling VDPAU (modern nVidia cards only)===<br />
<br />
For a complete list of VDPAU capable hardware, see [[http://en.wikipedia.org/wiki/PureVideo#Table_of_PureVideo_.28HD.29_GPUs this table]]. Ensure the ''nvidia'' driver is installed and consider one of the following two methods to automatically enable vdpau for playback.<br />
<br />
==== 1. Using a conf file ====<br />
Append the following to either the system-wide or user-specific config files<br />
<br />
vo=vdpau,<br />
vc=ffmpeg12vdpau,ffwmv3vdpau,ffvc1vdpau,ffh264vdpau,ffodivxvdpau,<br />
<br />
{{Note|The trailing commas are important!}}<br />
{{Warning|The ffodivxvdpau is only supported by the most recent series of nVidia hardware. Consider omitting it based on your specific hardware.}}<br />
<br />
==== 2. Using a wrapper script ====<br />
<br />
The [[AUR]] contains a trivial bash script called {{Package AUR|mplayer-vdpau-auto}} that detects which vc to use and when to use vo=vdpau.<br />
<br />
===Translucent Video with radeon and Composite enabled===<br />
<br />
To get translucent video output in X you have to enable textured video in mplayer:<br />
<br />
$ mplayer -vo xv:adaptor=1 <File><br />
<br />
Or add the following line to {{Filename|~/.mplayer/config}}:<br />
<br />
vo=xv:adaptor=1<br />
<br />
You can use xvinfo to check which video modes your graphic card supports.<br />
<br />
=== Smplayer No Video Issue ===<br />
<br />
Smplayer may have trouble opening mp4 (and probably flv) videos. If it plays only audio without video here is the fix:<br />
Open your {{Codeline|~/.mplayer/config}} file and add<br />
<br />
[extension.mp4]<br />
demuxer=mov<br />
<br />
If problem persists after doing so, it is because of smplayer is keeping settings for that specific file. Deleting file settings of smplayer will fix this.<br />
<br />
$ rm -rf ~/.config/smplayer/file_settings<br />
<br />
=== (S)mplayer fails to resume playback after pause ===<br />
<br />
Smplayer might stop playing a video after pausing it if your audio output driver is set wrong. If PulseAudio is used start mplayer with the "-ao pulse" argument or edit your {{Codeline|~/.mplayer/config}} file and add<br />
<br />
ao=pulse<br />
<br />
In Smplayer you have to change your "Output-driver" under "General" - "Audio" in the options.<br />
<br />
===Transparent SMPlayer in Gnome with Composite enabled===<br />
<br />
Have you noticed the transparent screen of smplayer when you are using compiz and maybe cairo-dock? Well it’s ridiculous that when you open your videos using SMplayer you can just hear audio and no video! Here’s how you fix this: [copy paste into terminal]<br />
<br />
sudo bash -c "cat > /usr/bin/smplayer.helper" <<EOF<br />
export XLIB_SKIP_ARGB_VISUALS=1<br />
exec smplayer.real "$@"<br />
EOF<br />
sudo chmod 755 /usr/bin/smplayer.helper<br />
sudo mv /usr/bin/smplayer{,.real}<br />
sudo ln -sf smplayer.helper /usr/bin/smplayer<br />
<br />
If you don’t use sudo then just use “su” to login as root and do the above!<br />
<br />
===Watching streamed video===<br />
If you want to play a video stream (e.g *.asx link) use:<br />
<br />
$ mplayer -playlist link-to-stream.asx <br />
<br />
To play the stream, as these are playlists of streams and won't be playable by omitting the -playlist option.<br />
<br />
===Play mplayer with dvdnav support===<br />
If you want to use mplayer with dvdnav support to enable the menus of a dvd then use the following syntax:<br />
<br />
$ mplayer -nocache dvdnav://<br />
<br />
===Seek forward/backward in a downloading file===<br />
If you want to be able to seek forward and backward in a video file which is still downloading whilst watching it, add the following to your config file. <br />
<br />
idx=yes<br />
<br />
===Increase the total volume===<br />
If the maximal volume provided by the sound settings is not loud enough, you can increase the volume by mplayer itself. Activate softvol and set a maximal level which has to range between 10 and 10000.<br />
<br />
softvol=1<br />
softvol-max=600<br />
<br />
===Stream mplayer audio to jackd===<br />
<br />
Edit {{Filename|~/.mplayer/config}} and add:<br />
<br />
ao=jack<br />
<br />
===Keybindings===<br />
<br />
:''This is a list of the most basic MPlayer keys.''<br />
<br />
{|<br />
! width=50 align=left | Key<br />
! align=left | Description<br />
|-<br />
| p<br />
| Toggle pause/play.<br />
|-<br />
| Space<br />
| Toggle pause/play.<br />
|-<br />
|-<br />
| Backspace<br />
| Return to menu when using dvdnav.<br />
|-<br />
| Left<br />
| Seek backward ten seconds.<br />
|-<br />
| Right<br />
| Seek forward ten seconds.<br />
|-<br />
| Down<br />
| Seek backward one minute.<br />
|-<br />
| Up<br />
| Seek forward one minute.<br />
|-<br />
| <<br />
| Go back in the playlist.<br />
|-<br />
| ><br />
| Go forward in the playlist.<br />
|-<br />
| m<br />
| Mute the sound.<br />
|-<br />
| 0<br />
| Volume up.<br />
|-<br />
| 9<br />
| Volume down.<br />
|-<br />
| f<br />
| Toggle fullscreen mode.<br />
|-<br />
| o<br />
| Toggle OSD state.<br />
|-<br />
| j<br />
| Toggle subtitle visibility.<br />
|-<br />
| <code>I</code><br />
| Show filename.<br />
|-<br />
| 1, 2<br />
| Adjust contrast.<br />
|-<br />
| 3, 4<br />
| Adjust brightness.<br />
|-<br />
| j<br />
| Cycle through the available subtitles.<br />
|-<br />
| #<br />
| Cycle through the available audio tracks.<br />
|}<br />
<br />
=== Mplayer fails to open files with spaces ===<br />
<br />
If you try to open a file with spaces (The Movie) and mplayer fails. Saying that it could not open the file (file:///The%20Movie), where all spaces are converted to %20. <br />
<br />
Then edit {{Filename|/usr/share/applications/mplayer.desktop}} to change the following line from:<br />
<br />
Exec=mplayer %U<br />
<br />
To:<br />
<br />
Exec=mplayer "%F"<br />
<br />
If you got frontend/GUI enter GUI name in Exec=gui_name "%F".<br />
<br />
==External links==<br />
* [http://www.mplayerhq.hu/ Official MPlayer website]<br />
* [http://www.keyxl.com/aaa2fa5/302/MPlayer-keyboard-shortcuts.htm List of shortcut keys]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=I3&diff=164497I32011-10-07T17:19:28Z<p>Taylorchu: /* Comparison of i3bar and dzen2 */</p>
<hr />
<div>{{i18n|i3}}<br />
{{DISPLAYTITLE:i3}}<br />
[[Category:Tiling WMs (English)]]<br />
<br />
[http://i3.zekjur.net/ i3] is a dynamic [[Wikipedia:Tiling window manager|tiling window manager]] inspired by [[Wmii]] that is primarily targeted at developers and advanced users.<br />
<br />
== Introduction ==<br />
The developers' attempt to hack and fix [[Wmii]] led to the creation of i3. At the time Wmii didn't provide certain features, like support for [[Wikipedia:Xinerama|Xinerama]], and lacked source code comments and documentation.<br />
<br />
Clients within i3 are either allowed to float or placed into containers. Clients can be stacked or tabbed within containers. <br />
<br />
== Installation ==<br />
i3 is located in the {{codeline|[[community]]}} repository. Installing i3 can be accomplished by choosing the {{Package Official|i3}} group, which includes the packages {{Package Official|i3lock}}, {{Package Official|i3status}} and {{Package Official|i3-wm}}.<br />
# pacman -S i3<br />
<br />
Alternatively, you can install the window manager exclusively:<br />
# pacman -S i3-wm<br />
<br />
Additionally, {{Package AUR|i3-git}} is available in [[AUR]].<br />
<br />
==Running i3==<br />
<br />
Edit your {{Filename|~/.xinitrc}} and add:<br />
exec i3<br />
If you want i3 to log its output (useful for debugging), add this line to {{Filename|~/.xinitrc}}:<br />
exec i3 -V >>~/.i3/i3log >&1<br />
If you use the Nvidia binary driver you need to add the --force-xinerama flag to {{Filename|~/.xinitrc}}. A detailed explanation can be found at [http://i3wm.org/docs/multi-monitor.html i3wm.org].<br />
exec i3 --force-xinerama<br />
<br />
== Basic Keybindings and Window Management ==<br />
The default keybindings mostly depend on Mod1 (usually mapped to Alt) as the basic modifier key sometimes combined with Ctrl or Shift.<br />
Other binds use Mod3 as the base modifier (often the Windows-key). To identify the different Mod# keys on your system, use the<br />
command {{Codeline|xmodmap}} without arguments.<br />
<br />
The key combinations are configured in the file {{Filename|~/.i3/config}} (or, if it does not exist, {{Filename|/etc/i3/config}}).<br />
<br />
The default key combinations rely on key codes and not on the actual letters of your keyboard layout! You can replace the {{Codeline|bind}} directives in the config with {{Codeline|bindsym}} directives if you do not like this. For more info on configuration see the next section.<br />
<br />
Some of the most important keybindings include the following:<br />
* Run a program: Mod1+v<br />
* Create a new terminal: Mod1+Enter<br />
* Switch between different windows: Mod1+ any of "jkl;" or cursor keys (somewhat Vim-like keybindings)<br />
* Move a window: Mod1+Shift+ any of "jkl;" or cursor keys<br />
* Switch to a different workspace: Mod1+ any number<br />
* Move window to a different workspace: Mod1+Shift+ any number<br />
<br />
Note that i3 uses containers for window management. So in contrast to [[Wmii]] you can also tile windows horizontally. To do this, simply move a window up or down (with Mod1+Shift+DirectionKey) beyond the edge of the screen. A new row will appear. You can then use Mod4+Ctrl+DirectionKey to enlarge the window into the chosen direction. DirectionKey can be the arrow keys as well as "jkl;".<br />
<br />
There are 3 container modes:<br />
* Normal (columns): Mod1+e<br />
* Tabbed: Mod1+w<br />
* Stacked: Mod1+s<br />
<br />
Additionally, you can put a window into fullscreen mode with Mod1+f.<br />
<br />
[http://i3wm.org/docs/refcard.pdf i3 keybinding cheatsheet (pdf)]<br />
<br />
== Configuration ==<br />
<br />
i3 is configured using a simple text file. It first looks for {{Filename|~/.i3/config}} and if it doesn't exist, reads the default config at {{Filename|/etc/i3/config}}. So to start customizing, copy the config file to your home directory:<br />
cp /etc/i3/config ~/.i3/config<br />
The config allows you to change such things as:<br />
*Border colors<br />
*Font<br />
*Keybindings<br />
*Workspace names<br />
*Default container layout<br />
*Assignment of apps to specific workspaces<br />
<br />
The i3 [http://i3.zekjur.net/docs/userguide.html User's Guide] gives a nice overview of the config settings.<br />
<br />
For users seeking to convert their configuration to v4, i3-wm comes with a perl script for conversion:<br />
<pre>mv config config.old #save the old file<br />
i3-migrate-config-to-v4 config.old > config<br />
</pre><br />
Have a look at the changes!<br />
<br />
== Status Bar ==<br />
As of version 4 the internal statusbar of i3 does not exist anymore. Instead, [http://git.merovius.de/i3bar/ i3bar] is the new default.<br />
It can be used to view information produced by conky or i3status:<br />
exec i3bar -c 'conky -c ~/.i3/conki3'<br />
exec i3bar -c 'i3status'<br />
<br />
[http://wiki.archlinux.org/index.php/Dzen dzen2] can be placed in the information bar at the bottom of the screen. Information for dzen2 can be generated using [http://www.archlinux.org/packages/community/i686/i3status/ i3status] or [http://wiki.archlinux.org/index.php/Conky conky].<br />
i3status | dzen2 &<br />
Or<br />
conky | dzen2 &<br />
The svn development version of [http://aur.archlinux.org/packages.php?ID=19926 dzen2] in the [[AUR]] offers a -dock option, which puts dzen2 at the bottom of the screen and tells i3 not to manage it.<br />
<br />
In the AUR you can also find [http://aur.archlinux.org/packages.php?ID=36389 i3-wsbar], which is able to get the list of workspaces from the socket that i3 offers for IPC. Thus you can pipe the conky output to i3-wsbar and tell it to use dzen2.<br />
E.g., put the following in {{Filename|~/.i3/config}}:<br />
exec conky | i3-wsbar -c "dzen2 -x %x -dock -fn -*-profont-*-*-*-*-11-*-*-*-*-*-*-* -ta l"<br />
Please note that in your conky configuration file you can use the color codes for dzen2, so that you can get a nice, colored statusbar (see this sample [http://archlinux.lando.imap.cc/i3/.conkyrc conkyrc] and the corresponding [http://archlinux.lando.imap.cc/i3/i3-wsbar.png screenshot]).<br />
<br />
=== Comparison of i3bar and dzen2 ===<br />
This is a comparison of i3bar and dzen2. It only takes into account how well the two programs can handle the input from conky or i3status (formatting, colors, alignment, special fonts etc).<br />
{| border="1" cellpadding="5" align="center"<br />
! Program !! Color Codes !! Formatting !! Special Fonts !! Dock !! Trayer<br />
|-<br />
| i3bar || No || No, right aligned || No (UTF8 only)|| Yes || Yes (git)<br />
|-<br />
| dzen2 || Yes || No, left aligned || Yes || Yes (the svn version) || No<br />
|-<br />
|}<br />
<br />
Though development of i3bar is very active and support for custom formatting and fonts has been announced, dzen2-svn has an edge over i3bar (as of 7th of August). From the i3bar man page:<br />
:"i3bar does not yet support formatting in the displayed statusline. However it does support setting colors for the<br />
: bar, the workspace-buttons and the statusline."<br />
<br />
== Other tools ==<br />
i3 currently uses [[Dmenu]] as a application launcher, which is bound by default to {{Keypress|Mod1|background=#FF0}}+{{Keypress|d}}. <br />
<br />
[http://www.archlinux.org/packages/community/i686/i3lock/ i3lock] is a screen locker inspired by {{Package Official|slock}}.<br />
<br />
== Additional sources ==<br />
* [http://i3wm.org/docs/ Official i3 Documentation]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=I3&diff=164495I32011-10-07T17:18:17Z<p>Taylorchu: /* Basic Keybindings and Window Management */</p>
<hr />
<div>{{i18n|i3}}<br />
{{DISPLAYTITLE:i3}}<br />
[[Category:Tiling WMs (English)]]<br />
<br />
[http://i3.zekjur.net/ i3] is a dynamic [[Wikipedia:Tiling window manager|tiling window manager]] inspired by [[Wmii]] that is primarily targeted at developers and advanced users.<br />
<br />
== Introduction ==<br />
The developers' attempt to hack and fix [[Wmii]] led to the creation of i3. At the time Wmii didn't provide certain features, like support for [[Wikipedia:Xinerama|Xinerama]], and lacked source code comments and documentation.<br />
<br />
Clients within i3 are either allowed to float or placed into containers. Clients can be stacked or tabbed within containers. <br />
<br />
== Installation ==<br />
i3 is located in the {{codeline|[[community]]}} repository. Installing i3 can be accomplished by choosing the {{Package Official|i3}} group, which includes the packages {{Package Official|i3lock}}, {{Package Official|i3status}} and {{Package Official|i3-wm}}.<br />
# pacman -S i3<br />
<br />
Alternatively, you can install the window manager exclusively:<br />
# pacman -S i3-wm<br />
<br />
Additionally, {{Package AUR|i3-git}} is available in [[AUR]].<br />
<br />
==Running i3==<br />
<br />
Edit your {{Filename|~/.xinitrc}} and add:<br />
exec i3<br />
If you want i3 to log its output (useful for debugging), add this line to {{Filename|~/.xinitrc}}:<br />
exec i3 -V >>~/.i3/i3log >&1<br />
If you use the Nvidia binary driver you need to add the --force-xinerama flag to {{Filename|~/.xinitrc}}. A detailed explanation can be found at [http://i3wm.org/docs/multi-monitor.html i3wm.org].<br />
exec i3 --force-xinerama<br />
<br />
== Basic Keybindings and Window Management ==<br />
The default keybindings mostly depend on Mod1 (usually mapped to Alt) as the basic modifier key sometimes combined with Ctrl or Shift.<br />
Other binds use Mod3 as the base modifier (often the Windows-key). To identify the different Mod# keys on your system, use the<br />
command {{Codeline|xmodmap}} without arguments.<br />
<br />
The key combinations are configured in the file {{Filename|~/.i3/config}} (or, if it does not exist, {{Filename|/etc/i3/config}}).<br />
<br />
The default key combinations rely on key codes and not on the actual letters of your keyboard layout! You can replace the {{Codeline|bind}} directives in the config with {{Codeline|bindsym}} directives if you do not like this. For more info on configuration see the next section.<br />
<br />
Some of the most important keybindings include the following:<br />
* Run a program: Mod1+v<br />
* Create a new terminal: Mod1+Enter<br />
* Switch between different windows: Mod1+ any of "jkl;" or cursor keys (somewhat Vim-like keybindings)<br />
* Move a window: Mod1+Shift+ any of "jkl;" or cursor keys<br />
* Switch to a different workspace: Mod1+ any number<br />
* Move window to a different workspace: Mod1+Shift+ any number<br />
<br />
Note that i3 uses containers for window management. So in contrast to [[Wmii]] you can also tile windows horizontally. To do this, simply move a window up or down (with Mod1+Shift+DirectionKey) beyond the edge of the screen. A new row will appear. You can then use Mod4+Ctrl+DirectionKey to enlarge the window into the chosen direction. DirectionKey can be the arrow keys as well as "jkl;".<br />
<br />
There are 3 container modes:<br />
* Normal (columns): Mod1+e<br />
* Tabbed: Mod1+w<br />
* Stacked: Mod1+s<br />
<br />
Additionally, you can put a window into fullscreen mode with Mod1+f.<br />
<br />
[http://i3wm.org/docs/refcard.pdf i3 keybinding cheatsheet (pdf)]<br />
<br />
== Configuration ==<br />
<br />
i3 is configured using a simple text file. It first looks for {{Filename|~/.i3/config}} and if it doesn't exist, reads the default config at {{Filename|/etc/i3/config}}. So to start customizing, copy the config file to your home directory:<br />
cp /etc/i3/config ~/.i3/config<br />
The config allows you to change such things as:<br />
*Border colors<br />
*Font<br />
*Keybindings<br />
*Workspace names<br />
*Default container layout<br />
*Assignment of apps to specific workspaces<br />
<br />
The i3 [http://i3.zekjur.net/docs/userguide.html User's Guide] gives a nice overview of the config settings.<br />
<br />
For users seeking to convert their configuration to v4, i3-wm comes with a perl script for conversion:<br />
<pre>mv config config.old #save the old file<br />
i3-migrate-config-to-v4 config.old > config<br />
</pre><br />
Have a look at the changes!<br />
<br />
== Status Bar ==<br />
As of version 4 the internal statusbar of i3 does not exist anymore. Instead, [http://git.merovius.de/i3bar/ i3bar] is the new default.<br />
It can be used to view information produced by conky or i3status:<br />
exec i3bar -c 'conky -c ~/.i3/conki3'<br />
exec i3bar -c 'i3status'<br />
<br />
[http://wiki.archlinux.org/index.php/Dzen dzen2] can be placed in the information bar at the bottom of the screen. Information for dzen2 can be generated using [http://www.archlinux.org/packages/community/i686/i3status/ i3status] or [http://wiki.archlinux.org/index.php/Conky conky].<br />
i3status | dzen2 &<br />
Or<br />
conky | dzen2 &<br />
The svn development version of [http://aur.archlinux.org/packages.php?ID=19926 dzen2] in the [[AUR]] offers a -dock option, which puts dzen2 at the bottom of the screen and tells i3 not to manage it.<br />
<br />
In the AUR you can also find [http://aur.archlinux.org/packages.php?ID=36389 i3-wsbar], which is able to get the list of workspaces from the socket that i3 offers for IPC. Thus you can pipe the conky output to i3-wsbar and tell it to use dzen2.<br />
E.g., put the following in {{Filename|~/.i3/config}}:<br />
exec conky | i3-wsbar -c "dzen2 -x %x -dock -fn -*-profont-*-*-*-*-11-*-*-*-*-*-*-* -ta l"<br />
Please note that in your conky configuration file you can use the color codes for dzen2, so that you can get a nice, colored statusbar (see this sample [http://archlinux.lando.imap.cc/i3/.conkyrc conkyrc] and the corresponding [http://archlinux.lando.imap.cc/i3/i3-wsbar.png screenshot]).<br />
<br />
=== Comparison of i3bar and dzen2 ===<br />
This is a comparison of i3bar and dzen2. It only takes into account how well the two programs can handle the input from conky or i3status (formatting, colors, alignment, special fonts etc).<br />
{| border="1" cellpadding="5" align="center"<br />
! Program !! Color Codes !! Formatting !! Special Fonts !! Dock<br />
|-<br />
| i3bar || No || No, right aligned || No (UTF8 only)|| Yes<br />
|-<br />
| dzen2 || Yes || No, left aligned || Yes || Yes (the svn version)<br />
|-<br />
|}<br />
<br />
Though development of i3bar is very active and support for custom formatting and fonts has been announced, dzen2-svn has an edge over i3bar (as of 7th of August). From the i3bar man page:<br />
:"i3bar does not yet support formatting in the displayed statusline. However it does support setting colors for the<br />
: bar, the workspace-buttons and the statusline."<br />
<br />
== Other tools ==<br />
i3 currently uses [[Dmenu]] as a application launcher, which is bound by default to {{Keypress|Mod1|background=#FF0}}+{{Keypress|d}}. <br />
<br />
[http://www.archlinux.org/packages/community/i686/i3lock/ i3lock] is a screen locker inspired by {{Package Official|slock}}.<br />
<br />
== Additional sources ==<br />
* [http://i3wm.org/docs/ Official i3 Documentation]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=I3&diff=164493I32011-10-07T17:13:12Z<p>Taylorchu: /* Basic Keybindings and Window Management */</p>
<hr />
<div>{{i18n|i3}}<br />
{{DISPLAYTITLE:i3}}<br />
[[Category:Tiling WMs (English)]]<br />
<br />
[http://i3.zekjur.net/ i3] is a dynamic [[Wikipedia:Tiling window manager|tiling window manager]] inspired by [[Wmii]] that is primarily targeted at developers and advanced users.<br />
<br />
== Introduction ==<br />
The developers' attempt to hack and fix [[Wmii]] led to the creation of i3. At the time Wmii didn't provide certain features, like support for [[Wikipedia:Xinerama|Xinerama]], and lacked source code comments and documentation.<br />
<br />
Clients within i3 are either allowed to float or placed into containers. Clients can be stacked or tabbed within containers. <br />
<br />
== Installation ==<br />
i3 is located in the {{codeline|[[community]]}} repository. Installing i3 can be accomplished by choosing the {{Package Official|i3}} group, which includes the packages {{Package Official|i3lock}}, {{Package Official|i3status}} and {{Package Official|i3-wm}}.<br />
# pacman -S i3<br />
<br />
Alternatively, you can install the window manager exclusively:<br />
# pacman -S i3-wm<br />
<br />
Additionally, {{Package AUR|i3-git}} is available in [[AUR]].<br />
<br />
==Running i3==<br />
<br />
Edit your {{Filename|~/.xinitrc}} and add:<br />
exec i3<br />
If you want i3 to log its output (useful for debugging), add this line to {{Filename|~/.xinitrc}}:<br />
exec i3 -V >>~/.i3/i3log >&1<br />
If you use the Nvidia binary driver you need to add the --force-xinerama flag to {{Filename|~/.xinitrc}}. A detailed explanation can be found at [http://i3wm.org/docs/multi-monitor.html i3wm.org].<br />
exec i3 --force-xinerama<br />
<br />
== Basic Keybindings and Window Management ==<br />
The default keybindings mostly depend on Mod1 (usually mapped to Alt) as the basic modifier key sometimes combined with Ctrl or Shift.<br />
Other binds use Mod3 as the base modifier (often the Windows-key). To identify the different Mod# keys on your system, use the<br />
command {{Codeline|xmodmap}} without arguments.<br />
<br />
The key combinations are configured in the file {{Filename|~/.i3/config}} (or, if it does not exist, {{Filename|/etc/i3/config}}).<br />
<br />
The default key combinations rely on key codes and not on the actual letters of your keyboard layout! You can replace the {{Codeline|bind}} directives in the config with {{Codeline|bindsym}} directives if you do not like this. For more info on configuration see the next section.<br />
<br />
Some of the most important keybindings include the following:<br />
* Run a program: Mod1+v<br />
* Create a new terminal: Mod1+Enter<br />
* Switch between different windows: Mod1+ any of "jkl;" or cursor keys (somewhat Vim-like keybindings)<br />
* Move a window: Mod1+Shift+ any of "jkl;" or cursor keys<br />
* Switch to a different workspace: Mod1+ any number<br />
* Move window to a different workspace: Mod1+Shift+ any number<br />
<br />
Note that i3 uses containers for window management. So in contrast to [[Wmii]] you can also tile windows horizontally. To do this, simply move a window up or down (with Mod1+Shift+DirectionKey) beyond the edge of the screen. A new row will appear. You can then use Mod4+Ctrl+DirectionKey to enlarge the window into the chosen direction. DirectionKey can be the arrow keys as well as "jkl;".<br />
<br />
There are 3 container modes:<br />
* Normal: Mod1+e<br />
* Maximized: Mod1+w<br />
* Stacked: Mod1+s<br />
<br />
Additionally, you can put a window into fullscreen mode with Mod1+f.<br />
<br />
[http://i3wm.org/docs/refcard.pdf i3 keybinding cheatsheet (pdf)]<br />
<br />
== Configuration ==<br />
<br />
i3 is configured using a simple text file. It first looks for {{Filename|~/.i3/config}} and if it doesn't exist, reads the default config at {{Filename|/etc/i3/config}}. So to start customizing, copy the config file to your home directory:<br />
cp /etc/i3/config ~/.i3/config<br />
The config allows you to change such things as:<br />
*Border colors<br />
*Font<br />
*Keybindings<br />
*Workspace names<br />
*Default container layout<br />
*Assignment of apps to specific workspaces<br />
<br />
The i3 [http://i3.zekjur.net/docs/userguide.html User's Guide] gives a nice overview of the config settings.<br />
<br />
For users seeking to convert their configuration to v4, i3-wm comes with a perl script for conversion:<br />
<pre>mv config config.old #save the old file<br />
i3-migrate-config-to-v4 config.old > config<br />
</pre><br />
Have a look at the changes!<br />
<br />
== Status Bar ==<br />
As of version 4 the internal statusbar of i3 does not exist anymore. Instead, [http://git.merovius.de/i3bar/ i3bar] is the new default.<br />
It can be used to view information produced by conky or i3status:<br />
exec i3bar -c 'conky -c ~/.i3/conki3'<br />
exec i3bar -c 'i3status'<br />
<br />
[http://wiki.archlinux.org/index.php/Dzen dzen2] can be placed in the information bar at the bottom of the screen. Information for dzen2 can be generated using [http://www.archlinux.org/packages/community/i686/i3status/ i3status] or [http://wiki.archlinux.org/index.php/Conky conky].<br />
i3status | dzen2 &<br />
Or<br />
conky | dzen2 &<br />
The svn development version of [http://aur.archlinux.org/packages.php?ID=19926 dzen2] in the [[AUR]] offers a -dock option, which puts dzen2 at the bottom of the screen and tells i3 not to manage it.<br />
<br />
In the AUR you can also find [http://aur.archlinux.org/packages.php?ID=36389 i3-wsbar], which is able to get the list of workspaces from the socket that i3 offers for IPC. Thus you can pipe the conky output to i3-wsbar and tell it to use dzen2.<br />
E.g., put the following in {{Filename|~/.i3/config}}:<br />
exec conky | i3-wsbar -c "dzen2 -x %x -dock -fn -*-profont-*-*-*-*-11-*-*-*-*-*-*-* -ta l"<br />
Please note that in your conky configuration file you can use the color codes for dzen2, so that you can get a nice, colored statusbar (see this sample [http://archlinux.lando.imap.cc/i3/.conkyrc conkyrc] and the corresponding [http://archlinux.lando.imap.cc/i3/i3-wsbar.png screenshot]).<br />
<br />
=== Comparison of i3bar and dzen2 ===<br />
This is a comparison of i3bar and dzen2. It only takes into account how well the two programs can handle the input from conky or i3status (formatting, colors, alignment, special fonts etc).<br />
{| border="1" cellpadding="5" align="center"<br />
! Program !! Color Codes !! Formatting !! Special Fonts !! Dock<br />
|-<br />
| i3bar || No || No, right aligned || No (UTF8 only)|| Yes<br />
|-<br />
| dzen2 || Yes || No, left aligned || Yes || Yes (the svn version)<br />
|-<br />
|}<br />
<br />
Though development of i3bar is very active and support for custom formatting and fonts has been announced, dzen2-svn has an edge over i3bar (as of 7th of August). From the i3bar man page:<br />
:"i3bar does not yet support formatting in the displayed statusline. However it does support setting colors for the<br />
: bar, the workspace-buttons and the statusline."<br />
<br />
== Other tools ==<br />
i3 currently uses [[Dmenu]] as a application launcher, which is bound by default to {{Keypress|Mod1|background=#FF0}}+{{Keypress|d}}. <br />
<br />
[http://www.archlinux.org/packages/community/i686/i3lock/ i3lock] is a screen locker inspired by {{Package Official|slock}}.<br />
<br />
== Additional sources ==<br />
* [http://i3wm.org/docs/ Official i3 Documentation]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=I3&diff=164492I32011-10-07T17:12:47Z<p>Taylorchu: /* Basic Keybindings and Window Management */</p>
<hr />
<div>{{i18n|i3}}<br />
{{DISPLAYTITLE:i3}}<br />
[[Category:Tiling WMs (English)]]<br />
<br />
[http://i3.zekjur.net/ i3] is a dynamic [[Wikipedia:Tiling window manager|tiling window manager]] inspired by [[Wmii]] that is primarily targeted at developers and advanced users.<br />
<br />
== Introduction ==<br />
The developers' attempt to hack and fix [[Wmii]] led to the creation of i3. At the time Wmii didn't provide certain features, like support for [[Wikipedia:Xinerama|Xinerama]], and lacked source code comments and documentation.<br />
<br />
Clients within i3 are either allowed to float or placed into containers. Clients can be stacked or tabbed within containers. <br />
<br />
== Installation ==<br />
i3 is located in the {{codeline|[[community]]}} repository. Installing i3 can be accomplished by choosing the {{Package Official|i3}} group, which includes the packages {{Package Official|i3lock}}, {{Package Official|i3status}} and {{Package Official|i3-wm}}.<br />
# pacman -S i3<br />
<br />
Alternatively, you can install the window manager exclusively:<br />
# pacman -S i3-wm<br />
<br />
Additionally, {{Package AUR|i3-git}} is available in [[AUR]].<br />
<br />
==Running i3==<br />
<br />
Edit your {{Filename|~/.xinitrc}} and add:<br />
exec i3<br />
If you want i3 to log its output (useful for debugging), add this line to {{Filename|~/.xinitrc}}:<br />
exec i3 -V >>~/.i3/i3log >&1<br />
If you use the Nvidia binary driver you need to add the --force-xinerama flag to {{Filename|~/.xinitrc}}. A detailed explanation can be found at [http://i3wm.org/docs/multi-monitor.html i3wm.org].<br />
exec i3 --force-xinerama<br />
<br />
== Basic Keybindings and Window Management ==<br />
The default keybindings mostly depend on Mod1 (usually mapped to Alt) as the basic modifier key sometimes combined with Ctrl or Shift.<br />
Other binds use Mod3 as the base modifier (often the Windows-key). To identify the different Mod# keys on your system, use the<br />
command {{Codeline|xmodmap}} without arguments.<br />
<br />
The key combinations are configured in the file {{Filename|~/.i3/config}} (or, if it does not exist, {{Filename|/etc/i3/config}}).<br />
<br />
The default key combinations rely on key codes and not on the actual letters of your keyboard layout! You can replace the {{Codeline|bind}} directives in the config with {{Codeline|bindsym}} directives if you do not like this. For more info on configuration see the next section.<br />
<br />
Some of the most important keybindings include the following:<br />
* Run a program: Mod1+v<br />
* Create a new terminal: Mod1+Enter<br />
* Switch between different windows: Mod1+ any of "jkl;" or cursor keys (somewhat Vim-like keybindings)<br />
* Move a window: Mod1+Shift+ any of "jkl;" or cursor keys<br />
* Switch to a different workspace: Mod1+ any number<br />
* Move window to a different workspace: Mod1+Shift+ any number<br />
<br />
Note that i3 uses containers for window management. So in contrast to [[Wmii]] you can also tile windows horizontally. To do this, simply move a window up or down (with Mod1+Shift+DirectionKey) beyond the edge of the screen. A new row will appear. You can then use Mod4+Ctrl+DirectionKey to enlarge the window into the chosen direction. DirectionKey can be the arrow keys as well as "jkl;".<br />
<br />
There are 3 container modes:<br />
* Normal: Mod1+e<br />
* Maximized: Mod1+w<br />
* Stacked: Mod1+s<br />
<br />
Additionally, you can put a window into fullscreen mode with Mod1+f.<br />
<br />
[http://i3wm.org/docs/refcard.pdf i3 keybinding cheatsheet]<br />
<br />
== Configuration ==<br />
<br />
i3 is configured using a simple text file. It first looks for {{Filename|~/.i3/config}} and if it doesn't exist, reads the default config at {{Filename|/etc/i3/config}}. So to start customizing, copy the config file to your home directory:<br />
cp /etc/i3/config ~/.i3/config<br />
The config allows you to change such things as:<br />
*Border colors<br />
*Font<br />
*Keybindings<br />
*Workspace names<br />
*Default container layout<br />
*Assignment of apps to specific workspaces<br />
<br />
The i3 [http://i3.zekjur.net/docs/userguide.html User's Guide] gives a nice overview of the config settings.<br />
<br />
For users seeking to convert their configuration to v4, i3-wm comes with a perl script for conversion:<br />
<pre>mv config config.old #save the old file<br />
i3-migrate-config-to-v4 config.old > config<br />
</pre><br />
Have a look at the changes!<br />
<br />
== Status Bar ==<br />
As of version 4 the internal statusbar of i3 does not exist anymore. Instead, [http://git.merovius.de/i3bar/ i3bar] is the new default.<br />
It can be used to view information produced by conky or i3status:<br />
exec i3bar -c 'conky -c ~/.i3/conki3'<br />
exec i3bar -c 'i3status'<br />
<br />
[http://wiki.archlinux.org/index.php/Dzen dzen2] can be placed in the information bar at the bottom of the screen. Information for dzen2 can be generated using [http://www.archlinux.org/packages/community/i686/i3status/ i3status] or [http://wiki.archlinux.org/index.php/Conky conky].<br />
i3status | dzen2 &<br />
Or<br />
conky | dzen2 &<br />
The svn development version of [http://aur.archlinux.org/packages.php?ID=19926 dzen2] in the [[AUR]] offers a -dock option, which puts dzen2 at the bottom of the screen and tells i3 not to manage it.<br />
<br />
In the AUR you can also find [http://aur.archlinux.org/packages.php?ID=36389 i3-wsbar], which is able to get the list of workspaces from the socket that i3 offers for IPC. Thus you can pipe the conky output to i3-wsbar and tell it to use dzen2.<br />
E.g., put the following in {{Filename|~/.i3/config}}:<br />
exec conky | i3-wsbar -c "dzen2 -x %x -dock -fn -*-profont-*-*-*-*-11-*-*-*-*-*-*-* -ta l"<br />
Please note that in your conky configuration file you can use the color codes for dzen2, so that you can get a nice, colored statusbar (see this sample [http://archlinux.lando.imap.cc/i3/.conkyrc conkyrc] and the corresponding [http://archlinux.lando.imap.cc/i3/i3-wsbar.png screenshot]).<br />
<br />
=== Comparison of i3bar and dzen2 ===<br />
This is a comparison of i3bar and dzen2. It only takes into account how well the two programs can handle the input from conky or i3status (formatting, colors, alignment, special fonts etc).<br />
{| border="1" cellpadding="5" align="center"<br />
! Program !! Color Codes !! Formatting !! Special Fonts !! Dock<br />
|-<br />
| i3bar || No || No, right aligned || No (UTF8 only)|| Yes<br />
|-<br />
| dzen2 || Yes || No, left aligned || Yes || Yes (the svn version)<br />
|-<br />
|}<br />
<br />
Though development of i3bar is very active and support for custom formatting and fonts has been announced, dzen2-svn has an edge over i3bar (as of 7th of August). From the i3bar man page:<br />
:"i3bar does not yet support formatting in the displayed statusline. However it does support setting colors for the<br />
: bar, the workspace-buttons and the statusline."<br />
<br />
== Other tools ==<br />
i3 currently uses [[Dmenu]] as a application launcher, which is bound by default to {{Keypress|Mod1|background=#FF0}}+{{Keypress|d}}. <br />
<br />
[http://www.archlinux.org/packages/community/i686/i3lock/ i3lock] is a screen locker inspired by {{Package Official|slock}}.<br />
<br />
== Additional sources ==<br />
* [http://i3wm.org/docs/ Official i3 Documentation]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=I3&diff=164491I32011-10-07T17:12:14Z<p>Taylorchu: /* Basic Keybindings and Window Management */</p>
<hr />
<div>{{i18n|i3}}<br />
{{DISPLAYTITLE:i3}}<br />
[[Category:Tiling WMs (English)]]<br />
<br />
[http://i3.zekjur.net/ i3] is a dynamic [[Wikipedia:Tiling window manager|tiling window manager]] inspired by [[Wmii]] that is primarily targeted at developers and advanced users.<br />
<br />
== Introduction ==<br />
The developers' attempt to hack and fix [[Wmii]] led to the creation of i3. At the time Wmii didn't provide certain features, like support for [[Wikipedia:Xinerama|Xinerama]], and lacked source code comments and documentation.<br />
<br />
Clients within i3 are either allowed to float or placed into containers. Clients can be stacked or tabbed within containers. <br />
<br />
== Installation ==<br />
i3 is located in the {{codeline|[[community]]}} repository. Installing i3 can be accomplished by choosing the {{Package Official|i3}} group, which includes the packages {{Package Official|i3lock}}, {{Package Official|i3status}} and {{Package Official|i3-wm}}.<br />
# pacman -S i3<br />
<br />
Alternatively, you can install the window manager exclusively:<br />
# pacman -S i3-wm<br />
<br />
Additionally, {{Package AUR|i3-git}} is available in [[AUR]].<br />
<br />
==Running i3==<br />
<br />
Edit your {{Filename|~/.xinitrc}} and add:<br />
exec i3<br />
If you want i3 to log its output (useful for debugging), add this line to {{Filename|~/.xinitrc}}:<br />
exec i3 -V >>~/.i3/i3log >&1<br />
If you use the Nvidia binary driver you need to add the --force-xinerama flag to {{Filename|~/.xinitrc}}. A detailed explanation can be found at [http://i3wm.org/docs/multi-monitor.html i3wm.org].<br />
exec i3 --force-xinerama<br />
<br />
== Basic Keybindings and Window Management ==<br />
The default keybindings mostly depend on Mod1 (usually mapped to Alt) as the basic modifier key sometimes combined with Ctrl or Shift.<br />
Other binds use Mod3 as the base modifier (often the Windows-key). To identify the different Mod# keys on your system, use the<br />
command {{Codeline|xmodmap}} without arguments.<br />
<br />
The key combinations are configured in the file {{Filename|~/.i3/config}} (or, if it does not exist, {{Filename|/etc/i3/config}}).<br />
<br />
The default key combinations rely on key codes and not on the actual letters of your keyboard layout! You can replace the {{Codeline|bind}} directives in the config with {{Codeline|bindsym}} directives if you do not like this. For more info on configuration see the next section.<br />
<br />
Some of the most important keybindings include the following:<br />
* Run a program: Mod1+v<br />
* Create a new terminal: Mod1+Enter<br />
* Switch between different windows: Mod1+ any of "jkl;" or cursor keys (somewhat Vim-like keybindings)<br />
* Move a window: Mod1+Shift+ any of "jkl;" or cursor keys<br />
* Switch to a different workspace: Mod1+ any number<br />
* Move window to a different workspace: Mod1+Shift+ any number<br />
<br />
Note that i3 uses containers for window management. So in contrast to [[Wmii]] you can also tile windows horizontally. To do this, simply move a window up or down (with Mod1+Shift+DirectionKey) beyond the edge of the screen. A new row will appear. You can then use Mod4+Ctrl+DirectionKey to enlarge the window into the chosen direction. DirectionKey can be the arrow keys as well as "jkl;".<br />
<br />
There are 3 container modes:<br />
* Normal: Mod1+e<br />
* Maximized: Mod1+w<br />
* Stacked: Mod1+s<br />
<br />
Additionally, you can put a window into fullscreen mode with Mod1+f.<br />
<br />
[http://i3wm.org/docs/refcard.pdf| i3 keybinding cheatsheet]<br />
<br />
== Configuration ==<br />
<br />
i3 is configured using a simple text file. It first looks for {{Filename|~/.i3/config}} and if it doesn't exist, reads the default config at {{Filename|/etc/i3/config}}. So to start customizing, copy the config file to your home directory:<br />
cp /etc/i3/config ~/.i3/config<br />
The config allows you to change such things as:<br />
*Border colors<br />
*Font<br />
*Keybindings<br />
*Workspace names<br />
*Default container layout<br />
*Assignment of apps to specific workspaces<br />
<br />
The i3 [http://i3.zekjur.net/docs/userguide.html User's Guide] gives a nice overview of the config settings.<br />
<br />
For users seeking to convert their configuration to v4, i3-wm comes with a perl script for conversion:<br />
<pre>mv config config.old #save the old file<br />
i3-migrate-config-to-v4 config.old > config<br />
</pre><br />
Have a look at the changes!<br />
<br />
== Status Bar ==<br />
As of version 4 the internal statusbar of i3 does not exist anymore. Instead, [http://git.merovius.de/i3bar/ i3bar] is the new default.<br />
It can be used to view information produced by conky or i3status:<br />
exec i3bar -c 'conky -c ~/.i3/conki3'<br />
exec i3bar -c 'i3status'<br />
<br />
[http://wiki.archlinux.org/index.php/Dzen dzen2] can be placed in the information bar at the bottom of the screen. Information for dzen2 can be generated using [http://www.archlinux.org/packages/community/i686/i3status/ i3status] or [http://wiki.archlinux.org/index.php/Conky conky].<br />
i3status | dzen2 &<br />
Or<br />
conky | dzen2 &<br />
The svn development version of [http://aur.archlinux.org/packages.php?ID=19926 dzen2] in the [[AUR]] offers a -dock option, which puts dzen2 at the bottom of the screen and tells i3 not to manage it.<br />
<br />
In the AUR you can also find [http://aur.archlinux.org/packages.php?ID=36389 i3-wsbar], which is able to get the list of workspaces from the socket that i3 offers for IPC. Thus you can pipe the conky output to i3-wsbar and tell it to use dzen2.<br />
E.g., put the following in {{Filename|~/.i3/config}}:<br />
exec conky | i3-wsbar -c "dzen2 -x %x -dock -fn -*-profont-*-*-*-*-11-*-*-*-*-*-*-* -ta l"<br />
Please note that in your conky configuration file you can use the color codes for dzen2, so that you can get a nice, colored statusbar (see this sample [http://archlinux.lando.imap.cc/i3/.conkyrc conkyrc] and the corresponding [http://archlinux.lando.imap.cc/i3/i3-wsbar.png screenshot]).<br />
<br />
=== Comparison of i3bar and dzen2 ===<br />
This is a comparison of i3bar and dzen2. It only takes into account how well the two programs can handle the input from conky or i3status (formatting, colors, alignment, special fonts etc).<br />
{| border="1" cellpadding="5" align="center"<br />
! Program !! Color Codes !! Formatting !! Special Fonts !! Dock<br />
|-<br />
| i3bar || No || No, right aligned || No (UTF8 only)|| Yes<br />
|-<br />
| dzen2 || Yes || No, left aligned || Yes || Yes (the svn version)<br />
|-<br />
|}<br />
<br />
Though development of i3bar is very active and support for custom formatting and fonts has been announced, dzen2-svn has an edge over i3bar (as of 7th of August). From the i3bar man page:<br />
:"i3bar does not yet support formatting in the displayed statusline. However it does support setting colors for the<br />
: bar, the workspace-buttons and the statusline."<br />
<br />
== Other tools ==<br />
i3 currently uses [[Dmenu]] as a application launcher, which is bound by default to {{Keypress|Mod1|background=#FF0}}+{{Keypress|d}}. <br />
<br />
[http://www.archlinux.org/packages/community/i686/i3lock/ i3lock] is a screen locker inspired by {{Package Official|slock}}.<br />
<br />
== Additional sources ==<br />
* [http://i3wm.org/docs/ Official i3 Documentation]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=I3&diff=164489I32011-10-07T17:12:01Z<p>Taylorchu: /* Basic Keybindings and Window Management */</p>
<hr />
<div>{{i18n|i3}}<br />
{{DISPLAYTITLE:i3}}<br />
[[Category:Tiling WMs (English)]]<br />
<br />
[http://i3.zekjur.net/ i3] is a dynamic [[Wikipedia:Tiling window manager|tiling window manager]] inspired by [[Wmii]] that is primarily targeted at developers and advanced users.<br />
<br />
== Introduction ==<br />
The developers' attempt to hack and fix [[Wmii]] led to the creation of i3. At the time Wmii didn't provide certain features, like support for [[Wikipedia:Xinerama|Xinerama]], and lacked source code comments and documentation.<br />
<br />
Clients within i3 are either allowed to float or placed into containers. Clients can be stacked or tabbed within containers. <br />
<br />
== Installation ==<br />
i3 is located in the {{codeline|[[community]]}} repository. Installing i3 can be accomplished by choosing the {{Package Official|i3}} group, which includes the packages {{Package Official|i3lock}}, {{Package Official|i3status}} and {{Package Official|i3-wm}}.<br />
# pacman -S i3<br />
<br />
Alternatively, you can install the window manager exclusively:<br />
# pacman -S i3-wm<br />
<br />
Additionally, {{Package AUR|i3-git}} is available in [[AUR]].<br />
<br />
==Running i3==<br />
<br />
Edit your {{Filename|~/.xinitrc}} and add:<br />
exec i3<br />
If you want i3 to log its output (useful for debugging), add this line to {{Filename|~/.xinitrc}}:<br />
exec i3 -V >>~/.i3/i3log >&1<br />
If you use the Nvidia binary driver you need to add the --force-xinerama flag to {{Filename|~/.xinitrc}}. A detailed explanation can be found at [http://i3wm.org/docs/multi-monitor.html i3wm.org].<br />
exec i3 --force-xinerama<br />
<br />
== Basic Keybindings and Window Management ==<br />
The default keybindings mostly depend on Mod1 (usually mapped to Alt) as the basic modifier key sometimes combined with Ctrl or Shift.<br />
Other binds use Mod3 as the base modifier (often the Windows-key). To identify the different Mod# keys on your system, use the<br />
command {{Codeline|xmodmap}} without arguments.<br />
<br />
The key combinations are configured in the file {{Filename|~/.i3/config}} (or, if it does not exist, {{Filename|/etc/i3/config}}).<br />
<br />
The default key combinations rely on key codes and not on the actual letters of your keyboard layout! You can replace the {{Codeline|bind}} directives in the config with {{Codeline|bindsym}} directives if you do not like this. For more info on configuration see the next section.<br />
<br />
Some of the most important keybindings include the following:<br />
* Run a program: Mod1+v<br />
* Create a new terminal: Mod1+Enter<br />
* Switch between different windows: Mod1+ any of "jkl;" or cursor keys (somewhat Vim-like keybindings)<br />
* Move a window: Mod1+Shift+ any of "jkl;" or cursor keys<br />
* Switch to a different workspace: Mod1+ any number<br />
* Move window to a different workspace: Mod1+Shift+ any number<br />
<br />
Note that i3 uses containers for window management. So in contrast to [[Wmii]] you can also tile windows horizontally. To do this, simply move a window up or down (with Mod1+Shift+DirectionKey) beyond the edge of the screen. A new row will appear. You can then use Mod4+Ctrl+DirectionKey to enlarge the window into the chosen direction. DirectionKey can be the arrow keys as well as "jkl;".<br />
<br />
There are 3 container modes:<br />
* Normal: Mod1+e<br />
* Maximized: Mod1+w<br />
* Stacked: Mod1+s<br />
<br />
Additionally, you can put a window into fullscreen mode with Mod1+f.<br />
<br />
[http://i3wm.org/docs/refcard.pdf | i3 keybinding cheatsheet]<br />
<br />
== Configuration ==<br />
<br />
i3 is configured using a simple text file. It first looks for {{Filename|~/.i3/config}} and if it doesn't exist, reads the default config at {{Filename|/etc/i3/config}}. So to start customizing, copy the config file to your home directory:<br />
cp /etc/i3/config ~/.i3/config<br />
The config allows you to change such things as:<br />
*Border colors<br />
*Font<br />
*Keybindings<br />
*Workspace names<br />
*Default container layout<br />
*Assignment of apps to specific workspaces<br />
<br />
The i3 [http://i3.zekjur.net/docs/userguide.html User's Guide] gives a nice overview of the config settings.<br />
<br />
For users seeking to convert their configuration to v4, i3-wm comes with a perl script for conversion:<br />
<pre>mv config config.old #save the old file<br />
i3-migrate-config-to-v4 config.old > config<br />
</pre><br />
Have a look at the changes!<br />
<br />
== Status Bar ==<br />
As of version 4 the internal statusbar of i3 does not exist anymore. Instead, [http://git.merovius.de/i3bar/ i3bar] is the new default.<br />
It can be used to view information produced by conky or i3status:<br />
exec i3bar -c 'conky -c ~/.i3/conki3'<br />
exec i3bar -c 'i3status'<br />
<br />
[http://wiki.archlinux.org/index.php/Dzen dzen2] can be placed in the information bar at the bottom of the screen. Information for dzen2 can be generated using [http://www.archlinux.org/packages/community/i686/i3status/ i3status] or [http://wiki.archlinux.org/index.php/Conky conky].<br />
i3status | dzen2 &<br />
Or<br />
conky | dzen2 &<br />
The svn development version of [http://aur.archlinux.org/packages.php?ID=19926 dzen2] in the [[AUR]] offers a -dock option, which puts dzen2 at the bottom of the screen and tells i3 not to manage it.<br />
<br />
In the AUR you can also find [http://aur.archlinux.org/packages.php?ID=36389 i3-wsbar], which is able to get the list of workspaces from the socket that i3 offers for IPC. Thus you can pipe the conky output to i3-wsbar and tell it to use dzen2.<br />
E.g., put the following in {{Filename|~/.i3/config}}:<br />
exec conky | i3-wsbar -c "dzen2 -x %x -dock -fn -*-profont-*-*-*-*-11-*-*-*-*-*-*-* -ta l"<br />
Please note that in your conky configuration file you can use the color codes for dzen2, so that you can get a nice, colored statusbar (see this sample [http://archlinux.lando.imap.cc/i3/.conkyrc conkyrc] and the corresponding [http://archlinux.lando.imap.cc/i3/i3-wsbar.png screenshot]).<br />
<br />
=== Comparison of i3bar and dzen2 ===<br />
This is a comparison of i3bar and dzen2. It only takes into account how well the two programs can handle the input from conky or i3status (formatting, colors, alignment, special fonts etc).<br />
{| border="1" cellpadding="5" align="center"<br />
! Program !! Color Codes !! Formatting !! Special Fonts !! Dock<br />
|-<br />
| i3bar || No || No, right aligned || No (UTF8 only)|| Yes<br />
|-<br />
| dzen2 || Yes || No, left aligned || Yes || Yes (the svn version)<br />
|-<br />
|}<br />
<br />
Though development of i3bar is very active and support for custom formatting and fonts has been announced, dzen2-svn has an edge over i3bar (as of 7th of August). From the i3bar man page:<br />
:"i3bar does not yet support formatting in the displayed statusline. However it does support setting colors for the<br />
: bar, the workspace-buttons and the statusline."<br />
<br />
== Other tools ==<br />
i3 currently uses [[Dmenu]] as a application launcher, which is bound by default to {{Keypress|Mod1|background=#FF0}}+{{Keypress|d}}. <br />
<br />
[http://www.archlinux.org/packages/community/i686/i3lock/ i3lock] is a screen locker inspired by {{Package Official|slock}}.<br />
<br />
== Additional sources ==<br />
* [http://i3wm.org/docs/ Official i3 Documentation]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=I3&diff=164487I32011-10-07T17:09:32Z<p>Taylorchu: /* Basic Keybindings and Window Management */</p>
<hr />
<div>{{i18n|i3}}<br />
{{DISPLAYTITLE:i3}}<br />
[[Category:Tiling WMs (English)]]<br />
<br />
[http://i3.zekjur.net/ i3] is a dynamic [[Wikipedia:Tiling window manager|tiling window manager]] inspired by [[Wmii]] that is primarily targeted at developers and advanced users.<br />
<br />
== Introduction ==<br />
The developers' attempt to hack and fix [[Wmii]] led to the creation of i3. At the time Wmii didn't provide certain features, like support for [[Wikipedia:Xinerama|Xinerama]], and lacked source code comments and documentation.<br />
<br />
Clients within i3 are either allowed to float or placed into containers. Clients can be stacked or tabbed within containers. <br />
<br />
== Installation ==<br />
i3 is located in the {{codeline|[[community]]}} repository. Installing i3 can be accomplished by choosing the {{Package Official|i3}} group, which includes the packages {{Package Official|i3lock}}, {{Package Official|i3status}} and {{Package Official|i3-wm}}.<br />
# pacman -S i3<br />
<br />
Alternatively, you can install the window manager exclusively:<br />
# pacman -S i3-wm<br />
<br />
Additionally, {{Package AUR|i3-git}} is available in [[AUR]].<br />
<br />
==Running i3==<br />
<br />
Edit your {{Filename|~/.xinitrc}} and add:<br />
exec i3<br />
If you want i3 to log its output (useful for debugging), add this line to {{Filename|~/.xinitrc}}:<br />
exec i3 -V >>~/.i3/i3log >&1<br />
If you use the Nvidia binary driver you need to add the --force-xinerama flag to {{Filename|~/.xinitrc}}. A detailed explanation can be found at [http://i3wm.org/docs/multi-monitor.html i3wm.org].<br />
exec i3 --force-xinerama<br />
<br />
== Basic Keybindings and Window Management ==<br />
The default keybindings mostly depend on Mod1 (usually mapped to Alt) as the basic modifier key sometimes combined with Ctrl or Shift.<br />
Other binds use Mod3 as the base modifier (often the Windows-key). To identify the different Mod# keys on your system, use the<br />
command {{Codeline|xmodmap}} without arguments.<br />
<br />
The key combinations are configured in the file {{Filename|~/.i3/config}} (or, if it does not exist, {{Filename|/etc/i3/config}}).<br />
<br />
The default key combinations rely on key codes and not on the actual letters of your keyboard layout! You can replace the {{Codeline|bind}} directives in the config with {{Codeline|bindsym}} directives if you do not like this. For more info on configuration see the next section.<br />
<br />
Some of the most important keybindings include the following:<br />
* Run a program: Mod1+v<br />
* Create a new terminal: Mod1+Enter<br />
* Switch between different windows: Mod1+ any of "jkl;" or cursor keys (somewhat Vim-like keybindings)<br />
* Move a window: Mod1+Shift+ any of "jkl;" or cursor keys<br />
* Switch to a different workspace: Mod1+ any number<br />
* Move window to a different workspace: Mod1+Shift+ any number<br />
<br />
Note that i3 uses containers for window management. So in contrast to [[Wmii]] you can also tile windows horizontally. To do this, simply move a window up or down (with Mod1+Shift+DirectionKey) beyond the edge of the screen. A new row will appear. You can then use Mod4+Ctrl+DirectionKey to enlarge the window into the chosen direction. DirectionKey can be the arrow keys as well as "jkl;".<br />
<br />
There are 3 container modes:<br />
* Normal: Mod1+e<br />
* Maximized: Mod1+w<br />
* Stacked: Mod1+s<br />
<br />
Additionally, you can put a window into fullscreen mode with Mod4+f.<br />
<br />
== Configuration ==<br />
<br />
i3 is configured using a simple text file. It first looks for {{Filename|~/.i3/config}} and if it doesn't exist, reads the default config at {{Filename|/etc/i3/config}}. So to start customizing, copy the config file to your home directory:<br />
cp /etc/i3/config ~/.i3/config<br />
The config allows you to change such things as:<br />
*Border colors<br />
*Font<br />
*Keybindings<br />
*Workspace names<br />
*Default container layout<br />
*Assignment of apps to specific workspaces<br />
<br />
The i3 [http://i3.zekjur.net/docs/userguide.html User's Guide] gives a nice overview of the config settings.<br />
<br />
For users seeking to convert their configuration to v4, i3-wm comes with a perl script for conversion:<br />
<pre>mv config config.old #save the old file<br />
i3-migrate-config-to-v4 config.old > config<br />
</pre><br />
Have a look at the changes!<br />
<br />
== Status Bar ==<br />
As of version 4 the internal statusbar of i3 does not exist anymore. Instead, [http://git.merovius.de/i3bar/ i3bar] is the new default.<br />
It can be used to view information produced by conky or i3status:<br />
exec i3bar -c 'conky -c ~/.i3/conki3'<br />
exec i3bar -c 'i3status'<br />
<br />
[http://wiki.archlinux.org/index.php/Dzen dzen2] can be placed in the information bar at the bottom of the screen. Information for dzen2 can be generated using [http://www.archlinux.org/packages/community/i686/i3status/ i3status] or [http://wiki.archlinux.org/index.php/Conky conky].<br />
i3status | dzen2 &<br />
Or<br />
conky | dzen2 &<br />
The svn development version of [http://aur.archlinux.org/packages.php?ID=19926 dzen2] in the [[AUR]] offers a -dock option, which puts dzen2 at the bottom of the screen and tells i3 not to manage it.<br />
<br />
In the AUR you can also find [http://aur.archlinux.org/packages.php?ID=36389 i3-wsbar], which is able to get the list of workspaces from the socket that i3 offers for IPC. Thus you can pipe the conky output to i3-wsbar and tell it to use dzen2.<br />
E.g., put the following in {{Filename|~/.i3/config}}:<br />
exec conky | i3-wsbar -c "dzen2 -x %x -dock -fn -*-profont-*-*-*-*-11-*-*-*-*-*-*-* -ta l"<br />
Please note that in your conky configuration file you can use the color codes for dzen2, so that you can get a nice, colored statusbar (see this sample [http://archlinux.lando.imap.cc/i3/.conkyrc conkyrc] and the corresponding [http://archlinux.lando.imap.cc/i3/i3-wsbar.png screenshot]).<br />
<br />
=== Comparison of i3bar and dzen2 ===<br />
This is a comparison of i3bar and dzen2. It only takes into account how well the two programs can handle the input from conky or i3status (formatting, colors, alignment, special fonts etc).<br />
{| border="1" cellpadding="5" align="center"<br />
! Program !! Color Codes !! Formatting !! Special Fonts !! Dock<br />
|-<br />
| i3bar || No || No, right aligned || No (UTF8 only)|| Yes<br />
|-<br />
| dzen2 || Yes || No, left aligned || Yes || Yes (the svn version)<br />
|-<br />
|}<br />
<br />
Though development of i3bar is very active and support for custom formatting and fonts has been announced, dzen2-svn has an edge over i3bar (as of 7th of August). From the i3bar man page:<br />
:"i3bar does not yet support formatting in the displayed statusline. However it does support setting colors for the<br />
: bar, the workspace-buttons and the statusline."<br />
<br />
== Other tools ==<br />
i3 currently uses [[Dmenu]] as a application launcher, which is bound by default to {{Keypress|Mod1|background=#FF0}}+{{Keypress|d}}. <br />
<br />
[http://www.archlinux.org/packages/community/i686/i3lock/ i3lock] is a screen locker inspired by {{Package Official|slock}}.<br />
<br />
== Additional sources ==<br />
* [http://i3wm.org/docs/ Official i3 Documentation]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Unofficial_user_repositories&diff=161223Unofficial user repositories2011-09-21T17:29:24Z<p>Taylorchu: /* i686 only */</p>
<hr />
<div>[[Category: Package management (English)]]<br />
==Why unofficial user repositories==<br />
Since the AUR only allows users to upload PKGBUILD and other package build related files, but does not provide a means for distributing a binary package, a user may want to create a binary repository of their packages elsewhere.<br />
<br />
==The future of Unofficial repos==<br />
I'd like to see more work of this type. Sometimes there are certain projects that don't mesh well with other things, such as the community repo. The 'kdemod' project is a good example. If you want to contribute with your own builds, you can check page [[Custom local repository]].<br />
<br />
In the future, well-thought-out user repositories may be ideal for lots of supplementary things. Forming a "web of trust" is important in cases like this, so we may begin keeping a list of "recommended" repositories somewhere, in order to make it seem more official and trustworthy.<br />
<br />
[[User:Phrakture|Phrakture]] 12:50, 18 May 2007 (EDT)<br />
<br />
==List of PUR (unofficial user repositories)==<br />
===Any===<br />
"Any" repos are architecture-independent, i.e. they can be used on both i686 and x86_64 systems.<br />
<pre><br />
[herecura-stable-any]<br />
# Just some stuff; a few java apps, wallpapers, small scripts, xbmc-skin<br />
Server = http://herecura.be/repo/herecura-stable/any<br />
<br />
[herecura-testing-any]<br />
# Some any testing stuff, xbmc-svn skin<br />
Server = http://herecura.be/repo/herecura-testing/any<br />
<br />
[xyne-any]<br />
# The home of Xyne's contributions.<br />
# More info including a package list can be found at http://xyne.archlinux.ca/repos<br />
Server = http://xyne.archlinux.ca/repos/xyne-any/<br />
<br />
[arch-fonts]<br />
# Prebuilt packages for font packages found in AUR<br />
# This should be faster than building from source<br />
# as many have download speed of 10KB/s. If you find<br />
# missing font, email to <gmail.com: jesse.jaara><br />
Server = http://huulivoide.pp.fi/Arch/arch-fonts<br />
</pre><br />
<br />
===Both i686 and x86_64===<br />
<!--Not exactly same as 'any' repositories, this section should probably be separate.--><br />
Repositories with both i686 and x86_64 versions. The $arch variable will be set automatically by pacman.<br />
<pre><br />
[allanbrokeit]<br />
# http://allanmcrae.com/2011/06/the-allanbrokeit-repo-that-might-really-break-your-system/<br />
Server = http://allanmcrae.com/$repo/$arch<br />
<br />
[adslgr]<br />
# The Hellenic (Greek) archlinux unofficial repository with many interesting packages.<br />
Server = http://archlinuxgr.tiven.org/archlinux/$arch<br />
<br />
[archlinuxfr]<br />
# The french Arch Linux communities packages.<br />
Server = http://repo.archlinux.fr/$arch<br />
<br />
[archaudio-production]<br />
# verified PKGBUILDs AND tested packages<br />
Server = http://repos.archaudio.org/$repo/$arch<br />
<br />
[archaudio-preview]<br />
# unverified PKGBUILDs AND/OR untested packages<br />
Server = http://repos.archaudio.org/$repo/$arch<br />
<br />
[archaudio-nightly]<br />
# verified devel PKGBUILDs<br />
Server = http://repos.archaudio.org/$repo/$arch<br />
<br />
[archaudio-experimental]<br />
# unverified devel PKGBUILDs<br />
Server = http://repos.archaudio.org/$repo/$arch<br />
<br />
[archstuff]<br />
# AUR's most voted and many bin32-* and lib32-* packages.<br />
Server = http://archstuff.vs169092.vserver.de/$arch<br />
<br />
[arch-games]<br />
# The Arch Linux Gaming repository project.<br />
# Active mirrors listed in https://github.com/Arch-Games/arch-games/wiki/Mirrors<br />
Server = http://repo.exigen.org/arch/games/$arch<br />
Server = ftp://mirror.selfnet.de/arch-games/$arch<br />
# Currently inactive mirrors<br />
#Server = http://arch.twilightlair.net/games/$arch<br />
#Server = http://pseudoform.org/arch-games/games/$arch<br />
<br />
[burg]<br />
# Burg bootloader repo<br />
# More info : http://archydeb.wordpress.com/<br />
Server = http://dl.dropbox.com/u/11529444/repos/archlinux/burg/$arch<br />
<br />
[catalyst]<br />
# ATI Catalyst proprietary drivers.<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/$arch<br />
<br />
[heftig]<br />
# Includes kernel26-zen and aurora (firefox development build - works alongside firefox in extra.)<br />
# https://bbs.archlinux.org/viewtopic.php?id=117157<br />
Server = http://pkgbuild.com/~heftig/repo/$arch<br />
<br />
[kde4-eyecandy]<br />
# Useful and beautiful plasmoids and themes for KDE4.<br />
Server = http://archlinuxgr.tiven.org/kde4-eyecandy/$arch<br />
<br />
[repo-ck]<br />
# ARCH kernel with Brain Fuck Scheduler and all the goodies in the ck1 patch set<br />
Server = http://repo-ck.com/$arch<br />
<br />
[kittyserve]<br />
# Contains kittykatt's packages and packages from friends of kittykatt, as well as most mint-related packages<br />
Server = http://repo.kattz.tk/$arch<br />
<br />
[kxstudio-free]<br />
# KXStudio Free<br />
Server = http://kxstudio.sf.net/repo/arch/$arch<br />
<br />
[kxstudio-non-free]<br />
# KXStudio Non-Free<br />
Server = http://kxstudio.sf.net/repo/arch/$arch <br />
<br />
[mate]<br />
# Contains official mate desktop packages (gnome2 fork)<br />
Server = http://matsusoft.com.ar/repository/archlinux/mate/$arch<br />
Server = http://germ.winpe.com/archlinux/mate/$arch<br />
<br />
[pfkernel]<br />
# linux-pf and kernel26-pf<br />
# Kernel packages: generic i686 and x86_64, optimized P3, P4, K7, Atom, Pentium-M, K8, Core2<br />
# amarok1, nvidia-pf, squid3, arora-git, nvidia-96xx+utils, gdm-old, w3perl<br />
Server = http://dl.dropbox.com/u/11734958/$arch<br />
<br />
[radeon]<br />
# ATI Radeon X.Org drivers, bleeding edge 'git' builds.<br />
Server = http://spiralinear.org/perry3d/$arch<br />
<br />
[repo-ck]<br />
# Public server that holds cpu optimized packages of linux-ck<br />
# See the kernel26-ck wiki page for more<br />
Server = http://repo-ck.com/$arch<br />
<br />
[sergej-repo]<br />
# ion3 and some other stuff.<br />
# http://code.google.com/p/archlinux-stuff/source/browse/trunk<br />
Server = http://repo.p5n.pp.ru/sergej-repo/$arch/<br />
<br />
[suckless]<br />
# suckless.org packages<br />
Server = http://dl.suckless.org/arch/$arch<br />
</pre><br />
<br />
===i686 only===<br />
<pre><br />
[andrwe]<br />
# For a list of packages see: http://andrwe.org/doku.php/linux/repository<br />
Server = http://repo.andrwe.org/i686<br />
<br />
[archlinux-es]<br />
# Repositorio Hispano (Spanish/Hispanic Respository).<br />
Server = http://repo.archlinux-es.org/i686<br />
<br />
[arch-graphics]<br />
# Repository aimed to provide applications mainly for 3D graphics.<br />
# For more info, look at http://arch-graphics.kx.cz/<br />
Server = http://arch-graphics.kx.cz/repo/i686<br />
<br />
[cgr-i686]<br />
# Packages for some ChicoGeek's PKGBUILDs.<br />
Server = http://cgr.i686.googlepages.com/<br />
<br />
[chaox-stable]<br />
# Pentesting packages and custom kernel patched for WIFI injection.<br />
Server = http://repo.chaox.net/stable<br />
<br />
[compiz-fusion]<br />
# compiz-fusion-git<br />
# Updated to June 2008.<br />
Server = http://compiz.dreamz-box.de/i686<br />
<br />
[esclinux]<br />
# Mostly games, interactive fiction and abc notation stuffs already on AUR.<br />
Server = http://download.tuxfamily.org/esclinuxcd/ressources/repo/i686/<br />
<br />
[fukawi]<br />
# Some Nagios Stuff; molly-guard; celtx and various networking tools.<br />
Server = http://repo.fukawi2.nl/i686/<br />
Server = ftp://repo.fukawi2.nl/i686/<br />
<br />
[jose1711repo]<br />
# Most of the packages I maintain in AUR (games, tools)<br />
Server = http://arch.l33t.in/i686/<br />
<br />
[kpiche]<br />
# Stable OpenSync packages.<br />
Server = http://kpiche.archlinux.ca/repo<br />
<br />
[rfad]<br />
# Repository made by haxit | Contact at: requiem [at] archlinux.us for package suggestions!<br />
Server = http://web.ncf.ca/ey723/archlinux/repo/<br />
<br />
[xdemon-repo]<br />
# madwimax, kismet-svn and aircrack-svn, etc...<br />
Server=http://repo.x-demon.org/archlinux/os/i686<br />
<br />
[herecura-stable]<br />
# Additional apps not found in community.<br />
Server = http://herecura.be/repo/herecura-stable/i686<br />
<br />
[herecura-testing]<br />
# Additional apps for testing build against stable Arch.<br />
Server = http://herecura.be/repo/herecura-testing/i686<br />
<br />
[studioidefix]<br />
# Precompiled boxee packages.<br />
Server = http://studioidefix.googlecode.com/hg/repo/i686<br />
<br />
[mingw32]<br />
# Libs & tools for crosscompiling for Win32, mainly taken from AUR.<br />
# Contact: Alexander 'hatred' Drozdov <adrozdoff [at] gmail (dot) com> (Russian-speaked guys can write on Russian :-)<br />
Server = http://hatred.homelinux.net/archlinux/mingw32/os/i686<br />
<br />
[ayatana]<br />
# Packages from Ubuntu (humanity-icon-theme, ttf-ubuntu, ubuntu-light-themes, ubuntuone-client, indicator-applet, notify-osd…),<br />
# packages from elementary project (dexter, elementary-icon-theme, gloobus-preview, gnome-theme-elementary, postler…),<br />
# packages from Linux Mint (gnome-theme-mint, mintbackup, mintdesktop, mint-icon-theme, mintmenu…) and<br />
# apps with ayatana support (audio-recorder, banshee-community-extensions, cloudsn, gwibber, pino, sbackup, smuxi…),<br />
# extra GNOME apps (conduit, eog-plugins, glabels, gnome-color-manager, gnome-globalmenu, gnome-subtitles, ontv, pdfmod, rygel, postr, tasque…),<br />
# mapping apps (bt747, emerillon, foxtrotgps, gpx-viewer, merkaartor, navit, prune…),<br />
# some other apps (backintime, connman, faenza-icon-theme, gdesklets, keepnote, kompozer, nautilus-terminal, openbve, pinta, textflow, uget…).<br />
# More info: http://arch.ballogyorgy.com/<br />
Server = http://repo.ayatana.info/<br />
<br />
[sylar_repo]<br />
# My built packages.<br />
# Additional info and package list: see http://dl.dropbox.com/u/8192972/arch_repo/arch_repo.html<br />
Server = http://dl.dropbox.com/u/8192972/arch_repo/repo<br />
<br />
[kernel26-pae]<br />
# PAE-enabled 32-bit kernel 2.6.39<br />
Server = http://kernel26-pae.archlinux.ca/<br />
<br />
[linux-pae]<br />
# PAE-enabled 32-bit kernel 3.0<br />
Server = http://pae.archlinux.ca/<br />
<br />
[aur]<br />
# most common packages in aur<br />
# readme: http://dl.dropbox.com/u/10527821/repo/i686/readme.txt<br />
# packages: http://dl.dropbox.com/u/10527821/repo/i686/pkglst.txt<br />
http://dl.dropbox.com/u/10527821/repo/i686/<br />
<br />
</pre><br />
<br />
===x86_64 only===<br />
<pre><br />
[andrwe]<br />
# For a list of packages see: http://andrwe.dyndns.org/doku.php/blog/repository<br />
Server = http://repo.andrwe.org/x86_64<br />
<br />
[archlinux-es]<br />
# Repositorio Hispano (Spanish/Hispanic Respository).<br />
Server = http://repo.archlinux-es.org/x86_64<br />
<br />
[archstudio]<br />
# ArchAudio Packages <br />
# Optimized for Intel Core {i3,i5,i7} CPU <br />
# Package Details: http://dl.dropbox.com/u/5977716/archstudio.html<br />
Server = http://dl.dropbox.com/u/5977716/x86_64<br />
<br />
[compiz-fusion]<br />
# compiz-fusion-git<br />
Server = http://compiz.dreamz-box.de/x86_64<br />
<br />
[nightly]<br />
# Nightly builds of some packages from the AUR.<br />
# Repo-Tracker: http://tracker.kromonos.net/projects/show/nightlyarch<br />
Server = http://files.shadowice.org/nightly/x86_64<br />
<br />
[zen]<br />
# Various and zengeist' AUR packages.<br />
Server = http://zloduch.cz/archlinux/x86_64<br />
<br />
[seiichiro]<br />
# VDR and some plugins, mms, foo2zjs-drivers<br />
Server = http://repo.seiichiro0185.org/x86_64<br />
<br />
[herecura-stable]<br />
# Additional apps not found in community.<br />
Server = http://herecura.be/repo/herecura-stable/x86_64<br />
<br />
[herecura-testing]<br />
# Additional apps for testing build against stable Arch.<br />
Server = http://herecura.be/repo/herecura-testing/x86_64<br />
<br />
[studioidefix]<br />
# Precompiled boxee packages.<br />
Server = http://studioidefix.googlecode.com/hg/repo/x86_64<br />
<br />
[pyropeter]<br />
# My AUR packages: https://aur.archlinux.org/packages.php?SeB=m&K=pyropeter<br />
Server = http://keks.selfip.org/arch/pyropeter<br />
<br />
[sorcix]<br />
# Various packages from AUR: dropbox, nautilus-dropbox, minecraft, etc..<br />
# Packagelist: http://archlinux.sorcix.com/repository/<br />
Server = http://archlinux.sorcix.com/repository/x86_64<br />
</pre><br />
<br />
==Add your own repository to this list==<br />
If you have your own repository, please add this to this list, so that all other users knows where to find your packages.</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Openbox&diff=141143Openbox2011-05-12T04:08:25Z<p>Taylorchu: /* Python-based xdg menu script */</p>
<hr />
<div>[[Category:Stacking WMs (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|Openbox}}<br />
<br />
Openbox is a lightweight and highly configurable window manager with extensive standards support. Its features are documented at the [http://openbox.org/ official website]. This article pertains to installing Openbox under Arch Linux.<br />
<br />
== Installation ==<br />
<br />
Openbox is available from the standard repositories:<br />
# pacman -S openbox<br />
<br />
After installation, you should copy the default configuration files '''{{Filename|rc.xml}}''', '''{{Filename|menu.xml}}''', and '''{{Filename|autostart.sh}}''' to ''{{Filename|~/.config/openbox}}'' :<br />
<br />
$ mkdir -p ~/.config/openbox<br />
$ cp /etc/xdg/openbox/{rc.xml,menu.xml,autostart.sh} ~/.config/openbox<br />
<br />
{{Note | Do this as a regular user, not as root.}}<br />
<br />
File '''{{Filename|rc.xml}}''' is the configuration file. It defines keyboard shortcuts, themes, virtual desktops, and more.<br />
<br />
File '''{{Filename|menu.xml}}''' defines the menu that appears when you click on the desktop. The default menu items are sparse and some are for applications you probably have not even installed. It's easy to modify your menu to suit your needs; see the [[#Menus|menus]] section below or visit the [http://openbox.org Openbox website].<br />
<br />
The default '''{{Filename|autostart.sh}}''' file defines several environment variables. You may wish to append commands to this script to launch a panel, install wallpaper, or something else. Details are in the [http://openbox.org/wiki/Help:Autostart Openbox Wiki].<br />
<br />
== Openbox as a stand-alone WM ==<br />
<br />
Openbox can be used as a stand-alone window manager (WM). This is usually simpler to install and configure than using Openbox with desktop environments. Running openbox alone may reduce your system's CPU and memory load.<br />
<br />
To run Openbox as a stand-alone window manager, append the following to '''{{Filename|~/.xinitrc}}''':<br />
exec openbox-session<br />
<br />
You may also start Openbox from the command shell (aka: text prompt) using '''xinit''':<br />
$ xinit /usr/bin/openbox-session<br />
<br />
If you used another window manager previously (such as Xfwm) and now Openbox won't start after logging out of X, try moving the autostart folder:<br />
mv ~/.config/autostart ~/.config/autostart-bak<br />
<br />
Using D-Bus or similar, use this instead:<br />
exec ck-launch-session openbox-session<br />
<br />
If you also use '''polkit''' and '''D-Bus''' (e.g. for auto-mount drivers in Nautilus/Gnome) use:<br />
exec ck-launch-session dbus-launch openbox-session<br />
<br />
{{Note | [http://www.archlinux.org/packages/extra/any/pyxdg/ pyxdg] is required for Openbox's xdg-autostart}}<br />
{{Note | "dbus-launch" must be placed after "ck-launch-session" or you will experience mounting problems}}<br />
<br />
== Openbox as a WM for desktop environments ==<br />
<br />
Openbox can be used as a replacement window manager for full-fledged desktop environments. The method for deploying Openbox depends on the desktop environment.<br />
<br />
=== GNOME 2.24 and 2.26 ===<br />
Create {{Filename|/usr/share/applications/openbox.desktop}} with the following lines:<br />
[Desktop Entry]<br />
Type=Application<br />
Encoding=UTF-8<br />
Name=OpenBox<br />
Exec=openbox<br />
NoDisplay=true<br />
# name of loadable control center module<br />
X-GNOME-WMSettingsModule=openbox<br />
# name we put on the WM spec check window<br />
X-GNOME-WMName=OpenBox<br />
In gconf, set '''{{Codeline|/desktop/gnome/session/required_components/windowmanager}}''' to '''{{Codeline|openbox}}:'''<br />
$ gconftool-2 -s -t string /desktop/gnome/session/required_components/windowmanager openbox<br />
Finally, choose '''GNOME''' session from the GDM sessions menu.<br />
<br />
=== GNOME 2.26 Redux ===<br />
'''''If the previous guide for GNOME 2.24 fails:'''''<br />
<br />
If, when attempting to log into a "Gnome/Openbox" session -- and it consistently fails to start, try the following. This is one way of achieving your goal of using Openbox as the WM anytime you open a Gnome session:<br />
<br />
#Log into your Gnome-only session (it should still be using Metacity as its window manager).<br />
#Install Openbox if you have not done so already<br />
#Navigate your menus to ''System &rarr; Preferences &rarr; Startup Applications'' (possibly named 'Session' in older Gnome versions)<br />
#Open Startup Application, select '+ Add' and enter the text shown below. Omit the text after #.<br />
#Click the 'Add' button for the data entry window. Make sure the checkbox beside your new entry is selected.<br />
#Log out from your Gnome session and log back in<br />
#You should now be running openbox as your window manager.<br />
<br />
Name: Openbox Windox Manager # Can be changed<br />
Command: openbox --replace # Text should not be removed from this line, but possibly added to it<br />
Comment: Replaces metacity with openbox # Can be changed<br />
<br />
This creates a startup list entry which is executed by Gnome each time the user's session is started.<br />
<br />
=== GNOME 2.22 and prior ===<br />
# If you use GDM, select the "GNOME/Openbox" login option<br />
# If you use {{Codeline|startx}}, add {{Codeline|exec openbox-gnome-session}} to {{Filename|~/.xinitrc}}<br />
# From the shell:<br />
$ xinit /usr/bin/openbox-gnome-session<br />
<br />
=== KDE ===<br />
# If you use KDM, select the "KDE/Openbox" login option<br />
# If you use startx, add {{Codeline|exec openbox-kde-session}} to {{Filename|~/.xinitrc}}<br />
# From the shell:<br />
$ xinit /usr/bin/openbox-kde-session<br />
<br />
=== Xfce4 ===<br />
Log into a normal Xfce4 session. From your terminal, type:<br />
$ killall xfwm4 ; openbox & exit<br />
<br />
This kills xfwm4, runs Openbox, and closes the terminal. Log out, being sure to check the ''"Save session for future logins"'' box. On your next login, Xfce4 should use '''Openbox''' as its WM.<br />
<br />
To enable exiting from a session using ''xfce4-session,'' edit '''{{Filename|~/.config/openbox/menu.xml}}'''. If the file isn't there, copy it from {{Filename|/etc/xdg/openbox/}}. Look for the following entry:<br />
<item label="Exit Openbox"><br />
<action name="Exit"><br />
<prompt>yes</prompt><br />
</action><br />
</item><br />
<br />
Change it to:<br />
<item label="Exit Openbox"><br />
<action name="Execute"><br />
<prompt>yes</prompt><br />
<command>xfce4-session-logout</command><br />
</action><br />
</item><br />
<br />
Otherwise, choosing "Exit" from the root-menu causes Openbox to terminate its execution, leaving you with no window manager.<br />
<br />
If you have a problem changing virtual desktops with the mouse wheel skipping over desktops, edit '''{{Filename|~/.config/openbox/rc.xml}}'''. Move the ''mouse binds with...'' actions "DesktopPrevious" and "DesktopNext" from context ''Desktop'' to the context ''Root''. (You may need to create a definition for the ''Root'' context as well.)<br />
<br />
When using the Openbox root-menu instead of Xfce's menu, you may exit the Xfdesktop with this terminal command:<br />
$ xfdesktop --quit<br />
Xfdesktop manages the wallpaper and desktop icons, requiring you to use other utilities such as ROX for these functions.<br />
<br />
(When terminating Xfdesktop, the above issue with the virtual desktops is no longer a problem.)<br />
<br />
== Preferences ==<br />
<br />
There are two options for configuring Openbox preferences:<br />
<br />
=== Manual configuration ===<br />
To configure Openbox manually, edit '''{{Filename|~/.config/openbox/rc.xml}}''' with a text editor. The config file has comments throughout. More documentation is found in the [http://openbox.org/wiki/Help:Configuration Help:Configuration] article at the Openbox website.<br />
<br />
=== ObConf ===<br />
[http://openbox.org/wiki/ObConf:About ObConf] is an Openbox configuration tool. It is used to set most preferences such as themes, virtual desktops, window properties, and desktop margins.<br />
<br />
# pacman -S obconf<br />
<br />
ObConf cannot configure keyboard shortcuts and certain other features. For these features edit '''{{Filename|rc.xml}}''' manually.<br />
<br />
An alternative is [http://code.google.com/p/obkey/ ObKey], available in the [[AUR]].<br />
<br />
=== Application customization ===<br />
<br />
Openbox allows per-application customizations. This lets you define rules for a given program. For example:<br />
* Start your web browser on a specific virtual desktop.<br />
* Open your terminal program with no window decorations (window chrome).<br />
* Make your bit-torrent client open at a given screen position.<br />
<br />
Per-application settings are defined in '''{{Filename|~/.config/openbox/rc.xml}}.''' Instructions are in the file's comments. Details are found in the [http://openbox.org/wiki/Help:Applications Help:Applications] article at the official Openbox web site.<br />
<br />
== Menus ==<br />
<br />
The default Openbox menu includes a variety of menu items to get you started. Many of these items launch applications you don't want, haven't installed yet, or never intend to install. You'll surely want to customize '''{{Filename|menu.xml}}''' at some point. There are a number of ways to do so.<br />
<br />
=== Manual configuration of menus ===<br />
<br />
You can edit {{Filename|~/.config/openbox/menu.xml}} with a text editor. Many of the settings are self-explanatory. The article [http://openbox.org/wiki/Help:Menus Help:Menus] has extensive details.<br />
<br />
=== MenuMaker ===<br />
<br />
[http://menumaker.sourceforge.net/ MenuMaker] creates XML menus for several window managers including Openbox. MenuMaker searchs your computer for executable programs and creates a menu file from the result. It can be configured to exclude certain application types (GNOME, KDE, etc) if you desire.<br />
# pacman -S menumaker # Install MenuMaker from the repository<br />
<br />
Once installed, generate a menu file (named {{Filename|menu.xml}}) by running the program.<br />
$ mmaker -v OpenBox3 # Will not overwrite an existing menu file.<br />
$ mmaker -vf OpenBox3 # Force option permits overwriting the menu file.<br />
$ mmaker --help # See the full set of options for MenuMaker.<br />
<br />
MenuMaker creates a comprehensive {{Filename|menu.xml}}. You may edit this file by hand or regenerate it after installing software.<br />
<br />
=== Obmenu ===<br />
<br />
Obmenu is a menu editor for Openbox. This GUI application is the best choice for those who dislike editing XML code. Obmenu is available in the community repository:<br />
# pacman -S obmenu<br />
<br />
Once installed, run {{Codeline|obmenu}} then add and remove applications as desired.<br />
<br />
==== Obm-xdg ====<br />
<br />
<tt>obm-xdg</tt> is a command-line tool that comes with Obmenu. It generates a categorized sub-menu of installed GTK/GNOME applications.<br />
<br />
To use obm-xdg with other menus, add the following line to '''{{Filename|~/.config/openbox/menu.xml}}''':<br />
<menu execute="obm-xdg" id="xdg-menu" label="xdg"/><br />
<br />
Then add the following line under your 'root-menu' entry where you want to have the menu appear:<br />
<menu id="xdg-menu"/><br />
<br />
To use obm-xdg by itself create '''{{Filename|~/.config/openbox/menu.xml}}''' and add these lines:<br />
<openbox_menu><br />
<menu execute="obm-xdg" id="root-menu" label="apps"/><br />
</openbox_menu><br />
<br />
<br />
Then run {{Codeline|openbox --reconfigure}} to refresh the Openbox menu. You should now see a sub-menu labeled '''xdg''' in your menu.<br />
<br />
{{Note|If you do not have GNOME installed, you need to install package '''gnome-menus''' for obm-xdg.}}<br />
<br />
=== Python-based xdg menu script ===<br />
<br />
This script is found in Fedora's Openbox package. You have only to put the script somewhere and create a menu entry.<br />
<br />
Here is the head: [http://pkgs.fedoraproject.org/gitweb/?p=openbox.git;f=xdg-menu;hb=HEAD latest script]<br />
<br />
Download from above repository. Place the file into the directory you want.<br />
<br />
Open '''{{Filename|menu.xml}}''' with your text editor and add the following entry. Of course, you can modify the label as you see fit.<br />
<menu id="apps-menu" label="xdg-menu" execute="python2 <path>/xdg-menu"/><br />
<br />
Save the file and run '''{{Codeline|openbox --reconfigure}}'''.<br />
<br />
=== Openbox menu generator ===<br />
<br />
Residing in the AUR as [http://aur.archlinux.org/packages.php?ID=27300 obmenugen-bin,] Openbox menu generator creates the menu file from *.desktop files. Obmenugen provides a text file which filters (hides) menu items using basic regex.<br />
$ obmenugen # Create a menu file<br />
$ openbox --reconfigure # To see the menu you generated<br />
<br />
=== Pipe menus ===<br />
<br />
Like other window managers, Openbox allows for scripts to dynamically build menus (menus on-the-fly). Examples are system monitors, media player controls, or weather monitors. Pipe menu script examples are found in the [http://openbox.org/wiki/Openbox:Pipemenus Openbox:Pipemenus] page at Openbox's site.<br />
<br />
User ''Xyne'' created a pipe menu file browser and user ''brisbin33'' created a pipe menu for scanning and connecting to wireless hot spots (using netcfg). Forum posts for these utilities are here: [http://bbs.archlinux.org/viewtopic.php?id=77197&p=1 file browser] and here: [http://bbs.archlinux.org/viewtopic.php?id=78290 wifi].<br />
<br />
User ''jnguyen'' created a pipe menu for managing removable devices using Udisks. The forum post is here: [https://bbs.archlinux.org/viewtopic.php?id=114702 obdevicemenu].<br />
<br />
== Startup programs ==<br />
<br />
Openbox supports running programs at startup. This is provided by command '''openbox-session'''.<br />
<br />
=== Enabling autostart ===<br />
<br />
There are two ways to enable autostart:<br />
# When using startx or xinit to begin a session, edit {{Filename|~/.xinitrc}}. Change the line that executes '''''openbox''''' to '''openbox-session'''.<br />
# When using GDM or KDM, selecting an ''Openbox'' session automatically runs the autostart script.<br />
<br />
=== Autostart script ===<br />
<br />
Openbox executes a user startup script located at {{Filename|~/.config/openbox/autostart.sh}}. This script is ''not'' created by default. In the absence of a user startup script, openbox executes the system startup script {{Filename|/etc/xdg/openbox/autostart.sh}}. The system script does not run when the user script is present.<br />
<br />
To create a personal startup script, copy the system script to your settings directory {{Filename|~/.config/openbox/}} and append your commands. This ensures your environment is properly configured.<br />
<br />
Full instructions are available from the [http://openbox.org/wiki/Help:Autostart Help:Autostart] article at the Openbox site.<br />
<br />
== Themes and appearance ==<br />
<br />
:{{Box YELLOW||The supplemental article '''[[Openbox_Themes_and_Apps|Openbox Themes and Apps]]''' has detailed information about changing Openbox's GUI.}}<br />
<br />
You probably installed a selection of Linux programs that were developed using different toolkits. Configuration settings for a given program may reside in an unexpected location.<br />
<br />
For example, the double-click setting used by [http://www.geany.org/ Geany] (an editor/IDE) is set within the file '''{{Filename|~/.gtkrc-2.0,}}''' not where you might expect in '''{{Filename|~/.config/openbox/rc.xml}}'''. Some visual aspects of Geany are set by .gtkrc-2.0 as well.<br />
<br />
Refer to the supplemental [[Openbox_Themes_and_Apps#Themes_and_appearance|Openbox Themes and Apps]] for visual theming information.<br />
<br />
=== Openbox themes ===<br />
<br />
Themes control the appearance of windows, titlebars, and buttons. They also control menu appearance and on-screen display (OSD). Additional themes are available from the standard repositories.<br />
# pacman -S openbox-themes<br />
<br />
=== Cursors, icons, wallpaper ===<br />
<br />
Please see [[Openbox_Themes_and_Apps#X11_Mouse_cursors|Openbox Themes and Apps]] for information on these GUI customizations.<br />
<br />
== Recommended programs ==<br />
:{{Box YELLOW||The supplemental wiki article '''[[Openbox_Themes_and_Apps#Recommended_programs|Openbox Themes and Apps]]''' has information on applications you may use with Openbox.<br>The article gives details about panels, trays, mixer controls, and other widgets used on a desktop interface.}}<br />
<br />
There is a list of [[Lightweight_Applications|Lightweight Applications]] in the wiki. Most of these work nicely with Openbox.<br />
<br />
=== Login managers ===<br />
<br />
[http://slim.berlios.de/ SLiM] is a graphical login manager. It works for standalone Openbox configurations. Refer to the [[SLiM]] wiki article for instructions.<br />
<br />
[http://qingy.sourceforge.net/ Qingy] is a light, highly-configurable graphical login manager. It supports login to either text console or X session. Qingy uses [http://www.directfb.org DirectFB]. Qingy does not start an X session unless you choose a session that uses X Windows. Read the Arch wiki article about [[Qingy|Qingy.]]<br />
<br />
=== Compositing the desktop view ===<br />
<br />
[[Xcompmgr]] is a compositing window manager capable of rendering drop shadows, fading, and window transparency for Openbox and other window managers.<br />
Note that xcompmgr is no longer being developed. Any problems are unlikely to be fixed. (For example, Xcompmgr has shown a problem with ''tint2 0.9'': systray icons have a tendency to become corrupted.)<br />
<br />
[[Cairo Compmgr]] is a versatile compositing window manager that uses [http://en.wikipedia.org/wiki/Cairo_(software) Cairo] for rendering. It is usually the better choice.<br />
<br />
=== Panels, trays, pagers ===<br />
<br />
Refer to the supplemental [[Openbox_Themes_and_Apps#Panels.2C_trays.2C_and_pagers|Openbox Themes and Apps]] to learn about these GUI embellishments for Openbox.<br />
<br />
=== File managers ===<br />
<br />
Two popular lightweight file managers are:<br />
* [[Thunar]]. Thunar supports auto-mount features and other plugins. <br />
* [http://rox.sourceforge.net ROX] (ROX provides desktop icons)<br />
# pacman -S thunar<br />
# pacman -S rox<br />
* [http://pcmanfm.sourceforge.net PCManFM]<br />
# pacman -S pcmanfm # PcManFM package also provides desktop icons.<br />
# pacman -S ntfs-3g # Allows PCManFM to access NTFS drives.<br />
<br />
More information is found at [[Openbox_Themes_and_Apps#File_managers|Openbox Themes and Apps]]. The supplemental article has further information about application launchers such as [http://sourceforge.net/projects/gmrun gmrun], clipboard managers, volume mixers, and more.<br />
<br />
== Tips and tricks ==<br />
<br />
=== File associations ===<br />
Because Openbox and the applications you use with it are not well-integrated you might run into the issues with your browser. Your browser may not know which program it is supposed to use for certain types of files.<br />
<br />
A package in the AUR called [http://aur.archlinux.org/packages.php?ID=23170 gnome-defaults-list] contains a list of file-types and programs specific to the Gnome desktop. The list is installed to {{Filename|/etc/gnome/defaults.list.}}<br />
<br />
Open this file with your text-editor. Now you can replace a given application with the name of the program of your choosing. For example, totem <=> vlc or eog <=> mirage. Save the file to {{Filename|~/.local/share/applications/defaults.list}}.<br />
<br />
Another way of setting file associations is to install package ''perl-file-mimeinfo'' from the repository and invoke '''mimeopen''' like this:<br />
mimeopen -d /path/to/file<br />
You are asked which application to use when opening /path/to/file:<br />
Please choose a default application for files of type text/plain<br />
1) notepad (wine-extension-txt)<br />
2) Leafpad (leafpad)<br />
3) OpenOffice.org Writer (writer)<br />
4) gVim (gvim)<br />
5) Other...<br />
Your answer becomes the default handler for that type of file. Mimeopen is installed as {{Filename|/usr/bin/perlbin/vendor/mimetype}}.<br />
<br />
=== Copy and paste ===<br />
<br />
From a terminal '''Ctrl+Insert''' for copy and '''Shift+Insert''' for paste.<br />
<br />
Also '''Ctrl+Shift+C''' for copy and '''mouse middle-click''' for paste (in terminals).<br />
<br />
Other applications most likely use the conventional keyboard shortcuts for copy and paste.<br />
<br />
=== Window transparency ===<br />
<br />
The program transset-df (virtually the same as ''transset'') is installed with pacman -S transset-df. With transset-df you can enable window-transparency on-the-fly.<br />
<br />
For instance by placing the following in {{Filename|~/.config/openbox/rc.xml}} you can have your mouse adjust window transparency by scrolling while hovering over the title bar (it is in the <mouse> section):<br />
<br />
<context name="Titlebar"><br />
. . .<br />
<mousebind button="Up" action="Click"><br />
<action name= "Execute" ><br />
<execute>transset-df -p .2 --inc </execute><br />
</action><br />
</mousebind><br />
<mousebind button="Down" action="Click"><br />
<action name= "Execute" ><br />
<execute>transset-df -p .2 --dec </execute><br />
</action><br />
</mousebind><br />
. . .<br />
</context><br />
It appears to work only when no additional actions are defined within the action group.<br />
<br />
=== Xprop values for applications ===<br />
If you use per-application settings frequently, you might find this bash alias handy:<br />
<br />
alias xp='xprop | grep "WM_WINDOW_ROLE\|WM_CLASS" && echo "WM_CLASS(STRING) = \"NAME\", \"CLASS\""'<br />
<br />
To use, run '''{{Codeline|xp}}''' and click on the running program that you'd like to define with per-app settings. The result displays only the info that Openbox requires, namely the WM_WINDOW_ROLE and WM_CLASS (name and class) values:<br />
<br />
[thayer@dublin:~] $ xp<br />
WM_WINDOW_ROLE(STRING) = "roster"<br />
WM_CLASS(STRING) = "gajim.py", "Gajim.py"<br />
WM_CLASS(STRING) = "NAME", "CLASS"<br />
<br />
==== Xprop for Firefox ====<br />
<br />
For whatever reason, Firefox and like-minded equivalents ignore application rules (e.g. <desktop>) unless {{Codeline|class&#61;"Firefox*"}} is used. This applies irrespective of whatever values xprop may report for the program's WM_CLASS.<br />
<br />
=== Linking the menu to a button ===<br />
<br />
Some people want to link the Openbox menu (or any menu) to an object. This is useful for creating a panel button to pop up a menu. Although Openbox does not provide this, a program called '''xdotool''' simulates a keypress. Openbox can be configured to bind that keypress to the ''ShowMenu'' action.<br />
<br />
Package [http://aur.archlinux.org/packages.php?do_Details=1&ID=14789&O=0&L=0&C=0&K=xdotool&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd xdotool] is available in the AUR. After installing ''xdotool'', add the following to the <keyboard> section of your '''{{Filename|rc.xml}}''':<br />
<keybind key="A-C-q"><br />
<action name="ShowMenu"><br />
<menu>root-menu</menu><br />
</action><br />
</keybind><br />
Restart/reconfigure Openbox. The following command summons a menu at your cursor position. The command may given as-is, linked to an object, or placed in a script.<br />
$ xdotool key ctrl+alt+q<br />
<br />
Of course, change the key shortcut to your liking. Here's a snippet from a '''tint2''' (a taskbar-like panel) configuration file which pops up a menu when the clock area is clicked. Each key combination is set to open a menu within openbox's '''{{Filename|rc.xml}}''' configuration file. The right‑click menu is different from the left‑click menu:<br />
clock_rclick_command = xdotool key --clearmodifiers "ctrl+XF86PowerOff"<br />
clock_lclick_command = xdotool key --clearmodifiers "alt+XF86PowerOff"<br />
<br />
=== Urxvt in the background ===<br />
<br />
With Openbox, running a terminal as desktop background is easy. You won't need '''devilspie''' here.<br />
<br />
First you must enable transparency, open your {{Filename|.Xdefaults}} file (if it doesn't exist yet, create it in your home folder).<br />
URxvt*transparent:true<br />
URxvt*scrollBar:false<br />
URxvt*geometry:124x24 #I don't use the whole screen, if you want a full screen term don't bother with this and see below.<br />
URxvt*borderLess:true<br />
URxvt*foreground:Black #Font color. My wallpaper is White, you may wish to change this to White.<br />
<br />
Then edit your {{Filename|.config/openbox/rc.xml}} file:<br />
<application name="URxvt"><br />
<decor>no</decor><br />
<focus>yes</focus><br />
<position><br />
<x>center</x><br />
<y>20</y><br />
</position><br />
<layer>below</layer><br />
<desktop>all</desktop><br />
<maximized>true</maximized> #Only if you want a full size terminal.<br />
</application><br />
<br />
The ''magic'' comes from the {{Codeline|<layer>below</layer>}} line, which place the application under all others. Here Urxvt is displayed on all desktops, change it to your convenience.<br />
<br />
Note: Instead of using <application name="URxvt">, you can use another name ("URxvt-bg" for example), and use the -name option when starting uxrvt. That way, only the urxvt terminals which you choose to name URxvt-bg would be captured and modified by the application rule in rc.xml. For example: urxvt -name URxvt-bg (case sensitive)<br />
<br />
====ToggleShowDesktop exception====<br />
<br />
Above method still minimizes Urxvt when using the ToggleShowDesktop command. A method for avoiding this is explained in this [https://bbs.archlinux.org/viewtopic.php?pid=865844#p865844 forum post]. This involves editing Urxvt's source code.<br />
<br />
=== Keyboard volume control ===<br />
<br />
If you use ALSA for sound, you can use the amixer program to adjust the volume of sound. You can use Openbox's keybindings to act like multimedia keys. (Alternatively, you can probably find out the names of your real multimedia keys and map them.) For example, in the <keyboard> section of rc.xml:<br />
<br />
<keybind key="W-Up"><br />
<action name="Execute"><br />
<command>amixer set Master 5%+</command><br />
</action><br />
</keybind><br />
<br />
This binds Windows key + Up arrow to increase your master ALSA volume by 5%. Corresponding binding for volume down:<br />
<br />
<keybind key="W-Down"><br />
<action name="Execute"><br />
<command>amixer set Master 5%-</command><br />
</action><br />
</keybind><br />
<br />
As another example you can also use the XF86Audio keybindings:<br />
<br />
<keybind key="XF86AudioRaiseVolume"><br />
<action name="Execute"><br />
<command>amixer set Master 5%+ unmute</command><br />
</action><br />
</keybind><br />
<keybind key="XF86AudioLowerVolume"><br />
<action name="Execute"><br />
<command>amixer set Master 5%- unmute</command><br />
</action><br />
</keybind><br />
<keybind key="XF86AudioMute"><br />
<action name="Execute"><br />
<command>amixer set Master toggle</command><br />
</action><br />
</keybind><br />
<br />
The above example should work for the majority of multimedia keyboards. It should enable to raise, lower and mute the Master control of your audio device by using the respective multimedia keyboard keys. Notice also that in this example:<br />
<br />
* The "Mute" key should unmute the Master control if it is already in mute mode.<br />
* The "Raise" and "Lower" keys should unmute the Master control if it is in mute mode.<br />
<br />
== Resources ==<br />
<br />
* [http://openbox.org/ Openbox Website] &ndash; The official website<br />
* [http://planetob.openmonkey.com/ Planet Openbox] &ndash; Openbox news portal<br />
* [http://www.box-look.org/ Box-Look.org] &ndash; A good resource for themes and related artwork<br />
* [https://bbs.archlinux.org/viewtopic.php?id=93126 Openbox Hacks and Configs Thread] @ Arch Linux Forums<br />
* [https://bbs.archlinux.org/viewtopic.php?id=45692 Openbox Screenshots Thread] @ Arch Linux Forums<br />
<!-- vim: set ft=Wikipedia: --></div>Taylorchuhttps://wiki.archlinux.org/index.php?title=PCManFM&diff=140721PCManFM2011-05-09T21:48:04Z<p>Taylorchu: /* Trashcan not working? */</p>
<hr />
<div>[[Category: Utilities (English)]]<br />
[[Category: File systems (English)]]<br />
[[Category: File managers (English)]]<br />
{{i18n|PCManFM}}<br />
[[pl:PCManFM]]<br />
<br />
'''PCManFM''' is "an extremly fast, lightweight, yet feature-rich file manager with tabbed browsing". Source: [http://pcmanfm.sourceforge.net/ PCManFM on sourceforge]. PCManFM is the default file manager of the [[LXDE]] (Lightweight X11 Desktop Environment).<br />
<br />
==Installation==<br />
Run the following command to install:<br />
# pacman -S pcmanfm<br />
<br />
You will also require gamin (a replacement for fam, which required a daemon) to pick up events such as file and directories changes:<br />
<br />
# pacman -S gamin<br />
<br />
<br />
==Volume handling==<br />
PCManFM is able to mount and unmount devices, both manually and automatically. This feature is offered as an alternative to CLI tools such as [[pmount]]. There are various 'up-to-date' versions of PCManFM (see below), and different volume handling strategies can be chosen.<br />
<br />
===Mounting with udisks===<br />
The current release of PCManFM is able to handle volumes through udisks. If you want to use this feature, make sure the D-Bus daemon is installed and running. See the [[D-Bus]] page for details. Note that you will most likely need to start dbus-launch from your .xinitrc or the autostart script of your window manager. Instructions how to do so can be found on the [[D-Bus]] page or the page for your window manager.<br />
<br />
===Mounting with gvfs===<br />
If you prefer to use the Gnome Virtual FileSystem, the procedure is the same as before but requires additional packages:<br />
<br />
* [[gvfs]] (and dependencies);<br />
* (optional) gvfs-smb, gvfs-obexftp, gvfs-afc, etc. in order to support additional features.<br />
<br />
Note : You must have a /media folder.<br />
<br />
===Mounting as normal user===<br />
To be able to mount devices like removeable USB harddisks, flashdrives or DVDs as a normal user, the PolicyKit toolkit needs to be configured accordingly. The configuration files can be found in the subdirectories of {{Filename|/etc/polkit-1}}. The rest of this section will show you how to configure PolicyKit to allow users belonging to the "storage" group to mount and umount temporary devices.<br />
{{ Note | Many users experience trouble mounting with lightweight windows manager and [[SLiM]], adding '''''ck-launch-session dbus-launch''''' after exec in login_cmd option usually help}}<br />
{{Note | Currently PolicyKit is configured to allow (un)mounting for users in group ''storage'' by default. Therefore this step is not necessary}}<br />
First off, start a terminal and make yourself root:<br />
su<br />
Then switch to the right directory:<br />
cd /etc/polkit-1/localauthority/50-local.d<br />
Fire up your favourite text editor and create a file:<br />
nano 55-myconf.pkla<br />
Note that you can name the file anything you want, as long as the name ends with .pkla. Type in or copy/paste the following lines:<br />
[Storage Permissions]<br />
Identity=unix-group:storage<br />
Action=org.freedesktop.udisks.filesystem-mount;org.freedesktop.udisks.drive-eject;org.freedesktop.udisks.drive-detach;org.freedesktop.udisks.luks-unlock;org.freedesktop.udisks.inhibit-polling;org.freedesktop.udisks.drive-set-spindown<br />
ResultAny=yes<br />
ResultActive=yes<br />
ResultInactive=no<br />
Do not forget to save the file. PolicyKit will notice the changes in the file and update its behaviour without any action from you. Last thing to do is making every user that should have the ability to mount drives a member of the storage group:<br />
usermod -a -G storage USERNAME<br />
Get back to your existence as a humble user and enjoy your ability to mount your USB Drives:<br />
exit<br />
<br />
If you want to grant other permissions instead of granting them to members of the storage group, or simply want to know what you were just doing, check out the manpage:<br />
man pklocalauthority<br />
<br />
==Tips & troubleshooting==<br />
===No "Applications"===<br />
# pacman -S gnome-menus<br />
<br />
===Trashcan not working?===<br />
# pacman -S gvfs consolekit<br />
Make sure that you also add "ck-lauch-session dbus-launch"(in this order) to .xinitrc. gvfs requires many gnome dependencies.<br />
<br />
===Not able to mount USB or other devices?===<br />
# pacman -S consolekit<br />
Make sure that you also add "ck-lauch-session dbus-launch"(in this order) to .xinitrc.<br />
<br />
<br />
===No icons?===<br />
If you are using a window manager over a desktop environment and notice you have no icons for folders and files, install an icon theme:<br />
# pacman -S tango-icon-theme<br />
<br />
Then edit {{Filename|~/.gtkrc-2.0}} '''or''' {{Filename|/etc/gtk-2.0/gtkrc}} and add the following line:<br />
gtk-icon-theme-name = "Tango"<br />
<br />
===NTFS Read/Write Support===<br />
Install ntfs-3g:<br />
# pacman -S ntfs-3g<br />
<br />
===gnome-open opens "Find" dialog instead of the directory===<br />
Remove or rename the file {{Filename|/usr/share/applications/pcmanfm-find.desktop}}. If you're running pcmanfm-mod from AUR, remove or rename the file {{Filename|/usr/share/applications/pcmanfm-mod-find.desktop}}.<br />
<br />
==Available Versions==<br />
There are several versions of PCManFM currently available:<br />
<br />
===PCManFM2===<br />
This is the package in Arch's extra repository as "pcmanfm". The current git test version of it is available in the AUR as [http://aur.archlinux.org/packages.php?ID=33601 pcmanfm-git]. More information is available on the [http://forum.lxde.org/viewforum.php?f=22 LXDE Forum].<br />
<br />
===PCManFM 0.5.2===<br />
The legacy PCManFM (version 0.5.2, which is currently "pcmanfm-gtk220" in the AUR repository) is frozen and is no longer being maintained by the original author. This version uses HAL for mounting. More information is available on the [http://pcmanfm.sourceforge.net/intro.html project page].<br />
<br />
===PCManFM-Mod===<br />
PCManFM-Mod adds user-definable commands, other features, and bugfixes to the legacy version of the PCManFM file manager v0.5.2. This version builds and installs as "pcmanfm-mod" and will run independently of other versions of PCManFM you have installed on your system. This legacy version is still desired by some due to more stability than the newer 0.9.x rewrite in progress, less Gnome dependencies, and the use of HAL rather than gnome-vfs. PCManFM-Mod is available in the [http://aur.archlinux.org/packages.php?ID=34819 AUR as pcmanfm-mod] and as [http://aur.archlinux.org/packages.php?ID=39547 pcmanfm-mod-prov] (latter provides pcmanfm). More information is available at [http://igurublog.wordpress.com/downloads/mod-pcmanfm/ IgnorantGuru's Blog].</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=PCManFM&diff=140720PCManFM2011-05-09T21:45:21Z<p>Taylorchu: /* Tips & troubleshooting */</p>
<hr />
<div>[[Category: Utilities (English)]]<br />
[[Category: File systems (English)]]<br />
[[Category: File managers (English)]]<br />
{{i18n|PCManFM}}<br />
[[pl:PCManFM]]<br />
<br />
'''PCManFM''' is "an extremly fast, lightweight, yet feature-rich file manager with tabbed browsing". Source: [http://pcmanfm.sourceforge.net/ PCManFM on sourceforge]. PCManFM is the default file manager of the [[LXDE]] (Lightweight X11 Desktop Environment).<br />
<br />
==Installation==<br />
Run the following command to install:<br />
# pacman -S pcmanfm<br />
<br />
You will also require gamin (a replacement for fam, which required a daemon) to pick up events such as file and directories changes:<br />
<br />
# pacman -S gamin<br />
<br />
<br />
==Volume handling==<br />
PCManFM is able to mount and unmount devices, both manually and automatically. This feature is offered as an alternative to CLI tools such as [[pmount]]. There are various 'up-to-date' versions of PCManFM (see below), and different volume handling strategies can be chosen.<br />
<br />
===Mounting with udisks===<br />
The current release of PCManFM is able to handle volumes through udisks. If you want to use this feature, make sure the D-Bus daemon is installed and running. See the [[D-Bus]] page for details. Note that you will most likely need to start dbus-launch from your .xinitrc or the autostart script of your window manager. Instructions how to do so can be found on the [[D-Bus]] page or the page for your window manager.<br />
<br />
===Mounting with gvfs===<br />
If you prefer to use the Gnome Virtual FileSystem, the procedure is the same as before but requires additional packages:<br />
<br />
* [[gvfs]] (and dependencies);<br />
* (optional) gvfs-smb, gvfs-obexftp, gvfs-afc, etc. in order to support additional features.<br />
<br />
Note : You must have a /media folder.<br />
<br />
===Mounting as normal user===<br />
To be able to mount devices like removeable USB harddisks, flashdrives or DVDs as a normal user, the PolicyKit toolkit needs to be configured accordingly. The configuration files can be found in the subdirectories of {{Filename|/etc/polkit-1}}. The rest of this section will show you how to configure PolicyKit to allow users belonging to the "storage" group to mount and umount temporary devices.<br />
{{ Note | Many users experience trouble mounting with lightweight windows manager and [[SLiM]], adding '''''ck-launch-session dbus-launch''''' after exec in login_cmd option usually help}}<br />
{{Note | Currently PolicyKit is configured to allow (un)mounting for users in group ''storage'' by default. Therefore this step is not necessary}}<br />
First off, start a terminal and make yourself root:<br />
su<br />
Then switch to the right directory:<br />
cd /etc/polkit-1/localauthority/50-local.d<br />
Fire up your favourite text editor and create a file:<br />
nano 55-myconf.pkla<br />
Note that you can name the file anything you want, as long as the name ends with .pkla. Type in or copy/paste the following lines:<br />
[Storage Permissions]<br />
Identity=unix-group:storage<br />
Action=org.freedesktop.udisks.filesystem-mount;org.freedesktop.udisks.drive-eject;org.freedesktop.udisks.drive-detach;org.freedesktop.udisks.luks-unlock;org.freedesktop.udisks.inhibit-polling;org.freedesktop.udisks.drive-set-spindown<br />
ResultAny=yes<br />
ResultActive=yes<br />
ResultInactive=no<br />
Do not forget to save the file. PolicyKit will notice the changes in the file and update its behaviour without any action from you. Last thing to do is making every user that should have the ability to mount drives a member of the storage group:<br />
usermod -a -G storage USERNAME<br />
Get back to your existence as a humble user and enjoy your ability to mount your USB Drives:<br />
exit<br />
<br />
If you want to grant other permissions instead of granting them to members of the storage group, or simply want to know what you were just doing, check out the manpage:<br />
man pklocalauthority<br />
<br />
==Tips & troubleshooting==<br />
===No "Applications"===<br />
# pacman -S gnome-menus<br />
<br />
===Trashcan not working?===<br />
# pacman -S gvfs consolekit<br />
Make sure that you also add "ck-lauch-session dbus-launch"(in this order) to .xinitrc.<br />
<br />
===Not able to mount USB or other devices?===<br />
# pacman -S consolekit<br />
Make sure that you also add "ck-lauch-session dbus-launch"(in this order) to .xinitrc.<br />
<br />
<br />
===No icons?===<br />
If you are using a window manager over a desktop environment and notice you have no icons for folders and files, install an icon theme:<br />
# pacman -S tango-icon-theme<br />
<br />
Then edit {{Filename|~/.gtkrc-2.0}} '''or''' {{Filename|/etc/gtk-2.0/gtkrc}} and add the following line:<br />
gtk-icon-theme-name = "Tango"<br />
<br />
===NTFS Read/Write Support===<br />
Install ntfs-3g:<br />
# pacman -S ntfs-3g<br />
<br />
===gnome-open opens "Find" dialog instead of the directory===<br />
Remove or rename the file {{Filename|/usr/share/applications/pcmanfm-find.desktop}}. If you're running pcmanfm-mod from AUR, remove or rename the file {{Filename|/usr/share/applications/pcmanfm-mod-find.desktop}}.<br />
<br />
==Available Versions==<br />
There are several versions of PCManFM currently available:<br />
<br />
===PCManFM2===<br />
This is the package in Arch's extra repository as "pcmanfm". The current git test version of it is available in the AUR as [http://aur.archlinux.org/packages.php?ID=33601 pcmanfm-git]. More information is available on the [http://forum.lxde.org/viewforum.php?f=22 LXDE Forum].<br />
<br />
===PCManFM 0.5.2===<br />
The legacy PCManFM (version 0.5.2, which is currently "pcmanfm-gtk220" in the AUR repository) is frozen and is no longer being maintained by the original author. This version uses HAL for mounting. More information is available on the [http://pcmanfm.sourceforge.net/intro.html project page].<br />
<br />
===PCManFM-Mod===<br />
PCManFM-Mod adds user-definable commands, other features, and bugfixes to the legacy version of the PCManFM file manager v0.5.2. This version builds and installs as "pcmanfm-mod" and will run independently of other versions of PCManFM you have installed on your system. This legacy version is still desired by some due to more stability than the newer 0.9.x rewrite in progress, less Gnome dependencies, and the use of HAL rather than gnome-vfs. PCManFM-Mod is available in the [http://aur.archlinux.org/packages.php?ID=34819 AUR as pcmanfm-mod] and as [http://aur.archlinux.org/packages.php?ID=39547 pcmanfm-mod-prov] (latter provides pcmanfm). More information is available at [http://igurublog.wordpress.com/downloads/mod-pcmanfm/ IgnorantGuru's Blog].</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Xorg&diff=138088Xorg2011-04-23T23:17:20Z<p>Taylorchu: /* Installing */ some packages are not required</p>
<hr />
<div>[[Category:X Server (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|Xorg}}<br />
[[pl:Xorg]]<br />
[[fr:Xorg]]<br />
<br />
{{Article summary start}}<br />
{{Article summary text|An all-inclusive overview about installing and managing Xorg}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|ATI}}<br />
{{Article summary wiki|Intel}}<br />
{{Article summary wiki|NVIDIA}}<br />
{{Article summary end}}<br />
<br />
'''Xorg''' is the public, open-source implementation of the X window system version 11. Since Xorg is the most popular choice among Linux users, its ubiquity has led to making it an ever-present requisite for GUI applications, resulting in massive adoption from most distributions. See the [[Wikipedia:X.Org Server|Xorg]] Wikipedia article or visit the [http://www.x.org/wiki/ Xorg website] for more details.<br />
<br />
==Installing==<br />
<br />
First, fully update your system<br />
# pacman -Syu<br />
<br />
Then you can install the Xorg base packages:<br />
# pacman -S xorg-server xorg-xinit<br />
<br />
For basic Xorg functionality you may also want to install some other packages:<br />
# pacman -S xorg-utils xorg-server-utils xorg-twm xorg-xclock xterm<br />
<br />
Since v.1.8, Xorg-server '''doesn't need HAL for hardware access'''. Udev can detect your hardware itself.<br />
<br />
You can remove HAL from your startup daemon in {{filename|/etc/rc.conf}} without problem if you don't have any other app installed in your system that requires HAL to be running.<br />
Moreover, the settings that were located in the {{filename|/etc/X11/xorg.conf}} file, can be found now in the files located in the {{filename|/etc/X11/xorg.conf.d/}} directory.<br />
<br />
Udev should be capable of detecting your hardware without problems and evdev (xf86-input-evdev) is the modern, hotplugging input driver for almost all devices so in most cases, installing input drivers is not needed.<br />
<br />
If evdev doesn't support your device, install the needed driver from the '''xorg-input-drivers''' group.<br />
<br />
Xorg-server can be initiated by the '''startx''' command. You should only use it in case you have properly edited the ~/.'''xinitrc''' file.<br />
<br />
{{Note|In case you are using a Desktop Environment (GNOME, KDE etc), you are encouraged to use a DM (KDM, GDM etc), which will manage the, possible, DE specific apps and libs which should be preloaded.}}<br />
<br />
==Configuring==<br />
<br />
Configuration files are located in {{filename|/etc/X11/xorg.conf.d/}}.<br />
<br />
You should have {{filename|10-evdev.conf}} which manages the keyboard, the mouse, the touchpad and the touchscreen.<br />
You are free to create new config files, but they must start with '''XX-''' (where XX is a number) and have a '''.conf''' suffix (10 read before 20 for example).<br />
<br />
===Touchpad/Synaptics===<br />
<br />
If you have a laptop, you need to install the touchpad driver.<br />
# pacman -S xf86-input-synaptics<br />
<br />
After installation, you can find {{filename|10-synaptics.conf}} in the {{filename|/etc/X11/xorg.conf.d}} directory. It is safe to comment out/delete the "InputClass" line regarding the touchpad in {{filename|10-evdev.conf}}.<br />
<br />
===Graphics card and driver===<br />
The default graphics driver is Vesa (xf86-video-vesa), which handles a large number of chipsets but does not include any 2d or 3d acceleration. To enable graphics acceleration, you will need to install and use the driver specific to your graphics card.<br />
<br />
First, identify your card:<br />
$ lspci | grep VGA<br />
<br />
Then, install an appropriate driver. You can ''search'' for these packages with the following command:<br />
# pacman -Ss xf86-video<br />
<br />
Common drivers (open source):<br />
*nvidia: xf86-video-nouveau (see [[Nouveau]])<br />
*intel: xf86-video-intel (see [[Intel]])<br />
*ati: xf86-video-ati (see [[ATI]])<br />
<!--add more drivers with links to wiki pages here--><br />
<br />
====Proprietary drivers====<br />
<br />
Xorg should run smoothly without closed source drivers, which are typically needed only for advanced features such as fast 3D-accelerated rendering for games, dual-screen setups, and TV-out. See [[NVIDIA]] and [[ATI]].<br />
<br />
=====Nvidia=====<br />
<br />
During the installation of the proprietary [[NVIDIA]] driver, a config file ('''20-nvidia.conf''') will be installed in the {{filename|/etc/X11/xorg.conf.d}} directory. It allows Xorg to use nvidia's driver at Xorg start.<br />
<br />
===Monitor settings===<br />
<br />
==== Getting started ====<br />
<br />
{{Note|This step is OPTIONAL and shouldn't be done unless you know what you are doing.}}<br />
{{Note|This step is '''NOT OPTIONAL''' if using dual monitors or the nouveau driver. See [[Nouveau#Configuration]].}}<br />
<br />
First, create a new config file, for example, {{filename|/etc/X11/xorg.conf.d/10-monitor.conf}}.<br />
# nano /etc/X11/xorg.conf.d/10-monitor.conf<br />
Copy and paste the following code.<br />
<br />
<pre><br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Device0"<br />
Driver "vesa" #Choose the driver used for this monitor<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0" #Collapse Monitor and Device section to Screen section<br />
Device "Device0"<br />
Monitor "Monitor0"<br />
DefaultDepth 16 #Choose the depth (16||24)<br />
SubSection "Display"<br />
Depth 16<br />
Modes "1024x768_75.00" #Choose the resolution<br />
EndSubSection<br />
EndSection<br />
</pre><br />
<br />
====Multiple monitors/Dual screen====<br />
<br />
=====Nvidia=====<br />
To activate dual screen support, you just need to edit the {{filename|10-monitor.conf}} file which you made before.<br />
<br />
Per each physical monitor, add one Monitor, Device, and Screen Section entry, and then a ServerLayout section to manage it. Be advised that when Xinerama is enabled, the Nvidia proprietary driver automatically disables compositing. If you desire compositing, you should comment the Xinerama line in "ServerLayout" out and use Twinview (see below) instead.<br />
<br />
<pre><br />
Section "ServerLayout"<br />
Identifier "DualSreen"<br />
Screen 0 "Screen0"<br />
Screen 1 "Screen1" RightOf "Screen0" #Screen1 at the right of Screen0<br />
Option "Xinerama" "1" #To move windows between screens<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
Option "Enable" "true"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor1"<br />
Option "Enable" "true"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Device0"<br />
Driver "nvidia"<br />
Screen 0<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Device1"<br />
Driver "nvidia"<br />
Screen 1<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Device0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
Option "TwinView" "0"<br />
SubSection "Display"<br />
Depth 24<br />
Modes "1280x800_75.00"<br />
EndSubSection<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen1"<br />
Device "Device1"<br />
Monitor "Monitor1"<br />
DefaultDepth 24<br />
Option "TwinView" "0"<br />
SubSection "Display"<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
</pre><br />
<br />
======TwinView======<br />
You want only one big screen instead of two. Set the TwinView argument to 1. This option should be used instead of Xinerama (see above), if you desire compositing.<br />
Option "TwinView" "1"<br />
<br />
======Using Nvidia Settings======<br />
You can also use the Nvidia-settings tool, with this method you will use the proprietary software Nvidia provides with their drivers. Simply open the settings as Root, then configure how you wish, and then save the configuration to /etc/X11/xorg.conf.d/10-monitor.conf .<br />
<br />
=====More than one graphic card=====<br />
You must define the good driver to use and put the ID bus of your graphic cards.<br />
<pre><br />
Section "Device"<br />
Identifier "Screen0"<br />
Driver "nouveau"<br />
BusID "PCI:0:12:0"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Screen1"<br />
Driver "radeon"<br />
BusID "PCI:1:0:0"<br />
EndSection<br />
</pre><br />
<br />
To get your ID bus :<br />
$ lspci | grep VGA<br />
01:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce 9600M GT] (rev a1)<br />
<br />
The ID bus here is 1:0:0.<br />
<br />
====Display Size and DPI ====<br />
<br />
'''Q:''' How does the Xorg server calculate DPI? <br /><br />
'''A:''' The DPI of the X server is determined in the following manner:<br />
<br />
# The -dpi command line option has highest priority.<br />
# If this is not used, the DisplaySize setting in the X config file is used to derive the DPI, given the screen resolution.<br />
# If no DisplaySize is given, the monitor size values from DDC are used to derive the DPI, given the screen resolution.<br />
# If DDC does not specify a size, 75 DPI is used by default.<br />
<br />
In order to get correct dots per inch (DPI) set, the display size must be recognized or set. Having the correct DPI is especially necessary where fine detail is required (like font rendering). Previously, manufacturers tried to create a standard for 96 DPI (a 10.3" diagonal monitor would be 800x600, a 13.2" monitor 1024x768). These days, screen DPIs vary and may not be equal horizontally and vertically. For example, a 19" widescreen LCD at 1440x900 may have a DPI of 89x87. To be able to set the DPI, the Xorg server attempts to auto-detect your monitor's physical screen size through the graphic card with [http://en.wikipedia.org/wiki/Display_Data_Channel DDC]. When the Xorg server knows the physical screen size, it will be able to set the correct DPI depending on resolution size.<br />
<br />
To see if your display size and DPI are detected/calculated correctly:<br />
<br />
$ xdpyinfo | grep dimensions<br />
$ xdpyinfo | grep "dots per inch"<br />
<br />
Check that the dimensions match your display size. If the Xorg server is not able to correctly calculate the screen size, it will default to 75x75 DPI and you will have to calculate it yourself.<br />
<br />
If you have specifications on the physical size of the screen, they can be entered in the Xorg configuration file so that the proper DPI is calculated:<br />
<br />
<pre><br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
DisplaySize 286 179 # In millimeters<br />
EndSection<br />
</pre><br />
<br />
If you only want to enter the specification of your monitor WITHOUT creating a full xorg.conf instead, first create a new config file, for example, {{filename|/etc/X11/xorg.conf.d/90-monitor.conf}}.<br />
# nano /etc/X11/xorg.conf.d/10-monitor.conf<br />
Copy and paste the following code:<br />
<br />
<pre><br />
Section "Monitor"<br />
Identifier "<default monitor>"<br />
DisplaySize 286 179 # In millimeters<br />
EndSection<br />
</pre><br />
<br />
If you do not have specifications for physical screen width and height (most specifications these days only list by diagonal size), you can use the monitor's native resolution (or aspect ratio) and diagonal length to calculate the horizontal and vertical physical dimensions. Using the Pythagorean theorem on a 13.3" diagonal length screen with a 1280x800 native resolution (or 16:10 aspect ratio):<br />
<br />
echo 'scale=5;sqrt(1280^2+800^2)' | bc # 1509.43698<br />
<br />
This will give the pixel diagonal length and with this value you can discover the physical horizontal and vertical lengths (and convert them to millimeters):<br />
<br />
<pre><br />
echo 'scale=5;(13.3/1509)*1280*25.4' | bc # 286.43072<br />
echo 'scale=5;(13.3/1509)*800*25.4' | bc # 179.01920<br />
</pre><br />
<br />
{{Note|This calculation works for most monitor sizes; however, there is the seldom monitor that may compress aspect ratio (e.g 16:10 aspect resolution to a 16:9 monitor). If this is the case, you should measure your screen size manually.}}<br />
<br />
DPI can be set manually if you only plan to use one resolution:<br />
<br />
<pre><br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
Option "DPI" "96 x 96"<br />
EndSection<br />
</pre><br />
<br />
If, for some odd reason, the nvidia drivers don't set the correct DPI, you can turn off auto-detection:<br />
<br />
Option "UseEdidDpi" "false"<br />
<br />
For RandR compliant drivers, you can set it by:<br />
<br />
xrandr --dpi 96<br />
<br />
See [[Execute commands after X start]] to make it permanent.<br />
<br />
====DPMS====<br />
<br />
DPMS (Display Power Management Signaling) is a technology that allows power saving behaviour of monitors when the computer is not in use. This will allow you to have your monitors automatically go into standby after a predefined period of time. See: [[DPMS]]<br />
<br />
===Disabling Input Hot-plugging===<br />
Since version''' 1.8''' Xorg-server uses udev for device detection. The following will disable the use of udev.<br />
<br />
Section "ServerFlags"<br />
Option "AutoAddDevices" "False"<br />
EndSection<br />
{{Warning|This will disable Xorg hot-plugging for '''all''' input devices and revert to the same behavior as xorg-server 1.4. It is much more convenient to let udev configure your devices. '''Therefore, disabling hot-plugging is not recommended!'''}}<br />
<br />
===InputClasses ===<br />
'''Taken from: https://fedoraproject.org/wiki/Input_device_configuration'''<br />
<br />
InputClasses are a new type of configuration section that does not apply to a single device but rather to a class of devices, including hotplugged devices. An InputClass section's scope is limited by the ''matches'' specified &ndash; to apply to an input device, all matches must apply to a device. An example InputClass section is provided below:<br />
<br />
<pre><br />
Section "InputClass"<br />
Identifier "touchpad catchall"<br />
MatchIsTouchpad "on"<br />
Driver "synaptics"<br />
EndSection<br />
</pre><br />
<br />
The next snippet might also be helpful:<br />
<pre><br />
Section "InputClass"<br />
Identifier "evdev touchpad catchall"<br />
MatchIsTouchpad "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Driver "evdev"<br />
EndSection<br />
</pre><br />
<br />
If this snippet is present in the {{Filename|xorg.conf}} or xorg.conf.d, any touchpad present in the system is assigned the synaptics driver. Note that due to precedence order (alphanumeric sorting of xorg.conf.d snippets) the Driver setting overwrites previously set driver options &ndash; the more generic the class, the earlier it should be listed. The default snippet shipped with the xorg-x11-drv-Xorg package is {{Filename|00-evdev.conf}} and applies the evdev driver to all input devices.<br />
<br />
The match options specify which devices a section may apply to. To match a device, all match lines must apply. The following match lines are supported (with examples):<br />
* {{Codeline|MatchIsPointer}}, {{Codeline|MatchIsKeyboard}}, {{Codeline|MatchIsTouchpad}}, {{Codeline|MatchIsTouchscreen}}, {{Codeline|MatchIsJoystick}} &ndash; boolean options to apply to a group of devices.<br />
* {{Codeline|MatchProduct "foo&#124;bar"}}: match any device with a product name containing either "foo" or "bar"<br />
* {{Codeline|MatchVendor "foo&#124;bar&#124;baz"}}: match any device with a vendor string containing either "foo", "bar", or "baz"<br />
* {{Codeline|MatchDevicePath "/dev/input/event*"}}: match any device with a device path matching the given patch (see fnmatch(3) for the allowed pattern)<br />
* {{Codeline|MatchTag "foo&#124;bar"}}: match any device with a tag of either "foo" or "bar". Tags may be assigned by the config backend &ndash; udev in our case &ndash; to label devices that need quirks or special configuration.<br />
<br />
An example section for user-specific configuration is:<br />
<br />
<pre><br />
Section "InputClass"<br />
Identifier "lasermouse slowdown"<br />
MatchIsPointer "on"<br />
MatchProduct "Lasermouse"<br />
MatchVendor "LaserMouse Inc."<br />
Option "ConstantDeceleration" 20<br />
EndSection<br />
</pre><br />
<br />
This section would match a pointer device containing "Lasermouse" from "Lasermouse Inc." and apply a constant deceleration of 20 on this device &ndash; slowing it down by factor 20.<br />
<br />
Some devices may get picked up by the X server when they really shouldn't be. These devices can be configured to be ignored:<br />
<br />
<pre><br />
Section "InputClass"<br />
Identifier "no need for accelerometers in X"<br />
MatchProduct "accelerometer"<br />
Option "Ignore" "on"<br />
EndSection<br />
</pre><br />
<br />
====Example configurations====<br />
<br />
The following subsections describe example configurations for commonly used configuration options. Note that if you use a desktop environment such as GNOME or KDE, options you set in the xorg.conf ''may'' get overwritten with user-specific options upon login.<br />
<br />
=====Example: Wheel Emulation (for a Trackpoint)=====<br />
<br />
If you own a computer with a Trackpoint (a Thinkpad for example) you can add the following to the {{Filename|xorg.conf}} to use the middle Button to emulate a mouse wheel:<br />
<br />
<pre><br />
Section "InputClass"<br />
Identifier "Wheel Emulation"<br />
MatchIsPointer "on"<br />
MatchProduct "TrackPoint"<br />
Option "EmulateWheelButton" "2"<br />
Option "EmulateWheel" "on"<br />
EndSection<br />
</pre><br />
<br />
For full support of TrackPoints (including horizontal scrolling) you can use the following:<br />
<pre><br />
Section "InputClass"<br />
Identifier "Trackpoint Wheel Emulation"<br />
MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint|ThinkPad USB Keyboard with TrackPoint|USB Trackpoint pointing device"<br />
MatchDevicePath "/dev/input/event*"<br />
Option "EmulateWheel" "true"<br />
Option "EmulateWheelButton" "2"<br />
Option "Emulate3Buttons" "false"<br />
Option "XAxisMapping" "6 7"<br />
Option "YAxisMapping" "4 5"<br />
EndSection<br />
</pre><br />
<br />
=====Example: Tap-to-click=====<br />
Tap-to-click can be enabled in the mouse configuration dialog (in the touchpad tab) but if you need tapping enabled at gdm already, the following snippet does it for you:<br />
<pre><br />
Section "InputClass"<br />
Identifier "tap-by-default"<br />
MatchIsTouchpad "on"<br />
Option "TapButton1" "1"<br />
EndSection<br />
</pre><br />
<br />
=====Example: Keyboard layout and model on Acer 5920G Laptop=====<br />
<br />
Keyboard model and layout may be set in the file {{filename|/etc/X11/xorg.conf.d/keyboard.conf}} or any other .conf file in the same directory.<br />
* {{Codeline|MatchIsKeyboard "yes"}}: set the input device to a keyboard<br />
* {{Codeline|Option "XkbModel" "acer_laptop"}}: set the keyboard model to an Acer * {{Codeline|Option "XkbLayout" "be"}}: set the keyboard layout to belgian. You may replace {{Codeline|be}} with whatever layout you have.<br />
* {{Codeline|Option "XkbVariant" "sundeadkeys"}}: set the layout variant to Sun dead keys. You may omit the {{Codeline|XkbVariant}} option if you stick with the default variant.<br />
laptop keyboard. You may replace {{Codeline|acer_laptop}} with your actual keyboard layout.<br />
<br />
Note that a list of keyboard layouts and models can be found in {{filename|/usr/share/X11/xkb/rules/base.lst}}<br />
<br />
<pre><br />
Section "InputClass"<br />
Identifier "Keyboard Defaults"<br />
MatchIsKeyboard "yes"<br />
Option "XkbModel" "acer_laptop"<br />
Option "XkbLayout" "be"<br />
Option "XkbVariant" "sundeadkeys"<br />
EndSection<br />
</pre><br />
<br />
===Keyboard settings===<br />
<br />
Xorg may fail to detect your keyboard correctly. This might give problems with your keyboard layout or keyboard model not being set correctly.<br />
<br />
To see a full list of keyboard models, layouts, variants and options, open:<br />
<br />
/usr/share/X11/xkb/rules/xorg.lst<br />
<br />
To set the keymap for the current Xorg session:<br />
# setxkbmap dvorak<br />
<br />
====Key repeat delay and rate====<br />
<br />
Use {{Codeline|xset r rate DELAY RATE}} to change them, then use [[xinitrc]] to make it permanent.<br />
<br />
====Viewing Keyboard Settings====<br />
$ setxkbmap -print -verbose 10<br />
<pre><br />
Setting verbose level to 10<br />
locale is C<br />
Applied rules from evdev:<br />
model: evdev<br />
layout: us<br />
options: terminate:ctrl_alt_bksp<br />
Trying to build keymap using the following components:<br />
keycodes: evdev+aliases(qwerty)<br />
types: complete<br />
compat: complete<br />
symbols: pc+us+inet(evdev)+terminate(ctrl_alt_bksp)<br />
geometry: pc(pc104)<br />
xkb_keymap {<br />
xkb_keycodes { include "evdev+aliases(qwerty)" };<br />
xkb_types { include "complete" };<br />
xkb_compat { include "complete" };<br />
xkb_symbols { include "pc+us+inet(evdev)+terminate(ctrl_alt_bksp)" };<br />
xkb_geometry { include "pc(pc104)" };<br />
};<br />
</pre><br />
<br />
====Setting Keyboard Layout With Hot-Plugging====<br />
To permanently change your keyboard layout, add the following to xorg.conf:<br />
<pre><br />
Section "InputClass"<br />
Identifier "Keyboard Defaults"<br />
MatchIsKeyboard "yes"<br />
Option "XkbLayout" "dvorak"<br />
EndSection<br />
</pre><br />
<br />
Note that this is in an InputClass Section and not the InputDevice section for the keyboard.<br />
<br />
====Setting Keyboard Layout Without Hot-Plugging (deprecated)====<br />
{{Note|Changing the keyboard layout through this method requires disabling input hot-plugging.}}<br />
<br />
To change the keyboard layout, use the XkbLayout option in the keyboard InputDevice section. For example, if you have a keyboard with English (Great Britain) layout, your keyboard InputDevice section might look similar to this:<br />
<br />
<pre><br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
Option "XkbLayout" "gb"<br />
EndSection<br />
</pre><br />
<br />
To change the keyboard model, use the XkbModel option in the keyboard InputDevice section. For example, if you have a Microsoft Wireless Multimedia Keyboard:<br />
<br />
Option "XkbModel" "microsoftmult"<br />
<br />
====Switching Between Keyboard Layouts====<br />
To be able to easily switch keyboard layouts, modify the Options used in either of the above two methods. For example, to switch between a US and a Swedish layout using the Caps Lock key, use:<br />
<br />
Option "XkbLayout" "us, se"<br />
Option "XkbOptions" "grp:caps_toggle"<br />
<br />
This is mainly useful if you run a Desktop Environment which does not take care of keyboard layouts for you.<br />
<br />
====Disable mousekeys Permanently====<br />
To disable the mousekeys permanently and prevent Shift+NumLock or Shift+Alt+NumLock to enable, edit:<br />
/usr/share/X11/xkb/compat/complete<br />
and comment out:<br />
augment "mousekeys"<br />
augment "accessx(full)"<br />
<br />
===Fonts===<br />
See [[Font Configuration]] for information on how to configure font rendering.<br />
<br />
===Sample xorg.conf Files===<br />
Anyone who has an Xorg.conf file written up that works, go ahead and post a link to it here for others to look at. Please do not in-line the entire configuration file; upload it somewhere else and link.<br /><br />
'''Please post input hotplugging configurations only, otherwise note that your config is not using input hotplugging.''' (Xorg 1.8 = udev)<br />
<br />
===== - Sample One: xorg.conf & xorg.conf.d/10-evdev.conf =====<br />
This is a sample configuration file using xorg.conf.d/10-evdev.conf for the keyboard layouts:<br /><br />
''Note: The "InputDevice" sections are commented out, because 10-evdev.conf is taking care of them.''<br />
xorg.conf: http://pastebin.com/raw.php?i=EuSKahkn<br />
xorg.conf.d/10-evdev.conf: http://pastebin.com/raw.php?i=4mPY35Mw><br />
xorg.conf.d/10-monitor.conf (VMWare): http://pastebin.com/raw.php?i=fJv8EXGb<br />
xorg.conf.d/10-monitor.conf (KVM): http://pastebin.com/raw.php?i=NRz7v0Kn<br />
<br />
==Running Xorg==<br />
<br />
You should add dbus to your DAEMONS array:<br />
<br />
DAEMONS=(syslog-ng '''dbus''' network crond)<br />
<br />
If you need to start dbus without rebooting, run<br />
<br />
# /etc/rc.d/dbus start<br />
<br />
Finally, start Xorg:<br />
$ startx<br />
or<br />
$ xinit -- /usr/bin/X -nolisten tcp<br />
<br />
{{Note|If you just installed Xorg, there is an empty .xinitrc file in your $HOME that you need to either delete or edit in order for X to start properly. If you do not do this X will show a blank screen with what appears to be no errors in your Xorg.0.log. Simply deleting it will get it running with a default X environment.}}<br />
<br />
The default X environment is rather bare, and you will typically seek to install window managers or desktop environments to supplement X. A list of suitable options is present in [[Common Applications#Window Managers (WM)]].<br />
<br />
If a problem occurs, then view the log at {{Filename|/var/log/Xorg.0.log}}. Be on the lookout for any lines beginning with {{Codeline|(EE)}} which represent errors, and also {{Codeline|(WW)}} which are warnings that could indicate other issues.<br />
<br />
===Methods for starting your Graphical Environment===<br />
What follows are a couple of methods for starting a graphical environment from the command line.<br />
{{Note|If you are using a full-blown Desktop Environment (Gnome, KDE, etc), you might be more interested in reading the wiki page dedicated to said DE.}}<br />
<br />
====Using runlevels====<br />
By default, Linux is set up to have different [[runlevels]]. Arch boots into runlevel 3 by default. Runlevel 5 is typically used in Linux for loading X server.<br />
Edit the file /etc/inittab. In the last section at the bottom of the file, uncomment the appropriate line for your desktop environment's display manager. For example, for XDM (X Display manager) it would look like this:<br />
# Example lines for starting a login manager<br />
x:5:respawn:/usr/bin/xdm -nodaemon<br />
#x:5:respawn:/usr/sbin/gdm -nodaemon<br />
#x:5:respawn:/usr/bin/kdm -nodaemon<br />
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1<br />
<br />
Now, simply start your desktop environment:<br />
# init 5<br />
<br />
====Using .xinitrc====<br />
This method involves the most configuring.<br />
<br />
First we need to configure ~/.xinitrc<br />
<br />
One of the main functions of this file is to dictate what '''X''' Window client is invoked with the '''/usr/bin/startx''' and/or '''/usr/bin/xinit''' program ''on a per-user basis''. (The '''startx''' script is merely a front end to the more versatile '''xinit''' command.) There are vast amounts of additional configurable specifications and commands that may also be added to ~/[[.xinitrc]] as you further customize your system.<br />
<br />
{{Note | '''[[.xinitrc]]''' is a so-called 'dot' (.) file. Files in a *nix filesystem which are preceded with a dot (.) are 'hidden', and will not show up with a regular 'ls' command, usually for the sake of keeping directories tidy. Dot files may be seen by issuing '''ls -a'''. The 'rc' denotes ''Run Commands'' and simply indicates that it is a configuration file. Since it controls how a program runs, it is (although historically incorrect) also said to stand for &quot;Run Control&quot;.}}<br />
<br />
The '''startx''' and '''xinit''' commands will start the '''X''' server and clients. To determine the client to run, '''startx/xinit''' will first look to parse a [[.xinitrc]] file in the user's home directory. In the absence of file ~/[[.xinitrc]], it defaults to the global xinitrc in the xinit library directory; /etc/X11/xinit/xinitrc, which defaults to using the TWM window manager. (Hence, if you invoke startx without a ~/[[.xinitrc]] file, a TWM session will start.) Further details in the [[.xinitrc]] wiki entry.<br />
<br />
Switch to your '''''normal, non-root''''' user:<br />
<br />
# su - ''yourusername''<br />
<br />
* /etc/skel/ contains files and directories to provide sane defaults for newly created user accounts. The name '''skel''' is derived from the word '''skeleton''', because the files it contains form the basic structure for users' home directories.<br />
{{Note | This template file '''[[.xinitrc]]''' is available in the /etc/skel directory when the package '''xorg-xinit''' is installed.}}<br />
<br />
* Sample .xinitrc provided [[Xinitrc#A_standard_.xinitrc | here]]<br />
Copy the sample xinitrc file from /etc/skel/ to your home directory:<br />
<br />
$ cp /etc/skel/[[.xinitrc]] ~/<br />
Edit the file:<br />
$ nano ~/.xinitrc<br />
and uncomment the line that corresponds to your Desktop Environment. For example, if you use Xterm, it will look something like this:<br />
<br />
<pre><br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
<br />
# exec gnome-session<br />
# exec startkde<br />
# exec startxfce4<br />
# exec wmaker<br />
# exec icewm<br />
# exec blackbox<br />
# exec fluxbox<br />
# exec openbox-session<br />
# ...or the Window Manager of your choice<br />
exec xterm<br />
</pre><br />
<br />
{{Note | ''Be sure to have only '''one''' uncommented '''exec''' line in ~/.xinitrc''.}}<br />
<br />
Now we're ready to launch X. Start '''X''' as a '''normal, non-root''' user, with:<br />
<br />
$ startx<br />
or<br />
$ xinit<br />
<br />
Your desktop should open up now. You can test your keyboard and its layout in it. Try moving your mouse around and enjoy the view.<br />
<br />
If trouble with automounting is experienced, try using the following command in ~/.xinitrc instead. (Replace "startxfce4" with the command that is appropriate for your window manager/DE.)<br />
exec ck-launch-session startxfce4<br />
This will ensure the various environment variables are set correctly by starting a clean consolekit session. ConsoleKit is a framework for keeping track of the various users, sessions, and seats present on a system. It provides a mechanism for software to react to changes of any of these items or of any of the metadata associated with them. It works in conjunction with dbus, and other tools.<br />
<br />
==Tips and tricks==<br />
<br />
===X startup (/usr/bin/startx) tweaking===<br />
For X's option reference see:<br />
$ man Xserver<br />
<br />
The following options have to be appended to the variable {{Codeline|"defaultserverargs"}} in the {{Filename|/usr/bin/startx}} file:<br />
<br />
* Enable deferred glyph loading for 16 bit fonts:<br />
-deferglyphs 16<br />
<br />
Note: If you start X with kdm, the startx script does not seem to be executed. X options must be appended to the variable {{Codeline|"ServerArgsLocal"}} or {{Codeline|"ServerCmd"}} in the {{Filename|/usr/share/config/kdm/kdmrc}} file. By default kdm options are:<br />
ServerArgsLocal=-nolisten tcp<br />
ServerCmd=/usr/bin/X<br />
<br />
===Virtual X session===<br />
To start another X session in, for example, CTRL + ALT + F8, you need to type this on a console:<br />
xinit /path/to/wm -- :1<br />
<br />
Change "/path/to/wm" to your window manager start file or to your login manager like gdm, kdm, or slim.<br />
<br />
===Nested X session===<br />
To run a nested session of another desktop environment:<br />
$ /usr/bin/Xnest :1 -geometry 1024x768+0+0 -ac -name Windowmaker & wmaker -display :1<br />
<br />
This will launch a Window Maker session in a 1024 by 768 window within your current X session.<br />
<br />
This needs the package ''xorg-server-xnest'' to be installed.<br />
<br />
==Troubleshooting==<br />
===Common problems===<br />
If Xorg will not start, the screen is completely black, the keyboard and mouse are not working, etc., first take these simple steps:<br />
*Check the log file: {{codeline|cat /var/log/Xorg.0.log}}<br />
*Install input driver (keyboard, mouse, joystick, tablet, etc...):<br />
*Finally, search for common problems in [[ATI]], [[Intel]] and [[NVIDIA]] articles.<br />
<br />
===Ctrl-Alt-Backspace doesn't work===<br />
There are two ways of restoring {{keypress|Ctrl}}+{{keypress|Alt}}+{{keypress|Backspace}}; with and without input-hotplugging. Using hot-plugging is recommended.<br />
<br />
====With input hot-plugging====<br />
In most situations, using user-specific configuration might be preferred over system-wide.<br />
<br />
{{Note|On GNOME, this system-wide setting has no effect. Every user must go to System -> Preferences -> Keyboard -> Layouts -> Options [button] -> Key sequence to kill the X server [expand with triangle on left]. Then check Ctrl + Alt + Backspace option.}}<br />
<br />
{{Note|On KDE, this system-wide setting has no effect. To restore, go to Kickoff > Computer > System Settings which will open up the System Settings window. Click on 'Regional & Language'. In this new window click the Keyboard tab and then check the box for 'Enable Keyboard layouts'. This will enable you to click on the advanced tab. In this new window, expand the entry for 'Key sequence to kill the X server' and ensure Control + Alt + Backspace is checked. Click Apply and close the System Settings window. You now have your CTRL-ALT-Backspace back in KDE.}}<br />
<br />
=====System-wide=====<br />
Add<br />
Option "XkbOptions" "terminate:ctrl_alt_bksp"<br />
to InputClass as so:<br />
<br />
<pre><br />
Section "InputClass"<br />
Identifier "Keyboard Defaults"<br />
MatchIsKeyboard "yes"<br />
Option "XkbOptions" "terminate:ctrl_alt_bksp"<br />
EndSection<br />
</pre><br />
<br />
=====User-specific=====<br />
Another way is to put this line in [[xinitrc]]:<br />
setxkbmap -option terminate:ctrl_alt_bksp<br />
<br />
====Without input hot-plugging====<br />
New Xorg disables zapping with {{Keypress|Ctrl}}+{{Keypress|Alt}}+{{Keypress|Backspace}} by default. You can enable it by adding the following line to {{Filename|/etc/X11/xorg.conf}},<br />
Option "XkbOptions" "terminate:ctrl_alt_bksp"<br />
to {{codeline|InputDevice}} section for keyboard.<br />
<br />
===Apple keyboard issues===<br />
:''See: [[Apple Keyboard]]''<br />
<br />
===Touchpad tap-click issues===<br />
:''See: [[Synaptics]]''<br />
<br />
===Extra mouse buttons not recognized===<br />
:''See: [[Get All Mouse Buttons Working]]''<br />
<br />
===X clients started with "su" fail===<br />
If you are getting "Client is not authorized to connect to server", try adding the line:<br />
session optional pam_xauth.so<br />
to {{filename|/etc/pam.d/su}}. {{codeline|pam_xauth}} will then properly set environment variables and handle {{codeline|xauth}} keys.<br />
<br />
===Program requests "font '(null)'"===<br />
*Error message: "''unable to load font `(null)'.''"<br />
Some programs only work with bitmap fonts. Two major packages with bitmap fonts are available, xorg-fonts-75dpi and xorg-fonts-100dpi. You do not need both; one should be enough. To find out which one would be better in your case, try this:<br />
$ xdpyinfo | grep resolution<br />
and use what is closer to you (75 or 100 instead of XX)<br />
# pacman -S xorg-fonts-XXdpi<br />
<br />
===Frame-buffer mode problems===<br />
If X fails to start with the following log messages,<br />
<pre><br />
(WW) Falling back to old probe method for fbdev<br />
(II) Loading sub module "fbdevhw"<br />
(II) LoadModule: "fbdevhw"<br />
(II) Loading /usr/lib/xorg/modules/linux//libfbdevhw.so<br />
(II) Module fbdevhw: vendor="X.Org Foundation"<br />
compiled for 1.6.1, module version=0.0.2<br />
ABI class: X.Org Video Driver, version 5.0<br />
(II) FBDEV(1): using default device<br />
<br />
Fatal server error:<br />
Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices<br />
</pre><br />
uninstall fbdev:<br />
# pacman -R xf86-video-fbdev<br />
<br />
===DRI with Matrox cards stops working===<br />
If you use a Matrox card and DRI stops working after upgrading to Xorg, try adding the line:<br />
Option "OldDmaInit" "On"<br />
to the Device section that references the video card in xorg.conf.<br />
<br />
===Recovery: disabling Xorg before GUI login===<br />
If Xorg is set to boot up automatically and for some reason you need to prevent it from starting up before the login/display manager appears (if {{filename|rc.conf}} is wrongly configured and Xorg does not recognize your mouse or keyboard input, for instance), you can accomplish this task with two methods.<br />
<br />
*From the grub menu, you can specify the runlevel in the kernel line by adding a number to the end of the kernel line specifying the run level you want. The following example sets the run level to 3:<br />
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/..ro 3<br />
<br />
*If you have not only a faulty {{filename|rc.conf}} to make Xorg unusable, but you have also set the grub menu wait time to zero, or cannot otherwise use grub to prevent Xorg from booting, you can use the Arch live CD. Boot up the live CD and login as root. You need a mount point, such as {{filename|/mnt}}, and you need to know the name of the partition you want to mount.<br />
<br />
:You can use the command,<br />
# fdisk -l<br />
:to see your partitions. Usually, the one you want will be resembling {{filename|/dev/sda1}}. Then, to mount this to {{filename|/mnt}}, use<br />
# mount /dev/sda1 /mnt<br />
<br />
:Then your file-system will show up under {{filename|/mnt}}. So your {{filename|rc.conf}} file, for example, would be in {{filename|/mnt/etc/rc.conf}}. From here you can delete the {{codeline|gdm}} module to prevent Xorg from booting up normally, or make any other necessary changes.<br />
<br />
==See also==<br />
* [[Display Manager]]<br />
* [[Execute commands after X start]]<br />
* [[Start X at boot]]<br />
* [[Font Configuration]]<br />
* Proprietary Video Drivers<br />
** [[ATI Catalyst]]<br />
** [[NVIDIA]]<br />
* [[Desktop Environment]]<br />
* [[Window Manager]]<br />
* [[Get All Mouse Buttons Working]]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Archiso&diff=137559Archiso2011-04-17T23:37:36Z<p>Taylorchu: /* Finishing the overlay */</p>
<hr />
<div>[[Category:Live_Arch_systems_(English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|Archiso}}<br />
[[fr:Archiso]]<br />
== What is it? ==<br />
'''Archiso''' is a small set of bash scripts that is capable of building fully functional '''Arch Linux based live CD/DVD and USB images'''. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, to install disks, to special interest live CD/DVD/USB systems, and who knows what else. Simply put, if it involves Arch on a shiny coaster, it can do it.<br />
The heart and soul of Archiso is '''mkarchiso'''. All of its options are documented in its usage output, so its direct usage wont be covered here. Instead, this wiki article will act as a guide for rolling your own live mediums in no time!<br />
<br />
Due to recent changes, '''Archiso''' will now automatically create ISO images that are also USB images! Separate CD/USB targets are therefore no longer necessary.<br />
<br />
== Install Archiso ==<br />
<br />
You have two options to get Archiso:<br />
<br />
*Get the [http://aur.archlinux.org/packages.php?ID=25996 archiso-git AUR package] (recommended)<br />
*Get it from the Git repo yourself:<br />
$ git clone git://projects.archlinux.org/archiso.git<br />
$ cd archiso/archiso<br />
$ sudo make install<br />
$ sudo pacman --needed -S mkinitcpio cdrkit squashfs-tools devtools syslinux mkinitcpio-nfs-utils nbd<br />
<br />
== Configure our live medium ==<br />
<br />
=== Makefile ===<br />
The very first thing you should do is creating a directory to work in, and cd to it. This'll help keep things organized. <br />
$ mkdir myarch && cd myarch<br />
Next, you'll want to create a Makefile and put our building instructions in there. The Makefile will define all actions that mkarchiso is going to execute. You could say it is our project file.<br />
$ vim Makefile<br />
Below you will find a sample Makefile that should work for most stuff you want and that works with everything described in this article.<br />
<br />
{{Warning | All indents within the makefile are with tabs. Using spaces gives a missing separator error}}<br />
<br />
{{Warning | Earlier versions of this makefile worked with "mkinitcpio -c mkinitcpio.conf..." however (possibly due to recent updates?) this may no longer work. If you see a warning regarding not being able to find the mkinitcpio.conf file, use the full path to the file, or "./". Otherwise you may get an empty initcpio, which will render the system unbootable (VFS error, kernel panic)}}<br />
<br />
{{Warning | This Makefile is untested. Is updated now to current mkarchiso, but maybe is broken... See [[Talk:Archiso#baseline_profile_.28for_current_archiso.git_.5B20101218.5D.29|baseline profile]] if you have any issue.}}<br />
<br />
<code><br />
#### Change these settings to modify how this ISO is built.<br />
# The directory that you'll be using for the actual build process.<br />
'''WORKDIR=work'''<br />
'''# INSTALL_DIR -> max 8 chars.'''<br />
'''INSTALL_DIR=mydir'''<br />
'''COMPRESS=gzip'''<br />
'''LABEL=MY_ARCH'''<br />
# A list of packages to install, either space separated in a string or line separated in a file. Can include groups.<br />
'''PACKAGES="$(shell cat packages.list) syslinux"'''<br />
# The name of our ISO. Does not specify the architecture!<br />
'''NAME=myarch'''<br />
# Version will be appended to the ISO.<br />
'''VER=1.00'''<br />
# Kernel version. You'll need this. Don't change it.<br />
'''kver_FILE=$(WORKDIR)/root-image/etc/mkinitcpio.d/kernel26.kver'''<br />
# Architecture will also be appended to the ISO name.<br />
'''ARCH?=$(shell uname -m)'''<br />
# Current working directory<br />
'''PWD:=$(shell pwd)'''<br />
# This is going to be the full name the final iso/img will carry<br />
'''FULLNAME="$(PWD)"/$(NAME)-$(VER)-$(ARCH)'''<br />
<br />
# Default make instruction to build everything.<br />
'''all: myarch'''<br />
<br />
# The following will first run the ''base-fs'' routine before creating the final iso image.<br />
'''myarch: base-fs'''<br />
'''mkarchiso -L "$(LABEL)" -D $(INSTALL_DIR) -c $(COMPRESS) -p syslinux iso "$(WORKDIR)" "$(FULLNAME)".iso'''<br />
<br />
# This is the main rule for make the working filesystem. It will run routines from left to right. <br />
# Thus, ''root-image'' is called first and ''syslinux'' is called last.<br />
'''base-fs: root-image boot-files initcpio overlay iso-mounts syslinux'''<br />
<br />
# The ''root-image'' routine is always executed first. <br />
# It only downloads and installs all packages into the ''$WORKDIR'', giving you a basic system to use as a base.<br />
'''root-image: "$(WORKDIR)"/root-image/.arch-chroot'''<br />
'''"$(WORKDIR)"/root-image/.arch-chroot:'''<br />
'''root-image:'''<br />
'''mkarchiso -D $(INSTALL_DIR) -c $(COMPRESS) -p $(PACKAGES) create "$(WORKDIR)"'''<br />
<br />
# Rule for make /boot<br />
'''boot-files: root-image'''<br />
'''cp -r "$(WORKDIR)"/root-image/boot "$(WORKDIR)"/iso/'''<br />
'''cp -r boot-files/* "$(WORKDIR)"/iso/ # mkarchiso will look for "$(WORKDIR)"/iso/syslinux/syslinux.cfg'''<br />
# During the boot, syslinux will look for /boot/syslinux/syslinux.cfg, because /boot/syslinux/ directory exists'''<br />
'''cp -r "$(WORKDIR)"/iso/syslinux "$(WORKDIR)"/iso/boot <br />
# Based on mkarchiso'''<br />
'''sed "s|%ARCHISO_LABEL%|$(LABEL)|g; s|%INSTALL_DIR%|$(INSTALL_DIR)|g;" -i "$(WORKDIR)"/iso/boot/syslinux/syslinux.cfg; <br />
<br />
# Rules for initcpio images<br />
'''initcpio: "$(WORKDIR)"/iso/boot/kernel26.img'''<br />
'''"$(WORKDIR)"/iso/boot/kernel26.img: mkinitcpio.conf "$(WORKDIR)"/root-image/.arch-chroot'''<br />
'''mkdir -p "$(WORKDIR)"/iso/boot'''<br />
'''mkinitcpio -c ./mkinitcpio.conf -b "$(WORKDIR)"/root-image -k `uname -r` -g $@'''<br />
<br />
# See: [[#overlay|Overlay]]<br />
'''overlay:'''<br />
'''mkdir -p "$(WORKDIR)"/overlay/etc/pacman.d'''<br />
'''cp -r overlay "$(WORKDIR)"/'''<br />
'''wget -O "$(WORKDIR)"/overlay/etc/pacman.d/mirrorlist http://www.archlinux.org/mirrorlist/all/'''<br />
'''sed -i "s/#Server/Server/g" "$(WORKDIR)"/overlay/etc/pacman.d/mirrorlist'''<br />
<br />
# Rule to process isomounts file.'''<br />
'''iso-mounts: "$(WORKDIR)"/$(INSTALL_DIR)/isomounts'''<br />
'''"$(WORKDIR)"/$(INSTALL_DIR)/isomounts: isomounts root-image'''<br />
'''sed "s|@ARCH@|$(ARCH)|g" isomounts > $@'''<br />
<br />
# This routine is always executed just before generating the actual image. <br />
'''syslinux: root-image'''<br />
'''mkdir -p $(WORKDIR)/iso/$(INSTALL_DIR)/boot/$(ARCH)'''<br />
'''mkdir -p $(WORKDIR)/iso/$(INSTALL_DIR)/syslinux'''<br />
'''cp -PR $(WORKDIR)/root-image/usr/lib/syslinux/*.c32 $(WORKDIR)/iso/$(INSTALL_DIR)/syslinux/'''<br />
'''cp -PR $(WORKDIR)/root-image/usr/lib/syslinux/isolinux.bin $(WORKDIR)/iso/$(INSTALL_DIR)/syslinux/'''<br />
<br />
# In case "make clean" is called, the following routine gets rid of all files created by this Makefile.<br />
'''clean:'''<br />
'''rm -rf "$(WORKDIR)" "$(FULLNAME)".img "$(FULLNAME)".iso'''<br />
<br />
.PHONY: all myarch<br />
.PHONY: base-fs<br />
.PHONY: root-image boot-files initcpio overlay iso-mounts<br />
.PHONY: syslinux<br />
.PHONY: clean<br />
<br />
So if "make myarch" is called (as '''root'''!), the following is what effectively happens:<br />
*'''root-image''' downloads and installs all chosen packages into ''$WORKDIR''<br />
*'''boot-files''' prepares generic bootloader files and then copies our custom bootloader settings<br />
*'''initcpio''' takes care of an ''initcpio'' for us<br />
*'''overlay''' copies our custom overlay files into the ''root-image'' in ''$WORKDIR'' <br />
*'''iso-mounts''' just a little sed magic so AUFS will be able to find its mount points at boot time<br />
*'''syslinux''' copies over our actual bootloader<br />
*'''myarch''' finally creates our bootable .iso file, ready for burning onto a CD/DVD or writing to a USB device<br />
</code><br />
<br />
A Makefile itself won't suffice, so you'll need to create some additional files which will be covered below.<br />
<br />
=== mkinitcpio.conf ===<br />
<br />
An ''initcpio'' is necessary for creating a system that is able to "wake-up" from a CD/DVD/USB.<br />
<br />
Therefore, you should create a mkinitcpio.conf that holds a list of our hooks:<br />
$ vim mkinitcpio.conf<br />
A typical set of hooks for archiso looks something like this:<br />
HOOKS="base udev memdisk archiso archiso_pxe_nbd archiso_loop_mnt pata scsi sata usb fw pcmcia filesystems usbinput"<br />
<br />
This list will get you a system that can be booted off a CD/DVD or a USB device. It's worth mentioning that hardware auto-detection and things of that nature do not belong here. Only what's necessary to get the system on its feet, and out of the ''initcpio'' really belong here, fancier stuff can be done on the booted system anyway.<br />
<br />
=== packages.list ===<br />
<br />
You'll also want to create a list of packages you want installed on your live CD system. A file full of package names, one-per-line, is the format for this. Typically you'll want '''base''' and '''kernel26''' as a bare minimum, but you're free to install whatever else you want. This is '''''great''''' for special interest live CDs, just specify packages you want and bake the image.<br />
<br />
{{Note|'''mkarchiso''' will use your local build machine's ''/etc/pacman.conf'' for sources. If you have activated [testing] in there, it will also be used for grabbing the packages for the live medium. If you want to use another ''pacman.conf'', you can copy it to the local project folder and use '''mkarchiso -C pacman.conf''' to use your local ''pacman.conf''. For this to work when building the ISO, you will have to add '''-C pacman.conf''' to all calls to '''mkarchiso''' in the Makefile.}}<br />
$ vim packages.list<br />
You may want to put at least the following into there:<br />
aufs2<br />
aufs2-util<br />
base<br />
bash<br />
coreutils<br />
cpio<br />
dhcpcd<br />
dnsutils<br />
file<br />
fuse<br />
kernel26<br />
syslinux<br />
nano<br />
<br />
This should already get you a booting system without much else. Be aware, though, that it lacks quite a lot drivers that aren't directly included in the kernel, notably wireless and graphics drivers and of course special purpose devices. Just add in driver packages as desired. A lot of hardware should run anyway, though. For some suggestions for different configurations, see the included examples for Archiso.<br />
<br />
{{Tip|You can also create a '''[[custom local repository]]''' for the purpose of preparing custom packages or packages from [[AUR]]/[[ABS]]. Just add your local repository at the first position (for top priority) of your build machine's '''pacman.conf''' and you are good to go! If you plan on using an X environment and plan to use the image for a wide array of machines consider patching xorg-server to default nvidia cards to use the nouveau driver instead of the nv driver. See '''[[Patching in ABS]]''' for patching help and '''[http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-base/xorg-server/files/ here]''' you can find a patch file to set nouveau as the default.}}<br />
<br />
=== isomounts ===<br />
<br />
You will need a small file that holds information about the file systems that are going to be mounted once the live medium boots.<br />
$ vim isomounts<br />
A sample ''isomounts'' for your convenience:<br />
# archiso isomounts file<br />
# img - location of image/directory to mount relative to addons directory<br />
# arch - architecture of this image<br />
# mount point - absolute location on the post-initrd root<br />
# type - either 'bind' or 'squashfs' for now<br />
# syntax: <img> <arch> <mount point> <type><br />
# ORDER MATTERS! Files take top-down precedence. Be careful<br />
@ARCH@/overlay.sqfs @ARCH@ / squashfs<br />
@ARCH@/root-image.sqfs @ARCH@ / squashfs<br />
<br />
<br />
{{warning| There should be an enter [empty line] which represents EOF [end of file] at the end of isomounts file or else expect kernel panic!}}<br />
<br />
=== boot-files ===<br />
<br />
You will add least need a "boot-files" directory and and a subdirectory "syslinux/" containing a "syslinux.cfg".<br />
<br />
{{warning|Due to recent changes, support for [[grub]] as a boot manager for Archiso live medium creation has been dropped. Please do not attempt to use grub. Instead, you will have to use syslinux's isolinux which will get you an iso that will double as a usb image for free.}}<br />
<br />
==== Using isolinux ====<br />
Using ''isolinux'' is easy:<br />
$ mkdir -p boot-files/syslinux/<br />
$ vim boot-files/syslinux/syslinux.cfg<br />
<br />
Sample contents:<br />
prompt 1<br />
timeout 0<br />
display myarch.msg<br />
DEFAULT myarch<br />
<br />
LABEL myarch<br />
LINUX /%INSTALL_DIR%/boot/%ARCH%/vmlinuz26<br />
APPEND APPEND initrd=/%INSTALL_DIR%/boot/%ARCH%/archiso.img archisobasedir=%INSTALL_DIR% archisolabel=%ARCHISO_LABEL% locale=en_US.UTF-8<br />
<br />
LABEL memtest86+<br />
KERNEL /%INSTALL_DIR%/boot/memtest86+-2.10.bin<br />
<br />
Additionally, you may want a message to be shown above the boot line:<br />
$ vim boot-files/syslinux/myarch.msg<br />
<br />
This can be any arbitrary message in ASCII:<br />
<br />
HI GENTLEMEN LOL<br />
WELCOME TO MY DISTRO<br />
I HOPE U ENJOY MAKE UR TIME<br />
HA-HA-HA<br />
<br />
Please do note that you will first have to manually get the memtest*.bin from somewhere first because it won't be put there for you. If you do not want to use it, please comment it out. You can install it locally via pacman or you can find the binary package online if you don't want it locally installed. Put it in the boot-files/ directory for USB usage. You will also have to rename the memtest*.bin file and remove the .bin extension, with .bin it will just boot a continuous display of "0104". Edit your syslinux.cfg KERNEL line accordingly.<br />
<br />
$ pacman -S memtest86+<br />
$ cp /boot/memtest86+/memtest.bin boot-files/memtest<br />
<br />
syslinux.cfg memtest entry:<br />
<br />
LABEL memtest86+<br />
KERNEL /%INSTALL_DIR%/boot/memtest<br />
<br />
Due to the modular nature of isolinux, you are able to use lots of addons since all *.c32 files are copied and available to you. Take a look at the [http://syslinux.zytor.com/wiki/index.php/SYSLINUX official syslinux site] and the [http://projects.archlinux.org/archiso.git/tree/configs/syslinux-iso/boot-files archiso git repo]. Using said addons, it is possible to make visually attractive and complex menus. See [http://syslinux.zytor.com/wiki/index.php/Comboot/menu.c32 here].<br />
<br />
=== overlay ===<br />
The last item of importance is the '''overlay'''. Basically this means any other stuff you might want to include on your live medium, including binary package repositories, special configurations, random files, anything you can think of. ''mkarchiso'' expects them all to be put in a single directory. The ''overlay'' will, as the name implies, be layered on top the base system at boot time using ''AUFS''. The structure inside the overlay is that of a root filesystem. <br />
<br />
All non-existing files and directories which are included in the overlay but do not exist in the base system will be created. <br />
All existing files and directories which do exist in the base system are overwritten with the files from the overlay.<br />
<br />
Next, create the ''overlay'':<br />
$ mkdir overlay && cd overlay/<br />
<br />
Woah, that was easy! Now, you still need to add some useful stuff in there. A couple of examples: <br />
<br />
{{Note | It is important that all files in the overlay carry the proper permissions. You are therefore advised to use the root account to commit changes to this directory. Remember, it is an actual root filesystem layer.}}<br />
<br />
==== Adding a fstab ====<br />
It is required to add a '''fstab''' file in /etc:<br />
$ mkdir etc<br />
$ vim etc/fstab<br />
<br />
aufs / aufs noauto 0 0<br />
none /dev/pts devpts defaults 0 0<br />
none /dev/shm tmpfs defaults 0 0<br />
<br />
==== Adding a predefined user ====<br />
<br />
===== Manually =====<br />
You will want a user in your live session. There are many ways to do that. One way to do it is to manually add the user and all groups you may want as files in etc/, without calling any commands. This can be accomplished by using your host system's /etc files and modifying them to make them fit the purpose:<br />
<br />
$ cp /etc/group etc/group<br />
$ cp /etc/passwd etc/passwd<br />
$ cp /etc/shadow etc/shadow<br />
<br />
{{Note | Be very careful not to leave your encrypted passwords in the passwd or shadow file! Your password is at the second position (after the first ':'). You must not leave it in there!}}<br />
<br />
To make a password-less user, simply clear the second position like so: <br />
root::99999::::::<br />
<br />
Additionally, the user will need a home directory or many things will fail (remember to change the home directory correctly in ''passwd''). You will want to use rc.local to create a home directory at boot time and fill it with /etc/skel. If you don't know about /etc/skel, you should read up on that.<br />
$ vim etc/rc.local<br />
mkdir /home/archie && chown archie:archie /home/archie<br />
su -c "cp -r /etc/skel/.[a-zA-Z0-9]* /home/archie/" archie<br />
<br />
===== Using useradd =====<br />
Another way of adding the user is using ''etc/rc.local'' to create the user at boot time:<br />
$ vim etc/rc.local<br />
<br />
useradd -u 1000 -g users -G storage,floppy,optical,audio,video,network,games,wheel,disk -d /home/archie archie<br />
<br />
$ chmod +x etc/rc.local<br />
<br />
This should take care of the user and his home directory.<br />
<br />
==== Putting stuff into the user's home directory at boot time ====<br />
It might be desirable to put some pre-defined user settings in place when the live user enters his session. Luckily, there is a directory which automatically copies itself into each new user's home directory: /etc/skel.<br />
<br />
You will need to create that directory and then put your stuff in there:<br />
$ mkdir etc/skel<br />
<br />
And for example:<br />
$ vim etc/skel/.bashrc <br />
<br />
alias ls='ls --color=auto'<br />
PS1='[\u@\h \W]\$ '<br />
<br />
Covering all the magic that could be done to a user at boot time is vastly beyond this article's scope.<br />
<br />
{{Note | You may NOT directly create any user's home directory directly in the overlay by putting stuff into /home/user/, it will break permissions in the guest system! Use /etc/skel/.}}<br />
<br />
==== Finishing the overlay ====<br />
Some tips that will not be covered in this article because there are other articles on this wiki that already do:<br />
*Configure an ''inittab'' to start into X at boot time<br />
*Configure the ''hosts'' file<br />
*Configure ''rc.conf'' (no fancy modules required here)<br />
*Configure ''sudoers''<br />
*Configure ''rc.local''<br />
*Put more stuff into etc/skel<br />
*Put additional artworks onto the medium <br />
*Put arbitrary binary stuff into opt/<br />
<br />
{{Note|A complete example at [http://projects.archlinux.org/archiso.git/tree/configs/syslinux-iso archiso.git]}}<br />
<br />
== Generate your live medium ==<br />
After so much time spent on configuring, here comes the fun part: Baking the image.<br />
<br />
It's quite easy, too: As root (important!) execute the following in your project directory (where your ''Makefile'' is located):<br />
# make all<br />
You will receive a .iso, ready for burning onto a CD/DVD or for dd'ing onto a USB key: <br />
dd if=my-image.iso of=/dev/some-usb-drive bs=8M<br />
<br />
{{Note| If you add an extra partition to your USB key, ensure to assign a LABEL to the filesystem, otherwise the live-medium will fail to boot. If you want to partition your USB key so that you'll have a partition of it that is mountable in Windows check [http://archlinux.me/brain0/2010/05/29/arch-linux-usb-install-and-resuce-media/ here] for instructions. Again, pay attention to the LABEL.}}<br />
{{Note | If you do decide to partition a USB key take note that the Makefile generates an image that will want a partition labeled as ARCH_201102 (with changing month/year accordingly). This is generally of no concern but occasionally with this the startup would fail because it couldn't find the correct device by label (due to adjusting dates). For the '''mkarchiso''' entries in the Makefile add a '''-L''' option to label it with your own label (mkarchiso lines can be found in the '''myarch:''' and '''root-image:''' entries) and avoid using the dated naming scheme. This has been advised against however so only consider using if you're running into this issue.}}<br />
Enjoy!<br />
{{warning|Careful with <tt>dd</tt>! If you use it on the wrong drive, a lot of precious data may be lost. Use with caution.}}<br />
{{Note | If you get any errors during the process try one of the the following: a) enable [testing] and update mkinitcpio, b) replace "iso-mounts" with "isomounts" in the Makefile, c) replace "archiso-early" with "archiso_early" in mkinitcpio.conf. May or may not help.}}<br />
<br />
== See also ==<br />
*[http://projects.archlinux.org/?p=archiso.git;a=summary Archiso project page]<br />
*[[Archiso_as_pxe_server|Archiso as pxe server]]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Openbox&diff=130223Openbox2011-02-08T06:47:43Z<p>Taylorchu: /* Obm-xdg */</p>
<hr />
<div>[[Category:Stacking WMs (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|Openbox}}<br />
<br />
Openbox is a lightweight and highly configurable window manager with extensive standards support. Its features are well-documented at the [http://openbox.org/ official website]. This article will pertain to running Openbox under Arch Linux.<br />
<br />
== Installation ==<br />
<br />
Openbox is available from the standard repositories:<br />
# pacman -S openbox<br />
<br />
Once installed, pacman will direct you to copy the default {{Filename|menu.xml}} and {{Filename|rc.xml}} configuration files to {{Filename|~/.config/openbox}}, for example:<br />
<br />
{{Note | Do this as a regular user, not as root.}}<br />
<br />
$ mkdir -p ~/.config/openbox<br />
$ cp /etc/xdg/openbox/{rc.xml,menu.xml,autostart.sh} ~/.config/openbox<br />
<br />
{{Filename|rc.xml}} is the core configuration file for Openbox. It is used to manage keyboard shortcuts, themes, virtual desktops and other features.<br />
<br />
{{Filename|menu.xml}} controls the Openbox application menu that appears when you click on your desktop. The default items are pretty sparse, but it's very easy to modify the menu structure to suit your needs. See the menu section below for more details, or visit the [http://openbox.org Openbox website].<br />
<br />
{{Filename|autostart.sh}} The default autostart file sets up a number of things for you. You can use this script to launch a panel, to set your desktop wallpaper, or anything else. More details in the [http://openbox.org/wiki/Help:Autostart Openbox Wiki].<br />
<br />
== Stand-alone window manager ==<br />
<br />
To run Openbox on its own, simply add the following to the bottom of {{Filename|~/.xinitrc}}:<br />
exec openbox-session<br />
<br />
You may also start OpenBox from the shell using '''xinit''':<br />
$ xinit /usr/bin/openbox-session<br />
<br />
If you have used another window manager before, such as Xfwm, and Openbox won't start after logging out of X, try moving the autostart folder:<br />
mv ~/.config/autostart ~/.config/autostart-bak<br />
<br />
Using D-Bus or similar, use this instead:<br />
exec ck-launch-session openbox-session<br />
<br />
If you also use '''polkit''' and '''D-Bus''' (e.g. for automount drivers in nautilus from Gnome 2.28 / 2.30) use:<br />
exec ck-launch-session dbus-launch openbox-session<br />
<br />
{{Note | [http://www.archlinux.org/packages/extra/any/pyxdg/ pyxdg] is required for Openbox's xdg-autostart}}<br />
<br />
== Window manager for Desktop Environments ==<br />
<br />
=== GNOME ===<br />
==== GNOME 2.26 ====<br />
'''''Follow the next guide for GNOME 2.24. If it fails try this:'''''<br />
<br />
If after installing openbox and trying to log into the 'Gnome/openbox' session but it always fails then you can do the following as one way to achieve running openbox as your window manager every time you log into the 'Gnome' session from your login manager (xdm, gdm, kdm, entrance, slim, etc.)<br />
<br />
#Log into your Gnome only session (which would still be using metacity as its window manager) if you aren't already.<br />
#Install openbox if you have not done so already<br />
#Explore your menus to ''System &rarr; Preferences &rarr; Startup Applications'' (possibly named 'Session' for older versions of Gnome)<br />
#Open Startup Application, select '+ Add' and enter the text as seen in the box below whilst omitting the text behind the #.<br />
#Now hit the 'Add' button for that data entry window and make sure the checkbox beside your new entry is selected.<br />
#Thus log out of your gnome session and log back in and you should be running openbox as your window manager.<br />
#Enjoy!<br />
<br />
Name: Openbox Windox Manager # Can be changed<br />
Command: openbox --replace # Text should not be removed from this line, but possibly added to it<br />
Comment: Replaces metacity with openbox # Can be changed<br />
<br />
This creates an entry in a startup list which is executed by gnome everytime that particular user's gnome-session is started.<br />
<br />
==== GNOME 2.24 ====<br />
First, create {{Filename|/usr/share/applications/openbox.desktop}} containing the following:<br />
[Desktop Entry]<br />
Type=Application<br />
Encoding=UTF-8<br />
Name=OpenBox<br />
Exec=openbox<br />
NoDisplay=true<br />
# name of loadable control center module<br />
X-GNOME-WMSettingsModule=openbox<br />
# name we put on the WM spec check window<br />
X-GNOME-WMName=OpenBox<br />
Then, in gconf, set {{Codeline|/desktop/gnome/session/required_components/windowmanager}} to {{Codeline|openbox}}:<br />
$ gconftool-2 -s -t string /desktop/gnome/session/required_components/windowmanager openbox<br />
Finally, choose the '''GNOME''' session in the GDM sessions menu.<br />
<br />
==== GNOME 2.22 and previous ====<br />
# If you use GDM, select the "GNOME/Openbox" login option<br />
# If you use {{Codeline|startx}}, add {{Codeline|exec openbox-gnome-session}} to {{Filename|~/.xinitrc}}<br />
# From the shell:<br />
$ xinit /usr/bin/openbox-gnome-session<br />
<br />
=== KDE ===<br />
# If you use KDM, select the "KDE/Openbox" login option<br />
# If you use startx, add {{Codeline|exec openbox-kde-session}} to {{Filename|~/.xinitrc}}<br />
# From the shell:<br />
$ xinit /usr/bin/openbox-kde-session<br />
<br />
=== Xfce4 ===<br />
Log into a normal Xfce4 session. From your terminal of choice, do:<br />
$ killall xfwm4 ; openbox & exit<br />
<br />
This will kill xfwm4, run Openbox, and close the terminal. <br />
<br />
Log out, making sure to check the "Save session for future logins" checkbox. On next login, Xfce4 will use Openbox as its WM. To be able to exit the session using xfce4-session, open your file {{Filename|~/.config/openbox/menu.xml}} (if it isn't there, copy it from {{Filename|/etc/xdg/openbox/menu.xml}}). <br />
<br />
Look for the entry:<br />
<br />
<item label="Exit Openbox"><br />
<action name="Exit"><br />
<prompt>yes</prompt><br />
</action><br />
</item><br />
<br />
and change it to:<br />
<br />
<item label="Exit Openbox"><br />
<action name="Execute"><br />
<prompt>yes</prompt><br />
<command>xfce4-session-logout</command><br />
</action><br />
</item><br />
<br />
Otherwise, using the "Exit" entry of the root-menu will cause Openbox to terminate its execution, leaving you without a window manager.<br />
<br />
If you have an issue changing between virtual desktops with the mouse wheel skipping over virtual desktops, open your {{Filename|~/.config/openbox/rc.xml}} file and move the mouse binds with actions "DesktopPrevious" and "DesktopNext" from the context "Desktop" to the context "Root" (you may need to define the Root context).<br />
<br />
If you want to use the Openbox root-menu instead of Xfce's, you may terminate Xfdesktop by running the following command in a terminal:<br />
$ xfdesktop --quit<br />
<br />
However, Xfdesktop manages the wallpaper and desktop icons, requiring you to use other utilities, such as ROX, for these functions.<br />
<br />
(When terminating Xfdesktop, the above issue with the virtual desktops is no longer a problem.)<br />
<br />
== Preferences ==<br />
<br />
Currently, there are two options for configuring the core Openbox preferences; manually edit the {{Filename|rc.xml}}, or use the ObConf tool.<br />
<br />
=== Manual configuration ===<br />
<br />
To configure Openbox manually, simply edit {{Filename|~/.config/openbox/rc.xml}} with your favorite text editor. The config file provides plenty of comments throughout, and [http://openbox.org/wiki/Configuration full documentation] is available at the official website.<br />
<br />
=== ObConf ===<br />
<br />
[http://icculus.org/openbox/index.php/ObConf:About ObConf] is GUI-based Openbox configuration tool, which can be used to set most preferences including themes, virtual desktops, window properties and desktop margins.<br />
<br />
To install ObConf, run:<br />
# pacman -S obconf<br />
<br />
{{Note | ObConf cannot be used to configure keyboard shortcuts and some other advanced features. For these modifications, you must edit {{Filename|rc.xml}} manually (see above). Other option is [http://code.google.com/p/obkey/ ObKey] application (available in [[AUR]]).}}<br />
<br />
=== Application configuration ===<br />
<br />
Openbox features per-application settings, allowing you to define rules for your programs. For example, you can:<br />
* load your web browser on a certain desktop<br />
* load your terminal without a window border<br />
* load your torrent client at a certain position on your screen<br />
<br />
These are defined in {{Filename|~/.config/openbox/rc.xml}}. As you might expect, the instructions are well-documented within the file itself. Full details can also be found here: http://openbox.org/wiki/Help:Applications<br />
<br />
== Menus ==<br />
<br />
The default Openbox menu includes a variety of applications to get you started, but you'll probably want to customize this at some point. There are a number of ways to do so:<br />
<br />
=== Manual configuration ===<br />
<br />
Similar to the {{Filename|rc.xml}} file, you can edit {{Filename|~/.config/openbox/menu.xml}} with your favourite text editor. Although many of the settings are self-explanatory, [http://openbox.org/wiki/Help:Menus full documentation] is available.<br />
<br />
=== MenuMaker ===<br />
<br />
[http://menumaker.sourceforge.net/ MenuMaker] is a powerful tool that creates XML-based menus for a variety of Window Managers, including Openbox. MenuMaker will search your computer for executable programs and create an XML menu based on the results. It can be configured to exclude Legacy X, GNOME, KDE, or Xfce applications if the user desires.<br />
<br />
MenuMaker is available in the community repository:<br />
# pacman -S menumaker<br />
<br />
Once installed, you can generate a complete menu by running:<br />
$ mmaker -v OpenBox3<br />
<br />
By default, MenuMaker will not overwrite an existing menu.xml. To do so, run it with the -f (force) argument:<br />
<br />
$ mmaker -vf OpenBox3<br />
<br />
To see a full list of options, run {{Codeline|mmaker --help}}.<br />
<br />
This will give you a pretty thorough menu. Now you can modify the menu.xml by hand, or simply regenerate the list whenever you install new software.<br />
<br />
=== Obmenu ===<br />
<br />
Obmenu is a GUI-based menu editor for Openbox. For those who don't enjoy editing XML source code, this is probably the best option for you.<br />
<br />
It is available in the community repository:<br />
# pacman -S obmenu<br />
<br />
Once installed, simply run {{Codeline|obmenu}} and add or remove the desired applications.<br />
<br />
==== Obm-xdg ====<br />
<br />
<tt>obm-xdg</tt> is a command-line tool that comes with Obmenu. It can generate a categorized sub-menu of installed GTK/GNOME applications.<br />
<br />
To use obm-xdg, add the following line to {{Filename|~/.config/openbox/menu.xml}}:<br />
<menu execute="obm-xdg" id="xdg-menu" label="xdg"/><br />
<br />
If your {{Filename|~/.config/openbox/menu.xml}} does not exist, add these lines:<br />
<openbox_menu><br />
<menu execute="obm-xdg" id="root-menu" label="apps"/><br />
</openbox_menu><br />
<br />
Then run {{Codeline|openbox --reconfigure}} to refresh the Openbox menu. You should now see a sub-menu labeled '''xdg''' in your menu.<br />
<br />
{{Note | If you do not have GNOME installed, then you need to install '''gnome-menus''' package for obm-xdg to work.}}<br />
<br />
=== Python based xdg menu script ===<br />
<br />
This script can be found in Fedora's Openbox package. You will only have to put the script somewhere and add a menu entry.<br />
<br />
Here is my paste: http://pastebin.com/f2f827625<br />
And here is the head: http://pkgs.fedoraproject.org/gitweb/?p=openbox.git;f=xdg-menu;hb=HEAD<br />
<br />
Download the one you like (maybe you'll prefer the head version of course). You can put the file anywhere, I used ~/Documents/build/xdg-menu (just modify the menu entry later according to YOUR filename/path.)<br />
<br />
Then open your menu.xml with your favourite text editor and add the following entry where you want the new menu (of course, you can modify the label however you want):<br />
<menu id="apps-menu" label="xdgmenu" execute="python /home/shiki/Documents/build/xdg-menu"/><br />
<br />
Save the file, and run: {{Codeline|openbox --reconfigure}}.<br />
<br />
=== OpenBox Menu Generator ===<br />
<br />
OpenBox Menu Generator, avaliable in the AUR as [http://aur.archlinux.org/packages.php?ID=27300 obmenugen-bin] is a menu generator for OpenBox using the *.desktop files. It provides a text file to filter using basic regex which menu items are hidden.<br />
To use, simply run:<br />
$ obmenugen<br />
Then update OpenBox by:<br />
$ openbox --reconfigure<br />
<br />
=== Pipe menus ===<br />
<br />
Openbox (and other WMs like WindowMaker and PekWM) allow you to write scripts that dynamically build menus on the fly. Some examples are system monitors, media player controls, and weather forecasts. Many examples can be found on the openbox [http://openbox.org/wiki/Openbox:Pipemenus site].<br />
<br />
Xyne has also created a file browser and brisbin33 has one for scanning for / connecting to wireless hot spots (requires netcfg). The relevant forum posts for these utilities are [http://bbs.archlinux.org/viewtopic.php?id=77197&p=1 here] and [http://bbs.archlinux.org/viewtopic.php?id=78290 here]<br />
<br />
== Startup programs ==<br />
<br />
Openbox features support for running programs at startup. This is provided by the "openbox-session" command.<br />
<br />
There are two ways to enable autostart:<br />
# If you use startx/xinit to log into your X session, edit {{Filename|~/.xinitrc}} and change the line that executes ''openbox'' to execute '''openbox-session''' instead.<br />
# If you log in with GDM/KDM, then select the ''Openbox'' session and it will automatically use autostart.<br />
<br />
Startup programs are managed in {{Filename|~/.config/openbox/autostart.sh}}. Full instructions and best practices for how to do this are available at the [http://openbox.org/wiki/Help:Autostart Openbox website].<br />
<br />
== Themes and appearance ==<br />
<br />
With the exception of the Openbox Themes topic, the following section is intended for users who have configured Openbox to run as a standalone desktop, without the assistance of GNOME, KDE or Xfce.<br />
<br />
=== Openbox themes ===<br />
<br />
Openbox themes control the appearance of window borders, including the titlebar and titlebar buttons. They also determine the appearance of the application menu and on-screen display (OSD). <br />
<br />
Additional themes are available from the standard repositories:<br />
<br />
# pacman -S openbox-themes<br />
<br />
This package is by no means definitive. You can download more themes at websites such as:<br />
*[http://www.box-look.org/index.php?xcontentmode=7402 box-look.org]<br />
*[http://customize.org/browse/tags/openbox customize.org]<br />
*http://www.minuslab.net/themes/<br />
*http://celo.wordpress.com/themes/<br />
*http://vault.openmonkey.com/pages/openbox<br />
*http://hewphoria.com/?p=submission&type=theme&cat=7<br />
<br />
Downloaded themes should be extracted to <tt>~/.themes</tt> and can be installed or selected with the [[Openbox#Preferences|ObConf]] tool.<br />
<br />
Creating new themes is fairly easy and again [http://openbox.org/wiki/Help:Themes well-documented].<br />
<br />
For a GUI theme editor, take a look at [http://xyne.archlinux.ca/info/obtheme ObTheme].<br />
<br />
=== X11 Appearance ===<br />
<br />
If you are running Openbox as a standalone, you will need to configure .Xdefaults file.<br />
Save a copy to ~/.Xdefaults and /home/root/.Xdefaults for windows opened as Root.<br />
<br />
Xdefaults is a user-level configuration dotfile, typically located at ~/.Xdefaults. When present, it is parsed by the xrdb (Xorg resource database) program automatically when Xorg is started, and can be used to set or override preferences for X and X applications. It can do many operations, including:<br />
<br />
- defining terminal colours<br />
- configuring terminal preferences<br />
- setting DPI, antialiasing, hinting and other X font settings<br />
- changing the Xcursor theme<br />
- theming xscreensaver<br />
- altering preferences on low-level X applications (xclock, xpdf, etc.) <br />
<br />
Xdefaults Arch WiKi<br />
http://wiki.archlinux.org/index.php/Xdefaults<br />
<br />
=== X11 Mouse cursors ===<br />
<br />
Extract the desired Xcursor theme to either <tt>/usr/share/icons</tt> (system-wide access) or <tt>~/.icons</tt> (local user access). There are also a limited amount of themes available in the community repository that can be installed using pacman.<br />
<br />
Add this to {{Filename|~/.Xdefaults}}:<br />
Xcursor.theme: [name-of-cursor-theme]<br />
where {{Codeline|[name-of-cursor-theme]}} is the name of the cursor theme directory. For example:<br />
Xcursor.theme: Vanilla-DMZ-AA<br />
To change the size:<br />
Xcursor.size: [size]<br />
Sometimes it is required to symlink the icon directory into each user directory to make the window manager use them:<br />
$ mkdir ~/.icons<br />
$ ln -s /usr/share/icons/[name-of-cursor-theme] ~/.icons/default<br />
<br />
For more information read the Arch WiKi<br />
http://wiki.archlinux.org/index.php/X11_Cursors<br />
<br />
=== GTK Themes ===<br />
<br />
==== GTK2/GTK+ ====<br />
<br />
First, extract the desired theme to <tt>/usr/share/themes</tt> (system-wide access) or <tt>~/.themes</tt> (local user access), then:<br />
<br />
GTK+ themes can be managed easily with the '''[[LXDE | lxappearance]]''', '''gtk-chtheme''', or '''switch2''' utilities. To install, run:<br />
# pacman -S lxappearance<br />
and/or<br />
# pacman -S gtk-chtheme<br />
and/or<br />
# pacman -S gtk-theme-switch2<br />
<br />
Now you can simply run {{Codeline|lxappearance}}, {{Codeline|gtk-chtheme}} or {{Codeline|switch2}} to set the desired theme.<br />
<br />
==== GTK1 ====<br />
For legacy GTK1 themes, install the '''gtk-theme-switch''' package:<br />
# pacman -S gtk-theme-switch<br />
Then run {{Codeline|switch}} to select a desired theme.<br />
<br />
==== GTK fonts ====<br />
<br />
To manually change the type and size of your fonts, add the following to {{Filename|~/.gtkrc.mine}}:<br />
style "user-font"<br />
{<br />
font_name = "[font-name] [size]"<br />
}<br />
widget_class "*" style "user-font"<br />
gtk-font-name = "[font-name] [size]"<br />
<br />
where {{Codeline|[font-name] [size]}} is the desired font and point size. For example:<br />
style "user-font"<br />
{<br />
font_name = "DejaVu Sans 8"<br />
}<br />
widget_class "*" style "user-font"<br />
gtk-font-name = "DejaVu Sans 8"<br />
<br />
Both {{Codeline|font_name}} and {{Codeline|gtk-font-name}} fields are required for backwards compatibility.<br />
<br />
You can also use '''gtk-chtheme''' or '''lxappearance''' to set GTK font settings. Please refer to the above section.<br />
<br />
==== GTK Icons ====<br />
<br />
First, extract the desired icon theme to <tt>/usr/share/icons</tt> (system-wide access) or <tt>~/.icons</tt> (local user access), then:<br />
<br />
Add the following to {{Filename|~/.gtkrc.mine}}: <br />
gtk-icon-theme-name = "[name-of-icon-theme]"<br />
<br />
where {{Codeline|[name-of-icon-theme]}} is the name of the icon theme directory. For example:<br />
gtk-icon-theme-name = "Tango"<br />
<br />
Ensure {{Filename|~/.gtkrc-2.0}} is configured to parse {{Filename|~/.gtkrc.mine}}:<br />
<br />
# ~/.gtkrc-2.0<br />
# -- THEME AUTO-WRITTEN DO NOT EDIT<br />
include "/usr/share/themes/Rezlooks-Gilouche/gtk-2.0/gtkrc"<br />
include "/home/username/.gtkrc.mine"<br />
# -- THEME AUTO-WRITTEN DO NOT EDIT<br />
<br />
You can use '''lxappearance''' to choose GTK icon themes. Please refer to the above section.<br />
You can also use [http://aur.archlinux.org/packages.php?ID=39339 lxappearance2-git] from the AUR to handle the Mouse Cursor, GTK Theme and Icon Theme and Colour Scheme. If you also install the optional [http://aur.archlinux.org/packages.php?ID=40223 lxappearance-obconf-git] as well, you can configure Openbox's Window Decoration settings from lxappearance as well.<br />
<br />
=== Desktop icons ===<br />
Openbox does not provide a means to display icons on the desktop. Xfdesktop, PcmanFM, [http://rox.sourceforge.net ROX], [[Idesk|iDesk]], or even Nautilus (and the gnome-settings-daemon) can provide this function. <br />
<br />
ROX and PCmanFM have the additional advantage of being lightweight file managers.<br />
<br />
=== Desktop wallpaper ===<br />
<br />
Openbox itself does not include a way to change the wallpaper. This can be done easily with programs like [[Feh]] or [[Nitrogen]]. Other options include ImageMagick, hsetroot and xsetbg. Or Pcmanfm and Xfdesktop can do it too.<br />
<br />
You can disable the wallpaper loading in gnome-settings-daemon like this:<br />
$ gconftool-2 --set /apps/gnome_settings_daemon/plugins/background/active --type bool False<br />
<br />
== Recommended programs ==<br />
<br />
There is a [[Lightweight Applications|list of Lightweight Software]] at Arch's wiki; most of it nicely fits with Openbox.<br />
<br />
=== Login managers ===<br />
<br />
[http://slim.berlios.de/ SLiM] provides a lightweight and elegant graphical login solution for standalone Openbox configurations. Refer to Arch's [[SLiM]] wiki for detailed instructions.<br />
<br />
[http://qingy.sourceforge.net/ Qingy] is ultralight and very configurable graphical login. It support login to both console and X Windows sessions. It uses [http://www.directfb.org DirectFB], therefore it does not start X Windows unless you choose X Windows session. See article about [[Qingy]] at Arch's wiki.<br />
<br />
=== Composite desktop ===<br />
<br />
[[Xcompmgr]] is a lightweight composite manager capable of rendering drop shadows, fading and simple window transparency within Openbox and other window managers.<br />
(It's worth noting that xcompmgr is no longer developed, and so any issues are unlikely to be fixed)<br />
(Developed an issue with tint2 0.9, the systray icons have a tendency to corrupt)<br />
<br />
[[Cairo Compmgr | Cairo Composite Manager]] -- A versatile and extensible composite manager which uses cairo for rendering, is an alternative.<br />
<br />
=== Panels, trays, and pagers ===<br />
<br />
There are quite a lot of utilities available that provide a panel (taskbar), system tray, and pager to Openbox. The most common are:<br />
<br />
==== Panels ====<br />
* [[PyPanel]]<br />
* [http://nsf.110mb.com/bmpanel/ BMPanel]<br />
* [[tint2]]<br />
* [http://www.gnomefiles.org/app.php/LXPanel LXPanel]<br />
* [http://fbpanel.sourceforge.net fbpanel]<br />
* [http://freshmeat.net/projects/perlpanel/ PerlPanel]<br />
* [http://www.chatjunkies.org/fspanel/ fspanel]<br />
* [http://www.xfce.org/projects/xfce4-panel/ Xfce4-panel]<br />
* [http://live.gnome.org/GnomePanel/ GnomePanel]<br />
* [[Avant Window Navigator]]<br />
* [http://developer.berlios.de/projects/cairo-dock/ cairo-dock]<br />
* [http://code.google.com/p/wbar/ wbar]<br />
* [http://www.screenlets.org/ screenlets]<br />
* [http://www.failedprojects.de/pancake/ pancake]<br />
<br />
==== Trays ====<br />
* [http://stalonetray.sourceforge.net/ Stalonetray]<br />
* [http://download.gna.org/fvwm-crystal/trayer/1.0/ Trayer]<br />
<br />
==== Pagers ====<br />
* [http://projects.l3ib.org/trac/visibility Visibility]<br />
* [http://bbtools.sourceforge.net/ bbpager]<br />
* [http://aur.archlinux.org/packages.php?ID=17563 netwmpager]<br />
* [http://useperl.ru/ipager/index.en.html IPager]<br />
* [http://code.google.com/p/neap/ neap]<br />
<br />
Make your choice and add it to your startup file. If you wish to set the desktop layout without using a pager, you can use [http://aur.archlinux.org/packages.php?ID=34376 obsetlayout], which is a packaged version of the setlayout tool from the Openbox wiki.<br />
<br />
=== File managers ===<br />
<br />
There are many possibilities, but the most popular lightweight file managers are:<br />
* [[Thunar]]. Thunar supports auto-mount features and other plugins. <br />
* [http://rox.sourceforge.net ROX] (ROX provides desktop icons)<br />
# pacman -S rox<br />
* [http://pcmanfm.sourceforge.net PCManFM] (pcmanfm also provides desktop icons)<br />
# pacman -S pcmanfm<br />
To access NTFS drives with PCManFM, install ntfs-3g:<br />
# pacman -S ntfs-3g<br />
For even lighter options, consider [http://www.obsession.se/gentoo/ Gentoo] or [http://emelfm2.net/ emelFM2], both of which use the familiar 'Midnight Commander' two pane layout.<br />
<br />
Others:<br />
Xfe<br />
muCommander<br />
''(Will edit it later after I have tried them both.)''<br />
<br />
Of course, you can also use GNOME's Nautilus. Although slower than the above solutions, it has the additional advantage of VFS support (e.g. remote SSH, FTP and Samba connections)<br />
<br />
=== Application launchers ===<br />
<br />
==== dmenu ====<br />
<br />
Set-up dmenu as described in the [[dmenu]] wiki article. Then, add the following entry to the <keyboard> section {{Filename|~/.config/openbox/rc.xml}} to enable a shortcut to launch dmenu:<br />
<keybind key="W-space"><br />
<action name="Execute"><br />
<execute>dmenu_run</execute><br />
</action><br />
</keybind><br />
<br />
==== [[Gmrun]] ====<br />
<br />
[http://sourceforge.net/projects/gmrun gmrun] provides an excellent Run dialog box, similar to the Alt+F2 features found in Gnome and KDE:<br />
# pacman -S gmrun<br />
For details regarding Gmrun, see the wiki article [[Gmrun|here]].<br />
Add the following entry to the <keyboard> section {{Filename|~/.config/openbox/rc.xml}} to enable Alt+F2 functionality:<br />
<keybind key="A-F2"><br />
<action name="execute"><execute>gmrun</execute></action><br />
</keybind><br />
<br />
==== Bashrun2 ====<br />
<br />
[http://bashrun.sourceforge.net bashrun2] provides a different, barebones approach to a run dialog, using a specialized bash session within a small xterm window. It is available in the [http://aur.archlinux.org/packages.php?ID=43465 AUR] and can be launched through the Alt+F2 style approach mentioned previously. To make bashrun2 act more like a traditional run dialog, add the following entry to the <applications> section {{Filename|~/.config/openbox/rc.xml}}:<br />
<application name="bashrun2-run-dialog"><br />
<desktop>all</desktop><br />
<decor>no</decor> # switch to yes if you prefer a bordered window<br />
<focus>yes</focus><br />
<skip_pager>yes</skip_pager><br />
<layer>above</layer><br />
</application><br />
<br />
==== Kupfer ====<br />
<br />
[https://aur.archlinux.org/packages.php?ID=27896 Kupfer] is a launcher inspired by Quicksilver, written in Python.<br />
<br />
"You use it to summon an application or document quickly by typing the first parts of its name. It can also do more than getting at something quickly: there are different plugins for accessing more objects and running custom commands."<br />
<br />
==== Launchy ====<br />
<br />
[http://www.launchy.net/ Launchy] is a less minimalistic approach; it is skinnable and offers more functionality such as a calculator, checking the weather, etc. Originally for Windows, similar to Gnome Do.<br />
# pacman -S launchy<br />
It is launched by Ctrl+Space key combination.<br />
<br />
==== LXPanel ====<br />
<br />
The LXPanel run dialog can be executed with <br />
lxpanelctl run<br />
<br />
==== gnome-panel ====<br />
<br />
The gnome-panel run dialog can be executed with <br />
gnome-panel-control --run-dialog<br />
<br />
=== Clipboard managers ===<br />
<br />
You may wish to install a clipboard manager for feature rich copy/paste ability. '''xfce4-clipman-plugin, parcellite,''' or '''glipper-old''' may be installed via pacman. Add your choice to autostart.sh. From the terminal, Ctrl+Insert as copy and Shift+Insert as paste generally works as well. You may also copy from terminal with Ctrl+Shift+C, and paste with mouse middle click.<br />
<br />
=== Volume managers ===<br />
<br />
==== gvolwheel ====<br />
<br />
a lightweight audio mixer which lets you control the audio volume through a tray icon [http://aur.archlinux.org/packages.php?ID=25502] <br />
<br />
==== gvtray ====<br />
<br />
A master volume mixer in the system tray [http://aur.archlinux.org/packages.php?ID=6362]<br />
<br />
==== obmixer ====<br />
<br />
Obmixer is a mixer appplet written in C which is intended to be a lightweight alternative to gnome volume control [http://aur.archlinux.org/packages.php?ID=31131]<br />
<br />
==== volti ====<br />
<br />
GTK+ application for controlling audio volume from system tray/notification area [http://aur.archlinux.org/packages.php?ID=33525]<br />
<br />
==== volumeicon ====<br />
<br />
Volume control for your system tray [http://aur.archlinux.org/packages.php?ID=35793]<br />
<br />
==== volwheel ====<br />
<br />
Tray icon to change volume with the mouse [http://www.archlinux.org/packages/community/any/volwheel/]<br />
<br />
=== Keyboard layout switchers ===<br />
<br />
==== fbxkb ====<br />
<br />
Keyboard indicator and switcher [http://aur.archlinux.org/packages.php?ID=3458]<br />
<br />
==== xxkb ====<br />
<br />
keyboard layout switcher/indicator [http://www.archlinux.org/packages/community/i686/xxkb/]<br />
<br />
==== axkb ====<br />
<br />
QT4 keyboard layout switcher [http://aur.archlinux.org/packages.php?ID=25555]<br />
<br />
==== xneur ====<br />
<br />
X Neural Switcher is a text analyser, it detects the language of input and corrects it if needed [http://aur.archlinux.org/packages.php?ID=9750]<br />
<br />
== Tips and tricks ==<br />
<br />
=== File associations ===<br />
Since Openbox and the applications you are going to use with it are not very well integrated you might run into the issue that your browser does not know which program it is supposed to use for certain types of files. The package in the AUR [http://aur.archlinux.org/packages.php?ID=23170 gnome-defaults-list] contains a list of file-types and programs specific to the gnome desktop. It will be installed to<br />
/etc/gnome/defaults.list<br />
Open it with your text-editor and now you can search & replace everything with your appropriate programs. Like totem<=>vlc or eog<=>mirage. Save the file to:<br />
~/.local/share/applications/defaults.list<br />
<br />
Another way is to use the package ''perl-file-mimeinfo'' from the repositories, and invoke the mimeopen command like this:<br />
mimeopen -d /path/to/file<br />
You will then be asked what application to use when opening /path/to/file:<br />
Please choose a default application for files of type text/plain<br />
1) notepad (wine-extension-txt)<br />
2) Leafpad (leafpad)<br />
3) OpenOffice.org Writer (writer)<br />
4) gVim (gvim)<br />
5) Other...<br />
Your answer will be set as the default handler for that type of file.<br />
If you can't find mimeopen, it is installed as:<br />
/usr/bin/perlbin/vendor/mimetype<br />
<br />
=== Copy and paste ===<br />
<br />
From the terminal, Ctrl+Insert as copy and Shift+Insert as paste generally works as well. You may also copy from terminal with Ctrl+Shift+C, and paste with mouse middle click.<br />
<br />
=== Transparency ===<br />
<br />
By using the program transset-df, it is virtually the same as [[transset]], (available by: pacman -S transset-df) you can enable transparancy of windows on the fly. For instance by editing the following in {{Filename|~/.config/openbox/rc.xml}} you can have your middle mouse scroll enable and disable transparency by scrolling down and up on the scroll button, respectively, while over the title bar (it is in the <mouse> section):<br />
<context name="Titlebar"><br />
<mousebind button="Left" action="Press"><br />
<action name="Focus"/><br />
<action name="Raise"/><br />
</mousebind><br />
<mousebind button="Left" action="Drag"><br />
<action name="Move"/><br />
</mousebind><br />
<mousebind button="Left" action="DoubleClick"><br />
<action name="ToggleMaximizeFull"/><br />
</mousebind><br />
<mousebind button="Middle" action="Press"><br />
<action name="Lower"/> <br />
<action name="FocusToBottom"/><br />
<action name="Unfocus"/><br />
</mousebind><br />
<mousebind button="Up" action="Click"><br />
<action name= "Execute" ><br />
<execute>transset-df -p .2 --inc </execute><br />
</action><br />
</mousebind><br />
<mousebind button="Down" action="Click"><br />
<action name= "Execute" ><br />
<execute>transset-df -p .2 --dec </execute><br />
</action><br />
</mousebind><br />
<mousebind button="Right" action="Press"><br />
<action name="Focus"/><br />
<action name="Raise"/><br />
<action name="ShowMenu"><br />
<menu>client-menu</menu><br />
</action><br />
</mousebind><br />
</context><br />
As of now, it only appears to work when no other actions are taken.<br />
<br />
=== Xprop values for applications ===<br />
If you use per-application settings frequently, you might find this bash alias handy:<br />
<br />
alias xp='xprop | grep "WM_WINDOW_ROLE\|WM_CLASS" && echo "WM_CLASS(STRING) = \"NAME\", \"CLASS\""'<br />
<br />
To use, run '''{{Codeline|xp}}''' and click on the running program that you'd like to define with per-app settings. The result will display only the info that Openbox requires, namely the WM_WINDOW_ROLE and WM_CLASS (name and class) values:<br />
<br />
[thayer@dublin:~] $ xp<br />
WM_WINDOW_ROLE(STRING) = "roster"<br />
WM_CLASS(STRING) = "gajim.py", "Gajim.py"<br />
WM_CLASS(STRING) = "NAME", "CLASS"<br />
<br />
==== Xprop for Firefox ====<br />
<br />
For whatever reason, Firefox and its open source equivalents will ignore application rules (e.g. <desktop>) unless {{Codeline|class&#61;"Firefox*"}} is used, regardless of what xprop reports as the actual WM_CLASS values.<br />
<br />
=== Linking the menu to a command ===<br />
<br />
Some people would want to link the Openbox main menu, or any other, to a command. This is useful for creating a menu button in a panel, for example. Although Openbox doesn't support this, a very simple script, xdotool, can simulate a keypress by running a command. Xdotool is [http://aur.archlinux.org/packages.php?do_Details=1&ID=14789&O=0&L=0&C=0&K=xdotool&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd available on AUR]. To use it, simply add the following code to the <keyboard> section of your {{Filename|rc.xml}}:<br />
<keybind key="A-C-q"><br />
<action name="ShowMenu"><br />
<menu>root-menu</menu><br />
</action><br />
</keybind><br />
Restart/reconfigure Openbox. You can now magically summon your menu at your cursor position by running the following command:<br />
# xdotool key ctrl+alt+q<br />
Of course, you can change the shortcut to your liking.<br />
<br />
=== Urxvt in the background ===<br />
<br />
With Openbox, running a terminal as desktop background is easy. You won't need '''devilspie''' here.<br />
<br />
First you must enable transparency, open your {{Filename|.Xdefaults}} file (if it doesn't exist yet, create it in your home folder).<br />
URxvt*transparent:true<br />
URxvt*scrollBar:false<br />
URxvt*geometry:124x24 #I don't use the whole screen, if you want a full screen term don't bother with this and see below.<br />
URxvt*borderLess:true<br />
URxvt*foreground:Black #Font color. My wallpaper is White, you may wish to change this to White.<br />
<br />
Then edit your {{Filename|.config/openbox/rc.xml}} file:<br />
<application name="URxvt"><br />
<decor>no</decor><br />
<focus>yes</focus><br />
<position><br />
<x>center</x><br />
<y>20</y><br />
</position><br />
<layer>below</layer><br />
<desktop>all</desktop><br />
<maximized>true</maximized> #Only if you want a full size terminal.<br />
</application><br />
<br />
The ''magic'' comes from the {{Codeline|<layer>below</layer>}} line, which place the application under all others. Here Urxvt is displayed on all desktops, change it to your convenience.<br />
<br />
Note: Instead of using <application name="URxvt">, you can use another name ("URxvt-bg" for example), and use the -name option when starting uxrvt. That way, only the urxvt terminals which you choose to name URxvt-bg would be captured and modified by the application rule in rc.xml. For example: urxvt -name URxvt-bg (case sensitive)<br />
<br />
====ToggleShowDesktop exception====<br />
Above method still minimizes Urxvt when using the ToggleShowDesktop command. A method for avoiding this is explained in this [https://bbs.archlinux.org/viewtopic.php?pid=865844#p865844 forum post]. This involves editing Urxvt's source code.<br />
<br />
=== Keyboard Volume Control ===<br />
If you use ALSA for sound, you can use the amixer program to adjust the volume of sound. You can use Openbox's keybindings to act like multimedia keys. (Alternatively, you can probably find out the names of your real multimedia keys and map them.) For example, in the <keyboard> section of rc.xml:<br />
<br />
<keybind key="W-Up"><br />
<action name="Execute"><br />
<command>amixer set Master 5%+</command><br />
</action><br />
</keybind><br />
<br />
This binds Windows key + Up arrow to increase your master ALSA volume by 5%. Corresponding binding for volume down:<br />
<br />
<keybind key="W-Down"><br />
<action name="Execute"><br />
<command>amixer set Master 5%-</command><br />
</action><br />
</keybind><br />
<br />
As another example you can also use the XF86Audio keybindings:<br />
<br />
<keybind key="XF86AudioRaiseVolume"><br />
<action name="Execute"><br />
<command>amixer set Master 5%+ unmute</command><br />
</action><br />
</keybind><br />
<keybind key="XF86AudioLowerVolume"><br />
<action name="Execute"><br />
<command>amixer set Master 5%- unmute</command><br />
</action><br />
</keybind><br />
<keybind key="XF86AudioMute"><br />
<action name="Execute"><br />
<command>amixer set Master toggle</command><br />
</action><br />
</keybind><br />
<br />
The above example should work for the majority of multimedia keyboards. It should enable to raise, lower and mute the Master control of your audio device by using the respective multimedia keyboard keys. Notice also that in this example:<br />
<br />
* The "Mute" key should unmute the Master control if it is already in mute mode.<br />
* The "Raise" and "Lower" keys should unmute the Master control if it is in mute mode.<br />
<br />
== Resources ==<br />
<br />
* [http://openbox.org/ Openbox Website] &ndash; The official website<br />
* [http://planetob.openmonkey.com/ Planet Openbox] &ndash; Openbox news portal<br />
* [http://www.box-look.org/ Box-Look.org] &ndash; A good resource for themes and related artwork<br />
* [https://bbs.archlinux.org/viewtopic.php?id=93126 Openbox Hacks and Configs Thread] @ Arch Linux Forums<br />
* [https://bbs.archlinux.org/viewtopic.php?id=45692 Openbox Screenshots Thread] @ Arch Linux Forums<br />
<!-- vim: set ft=Wikipedia: --></div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Beginners%27_guide_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=125681Beginners' guide (正體中文)2010-12-21T03:55:32Z<p>Taylorchu: </p>
<hr />
<div>{{translateme}}{{stub}}<br />
<br />
參考資料<br />
<br />
[http://tailinchu.tk/bbs/viewtopic.php?id=7 archlinux簡易安裝]<br />
<br />
[http://tailinchu.tk/bbs/viewtopic.php?id=123 archlinux高階安裝(openbox)]<br />
<br />
[http://tailinchu.tk/bbs/viewtopic.php?id=8 必裝套件]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Beginners%27_guide_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=125511Beginners' guide (正體中文)2010-12-18T00:48:15Z<p>Taylorchu: </p>
<hr />
<div>{{translateme}}{{stub}}<br />
<br />
參考資料<br />
<br />
[http://tiik.org.ru/forum/viewtopic.php?id=7 archlinux簡易安裝]<br />
<br />
[http://tiik.org.ru/forum/viewtopic.php?id=123 archlinux高階安裝(openbox)]<br />
<br />
[http://tiik.org.ru/forum/viewtopic.php?id=8 必裝套件]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Beginners%27_guide_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=125510Beginners' guide (正體中文)2010-12-18T00:46:28Z<p>Taylorchu: /* 安裝軟體 */</p>
<hr />
<div>{{translateme}}{{stub}}<br />
這篇筆記是給archlinux新手使用, 完全避免archlinux在安裝時需要的複雜設定 ,在20分鐘內讓你有一個linux桌面<br />
<br />
[http://tiik.org.ru/forum/viewtopic.php?id=7 archlinux簡易安裝]<br />
[http://tiik.org.ru/forum/viewtopic.php?id=123 archlinux高階安裝(openbox)]<br />
[http://tiik.org.ru/forum/viewtopic.php?id=8 必裝套件]</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Beginners%27_guide_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=125509Beginners' guide (正體中文)2010-12-18T00:43:52Z<p>Taylorchu: /* 安裝完成 */</p>
<hr />
<div>{{translateme}}{{stub}}<br />
這篇筆記是給archlinux新手使用, 完全避免archlinux在安裝時需要的複雜設定 ,在20分鐘內讓你有一個linux桌面<br />
<br />
== 安裝軟體 ==<br />
<br />
一口氣弄完吧<br />
輸入root登入<br />
輸入 pacman -Syu 注意大小寫<br />
接著就簡單了<br />
我建議用gnome<br />
因為比kde4小些, 比xfce4開發步調快, 比lxde穩<br />
開始吧, 請按照順序<br />
<br />
1. 安裝桌面<br />
<br />
pacman -S xorg gnome gnome-terminal gdm gamin<br />
<br />
<br />
會等上一段時間<br />
<br />
請稍等10分鐘<br />
說明: xorg - x windows 必裝<br />
<br />
gnome - gnome 圖形化桌面<br />
<br />
gnome-terminal - 在gnome中用終端機<br />
<br />
gamin - 取代 fam<br />
<br />
gdm - gnome 的登入畫面<br />
<br />
<br />
2. 音效驅動<br />
<br />
pacman -S alsa-utils<br />
<br />
3. 顯卡驅動<br />
<br />
一般先裝intel<br />
pacman -S xf86-video-intel<br />
<br />
4. 開機時載入<br />
<br />
nano /etc/rc.conf<br />
<br />
再最下面的再最下面的daemon 加上 alsa dbus gdm <br />
<br />
DAEMONS = ( ... alsa dbus gdm)<br />
<br />
5. 加入使用者<br />
<br />
root不建議使用<br />
輸入adduser<br />
輸入你的id<br />
按enter直到要輸入password<br />
<br />
6. 中文化<br />
<br />
pacman -S wqy-zenhei gcin<br />
<br />
nano /etc/rc.conf<br />
<br />
把locale的en_US改成zh_TW<br />
<br />
nano /etc/locale.gen<br />
<br />
找到 zh_TW.utf-8把這行最前面的#去掉<br />
<br />
退出後 locale-gen<br />
<br />
7. 雜七雜八<br />
<br />
pacman -S 你要的軟體<br />
[http://tiik.org.ru/forum/viewtopic.php?id=8 必裝套件]<br />
<br />
8. reboot</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Beginners%27_guide_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=125508Beginners' guide (正體中文)2010-12-18T00:43:14Z<p>Taylorchu: /* 安裝開始 */</p>
<hr />
<div>{{translateme}}{{stub}}<br />
這篇筆記是給archlinux新手使用, 完全避免archlinux在安裝時需要的複雜設定 ,在20分鐘內讓你有一個linux桌面<br />
<br />
== 安裝完成 ==<br />
<br />
目前archlinux的文字介面已安裝完成,但是你開機時會嚇到<br />
因為還是文字介面,請繼續安裝<br />
<br />
<br />
== 安裝軟體 ==<br />
<br />
一口氣弄完吧<br />
輸入root登入<br />
輸入 pacman -Syu 注意大小寫<br />
接著就簡單了<br />
我建議用gnome<br />
因為比kde4小些, 比xfce4開發步調快, 比lxde穩<br />
開始吧, 請按照順序<br />
<br />
1. 安裝桌面<br />
<br />
pacman -S xorg gnome gnome-terminal gdm gamin<br />
<br />
<br />
會等上一段時間<br />
<br />
請稍等10分鐘<br />
說明: xorg - x windows 必裝<br />
<br />
gnome - gnome 圖形化桌面<br />
<br />
gnome-terminal - 在gnome中用終端機<br />
<br />
gamin - 取代 fam<br />
<br />
gdm - gnome 的登入畫面<br />
<br />
<br />
2. 音效驅動<br />
<br />
pacman -S alsa-utils<br />
<br />
3. 顯卡驅動<br />
<br />
一般先裝intel<br />
pacman -S xf86-video-intel<br />
<br />
4. 開機時載入<br />
<br />
nano /etc/rc.conf<br />
<br />
再最下面的再最下面的daemon 加上 alsa dbus gdm <br />
<br />
DAEMONS = ( ... alsa dbus gdm)<br />
<br />
5. 加入使用者<br />
<br />
root不建議使用<br />
輸入adduser<br />
輸入你的id<br />
按enter直到要輸入password<br />
<br />
6. 中文化<br />
<br />
pacman -S wqy-zenhei gcin<br />
<br />
nano /etc/rc.conf<br />
<br />
把locale的en_US改成zh_TW<br />
<br />
nano /etc/locale.gen<br />
<br />
找到 zh_TW.utf-8把這行最前面的#去掉<br />
<br />
退出後 locale-gen<br />
<br />
7. 雜七雜八<br />
<br />
pacman -S 你要的軟體<br />
[http://tiik.org.ru/forum/viewtopic.php?id=8 必裝套件]<br />
<br />
8. reboot</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Beginners%27_guide_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=125507Beginners' guide (正體中文)2010-12-18T00:42:58Z<p>Taylorchu: /* ArchLinux的優點 */</p>
<hr />
<div>{{translateme}}{{stub}}<br />
這篇筆記是給archlinux新手使用, 完全避免archlinux在安裝時需要的複雜設定 ,在20分鐘內讓你有一個linux桌面<br />
<br />
== 安裝開始 ==<br />
<br />
1. ArchLinux安裝ISO在官網上有兩種 <br />
一個是Core另一個是FTP,差別在Core可以在一開始就安裝完基礎系統 ,而FTP本身檔案比較小,它透過網路來安裝所有的套件 。<br />
<br />
這裡我使用FTP版,因為ArchLinux的更新太頻繁了 ,通常過了一兩個月,你的基礎系統套件幾乎全更新了 。<br />
所以像現在我們選擇由FTP安裝其實還比較快一點!<br />
[http://www.archlinux.org/download/ 下載netboot版本]<br />
<br />
2. 開機後輸入root登入 <br />
<br />
再輸入/arch/setup進入安裝程式<br />
<br />
3. 由於我是用網路安裝,這裡我們必須選擇FTP/HTTP安裝模式<br />
<br />
在設定網路的過程,會詢問要由哪個鏡像站更新<br />
<br />
選擇選擇kernel.org的站台<br />
<br />
4. 調整或新增硬碟分區<br />
<br />
選擇自己分區<br />
<br />
如果記憶體大的話就不用swap<br />
<br />
檔案系統格式用檔案系統格式用最新的ext4<br />
<br />
接著接著,退出指定剛才格式化區域<br />
<br />
會出現warning可忽略<br />
<br />
5. 回到主選單,選擇安裝套件<br />
<br />
直接用base複雜設定, 按ok開始安裝<br />
<br />
此時會從網路下載最新的package<br />
<br />
會等上一段時間,請稍等5分鐘<br />
<br />
6. 按continue回主選單<br />
<br />
開始設定<br />
<br />
選擇簡單的nano編輯器<br />
<br />
nano的控制比較特殊: ^X 就是 Ctrl + x<br />
<br />
找到 /etc/pacman.d/mirrorlist<br />
<br />
把kernel.org兩行的開頭 # 去掉<br />
<br />
按Ctrl + x 退出, 按y確認 , 按enter儲存<br />
<br />
暫時先這樣<br />
<br />
按done後,archlinux開始設定<br />
<br />
7. 安裝開機引導程式 <br />
<br />
選擇GRUB作為開機引導程式<br />
<br />
選擇之後它會跳出fstab掛載的情況 <br />
<br />
按^x退出<br />
<br />
詢問GRUB要裝在那 <br />
<br />
一般建議安裝在MBR,這裡我選擇裝在/dev/sda <br />
<br />
大致上告一段落了,跳回主選單離開安裝程式<br />
<br />
8. 輸入 reboott安裝完成<br />
<br />
== 安裝完成 ==<br />
<br />
目前archlinux的文字介面已安裝完成,但是你開機時會嚇到<br />
因為還是文字介面,請繼續安裝<br />
<br />
<br />
== 安裝軟體 ==<br />
<br />
一口氣弄完吧<br />
輸入root登入<br />
輸入 pacman -Syu 注意大小寫<br />
接著就簡單了<br />
我建議用gnome<br />
因為比kde4小些, 比xfce4開發步調快, 比lxde穩<br />
開始吧, 請按照順序<br />
<br />
1. 安裝桌面<br />
<br />
pacman -S xorg gnome gnome-terminal gdm gamin<br />
<br />
<br />
會等上一段時間<br />
<br />
請稍等10分鐘<br />
說明: xorg - x windows 必裝<br />
<br />
gnome - gnome 圖形化桌面<br />
<br />
gnome-terminal - 在gnome中用終端機<br />
<br />
gamin - 取代 fam<br />
<br />
gdm - gnome 的登入畫面<br />
<br />
<br />
2. 音效驅動<br />
<br />
pacman -S alsa-utils<br />
<br />
3. 顯卡驅動<br />
<br />
一般先裝intel<br />
pacman -S xf86-video-intel<br />
<br />
4. 開機時載入<br />
<br />
nano /etc/rc.conf<br />
<br />
再最下面的再最下面的daemon 加上 alsa dbus gdm <br />
<br />
DAEMONS = ( ... alsa dbus gdm)<br />
<br />
5. 加入使用者<br />
<br />
root不建議使用<br />
輸入adduser<br />
輸入你的id<br />
按enter直到要輸入password<br />
<br />
6. 中文化<br />
<br />
pacman -S wqy-zenhei gcin<br />
<br />
nano /etc/rc.conf<br />
<br />
把locale的en_US改成zh_TW<br />
<br />
nano /etc/locale.gen<br />
<br />
找到 zh_TW.utf-8把這行最前面的#去掉<br />
<br />
退出後 locale-gen<br />
<br />
7. 雜七雜八<br />
<br />
pacman -S 你要的軟體<br />
[http://tiik.org.ru/forum/viewtopic.php?id=8 必裝套件]<br />
<br />
8. reboot</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Beginners%27_guide_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=123581Beginners' guide (正體中文)2010-12-03T02:41:32Z<p>Taylorchu: /* 安裝軟體 */</p>
<hr />
<div>這篇筆記是給archlinux新手使用, 完全避免archlinux在安裝時需要的複雜設定 ,在20分鐘內讓你有一個linux桌面<br />
<br />
== ArchLinux的優點 ==<br />
<br />
1. i686優化<br />
<br />
2. 只裝你需要的<br />
<br />
3. 無縫升級<br />
<br />
4. 高度的自訂性<br />
<br />
5. 享受最新的linux軟體<br />
<br />
== 安裝開始 ==<br />
<br />
1. ArchLinux安裝ISO在官網上有兩種 <br />
一個是Core另一個是FTP,差別在Core可以在一開始就安裝完基礎系統 ,而FTP本身檔案比較小,它透過網路來安裝所有的套件 。<br />
<br />
這裡我使用FTP版,因為ArchLinux的更新太頻繁了 ,通常過了一兩個月,你的基礎系統套件幾乎全更新了 。<br />
所以像現在我們選擇由FTP安裝其實還比較快一點!<br />
[http://www.archlinux.org/download/ 下載netboot版本]<br />
<br />
2. 開機後輸入root登入 <br />
<br />
再輸入/arch/setup進入安裝程式<br />
<br />
3. 由於我是用網路安裝,這裡我們必須選擇FTP/HTTP安裝模式<br />
<br />
在設定網路的過程,會詢問要由哪個鏡像站更新<br />
<br />
選擇選擇kernel.org的站台<br />
<br />
4. 調整或新增硬碟分區<br />
<br />
選擇自己分區<br />
<br />
如果記憶體大的話就不用swap<br />
<br />
檔案系統格式用檔案系統格式用最新的ext4<br />
<br />
接著接著,退出指定剛才格式化區域<br />
<br />
會出現warning可忽略<br />
<br />
5. 回到主選單,選擇安裝套件<br />
<br />
直接用base複雜設定, 按ok開始安裝<br />
<br />
此時會從網路下載最新的package<br />
<br />
會等上一段時間,請稍等5分鐘<br />
<br />
6. 按continue回主選單<br />
<br />
開始設定<br />
<br />
選擇簡單的nano編輯器<br />
<br />
nano的控制比較特殊: ^X 就是 Ctrl + x<br />
<br />
找到 /etc/pacman.d/mirrorlist<br />
<br />
把kernel.org兩行的開頭 # 去掉<br />
<br />
按Ctrl + x 退出, 按y確認 , 按enter儲存<br />
<br />
暫時先這樣<br />
<br />
按done後,archlinux開始設定<br />
<br />
7. 安裝開機引導程式 <br />
<br />
選擇GRUB作為開機引導程式<br />
<br />
選擇之後它會跳出fstab掛載的情況 <br />
<br />
按^x退出<br />
<br />
詢問GRUB要裝在那 <br />
<br />
一般建議安裝在MBR,這裡我選擇裝在/dev/sda <br />
<br />
大致上告一段落了,跳回主選單離開安裝程式<br />
<br />
8. 輸入 reboott安裝完成<br />
<br />
== 安裝完成 ==<br />
<br />
目前archlinux的文字介面已安裝完成,但是你開機時會嚇到<br />
因為還是文字介面,請繼續安裝<br />
<br />
<br />
== 安裝軟體 ==<br />
<br />
一口氣弄完吧<br />
輸入root登入<br />
輸入 pacman -Syu 注意大小寫<br />
接著就簡單了<br />
我建議用gnome<br />
因為比kde4小些, 比xfce4開發步調快, 比lxde穩<br />
開始吧, 請按照順序<br />
<br />
1. 安裝桌面<br />
<br />
pacman -S xorg gnome gnome-terminal gdm gamin<br />
<br />
<br />
會等上一段時間<br />
<br />
請稍等10分鐘<br />
說明: xorg - x windows 必裝<br />
<br />
gnome - gnome 圖形化桌面<br />
<br />
gnome-terminal - 在gnome中用終端機<br />
<br />
gamin - 取代 fam<br />
<br />
gdm - gnome 的登入畫面<br />
<br />
<br />
2. 音效驅動<br />
<br />
pacman -S alsa-utils<br />
<br />
3. 顯卡驅動<br />
<br />
一般先裝intel<br />
pacman -S xf86-video-intel<br />
<br />
4. 開機時載入<br />
<br />
nano /etc/rc.conf<br />
<br />
再最下面的再最下面的daemon 加上 alsa dbus gdm <br />
<br />
DAEMONS = ( ... alsa dbus gdm)<br />
<br />
5. 加入使用者<br />
<br />
root不建議使用<br />
輸入adduser<br />
輸入你的id<br />
按enter直到要輸入password<br />
<br />
6. 中文化<br />
<br />
pacman -S wqy-zenhei gcin<br />
<br />
nano /etc/rc.conf<br />
<br />
把locale的en_US改成zh_TW<br />
<br />
nano /etc/locale.gen<br />
<br />
找到 zh_TW.utf-8把這行最前面的#去掉<br />
<br />
退出後 locale-gen<br />
<br />
7. 雜七雜八<br />
<br />
pacman -S 你要的軟體<br />
[http://tiik.org.ru/forum/viewtopic.php?id=8 必裝套件]<br />
<br />
8. reboot</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Beginners%27_guide_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=123579Beginners' guide (正體中文)2010-12-03T02:16:00Z<p>Taylorchu: /* 安裝軟體 */</p>
<hr />
<div>這篇筆記是給archlinux新手使用, 完全避免archlinux在安裝時需要的複雜設定 ,在20分鐘內讓你有一個linux桌面<br />
<br />
== ArchLinux的優點 ==<br />
<br />
1. i686優化<br />
<br />
2. 只裝你需要的<br />
<br />
3. 無縫升級<br />
<br />
4. 高度的自訂性<br />
<br />
5. 享受最新的linux軟體<br />
<br />
== 安裝開始 ==<br />
<br />
1. ArchLinux安裝ISO在官網上有兩種 <br />
一個是Core另一個是FTP,差別在Core可以在一開始就安裝完基礎系統 ,而FTP本身檔案比較小,它透過網路來安裝所有的套件 。<br />
<br />
這裡我使用FTP版,因為ArchLinux的更新太頻繁了 ,通常過了一兩個月,你的基礎系統套件幾乎全更新了 。<br />
所以像現在我們選擇由FTP安裝其實還比較快一點!<br />
[http://www.archlinux.org/download/ 下載netboot版本]<br />
<br />
2. 開機後輸入root登入 <br />
<br />
再輸入/arch/setup進入安裝程式<br />
<br />
3. 由於我是用網路安裝,這裡我們必須選擇FTP/HTTP安裝模式<br />
<br />
在設定網路的過程,會詢問要由哪個鏡像站更新<br />
<br />
選擇選擇kernel.org的站台<br />
<br />
4. 調整或新增硬碟分區<br />
<br />
選擇自己分區<br />
<br />
如果記憶體大的話就不用swap<br />
<br />
檔案系統格式用檔案系統格式用最新的ext4<br />
<br />
接著接著,退出指定剛才格式化區域<br />
<br />
會出現warning可忽略<br />
<br />
5. 回到主選單,選擇安裝套件<br />
<br />
直接用base複雜設定, 按ok開始安裝<br />
<br />
此時會從網路下載最新的package<br />
<br />
會等上一段時間,請稍等5分鐘<br />
<br />
6. 按continue回主選單<br />
<br />
開始設定<br />
<br />
選擇簡單的nano編輯器<br />
<br />
nano的控制比較特殊: ^X 就是 Ctrl + x<br />
<br />
找到 /etc/pacman.d/mirrorlist<br />
<br />
把kernel.org兩行的開頭 # 去掉<br />
<br />
按Ctrl + x 退出, 按y確認 , 按enter儲存<br />
<br />
暫時先這樣<br />
<br />
按done後,archlinux開始設定<br />
<br />
7. 安裝開機引導程式 <br />
<br />
選擇GRUB作為開機引導程式<br />
<br />
選擇之後它會跳出fstab掛載的情況 <br />
<br />
按^x退出<br />
<br />
詢問GRUB要裝在那 <br />
<br />
一般建議安裝在MBR,這裡我選擇裝在/dev/sda <br />
<br />
大致上告一段落了,跳回主選單離開安裝程式<br />
<br />
8. 輸入 reboott安裝完成<br />
<br />
== 安裝完成 ==<br />
<br />
目前archlinux的文字介面已安裝完成,但是你開機時會嚇到<br />
因為還是文字介面,請繼續安裝<br />
<br />
<br />
== 安裝軟體 ==<br />
<br />
一口氣弄完吧<br />
輸入root登入<br />
輸入 pacman -Syu 注意大小寫<br />
接著就簡單了<br />
我建議用gnome<br />
因為比kde4小些, 比xfce4開發步調快, 比lxde穩<br />
開始吧, 請按照順序<br />
<br />
1. 安裝桌面<br />
<br />
pacman -S xorg gnome gnome-terminal gdm gamin<br />
<br />
<br />
會等上一段時間<br />
<br />
請稍等10分鐘<br />
說明: xorg - x windows 必裝<br />
<br />
gnome - gnome 圖形化桌面<br />
<br />
gnome-terminal - 在gnome中用終端機<br />
<br />
gamin - 取代 fam<br />
<br />
gdm - gnome 的登入畫面<br />
<br />
<br />
2. 音效驅動<br />
<br />
pacman -S alsa-utils<br />
<br />
3. 顯卡驅動<br />
<br />
一般先裝intel<br />
pacman -S xf86-video-intel<br />
<br />
4. 開機時載入<br />
<br />
nano /etc/rc.conf<br />
<br />
再最下面的再最下面的daemon 加上 alsa dbus gdm <br />
<br />
DAEMONS = ( ... alsa dbus gdm)<br />
<br />
5. 加入使用者<br />
<br />
root不建議使用<br />
輸入adduser<br />
輸入你的id<br />
按enter直到要輸入password<br />
<br />
6. 中文化<br />
<br />
pacman -S wqy-zenhei scim-chewing<br />
<br />
nano /etc/rc.conf<br />
<br />
把locale的en_US改成zh_TW<br />
<br />
nano /etc/locale.gen<br />
<br />
找到 zh_TW.utf-8把這行最前面的#去掉<br />
<br />
退出後 locale-gen<br />
<br />
7. 雜七雜八<br />
<br />
pacman -S 你要的軟體<br />
[http://tiik.org.ru/forum/viewtopic.php?id=8 必裝套件]<br />
<br />
8. reboot</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Beginners%27_guide_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=120127Beginners' guide (正體中文)2010-10-28T00:51:56Z<p>Taylorchu: /* 安裝開始 */</p>
<hr />
<div>這篇筆記是給archlinux新手使用, 完全避免archlinux在安裝時需要的複雜設定 ,在20分鐘內讓你有一個linux桌面<br />
<br />
== ArchLinux的優點 ==<br />
<br />
1. i686優化<br />
<br />
2. 只裝你需要的<br />
<br />
3. 無縫升級<br />
<br />
4. 高度的自訂性<br />
<br />
5. 享受最新的linux軟體<br />
<br />
== 安裝開始 ==<br />
<br />
1. ArchLinux安裝ISO在官網上有兩種 <br />
一個是Core另一個是FTP,差別在Core可以在一開始就安裝完基礎系統 ,而FTP本身檔案比較小,它透過網路來安裝所有的套件 。<br />
<br />
這裡我使用FTP版,因為ArchLinux的更新太頻繁了 ,通常過了一兩個月,你的基礎系統套件幾乎全更新了 。<br />
所以像現在我們選擇由FTP安裝其實還比較快一點!<br />
[http://www.archlinux.org/download/ 下載netboot版本]<br />
<br />
2. 開機後輸入root登入 <br />
<br />
再輸入/arch/setup進入安裝程式<br />
<br />
3. 由於我是用網路安裝,這裡我們必須選擇FTP/HTTP安裝模式<br />
<br />
在設定網路的過程,會詢問要由哪個鏡像站更新<br />
<br />
選擇選擇kernel.org的站台<br />
<br />
4. 調整或新增硬碟分區<br />
<br />
選擇自己分區<br />
<br />
如果記憶體大的話就不用swap<br />
<br />
檔案系統格式用檔案系統格式用最新的ext4<br />
<br />
接著接著,退出指定剛才格式化區域<br />
<br />
會出現warning可忽略<br />
<br />
5. 回到主選單,選擇安裝套件<br />
<br />
直接用base複雜設定, 按ok開始安裝<br />
<br />
此時會從網路下載最新的package<br />
<br />
會等上一段時間,請稍等5分鐘<br />
<br />
6. 按continue回主選單<br />
<br />
開始設定<br />
<br />
選擇簡單的nano編輯器<br />
<br />
nano的控制比較特殊: ^X 就是 Ctrl + x<br />
<br />
找到 /etc/pacman.d/mirrorlist<br />
<br />
把kernel.org兩行的開頭 # 去掉<br />
<br />
按Ctrl + x 退出, 按y確認 , 按enter儲存<br />
<br />
暫時先這樣<br />
<br />
按done後,archlinux開始設定<br />
<br />
7. 安裝開機引導程式 <br />
<br />
選擇GRUB作為開機引導程式<br />
<br />
選擇之後它會跳出fstab掛載的情況 <br />
<br />
按^x退出<br />
<br />
詢問GRUB要裝在那 <br />
<br />
一般建議安裝在MBR,這裡我選擇裝在/dev/sda <br />
<br />
大致上告一段落了,跳回主選單離開安裝程式<br />
<br />
8. 輸入 reboott安裝完成<br />
<br />
== 安裝完成 ==<br />
<br />
目前archlinux的文字介面已安裝完成,但是你開機時會嚇到<br />
因為還是文字介面,請繼續安裝<br />
<br />
<br />
== 安裝軟體 ==<br />
<br />
一口氣弄完吧<br />
輸入root登入<br />
輸入 pacman -Syu 注意大小寫<br />
接著就簡單了<br />
我建議用gnome<br />
因為比kde4小些, 比xfce4開發步調快, 比lxde穩<br />
開始吧, 請按照順序<br />
<br />
1. 安裝桌面<br />
<br />
pacman -S xorg gnome gnome-terminal gdm gamin<br />
<br />
<br />
會等上一段時間<br />
<br />
請稍等10分鐘<br />
說明: xorg - x windows 必裝<br />
<br />
gnome - gnome 圖形化桌面<br />
<br />
gnome-terminal - 在gnome中用終端機<br />
<br />
gamin - 取代 fam<br />
<br />
gdm - gnome 的登入畫面<br />
<br />
<br />
2. 音效驅動<br />
<br />
pacman -S alsa-utils<br />
<br />
3. 顯卡驅動<br />
<br />
一般先裝intel<br />
pacman -S xf86-video-intel<br />
<br />
4. 開機時載入<br />
<br />
nano /etc/rc.conf<br />
<br />
再最下面的再最下面的daemon 加上 alsa hal gdm <br />
<br />
DAEMONS = ( ... alsa hal gdm)<br />
<br />
<br />
5. 加入使用者<br />
<br />
root不建議使用<br />
輸入adduser<br />
輸入你的id<br />
按enter直到要輸入password<br />
<br />
6. 中文化<br />
<br />
pacman -S wqy-zenhei scim-chewing<br />
<br />
nano /etc/rc.conf<br />
<br />
把locale的en_US改成zh_TW<br />
<br />
nano /etc/locale.gen<br />
<br />
找到 zh_TW.utf-8把這行最前面的#去掉<br />
<br />
退出後 locale-gen<br />
<br />
7. 雜七雜八<br />
<br />
pacman -S 你要的軟體<br />
[http://tiik.org.ru/forum/viewtopic.php?id=8 必裝套件]<br />
<br />
8. reboot</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Beginners%27_guide_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=120126Beginners' guide (正體中文)2010-10-28T00:49:55Z<p>Taylorchu: Created page with "這篇筆記是給archlinux新手使用, 完全避免archlinux在安裝時需要的複雜設定 ,在20分鐘內讓你有一個linux桌面 == ArchLinux的優點 == 1. i686優化..."</p>
<hr />
<div>這篇筆記是給archlinux新手使用, 完全避免archlinux在安裝時需要的複雜設定 ,在20分鐘內讓你有一個linux桌面<br />
<br />
== ArchLinux的優點 ==<br />
<br />
1. i686優化<br />
<br />
2. 只裝你需要的<br />
<br />
3. 無縫升級<br />
<br />
4. 高度的自訂性<br />
<br />
5. 享受最新的linux軟體<br />
<br />
== 安裝開始 ==<br />
<br />
1. ArchLinux安裝ISO在官網上有兩種 <br />
一個是Core另一個是FTP,差別在Core可以在一開始就安裝完基礎系統 ,而FTP本身檔案比較小,它透過網路來安裝所有的套件 。<br />
<br />
這裡我使用FTP版,因為ArchLinux的更新太頻繁了 ,通常過了一兩個月,你的基礎系統套件幾乎全更新了 。<br />
所以像現在我們選擇由FTP安裝其實還比較快一點!<br />
[http://www.archlinux.org/download/ 下載netboott版本]<br />
<br />
2. 開機後輸入root登入 <br />
<br />
再輸入/arch/setup進入安裝程式<br />
3. 由於我是用網路安裝,這裡我們必須選擇FTP/HTTP安裝模式<br />
在設定網路的過程,會詢問要由哪個鏡像站更新<br />
選擇選擇kernel.org的站台<br />
<br />
4. 調整或新增硬碟分區<br />
<br />
選擇自己分區<br />
如果記憶體大的話就不用swap<br />
檔案系統格式用檔案系統格式用最新的ext4<br />
接著接著,退出指定剛才格式化區域<br />
會出現warning可忽略<br />
<br />
5. 回到主選單,選擇安裝套件<br />
<br />
直接用base複雜設定, 按ok開始安裝<br />
此時會從網路下載最新的package<br />
會等上一段時間<br />
請稍等5分鐘<br />
<br />
6. 按continue回主選單<br />
<br />
開始設定<br />
選擇簡單的nano編輯器<br />
nano的控制比較特殊: ^X 就是 Ctrl + x<br />
找到 /etc/pacman.d/mirrorlist<br />
把kernel.org兩行的開頭 # 去掉<br />
按Ctrl + x 退出, 按y確認 , 按enter儲存<br />
暫時先這樣<br />
按done後後archlinux開始設定<br />
<br />
6. 安裝開機引導程式 <br />
<br />
選擇GRUB作為開機引導程式<br />
選擇之後它會跳出fstab掛載的情況 <br />
按^x退出<br />
詢問GRUB要裝在那 <br />
一般建議安裝在MBR,這裡我選擇裝在/dev/sda <br />
大致上告一段落了,跳回主選單離開安裝程式<br />
<br />
7. 輸入 reboott安裝完成<br />
<br />
<br />
== 安裝完成 ==<br />
<br />
目前archlinux的文字介面已安裝完成,但是你開機時會嚇到<br />
因為還是文字介面,請繼續安裝<br />
<br />
<br />
== 安裝軟體 ==<br />
<br />
一口氣弄完吧<br />
輸入root登入<br />
輸入 pacman -Syu 注意大小寫<br />
接著就簡單了<br />
我建議用gnome<br />
因為比kde4小些, 比xfce4開發步調快, 比lxde穩<br />
開始吧, 請按照順序<br />
<br />
1. 安裝桌面<br />
<br />
pacman -S xorg gnome gnome-terminal gdm gamin<br />
<br />
<br />
會等上一段時間<br />
<br />
請稍等10分鐘<br />
說明: xorg - x windows 必裝<br />
<br />
gnome - gnome 圖形化桌面<br />
<br />
gnome-terminal - 在gnome中用終端機<br />
<br />
gamin - 取代 fam<br />
<br />
gdm - gnome 的登入畫面<br />
<br />
<br />
2. 音效驅動<br />
<br />
pacman -S alsa-utils<br />
<br />
3. 顯卡驅動<br />
<br />
一般先裝intel<br />
pacman -S xf86-video-intel<br />
<br />
4. 開機時載入<br />
<br />
nano /etc/rc.conf<br />
<br />
再最下面的再最下面的daemon 加上 alsa hal gdm <br />
<br />
DAEMONS = ( ... alsa hal gdm)<br />
<br />
<br />
5. 加入使用者<br />
<br />
root不建議使用<br />
輸入adduser<br />
輸入你的id<br />
按enter直到要輸入password<br />
<br />
6. 中文化<br />
<br />
pacman -S wqy-zenhei scim-chewing<br />
<br />
nano /etc/rc.conf<br />
<br />
把locale的en_US改成zh_TW<br />
<br />
nano /etc/locale.gen<br />
<br />
找到 zh_TW.utf-8把這行最前面的#去掉<br />
<br />
退出後 locale-gen<br />
<br />
7. 雜七雜八<br />
<br />
pacman -S 你要的軟體<br />
[http://tiik.org.ru/forum/viewtopic.php?id=8 必裝套件]<br />
<br />
8. reboot</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Arch_Linux_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=120125Arch Linux (正體中文)2010-10-28T00:41:45Z<p>Taylorchu: /* 中文資料 */</p>
<hr />
<div>[[Category:正體中文]]<br />
[[Category:General 正體中文]]<br />
{{i18n|Arch Linux}}<br />
Arch Linux是一個獨立發展的i686/x86-64 GNU/Linux發行版,基於輪轉發行模型(rolling-release model),Arch Linux提供一個豐富的套件庫、完整的套件管理機制和類似ports的套件系統,適合具備基本能力的GNU/Linux使用者。Arch Linux的發展專注於簡約(minimalism)、 典雅(elegance)、正確的程式碼(code-correctness)和現代性(modernity)。Arch Linux 0.1版(代號Homer)在2002年3月11日釋出。<br />
<br />
== 優勢 ==<br />
Arch Linux系統安裝完成後僅具備一個精簡的環境。Arch Linux非常的輕巧、靈活、簡單和UNIX-like,其設計哲學使其能夠很輕易的變成任何你想要的系統,無論是一個簡單的終端機機器,或是一個具備各種功能的桌面環境,Arch Linux具有相當高的可塑性,Arch Linux並不會限制使用者在安裝時一併安裝預設套件,而是讓使用者從一個基礎的系統建立一個專屬的系統,只有使用者才有權力決定Arch Linux該長什麼樣子、該有什麼功能!<br />
<br />
== 獨一無二的套件管理程式 ==<br />
<br />
Arch Linux使用的由C語言編寫、輕巧、快速、易於使用的套件管理程式pacman,透過pacman你甚至可以只用一道指令就升級整個系統。Arch也提供類似ports的套件建置系統ABS([[Arch Build System (正體中文)|Arch Build System]]),這表示您可以非常簡單地從原始碼編譯、建立和安裝套件。有了pacman和ABS,所有的工作都能在極為簡潔和透明的過程中完成。Arch Linux的輪轉發行模型也讓您不必在對系統做整體升級時重新下載和安裝整套系統──只需透過pacman下載某些經重大更新後的套件,就能讓您的系統保持在最新且最穩定的狀態。<br />
<br />
== 最新與最穩定 ==<br />
在輪轉發行模型的幫助下,Arch開發團隊努力地將所有套件維持在最新的版本。我們提供了相當精簡的core套件庫給最為精簡的i686或x86-64系統,而開發者或使用者向套件庫提供的各種高品質的擴充套件,此外還有眾多利於使用者從原始碼編譯和包裝任何套件的PKGBUILD腳本。Arch Linux所提供的大部分是來源可信、經作者正式發布、非經補強的穩定套件。但在某些極少發生的特定情況之下,舊的套件有可能會因為版本相容的問題而導致輪轉發行模型無法針對這個套件作升級或補強,此時為了維持系統的順利運作,我們才會發布補強套件進行修補。<br />
<br />
Arch也應用了許多已被GNU/Linux支援的新技術,例如ext 2/3/4 、Reiser、XFS、JFS檔案系統、LVM2/EVMS磁碟管理系統、軟體RAID、udev支援、initcpio和最新的Linux核心等。<br />
<br />
== 簡單就是美 ==<br />
[[The Arch Way (正體中文)|Arch Linux的設計哲學]]之一即'''簡單就是美'''。即便Arch Linux的基本系統非常地輕巧與迷你,但GNU工具、一些有用的擴充命令工具如'''Vi'''和'''links'''卻一個也沒少。這些實用的工具對使用者擴充Arch成為較為適合自己的版本這件事情大有幫助。<br />
<br />
Arch的init框架的設計靈感來自於*BSD系列將所有的資訊集合於一個檔案([[rc.conf]])中的設計,避免使用包含大量符號連結( symlinks )的資料夾中讀取設定。而大多數的系統設定可透過編輯簡單的文字設定檔完成。<br />
<br />
== 其他參考資料 ==<br />
<br />
Arch Linux的官方網站在[http://www.archlinux.org/ ArchLinux.org]。在官方網站上你也可以找到其他相關資源的連接,例如官方提供的[http://bbs.archlinux.org/ 使用者論壇],官方文件和其他Arch Linux的相關資源。你也可以參閱[[The Arch Way (正體中文)|Arch Linux 的設計哲學]]這一篇文章了解更多關於Arch Linux的資訊與設計哲學。<br />
<br />
== 中文資料 ==<br />
中文方面的資料目前可分為正體中文(台灣)和簡體(中國大陸)兩部分。<br />
<br />
正體中文的部分主要是由[http://cle.linux.org.tw CLE]負責。目前提供的資源有官方ftp的mirror,一個討論區和一個wiki來作中文方面得資源整合。<br />
<br />
另一個正體中文的討論區為[http://tiik.org.ru/forum/viewforum.php?id=10 提克論壇ArchLinux],包含最新的簡易的安裝和設定說明。<br />
<br />
簡體中文主要是由[http://www.linuxsir.org Linuxsir]來負責。目前提供了一個入口網頁作中文資源整合,和一個討論區。</div>Taylorchuhttps://wiki.archlinux.org/index.php?title=Arch_Linux_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=120124Arch Linux (正體中文)2010-10-28T00:41:25Z<p>Taylorchu: /* 中文資料 */</p>
<hr />
<div>[[Category:正體中文]]<br />
[[Category:General 正體中文]]<br />
{{i18n|Arch Linux}}<br />
Arch Linux是一個獨立發展的i686/x86-64 GNU/Linux發行版,基於輪轉發行模型(rolling-release model),Arch Linux提供一個豐富的套件庫、完整的套件管理機制和類似ports的套件系統,適合具備基本能力的GNU/Linux使用者。Arch Linux的發展專注於簡約(minimalism)、 典雅(elegance)、正確的程式碼(code-correctness)和現代性(modernity)。Arch Linux 0.1版(代號Homer)在2002年3月11日釋出。<br />
<br />
== 優勢 ==<br />
Arch Linux系統安裝完成後僅具備一個精簡的環境。Arch Linux非常的輕巧、靈活、簡單和UNIX-like,其設計哲學使其能夠很輕易的變成任何你想要的系統,無論是一個簡單的終端機機器,或是一個具備各種功能的桌面環境,Arch Linux具有相當高的可塑性,Arch Linux並不會限制使用者在安裝時一併安裝預設套件,而是讓使用者從一個基礎的系統建立一個專屬的系統,只有使用者才有權力決定Arch Linux該長什麼樣子、該有什麼功能!<br />
<br />
== 獨一無二的套件管理程式 ==<br />
<br />
Arch Linux使用的由C語言編寫、輕巧、快速、易於使用的套件管理程式pacman,透過pacman你甚至可以只用一道指令就升級整個系統。Arch也提供類似ports的套件建置系統ABS([[Arch Build System (正體中文)|Arch Build System]]),這表示您可以非常簡單地從原始碼編譯、建立和安裝套件。有了pacman和ABS,所有的工作都能在極為簡潔和透明的過程中完成。Arch Linux的輪轉發行模型也讓您不必在對系統做整體升級時重新下載和安裝整套系統──只需透過pacman下載某些經重大更新後的套件,就能讓您的系統保持在最新且最穩定的狀態。<br />
<br />
== 最新與最穩定 ==<br />
在輪轉發行模型的幫助下,Arch開發團隊努力地將所有套件維持在最新的版本。我們提供了相當精簡的core套件庫給最為精簡的i686或x86-64系統,而開發者或使用者向套件庫提供的各種高品質的擴充套件,此外還有眾多利於使用者從原始碼編譯和包裝任何套件的PKGBUILD腳本。Arch Linux所提供的大部分是來源可信、經作者正式發布、非經補強的穩定套件。但在某些極少發生的特定情況之下,舊的套件有可能會因為版本相容的問題而導致輪轉發行模型無法針對這個套件作升級或補強,此時為了維持系統的順利運作,我們才會發布補強套件進行修補。<br />
<br />
Arch也應用了許多已被GNU/Linux支援的新技術,例如ext 2/3/4 、Reiser、XFS、JFS檔案系統、LVM2/EVMS磁碟管理系統、軟體RAID、udev支援、initcpio和最新的Linux核心等。<br />
<br />
== 簡單就是美 ==<br />
[[The Arch Way (正體中文)|Arch Linux的設計哲學]]之一即'''簡單就是美'''。即便Arch Linux的基本系統非常地輕巧與迷你,但GNU工具、一些有用的擴充命令工具如'''Vi'''和'''links'''卻一個也沒少。這些實用的工具對使用者擴充Arch成為較為適合自己的版本這件事情大有幫助。<br />
<br />
Arch的init框架的設計靈感來自於*BSD系列將所有的資訊集合於一個檔案([[rc.conf]])中的設計,避免使用包含大量符號連結( symlinks )的資料夾中讀取設定。而大多數的系統設定可透過編輯簡單的文字設定檔完成。<br />
<br />
== 其他參考資料 ==<br />
<br />
Arch Linux的官方網站在[http://www.archlinux.org/ ArchLinux.org]。在官方網站上你也可以找到其他相關資源的連接,例如官方提供的[http://bbs.archlinux.org/ 使用者論壇],官方文件和其他Arch Linux的相關資源。你也可以參閱[[The Arch Way (正體中文)|Arch Linux 的設計哲學]]這一篇文章了解更多關於Arch Linux的資訊與設計哲學。<br />
<br />
== 中文資料 ==<br />
中文方面的資料目前可分為正體中文(台灣)和簡體(中國大陸)兩部分。<br />
<br />
正體中文的部分主要是由[http://cle.linux.org.tw CLE]負責。目前提供的資源有官方ftp的mirror,一個討論區和一個wiki來作中文方面得資源整合。<br />
另一個正體中文的討論區為[http://tiik.org.ru/forum/viewforum.php?id=10 提克論壇ArchLinux],包含最新的簡易的安裝和設定說明。<br />
<br />
簡體中文主要是由[http://www.linuxsir.org Linuxsir]來負責。目前提供了一個入口網頁作中文資源整合,和一個討論區。</div>Taylorchu