Hello I also encountered this bug after upgrading the kernel today.
A quick workaround was to * boot using a grml64 CD * mount the /, /usr and /var partions * chroot to the partions * execute "lilo -v" * reboot I now wonder if the system is permanently "fixed" or if it might randomly hang on the next reboots again. And if it's fixable by just running "lilo -v" then why couldn't the lilo postinst script do this (or if it does why didn't that work). bye, -christian- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
