# CLUSTER_README

NAME: Solaris 2.3 y2000_ALL Patch Cluster
DATE: Feb/06/01

########################################################################

This patch cluster is intended to provide a selected set of patches for
the designated Solaris release level.  This is a bundled set of patches
conveniently wrapped for one-step installation.  Only install this
cluster on the appropriate Solaris system.  Carefully read all important
notes and install instructions provided in this README file before
installing the cluster.  A cluster grouping does not necessarily imply
that additional compatibility testing has occured since the individual
patches were released.

########################################################################
Y2000 CLUSTER DESCRIPTION
-------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+     N O T E		N O T E		N O T E		 N O T E     +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

This current Solaris Year 2000 patch cluster contains ALL the Year 2000
patches for this Operating System. If the system is up to date with
respect to the Solaris Recommended Patch cluster then use this cluster
to bring the system to Year 2000 compliance.
Some of the patches included in this Solaris Year 2000 cluster set are
also included in the Solaris Recommended cluster.
You may see an error message stating that "the patch has already been 
installed". This means that the patch has already been applied to the 
system by some other means, either the Solaris Recommended cluster or by
installing the patch by itself. Please disregard this error message, for
it is only an informative message and the attempt to install the patch 
did not change the state of the Operating System.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

This Year 2000 patch set completes the fixes required for Year 2000
compliance.  These patches should be installed to avoid critical
system, user, or security related Year 2000 bugs which have been
reported and fixed to date.

To obtain any or all Sun released patches, Please visit the 
following SunSolve website located at:

		http://sunsolve.Sun.COM/

To obtain the most current information regarding Year 2000 program,
Please visit the Year 2000 program website located at:

		http://www.sun.com/y2000
 
PATCHES INCLUDED:
-----------------

107983-01  SunOS 5.3: Patch for SPARCompiler Binary Compatibility Libraries
101318-94  SunOS 5.3: Kernel Update (includes libc, lockd)
101362-51  OpenWindows 3.3: Server (Xsun) Patch
106676-02  OpenWindows 3.3: libdeskset patch
106675-03  OpenWindows 3.3: libce suid/sgid security fix
101512-43  OpenWindows 3.3: XView patch
101317-30  SunOS 5.3: lp patch
101331-08  SunOS 5.3: fixes for package utilities
101572-15  SunOS 5.3: /usr/bin/at and /usr/sbin/cron patch
104797-02  SunOS 5.3: eeprom patch
102787-07  SunOS 5.3: patch for sccs
101343-04  SunOS 5.3: troff macro patch
101767-02  SunOS 5.3: usr/bin/passwd patch
103941-02  SunOS 5.3: accounting patch
104877-01  SunOS 5.3: usr/sbin/sar patch
104878-01  SunOS 5.3: usr/bin/date patch
104880-02  SunOS 5.3: usr/bin/uustat patch
104882-01  SunOS 5.3: usr/lib/saf/listen patch
104883-02  SunOS 5.3: usr/lib/fs/ufs/ufsdump and usr/lib/fs/ufs/ufsrestore patch
104884-01  SunOS 5.3: usr/vmsys/bin/initial patch
105013-01  SunOS 5.3: usr/lib/libkrb.a and usr/lib/libkrb.so.1 patch
105677-02  SunOS 5.3: /usr/sbin/auditreduce patch
105713-01  SunOS 5.3: /usr/sbin/sysidsys patch
105956-01  SunOS 5.3: /usr/bin/touch patch
101514-10  OpenWindows 3.3: filemgr patch
101605-08  OpenWindows 3.3: Mailtool Patch
101556-03  OpenWindows 3.3: Imagetool fixes
105307-01  OpenWindows 3.3: perfmeter fixes
101533-07  OpenWindows 3.3: xterm patch
106443-01  SunOS 5.3: /usr/sbin/whodo fix
101513-17  OpenWindows 3.3: Calendar Manager patch
107522-01  SunOS 5.3: On Y2000, runacct cannot update /var/adm/acct/sum/loginlog
105020-01  SunOS 5.3 (JFP 2.3): Japanese BCP libc patch
105233-01  SunOS 5.3: BCP libc patch (Asian)


IMPORTANT NOTES AND WARNINGS:
-----------------------------

SYSTEMS WITH LIMITED DISK SPACE SHOULD *NOT* INSTALL PATCHES:
With or without using the save option, the patch installation process
will still require some amount of disk space for installation and
administrative tasks in the /, /usr, /var, or /opt partitions where
patches are typically installed.  The exact amount of space will
depend on the machine's architecture, software packages already
installed, and the difference in the patched objects size.  To be
safe, it is not recommended that a patch cluster be installed on a
system with less than 4 MBytes of available space in each of these
partitions.  Running out of disk space during installation may result
in only partially loaded patches.  Be sure a recent full system backup
is available in case a problem occurs, and check to be sure adequate
disk space is available before installing the patch cluster. 

SAVE AND BACKOUT OPTIONS:
By default, the cluster installation procedure uses the installpatch
save feature to save the base objects being patched.  Prior to installing
the patches the cluster installation script will first determine if
enough system disk space is available in /var/sadm/patch to save the
base objects and will terminate if not.  Patches can only be individually
backed out with the original object restored if the save option was used
when installing this cluster.  Please later refer to the backoutpatch
instructions provided in the individual patch README file which will be
located in the specific patch directory under /var/sadm/patch after
the patch has been installed.  It is possible to override the save
feature by using the [-nosave] option when executing the cluster
installation script.  Using the nosave option, however, means that you
will not be able to backout individual patches if the need arises.

SPECIAL INSTALL INSTRUCTIONS:
As with any patch individually applied, there may be additional special
installation instructions which are documented in the individual patch
readme file.  It is recommended that each individual patch readme is
reviewed after installing this cluster to determine if any additional
installation steps are necessary for a patch.  Otherwise it is possible
that an individual patch may still not be completely installed in all
respects after the cluster has been installed.

DISKLESS OR DATALESS CLIENT SYSTEMS:
On server machines that service diskless and/or dataless clients, a
patch is NOT applied to existing clients or to the client root template
space.  Therefore, all client machines of the server that will need
this cluster will have to individually apply this cluster.  Install
this cluster on the client machines first, then the server.

A PATCH MAY NOT BE APPLIED:
Under certain circumstances listed below, a particular patch provided in
this cluster may not be installed if:
 
- The patch applies to a package that has not originally been installed
- The same or newer revision of the patch has already been installed
- The patch was obsoleted by another patch that has already been installed
- The package database is corrupt or missing

Use the 'showrev -p' command to compare the list of patches already 
installed on the system with the patch list and revision levels provided
in this cluster.  During installation, the install process will indicate
if a patch was not applied and more detailed installation messages will
be logged to the installation log file.  The README file with each patch
also provides documentation regarding install and backout messages.

OLDER VERSIONS OF PATCHES ALREADY INSTALLED:
Backout of older versions of patches provided in the cluster is not
required in order for the newer version to be installed.  However
not backing out an older rev before installing a newer rev will
cause showrev -p to continue to show the older rev along with the
newer rev.  And, if the older rev was previously installed with
the save option, the older rev will continue to occupy disk space
in /var/sadm/patch even though it has been obsoleted by the new rev.
The backoutpatch utility will only allow the most recently saved
objects to be restored, thus there are no serious risks associated
with leaving an older rev on the system.  It just may, however,
avoid confusion and be more economical to first backout an older
patch rev before installing a newer rev.


INSTALL INSTRUCTIONS:
---------------------

First, be sure the patch cluster has been uncompressed and extracted
if the cluster was received as a tar.Z file, then proceed as follows:


1)      Decide on which method you wish to install the cluster:

Recommended Method Using Save Feature:
 
By default, the cluster installation procedure uses the installpatch
save feature to save the original objects being patched.  Prior
to installing the patches the cluster installation script will
first determine if enough system disk space is available in
/var/sadm/patch to save the objects and will terminate if not.
Using the default save feature is recommended. 
 
Method Using No Save Option:
 
It is possible to override the save feature by using the [-nosave]
option when executing the cluster installation script.  Using the
nosave option means that you will not be able to backout individual
patches if the need arises.
 
 
2)      Run the install_cluster script

        cd <patch cluster directory>
        ./install_cluster

By default, a message warning the user to check for minimum disk
space allowance (separate from the save feature) will appear
and allow the user to abort if inadequate space exists.  To
suppress this interactive message the "-q" (quiet) option can
be used when invoking install_cluster.
 
The progress of the script will be displayed on your terminal.
It should look something like:
 
# ./install_cluster
 
Patch cluster install script for <cluster name>
 
Determining if sufficient save space exists...
Sufficient save space exists, continuing...
Installing patches located in <patch cluster directory>
Installing <patch-id>
Installing <patch-id>
.
.
.
Installing <patch-id>
 
For more installation messages refer to the installation logfile:
   /var/sadm/install_data/<cluster name>_log
 
Use '/usr/bin/showrev -p' to verify installed patch-ids.
Refer to individual patch README files for more patch detail.
Rebooting the system is usually necessary after installation.
#
         
 
3)      Check the logfile if more detail is needed.
 
If errors are encountered during the installation of this cluster,
error messages will be displayed during installation.  More details
about the causes of failure can be found in the detail logfile:
 
        more /var/sadm/install_data/<cluster name>_log
 
If this log file previously existed the latest cluster installation
data will be concatenated to the file, so check the end of the file.
 
         
4)      THE MACHINE SHOULD BE REBOOTED FOR ALL PATCHES TO TAKE EFFECT!!

