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

en: Add Xvesa Terminal to Hdbk
author Paul Issott <paul@slitaz.org>
date Sat Aug 30 18:04:04 2008 +0000 (2008-08-30)
parents a1fd009ac7b3
children 66984a972006
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" />
MikeDSmith25@117 9 <meta name="modified" content="2008-07-18 07: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>
paul@28 35 <li><a href="#slim">Slim</a> - Simple Login Manager.</li>
paul@28 36 <li><a href="#xorg">Xorg</a> - X server.</li>
paul@28 37 <li><a href="#jwm">JWM</a> - Window Manager.</li>
paul@28 38 <li><a href="#enlightenment">Enlightenment (e17).</a> - Desktop
paul@18 39 environment.</li>
pankso@16 40 <li><a href="#openbox">Openbox</a> - Window Manager.</li>
paul@149 41 <li><a href="#terminalX">Use Xvesa as X terminal</a> - Launch a
paul@149 42 graphical session from a remote machine.</li>
paul@28 43 <li><a href="#fonts">Fonts</a> - System Fonts.</li>
pankso@7 44 </ul>
pankso@7 45
pankso@7 46 <a name="X11"></a>
pankso@7 47 <h3>X11 - X Window System</h3>
pankso@7 48 <p>
pankso@7 49 The X Window System or X11 provides a window manager running on
MikeDSmith25@117 50 top of a X server. SliTaz by default uses the lightweight X server called
pankso@7 51 <code>Xvesa</code> from the Xorg project (<a href="http://www.x.org/">www.x.org</a>).
pankso@7 52 Xvesa can be started with the Slim login manager or directly from a Linux console
pankso@7 53 with the command <code>startx</code>, but for this you must first disable the
pankso@7 54 Login Manager. To reconfigure your X session you can use <code>tazx</code>
pankso@7 55 as root or as the current user if you start X from the command line.
pankso@7 56 </p>
pankso@7 57
pankso@7 58 <a name="slim"></a>
pankso@7 59 <h3>Slim - Simple Login Manager</h3>
pankso@7 60 <p>
pankso@7 61 Slim is a lightweight session manager that is very easy to configure and is
pankso@7 62 customizable using system themes. The configuration file is found in
MikeDSmith25@117 63 <code>/etc/slim.conf</code>. It defines window managers available via the
MikeDSmith25@117 64 <code>F1</code> key, the default user or theme, and the X window system parameters.
MikeDSmith25@117 65 Slim offers special user commands like <code>console</code> to help manage
pankso@7 66 the session.
pankso@7 67 </p>
pankso@7 68 <p>
pankso@7 69 In LiveCD mode you can disable Slim with the boot option <code>screen=text</code>.
pankso@7 70 On an installed system you can remove the package or delete slim from the
pankso@7 71 <code>RUN_DAEMONS</code> variable in <code>/etc/rcS.conf</code>.
pankso@7 72 </p>
pankso@7 73 <p>
pankso@7 74 More details and themes can be found on the
paul@105 75 <a href="http://slim.berlios.de/">website</a>
pankso@7 76 </p>
pankso@16 77 <h4>Default user</h4>
pankso@16 78 <p>
paul@18 79 Slim offers a way to pre-load a user login name, by default hacker is configured
paul@18 80 for convenience. You can change this by editing the Slim configuration file
paul@18 81 <code>/etc/slim.conf</code> and modifying the line <code>default_user</code> or just
paul@18 82 leave the line blank to avoid pre-loading a user name. Example:
pankso@16 83 </p>
paul@18 84 <pre class="script">default_user hacker
pankso@16 85 </pre>
pankso@7 86
paul@28 87 <a name="xorg"></a>
paul@28 88 <h3>Xorg</h3>
paul@28 89 <p>
MikeDSmith25@117 90 By default, SliTaz provides the graphical mini-server Xvesa. Xorg server is available
paul@28 91 in the packages on the mirror. Xorg is a very comprehensive server, but uses a lot more
paul@28 92 resources than Xvesa. If your resolution is supported by the mini-server and you're happy
paul@28 93 with the refresh rate, then there's no reason to use Xorg.
paul@28 94 </p>
paul@28 95 <p>
MikeDSmith25@117 96 There is no GUI configuration which means having to use the command line in console mode. The installation
paul@28 97 and configuration of the server is relatively simple and you can always go back and reuse Xvesa at any time.
paul@28 98 Xorg is distributed in modular form, which means that you'll need to install the server, a few configuration
paul@28 99 files and the right driver for your graphics card. However the <code>xorg-server</code> package has all
paul@28 100 the correct dependancies to work directly with the <code>vesa</code> driver. Minimal install:
paul@28 101 </p>
paul@28 102 <pre> # tazpkg get-install xorg-server
paul@28 103 </pre>
paul@28 104 <p>
paul@28 105 Once installed, you can go directly to the configuration or you can install the correct driver for your card
paul@28 106 (if you know it). Example using the Nvidia driver and listing all available drivers:
paul@28 107 </p>
paul@28 108 <pre> # tazpkg get-install xorg-xf86-video-nv
paul@28 109 List:
paul@28 110 # tazpkg search xorg-xf86-video
paul@28 111 </pre>
paul@28 112 <h4>Automatic configuration of the server</h4>
paul@28 113
paul@28 114 <p>To configure the Xorg server you have two options: <code>Xorg -configure</code>
paul@28 115 or the script <code>xorgconfig</code>. It is recommended that you start by using Xorg with
paul@28 116 the <code>-configure</code> option. The automatic configuration of Xorg must be done in console
paul@28 117 mode without an X-server running; this is achieved by closing all applications and windows and hitting
paul@28 118 the <code>alt-ctrl-del</code> buttons. You should now be in console mode. Now you need to run Xorg with the
paul@28 119 <code>-configure</code> option and copy the newly generated file to <code>/etc/X11</code>:
paul@28 120 </p>
paul@28 121 <pre> # Xorg -configure
paul@28 122 # cp /root/xorg.conf.new /etc/X11/xorg.conf
paul@28 123 </pre>
paul@28 124 <p>
paul@28 125 Finally you then change the configuration of Slim to use Xorg instead of Xvesa and restart the window manager.
paul@28 126 </p>
paul@28 127 <h4>Using Xorg with Slim</h4>
paul@28 128 <p>
paul@28 129 In the Slim configuration file (<code>/etc/slim.conf</code>), we need to comment out
paul@28 130 (<code>#</code>) the lines pertaining to Xvesa and change Xorg to the <code>default_xserver</code>:
paul@28 131 </p>
paul@28 132 <pre class="script">default_xserver /usr/bin/Xorg
paul@28 133 #default_xserver /usr/bin/Xvesa
paul@28 134 #xserver_arguments -ac -shadow dpms +extension Composite -screen 1024x768x24
paul@28 135 </pre>
paul@28 136 <p>
paul@28 137 Now we can start Slim to return us to an X server session.
paul@28 138 Slim works likes a daemon, it can be stopped or started from the console:
paul@28 139 </p>
paul@28 140 <pre> # /etc/init.d/slim start
paul@28 141 </pre>
paul@28 142 <h4>xorg.conf - Configuration file</h4>
paul@28 143 <p>
MikeDSmith25@117 144 Xorg uses the configuration file <code>/etc/X11/xorg.conf</code>. This file can be
MikeDSmith25@117 145 automatically generated and edited with your favorite text editor. It is divided into
paul@28 146 several sections, including the specification of paths, modules to be loaded, default screen,
MikeDSmith25@117 147 mouse, keyboard, etc. This document provides only a few examples, it is advisable to run
paul@28 148 <code>xorgconfig</code> once to generate a complete file to use as an example.
paul@28 149
paul@28 150 </p>
paul@28 151 <p>
paul@28 152 Keyboard (en):
paul@28 153 </p>
paul@28 154 <pre class="script">Section "InputDevice"
paul@28 155 Identifier "Keyboard0"
paul@28 156 Driver "kbd"
paul@28 157 Option "XkbRules" "xorg"
paul@28 158 Option "XkbModel" "pc105"
paul@28 159 Option "XkbLayout" "en"
paul@28 160 Option "XkbVariant" "en"
paul@28 161 EndSection
paul@28 162 </pre>
paul@28 163 <p>
paul@28 164 Mice with auto detection protocol:
paul@28 165 </p>
paul@28 166 <pre class="script">Section "InputDevice"
paul@28 167 Identifier "Mouse0"
paul@28 168 Driver "mouse"
paul@28 169 Option "Protocol" "auto"
paul@28 170 Option "Device" "/dev/input/mice"
paul@28 171 Option "ZAxisMapping" "4 5 6 7"
paul@28 172 EndSection
paul@28 173 </pre>
paul@28 174 <p>
paul@28 175 Composite extensions:
paul@28 176 </p>
paul@28 177 <pre class="script">Section "Extensions"
paul@28 178 Option "Composite" "1"
paul@28 179 EndSection
paul@28 180 </pre>
paul@28 181
pankso@7 182 <a name="jwm"></a>
pankso@7 183 <h3>JWM - Window manager</h3>
pankso@7 184 <p>
pankso@7 185 JWM (Joe's Window Manger) is a lightweight Window Manager, easy to use, fast,
pankso@7 186 stable and insanely configurable. The menu and theme can all be changed from a
pankso@7 187 single configuration file found in your home directory: <code>~/.jwmrc</code>,
pankso@7 188 the file uses XML syntax and the code is nicely colored if you use Geany to
pankso@7 189 edit it. To add an entry in the menu you can use the following example:
pankso@7 190 </p>
paul@18 191 <pre class="script"> &lt;Program icon="kino.png" label="Kino (Video Editor)"&gt;kino&lt;/Program&gt;
pankso@7 192 </pre>
pankso@7 193 <p>
pankso@7 194 The <a href="http://www.joewing.net/programs/jwm/config.shtml">JWM Web site</a>
pankso@7 195 has got more information on how to configure the application to your needs
pankso@7 196 and preferences.
pankso@7 197 </p>
pankso@7 198
pankso@7 199 <a name="enlightenment"></a>
pankso@7 200 <h3>Enlightenment (e17)</h3>
pankso@7 201 <p>
paul@135 202 Enlightenment aka e17 is a lightweight and fast desktop environment that can be
paul@135 203 configured graphically. To install e17:
pankso@7 204 </p>
paul@18 205 <pre> # tazpkg get-install enlightenment
pankso@7 206 </pre>
pankso@7 207 <p>
pankso@7 208 Logout your current X session, type <code>F1</code> at Slim login and choose
pankso@7 209 <code>e17</code> to start Enlightenment.
pankso@7 210 </p>
paul@105 211 <p>
paul@106 212 Additional themes can be found on the <a href="http://www1.get-e.org/Themes/E17/">website</a>
paul@105 213 </p>
pankso@7 214
pankso@7 215 <a name="openbox"></a>
pankso@7 216 <h3>Openbox</h3>
pankso@7 217 <p>
paul@124 218 Openbox is a lightweight window manager that can be configured using the obconf
pankso@7 219 utility. To install openbox:
pankso@7 220 </p>
paul@18 221 <pre> # tazpkg get-install openbox
pankso@16 222 # tazpkg get-install obconf
pankso@7 223 </pre>
pankso@7 224 <p>
pankso@7 225 Logout your current X session, type <code>F1</code> at Slim login and choose
pankso@7 226 <code>openbox</code> to start Openbox. To make Openbox your default Window
pankso@7 227 Manager just type: <code>tazx openbox</code>.
pankso@7 228 </p>
pankso@7 229 <p>
pankso@7 230 Note: you can also use the configuration file <code>menu.xml</code> found
pankso@7 231 in <code>/etc/xdg/openbox</code> to edit menu items. Here's an example using
pankso@7 232 Htop:
pankso@7 233 </p>
paul@18 234 <pre class="script">&lt;item label="Htop"&gt;
pankso@7 235 &lt;action name="Execute"&gt;&lt;command&gt;xterm -e htop&lt;/command&gt;&lt;/action&gt;
pankso@7 236 &lt;/item&gt;
pankso@7 237 </pre>
pankso@7 238 <p>
pankso@7 239 More information can be found on the
pankso@7 240 <a href="http://icculus.org/openbox/index.php/Help:Menus">openbox</a> site.
pankso@7 241 </p>
pankso@7 242
paul@149 243 <a name="terminalX"></a>
paul@149 244 <h3>Use Xvesa as X terminal</h3>
paul@149 245 <p>
paul@149 246 You can use Xvesa as X terminal, if you have a machine on
paul@149 247 the network that accepts Xdmcp connections. To enable this,
paul@149 248 you can start the server with the option <code>-query</code> followed by
paul@149 249 the machine name or IP address. Example of machine 192.168.0.2
paul@149 250 on a local network:
paul@149 251 </p>
paul@149 252 <pre> $ Xvesa -ac -shadow -screen 1024x768x24 -query 192.168.0.2
paul@149 253 </pre>
paul@149 254 <p>
paul@149 255 The use of a graphical remote server can be of great use, although
paul@149 256 reponse times of applications depend greatly on Internet
paul@149 257 speed and the remote machine's power. This technique works
paul@149 258 very well within a local area network (LAN) and allows you
paul@149 259 to control applications installed on the remote machine directly
paul@149 260 from the screen of the local machine on which you work.
paul@149 261 Note that the distant remote machine may have
paul@149 262 multiple accounts in use simultaneously and/or direct access.
paul@149 263 </p>
paul@149 264
paul@18 265 <a name="fonts"></a>
hacker@20 266 <h3>Fonts</h3>
paul@18 267 <p>
paul@18 268 The management of Fonts (<em>fonts</em>) is powered by the package Fontconfig.
paul@18 269 This package provides tools to add, list and manipulate fonts. The <em>fonts</em>
paul@18 270 can be installed in user space or at the system level, this means that each user can use his/her own
paul@18 271 fonts or the adminstrator (<em>root</em>) can install fonts available to all users of the system.
hacker@20 272 If you use USB media associated with SliTaz <a href="http://www.slitaz.org/en/doc/handbook/livecd.html">LiveCD</a>,
paul@18 273 you can easily install fonts and retain them the next time you use the cdrom.
paul@18 274 </p>
paul@18 275 <h4>Installing <em>fonts</em></h4>
paul@18 276 <p>
paul@18 277 At the system level fonts are installed in the directory:
paul@18 278 <code>/usr/share/fonts</code>, core SliTaz provides TTF Vera fonts,
MikeDSmith25@117 279 they take up little space and are rendered correctly. In user space, fonts are found in the hidden
MikeDSmith25@117 280 directory: <code>.fonts</code>. This directory should be at the root of user space.
paul@18 281 To create a home directory to accomodate new fonts, you can use the graphical window manager emelFM2,
paul@18 282 Clex or use the command line:
paul@18 283 </p>
paul@18 284 <pre> $ mkdir ~/.fonts
paul@18 285 </pre>
paul@18 286 <p>
hacker@20 287 Once you have installed the fonts you need to run the <code>fc-cache</code> tool to generate
hacker@20 288 configuration files, this ensures that your <em>fonts</em> are available for use in applications:
paul@18 289 </p>
paul@18 290 <pre> $ fc-cache
paul@18 291 </pre>
paul@18 292
pankso@7 293 <!-- End of content -->
pankso@7 294 </div>
pankso@7 295
pankso@7 296 <!-- Footer. -->
pankso@7 297 <div id="footer">
pankso@7 298 <div class="footer-right"></div>
pankso@7 299 <a href="#top">Top of the page</a> |
paul@68 300 <a href="index.html">Table of contents</a>
pankso@7 301 </div>
pankso@7 302
pankso@7 303 <div id="copy">
paul@18 304 Copyright © 2008 <a href="http://www.slitaz.org/en/">SliTaz</a> -
pankso@7 305 <a href="http://www.gnu.org/licenses/gpl.html">GNU General Public License</a>;<br />
pankso@7 306 Documentation is under
pankso@7 307 <a href="http://www.gnu.org/copyleft/fdl.html">GNU Free Documentation License</a>
pankso@7 308 and code is <a href="http://validator.w3.org/">valid xHTML 1.0</a>.
pankso@7 309 </div>
pankso@7 310
paul@68 311 </body>
paul@68 312 </html>
pankso@7 313