Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
 Contact HP
HP.com home
HP Tru64 UNIX Version 5.1B-2 and Higher: Patch Kit Installation Instructions > Chapter 1 Patch Process Overview

General Issues and Restrictions


Table of Contents
Content starts here

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.

When Single-User Mode Is Recommended

Although you can install patches in multi-user 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 multi-user 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 multi-user mode. Patch removals can only be done in single-user mode.

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.

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:

  1. Install and configure the Tru64 UNIX operating system.

  2. 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.

  3. Patch the system.

  4. 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.

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.

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.

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.

Do Not Enter Ctrl/c During Installation Phase

Do not enter a Ctrl/c command during the installation phase of the patch kit.


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.

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:


        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. 

        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

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 “Patch Installation Blocked by Installed Patch or Subset ” 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. The Patch Summary and Release Notes document included with Version 5.1B-2 and higher includes a list of CSPs that were reconciled in the patch kit.

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.

Some Patch Kits Cannot Be Removed

You cannot remove a patch kit on systems that have New Hardware Delivery 7 (NHD-7) kit installed when either of the following conditions exist:

  • The patch kit you want to remove was installed before the NHD kit.

    For example, if you installed Patch Kit 2 and then installed NHD-7, you cannot remove that patch kit. However, if you later installed Patch Kit 4, you can remove that patch kit.

  • The patch kit was installed with NHD-7.

    Beginning with the release of Patch Kit 3, patch kits were incorporated into the NHD-7 kits. As a result, when you installed NHD-7, you automatically installed the current patch kit. These patch kits cannot be removed. However, you can remove any subsequent patch kits. For example, if you installed NHD-7 with Patch Kit 4 and later installed Patch Kit 5, you cannot remove Patch Kit 4, but can remove Patch Kit 5.

If you must remove the patch kit, the only solution is to rebuild your system environment by reinstalling the Version 5.1B operating system and then restoring your system to its state before you installed NHD-7 with the unwanted patch kit.

Do Not Install Prior NHD Kits on a Patched System

Do not install the NHD–5 or NHD–6 kits on your TruCluster system if you have installed this patch kit or earlier patch kits. Doing so may cause an incorrect system configuration. The installation code for these new hardware delivery kits does not correctly preserve some cluster subset files.

Changes to System May Need to Be Reversed

If you made the following changes to your system after installing this patch kit, you will have to undo those changes before you can uninstall it:

  • If you changed your hardware configuration (for example, by adding a new disk), the system configuration that existed prior to installing this patch kit might not recognize the new devices or may not provide the necessary support for them.

  • If you added new cluster members, the new members will not have an older state to revert to if you attempt to uninstall this patch kit.

To uninstall this kit, do the following:

  1. Remove all new hardware and new cluster members that you added after installing this kit.

  2. Run dupatch to uninstall the patch kit.

  3. Verify that the patch kit was successfully uninstalled.

You can now add the cluster members you removed and reinstall the hardware you removed, as long as the support for it existed in the pre-patched system. You can also reinstall the patch kit.

Script Required When Returning to Pre-Patched System

If removing this patch kit restores your system to a pre-patched state, you must run the script /etc/dn_fix_dat.sh before rebooting your system during the patch-deletion process.

This situation would occur if Version 5.1B-4 is the only Tru64 UNIX patch kit installed on your 5.1B system.


Because the no-roll procedure automatically reboots the system after deleting the patches, you cannot use this method to delete this patch kit if doing so returns your system to a pre-patched state.

Failing to run this script will result in your system being unable to boot normally. If this occurs, do the following:

  1. Boot your system in single-user mode:

     >>> boot -fl s 
  2. Run the script:

    # /etc/dn_fix_dat.sh
  3. Reboot normally.

If you also need to reverse the version switch as described in “Version Switches”, run the /etc/dn_fix_dat.sh script after step 5 in that process.


If during the dupatch installation and deletion processes you see a Special Instruction about running this script, you should ignore that instruction unless your system meets the requirement described here.

Printable version
Privacy statement Using this site means you accept its terms
2006 Hewlett-Packard Development Company, L.P.