HP Tru64 UNIX Version 5.1B-2 and Higher Patch Kit Installation Instructions (March 2009)
Manually Installed Release Patches
For some software products, manual installation has been the practiced method for patch
installation. For example, patches for TruCluster software used to be installed manually.
You must determine whether the fixes delivered by the manually installed Release patches are
included in the current dupatch-based Release Patch Kit before enabling dupatch to overwrite
any unknown or missing system files. Once you have made this determination, proceed as
follows:
• If the unknown or missing system files are attributable to the manual installation of Release
patches and those patches are included in the current dupatch-based Release Patch Kit,
you can safely enable dupatch to overwrite applicable missing or unknown system files.
• If the unknown or missing system files are not attributable to manual installation, you must
understand the origin of the unknown or missing system files by reviewing the information
reported in Phase 4 against your log of manual system changes to ensure you understand
why the system was intentionally customized, and to determine how to proceed.
User Customized Commands and Utilities
Periodically, system administrators of production computing environments replace Tru64 UNIX
commands or utilities with freeware or their own customized version of the command or utility.
In this situation you must ensure the unknown or missing files are attributable to intentional
replacement of commands, utilities, or other system files.
If the unknown or missing system files are attributable to the replacement of commands, utilities,
or other system files with customized versions for the computing environment, do not enable
dupatch to overwrite the manually installed customized files. Instead, determine the reason
for the customization and then decide how to proceed.
Phase 5 – Enabling dupatch to Overwrite Changed System Files
Phase 5 reports patches that are blocked due to missing or unknown system files, and optionally
allows you to override the dupatch conflict management mechanism so the dupatch-based
patch may be installed.
For each patch that is blocked by a missing or unknown system file you are presented with the
following information:
• Software product identifier
• Patch category
• Patch identifier
• Patch subset description
• The list of unknown and missing files that block the patch installation
• The origin of all other files contained in the patch
Optionally, you can enable dupatch to override the collision detection mechanisms and install
any of these patches. Use the missing and unknown file information presented in Phase 4 and
your system administration log of manual system changes to make Phase 5 patch installation
enabling decisions.
We recommended that you do not enable dupatch to install patches over missing or unknown
system files for which you do not know the origin. Doing so may leave your operating system
and TruCluster software environment in an inconsistent and nonoperational state.
We also recommend that you backup your operating system prior to the actual patch installation.
Phase 6 – Report CSPs with Inventory Conflicts
Phase 6 provides the information about patches that have inventory conflict due to certain CSPs
that are installed on the system. You will use this information when considering your decision
in Phase 7.
28 Preparing for the Installation