• Antelope Release 5.10 Linux CentOS release 7.6.1810 (Core) 3.10.0 2020-05-12

 

NAME

antelope_update - check for and apply uninstalled patches from BRTT

SYNOPSIS 

antelope_update [-lLnQtv] [-m email] [url]

DESCRIPTION

antelope_update compares the patches available from the BRTT downloads web site -- http://downloads.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).

The antelope_update program 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.10, you might download the contents of http://downloads.brtt.com/patches/5.10/Linux_x86/ to another machine and then transfer them 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
It may be possible specify a proxy, with or without password authentication, using a form like: 
# http://username:password@proxy.host.domain

OPTIONS

  • -l
    List the unapplied patches in terminal mode, with descriptions. Don't apply any patches.
  • -L
    List all patches in terminal mode, with a preceding '*' if the patch has not been applied. Don't apply any patches.
  • -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.
  • -Q
    In terminal mode, ignores warnings about running Antelope systems and applies patches without any user interaction. Be sure you know what you're doing if you use this option.
  • -t
    Terminal mode (no gui)
  • -v
    Be more verbose
  • The -l, -L, and -n options imply terminal mode and that no patches will be applied.

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 -tn

Not Installed: TrialPatch
        This empty patch verifies that antelope_update is working properly.

Steps that would be taken are:

Check for running real time systems ...
No running real time systems detected

Download and install patch files ...

Update applied_patches.html ...

You may restart systems now

% antelope_update -t

Not Installed: TrialPatch
        This empty patch verifies that antelope_update is working properly.

Check for running real time systems ...
No running real time systems detected

Do you wish to download and install these patches [y|n]?
y

Download patch files ...
Downloaded TrialPatch.tar.gz

Apply patches to Antelope installation ...

x /opt/antelope/dev/patched/TrialPatch

 ** installed TrialPatch.tar.gz

Update applied_patches.html ...

applied_patches.html updated

You may restart systems now

 

% antelope_update http://downloads.brtt.com/patches/5.10/Linux_x86
  ...

SEE ALSO 

brtt_installed_patches(1), rtsystems(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. Running-rtsystem detection is outsourced to the rtsystems(1) command. If that is not on the path or unable to run, antelope_update will be unable to detect running real-time systems (and will note such in the top bar, showing the rtsystems(1) problem output in the Progress box at the bottom of the user interface.

AUTHOR

This program by Sue Simoncic is based on original work by Daniel Quinlan.

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

Printer icon