1    Introduction

This chapter provides an overview of the concepts and features of the patch kits for the Tru64 UNIX operating system and TruCluster software products.

1.1    Overview

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 more than one problem.

The Tru64 UNIX and TruCluster software patch kits contain patches for critical problems for those software products. These kits, which are distributed as needed, provide interim maintenance that prevents the occurrence of known critical problems. The patch kits contain the following elements:

Patch kits are not intended to provide general maintenance and new functions; applying them to your system does not eliminate the need to upgrade to later versions of Tru64 UNIX and TruCluster software.

Patches are applicable to a specific version of the software products, unless stated otherwise in the Patch Summary and Release Notes. You cannot install version-specific kits on other software versions. HP recommends that you install all of the patches included in the kits and that you update the TruCluster software products (if applicable) at the same time you update your operating system.

To install Tru64 UNIX and TruCluster software patches, your system must meet the following requirements:

After you install the patches, the following items are left on the system:

1.2    Types of Patches

HP distributes three kinds of patches for its Tru64 UNIX and TruCluster software products — Release Patch Kits, Customer-Specific Patch Kits, and Early Release Patch Kits:

1.3    Patch Kit Distribution and Naming

Tru64 UNIX patches for specific operating system and TruCluster software releases and Customer-Specific patches are packaged together in tar files. Each patch kit contains the following components:

The contents of the tar file varies, depending on the type of kit. For example, a CSP kit might contain patches for several operating system versions, while Release Patch Kits always contain patches for only one operating system version. Also, the tar file may or may not contain TruCluster software patches. However, the structure of the tar file is the same for each type of kit. Figure 1-1 illustrates the contents of a patch tar file.

Figure 1-1:  Structure of a Patch Kit Tar File

The following sections describe Release and Customer-Specific Patch Kits.

1.3.1    Release Patch Kits

Tru64 UNIX and TruCluster software Release Patch Kits are available from the Internet and on CD-ROM.

Release patch kit names have the following syntax:

OS Product|Version|BaseLevel|KitType|Kit#|-MfgDate

For example, a file named T64V51B18AS0003-20011020.tar contains Patch Kit 0003, built in base level 18 for Tru64 UNIX Version 5.1 and TruCluster software Version 5.1, and manufactured on October 20, 2001.

The following list describes the attributes currently used in patch kit names:

OS Product

T64 = Tru64 UNIX

DU = DIGITAL UNIX

Version
Operating System Version

V51B

V51A

V51

V50A

V50

V40G

V40F

V40E

V40D

BaseLevel

The support pool in which the kit was built. This formerly internal number has become a common way of identifying kits.

KitType

AS = Aggregate Selective installation patch kit

SS = A patch kit containing a single patch

Kit#

The numeric identifier that HP uses to track the kit contents

-MfgDate

The year, month, and day the kit was built in the form of YYYYMMDD

1.3.2    Customer-Specific and Early Release Patch Kits

Customer-Specific Patch Kits provide interim patches for a specific customer's problem and computing environment.

Early Release Patch Kits, which provide one or more patches that will be incorporated into a future Release Patch Kit, are a type of Customer-Specific Patch Kit. Most of the information about CSPs in this manual also pertains to ERPs.

ESP and ERP kits have names similar to the following:

T64KIT0013825-V51B22-ES-20030708.tar

This tar file contains an an early release patch for Tru64 UNIX Version 5.1B, built in base level 22, with a patch identification of KIT0013825, and built on July 8, 2003.

The following list describes the attributes currently used in these patch kit names:

Product

T64 = Tru64 UNIX

TCR = TruCluster

DUX = DIGITAL UNIX (the name of the operating system prior to the Version 4.0F release)

Kit Identifcation Number

A seven-digit number.

Operating System Version

V51B

V51A

V51

V50A

V50

V40G

V40F

V40E

V40D

Base Level

The Release patch base level the Customer-Specific patch is built against, for example, 22. This field is used by the service provider.

Kit Type

E = Early Release

PatchID

The numeric identifier used to track patches that are relative to the product version patch kit. Patch identifiers have the following format:

MajorID

Five numeric digits, for example 00223.

MinorID

Two numeric digits, for example, 00.

-UniqueID

A unique kitting ID for the patch, for example, 1875.

-OptionalField

A field that provides information about the type of patch and its installation method.

Type:

E = Early release

S = Security

M = Manual installation

Valid Optional Field combinations:

E = Early release patch — dupatch installation

EM = Early release patch — Manual installation

ES = Early release patch — Security

EMS = Early release patch — Manual installation — Security

M = Manually installed CSP

-MfgDate

The year, month, and day the kit was built, in the form of YYYYMMDD.

1.4    Patch Process Resources

HP provides Web sites to help you with the patching process. The following sections provide pointers to general information and additional documents you can use.

1.4.1    Sites for Patching and General Information

1.4.2    Related Documentation

The following documentation can help you work with patch kits:

You can find the patch-specific documentation at the following Web site:

http://www.tru64unix.compaq.com/docs/patch/

You can find Tru64 UNIX and TruCluster software documentation at the following Web site:

http://www.tru64unix.compaq.com/docs