README NAME: Recommended OS Patchset Solaris 10 SPARC DATE: 2013.05.

30 INTENT: ------Please see "Critical Patch Updates, Security Alerts and Third Party Bulletin", http://www.oracle.com/technetwork/topics/security/alerts-086861.html for information on security vulnerabilities. For information on Solaris, click on the relevant CPU link, and select the "Oracle Sun Product" link. Please note, the Solaris Critical Patch Updates (CPUs) are re-named, archived copies of the Recommended patchset. Subsequent versions of the Recommended patchset will be a superset of the CPU. See: https://blogs.oracle.com/patch/entry/a_solaris_recommended_patchset_to NOTE: From 2011.06.28 some core changes have been made to the Recommended OS Patchset : - The patch inclusion criteria have been extended to include patches for selected issues identified by Oracle Proactive Services and the Oracle Technical Support Center. - The term 'Patch Cluster' has been replaced by 'Patchset', and the associated rebranding has been effected. The patchset install script is now named 'installpatchset'. A symlink to 'installpatchset' is provided in place of the legacy 'installcluster' script for now, but this symlink is purely transitional and will be removed at some future point in time. Where applicable, please update infrastructure to use the 'installpatchset' script directly. - The patchset 'README' file has been renamed '10_Recommended.README'. For further information about these changes, please see: http://blogs.oracle.com/patch/entry/a_solaris_recommended_patchset_to The Recommended OS Patchset Solaris 10 SPARC provides the minimum set of patches needed to address security and Sun Alert issues, and selected issues identified by Oracle Proactive Services and the Oracle Technical Support Center, for the Solaris 10 Operating System for sparc. The patches contained in this patchset are considered the most important and highly recommended patches for Solaris 10. They provide the least amount of change required to address known security, data corruption and availability issues, as well as other functional issues that have been identified to be commonly encountered in the field. The Recommended OS Patchset comprises: 1. The latest revision of the patch and package utility patches that ensure correct patching operations. 2. The minimum revision of Solaris Operating System patches which address security and Sun Alert (data corruption and availability) issues, and selected issues identified by Oracle Proactive Services and the Oracle Technical Support Center. 3. Any patch that is required to correctly install the above patches.

When new patches are released that meet the above criteria, the patchset is updated. If a patch is withdrawn from release due to problems, the patchset is also updated. The withdrawn patches are removed from the patchset. As the patchset contains the minimum revision (as opposed to the latest available revision) of patches meeting criteria two and three above, the patchset is likely to contain some obsoleted patches. This is deliberate and not a cause for concern. The patchset can be installed to a system running Solaris 10 3/05 ("FCS") or a later Solaris 10 Update. Depending on the current patch level of the target system, installation of this patchset can involve applying a number of complex Solaris 10 patches. These complex patches may require the user to follow specific install instructions listed in the Special Install Instructions section of the patches' README files, particularly if the patches are applied to the active boot environment of a system. The key issues are also described below in this README file. The matter of applying complex patches is primarily a concern for systems which are running an early Solaris 10 Update and have not recently been patched. To avoid applying complex patches, and to get full new feature functionality, it is recommended to install or upgrade these systems using the latest Solaris 10 Update install media. Following an install or upgrade operation, it is recommended to install this patchset to ensure the system has all current patches which address security and Sun Alert issues applied, including those patches released after the latest Solaris 10 Update content was finalised. This README contains important information. Please read this README before installing this patchset. PATCHSET DESCRIPTION: --------------------This patchset is provided as a single zip file. The zip file is named: 10_Recommended.zip Once the zip file has been downloaded, it may be extracted. For example, to extract this patchset in the current working directory, run: # unzip -q 10_Recommended.zip If you experience problems unzipping this patchset please refer to MOS article 1020109.1 'Unzip of Solaris 10 Recommended Patchsets fails', available from: https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PROBLEM&id =1020109.1 ************** ATTENTION ************** If this patchset is installed to the active boot environment, then depending on the starting patch level of the system, complete installation of the patchset may require up to two installation phases with intervening reboots. For further information, refer to section 'III. Installing this Patchset to the Active Boot Environment' below.

If this patchset is installed to an inactive boot environment, then the need for multiple reboots and some special instructions can be avoided. *************** PASSCODE ************** The install script will only execute when the passcode specified in this README file is provided as a command line flag. This is a safety mechanism to ensure you have read this README. You must follow the Special Install Instructions for key patches such as those highlighted in this README. It is also strongly recommended to read the Special Install Instructions section of the README of patches included in this patchset to check for any special install instructions which may apply to your specific system configuration. PASSCODE: s10patchset PATCHES INCLUDED: ----------------Note that the patch list order below reflects the patch install order. 120900-04 121133-02 119254-88 119317-01 121296-01 138215-01 148336-01 146054-07 142251-02 125555-12 118367-04 118666-47 118667-47 118705-02 118706-01 118707-05 118708-19 118711-03 118712-23 Patch 118718-06 Graphics 118777-16 patch 121181-05 118918-24 138217-01 119578-30 140860-02 121453-02 121118-19 .0.19 118833-36 118945-01 118981-03 119059-61 119063-01 119081-25 SunOS 5.10: libzonecfg Patch SunOS 5.10: zones library and zones utility patch SunOS 5.10: Install and Patch Utilities Patch SunOS 5.10: SVr4 Packaging Commands (usr) Patch SunOS 5.10: fgrep Patch SunOS 5.10: sort patch SunOS 5.10: awk patch SunOS 5.10: ksh patch SunOS 5.10: sh patch SunOS 5.10: patch behavior patch SunOS 5.10: csh Patch JavaSE 5.0: update 45 patch (equivalent to JDK 5.0u45) JavaSE 5.0: update 45 patch (equivalent to JDK 5.0u45), 64bit SunOS 5.10: XVR-1000 GFB Graphics Patch SunOS 5.10: Creator and Creator3D: FFB Graphics Patch SunOS 5.10: Expert3D IFB Graphics Patch SunOS 5.10: Sun XVR-1200 and Sun XVR-600 Graphics Accelerator Patch SunOS 5.10: M64 Graphics Patch Obsoleted by: 118712-24 SunOS 5.10: Sun XVR-100 Graphics Accelerator Obsoleted by: 118718-07 SunOS 5.10: Generic Framebuffer configuration Patch Obsoleted by: 118777-17 SunOS 5.10: Sun GigaSwift Ethernet 1.0 driver Obsoleted by: 121181-06 Sun Trunking Utility 1.3: maintenance patch SunOS 5.10: Solaris Crypto Framework patch SunOS 5.10: svccfg & svcprop patch SunOS 5.10: FMA Patch SunOS 5.10: su patch SunOS 5.10: Sun Update Connection Client Foundation Obsoleted by: 121118-20 SunOS 5.10: Update Connection System Client 1 SunOS 5.10: kernel patch SunOS 5.10: Sun Gigabit Ethernet 3.0 driver patch SunOS 5.10: Sun Quad FastEthernet qfe driver Obsoleted by: 119059-62 X11 6.6.2: Xsun patch SunOS 5.10: libXpm patch SunOS 5.10: CD-ROM Install Boot Image Patch

119115-35 119117-52 119130-33 119213-27 119246-39 0 124628-10 119252-29 s Patch 123611-04 119280-25 119278-38 119282-01 119309-03 140899-01 119313-42 124188-03 119315-19 atch 120199-15 119534-29 119538-19 120099-08 119546-08 119548-14 119648-03 120272-31 122640-05 126897-02 127755-01 125503-02 118731-01 124204-04 122660-10 125547-02 140796-01 120011-14 139520-02 119757-27 119764-07 119783-25 119810-07 120460-20 119812-16 119900-16 ch 119903-02 119906-18 tch 119955-05 0 119963-24 119966-01 119986-03 120094-30 120101-01 120195-02 120201-05 120256-01 120284-07

Mozilla 1.7: patch Obsoleted by: 119117-53 Evolution 1.4.6 patch SunOS 5.10: Sun Fibre Channel Device Drivers NSS_NSPR_JSS 3.13.1: NSPR 4.8.9 / NSS 3.13.1 / JSS 4.3.2 Obsoleted by: 119246-40 SunOS 5.10: Manual Page updates for Solaris 1 Obsoleted by: 124628-11 SunOS 5.10: CD-ROM Install Boot Image Patch Obsoleted by: 119252-30 SunOS 5.10: System Administration Application X11 6.6.2: Trusted Extensions patch CDE 1.6: Runtime library patch for Solaris 10 Obsoleted by: 119278-42 CDE 1.6: dtlogin patch CDE 1.6: GNOME/CDE Menu for Solaris 10 SunOS 5.10: PGX32 Graphics SunOS 5.10: [ir].manifest patch SunOS 5.10: WBEM Patch SunOS 5.10: Trusted Solaris Attributes Patch Obsoleted by: 119315-20 SunOS 5.10: Solaris Management Applications P Obsoleted by: 120199-16 SunOS 5.10: sysidtool Patch Obsoleted by: 119534-30 SunOS 5.10: Flash Archive Patch Obsoleted by: 119538-20 GNOME 2.6.0: Window Manager Patch APOC 1.2: Sun Java(tm) Desktop System Configuration Shared Libraries APOC 1.2: APOC Configuration Agent Patch GNOME 2.6.0: Gnome Multi-protocol instant messaging client Patch SunOS 5.10: vlan driver patch Obsoleted by: 120272-32 SunOS 5.10: SMA patch SunOS 5.10: zfs genesis patch SunOS 5.10: Fault Manager Patch SunOS 5.10: Fault Manager patch SunOS 5.10: package-move-of-IP-objects patch Obsoleted by: 120011-14 SunOS 5.10: /usr/sbin/zonecfg patch Obsoleted by: 120473-05 SunOS 5.10: zfs patch Obsoleted by: 120011-14 SunOS 5.10: zones patch SunOS 5.10: zoneadm indirect dependency patch SunOS 5.10: umountall patch SunOS 5.10: kernel patch SunOS 5.10: package specific [ir].manifest removal patch SunOS 5.10: Samba patch Obsoleted by: 119764-08 SunOS 5.10: ipmitool patch Obsoleted by: 119783-26 SunOS 5.10: BIND patch SunOS 5.10: International Components for Unicode Patch Obsoleted by: 120460-21 GNOME 2.6.0: Gnome libs Patch Obsoleted by: 119812-17 X11 6.6.2: FreeType patch GNOME 2.6.0: GNOME libtiff - library for reading and writing TIFF Pat OpenWindows 3.7.3: Xview Patch Obsoleted by: 119906-19 GNOME 2.6.0: Virtual File System Framework pa Obsoleted by: 143733-03 CDE 1.6: Tooltalk Runtime patch for Solaris 1 Obsoleted by: 119963-25 SunOS 5.10: Shared library patch for C++ SunOS 5.10: Math Libraries (libm+libmvec) patch SunOS 5.10: clri patch Obsoleted by: 120094-31 X11 6.6.2: xscreensaver patch SunOS 5.10: libsmedia patch SunOS 5.10: patch schpc sc_gptwocfg gptwo_pci X11 6.8.0: Xorg client libraries patch SunOS 5.10: hci1394 Patch GNOME 2.6.0: GNOME CORBA ORB and component framework

119368-04 Obsoleted by: 119368-05 GNOME 2.6.0: Printing Technology Patch 120286-03 Obsoleted by: 120286-04 GNOME 2.6.0: Gnome text editor Patch 120292-02 Obsoleted by: 120292-03 SunOS 5.10: mysql patch 120348-03 Obsoleted by: 146234-01 SunOS 5.10: Fibre Channel HBA Port utility 121975-01 CDE 1.6: Xsession patch 120410-33 Obsoleted by: 120410-34 SunOS 5.10: Internet/Intranet Input Method Fr amework patch 120412-11 Obsoleted by: 120412-12 SunOS 5.10: Simplified Chinese locale patch 120414-27 Obsoleted by: 120414-28 SunOS 5.10: Asian CCK locales patch 120543-31 SunOS 5.10: Apache 2 Patch 120719-03 Obsoleted by: 120719-04 SunOS 5.10: SunFreeware gzip patch 120732-01 SunOS 5.10: libusb patch 120739-08 GNOME 2.6.0: GNOME PDF Viewer based on Xpdf 120753-09 Obsoleted by: 120753-10 SunOS 5.10: Microtasking libraries (libmtsk) patch 120811-09 Obsoleted by: 120811-10 SunOS 5.10: FUJITSU PCI Fibre Channel Driver 3.0 patch 120812-32 OpenGL 1.5: OpenGL Patch for Solaris 120815-01 SunOS 5.10: dmfe patch 120830-06 SunOS 5.10: vi and ex patch 120849-04 SunOS 5.10: Sun PCI-E Gigabit Ethernet Adapter Patch 120928-32 Obsoleted by: 120928-33 SunOS 5.10: Sun XVR-2500 Graphics Accelerator Patch 121095-03 GNOME 2.6.0: GNOME EXIF tag parsing library for digital cameras 121104-11 SunOS 5.10: Adobe Acrobat Reader patch 121136-02 SunOS 5.10: Adobe Acrobat Reader browser-plugin patch 121211-02 SunOS 5.10: Sun Java Web Console (Lockhart) Patch 121308-20 Obsoleted by: 121308-21 SunOS 5.10: Solaris Management Console Patch 121337-01 SunOS 5.10: tlimod patch 120235-01 SunOS 5.10: Live Upgrade Zones Support Patch 121428-15 SunOS 5.10: Live Upgrade Zones Support Patch 121606-04 GNOME 2.6.0: Python patch 121946-01 SunOS 5.10: Error processing FRU tree: IO error patch 122031-01 SunOS 5.10: cgsix Patch 122212-46 GNOME 2.6.0: GNOME Desktop Patch 122259-06 Obsoleted by: 122259-07 SunOS 5.10: SunFreeware gnu esp ghostscript p atch 122470-03 Obsoleted by: 122470-04 GNOME 2.6.0: GNOME Java Help Patch 122472-07 SunOS 5.10: XVR200 Graphics 122911-31 SunOS 5.10: Apache 1.3 Patch 123003-04 SunOS 5.10: SAM module patch 124171-07 Obsoleted by: 124171-08 SunOS 5.10: SCN Base cacao module patch 123630-03 Obsoleted by: 123630-04 SunOS 5.10: HTTP proxy settings patch 123005-07 Obsoleted by: 123005-08 SunOS 5.10: Basic Registration Update 123252-01 SunOS 5.10: platform/SUNW,Netra-T2000 patch 123301-01 SunOS 5.10: i2c_svc patch 123358-02 SunOS 5.10: jumpstart and live upgrade compliance patch 123526-01 SunOS 5.10: libcurses patch 123590-12 SunOS 5.10: PostgresSQL patch 123893-22 Obsoleted by: 123893-23 SunOS 5.8 5.9 5.10: Common Agent Container (c acao) runtime 2.2.4.2 upgrade patch 22 123938-02 GNOME 2.6.0: GNU Transport Layer Security Library Patch 124149-16 SunOS 5.10: Sun XVR-300 Graphics Accelerator Patch 124325-01 SunOS 5.10: rcm modules patch 124393-11 CDE 1.6: Dtlogin smf patch 124397-02 CDE 1.6: libDtWidget patch 124457-02 Obsoleted by: 124457-03 X11 6.6.2: xdm patch 124630-42 Obsoleted by: 124630-43 SunOS 5.10: System Administration Application s, Network, and Core Libraries Patch 124939-04 SunOS 5.10 5.10_x86: JDMK 5.1 patch

124997-01 SunOS 5.10: /usr/bin/tip patch 125075-01 SunOS 5.10: svc-volfs patch 125136-48 JavaSE 6: update 45 patch (equivalent to JDK 6u45) 125137-48 JavaSE 6: update 45 patch (equivalent to JDK 6u45), 64bit 125215-04 SunOS 5.10: wget patch 125279-05 Obsoleted by: 125279-06 CDE 1.6: dtsession patch 125332-24 JDS 3: Macromedia Flash Player Plugin Patch 125505-01 SunOS 5.10: daktari and cherrystone header files patch 125533-17 GNOME 2.6.0: Trusted Extension Runtime Patch 125670-04 SunOS 5.10: Sun x8 10G/1G Ethernet Adapter driver patch 125719-42 Obsoleted by: 125719-43 X11 6.8.0: Xorg server patch 125725-02 X11 6.6.2: xinerama patch 125731-10 SunOS 5.10: XML and XSLT libraries patch 125891-01 SunOS 5.10: libc_psr_hwcap.so.1 patch 126119-02 CDE 1.6: sys-suspend patch 126206-10 SunOS 5.10: zebra ripd quagga patch 126363-08 SunOS 5.10: X Window System changes - Solaris Trusted Extensions 126365-16 Obsoleted by: 126365-17 SunOS 5.10: CDE Desktop changes - Solaris Tru sted Extensions 126425-01 SunOS 5.10: fsckall patch 126440-01 SunOS 5.10: rm patch 126540-02 SunOS 5.10: libumem library patch 126546-04 SunOS 5.10: bash patch 126868-04 SunOS 5.10: SunFreeware bzip2 patch 127127-11 SunOS 5.10: kernel patch 127724-02 Obsoleted by: 148881-01 SunOS 5.10: xntpd patch 127752-01 SunOS 5.10: SUNW,Netra-CP3060 platform symlinks patch 127872-02 SunOS 5.10: mailx patch 128292-01 SunOS 5.10: rsm Patch 128298-02 SunOS 5.10: se patch 128310-01 SunOS 5.10: hsfs patch 128332-01 SunOS 5.10: conskbd patch 136882-03 SunOS 5.10: ImageMagick patch 136998-10 SunOS 5.10: PostgreSQL 8.2 core patch 137000-08 SunOS 5.10: PostgreSQL 8.2 documentation patch 137004-09 SunOS 5.10: PostgreSQL 8.2 source code patch 137032-01 SunOS 5.10: namefs patch 137080-07 SunOS 5.10: libpng Patch 137090-02 SunOS 5.10: rmc_comm, rmclomv patch 137093-01 SunOS 5.10: logindevperm patch 137097-02 SunOS 5.10: inetd-upgrade patch 137102-01 SunOS 5.10: flowacct patch 137115-01 SunOS 5.10: SUNWcsr postinstall patch 138866-03 SunOS 5.10: sharetab patch 137137-09 SunOS 5.10: kernel patch 137147-07 SunOS 5.10: libexpat patch 137282-01 SunOS 5.10: intpexec patch 137321-02 SunOS 5.10: p7zip patch 137871-02 SunOS 5.10: tk patch 138096-02 SunOS 5.10: syslogd patch 138181-01 SunOS 5.10: ike.preshared patch 138195-04 Service Tags 1.0: patch for Solaris 10 138245-01 SunOS 5.10: nss_compat patch 138247-01 Obsoleted by: 148381-02 SunOS 5.10: cdrw patch 138361-01 Obsoleted by: 138361-02 SunOS 5.10: snmpXdmid patch 138647-01 SunOS 5.10: /usr/bin/dircmp patch 138649-01 SunOS 5.10: i.renamenew r.renamenew patch 138766-01 SunOS 5.10: ldap-client manifest patch 138822-12 SunOS 5.10: PostgreSQL 8.3 documentation patch 138824-12 SunOS 5.10: PostgreSQL 8.3 source code patch

138826-12 SunOS 5.10: PostgreSQL 8.3 core patch 138852-01 SunOS 5.10: postreverse patch 138854-01 Obsoleted by: 146292-01 SunOS 5.10: sulogin patch 138876-01 Obsoleted by: 138876-02 SunOS 5.10: usr/lib/inet/in.dhcpd patch 139099-04 Obsoleted by: 139099-05 SunOS 5.10: gtar patch 139289-02 SunOS 5.10: pgadmin3 patch 139291-02 SunOS 5.10: pgadmin3 sources patch 141016-01 SunOS 5.10: Dummy Patch 139555-08 SunOS 5.10: Kernel Patch 139615-01 SunOS 5.10: Foomatic patch 139620-01 Obsoleted by: 119278-42 CDE 1.6: Dthelp patch 139944-01 Obsoleted by: 148161-02 SunOS 5.10: brand patch 139962-02 SunOS 5.10: i.rbac and patch postinstall patch 139980-01 SunOS 5.10: SunFire T200 libprtdiag_psr patch 139986-01 SunOS 5.10: rpc.ypupdated patch 140159-03 Obsoleted by: 143937-03 SunOS 5.10: rsh/rlogin/rcp/rdist patch 140455-01 Obsoleted by: 140455-02 X11 6.6.2: VNC Viewer patch 140912-01 Obsoleted by: 140912-02 SunOS 5.10: ufsrestore patch 141032-01 SunOS 5.10: audit patch 141104-04 SunOS 5.10: ZFS Administration Java Web Console Patch 142292-01 SunOS 5.10: Place Holder patch 141444-09 SunOS 5.10: kernel patch 141496-01 SunOS 5.10: patchchk patch 141532-04 Obsoleted by: 146075-01 SunOS 5.10: in.mpathd patch 141548-01 SunOS 5.10: svccfg patch 141558-01 SunOS 5.10: acctcom patch 141586-01 Obsoleted by: 148985-01 SunOS 5.10: libgss.so.1 patch 142049-01 Obsoleted by: 149057-01 SunOS 5.10: llc2 patch 142088-02 Obsoleted by: 142088-03 SunOS 5.10: fp.so patch 142234-01 Obsoleted by: 148029-01 SunOS 5.10: ntp.xml patch 142240-01 SunOS 5.10: ntpq patch 142244-02 SunOS 5.10: hme driver patch 142340-02 SunOS 5.10: libresolv.so.2 patch 142373-02 Obsoleted by: 142373-03 SunOS 5.10: AST Graphics Patch 142394-01 SunOS 5.10: icmp patch 142397-01 SunOS 5.10: libsasl.so.1 patch 142428-02 SunOS 5.10: unshare patch 142430-01 SunOS 5.10: libscf.so.1 patch 142529-01 SunOS 5.10: uptime w utmp_update whodo patch 142543-01 Obsoleted by: 142543-02 SunOS 5.10: svc-snmpdx libssagent.so.1 mibiis a snmpdx snmpdx.xm patch 142911-01 SunOS 5.10: Place Holder patch 142933-05 SunOS 5.10: failsafe patch 142909-17 SunOS 5.10: kernel patch 143317-03 GNOME 2.6.0: Instant Messaging patch 143502-01 GNOME 2.6.0: Trusted Extensions patch 143506-06 GNOME 2.6.0: Python patch 143513-02 Obsoleted by: 143581-03 SunOS 5.10: dladm patch 143527-01 SunOS 5.10: mc-opl patch 143609-03 SunOS 5.10: svc-iscsitgt patch 144526-02 SunOS 5.10: place holder patch 144500-19 SunOS 5.10: Solaris kernel patch 143643-08 SunOS 5.10: libMPAPI.so libmpscsi_vhci.so libMPAPI.so.1 libmpscsi_vhc i.so.1 patch 143651-01 SunOS 5.10: hpc3130 patch 143725-01 SunOS 5.10: SunFreeware ntp patch 143727-01 SunOS 5.10: SunFreeware ntp source patch 143731-01 SunOS 5.10: libaudiofile patch 143733-01 Obsoleted by: 143733-03 CDE 1.6: ToolTalk RPC patch 143739-01 SunOS 5.10: Gedit patch

143954-04 144047-01 144106-01 144112-02 144188-02 144325-01 e Patch 144327-02 144455-01 144486-05 144492-01 144569-01 144909-03 144911-02 144994-02 144996-02 145006-04 145019-01 145023-01 147217-02 145080-12 145096-03 145120-01 145200-12 145929-05 145953-06 147442-01 147147-26 146232-21 146334-01 146470-08 146489-06 146673-01 146679-01 146681-02 146683-01 146694-02 146834-02 146954-03 147023-01 147194-03 147227-01 147378-01 147673-06 147692-21 147693-21 147715-04 147805-01 147992-05 148002-01 148004-01 148006-01 148027-03 ar patch 148067-02 148071-11 148112-02 148135-01 148165-02 148169-03

Obsoleted by: 149277-01 SunOS 5.10: mpxio-upgrade patch SunOS 5.10: traceroute patch SunOS 5.10: usr/lib/nfs/nfslogd patch Obsoleted by: 148103-02 SunOS 5.10: liba5k patch SunOS 5.10: emlxs patch Obsoleted by: 144325-02 SunOS 5.10: Resource Management User Interfac SunOS 5.10: Solaris Product Registry Patch Obsoleted by: 143962-02 SunOS 5.10: audit_syslog.so.1 patch Obsoleted by: 145648-03 SunOS 5.10: qlge patch Obsoleted by: 144742-02 SunOS 5.10: JPool.jar patch Obsoleted by: 148223-02 SunOS 5.10: zonecfg patch SunOS 5.10: yp method ldap patch Obsoleted by: 148237-01 SunOS 5.10: vold patch SunOS 5.10: Ant patch SunOS 5.10: Ant source patch SunOS 5.10: Webmin patch SunOS 5.10: ifconfig patch SunOS 5.10: rc scripts Solaris Containers patch SunOS 5.10: SUNWdbus-bindings-priv patch SunOS 5.10: Firefox patch Obsoleted by: 146586-03 SunOS 5.10: oce driver patch SunOS 5.10: auditd.xml patch SunOS 5.10: Thunderbird patch Obsoleted by: 145929-06 SunOS 5.10: igb driver Patch Obsoleted by: 145953-07 SunOS 5.10: emlxs driver Patch SunOS 5.10: place holder patch SunOS 5.10: kernel patch Obsoleted by: 146232-22 SunOS 5.10: iSCSI patch SunOS 5.10: zlogin patch Obsoleted by: 146470-09 SunOS 5.10: timezone patch Obsoleted by: 149175-02 SunOS 5.10: qlc patch SunOS 5.10: auth_attr prof_attr patch SunOS 5.10: hxge patch SunOS 5.10: arp patch Obsoleted by: 148031-02 SunOS 5.10: klmmod patch SunOS 5.10: cron patch Obsoleted by: 149217-02 SunOS 5.10: zones resource controls patch Obsoleted by: 146954-04 SunOS 5.10: routed patch SunOS 5.10: ds_snmp patch Obsoleted by: 148023-03 SunOS 5.10: bmc patch X11 6.6.2: xrdb patch Obsoleted by: 147378-02 SunOS 5.10: zip patch SunOS 5.10: Oracle Java Web Console 3.1 Patch JavaSE 7: update 21 patch (equivalent to JDK 7u21) JavaSE 7: update 21 patch (equivalent to JDK 7u21), 64bit Obsoleted by: 146664-02 SunOS 5.10: krb5 patch SunOS 5.10: tl patch SunOS 5.10: Pidgin libraries patch SunOS 5.10: libdbus-1.so.3.4.2 patch SunOS 5.10: libpixbufloader-gif.so patch SunOS 5.10: libogg patch Obsoleted by: 148027-04 SunOS 5.10: compress cp cpio ln mv pack pax t Obsoleted by: 148415-02 SunOS 5.10: SunOS 5.10: openssl patch SunOS 5.10: root_archive patch Obsoleted by: 149395-01 SunVTS 7.0: Obsoleted by: 148165-03 SunOS 5.10: Obsoleted by: 148169-04 SunOS 5.10: ibd patch Patch Set 14 consolidation patch password policy migration patch ixgbe patch

148241-02 148342-06 148383-01 148403-01 148407-01 148412-02 148423-01 148561-04 148565-01 148625-01 148657-01 148768-01 148870-01 148888-03 148948-01 148975-01 149067-01 149108-01 149112-01 149149-01 149163-01 149165-01 121081-08 149453-02 149483-01 150117-01 150123-01 150125-01 150157-01

SunOS 5.10: statd patch SunOS 5.10: nxge patch SunOS 5.10: IPv6 patch SunOS 5.10: strmod/spppcomp patch SunOS 5.10: mount patch Obsoleted by: 148419-03 SunOS 5.10: nss_dns patch SunOS 5.10: /usr/ccs/bin/error patch SunOS 5.10: Perl patch SunOS 5.10: fdformat patch SunOS 5.10: in.tnamed patch SunOS 5.10: telnet patch SunOS 5.10: calendar diff3 spell uupick patch SunOS 5.10: mailx.rc patch SunOS 5.10: kernel patch SunOS 5.10: bsmconv bsmunconv patch SunOS 5.10: in.rexecd patch SunOS 5.10: SunFreeware GNU grep SunOS 5.10: libgsf-1.so.1.8.2 patch SunOS 5.10: libglib-2.0.so.0.1800.3 patch SunOS 5.10: LP Alerts Patch SunOS 5.10: rlmod patch SunOS 5.10: timod patch SunOS 5.10: Connected Customer Agents 1.1.0 SunOS 5.10: CCR Update SunOS 5.10: Foomatic patch SunOS 5.10: mac patch SunOS 5.10: sharefs patch Obsoleted by: 150125-02 SunOS 5.10: ZFS patch SunOS 5.10: RPC patch

Extra Patches: The patchset contains the following patches which are themselves obsoleted by other patches in the patchset. These patches are required to ensure correct installation of the patchset on Solaris 10 11/06 (Update 3) and earlier Solaris 10 Updates. The obsolete patches will only be applied to those systems where they are necessary, they will not be applied if the system is already at a higher patch level. Patch Reason 122660-10: Obsolete patch required by 125547-02. 125547-02 is the zoneadm indirect dependency patch, which is needed to resolve an issue applying kernel patch 120011-14 on a system with zones support. See CR 6471974. 124204-04: Obsolete patch required by 122660-10. 118731-01: Obsolete patch required by 124204-04. The patchset contains the following patches for Unbundled Software Products (ie. add on products that are not part of a default Solaris 10 installation). Patches for Unbundled Products are included in the patchset only if their use is required to avoid critical OS problems. These patches will only be applied to systems where the associated Unbundled Product is installed. Patch Reason 121181-05: Patch is required to avoid a kernel panic caused by an incompatibility between Sun Trunking Utility and GigaSwift Ethernet drivers (see MOS article 1000555.1).

Live Upgrade patch 121430-XX is included in the patches/ directory of the patchset, but this patch will not be applied during patchset installation. The decision to apply the Live Upgrade patch is left to the user, this is done to accommodate users who wish to independently manage the version of the Live Upgrade patch on their system. Where a user wishes to apply the Live Upgrade patch, this needs to be done manually with the patchadd command. Patches for removed products: Certain products that are components of earlier Solaris 10 Updates were removed from Solaris 10 as it evolved. Patches for removed products are not relevant to later solaris 10 Updates, and therefore have been excluded from this patchset. The excluded patches are listed below, to allow a user to determine if any are applicable to products that may still be installed on their systems. Patch 120185 125541-06 125539-06 122958-06 Product StarOffice 8 Mozilla 1.7 Thunderbird email client Mozilla 1.7 Firefox Web browser RealPlayer media application

IMPORTANT NOTES AND WARNINGS: ----------------------------KNOWN ISSUES: When installing the patchset to an inactive boot environment, the install script may abort with the following message: ERROR: Failed to determine zone configuration for target boot environment. Please verify configuration with zoneadm(1M). This will occur when the /etc/zones/index file of the inactive boot environment specifies an invalid state for the global zone. The correct state is 'installed', however the state may have been incorrectly changed to 'configured' as a consequence of CR 6804076. To confirm whether the issue exists, mount the inactive boot environment and run the following command: # grep "^global:configured:" <inactive-BE-mount-point>/etc/zones/index global:configured:/ # The issue exists if the grep command outputs a line as above. To resolve the issue, first make a backup copy of /etc/zones/index in the inactive boot environment, then manually edit /etc/zones/index in the inactive boot environment and correct the entry for the global zone by replacing 'configured' with 'installed'. PATCHSET SIZE: This patchset is delivered as a single zip file. The size of this file is approximately 2.2G. In uncompressed form, the size of the patchset is approximately 5.7G.

FILESYSTEM FREE SPACE REQUIREMENTS: It is difficult to give a precise estimate of how much free disk space is required to install the patchset. The amount of free space required depends on many factors. The following factors all increase the amount of space needed: - The Solaris 10 Update onto which the patchset is being installed. A Solaris 10 3/05 ("FCS") system will require considerably more free space than a system running the latest Solaris 10 Update. - Whether zones are installed or not. The nature of the zones is important. Each whole root non-global zone will require approximately the same amount of free space as the global zone, while each sparse root non-global zone will require much less space on the filesystems where the zone resides. - Whether the patchset is installed with the "save" feature disabled. It is strongly recommended to use the default "save" feature when installing the patchset even though this requires more disk space. It allows the patches that are applied to be removed in case any issues are found post installation. Disabling the "save" feature with the "-d" flag (described below) will reduce the amount of disk space needed, however this is not the recommended way of installing the patchset. As a guide, the free space required to install this patchset using the default "save" feature to an unpatched Solaris 10 FCS system with the entire distribution plus OEM support metacluster is approximately 2.7G. Each whole root non-global zone would need approximately the same amount of space free in the filesystem that contains the zone's root. The install script will check that sufficient space is free before applying each patch. The script will stop if it estimates there is not enough free space available, and will provide instructions on how to override space checking should the user wish to continue patchset installation anyway. The backout data for patches applied using patchadd's default save mode is stored under the /var/sadm/pkg directory in the target system. The amount of backout data stored builds up as more patches are applied to the system. If the filesystem on which the /var/sadm/pkg directory resides becomes low on free space, MOS article 1005804.1 'Solaris[TM]: Recovering Space Used for Saved Backout Data from Patches' describes a number of options for increasing the amount of free space available. This article is available from: https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=1 005804.1 SYSTEMS WITH LIMITED DISK SPACE SHOULD *NOT* INSTALL PATCHES: Whether you use the default "save" feature to store backout data or not, the patch application process still requires disk space for installation and administrative tasks. The disk space is needed in filesystems where patches deliver payload. The exact amount of space depends on the system's architecture, the software packages already installed, and the difference in size of the patched objects. In case a problem occurs, ensure a recent full system backup is available. SAVE AND BACKOUT OPTIONS:

By default, the install script uses the patchadd command's default save mode 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" feature is used when installing this patchset. You can override the "save" feature by using the "-d" flag when executing the install script. Using the "-d" flag means that you will not be able to backout the patches. This would be problematic if ever there was a need to remove a patch, therefore use of the "-d" flag is not the recommended option. BOOTING OF NEWLY CREATED NON-GLOBAL ZONES: Newly created non-global zones can fail to boot for a short period (~5 minutes) immediately after having been installed. This problem will typically affect systems running Solaris 10 11/06 (Update 3) and earlier Solaris 10 Updates, where this patchset has been installed but patch 121428-13 (or higher), and required patch 121430-16 (or higher) have not been applied - please refer to the note on patch 121430 in the Extra Patches section above. Resolution is to either manually apply these patches before creating a new non-global zone, or to wait for a sufficient period before booting a newly created non-global zone. 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, it is recommended to read each patch README before installing this patchset. A PATCH MAY NOT BE APPLIED: Some of the patches in the patchset will not apply on particular systems. The following are examples of when a patch might not apply. These situations are nominal and are not a cause for concern. The patch may be one of the obsolete or Unbundled Software Product patches listed in the "PATCHES INCLUDED" section. The patch might patch packages that: - Are only installed on specific hardware. - Were introduced in a later Solaris 10 Update than the Solaris 10 Update 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 patchadd command recognises packages that already have a patch applied and will only apply a patch to those packages which aren't already patched. 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 APPLIED: Backing out older revisions of patches provided in the patchset is not required for the newer revision to be applied. If the patchset is installed using the default "save" feature, then the patchadd command will save off the preexisting objects. If a patch is subsequently removed, the objects will be restored to the prior patch level. INSTALL INSTRUCTIONS: --------------------This patchset can be installed on the active boot environment, or to an inactive boot environment using either the "-B" Live Upgrade flag, or the "-R" alternate root flag. The "-R" alternate root flag can be used to patch alternate boot environments that have been created manually and not necessarily via Live Upgrade. 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 a significant number of Special Install Instructions that would be required if you patched the active boot environment. If the patchset is installed to an inactive boot environment then some patches may need to be applied to the active boot environment initially. Further details of this requirement are given in the appropriate sections below. Specific details for the three install methods are given in the following sections. General installation instructions applicable to all methods are given in the "PATCHSET INSTALLATION INSTRUCTIONS" section.

I. Installing this Patchset to a Live Upgrade Boot Environment Before installing this patchset to an inactive Live Upgrade boot environment, it is important those patches necessary to ensure the correct functioning of Live Upgrade are applied to the required boot environments. If the intent is use of Live Upgrade on a system running Solaris 10 8/07 (Update 4) or an earlier Solaris 10 Update, then it is recommended to install the Live Upgrade Starter Patchset for Solaris 10. Installing the LU Starter Patchset will provide the system with a level of functionality sufficient to enable use of Live Upgrade. The LU Starter Patchset can be located with the patch search facility under the 'Patches & Updates' tab on MOS. If the intent is use of Live Upgrade on a system running Solaris 10 5/08 (Update 5) or a later Solaris 10 Update, then the list of required patches can be found in MOS article 1004881.1 'Solaris[TM] Live Upgrade Software: Patch Requirements', available from: https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=1 004881.1 It is generally recommended to review article 1004881.1 before installing this patchset to an inactive Live Upgrade boot environment. The article provides the most current information on those patches necessary to ensure the correct

functioning of Live Upgrade on various different system configurations. When installing this patchset to an inactive Live Upgrade boot environment, the install script may stop and notify the user of the need to invoke the script with the "--apply-prereq" flag to ensure appropriate levels of various patches (including the patch utility patches) are applied to the running system. The patchset will not install to an inactive boot environment if the running system does not have these patches applied. There is no need to bring the running system to single-user mode when installing this patchset to an inactive Live Upgrade boot environment. A discussion of how to use Live Upgrade to create and manage boot environments is outside the scope of this document. The install script accompanying this patchset will not create Live Upgrade boot environments. For information on how to use Live Upgrade please see document "Solaris 10 Installation Guide: Solaris Live Upgrade and Upgrade Planning.", available from: http://download.oracle.com/docs/cd/E18752_01/html/821-1910/index.html The following command installs this patchset to an inactive boot environment that was previously created with Live Upgrade: ./installpatchset -B <inactive-BE-name> For example, to install the patchset to an inactive boot environment named 'second_disk', the following command would be run: # lustatus Boot Environment Name -------------------------first_disk second_disk Is Complete -------yes yes Active Now -----yes no Active On Reboot --------yes no Can Delete -----no yes Copy Status ----------

# ./installpatchset -B second_disk

II. Installing this Patchset to an Alternate Root This patchset can be installed to an arbitrary alternate root. This method of installation is not recommended for general users, it is provided for advanced users who recognise situations where this method of installation is beneficial, and have a thorough understanding of the additional complexities involved in setting up the alternate root. When installing this patchset to an alternate root, the install script may stop and notify the user of the need to invoke the script with the "--apply-prereq" flag to ensure appropriate levels of various patches (including the patch utility patches) are applied to the running system. The patchset will not install to an alternate root if the running system does not have these patches applied. There is no need to bring the running system to single-user mode when installing this patchset to an alternate root. The following command installs this patchset to an alternate root: ./installpatchset -R <alternate-root-path>

For example, if an alternate boot environment has its root and all subordinate file systems mounted under /mnt/altroot, the following command would be run: # ./installpatchset -R /mnt/altroot

III. Installing this Patchset to the Active Boot Environment Patching an inactive boot environment using either the "-B" Live Upgrade flag, or the "-R" alternate root flag is recommended over patching the active boot environment. The following special warnings apply if this patchset is applied to the active boot environment: 1. SINGLE USER MODE Ideally the installation should be performed in single-user mode (run level S), although this in not a strict requirement. Depending on system configuration, it may be necessary to mount local filesystems before installing this patchset (for example, if a system configuration has zone roots on a local filesystem that is not mounted in single-user mode). In most cases, onlining the filesystem/local service will be sufficient to ensure the required filesystems are mounted. This can be accomplished by running the following command: # svcadm enable svc:/system/filesystem/local:default Note that the install script may abort during the setup phase with an indefinite error message if the required filesystems are not mounted. The exact error messaging can vary from one system configuration to another - for illustrative purposes one example of such messaging follows: # ./installpatchset Setup .zoneadm: /export/zones/z1s: No such file or directory could not verify zonepath /export/zones/z1s because of the above errors. zoneadm: zone z1s failed to verify ERROR: Zone verification failed : unable to mount zone 'z1s'. # Should this problem occur, ensure local filesystems are mounted then reinvoke the install script. 2. REBOOTS Some patches specify in their README file that an immediate reboot or reconfiguration reboot ('reboot -- -r') is required when they are applied to an active boot environment. Generally, it is possible to complete patching operations before initiating the reboot, but normal production operations should not be resumed until the reboot is performed. In the rare case where it is not possible to continue patching operations, the specific patches involved will contain logic that prevents further patching operations until a reboot is performed. For further information, please see MOS article 1019921.1 'Definitive interpretation of the "rebootimmediate" and "reconfigimmediate" patch flags',

available from: https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=REFERENCE& id=1019921.1 The install script will stop installation of the patchset when an interim reboot is required, and notify the user that a reboot is needed. The install script should be reinvoked after the reboot and patchset installation will resume. See "PATCHSET INSTALLATION INSTRUCTIONS" for details of the messages that are displayed. The factors that determine how many reboots are necessary are described below. Depending on the starting patch level of the target system, up to two reboots are needed. If the active boot environment is running a kernel at a patch level below 118833-36, the install script needs to be invoked TWO times, with a reboot after each invocation. First reboot: A reboot is necessary after applying patch 118833-36 because the patchadd command is disabled and no further patches can be applied until the system is rebooted. This is a safety device which is necessary due to the complexity of installing the code changes delivered in kernel patch 118833-36 to an active boot environment. Kernel patch 118833-36 is the kernel patch released shortly after Solaris 10 11/06 (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 118833-36 patch README. Final reboot: A reboot is required at the end of the patchset installation to ensure all changes are activated. 3. ZONES MUST BE HALTED If the active boot environment is running a kernel at a patch level of 118833-36 or above, all native non-global zones need to be halted before the patchset can be installed (in the output of 'zoneadm list -cv,' halted zones are shown as being in the 'installed' state). 4. PATCHES UTILISING DEFERRED ACTIVATION PATCHING The deferred activation patches included in the patchset are listed below: Patch 120011-14: 127127-11: 137137-09: 139555-08: 141444-09: 142909-17: 144500-19: 147147-26: Details Solaris Solaris Solaris Solaris Solaris Solaris Solaris Solaris 10 10 10 10 10 10 10 10 8/07 (Update 4) kernel patch. 5/08 (Update 5) kernel patch. 10/08 (Update 6) kernel patch. 5/09 (Update 7) kernel patch. 10/09 (Update 8) kernel patch. 9/10 (Update 9) kernel patch 8/11 (Update 10) kernel patch. 1/13 (Update 11) kernel patch.

Please carefully review the Special Install Instructions in the README files of these patches. Deferred activation patching was introduced in the patch utilities prior to the release of Solaris 10 8/07 (Update 4) as a way of ensuring system consistency while patching an active boot environment. Patches that need to be applied in

deferred activation patching mode will have the SUNW_PATCH_SAFE_MODE parameter set to true in their pkginfo files. Deferred activation patching utilises 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 applied in deferred activation patching mode, the patch will also automatically be applied in deferred activation patching mode by the patchadd command. Objects updated using deferred activation patching will be activated upon reboot of the system. After applying patches in deferred activation patch mode, a system will have a large number of files mounted via loop back filesystem. The df and mount commands will show these mounted files. For more information on deferred activation patching see: http://download.oracle.com/docs/cd/E19253-01/817-0547/gfick/ A reboot is required after applying deferred activation patches, to activate the changes. PATCHSET INSTALLATION INSTRUCTIONS: 1. Make sure the patchset has been extracted. See "PATCHSET DESCRIPTION" section for more details. 2. Decide if you want to save backout data so that patches can be removed at a later date. By default, the install script uses the patchadd command's default save mode 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" feature is used when installing this patchset. You can override the "save" feature by using the "-d" flag when executing the install script. Using the "-d" flag means that you will not be able to backout the patches. This would be problematic if ever there was a need to remove a patch, therefore use of the "-d" flag is not the recommended option. 3. Run the installpatchset script. # cd 10_Recommended # ./installpatchset -h usage: installpatchset [-d] [-h] [-R alt-root-path|-B alt-boot-env] [--apply-prereq] --<passcode> [-d] [-h] [-B alt-boot-env] [-R alt-root-path] [--apply-prereq] --<passcode> # - The "-d" flag is explained in step 2. don't save undo packages display this usage message specify LU boot environment as target specify alternate root as target apply prerequisite patches only passcode required for script execution

- The "-B" flag is explained in section "I. Installing this Patchset to a Live Upgrade Boot Environment". - The "-R" flag is explained in section "II. Installing this Patchset to an Alternate Root". - The "--apply-prereq" flag is for use on the active boot environment, prior to installing the patchset to an inactive boot environment. It ensures at least the same revision (or higher) of the patch utilities patches contained in this patchset are applied to the running system. This is a prerequisite for installing the patchset to an inactive boot environment. - The "--<passcode>" flag is a safety mechanism to ensure the README file has been read. The passcode can be found at the end of the "PATCHSET DESCRIPTION" section. 4. The progress of the install script is displayed on your terminal. The output should look similar to the following (this is from a system on which kernel patch 118833-36 was already applied): # ./installpatchset --s10patchset Setup ........ Recommended OS Patchset Solaris 10 SPARC (2013.02.13) The patch set will complete installation in this session. No intermediate reboots are required. Application of patches started : 2013.02.14 07:49:53 Applying 120900-04 ( 1 of Applying 121133-02 ( 2 of Applying 119254-88 ( 3 of . . <similar output omitted> . Applying 121081-08 (334 of Applying 149453-02 (335 of Applying 149483-01 (336 of 336) ... skipped 336) ... skipped 336) ... success

336) ... success 336) ... success 336) ... success

Application of patches finished : 2013.02.14 10:18:00 Following patches were applied : 119254-88 119966-01 127127-11 138215-01 120094-30 127724-02 147061-01 120201-05 127872-02 146054-07 120284-07 128292-01 142251-02 120286-03 128298-02 125555-12 120292-02 128310-01 118666-41 120348-03 128332-01 118667-41 120410-33 136882-03 118705-02 120412-11 136998-10 118707-05 120414-27 137000-08 118708-19 120543-30 137032-01 118711-03 120719-03 137080-07 118712-23 120739-08 137090-02

141496-01 141532-04 141548-01 141558-01 141586-01 142049-01 142088-02 142234-01 142240-01 142244-02 142340-02 142394-01 142397-01

145096-03 145120-01 145953-06 146032-05 147442-01 147147-26 146232-21 146334-01 146470-08 146489-06 146673-01 146681-02 146683-01

118718-06 118777-16 138217-01 140860-02 121118-19 119059-61 119115-35 119117-52 119213-27 119246-39 124628-10 119252-29 123611-04 119280-25 119278-38 140899-01 119313-42 124188-03 119315-19 120199-15 119534-29 119538-19 119548-14 120272-31 127755-01 140796-01 139520-02 119757-24 119764-07 119783-25 119810-07 120460-20 119812-16 119900-16 119906-18 119963-24

120753-09 120812-32 120830-06 120928-32 121095-03 121104-11 121136-02 121308-20 121428-15 121606-04 122212-46 122259-06 122470-03 122911-30 123003-04 124171-07 123630-03 123005-07 123590-12 123893-22 123938-02 124149-16 124393-11 124457-02 124630-42 124939-04 125215-04 125279-05 125332-24 125719-42 125731-08 125891-01 126119-02 126206-10 126546-04 126868-04

137093-01 137097-02 137102-01 137115-01 138866-03 137137-09 137147-07 137282-01 137321-02 137871-02 138096-02 138181-01 138195-04 138245-01 138247-01 138361-01 138647-01 138649-01 138766-01 138852-01 138854-01 138876-01 139099-04 141016-01 139555-08 139615-01 139620-01 139962-02 139986-01 140159-03 140912-01 141032-01 141104-04 142292-01 141444-09

142428-02 142430-01 142529-01 142543-01 142911-01 142933-05 142909-17 143317-03 143502-01 143506-06 143513-02 143527-01 143609-03 144526-02 144500-19 143643-08 143651-01 143731-01 143733-01 143739-01 143954-04 144047-01 144106-01 144112-02 144188-02 144325-01 144327-02 144455-01 144486-05 144492-01 144569-01 144909-03 144911-02 145006-04 145019-01

146694-02 146834-02 146954-03 147194-03 147227-01 147378-01 147434-01 147673-04 147707-09 147715-04 147805-01 148006-01 148027-03 148067-02 148112-02 148165-02 148383-01 148403-01 148407-01 148412-02 148423-01 148565-01 148625-01 148657-01 148768-01 148870-01 148948-01 148975-01 149108-01 149149-01 149163-01 149165-01 121081-08 149453-02 149483-01

Following patches were skipped : Patches already applied 120900-04 118945-01 122640-05 120256-01 123526-01 121133-02 118981-03 126897-02 121975-01 124325-01 119317-01 119063-01 125503-02 120732-01 124397-02 121296-01 119081-25 125547-02 120815-01 124997-01 118367-04 119130-33 120011-14 121337-01 125075-01 118706-01 119282-01 119903-02 120235-01 125505-01 118918-24 119309-03 119955-05 121946-01 125725-02 119578-30 120099-08 119986-03 122031-01 126425-01 121453-02 119546-08 120101-01 123301-01 126440-01 121453-02 119648-03 120195-02 123358-02 126540-02 118833-36 Patches obsoleted by one or more patches already applied 118731-01 124204-04 122660-10 119368-04 Patches not applicable to packages on the system 121181-05 125533-17 138826-11 143727-01 147692-13 120811-09 125670-04 139289-02 145023-01 147693-13 120849-04 126363-08 139291-02 147217-02 147992-04 121211-02 126365-16 139944-01 145080-12 148002-01 122472-07 127752-01 139980-01 145200-12 148004-01 123252-01 137004-09 140455-01 145929-05 148135-01 125136-42 138822-11 142373-02 146679-01 148169-03

125137-42

138824-11

143725-01

147023-01

Installation of patch set complete. PLEASE REBOOT THE SYSTEM. Install log files written : /var/sadm/install_data/s10s_rec_patchset_short_2013.02.14_07.49.53.log /var/sadm/install_data/s10s_rec_patchset_verbose_2013.02.14_07.49.53.log # If the patchset is installed on the active boot environment, the system may require one or more interim reboots before completing installation. If a message similar to the following is seen during installation, reboot the system and reinvoke the install script. "The installation of this patch set has halted after applying patch 118833-36. The machine must now be rebooted before further patches can be applied. Please reboot the machine and rerun this script. For further details, see patch set README file." Once the system is rebooted and the install script is reinvoked, installation of the patchset will continue. 5. If an unexpected error is encountered during the installation of this patchset, the install script will abort. Should this occur, the error must be investigated and the issue resolved before proceeding further. More details about the causes of failure can be found in the log files. The following log files are created during installation of the patchset: /var/sadm/install_data/s10s_rec_patchset_failed_<time-stamp>.log This log file contains patchadd output from patches that failed to apply. Review this log file to determine why a patch failed to apply. Note that this log file will only be created if a patch fails to apply. /var/sadm/install_data/s10s_rec_patchset_short_<time-stamp>.log This log file contains the same output that the install script displays on the terminal while the patchset is installing. /var/sadm/install_data/s10s_rec_patchset_verbose_<time-stamp>.log This log file contains all patchadd output generated during the installation of the patchset. The individual patch log files can also be inspected under /var/sadm/patch/<PatchID>/log. If the patchset is installed either with the "-B" Live Upgrade flag, or the "-R" alternate root flag, log files will reside in the inactive boot environment. 6. Reboot the system.

If this patchset is installed to an inactive boot environment using either the "-B" Live Upgrade flag or the "-R" alternate root flag, then a reboot will be needed to activate the inactive boot environment. If the "-B" Live Upgrade flag is used, then the luactivate command will need to be run, and either an init(1M) or a shutdown(1M) will be needed to complete activation of the boot environment. A reboot(1M) will not complete activation of a boot environment following an luactivate. If the "-R" alternate root flag is used, it may be necessary to rebuild the boot archive in the alternate root before booting the alternate root. The "-R" flag can be used to patch an alternate root in many different contexts however, and whether the boot archive rebuild step is necessary, not necessary, or even undesirable very much depends on user intent and the circumstances of each individual case. For this reason, the install script does not rebuild the boot archive. The decision and responsibility for rebuilding the boot archive is left to the user. Rebuilding the boot archive in an alternate root can be accomplished by running the following command: <alternate-root-path>/boot/solaris/bin/create_ramdisk -R <alternate-root-path> If this patchset is installed to the active boot environment, a reboot is needed to activate certain objects which have been patched, and to resolve potentially inconsistent states resulting from newly patched code interacting with old code running in memory. Normal operations should not be resumed until the reboot is performed. Depending on the starting patch level of the target system, interim reboots may also be required. The install script will stop installation of the patchset when a reboot is required, and notify the user that a reboot is needed. The install script should be reinvoked following an interim reboot.