.nr PO 1.5i
.nr LL 5.5i
.nr FL 5.5i 
.nr HL 5.5i
.nr PD 0.7v
.nr PI 0.5i
.	\" IX - index words to stderr
.de IX
.tm \\$1 \\$2 \\$3 \\$4\t2-\\n(PN
..
.ds CH "\f2EXOS 8015-01:  Installation\f1 
.ds CF "2\-%
.de GD
.sp 0.2 
.vs 2
\l'5i'
\l'5i'
.LP
.sp -1.0
..
.de GP
.fi
\l'5.0i'
..
.fp 1 HR
.fp 2 MI
.fp 3 HB
.bd 2 2
.LP
.nh
.lt 5.5i
.NH 1
.NH 1
.pn 1
.bp
.ps 12
.tl '''Chapter  2'
.vs 15
.B 
.tl '''INSTALLATION'
.R
.NH 2
INTRODUCTION
.RS
.LP
The EXOS\ 8015 TCP/IP Network Software is designed for use on VAXes
running AT&T UNIX System V
(Release 2, Version 2 or Release 2.0, Version 2).
The EXOS 8015 TCP/IP software is distributed on a standard
magnetic tape in UNIX \f2tar\f1 format.
The software includes several binary (executable) files, 
an archive (programming library), 
and a device driver that is linked with the UNIX\ kernel.
.LP
Before installing the EXOS\ 8015 software, you must first
suitably configure the EXOS 204 Intelligent Ethernet Controller
and then install it in your VAX.
To install the software, you login as the super user, copy the
EXOS 8015 files from the distribution tape, and set several
installation parameters.
When the procedure is done, you shutdown the system
and then reboot it with the new\ kernel.
.LP
Note that the EXOS 8015 I/O drivers add about 12 Kbytes (\(+-2\ Kbytes, 
depending on code compactness) to the UNIX kernel's code segment.
.IX kernel, UNIX
The drivers borrow buffers from the kernel's disk buffer cache
for message queues and data buffers.
Therefore, they do not add appreciably to 
the kernel's data segment size.
.LP
This chapter describes the installation of the EXOS\ 8015
network software on a VAX/UNIX system.
.RE
.NH 2
PREREQUISITES FOR INSTALLATION
.RS
.LP
In order to install the EXOS 8015 software,
a thorough understanding of the UNIX operating system is not required.
However, it can help if problems are encountered.
Familiarity with the UNIX
system development tools (such as \f2make(1)\f1 and \f2cc(1)\f1) and 
with the design and installation of UNIX device drivers is\ desirable.
.LP
The following is a list of prerequisites for installing 
the EXOS\ 8015 software:
.RS
.IP \(bu 3
Operating System
.br
In order to install the EXOS 8015 software on a VAX,
it must be running Release 2, Version 2 or Release 2.0, Version 2
of AT&T's UNIX System V.
.IP \(bu 3
Hardware Requirements
.br
The EXOS 8015 requires at least 128 Kbytes of on-board RAM 
on the EXOS 204 board.
.IX EXOS 205 board
The EXOS 8015 software is distributed on a standard 9-track, 
1600-bpi magnetic tape.  
Therefore, a tape drive capable of reading this kind of
tape is required.
.bp
.IP \(bu 3
EXOS 204 Board Configuration
.br
The EXOS 204 board must be configured as discussed in 
Section\ 2.4.1 and then installed in the VAX.
.IX EXOS 205 board
The following must be\ configured:
.RS
.RS
.IP \- 3
I/O Port Address (CSR).
The EXOS 204 Intelligent Ethernet Controller has two I/O ports.
.IX "I/O port address, EXOS 204"
.IX CSR
The host system I/O address space location for these ports is 
jumper-selectable.
The two ports require four contiguous bytes
within the system's I/O page, starting at a longword-aligned address.
The I/O port addresses must not overlap any other
device address that the system currently uses or may use in the future.
.IP \- 3
Interrupt Level.
.IX interrupt level, EXOS 205
EXOS 204 generates a vectored interrupt at a programmable location.
The interrupt vector location, which is jumper-selectable, should 
not conflict with any other interrupt\ level.
.RE
.RE
.IP \(bu 3
Disk Space Requirements.
.br
The network daemons and data files in the EXOS 8015 distribution
occupy about 185 Kbytes in the root file system; the utilities occupy
approximately 190 Kbytes in the \f2/usr\f1 file system.  
Most of these files can be relocated to other file systems if necessary.
.RE
.RE
.NH 2
EXOS 8015 FILES
.IX files, EXOS 8015
.RS
.LP
The EXOS\ 8015 TCP/IP software is distributed on 
a standard magnetic tape in UNIX \f2tar\f1 format.
The installation includes the directories and files 
listed in Table\ 2-1 in the directory structure shown.
This directory structure is designed for ease of installation on
a VAX running UNIX.
The contents of the directories and files listed in Table 2-1
are described in Table\ 2-2.
For a complete list of the directories and files supplied with
the EXOS 8015 distribution, refer to the \f2EXOS\ 8015 Release Note\f1.
.sp 2
.KS
.ce
\s9\f3Table 2-1:  EXOS 8015 Directory Tree\f1
.GD
.DS 
.ps 9
.vs 11
.nf
lib/
\h'\w.lib/.u'libsocket.a
\h'\w.lib/.u'libex_driver.a
net/
\h'\w.net/.u'ftpd
\h'\w.net/.u'MKNODS
\h'\w.net/.u'net
\h'\w.net/.u'netload
\h'\w.net/.u'rshd
\h'\w.net/.u'rwhod
\h'\w.net/.u'ud
usr/src/EXOS/
\h'\w.usr/src/EXOS/.u'Makefile
\h'\w.usr/src/EXOS/.u'include/EXOS/
\h'\w.usr/src/EXOS/.u'src/
\h'\w.usr/src/EXOS/src/.u'bin/test/
\h'\w.usr/src/EXOS/src/bin/test/.u'Makefile
\h'\w.usr/src/EXOS/src/bin/test/.u'sender.c
\h'\w.usr/src/EXOS/src/bin/test/.u'receiver.c
\h'\w.usr/src/EXOS/src/.u'lib/libex_driver/
\h'\w.usr/src/EXOS/src/lib/libex_driver/.u'Makefile
\h'\w.usr/src/EXOS/src/lib/libex_driver/.u'config.h
\h'\w.usr/src/EXOS/src/lib/libex_driver/.u'ex_config.c
\h'\w.usr/src/EXOS/src/lib/.u'libndir/
\h'\w.usr/src/EXOS/src/lib/libndir/.u'libndir.a
\h'\w.usr/src/EXOS/src/lib/.u'xlib/xgenlib/
\h'\w.usr/src/EXOS/src/lib/xlib/xgenlib/.u'xgenlib.a
\h'\w.usr/src/EXOS/src/lib/xlib/.u'xoslib/
\h'\w.usr/src/EXOS/src/lib/xlib/xoslib/.u'xoslib.a
\h'\w.usr/src/EXOS/src/lib/xlib/xoslib/.u'main.o
usr/bin/
\h'\w.usr/bin/.u'arp
\h'\w.usr/bin/.u'bstat
\h'\w.usr/bin/.u'exosid
\h'\w.usr/bin/.u'ftp
\h'\w.usr/bin/.u'netdump
\h'\w.usr/bin/.u'netstat
\h'\w.usr/bin/.u'rcp
\h'\w.usr/bin/.u'rlogin
\h'\w.usr/bin/.u'route
\h'\w.usr/bin/.u'rsh
\h'\w.usr/bin/.u'ruptime
\h'\w.usr/bin/.u'rwho
\h'\w.usr/bin/.u'telnet
.DE
.GP
.KE
.fi
.sp
.bp
.KS
.nr PS 9
.nr VS 11
.ps 9
.vs 11
.ce
\s9\f3Table 2-2:  EXOS\ 8015 Files\f1
.TS
doublebox;
lw(1.5i) | lw(3.3i).
.ps 9
.vs 11
\f3Directory/
   File	Contents\f1
.sp 0.4
=	=
.sp 0.1
lib/
.sp 0.1
_	_
.sp 0.1
     libsocket.a	T{
Programming library for user-written applications
T}
.sp 0.1
_	_
.sp 0.1
     libex_driver.a	T{
Object modules for the EXOS device driver
T}
.sp 0.1
=	=
.sp 0.1
net/
.sp 0.1
_	_
.sp 0.1
     ftpd	T{
\f2ftp\f1 daemon
T}
.sp 0.1
_	_
.sp 0.1
     MKNODS	T{
Shell script for creating device entries in the file system
necessary for correct operation of EXOS 8015
T}
.sp 0.1
_	_
.sp 0.1
     net	T{
Protocol module
T}
.sp 0.1
_	_
.sp 0.1
     netload	T{
Program that loads the protocol module
T}
.sp 0.1
_	_
.sp 0.1
     rshd	T{
\f2rsh\f1 daemon
T}
.sp 0.1
_	_
.sp 0.1
     rwhod	T{
\f2rwho\f1 daemon
T}
.sp 0.1
_	_
.sp 0.1
     ud	T{
\f2uucp\f1 daemon
T}
.sp 0.1
=	=
.sp 0.1
/usr/src/EXOS/
.sp 0.1
_	_
.sp 0.1
     Makefile	T{
For recompiling the driver modules if the default 
values are incorrect for your system
T}
.sp 0.1
_	_
.sp 0.1
     include/	T{
Directory that contains network
header files for user-written applications
T}
.sp 0.1
_	_
.sp 0.1
     src/lib/libex_driver/	T{
Directory that contains the driver modules, 
which are used if it is necessary to recompile them
T}
.sp 0.1
_	_
.sp 0.1
.nf
     src/libndir/, src/xlib/	T{
Directories that contain proprietary libraries
T}
.sp 0.1
=	=
.sp 0.1
/usr/bin/
.sp 0.1
_	_
.sp 0.1
     arp	T{
Executable copy of the \f2arp\f1 utility
T}
.sp 0.1
_	_
.sp 0.1
     bstat	T{
Executable copy of the \f2bstat\f1 utility
T}
.sp 0.1
_	_
.sp 0.1
     exosid 	T{
Executable copy of the \f2exosid\f1 utility
T}
.sp 0.1
_	_
.sp 0.1
     ftp	T{
Executable copy of the \f2ftp\f1 utility
T}
.sp 0.1
_	_
.sp 0.1
     netdump 	T{
Executable copy of the \f2netdump\f1 utility
T}
.sp 0.1
_	_
.sp 0.1
     netstat 	T{
Executable copy of the \f2netstat\f1 utility
T}
.sp 0.1
_	_
.sp 0.1
     rcp	T{
Executable copy of the \f2rcp\f1 utility
T}
.sp 0.1
_	_
.sp 0.1
     rlogin	T{
Executable copy of the \f2rlogin\f1 utility
T}
.sp 0.1
_	_
.sp 0.1
     route	T{
Executable copy of the \f2route\f1 utility
T}
.sp 0.1
_	_
.sp 0.1
     rsh	T{
Executable copy of the \f2rsh\f1 utility
T}
.sp 0.1
_	_
.sp 0.1
     ruptime	T{
Executable copy of the \f2ruptime\f1 utility
T}
.sp 0.1
_	_
.sp 0.1
     rwho	T{
Executable copy of the \f2rwho\f1 utility
T}
.sp 0.1
_	_
.sp 0.1
     telnet	T{
Executable copy of the \f2telnet\f1 utility
T}
.sp 0.2
.TE
.nr PS 10
.nr VS 12
.ps 10
.vs 12
.KE
.RE
.RE
.bp
.NH 2
INSTALLATION PROCEDURE
.RS
.LP
This section gives the step-by-step procedure for installing the 
EXOS 8015 TCP/IP software.
.LP
The following conventions are used in the description of the procedure: 
.RS
.IP \(bu 3
Regular, nonbold characters represent system responses.
.IP \(bu 3
\f3Bold\f1 characters represent commands, parameters, or 
values that you enter.
.IP \(bu 3
\f2Italicized\f1 characters give descriptive names for parameters that
you must replace with appropriate values.
.IP \(bu 3
Each command line is assumed to be terminated by a carriage return <cr>.
.RE
.RE
.sp
.ce 2
\f3IMPORTANT\f1 
.sp 0.5
You must be a super user to install the EXOS 8015 software.
.sp
.RS
.LP
.ne 14
As distributed, the EXOS 8015 software is set to use the
following defaults:
.RS
.IP \(bu 3
Number of TTYs:  16
.IP \(bu 3
Number of sockets:  32
.IP \(bu 3
UNIBUS address (CSR):  764000 (octal)
.IP \(bu 3
Interrupt level:  5
.IP \(bu 3
Interrupt vector location:  770 (octal)
.RE
.LP
If there is any conflict for the UNIBUS address or the
interrupt level, they can be changed as described in Section\ 2.4.1.
The number of TTYs, number of sockets, and interrupt vector
location can be changed during the EXOS 8015 software
installation, as described in Section\ 2.4.2.
.RE
.NH 3
Hardware Installation
.IX installation, EXOS 204 (b)
.RS
.LP
Before you install the EXOS 8015 software, you must check the
jumper settings on the EXOS 204 Intelligent Ethernet Controller,
reconfigure them if necessary, and then install the board into your VAX.
Refer to the \f2EXOS 204 Reference Manual\f1 for information about
the location of the jumpers.
.RS
.IP 1. 4
Determine whether you plan to use the default UNIBUS I/O
address (CSR), which is 764000 (octal).
(Note that as shipped from the factory, the EXOS 204 board is
set to the default address.)
.sp 0.6
.bp
If you do not plan to use the default address, 
set the EXOS 204 board appropriately.
Make a note of the address, as you will need it in Step 3 of
the software installation (described in the next\ section).
.IP 2. 4
Determine whether you plan to use the default interrupt level,
which is 5.
(Note that as shipped from the factory, the EXOS 204 is set
to the default interrupt level.)
.sp 0.6
If you do not plan to use the default interrupt level,
set the EXOS\ 204 board appropriately.
Make a note of the new interrupt level, as you will need it in
Step 3 of the software installation (described in the next section).
.IP 3. 4
Install the EXOS 204 board in your system. 
Refer to the \f2EXOS 204 Reference Manual\f1 and your system's 
hardware reference manual for information on installing the\ board.
.RE
.IX installation, EXOS 204 (e)
.LP
Following Step 3, you can install the EXOS 8015 software, as
described in the next section.
.RE
.NH 3 
Software Installation
.RS
.LP
After you have properly configured and installed the EXOS 204
board, as described in the previous section, you can install the
EXOS 8015 TCP/IP software.
The following steps describe the procedure for installing the software:
.IX installation, EXOS 8015 (b)
.RS
.IP 1. 4
Login as the super user and enter single-user mode.
.IP 2. 4
Change into the root directory:
.RS
.sp 0.6
#  \f3cd  /\f1
.RE
.IP 3. 4
Mount the EXOS 8015 distribution tape on the system tape drive.
.IP 4. 4
Copy the files from the distribution tape:
.DS
#  \f3tar  xvo
.DE
(Note that the last \f2tar\f1 option is the lowercase letter oh,
not a zero.)
.IP 5. 4
Start the software installation procedure:
.DS
#  \f3cd  /usr/src/EXOS\f1
#  \f3make  install\f1
.DE
The system displays the following messages and prompt:
.DS
Starting installation of the EXOS 8015 software.
.sp 0.6
The default installation parameters are as follows:
.sp 0.6
.ta 2.0i
Number of Remote Logins	= 16
Number of Sockets	= 32
UNIBUS Adapter Number	= 0
UNIBUS address	= 764000 (octal)
Interrupt Level	= 5
Interrupt Vector Location	= 770 (octal)
On-line Man Pages Installed	= yes
.sp 0.6
Do you wish to change the default settings (y/n)?
.DE
Enter \f3y\f1 to accept the default values.
The system then proceeds to install the software.  
Note that the default values for the port address and interrupt
level must agree with the jumper
settings on the EXOS 204 board installed in your system.
.sp 0.6
Enter \f3n\f1 if you want to alter any of the default values.
The system then prompts you
for each of the configurable parameters as follows.
After each prompt, enter the desired value followed by a <cr>.
Again, the default values for the port address and interrupt
level must agree with the jumper
settings on the EXOS 204 board installed in your system.
Note that entering a carriage return with no value 
uses the default value, which is given in brackets.
.RS
.IP a. 4
The system first prompts you for the number of remote logins to permit.
This is the number of logins to allow to come to your host
from remote hosts via \f2rlogin\f1 or\ \f2telnet\f1. 
.DS
Enter the number of remote logins to permit (0-64) [16]: 
.DE
It is recommended that you specify only as many logins as you think 
you will need since each login allowed consumes system resources.
(For each additional login a \f2getty\f1 process must be
running on your system.)
You may want to consider the following process information
when determining how many logins to specify:
.RS
.IP \(bu 3
The process table for UNIX System V supports 65 processes.
.IP \(bu 3
The system processes (\f2init\f1, \f2swap\f1, \f2console\f1, and
\f2cron\f1) and the EXOS\ 8015 processes (\f2ftpd\f1, \f2rshd\f1,
and two processes each for \f2rwhod\f1 and \f2ud\f1),
require 10 of the available processes.
These processes are always active.
.IP \(bu 3
Each \f2xty\f1 device enabled requires one process (\f2getty\f1).
When a remote login session begins, the \f2getty\f1 process is
replaced by a \f2sh\f1 process.
.IP \(bu 3
Each direct \f2tty\f1 device enabled requires one process (\f2getty\f1).
When a login session begins, the \f2getty\f1 process is replaced by a
\f2sh\f1 process.
.IP \(bu 3
When a remote process accesses the local host, one or two processes 
are required (one for \f2sh\f1, one for the command being executed).
These processes are required only when a remote login session
is in progress.
.IP \(bu 3
When the local host accesses a remote host, three processes are
required (\f2sh\f1, \f2telnet\f1 read, and \f2telnet\f1 write).
These processes are required only when a remote login session
is in progress.
.RE
.IP b. 4
The system prompts you for the number of sockets:
.DS
Number of sockets (0-64) [32]:
.DE
It is suggested that you select the default value of 32 sockets.
Depending on the amount of RAM present, 
EXOS 204 boards can support up to 64 sockets.
.IP c. 4
The system prompts you for the UNIBUS adapter number:
.DS
Enter the UNIBUS adapter number (0-3) [0]:
.DE
If the board is installed in the first UNIBUS adapter, 
enter "0" in response to the first prompt;
if it is installed in the second UNIBUS adapter, enter "1;" and so on.
Do not enter the NEXUS number for this adapter.
.IX NEXUS number
.sp 0.6
Note that VAX 11/750s can support only 
.ne 3
a single UNIBUS adapter.
Therefore, you must enter a 0 in response to this\ prompt.
.IP d. 4
The system prompts you for the UNIBUS address:
.DS 
Enter the UNIBUS address in octal (760000-777774) [764000]: 
.DE
Enter the port address.
It must be an octal number in the range specified in the prompt.
This address must be the same as selected in Step 1 of the
hardware installation.
.IP 3. 4
The system prompts you for the interrupt level to be used:
.DS
Enter the interrupt level for the EXOS 204 (4-7) [5]: 
.DE
The allowable interrupt levels are 4, 5, 6, and 7.  
The interrupt level must be the same as selected in Step 2 of
the hardware installation.
.IP f. 4
The system prompts you for the interrupt vector location:
.DS
Enter the interrupt vector location (0-774) [770]:
.DE
Enter the interrupt vector level.
It must be in octal and can be from one to three digits long.
.IP g. 4
The system prompts whether you want the on-line manual pages for
the EXOS 8015 software installed:
.DS
Install on-line man pages (Y/N) [Y]:
.DE
The EXOS 8015 man pages require about 160 Kbytes of space.
These are the same reference manuals pages as shown in Appendix\ A.
.RE
.IP 6. 4
The system proceeds with the EXOS 8015 installation process and
displays several self-explanatory messages during the installation.
When the installation completes, the system rebuilds the kernel
shuts itself down, and reboots.
.IP 7. 4
The system creates the file \f2/etc/hosts\f1 file if one does
not already exist on your system.
You should change the entry "host1" in this file to the name of
your system.
Refer to Section 4.5.5.2 for a discussion of the
\f2/etc/hosts\f1 file.
.sp 0.6
If the file \f2/etc/hosts\f1 already exists on your system, 
the system does not alter it nor does it create a new one.
.RE
.sp 0.6
.IX installation, EXOS 8015 (e)
.LP
Following Step 7, installation of the EXOS 8015 TCP/IP software 
is complete.
You can now begin using the EXOS 8015 network utilities
described in Chapters\ 3 and 4.
Note, however, that before you can use the \f2mail\f1 utility to
send mail between hosts on your local Ethernet network,
.ne 2
your network administrator must make the modifications 
described in Section 4.6.7.
.LP
To ensure proper communication between all systems on the network, 
you should update the \f2/etc/hosts\f1 files on all the other systems 
on your network so that each contains the name of your system as well 
as the names of all the other systems on the network.
.IX /etc/hosts file
This means that the \f2/etc/hosts\f1 file on each system should
contain the Internet address and name of every system currently
on the network.
Aliases for systems can also be included.
Refer to Section\ 4.5.5.2 for a discussion of the \f2/etc/hosts\f1 file.
.bp
