Messages in this thread |  | | | Date | Wed, 19 Nov 2003 16:15:25 +0300 | | From | Samium Gromoff <> | | Subject | Re: Patrick's Test9 suspend code. |
| |
> > > > :-), Okay, we could make grub read /etc/fstab... But again user can do > > > > > > > > swapoff and swapon manually etc. > > > > > > During resume? > > > > No, imagine /dev/hda3 being set as swap in /etc/fstab, but user doing > > swapoff /dev/hda3, swapon /dev/usb_zip_drive, then suspend. > > A) Any scheme we come up with there will be a way the user can do something > stupid enough to break it. (Put the swap partition on a ramdisk living on > the video card, or on a device require an initrd to load the driver to > access...) > > B) A heuristic that looks at the mounted block devices for things that smell > like a resume partition would actually be more robust in that case.
Really, what i think here is appropriate is a more fundamental approach.
We should reserve a new partition type in addition to three already existing, namely "linux"==0x83, "linux swap"==0x82 and "linux lvm"==0x8e.
And call it something like "linux suspend". And initialize it, if needed (i presume to write a signature etc), with something like "mksusp".
regards, Samium Gromoff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |