Ultimate Edition Forum

SomeUbuntuAdminGuy wrote:A final note: at this point in time the -17 kernels are only available in the hardy-proposed repository. This is where bugfix updates to Hardy are pushed first, to recieve testing. As such, this repository is subject to the same sort of problems as an unstable release, but on a lesser scale. Everything should work in there, but it's explicitly for testing, so breakage may occur. In particular, this sort of breakage (where the kernel image is built but an associated package isn't yet built) is going to happen each time a new kernel ABI is pushed (the -17 part of the version string). You can't build the restricted modules without the new kernel, so there's an unavoidable period of time when the repository is in this state.

If you're going to run with the hardy-proposed repository enabled you should be treating it somewhat like running the development release, and be careful on updates. For most people it's better to not have hardy-proposed enabled, unless they want to test a bugfix for a specific bug they are seeing]A final note: at this point in time the -17 kernels are only available in the hardy-proposed repository. This is where bugfix updates to Hardy are pushed first, to receive testing. As such, this repository is subject to the same sort of problems as an unstable release, but on a lesser scale. Everything should work in there, but it's explicitly for testing, so breakage may occur. In particular, this sort of breakage (where the kernel image is built but an associated package isn't yet built) is going to happen each time a new kernel ABI is pushed (the -17 part of the version string). You can't build the restricted modules without the new kernel, so there's an unavoidable period of time when the repository is in this state.

If you're going to run with the hardy-proposed repository enabled you should be treating it somewhat like running the development release, and be careful on updates. For most people it's better to not have hardy-proposed enabled, unless they want to test a bugfix for a specific bug they are seeing.

DaddyX3 wrote:I have to make a post about upgrading your kernel. I don't think everyone is aware that there are repercussions to upgrading your kernel to the 2.6.24-17. In order for you to even get the 2.6.24-17 kernal, you have to open up and enable the backports repository. This repository is basically (with little difference) a beta repo. By doing this you don't know what kinda problems you are going to run into. I understand that Hardy was pushed through and didn't really (IMHO) have the time needed to get all the little stuff worked out in it, this will change soon enough with regular updates. There seems to be a problem with envyng and the new 2.6.24-17 kernel. I hope that all involved with this problem know what they are doing and have already made up their own work around for this issue. I read the posts in the Ubuntu Forums about this envy issue and read a really good post from one of the developers. Thought everyone might want to read this. .....

SomeUbuntuAdminGuy wrote:A final note: at this point in time the -17 kernels are only available in the hardy-proposed repository. This is where bugfix updates to Hardy are pushed first, to recieve testing. As such, this repository is subject to the same sort of problems as an unstable release, but on a lesser scale. Everything should work in there, but it's explicitly for testing, so breakage may occur. In particular, this sort of breakage (where the kernel image is built but an associated package isn't yet built) is going to happen each time a new kernel ABI is pushed (the -17 part of the version string). You can't build the restricted modules without the new kernel, so there's an unavoidable period of time when the repository is in this state.

If you're going to run with the hardy-proposed repository enabled you should be treating it somewhat like running the development release, and be careful on updates. For most people it's better to not have hardy-proposed enabled, unless they want to test a bugfix for a specific bug they are seeing]A final note: at this point in time the -17 kernels are only available in the hardy-proposed repository. This is where bugfix updates to Hardy are pushed first, to receive testing. As such, this repository is subject to the same sort of problems as an unstable release, but on a lesser scale. Everything should work in there, but it's explicitly for testing, so breakage may occur. In particular, this sort of breakage (where the kernel image is built but an associated package isn't yet built) is going to happen each time a new kernel ABI is pushed (the -17 part of the version string). You can't build the restricted modules without the new kernel, so there's an unavoidable period of time when the repository is in this state.

If you're going to run with the hardy-proposed repository enabled you should be treating it somewhat like running the development release, and be careful on updates. For most people it's better to not have hardy-proposed enabled, unless they want to test a bugfix for a specific bug they are seeing.

I'm going to lock this topic so it doesn't get all cluttered and people miss the point all together. There are benefits to running the 2.6.24-17 kernel, but they also come with a price .... its not complete yet and therefore you might be one of the poor saps that turn in to a involuntary beta testers
This was just a warning and could answer a lot of questions before you have a need to ask them. You have been WARNED!