I performed a Linux Server upgrade from 12.04 LTS to 14.04 LTS last night. Disaster. Well, the upgrade wasn’t quite as seamless than I thought. Apache died. I was getting 500 error on all my websites. I wasn’t about to spend hours trying to fix Apache, and who knows what else was not working. I have several applications running on my Linode VPS server in addition to the standard LAMP. So, I started the image recovery 20 minutes after I found out things weren’t working as well as they should be. My only other option now is to create a new server from scratch with the latest Ubuntu Server release, and then migrate all my apps and data. I think I’ll wait for 16.04 LTS to come out in a couple of months.
If you’re running an older Ubuntu version and you want to upgrade to the latest 14.10 Utopic Unicorn, there are two ways of doing it. You can upgrade from the Ubuntu Gnome desktop via Software & Updates or you can run the upgrade via the Terminal using this command.
Be sure the backup your previous work. There’s a third option. Install Ubuntu 14.10 from scratch.
Ubuntu 11.04 recently upgraded to Linux kernel 2.6.38-11. Unfortunately, every new Linux kernel introduced on your system will break your Virtualbox setup. This article will show you how to fix Virtualbox with a new kernel. The error will appear if you try to launch a Virtual Machine. You will most likely get the following errors:
As detailed in the error box, you will need to run vboxdrv setup to fix the problem. All you need to do is open up the Terminal and type this command:
$ sudo /etc/init.d/vboxdrv setup
As displayed in the Terminal, the vboxdrv setup will stop the current Virtualbox kernel module, uninstall it, register a new kernel module, and finally start it. This completes the Virtualbox upgrade that’s necessary after each Linux kernel upgrade.
So, in the future, if your Ubuntu distro upgrades to a newer Linux kernel, you know exactly what to do to make your Virtualbox work with the latest kernel.
I upgraded to WordPress 3.0.2 just the other day. Now WordPress 3.0.3 is out. This particular upgrade is not critical by any means, but it fixes a bug in the remote publishing interface that allowed authors and contributors to have improper access to certain posts.
As mentioned in the WordPress.org blog, the remote publishing feature is disabled by default. You have to turn it on to enable the feature. You can access remote publishing from the Settings – Writing in the Dashboard.
If you’ve never heard of the remote publishing feature in WordPress, you are most likely not using this feature. So, the question is, is it worth upgrading to WordPress 3.0.3? Probably not, but WordPress upgrades are relatively painless nowadays.
All it takes is a click of a button. It’s as simple as it can get. In any case, I suspect most WordPress users will probably upgrade to 3.0.3.
If you don’t upgrade, no harm will be done, except for the incessant Please update now messages in the WordPress Dashboard. If you can ignore the hounding, you’re a better man or a woman. In my case, I’m upgrading just for this purpose.
It’s good enough reason for me to update to WordPress 3.0.3.
There is a mandatory upgrade to WordPress 3.0.2 from all previous versions. This is a maintenance release to fix a moderate security issue which allows a user with an author level access to gain access of the rest of the site. The upgrade is particularly important to blogs with multiple users, and all others.
There should be no valid excuse not to upgrade to version 3.0.2 since WordPress upgrades are easy and painless. All it takes is just one click. I upgraded my blogs just a tad different than most WordPress users. I use Subversion update. I have a script that updates all my blogs all at once. Based on the Subversion upgrade, there are only about a dozen files that have changed.
So, update to WordPress 3.0.2. It should be quick and worth the while.
I was able to perform a WordPress 3.0 upgrade yesterday. It went without a hitch. Making a single blog into a multi-site blog was a bit more involved. It wasn’t entirely a smooth transition because WordPress somehow detected that I already had a network running, which was simply not true. I ended up cutting and pasting several pieces of code to configure wp-config.php and .htaccess. In the end, the upgrade was a success.
Just a couple of minor things that I want to mention. The current version of of the Google Sitemaps plugin no longer works with WordPress 3.0. I’m not sure why. I also ended up removing the ‘blog’ slug from the permalink, so that it didn’t break my old permalinks. I also had to reconfigure the plugin called ‘Download Manager’ because it didn’t work after the upgrade.
This is probably the most involved WordPress upgrade I have done. It’s was involved because there were a large amount of features and enhancements in this version as well as merging WordPress and WordPress Mu. Congratulations to the WordPress Development team for making this release a huge success.
A recent article from CNNMoney stated that as many as 31% of Windows users have reported problems upgrading to Windows 7. Most of the problems are with the installation and migration of data.
One common gripe, experienced by 9% of installers, is that the half-hour to an hour-long upgrade process gets to the “62% completed” point and then freezes. It’s a problem that Microsoft is aware of, and can be fixed by rebooting the computer, going into advanced settings, and typing in a code that instructs the computer to ignore plug-ins.
Here’s the top 10 list of common problems:
- Problems with installation – 31%
- Missing applets or components – 26%
- Aero theme is not running – 14%
- DVD drive not found – 8%
- Hidden extensions – 6%
- Too many minidumps – 6%
- Aero snap problems – 3%
- iPhone won’t sync with Windows 7 – 2%
- Custom icons get changed with new theme – 2%
- Taskbar problems – 1%
If you are thinking of using Windows 7, you are better off not upgrading. The ideal is to get a system that already has Windows 7 installed. If you have Windows Vista now, opt for a clean installation. Backup all your data to a USB hard drive, install, and restore your applications and documents.
It’s just a few days away from the official release of Ubuntu 9.10 Karmic Koala. Are you wondering how to upgrade your desktop or laptop to Ubuntu 9.10? There are two ways in getting Karmic Koala installed on your system. You can:
- Upgrade using the Update Manager
- Perform a Clean Install
Press Alt-F2. Type in “update-manager -d.” Update Manager will open and tell you a new distribution release â€˜9.10â€² is available. Click Upgrade.
Download the appropriate ISO from Ubuntu. Ubuntu 9.10 will be available from this download page after the official release on Oct. 29th. Prior to that, you can find it here. Burn the ISO to a CD. Boot from the CD to perform the install.
If you can’t wait, you can upgrade now.
This is a security release. So, I better do it. It took me less than a minute to upgrade all 5 WordPress instances. Thanks to the little shell script. The upgrade was a breeze. You got to love Subversion. It beats the automated upgrade feature in WordPress. I heard a few glitches with that feature, but this is solid.
I finally decided to upgrade my Ubuntu Server running on an old PC from Ubuntu 8.04 LTS Hardy Heron to the latest release, Ubuntu 9.04 Jaunty Jackalope.
As most of you know, the Ubuntu Server lacks a desktop environment such as Gnome or KDE. The server is managed from the Terminal via a SSH connection.
The following detail the steps necessary in upgrading the Ubuntu Server from one version to the next. Before an upgrade can begin, it’s always a good idea to get the latest updates from the repository.
sudo apt-get update sudo apt-get upgrade
If you are upgrading from a LTS release to a normal release, from Ubuntu 8.04 to 8.10 for example, you’ll need to edit the release-upgrades file. If you are upgrading from a non-LTS version to a non-LTS version, you can skip this step altogether.
sudo vi /etc/update-manager/release-upgrades
You can now perform the actual upgrade.
sudo apt-get install update-manager-core sudo do-release-upgrade
Grab yourself a nice cup of coffee, a movie and some popcorn. The upgrade process may take several hours to complete depending on your server hardware and internet connection.