12.5 Patch Naming Convention

     

Patches that offer additional or enhanced functionality may use a patch depot name appropriate to the software being loaded; for example, TOUR_A.01.00_HP- UX_B.11.11_32+64.depot is the name of the depot file to install IPv6 via the TOUR (Transport Optional Upgrade Release) bundle. An HP-UX patch fixing a defect will use a specific patch naming convention. This patch identifier will consist of a four-character type identifier, an underscore , and then a unique four- or five-digit numeric field. The four-character type identifier can be one of the following:

PHCO : A patch for commands and libraries

PHKL : A kernel patch

PHNE : A networking patch

PHSS : Other HP-UX subsystems, e.g., diagnostics, X11

The patch number is unique regardless of patch type. The resulting identifier is known as a patch handle or Patch ID . An example could be of the form PHCO_1000 . While Software Distributor does not recognize this naming convention, as of HP-UX 11.0 we have additional attributes that can be applied to a patch to identify it as being different to a normal product or fileset. Attributes such as is_patch and is_sparse are used to identify patches as well as the category tag of patch . We use this later to list patches with swlist .



HP-UX CSE(c) Official Study Guide and Desk Reference
HP-UX CSE(c) Official Study Guide and Desk Reference
ISBN: N/A
EAN: N/A
Year: 2006
Pages: 434

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net