iraf/vnnn/HPUX,
where "vnnn" is the IRAF version number, e.g., subdirectory
iraf/v211/HPUX for V2.11 HPUX/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.hpux.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.hpux.gen
CHECKSUMS as.hpux.gen.Z.12 as.hpux.gen.Z.26
FILES.Z as.hpux.gen.Z.13 as.hpux.gen.Z.27
as.hpux.gen.Z.00 as.hpux.gen.Z.14 as.hpux.gen.Z.28
as.hpux.gen.Z.01 as.hpux.gen.Z.15 as.hpux.gen.Z.29
as.hpux.gen.Z.02 as.hpux.gen.Z.16 as.hpux.gen.Z.30
as.hpux.gen.Z.03 as.hpux.gen.Z.17 as.hpux.gen.Z.31
(etc.)
as.hpux.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.hpux.gen/as.* | uncompress | tar -xpf -After the above finishes the root IRAF directory should appear as follows (this is for V2.11).
HS.HPUX.GEN bin.generic dev local noao tags IS.PORT.GEN bin.hp300 doc math pkg unix bin bin.hp700 lib mkpkg sysThe file
bin.hp700 is a link to the IRAF BIN
directory for the "hp700" architecture (for binary executables), which
probably does not contain anything 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 will likely be different than that shown in the examples).
% mt -t /dev/rmt/0mn rew; cat /dev/rmt/0mnThis 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 actual file sizes may differ from what is shown). The example below is for a distribution of HPUX/IRAF including all available binaries. The file sizes are only examples in this case.
0 Table of Contents 1 AS.HPUX.GEN 47.2 Mb IRAF, NOAO packages and HPUX/OS sources 2 IB.HPUX.HP7 27.5 Mb HPUX binaries for IRAF system 3 NB.HPUX.HP7 25.6 Mb HPUX 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 file size in megabytes (this tells you how much space will be needed to unpack the file on disk), 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 HPUX host system interface), the IB files, or IRAF core
system binaries, one for each architecture, and the NB files, or
NOAO package binaries. 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
this if desired. 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.
In the above example, the HPUX in the file names indicates that
these files are for HP HPUX. A SunOS version 4 distribution is
indicated by a SOS4 in the file names, and a DECstation Ultrix
distribution is indicated by a DSUX, and so on. In principle a
given distribution tape may contain any combination of these files.
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 actual tape device used.
% whoami iraf % cd $iraf % mt -t /dev/rmt/0mn rew; mt -t /dev/rmt/0mn fsf 1 % tar -o -xpbf 126 /dev/rmt/0mnAfter 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 directories (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.hp700 -> ../irafbin/bin.hp700 link noao/bin.hp700 -> ../../irafbin/noao.bin.hp700If 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 the IRAF system software (mkpkg) 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 very common error to manually delete the bin link and manually set it to bin.hp700 or some other architecture. The bin.hp700 can be modified as desired but bin and bin.generic should be left alone.
Assume that the bin.hp700 directory has been created somewhere (e.g. in the
iraf/irafbin directory) and that the ib.hpux.hp7 distribution files
for the core IRAF system HPUX binaries have been downloaded from the
network archive. We can restore the HPUX binaries with the following
commands.
% cd $iraf/bin.hp700 % cat /path/ib.hpux.hp7/ib.* | uncompress | tar -xpf -Similarly, to restore the NOAO package HPUX binaries:
% cd $iraf/noao/bin.hp700 % cat /path/nb.hpux.hp7/nb.* | uncompress | tar -xpf -If you get an error message in the cd above probably the BIN directory pointed to by the symbolic link has not been created yet, and you should do so.
Note that when restoring the NOAO package binaries the BIN is yet
another link to the irafbin directory, and specifically to a
noao.bin.hp700 directory the installer has created within
irafbin.
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.hp700 % mt -t /dev/rmt/0mn rew; mt -t /dev/rmt/0mn fsf 2 % tar -o -xpbf 126 /dev/rmt/0mnwould restore the core system bin.hp700 directory from a cartridge tape containing an uncompressed
ib.hpux.hp7 as file 2 on the tape.