>The resume procedure is smarter and can resume a suspended image of a >similar kernel so unless you dist-upgrade or something like that you >should still be able to resume.
I just updated from 2.6.32-26 to 2.6.32-27 and run (once again) into this issue. How did I skip the smart part? Sebastian -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
