THE ALLIANT/IRAF NETWORK DISTRIBUTION This directory and its subdirectories contain the Alliant/IRAF distribution. The V2.9.1 binary distribution was compiled under Concentrix 5.6.0 on a VFX/80 at the Naval Research Labs in collaboration with NOAO. README This file. as.alnt.gen All sources. ib.alnt.fx8 Core system binaries. nb.alnt.fx8 NOAO packages binaries. alntiraf.ms.Z BSD/IRAF Installation Guide source alntiraf.ps.Z BSD/IRAF Installation Guide, Postscript unixsmg.ms.Z Generic UNIX/IRAF Site Manager's Guide unixsmg.ps.Z Generic UNIX/IRAF Site Manager's Guide To install Alliant/IRAF you will need to transfer the AS.ALNT.GEN file and the two sets of binaries, IB.ALNT.FX8 and NB.ALNT.FX8. 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 Sun 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.alnt.gen o Set the current directory on both the local and remote systems. ftp> cd as.alnt.gen ftp> lcd as.alnt.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 UNIX command "sum" will compute the checksum of a file. ALLIANT CHECKSUMS NOTE: The "sum" command in Concentrix gives block counts in the second field that are not kbytes or half kbytes. Ignore these; it is the checksum itself that counts. 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 Alliant/IRAF Complete instructions for installing and configuring Alliant/IRAF are given in the Alliant/IRAF Installation Guide and UNIX/IRAF Site Manager's Guide, compressed Postscript versions of which are given in the files alntiraf.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 alntiraf.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.ALNT.GEN to the remote directory $iraf, while logged in as user "iraf": % whoami iraf % cd ALNT/as.alnt.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/ALNT and you want to install iraf in the root directory /usr/iraf on the remote system "fred": % cd /tmp2/ALNT/as.alnt.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/ALNT/as.alnt.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.fx; mkdir bin.fx % cd bin.fx % (cd /tmp2/ALNT/ib.alnt.fx8; cat ib.*) | uncompress | tar -xpf - % cd /usr/iraf/noao % rm bin.fx; mkdir bin.fx % cd bin.fx % (cd /tmp2/ALNT/nb.alnt.fx8; 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 Alliant/IRAF, but it might be used to experiment with different compilers for example; see the file $iraf/local/notes.v29.fx after you get the system unpacked for a discussion of compilers and switches). 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 XTERM, available in most X Window implementations, can be used as the terminal emulator within which to run the IRAF CL. Just tell iraf what size window you are using interactively or edited into your login.cl, e.g. "stty xterm nl=54" for a 54-line xterm window. An alternative is "xtermjh" for a different type of graphics/text interaction in the Tek graphics subwindow. The image display server for IRAF in the X Window environment is currently SAOIMAGE. SAOIMAGE is not distributed automatically with Alliant/IRAF, as it had to be modified slightly to work on the Alliant, and there wasn't time to check it out thoroughly at distribution time. Contact iraf@noao.edu to find out how to get a copy, or call the IRAF Hotline.