On Mon, Sep 15, 2008 at 7:26 PM, Kathy Slattery <kathy.slattery at sun.com> wrote: > Peter, > > Thanks for your comments. I'm not sure what happened to this message, > but I couldn't find this thread until this morning. Very strange. No doubt a > network or server glitch of some sort.
As Alan said, if you're using the forums (which it looks like you are) then things are getting a bit out of sync. Never mind. >> On Wed, Aug 20, 2008 at 6:42 PM, Kathy Slattery >> <kathy.slattery at sun.com> wrote: >> > A new version of the OpenSolaris System >> Administration Guide >> > that will be included in the Student Pack can be >> found at: >> > >> > http://www.opensolaris.org/os/project/indiana/files >> >> Some quick miscellaneous comments: >> >> It says 'your laptop'. I feel that's a little too >> specific - readers >> may interpret >> that as meaning you can't use other types of >> computer. > > OK, I'll remove any specific mentions of "laptop". > We were told to focus on the laptop user when putting the > information together, but I don't need to do that in the text itself. Well yes. It's clear that laptop users are a major focus point, but it's applicable to any type of computer (although some of us might have to skip the bit about wireless). >> Page 10. I wouldn't introduce svcadm before >> mentioning svcs. > > Do you think I need a section introducing SMF, svcs and svcadm before the > procedure? We we trying to keep things as simple and clean as possible. > Another > option would be to add a reference chapter that covers these topics. What do > you > think would be best? I think you need to define SMF, and say that you can use the svcs command to see which services are running. It probably doesn't need to be more than that, but that would give a curious new user enough of a hint that they would know what to look for if they wanted to learn more. And that's it really - just enough breadcrumbs to give them a start. Otherwise svcadm is just gobbledygook out of the blue. (I would note in passing, though, that I've ended up using the phrase "using svcadm" when explaining to developers what they have to do, as it's the name of the command they have to type, rather than tell them to "use SMF".) >> Page 11/12 modifying NWAM. Step 5. You don't restart >> the service, you enable >> it again. >> >> Page 13 'Manually configuring a wired connection'. >> Step 2. Should disable >> come before enable? Step 3. So how could you tell >> that bge0 is the wired >> interface? I mean, I know that the wired broadcom and >> ath0 the wireless >> atheros, but how does a new user work that out? >> >> Page 14/15 Manually configuring wireless. Same as >> above. Step 6, is that >> "connect-wifi-e" or "connect-wifi -e"? > > I think Steff covered most of these issues. There is a space in > the source before the -e. There's another one on page 36, so > I'm not sure why this one isn't rendering properly. I'll look into it. > >> >> Page 25 Monitoring ZFS disk space. It should be >> explained that ZFS quotas >> are something different to normal filesystem quotas. >> It may be better not to >> refer to them as quotas at all. Something like 'You >> can limit the >> amount of space >> used by a ZFS filesystem by ...'. (And a note that >> snapshots count against >> the limit too.) > > I'll ask Cindy to fix or comment on this one. One of the problems > with a book by multiple writers. I don't "own" all of the text. > >> >> Page 27 'How to see available NFS shares' Confused >> me. What's missing from the >> text is that 'localserver' is the host that you want >> to query to see >> what filesystems >> it's exporting. Otherwise it appears in the command >> for no reason. (And would >> 'remoteserver' be a better name?) >> > > Remoteserver seems a better name. I'll change it and add a little > more text to make it clearer. > > Thanks again for the comments. You're welcome. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
