On Fri, Aug 1, 2008 at 11:21 PM, Kathy Slattery <[EMAIL PROTECTED]> wrote: > Mike, > > Please see my comments below: > >> On Fri, Aug 1, 2008 at 5:39 PM, Kathy Slattery >> <[EMAIL PROTECTED]> wrote: >> > 1) send any corrections to me or to the alias if >> discussion is needed >> >> Page 10: "kill -9 <pid>" should only be used if "kill >> <pid>" doesn't >> work. Those that subscribe to the "kill -9" >> philosophy are likely to >> be the same ones that suggest pulling the power cord >> (and battery, if >> applicable) to shut down a system. It works, but it >> doesn't allow >> things to come down cleanly. > > The reason that I used kill -9 in this case was that kill didn't work. > I could change the procedure to use kill and then add a note > suggesting that they use -9 if kill doesn't work. Would that be better?
That would probably be better. >> Page 25: >> - Quotas only affect data written after compression >> is enabled. >> - Based upon failures that I've seen on sparc with >> live upgrade and >> manually tweaking compression, I think that >> compressed / may not work >> (I may be wrong). If so, this should be noted. >> > > OK, I'll get someone to give it a try. Be sure that you try pkg image-update et. al. or (better) confirm whether it is intended to be supported or not. >> > 2) tell me about any procedures that we should add >> >> As others mentioned, pkg. beadm and grub probably >> belong nearby. > > Will pointers to the coverage in the Getting Started guide > be enough? or do we need more? We had some GRUB > procedures in an earlier working copy, but none of them > worked right, so we cut them. Is there something in > specific you'd like to see? I guess I'm not sure of the role of the two documents. I'll have to look around a bit more to see if I have some suggestions on how this would make most sense. >> Compatibility with pkgadd >> > > Do you want us to tell them how to run pkgadd? > With the new packaging system, we were staying away > from mentioning pkgadd. Are there useful packages > that you could add to an OpenSolaris system? Studio 11, needed for ON development is a key one. If I were bringing this into an existing Solaris environment I may have my own or third party packages to install. >> Multi-boot configuration with Windows, Linux. Major >> bonus points for >> any tips for sharing data between OS's in a >> multi-boot configuration >> without network storage. >> > > Multi-boot is covered in the Getting Started Guide. > Again, do we need more pointers? I'll look... > > I knew the sharing data question was going to come up. > Unfortunately, I'm not sure that I can get fully tested > procedure ready by Wednesday, but if I can't we will > get something in as soon as possible. Quite understandable. -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
