# CLUSTER_README

NAME: J2SE Solaris 8 Recommended Patch Cluster
DATE: Nov/11/04

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

This patch cluster is intended to provide a selected set of patches for
the designated Solaris release level. This bundle provides the 
recommended patches for support of the Java(tm) 2 Platform, Standard 
Edition on the Solaris(tm) Operating Environment. This is a bundled set 
of patches conveniently wrapped for one-step installation.  Note that 
there are ten patch clusters similar to this one - one each for Solaris 
5.5.1, Solaris 5.6, Solaris 7, Solaris 8, and Solaris 9 for both SPARC(tm) 
and Intel processors.  Be sure to install only the cluster that is 
appropriate for your system 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.

WARNING!! IT IS HIGHLY RECOMMENDED that the installation of this patch 
cluster be performed in single-user mode (Run Level S).

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

CLUSTER DESCRIPTION
-------------------

These recommended patches are considered the most important and highly 
recommended patches that avoid the most critical system, user, or
other bugs related to the functionality of the Java platform on the 
Solaris Operating Environment which have been reported and fixed 
to date. 

Other patches or patch sets are provided with the initial installation 
of the Solaris Operating Environment. 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:
-----------------

108652-84  X11 6.4.1: Xsun patch
108921-22  CDE 1.4: dtwm patch
108940-65  Motif 1.2.7 and 2.1.1: Runtime library patch for Solaris 8
112003-03  SunOS 5.8: Unable to load fontset in 64-bit Solaris 8 iso-1 or iso-15
108773-18  SunOS 5.8: IIIM and X Input & Output Method patch
111310-01  SunOS 5.8: /usr/lib/libdhcpagent.so.1 patch
112472-01  SunOS 5.8: Font2DTest2 abort when Lucida Sans Thai Typewriter selected
109147-31  SunOS 5.8: linker patch
111308-05  SunOS 5.8: /usr/lib/libmtmalloc.so.1 patch
112438-03  SunOS 5.8: /kernel/drv/random patch
108434-18  SunOS 5.8: 32-Bit Shared library patch for C++
108435-18  SunOS 5.8: 64-Bit Shared library patch for C++
113886-26  OpenGL 1.3: OpenGL Patch for Solaris (32-bit)
113887-26  OpenGL 1.3: OpenGL Patch for Solaris (64-bit)
111111-04  SunOS 5.8: /usr/bin/nawk patch
112396-02  SunOS 5.8: /usr/bin/fgrep patch
110386-03  SunOS 5.8: RBAC Feature Patch
111023-03  SunOS 5.8: /kernel/fs/mntfs and /kernel/fs/sparcv9/mntfs patch
111317-05  SunOS 5.8: /sbin/init and /usr/sbin/init patch
113648-03  SunOS 5.8: /usr/sbin/mount patch
115827-01  SunOS 5.8: /sbin/sulogin and /sbin/netstrategy patch
116602-01  SunOS 5.8: /sbin/uadmin and /sbin/hostconfig patch
108987-13  SunOS 5.8: Patch for patchadd and patchrm
108528-29  SunOS 5.8: kernel update  and Apache patch
108989-02  SunOS 5.8: /usr/kernel/sys/acctctl and /usr/kernel/sys/exacctsys patch
108993-38  SunOS 5.8: LDAP2 client, libc, libthread and libnsl libraries patch
109326-16  SunOS 5.8: libresolv.so.2 and in.named patch
110615-13  SunOS 5.8: sendmail 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 directories 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 10 MBytes of available space in each of these directories. 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 patchadd
command 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 patchrm command manual page for instructions and more
information.  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 before 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 CLIENT SYSTEMS:
On server machines that service diskless 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 patchrm command 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 revision before installing a newer revision.


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

First, be sure the contents of the patch cluster's .tar file have
been extracted (using the 'tar xvf <filename>' command), 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 patchadd
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!!
