THE Domain/IRAF NETWORK DISTRIBUTION This directory and its subdirectories contain the Domain/IRAF distribution, for all Apollo DN-35xx, 45xx, and DN-100x0 running Domain/OS Release SR10.2 (and possibly beyond SR10.2, though this is not known now). README This file. as.dom2.gen AS.DOM2.GEN (all sources) ib.dom2.a88 IB.DOM2.A88 (core system, prism binaries) ib.dom2.f68 IB.DOM2.F68 (core system, 68882 binaries) ib.dom2.fpa IB.DOM2.FPA (core system, fpa binaries) nb.dom2.a88 NB.DOM2.A88 (NOAO packages, prism binaries) nb.dom2.f68 NB.DOM2.F68 (NOAO packages, 68882 binaries) nb.dom2.fpa NB.DOM2.FPA (NOAO packages, fpa binaries) domainiraf.ms.Z Domain/IRAF cover letter source domainiraf.ps.Z Domain/IRAF cover letter, Postscript bsdiraf.ms.Z Berkeley UNIX/IRAF installation guide source bsdiraf.ps.Z BSD/IRAF installation guice, Postscript output unixsmg.ms.Z BSD/IRAF Site Manager's Guide source unixsmg.ps.Z BSD/IRAF Site Manager's Guide, Postscript zzmake Build utility (not part of distribution) To install Domain/IRAF you will need to transfer the AS.DOM2.GEN file plus the binaries for whatever systems you want to run IRAF on. For example, to install IRAF on a DN-10000, you will need AS.DOM2.GEN and the Prism binaries for the core system and NOAO packages, files IB.DOM2.A88 and NB.DOM2.A88. 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 SunOS version of FTP (which seems to work for Domain as well...). 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.dom2.gen o Set the current directory on both the local and remote systems. ftp> cd as.dom2.gen ftp> lcd as.dom2.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 Domain/BSD and SYS5 checksums are given. The Domain/BSD 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 Domain/IRAF Instructions for installing Domain/IRAF begin with the "Domain/IRAF" "cover letter", which is included in this directory as "domainiraf.ps.Z" or "domainiraf.ms.Z". This letter refers to the other documents bsdiraf.ps.Z and unixsmg.ps.Z, also in this directory. Detailed instructions for installing and configuring BSD UNIX/IRAF are given in the BSD/IRAF Installation Guide and UNIX/IRAF Site Manager's Guide, compressed Postscript versions of which are given in the files bsdiraf.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 bsdiraf.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.DOM2.GEN to the remote directory $iraf, while logged in as user "iraf": % whoami iraf % cd DOM2/as.dom2.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/DOM2 and you want to install iraf in the root directory /usr/iraf on the remote system "fred": % cd /tmp2/DOM2/as.dom2.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/DOM2/as.dom2.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.a88k; mkdir bin.a88k % cd bin.a88k % (cd /tmp2/DOM2/ib.dom2.a88; cat ib.*) | uncompress | tar -xpf - % cd /usr/iraf/noao % rm bin.a88k; mkdir bin.a88k % cd bin.a88k % (cd /tmp2/DOM2/nb.dom2.a88; cat nb.*) | uncompress | tar -xpf - If multiple architecture support is desired you need only create additional sets of BIN directories, e.g., bin.m68k_f68, bin.m68k_fpa, and so on. Note that 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. As you will see in the other documents, help is available through the IRAF Hotline at (602) 323-4160, which is currently answered weekday mornings, and through electronic mail at "iraf@noao.edu" throughout the week.