HP-UX 9.10 Series 300/400 Only

NAME

xterm300 − Using your 300/400 as an X-Terminal. 

DESCRIPTION

The XTERM300 fileset allows you to use your HP 9000s300 or 9000s400 computer as an X-Terminal. The X-Terminal can connect via XDMCP to another computer, called an X-Terminal Server that offers login services such as vuelogin(1) and logon as if the X-Terminal was connected directly to the X-Terminal Server. 

The XTERM300 fileset is loaded on an HP 9000 computer that will act as an X-Terminal Boot Server. The X-Terminal Boot Server is the computer that receives boot requests from an X-Terminal. It also may or may not be the X-Terminal Server described above. Once the XTERM300 fileset is installed on the X-Terminal Boot Server you will need to configure an X-Terminal for use. This is done with the /usr/xterm300/bin/xtconfig utility. The xtconfig utility is run by the system administrator. 

Each X-Terminal may connect to a different X-Terminal Server. The individual X-Terminal Server machines will provide a working environment for the X-Terminal. Using a machine as an X-Terminal Server implies extra demands on the X-Terminal Server. The X-Terminal Server must have adequate system resources such as disk space, RAM and CPU bandwidth for the X-Terminal to operate smoothly. HP recomends treating each X-Terminal serviced by an X-Terminal Server as an additional user with respect to system tuning. You may need the system administrator to adjust the kernel paramaters such as MAXUSERS,NPROC, NPTY and MAXUPRC. 

CONFIGURATION

Each X-Terminal is configured for use using the /usr/xterm300/bin/xtconfig utility. This utility must be run by the system administrator. Before running xtconfig you will need to obtain several pieces of information that are specific to each X-Terminal. These are listed below. 

The hexadecimal link level address for each X-Terminal. This address is displayed on the X-Terminal console at boot time. ie: 0800099124CC

The IP address in dot notation that will be used by the X-Terminal.  ie:1.2.3.4

The IP address in dot notation of the X-Terminal Server

The netmask that will be used by the X-Terminal

The IP address in dot notation of the machine that your font server will be running on. Normally this will be the same address as that of the X-Terminal Server. This is the default. 

The port number that the font server listens on. The default is 7001. 

The IP address in dot notation of a default gateway that the X-Terminal will use. The dafault is the same as the X-Terminal Boot Server. 

After you have obtained this information, run the xtconfig utility with the -u option to update the configuration. You will be prompted for the information you need and for any further action that you need to take. 

CUSTOMIZING

The XTERM300 fileset allows you to customize the behavior of the X-Terminal much as you would for any other X-Terminal. However; you will find some differences in file locations and naming conventions. For the user running a vanilla X-Terminal, this should not be an issue. The xtconfig utility should cover all setup and configuration for these users. 

If you are planning on running your X-Terminal with multiple screns or a non-default display mode you will need to enter this information in the correct file for the XTERM300 fileset to work correctly. The files that are normally used to perform this type of action, such as /usr/lib/X11/X0screens are found in a different location. This location is slightly different for each X-Terminal. The path naming convention is as follows:

/usr/xterm300/usr/config/IP-ADDRESS with IP-ADDRESS being the IP address for the X-Terminal that you want to customize. 

Note that the X-Terminal specific directory will be created by the xtconfig utility. The normal procedure is to run xtconfig and then perform any further customization that is required. The configuration files in the per-client directory follow the same rules for configuration as the configuration files in the standard /usr/lib/X11 directory. 

DEPENDENCIES

The XTERM300 fileset is designed to be installed on multiple versions of HP-UX running on different types of HP hardware. This design prevents the XTERM300 fileset from containing explicit dependencies on other filesets. It is up to the system administrator to verify that the necessary filesets are installed on the X-Terminal Boot Server. Note that there are also different dependencies on the X-Terminal Boot Server and the X-Terminal Server. 

X-Terminal Boot Server dependencies:

The RBOOTD and NFS-RUN filesets must be installed on the X-Terminal Boot Server. If you do not have these two filesets installed, the XTERM300 fileset will not operate correctly. To install these two filesets, use the /etc/update(1m) command and mark the asppropriate filesets for installation. 

The X-Terminal Boot Server services boot requests from an X-Terminal and provides access to binary files via NFS for the X-Terminal. The X-Terminal must me able to NFS mount the /usr/xterm300 directory. See the nfs(7) manual page and the exportfs(1m) manual page for more information. 

The /etc/rbootd process must be running for the X-Terminal to communicate boot requests to the X-Terminal Boot Server. The normal method for starting the /etc/rbootd process is via /etc/rc. If rbootd is not running on the X-Terminal Boot Server have your system administrator start it manualy and verify that rbootd will be started in the future via the /etc/rc file. See the rbootd(1m) manual for more information. 

X-Terminal Server dependencies:

The X-Terminal requires access to fonts to display data correctly on the screen.  Access to fonts is provided by the fs(1) command. If the font server is not running or was configured incorrectly while using the xtconfig utility the X-Terminal will not function correctly. You must have the font server running on the machine specified by the xtconfig utility and the listen port must be correct.  A commented entry for the correct usage of this utility was added to the file /fI/etc/rc when the XTERM300 fileset was installed. See /etc/rc for an example of how to start the font server. 

The X-Terminal Server must also be running the vuelogin(1X) process for the X-Terminal to function correctly. If vuelogin(1X is not running, the X-Terminal will not see a login screen. If the X-Terminal Server runs VUE by default then no further action needs to be taken. If the X-Terminal Server does not run VUE, you will need to start the vuelogin(1X) process manually. You may automate this procedure by uncommenting the vuelogin entry in the localrc function within the /etc/rc file. A commented entry with the proper use for the vuelogin command was added when you installed the XTERM300 fileset. If the X-Terminal Server does not run VUE and you want to use the system console on the X-Terminal Server for non VUE related tasks, you need to edit the file /usr/vue/config/Xservers and comment out the line that contains Local local@console. If this is not done, vuelogin will display the VUE login screen on the console. 

AUTHOR

XTERM300 fileset was developed by HP. 

FILES

/usr/xterm300/* X-Terminal runtime files, commands and utilities. 

/usr/xterm300/bin/xtconifg Configuration utility for adding and deleting X-Terminal clients. 

/etc/boottab Contains X-Terminal specific entries for rbootd(1m)

/usr/vue/config/* VUE specific onfiguration files. 

/usr/lib/xtclient.data Contains information on each client that boots as an X-Terminal from this X-Terminal Boot Server. Information is added by xtconfig(1)

/usr/lib/xtkern.300 Kernel for the X-Terminal

/usr/lib/xtfs.300 RAM filesystem for the X-Terminal

/usr/boot/SYSXTERM Boot code for X-Terminal

SEE ALSO

X(1), fs(1), rbootd(1m), nfs(7). 

STANDARDS CONFORMANCE

None

  —  February 27, 1995