By Gerry Haskins-Oracle on Apr 12, 2013
We're tweaking the naming convention used by Oracle Solaris SRUs (Support Repository Updates) to use a 5-digit taxonomy.
For example, Oracle Solaris 188.8.131.52.0
The digits represent Release.Update.SRU.Build.Respin
For the above example, the old name would have been Oracle Solaris 11.1 SRU 6.4.
As with Oracle Solaris 10 and below, all bug fixes are putback to the tip of the source tree for Solaris 11, which is currently Solaris 11.1.x.y.z.
Therefore, these same SRUs are also the way to get fixes for systems installed with Oracle Solaris 11 11/11, in exactly the same way that Solaris 10 Kernel patches included code from all preceding Solaris 10 Updates.
As discussed in previously postings, systems should be updated to a later SRU, for example from Oracle Solaris 11 11/11 SRU13.4 to Oracle Solaris 184.108.40.206.0.
If you maintain a local Solaris Repository behind your firewall, both Solaris 11.1 and whichever subsequent SRUs you are interested in should be added to your Repo. This is because SRUs only contain the change delta relative to the preceding Solaris Update.
Solaris's long standing Binary Compatibility Guarantee coupled with the technical benefits of Image Packaging System (IPS) help to ensure a smooth update experience.