Tuesday 15 June 2010
Looking at the next release of Ubuntu 10.10 with Virtualbox
As the first Alpha iso was placed up on the mirrors for us all to start having a play , I decided to run it up in a virtual machine and see what - if anything - has changed. The install went fine, with my first run I just followed the usual install options , clicking next, and then install. All went fine until right at the end it had to removed some information with "dpkg" and then it started to error. I clicked through these and it finished, in what on the surface seemed to be a successful and stable install. Once rebooted however, I noticed there was something wrong with the way packages were not being installed , so I decided that this initial release had issues. I did have a good look at the errors that were being generated, and it was obvious that those errors on install, were more of a problem than I had originally thought.
Not a big problem, as I left it over the weekend , knowing come Monday on the daily builds the problem would almost certainly be fixed, and it was.
So, rather than download the latest daily iso image, I used the really useful zsync utility to just upgrade my iso - look here on how to use this utility.
Once all was installed and up and running, I had a look around. At this early stage there is not a great deal to see, except the latest kernel 2.6.35 (see the picture above). Gnome is the same and most of the apps are the same, as far as I can tell, except the software centre which has had an upgrade and looks a much improved. I'm sure most of the underlying apps have had their versions bumped, but to the eye it looks very similar to Lucid, not surprisingly.
I installed Google Chrome to see how that worked with the new OS, and all went well. It is worth doing this, as under the virtual image this gives you just that little extra performance.
At least the Meerkat is out of the cage now so I can keep an eye on where this great distribution is heading next in it's evolutionary track.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment