Comment 21 for bug 350491

This still feels like the wrong solution. We have to have the currently running kernel available anyways, so why not just boot that on resume, and keep hibernation working? Configurations that have ubuntu hibernate on a critical battery shortage will suffer data loss right now anyways, even with the prevent-hibernation fix.

If you're going to hibernate, just fix grub's configuration so that it has to boot the correct kernel (or at least provides a warning message if the user tries to boot anything else). Everything just works right, the right kernel always loads, no data loss.

> Problem persists in intrepid. Seems to be the best of all possible options is:
> 1) Whenever you hibernate, save a copy of the grub menu.lst to a backup location
> 2) Change menu.lst to boot the currently running kernel by default, with a label simply reading "Resume from Hibernation".
> 3) If possible, add a warning message to the grub menu that booting any other option will result in a loss of the hibernated state
> 4) On resume from hibernation, restore the backup menu.lst from step 1.