# CLUSTER_README

NAME: Solaris 2.3 Recommended Patch Cluster
DATE: Jun/25/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.

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

These Solaris Recommended patches are considered the most important and
highly recommended patches that avoid the most critical system, user, or
security related bugs which have been reported and fixed to date.  In
most cases a Solaris security patch will be included in the recommended
patch set.  It is possible, however, that a security patch may not be
included in the recommended set if it is determined to be a more obscure
application specific issue and not generally applicable.

During initial installation of the Solaris product other patches or patch
sets may be provided with the product and required with product installation.
Refer to the Solaris product installation documentation to be sure that all
the patches required at product installation are already installed.  This
patch cluster can then be used to update or augment the system with the
recommended patches included.


PATCHES INCLUDED:
-----------------

101359-10  SunOS 5.3: libresolv, in.named, named-xfer, nslookup & nstest patch
101317-30  SunOS 5.3: lp patch
101318-94  SunOS 5.3: Kernel Update (includes libc, lockd)
101327-08  SunOS 5.3: security and miscellaneous tar fixes
101331-08  SunOS 5.3: fixes for package utilities
101347-02  SunOS 5.3: fixes for ttcompat
101494-04  SunOS 5.3: rdist patch
101497-02  SunOS 5.3: in.rexecd fixes
101545-03  SunOS 5.3: /usr/bin/ps and /usr/ucb/ps fixes
101572-15  SunOS 5.3: /usr/bin/at and /usr/sbin/cron patch
101574-07  SunOS 5.3: /usr/bin/mail patch
101620-01  SunOS 5.3: keyserv has a file descriptor leak
101631-02  SunOS 5.3: kd and ms fixes
101712-01  SunOS 5.3: uucleanup isn't careful enough when sending mail
101734-03  SunOS 5.3: iommu fixes for sun4m
101736-04  SunOS 5.3: nisplus patch
101782-03  SunOS 5.3: /usr/lib/sendmail patch
101786-03  SunOS 5.3: inetd fixes
102034-05  SunOS 5.3: usr/sbin/rpcbind patch
102167-03  SunOS 5.3: dns fix
102546-01  SunOS 5.3: drvconfig changes permissions on existing device
102615-01  SunOS 5.3: praudit core dumps on certain audit trails
102622-01  SunOS 5.3: auditd crashes if hard limit is exceeded
102654-02  SunOS 5.3: /usr/lib/nfs/mountd patch
102666-01  SunOS 5.3: data fault in scanc() due to bad "cp" argument
102707-02  SunOS 5.3: jumbo patch for NIS commands
102787-07  SunOS 5.3: patch for sccs
102892-01  SunOS 5.3: libm can hit SEGV in multi-threaded mode
102932-05  SunOS 5.3: statd fixes
102962-01  SunOS 5.3: vipw has a security problem
103269-01  SunOS 5.3: nissetup default permissions not secure enough
103705-01  SunOS 5.3: rpc.nisd_resolv rebuild for BIND 4.9.3
104698-01  SunOS 5.3: in.talkd security problem fix
104797-02  SunOS 5.3: eeprom patch
104938-04  SunOS 5.3: usr/sbin/in.ftpd patch
105205-01  SunOS 5.3: usr/sbin/sysdef patch
105253-01  SunOS 5.3: usr/bin/rlogin patch
106006-03  SunOS 5.3: usr/sbin/vold patch
106450-01  SunOS 5.3: /usr/sbin/ping fix
101428-19  OpenWindows 3.3: OLIT Patch
101429-04  OpenWindows 3.3: libXt patch
101362-51  OpenWindows 3.3: Server (Xsun) Patch
101512-43  OpenWindows 3.3: XView patch
101513-17  OpenWindows 3.3: Calendar Manager patch
101889-05  OpenWindows 3.3: filemgr (ff.core) fixes
105243-01  OpenWindows 3.3: libXt Binary Compatibility Patch
101653-03  SunOS 5.3: /usr/bin/ftp patch
105677-02  SunOS 5.3: /usr/sbin/auditreduce patch
106702-01  SunOS 5.3: Fix security problem in in.uucpd
106911-01  SunOS 5.3: /usr/bin/apropos patch
106989-01  SunOS 5.3: uux has buffer overflow problems
106675-03  OpenWindows 3.3: libce suid/sgid security fix
106676-02  OpenWindows 3.3: libdeskset patch
101605-08  OpenWindows 3.3: Mailtool Patch
108489-01  SunOS 5.3: Snoop may be exploited to gain root access
101495-04  OpenWindows 3.3: ToolTalk patch
104880-02  SunOS 5.3: usr/bin/uustat patch
108494-01  SunOS 5.3: ASET sets gid on /tmp,/var/tmp when med or high security
108771-02  SunOS 5.3: Telnet environment has extra NULL field between HZ & TZ var
109102-01  SunOS 5.3: tip has buffer overrun with security implications
101325-05  SunOS 5.3: fmli patch, libcurses.a
101791-03  SunOS 5.3: ksh patch


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!!

