For those who have *some* method of booting into their system... It should be noted that there were a number of issues related to booting as a result of what was done in Gutsy. See bug 133666 for one prominent example. This documents an issue that had a known fix that will not be put into Gutsy simply because this show-stopping bug was found only after the release of Gutsy when people actually started using the distribution. This is actually an upstream thing -- the Linux kernel had the bug in 2.6.22, but it had been fixed in 2.6.23 and beyond.
As I understand the situation, Linux is trying to alter how drives are accessed. For many of us, that means that instead of /dev/hd*, we now have /dev/sd*. UUID's do not change between the two access methods, but there were some kernel bugs that were not identified until after Gutsy. There is no intention to pull these bugs out of Gutsy. Instead, they are asking that people test out the Hardy kernels to make sure that these issues are truly fixed in Hardy. I'm of the understanding that this is done by temporarily altering the /etc/apt/sources.list in order to include the Hardy main and restricted repositories. Once you have retrieved the Hardy kernels, and installed them on your system, you can change /etc/apt/sources.list back to just Gutsy repositories. Unless you actually want to test Hardy, it is advised that you do not do any upgrades while you are using the altered sources.list. At this point, the primary concern is if these issues are not fixed in the Hardy kernels. If there are still issues in the 2.6.24 kernels, please document the bugs appropriately. -- Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable https://bugs.launchpad.net/bugs/152820 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
