CLUSTER_README NAME: Solaris 10 x86 Recommended Patch Cluster DATE: Feb/24/09 INTENT: ------- This patch cluster provides a recommended set of patches for the Solaris 10 release for x86 based systems. An installation script to install the patch cluster is included. The CLUSTER_README notes and installation instructions contain important information. Read the notes and instructions before installing this patch cluster. CLUSTER DESCRIPTION: -------------------- The Solaris Recommended Patch Cluster contains the following patches: 1. The latest revision of the patch and package utility patches that ensure correct patching operations. 2. The latest revision of any patch that addresses a SunAlert issue. These are patches which fix a Security, Data Corruption, or Availability issue. 3. Any patch that is required to correctly install the above patches. When new patches are released that meet the above criteria, the Solaris Recommended Patch Cluster is updated. If a patch is withdrawn from release due to problems, the patch cluster is also updated. The withdrawn patches are removed from the cluster. ************** CAUTION:************** The cluster installation script may need to be invoked up to three times if patching an active boot environment, depending on the patch level of the target system. If this patch cluster is applied to an active boot environment that is running a kernel at a patch level below 118844-19, the cluster installation script will need to be invoked three times. Three reconfiguration reboots ('reboot -- -r') are required: one reboot after each invocation of the installation script. If this patch cluster is applied to an active boot environment that is running a kernel at a patch level below 118855-36, the cluster installation script will need to be invoked twice. Two reconfiguration reboots are required: one reboot after each invocation of the installation script. If you use Solaris Live Upgrade or the "-R" option to the cluster install script to patch an inactive boot environment, then the need for multiple reboots and most special instructions can be avoided. See below for further details. The cluster install script asks for a password. This is a safety device to ensure you have read this README. You must follow the Special Install Instructions for key patches such as those highlighted in this README. These instructions specify the steps necessary to patch an active boot environment. ************************************* PASSCODE: dapku PATCHES INCLUDED: ----------------- 124205-05 SunOS 5.10_x86: zfs patch 122661-08 SunOS 5.10_x86: zones patch 118844-20 SunOS 5.10_x86: kernel Patch 120720-02 SunOS 5.10_x86: SunFreeware gzip patch 121297-01 SunOS 5.10_x86: fgrep patch 126869-03 SunOS 5.10_x86: SunFreeware bzip2 patch 122035-05 SunOS 5.10_x86: awk nawk Patch 118344-14 SunOS 5.10_x86: Fault Manager Patch 118919-21 SunOS 5.10_x86: Solaris Crypto Framework patch 120901-03 SunOS 5.10_x86: libzonecfg patch 121334-04 SunOS 5.10_x86: zoneadmd, zlogin and zoneadm patch 123840-04 SunOS 5.10_x86: Fault Manager Patch 127756-01 SunOS 5.10_x86: Fault Manager patch 117435-02 SunOS 5.10_x86: biosdev patch 121264-01 SunOS 5.10_x86: cadp160 driver patch 126420-01 SunOS 5.10_x86: umountall patch 119575-02 SunOS 5.10_x86: su patch 125548-02 SunOS 5.10_x86: zoneadm indirect dependency patch 119255-64 SunOS 5.10_x86: Install and Patch Utilities Patch 113000-07 SunOS 5.10_x86: SUNWgrub patch 138218-01 SunOS 5.10_x86: svccfg & svcprop patch 126539-02 SunOS 5.10_x86: i.manifest and r.manifest patch 118855-36 SunOS 5.10_x86: kernel patch 126424-03 SunOS 5.10_x86: bootadm patch 120273-24 SunOS 5.10_x86: SMA patch 122641-06 SunOS 5.10_x86: zfs genesis patch 125504-02 SunOS 5.10_x86: package-move-of-IP-objects patch 120012-14 SunOS 5.10_x86: kernel patch 127128-11 SunOS 5.10_x86: kernel patch 119758-14 SunOS 5.10_x86: Samba patch 119318-01 SunOS 5.10_x86: SVr4 Packaging Commands (usr) Patch 123612-05 X11 6.6.2_x86: Trusted Extensions patch 126366-14 SunOS 5.10_x86: CDE Desktop changes - Solaris Trusted Extensions 120740-05 GNOME 2.6.0_x86: GNOME PDF Viewer based on Xpdf 123591-09 SunOS 5.10_x86: PostgresSQL patch 128412-01 SunOS 5.10_x86: vuidm patch 125542-03 Mozilla 1.7_x86: Mozilla Thunderbird email client 119060-45 X11 6.6.2_x86: Xsun patch 121976-01 CDE 1.6_x86: Xsession patch 120411-30 SunOS 5.10_x86: Internet/Intranet Input Method Framework patch 120415-23 SunOS 5.10_x86: Asian CCK locales patch 138182-01 SunOS 5.10_x86: ike.preshared patch 120202-06 X11 6.8.0_x86: Xorg client libraries patch 119082-25 SunOS 5.10_x86: CD-ROM Install Boot Image Patch 121212-02 SunOS 5.10_x86: Sun Java Web Console (Lockhart) Patch 122912-15 SunOS 5.10_x86: Apache 1.3 Patch 125556-02 SunOS 5.10_x86: patch behavior patch 138867-02 SunOS 5.10_x86: sharetab patch 138884-01 SunOS 5.10_x86: GRUB patch 137138-09 SunOS 5.10_x86: kernel patch 137122-06 SunOS 5.10_x86: e1000g driver patch 124445-01 SunOS 5.10_x86: mountd patch 126541-02 SunOS 5.10_x86: libumem library patch 136999-05 SunOS 5.10_x86: PostgreSQL 8.2 core patch 125333-04 JDS 3_x86: Macromedia Flash Player Plugin Patch 137872-02 SunOS 5.10_x86: tk patch 138276-01 SunOS 5.10_x86: cpio patch 119765-06 SunOS 5.10_x86: ipmitool patch 123614-01 X11 6.6.2_x86: OpenGL patch 125720-25 X11 6.8.0_x86: Xorg server patch 138362-01 SunOS 5.10_x86: snmpXdmid patch 119811-05 SunOS 5.10_x86: International Components for Unicode Patch 119214-17 NSS_NSPR_JSS 3.11.9_x86: NSPR 4.7 / NSS 3.11.9 / JSS 4.2.6 125540-05 Mozilla 1.7_x86: Mozilla Firefox Web browser 120330-02 SunOS 5.10_x86: rexec patch 137128-05 SunOS 5.10_x86: md and lib/libmeta.so.1 patch 118669-18 JavaSE for business 5.0_x86: update 17 patch (equivalent to JDK 5.0u17), 64bit 138323-02 SunOS 5.10_x86: Perl patch 120223-30 SunOS 5.10_x86: Emulex-Sun LightPulse Fibre Channel Adapter driver 124629-10 SunOS 5.10_x86: CD-ROM Install Boot Image Patch 119253-30 SunOS 5.10_x86: System Administration Applications Patch 120200-14 SunOS 5.10_x86: sysidtool Patch 124631-20 SunOS 5.10_x86: System Administration Applications, Network, and Core Libraries Patch 128001-01 SunOS 5.10_x86: in.ftpd patch 121395-02 SunOS 5.10_x86: kaio and aio_impl.h patch 124189-02 SunOS 5.10_x86: Trusted Solaris Attributes Patch 121309-16 SunOS 5.10_x86: Solaris Management Console Patch 119314-26 SunOS 5.10_x86: WBEM Patch 138270-02 SunOS 5.10_x86: devfs patch 119901-06 GNOME 2.6.0_x86: Gnome libtiff - library for reading and writing TIFF Patch 140775-02 SunOS 5.10_x86: sshd patch 137081-01 SunOS 5.10_x86: libpng Patch 138857-02 SunOS 5.10_x86: Timezone commands and zoneinfo database update Patch 138624-02 SunOS 5.10_x86: usr/bin/pax patch 118960-03 SunOS 5.10_x86: patch usr/bin/acctcom and usr/bin/lastcomm 140384-01 SunOS 5.10_x86: ptsl patch 128329-01 SunOS 5.10_x86: usbms patch 138264-03 SunOS 5.10_x86: nscd patch 136840-01 Service Tags SunOS 5.10_x86 139100-01 SunOS 5.10_x86: gtar patch 121013-02 SunOS 5.10_x86: traceroute patch 119116-34 Mozilla 1.7_x86 patch 138628-05 SunOS 5.10_x86: printing patch 124458-01 X11 6.6.2_x86: xdm patch 139561-01 SunOS 5.10_x86: autofs patch 123896-05 SunOS 5.9_x86 5.10_x86: Common Agent Container (cacao) runtime 2.2.0.1 upgrade patch 05 119784-10 SunOS 5.10_x86: bind patch 124998-01 SunOS 5.10_x86: /usr/bin/tip patch 119131-33 SunOS 5.10_x86: Sun Fibre Channel Device Drivers 125165-12 SunOS 5.10_x86: Qlogic ISP Fibre Channel Device Driver 119091-32 SunOS 5.10_x86: Sun iSCSI Device Driver and Utilities 138877-01 SunOS 5.10_x86: usr/lib/inet/in.dhcpd patch 138224-03 SunOS 5.10_x86: cron patch 138882-02 SunOS 5.10_x86: SUNW_md_link.so patch 138242-04 SunOS 5.10_x86: svccfg & svcprop patch 139482-01 SunOS 5.10_x86: rpc.ypupdated patch 126207-04 SunOS 5.10_x86: zebra ripd quagga patch 120236-01 SunOS 5.10_x86: Live Upgrade Zones Support Patch 121454-02 SunOS 5.10_x86: Sun Update Connection Client Foundation 140145-01 SunOS 5.10_x86: ldap_cachemgr patch 138266-01 SunOS 5.10_x86: picld patch 138105-01 SunOS 5.10_x86: snoop patch 127854-02 SunOS 5.10_x86: sad driver patch 138374-02 SunOS 5.10_x86: fifofs patch 120095-21 X11 6.6.2_x86: xscreensaver patch 137033-01 SunOS 5.10_x86: namefs patch 120413-09 SunOS 5.10_x86: Simplified Chinese locale patch 125185-10 SunOS 5.10_x86: Sun Fibre Channel Device Drivers 119813-08 X11 6.6.2_x86: Freetype patch 139580-02 SunOS 5.10_x86: zfs Patch 125953-18 Sun Java Web Console 3.1[_x86] 139501-02 SunOS 5.10_x86: openssl patch 120293-02 SunOS 5.10_x86 : mysql patch 123939-01 GNOME 2.6.0_x86: GNU Transport Layer Security Library Patch 139484-04 SunOS 5.10_x86: ufs patch 119247-34 SunOS 5.10_x86: Manual Page updates for Solaris 10 124394-09 CDE 1.6_x86: Dtlogin smf patch 137094-01 SunOS 5.10_x86: logindevperm patch 140456-01 X11 6.6.2_x86: VNC Viewer patch 138889-03 SunOS 5.10_x86: Kernel Patch 136883-02 SunOS 5.10_x86: ImageMagick patch 121096-02 GNOME 2.6.0_x86: GNOME EXIF tag parsing library for digital cameras 124939-03 SunOS 5.10 5.10_x86: JDMK 5.1 patch 119987-03 SunOS 5.10_x86: clri patch 137322-01 SunOS 5.10_x86: p7zip patch 138372-05 SunOS 5.10_x86: mech_krb5.so.1 patch 118668-18 JavaSE for business 5.0_x86: update 17 patch (equivalent to JDK 5.0u17) 139467-04 SunOS 5.10_x86: nfs patch 119904-02 Openwindows 3.7.3_x86: Xview Patch 122213-30 GNOME 2.6.0_x86: GNOME Desktop Patch 120831-06 SunOS 5.10_x86: vi and ex patch 120544-14 SunOS 5.10_x86: Apache 2 Patch 125732-04 SunOS 5.10_x86: XML and XSLT libraries patch 126364-07 SunOS 5.10_x86: X Window System changes - Solaris Trusted Extensions 121119-15 SunOS 5.10_x86: Sun Update Connection System Client 1.0.10 126441-01 SunOS 5.10_x86: rm patch 138254-02 SunOS 5.10_x86: /sbin/sh patch 125280-05 CDE1.6_x86: dtsession patch IMPORTANT NOTES AND WARNINGS: ----------------------------- SYSTEMS WITH LIMITED DISK SPACE SHOULD *NOT* INSTALL PATCHES: Whether you use the 'patchadd' command's default save option to store backout data or not, the patch installation process still requires disk space for installation and administrative tasks. The disk space is needed in the /, / usr, /var, or /opt directories where patches are typically installed. The exact amount of space depends on the system's architecture, the software packages already installed, and the difference in the patched objects size. Caution: Before installing the patch cluster, check to ensure adequate disk space is available. To be safe, do not install a patch cluster on a system with less than 100 MBytes of available space in each of these directories. Running out of disk space during the installation might result in only partially applied patches. In case a problem occurs, ensure a recent full system backup is available. SAVE AND BACKOUT OPTIONS: By default, the cluster installation script uses the patchadd command's save feature to save a copy of the objects being patched. This is the recommended option. Patches can only be removed and the original objects restored if the default save option was used when installing this cluster. You can 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 the patches. Failure to save backout data could cause difficulty to recover from a patching problem. For systems running a Kernel at a patch level below 118855-36, use of the '- nosave' option with the install cluster script must not be used unless a workaround or fix to a known bug is first applied. See 118855-36 README, Special Install Instruction, NOTE 61. See the "CLUSTER INSTALLATION INSTRUCTIONS:" section below for further details. SPECIAL INSTALL INSTRUCTIONS: As with any patch individually applied, there might be additional Special Install Instructions. These instructions are documented in the individual patch README file. To determine if any additional installation steps are necessary, read each patch README before installing this cluster. DISKLESS CLIENT SYSTEMS: On server systems that service diskless clients, a patch is not applied to existing clients or to the client root template space. Therefore, all client systems of the server that need this cluster will have to individually apply this cluster. Install this cluster on the client systems first, then the server. A PATCH MAY NOT BE APPLIED: Some of the patches in the patch cluster might not install on particular systems. The following are examples of when a patch might not install. These situations are normal and are not a cause for concern. The patches might patch packages that: - Are only installed on specific hardware. - Were introduced in a later Solaris Update release than the release installed on the target system. - Are not present in the installation Software Group (metacluster) that was installed on the target system. - Have been deliberately removed from the target system during system hardening. The patch utilities recognize packages that have a patch applied and only patch those packages to which the patch has not already been applied. Therefore, if a patch patches several packages and only some of them are present on the target system, then those packages present are patched. If other packages are installed on the system at a later date, then patches for those packages need to be reapplied. OLDER VERSIONS OF PATCHES ALREADY INSTALLED: Backing out older versions of patches provided in the patch cluster is not required for the newer version to be installed. INSTALL INSTRUCTIONS: --------------------- This patch cluster can be installed on either the currently running boot environment or on an inactive boot environment. The patch cluster can be installed on an inactive boot environment using either Solaris Live Upgrade or the "-R" option to the cluster install-script command. Patching an inactive boot environment is recommended, because the downtime associated with patching is reduced and there's a simple fallback option if needed: reboot back into the original boot environment. Patching an inactive boot environment removes the need to follow most patch Special Install Instructions that would be required if you patched an active boot environment. The three installation options are described in the following sections. I. Installing This Patch Cluster By Using Solaris Live Upgrade To patch an inactive boot environment by using Solaris Live Upgrade, first ensure that the currently running boot environment has the patches specified in Infodoc 72099 installed. Infodoc 72099 is available from sunsolve.sun.com. When applying patches to an inactive boot environment by using Solaris Live Upgrade, you do not need to bring the running boot environment to single user mode. The following command applies this patch cluster to the inactive boot environment that was previously created. The patch_order file that is included in this cluster provides the list of patches in the correct order to install the cluster. luupgrade -n \ -s \ -t `cat patch_order` For more information on Solaris Live Upgrade, see http://docs.sun.com/app/docs/ doc/820-0178. II. Installing This Patch Cluster to an Inactive Boot Environment by Using the -R Option This cluster can also be installed on an inactive boot environment by using the '-R ' option when running the cluster install script. You specify the path name of the root (/) file system of the inactive boot environment as an option to the install_cluster script. Follow the installation instructions in the "CLUSTER INSTALLATION INSTRUCTIONS" section below. III. Installing This Patch Cluster To an Active Boot Environment The following special warnings apply if this patch cluster is applied to an active boot environment: 1. The installation should be performed in single-user mode (run level S). 2. If the active boot environment is running a Kernel at a patch level below 118844-19, the cluster installation script needs to be invoked THREE times, with a reconfiguration reboot ('reboot -- -r') after each invocation. The first reconfiguration reboot is necessary to ensure patch 118844-19 or higher is active on the running boot environment. This is required to ensure compatibility with library changes provided in subsequent patches. Patch 118844-20 is provided in the patch cluster. The reconfiguration reboot after the first invocation of the cluster installation script brings the active boot environment kernel to the 118844-20 patch level. 3. The patch cluster installs the GNU GRand Unified Bootloader (GRUB) architecture if the active boot environment is running at a Kernel patch level below 118844-21. Caution: Please follow the appropriate system specific instructions specified in SunAlert http://sunsolve.sun.com/search/document.do? assetkey=1-26-102087-01 . Failure to follow these instructions might result in the system failing to boot. 4. If the active boot environment is running a Kernel at a patch level of 118844-19 or above but below a patch level of 118855-36, the cluster install script needs to be invoked TWICE with a reconfiguration reboot ('reboot -- -r') after each invocation. The two reconfiguration reboots are necessary because no more patches can be applied after installing patch 118855-36 until the system is rebooted. All subsequent patches in this patch cluster will fail to install until the system is rebooted. To complete the patch cluster installation, perform a reconfiguration reboot of the system and then invoke the cluster install script again. Kernel patch 118855-36 is the kernel patch associated with the Solaris 10 11/06 release (Solaris 10 Update 3). This patch delivers a significant amount of code change. Some manual steps might be required in order to safely apply this patch. Please carefully review the Special Install Instructions in the 118855-36 patch README. 5. If the target system is running a Kernel at a patch level below 120012-14, all non-global zones must be halted before 120012-14 can be applied. (In the output of 'zoneadm list -cv,' halted zones are shown as being in the 'installed' state.) Kernel patch 120012-14 is the kernel patch associated with the Solaris 10 08/07 release (Solaris 10 Update 4). Please carefully review the Special Install Instructions in the 120012-14 patch README. Kernel patch 120012-14 is the first patch to utilize the "deferred activation patching" functionality. Such patches set the SAFEMODE parameter in their pkginfo file or files. Deferred activation patching support was introduced in patch utility patch 119255-42 to ensure system consistency during patching of an active boot environment. Deferred activation patching utilizes loopback mounts (lofs) to mask the patched objects until a reboot is performed. Deferred activation patching is designed to enable subsequent patches to be applied before the reboot is initiated. If any subsequent patch directly or indirectly requires a patch installed in deferred activation patching mode, the patch will also automatically be installed in deferred activation patching mode by the patchadd command. Objects updated using deferred activation patching will be activated upon reboot of the system. CLUSTER INSTALLATION INSTRUCTIONS: 1. If the cluster was received as a .zip file, make sure the patch cluster has been unzipped. 2. Decide if you want to save backout data so that patches can be removed at a later date. By default, the cluster installation script uses the patchadd command's save feature to save a copy of the objects being patched. This is the recommended option. Patches can only be removed and the original objects restored if the default save option was used when installing this cluster. You can 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 the patches. Failure to save backout data could cause difficulty to recover from a patching problem. For systems running a Kernel at a patch level below 118855-36, use of the '- nosave' option with the install cluster script must not be used unless a workaround or fix to a known bug is first applied. See 118855-36 README, Special Install Instruction, NOTE 61. Caution: The cluster installation script will terminate if disk space is insufficient. Prior to installing the patches, the cluster installation script attempts to determine if enough disk space is available for /var/sadm/patch to save the objects to be patched. 3. Run the install_cluster script. cd ./install_cluster [-q] [-nosave] [-R ] - By default, a message warning you to check for minimum disk space allowance displays. This warning is separate from the save feature. If inadequate space exists, the script enables the user to abort. To suppress this interactive message, the "-q" (quiet) option can be used when invoking the install_cluster command. - The -nosave option is explained in step 2. - The -R option is explained in section "II. Installing This Patch cluster to an Inactive Boot Environment by Using the -R Option." 4. Enter the password: dapku The cluster install script asks for a password. This is a safety device to ensure you have read this README. You must follow the Special Install Instructions for key patches such as those highlighted above. These instructions provide the requirements when patching an active boot environment. The progress of the script is displayed on your terminal. The output should look similar to the following: Patch cluster install script for Solaris 10_x86 Recommended Patch Cluster Special handling may be required for some of the patches in this cluster. Please refer to the CAUTION section in the cluster README for further instructions on how to proceed. This section also contains a passcode that will need to be provided below to allow the install_cluster script to continue running. Please enter passcode: Determining if sufficient save space exists... Sufficient save space exists, continuing... Installing patches located in patch_order file in /export/10_x86_Recommended Using /export/10_x86_Recommended/patch_order file for patch installation sequence Installing 120720-02... Installation of 120720-02 succeeded. Return code 0. Installing 121297-01... Installation of 121297-01 succeeded. Return code 0. Installing 122035-05... Installation of 122035-05 succeeded. Return code 0. Installing 118873-04... Installation of 118873-04 succeeded. Return code 0. Installing 120901-03... Installation of 120901-03 succeeded. Return code 0. Installing 121334-04... Installation of 121334-04 succeeded. Return code 0. Installing 119255-44... Installation of 119255-44 succeeded. Return code 0. Installing 119043-10... Installation of 119043-10 succeeded. Return code 0. Installing 126539-01... Installation of 126539-01 succeeded. Return code 0. Installing 118344-14... Installation of 118344-14 succeeded. Return code 0. Installing 118919-21... Installation of 118919-21 succeeded. Return code 0. Installing 119575-02... Installation of 119575-02 succeeded. Return code 0. Installing 123840-04... Installation of 123840-04 succeeded. Return code 0. Installing 125370-05... Installation of 125370-05 succeeded. Return code 0. Installing 126420-01... Installation of 126420-01 succeeded. Return code 0. Installing 117435-02... Installation of 117435-02 succeeded. Return code 0. Installing 121264-01... Installation of 121264-01 succeeded. Return code 0. Installing 113000-07... Installation of 113000-07 succeeded. Return code 0. Installing 120273-15... Installation of 120273-15 failed. Return code 2. Installing 122641-06... Installation of 122641-06 failed. Return code 2. Installing 124205-05... Installation of 124205-05 failed. Return code 2. Installing 122661-08... Installation of 122661-08 failed. Return code 2. Installing 125548-02... Installation of 125548-02 failed. Return code 15. Installing 125504-02... Installation of 125504-02 failed. Return code 2. Installing 126424-03... Installation of 126424-03 failed. Return code 2. Installing 119318-01... Installation of 119318-01 succeeded. Return code 0. Installing 118844-20... Installation of 118844-20 succeeded. Return code 0. Installing 118855-36... Installation of 118855-36 failed. Return code 15. Installing 118561-02... Installation of 118561-02 succeeded. Return code 0. Installing 120293-01... Installation of 120293-01 succeeded. Return code 0. Installing 120330-02... Installation of 120330-02 succeeded. Return code 0. Installing 121005-03... Installation of 121005-03 succeeded. Return code 0. Installing 124189-02... Installation of 124189-02 succeeded. Return code 0. Installing 118960-03... Installation of 118960-03 succeeded. Return code 0. Installing 124998-01... Installation of 124998-01 succeeded. Return code 0. Installing 119904-02... Installation of 119904-02 succeeded. Return code 0. Installing 121013-02... Installation of 121013-02 succeeded. Return code 0. Installing 121003-03... Installation of 121003-03 succeeded. Return code 0. Installing 124458-01... Installation of 124458-01 succeeded. Return code 0. Installing 122078-03... Installation of 122078-03 succeeded. Return code 0. Installing 122912-07... Installation of 122912-07 succeeded. Return code 0. Installing 119765-06... Installation of 119765-06 succeeded. Return code 0. Installing 120223-21... Installation of 120223-21 failed. Return code 8. Installing 125280-03... Installation of 125280-03 succeeded. Return code 0. Installing 123591-06... Installation of 123591-06 failed. Return code 8. Installing 119060-30... Installation of 119060-30 succeeded. Return code 0. Installing 119813-06... Installation of 119813-06 succeeded. Return code 0. Installing 126441-01... Installation of 126441-01 succeeded. Return code 0. Installing 125379-02... Installation of 125379-02 succeeded. Return code 0. Installing 125419-01... Installation of 125419-01 succeeded. Return code 0. Installing 119247-27... Installation of 119247-27 succeeded. Return code 0. Installing 126541-02... Installation of 126541-02 succeeded. Return code 0. Installing 126259-03... Installation of 126259-03 succeeded. Return code 0. Installing 120095-13... Installation of 120095-13 succeeded. Return code 0. Installing 126449-04... Installation of 126449-04 failed. Return code 8. Installing 121309-11... Installation of 121309-11 succeeded. Return code 0. Installing 124445-01... Installation of 124445-01 succeeded. Return code 0. Installing 123614-01... Installation of 123614-01 succeeded. Return code 0. Installing 119784-05... Installation of 119784-05 succeeded. Return code 0. Installing 121454-02... Installation of 121454-02 succeeded. Return code 0. Installing 119987-03... Installation of 119987-03 failed. Return code 2. Installing 119082-25... Installation of 119082-25 failed. Return code 2. Installing 119131-33... Installation of 119131-33 failed. Return code 2. Installing 125720-12... Installation of 125720-12 succeeded. Return code 0. Installing 121119-13... Installation of 121119-13 succeeded. Return code 0. Installing 126254-02... Installation of 126254-02 failed. Return code 2. Installing 125483-03... Installation of 125483-03 failed. Return code 2. Installing 125423-01... Installation of 125423-01 failed. Return code 2. Installing 126422-01... Installation of 126422-01 failed. Return code 2. Installing 127751-01... Installation of 127751-01 failed. Return code 2. Installing 125185-04... Installation of 125185-04 failed. Return code 2. Installing 126662-02... Installation of 126662-02 failed. Return code 2. Installing 125205-06... Installation of 125205-06 failed. Return code 2. Installing 120236-01... Installation of 120236-01 succeeded. Return code 0. Installing 122175-03... Installation of 122175-03 failed. Return code 2. Installing 125197-05... Installation of 125197-05 failed. Return code 8. The following patches were able to be installed: 120720-02 121297-01 122035-05 118873-04 120901-03 121334-04 119255-44 119043-10 126539-01 118344-14 118919-21 119575-02 123840-04 125370-05 126420-01 117435-02 121264-01 113000-07 119318-01 118844-20 118561-02 120293-01 120330-02 121005-03 124189-02 118960-03 124998-01 119904-02 121013-02 121003-03 124458-01 122078-03 122912-07 119765-06 125280-03 119060-30 119813-06 126441-01 125379-02 125419-01 119247-27 126541-02 126259-03 120095-13 121309-11 124445-01 123614-01 119784-05 121454-02 125720-12 121119-13 120236-01 ERROR: The following patches were not able to be installed: 120273-15 122641-06 124205-05 122661-08 125548-02 125504-02 126424-03 118855-36 120223-21 123591-06 126449-04 119987-03 119082-25 119131-33 126254-02 125483-03 125423-01 126422-01 127751-01 125185-04 126662-02 125205-06 122175-03 125197-05 For more installation messages refer to the installation logfile: /var/sadm/install_data/Solaris_10_x86_Recommended_Patch_Cluster_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. 5. If errors are encountered during the installation of this cluster, error messages are displayed during installation. More details about the causes of failure can be found in the logfile: /var/sadm/install_data/_log If this log file previously existed, the latest cluster installation data is appended to the file. Check the end of the file for the latest log information. The individual patch logfiles can also be inspected under /var/sadm/patch/ /log. 6. Reboot the system. To activate an inactive boot environment, a reboot is needed. This reboot is needed if you are using either Solaris Live Upgrade or the -R option to the installation cluster script. If patching an active boot environment, a reconfiguration reboot ('reboot -- - r') is needed to activate certain objects which have been patched, such as the Kernel. After installation to an active boot environment, some patches specify in their README file that a reboot or reconfiguration reboot is required. Some of these patches specify that a reboot must occur immediately after the patch is installed on an active boot environment. If the target system is running a Kernel at a patch level below 120012-14, the active boot environment is in an inconsistent state after applying such patches until the reboot is performed. For example, a patch could deliver new kernel binaries and a new library. After the new kernel binaries are installed on the active boot environment, the kernel binaries are still inactive, because they will not be loaded until the system is rebooted. The new library might contain interface or behavior changes that depend on the new kernel. For systems running a Kernel at a patch level below 120012-14, the new library could be linked and invoked at any point after the library is installed in the file system. This can result in an inconsistent system state, which could potentially lead to serious problems. Generally, you can complete patching operations before initiating the reboot, but normal operations should not be resumed until the reboot is performed. Some patches, such as 118855-36, require a reconfiguration reboot when applied to an active boot environment before further patches can be applied. The instruction is specified in the Special Install Instructions section of the Patch README. As an added safety mechanism, such patches typically contain code to prevent further patching until the reboot is performed. As mentioned above, Kernel patch 120012-14 is the first patch to utilize the "deferred activation patching" functionality. Such patches set the SAFEMODE parameter in their pkginfo file or files. Deferred activation patching support was introduced in patch utility patch 119255-42 to ensure system consistency during patching of an active boot environment. Deferred activation patching utilizes loopback mounts (lofs) to mask the patched objects until a reboot is performed. Deferred activation patching is designed to enable subsequent patches to be applied before the reboot is initiated. If any subsequent patch directly or indirectly requires a patch installed in deferred activation patching mode, the patch will also automatically be installed in deferred activation patching mode by the patchadd command. Objects updated using deferred activation patching will be activated upon reboot of the system.