[Next] [Previous] [Up] [Top] [Contents] [Index]
Chapter 10: Accessing Software Products
UPS products are also available via anonymous ftp from the host FTP.FNAL.GOV. We recommend that after copying over the product tar file using ftp you use UPD to install the product.
If you have a local UPS database, we recommend distributing via UPD because it provides a better interface for declaring products once the tar file is copied. You can always invoke UPD to do this after downloading via ftp, of course.
To access anonymous ftp, enter the command:
% ftp ftp.fnal.gov
You will get a response similar to the following, to which you enter anonymous at the Name prompt:
|
Once that is accepted, you will be prompted to enter your email address as a password (e.g., qjones@fnal.gov), which is not echoed to the screen:
|
The screen will then display the following information[50]:
|
In the top level directory a readme file is provided that discusses some of the available tools and features.
[Missing image]If you are on an off-site node, it must be registered with Fermilab in order to use anonymous ftp to obtain tar files[51] from the KITS area. If you need to register, use the UNIX Product Distribution Registration Form in the top level directory under the filename registration. All machines in the fnal.gov domain are automatically registered.
Here is a top-level directory listing for reference:
|
Most UPS products can be found under the KITS directory. Access to this directory is restricted to registered users. Directly under KITS is a directory for each supported OS type, under which the product instance tar files appropriate to each one are maintained. The declared directory containing the product declaration files is also available under KITS. The public ftp area KITS/pub, available to all (registered and nonregistered) users, includes the Fermilab Software Tools (FermiTools). This collection of software is intended to provide the internet community with many of the Fermilab-developed software packages that we believe have general value to other application domains.
To see the contents of KITS, run the following (the output has been abbreviated for this manual):
|
From the root directory (/), cd to the appropriate OS type subdirectory under KITS (SunOS is used as an example here). You'll need to "get" the index file since you can't list a remote file from ftp. Since index is an ASCII file, make sure you set the mode to ASCII first, as shown below:
|
Now you have a local (renamed) copy. Use the ftp command ! to run less as a shell command to list the file contents:
ftp> !less index_SunOS
You'll find that the file lists everything under KITS; all directories, subdirectories and tar files.
Any file that is not a straight text file must be transferred in binary mode. Set the mode to binary (bin) and then use the standard ftp get function to copy the tar file. Refer to section 13.1.1 for information on standard ftp commands.
After the tar file is downloaded, use UPD to unwind it into the appropriate location on your system and declare it, as described in section 10.3.1.