Thanks for the edits and feedback, Alan. Some responses inline.

Jyothi

On 04/17/09 15:53, alan mcclellan wrote:
> Jyothi, sorry that I'm late in getting to this, but here are some inputs. 
> (FYI: I was working from the doc on  
> http://dlc.sun.com/osol/docs/content/2009.06/IMGPACKAGESYS/.)
>
> * Update Manager section.
> It reads funny to say 
>       "complete documentation for the Update Manager is 
>       available in the Help menu of the Package Manager application." 
>
> I know it's true, but I do read it twice to make sure I'm getting it. Guess 
> this isn't really a doc issue, but does make me ask, why isn't there a help 
> option on Update Manager?
>   
The UM is a separate app and does not have any menus, hence the help 
info is included in the PM Help.
> * Installing and Managing Packages -  I like the list of "how to" things you 
> can do with IPS commands. 
>
> * Learning about IPS - I like the separation of user and developer tasks. I 
> would like to see this more clearly spelled out at the chapter level. Is 
> there any way to do that? It sure would make it more straightforward to find 
> the information I might need if I were wearing one user hat over another. 
>   
Since a developer is a "superset" of "user", I didn't want the make 
topics  to
> * Why Should You Create an Image" -  In the following sentence, drop the s in 
> "images." 
>
>       An images can be one of these types:
>
> * Why Should You Create an Image - Unfortunately, after reading this section, 
> I couldn't answer that question. 
>   
> * Actions in IPS
>       - I wasn't sure why I should care about this, although I'm sure there 
> is a reason.
>   
I will see what I can add/edit to make the above sections clearer.
>       - In the table in Driver row, remove one "T" in "TThe."
>
> * pkg(1) Command Reference - Seems odd that chapter 10  title and first 
> section have the same name. Can they be combined into one page? 
>
> * Accessing a Windows Server from OSOL 2009.06 - while this seems like 
> interesting info, why is it in the IPS document? What's the specific 
> relevance to IPS? 
>   
I wanted to call attention to the specific package available in the repo 
to access a Windows server. I agree this is not specific to IPS.
> * General comment - I noticed that some procedures said to become 
> "superuser," while others said to become "root." Should these be 
> standardized? And others use "pfexec."
>   
Good point. I will edit accordingly.



Reply via email to