1
Introduction
This chapter provides an overview of the concepts and features of "Manually
installed" patch kits for the Tru64 UNIX operating system and TruCluster
Software (TCR) products.
1.1
Overview
"Manually installed" Patch kits provide immediate interim maintenance that
addresses the occurrence of known critical problems with the Tru64
UNIX operating system and the TruCluster Software products. These kits,
which are distributed as needed, contain the following elements:
"Manually installed" Patch kits are not intended to provide general maintenance
and new functions; applying them to your system does not obviate the need
to upgrade to later versions of Tru64 UNIX and TCR. Neither are they a
replacement for the Official patch kits regularly released containing
the aggregation of fixes for known critical problems.
1.1.1
Applicability of Patch Kits
Patch kits are applicable to a specific version of the software products,
unless stated otherwise in the patch kit release notes. You cannot install
version-specific kits on other software versions. Compaq recommends that
you install all of the patches included in the kits and that you update
the TCR products (if applicable) at the same time you update your operating
system.
1.1.2
Types of Patches
Compaq provides three kinds of patch kits for its Tru64 UNIX and TCR software
products -- release kits, customer-specific kits and manually installed
kits:
Release patches
These patches provide interim maintenance that prevent the occurrence
of known critical problems. Release patches (also referred to as
official
patches) are provided in kits, grouped by software product versions
such as DIGITAL UNIX V4.0D, Tru64 UNIX 5.0, and TCR 1.6. The following
are features of release patch kits:
Provide selective patch installation and removal
Use
dupatch for installing, viewing, removing, and managing
patches
Are provided on the Internet or CD-ROM
Customer-specific patches (CSPs)
These patches are provided by your service provider in response to
Tru64 UNIX or TCR problems that are specific to your own system's hardware
and software configuration. CSP kits have the following features:
Generally use the
dupatch utility for
installing, viewing, removing, and managing patches
May contain patches for one or more software products. For example,
a single tar file may contain patches for DIGITAL UNIX 4.0E, DIGITAL UNIX
4.0F, Tru64 UNIX 5.0, TCR1.5, and TCR1.6
May require release patches but do not contain any release patches
Manually installed Customer-specific patches (CSPs)
These patches are provided by your service provider in response to
immediate Tru64 UNIX or TCR problems that are specific to your own system's
hardware and software configuration, and that for some reason could not
be delivered as dupatch based kits. These kits have the following
features:
Minimal amount of management and patch relationship functionality.
Per-patch Shell script that does some pre-installation validations and
then the installation itself.
May contain patches for one or more software products. For example,
a single tar file may contain patches for DIGITAL UNIX 4.0E, DIGITAL UNIX
4.0F, Tru64 UNIX 5.0, TCR1.5, and TCR1.6. However, the installation scripts
are on a per-patch basis
This manual deals only with manually installed patches..
1.1.3
Patch Kit Distributions
Manually Installed Tru64 UNIX and TCR release patch kits are provided by
Compaq service providers.
1.1.4
Patch Kit Contents
Each patch kit contains the following components:
Documentation
The
Patch Summary
and Release Notes, which contains summaries and full descriptions of
the problems that the patches correct, and provides any information you
may need to know about specific patches.
The
Installation
Instructions (the manual you are reading) is common to all manually
installed patch kits.
The
release notes are available in text format, and the Installation Instructions
are provided in HTML and text format. The HTML version can be viewed with
your Internet browser, such as Netscape.
Patch subsets (the patched files themselves) and installation scripts
for the operating system and TruCluster Server products.
1.2
Patch Kit Packaging
A patch is a collection of files that contain fixes to problems. When possible,
patches are merged together into one patch if they have intersecting files
or codependencies. A patch may correct one or more problems.
Each patch is packaged in it's own subset and has it's own installation
script. You can choose which patches to install.
The following sections describe the syntax for
the names of the patch kits .
1.3
Patch Kit Naming
The naming conventions for release patch kits and for CSP kits are slightly
different.
1.3.1
Release Patch Kit Naming
Release patch kit names have the following syntax:
OS Product|Version|KitType|Kit#|-MfgDate|.FileType
The following list describes the attributes currently used in patch
kit names:
-
OS Product
DU = DIGITAL UNIX
T64 = Tru64 UNIX (some versions of Tru64 UNIX may have the DU label)
-
-
Version
V50
V40F
V40E
V40D
-
-
KitType
AS = Aggregate Selective (a kit that contains multiple patches)
SS = A patch kit containing a single patch (rarely used)
-
-
Kit#
The numeric identifier that Compaq uses to track the kit contents
-
-
-MfgDate
This is the year, month, and day the kit was built and is in the form
of YYYYMMDD
-
-
.FileType
.tar
For example, a file named
DUV4-FAS0001-19990609.tar contains Patch
Kit 1 for Tru64 UNIX Version 4.0F and TruCluster Server Version 1.6, manufactured
on June 9, 1999.
1.3.2
CSP Kit Naming
Customer-specific patch kits are provided by your server provider in response
to any of your reported Tru64 UNIX or TCR that require a software correction.
CSP kits provide interim patches for a specific customer's problem and
computing environment.
customer-specific patch
kit names have the following syntax:
Product|Version|BL|CPatchType|UniqueID|-MfgDate|.FileType
The following list describes the attributes currently used in patch
kit names:
-
Product
DU = DIGITAL UNIX
T64 = Tru64 UNIX
TCR = TruCluster
-
-
Version
V50
V40F
V40E
V40D
-
-
BL
The release patch base level the customer-specific patch is built against.
This is used by the service provider. For example: BL12
-
-
C
Indicates a customer-specific patch
-
-
PatchID
The numeric identifier used to track patches which are relative to
the product version patch kit
Patch identifiers have the following format:
-
MajorID
Five numeric digits, starting at 1
-
-
MinorID
Two numeric digits, starting at 0
-
UniqueID
The 4-8 place unique kitting ID for that patch
-
-
-MfgDate
The year, month, and day the kit was built and is in the form of YYYYMMDD
-
-
.FileType
.tar
For example, a file named
DUV40D11-C0039200-1007-19990822.tar
contains a customer-specific patch distribution for DIGITAL UNIX 4.0D patch
C392.00 manufactured on August 8, 1999 against base level 11.
1.3.3
Manually Installed CSP Kit Naming
The Naming of "Manually installed" kits is similar to that of dupatch
based CSP kits, with the addition of the word "Manual" in them. For example:
T64V511-C0000100-4584-Manual-20010117.
1.4
Patch Kit Installation Requirements
To successfully install Tru64 UNIX or TCR patch kits, your system must
meet the following requirements:
Be running the appropriate version of Tru64 UNIX or TCR.
Contain the necessary temporary and permanent storage space described
in the
Patch Summary and Release Notes document for the kit you
are installing.