HP Tru64 UNIX and TruCluster Server Version 5.1.B-4 Patch Summary and Release Notes (13156)

B Prior Patch Installation Changes
Beginning with Version 5.1B-2, we changed the way Tru64 UNIX patch kits are installed and
removed, and Version 5.1B-3 introduced additional changes. The following sections describe
these changes.
See the Patch Kit Installation Instructions manual for complete information about installing,
removing, and managing Tru64 UNIX patch kits.
B.1 Changes Made in Version 5.1B-3
If you did not install Version 5.1B-3 but have installed earlier kits, you will see the following
differences in the kitting process:
• Before you can install this kit you must accept the conditions included in the license that
the dupatch utility displays. You can read this license in Appendix C “Component
Licensing”.
• You can delete the patch kit by kit name rather than by specifying individual patches. With
the introduction of this feature, you can easily delete patches interactively using the dupatch
utility or from the dupatch command line. This feature also works on pre-Version 5.1B-4
kits.
• You can delete patches in multi-user mode.
• You can force the installation of the patch kit even if file conflicts exist. This feature is an
extension of the dupatch baselining feature.
• A new command-line option, Patch Level, provides a single command that provides a full
description of the patch kits, CSPs, and ERPs installed on your system.
B.2 Changes Made in Version 5.1B-2
If you did not install versions 5.1B-2 or 5.1B-3 but have installed earlier kits, you will see the
following differences in the kitting process:
• All or none installation
When you install an inclusive patch kit, you must install all patches; you can no longer select
specific patches to install. By making the installation of all patches mandatory, you can patch
with greater confidence that the process will be problem free.
Before a patch kit is released, it is tested on many types of systems and system configurations.
This testing continues until we are assured that the patches perform the tasks they were
designed for and do not introduce new problems. It is not possible to achieve this type of
testing on every possible combination of individually selected patches.
• Substantially reduced installation time
The installation process for inclusive patch kits can reduce the time it takes to install the
patches by as much as half from what you are used to. For large, clustered systems, the
difference can be several hours faster.
• Fewer patches displayed
Because of the way these new patch kits are designed, you will see many fewer patches
listed by dupatch during the installation process. For example, a partial listing you see will
be similar to the following:
- Tru64_UNIX_V5.1B / Security Related Patches:
* Patch 27001.00 - SP04 OSFACCT540
* Patch 27002.00 - SP04 OSFADVFS540 (SSRT2275)
* Patch 27003.00 - SP04 OSFADVFSBIN540
In the old-style patch kits, these three patches might have consisted of perhaps 20 individual
patches being displayed. The difference is not in the content of the kits, but rather in the
B.1 Changes Made in Version 5.1B-3 187