# CLUSTER_README
NAME: 9_x86 Recommended Patch Cluster
DATE: Sep/14/06
########################################################################
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.
WARNING!! IT IS HIGHLY RECOMMENDED that the installation of this patch
cluster be performed in single-user mode (Run Level S).
########################################################################
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:
-----------------
116341-05 SunOS 5.9_x86: gzip and Freeware info files patch
121993-01 SunOS 5.9_x86: fgrep Patch
117068-04 SunOS 5.9_x86: awk nawk oawk Patch
114343-13 SunOS 5.9_x86: ksh patch
114568-20 SunOS 5.9_x86: usr/sadm/install/bin/pkginstall Patch
114194-10 SunOS 5.9_x86: patchadd and patchrm Patch
113996-02 SunOS 5.9_x86: utmp_update Patch
113924-02 X11 6.6.1_x86: security font server patch
114136-02 SunOS 5.9_x86: at utility Patch
114134-02 SunOS 5.9_x86: mail Patch
114009-01 SunOS 5.9_x86: cachefsd Patch
114714-02 SunOS 5.9_x86: newtask Patch
114685-03 SunOS 5.9_x86: samba Patch
114862-01 SunOS 5.9_x86: /usr/sbin/wall Patch
114730-01 SunOS 5.9_x86: /usr/sbin/in.telnetd Patch
114483-04 SunOS 5.9_x86: Product Registry CLI Revision
114715-01 SunOS 5.9_x86: libdb2.so.1 Patch
114570-01 SunOS 5.9_x86: libdbm.so.1 Patch
113241-11 CDE 1.5_x86: dtsession patch
114637-03 SunOS 5.9_x86: KCMS security fix
114858-08 SunOS 5.9_x86: usr/lib/ssh/sshd Patch
115755-02 SunOS 5.9_x86: zlib security Patch
116045-01 SunOS 5.9_x86: krbv5 Patch (krb5kdc)
116044-03 SunOS 5.9_x86: krbv5 Patch
114496-01 CDE 1.5_x86: dtprintinfo patch
114017-01 SunOS 5.9_x86: tomcat security patch
114362-01 SunOS 5.9_x86: lofi patch
114436-01 SunOS 5.9_x86: ike hardware - config.sample patch
114876-01 SunOS 5.9_x86: XML library source patch
116238-01 SunOS 5.9_x86: pfexec Patch
116248-01 SunOS 5.9_x86: audit_warn Patch
116246-01 SunOS 5.9_x86: uncompress Patch
116508-01 SunOS 5.9_x86: sulogin Patch
116454-02 SunOS 5.9_x86: sadmind patch
117115-02 CDE 1.5_x86: sdtwebclient patch
116309-01 CDE 1.5_x86: libDtHelp patch
117072-01 SunOS 5.9_x86: memory leak in llc1_ioctl()
117172-17 SunOS 5.9_x86: Kernel Patch
113870-05 CDE 1.5_x86: dtmail patch
114050-12 SunOS 5.9_x86: NSPR 4.1.6 / NSS 3.3.4.5
114348-14 SunOS 5.9_x86: /usr/sbin/in.routed patch
116775-03 SunOS 5.9_x86: ping Patch
117456-02 SunOS 5.9_x86: in.rwhod Patch
116539-03 SunOS 5.9_x86: SUNW_disk_link.so Patch
116106-04 X11 6.6.1_x86: FreeType patch
117204-05 X11 6.6.1_x86: fontconfig patch
117202-09 X11 6.6.1_x86: st patch
119434-01 SunOS 5.9_x86: telnet
114273-04 SunOS 5.9_x86: Sun ONE Directory Server 5.1 patch
117446-01 SunOS 5.9_x86: newgrp patch
116808-02 SunOS 5.9_x86: /usr/sadm/lib/smc/lib/preload/jsdk21.jar patch
114328-06 SunOS 5.9_x86: nss_ldap.so.1 Patch
114357-06 SunOS 5.9_x86: usr/bin/ssh patch
117486-01 SunOS 5.9_x86: fn_ctx_x500.so.1 Patch
119450-01 SunOS 5.9_x86: Perl Patch
114932-01 SunOS 5.9_x86: usr/sbin/syslogd Patch
113986-21 SunOS 5.9_x86: linker Patch
112786-45 X11 6.6.1_x86: Xsun patch
112662-06 SunOS 5.9_x86: IIIM and X Input & Output Method patch
114220-11 CDE 1.5_x86: sdtimage patch
117482-01 SunOS 5.9_x86: c2audit Patch
116046-07 SunOS 5.9_x86: krbv5 Patch (libkadm5srv.so.1)
114355-03 SunOS 5.9_x86: sort patch
114504-14 SunOS 5.9_x86: usr/sadm/lib/usermgr/VUserMgr.jar Patch
113838-02 CDE 1.5_x86: libDtSvc patch
115167-05 SunOS 5.9_x86: usr/bin/cpio Patch
116244-01 SunOS 5.9_x86: umountall Patch
117163-01 SunOS 5.9_x86: patch usr/src/uts/common/sys/cpc_impl.h
117478-01 SunOS 5.9_x86: vol Patch
119902-01 Openwindows 3.7.0_x86: Xview Patch
118301-02 X11 6.6.1_x86: libXpm patch
120465-01 SunOS 5.9_x86: bios utility patch
115880-02 SunOS 5.9_x86: uucp patch
115159-10 X11 6.6.1_x86: xscreensaver patch
114432-24 SunOS 5.9_x86: libc patch
113719-18 SunOS 5.9_x86: libnsl, rpc.nispasswdd patch
118908-02 X11 6.7.0_x86: Xorg patch
114354-08 SunOS 5.9_x86: libresolv patch
117470-07 SunOS 5.9_x86: tcp Patch
114980-18 SunOS 5.9_x86: lp Patch
121995-01 SunOS 5.9_x86: hsfs Patch
120463-02 SunOS 5.9_x86: sockfs Patch
121195-01 SunOS 5.9_x86: usr/lib/nfs/statd Patch
116528-02 SunOS 5.9_x86: timod Patch
114243-15 SunOS 5.9_x86: st driver Patch
121997-02 SunOS 5.9_x86: S9 perl 5.005_03`s CGI.pm and Safe.pm modules Patch
121322-03 SunOS 5.9_x86: ldap patch
120239-01 SunOS 5.9_x86: ps cmd patch
118536-03 SunOS 5.9_x86: sh/jsh/rsh/pfsh Patch
115678-02 SunOS 5.9_x86:/usr/lib/ldap/idsconfig Patch
116545-03 SunOS 5.9_x86: Timezone commands and zoneinfo database update Patch
116503-03 SunOS 5.9_x86: mountd Patch
114435-10 SunOS 5.9_x86: IKE patch
114193-33 SunOS 5.9_x86: wbem Patch
114565-09 SunOS 5.9_x86: /usr/sbin/in.ftpd Patch
114145-06 SunOS 5.9_x86: Apache Security Patch
117468-12 SunOS 5.9_x86: NFS patch
114423-07 SunOS 5.9_x86: format patch
119212-09 NSS_NSPR_JSS 3.11.2_x86: NSPR 4.6.2 / NSS 3.11.2 / JSS 4.2.4
119439-08 SunOS 5.9_x86: NFS Daemon, rpcmod Patch
114342-09 SunOS 5.9_x86: ypserv/ypxfrd/rpc.yppasswdd patch
114263-06 SunOS 5.9_x86: libgss.so.1 Patch
118559-30 SunOS 5.9_x86: Kernel Patch
114015-12 SunOS 5.9_x86: libxml, libxslt and Freeware man pages Patch
114137-06 SunOS 5.9_x86: sendmail Patch
119443-05 SunOS 5.9_x86: sd patch
115168-13 SunOS 5.9_x86: krb5, gss patch
114242-26 SunOS 5.9_x86: ldap library Patch
114210-17 CDE 1.5_x86: dtlogin patch
117472-03 SunOS 5.9_x86: fifofs Patch
117481-01 SunOS 5.9_x86: pkgadd 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 patch cluster has been unzipped
if the cluster was received as a .zip 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 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>
