Bug#464595: linux-source-2.6.24: booting takes far longer than 2.6.22

Package: linux-source-2.6.24 Version: 2.6.24-1 Severity: normal File: linux-source-2.6.24 this bug report will be dismissed as both useless and unimportant, but slow boots greatly increase the time it takes for users to fix issues trying to get their kernels to work, so it is important to some of

Bug#464591: linux-source-2.6.24: kill -9 is a nop

Package: linux-source-2.6.24 Version: 2.6.24-1 Severity: normal File: linux-source-2.6.24 this bug report will be dismissed as useless, but it's important to document the existence of the bug. a process, index++, which uiam is part of swish++, consumed 100% of cpu. kill -1 failed. all values o

Bug#435472: linux-source-2.6.22: make booting more pleasant to debug

Package: linux-source-2.6.22 Version: 2.6.22-1 Severity: wishlist File: linux-source-2.6.22 for example, when you supply root= with the wrong device, the kernel can panic. this requires physically traveling to the box and rebooting it, since ctrl-alt-del does not work. is it possible for the ke

Bug#435469: linux-source-2.6.22: udev: common user action causes undecipherable hang

Package: linux-source-2.6.22 Version: 2.6.22-1 Severity: normal File: linux-source-2.6.22 summary: you can't boot from a naive mirror anymore. i have a solution below. a user who copies to a root partition with rsync (at least with --one-file-system) will most likely expect it to boot. instead

Bug#368683: linux-source-2.6.16: menuconfig should say what the raw default is

Package: linux-source-2.6.16 Version: 2.6.16-13 Severity: normal menuconfig provides defaults, and it also sometimes gives hints like "if you're all like 'WTF?' then you can safely say Y here". that's nice, but was that default there because of my old .config? or is it a real default? menuconf