> What's meant by a Micro binding?
I think "Minor" will do just fine (as we haven't ship "Micro" since 2.5.1) >> INTERFACES >> +-----------------------+------------------+------------------------+ >> | Interface | Classification | Comments | >> +-----------------------+------------------+------------------------+ >> | <klpd.h> | Consolidation | | >> | klpd_create | Private | libc.so, SUNWprivate | >> | klpd_getpath | | | >> | klpd_getport | | | >> | klpd_getucred | | | >> | klpd_register | | | >> | klpd_register_id | | | >> | klpd_unregister | | | >> | klpd_unregister_id | | | >> | | | | >> | PRIV_XPOLICY | | <sys/priv.h> | >> | (flag to setpflags) | | | >> | | | | >> | ppriv(1) -x | | New option | >> +-----------------------+------------------+------------------------+ > >> The intention is to fully document and publish the final versions of >> these interfaces in a future case, once the project team has had sufficient >> time to experiment with them and receive feedback from the community. > > I'm unclear on what is actually being delivered by this case. > Is there a policy daemon delivered? If so, what policies (privileges) > does it support? If not, why is this case being brought at this > time? Is it just too hard to keep the kernel in sync with prototyping > of FGAP? Are there some OS.O dependences that can't be met with a > project consolidation/gate? If this is dormant functionality, how > will it be tested from build to build? No, this case publishes exactly these interfaces and does not include a policy or or policy daemon. The list of interfaces here is complete. There is a particular community member which has requested these interfaces brought forward ASAP. Casper
