.if n .pH scrn.chap1 @(#)chap2	40.5
.BK "Source Code Product Build Instructions"
.CH "Graphics Source Product Installation and Build Instructions" 2
.H 1 "The Graphics Source Product"
The System V Release 4.0 Graphics Source Product consists of
the following components:
.BL
.LI
XWIN Server, Xlib, Intrinsics, clients and utilities (based on X11 R3 of
MIT's X Window System)
.LI
OPEN LOOK Graphical User Interface Toolkit and clients
.LE
The Graphics Source Product is packaged as \f4cpio\fP archives on a 6250
bpi nine-track tape, a 386 60-megabyte SCSI quarter-inch tape, and a 3B2 CTC
cartridge tape.
.P
The nine-track tape contains
.BL
.LI
XWIN/OPEN LOOK for the i386 porting base
.LI
XWIN/OPEN LOOK for the u3b2 porting base
.LE
.P
The 386 cartridge tape contains
.BL
.LI
XWIN/OPEN LOOK for the i386 porting base
.LE
.P
The 3B2 cartridge tape contains
.BL
.LI
XWIN/OPEN LOOK for the u3b2 porting base
.LE
.P
For information pertaining to the contents of the Graphics Source
Product tape, refer to Appendix A.
.H 1 "Dependency Notes"
.H 2 "Hardware Dependencies"
The procedures described here for installing and building the
System V Release 4.0 Graphics Source Product are based on a
AT&T 3B2/400 running UNIX System V Release 4.0 and an AT&T 6386 WGS
running UNIX System V Release 3.2.1, 3.2.2, or 4.0.
.H 3 "Space Requirements"
The space requirements table (Figure 2-1) shows the disk space requirements for the two components of
the Graphics Source Product in units of 512-byte blocks.
.FG "Space Requirements for the Graphics Source Product"
.TS
center, expand, doublebox;
l|c|c
l|c|c.
	XWIN/OL (u3b2)	XWIN/OL (i386)
=
Installation of source tree	56,000	56,200
_
Compilation	42,000	83,000
_
Installation of binary tree	24,000	50,000
_
Space needed in \f4/usr/lib\fP	1,000	1,000
.TE
Notes about the table:
.BL
.LI
For compilation: in addition to the disk space required for the installation of the source
tree.
.LI
The binary tree is where the libraries and executables will be installed
from the source tree (i.e., \f4/usr/X\fP).
.LI
For space needed: only if compiling on System V Release 4.0.
This space is needed for installing \f4/usr/lib/libX11.so.1.\fP
.LE
.H 3 "Building With Insufficient Disk Space"
If you do not have the necessary disk space as specified in the table above,
try the following:
.BL
.LI
If there is not enough space in the \f4/usr\fP file system to install the
binary tree, use symbolic linking (available only in System V Release 4.0
UNIX systems) to link a directory (with sufficient disk space) from another
file system to \f4/usr/X\fP (this is where the XWIN and OPEN LOOK binary
tree will be installed).
For example, you might enter
.DS UI
\f4mkdir /usr2/X
ln -s /usr2/X  usr/X
.DE
.AB N
This must be done before running \f4make install\fP. The \f4/usr/X\fP
must not exist before linking.
.AC
.LI
Another way of resolving the disk space problem would be to run
\f4make install\fP in individual directories in the source tree
rather from the top level of the source tree, and clean up parts
of the source tree as you go along. For instance
.DS UI
\f4cd fonts
make install
make clobber
cd server
make install
make clobber\fP
.DE
You should do this on the \f4X11\fP and \f4lib\fP
directories last as some libraries and header files in that
directory might still be required during the \f4make install\fPs.
We suggest you do the \f4make install\fP in the following order:
.AL
.LI
\f4fonts\fP
.LI
\f4server\fP
.LI
\f4rgb\fP
.LI
\f4nameserver\fP
.LI
\f4local\fP
.LI
\f4clients\fP
.LI
\f4demos\fP
.LI
\f4contrib\fP
.LI
\f4att\fP
.LI
\f4examples\fP
.LI
\f4util\fP
.LI
\f4X11\fP
.LI
\f4lib\fP
.LE
.LE
.H 2 "Software Dependencies"
If you are building XWIN and OPEN LOOK on a 3B2, the following software packages must be installed on your machine in addition to the basic
UNIX system software:
.BL
.LI
C Programming Language Utilities
.LI
EMD Utilities
.LI
Internet Utilities
.LI
Networking Support Utilities
.LI
RFS Utilities
.LI
STARLAN NETWORK 3B2 Name-to-Address Mapping
.LI
STARLAN NETWORK 3B2 NAU Package Release 3.2
.LI
NPP-StarGROUP Software OSI Network Program Version 3.3 FTI
.LI
Terminal Information Utilities
.LE
If you are building XWIN and OPEN LOOK on a 386, the following software
packages must be installed on your machine in addition to the
basic UNIX system software:
.BL
.LI
C Software Development Set
.LI
Extended Terminal Interface (ETI) Package
.LI
FMLI
.LI
FACE
.LI
Mouse Driver Package
.LI
Network Support Utilities Package
.LI
Remote File Sharing (RFS) Package
.LI
Depending on what network configuration will be used
.DL
.LI
STARLAN Network 386 Network Program Package
.LI
NP622A (Version 2.1) Interlan TCP/IP Package
.LI
Wollongong Integrated Networking WIN/386 Release 3.0.1 Package
.LE
.LE
.H 1 "Source Installation Instructions"
In the procedures below, \f4I386SRCDIR\fP and \f4U3B2SRCDIR\fP are the source
directories for the i386 XWIN/OPEN LOOK source tree and the u3b2 XWIN/OPEN LOOK
source tree.
It is recommended that you do not install the XWIN/OPEN LOOK source
in the \f4/usr\fP file system unless you have enough disk space.
This is because that is where the XWIN/OPEN LOOK binary tree
will be installed.
The XWIN/OPEN LOOK source code will be installed in a relative
path of \f4usr/src/X11R3\fP.
.H 2 "Installing Source From the Nine-Track Tape"
\f4TAPE\fP
is to be substituted with the tape device name for the source tape.  The
two \f4cpio\fP archives on the nine-track source tape were written at 6250 bpi.
.P
.AB N
We assume you are at the beginning
of the tape in each step.  If you want to read the next file after
reading the previous one, use the option appropriate to your site to
not rewind the tape after reading the previous file.  Make sure that
the source directory exists before reading the tape and that you are
in a different source directory before reading the next file.
.AC
.BL
.LI
To read the first and second files consecutively, enter:
.nf
.sp
\f4	cd $I386SRCDIR
	cpio -icdvB < $TAPE\fP \f2(with "no rewind" option)\fP
\f4	cd $U3B2SRCDIR
	cpio -icdvB < $TAPE\fP 
.LI
To read the first file only, enter:
.nf
.sp
\f4	cd $I386SRCDIR
	cpio -icdvB < $TAPE\fP
.fi
.LI
To read the second file only, enter:
.nf
.sp
\f4	cat $TAPE > /dev/null\fP \f2(with "no rewind" option)\fP
\f4	cd $U3B2SRCDIR
	cpio -icdvB < $TAPE\fP
.fi
.LE
.H 2 "Installing Source From the Cartridge Tapes"
To read the i386 source code from the 386 cartridge tape:
.AL
.LI
Insert the cartridge tape containing the i386 source code
into the tape drive.
.LI
Enter
.DS UI
\f4cd $I386SRCDIR\fP
.DE
.LI
Enter
.DS UI
\f4cpio -icdvC102400 -I /dev/rmt/c0s0r\fP
.DE
.AB N
You must have the 386 Cartridge Tape Utilities installed on
your machine to read the cartridge tape containing the i386 source code.
.AC
.LE
To read the u3b2 source code from the cartridge tape:
.AL
.LI
Insert the cartridge tape containing the u3b2 source code
into the tape drive.
.LI
Enter
.DS UI
\f4cd $U3B2SRCDIR\fP
.DE
.LI
Enter
.DS UI
\f4ctccpio -idvT/dev/rSA/ctape1\fP
.DE
.AB N
You must have the 3B2 CTC Cartridge Tape Utilities installed on
your machine to read the cartridge tape containing the u3b2 source code.
.AC
For example, to install the i386 XWIN/OPEN LOOK source code
from the 386 cartridge tape in the \f4/usr2/graphics/i386\fP
directory, enter
.DS UI
\f4cd /usr2/graphics/i386
cpio -icdvC102400 -I /dev/rmt/c0s0r\fP
.DE
When the source installation is completed, you will find
the i386 XWIN/OPEN LOOK source code in \f4/usr2/graphics/i386/usr/src/X11R3\fP.
.LE
.H 1 "Content of the XWIN/OPEN LOOK Source Trees"
The following files and directories should be present in the top level
of the i386 and u3b2 XWIN/OPEN LOOK source trees after the Graphics Source Product is installed.
.TS
center, expand, doublebox;
l|c
lf4|l.
File/Directory Name	Description
=
Imakefile	template to create main makefile
X11	X11 headers and bitmaps
att	AT&T-specific client programs, demos, and games
boot.sh	shell script to create all makefiles and to run \f4make depend\fP
clients	X11R3 and OPEN LOOK client programs
contrib	contributed software
demos	X11R3 demos
examples	Athena widget examples
extensions	server extensions
fonts	font utilities and fonts (\f4bdf\fP files)
lib	\f4Xaw, Xau, Xmu, Xt, X\fP
local	AT&T-specific routines for building \f4att\fP
nameserver	networking-specific code
olpkg	packaging scripts for OPEN LOOK
pkg	packaging scripts for XWIN
rgb	\f4rgb\fP database
server	source code for server (X11R3)
util	utilities and templates for \f4imake\fP
.TE
A list of files in each \f4cpio\fP archive is in Appendix A.  Note that the
u3b2 and i386 XWIN/OPEN LOOK source trees contain the same files with the
exception of \f4usr/src/X11R3/util/imake.includes/i386.macros\fP and
\f4usr/src/X11R3/util/imake.includes/u3b2.macros\fP which only exist in the i386
and u3b2 source tree respectively, and \f4libX11_s\fP and \f4libX11_sa.\fP which only exist
in the i386 source tree. 
.H 1 "Building the Graphics Source Product"
.H 2 "Building XWIN/OPEN LOOK"
XWIN and OPEN LOOK are treated as one product.
They are to be installed in the same source tree;
there are no overlapping files in the two products.
To build them, copy the appropriate \f4cpio\fP archive into your
source directory (refer to "Source Installation Instructions")
and follow the procedure below.
.AB N
Building XWIN/OPEN LOOK requires super-user permission.
.sp
Some warning messages will occur during \f4boot.sh, make\fP and \f4make install\fP, but they can be ignored.
.sp
If building on a 3B2, fatal "accomp" errors could occur during the build. These problems
indicate too little system swap space.
Refer to \f4swap\fP(1) for a way to dynamically increase your system swap space.
For example:
.sp
\f4cat /stand/unix /stand/unix > /home/swaptmp
.sp
swap -a /home/swaptmp 0 6416\fP
.AC
.AL
.LI
Login as \f4root\fP.
.AL a
.LI
If building on a 3B2:
.BL
.LI
Make sure that the \f4MAXUP\fP (Maximum Processes per User)
variable in \f4/etc/master.d/kernel\fP is
set to at least 50.
If not, change it and rebuild UNIX.
.LI
Set the environment variable \f4PATH\fP to include \f4/usr/ccs/bin.\fP
.LI
Set the ulimit to at least 8192.
.LE 
.AB N
The 3B2 build will take approximately 48 hours.
.AC
.LI
If building on a 386:
.BL
.LI
Make sure that the \f4MAXUP\fP variable in
\f4/etc/conf/cf.d/stune\fP is set to at least 50.
If not, change it and rebuild UNIX.
.LI
If running System V Release 4.0, 
(a)
the variables \f4NINODE\fP and \f4NS5NINODE\fP in \f4/etc/cont/cf.d/stune\fP
must both be changed to 350, and UNIX must be rebuilt.
This change increases the number of inodes, allowing
the \f4Xlib\fP shared object to build.
And (b), include \f4/usr/ccs/bin\fP in your \f4PATH\fP variable.
.LI
Set the ulimit to at least 4096.
.LE 
.AB N
The 386 build will take approximately 10 hours.
.AC
.LE
.LI
Assuming \f4SRCDIR\fP is where the source code is installed,
enter
.DS UI
\f4cd $SRCDIR/usr/src/X11R3\fP
.DE
For example, if the source tree is installed in the
\f4/usr2/graphics/i386\fP directory, change directory to 
\f4/usr2/graphics/i386/usr/src/X11R3\fP.
.LI
To build the necessary nameservers the
variable \f(CWNAMESEPVERS\fP
should be set in the template file
(\f(CWutil/imake.includes/Imake.tmpl\fP) to the proper value.
For example, to enable the STARLAN nameserver and Wollongong
tcp nameserver, enter
.DS UI
\f(CWNAMESERVERS=starserver tcpserver\fP
.DE
.AB N
In addition to STARLAN
and MICOM-INTERLAN Ethernet, XWIN will also communicate using the
Wollongong Ethernet package.  Also, the networking environment changes under
the new System V Release 4.0 name-to-address translation utilities.
.sp
Currently, three nameservers can be built on System V Release 3.2.x.
They are \f(CWstarserver\fP, \f(CWitserver\fP
and \f(CWtcpserver\fP.
The \f(CWitserver\fP and \f(CWtcpserver\fP share the same source file,
\f(CWitserver.c\fP.
The makefile will pass the flag \f(CW-DITSERVER\fP to \f(CWcpp\fP when building
\f(CWitserver\fP and \f(CW-DTCPSERVER\fP when building \f(CWtcpserver\fP.
Note that these nameservers are not required for SVR4.0 systems.
.sp
The \f(CWitserver\fP depends on the MICOM-INTERLAN package and
\f(CWtcpserver\fP depends
on the Wollongong package during compilation.
.AC
.LI
Enter
.DS UI
\f4chmod +x boot.sh\fP
.DE
.LI
Enter
.DS UI
\f4nohup boot.sh > nohup.boot &\fP
\f4tail -f nohup.boot\fP (to monitor this step's progress)
.DE
.sp
Note that this step will take approximately 2 hours on a 386 with
4MB RAM or 8 hours on a 3B2/400.  When this step is completed,
the last two lines in \f4nohup.boot\fP should be:
.DS UI
\f4making scripts ...
depend not required for $SRCDIR/util/scripts\fP
.DE
.LI
Enter
.DS UI
\f4nohup make > nohup.make &\fP
\f4tail -f nohup.make\fP (to monitor this step's progress)
.DE
.sp
Note that this step will take approximately 6 hours on a 386 with
4MB RAM or 35 hours on a 3B2/400.  When this step is completed,
the last two lines in \f4nohup.make\fP should be:
.DS UI
\f4/bin/ln lninst.sh lninst.script
/bin/ln mkdirhier.sh mkdirhier.script\fP
.DE
.LI
Enter
.DS UI
\f4nohup make install > nohup.install &\fP
\f4tail -f nohup.install\fP (to monitor this step's progress).
.DE
.sp
Note that this step will take approximately 2 hours on a 386 with
4MB RAM or 5 hours on a 3B2/400.  When this step is completed,
the last two lines in \f4nohup.install\fP should be:
.DS UI
\f4/bin/mv /usr/X/bin/mkdirhier.script /usr/X/bin/mkdirhier
install done\fP
.DE
.LI
Enter
.DS UI
\f4cp lib/X/libX11_s  lib/X/libX11_s.a  /usr/X/lib\fP
.DE
if building on a 386 running SVR4.0.
.LI
Change the owner and group of all the files in \f4/usr/X\fP to
\f4bin\fP.
Enter
.DS UI
\f4cd /usr/X
find -exec chgrp bin {} \e;
find -exec chown bin {} \e;\fP
.DE
.LE
Please note the following about building the Graphics Source Product:
.BL
.LI
Both dynamic shared library and archive versions of the X library
are built under UNIX System V Release 4.0.
The X library is built as a static shared library on UNIX System V Release 3.2.x.
.LI
If you are copying the System V Release 4.0 XWIN/OPEN LOOK binaries
to another machine, be sure to relink
\f4/usr/lib/libX11.so.1\fP to
\f4/usr/X/lib/libX11.so\fP.
.LI
The server and fonts will not be built on the 3B2.
.LI
The default destination directory (\f4DESTDIR\fP) is \f4/usr/X\fP and should not be
changed.
.LI
Building in a cross environment is not supported.
.LI
Note that the OPEN LOOK examples in the \f4examples/Xol\fP directory
will not be built in the procedure above.
To compile the OPEN LOOK examples, you have to run \f4make all\fP
in the \f4examples/Xol\fP directory to build all the OPEN LOOK
examples, or \f4make\fP in the individual directories under \f4examples/Xol\fP.
.LE
.H 1 "Setup Procedures for Executing XWIN and OPEN LOOK"
.H 2 "Setup for XWIN"
.AB N
You need root privileges to run the following procedure.
.AC
To run the \f4xwin_setup2.0\fP script:
.AL
.LI
Enter
.DS UI
\f4cd $SRCDIR/usr/src/X11R3/pkg
PATH=$PATH:/usr/ccs/bin export PATH\fP\f2 (if running System V Release 4.0)\fP
\f4sh xwin_setup2.0\fP
.DE
.P
This shell script sets system tunables, creates default XWIN files,
installs the console emulator, sets up \f4/dev/X\fP, copies files
from \f4$DESTDIR/lib/terminfo\fP to \f4/usr/lib/terminfo\fP, and modifies
\f4/etc/profile.\fP
.LI
Reboot your machine to link to the new kernel after it is rebuilt in the
Step 1.
.LI
On the machine that will be running clients,
set the \f4DISPLAY\fP environment variable to \f4machine-name:0\fP
(where \f4machine-name\fP is the name of the machine running
the X server), and export \f4DISPLAY\fP.
For example, if the machine on which the X server will be
running is named \f4bonzo\fP, enter
.DS UI
\f4DISPLAY=bonzo:0; export DISPLAY\fP
.DE
on the client machine.
.LE 
.H 3 "Running XWIN Over the Network on System V Release 3.2.x Systems"
To administer the network for XWIN and OPEN LOOK on System V Release 3.2.x systems,
use \f4olam\fP, the OPEN LOOK Administration Manager. Refer to the
.BT "Programmer's Guide: OPEN LOOK\(tm Graphical User Interface"
for information on \f4olam\fP.
.H 3 "Running XWIN Over the Network on System V Release 4.0 Systems"
When listening for connections on System V Release 3.2.x systems, the XWIN
server uses the directory \f(CW/usr/X/lib/net\fP to
determine the available networks.
On System V Release 4.0 systems, the XWIN server
uses the SHELL variable \f(CWNETPATH\fP instead.
Set \f(CWNETPATH\fP by entering
.DS UI
\f(CWNETPATH="net1:net2:...:netN"; export NETPATH\fP
.DE
where \f(CWnet1\fP, \f(CWnet2\fP, \f(CW...\fP, \f(CWnetN\fP
are network identifiers (NIDs).
Each NID must match the first column of an entry
in the network configuration table \f(CW/etc/netconfig\fP.
If \f(CWNETPATH\fP is not set, the server will
listen to all networks listed in \f(CW/etc/netconfig\fP.
.sp
On System V Release 3.2.x systems, XWIN clients wishing to establish connections
with remote servers use the table \f(CW/usr/X/lib/Xconnections\fP to
determine available networks.
On System V Release 4.0 systems,
XWIN clients use the SHELL variable \f(CWNETPATH\fP for that purpose.
Clients will try to connect to a remote server via the networks
represented by the NIDs listed in the \f(CWNETPATH\fP variable.
The networks will be tried one after the other, in the order listed,
until a connection succeeds.
If \f(CWNETPATH\fP is not set, all the networks listed in
\f(CW/etc/netconfig\fP will be tried.
If a connection cannot be established with the remote server,
the Xlib call \f(CWXOpenDisplay\fP will fail.
\f(CW/usr/X/lib/xdaemon\fP is not used on System V Release 4.0 systems.
.sp
For each network, there are two files that need to be updated:
\f(CWhosts\fP and \f(CWservices\fP.
For TCP/IP, these two files resides in \f(CW/etc\fP,
for STARLAN they reside in \f(CW/etc/net/starlan\fP.
.sp
On the client side, the \f(CWhosts\fP file must have a line
containing the address of the remote host running the server.
On the server side, if you want
the server to listen for connections over a particular network,
an entry for the server's host is required in the
\f(CWhosts\fP file for that network.
Each entry in a \f(CWhosts\fP file must have the following format:
.sp
.ti +8n
\f(CWhost-name	host-address\fP
.sp
where the structure of \f(CWhost-address\fP is network dependent.
For example, the file \f(CW/etc/hosts\fP, used for TCP/IP,
will have entries like this:
.sp
.ti +8n
\f(CWfoo	186.23.45.137\fP
.sp
while \f(CW/etc/net/starlan/hosts\fP, used for STARLAN,
will have entries like this:
.sp
.ti +8n
\f(CWfoo	foo-uname\fP
.sp
The \f(CWservices\fP files describe on which port the server will
be listening for connections.
There should one entry for each display.
If your machine has more than one display, there will be multiple
entries in each \f(CWservices\fP file.
For TCP/IP, the file \f(CW/etc/services\fP should have the following
entry for \f(CWDisplay 0\fP:
.sp
.ti +8n
\f(CWxserver0	6000/tcp\fP
.sp
For STARLAN, the file \f(CW/etc/net/starlan/services\fP
should have the following entry for \f(CWDisplay 0\fP:
.sp
.ti +8n
\f(CWxserver0	0\fP
.sp
.H 2 "Setup for OPEN LOOK"
If OPEN LOOK is to be used, the following setup procedure must be done
in addition to the procedure described in "Setup for XWIN."
.AL
.LI
Enter
.DS UI
\f4cd $SRCDIR/usr/src/X11R3/olpkg/adm
find . -print | cpio -pv /usr/X/adm\fP
.DE
to copy the files in the \f4olpkg/adm\fP in the source tree to \f4/usr/X/adm.\fP
.LI
Enter
.DS UI
\f4cd /usr/X/adm
chmod +x ol*
oladduser\fP \f2login\fP
.DE
This sets up the proper environment to run OPEN LOOK for
a particular user
and creates two files called \.\f4Xdefaults\fP and \f4.olinitrc\fP
in your home directory.
The \f4.olinitrc\fP file contains the following lines:
.DS UI
\f4olwm &
olfm &\fP
.DE
This will run the window manager and file manager at startup.
.LE
.H 1 "Running XWIN and OPEN LOOK Clients"
After doing the setup procedures above, the following
procedures may be used to run the X server and clients.
.H 2 "Running System V Release 3.2.x Clients on a System V Release 3.2.x System"
.AL
.LI
If you are running on a machine running UNIX 3.2.x and are
running clients on a different machine from the X server
(\f4remote\fP session),
enter
.DS UI
\f4/usr/X/lib/xdaemon &\fP
.DE
to run \f4/usr/X/lib/xdaemon\fP in the background.
.P
If the remote machine is running UNIX 3.2.x, then
\f4/usr/X/lib/xdaemon\fP should be run there as well.
.LI
If you are running OPEN LOOK clients, the X server must be
told where the OPEN LOOK fonts may be found.
Options 1 and 2 below explain how you might do this.
In the examples, note that
\f4$FDIR\fP is the installed location of the fonts.
For example, it is set to \f(CW/usr/X/lib/fonts\fP when \f4/usr/X\fP
is the installed location for the XWIN tree.
.VL 1i
.LI "Option 1:"
Enter
.DS UI
\f4XWINFONTPATH=$FDIR/Xol/,$FDIR/misc/,$FDIR/75dpi/,
     $FDIR/100dpi

export XWINFONTPATH\fP
.DE
to set the environment variable \f4XWINFONTPATH\fP on the machine
on which the X server will be run, and export \f4XWINFONTPATH\fP before
running the server.
This can be done in your \f4$HOME/.profile\fP so that the variable will be set
automatically when you log in. In order for the
OPEN LOOK\f4Start OPEN LOOK at login\fP feature to work, the \f4XWINFONTPATH\fP
variable must be set to include \f4/usr/X/lib/fonts/Xol\fP
at login.
.LI "Option 2:"
Enter
.DS UI
\f4X -fp $FDIR/Xol/,$FDIR/misc/,$FDIR/75dpi/,
     $FDIR/100dpi &\fP
.DE
to start the server with a font path argument.
.LE 1
.LI
If using XWIN without OPEN LOOK, enter
.DS UI
\f4X &
arbitrary_X_client &\fP
.DE
to start the X server manually and run the desired XWIN clients.
.LI
If using OPEN LOOK:
.VL 1i
.LI "Option 1:"
If running the clients and X server on the same machine
(\f4local\fP session), \f4olinit\fP may be
used to start the
X server, workspace manager, window manager, and file manager.
Note that \f4olinit\fP should not be used when the X server
is or will be running on a remote host.
.LI "Option 2:"
If running a remote session:
.BL
.LI
Start the X server manually on the server machine.
Note that the X server cannot be run on a 3B2.
.LI
Run \f4olwsm&\fP on the client machine to start the workspace
manager, window manager, and file manager.
.LE 1
.LE 1
.LE 1
.H 2 "Running System V Release 3.2.x Clients On A System V Release 4.0 System"
There is a new daemon for name-to-address translation on System V Release 4.0
called \f(CWxntad\fP (X name to address daemon.)
This daemon is intended only for clients 
compiled and linked with the X static shared library on a System V Release 3.2.x
machine.
This daemon will use the name-to-address translation library
in System V Release 4.0 to do the translation
rather than fork a nameserver.
The functionality provided by
\f(CW/usr/X/lib/Xconnections\fP will be replaced by the SHELL variable
\f(CWNETPATH\fP described above.
.P
If you will be running clients compiled and linked
on an System V Release 3.2.x system, you must manually install the provided
static shared X library into \f4/usr/X/lib\fP before running the clients.
(This is the Step 8 in "Building XWIN/OPEN LOOK" above.)
The \f(CWxntad\fP can only be used with the provided static shared
X library; do not attempt to use an older static shared X library.
.P
The new daemon, \f(CWxntad\fP, is executed automatically
at boot time on System V Release 4.0 systems.
If you will not be using any clients compiled and
linked on an System V Release 3.2.x system, you may not want the
daemon to execute automatically at boot time.
If you do not want the daemon to execute at boot time,
delete the following files:
.DS UI
\f(CW/etc/init.d/xwin
/etc/rc2.d/K95xwin
/etc/rc3.d/S95xwin\fP
.DE
