 |
» |
|
|
 |
To minimize system down
time, you can perform the preinstallation check on a system running
in multi-user mode, even if you will perform the actual installation
in single-user mode. The example in this section shows a preinstallation
check that results in a patch that fails the check and is prevented
from being installed. If this occurs, you would set the system patch
baseline, as described in “Creating a Baseline”. If patches
are prevented from being installed because dependent patches were
not selected, choose the select patches again item
and add the required patches that are missing. If no patches are blocked, you can proceed to the
installation phase, as described in Chapter 3 “Patch Installation and Removal Instructions”. Note that the menu you see will differ slightly, depending
upon whether you log in from a pseudo-terminal or a system console.
The following steps assume you logged in from a pseudo-terminal. Log in as root. From the main dupatch menu, enter 1 at the Enter your choice prompt: Tru64 UNIX Patch Utility (Rev. 48-00)
==========================
- This dupatch session is logged in /var/adm/patch/log/session.log
Main Menu:
---------
1) Patch Kit Installation
2) Patch Kit Deletion
3) Patch Kit Documentation
4) Patch Tracking
5) Patch Baseline Analysis/Adjustment
h) Help on Command Line Interface
q) Quit
Enter your choice: 1 |
The program responds with
the Patch Installation Menu. Enter 1 at the Enter your choice prompt: Patch Installation Menu:
------------------------
1) Pre-Installation Check ONLY
2) Check & Install in single-user mode w/ network services
3) Check and Install in Multi-User mode
b) Back to Main Menu
q) Quit
Enter your choice: 1
Enter path to the top of the patch distribution,
or enter "q" to get back to the menu : ./patch_kit
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
Gathering patch information...
(depending upon the size of the patch kit, this may take awhile)
*** Start of Special Instructions ***
⋮
*** End of Special Instructions ***
Press RETURN to proceed... |
You have the option to make
the patches reversible so you can revert the system to its state prior
to the installation of a patch. The dupatch utility
lists the following information. Press Return at the prompt to make
the patches reversible. This is the recommended action.  |
------------------------------------------------------------------------
To Make Patches Reversible - PLEASE READ THE FOLLOWING INFORMATION:
- You have the option to make the patches reversible so you can
revert the system to its state prior to the installation of a patch.
- Reversibility is achieved by compressing and saving a copy of the
files being replaced by the patches. These files would be restored
to the system if you choose to delete a patch.
- If you choose to make patches NON-reversible, then the system cannot
be restored to the state prior to the installation of a patch; you
will not be able to delete the patches later.
- This patch kit may force a small set of patches to be reversible to
ensure your upgrades to future versions of Tru64 UNIX are successful.
The Patch Utility will make those patches reversible automatically.
Refer to the Release Notes / Installation Instructions provided with
this patch kit.
Do you want the patches to be reversible? [y]: y
By default, the backup copies of the installed patches will be 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.
You must ensure the backup directory is configured the same way during
any patch removal operations.
Your current setup of "/var/adm/patch/backup" is:
* A plain directory (not a mount point or a symbolic link) |
 |
By default,
the backup copies of the installed patches will be 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. Answer yes when asked if you want to perform the preinstallation check with
this setup: Do you want to proceed with the pre-installation check with this setup? [y]: y |
Enter your name and any
information that you want to appear in the preinstallation check log: Your name: Betty
Enter any notes about this operation that you would like stored for
future reference (To end your input, enter a "."):
: preinstall check for patch kit 5
: .
|
The program lists any patches
that fail the prerequisite and applicability checks, and asks how
you want to proceed. You have the following choices:  |
Checking patch prerequisites and patch file applicability...
(depending upon the number of patches you select, this may take awhile)
*** The Patch Kit will install 80 patches ***
-------------------------------------------------------------------------
Problem installing:
- Tru64_UNIX_V5.1B / Kernel Patches:
Patch 26009.00 - SP05 OSFBASE540 (SSRT3631 SSRT3469 SSRT2439 ...)
./usr/sbin/cron:
is installed by Customer Specific Patch (CSP):
- Tru64_UNIX_V5.1B:
Patch C 00981.00
and can not be replaced by this patch. To install this patch,
ideally, you must first remove the CSP using dupatch.
Before performing this action, you should contact your
HP Service Representative to determine if this patch kit
contains the CSP. If it does not, you may need to obtain a new
CSP from HP in order to install the patch kit and retain the
CSP fix.
or
you may use dupatch baselining to enable the patch installation.
This patch will not be installed.
-------------------------------------------------------------------------
* The following 1 patch(es) failed in prerequisite/file applicability check:
- Tru64_UNIX_V5.1B / Kernel Patches:
Patch 26009.00 - SP05 OSFBASE540 (SSRT3631 SSRT3469 SSRT2439 ...)
* There were 1 patch(es) which failed in prerequisite/file applicability check:
Press Return to go back to the previous menu
|
 |
|