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
The following list describes a subset of available attributes:
• ancestor
◦ Applies to filesets.
◦ Identifies the fileset that must be on the system for the patch to be installable.
• category_tag
◦ Applies to products or filesets.
◦ Provides a label for a fileset or product. Several tags are defined during patch creation;
users can create others with the swmodify command.
◦ See “Category tags” (page 21).
• is_patch
◦ Applies to both patch products and filesets.
◦ When set to true, is_patch enables patch behavior.
• is_reboot
◦ Applies to filesets.
◦ When set to true, is_reboot indicates that installation of the fileset will cause the
system to reboot.
• patch_state
◦ Applies to patch filesets.
◦ Records the condition of patches.
◦ See “Patch state” (page 20).
• readme
◦ Applies to products.
◦ Contains the patch's original text file.
• software_spec
◦ Applies to bundles, products, or filesets.
◦ Contains the fully qualified identifier for the bundle, product, or fileset. Uniquely identifies
a specific instance of a software object.
• state
◦ Applies to filesets.
◦ Provides useful information about the installation state of software.
◦ See “State” (page 20).
Patch-related attributes 31