On Saturday 16 September 2006 00:23, Nigel Cunningham wrote:
> > I would even prefer if suspend2 was added to this list and not run via a
> > separate hook (EVENT_GLOBAL_SUSPEND2DISK_OTHER) because it needs to have
> > the hibernate scripts package installed, which basically duplicate all
> > the functionality of the powersaved scripts (unloading modules,
> > unmounting partitions, stopping services etc) and needs to be configured
> > separately.
> > So basically simply call the equivalent of
> > "echo disk > /sys/power/state" for suspend2 in do_acpi_sleep.
> > But then again, I don't know if it's that easy for suspend2 or if you
> > need more configuration to get it running.
>
> The next stable release of Suspend2 will have support for being a
> drop-in replacement for swsusp. As part of preparing for that, I've made
> it so that the most common configuration (lzf compression, no
> encryption) works 'out of the box', and still works if LZF wasn't
> compiled in. As a result, it will be that easy. This might also make
> things easier for Stefan - the echo disk > /sys/power/state will start
> Suspend2 as well, if the user has configured it that way. The old method
> of activating suspend2 (echo > /sys/power/suspend2/do_suspend) will
> still work, regardless of whether replacing swsusp is enabled or not.

Note that powersave's suspend2 support probably needs /proc/suspend2, so that 
is "the old method". That one certainly does not work anymore, 
since /proc/suspend2 has gone recently. I don't know it it's already updated 
to use /sys, someone? For backwards compatibility, it makes sense to check 
for either /proc/suspend2 or /sys/power/suspend2.

> > Ideally powersaved would then (if SUSPEND2DISK_METHOD is not set), first
> > try uswsusp, then fallback to suspend2 and finally to swsusp. We could
> > argue if it would be better to try suspend2 before uswsusp.
>
> We could. Wouldn't it be better, though, to let the user choose what
> order they want things to happen in?

I don't think the user should care about that. The setup that is most likely 
to work should be the default, it should be easy, however to change it. In 
the long term, probably having care HAL about that is the way to go.

The current way the userspace and kernelside things are handled it quite 
cumbersone IMO, there are 3 solutions for S4, and roughly one corresponding 
userspace addition *per_distro*. That makes a lot of possible combinations.
-- 
sebas

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
mknod. war.

Attachment: pgpfGAZLql3lQ.pgp
Description: PGP signature

_______________________________________________
powersave-devel mailing list
powersave-devel@forge.novell.com
http://forge.novell.com/mailman/listinfo/powersave-devel

Reply via email to