Common Installation Steps

The following steps provide instructions for continuing the installation of Tru64 UNIX and TruCluster software patches after you have selected either single-user or multi-user mode.

Specify whether or not you accept the license agreement. You can read the license on screen or you can read the license before beginning the installation process in the Patch Summary and Release Notes that comes with the patch kit. In the following output, the license is removed to save space:

Tru64 Unix License Agreement
** ... **

To read the license again, type 'license'.
Do you accept the license agreement? (y/n) : y

Checking patch kit for transmission errors during download...

Finished Checking patch kit checksums

You have the option to make patches reversible so you can return the system to its state prior to the installation of a patch. Enter y or press Return to make the patches reversible. For example:
Do you want the patches to be reversible? [y]:
By default, backup copies of the installed patches are saved in /var/adm/patch/backup. If you have limited space in /var, you may want to make the backup directory the mount point for a separate disk partition, an NFS-mounted directory, or a symbolic link to another file system.
If you answer no to this question, the existing system files will not be saved and the installed patches will not be reversible. HP recommends that you install patches so they are reversible.
The program describes your backup setup and asks you if you want to proceed:
Do you want to proceed with the installation with this setup? [y]:
You are asked to record your name as the person installing the patches and to add any comments you would like stored for future reference. For example:
Your name: Joe C.
Enter any notes about this operation that you would like stored for future reference. To end your input, enter a period (.) and press Return.
: Installing Patch Kit 5 : . Return
The next action depends on the type of kit you are installing:
- Inclusive patch kit
  With this type of kit dupatch peforms a preinstallation check and begins to install the patches if it finds no problems. For example:
  Checking patch prerequisites and patch file applicability... (depending upon the number of patches you select, this may take awhile). *** Installing 78 patches ***
  If any patches fail the preinstallation check, do one of the following:
  If the failure is the result of a file conflict, you will need to run the patch baseline process, as described in “Creating a Baseline”.
  If the failure is caused by an installed CSP that is not included in the current patch kit, you will have to remove the CSP, install the patch kit, and reinstall the CSP. See “Patch Installation Blocked by an Existing CSP” for more information.
- Customer-Specific patch kit
  With this type of kit you must install all patches. You can, however, remove individual CSPs after the installation process is completed and the system has been rebooted.