1    Release Notes

This chapter provides information that you must be aware of when working with DIGITAL UNIX 3.2G, TCR 1.5, and ASE 1.0 Patch Kit-0005.

1.1    Required Storage Space

The following storage space is required to successfully install this patch kit:

Available Server Environment

• Temporary Storage Space

  A total of ~250 MB of storage space is required to untar this patch kit. It is recommended that this kit not be placed in the /, /usr, or /var file systems because this may unduly constrain the available storage space for the patching activity.

• Permanent Storage Space

  Up to ~34.4 MB of storage space in /var/adm/patch/backup may be required for archived original files if you choose to install and revert all patches. See the Patch Kit Installation Instructions for more information.

  Up to ~35.0 MB of storage space in /var/adm/patch may be required for original files if you choose to install and revert all patches. See Patch Kit Installation Instructions for more information.

  Up to ~502 KB of storage space is required in /var/adm/patch/doc for patch abstract and README documentation.

  A total of ~120 KB of storage space is needed in /usr/sbin/dupatch for the patch management utility.

Base Operating System

• Temporary Storage Space

  A total of ~250 MB of storage space is required to untar this patch kit. It is recommended that this kit not be placed in the /, /usr, or /var file systems because this may unduly constrain the available storage space for the patching activity.

• Permanent Storage Space

  Up to ~30.0 MB of storage space in /var/adm/patch/backup may be required for archived original files if you choose to install and revert all patches. See the Patch Kit Installation Instructions for more information.

  Up to ~30.4 MB of storage space in /var/adm/patch may be required for original files if you choose to install and revert all patches. See Patch Kit Installation Instructions for more information.

  Up to ~469 KB of storage space is required in /var/adm/patch/doc for patch abstract and README documentation.

  A total of ~105 KB of storage space is needed in /usr/sbin/dupatch for the patch management utility.

TruCluster Software products

• Temporary Storage Space

  A total of ~250 MB of storage space is required to untar this patch kit. It is recommended that this kit not be placed in the /, /usr, or /var file systems because this may unduly constrain the available storage space for the patching activity.

• Permanent Storage Space

  Up to ~35.0 MB of storage space in /var/adm/patch/backup may be required for archived original files if you choose to install and revert all patches. See the Patch Kit Installation Instructions for more information.

  Up to ~36.0 MB of storage space in /var/adm/patch may be required for original files if you choose to install and revert all patches. See the Patch Kit Installation Instructionsfor more information.

  Up to ~503 KB of storage space is required in /var/adm/patch/doc for patch abstract and README documentation.

  A total of ~120 KB of storage space is needed in /usr/sbin/dupatch for the patch management utility.

1.2    New dupatch Features

The following sections describe new features of dupatch.

1.2.1    Dupatch-based Patch Kits for ASE and TCR Patches

Patches for ASE and TCR are now installed, removed, and managed through dupatch. The ASE and TCR patch kits have been converted to dupatch-based patch kits and distributed in the same patch distribution as the applicable operating system.

The multi-product support within dupatch is most visible when installing or removing patches. dupatch will display a list of the products which are on the system and in the patch kit, allowing the user to select one or more products before proceeding with patch selections.

You must load the new patch tools provided in this patch kit. See the Patch Kit Installation Instructions for more information.

Since all prior ASE and TCR patches have been installed manually, you must set the system patch baseline. See the Patch Kit Installation Instructions for detailed information.

1.2.2    New Cross-Product Patch Dependency Management

The dupatch utility now manages patch dependencies across the DIGITAL UNIX operating system, ASE, and TCR patch kits. An example of patch cross-product dependency handling for a system with both DIGITAL UNIX 3.2G and TCR 1.0 installed follows:

• If a DIGITAL UNIX 3.2G Patch 1.00 is chosen for installation and it depends upon TruCluster 1.0 Patch 17.00 which is not already installed or chosen for installation, the dupatch installation precheck will warn you of the dependency and block the installation of the DIGITAL UNIX 3.2G Patch 1.00.

  If the patch selections are reversed, dupatch will still warn you and block installation of the chosen patch.

1.2.3    Patch Special Instruction Handling by dupatch

The format and content of the per-patch special instructions has been revised to make it easier to use. The special instructions are now displayed when patches are removed. The per-patch special instructions are viewable through the dupatch documentation menu.

1.2.4    Patch Tracking and Documentation Viewing

The patch tracking and documentation viewing features within dupatch can now be used in multi-user mode by non-root users. See the Patch Kit Installation Instructions for more information.

From the dupatch patch tracking menu you can now list the patch kits from which patches installed on your system originated.

1.2.5    System Patch Baselining

The system patch baselining feature of dupatch has been improved. Phase 4 now reports all missing or unknown system files regardless of their applicability to the patch kit. This will help you identify the origin of manually changed system files. See the Patch Kit Installation Instructions for more information.

1.2.5.1    Known Problem with Patch Baseline Analysis/Adjustment

There is a known problem when running Patch Baseline Analysis/Adjustment, selection 5, from the dupatch main menu.

This will not block the installation of any patches.

The following is a section from the Patch Baseline Analysis/Adjustment output showing missing hardlink to and files. This output should be ignored.

Phase 4 - Report changed system files and missing files
=======================================================
 
    This phase provides information to help you make choices later in
    this process.  It reports both 'missing' and files whose origin
    cannot be determined.  Some of these files may affect patch
    installation.  You will want to consider this information when you
    later make decisions in phase 5.
 
    * list of changed files with unknown origin:
      ------------------------------------------
 
  ./sbin/pax     OSFBASE375            UNKNOWN
      MISSING HARDLINK TO ./sbin/cpio.new
  ./sbin/sh      OSFPAT00042200375     UNKNOWN
      BROKEN HARDLINK TO ./sbin/Rsh
  ./sbin/Rsh     OSFPAT00042200375     UNKNOWN
      BROKEN HARDLINK TO ./sbin/sh
  ./sbin/tar     OSFBASE375            UNKNOWN
      MISSING HARDLINK TO ./sbin/cpio.new
 
    * list of "missing" files:
      --------------------------
 
  ./isl/sas/.profile                OSFBASE350      MISSING
  ./isl/sifsync                     OSFBASE350      MISSING
  ./usr/lib/emacs/lisp/term/.el     OSFEMACS350     MISSING
 

1.2.6    New Command Line Interface Switches

The dupatch command line mode contains the following new switches:

• The -product switch must be used when you specify the -install or -delete switches when the target system has more than one installed product that is on the kit (such as DIGITAL UNIX, ASE, and TCR). This switch allows you to specify the product name which the rest of the patch operations will affect. The -product switch must precede the -patch switch on the command line. See the Patch Kit Installation Instructions for more information.

• A -nolog switch has been added to enable you to turn off session logging.

• The -version switch is no longer used for delete. Using this switch will cause an error and the help information will be displayed on the screen.

Any error on the command line will cause the help information to be displayed on the screen.

If any mandatory switch is missing when using the command line interface, the command fails with the appropriate usage message. Once you select the command line interface, dupatch will not go into interactive mode. Prompting is no longer mixed with the command line interface.

1.2.7    Compatibility Between Revisions of dupatch

The new dupatch will work with older revisions of dupatch-based patch kits.

The older revisions of dupatch, however, rev 15 and lower, do not know how to install, remove, or manage patches from the new style patch kits. Please ensure that you load the new patch installation tools when you receive this patch kit. See the Patch Kit Installation Instructions for more information.

1.3    Special Instructions for Patch 371.00

The printer log, lpr.log now reports the creation of files preceded by a dot (.) in the spooling directories. Do not amend or delete these files as the printer subsystem manages their creation and cleanup.

For initial use, DIGITAL recommends that you set the logging level to lpr.info. If you have a problem that is escalated to technical support, the support organization will request lpr.log at the lpr.debug level. This is because the DEBUG messages provide a detailed trace that can only be interpreted by reference to the source code and lpr.log will simply grow more quickly if DEBUG messages are logged. The lpr.info level provides a shorter report of an event, including any network retry messages and unusual occurences (which are not always errors).

All changes to the status file of a queue, including reports of any files printed, are reported at the DEBUG level rather than the INFO level. This reduces the rate of growth of the file and allows you to monitor and react to important events more quickly. The WARNING level logs events that may need to be attended to, while the ERROR level logs hard (often fatal) errors.

To modify the logging level, edit your /etc/syslog.conf file and change the lpr line to the required level, such as lpr.info as follows:

lpr.info /var/adm/syslog.dated

Use the ps command to find the PID for the syslog daemon, and the following command to re-start syslogd:

# kill -HUP

A new set of log files will be created in /var/adm/syslog.

1.4    Special Instructions for Patch 401.00

When you install Patch 401.00 you must enable it before NFS is started because it must perform configuration operations before client requests arrive.

To manually enable Patch 401.00, first rebuild the kernel, then issue the following commands::

% dbx -k /vmunix 
      (dbx) patch stall_write_patch_enabled=1
 (dbx) quit
% reboot

1.5    Special Instructions for Patch 386.00

Because Patch 386.00 will overwrite the system's existing cam_data.c file, you will need to perform additional steps when installing the patch. The steps you take depend upon your system configuration. This section decribes the steps you must take.

Patch 386.00 also provides new support for several tape drives. For information about that support, see Section 1.6.

1.5.1    Select Appropriate Steps

Choose the following option that describes your system, then perform the indicated steps described in Section 1.5.2. In every case, you must rebuild the kernel and reboot the system:

Option A

You have a cam_data.c file containing customized device information. Follow the steps listed in Case 1.

Option B

You have CLC, OSMS/OSDS, and/or MME layered products and/or other products that make modifications to the cam_data.c file. Follow the steps listed in Case 2.

Option C

Your system matches both Option A and Option B on your system. Follow the steps listed in both Case 1 and Case 2.

Option D

You have neither Option A nor Option B on your system. Follow the steps listed in Case 3.

1.5.2    Perform Appropriate Steps

The steps decribed in the following situations must be take before you install Patch 386.00 and continue after it is installed.

Case 1:

1. Back up the original cam_data.c file:

   # cp -p /usr/sys/data/cam_data.c /usr/sys/data/cam_data.c.org 
   

2. Install Patch 386.00.

3. Manually merge the original cam_data.c and the patched cam_data.c using the editor of your choice. The following steps assume that the patched cam_data.c file has been placed in a /patches directory:

   1. In window 1, edit the /usr/sys/data/cam_data.c.org file and select the customized information:

      # view /usr/sys/data/cam_data.c.org 
      

   2. In window 2, copy /patches/cam_data.c into /usr/sys/data/cam_data.c

      # cp /patches/cam_data.c /usr/sys/data/cam_data.c
      

   3. Edit the /usr/sys/data/cam_data.c file:

      # vi /usr/sys/data/cam_data.c
      

   4. At the location where the customized information needs to be located, paste the selected information from window 1, save the changes, and exit the file.

4. If your system has CLC, OSMS/OSDS, and/or MME layered products and/or other products installed, proceed to Case 2. Otherwise, proceed to Section 1.5.3.

Case 2:

When CLC, OSMS/OSDS, and/or MME layered products and/or other products are installed, you will need to determine which products have changed the cam_data.c file. To do this, search the setld script files, as follows:

# grep cam_data.c /usr/.smdb./*.scp

With the exception of the OSFBINCOM375 subset (Base Operating System), any subset that is displayed has modified the cam_data.c file. If this applies, then perform the following steps:

1. Backup the original cam_data.c file:

   # cp -p /usr/sys/data/cam_data.c /usr/sys/data/cam_data.c.org
   

2. Deinstall the layered products/other products using the setld -d. For example:

    # setld -d [product_name]
   

3. Install Patch 386.00.

4. Reinstall the products that you deinstalled. See the appropriate installation guides.

5. Manually merge the original cam_data.c and the patched cam_data.c using the editor of your choice. The following steps assume that the patched cam_data.c file has been placed in a /patches directory:

   1. In window 1, edit the /usr/sys/data/cam_data.c.org file and select the customized information:

      # view /usr/sys/data/cam_data.c.org 
      

   2. In window 2, copy /patches/cam_data.c into /usr/sys/data/cam_data.c

      # cp /patches/cam_data.c /usr/sys/data/cam_data.c
      

   3. Edit the /usr/sys/data/cam_data.c file:

      # vi /usr/sys/data/cam_data.c
      

   4. At the location where the customized information needs to be located, paste the selected information from window 1, save the changes, and exit the file.

Case 3:

1. Backup the original cam_data.c file:

   # cp -p /usr/sys/data/cam_data.c /usr/sys/data/cam_data.c.org
   

2. Install Patch 386.00.

3. Proceed to Section 1.5.3.

1.5.3    Rebuild the Kernel

Complete the following steps to rebuild the kernel. For more information, see the DIGITAL UNIX Installation Guide.

1. Backup the original /vmunix:

   # cp /vmunix /vmunix.prepatch 
   

   If there is not enough space in the root directory, move the/vmunix patch file to a location in the /usr directory.

2. Run doconfig to create a new kernel:

    #  doconfig -c <system_name>
   

3. Copy the new /vmunix to the root directory:

   # cp /sys/<system_name>/vmunix  /vmunix
   

4. Reboot the system:

   # shutdown -r now
   

1.5.4    Restore Original Files

To restore the original configuration, you should be able to use the following steps.

1. Restore the original files:

   # cp -p /usr/sys/data/cam_data.c.org /usr/sys/data/cam_data.c

# cp -p (location of backed up vmunix) /vmunix
   

2. Reboot the system:

   # shutdown -r now
   

1.6    Patch 386.00 Support for Tape Drives

Patch 386.00 adds device recognition for several tape drives, including the TZ89, TZS20, and TLZ10. This section describes the media and format information for these tape drives. For convenience, it includes this information for other tape drives, which is provided in the tz(7) Reference Page.

Table 1-1 lists the tape compatibility for various TZn tape drives.

Table 1-1:  Media Type for TZn Tape Drives

Table 1-2 provides information about TZ85, TZ86, TZ87, TZ88, and TZ89 tape drives. Note that in the capacity column, a number followed by an asterisk (*) assumes a 2:1 compression ratio. The actual compression ratio may vary depending on the type of data being compressed.

Table 1-2:  Supported Formats for TZn Tape Drives

Table 1-3 lists the tape compatibility for the TLZ04, TLZ06, TLZ07, TLZ09, and TLZ10 tape drives.

Table 1-3:  Tape Compatibility for TLZn Tape Drives

Table 1-4 provides information about the TLZ-family of tape drives. The TLZn tape drives support variable block size. Note that in the capacity column, a number followed by an asterisk (*) assumes a 2:1 compression ratio. The actual compression ratio may vary depending on the type of data being compressed.

Table 1-4:  Supported Formats for TLZn Tape Drives

Table 1-5 provides information about TZS20 Tape Drives.

Table 1-5:  Supported Formats for TZS20 Tape Drives