From: Manoj Srivastava [mrsi@mebscs01.telecorp1.com] Sent: Tuesday, April 30, 2002 12:18 PM To: msrivast@telecorp1.com ############################################################################### # # X0screens # $Date: 96/06/19 09:01:38 $ # $Revision: 57.2 $ # ############################################################################### ############################################################################### # # IMPORTANT # --------- # # - The format of the X*screens file has changed for HP-UX 10.0. The new # format is described below. # # - Before HP-UX 10.0, options were specified to the X server via environment # variables. These variables must now be specified in an X*screens file as # either server or screen options. # # - Although the X*screens file can be manually edited, X Server screen # configuration has been incorporated into the "HP System Administration # Manager" (SAM) and this is the recommended method for performing this # task. # # - For more information about device-dependent features, look in an X server # information file (for example, /usr/lib/X11/Xserver/info/screens/hp). # # - See our web site (http://www.hp.com/go/xwindow) for the latest in # "World Class X Servers". # ############################################################################### ############################################################################### # # Description of the X*screens Configuration File # ----------------------------------------------- # # This file belongs in /etc/X11/X*screens, where "*" is the display number of # the server. For example, the "X0screens" file is used when the $DISPLAY # environment variable is set to :0. and the server is # invoked using the ":0" option. # # The X*screens file is used to specify: # - Device-independent server options # - For each screen # what device file to use (required) # the default visual # monitor size # device-dependent screen options # # Note that all of the items above, except for device-independent server # options, are specified on a per-screen basis. # # The X server supports up to FOUR (4) screens at a time. Specifying more than # four screens will cause a server error message. # # # Syntax Guidelines # ----------------- # # - Blank lines and comments (text following '#') are ignored. # - Entries can occupy more than a single line. # - All symbols in the file are recognized case-insensitive. # # # X*screens Format # ---------------- # # SYNOPSIS # # Items must appear in the X*screens file in the order that they are # specified below. # # [ServerOptions # # . # . # . # ] # # {Screen } || <---+ # {SingleLogicalScreen | # ... } | # | # [DefaultVisual | # [Class ] | This block is referred to # [Depth ] | as a either a "Screen # [Layer ] | Entry" or as a "Single # [Transparent]] | Logical Screen entry". # | # [MonitorSize ] | # | # [MinimumMonitorPowerSaveLevel ] | # | # [ScreenOptions | # | # . | # . | # . | # ] <---+ # # Square brackets ("[" and "]") denote optional items. Angle brackets # ("<" and ">") denote values to be specified. A double-vertical line ("||") # denotes that ONE of the "or'ed" values (items surrounded by curly # braces, "{" and "}") must be included. # # DESCRIPTION # # The X*screens format is composed of an optional block specifying # device-independent server options followed by one or more either # Screen or Single Logical Screen entries (maximum of 4 graphics devices). # # The minimum X*screens file is a line with the keyword "Screen" followed by # a screen device file. For example: # # Screen /dev/crt # # ServerOptions # ------------- # # For more information about server options, or about additional server # options, look in an information file (for example, # /usr/lib/X11/Xserver/info/screens/hp). # # GraphicsSharedMemorySize # Specify the size of the graphics shared memory region. The size # must be specified in bytes and must be in hexadecimal. # # Default Value: # 0x580000 # # Environment Variable Replaced: # GRM_SIZE, WMSHMSPC # # SMTSizes # The size of the SMT regions (see the SMT Section below). # # Default: # 0 (i.e. Disabled) # # FileDescriptors # The number of file descriptors available to the X server # for its use. The number of connections (clients, more or less) # is limited by the number of file descriptors. # # The minimum value is 25, and a current (as of 10.20) maximum of # 384, allowing a maximum of slightly under 256 total connections to # the Server. The default value is 192 (which allows a few under 128 # connections). If a value provided is out of range, the server yields # a warning and continues using the minimum or maximum, as appropriate. # There is, however, a limit of 128 clients that can connect. # # The command line option -lf also specifies the value. # # ServerMode # This server option places the X server in either "XPrint" or # "XVideo" mode, "XVideo" is the default behavior. X Print is an X # extension supporting managment of networked printers. Use of the # "XPrint" mode disables the normal video output mode of the X server. # It is necessary to start two X servers to have both functionalities. # To do this run each invocation with a different display identifier. # # ConfigXPrintServer # This server option identifies a configuration file for use by # the X Print extension. "ConfigXPrintServer" is only meaningful when # used in conjuction with the server option "ServerMode XPrint". # # The command line option -Xpfile is an alternate # method to specify the same information. # # ImmediateLoadDles # The Xserver delays loading of some X extensions until the first # protocol request to the given extension is received. Specifying this # ServerOption forces all extensions to be loaded at X server startup. # # ScreenEntries # ------------- # # The minimum screen entry is a line with the keyword "Screen" followed # by a screen device file. # # Optional specifications for default visual, monitor size, and # device-dependent screen options may follow this minimal screen # description line. # # DefaultVisual: # # This optional part of the format specifies the default visual that # the screen uses. Valid keywords following the "DefaultVisual" # keyword are "Class", "Depth", "Layer", and "Transparent". # # If no default visual is specified, then the standard default visual # class, depth, layer, and transparency for the graphics device is # used. # # Not all default visual specifications will work on all devices. # # If there is an error in a specification, look in an information file # for more details (for example, # /usr/lib/X11/Xserver/info/screens/hp). # # Class # Specify the class of the default visual. # # Depth # Specify the depth of the default visual (for example 8, 12, or # 24). # # Layer # Specify the layer of the default visual. # # Transparent # Specify that a visual with an application-accessible transparent # entry in the default colormap be used. # # Specifications in the "DefaultVisual" section, except for "Depth", # are ignored on VRX devices. See the "ScreenOptions" section below # for VRX-related options. # # MonitorSize: # # MonitorSize # # Specify the diagonal size of the monitor. After the "MonitorSize" # keyword, you must specify the diagonal length of the monitor and # then the units. Use this entry only if you are using a non-standard # monitor. # # Look in an information file for more details (for example, # /usr/lib/X11/Xserver/info/screens/hp). # # MinimumMonitorPowerSaveLevel: # # MinimumMonitorPowerSaveLevel # # Specify the minimum power save level to be used by the monitor # during screen blanking. You must specify a level of 0-3. If # the option is not used, the default is level 0. On devices # that do not support DPMS, this option will be ignored. Do not # use this option on monitors that do not support DPMS. # # Look in an information file for more details (for example, # /usr/lib/X11/Xserver/info/screens/hp). # # ScreenOptions: # # Screen options are device-dependent options that are documented in a # file in the X server information directory (for example, # /usr/lib/X11/Xserver/info/screens/hp). # # # Sample X*screens Files # ---------------------- # # Below are several sample X*screens files that illustrate the new format. # # ----------------------------------------------------------------------------- # # This is the minimum legal X*screens file, the "Screen" keyword followed by # the screen device. Since no other information is given, the X server will # assume default values for other options and settings. # # +-----------+ # | | # | | # | /dev/crt0 | # | | # | | # +-----------+ # # Screen /dev/crt # # ----------------------------------------------------------------------------- # # This is the minimum specification for a two-screen configuration. The # maximum number of screens supported on the X server is four. Here, the # displays associated with /dev/crt0 and /dev/crt1 are referred to as # ":0.0" and ":0.1", respectively. # # +-----------+ +-----------+ # | | | | # | | | | # | /dev/crt0 | | /dev/crt1 | # | | | | # | | | | # +-----------+ +-----------+ # # Screen /dev/crt0 # # Screen /dev/crt1 # # ----------------------------------------------------------------------------- # # This sample X*screens file could be used on a system using Integrated Color # Graphics with a 17-inch monitor. In this example, the # GraphicsSharedMemorySize is decreased to 1 Mbyte in order to reduce the swap # space requirements of the system. Decreasing GraphicsSharedMemorySize is # appropriate when you do not intend to run any 3D graphics applications. # # ServerOptions # GraphicsSharedMemorySize 0x100000 # # Screen /dev/crt # MonitorSize 17 inches # # ----------------------------------------------------------------------------- # # This sample X*screens file could be used on a system with a HCRX-24 graphics # device. The default visual on the HCRX-24 is the opaque overlay visual. All # 256 colormap entries are opaque and allocable. If an application requires # transparency in the default visual, the "Transparent" keyword can be used to # select the transparent overlay visual as shown below. # # Screen /dev/crt # DefaultVisual # Transparent # # ----------------------------------------------------------------------------- # # This sample X*screens file could be used on a system with an HCRX24 graphics # device as above (with transparency in the default visual). There are 255 # overlay colormap entries available in this configuration; the 256th entry is # hard-wired to transparent. Having less than 256 colormap entries should not # cause a problem for most applications. For those application that require # 256 colormap entries, the CountTransparentInOverlayVisual screen option # should be used as shown below. Note that any attempts to modify the 256th # entry will have no effect on the colormap. # # Screen /dev/crt # DefaultVisual # Transparent # ScreenOptions # CountTransparentInOverlayVisual # # ----------------------------------------------------------------------------- # # This sample X*screens file could be used on a system with a HCRX-8 graphics # device. By default on the HCRX-8, the overlay visual does not have a # transparent entry available to applications for rendering transparency. If # an application requires overlay transparency, an optional X server mode is # available, but it is restrictive. In this optional mode, only one hardware # colormap is available in the overlays (instead of two) and only one hardware # colormap is available in the image planes (instead of two). The optional X # server mode can be set via the EnableOverlayTransparency screen option as # shown below. # # Screen /dev/crt # ScreenOptions # EnableOverlayTransparency # # ----------------------------------------------------------------------------- # # These sample X*screens file entires could be used on a system with two # homogeneous graphics devices. Assuming the first device is associated # with the device file "/dev/crt0" and the second device is associated with # the device file "/dev/crt1", both examples specify a horizontal # Single Logical Screen configuration. # # +-----------+-----------+ # | | | # | | | # | | | # | | | # +-----------+-----------+ # # SingleLogicalScreen 1 2 # /dev/crt0 /dev/crt1 # # ............................................................................. # # SingleLogicalScreen 1 2 # /dev/crt0 # /dev/crt1 # # ----------------------------------------------------------------------------- # # These sample X*screens entries could be used on a system with four homogeneous # graphics devices. Assuming the first device is associated with the device # file "/dev/crt0", the second device is associated with the device file # "/dev/crt1", etc. The following examples specify valid Single Logical # Screen configurations. # # +-----------+-----------+-----------+-----------+ # | | | | | # | | | | | # | | | | | # | | | | | # | | | | | # +-----------+-----------+-----------+-----------+ # # SingleLogicalScreen 1 4 # /dev/crt0 /dev/crt1 /dev/crt2 /dev/crt3 # # ............................................................................. # # +-----------+ # | | # | | # | | # | | # +-----------+ # | | # | | # | | # | | # +-----------+ # | | # | | # | | # | | # +-----------+ # | | # | | # | | # | | # +-----------+ # # SingleLogicalScreen 4 1 # /dev/crt0 # /dev/crt1 # /dev/crt2 # /dev/crt3 # # ............................................................................. # # +-----------+-----------+ # | | | # | | | # | /dev/crt0 | /dev/crt1 | # | | | # | | | # +-----------+-----------+ # | | | # | | | # | /dev/crt2 | /dev/crt3 | # | | | # | | | # +-----------+-----------+ # # SingleLogicalScreen 2 2 # /dev/crt0 /dev/crt1 # /dev/crt2 /dev/crt3 # # ----------------------------------------------------------------------------- # # It is possible to include a Screen Entry and an SLS Screen Entry in the # same X*screens File. This creates a situation where there are two # X Screens (e.g. display:0.0 & display:1.0), one of which happens to be # a Single Logical Screen. Below is an example of this: # # +-----------+ +-----------+-----------+ # | | | | | # | | | | | # | | | | | # | | | | | # +-----------+ +-----------+-----------+ # # Screen /dev/crt0 # SingleLogicalScreen 1 2 # /dev/crt1 /dev/crt2 # # ----------------------------------------------------------------------------- # # Distributed Single Logical Screen (SLS/d) # ----------------------------------------- # # SLS/d uses a Master/Slave relationship between X displays to create # and manage the logical screen. SLS/d is functionally identical to # SLS, except for the way the screens are configured. To configure an # SLS/d screen, you must first choose a group of X displays, all running # the same version of HP-UX, either 10.20 running the January 1999 periodic # patch (or subsequent HP-UX 10.20 patch or ACE), or HP-UX 11.0 running the # November 1999 ACE. # # In addition, all of the systems running the displays must be running # /usr/bin/X11/SLSd_daemon (this is normally launched automatically # when the system is booted; if it is not, you may start it by hand, # as root). # # Then, the master and slaves must be configured correctly. The SLS/d master # X server can execute on any appropriate system, including one that # is also executing a SLS/d slave X server. The SLS/d master X server # does not require a graphics display device. The SLS/d slave displays must # all have the same underlying graphics display device. To determine this, # run "/bin/graphinfo " (where represents the graphics # device file (e.g., /dev/crt0) listed in that slave's /etc/X11/X*screens file) # and search for the "graphics product". # # To Configure the SLS/d Slave X Servers: # ...................................... # # Configuring an SLS/d slave X server is identical to configuring # a normal (non-SLS) screen as described above. The catch is that # if any Screen or ServerOption(s) are configured for one slave, # they must be configured for each of the slave X servers. # # For example, to configure SLS/d slave X servers on hpslsd1, hpslsd2, # hpslsd3, and hpslsd4, do the following as root: # # Copy each system's /etc/X11/X0screens file to /etc/X11/X50screens # (the use of "50" as the display name is an SLS/d convention only; # you can choose any number from 0-99 that meets your needs). Unless # you're making changes to screen options or server options, you need # not edit this file any further. This step can be accomplished # using SAM by saving the default configuration to "X50screens". # # Create a file called /etc/X11/X50devices (unless you chose a different # display number, then instead use the same number you selected for # the X*screens file) and enter the following: # # +------------------------------- # |first NULL keyboard # |first NULL pointer # | # # Make sure that SLSd_daemon is running on each system, then take the # systems down to init state 2 (e.g., as root: /etc/init 2) # # To Configure the SLS/d Master X Server: # ...................................... # # Configuring the SLS/d Master is almost identical to configuring # a SLS screen as described above. As root, edit /etc/X11/X0screens on # the system which will host the master (remember that the master # can execute on the same system that is executing a slave; which # is why we choose to use :50 for the slave display numbers). The # use of "0" for the master is very important. If you change this # number, CDE will not run properly unless you also make the # necessary changes to have CDE run to a non-default screen location. # # Then, to configure the logical screen as follows: # # +-----------+ +-----------+ +-----------+ +-----------+ # | | | | | | | | # |hpslsd1:50 | |hpslsd3:50 | |hpslsd4:50 | |hpslsd2:50 | # | | | | | | | | # | | | | | | | | # +-----------+ +-----------+ +-----------+ +-----------+ # # Edit the /etc/X11/X0screens file and enter: # # SingleLogicalScreen 1 4 # hpslsd1:50 hpslsd3:50 hpslsd4:50 hpslsd2:50 # # Then, on the master system, make sure that SLSd_daemon is running # and enter init state 4 (e.g., as root: /etc/init 4). # # You will notice all of the slave X servers starting in turn, then # finally when the master initializes, you will see your CDE # environment start. # # Up to 64 displays can be configured as a Distributed Single Logical # Screen with the following restrictions: # # * All SLS/d slave systems must be running HP-UX 10.20 with the # 1999 January periodic patch or a subsequent HP-UX 10.20 patch. # # * All SLS/d slave displays must be using the same graphics display # device # # * All SLS/d slave displays must be in the same resolution (see # /opt/graphics/common/bin/setmon) # # * The systems hosting the graphics devices (e.g., hpslsd1) need # not be the same model. For example, hpslsd1 could be a J2240 # and hpslsd2 could be a C360. They just need to be running the # same graphics devices. # # SLS/d is also used in 3DSLS/d, or 3D Distributed Single Logical # Screen. In this case, you may also need to specify a fast lan # IP address. # # *NOTE* ONLY DO THIS STEP IF YOU HAVE A GIGABIT ETHERNET CONFIGURED # CONNECTING EACH SLAVE TO THE MASTER! # # In addition, the fast Lan IP addresses must all be # on the same subnet. # # In the master's /etc/X11/X0screens file, modify the entries # to also specify their Fast LAN IP addresses (those IP addresses # associated with the Gigabit Ethernet). Assume that the # following is true: # # hpslsd1 has the fast lan on 17.1.1.200 # hpslsd2 has the fast lan on 17.1.1.201 # hpslsd3 has the fast lan on 17.1.1.202 # # Then, to configure the SLS/d with Fast Lan using a similar # configuration as used above, modify the X0screens file as # follows: # # SingleLogicalScreen 1 4 # hpslsd1:50/17.1.1.200 # hpslsd3:50/17.1.1.201 # hpslsd4:50/17.1.1.202 # hpslsd4:50/17.1.1.203 # ############################################################################### # # X*screens Configuration # ----------------------- # # Place any additional/different configuration information below. # ############################################################################### Screen /dev/crt