|baselining || |
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) Kit|| |
A patch kit 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. An Early Release patch is a type of CSP.
See also Early Release Patch (ERP) Kit, Release Patch Kit.
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.
|Early Release Patch (ERP) Kit|| |
A patch kit that contains a patch or patches that will be included in a Release Patch Kit that is still under development. ERPs, which are a type of Customer-Specific patch, are provided by HP to help customers who have an immediate need for some specific functionality that will be included in an upcoming Release Patch Kit.
See also Customer-Specific Patch (CSP) Kit, Release Patch Kit.
|force install|| |
A term somtimes used to describe the abilility of the baselining procedure to enable the installation of patches that are blocked by the intallation procedure.
|inclusive patch kit|| |
See new style patch kit.
|new style patch kit|| |
Also called an inclusive patch kit, a new style patch kit is a Release Patch Kit that provides an improved way of delivering patches. Among the ways that a new style patch kit differs from its predecessors is that it requires an all or none installation and removal of the patches in that kit. The first Tru64 UNIX new style patch kit was Version 5.1B Patch Kit 4 (Base Level 25).
See also Release Patch Kit.
|no-roll patching|| |
A process that patches your cluster in one operation and requires only one reboot of the whole cluster to complete the operation. This method was developed for mission-critical environments to provide a way to apply patches quickly, with a minimum amount of down time.
The no-roll patch process is a modification of dupatch; that is, all patches are installed or removed entirely using the dupatch utility, as opposed to the clu_upgrade and dupatch utilities used in the rolling upgrade procedure. The no-roll process conducts significantly fewer operations than the rolling upgrade procedure.
See also rolling upgrade.
|official patch|| |
See Release Patch Kit.
|old style patch kit|| |
See new style patch kit.
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 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 Kit|| |
A patch kit that HP provides to modify a specific version of the Tru64 UNIX operating system and TruCluster software. Sometimes referred to as official patch kits, Release Patches Kits are intended for worldwide distribution and can be safely used on any customer's system within the guidelines documented in the kit. The patches in a Release Patch Kit are referred to as Release patches.
See also Customer-Specific Patch (CSP) Kit, Early Release Patch (ERP) Kit, new style patch kit.
|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 (WLS) 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 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.
See also no-roll patching.
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 UNIXpatch kits are provided as tar files (except for kits included on a Patch CD–ROM).
|version switch|| |
During a rolling upgrade, a version switch manages the transition of the active version to the new version of an operating system. The active version is the one that is currently in use. The purpose of a version switch in a cluster is to prevent the introduction of potentially incompatible new features until all members have been updated.
See also rolling upgrade.