I started by backing up the virtual machines (basically shut them down and tar'ed them up). Then I followed the direction for doing a network upgrade for Ubuntu servers. BTW, this took a while, I should have done it inside a screen session.
# apt-get install update-manager-corePresumably I did that during the 8.10 upgrade, so on to step 2:
Reading package lists... Done
Building dependency tree
Reading state information... Done
update-manager-core is already the newest version.
# do-release-upgradeAt this point installs started and I answered various questions. I won't mention all of them, just hit the highlights...
Checking for a new ubuntu release
Done Upgrade tool signature
Done Upgrade tool
Done downloading
extracting 'jaunty.tar.gz'
authenticate 'jaunty.tar.gz' against 'jaunty.tar.gz.gpg'
...a few minutes go by here...
1 package is going to be removed. 23 new packages are going to be
installed. 270 packages are going to be upgraded.
You have to download a total of 188M. This download will take about
15 minutes with your connection.
Fetching and installing the upgrade can take several hours. Once the
download has finished, the process cannot be cancelled.
Continue [yN] Details [d]y
Fetching
...25 minutes of downloading go by here...
I kept my version of the following files:
- /etc/apache2/ports.conf and /etc/apache2/sites-available/default
- /etc/apt/apt.conf.d/50unattended-upgrades
- smb.conf
Then I went ahead and answered yes to reboot and when the VM came back up, all looked good.
$ cat /etc/lsb-releaseVMWare tools were even running:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.04
DISTRIB_CODENAME=jaunty
DISTRIB_DESCRIPTION="Ubuntu 9.04"
$ ps auxwww | grep vmwareThat's it.
root 2448 0.3 0.1 2204 660 ? Ss 22:21 0:02 /usr/sbin/vmware-guestd --background /var/run/vmware-guestd.pid
Upgrading another VM, I saw the following message, which I thought was interesting. I went ahead and said "y":
Continue running under SSH?
This session appears to be running under ssh. It is not recommended
to perform a upgrade over ssh currently because in case of failure it
is harder to recover.
If you continue, a additional ssh daemon will be started at port
'9004'.
Do you want to continue?
No comments:
Post a Comment