HP Tru64 UNIX and TruCluster Server Version 5.1B-5 Patch Summary and Release Notes (March 2009)

.
.
You can ignore this message. In all cases, the subsets will be installed correctly.
See “Cluster Cloning Offers Alternative to No-Roll Patching” (page 40) for an
introduction to dupclone.
2.2.3.2 Installed CSP Could Affect dupatch Cloning Process
If you have installed customer-specific patches (CSPs) on your system, you may see a
message similar to the following when installing this kit using the dupatch cloning
process, at which time the cloning process will be terminated:
Inspecting 69 patches for possible system conflicts ...
./usr/bin/ls:
is installed by Customer Specific Patch (CSP):
- Tru64_UNIX_V5.1B / Installation Patches:
Patch 01682.00 - Fix for dupatch command
and can not be replaced by this patch. To install this patch,
ideally, you must first remove the CSP using dupatch.
Before performing this action, you should contact your
HP Service Representative to determine if this patch kit
contains the CSP. If it does not, you may need to obtain a new
CSP from HP in order to install the patch kit and retain the
CSP fix. Or, you may use dupatch baselining to enable the
patch installation.
The recommended action is to perform dupatch baselining on your existing system
to enable the patch installation process and retain the CSP on your system. Removing
the CSP (as mentioned in message) could eliminate the fixes made by that CSP.
After running the baselining process on your existing system, you will need to begin
the cloning process from the beginning by reduplicating your system on an alternate
set of disks and rerunning the dupatch cloning process. See the Patch Kit Installation
Instructions for information about performing baselining and on the patch cloning
process.
2.2.3.3 Migrating a Patched Standalone System to a Cluster
Installing only the base patches on a non-cluster system omits various patches (including
some security patches) because of dependencies on TruCluster Server patches. Such
patches are not needed in standalone systems. However, if the standalone system is
then clustered using the clu_create command and you attempt to apply the cluster
patches, many patches will fail with errors because various prerequisite patches failed.
These errors do not necessarily indicate that the patch process has failed, but they are
numerous, can be confusing and might obscure genuine errors.
The preferred procedure for adding a standalone system into a cluster is as follows:
2.2 Important Kit Installation and Removal Release Notes 31