Updates to Ubuntu have, for the most part, been without drama. Updates to 11.10 are equally without drama. The updater for Ubuntu performed its task flawless. When finished I rebooted the VM to check that it at least started correctly.
I've had a question about whether the distributions would keep up with the Firefox release schedule. The answer is a good news/bad news kind of answer. The good news is that yes, Ubuntu (and Linux Mint below) do keep up with Firefox, at least up to 9.0.1 in both of these. The bad news is that Firefox 10 has been released, and it's landed on all the Windows boxen and VMs in the lab. The only Linux distribution that is fully up to date is Fedora 16 (see more below).
Bringing Linux Mint 12 up to date was as painless as bringing Ubuntu 11.10 up to date. I just find it somewhat surprising that the update UI is so different between the two distributions. I can't say which one is better; they both get the job done without getting in the way.
Once the update was finished I performed a nominal check, restarting the VM to make sure it started properly and all services were operational. Again, checking Firefox, it was at version 9.0.1. I'm assuming that because Linux Mint is downstream from Ubuntu, that it forces Linux Mint to be in lock-step with Ubuntu's versions, so that if Ubuntu is just stepping up to 9.0.1 then Linux Mint steps up to 9.0.1.
Once the Ubuntu and Linux Mint VMs were updated and shut down, I installed an instance of 64-bit Fedora 16. I actually installed it twice, once to see what it was like with all defaults, then a second time to strip out all the bits I didn't want, and add in the few I did, in particular gcc and the kernel development bits. On first start, after installation had finished, I was presented with the Gnome 3 "Failed to Load" dialog. I expected this and wanted to see how Fedora would operate. It operated flawlessly, if only in plain old 2D mode on the desktop.
I'm still running with VMware Player 4.0.1 build-528992 in the lab, and have no plans to update something that appears to work just fine as is. So it was with a certain keen interest that I installed the VMware Tools in Fedora 16. For the most part it turned out rather uneventful, if boring. I took all the default settings (as usual).
At the tail end I got a kernel abort. What's interesting (and rather delightful, actually) about current kernels is their ability to trap the error, tell you about it, and continue on without crashing and burning. Rather than dig into this one, I decided to reboot.
A full reboot later and the VM came up, with a "fire alarm" signal on the upper panel. Part of the construction of this VM included updating all the files. I use 'yum update' to perform this, but before I could do that I had to let yum know about the network proxy.
I need to document this yet again because of so much poor information about how to do this on the web. To tell yum about a proxy, you need to do the following:
- su to root (su -)
- cd to /etc and edit yum.conf
- In the [main] section cursor down to the line 'installonly_limit=3' and add beneath that line the following text on a new line: 'proxy=http://proxy.domain.name:proxy_port_number'
I'm in the process of installing Fedora 16 with the KDE desktop in place of OpenSUSE. I'll write up a little note about that sometime next week.