Tom Mueller (pkg-discuss) wrote: > For the server, then it would seem reasonable to document the interface > in terms of the SMF properties. Although this does make the the > documentation Solaris-specific - I'm not very worried about that for the > server though since our primary deployment platform for the server is > Solaris.
Right, but until we have that SMF interface implemented, I need to document it in terms of editing cfg_cache. Once the SMF aspect is implemented, the idea would be that the manpage documentation would simply state that these values could be directly edited via cfg_cache if SMF was unavailable (or something to that effect). My hope is to make our documentation as useful as possible to our primary deployment platform while still being useful to other ones. > For the client, I don't see what SMF service would be associated with > the image itself, such that the cfg_cache is a cache of SMF properties. > So I don't see how the name follows for an image (user or full). See section 2.2.1 of docs/image.txt; in short, this gives an administrator a way to setup defaults for control over image behaviour. I'm not the person who invented the concept, so I'll rely on others to explain further. Cheers, -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
