Ubuntu – Long Term Support

One item of particular interest with Ubuntu is their development schedule. Because a typical Linux distribution is composed of many applications from many different parties, the Ubuntu developers do not directly control or develop a lot of the software included in Ubuntu. Furthermore Ubuntu tries to be a complete desktop environment rather than just an operating system, which means it includes a wider variety of software than what’s found in Windows and Mac OS X.

What this amounts to is that Ubuntu needs to both provide future patch support for included applications, and it needs to compensate for the fact that they don’t develop many of these programs. Coupled with this is the fact that 2nd party application development is not necessarily synchronized to Ubuntu’s release schedule and some applications (and the kernel itself) can have a rather rapid development rate.

Trying to deal with all of these factors, Ubuntu has settled on two classes of releases. Every 6 months – in October and April – Ubuntu takes what’s ready and releases a new version of the OS. For 1st party material this is tied with some goal for the release (such as replacing the audio daemon) while for 3rd party software this may be as simple as grabbing the latest version. This puts regular Ubuntu versions in an unusual position when trying to classify them – it’s significantly more than a Mac OS X point update, still more than a Windows service pack, and yet a single release generally encompasses less than a new version of either OS. But at the same time, there’s no guarantee that any given release of Ubuntu won’t break software compatibility or binary driver compatibility, which puts it up there with major OS releases.

Furthermore because of the need to provide security updates for all these different programs in all of these different versions, Ubuntu has a very short support cycle, and in that cycle only bug fixes and security updates will be issued, software is not otherwise changed as it’s intended to represent a stable platform. A regular release is only supported for 1.5 years; which for example means support for 7.10 Gutsy, the immediate predecessor to 8.04 Hardy Heron, expired in April. This pushes new versions of Ubuntu back towards the idea of them being closer to a service pack or a point release. In essence, it’s intended that everyone using regular versions of Ubuntu will stick to a relatively rapid upgrade treadmill.

But this obviously doesn’t work for everyone, which results in there being two classes of Ubuntu. What we’re looking at today, 8.04, is what Ubuntu calls a long term support (LTS) release. Every 2 years a version of Ubuntu is labeled as a LTS release, which entails a much greater effort on the developer’s part to support that edition of the OS. The standard support period is 3 years instead of 1.5 years, and for the server edition of the OS that becomes 5 years.

This makes the LTS releases more comparable to Mac OS X and Windows, both of which have long support periods in excess of 3 years. This is also why we’re starting with a review of Hardy, in spite of it being over a year old now, because it’s the current LTS release. Regular short-support Ubuntu releases have their place, but they are not intended for long-term use. Coming from Windows or Mac OS X, a LTS release is the comparable equivalent.

Operating System Mainstream Support Extended Support
Windows 5 years 5 additional years
Ubuntu 1.5 years None
Ubuntu LTS 3 years None
Mac OS X So long as it's the newest OS So long as it's one version behind

Unfortunately, in spite of the LTS designation, not all of the applications in a LTS release are intended to be used for such a long period of time, or are their developers willing to support them for that length of time. If we take Firefox for example, the last Ubuntu LTS release, 6.06 Dapper, shipped with Firefox 1.5. Mozilla very quickly ended support for Firefox 1.xx after Firefox 2 shipped, and now you can’t even get support for 2.xx now that 3.xx has been out for quite some time. This leaves the Ubuntu developers in charge of supplying security updates for the older versions of Firefox they still support, which while better than the alternative (no security patches) isn’t necessarily a great solution.

The Ubuntu developers have done a good job of staying on top of the matter (they just published a new 1.5 security patch as recently as last month) but it highlights the fact that the Ubuntu developers do not always have the resources to maintain both a stable platform and the necessary security updates. So while an LTS release is supposed to be supported for 3 years, in reality not every component is going to make it that long.

Digging through the bugs list for Dapper and Hardy, I get the impression that these kinds of cracks only occur on less-used software (particularly that which is not part of the default install, such as VLC), so an option for users who need to stick with the base OS for the entire life of a LTS release, but don’t mind upgrading a few applications can go that route and cover all of their bases. Unfortunately this is easier said than done, and we’ll get to why that is when we discuss the package manager.

What this amounts to is that if you’re the kind of person that intends to run a computer and an OS for a very long period of time – say on the scale of XP, which turns 8 this year – Ubuntu likely isn’t a good fit for you.

It’s Secure What’s the Value of Technical Support, Anyhow?
Comments Locked

195 Comments

View All Comments

  • LittleMic - Wednesday, August 26, 2009 - link

    http://en.wikipedia.org/wiki/NTFS_symbolic_link">http://en.wikipedia.org/wiki/NTFS_symbolic_link
    Well, Windows 2000 had symbolic links for a long time :-p (only for directory until Vista though)
  • ekul - Wednesday, August 26, 2009 - link

    ntfs has symlinks but the windows shell can't create or manipulate them. Pretty pointless. MS can (and does) use them in vista/7 but you can't make your own
  • Eeqmcsq - Wednesday, August 26, 2009 - link

    "hint: symlinks are your best friend. My home dir is littered with links to places on the filesystem I visit a lot to avoid a lot of clicking/typing"

    I use Gnome's bookmarks for that. Those bookmarks even include SMB shares on my other computers.
  • ekul - Wednesday, August 26, 2009 - link

    gnome bookmarks are very handy I just find symlinks to be more flexible since they work regardless of gnome vs kde, gtk vs qt and gui vs cli. Even wine can take advantage of them
  • jigglywiggly - Wednesday, August 26, 2009 - link

    one more thing you should have covered is battery life on laptops. Linux in general is pretty awful at managing battery life. Just web browsing 4 hrs on Vista on my vostro 1310(not using 7) but with Ubuntu 2 1/2. It's a huge difference, but oh well.
  • Ryan Smith - Wednesday, August 26, 2009 - link

    Laptops are out of our domain, that would be Jarred. If this two-part series is successful, I'll see what I can do about talking him in to putting some Ubuntu (or any Linux for that matter) battery benchmarks in. But I'm told a complete workup takes a while.
  • strikeback03 - Wednesday, August 26, 2009 - link

    On my Thinkpad T43, battery life is essentially equal between XP and Ubuntu. Ubuntu may even be slightly better, though I have never bothered with a formal test to put real numbers on both. Have you looked at whether the processor is throttling down properly or not while in Ubuntu?
  • sprockkets - Wednesday, August 26, 2009 - link

    "Now we have yet to touch on hardware accelerated playback, which is something we’re going to hold off on until we take a look at Ubuntu 9.04. Linux does not have a common media framework like Windows and Mac OS X have DirectShow/DXVA and QuickTime respectively. Rather the desktop environment that Ubuntu is based off of (GNOME) includes a lesser framework called GStreamer, which is closer to a basic collection of codecs and an interface to them. As such hardware accelerated playback is not as easy to do under Ubuntu as it is under Windows and Mac OS X. We’ll take look at the APIs and the software for this in our look at Ubuntu 9.04."

    Well, not exactly. There is this: http://en.wikipedia.org/wiki/VaAPI">http://en.wikipedia.org/wiki/VaAPI, which is not exactly widespread yet. nVidia's VDPAU, which provides hardware acceleration for h.264 and if you have the latest version of PureVideo in your card, it does VC-1 as well. It can work with this or alone as well.

    Also, while it is wacky that bin or binaries are in one spot, and lib or libraries are in another, and anything you install is in a /usr/lib/local, it does keep all related files in one spot. Keeping all your libraries registered as packages also makes it easy to repair.

    Also, one click installs are possible on openSuSE as well, though it does involve a small gui process and adding a repository as well. But doesn't any program require this?

    Also, I believe your problem with SMB shares is something I run into as well, but only on GNOME. On KDE, browsing shares is quite normal. Since I never bother mounting the share, I can't directly access it without KDE caching the file locally.

    Isn't /home/$Your Name$ intuitive as to where your stuff would be? That is very nice, as I can keep my stuff separate from the OS, thus I can reformat the OS partition without having to touch my data. Imagine reinstalling Windows and finding all your apps working exactly as before with no work. Can OSX do that (not rhetorical)?

  • Ryan Smith - Wednesday, August 26, 2009 - link

    VDPAU is something we'll specifically be covering in the Part 2; in fact it's what I'm working on at this moment.
  • GeorgeH - Wednesday, August 26, 2009 - link

    I'm sure the comment section will quickly be swamped with quibbles, so I just wanted to say that I found this article to be very informative, accurate (WRT my own Ubuntu experiences), and thorough. Kudos - now it's time to ask for a raise. :)

Log in

Don't have an account? Sign up now