6    System Upgrade Information

This chapter provides background information on Tru64 UNIX system upgrades in the presence of operating system patches. Releases of Tru64 UNIX are structured and distributed as full or sparse inventory kits.

6.1    Full Inventory Kit

This type of kit contains a full inventory of operating system objects (headers, libraries, kernel modules, and the like). It can be used to perform full and update installations:

The end result of either a full or an update installation is an operating system consisting of a known set of operating system objects that provides predictable system behavior.

Following an update installation it is necessary to install all layered products and all Tru64 UNIX patches (official as well as test) that were built for the new release.

6.2    Sparse Inventory Installation

The Tru64 UNIX Version 3.2C family sparse inventory operating system kits do not contain a full inventory of operating system objects. Also, it does not use either the full or the update installation processes described above; it uses setld directly.

Because a sparse inventory kit contains only a partial inventory of Tru64 UNIX objects, installing from this type of kit does not load an entire copy of Tru64 UNIX onto a system. Existing objects are overwritten only if replacement objects exist on the software kit.

Sparse inventory kits are produced assuming that any system to be upgraded is running the baseline operating system objects from a previous release. In the presence of patches, a layered product that modifies base operating system files and other files causes the system to deviate from one of the supported baselines and has the potential to cause object inconsistency following an installation from a sparse inventory kit. Therefore, you must exercise special care when upgrading from a sparse inventory kit.

Following a sparse inventory installation, you must install all appropriate versions of layered products and all operating system patches (official as well as test) that were built for the new release. Failure to do so will probably cause a regression in the behavior of layered products, the operating system, or both.

The following tables provide upgrade information for the V4.0 and V3.2 families of releases.

Table 6-1:  Upgrade Migration for Version 4.0 Family

Version Kit Type Upgrade Migration Supported
V4.0F Full From 4.0A, 4.0B, 4.0C, 4.0D, 4.0E
V4.0E Full From 4.0A, 4.0B, 4.0C, 4.0D
V4.0D Full From 4.0A, 4.0B, 4.0C
V4.0C Full Installs only on DIGITAL Personal Workstation 433AU and DIGITAL Personal Workstation 500AU
V4.0B Full From V4.0A
V4.0A Full From V3.2G or V4.0
V4.0 Full From V3.2C, V3.2D-1, V3.2D-2 via update installation

Table 6-2:  Upgrade Migration for Version 3.2 Family

Version Kit Type Upgrade Migration Supported
V3.2G Sparse From V3.2C, V3.2D-1, V3.2D-2, V3.2E-1, V3.2E-2, V3.2F via setld.
V3.2F Sparse Full From V3.2C, V3.2D-1 via setld. No migration path. Full installation only for AlphaServer 4100.
V3.2E-2 Sparse From V3.2D-2 via setld This release contains DIGITAL UNIX fixes necessary for TruCluster V1.0 to function.
V3.2D-2 Full No migration path. Full installation only for AlphaServer 2100A.
V3.2E-1 Sparse From V3.2D-1 via setld. This release contains DIGITAL UNIX fixes necessary for TruCluster V1.0 to function.
V3.2D-1 Sparse From V3.2C via setld.
V3.2C Full From V3.2, V3.2A, V3.2B via an update installation.
V3.2B Sparse This release provided V3.2 functionality for new hardware.
V3.2A -- This release consisted of layered products only.
V3.2 Full From V3.0, V3.0A, V3.0B via an update installation.