This chapter provides information that you must be aware of when working with Tru64 UNIX 4.0F and TCR 1.6 Patch Kit-0001.
The following storage space is required to successfully install this patch kit:
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 ~15.6 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 ~15.8 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 ~126 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.
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 ~12.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 ~12.3 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 ~132 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.
The following sections describe new features of
dupatch
.
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.
The
dupatch
utility now manages patch dependencies
across the Tru64 UNIX operating system, ASE, and TCR patch kits.
An example
of patch cross-product dependency handling for a system with both Tru64 UNIX
4.0F and TCR 1.6 installed follows:
If a Tru64 UNIX 4.0F Patch 1.00 is chosen for installation
and it depends upon TruCluster 1.6 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 Tru64 UNIX 4.0F Patch 1.00.
If the patch selections are reversed,
dupatch
will
still warn you and block installation of the chosen patch.
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.
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.
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.
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 Tru64 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.
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.
The following list of
dupatch
error
messages will be created when executing
dupatch
.
This problem will be addressed in a future release of
dupatch
.
After installation of the V4.0F Patch Kit-0001, the target root contains these three files:
# ls -l PCI*
-rw-r--r-- 1 root system 0 Jun 1 18:35 PCITMP1
-rw-r--r-- 1 root system 0 Jun 1 18:35 PCITMP2:
-rw-r--r-- 1 root system 0 Jun 1 18:35 PCITMP3
Also, the root directory of the system installing the patches contains the files:
# ls -l /P_P*
-rw-r--r-- 1 root system 54 Jun 1 18:35
/P_ProdCacheInfo.tmp1
-rw-r--r-- 1 root system 0 Jun 1 18:35
/P_ProdCacheInfo.tmp2
These are error messages from
dupatch
that are not being properly trapped.
This problem will be addressed in a
future release of
dupatch
.