A dupatch feature that looks at the files installed on a system, compares them to the files it expects to find, and prevents the installation of any patch files that might cause an incompatibility among system files.

customer-specific patch (CSP)

Any patch that is developed and made available to resolve a problem for a specific customer. A customer-specific patch is developed with prior knowledge of that customer's unique hardware and software configuration and environment. Customer-specific patches may not be useful for another customer's system.

See also release patch


A utility included in a patch kit that installs, removes, and manages patches for Tru64 UNIX and TruCluster software products. This utility is installed and left on the system through the successful installation of a patch kit.

full installation

A Tru64 UNIX installation that creates new file systems and loads a full copy of the operating system from the kit onto a system. Any other version of the operating system, any layered products, and any patches that previously existed on the system are overwritten. A full installation does not preserve system customizations (for example, user or data files) because the root (/), /usr, and /var file systems are re-created during the process.

See also update installation

official patch

See release patch


A file or 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 its own setld subset. The subsets are managed by a utility named dupatch.

patch applicability

A file-by-file check of system files to determine whether a patch might cause a a system to be degraded or crash. The installation of a patch is blocked if any system files to be replaced by that patch are not valid predecessors of the patch files.

release patch

Any patch that is included in a Tru64 UNIX patch kit. Sometimes referred to as official patches, release patches are intended for worldwide distribution and can be safely used on any customer's system within the guidelines documented in the patch kit.

See also customer-specific patch (CSP)

rolling upgrade

A software upgrade of a cluster that is performed while the cluster is in operation. One member at a time is rolled and returned to operation while the cluster transparently maintains a mixed-version environment for the base operating system, cluster, and Worldwide Language Support (WSL) software. Clients accessing services are not aware that a rolling upgrade is in progress.

On Version 5.0A and higher systems, you use a rolling upgrade to patch a cluster or to update the Tru64 UNIX operating system or TruCluster Server software on a cluster. The procedure is the same for both types of upgrades -- the only difference is the command you run during the install stage of the rolling upgrade procedure.


An interactive program for installing and managing software subsets. Software products are organized into subsets that can be loaded, deleted, inventoried, and configured. The load operation reads software from disk, tape, CD-ROM, or an Internet installation server. The patch installation tool, dupatch, is based on the setld program.

tar file

A file created with the tar command that saves and restores multiple files in a single file. Tru64 UNIX patch kits are provided as tar files (except for kits included on the Tru64 UNIX CD-ROM).

update installation

A type of installation that preserves disk partitions, file systems, file customizations, the network, print and mail environments, user accounts, user-created files, and any other system setup you may have done. If software patches had been applied to the operating system, it would not be necessary to remove the patches before beginning the update process, which is designed to update and reinstall any software fixes or features that were supplied in release patches.

See also full installation