> > > > > - user can abort at any time during suspend (oh, I forgot, I wanted
> > > > > to...) by just pressing Escape
> > > >
> > > > That seems like missfeature. We don't want joe random user that is at
> > > > the console to prevent suspend by just pressing Escape. Maybe magic
> > > > key to do that would be acceptable...
>
> Dumb question applicable to 9x% of computers: how do you secure the suspend
> switch and OFF switch, not to mention the power plug or the battery?
>
> As to security many portables have a bios password and no other passwords
> thereafter for the user account. The abort feature events could be enabled
> via swsusp proc entry mainly for (desktop) security. Also, then you ought
> to think about securing suspend events (don't swsusp the webserver
> please)!
Only root can write to /proc/acpi/sleep, so there's no problem.
And having config variable just for escape during suspend is ugly.
> In practice, when suspending, in many cases one would like to abort. Suspend
> should be abortable by ESC and post 1.0: the lid switch and/or suspend switch.
> If you think about it it makes sense to abort suspend instead of having
> to wait 15-40 seconds and reenter the bios password and wait another 10-30
> seconds. (assuming 2.4 speeds)
>
> The way I would use S3/S4 is reboot only for a new kernel, and really use the
> machine portably much more. S3 would be used for short suspends and S4 for
> longer suspends.
>
> In short, this is an _important_ feature _as_ much as S3 and S4.
If you say that aborting with Esc is as important as having swsusp in
the first place... that's not true.
Pavel
-- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] - 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/