
   [DUTRANS.GIF]              [COMPAQN2.GIF]
                 Manual Patch Kit Installation Instructions
                    Tru64 UNIX Patch Kits, February 2001
   
                      Compaq Computer Corporation 2001
     _________________________________________________________________
   
     This manual provides instructions for installing "manually
     installed " Customer Specific Patches. It also describes other
     information for working with this type of patches. For information
     about individual patches, see the Patch Summary and Release Notes
     document for the kit you are installing.
     
     
     _________________________________________________________________
   
   COMPAQ, the Compaq logo, and the Digital logo are registered in the
   U.S. Patent and Trademark Office. Alpha, AlphaServer, NonStop,
   TruCluster, and Tru64 are trademarks of Compaq Computer Corporation.
   
   Microsoft and Windows NT are registered trademarks of Microsoft
   Corporation. Intel, Pentium, and Intel Inside are registered
   trademarks of Intel Corporation. UNIX is a registered trademark and
   The Open Group is a trademark of The Open Group in the United States
   and other countries. Other product names mentioned herein may be the
   trademarks of their respective companies.
   
   Possession, use, or copying of the software described in this
   publication is authorized only pursuant to a valid written license
   from Compaq Computer Corporation or an authorized sublicensor.
   
   Compaq Computer Corporation shall not be liable for technical or
   editorial errors or omissions contained herein. The information in
   this document is subject to change without notice.
   
   7/10 (csp)

   [1]Title and Copyright Information
   
   
   [2]About This Manual
   
   [3]Audience
   
   [4]Organization
   
   [5]Related Documentation
   
   [6]Reader's Comments
   
   
   1  [7]Introduction
   
   1.1  [8]Overview
   
   1.1.1  [9]Applicability of Patch Kits
   
   1.1.2  [10]Types of Patches
   
   1.1.3  [11]Patch Kit Distributions
   
   1.1.4  [12]Patch Kit Contents
   
   1.2  [13]Patch Kit Packaging
   
   1.3  [14]Patch Kit Naming
   
   1.3.1  [15]Release Patch Kit Naming
   
   1.3.2  [16]CSP Kit Naming
   
   1.3.3  [17]Manually Installed CSP Kit Naming
   
   1.4  [18]Patch Kit Installation Requirements
   
   
   2  [19]Manually Installed Patch Management
   
   2.1  [20]Overview of manually Installed patches
   
   2.2  [21]Accessing files delivered with a given patchl
   
   2.3  [22]Acessing files saved during backup
   
   2.4  [23]Acessing patch documentation
   
   2.5  [24]Patch Installation Log
   
   2.6  [25]Patch Installation Event log
   
   
   
   
   3  [26]Issues and Restrictions
   
   3.1  [27]When Single-User Mode Is Recommended
   
   3.2  [28]Impact on System Upgrades to Later Versions of Tru64 UNIX
   
   3.3  [29]No RIS or DMS Installation of Patches
   
   3.4  [30]Direct setld Installation and Removal of Patch Subsets Is Not
   Allowed
   
   3.5  [31]Limitation for /var/adm/patch/backup Directory Handling
   
   3.6  [32]No Ctrl/c During Installation Phase
   
   3.7  [33]Manually Installed patches can not be deleted.
   
   3.8  [34]Release Patches Do Not Automatically Supersede CSPs
   
   
   4  [35]Patch Installation Instructions
   
   4.1  [36]Summary of Steps for Using Patch Kits
   
   4.2  [37]Preparing to Install Patches
   
   4.3  [38]Making the Patch Distribution Available
   
   4.4  [39]Installing Patches
   
   4.4.1  [40]Choosing SIngle-User or Multiuser Mode
   
   4.4.2  [41]Choosing which patch to install
   
   4.4.3  [42]Find installation script
   
   4.4.4  [43]Execute installation script
   
   4.5  [44]Rebuilding the Kernel
   
   
   5  [45]Sample Patch Kit Installation
   
   5.1  [46]Sample 1: Typical Patch Kit Installation
   
   
   6  [47]Common Error, Warning, and Informational Messages
   
   6.1  [48]Patch Installation Messages
   
   6.1.1  [49]Patch Installation must be executed by root
   
   6.1.2  [50]Patch Installation is installing a new file
   
   6.1.3  [51]Patch Installation tried to save the file twice
   
   6.1.4  [52]Patch Installation Can't find doucment in kit
   
   6.1.5  [53]Patch Installation requires kernel rebuild and reboot
   
   6.1.6  [54]Patch Installation Blocked by non-installed subsets
   
   6.1.7  [55]Patch Installation Blocked by product version check
   
   6.1.8  [56]Patch Installation Blocked by name sanity check
   
   6.1.9  [57]Patch was already installed
   
   6.1.10  [58]Patch installation can not be logged
   
   6.1.11  [59]Patch installation can not find tar file
   
   
   [60]Glossary
   
   
   
   
   Index


     _________________________________________________________________
   
                               About This Manual
                                       
   This manual provides instructions for installing "manually installed"
   Customer Specific Patches. It also describes other information for
   working with this type of patches. For information about individual
   patches, see the Patch Summary and Release Notes document for the kit
   you are installing.
   
                                    Note
                                      
     In most instances, this manual uses the name Tru64 UNIX for all
     versions of the operating system, including those that were
     originally released as DIGITAL UNIX.
     
     In general, the terms TruCluster Software Products and TCR are used
     throughout this manual to refer to all releases of the Compaq's
     TruCluster products.
     
     This manual does not deal with the patches delivered using the
     dupatch management utility. Rather it deals with a specialized type
     of patch, that normally is not used.
     
Audience

   This manual is for the person who installs "manually installed" patch
   kits and for anyone who manages patches after they are installed.
   
Organization

   This manual is organized as follows:
   
   CAPTION:
   
   [1]Chapter 1 Provides an overview of the concepts and features of the
   "manually installed" patch kits.
   [2]Chapter 2 Describes the (minimal) management functions available.
   [3]Chapter 3 Provides information you must be aware of when installing
   patches.
   [4]Chapter 4 Describes the procedures for installing patches.
   [5]Chapter 5 Provides samples for installing patches, and viewing
   patch documentation.
   [6]Chapter 6 Describes error messages you might see while installing
   or maintaining patches.
   
Related Documentation

   In addition to this manual, you should be familiar with the concepts
   and mechanisms described in the following documents:
   [dupatch] Patch Installation Guide
       Patch Summary and Release Notes document for the patch kit you are
       working with
       Tru64 UNIX Installation Guide
       Tru64 UNIX System Administration manual
       TruCluster Software Products Software Installation manual
       TruCluster Software ProductsCluster Administration manual
       Any release-specific installation documentation
       
Reader's Comments

   Compaq welcomes any comments and suggestions you have on this and
   other Tru64 UNIX manuals.
   
   You can send your comments in the following ways:
   Fax: 603-884-0120 Attn: UBPG Publications, ZK03-3/Y32
       Internet electronic mail: [7]readers_comment@zk3.dec.com
       A Reader's Comment form is located on your system in the following
       location:
/usr/doc/readers_comment.txt
       Mail:
       Compaq Computer Corporation
       UBPG Publications Manager
       ZK03-3/Y32
       110 Spit Brook Road
       Nashua, NH 03062-9987
       
       
   Please include the following information along with your comments:
   The full title of this document.
       The section numbers and page numbers of the information on which
       you are commenting.
       The version of Tru64 UNIX that you are using.
       If known, the type of processor that is running the Tru64 UNIX
       software.
       
   The Tru64 UNIX Publications group cannot respond to system problems or
   technical support inquiries. Please address technical questions to
   your local system vendor or to the appropriate Compaq technical
   support office. Information provided with the software media explains
   how to send problem reports to Compaq.
     _________________________________________________________________


     _________________________________________________________________
   
                               1    Introduction
                                       
   This chapter provides an overview of the concepts and features of
   "Manually installed" patch kits for the Tru64 UNIX operating system
   and TruCluster Software (TCR) products.
   
1.1    Overview

   "Manually installed" Patch kits provide immediate interim maintenance
   that addresses  the occurrence of known critical problems with the
   Tru64 UNIX operating system and the TruCluster Software products.
   These kits, which are distributed as needed, contain the following
   elements:
   Version-specific patches and patch-specific documentation
       A minimal patch-management utility for "manually" installing
       patches
       
   "Manually installed" Patch kits are not intended to provide general
   maintenance and new functions; applying them to your system does not
   obviate the need to upgrade to later versions of Tru64 UNIX and TCR.
   Neither are they a replacement for the Official patch kits regularly
   released containing the aggregation of fixes for known critical
   problems.
   
  1.1.1    Applicability of Patch Kits
  
   Patch kits are applicable to a specific version of the software
   products, unless stated otherwise in the patch kit release notes. You
   cannot install version-specific kits on other software versions.
   Compaq recommends that you install all of the patches included in the
   kits and that you update the TCR products (if applicable) at the same
   time you update your operating system.
   
  1.1.2    Types of Patches
  
   Compaq provides three kinds of patch kits for its Tru64 UNIX and TCR
   software products -- release kits, customer-specific kits and manually
   installed kits:
   Release patches
       These patches provide interim maintenance that prevent the
       occurrence of known critical problems. Release patches (also
       referred to as official patches) are provided in kits, grouped by
       software product versions such as DIGITAL UNIX V4.0D, Tru64 UNIX
       5.0, and TCR 1.6. The following are features of release patch
       kits:
       
   Provide selective patch installation and removal
       Use dupatch for installing, viewing, removing, and managing
       patches
       Are provided on the Internet or CD-ROM
       
   Customer-specific patches (CSPs)
   These patches are provided by your service provider in response to
   Tru64 UNIX or TCR problems that are specific to your own system's
   hardware and software configuration. CSP kits have the following
   features:
   Generally use the dupatch utility for installing, viewing, removing,
       and managing patches
       May contain patches for one or more software products. For
       example, a single tar file may contain patches for DIGITAL UNIX
       4.0E, DIGITAL UNIX 4.0F, Tru64 UNIX 5.0, TCR1.5, and TCR1.6
       May require release patches but do not contain any release patches
       
   Manually installed Customer-specific patches (CSPs)
   These patches are provided by your service provider in response to
   immediate Tru64 UNIX or TCR problems that are specific to your own
   system's hardware and software configuration, and that for some reason
   could not be delivered as dupatch based kits. These kits have the
   following features:
   
       Minimal amount of management and patch relationship functionality.
       Per-patch Shell script that does some pre-installation validations
       and then the installation itself.
       May contain patches for one or more software products. For
       example, a single tar file may contain patches for DIGITAL UNIX
       4.0E, DIGITAL UNIX 4.0F, Tru64 UNIX 5.0, TCR1.5, and TCR1.6.
       However, the installation scripts are on a per-patch basis
       
   This manual deals only with manually installed patches..
   
  1.1.3    Patch Kit Distributions
  
   Manually Installed Tru64 UNIX and TCR release patch kits are provided
   by Compaq service providers.
   
  1.1.4    Patch Kit Contents
  
   Each patch kit contains the following components:
       Documentation
       The Patch Summary and Release Notes, which contains summaries and
       full descriptions of the problems that the patches correct, and
       provides any information you may need to know about specific
       patches.
       The Installation Instructions (the manual you are reading) is
       common to all manually installed patch kits.
       The release notes are available in text format, and the
       Installation Instructions are provided in HTML and text format.
       The HTML version can be viewed with your Internet browser, such as
       Netscape.
       Patch subsets (the patched files themselves) and installation
       scripts for the operating system and TruCluster Server products.
       
1.2    Patch Kit Packaging

   A patch is a collection of files that contain fixes to problems. When
   possible, patches are merged together into one patch if they have
   intersecting files or codependencies. A patch may correct one or more
   problems.
   
   Each patch is packaged in it's own subset and has it's own
   installation script. You can choose which patches to install.
   
   The following sections describe the syntax for the names of the patch
   kits .
   
1.3    Patch Kit Naming

   The naming conventions for release patch kits and for CSP kits are
   slightly different.
   
  1.3.1    Release Patch Kit Naming
  
   Release patch kit names have the following syntax:
   
   OS Product|Version|KitType|Kit#|-MfgDate|.FileType
   
   The following list describes the attributes currently used in patch
   kit names:
   
   OS Product
          DU = DIGITAL UNIX
          T64 = Tru64 UNIX (some versions of Tru64 UNIX may have the DU
          label)
          
   Version
          V50
          V40F
          V40E
          V40D
          
   KitType
          AS = Aggregate Selective (a kit that contains multiple patches)
          SS = A patch kit containing a single patch (rarely used)
          
   Kit#
          The numeric identifier that Compaq uses to track the kit
          contents
          
   -MfgDate
          This is the year, month, and day the kit was built and is in
          the form of YYYYMMDD
          
   .FileType
          .tar
          
   For example, a file named DUV4-FAS0001-19990609.tar contains Patch Kit
   1 for Tru64 UNIX Version 4.0F and TruCluster Server Version 1.6,
   manufactured on June 9, 1999.
   
  1.3.2    CSP Kit Naming
  
   Customer-specific patch kits are provided by your server provider in
   response to any of your reported Tru64 UNIX or TCR that require a
   software correction. CSP kits provide interim patches for a specific
   customer's problem and computing environment.
   
   customer-specific patch kit names have the following syntax:
   
   Product|Version|BL|CPatchType|UniqueID|-MfgDate|.FileType
   
   The following list describes the attributes currently used in patch
   kit names:
   
   Product
          DU = DIGITAL UNIX
          T64 = Tru64 UNIX
          TCR = TruCluster
          
   Version
          V50
          V40F
          V40E
          V40D
          
   BL
          The release patch base level the customer-specific patch is
          built against. This is used by the service provider. For
          example: BL12
          
   C
          Indicates a customer-specific patch
          
   PatchID
          The numeric identifier used to track patches which are relative
          to the product version patch kit
          
          Patch identifiers have the following format:
          
        MajorID
                Five numeric digits, starting at 1
                
        MinorID
                Two numeric digits, starting at 0
                
   UniqueID
          The 4-8 place unique kitting ID for that patch
          
   -MfgDate
          The year, month, and day the kit was built and is in the form
          of YYYYMMDD
          
   .FileType
          .tar
          
   For example, a file named DUV40D11-C0039200-1007-19990822.tar contains
   a customer-specific patch distribution for DIGITAL UNIX 4.0D patch
   C392.00 manufactured on August 8, 1999 against base level 11.
   
   
  1.3.3    Manually Installed CSP Kit Naming
  
   The Naming of "Manually installed" kits is similar to that of dupatch
   based CSP kits, with the addition of the word "Manual" in them. For
   example: T64V511-C0000100-4584-Manual-20010117.
   
1.4    Patch Kit Installation Requirements

   To successfully install Tru64 UNIX or TCR patch kits, your system must
   meet the following requirements:
   Be running the appropriate version of Tru64 UNIX or TCR.
       Contain the necessary temporary and permanent storage space
       described in the Patch Summary and Release Notes document for the
       kit you are installing.
     _________________________________________________________________

     _________________________________________________________________
   
                   2    Manually Installed Patch Management
                                       
   This chapter describes the (minimal) management functions available
   for working with manually installed patches.
   
2.1    Overview of Manually Installed patches

   Manually installed patches have minimal management functionality
   associated with them. They are not intended to be the normal release
   mechanism for patches (which is dupatch). In general this type of
   packaging supplies some functionality to validate that the patch
   actually belongs on the system, and to leave some record of the
   installation. There is no supported way to de-install Patches that
   were "manually installed". If you wish to install a dupatch-based
   patch over a "Manually installed" patch, you will first need to
   [1]baseline the system. For more details, see the dupatch
   documentation.
   
   In general, there are no supplied utilitites for user management of
   the manually installed patches. However the installation script leaves
   some information on the system that can be accessed as detailed in the
   following sections.
   
2.2    Accessing files delivered with a given patch.

   A list of the files delivered with a given patch can be found in
   ./var/adm/manual_patch/db/$PatchId.FileList. For example:
   fenster@fenster_digital> cat
   /var/adm/manual_patch/db/OSFPATC0000100510.FileList
   ./usr/sbin/mknod
   ./var/adm/patch/support/OSFPATC0000100510/passwd
   
2.3    Accessing files saved during backup

   Before a file is replaced by the installation script, it is saved in
   the name space of OriginalFile.PreManualCSP.$TimeStamp. For example:
   ./usr/sbin/mknod was saved as
   ./usr/sbin/mknod.PreManualCSP.2001-02-11-12:35:54.
   
   
2.4    Accessing patch documentation

   As part of the installation procedure, patch associated documentation
   is copied onto the system. The documentation can be found in
   /var/adm/manual_patch/doc/$PatchId.Suffix. For example:
   
   
   CAPTION: List of documentation files copied onto the system
   
   Filename Description of contents
   /var/adm/manual_patch/doc/OSFPATC0000100510.abs Abstract of problem(s)
   that the patch fixes.
   /var/adm/manual_patch/doc/OSFPATC0000100510.problem_ids List of
   problem ids that the patch fixes.
   /var/adm/manual_patch/doc/OSFPATC0000100510.rcs_strings List of rcs
   ids of files used to create patch.
   /var/adm/manual_patch/doc/OSFPATC0000100510.txt Description of
   problem(s) that the patch fixes.
   /var/adm/manual_patch/doc/OSFPATC0000100510.special_instructions
   Special instructions for this patch.
   
   In addition the release notes for each patch kit are copied into
   ./var/adm/manual_patch/doc. For example:
   /var/adm/manual_patch/doc/T64V511-C0000100-4584-Manual-20010117.txt
   
2.5    Patch Installation log

   A log of the installation of a given patch can be found in
   ./var/adm/manual_patch/logs/$PatchId.log. For example:
   /var/adm/manual_patch/log/OSFPATC0000100510.
   
2.6    Patch Installation Event log

   A log of all of the activity around manually installed patches can be
   found in /var/adm/manual_patch/log/Install.log. The format is of one
   entry per line, with each entry having the following format:
   Keyword%Date%KitName%Patch Description%Patch Category
   
     For example:
     
     INSTALL%2001-02-11-12:35:54%T64V511-C0000100-4584-Manual-20010117%T
     ru64 UNIX V5.1 Patch C1.00%Patch:Description%Miscellaneous Patches
   ______________________________________________________________________


     _________________________________________________________________
   
                         3    Issues and Restrictions
                                       
   This chapter provides information you must be aware of when installing
   patches. Be sure to check the Patch Summary and Release Notes document
   of the kit you are installing for any issues and restrictions that
   pertain to that installation.
   
3.1    When Single-User Mode Is Recommended

   Although you can install patches in multiuser mode, Compaq recommends
   that you bring down your system to single-user mode when installing
   patches that affect the operation of the Tru64 UNIX operating system
   or the product you are patching. If your system must remain in
   multiuser mode, it is recommended that you apply the patches when the
   system is as lightly loaded as possible.
   
   
3.2    Impact on System Upgrades to Later Versions of Tru64 UNIX

   In the presence of patches or layered products, certain procedures
   used to upgrade a system to a later version of Tru64 UNIX can lead to
   an inconsistency among operating system and layered product objects.
   For more information see [1]Appendix A for general Tru64 UNIX system
   upgrade information.
   
3.3    No RIS or DMS Installation of Patches

   Remote Installation Services (RIS) and Dataless Management Services
   (DMS) installations of patches are not supported. However, the patch
   kit installation mechanism does support network installation via NFS.
   
3.4    Direct setld Installation and Removal of Patch Subsets Is Not Allowed

   Manually installed patches are installable only using their
   installation script. Using setld or dupatch will not work.
   
3.5    Limitation for /var/adm/manual_patch/backup Directory Handling

   The patch management utility assumes there is one
   /var/adm/manual_patch/backup directory per system. It does not handle
   placement of archived original files for multiple systems in one
   directory.
   
3.6    No Ctrl/c During Installation Phase

   Do not enter a Ctrl/c command during the installation phase of the
   patch kit.
   
                                  Caution
                                      
     As with any system update, entering a Ctrl/c during this phase may
     leave the operating system software environment in an inconsistent
     and nonrecoverable state.
     
3.7    Manually Installed patches can not be deleted

   There is no supported way to de-install Patches that were "Manually
   Installed".
   
   
3.8    Release Patches Do Not Automatically Supersede CSPs

   Currently, release patches cannot automatically supersede manually
   installed customer-specific patches (CSPs). Any release patch that
   delivers a file, previously delivered by a CSP will have it's
   installation blocked and will result in a dupatch message and require
   baselining.
     _________________________________________________________________


     _________________________________________________________________
   
                     4    Patch Installation Instructions
                                       
   This chapter provides instructions for installing manually installed
   patches on the Tru64 UNIX operating system and the TruCluster Software
   Products (TCR).
   
4.1    Summary of Steps for Using Patch Kits

   The following list summarizes the steps necessary to install patches
   on your system. The referenced sections provide the full details.
   Compaq recommends that you familiarize yourself with these steps
   before attempting to install Tru64 UNIX or TCR patch kits.
   Prepare your system for patch installation ([1]Section 4.2).
       Make the patch distribution available to your system ([2]Section
       4.3).
       Install patches mode ([3]Section 4.4).
       Rebuild the kernel and reboot the system ([4]Section 4.5).
       
4.2    Preparing to Install Patches

   Before using the latest Tru64 UNIX or TCR patch distribution, make
   sure that your system meets the required criteria and that you perform
   certain preinstallation tasks, as described in the following list:
   Make sure you have the correct software. See System administrators
       documentation for details.
       You must have the appropriate versions of Tru64 UNIX and TCR
       installed on your system to install patch kits. There are separate
       patch kits for each version of the Tru64 UNIX and TCR products.
       The patch kits will not install on any other version of those
       products. For example, the DIGITAL UNIX 4.0D patch kit will only
       install on DIGITAL UNIX Version 4.0D.
       Back up your system
       It is recommended that you backup your /, /usr, and /var file
       systems prior to installing patches or baselining your system.
       Make sure you have enough storage space
       Refer to the Patch Summary and Release Notes for the required
       storage space.
       
4.3    Making the Patch Distribution Available

   Tru64 UNIX and TCR manually installed patches are available from your
   Compaq service provider. Once you have obtained the patch
   distributions use the following instructions to make the patch kits
   available to the system targeted for update:
   Ensure the installation prerequisites described in [5]Section 4.2 are
       met.
       Expand the tar file to access the patch kits.
       The tar file can be expanded on any NFS mountable file system. It
       is recommended that the file system not exist in /usr or /var of
       the system that will be patched. For example:
       #/usr/sbin/mount /dev/rz3g /PatchKits
       #cd /PatchKits
       #mkdir kit8
       Copy or ftp the patch kit to /PatchKits/kit8. For example:
       #cp T64V511-C0000100-4584-Manual-20010117.tar /PatchKits/kit8
       #script untar.log
       #tar -xpvf T64V511-C0000100-4584-Manual-20010117.tar
       #^D
       View the untar.log for errors or failures untarring the file.
       Once the tar file has been expanded, make the file system
       containing the patch kits available to the system being patched.
       For example, on the system you are patching do the following:
       #/usr/sbin/mount /PatchKits/kit8@hostname /mnt
       
4.4    Installing Patches

   Patch installation is performed on a patch by patch basis using
   installation scripts. Manually installed patches can not be installed
   using dupatch or setld.
   
   Before beginning the installation, make sure that you have completed
   all of the preliminary steps:
   Make sure you have met the installation prerequisites described in
       [6]Section 4.2.
       Make sure you made the patch distribution available to your
       system, as described in [7]Section 4.3.
       
   The following sections provide step-by-step instructions for
   installing and enabling patches.
   
  4.4.1    Choosing Single-User or Multiuser Mode
  
   You can install patches from either single-user or multiuser modes.
   See [8]Section 3.1 for information about selecting one of these modes.
   
   
  4.4.2    Choosing which patch to install.
  
   Now you need to choose which patch to install. Read the documents that
   came with the patch kit in order to determine which patches you wish
   to install.
   
   
  4.4.3    Find installation script
  
   Now look at the the untared hiearchy of the patch kit in
   patch_kit/$ProductName/ManualKit/ for files called *.install.sh. For
   example:
   patch_kit/Tru64_UNIX_V5.1/ManualKit/OSFPATC0000100510.install.sh.
   
   Each one of these files is an installation script for a patch.
   
  4.4.4    Execute installation script.
  
   Just execute the installation script. For example.
   patch_kit/Tru64_UNIX_V5.1/ManualKit/OSFPATC0000100510.install.sh.
   
4.5    Rebuilding the Kernel

   The installation scripts will inform you whether a kernel rebuild and
   a system reboot are needed in order to make the patch become
   effective.
   Please refer to your system documentation for instructions on how to
   do this.
     _________________________________________________________________


     _________________________________________________________________
   
                      5    Sample Patch Kit Installation
                                       
   This chapter provides samples of using the installation scripts to do
   the following:
   Perform a typical patch kit installation ([1]Section 5.1)
       
5.1    Sample 1: Typical Patch Kit Installation

   The example in this section shows a typical patch kit installation
   performed from a psuedo-terminal on a system running in single-user
   mode.
   
# cd patch_kit
# ls -l
total 21
-rwxr-xr-x   1 root     system      4164 Jan 18 06:33 00-READ-ME-FIRST
drwxr-xr-x   6 bin      bin         8192 Jan 18 06:33 PatchInstallGuide
drwxr-xr-x   4 bin      bin         8192 Jan 18 06:33 Tru64_UNIX_V5.1
# cd Tru64_UNIX_V5.1
# ls -l
total 16
drwxr-xr-x   3 bin      bin         8192 Jan 18 06:33 Documentation
drwxr-xr-x   3 bin      bin         8192 Jan 18 06:33 ManualKit
lrwxrwxrwx   1 root     system        59 Feb 14 11:25 ReleaseNotes.txt -> Docum
entation/txt/T64V511-C0000100-4585-Manual-
20010117.txt
# cat ReleaseNotes.txt
                         Release Notes

     This document summarizes the contents and special instructions for the
     Tru64 UNIX V5.1 patches contained in this kit.


1 Release Notes


This Customer-Specific Patch Kit Distribution contains:

   - fixes which are intended to resolve the problem(s) reported in:
        o HPXQB2541
             * for Tru64 UNIX V5.1 T64V51AS0001-20001114.tar (BL1)

 WARNING! NOT FOR GENERAL USE.
          These patches are tailored for an individual system's hardware and
          software configuration. Use of this patch kit, or patches contained
          in this kit, on any other system may cause that system to be in an
          inconsistent and non-operational state.

          This patch kit, or its content, may not be posted on any network or
          bulletin boards.


 The Release Notes contain a summary of each patch in this kit.

 Patches in this kit are installed by manually typing commands or by the
 simple installation script included in the kit. For example, as root on
 the target system:

        > mkdir -p /tmp/CSPkit1
        > cd /tmp/CSPkit1
        > <copy the kit to /tmp/CSPkit1>
        > tar -xpvf DUV40D13-C0045600-1340-Manual-20000404.tar
        > cd patch_kit/DIGITAL_UNIX_V4.0D/ManualKit
        > ./OSFPATC0045600425.install.sh

 NOTE: The simple installation script provides:

        o Prior to installing anything, it verifies
                - product version matches the target product for the patch
                - affected product subsets are installed

        o Saves existing system files (so the patch can be removed)
                - in their current location with .PreManualCSP.<timestamp>
                  appended

        o Installs patched system files in the proper location with the proper
          access modes

        o Installs the patch documentation on the target system
                - copies <PatchID>.abs,
                         <PatchID>.txt,
                         <PatchID>.problem_ids,
                         <PatchID>.rcs_strings and optionally
                         <PatchID>.special_instructions

                  to /var/adm/manual_patch/doc

        o Updates the manually-installed patch installation log
                - /var/adm/manual_patch/log/Install.log

        o Updates the manually-installed patch database
               - copies <ManualPatchName>.sh,
                         <ManualPatchName>.FileList
                         <ManualPatchName>.Installed

                  to /var/adm/manual_patch/db/

        The installation script DOES not provide patch dependency management
        nor patch removal capabilities.

 These patches have been tested and found to work correctly in the support
 engineering environment. However, it is possible that you may experience
 different results running these patches in your computing environment.

 Compaq recommends that you install these patches in a NON-Production (testing)
 computing environment to ensure there are no side-effects (due to your specifi
c
 configurations) PRIOR to installing the patches in your production environment
.


2 Special Instructions

SPECIAL INSTRUCTIONS for Tru64 UNIX V5.1 Patch C1.00
Special Instructions



3 Summary of CSPatches contained in this kit


Tru64 UNIX V5.1

PatchId                 Summary Of Fix
----------------------------------------
C1.00                   Description


4 Additional information from Engineering

The following test program(s) are delivered and installed with
Patch C1.00:
        ./var/adm/patch/support/OSFPATC0000100510/passwd
The special instructions for this patch describe the use of the
test program(s)




5 Affected system files
This patch delivers the following files:

Tru64 UNIX V5.1
        Patch C1.00
                ./usr/sbin/mknod
                        CHECKSUM:       37452 20
                        SUBSET: OSFBASE510
                ./var/adm/patch/support/OSFPATC0000100510/passwd
                        CHECKSUM:       12226 3
                        SUBSET: Unknown
# cd ManualKit
# ls -l
total 48
-rwxr-xr-x   1 bin      bin         9728 Jan 18 06:33 OSFPATC0000100510.install
.sh
-rw-r--r--   1 bin      bin        30720 Jan 18 06:33 OSFPATC0000100510.tar
drwxr-xr-x   2 bin      bin         8192 Jan 18 06:33 RCSIdInformation

# ./OSFPATC0000100510.install.sh
Now installing Tru64 UNIX V5.1 Patch C1.00 at  (Logging to //./var/adm/manual_p
atch/log/OSFPATC0000100510)

File ./var/adm/patch/support/OSFPATC0000100510/passwd isn't on the system - pro
bably since it is a new file

Finished installing Tru64 UNIX V5.1 Patch C1.00 at 2001-02-11-12:35:56
     _________________________________________________________________


     _________________________________________________________________
   
            6    Common Error, Warning, and Informational Messages
                                       
   This chapter describes error, warning, and informational messages for
   the "Manually Installed" installation scripts. The following
   information is provided for each message:
   
   Source: The function that generates the message.
   
   Problem: A brief description of possible causes for the message.
   
   Causes: A summary of situations that cause the message.
   
   Action: General recovery guidance.
   
   Output: A sample of the message.
   
6.1    Patch Installation Messages

   The following sections describe messages you might see when running
   the dupatch preinstallation check or installation functions.
   
  6.1.1    Patch Installation must be executed as root.
  
   Source: Preinstallation check or installation.
   
   Problem: The installation script is being run from a non-root account.
   
   Cause: The installation script is being run from a non-root account.
   
   Action: Change to the root account and re-execute the installation
   script..
   
   Output:
   
   Script must be executed as root
   
   This error will prevent the installation of the patch.
   
  6.1.2    Patch Installation is installing a new file
  
   Source: Preinstallation check or installation.
   
   Problem: A patch is delivering a file that was not present on the
   system previously.
   
   Causes: Generally this situation occurs when a the patch is delivering
   a new file, or a specialized script.
   
   Action: Nothing.
   
   Output:
   
   File ./var/adm/patch/support/OSFPATC0000100510/passwd isn't on the
   system - probably since it is a new file
   
   
  6.1.3    Patch Installation tried to save the file twice
  
   Source:Preinstallation check or installation.
   
   Problem: While backing up a patched file, the installation realized
   that it had backed up the same file as part of an installation of the
   same patch previously.
   
   Causes: Somebody has tried to fiddle with the files indicating what
   "manually installed" patches are on the system.
   
   Action: To resolve this situation contact the Product Customer
   Services representative.
   
   Output:
   
   Already have saved file name
   /var/adm/patch/support/OSFPATC0000100510/passwd.PreManualCSP.2001-02-1
   1-15:02:36
   
   This error will prevent the installation of the patch.
   
  6.1.4    Patch Installation Can't find document in kit
  
   Source:Preinstallation check or installation.
   
   Problem: The installation script can't find part of the associated
   documentation.
   
   Causes: Tar file was damaged.
   
   Action: Download and unpack tar file again. Then re-run installation
   script.
   .
   Output:
   
   Can't find document ./../Documentation/txt/OSFPATC0000100510.txt
   
   or
   
   Can't find release notes
   ./../Documentation/txt/T64V511-C0000100-4584-Manual-20010117.txt
   
   
  6.1.5    Patch Installation requires kernel rebuild and reboot.
  
   Source:Preinstallation check or installation.
   
   Problem: The patch installed requires a kernel rebuild and reboot in
   order to take effect.
   
   Causes: The patch installed requires a kernel rebuild and reboot in
   order to take effect.
   
   Action: Rebuild the kernel, and reboot the system.
   
   Output:
   
   Please note that you need to re-build the kernel and reboot
   so that this patch will take effect.
   
  6.1.6    Patch Installation Blocked by non-installed subsets
  
   Source:Preinstallation check or installation.
   
   Problem: The patch can not be installed because a required software
   subset is missing from your system.
   
   Causes: This patch replaces patches that were originally installed in
   certain subsets. Since these subsets are not installed on this system,
   installing the patch could corrupt your system and is therefore
   blocked.
   
   Action: Re-evaluate whether or not you need this patch. If you do,
   install the apropriate softwrae subsets.
   
   Output:
   
   This patch contains files originally shipped in the following
   subset(s)
   
   Atom Program Analysis Tools         (Subset ATMBASE500)
   Subset ZZZTOOLS001
   
   However, these subset(s) are not installed on your system, therefore
   this patch
   will not be installed
   
  6.1.7    Patch Installation Blocked by product version check
  
   Source:Preinstallation check or installation.
   
   Problem: The patch can not be installed, since there are no subsets of
   this product version installed on the system.
   
   Causes: This patch shouldn't be installed on the system.
   
   Action: Make sure that you are on the correct system.
   
   Output:
   
   No subsets of this product (USF 510) are installed on this system
   
  6.1.8    Patch Installation Blocked by name sanity check
  
   Source:Preinstallation check or installation.
   
   Problem: The patch can not be installed, since the installation script
   failed a sanity check.
   
   Causes: Somebody has renamed the patch installation script.
   
   Action: Start over from the original tar file delivered to you by your
   service provider.
   
   Output:
   
   The base name of the file OSFPATC0000100510 has changed from it's
   original                      (USFPATC0000100510)
   
  6.1.9    Patch was already installed
  
   Source:Preinstallation check or installation.
   
   Problem: The patch can not be installed, since it was previously
   installed.
   
   Causes: Patch was previously installed.
   
   Action: Nothing.
   
   Output:
   
   Patch is already installed.
   
  6.1.10    Patch installation can not be logged
  
   Source:Preinstallation check or installation.
   
   Problem: The patch can not be installed, since the logging mechanism
   isn't working.
   
   Causes: Internal error.
   
   Action: Contact your Compaq service provider.
   
   Output:
   
   Can't log installation.
   
  6.1.11    Patch installation can not find tar file
  
   Source:Preinstallation check or installation.
   
   Problem: The patch can not be installed, since the tar file with the
   patched files is missing.
   
   Causes: Somebody messed with the contents of the kit.
   
   Action: Nothing.
   
   Output:
   
   Can't find tar file OSFPATC0000100510.tar
     _________________________________________________________________

     _________________________________________________________________
   
                                   Glossary
                                       
   baselining
          
          A [1]dupatch feature that looks at the files installed on a
          system, compares them to the files it expects to find, and
          prevents the installation of any patch files that might cause
          an incompatibility among system files.
          
   customer-specific patch
          
          Any patch that is developed and made available to resolve a
          problem for a specific customer. A customer-specific patch is
          developed with prior knowledge of that customer's unique
          hardware and software configuration and environment.
          
          Also referred to as test patches and prerelease patches,
          customer-specific patches may not be useful for another
          customer's system.
          
   dupatch
          
          A utility included in a patch kit that installs, removes, and
          manages patches for Tru64 UNIX and TruCluster Software
          Products. This utility is installed and left on the system
          through the successful installation of a patch kit.
          
   full installation
          
          A Tru64 UNIX installation that creates new file systems and
          loads a full copy of the operating system from the kit onto a
          system. Any other version of the operating system, any layered
          products, and any patches that previously existed on the system
          are overwritten. A full installation does not preserve system
          customizations (for example, user or data files) because the
          root (/), /usr, and /var file systems are re-created during the
          process.
          
          See also [2]update installation
          
   HTML file
          
          The coding inserted in a file intended for display on a World
          Wide Web browser that tells the browser how to display a Web
          page's words and other elements. The markup is done with tags,
          which are command words enclosed in angle brackets. For
          example, the tag <p> creates a new paragraph. HTML (hypertext
          markup language) files are text (ASCII) files. The
          documentation provided with the Tru64 UNIX patch kits is
          provided in HTML files for viewing on a Web browser.
          
          See also [3]PDF file
          
   manually installed patch
          
          A manually installed patch is a patch kit that is not packaged
          as a [4]dupatch based kit. It has a minimal amount of
          management functionality associated with it - just enough to
          track the patch on the system. Typically a customer will never
          see this type of packaging.
          
   patch
          
          A file or a collection of files that contain fixes to problems.
          When possible, patches are merged together into one patch if
          they have intersecting files or codependencies. A patch may
          correct one or more problems.
          
          Each patch is packaged in its own [5]setld subset. The subsets
          are managed by a utility named [6]dupatch.
          
   patch applicability
          
          A file-by-file check of system files to determine whether a
          patch might cause a a system to be degraded or crash. The
          installation of a patch is blocked if any system files to be
          replace by that patch are not valid predecessors of the patch
          files.
          
   PDF file
          
          A file type recognized by the Adobe Acrobat Reader, which
          provides an easy way to view and print documentation. As the
          next generation of Adobe's PostScript format, PDF files have
          become a standard way of distributing documentation, especially
          on CD-ROM and over the Internet. The Tru64 UNIX patch
          documentation is provided in PDF and HTML formats. The Acrobat
          Reader is provided on the Tru64 UNIX Documentation CD-ROM of
          Version 4.0E and higher. It is also available at the Adobe Web
          site, [7]http://www.adobe.com/
          
          See also [8]HTML file
          
   released patch
          
          Any patch that is included in a Tru64 UNIX patch kit. Also
          called official patches, released patches are intended for
          worldwide distribution and can be safely used on any customer's
          system within the guidelines documented in the patch kit.
          
   rolling upgrade
          
          A software upgrade of a cluster that is performed while the
          cluster is in operation. One member at a time is rolled and
          returned to operation while the cluster transparently maintains
          a mixed-version environment for the base operating system,
          cluster, and Worldwide Language Support (WSL) software. Clients
          accessing services are not aware that a rolling upgrade is in
          progress.
          
          A rolling patch uses the same procedure as rolling in a new
          release of the base operating system and cluster software. The
          only difference is whether you run installupdate, dupatch, or
          both during the installation stage.
          
   setld
          
          An interactive program for installing and managing software
          subsets. Software products are organized into subsets that can
          be loaded, deleted, inventoried, and configured. The load
          operation reads software from disk, tape, CD-ROM, or an
          Internet installation server. The patch installation tool,
          [9]dupatch, is based on the setld program.
          
   tar file
          
          A file created with the tar command that saves and restores
          multiple files in a single file. Tru64 UNIX patch kits are
          provided as tar files (except for kits included on the Tru64
          UNIX CD-ROM).
          
   update installation
          
          A type of installation that preserves disk partitions, file
          systems, file customizations, the network, print, and mail
          environments, user accounts, user created files, and any other
          system setup you may have done. If software patches had been
          applied to the operating system, it would not be necessary to
          remove the patches before beginning the update process, which
          is designed to update and reinstall any software fixes or
          features that were supplied in release patches.
          
          See also [10]full installation
     _________________________________________________________________

