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