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.