> 1) Are there any simple procedures to check for error > log output in the event of bugs as I described?
Suppose build 107 is in your boot environment (BE) "opensolaris-2", which you have failed to boot into, and you are now booting into build 106, which has been installed as BE opensolaris-1 . To look at what caused the boot failure, you can do the following procedure; pfexec beadm mount opensolaris-2 /a cd /a/var/log cat Xorg.0.log and cat Xorg.0.log.old It will list the log(s) of your failed, updated, boot environment. (Now a brief commercial break: I don't think you will find any other operating system that will allow you to do this so conveniently. Viva OpenSolaris!) > 2) What's the best way to "keep my ear to the ground" > in terms of gauging the stability of any new build? Jim made a great suggestion. We should have a number of OpenSolaris addicts who can be organized into providing real time bug summaries. It will save a lot of our time. > 3) What's the best approach to stay cutting edge, but > not bleeding edge? Welcome to the OpenSolaris land (really). Just do an image-update (in junction with your point No. 2, to avoid getting into unforeseen/unrecoverable disaster). If you can stay in the bleeding edge, great (should be the case most of the time). If not, then just do a "beadm activate (old BE)", you should be able to retreat to the cutting edge. -- This message posted from opensolaris.org _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
