Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ update(1) — SAS/C 370 5.50.07

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

sascc370(1)

spatch(1)

tar(1)

UPDATE(1)  —  USER COMMANDS

NAME

update − SAS/C Cross-Platform update application tool

USAGE

update [ install_directory ]

DESCRIPTION

update is a utility which applies maintenance to SAS/C Cross-Platform software, using updates supplied either with a distribution or available from the SAS/C Technical Support bulletin board system, or via anonymous FTP. 

These updates are supplied as tar(1) images; and placed in the updates subdirectory of your install_directory. 

On execution update examines the updates subdirectory to locate any possible updates and applies them in order.  The user is queried for each update in turn. 

update uses the SAS/C Cross Platform binary patch application tool, spatch to actually apply the updates. 

After an update has been successfully applied, the update tar(1) image is moved into the updates.apd subdirectory. 

OPTIONS

install_directory
Although update searches the PATH environment variable for sascc_location to determine the installation directory, it is also possible to specify it as an argument to update. 

UPDATE IMAGE

Each update image  is a tar file containing, at least, two other files.  A README.??  file which is placed in the installation directory when extracted, to describe this update, and a file named DIR which is the directory describing the locations of the files to be patched, the name of the new file, the file mode of the new file and the name of the patch in the update image.  Each of these fields is separated by a single blank character. 

An example DIR file would be:

host/s4x/bin/lc1 host/s4x/bin/lc1 0755 lc1.pch
/dev/null include/newinc.h 0444 newinc.pch

This file indicates the the patch files "lc1.pch" and "newinc.pch" will be present in the update tar(1) image, and they are to be used to change host/s4x/bin/lc1 into host/s4x/bin/lc1, and to create a new file, include/newinc.h. 

The update program will then invoke the spatch program to apply the patches and create the new versions of the files. 

In this example, the commands executed would be:

spatch -otmpfile -plc1.pch host/s4x/bin/lc1
rm -f host/s4x/bin/lc1
mv tmpfile host/s4x/bin/lc1
chmod 0755 host/s4x/bin/lc1
 spatch -otmpfile -pnewinc.pch /dev/null
mv tmpfile include/newinc.h
chmod 0444 include/newinc.h

EXAMPLE

update /usr/local/sasc5.50
Assuming /usr/local/sasc5.50 is the installation directory, update will look in /usr/local/sasc5.50/updates for tar(1) images in the form updateNN.tar and ask if you would like this update applied. 

On successful application of an update, the tar(1) image will be moved to /usr/local/sasc5.50/updates.apd. 

FILES

update      Update application tool
spatch  Binary patch application tool

RELATED INFORMATION

sascc370(1), SAS/C Compiler and Library User’s Guide. 
spatch(1), SAS/C Cross Platform binary patch application tool
tar(1) Tape archiver

BUGS

Due to the nature of an installation, and the possible sharing of installation directories between many hosts, updates distributed with a tape or CD-ROM may be duplicated.  Thus, a previously applied update may be duplicated in updates subdirectory, in future releases.  The spatch program used by update will recognize redundant patches, so there is no harm. 

update is simply a bourne shell script - do not interrupt it will updates are being applied. 

5.50  —  Last change: SAS/C

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026