README.KSKIT-2102 -- Instructions for installing an IRAF v2.10.2 or later
"Kernel Server Kit".

Although there are separate kits for SunOS and other platforms, the install-
ation instructions are the same (see "limitations" below).  This kit installs 
a skeleton IRAF system which can support tape and disk access.  The fully 
unpacked archive requires ~1.2 Mb on disk; some of this space can be recovered
in step [6].  Refer to the IRAF Installation Guide (IG) and IRAF Site Manager's
Guide (SMG) for additional information.

LIMITATIONS:  This kit does not cover all possible combinations of operating
	system version and hardware architecture.  If you need something other
	than what is listed below, contact the IRAF HOTLINE (602-323-4160)
	or send a request to iraf@noao.edu  (5355::iraf).

File:		      OS Type:	      Description:
-----                 --------        ------------
KS.sun-2102.tar.Z     SunOS v4.1:     Kernel Server for sparc, f68881, and ffpa



INSTALLATION INSTRUCTIONS:
On the server node:

[1] Establish an IRAF account.  Make the login directory for this account be
    subdirectory "local" of the iraf root [we refer to the iraf root directory
    as $iraf, a csh setenv environment variable; the account login directory
    is then $iraf/local].  On a Sun-3 or Sun-4, a typical value of $iraf
    would be /iraf/iraf/ or /usr/iraf/ but it can be anything reasonable.

[2] Read the tar file, uncompressing if necessary.  Be logged on as iraf
    when unpacking the files; execute the tar command from the $iraf root,
    rather than the iraf account login directory, which is $iraf/local.
    Substitute the file name of the tarfile for "tarfile" in the commands
    below, e.g. "OS4kskit2102.tar".  [Execute either the uncompress or tar
    command below, not both.]
   
	(login as iraf)
	% setenv iraf /local/iraf/		# or whatever, see above.
	% cd $iraf
either	% uncompress < tarfile.Z | tar -xptvf - # for compressed tarfile
or	% tar -xptvf tarfile	    		# if not compresssed

    Be sure to include the trailing slash in the "iraf" environment variable
    definition.  The value of $iraf must be valid for the rest of this
    installation to proceed.

[3] Now run the ksinstall script.  You must be logged on as root to run the
    script; the "-n" flag is a dry run just to see what would happen.  The
    Sun/IRAF IG describes the normal (full system) install script, which is 
    similar to this one except that no task links are installed in UNIX, 
    and fewer installation files are edited.
	
	% cd $iraf/unix/hlib
	% source irafuser.csh			# pick up host, hlib def's.
	% su					# become superuser
	% ./ksinstall -n			# dry installation run
	% ./ksinstall				# actual run if satisfied
	% ^Z		# or ^D, whatever, to return to iraf from superuser

[4] Edit the $iraf/dev/tapecap file to identify the available tape devices,
    i.e. those tape drives on the kernel server Sun node that you expect
    to access from other machines running IRAF.  The 1992 Sun/IRAF SMG
    describes this file in sec. 2.2.3.

[5] On the (client) machine currently running the full IRAF system, edit the
    file $iraf/dev/hosts.  Each node (the kernel server and full IRAF node)
    must appear on a separate line; enter the pathname to the kernel server
    following the examples already in the file.

[6] We have included executables for sparc and the two mc68020 architectures 
    (f68881 and ffpa).  You can delete the ones you won't be using.  Binaries 
    appear in two locations: $iraf/bin.* (the kernel server) and 
    $iraf/unix/bin.* (the tape allocation  executables).

As always, if you encounter difficulties, send email to iraf (iraf@noao.edu,
5355::iraf) or contact the IRAF HOTLINE (602-323-4160).

Mike Fitzpatrick 
July 5, 1994