# CLUSTER_README NAME: Solaris 10_x86 Recommended Patch Cluster DATE: Sep/18/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. ************** CAUTION:************** This cluster includes a number of patches which will install a new GNU GRand Unified Bootloader (GRUB) architecture. To install these safely it is necessary to first read the Sun Alert which contains system specific instructions. The Sun Alert is located here:- http://sunsolve.sun.com/search/document.do?assetkey=1-26-102087-1 Failure to follow these system specific instructions may result in the system failing to boot. Once these preliminary precautions have been taken, the cluster may be installed. Depending upon the starting patch level of the system, the cluster install script may need to be run up to three times with a reboot after each run in order for all the patches to be installed. ************************************* PASSCODE: newboot PATCHES INCLUDED: ----------------- 120720-01 SunOS 5.10_x86 : gzip patch 121297-01 SunOS 5.10_x86: fgrep patch 122035-04 SunOS 5.10_x86: awk nawk Patch 118873-04 SunOS 5.10_x86: ksh patch 121334-04 SunOS 5.10_x86: zoneadmd, zlogin and zoneadm patch 120901-03 SunOS 5.10_x86: libzonecfg patch 119255-27 SunOS 5.10_x86: Install and Patch Utilities Patch 119318-01 SunOS 5.10_x86: SVr4 Packaging Commands (usr) Patch 120086-01 SunOS 5.10_x86: patch usr/sbin/in.ftpd 119594-01 SunOS 5.10_x86: net-svc patch 120293-01 SunOS 5.10_x86 : mysql patch 118871-01 SunOS 5.10_x86: nss_ldap patch 117435-02 SunOS 5.10_x86: biosdev patch 120236-01 SunOS 5.10_x86: Live Upgrade Zones Support Patch 118344-13 SunOS 5.10_x86: Fault Manager Patch 121127-02 SunOS 5.10_x86: umountall.sh Patch 113000-07 SunOS 5.10_x86: SUNWgrub patch 118844-30 SunOS 5.10_x86: kernel Patch 122082-01 SunOS 5.10_x86: perl format string patch 119575-02 SunOS 5.10_x86: su patch 121230-01 SunOS 5.10_x86: libssl patch 120330-02 SunOS 5.10_x86: rexec patch 121454-02 SunOS 5.10_x86: Sun Update Connection Client Foundation 122033-02 SunOS 5.10_x86: Update timezones patch 118372-07 SunOS 5.10_x86: elfsign Patch 119131-22 SunOS 5.10_x86: Sun Fibre Channel Device Drivers 119043-09 SunOS 5.10_x86: usr/sbin/svccfg patch 121264-01 SunOS 5.10_x86: cadp160 driver patch 118855-15 SunOS 5.10_x86: kernel patch 118966-24 X11 6.8.0_x86: Xorg patch 118997-10 SunOS 5.10_x86: format patch 118960-03 SunOS 5.10_x86: patch usr/bin/acctcom and usr/bin/lastcomm 119758-02 SunOS 5.10_x86: Samba patch 121309-07 SunOS 5.10_x86: Solaris Management Console Patch 119765-05 SunOS 5.10_x86: ipmitool patch 119247-15 SunOS 5.10_x86: Manual Page updates for Solaris 10 121005-02 SunOS 5.10_x86: sh patch 122078-02 SunOS 5.10_x86: NIS yp utilities patch 118919-17 SunOS 5.10_x86: Solaris Crypto Framework patch 122912-01 SunOS 5.10_x86 : Apache Patch 118563-09 SunOS 5.10_x86: Solaris Data Encryption Kit Patch 122857-03 SunOS 5.10_x86: sendmail patch 119904-02 Openwindows 3.7.3_x86: Xview Patch 119060-16 X11 6.6.2_x86: Xsun patch 121013-02 SunOS 5.10_x86: traceroute patch 120468-05 SunOS 5.10_x86: lp patch 120544-05 SunOS 5.10_x86 : Apache Patch 118561-02 SunOS 5.10_x86: usr/bin/telnet 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. SOLARIS LIVE UPGRADE: To patch a system using Solaris Live Upgrade make sure the system has the latest patchadd and Solaris Live Upgrade patches (see infodoc 72099). When applying patches to an inactive boot environment using Solaris Live Upgrade, you do not need to take the system to single user mode. Use the patch_order file included with this patch cluster, e.g., # luupgrade -n \ -s \ -t `cat patch_order` Standard Solaris testing includes applying the Recommended Patch Cluster through Solaris Live Upgrade. 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!!