On Sun, Apr 23, 2006 at 01:25:27PM +0200, Hans Ulrich Niedermann wrote: > A few ideas for fixing the problem: > > a) When "hibernate" is run to suspend the system, check that the > exact version of currently running kernel will be available on > the next boot. If it will not be available, do not suspend. > > b) This could be achieved by a script run on system boots (but not > resumes) which records the exact version of the kernel running, > making a connection to the Debian package behind it. The > hibernate script could then check the currently installed kernel > package against the package on startup.
Though just because the package is still installed does not guarantee that it's bootable. Without parsing lilo and grub config files, it's impossible to tell if it's really bootable. I believe the kernel-patch-suspend2 package modified the install script of a suspend2 patched kernel to touch a file /var/run/suspend2-new-kernel, which hibernate respects. I gather your issue though is with the vanilla suspend. Perhaps something similar could get pushed into the Debian kernel packages themselves? Bernard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
