This chapter describes information you need to be aware of before you
install a patch kit.
It also describes the steps to take for tasks such as
performing a preinstallation check and a baselining operation.
2.1 Preinstallation Tasks
Before using the latest Tru64 UNIX and TruCluster software 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
You must have the appropriate versions of Tru64 UNIX and TruCluster software installed on your system to install patch kits. There are separate patch kits for each version of the Tru64 UNIX and TruCluster software products. The patch kits will not install on any other version of those products. For example, a Tru64 UNIX 5.1B patch kit will only install on Tru64 UNIX Version 5.1B.
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.
2.2 Making the Patch Distribution Available
The following list describes the steps to make the patches available for installation:
Ensure the installation prerequisites described in Section 2.1 are met.
If you are using patch tar files obtained via the Internet from HP (see Patch Process Resources), you must expand the tar file to access the patch kits. The tar file can be expanded on any mountable file system. For example:
# /usr/sbin/mount /dev/disk/dsk3g /patches # cd /patches # mkdir pk4
Note
If you are installing successive patch kits, place and untar each kit in a separate directory.
Copy or ftp the patch kit to
/patches/pk4
.
For example:
# cp T64V51B18AS0003-20011020.tar /patches/pk4
Untar the patch kit, capturing the process to a log file. For example:
# script untar.log # tar -xpvf /patches/pk4/T64V51B18AS0003-20011020.tar # [Ctrl/d]
View the
untar.log
for errors or failures
untarring the file.
After you have made the patch kits available to the system being patched,
run
dupatch
; for example:
# /patches/pk4/patch_kit/dupatch
You can also change directories to the
patch_kit
directory:
# cd /patches/pk4/patch_kit # ./dupatch
If new patch tools are available they will be loaded and you will see messages similar to the following:
* A new version of patch tools required for patch management is now being installed on your system. * Tools updated, invoking the updated Patch Utility...
The
dupatch
utility saves information on the tools
that have been loaded to the log file
/var/adm/patch/log/Dupatch_load_date.log
.
(See
Appendix A
for information
about log files.)
Note
It is important that you run the
dupatch
utility located in the/patch_kit
directory every time you obtain new patch tar files or a new Tru64 UNIX Patch CD-ROM in order to update the patch tools. See Section 2.6.4 for information you need to be aware of when installing from the command line.
After the new tools have been loaded,
dupatch
prompts
you for the path to the patch kit files.
After you specify the path (or press
Return if the patch kit is in your current directory) you will see the main
menu.
For example:
Enter path to the top of the patch distribution, or enter "q" to get back to the menu : /patches/pk4/patch_kit Tru64 UNIX Patch Utility (Rev. 46-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:
2.4 Performing Patch Preinstallation Check Instructions
To minimize system down time, you can perform the preinstallation check on a system running in multiuser mode, even if you will perform the actual installation in single-user mode.
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. 46-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 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 *** *** There are NO 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]: [Return] 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]: [Return]
For the old style kits kits, the program then lists the patches that apply to your system. When performing this operation on an inclusive patch kit, the individual patches are not displayed. Another difference between the two types of kits is that for the old style kits kits you can perform the preinstallation check on specific patches.
The patches you select during this process are only analyzed in relation
to your system; they are not installed.
The option that reads
EXIT
without installing any patches
is misleading in that no patches
are installed regardless of which option you select during the preinstallation
check.
The following output is from a preinstallation check of the old style patch kit.
The patches listed below are optional: There may be more optional patches than can be presented on a single screen. If this is the case, you can choose patches screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any patches are installed. - Tru64_UNIX_V5.0A/ Cluster Kernel Patches: 1) Patch 00090.00 - versw command can core dump during rolling upgrade 2) Patch 00186.00 - Disks can become inaccessible on a cluster node - Tru64_UNIX_V5.0A / Commands, Shells, & Utilities Patches: 3) Patch 00015.00 - Fixes a problem that occurs in multibyte local
.
.
.
96) Patch 00176.00 - Memory leaks occur when creating widgets 97) Patch 00180.00 - Fixes memory leak in libXm 98) Patch 00182.00 - libXm memory leak when creating widgets Or you may choose one of the following options: 99) ALL of the above 100) CANCEL selections and redisplay menus 101) EXIT without installing any patches Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 99
After the program lists the patches you have selected,
it asks you to confirm the selection and runs the preinstallation check if
you answer
yes
:
Is this correct? (y/n): y Checking patch prerequisites and patch file applicability... (depending upon the number of patches you select, this may take awhile) *** You have selected 98 patches *** Checking system space needed for patch installation and backup... ************************************************************** Pre-Installation Check COMPLETED with the following results: 98 patches passed Pre-Installation Check 0 patches failed Pre-Installation Check ************************************************************** Press RETURN to continue...
The program lists any patches that fail the prerequisite and applicability checks, and asks how you want to proceed. You have the following choices:
Select the action you'd like to take: 1) proceed with the patches that passed the check 2) select patches again 3) go back to the previous menu
If the patches are prevented from being installed because of missing
or unknown system files, set the system patch baseline, as described in
Section 2.5.
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.
Otherwise, proceed to the installation phase, as described in Chapter 3.
If your system was customized as a result of the manual installation of any system files, you will need to set the patch baseline for your system. If you do not need to set the patch baseline for your system, proceed to Chapter 3.
Note
You will need to be familiar with the concepts of baselining in Section 1.7 before preforming the steps in this section.
You can set the patch baseline in multiuser mode, thereby minimizing system down time.
The following steps show you how to set a patch baseline for an inclusive
patch kit.
The process is similar for the old style kits, but the
dupatch
display differs slightly.
Log in as root.
Run
dupatch
and enter
5
in response to the
Enter your choice
prompt of the Main
Menu:
Tru64 UNIX Patch Utility (Rev. 46-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: 5
Enter the location of the patch distribution:
Enter path to the top of the patch distribution, or enter "q" to get back to the menu [/patches/PK4/patch_kit]:
The old style patch kits do not provide a default location.
The summary of the patch baselining phases provides the following information:
Baselining Phase 1 evaluates your system relative to the patch kit.
Baselining Phase 2 reports information for patches whose installation
is blocked by system files that were installed by layered products.
You cannot
enable
dupatch
to install patches that replace system files
installed by layered products.
You must contact your layered product customer
services or HP Services if you have purchased Business Critical
Services.
Baselining Phase 3 reports on patches that match existing
files on your system, but are not marked as
installed
by the system inventory.
You can tell
dupatch
to mark
these patches as
installed.
This involves copying valid
setld
database information to your system.
If exact matches are
found you will be asked the following question:
Do you want to mark these patches as installed ? [y/n]
You must provide an answer; there is no default answer.
Baselining Phase 4 reports information about any unknown or missing system files. This information is provided to assist you in understanding the state of files that may prevent patch installation.
Consider this information carefully when making decisions to override patch-installation checks for patches noted in Phase 5.
Phase 5 reports patches that do not pass installation applicability tests due to the current state of your system. The installation of these patches is prevented by missing or unknown system files.
The
dupatch
utility reports the known information
about the files contained in each patch and asks if you want to enable the
installation:
Do you want to enable the installation of any of these patches? [y/n]:
Answer
n
, until you know the origin of the files
that are preventing the patch installation.
The changed system files that
are preventing the Release patch installation may be part of a manually installed
Customer-Specific patch or an intentionally customized utility or file.
If, for example, the file that is preventing the installation of a Release patch is one of many files that are part of a Customer-Specific patch, you must determine how to proceed. For more information, see Section 1.7.4.1 and Section 1.7.5.
If you answer
y
to this question, what follows depends
on whether you are installing an inclusive patch kit or an old style patch
kit:
When installing an inclusive patch kit,
dupatch
enables all of the patches to be installed.
When installing an old style patch kit kit, you are given the option to select which patches you want installed and are given the opportunity to confirm your selections.
Caution
Do not enable
dupatch
to install patches over missing or unknown system files for which you do not know the origin. To do so might leave your operating system or TruCluster software environments in an inconsistent or nonoperational state.
2.6 General Issues and Restrictions
This section provides information you must be aware of when installing
or removing 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.
2.6.1 When Single-User Mode Is Recommended
Although you can install patches in multiuser mode, we recommend 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, apply the patches when the system is as lightly loaded as possible.
There are no restrictions on performing patch selection and preinstallation
checking in multiuser mode.
Patch removals can only be done in single-user
mode.
2.6.2 Use Clean Directory for Each Patch Kit
When installing a patch kit downloaded from the Web, untar the file
in a clean directory; that is, one that does not contain files from a previous
patch kit.
A failure to do this can have adverse consequences when installing
the new kit.
2.6.3 Patching a System Prior to Creating a Cluster
Patching your system before creating your cluster can save you time, although if you do so, be aware that you cannot then remove the patch kit.
The following steps describe how to patch your system before creating a cluster:
Install and configure the Tru64 UNIX operating system.
Use the
setld
command to install the TruCluster software
kit.
If the TruCluster software kit is not loaded before the patch operation,
patches for TruCluster software will not be loaded.
Patch the system.
Use the
clu_create
command to create the
single-member cluster.
See the Tru64 UNIX
Installation Guide
for information
about installing the operating system and the TruCluster
Cluster Installation
manual for information about creating your cluster.
2.6.4 Restriction on Loading New dupatch Tools from the Command Line
The new patch tools cannot be loaded using the
delete
command on the command line.
Doing that will cause the following error to
be displayed:
product_map does not exist or is empty, Cannot continue.
If you want to use
delete
from
the command line, you can first load the new tools, without affecting the
system, by issuing the
install
command with the
-precheck_only
option.
This will load the tools and not cause changes
to your system.
2.6.5 RIS and DMS Unsupported for Patch Installation
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.
2.6.6 Direct setld Installation and Removal of Patch Subsets Is Not Allowed
You can install and remove Tru64 UNIX and TruCluster software patches
only through
dupatch
.
You cannot directly install or reinstall
the patch subsets with
setld
.
This ensures that patch tracking
and management are not compromised.
2.6.7 Limitation for /var/adm/patch/backup Directory Handling
The patch
management utility assumes there is one
/var/adm/patch/backup
directory per system.
It does not handle placement of archived original files
for multiple systems in one directory.
2.6.8 Do Not Enter 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 could leave the operating system software environment in an inconsistent and nonrecoverable state.
2.6.9 Removing Patches Containing Customized Files
If you
use
dupatch
to remove a patch containing a customized file,
messages similar to the following may appear in the session log file,
/var/adm/patch/log/session.log
:
- Tru64_UNIX_V5.1B / Network Patches: Patch 25020.00 - SP04 OSFCLINET540 (SSRT3653 SSRT2384 SSRT2275 ...) Customization found in ./etc/inetd.conf. Before the backup was restored, we had saved a copy of this file in: ./etc/inetd.conf.PreDel_OSFPAT02502000540 Please compare ./etc/inetd.conf with this saved copy. If there are extra customizations you want to keep, you would need to merge them into ./etc/inetd.conf manually. ./etc/inetd.conf.PreDel_OSFPAT02502000540 can be removed afterwards.
This message warns you to examine the removed patch for any customized
files it may contain, which in this example is the file
/etc/inetd.conf
.
In order to keep those customizations, you will have to manually
add them.
The following are examples of such customized files:
/usr/var/spool/cron/crontabs/root
/etc/sysconfigtab
/usr/var/adm/sendmail/sendmail.cf
2.6.10 Release Patches Do Not Automatically Supersede CSPs
Release patches do not automatically supersede
dupatch
-based Customer-Specific patches (CSPs).
Any Release patch
blocked by a CSP will result in a
dupatch
message.
See
Section B.1.7
for more information.
See the release notes
of the new style patch kits for a list of CSPs that are included in those
patch kits.
2.6.11 Impact on System Upgrades to Later Versions of Tru64 UNIX
In the presence of patches of layered products, certain procedures used to upgrade a system to a later version of Tru64 UNIX can lead to inconsistencies among operating system and layered product objects.
Note
After successfully installing a new version of Tru64 UNIX, you should obtain and install the latest patch kit that is applicable to that version of Tru64 UNIX.