Hmm, I dunno, however it makes sense for me: since the kernel image itself is also only 'vmlinuz' there, I guess it boots the 'current' kernel maintained by symlinks for kernel image and the initrd itself (at that time there was no 2.6.20-14 kernel, only 13, by the way, however I've just checked with -14, and it's the same). Also, /boot/initrd.img and /boot/vmlinuz points to the right files. But to be sure, I've just selected the 'right' entry in grub menu (which does not point the symlinks but the desired kernel image and initrd) and the problem remains. And also, this problem occured on several machines both on AMD64 and i386.
-- double swap space usage https://bugs.launchpad.net/bugs/96715 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
