SliTaz GNU/Linux official and community documentation wiki.
.png

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
en:handbook:xwindow [2010/07/08 17:14]
127.0.0.1 external edit
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, there is however ​an Xvesa flavor.+Slitaz 3.0 by default uses the Xorg server, there is however ​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 =====
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.confThis 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 =====
 
en/handbook/xwindow.txt · Last modified: 2022/07/29 11:59 by hgt