Comment 306 for bug 204996

Revision history for this message
Sergio Callegari (callegar) wrote :

In response to John:

For what concerns the "fix released" indication... unfortunately it does not indicate that there is a fix released for hardy, as far as I know the part of the 2.6.24 kernel causing the issue is still to be identified. There has been some discussion on whether it was appropriate to place the "fix released" tag on this bug (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/204996/comments/273).

In response to Tom M.

Unfortunately, this is one more indication that going with 2.6.24 for hardy has been a very unfortunate choice: it is not the kernel of fedora, it is not the kernel of opensuse, it is not the kernel of debian, and it has a userbase that is probably limited to hardy only. Furthermore it is not anymore upstream maintained. Patchsets for 2.6.26 and 2.6.25 come out regularly (2.6.25 is at .16 delivered on August 20th), while 2.6.24 stopped at .7 shipped on May 7th.

There has been in the past a strong request to make a version of the intrepid kernel installable on hardy. As a matter of fact it is, but to the best of my knowledge the headers (necessary for compilation against the kernel) are not.

Sergio