[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

SunOS : Solaris 9 Patch Cluster


NAME: Solaris 9 Recommended Patch Cluster
DATE: Jun/22/04


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). 



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.


114008-01  SunOS 5.9: cachefsd Patch
112998-03  SunOS 5.9: patch /usr/sbin/syslogd
112875-01  SunOS 5.9: patch /usr/lib/netsvc/rwall/rpc.rwalld
113146-03  SunOS 5.9: Apache Security Patch
113068-04  SunOS 5.9: hpc3130 patch
112963-13  SunOS 5.9: linker patch
113273-06  SunOS 5.9: /usr/lib/ssh/sshd Patch
112233-12  SunOS 5.9: Kernel Patch
112964-07  SunOS 5.9: /usr/bin/ksh Patch
112808-06  CDE1.5: Tooltalk patch
113492-04  SunOS 5.9: fsck Patch
113279-01  SunOS 5.9: klmmod Patch
113278-06  SunOS 5.9: NFS Daemon , rpcmod Patch
113023-01  SunOS 5.9: Broken preremove scripts in S9 ALC packages
112764-07  SunOS 5.9: Sun Quad FastEthernet qfe driver
113033-04  SunOS 5.9: patch /kernel/drv/isp and /kernel/drv/sparcv9/isp
112601-09  SunOS 5.9: PGX32 Graphics
113923-02  X11 6.6.1: security font server patch
112817-17  SunOS 5.9: Sun GigaSwift Ethernet 1.0 driver patch
113718-02  SunOS 5.9: usr/lib/utmp_update Patch
114135-01  SunOS 5.9: at utility Patch
114133-01  SunOS 5.9: mail Patch
114153-01  SunOS 5.9: Japanese SunOS 4.x Binary Compatibility(BCP) patch
113575-05  SunOS 5.9: sendmail Patch
113713-15  SunOS 5.9: pkginstall Patch
114636-02  SunOS 5.9: KCMS security fix
112975-03  SunOS 5.9: patch /kernel/sys/kaio
114564-03  SunOS 5.9: /usr/sbin/in.ftpd Patch
114713-01  SunOS 5.9: newtask Patch
113240-10  CDE 1.5: dtsession patch
114721-05  SunOS 5.9: ufsrestore and ufsdump Patch
114684-02  SunOS 5.9: samba Patch
113077-12  SunOS 5.9: /platform/sun4u/kernal/drv/su Patch
114861-01  SunOS 5.9: /usr/sbin/wall
114729-01  SunOS 5.9: usr/sbin/in.telnetd Patch
114482-04  SunOS 5.9: Product Registry CLI Revision
114571-02  SunOS 5.9: libc.so.*.9/bcp Patch
114569-02  SunOS 5.9: libdbm.so.1 Patch
115754-02  SunOS 5.9: zlib security Patch
114332-12  SunOS 5.9: c2audit & *libbsm.so.1 Patch
113573-05  SunOS 5.9: libpsvc Patch
114495-01  CDE 1.5: dtprintinfo patch
112965-03  SunOS 5.9: patch /kernel/drv/sparcv9/eri
113073-08  SunOS 5.9: ufs_log patch
112945-27  SunOS 5.9: wbem Patch
115158-05  X11 6.6.1: xscreensaver patch
115172-01  SunOS 5.9: kernel/drv/le Patch
114971-02  SunOS 5.9: usr/kernel/fs/namefs Patch
112540-22  SunOS 5.9: Expert3D IFB Graphics Patch
113329-08  SunOS 5.9: lp Patch
112617-02  CDE 1.5: rpc.cmsd patch
112661-06  SunOS 5.9: IIIM and X Input & Output Method patch
112807-10  CDE 1.5: dtlogin patch
112926-05  SunOS 5.9: smartcard Patch
113451-07  SunOS 5.9: IKE Patch
114014-08  SunOS 5.9: libxml, libxslt and Freeware man pages Patch
114016-01  tomcat security patch
114049-11  SunOS 5.9: NSPR 4.1.6 / NSS
114125-01  SunOS 5.9: IKE config.sample patch
114361-01  SunOS 5.9: /kernel/drv/lofi Patch
114875-01  SunOS 5.9: XML library source patch
116237-01  SunOS 5.9: pfexec Patch
116247-01  SunOS 5.9: audit_warn Patch
116308-01  CDE 1.5: libDtHelp patch
116245-01  SunOS 5.9: uncompress Patch
114363-02  SunOS 5.9: sort Patch
113226-05  SunOS 5.9: hme Driver Patch
113482-02  SunOS 5.9: sbin/sulogin Patch
113457-05  SunOS 5.9: ufs headers
114388-05  SunOS 5.9: dmfe driver patch
113322-02  SunOS 5.9: patch uucp
117067-01  SunOS 5.9: awk nawk oawk Patch
113447-17  SunOS 5.9: libprtdiag_psr Patch
117071-01  SunOS 5.9: memory leak in llc1_ioctl()
116807-01  SunOS 5.9: patch usr/sadm/lib/smc/lib/preload/jsdk21.jar
117171-02  SunOS 5.9: Kernel Patch
114126-02  SunOS 5.9: todds1287 patch
116536-01  SunOS 5.9: dlcosmk Patch
112906-03  SunOS 5.9: ipgpc Patch
112874-24  SunOS 5.9: lgroup API libc Patch
113096-03  X11 6.6.1: OWconfig patch
115689-01  SunOS 5.9: /usr/lib/patch/patchutil Patch
112834-03  SunOS 5.9: patch scsi
115165-03  SunOS 5.9: usr/lib/libnisdb.so.2 Patch
114129-02  SunOS 5.9: multi-terabyte disk support -libuuid patch
112907-03  SunOS 5.9: libgss Patch
112912-01  SunOS 5.9: libinetcfg Patch
116532-02  SunOS 5.9: mpt Patch
113319-18  SunOS 5.9: libnsl nispasswdd patch
112785-35  X11 6.6.1: Xsun patch
112970-07  SunOS 5.9: patch libresolv
112951-08  SunOS 5.9: patchadd and patchrm Patch
113277-22  SunOS 5.9: sd and ssd Patch
113579-06  SunOS 5.9: ypserv/ypxfrd Patch
112908-13  SunOS 5.9: krb5 shared object patch
114864-02  SunOS 5.9: Sun-Fire-480R libpsvcpolicy_psr.so.1 Patch
112922-02  SunOS 5.9: krb5 lib Patch
112925-03  SunOS 5.9: ktutil kdb5_util kadmin kadmin.local kadmind Patch
112923-03  SunOS 5.9: krb5 usr/lib Patch
112921-03  SunOS 5.9: libkadm5 Patch
112960-14  SunOS 5.9: patch libsldap ldap_cachemgr libldap
112911-06  SunOS 5.9: ifconfig Patch
115665-07  SunOS 5.9: Chalupa platform support Patch
113475-03  SunOS 5.9: usr/lib/security crypt Patch
114127-03  SunOS 5.9: abi_libefi.so.1 and fmthard Patch
113993-06  SunOS 5.9: mkfs Patch
113026-19  SunOS 5.9: /kernel/drv/md Patch


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.

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.

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.

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.

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.

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.


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>

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.