# CLUSTER_README NAME: Solaris 10 Sun Alert Patch Cluster DATE: 7/27/2006 ######################################################################## 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 occurred 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 ------------------- This cluster contains the minimum set of Sun Alert patches that contribute to the concerned Solaris Release. It also contains all the required dependency patches, which may or may not be Sun Alert patches. These Sun Alert Solaris 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 particular, Sun Alert patches are to resolve issues regarding to Data Loss, Availability and Security. This cluster is updated whenever there are new Sun Alert patches or any updates to existing member patches. This cluster may contain obsoleted patches. For more information about corresponding Sun Alert notification, please reference the Sun Alert Patch Report at http://sunsolve.sun.com/pub-cgi/show.pl?target=sunalert_patches PATCHES INCLUDED: ----------------- 119254-06 Obsoleted by: 119254-09 SunOS 5.10: Install and Patch Utilities Patch 120900-04 SunOS 5.10: libzonecfg Patch 121133-02 SunOS 5.10: zones library and zones utility patch 119317-01 SunOS 5.10: SVr4 Packaging Commands (usr) Patch 119683-02 Obsoleted by: 118822-23 SunOS 5.10: lib/svc/bin/svc.configd Patch 121296-01 SunOS 5.10: fgrep Patch 118815-03 SunOS 5.10: awk patch 118872-03 SunOS 5.10: ksh patch 119254-25 SunOS 5.10: Install and Patch Utilities Patch 120719-01 SunOS 5.10 : gzip patch 119578-09 SunOS 5.10: FMA Patch 118822-19 Obsoleted by: 118822-20 SunOS 5.10: kernel Patch 119075-11 SunOS 5.10: ip Patch 120467-01 Obsoleted by: 120467-02 SunOS 5.10: lp subsystem remote file patch 118560-01 SunOS 5.10: patch usr/bin/telnet 119903-01 OpenWindows 3.7.3: Xview Patch 120469-02 SunOS 5.10: kerberos patch 119757-01 SunOS 5.10: Samba patch 118959-02 SunOS 5.10: patch usr/bin/lastcomm and usr/bin/acctcom 118996-02 SunOS 5.10: patch usr/sbin/format 120085-01 SunOS 5.10: in.ftpd patch 119593-01 SunOS 5.10: net-svc patch 118870-01 SunOS 5.10: nss_ldap patch 120292-01 SunOS 5.10 : mysql patch 120664-01 SunOS 5.10: tl driver patch 120537-01 Obsoleted by: 120537-02 SunOS 5.10: md patch 118553-02 Obsoleted by: 118553-03 SunOS 5.10: kernel/misc/sparcv9/md_mirror patch 119715-02 Obsoleted by: 119715-03 SunOS 5.10: patch kernel/drv/sparcv9/scsi_vhci 117461-04 Obsoleted by: 117461-05 SunOS 5.10: ld Patch 119689-02 Obsoleted by: 119689-03 SunOS 5.10: libc.so.1 patch 119059-08 X11 6.6.2: Xsun patch 119130-12 SunOS 5.10: Sun Fibre Channel Device Drivers 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 100 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!!