Glossary
| This glossary defines key terms related to patching that are used in this book. HP |
| recommends the Software Distributor Administration Guide on the HP Business Support |
| Center website at |
ancestor | An ancestor of a patch is the preexisting software that is being modified or replaced by the |
| patch. |
applied | One of four possible states in which a patch is first installed. When a patch is installed, by |
| default it has the patch_state of applied. Other patch states include committed, |
| committed/superseded, and superseded. |
base software | The software that will be modified by a patch. |
bundle | An encapsulation of products, subproducts, and filesets into a single software object. Bundles |
| are a convenient way to group software objects for easy selection. When a bundle is specified |
| in a Software Distributor operation, all products or filesets contained in that bundle are included |
| in the operation. If the filesets within the bundle are patches, this is known as a patch bundle. |
| See also patch bundle. |
catalog, catalog | An area within a depot that contains all the information needed by |
directory | organization and contents of the products stored in the depot. The catalog (or catalog directory) |
| includes a global index file and a directory of information for each product version in the depot. |
category tags | See patch category. |
committed | The patch state in which the patch is applied and rollback files have been deleted. |
committed/ | The patch state in which the patch is both committed and superseded. |
superseded | See also superseded. |
control script | An optional script that is run during software installation, software removal, or software |
| configuration. |
corequisite | A dependency in which a fileset requires that another fileset be installed or configured at the |
| same time. For example, if fileset A requires that fileset B is installed at the same time, fileset |
| B is a corequisite. |
| See also dependency, prerequisite. |
cumulative patch | Each new patch contains all aspects of all its preceding patches. Patches for |
| are always cumulative. |
dependency | A relationship between filesets in which one requires another in a specific manner. For example, |
| before fileset A can be installed, it might require fileset B to be installed. |
| corequisite and prerequisite dependencies. |
| See also dependent. |
dependent | A fileset that has a dependency on another fileset. For example, if fileset A depends on fileset |
| B, then B is dependent or has a dependency on A. |
depot | A repository of software products and a catalog, organized so that |
| a software source. The contents of a depot reside in a directory structure with a single, common |
| root. |
depot source | See depot. |
directory depot | The directory on a target host in which a depot is located. The default is /var/spool/sw. |
DRD | See Dynamic Root Disk. |
Dynamic Root | Patches |
Disk | ability to install and manage patches on an inactive system image while the system is up and |
| running, allows most software maintenance tasks to be done during normal business hours, |
| limits the downtime required to the time it takes to reboot the system, and enables use of both |
| proactive and reactive patching. |
fileset | A grouping of one or more files contained in a product or subproduct. A fileset groups a subset |
| of a product's files into a manageable unit. Most Software Distributor operations are performed |
| on filesets. |
104 Glossary