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)!
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.
Regards
Michael
-- Powered by linux-2.5.75-mm1. Compiled with gcc-2.95-3 - mature and rock solidMy current linux related activities: - 2.5 yenta_socket testing - Test development and testing of swsusp for 2.4/2.5 and ACPI S3 of 2.5 kernel - Everyday usage of 2.5 kernel
More info on 2.5 kernel: http://www.codemonkey.org.uk/post-halloween-2.5.txt More info on swsusp: http://sourceforge.net/projects/swsusp/
- 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/