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.
I just got an email from Oliver Gerlich regarding my post about Intrepid and VM’s. It appears that this issue is indeed an Intrepid problem and a bug has been filed on it. Looking at the thread there are some workarounds that are stable but slow, but I’m hoping that the upcoming kernel patches solve the issue.
In the same email Oliver noted that my Planet Ubuntu Feed was broken. To be quite honest I set it up and never bothered to check on it other than to see that I was listed. For all you wordpress.com users that are also Planet Ubuntu Members, try adding /atom to the end of your feed URL if clicking on your post title sends you back to the planet instead of to your blog post. As an aside I’m also wiping out my planet-ubuntu category because I can’t find an option to hide that categories in the widgets. Thanks Oliver for bringing the bug report to my attention and pointing out the glitch in feed URL handling between planet and WordPress. Although I’ve had this WordPress blog for a little while, I’m an oldtime MT user and haven’t quite got the hang of WordPress.
My experiences so far with Intrepid and Virtualbox have been less than stellar. I’ve has issues with Alpha 4 and am trying to get Alpha5 working correctly now.
I’m not sure if it is a Virtualbox issue or an intrepid issue, so I’ll most likely try running VMWare to see if I get better results.I have heard through the grapevine that its an Intrepid issue, but until I’ve tried on least VMWare I’ll have to pass on judgment.
Either way I’m starting to get a little antsy because string freeze should be coming up soon, not having a clean VM of Intrepid will hinder my work on the documentation. There is always a chance of epic failure whenever using a alpha OS but when I was working with Hardy I had very few issues overall and certainly none that kept me from booting from a VM or sparate partition.