HP Tru64 UNIX Version 5.1B-2 and Higher Patch Kit Installation Instructions (March 2009)

4. 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
5. 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.
Rebuilding the Kernel
The dupatch utility determines whether the installation or removal of patches requires that the
kernel be rebuilt. This action is performed automatically or manually, depending upon the
method you used to install the patches:
• When using the menu-based interface, you will be prompted for actions to take. Those
prompts are the same ones you would see if you ran the doconfig command. The dupatch
utility asks if your system has a custom configuration file and if you want to change it.
• When using dupatch from the command line, the kernel is built automatically. It does this
by calling the doconfig -a command. If you specify the dupatch -cfgfile command,
dupatch calls doconfig with the -a-c options.
After the patch kit is installed you will see output similar to the following:
Configuring "Patch: SP04 OSFADVFSBIN540" (OSFPAT02500300540)
Configuring "Patch: SP04 OSFADVFS540 (SSRT2275)" (OSFPAT02500200540)
Beginning kernel build...
Do you have a pre-existing configuration file?:
If you answer yes, dupatch will build the kernel noninteractively, enabling all (mandatory and
optional) kernel options automatically. This procedure is similar to running the doconfig -a
command.
Rebuilding the Kernel 37