website annotate en/doc/handbook/x-window.html @ rev 442

en,fr: Add tazx to handbook and tiny fix
author Christophe Lincoln <pankso@slitaz.org>
date Mon May 04 23:10:02 2009 +0200 (2009-05-04)
parents ec74ec0a4ebd
children 9b13fc8eeafd
rev   line source
paul@68 1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
paul@68 2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
paul@68 3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
paul@68 4 <head>
paul@68 5 <title>SliTaz Handbook (en) - X Window System</title>
pankso@7 6 <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" />
pankso@16 7 <meta name="description" content="slitaz English handbook X server window manager jwm openbox e17 slim login" />
pankso@7 8 <meta name="expires" content="never" />
paul@329 9 <meta name="modified" content="2009-03-25 14:00:00" />
pankso@7 10 <meta name="publisher" content="www.slitaz.org" />
paul@18 11 <meta name="author" content="Christophe Lincoln, Paul Issot" />
paul@39 12 <link rel="shortcut icon" href="favicon.ico" />
paul@68 13 <link rel="stylesheet" type="text/css" href="book.css" />
paul@68 14 </head>
paul@68 15 <body bgcolor="#ffffff">
pankso@7 16
pankso@7 17 <!-- Header and quick navigation -->
pankso@7 18 <div id="header">
paul@18 19 <div id="quicknav" align="right">
pankso@7 20 <a name="top"></a>
paul@39 21 <a href="gen-livecd.html">Generate a LiveCD flavor</a> |
paul@39 22 <a href="index.html">Table of contents</a>
pankso@7 23 </div>
paul@18 24 <h1><font color="#3e1220">SliTaz Handbook (en)</font></h1>
pankso@7 25 </div>
pankso@7 26
pankso@7 27 <!-- Content. -->
pankso@7 28 <div id="content">
pankso@7 29 <div class="content-right"></div>
pankso@7 30
paul@18 31 <h2><font color="#df8f06">X Window System</font></h2>
pankso@7 32
pankso@7 33 <ul>
paul@28 34 <li><a href="#X11">X Window System.</a></li>
pankso@442 35 <li><a href="#tazx">Tazx</a> - SliTaz X configuration tool.</li>
paul@28 36 <li><a href="#slim">Slim</a> - Simple Login Manager.</li>
paul@28 37 <li><a href="#xorg">Xorg</a> - X server.</li>
paul@149 38 <li><a href="#terminalX">Use Xvesa as X terminal</a> - Launch a
paul@149 39 graphical session from a remote machine.</li>
paul@28 40 <li><a href="#fonts">Fonts</a> - System Fonts.</li>
pankso@442 41 <li><a href="desktop.html">Openbox</a> - Window Manager.</li>
pankso@442 42 <li><a href="enlightenment.html">Enlightenment (e17).</a> - Desktop
pankso@442 43 environment.</li>
pankso@442 44 <li><a href="jwm.html">JWM</a> - Window Manager.</li>
pankso@7 45 </ul>
pankso@7 46
pankso@7 47 <a name="X11"></a>
pankso@7 48 <h3>X11 - X Window System</h3>
pankso@7 49 <p>
pankso@7 50 The X Window System or X11 provides a window manager running on
MikeDSmith25@117 51 top of a X server. SliTaz by default uses the lightweight X server called
pankso@7 52 <code>Xvesa</code> from the Xorg project (<a href="http://www.x.org/">www.x.org</a>).
pankso@7 53 Xvesa can be started with the Slim login manager or directly from a Linux console
pankso@7 54 with the command <code>startx</code>, but for this you must first disable the
pankso@7 55 Login Manager. To reconfigure your X session you can use <code>tazx</code>
pankso@7 56 as root or as the current user if you start X from the command line.
pankso@7 57 </p>
pankso@7 58
pankso@442 59 <a name="tazx"></a>
pankso@442 60 <h3>Tazx - SliTaz X configuration tool</h3>
pankso@442 61 <p>
pankso@442 62 Tazx is the configuration tool to manage your X window sessions on a
pankso@442 63 SliTaz box. Simply select a value and press OK. You can also select a
pankso@442 64 (Xorg) session by selecting a video driver best suited to your hardware.
pankso@442 65 After you first run 'startx', the configuration is saved in the executable
pankso@442 66 files ~/.xsession and ~/.xinitrc. These files are then used to start a
pankso@442 67 X session with 'startx' or via the Slim login manager. Note that these
pankso@442 68 files can be edited with a text editor.
pankso@442 69 </p>
pankso@442 70
pankso@7 71 <a name="slim"></a>
pankso@7 72 <h3>Slim - Simple Login Manager</h3>
pankso@7 73 <p>
pankso@7 74 Slim is a lightweight session manager that is very easy to configure and is
pankso@7 75 customizable using system themes. The configuration file is found in
MikeDSmith25@117 76 <code>/etc/slim.conf</code>. It defines window managers available via the
MikeDSmith25@117 77 <code>F1</code> key, the default user or theme, and the X window system parameters.
MikeDSmith25@117 78 Slim offers special user commands like <code>console</code> to help manage
pankso@7 79 the session.
pankso@7 80 </p>
pankso@7 81 <p>
pankso@7 82 In LiveCD mode you can disable Slim with the boot option <code>screen=text</code>.
pankso@7 83 On an installed system you can remove the package or delete slim from the
pankso@7 84 <code>RUN_DAEMONS</code> variable in <code>/etc/rcS.conf</code>.
pankso@7 85 </p>
pankso@7 86 <p>
pankso@7 87 More details and themes can be found on the
paul@105 88 <a href="http://slim.berlios.de/">website</a>
pankso@7 89 </p>
pankso@16 90 <h4>Default user</h4>
pankso@16 91 <p>
paul@18 92 Slim offers a way to pre-load a user login name, by default hacker is configured
paul@18 93 for convenience. You can change this by editing the Slim configuration file
paul@18 94 <code>/etc/slim.conf</code> and modifying the line <code>default_user</code> or just
paul@18 95 leave the line blank to avoid pre-loading a user name. Example:
pankso@16 96 </p>
paul@18 97 <pre class="script">default_user hacker
pankso@16 98 </pre>
pankso@7 99
paul@28 100 <a name="xorg"></a>
paul@28 101 <h3>Xorg</h3>
paul@28 102 <p>
MikeDSmith25@117 103 By default, SliTaz provides the graphical mini-server Xvesa. Xorg server is available
paul@28 104 in the packages on the mirror. Xorg is a very comprehensive server, but uses a lot more
paul@28 105 resources than Xvesa. If your resolution is supported by the mini-server and you're happy
paul@28 106 with the refresh rate, then there's no reason to use Xorg.
paul@28 107 </p>
paul@28 108 <p>
MikeDSmith25@117 109 There is no GUI configuration which means having to use the command line in console mode. The installation
paul@28 110 and configuration of the server is relatively simple and you can always go back and reuse Xvesa at any time.
paul@28 111 Xorg is distributed in modular form, which means that you'll need to install the server, a few configuration
paul@28 112 files and the right driver for your graphics card. However the <code>xorg-server</code> package has all
paul@28 113 the correct dependancies to work directly with the <code>vesa</code> driver. Minimal install:
paul@28 114 </p>
paul@28 115 <pre> # tazpkg get-install xorg-server
paul@28 116 </pre>
paul@28 117 <p>
paul@28 118 Once installed, you can go directly to the configuration or you can install the correct driver for your card
paul@28 119 (if you know it). Example using the Nvidia driver and listing all available drivers:
paul@28 120 </p>
paul@28 121 <pre> # tazpkg get-install xorg-xf86-video-nv
paul@28 122 List:
paul@28 123 # tazpkg search xorg-xf86-video
paul@28 124 </pre>
paul@28 125 <h4>Automatic configuration of the server</h4>
paul@28 126
paul@28 127 <p>To configure the Xorg server you have two options: <code>Xorg -configure</code>
paul@28 128 or the script <code>xorgconfig</code>. It is recommended that you start by using Xorg with
paul@28 129 the <code>-configure</code> option. The automatic configuration of Xorg must be done in console
paul@159 130 mode without an X-server running, this is achieved by closing all applications and windows and hitting
paul@28 131 the <code>alt-ctrl-del</code> buttons. You should now be in console mode. Now you need to run Xorg with the
paul@28 132 <code>-configure</code> option and copy the newly generated file to <code>/etc/X11</code>:
paul@28 133 </p>
pankso@442 134 <pre>
pankso@442 135 # Xorg -configure
paul@28 136 # cp /root/xorg.conf.new /etc/X11/xorg.conf
paul@28 137 </pre>
paul@28 138 <p>
pankso@442 139 Finally you then change the configuration of Slim to use Xorg instead of Xvesa
pankso@442 140 and restart the window manager.
paul@28 141 </p>
paul@28 142 <h4>Using Xorg with Slim</h4>
paul@28 143 <p>
paul@28 144 In the Slim configuration file (<code>/etc/slim.conf</code>), we need to comment out
paul@28 145 (<code>#</code>) the lines pertaining to Xvesa and change Xorg to the <code>default_xserver</code>:
paul@28 146 </p>
pankso@442 147 <pre class="script">
pankso@442 148 default_xserver /usr/bin/Xorg
paul@28 149 #default_xserver /usr/bin/Xvesa
paul@28 150 #xserver_arguments -ac -shadow dpms +extension Composite -screen 1024x768x24
paul@28 151 </pre>
paul@28 152 <p>
paul@28 153 Now we can start Slim to return us to an X server session.
paul@28 154 Slim works likes a daemon, it can be stopped or started from the console:
paul@28 155 </p>
pankso@442 156 <pre>
pankso@442 157 # /etc/init.d/slim start
paul@28 158 </pre>
paul@28 159 <h4>xorg.conf - Configuration file</h4>
paul@28 160 <p>
MikeDSmith25@117 161 Xorg uses the configuration file <code>/etc/X11/xorg.conf</code>. This file can be
MikeDSmith25@117 162 automatically generated and edited with your favorite text editor. It is divided into
paul@28 163 several sections, including the specification of paths, modules to be loaded, default screen,
MikeDSmith25@117 164 mouse, keyboard, etc. This document provides only a few examples, it is advisable to run
paul@28 165 <code>xorgconfig</code> once to generate a complete file to use as an example.
paul@28 166
paul@28 167 </p>
paul@28 168 <p>
paul@28 169 Keyboard (en):
paul@28 170 </p>
pankso@442 171 <pre class="script">
pankso@442 172 Section "InputDevice"
paul@28 173 Identifier "Keyboard0"
paul@28 174 Driver "kbd"
paul@28 175 Option "XkbRules" "xorg"
paul@28 176 Option "XkbModel" "pc105"
paul@28 177 Option "XkbLayout" "en"
paul@28 178 Option "XkbVariant" "en"
paul@28 179 EndSection
paul@28 180 </pre>
paul@28 181 <p>
paul@28 182 Mice with auto detection protocol:
paul@28 183 </p>
pankso@442 184 <pre class="script">
pankso@442 185 Section "InputDevice"
paul@28 186 Identifier "Mouse0"
paul@28 187 Driver "mouse"
paul@28 188 Option "Protocol" "auto"
paul@28 189 Option "Device" "/dev/input/mice"
paul@28 190 Option "ZAxisMapping" "4 5 6 7"
paul@28 191 EndSection
paul@28 192 </pre>
paul@28 193 <p>
paul@28 194 Composite extensions:
paul@28 195 </p>
pankso@442 196 <pre class="script">
pankso@442 197 Section "Extensions"
paul@28 198 Option "Composite" "1"
paul@28 199 EndSection
paul@28 200 </pre>
paul@28 201
paul@149 202 <a name="terminalX"></a>
paul@149 203 <h3>Use Xvesa as X terminal</h3>
paul@149 204 <p>
paul@151 205 You can use Xvesa as X terminal, if you have a machine on
paul@149 206 the network that accepts Xdmcp connections. To enable this,
paul@149 207 you can start the server with the option <code>-query</code> followed by
paul@149 208 the machine name or IP address. Example of machine 192.168.0.2
paul@149 209 on a local network:
paul@149 210 </p>
paul@149 211 <pre> $ Xvesa -ac -shadow -screen 1024x768x24 -query 192.168.0.2
paul@149 212 </pre>
paul@149 213 <p>
paul@149 214 The use of a graphical remote server can be of great use, although
paul@149 215 reponse times of applications depend greatly on Internet
paul@149 216 speed and the remote machine's power. This technique works
paul@149 217 very well within a local area network (LAN) and allows you
paul@149 218 to control applications installed on the remote machine directly
paul@150 219 from the screen of the local machine from which you work.
paul@149 220 Note that the distant remote machine may have
paul@149 221 multiple accounts in use simultaneously and/or direct access.
paul@149 222 </p>
paul@149 223
paul@18 224 <a name="fonts"></a>
hacker@20 225 <h3>Fonts</h3>
paul@18 226 <p>
paul@18 227 The management of Fonts (<em>fonts</em>) is powered by the package Fontconfig.
paul@18 228 This package provides tools to add, list and manipulate fonts. The <em>fonts</em>
paul@18 229 can be installed in user space or at the system level, this means that each user can use his/her own
paul@150 230 fonts or the system adminstrator (<em>root</em>) can install fonts available to all users of the system.
paul@150 231 If you use USB media associated with the SliTaz <a href="http://www.slitaz.org/en/doc/handbook/livecd.html">LiveCD</a>,
paul@18 232 you can easily install fonts and retain them the next time you use the cdrom.
paul@18 233 </p>
paul@18 234 <h4>Installing <em>fonts</em></h4>
paul@18 235 <p>
paul@18 236 At the system level fonts are installed in the directory:
paul@18 237 <code>/usr/share/fonts</code>, core SliTaz provides TTF Vera fonts,
paul@194 238 they take up little space and are rendered correctly. At the root of user space <code>~/</code>,
paul@151 239 fonts are found in the hidden directory: <code>.fonts</code>. To create a home
paul@151 240 directory to accomodate new fonts, you can use the graphical window manager emelFM2,
paul@151 241 Clex or the command line:
paul@18 242 </p>
paul@18 243 <pre> $ mkdir ~/.fonts
paul@18 244 </pre>
paul@18 245 <p>
hacker@20 246 Once you have installed the fonts you need to run the <code>fc-cache</code> tool to generate
hacker@20 247 configuration files, this ensures that your <em>fonts</em> are available for use in applications:
paul@18 248 </p>
paul@18 249 <pre> $ fc-cache
paul@18 250 </pre>
paul@18 251
pankso@7 252 <!-- End of content -->
pankso@7 253 </div>
pankso@7 254
pankso@7 255 <!-- Footer. -->
pankso@7 256 <div id="footer">
pankso@7 257 <div class="footer-right"></div>
pankso@7 258 <a href="#top">Top of the page</a> |
paul@68 259 <a href="index.html">Table of contents</a>
pankso@7 260 </div>
pankso@7 261
pankso@7 262 <div id="copy">
paul@18 263 Copyright © 2008 <a href="http://www.slitaz.org/en/">SliTaz</a> -
pankso@7 264 <a href="http://www.gnu.org/licenses/gpl.html">GNU General Public License</a>;<br />
pankso@7 265 Documentation is under
pankso@7 266 <a href="http://www.gnu.org/copyleft/fdl.html">GNU Free Documentation License</a>
pankso@7 267 and code is <a href="http://validator.w3.org/">valid xHTML 1.0</a>.
pankso@7 268 </div>
pankso@7 269
paul@68 270 </body>
paul@68 271 </html>
pankso@7 272