iraf.noao.edu, in the subdirectory iraf/vnnn/PCIX,
where "vnnn" is the IRAF version number, e.g., subdirectory
iraf/v211/PCIX for all versions of V2.11 PC-IRAF.
If IRAF is being installed from a network distribution all the architecture
independent IRAF files for both the core IRAF system and the NOAO packages
will be in the distribution file as.pcix.gen. This "file" is stored
in the network archive as a directory wherein the large distribution file
has been split into a number of smaller pieces, e.g.,
% ls as.pcix.gen CHECKSUMS as.pcix.gen.gz.06 as.pcix.gen.gz.14 as.pcix.gen.gz.22 FILES.Z as.pcix.gen.gz.07 as.pcix.gen.gz.15 as.pcix.gen.gz.23 as.pcix.gen.gz.00 as.pcix.gen.gz.08 as.pcix.gen.gz.16 as.pcix.gen.gz.24 as.pcix.gen.gz.01 as.pcix.gen.gz.09 as.pcix.gen.gz.17 as.pcix.gen.gz.25 as.pcix.gen.gz.02 as.pcix.gen.gz.10 as.pcix.gen.gz.18 as.pcix.gen.gz.26 as.pcix.gen.gz.03 as.pcix.gen.gz.11 as.pcix.gen.gz.19 as.pcix.gen.gz.04 as.pcix.gen.gz.12 as.pcix.gen.gz.20 as.pcix.gen.gz.05 as.pcix.gen.gz.13 as.pcix.gen.gz.21
as.pcix.gen as shown above has been
recreated somewhere on the machine on which IRAF is to be installed.
We can restore the main IRAF source tree as follows.
% whoami iraf % cd $iraf % cat /path/as.pcix.gen/as.* | zcat | tar -xpf -After the above finishes the root IRAF directory should appears as follows (this is for V2.11).
HS.PCIX.GEN bin.generic bin.redhat lib mkpkg sys bin bin.linux dev local noao unix bin.freebsd bin.linuz doc math pkgThe files
bin.linux, bin.freebsd, and bin.redhat
are links to the actual BIN directories (for binary executables), which
may not exist yet. Configuring the BIN directories is discussed in section
§2.2.3.
IRAF distribution tapes consist of multiple files separated by tape marks, with a TOC (table of contents) file as the first file on the tape. To find out what is on the tape, rewind it and read out the TOC file as follows (the actual device name may be different than that shown in the examples - on Linux systems /dev/tape is an optional link pointing to the actual tape device, e.g. /dev/nst0).
% mt -f /dev/tape rewind; cat /dev/tapeThis should cause a TOC file to be listed similar to the following, except for the file names which will vary depending upon what type of distribution you have. The example below is for a distribution of PC-IRAF.
0 Table of Contents 1 AS.PCIX.GEN 76.3Mb IRAF, NOAO packages and sources 2 IB.FBSD.X86 37.1Mb FreeBSD binaries for IRAF core system 3 NB.FBSD.X86 42.6Mb FreeBSD binaries for NOAO packages 4 IB.LNUX.X86 34.4Mb Linux binaries for IRAF core system 5 NB.LNUX.X86 37.1Mb Linux binaries for NOAO packages 6 IB.RHLX.X86 37.6Mb Red Hat Linux binaries for IRAF core system 7 NB.RHLX.X86 35.4Mb Red Hat Linux binaries for NOAO packagesHere, the first column is the file number on the tape, the TOC file being file zero (the first distribution file is number one), the second column is the name of the tape file, the third column is the installed (uncompressed) disk usage for the package in megabytes, and the last column is a description of the file contents.
There are three types of tape files in the example shown: the AS
file, which is all the IRAF sources (the core IRAF system, NOAO packages,
and the host system interface), the IB files, or IRAF core system
binaries, and the NB files, or NOAO package binaries, for each
architecture. The NOAO package sources are included in the AS
file since most people requesting IRAF are expected to want the astronomical
reduction software, although IRAF can be configured without the NOAO
packages if desired. For PC-IRAF a fourth type of distribution file
exists, the DB file, which contains debugging version of the IRAF
core system libraries; this is optional and is not required to run IRAF.
All of the file objects are UNIX tar format files, with the exception
of the TOC file which is a simple text file. The distribution files may
be compressed if this was necessary to fit all the files on a tape.
The following commands would suffice to restore the main IRAF system to disk, given the distribution tape described by the TOC file in our example above. Once again, the tape device file and block size shown in the example will very likely have to be changed to whatever is needed for the tape device being used.
% whoami iraf % cd $iraf % mt -f /dev/tape rewind; mt -f /dev/tape fsf 1 % tar -xpf /dev/tapeAfter the above tar file read operation, the tape is left positioned to just before the EOF of the file just read, since tar stops reading the file data before reading the physical EOF. Hence, an mt fsf will be required to position to the next file on the tape. Any combination of fsf (forward skip file) or bsf (backward skip file) operations may be used to position to a file on a 9 track tape, DAT, or Exabyte. On a cartridge tape, it is best to plan things so that only forward file skips are used, using a rewind and forward skip if it is necessary to position to an earlier file on the tape.
Once the main system, containing only sources, is installed it is possible to create one or more empty BIN directories for the executables, then compile and link the full system. More commonly one will merely read the precompiled executables off the distribution tape, as we discuss in the next section.
AS (all-sources) directory tree, but
the BIN directory for each architecture. The IRAF core system and the
NOAO packages have separate BIN directories.The BIN directories for the IRAF core system or a layered package (such as NOAO) are located, logically or physically, in the root directory of the IRAF core system or layered package. Every layered package has its own set of BIN directories. In the distributed V2.11 system you will find the following BIN files (directories or symbolic links) at the IRAF root.
link bin -> bin.generic directory bin.generic link bin.freebsd -> ../irafbin/bin.freebsd link bin.linux -> ../irafbin/bin.linux link bin.redhat -> ../irafbin/bin.redhatIf the IRAF directory structure is set up as described in §2.1.2, with $iraf located at iraf/iraf and the BIN directories stored in iraf/irafbin, then these links will not have to be modified. If a different directory structure is used you will have to modify the links accordingly.
The bin link and the bin.generic directory are required for the correct operation of IRAF and are maintained automatically by the IRAF software management utilities. Under no circumstances should "bin" or "bin.generic" be modified or deleted! It is a common error to manually delete the bin link and manually set it to bin.linux or some other architecture, e.g. to link external programs (people get confused by the library links in lib which point to ../bin). The bin.<arch> link can be modified as desired but bin and bin.generic should be left alone. The proper way to change the IRAF architecture (i.e., set bin to a particular architecture) is to run "mkpkg arch" at the IRAF root. See the Site Manager's Guide for a complete discussion of package architecture support.
In the following example we will demonstrate the installation of the
Slackware Linux binaries, the process is the same for the other architectures
as well. Assume that the bin.linux directory has been created somewhere,
e.g. in the iraf/irafbin directory, and that the ib.lnux.x86
distribution files for the core IRAF system linux binaries have been
downloaded from the network archive. We can restore the linux binaries
with the following commands.
% cd $iraf/bin.linux % cat /path/ib.lnux.x86/ib.* | zcat | tar -xpf -Similarly, to restore the NOAO package linux binaries:
% cd $iraf/noao/bin.linux % cat /path/nb.lnux.x86/nb.* | zcat | tar -xpf -The procedure for restoring a BIN directory from a tape distribution is similar to that described in §2.2.2 for the core system. For example,
% cd $iraf/bin.linux % mt -f /dev/tape rewind; mt -f /dev/tape fsf 2 % tar -xpf /dev/tapewould restore the core system bin.linux directory from a tape containing an uncompressed
ib.lnux.x86 as file 2 on the tape.