Why such frequent kernel updates?

[daihard]

I installed Kubuntu 8.04 in mid May. I've had three kernel updates since then. That's three in a month. I'd call that very frequent updates. Is there any benefit to such frequent kernel updates?

My understanding is that Hardy Heron (8.04) is supposed to be a long-term supported (LTS) version. That being the case, will such frequent kernel updates be helpful? Kernel updates usually mean having to recompile kernel modules that depend upon a particular kernel version. It is also my experience that a brand new kernel often causes driver compatibility problems. When I was using Fedora, I often upgraded to a new kernel that broke something and ended up rolling back to the older one. I'm hoping I don't have to go through the same trouble with Kubuntu.

Please educate this poor soul...

Dai

[nowshining]

Re: Why such frequent kernel updates?

well a lot things depend on the kernel - such as iptables, etc.. ubuntu patches the kernel to death with their own, etc.. or u can pick a kernel from kernel.org and compile one urself and go by them. Plus fixing the kernel fixes many errors, bugs, etc.. reported on the launchpad website, etc..

[Rog131]

Re: Why such frequent kernel updates?

Updates:

Updates after K/X/Ubuntu final release date > Stable Release Updates:

Once an Ubuntu release has been completed and published, updates for it are only released under certain circumstances, and must follow a special procedure.

=> that is, there are severe bugs/security risks...


Or as Ubuntu backports says:

Ubuntu releases a new version of its OS every 6 months. After a release, the version of all packages stays constant for the entire 6 months. For example, if Ubuntu ships with OpenOffice.org 2.0.x, it will remain at OpenOffice.org 2.0.x for the entire 6-month release cycle, even if a later version gets released during this time. The Ubuntu team may apply important security fixes to 2.0.x, but any new features or non-security bugfixes will not be made available.

BUT as Ubuntu backports tells:

This is where Ubuntu Backports comes in. The Backports team believes that the best update policy is a mix of Ubuntu's security-only policy AND providing new versions of some programs. Candidates for version updates are primarily desktop applications, such as your web browser, word processor, IRC client, or IM client. These programs can be updated without replacing a large part of the operating system that would affect stability of the whole system.

Backports is an official Ubuntu repository and maintained by knowledgeable Ubuntu developers who are often present on IRC and other communications media. But note that software in backports will not receive review or updates from the Ubuntu security team itself. ....

How to request new packages

When you need a package backported which is not currently available, create a new bug report in the Backports Product of Launchpad...

What is in the pipe > Pending Ubuntu stable release updates

Pending Ubuntu stable release updates

Generated: 06/17/08 07:10:10 UTC by sru-report

A stable release update is currently in progress for the following packages, i. e. they have a newer version in -proposed than in -updates.

Bugs in green are verified by QA, bugs in red failed verification.

Changelogs

On your own computer:
/usr/share/doc/<application>

with the linux-image-2.6.24-19-generic
=>
/usr/share/doc/linux-image-2.6.24-19-generic

Or in the Ubuntu Packages:

You have searched for packages that names contain linux-image in suite(s) hardy-updates, all sections, and all architectures. Found 1 matching packages....

linux-image (2.6.24.19.21) Ubuntu Changelog tells:

inux-meta (2.6.24.19.21) hardy-proposed; urgency=low

* ABI bump to -19

-- Tim Gardner <tim.gardner@canonical.com> Wed, 04 Jun 2008 10:36:32 -0600

linux-meta (2.6.24.18.20) hardy-security; urgency=low

* ABI bump to -18

-- Tim Gardner <tim.gardner@canonical.com> Fri, 30 May 2008 11:22:12 -0600

linux-meta (2.6.24.17.19) hardy-proposed; urgency=low

[Stefan Bader]

* Remove linux-restricted-modules-amd64-server meta package.
* Add linux-restricted-modules-server meta package.
* Change descriptions for openvz and xen in the source files.

[Tim Gardner]

* Bump ABI to -17

-- Tim Gardner <tim.gardner@canonical.com> Fri, 18 Apr 2008 14:59:42 +0000

linux-meta (2.6.24.16.18) hardy; urgency=low

* Bump ABI to -16

[Daniel Hahler]

* Fix references to "rt" in "xen" descriptions.

-- Tim Gardner <tim.gardner@canonical.com> Tue, 08 Apr 2008 12:27:04 -0600

linux-meta (2.6.24.15.17) hardy; urgency=low

* Bump ABI to -15
* Extract ABI from debian/changelog.

-- Tim Gardner <tim.gardner@canonical.com> Thu, 03 Apr 2008 14:43:41 -0600

linux-meta (2.6.24.14.16) hardy; urgency=low

* Forgot to change the ABI in debian/rules.

-- Tim Gardner <tim.gardner@canonical.com> Wed, 02 Apr 2008 09:50:55 -0600

linux-meta (2.6.24.14.15) hardy; urgency=low

* Bump ABI to -14
* Added openvz to i386/amd64 meta dependencies.

-- Tim Gardner <tim.gardner@canonical.com> Wed, 02 Apr 2008 09:28:58 -0600

[daihard]

Re: Why such frequent kernel updates?

Thanks for the info, guys. From the kernel changelogs Rog131 quoted, it does not look like too many changes have gone into the kernel between the original and the latest, let alone any security-related fixes. Were those frequent updates warranted?

[kjjjjshab]

Re: Why such frequent kernel updates?

...Were those frequent updates warranted?

I don't know about that, but I sure hope 2.6.25 can fix some of my wireless issues, with its inclusion of ath5k...

[Rog131]

Re: Why such frequent kernel updates?

And those ABI bumps: what's an abi bump