Re: Patrick's Test9 suspend code.

[Pavel Machek <pavel@suse.cz>]

Hi!

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

/etc/mtab would be better choice, but swap does not appear there.

> > Having sto stop userspace processes and bring hardware back to some
> > sane state would complicate swsusp (and its testing!) a lot. Maybe in
> > 2.8 when it works perfectly in other cases....
> 
> If there's only one "init" style task running from initramfs, which simply 
> looks at the partitions and gets the info it needs from disk labels or 
> something without actually mounting a filesystem (or mounts it read only, no 
> journal playback, and then unmounts it again afterwards...)  And then the 
> system call/whatever it does is sematically "exit and resume from
> swap"...

Well, I'd hate to write docs for that system call.

"It is exit and resume from specified swap, you must not write any
disk before you call it, must not access (list) devices, must not
access any network."

> > ....but swsusp with modular kernels... I'm not sure if it can even
> > work. .. yes it can but you really should get it working monolithic, first.
> 
> Okay.  Tell me how to get hotplug devices (cardbus, usb) working 
> monolithically, and I'm all for it.

Well, just compile all the drivers you need in, and it just
works.... I'm using both cardbus and usb and no, I'm not using
modules.

							Pavel

-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]