# CLUSTER_README NAME: Solaris 9 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: ----------------- 116340-05 SunOS 5.9: gzip and Freeware info files patch 121992-01 SunOS 5.9: fgrep Patch 117067-04 SunOS 5.9: awk nawk oawk Patch 112964-15 SunOS 5.9: ksh patch 113713-21 SunOS 5.9: pkginstall Patch 112951-13 SunOS 5.9: patchadd and patchrm Patch 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 112233-12 SunOS 5.9: Kernel Patch 113068-06 SunOS 5.9: hpc3130 patch 113279-01 SunOS 5.9: klmmod Patch 113023-01 SunOS 5.9: Broken preremove scripts in S9 ALC packages 113033-05 SunOS 5.9: patch /kernel/drv/isp and /kernel/drv/sparcv9/isp 113923-02 X11 6.6.1: security font server patch 113718-02 SunOS 5.9: usr/lib/utmp_update Patch 114135-03 SunOS 5.9: at utility Patch 114133-02 SunOS 5.9: mail Patch 114153-01 SunOS 5.9: Japanese SunOS 4.x Binary Compatibility(BCP) patch 114636-03 SunOS 5.9: KCMS security fix 114713-02 SunOS 5.9: newtask Patch 113240-11 CDE 1.5: dtsession patch 114684-03 SunOS 5.9: samba 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 112908-27 SunOS 5.9: krb5, gss patch 112922-02 SunOS 5.9: krb5 lib Patch 115754-02 SunOS 5.9: zlib security Patch 114129-02 SunOS 5.9: multi-terabyte disk support -libuuid patch 114127-03 SunOS 5.9: abi_libefi.so.1 and fmthard Patch 114495-01 CDE 1.5: dtprintinfo patch 113073-14 SunOS 5.9: ufs and fsck patch 115172-01 SunOS 5.9: kernel/drv/le Patch 114971-02 SunOS 5.9: usr/kernel/fs/namefs Patch 112923-03 SunOS 5.9: krb5 usr/lib Patch 112617-02 CDE 1.5: rpc.cmsd patch 114016-01 tomcat security patch 114049-12 SunOS 5.9: NSPR 4.1.6 / NSS 3.3.4.5 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 113226-05 SunOS 5.9: hme Driver Patch 113482-02 SunOS 5.9: sbin/sulogin Patch 117071-01 SunOS 5.9: memory leak in llc1_ioctl() 117171-17 SunOS 5.9: Kernel Patch 117114-02 CDE 1.5: sdtwebclient patch 116453-02 SunOS 5.9: sadmind patch 115683-03 SunOS 5.9: Header files Patch 112810-06 CDE 1.5: dtmail patch 116538-03 SunOS 5.9: SUNW_disk_link.so Patch 112926-06 SunOS 5.9: smartcard Patch 116774-03 SunOS 5.9: ping patch 117455-01 SunOS 5.9: in.rwhod Patch 113096-03 X11 6.6.1: OWconfig patch 112834-06 SunOS 5.9: patch scsi 112912-01 SunOS 5.9: libinetcfg Patch 116105-05 X11 6.6.1: Freetype patch 117203-05 X11 6.6.1: fontconfig patch 116532-03 SunOS 5.9: mpt Patch 117201-09 X11 6.6.1: st patch 117459-01 SunOS 5.9: routing socket module Patch 114332-23 SunOS 5.9: c2audit & *libbsm.so.1 Patch 118300-02 X11 6.6.1: libXpm patch 112811-02 OpenWindows 3.7.0: Xview Patch 117445-01 SunOS 5.9: newgrp patch 119433-01 SunOS 5.9: telnet 117485-01 SunOS 5.9: fn_ctx_x500.so.1 Patch 112965-05 SunOS 5.9: patch /kernel/drv/sparcv9/eri 112921-07 SunOS 5.9: libkadm5 Patch 112925-06 SunOS 5.9: ktutil kdb5_util kadmin kadmin.local kadmind Patch 114219-11 CDE 1.5: sdtimage patch 114014-10 SunOS 5.9: libxml, libxslt and Freeware man pages Patch 114363-03 SunOS 5.9: sort Patch 113280-06 SunOS 5.9: patch /usr/bin/cpio 113798-02 CDE 1.5: libDtSvc patch 116489-01 SunOS 5.9: ttymux Patch 116494-01 SunOS 5.9: libdevice Patch 116559-01 SunOS 5.9: powerd pmconfig patch 117162-01 SunOS 5.9: patch usr/src/uts/common/sys/cpc_impl.h 117477-01 SunOS 5.9: vol Patch 117418-01 SunOS 5.9: consms patch 119449-01 SunOS 5.9: Perl Patch 112874-34 SunOS 5.9: libc patch 113319-24 SunOS 5.9: libnsl, nispasswdd patch 114503-14 SunOS 5.9: usr/sadm/lib/usermgr/VUserMgr.jar Patch 116807-02 SunOS 5.9: /usr/sadm/lib/smc/lib/preload/jsdk21.jar patch 112970-09 SunOS 5.9: patch libresolv 113322-03 SunOS 5.9: uucp patch 115158-10 X11 6.6.1: xscreensaver patch 112540-26 SunOS 5.9: Expert3D IFB Graphics Patch 113451-11 SunOS 5.9: IKE patch 113329-17 SunOS 5.9: lp Patch 112963-25 SunOS 5.9: linker Patch 116548-05 SunOS 5.9: ufsboot Patch 116502-03 SunOS 5.9: mountd Patch 120240-01 SunOS 5.9: ps cmd patch 112808-09 CDE1.5: Tooltalk patch 121996-01 SunOS 5.9: S9 perl 5.005_03`s CGI.pm and Safe.pm modules Patch 112601-10 SunOS 5.9: PGX32 Graphics 116047-03 SunOS 5.9: hsfs Patch 121321-03 SunOS 5.9: ldap Patch 118335-05 SunOS 5.9: sockfs Patch 118305-08 SunOS 5.9: tcp Patch 118535-03 SunOS 5.9: sh/jsh/rsh/pfsh Patch 115677-02 SunOS 5.9: usr/lib/ldap/idsconfig Patch 113225-04 SunOS 5.9: Timezone commands and zoneinfo database update Patch 113277-47 SunOS 5.9: st, sd and ssd drivers patch 112764-09 SunOS 5.9: Sun Quad FastEthernet qfe driver 116527-02 SunOS 5.9: timod Patch 121194-01 SunOS 5.9: usr/lib/nfs/statd Patch 114128-03 SunOS 5.9: sd_lun patch 112960-39 SunOS 5.9: ldap library Patch 112785-56 X11 6.6.1: Xsun patch 114564-09 SunOS 5.9: /usr/sbin/in.ftpd Patch 119211-09 NSS_NSPR_JSS 3.11.2: NSPR 4.6.2 / NSS 3.11.2 / JSS 4.2.4 112954-14 SunOS 5.9: uata Driver Patch 118558-30 SunOS 5.9: Kernel Patch 113579-09 SunOS 5.9: ypserv/ypxfrd patch 123056-01 SunOS 5.9: ldterm patch 114344-21 SunOS 5.9: arp, dlcosmk, ip, and ipgpc Patch 112661-10 SunOS 5.9: IIIM and X Input & Output Method patch 113077-18 SunOS 5.9: su driver patch 113146-07 SunOS 5.9: Apache Security Patch 113318-26 SunOS 5.9: NFS patch 112807-18 CDE 1.5: dtlogin patch 117124-12 SunOS 5.9: platmod, drmach, dr, ngdr, & gptwocfg Patch 111711-16 SunOS 5.9: 32-bit Shared library patch for C++ 112817-29 SunOS 5.9: Sun GigaSwift Ethernet 1.0 driver patch 116561-13 SunOS 5.9: Volume System H/W Series platmod patch 111712-16 SunOS 5.9: 64-Bit Shared library patch for C++ 113072-08 SunOS 5.9: patch /usr/sbin/format 114538-37 SunOS 5.9: Sun XVR-100 Graphics Accelerator Patch 113273-11 SunOS 5.9: /usr/lib/ssh/sshd Patch 114356-08 SunOS 5.9: /usr/bin/ssh Patch 113575-07 SunOS 5.9: sendmail Patch 113278-15 SunOS 5.9: NFS Daemon, rpcmod Patch 116669-20 SunOS 5.9: md Patch 114555-32 SunOS 5.9: Sun XVR-1200 and Sun XVR-600 Graphics Accelerator Patch 114731-09 SunOS 5.9: glm driver patch 115553-22 SunOS 5.9: USB Drivers and Framework Patch 112945-42 SunOS 5.9: wbem Patch 117480-01 SunOS 5.9: pkgadd Patch 117471-03 SunOS 5.9: fifofs 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 ./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 Determining if sufficient save space exists... Sufficient save space exists, continuing... Installing patches located in Installing Installing . . . Installing For more installation messages refer to the installation logfile: /var/sadm/install_data/_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/_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!!