THE DECSTATION/IRAF NETWORK DISTRIBUTION This directory and its subdirectories contains the DECstation/IRAF distribution. The V2.9 binary distribution was compiled under Ultrix 3.2. README This file. as.dsux.gen All sources. ib.dsux.mip Core system binaries. nb.dsux.mip NOAO packages binaries. dsux.patch1.Z May 5 patch to DSUX. Install this only if you got DSUX from the archive before May 5. Installation instructions are given below. dsux.patch2.Z July 10 IMFORT patch. dsux.patch3.Z V2.9.1 BUG FIX UPGRADE PATCH (supercedes all earlier patches). dsiraf.ms.Z DECstation/IRAF Installation Guide source dsiraf.ps.Z DECstation/IRAF Installation Guide, Postscript unixsmg.ms.Z Generic UNIX/IRAF Site Manager's Guide unixsmg.ps.Z Generic UNIX/IRAF Site Manager's Guide zzmake Build utility (not part of distribution) To install DECstation/IRAF you will need to transfer the AS.DSUX.GEN file and the two sets of binaries, IB.DSUX.MIP and NB.DSUX.MIP. REGISTERING YOUR SITE While the network archive makes it easier to get IRAF, it also makes it harder for us to track IRAF usage by the community. We need this information, e.g., to help obtain funding to continue to develop and support IRAF for the community. PLEASE REGISTER YOUR SITE IF YOU USE IRAF! This takes only a moment; all you need do is fill out the form in the v29/REGISTER file and mail it to iraf-requests@noao.edu. As an added benefit you will get on the IRAF mailing list, and will receive the IRAF Newsletter and other IRAF mail. TRANSFERRING THE FILES Each distribution file is stored in a subdirectory containing the compressed and split distribution file, a CHECKSUMS file, and a FILES.Z file. The distribution file is a UNIX TAR file containing one or more directory trees from the IRAF system. To facilitate transfers over unreliable network connections, the distribution file is split into a number of smaller (512 Kb) files. The files can be transferred as follows. These examples are for the DECstation version of FTP. o If you did not start up FTP as "ftp -i", exit and restart it with the "-i" switch. This is necessary to be able to do bulk transfers without having to answer annoying and unnecessary yes or no queries for each individual file. o On the local system, create a subdirectory for each distribution file you want to transfer, e.g., ftp> !mkdir as.dsux.gen o Set the current directory on both the local and remote systems. ftp> cd as.dsux.gen ftp> lcd as.dsux.gen o Transfer all the files in the distribution file directory. A binary transfer is required for the compressed tar files, and will work for the text files as well since both systems are UNIX. ftp> binary ftp> mget * If problems are encountered, use the CHECKSUMS file to verify that any subfiles already transferred are correct. Delete any partially transferred subfiles and restart the transfer (by subfile we mean the 512 Kb files with extensions .00, .01, .02 etc. files making up the distribution file). Both BSD (Ultrix) and SYS5 checksums are given. The Ultrix command "sum" will compute the checksum of a file. Once all the files have been transferred the subfiles can be concatenated and uncompressed to reconstruct the original distribution TAR file, e.g.: % cat as.* | uncompress | tar -tvf - would list the contents of the distribution file. Such a listing is provided in the file FILES.Z in each distribution file directory. An easy way to look at a compressed text file such as FILES.Z is with "zcat": % zcat FILES.Z | page INSTALLING DECstation/IRAF Complete instructions for installing and configuring DECstation/IRAF are given in the DECstation/IRAF Installation Guide and UNIX/IRAF Site Manager's Guide, compressed Postscript versions of which are given in the files dsiraf.ps.Z and unixsmg.ps.Z. On most BSD networks containing a Postscript printer, a hardcopy version of the manual can be obtained with a command such as % zcat dsiraf.ps.Z | lpr [-P] where is the name of the local printer device you want the manual to be printed on. Troff source for the manuals is also provided for sites that do not have ready access to a Postscript printer. Installation is as described in the manuals except that, since you will be installing a network distribution, you install from the compressed and split disk version of the distribution file instead of from tape. For example, to restore AS.DSUX.GEN to the remote directory $iraf, while logged in as user "iraf": % whoami iraf % cd DSUX/as.dsux.gen % cat as.* | uncompress | (cd $iraf; tar -xpf -) This example assumes that "iraf" is defined in your unix environment (if not, just type in the pathname of the iraf root directory instead). As a variation, suppose the distribution files are stored on the local system "alex" in directory /tmp2/DSUX and you want to install iraf in the root directory /usr/iraf on the remote system "fred": % cd /tmp2/DSUX/as.dsux.gen % cat as.* | uncompress | rsh fred "cd /usr/iraf; tar -xpf -" Or, if you are logged in on fred instead: % cd /usr/iraf % rsh -n alex "cat /tmp2/DSUX/as.dsux.gen/as.*" |\ uncompress | tar -xpf - (The -n argument allows you to suspend the rsh without having the job stop waiting for terminal input). Note that, even if the two systems are connected by NFS, it is always safer, faster, and more efficient to use rsh instead of NFS for file transfers such as these. The BIN directories are restored in much the same fashion, e.g., % cd /usr/iraf % rm bin.mips; mkdir bin.mips % cd bin.mips % (cd /tmp2/DSUX/ib.dsux.mip; cat ib.*) | uncompress | tar -xpf - % cd /usr/iraf/noao % rm bin.mips; mkdir bin.mips % cd bin.mips % (cd /tmp2/DSUX/nb.dsux.mip; cat nb.*) | uncompress | tar -xpf - If multiple architecture support is desired you need only create additional sets of BIN directories (multiple architecture support is not currently common practice with DECstation/IRAF). The system as shipped will contain existing symbolic links with these names which should be deleted (you can use a symbolic link to store the BIN directory on another disk if space is tight). DO NOT delete the "bin.generic" directory, or modify the symbolic links "iraf$bin" and "iraf$noao/bin" to point to anything other than bin.generic. Please read the installation guide for more complete instructions regarding the installation. There is more to installing and configuring IRAF than just restoring the files to disk as discussed in these examples. X WINDOW SYSTEM SUPPORT At the time of the V2.9 release we are just beginning to convert to X (e.g., DECwindows) at NOAO and IRAF graphics and image display under X is not as nice as one would like. Nonetheless, basic facilties are available. The V2.9 DECstation release contains two executables which may be installed to provide graphics and image display facilities. The most important of these is SAOIMAGE, an image display server for X11 which can be used with IRAF like IMTOOL on the Suns. An installable SAOIMAGE installation kit is available from the ftp archive on tucana, and this may be obtained and installed if you want the latest version. Otherwise, a version of SAOIMAGE comes prebuilt and installed in IRAF, in the following directories: iraf/unix/x11/saoimage source directory iraf/unix/bin.mips/saoimage.e executable To install saoimage at the host level, you can do the following (this example assumes that $iraf, the iraf root directory, is defined in the environment; if not, just type in the full pathname instead): % su # ln -s $iraf/unix/bin.mips/saoimage.e /usr/local/bin/saoimage # cp $iraf/unix/x11/saoimage/imtoolrc /usr/local/lib # # cd /dev # /etc/mknod imt1i p # chmod 777 imt1i # /etc/mknod imt1o p # chmod 777 imt1o The manual page is in the source directory. The distribution also includes a DECstation executable for the new, improved version of XTERM from the X11R4 distribution. This can also be installed in /usr/local/bin (or anywhere); it wants to be installed suid root. The executable is hidden in iraf/local/bin. To install: % su # cd /usr/local/bin # cp $iraf/local/bin/r4xterm xterm # chmod 4755 xterm # chown 0 xterm More thorough support for X will be available later this year. PATCH 1 (May 5) STSDAS support If you got the DSUX distribution from the archive after May 5 you can ignore this patch. If you got DSUX before May 5, you need to install the patch to: o Compile STSDAS. The patch contains a bug fix which is needed to compile and install STSDAS. To install the patch, retrieve the file dsux.patch1.Z from the archive, then when logged in as "iraf": % cd $iraf % zcat dsux.patch1.Z | tar -xpvf - It is harmless to install the patch when it has already been installed. PATCH 2 (July 10) IMFORT patch This patch fixes a bug in imfort which would prevent it from being able to access images not in the current directory. The patch replaces only the compiled imfort library (libimfort.a). The patch is applied as for patch1 above (i.e., unpack with tar at the iraf root). PATCH 3 (Sept. 6) V2.9.1 UPGRADE patch This patch supercedes all earlier V2.9 patches; sites installing the patch do not need to have installed the earlier patches, although it is harmless if one has done so. Sites doing a complete installation of IRAF V2.9 from the archive after September 6 do NOT need to install this patch, as the version of IRAF in the network archive has been replaced by V2.9.1 with the patches already installed. The V2.9.1 patch includes the following bug fixes or enhancements to V2.9: o Support for the beta test release of PROS has been added. This involved minor changes to the system interfaces QPOE, MWCS, and PLIO. Any site wishing to run PROS should first upgrade to V2.9.1. o MTIO and the DATAIO package underwent some revisions, partially motivated by the addition of Exabyte support (Exabyte support is available in V2.9.1 only for Sun/OS). The maximum tape blocksize is increased to 65535 bytes and the maximum FITS blocking factor is increased to 22 (anything over 10 is not standard FITS tape, however, and may not be readable on other systems). o A bug in the IMDKERN graphics kernel (graphics overlays on image displays) which could cause the kernel to crash on a segmentation violation has been fixed. (Bug #137) o A bug in IMFORT which could prevent access to images not in the current directory has been fixed. (Bug #128) o A bug in ONEDSPEC.CALIBRATE involving an error of one pixel in the wavelength scale for extinction correction has been fixed. (Bug #129) o The entire ARTDATA package (first introduced in V2.9) has been replaced by a newer version. o Support for output to the null image (as in imcopy image dev$null) has been added to the OIF image kernel. To install V2.9.1 for the first time one merely follows the instructions for installing V2.9 given above (V2.9.1 replaces the old V2.9 distribution files). To install the V2.9.1 patch into an existing V2.9 system: 1) Unpack the file dsux.patch3.Z at the iraf root: % login iraf % cd $iraf % zcat dsux.patch3.Z | tar -xpvf - 2) Edit the file $iraf/unix/hlib/zzsetenv.def and change the "V2.9" in "set version" to "V2.9.1". 3) Do a full update of each IRAF core system and NOAO package BIN from the distribution files in the archive, as you did in the initial installation. By "full update" we mean delete the contents of the old BIN directory and replace by the contents of the appropriate IB or NB distribution file from the archive. You must update the BINs to upgrade to V2.9.1. Since the update includes a new version of the ARTDATA package it is recommended that each user do an "unlearn artdata" after logging into the V2.9.1 CL. ------- IMPORTANT NOTE: the distribution file for the full V2.9.1 release was cut from a system that designates the Decstation/Ultrix architecture as "dsux" rather than "mips" as in V2.9 Decstation/IRAF. If you install this version, change "mips" to "dsux" wherever the architecture name is used, e.g., name the BIN directories "bin.dsux" rather than "bin.mips", if you use IRAFARCH define it as "dsux" rather than "mips", and so on. In future versions of Decstation/IRAF the architecture will be called DSUX.