Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
en:handbook:xwindow [2010/05/23 00:59] linea |
en:handbook:xwindow [2012/04/09 22:13] linea |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| The X Window System or X11 provides a window manager running on top of a X server. | The X Window System or X11 provides a window manager running on top of a X server. | ||
| - | SliTaz 2.0 by default uses the lightweight X server called Xvesa from the Xorg project (www.x.org). | + | SliTaz 1.0 and 2.0 by default use the lightweight X server called Xvesa from the Xorg project (www.x.org). |
| - | Slitaz 3.0 by default uses the Xorg server, there is however an Xvesa flavor. | + | 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 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 ===== | ||
| - | 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. | + | Xorg is the default server on SliTaz and designed to work out of the box on most systems. It should detect and configure most devices such as keyboards, mice, displays, etc. Once installed, running Tazx allows you to reconfigure/reinstall the xorg-server package and select the correct driver for your card. Example: |
| - | 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: | + | First stop the Xorg server using alt-ctrl-backspace, you should now be in console mode. Then run tazx as root: |
| - | <code> # tazpkg get-install xorg-server </code> | + | <code> # tazx </code> |
| - | Once installed, you can go directly to the configuration or you can install the correct driver for your card (provided you know it). Example using the Nvidia driver and listing all available drivers: | + | Then select Xorg and select your video driver, this reconfigures Xorg. Then restart the slim login manager: |
| - | <code> | + | |
| - | # tazpkg get-install xorg-xf86-video-nv | + | |
| - | List: | + | |
| - | # tazpkg search xorg-xf86-video | + | |
| - | </code> | + | |
| - | === Automatic configuration of the server === | + | <code> # /etc/init.d/slim start </code> |
| - | 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//: | + | You can also do this by searching for and installing a video driver and reconfiguring Xorg manually (after stopping the server): |
| - | <code> | + | <code> |
| - | # Xorg -configure | + | # tazpkg search xorg-xf86-video |
| - | # cp /root/xorg.conf.new /etc/X11/xorg.conf | + | # tazpkg get-install xorg-xf86-video-nv |
| + | # Xorg -configure | ||
| </code> | </code> | ||
| - | Finally you then change the configuration of Slim to use Xorg instead of Xvesa and restart the window manager. | + | Then copy the newly generated file to /etc/X11: |
| - | === Using Xorg with Slim === | + | <code> # cp /root/xorg.conf.new /etc/X11/xorg.conf </code> |
| - | 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: | + | And restart the login manager: |
| - | <code> | + | <code> # /etc/init.d/slim start </code> |
| - | default_xserver /usr/bin/Xorg | + | |
| - | #default_xserver /usr/bin/Xvesa | + | |
| - | #xserver_arguments -ac -shadow dpms +extension Composite -screen 1024x768x24 | + | |
| - | </code> | + | |
| - | 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: | ||
| - | + | === xorg.conf.d - Configuration files === | |
| - | <code> # /etc/init.d/slim start </code> | + | |
| - | === xorg.conf - Configuration file === | + | Xorg uses the configuration files found in the xorg.conf.d directory which are automatically setup when you first boot and can be easily edited with your favorite text editor. The files are configured separately into sections such as modules to be loaded, default screen, mouse, keyboard, etc. This document provides a few examples: |
| - | 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. | + | 10-ServerLayout.conf: |
| - | Keyboard (en): | + | <file> |
| - | + | Section "ServerLayout" | |
| - | <code> | + | Identifier "X.org Configured" |
| - | Section "InputDevice" | + | Screen 0 "Screen0" 0 0 |
| - | Identifier "Keyboard0" | + | |
| - | Driver "kbd" | + | |
| - | Option "XkbRules" "xorg" | + | |
| - | Option "XkbModel" "pc105" | + | |
| - | Option "XkbLayout" "en" | + | |
| - | Option "XkbVariant" "en" | + | |
| EndSection | EndSection | ||
| - | </code> | + | </file> |
| - | Mice with auto detection protocol: | + | 30-Module.conf: |
| - | <code> | + | <file> |
| - | Section "InputDevice" | + | Section "Module" |
| - | Identifier "Mouse0" | + | Load "dbe" |
| - | Driver "mouse" | + | Load "dri2" |
| - | Option "Protocol" "auto" | + | Load "extmod" |
| - | Option "Device" "/dev/input/mice" | + | Load "dri" |
| - | Option "ZAxisMapping" "4 5 6 7" | + | Load "record" |
| + | Load "glx" | ||
| EndSection | EndSection | ||
| - | </code> | + | </file> |
| - | Composite extensions: | + | Note that a xorg.conf file can also be found in /etc/X11 as another way to configure Xorg. This file is read before all files in /etc/X11/xorg.conf.d and will NOT be erased by any updates. |
| - | + | ||
| - | <code> | + | |
| - | Section "Extensions" | + | |
| - | Option "Composite" "1" | + | |
| - | EndSection | + | |
| - | </code> | + | |
| - | ===== Use Xvesa as X terminal ===== | + | ===== Use Xvesa as X terminal (Deprecated) ===== |
| You can use Xvesa as X terminal, if you have a machine on the network that accepts Xdmcp connections. To enable this, you can start the server with the option -query followed by the machine name or IP address. Example of machine 192.168.0.2 on a local network: | You can use Xvesa as X terminal, if you have a machine on the network that accepts Xdmcp connections. To enable this, you can start the server with the option -query followed by the machine name or IP address. Example of machine 192.168.0.2 on a local network: | ||
| Line 115: | Line 94: | ||
| <code> $ Xvesa -ac -shadow -screen 1024x768x24 -query 192.168.0.2 </code> | <code> $ Xvesa -ac -shadow -screen 1024x768x24 -query 192.168.0.2 </code> | ||
| - | The use of a graphical remote server can be of great use, although reponse times of applications depend greatly on Internet speed and the remote machine's power. This technique works very well within a local area network (LAN) and allows you to control applications installed on the remote machine directly from the screen of the local machine from which you work. Note that the distant remote machine may have multiple accounts in use simultaneously and/or direct access. | + | The use of a graphical remote server can be of great use, although response times of applications depend greatly on Internet speed and the remote machine's power. This technique works very well within a local area network (LAN) and allows you to control applications installed on the remote machine directly from the screen of the local machine from which you work. Note that the distant remote machine may have multiple accounts in use simultaneously and/or direct access. |
| ===== 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 for 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 administrator (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 === | ||
| - | At the system level fonts are installed in the directory: ///usr/share/fonts//, core SliTaz provides TTF Vera fonts, they take up little space and are rendered correctly. At the root of user space ~/, fonts are found in the hidden directory: .fonts. To create a home directory to accomodate new fonts, you can use the graphical window manager emelFM2, Clex or the command line: | + | At the system level fonts are installed in the directory: ///usr/share/fonts//, core SliTaz provides TTF Vera fonts, they take up little space and are rendered correctly. At the root of user space ~/, fonts are found in the hidden directory: .fonts. To create a home directory to accommodate new fonts, you can use the graphical window manager emelFM2, Clex or the command line: |
| <code> $ mkdir ~/.fonts </code> | <code> $ mkdir ~/.fonts </code> | ||