# CLUSTER_README NAME: 9_x86 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 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: ----------------- 113996-02 SunOS 5.9_x86: utmp_update Patch 113924-02 X11 6.6.1_x86: security font server patch 113986-13 SunOS 5.9_x86: linker Patch 114136-01 SunOS 5.9_x86: at utility Patch 112234-12 SunOS 5.9_x86: Kernel Patch 114134-02 SunOS 5.9_x86: mail Patch 114343-07 SunOS 5.9_x86: ksh patch 114565-04 SunOS 5.9_x86: /usr/sbin/in.ftpd Patch 114137-04 SunOS 5.9_x86: sendmail Patch 114009-01 SunOS 5.9_x86: cachefsd Patch 114568-17 SunOS 5.9_x86: usr/sadm/install/bin/pkginstall Patch 114714-02 SunOS 5.9_x86: newtask Patch 114722-05 SunOS 5.9_x86: ufsrestore and ufsdump Patch 114685-02 SunOS 5.9_x86: samba Patch 114193-19 SunOS 5.9_x86: wbem Patch 114862-01 SunOS 5.9_x86: /usr/sbin/wall Patch 114273-03 SunOS 5.9_x86: Sun ONE Directory Server 5.1 patch 114730-01 SunOS 5.9_x86: /usr/sbin/in.telnetd Patch 114243-09 SunOS 5.9_x86: st driver 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 115159-06 X11 6.6.1_x86: xscreensaver patch 114858-08 SunOS 5.9_x86: usr/lib/ssh/sshd Patch 114972-02 SunOS 5.9_x86: usr/kernel/fs/namefs Patch 115755-02 SunOS 5.9_x86: zlib security Patch 116046-05 SunOS 5.9_x86: krbv5 Patch (libkadm5srv.so.1) 116045-01 SunOS 5.9_x86: krbv5 Patch (krb5kdc) 116044-02 SunOS 5.9_x86: krbv5 Patch (kdb5_util) 115168-05 SunOS 5.9_x86: usr/lib/security/pam_krb5.so.1 Patch 114496-01 CDE 1.5_x86: dtprintinfo patch 114328-04 SunOS 5.9_x86: nss_ldap.so.1 Patch 114980-12 SunOS 5.9_x86: lp Patch 112662-04 SunOS 5.9_x86: IIIM and X Input & Output Method patch 114015-09 SunOS 5.9_x86: libxml, libxslt and Freeware man pages Patch 114017-01 SunOS 5.9_x86: tomcat security patch 114145-05 SunOS 5.9_x86: Apache Security Patch 114210-11 CDE 1.5_x86: dtlogin patch 114362-01 SunOS 5.9_x86: lofi patch 114435-07 SunOS 5.9_x86: IKE Hardware - libike 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 114355-02 SunOS 5.9_x86: sort patch 114432-17 SunOS 5.9_x86: libthread.so.1 libc 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 114242-13 SunOS 5.9_x86: passwdutil.so.1 & pam_authtok Patch 112786-33 X11 6.6.1_x86: Xsun patch 115880-01 SunOS 5.9_x86: /usr/bin/uucp Patch 117068-01 SunOS 5.9_x86: awk nawk oawk Patch 116309-01 CDE 1.5_x86: libDtHelp patch 117072-01 SunOS 5.9_x86: memory leak in llc1_ioctl() 116808-01 SunOS 5.9_x86: patch usr/sadm/lib/smc/lib/preload/jsdk21.jar 117172-12 SunOS 5.9_x86: Kernel Patch 116558-02 SunOS 5.9_x86: c2audit Patch 114345-08 SunOS 5.9_x86: arp, dlcosmk, ip, and ipgpc Patch 113870-05 CDE 1.5_x86: dtmail patch 114050-12 SunOS 5.9_x86: NSPR 4.1.6 / NSS 3.3.4.5 115690-01 SunOS 5.9_x86: /usr/lib/patch/patchutil Patch 114420-02 SunOS 5.9_x86: multi-terabyte disk support - libuuid patch 115166-05 SunOS 5.9_x86: usr/lib/libnisdb.so.2 Patch 114194-06 SunOS 5.9_x86: patchadd and patchrm Patch 113719-14 SunOS 5.9_x86: libnsl rpc.nispasswdd Patch 114342-07 SunOS 5.9_x86: ypserv/ypxfrd/rpc.yppasswdd patch 114419-04 SunOS 5.9_x86: Multiterabyte Disk Support - abi_libefi.so.1 patch 114354-06 SunOS 5.9_x86: libresolv patch 114733-13 SunOS 5.9_x86: ufs and fsck Patch 113994-25 SunOS 5.9_x86: md 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!!