Andy Brown wrote: > Can anyone point me in the right direction, the file > /usr/sausalito/schemas/base/sauce-basic/capabilities.schema > > Appears to contain part of this, however I can't tie this up with info > that I've found from the CCE interface via the cceclient.
What can't you tie together? Ask a question and I'll try to answer. The overview: * User objects have a capabilities field * Various tasks need various capabilities * the Capabilities object is a holder for namespaces that enumerate capabilities. From cceclient try 'names Capabilities'. You should see the capabilities on the System. To make a new capability, all you need to do is use it. If your readacl or something uses ruleCapable(fooBar); then the fooBar capability exists. To make it usable you'd need to provide some mechanism to assign that capability to users. I don't know if the Qube capabilities page will autodetect everything on the Capabilities object, but I believe it does. In that case, provide a Namespace on Capabilities named the same as your capability (fooBar, here). See the examples for details. It's very elegant once you grok the details. :) As for docs - I don't know when the full docs will be available, I'm embarrassed to say. -- Tim Hockin Systems Software Engineer Sun Microsystems, Cobalt Server Appliances [EMAIL PROTECTED] _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
