Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:handbook:xwindow [2010/08/17 19:54] – lineaen:handbook:xwindow [2022/07/29 09:59] (current) – sessiondir explained hgt
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 a Xvesa flavor. Slitaz 3.0 by default uses the Xorg server, there is however a Xvesa flavor.
Line 20: Line 20:
 ===== Slim - Simple Login Manager ===== ===== Slim - Simple Login Manager =====
  
-Slim is a lightweight session manager that is very easy to configure and is customizable using system themes. The configuration file is found in ///etc/slim.conf//. It defines window managers available via the F1 key, the default user or theme, and the X window system parameters. Slim offers special user commands like console to help manage the session.+Slim is a lightweight session manager that is very easy to configure and is customizable using system themes.
  
-In LiveCD mode you can disable Slim with the boot option //screen=text//. On an installed system you can remove the package or delete slim from the //RUN_DAEMONS// variable in ///etc/rcS.conf//.+The configuration file is ''/etc/slim.conf''.
  
-More details and themes can be found on the website+It defines the default user, default theme, and the X window system parameters. Slim offers special user commands like ''console'' to help manage the session. 
 + 
 +More details and themes can be found on https://github.com/iwamatsu/slim 
 + 
 +=== Choose window manager === 
 + 
 +In version **1.3.5** available window managers via the F1 key are defined by use of the ''sessions'' statement in ''/etc/slim.conf''. 
 + 
 +In version **1.3.6** the 
 +<file>sessiondir /usr/share/xsessions</file> 
 +statement in ''/etc/slim.conf'' makes slim look for available window managers in the specified directory. 
 +To choose one, the ''F1'' key must be pressed. 
 + 
 +Users who use just one window manager should omit the ''sessiondir'' statement, so that ''.xinitrc'' will start the window manager specified by 
 +the ''WINDOW_MANAGER'' variable in ''$HOME/.config/slitaz/applications.conf''. 
 + 
 +<note tip>Users who want to choose between available window managers must uncomment the **sessiondir** statement in **/etc/slim.conf**. 
 + 
 +When updating from 1.3.5 to 1.3.6, **sessions ...** must be replaced by **sessiondir /usr/share/xsessions**.</note> 
 + 
 +=== Disable Slim === 
 + 
 +In live mode Slim can be disabled with the boot option ''screen=text''. 
 + 
 +On an installed system the package can be removed or ''slim'' can be deleted from the ''RUN_DAEMONS'' variable in ''/etc/rcS.conf''.
  
 === Default user === === Default user ===
  
-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 name, by default this is the user name with user number 1000 (usually ''tux''). 
 +This can be changed 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:
  
-<file> default_user        tux </file>+<file>default_user        nottux</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> # Xorg -configure +<code> 
- # cp /root/xorg.conf.new /etc/X11/xorg.conf+ # tazpkg search xorg-xf86-video 
 + # 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: 
  
-<file> 
-default_xserver     /usr/bin/Xorg 
-#default_xserver     /usr/bin/Xvesa 
-#xserver_arguments   -ac -shadow dpms +extension Composite -screen 1024x768x24 
-</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: 
- 
-  
 <code> # /etc/init.d/slim start </code> <code> # /etc/init.d/slim start </code>
  
-=== 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.conf.d - Configuration files ===
  
-Keyboard (en):+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: 
  
-<file> +10-ServerLayout.conf:
-Section "InputDevice" +
- Identifier  "Keyboard0" +
- Driver      "kbd" +
- Option      "XkbRules" "xorg" +
- Option      "XkbModel" "pc105" +
- Option      "XkbLayout" "en" +
- Option      "XkbVariant" "en" +
-EndSection +
-</file>+
  
-Mice with auto detection protocol: 
 <file> <file>
-Section "InputDevice" +Section "ServerLayout" 
- Identifier  "Mouse0" + Identifier     "X.org Configured" 
- Driver      "mouse" + Screen      0  "Screen0" 0 0
- Option     "Protocol" "auto" +
- Option     "Device" "/dev/input/mice" +
- Option     "ZAxisMapping" "4 5 6 7"+
 EndSection EndSection
 </file> </file>
  
-Composite extensions: +30-Module.conf: 
 <file> <file>
-Section "Extensions" +Section "Module" 
- Option      "Composite" "1"+ Load  "dbe" 
 + Load  "dri2" 
 + Load  "extmod" 
 + Load  "dri" 
 + Load  "record" 
 + Load  "glx"
 EndSection EndSection
 </file> </file>
  
-===== Use Xvesa as X terminal =====+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. 
 + 
 +===== 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 114: Line 122:
 <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>
 
en/handbook/xwindow.1282074857.txt.gz · Last modified: by linea