Stephane Chazelas <[email protected]> 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.
> Thanks. So if I understand correctly what you're saying, Solaris
> 11 may or may not be compliant, the OpenGroup doesn't tell us as
> much. Just that it should be possible to order/download a system
> from Oracle that uses Solaris 11 (that bears the name? That has
> some components of Solaris 11?) that one should be able to
> configure to be POSIX compliant using vendor supplied
> instructions?
It seems that this causes a similar problem as with certain Apple platforms.
While people know that on Solaris it was sufficient to prepend your PATH
with /usr/xpg6/bin:/usr/xpg4/bin to get POSIX behavior, I know of nobody wo
knows the exact procedure to apply to an Apple system to make it behave POSIX
compliant.
There are of course other problems, e.g. the well known fact that the POSIX
test suite in the past did not have a sufficient test coverage, so waitid()
from Apple slipped through the tests.
>From reading the rules in a previous mail about free POSIX certification for
OSS projects, I have in mind that passing the test suite permits you to
mention POSIX compliance for a certain amount of time. If you like to extent
this period, you have to pay.
Is there probaly a way to withdraw a certification after that time in case
that a new enhanced or fixed test suite is no longer passed?
Would it be a good idea if in future, the public information for a certified
system would include a description on what to do on a "standard installation"
in order to get a shell that could pass the test suite?
Jörg
--
EMail:[email protected] (home) Jörg Schilling D-13353 Berlin
[email protected] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'
