README FOR DECSTATION-ULTRIX IRAF VERSION 2.10 Current patch level V2.10.1 Updated 14 Sep 1992 Updated 23 Jul 1993 - Patch-ks THE DECSTATION-ULTRIX/IRAF NETWORK DISTRIBUTION This directory and its subdirectories contains the Ultrix/IRAF distribution for the Decstation. This distribution is ONLY for the Decstation (MIPS cpu). The distribution for the VAXstation running Ultrix (VAX cpu) will be found in iraf/v210/VXUX. The distribution for the VAXstation running VMS will be found in iraf/v210/VMS5. At this time there is no IRAF release for the new Alpha machines from DEC, which we have not seen yet. README This file. as.dsux.gen AS.DSUX.GEN (all sources) ib.dsux.dec IB.DSUX.DEC (ddec binaries for core system) nb.dsux.dec NB.DSUX.DEC (ddec binaries for NOAO packages) ib.dsux.mip IB.DSUX.MIP (dmip binaries for core system) nb.dsux.mip NB.DSUX.MIP (dmip binaries for NOAO packages) patch-ks.tar.Z Upgrades IRAF networking to V2.10.3 level dsuxiraf.ms.Z Ultrix/IRAF installation guide source dsuxiraf.ps.Z Ultrix/IRAF installation guide Postscript unixsmg.ms.Z UNIX/IRAF Site Manager's Guide source unixsmg.ps.Z UNIX/IRAF Site Manager's Guide Postscript Additional release related documentation of interest. iraf/v210/v210revs.ms.Z V2.10 revisions summary source iraf/v210/v210revs.ps.Z V2.10 revisions summary in postscript iraf/v210/pkgnotes.v210.Z V2.10 package revisions notes iraf/v210/sysnotes.v210.Z V2.10 system revisions notes See also iraf/docs for general documentation. To install Ultrix/IRAF on a Decstation you need AS.DSUX.GEN, and either or both of the ddec (DEC Fortran) and dmip (MIPS Fortran) binaries, plus all the release documentation. See the note at the end of this file for additional information on the supported architectures (ddec and dmip). REGISTERING YOUR SITE Please register with us if you use IRAF, so that we can track use of IRAF by the community. This also gets you on the IRAF mailing list so that you will receive the IRAF newsletters and other IRAF relating mailings. To register, fill out the form in the v210/REGISTER file and email it to iraf-requests@noao.edu. 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 SunOS 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 and SYS5 checksums are given. The Ultrix command "sum" will compute the BSD 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 ULTRIX/IRAF Complete instructions for installing and configuring Ultrix/IRAF are given in the Decstation Ultrix/IRAF Installation Guide and in the UNIX/IRAF Site Manager's Guide, compressed Postscript versions of which are given in the files dsuxiraf.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 dsuxiraf.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 or for those who want to read the manuals online with nroff. The IRAF sources and binaries, and the IRAF layered packages are distributed as separate modules that can be installed anywhere. However, the following directory structure is recommended to help organize all IRAF related files. Adhering to this directory structure will simplify the installation as well as future upgrades. iraf/iraf core iraf system iraf/iraf/local iraf system manager login dir iraf/irafbin binaries for main iraf release iraf/irafbin/bin. core iraf bin directory iraf/irafbin/noao.bin. noao package bin directory (other binaries) iraf/stsdas layered package iraf/xray layered package iraf/grasp layered package iraf/ice layered package (other layered packages) The location of the root directory "iraf" above is arbitrary, although to avoid possible filename truncation problems it is recommended that the path be kept reasonably short. A good practice is to set up a symbolic link such as /iraf or /usr/iraf pointing to the actual root directory, and use this in all external references to the iraf files, to allow the root directory to be relocated without affecting software that knows the path to the iraf root. This is especially important when iraf is installed in a central location and NFS mounted on a number of client machines. Any of the directories above can be symbolic links pointing to the actual location of the directory, if disk space becomes tight and it is necessary to move something. Please read the installation guide for detailed instructions regarding the installation. ARCHITECTURE NOTES The V2.10 Ultrix/IRAF release for the Decstation supports two software architectures, ddec and dmip. These are the IRAF binaries, built using either the DEC Fortran compiler (ddec) or the MIPS Fortran compiler (dmip). Either set of binaries can be used to run IRAF on the Decstation. If both sets of binaries installed the user can specify the architecture to be used by setting IRAFARCH in their unix environment. For example, % setenv IRAFARCH dmip will cause the MIPS Fortran binaries to be used. If no architecture is specified the ddec binaries will be used by default, if they are installed. The choice of which set of binaries are used to run IRAF does not depend upon whether the DEC or MIPS Fortran compiler is installed. However, if any IRAF programs such as layered packages or IMFORT programs are to be compiled and linked, it is necessary to have the correct set of IRAF binaries installed. The "correct set" is whatever corresponds to the compiler to be used. If the MIPS compiler is used, the dmip binaries should be installed. If the DEC compiler is used, the ddec binaries should be installed. If either compiler may be used, both sets of binaries should be installed, and IRAF will automatically link against the correct set of binaries. It is the XC command in IRAF (known as FC when building IMFORT programs) which determines whether the ddec or dmip binaries are linked against. This is done by examination of the "f77" command in the user's search path. For this feature to work correctly, "f77" MUST BE A SYMBOLIC LINK. This is the default on DEC Ultrix systems if the manufacturer's instructions are followed to install the compiler. For example, if the DEC Fortran compiler is installed, a link /usr/bin/f77 is created as follows: /usr/bin/f77 -> ../lib/cmplrs/fort/fort (/usr/lib/cmplrs/fort/fort) If the MIPS Fortran compiler is installed, the f77 link will have a value such as the following (the version number may vary but that does not matter): f77 -> /usr/lib/cmplrs/cc2.1/driver (MIPS Fortran compiler) Regardless of which compiler is the default, if both compilers are installed on a particular system the user or IRAF system manager can determine the compiler to be used by creating a private f77 link somewhere in their personal search path. IRAF will use this personal link for all compilations. IRAF will automatically set IRAFARCH when a user uses the FC command to link a host IMFORT program. The architecture used for linking is determined solely by which f77 compiler is used, regardless of which architecture IRAF is executing at the time. When building layered packages however, it is a good idea to ensure that IRAFARCH is defined beforehand and that it matches the f77 to be used, to ensure that the correct default mkpkg compiler switches are used. In summary, to use the DEC Fortran compiler, [1] The ddec binaries must be installed in iraf. [2] Create the following link in your command search path (assuming it does not exist already): ln -s /usr/lib/cmplrs/fort/fort f77 [3] If doing IRAF software development (e.g. building layered packages) setenv IRAFARCH ddec To use the MIPS Fortran compiler, [1] The dmip binaries must be installed in iraf. [2] Create the following link in your command search path (assuming it does not exist already): ln -s /usr/lib/cmplrs/cc/driver f77 [3] If doing IRAF software development (e.g. building layered packages) setenv IRAFARCH dmip In simple cases, e.g., a user doing IMFORT development using the system default version of f77, which matches the installed IRAF binaries, it is not necessary for the user to do anything or be aware of architecture issues. ---------------------------------------------------------------------------- PATCH-KS - Updates IRAF networking to V2.10.3 level, adds support for networking to V2.10 VMS/IRAF. 23 July 1993. Download the following file from the DSUX directory in the network archive: 3442833 Jul 23 15:26 patch-ks.tar.Z First backup the affected files: % whoami iraf % cd $iraf % zcat patch-ks.tar.Z | tar -tf - | grep -v '/$' > _f % tar -cf ks-backup.tar `cat _f` % rm _f Then install the patch: % cd $iraf % zcat patch-ks.tar.Z | tar -xpvf - IRAF must be installed before the patch can be installed. The patch contains both DDEC and DMIP binaries. If you only use one set of binaries errors may be seen when tar tries to unpack files to nonexistent directories. If you only use one set of binaries you may with to delete the binaries for the unused architecture. The patch replaces the file dev$hosts. If you have a local version of this you may wish to save it before unpacking the patch. Note that the hosts file syntax has changed, so do not blindly replace the old version. Refer to the V2.10 IRAF Sysems Revisions Summary and the VMS/IRAF Installation and Site Manger's Guide for detailed information on the changes to the hosts file syntax. This is a PARTIAL binary-only patch. Source files are not included. Only the cl.e, x_system.e, x_dataio.e, and irafks.e executables are updated. This patch has undergone limited testing and is probably only worth installing at sites that need to do networking between Ultrix and VAX/VMS systems.