Patch Management User Guide for HP-UX 11.x Systems (5900-3011, April 2013)
Table Of Contents
- Patch Management User Guide for HP-UX 11.x Systems
- Contents
- 1 HP-UX patches and patch management
- 2 Quick start guide for patching HP-UX systems
- 3 HP-UX patch overview
- 4 Patch management overview
- Patch management life cycle
- HP service contracts
- Patch management and software change management strategies
- Establishing a software change management strategy
- Recommendations for software change management
- Consideration of HP patch rating
- Patch management and software depots
- Proactive patching strategy
- Reactive patching strategy
- Advanced topic: security patching strategy
- Advanced topic: scanning for security patches
- Testing the patches to be installed
- 5 What are standard HP-UX patch bundles?
- 6 Using the HP Support Center
- Obtaining an HPSC user account
- Useful pages on the HPSC
- Find individual patches
- Advanced topic: checking for special installation instructions
- Advanced topic: checking for all patch dependencies
- Standard patch bundles
- Custom patch bundles - run a patch assessment
- Support information digests
- Ask your peers in the forums
- Search knowledge base
- 7 Using software depots for patch management
- Common software distributor commands for patching
- Depot types
- Using depots
- Viewing depots
- Creating and adding to a directory depot
- Registering and unregistering directory depots
- Verifying directory depots
- Removing software from a directory depot
- Removing a directory depot
- Installing patches from a depot
- Custom patch bundles
- 8 Using HP-UX Software Assistant for patch management
- 9 Using Dynamic Root Disk for patch management
- 10 The Patch Assessment Tool
- 11 Support and other resources
- A Patch usage models
- Glossary
- Index
• supersedes
◦ Applies to patch filesets.
◦ Lists all prior filesets that a patch fileset supersedes.
◦ See “Ancestors and supersession” (page 26).
• superseded_by
◦ Applies to patch filesets.
◦ Records the software specification of the fileset that superseded the fileset on a given
system. This attribute is set only for installed patch filesets, and never in software depots.
◦ See “Ancestors and supersession” (page 26).
You can show these attributes with the swlist command using the -a attribute argument,
replacing attribute with one of the previously listed attributes. For more information about the
swlist command, see “Which patches are on a system?” (page 22).
Patch dependencies
A patch that depends on other software in order to install or run correctly is said to have a
dependency on that other software. In order to become fully active, a patch might require changes
to areas of the system other than those it modifies. Such a patch might have a documented
dependency on one or more patches or nonpatch software products that are responsible for the
changes in these other areas.
For example, in Figure 3: “Patch Supersession Chains and Patch Dependencies” (page 32),
PHXX_31967 and PHXX_31937 depend on each other (mutual dependency). At a later time,
PHXX_32384 supersedes PHXX_31937, and PHXX_31967 can be successfully installed with
either patch. (PHXX_32384, as a cumulative patch, will satisfy the entire dependency.)
Figure 3 Patch Supersession Chains and Patch Dependencies
However, a superseded (older) patch does not satisfy a dependency on a superseding (newer)
patch. Figure 3: “Patch Supersession Chains and Patch Dependencies” (page 32) provides an
example. PHXX_33662 supersedes PHXX_31967, but PHXX_33662 has an updated dependency
on the superseding patch PHXX_32384. In this case, the older patch (PHXX_31937) doesn't satisfy
the new dependency
For more information about supersession, see “Ancestors and supersession” (page 26).
32 HP-UX patch overview