In the spirit of contributing something useful to this thread, I have a few questions.
First of all, I'm running OpenSolaris in VirtualBox 2.1.4. Build 107 didn't boot for me once I installed the VirtualBox additions. I'm not sure why, and I'm not familiar with the procedures to check the error logs on why it didn't. This happened to me after several installations. Also, I have another computer where OpenSolaris is installed on bare metal. It runs solidly, but if I run the update manager, I am able to boot into it, but the GUI package manager doesn't work, and the notification area in the top panel is empty. Thanks to ZFS, I was able to roll back to the previous state in the Grub menu. Again, I don't know where to check the logs, so I can't report any more than that. Given the fact that build 107 didn't work for me, I'm sticking with build 106, which so far seems to be fairly reliable. What I hope to get out of OpenSolaris is to have access to the latest and greatest packages, but not necessarily run absolutely cutting-edge versions of the OS. For instance, I'd like to get updates for software packages from the dev repository as opposed to having to wait 6 months for each release. So here are my questions: 1) Are there any simple procedures to check for error log output in the event of bugs as I described? 2) What's the best way to "keep my ear to the ground" in terms of gaging the stability of any new build? 3) What's the best approach to stay cutting edge, but not bleeding edge? -- This message posted from opensolaris.org _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
