All users should check:
• the DISPLAY variable.
• the XO. hosts file.
• the / etc/hosts file if your system is not configured to query a nameserver.
OSF /1 and Domain/OS users should read the next section, "Finding Your System Directory" for information about directories and file locations.
The rest of this chapter covers optional configuration. The following table shows the assumed configuration, and what you should read if you want to change it.
Table 3-1. Standard X Configuration
Expected configuration H you want to change it, read ...
1 display "U sing Custom Screen Configurations"
1 mouse "Using Special Input Devices"
1 keyboard "Using Special Input Devices"
American English language "Customizing for Native Language Support"
For HP-UX, X starts the hpterm and mwm "Software Configuration Files"
clients as part of its own start-up chapter 4 procedures.
For OSF /1 and Domain/OS systems, X starts the xterm and mwm clients as part of its own start-up procedures.
Default mwm colors, window decorations, "Software Configuration Files"
and menus. chapter 5
chapter 7
Finding Your System Directory
The operating systems have slightly different directory structures. The directory containing most of the X Window System is called the system directory.
Table 3-2. System Directory Operating System
HP-UX OSF/1 Domain/OS
System Directory /usr/lib/Xii
/usr/Xii/lib /usr/Xii/lib
This document uses the HP- UX paths, as does most general purpose X documentation.
On OSF/1 and Domain/OS systems, links are established between the HP-UX directory names and their corresponding OSF /1 and Domain/OS directory names. You can specify the HP- UX file path and have the links automatically connect you with the right path on your system.
3
3
Table 3-3. OSF/1 and Domain/OS Symbolic Links
Use ... to refer to ...
Directories
/usr/lib/Xll /usr/Xll/lib
/usr/bin/Xll /usr/Xll/bin
/usr/include (Domain/OS) /usr/Xll/include /usr/include/XllR4 (OSF /1) /usr/Xll/include/XllR4 /usr/include/Motifl.l (OSF /1) /usr/Xll/include/Motifl.l
Files
/usr/bin/xllstart /usr/Xll/bin/xllstart
/usr/bin/stconv' /usr/Xll/bin/stconv
/usr/bin/stload /usr/Xll/bin/stload
/usr/bin/stmkfont /usr/Xll/bin/stmkfont
/usr/bin/stlicense /usr/Xll/bin/stmkfont
/usr/bin/stmkdirs /usr/Xll/bin/stmkdirs
You may wish to set up other links yourself.
For example, on an OSF /1 system, you could see the contents of your system directory by entering either:
or
cd /usr/lib/Xll Is
cd /usr/Xll/1ib.
Is
I
Note The Domain/OS links are to your node entry directory. If you want the contents of a remote node directory, you must enter the specfic Domain/OS path to that directory. For example:
Assume you are on system / /bar.
Using Domain/OS path names, if you type ...
cd //foo/usr/Xll/1ib pwd
... then the sytem responds with ...
//foo/usr/Xll/1ib
But using HP- UX path names, if you type ...
cd //foo/usr/lib/Xl1 pwd
you get ...
//bar/xsr/Xll/1ib
Setting the DISPLAY Variable
The DISPLAY environment variable establishes the host, display number, and screen number to which a system sends bitmapped output.
You can check the current setting of your system's DISPLAY variable by typing the appropriate command from the following table:
Table 3-4. Checking the DISPLAY Variable
Operating System Command
HP-UX env
OSF/1
Domain/OS SysV
Domain/OS BSD printenv
Domain/OS Aegis Ivar
3
A list similar to the following is displayed:
DISPLAY=hpaaaaa:O.O HOME=/users/ellen TZ=PST8PDT
3 The DISPLAY variable has the syntax:
[ 1 s~:~me 11 :
display{.screen}shmll.nk
The default is hostname: 0.0, which is display 0, screen 0 of the display running the X server. (shmlink is not supported on Domain/OS.)
To reset the DISPLAY environment variable type the appropriate command shown below, or put it into the configuration file used by your system if you want it to be in effect every time you log in.
Table 3-5. Setting Environment Variables Shell
sh
csh
Conunand DISPLAY=host.·display.screen export DISPLAY
setenv DISPLAY host:display.screen Aegis DISPLAY :
=
host:display.screen (Domain/OS) export DISPLAYksh DISPLAY=host:display.screen export DISPLAY
Configuration File -I.profile
-I.login
-/user_data/startup_dm.xxx or
Isys/dm/startup_login.xxx -I.profile
Making an XO.hosts File
The / etc/XO. hosts file is an ASCII text file containing the hostnames of each remote host permitted to access your local server .
• If you are running as a stand-alone system, you must have your system's name in this file.
• If you are part of a network, the other system names must be included.
The syntax is as follows:
host host host
For example, if you are hpaaaaa, and regularly ran clients on hpccccc, and hpddddd, you would want the following lines.
hpaaaaa hpccccc hpddddd
Note that aliases work as well as hostnames, provided they are valid, that is, commonly known across the network.
The default screen configuration file XOscreens uses the default XII remote host file XO .hosts.
Note The OSF /1 and Domain operating systems use only XO .hosts, not custom X* . hosts or custom X*screens files.
Each custom X*screens file is associated with a special X* . hosts file. The number represented by the
*
causes the correct screen and host files to be used together. For example, X3screens takes an X3 .hosts file. Both are referenced by the server when it is started with a /usr/bin/X11/X :3 command.If you use a special X*screens file, you need to set your DISPLAY variable appropriately. For the previous example, it would be set to hostname: 3.
o.
3
Using an /etc/hosts File
This file need not be present if your system is configured to query a nameserver.
The / etc/hosts file is an ASCII text file containing a list of all the host names 3 and internet addresses known to your system, including your own system.
If your system is not connected to a network, use the loopback address ( 127 .0.0. 1) and the host name unknown:
127.0.0.1 unknown
For a local system to access a remote host:
• The address and host name of the romote host must be listed in the local system's / etc/hosts file .
• The user must have a valid login (username and password) and home directory on the remote host.