Skip to contentSkip to conversation

Patrick's Test9 suspend code.

DISCUSSION Samium Gromoff 2 participants 2 messages Nov 19, 2003 – Nov 20, 2003

lore
Share & tools
lore
#0 lore raw
Quoted 10 lines
Quoted 9 lines
Quoted 6 lines
Quoted 4 lines

:-), 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.

Quoted 7 lines

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

#1 lore raw

Hi!

Quoted 8 lines
Quoted 7 lines

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.

Quoted 8 lines

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".

Yes and we should create separate partition type for root filesystem and have separate mkfs.ext2.root.

NOT!

I see no advantages in mksusp; it only means you need to re-fdisk your machine. Bad idea, and its way too late for 2.6 anyway.

Signature · 2 lines
				Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...