Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
en:handbook:xwindow [2010/04/20 17:21] jpeg Clearer formatting |
en:handbook:xwindow [2010/08/17 21:54] linea |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| SliTaz 2.0 by default uses the lightweight X server called Xvesa from the Xorg project (www.x.org). | SliTaz 2.0 by default uses the lightweight X server called Xvesa from the Xorg project (www.x.org). | ||
| - | Slitaz 3.0 by default uses the Xorg server. | + | Slitaz 3.0 by default uses the Xorg server, there is however a Xvesa flavor. |
| The X server can be started with the Slim login manager or directly from a Linux console with the command startx, but for this you must first disable the Login Manager. To reconfigure your X session you can use tazx as root or as the current user if you start X from the command line. | The X server can be started with the Slim login manager or directly from a Linux console with the command startx, but for this you must first disable the Login Manager. To reconfigure your X session you can use tazx as root or as the current user if you start X from the command line. | ||
| Line 13: | Line 13: | ||
| ===== Tazx - SliTaz X configuration tool ===== | ===== Tazx - SliTaz X configuration tool ===== | ||
| - | Tazx is the configuration tool to manage your X window sessions on a SliTaz box. Simply select a resolution and press OK. You can also select a (Xorg) session by selecting a video driver best suited to your hardware. After you first run 'startx', the configuration is saved in the executable files //~/.xsession// and //~/.xinitrc//. These files are then used to start a X session with 'startx' or via the Slim login manager and can be easily altered with a text editor. Tazx can also be used to change your default window manager. Example: | + | Tazx is the configuration tool to manage your X window sessions on a SliTaz box. Simply select a resolution and press OK. You can also select a (Xorg) session by selecting a video driver best suited to your hardware. After you first run 'startx', the configuration is saved in the executable files //~/.xsession// and //~/.xinitrc//. These files are then used to start a X session with either 'startx' or via the Slim login manager and can be easily altered with a text editor. Tazx can also be used to change your default window manager. Example: |
| <code> tazx jwm | <code> tazx jwm | ||
| Line 30: | Line 30: | ||
| Slim offers a way to pre-load a user login name, by default tux is configured for convenience. You can change this by editing the Slim configuration file ///etc/slim.conf// and modifying the line default_user or just leave the line blank to avoid pre-loading a user name. Example: | Slim offers a way to pre-load a user login name, by default tux is configured for convenience. You can change this by editing the Slim configuration file ///etc/slim.conf// and modifying the line default_user or just leave the line blank to avoid pre-loading a user name. Example: | ||
| - | <code> default_user tux </code> | + | <file> default_user tux </file> |
| ===== Xorg ===== | ===== Xorg ===== | ||
| Line 36: | Line 36: | ||
| By default, SliTaz provides the graphical mini-server Xvesa. Xorg server is available in the packages on the mirror. Xorg is a very comprehensive server, but uses a lot more resources than Xvesa. If your resolution is supported by the mini-server and you're happy with the refresh rate, then there's no reason to use Xorg. | By default, SliTaz provides the graphical mini-server Xvesa. Xorg server is available in the packages on the mirror. Xorg is a very comprehensive server, but uses a lot more resources than Xvesa. If your resolution is supported by the mini-server and you're happy with the refresh rate, then there's no reason to use Xorg. | ||
| - | There is no GUI configuration which means having to use the command line in console mode. The installation and configuration of the server is relatively simple and you can always go back and reuse Xvesa at any time. Xorg is distributed in modular form, which means that you'll need to install the server, a few configuration files and the right driver for your graphics card. However the xorg-server package has all the correct dependancies to work directly with the vesa driver. Minimal install: | + | There is no GUI configuration which means having to use the command line in console mode. The installation and configuration of the server is relatively simple and you can always go back and reuse Xvesa at any time. Xorg is distributed in modular form, which means that you'll need to install the server, a few configuration files and the right driver for your graphics card. However the xorg-server package has all the correct dependencies to work directly with the vesa driver. Minimal install: |
| <code> # tazpkg get-install xorg-server </code> | <code> # tazpkg get-install xorg-server </code> | ||
| Line 51: | Line 51: | ||
| To configure the Xorg server you have two options:// Xorg -configure// or the script xorgconfig. It is recommended that you start by using Xorg with the //-configure// option. The automatic configuration of Xorg must be done in console mode without an X-server running, this is achieved by closing all applications and windows and hitting the //alt-ctrl-del// buttons. You should now be in console mode. Now you need to run Xorg with the //-configure// option and copy the newly generated file to ///etc/X11//: | To configure the Xorg server you have two options:// Xorg -configure// or the script xorgconfig. It is recommended that you start by using Xorg with the //-configure// option. The automatic configuration of Xorg must be done in console mode without an X-server running, this is achieved by closing all applications and windows and hitting the //alt-ctrl-del// buttons. You should now be in console mode. Now you need to run Xorg with the //-configure// option and copy the newly generated file to ///etc/X11//: | ||
| - | <code> | + | <code> # Xorg -configure |
| - | # Xorg -configure | + | |
| # cp /root/xorg.conf.new /etc/X11/xorg.conf | # cp /root/xorg.conf.new /etc/X11/xorg.conf | ||
| </code> | </code> | ||
| Line 62: | Line 61: | ||
| In the Slim configuration file (///etc/slim.conf//), we need to comment out (#) the lines pertaining to Xvesa and change Xorg to the default_xserver: | In the Slim configuration file (///etc/slim.conf//), we need to comment out (#) the lines pertaining to Xvesa and change Xorg to the default_xserver: | ||
| - | <code> | + | <file> |
| default_xserver /usr/bin/Xorg | default_xserver /usr/bin/Xorg | ||
| #default_xserver /usr/bin/Xvesa | #default_xserver /usr/bin/Xvesa | ||
| #xserver_arguments -ac -shadow dpms +extension Composite -screen 1024x768x24 | #xserver_arguments -ac -shadow dpms +extension Composite -screen 1024x768x24 | ||
| - | </code> | + | </file> |
| Now we can start Slim to return us to an X server session. Slim works likes a daemon, it can be stopped or started from the console: | Now we can start Slim to return us to an X server session. Slim works likes a daemon, it can be stopped or started from the console: | ||
| Line 75: | Line 74: | ||
| === xorg.conf - Configuration file === | === xorg.conf - Configuration file === | ||
| - | Xorg uses the configuration file /etc/X11/xorg.conf. This file can be automatically generated and edited with your favorite text editor. It is divided into several sections, including the specification of paths, modules to be loaded, default screen, mouse, keyboard, etc. This document provides only a few examples, it is advisable to run xorgconfig once to generate a complete file to use as an example. | + | Xorg uses the configuration file ///etc/X11/xorg.conf// This file can be automatically generated and edited with your favorite text editor. It is divided into several sections, including the specification of paths, modules to be loaded, default screen, mouse, keyboard, etc. This document provides only a few examples, it is advisable to run xorgconfig once to generate a complete file to use as an example. |
| Keyboard (en): | Keyboard (en): | ||
| - | <code> | + | <file> |
| Section "InputDevice" | Section "InputDevice" | ||
| Identifier "Keyboard0" | Identifier "Keyboard0" | ||
| Line 88: | Line 87: | ||
| Option "XkbVariant" "en" | Option "XkbVariant" "en" | ||
| EndSection | EndSection | ||
| - | </code> | + | </file> |
| Mice with auto detection protocol: | Mice with auto detection protocol: | ||
| - | <code> | + | <file> |
| Section "InputDevice" | Section "InputDevice" | ||
| Identifier "Mouse0" | Identifier "Mouse0" | ||
| Line 99: | Line 98: | ||
| Option "ZAxisMapping" "4 5 6 7" | Option "ZAxisMapping" "4 5 6 7" | ||
| EndSection | EndSection | ||
| - | </code> | + | </file> |
| Composite extensions: | Composite extensions: | ||
| - | <code> | + | <file> |
| Section "Extensions" | Section "Extensions" | ||
| Option "Composite" "1" | Option "Composite" "1" | ||
| EndSection | EndSection | ||
| - | </code> | + | </file> |
| ===== Use Xvesa as X terminal ===== | ===== Use Xvesa as X terminal ===== | ||
| Line 119: | Line 118: | ||
| ===== Fonts ===== | ===== Fonts ===== | ||
| - | The management of Fonts (fonts) is powered by the package //fontconfig//. This package provides tools to add, list and manipulate fonts. The fonts can be installed in user space or at the system level, this means that each user can use his/her own fonts or the system adminstrator (root) can install fonts available to all users of the system. If you use USB media associated with the SliTaz LiveCD, you can easily install fonts and retain them the next time you use the cdrom. | + | The management of Fonts (fonts) is powered by the package //fontconfig//. This package provides tools to add, list and manipulate fonts. The fonts can be installed in user space or at the system level, this means that each user can use his/her own fonts or the system adminstrator (root) can install fonts available to all users of the system. If you use USB media associated with the SliTaz LiveCD, you can easily install fonts and retain them for the next time you use the cdrom. |
| === Installing fonts === | === Installing fonts === | ||