Solaris 1. 1 Version Schema . The Oracle binary guarantee warrants that an application will work on any Solaris 1. It's however a reasonable idea to ask a user to be at same minimum patch level you qualified your application on. Which Solaris OS am I working on? There are a number of ways to distinguish Solaris 1. Open. Solaris or Solaris 1. Express systems. One way is to parse the file /etc/release. Oracle Solaris 1. X8. 6Copyright (c) 1. Oracle and/or its affiliates. It means it got released in November 2. Oracle. This is the final Solaris 1. The version to build professional, long lasting software against. Another option is the uname command. It'll let you know that you're working on a Sun. OS 5. 1. 1 platform. This is Solaris 1. Solaris 1. 1 Express, or may be Open Solaris. It's not very concise.. You will know that you are on Solaris 1. Being on Solaris 1. Oracle improves this product over time and there will be most likely update releases and patch bundles (SRU) as we know them from Solaris 1. The above commands will allow only to figure out if this is a Solaris 1. This date is likely to correlate with the update releases. Which Solaris Patch Level am I working on? Solaris 1. 1 isn't using anymore System V packages it uses the new IPS. IPS doesn't distinguish between packages and patches for packages. It deals with packages and their revisions only. Patches happen to be packages with higher minor version numbers. Oracle is now pursuing a uniform approach. IPS allows to check the concise version number of a package with the command pkg info < package name>. This allows to check the fine grained patch revision for any given package. The individual package granularity will be an overkill for most applications. Most applications will be happy to find a minimum Oracle patch level for the entire system. I have Solaris 10 and 11 running on my system. What about Solaris 10? Can I fetch patch bundle and install it without connect to Oracle. Home / Solaris 10 / Latest OS Patch Bundles for Solaris. Latest OS Patch Bundles for Solaris. 7.Click on that highlighted link to get the below screen where you can start OS patch bundle download. Question about Solaris 10 releases (Updates) pzxkys. We are running Solaris 10 Update 1 on multiple servers. This article describes the process of applying a Solaris recommended patch cluster, or patchset as it is now called. 2012.09.10: Solaris 11 OS Application Server 5300 3.0 Patch Bundle 1. Server 5300 Release 3.0 External Maintenance Release Bulletin Patch Bundle 1; Server Platform (O/S) Patch Update 15.0.28. How can I set up and configure a Solaris 8 zone under Solaris 10? Since update 4 of Solaris 10. 11.10.0,REV=2007.10.08.16.51. StorageTek Tape Storage. Sun Blade 6000 Modular Systems. Sun Desktops & Peripherals. Oracle Solaris 10 1/13. Full DVD Image (ISO image): Oracle Solaris 10. Oracle Solaris 10 8/11 s10s. Patch 16619892 (Patchset Update). SAP Bundle Patch for GI, 11.2.0.3.6 or 11.2.0.3.7.A check of the kernel package is all it takes. Most other packages of the OS will depend on the kernel revision. Oracle has a concept of making update revisions freely available through the OTN license. Patch bundles in between update release are available for customers as Support Repository Updates (SRU). These SRUs are what you will want to rely on to operate a high quality Solaris 1. It happens that Oracle has been shipping the first SRU and the pkg info commands allows to understand versioning scheme. Name: system/kernel. Summary: Core Kernel. Description: Core operating system kernel, device drivers and other modules. Category: System/Core. State: Installed. Publisher: solaris. Version: 0. 5. 1. Build Release: 5. Branch: 0. 1. 75. Packaging Date: November 1. PM Size: 3. 2. 3. MBFMRI: pkg: //solaris/system/kernel@0. T1. 84. 93. 5ZThe relevant information can be found in the Branch or in the FMRI attribute: It can be deciphered as follows: 1. The trunk identifier. This is an indicator for Solaris 1. GA. Lower build numbers are indicators of older developer releases (1. Solaris 1. 1 Express). You will want to deploy your application on build 1. This digit is defacto frozen for Solaris 1. It documents that Oracle and Sun worked for seven years on Solaris 1. The next 0 is indicating the update release. Solaris 1. 1 is brand new. There hasn't been an update release. This number is likely to be incremented when update release will happen. This 0 translates into the . This is the first SRU for Solaris 1. Oracle's first patch bundle. It has been released a few days after the intial release. More of them are likely to follow. It'll take support contracts and access to the the Oracle support repositories to obtain these patches. This field doesn't seem to get used. These seem to Oracle internal counters which are likely to distinguish internal builds in between SRUs. They have no relevance to regular users. Higher SRUs levels shouldn't break anything. They're supposed to fix bugs. Higher update levels aren't supposed to break anything either. They may add new functionality without breaking old APIs. Oracle is updating the support repositories on demand in between SRUs. Every update in the support repositories will lead to an increased version number of the package . It's a developer focused Solaris 1. November 2. 01. 0. It's of little interest for everyone who wants to invest into Solaris 1. November 2. 01. 1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2017
Categories |