On 04/21/17 08:47 AM, Joerg Schilling wrote:
Stephane Chazelas <stephane.chaze...@gmail.com> wrote:
OK, "Solaris 11 and its maintenance releases" make more sense
than "Solaris 11 FCS and later". Thanks for clarifying.
This is how I thought Solaris always was maintained:
There are updates to a specific version that grant not to
break interfaces.
In other words Solaris 11 and Solaris 11.3 are something different, while
Solaris 11 update XXX is still Solaris 11.
That is incorrect. The "update XXX" naming has always been internal to Solaris.
Solaris 10 and prior releases used the date for the marketing name ("Solaris 7
8/99", "Solaris 10 8/07", and so on). Solaris 11 adopted the Oracle naming
conventions, so "Solaris 11 update 1" is marketed as "Oracle Solaris 11.1",
"Solaris 11 update 3" is "Oracle Solaris 11.3", and so on.
Whether or not interfaces may be broken depends on the declared interface
stability level - Private or Volatile interfaces can be broken at any time;
Committed interfaces should not be broken in an update release, whether it's
named Solaris 10 8/07 or Solaris 11.3. I believe all non-deprecated interfaces
specified by the POSIX & X/Open standards are Committed.
While people know that on Solaris it was sufficient to prepend your PATH
with /usr/xpg6/bin:/usr/xpg4/bin to get POSIX behavior,
Hopefully they know that is the current implementation, but the standard
mechanism is "getconf PATH" as defined in:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/confstr.html
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/getconf.html
so that if we add /usr/xpg7/bin in a future version, they'd get that too.
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - http://blogs.oracle.com/alanc
