Sorry for the binary content in the first attempt to reply....
Alan Coopersmith <alan.coopersm...@oracle.com> wrote:
> 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.
So is it possible that Stephane is correct and some POSIX interfaces may have
been broken meanwhile?
> > 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.
BTW: One problem I see with this method is that there are different versions of
the standard and that it may be hard for people to know that they would need to
call
/usr/xpg6/bin/getconf PATH
to get the right one. Do you see a better way?
Jörg
--
EMail:jo...@schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'
