Re: Which is simpler? (Was Re: [Suspend2-devel] Re: [ 00/10] [Suspend2] Modules support.)

[Nigel Cunningham <nigel@suspend2.net>]

[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]

Hi.

On Tuesday 07 February 2006 19:23, Pavel Machek wrote:
> Hi!
> 
> > > *Users* would not be at disadvantage, but, surprise, there's one 
thing
> > > more important than users. Thats developers, and I can guarantee you
> > > that merging 14K lines of code just to delete them half a year later
> > > would drive them crazy.
> > 
> > It would more be an ever-changing interface that would drive them 
crazy. So 
> > why don't we come up with an agreed method of starting a suspend and 
> > starting a resume that they can use, without worrying about whether 
> > they're getting swsusp, uswsusp or Suspend2? /sys/power/state seems the 
> > obvious choice for this. An additional /sys entry could perhaps be used 
to 
> > modify which implementation is used when you echo disk 
> /sys/power/state 
> > - something like
> > 
> > # cat /sys/power/disk_method
> > swsusp uswsusp suspend2
> > # echo uswsusp > /sys/power/disk_method
> > # echo > /sys/power/state
> > 
> > Is there a big problem with that, which I've missed?
> 
> Well, for _users_ method seems to be clicking "suspend" in KDE. For
> more experienced users it is powersave -U. And you are already
> distributing script to do suspend... Just hook suspend2 to the same
> gui stuff distributions already use.

The problem is that kpowersave, for example, doesn't provide any way to say 
that you want to start the cycle by doing something other than echo 
> /sys/power/state. They're apparently planning on changing it to support 
suspend2, but should they have to (and why again for uswsusp?).
 
> Besides what you described can't work for uswsusp.

call_usermodehelper

Regards,

Nigel
-- 
See our web page for Howtos, FAQs, the Wiki and mailing list info.
http://www.suspend2.net                IRC: #suspend2 on Freenode

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]