> The one described in ddi_cred(9f).
>
> > crsetugid() won't change incompatibly.
>
> That's not what "Evolving" means, as I understand it. That is, if we're
> going to start using this new interface, it'd be nice to know that it's not
> going to change out from under us. But admittedly, the issue is mostly
> academic; after all, we run on Linux, too. :-)
For kernel interfaces (and many others[1]), "Evolving" has really meant
"Stable" and in fact, some recent changes to the classifications available
during architectural review now reflect this. It will take a little while
manpages to be updated accordingly, but in short: when you see "Evolving"
in a section 9F manpage, you can treat it as "Stable", meaning "will not
change in a minor release of Solaris" (where S10 is a minor release).
[1] We have several architectural comittees at Sun, and unfortunately
they did not all agree on the original interpretation of "Evolving".
PSARC, which reviews the vast majority of core kernel, library, and
command interfaces that you are likely to use, has consistently viewed
"Evolving" as "Stable".
--
meem
_______________________________________________
networking-discuss mailing list
[email protected]
