This chapter provides important information that you need in order to
work with the Tru64 UNIX 5.0A and TruCluster 5.0A Patch Kit-0002.
1.1 Required Storage Space
The following storage space is required to successfully install this
patch kit:
Base Operating System
Temporary Storage Space
A total of ~250 MB of storage space is required to untar this patch
kit.
Compaq recommends that this kit not be placed in the
/
,
/usr
, or
/var
file systems because doing so may
unduly constrain the available storage space for the patching activity.
Permanent Storage Space
Up to ~35 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 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 Instructions
for more
information.
Up to ~150 KB of storage space is required in
/var/adm/patch/doc
for patch abstract and README documentation.
A total of ~152 KB of storage space is needed in
/usr/sbin/dupatch
for the patch management utility.
TruCluster Server
Temporary Storage Space
A total of ~250 MB of storage space is required to untar this patch
kit.
Compaq recommends that this kit not be placed in the
/
,
/usr
, or
/var
file systems because doing so may
unduly constrain the available storage space for the patching activity.
Permanent Storage Space
Up to ~41 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 ~44 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 Instructions
for more
information.
Up to ~374 KB of storage space is required in
/var/adm/patch/doc
for patch abstract and README documentation.
A total of ~152 KB of storage space is needed in
/usr/sbin/dupatch
for the patch management utility.
Beginning with Revision 26-02 of
dupatch
, this
patch tool utility has been enhanced to provide new features, as described
in the following sections.
For more information, see the
Patch Kit Installation Instructions.
1.2.1 Patch Installation from Multiuser Mode
You can now install patches when a system is in multiuser mode.
There are no restrictions on performing patch selection and preinstallation checking in multiuser mode.
Although you can now install patches in multiuser mode, Compaq recommends
that you bring down your system to single-user mode when you install 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, we recommend
that you apply the patches when the system is as lightly loaded as possible.
1.2.2 Automatic Kernel Build
If the patches that are installed indicate that a kernel build is required,
dupatch
will initiate the kernel build automatically.
Most times a reboot is required to complete the installation and bring the system to a consistent running environment. Certain file types, such as libraries, are not moved into place until you reboot the system.
When installing patches in multiuser mode, you can take one of three options after the kernel build is complete:
Reboot the system immediately.
Reboot the system at a specified time.
Do not reboot the system.
1.2.3 Patch Installation from a Pseudo-Terminal
You can now install patches on the system from a pseudo-terminal (pty)
while in single-user mode.
To do this, log in to the system as root from
a remote location and specify that the patches are to be installed in single-user
mode.
After all the patch prerequisites are completed, the system goes into
single-user mode while it maintains the network connection for the root user.
The system then installs the patches.
1.3 Release Note for Tru64 UNIX Patch 75.00
SysMan Station does not dynamically update changes to a device name.
If you use
dsfmgr
(8) to change the
base_name
of a device while
smsd
(8) is running, any SysMan Station
clients that connect to the running
smsd
(8) will reflect
the old
base_name
in their views.
To obtain a correct view, restart the SysMan Station daemon
smsd
(8) by performing the following steps.
If you are on a cluster,
perform these steps on all affected cluster members.
Close all open SysMan Station client sessions.
Enter the following command:
#
/sbin/init.d/smsd restart
1.4 Release Note for TruCluster Server
If you are installing only TCR patches, you MUST rebuild the kernel and reboot the machine for the changes to take effect. If removing only TCR patches, you MUST also rebuild the kernel and reboot the machine for the changes to take effect.