HP Tru64 UNIX Version 5.1B-2 and Higher Patch Kit Installation Instructions (March 2009)

Your name: Betty
Enter any notes about this operation that you would like stored for
future reference (To end your input, enter a "."):
: preinstall check for patch kit 5
: .
7. The program lists any patches that fail the prerequisite and applicability checks, and asks
how you want to proceed. You have the following choices:
Checking patch prerequisites and patch file applicability...
(depending upon the number of patches you select, this may take awhile)
*** The Patch Kit will install 80 patches ***
-------------------------------------------------------------------------
Problem installing:
- Tru64_UNIX_V5.1B / Kernel Patches:
Patch 26009.00 - SP05 OSFBASE540 (SSRT3631 SSRT3469 SSRT2439 ...)
./usr/sbin/cron:
is installed by Customer Specific Patch (CSP):
- Tru64_UNIX_V5.1B:
Patch C 00981.00
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.
This patch will not be installed.
-------------------------------------------------------------------------
* The following 1 patch(es) failed in prerequisite/file applicability check:
- Tru64_UNIX_V5.1B / Kernel Patches:
Patch 26009.00 - SP05 OSFBASE540 (SSRT3631 SSRT3469 SSRT2439 ...)
* There were 1 patch(es) which failed in prerequisite/file applicability check:
Press Return to go back to the previous menu
Creating a Baseline
The dupatch baselining process 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. This section provides an overview of the baselining process.
See “Creating a Baseline” for instructions on setting a baseline.
Unknown system files occur when the files are replaced through non-standard system file
installation methods such as the following:
• The manual installation of system files such as system administration customizations or
manually installed patches
• Using the setld utility to install system files from user-derived setld subsets
• Using the setld utility to install files for layered software products
• Changes that result from weak system control programs (usually named file.scp)
Missing system files result from a root user manually deleting system files that were installed
during a standard full or update installation procedure or with the dupatch utility. The file is
removed but the system inventory records are still in place.
Unknown and missing system files will block patch installations until you take corrective action.
However, before taking any action, it is important that you understand the origin of the unknown
Creating a Baseline 25