NAME

antelope_update - check for uninstalled patches from BRTT

SYNOPSIS

antelope_update [-dilLnQtv] [-m address] [-p proxy] [-q proxy] [-r id] [url]

DESCRIPTION

antelope_update compares the patches available from the BRTT web site -- http://www.brtt.com/patches -- to the locally installed patches (using the contents of the local directory $ANTELOPE/patched). It then copies any uninstalled patches to the local $ANTELOPE/patches directory, and unpacks/installs them with gunzip(1) and tar(1).

antelope_update also updates an html file, $ANTELOPE/html/applied_patches.html, which shows the currently installed patches.

For sites where the BRTT web site is inaccessible, you may copy the contents of the appropriate subdirectory of the BRTT web site by other means to the machine, and specify a file url for that location. For example, if your machine is a Mac and the Antelope release is 5.1-64, you might copy the contents of http://www.brtt.com/patches/5.1-64/Darwin_x86/ to a disk that you carry to the machine which needs the patches. If you install those files (including the index.html file and all the patch tar.gz files) in a local directory like /tmp/patches, you can then run antelope_update against that directory:

# antelope_update file://tmp/patches

OPTIONS

-i

ask before installing each patch

-l

just list the unapplied patches, with descriptions

-L

list all the patches at the terminal, with a preceding '*' if the patch has not been applied.

-m address

run silently, but send email to address if any patches need to be applied

-n

show what would happen, don't actually do it

-p proxy

Use proxy; eg "-p machine:port"

-q proxy

Use proxy, with password authentication; you are prompted at the command line for the name and password. Alternatively, one may be able to use a proxy form like:

-p http://username:password@proxy.host.domain

-Q

Don't ask about or run /etc/init.d/antelope to stop/start antelope. Be sure you know what you're doing if you use this option.

-r id

Specify a different antelope release, eg "4.3u"

-t

terminal mode (no gui)

-d

Additional logging

-v

Be more verbose

FILES

Antelope patches include a simple description file which is unloaded into the directory $ANTELOPE/patched. This directory patched is used by antelope_update to discover what patches have already been applied.

The compressed tar files which comprise a patch are fetched into the directory $ANTELOPE/patches. The script does not remove these files.

EXAMPLE

% antelope_update -n
Not Installed: notagain.4
   (http://www.brtt.com/patches/4.10/SunOS_sparc/notagain.4.tar.gz)
    patch description

Not Installed: example.0
   (http://www.brtt.com/patches/4.10/SunOS_sparc/example.0.tar.gz)
    This is an example to show how antelope_update should work.
Attempt to stop systems using /etc/init.d/antelope
 (copy and install notagain.4)
 (copy and install example.0)
Attempt to restart systems using /etc/init.d/antelope

% antelope_update -i
Not Installed: example.0
   (http://www.brtt.com/patches/4.10/SunOS_sparc/example.0.tar.gz)
    This is an example to show how antelope_update should work.

It's best to stop the real time systems before applying a patch.
: Run /etc/init.d/antelope stop'? n
:
Install example.0? y
Attempting to install example.0
Installing example.0
    .
    .
    .
x /opt/antelope/dev/patched/example.0, 605 bytes, 2 tape blocks
You may restart systems now
% 

SEE ALSO

brtt_installed_patches(1)

BUGS AND CAVEATS

The patches for Antelope must be applied in order, and all patches must be applied. Later patches may depend on earlier patches. No attempt is made to make all patches independent.

AUTHOR

Daniel Quinlan

Thanks to Nikolaus Horn for proxy modifications, and to Phil Cummins for password authentication of proxy modifications.