I think this is a bug! Just because suspend won't umount any partition
and when resuming, what would happen if a partition had been used in a
previous session? I think a horrible data loss!
well, there are suspend.d scripts, I think the best way to face with
this problem is to use them. we could write a simple script that enables
only the current kernel in grub!
Il giorno lun, 15/05/2006 alle 05.14 +0000, chipzz ha scritto:
> I consider this a feature, not a bug; this enables me to hibernate, boot windows; do something there, exit windows, resume.
> I think the correct fix is to replace "default 0" with "default saved" (which does have the undesirable side-effect of not automatically booting the latest kernel when you install a new kernel and reboot).
>
I think this is a bug! Just because suspend won't umount any partition
and when resuming, what would happen if a partition had been used in a
previous session? I think a horrible data loss!
well, there are suspend.d scripts, I think the best way to face with
this problem is to use them. we could write a simple script that enables
only the current kernel in grub!
Il giorno lun, 15/05/2006 alle 05.14 +0000, chipzz ha scritto:
> I consider this a feature, not a bug; this enables me to hibernate, boot windows; do something there, exit windows, resume.
> I think the correct fix is to replace "default 0" with "default saved" (which does have the undesirable side-effect of not automatically booting the latest kernel when you install a new kernel and reboot).
>