Earlier I had mentioned my issues running Intrepid on VirtualBox. After doing some reading, I decided to upgrade from the “latest stable” VirtualBox 1.6.6 to the 2.0.0 version. This seems to have solved all of the issues I was having with failure to boot.
Vbox 2.0 installed Intrepid and ran the .26 kernel ok and upgrading to .27-3 didn’t break it. Thats a good start! Sure, running an Apha OS on a RC VM may not be the optimal solution, but it is working here. My initial feeling is that its looking good, but I’ll keep you updated as more runtime use either validates or invalidates my initial experiences.
The UI freeze for Intrepid has been implemented, so now it is crunch time for the Ubuntu Documentation Team. There are about three weeks before the string freeze, so special emphasis needs to be placed on reviewing the documents and fixing them now.
Matthew East made an appeal to the Ubuntu-Doc mailing list last night, now I’m going to make an appeal to blog readers and Ubuntu users at large. If you have Intrepid installed please take a few moments and scan through the documents. If you see an error, omission, or typo please take a moment to submit a bug report. Your bug reports help us make the documentation better.
As a side note, the reason I am making this appeal to folks is directly related to Ubuntu’s 6 month release cycle. The documentation for the newest release is always rushed for time, because it is almost counterproductive to do major work prior to the UI freeze. That leaves only a short window of opportunity before the string freeze. Yes we will continue to improve and fix the documentation as bugs are found, but once the string freeze is implemented, doc patches can’t happen until after release.