test

OpenWindows Advanced User's Guide

Appendix E SPARC -- DECnet Internetworking (DNI)

This appendix describes how to internetwork the OpenWindows environment and the DECwindowsTM environment via the NSP DECnet transport protocol.

SPARC only -

Note that this whole chapter concerning "DECnet Internetworking" applies only to SPARC-based machines. DECnet internetworking is also available only with 8.x DNI.

There are two DNI scenarios:

These two scenarios are described in the following sections after an initial section on how to set up the DNI software for either scenario.

E.1 Setting Up DECnet Internetworking

To set up DECnet internetworking, follow these steps:

  1. Enable a connection via DNI.

    The OpenWindows server and client libraries use a dynamically loadable version of the DNI transport library libdni. In order for the server and client libraries to load libdni you must set the environment variable DNI_X_ENABLE to the directory where libdni.so is installed.

    The example below assumes you loaded DNI via pkgadd in the default location:

    $ DNI_X_ENABLE=/opt/SUNWconn/dni/lib

  2. Start the OpenWindows server.

    By default, the OpenWindows server supports "MIT-MAGIC-COOKIE" security. This security mechanism is user-specific, rather than host-specific -- you decide which users may connect to the server instead of which machines may connect to the server. In the default mode, the xhost command returns an empty list, and states only that security is turned on. You can turn off this security mode (and revert to the security mode of previous OpenWindows server versions) by using the -noauth option with the openwin command.

    $ openwin -noauth

  3. Request the owner of the machine running the OpenWindows software to use the xhost command to give DEC® VAX® permission to have an X11 connection to the OpenWindows server.

    In order for X11 clients to connect to the OpenWindows server through the DNI software, the DECnet node addresses must be mapped to their DECnet node names. You do this by creating and initializing the NCP database. This must also be done on the DEC VAX system.

    $ xhost decvax::

    The double colon specifies the DECNet transport.

E.2 Displaying a Remote Client on an OpenWindows Machine

You can run X11 clients from VMS by using the SunLink DNI dnilogin command to log into the VAX system. First, set the environment variable DISPLAY on your local machine to be the X11 server on the remote machine. Then run an X11 client by entering the name of the client, represented here by x11_client. (See the VMS DECwindows User's Guide, Running Applications Across the Network for more information on using the VMS operating system.)

For example:

$ dnilogin decvax
   .
   .
   .
$ define DECW$DISPLAY OW_machine::0
$ spawn/nowait run x11_client

E.3 Displaying a Remote Client on a VAX

You can run X11 clients on an OpenWindows machine and display them on a DECwindows server by setting the DISPLAY variable to the remote VAX system.

Before you can run any of the X11 clients you must compile and install the OpenWindows fonts in the DECwindows server. These fonts are available in the X11R5 release or in the optional font package with the OpenWindows software. Follow these steps to install the proper fonts in the DECwindows server:

  1. Install the optional OpenWindows font sources (of the font sources from the X11R5 release) on the OpenWindows machine.

  2. See the Solaris X Window System Developer's Guide for font installation instructions.

  3. Copy the font sources to a directory on the VAX system.

    $ cd /usr/openwin/share/src/fonts/misc$ dnicp *.bdf `decvax::[vaxdir]'

  4. Compile the cursor fonts on the VAX system.

    This results in files such as: olcursor.decw$font;1 olglyph10.decw$font;1...

    $ font olcursor.bdf
$ font olglyph10.bdf
...

  5. Copy the fonts to the sysfont directory:

    $ set def sys$sysroot:[sysfont.decw.user_cursor16]
$ copy [vaxdir]olcursor.decw$font;1 *

    Note -

    You must be logged in as "system" on the DEC VAX system to copy the fonts to the sysfont directory.

  6. You must also perform steps 2-4 for the rest of the cursor fonts and for the Lucida fonts in /usr/openwin/share/src/fonts/75dpi and /usr/openwin/share/src/fonts/100dpi.

    Note -

    The Lucida fonts should be installed in sys$sysroot:[sysfont.decw.user_75dpi] and sys$sysroot:[sysfont.decw.user_100dpi].

    The following list shows the minimum working set of fonts needed to be installed in order to run the OpenWindows DeskSet tools. If you are using default fonts for the applications you should only have to install these fonts. You can, however, install more fonts as needed.

    • olcursor.bdf

    • olglyph10.bdf

    • olglyph12.bdf

    • olglyph14.bdf

    • olglyph19.bdf

    • luBS08.bdf

    • luBS10.bdf

    • luBS12.bdf

    • luBS14.bdf

    • luRS08.bdf

    • luRS10.bdf

    • luFS12.bdf

    • lutBs12.bdf

    • lutRS10.bdf

    • lutRS12.bdf

  7. Restart the DECwindows server.

  8. You can verify that the fonts were installed by listing the available fonts in the DECwindows server:

    $ DISPLAY=decvax::0
$ xlsfonts | grep Sun   (Cursor fonts)$ xlsfonts | grep Lucida

  9. Make sure you have given the OpenWindows node permission to display on the DECwindows server by using the Security Menu in the DECwindows Session Manager.

  10. Run an X11 application (for example, an OpenWindows DeskSet tool).

    $ DISPLAY=decvax::0
$ mailtool

    Note -

    DNI_X_ENABLE must be set to the location of the DNI transport library libdni. See Step 1 under "E.1 Setting Up DECnet Internetworking", in this chapter.

    If an error message such as the one below is printed, you need to install that font in the DECwindows server in order to run the application.


    XView warning: Cannot load font
  `-b&h-lucida-medium-r-*-*-*-80-*-*-*-*-*-*' (Font package)

    This error message means font luRS10.bdf needs to be installed.

    See the Solaris X Window System Developer's Guide for more information on fonts.