Hah, my /boot partition is not mounted automatically, so I generally end up having to "dpkg --configure -a" after I mount it when there are failed kernel updates.
I don't think this is the cause of the problem though. The second box has /boot always mounted and still had the same problem. Logs attached. BTW, I had filed a bug about this with the update-manager but the bug report has vanished. I stand by my belief that the update manager (since it is running as root) should be clever enough to mount /boot if needed. Just because this is not the way the "default" install sets up /boot, does not mean that good sysadmins won't end up doing just that. I am quite unhappy to see that this bug report I made seems to have completely vanished, without addressing my comments. Saying "we're not going to deal with this yet" is one thing, ignoring/dismissing valid arguments and hiding the discussion is another. ** Attachment added: "dist-upgrade on the box with /boot always mounted" http://launchpadlibrarian.net/34406555/dist-upgrade-netbook.tar.bz2 -- karmic upgrade screwed mtab on reboot https://bugs.launchpad.net/bugs/456493 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
