Yes, I can make that change. I'm just not familiar with the manifestreader function, so I didn't realize that key-value pairs would also fall into a ManifestReader section. Can I name this new section "Using ManifestReader", or is there a more descriptive title?
Barbara On 11/11/08 11:37, Jack Schwartz wrote: > Hi Barbara. > > Response inline. > > On 11/10/08 17:04, Barbara.Lundquist at Sun.COM wrote: >> Jack, I've made these edits in my master copies. Please see my added >> comments below. There's >> a few responses worth noting. > <snip> >> >> >>> Note: it may be clearer to the reader to put how to use ManifestRead in >>> a different section, and refer to that section from here. Then you can >>> just state that the first arg is just the server socket file name and it >>> is used with the ManifestReader, and see section xxx on how to use the >>> ManifestReader. >>> >>> If you do this, you can put the key/value pair section (starts on page >>> 14) there with it. >>> >> I'm unclear on this piece, so will leave as is for now > This comment pertained to the table on page 13. I was suggesting to > reduce the "Server socket file name" description to something like this: > > The first argument is the manifest reader socket. This argument > specifies the > socket that is used with /usr/bin/ManifestRead for accessing the > manifest data. > Please see section xxx on how to use the ManifestReader. > > and then have a different section dedicated to the ManifestReader > which takes the rest of the text (the remainder of the "Server socket > file name" description in table 2.2) plus the stuff in the key/value > pair section. > > Does this make more sense? > > Thanks, > Jack > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20081111/bc3380d4/attachment.html>
