This document describes the procedure for installing DOME.


System Requirements
-------------------

The minimum system requirements for DOME are listed below:

	Platform	OS Version
       -------------------------------
	Linux x86	RedHat 5.1/5.2
	Sun SPARC	SunOS 5.6

ALL installations will require approximately 11MB of disk space.  If you
receive multiple releases and wish to put the files on a common, network
file server, that should be possible.  Be warned however that we may not be
able to help you if your installation is too complex or deviates much from
the distribution suggestions.

Additional requirements include the obvious monitor, keyboard and mouse.
DOME will make use of a color monitor if you have it and many mouse
functions will be simplified if you have a three-button mouse, however
neither is required.


INSTALLATION PROCEDURE
----------------------

NOTE: a % indicates the command prompt - you do not enter that literally.

 o Log into a machine with adequate resources for DOME.
   
   This may be an NFS server, but due to the stateless nature of NFS you
   should log into that server to install locally if possible.  Also, we
   recommended that you log in using a local UNIX user name so that the
   DOME files will be owned by that user.  If you copy the files as root,
   the file ownerships and permissions are maintained, which may result in
   file protection errors for users at your site.  Nothing in this
   installation requires root permissions.

 o Set up an installation directory.

   Determine where you wish to put the DOME software.  Check that
   sufficient disk space exists on the partition you wish to install DOME.
   You may use the "df" command for this.
   
   We recommend that DOME be installed in /usr/local/dome, but you can put
   it anywhere you wish.  If you put it elsewhere, you may have to complete
   "Step 5) Adjust DOME startup script for local installation."
   
   Create the directory to hold DOME.  For example
   
     % mkdir /usr/local/dome

   From now on, we'll refer to this directory as the installation
   directory, INSTALL_DIR.  When you see INSTALL_DIR in a command or path
   name, substitute the name of this directory.

 o Extracting the DOME files from an archive

   If you received an archive file via ftp, place it in the INSTALL_DIR.
   To save space and transmission time, your archive may be compressed with
   gnu-zip, a free compression program available from the Free Software
   Foundation (FSF).  The source for gnu-zip may be found at
   ftp:/prep.ai.mit.edu/pub/gnu.
   
     % cd INSTALL_DIR
     % sh DOME_VERSION.sis
       
   Replace DOME_VERSION with the appropriate string.  e.g.

     % cd INSTALL_DIR
     % sh DOME-5.0.sis

   The DOME files should now be extracted in a subdirectory named with the
   DOME_VERSION name.  In addition to extracting the DOME files an
   installation script (DOME_VERSION/bin/install-dome) is automatically
   executed

 o Customize the installation.

   In order for DOME to work for all users easily, some minor customization
   of some DOME files may be necessary.  A script is provided for this:

     % INSTALL_DIR/DOME_VERSION/bin/install-dome -i

   By default this script is run automatically during installation.  If for
   some reason the INSTALL_DIR is moved or DOME is experiencing NFS related
   problems then rerunning the script may fix the problem.

   The interactive script will ask you a question and modify the
   DOME_VERSION/bin/dome file for you.  If you make a mistake, you may
   re-execute the script; This will also work correctly if you later move
   DOME.

 o Test DOME

   To confirm that the installation is complete, simply start dome:

     % INSTALL_DIR/DOME_VERSION/bin/dome

   If you plan to run DOME often, you may choose to put the
   INSTALL_DIR/DOME_VERSION/bin directory in your PATH environment
   variable.


Multiple Version Support
------------------------

If your site has a need to support more than one version of DOME at the
same time then this section may be of interest to you.

The dome script that is normally invoked to fire up DOME supports the
notion of multiple versions of DOME on the system at the same time.  To
make use of this feature you need to copy the bin directory of one of the
versions that you have installed into a bin directory that is at the same
level as the versions on your system

So assuming that the various version of DOME are installed in the
/usr/local/dome directory then the copied bin directory should be placed
there also.  Next, the install-dome script that is in the new bin directory
should be executed so that the dome file is updated to know about its new
location.  Finally, an etc directory must be created at the same level as
the bin directory and a DOME.Versions file created and placed in it.  This
file works in conjunction with symbolic links in the bin directory to allow
end users to easily fire up other version of DOME.  Ultimately, end users
only require this single bin directory to fire up any version of DOME.
They can fire up DOME it two manners via dome or via the symbolic link
name.  For example:

     /usr/local/dome/bin/olddome  # would fire up the 4.29 version
     /usr/local/dome/bin/dome     # would fire up the DOME-5.0 version
     /usr/local/dome/bin/dome -v 4.26  # would fire up the 4.26 version

The output below shows what a properly configured multiple version site
would look like.

	% cd /usr/local/dome
	% ls
	4.26        4.29	  DOME-5.0       bin	    etc
	% ls bin
	dome	    install-dome  olddome
	% cd bin
	% ls -l olddome
	lrwxrwxrwx   1 user dome    4 Feb 11  1996 olddome -> dome
	% cd ..
	% ls etc
	DOME.Versions
	% cat etc/DOME.Versions
	# File to map symbolic dome startup name to a real version
	# See the dome script in $DOMEHOME/bin for how this is used.
	#
	# Syntax:  Each line must be of the form symbolic-name:version
	#	   symbolic-name is case-sensitive
	
	# Standard version
	dome:DOME-5.0
	
	# support for old/new versions
	olddome:4.29
	##
	%