April 30th, 2010
Ubuntu 10.04 LTS (Lucid Lynx) 32-bit and 64-bit Images Available
Canonical released Ubuntu Lucid Lynx earlier today and we are pleased to announce that the 32-bit and 64-bit version are now available for your slice as well.
Something to take notice of is that this release is an LTS (Long Term Support) version. This means that Canonical will continue to provide security updates and bug fixes for the applications available from their repositories for a period of five years, as opposed to 18 months with a normal release.
If you wish to take advantage of this new Ubuntu Lucid image, please login to the SliceManager to create a new slice or you can perform a rebuild of an existing slice. Keep in mind that a rebuild will erase any existing data on the slice.
Our community liaison, Jered, was nice enough to put together a few setup articles to help you get started right away with configuring and securing your Ubuntu Lucid slice.
There is also an Ubuntu Lucid category where you can find other articles that have been tested for this distribution.
On another note, Canonical will end support for Ubuntu 8.10 Intrepid Ibex tomorrow April 30th, 2010. Therefore, we will be removing this image as an option in two weeks time to avoid any complications. If you wish to preserve a base image of Ubuntu Intrepid, you can do so by creating a backup in the SliceManager.
If you have any questions or would like to speak directly with a member of our support team, we are available 24 hours a day in our official SliceChat room. Additionally, please feel free to email us at support@slicehost.com at any time.
April 30th, 2010 at 01:14 PM Trevor
That was fast! Nice work
April 30th, 2010 at 01:44 PM kirk
woot!
April 30th, 2010 at 03:18 PM John King
Nice try, but Linode was faster.
April 30th, 2010 at 04:03 PM Martha
Nice and fast, thanks for getting that out. Rebuilt my Slice last night!
April 30th, 2010 at 07:46 PM Busara
Awesome – excellent work, slicehost team.
April 30th, 2010 at 09:00 PM Michael
+1 to speed
May 1st, 2010 at 03:04 AM steve
Awesome, amazingly fast
May 1st, 2010 at 11:48 AM Jesse
I made an upgrade on my slice.
1. Cloned the existing one as a backup. 2. Upgrade the old one. 3. Done, and I removed the clone.
It’s upgraded and running Lucid without rebuild.
But, the slice is still showing the the old distro, any way to update this?
May 3rd, 2010 at 02:54 PM Mark
Jesse,
If you create a support ticket in the SliceManager we can get it taken care of for you.
Also, note that the change is purely cosmetic and does not have any effect on your slice if you wish to keep it the way it is.
May 10th, 2010 at 01:30 AM Luis
Jesse: have you rebooted yet? I was able to upgrade and reboot the first time (during the reboot process), but after that every reboot died hard with ureadahead errors. I didn’t have time to investigate very much last night; enough googling to (1) find that there was no record of identical error messages or fixes and (2) it might be related to virtualization, which suggested the fix might be very involved.
I rolled back to the backup and everything has been fine, so big thanks to slicehost on making that work great, but it would be nice to have some advice on upgrading existing slices rather than installing a new one.
May 10th, 2010 at 03:31 PM Jered
To be honest, we haven’t wanted to put out an article on upgrading to Lucid because we don’t want to give upgrades that kind of blessing from a support perspective. On a production server it’s much, much safer to migrate to a clean install of a new distribution version than to kick off an upgrade on your server and hope for the best. It’s just not worth the risk that a hidden problem may crop up down the line, even if the upgrade appears to go well.
But that said, Luis, have you tried updating the kernel on the slice you were upgrading? The kernel is managed by the VM and updated through the SliceManager, and can’t be controlled by aptitude from the slice itself.
May 10th, 2010 at 10:38 PM Luis
But that said, Luis, have you tried updating the kernel on the slice you were upgrading? The kernel is managed by the VM and updated through the SliceManager, and can’t be controlled by aptitude from the slice itself.
That is what I suspected. I did not directly upgrade the kernel myself; I just used apt.
And totally understandable that you don’t want to support that. Given that, pointers on non-upgrade migration (how to slop the data around, and how best to keep data in a movable state) would be a great service you guys could provide.
May 11th, 2010 at 06:27 AM Jered
On shuffling data around, we do have an article on rsync that can help with the basics of moving data over to a new slice. Writing a series on how to prepare a slice for migration and doing a migration itself is a good idea though. I’ll add it to the list.
May 30th, 2010 at 04:22 AM Jesse
Luis,
I have no problems with rebooting. Now, I just switched to the latest kernel 2.6.32.12.
May 30th, 2010 at 04:25 AM Jesse
Other things to be taken as consideration:
I made an upgrade from Hardy, which is a previous LTS version. So, I don’t know if this could be taken as a good advice but It’s safer to upgrade it between LTS versions.