Comment 8 for bug 29858

Well, this class (half-baked initrd) of bug manifests in two ways. The first way is that when doing an upgrade of a system to a new kernel *and* new udev, depending on the order the packages were unpacked, you may have end up with a new kernel but an old udev in the initramfs. The above change fixed that, so dapper kernels should always work now after a breezy->dapper upgrade.

The second way this fails, though, is that all the packages calling "update-initramfs -u" during upgrade will upgrade the OLD kernel's initrd if the new kernel hasn't been installed yet, so the old kernel can become unbootable (thanks to udev not being backward-compatible). Other than backing out all the update-initramfs magic, or getting dpkg hooks, I'm not sure how best to solve this case.

We can probably get the upgrade tool to try to intelligently order upgrades to work around this, but that won't solve the classic "apt-get dist-upgrade" case.