linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Frank <mflt1@micrologica.com.hk>
To: Pavel Machek <pavel@suse.cz>,
	Nigel Cunningham <ncunningham@clear.net.nz>
Cc: swsusp-devel <swsusp-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] Re: Thoughts wanted on merging Software Suspend enhancements
Date: Mon, 14 Jul 2003 02:17:29 +0800	[thread overview]
Message-ID: <200307140207.47711.mflt1@micrologica.com.hk> (raw)
In-Reply-To: <20030712153719.GA206@elf.ucw.cz>

On Saturday 12 July 2003 23:37, Pavel Machek wrote:
> > > > - 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)!

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 solid

My 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/


  parent reply	other threads:[~2003-07-13 18:10 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11 22:45 Thoughts wanted on merging Software Suspend enhancements Nigel Cunningham
2003-07-12 14:00 ` Pavel Machek
2003-07-12 14:55   ` Nigel Cunningham
2003-07-12 15:37     ` Pavel Machek
2003-07-12 19:38       ` Nigel Cunningham
2003-07-12 20:15         ` Pavel Machek
2003-07-12 20:22           ` [Swsusp-devel] " Nigel Cunningham
2003-07-12 22:52             ` Pavel Machek
2003-07-13  2:17               ` Jan Rychter
2003-07-12 20:20       ` Nigel Cunningham
2003-07-12 22:56         ` Pavel Machek
2003-07-13 13:27         ` Jamie Lokier
2003-07-13 19:23           ` Pavel Machek
2003-07-13 19:29             ` Jamie Lokier
2003-07-13 18:17       ` Michael Frank [this message]
2003-07-13 19:29         ` [Swsusp-devel] " Pavel Machek
2003-07-12 22:34   ` Dmitry Torokhov
2003-07-12 22:51     ` Pavel Machek
2003-07-13 13:35       ` Jamie Lokier
2003-07-13 19:31         ` Pavel Machek
2003-07-13 21:01           ` [Swsusp-devel] " Nigel Cunningham
2003-07-13 21:09             ` Pavel Machek
2003-07-13 21:21               ` Jan Rychter
2003-07-14  1:54               ` Nigel Cunningham
2003-07-14  3:41                 ` Michael Frank
2003-07-14 13:11                 ` Pavel Machek
2003-07-14 17:30                   ` Jan Rychter
2003-07-14 18:44                     ` Nigel Cunningham
2003-07-14 20:12                 ` Vojtech Pavlik
2003-07-14 20:18                   ` Pavel Machek
2003-07-14 20:30                     ` Nigel Cunningham
2003-07-14 20:43                       ` Pavel Machek
2003-07-14 21:20                         ` Nigel Cunningham
2003-07-14 20:41                     ` Vojtech Pavlik
     [not found]                       ` <20030714230219.GB11283@elf.ucw.cz>
2003-07-15  6:36                         ` Vojtech Pavlik
2003-07-15 10:08                           ` Pavel Machek
2003-07-15 11:11                             ` Markus Gaugusch
2003-07-15 11:31                               ` Pavel Machek
     [not found]             ` <Pine.LNX.4.53.0307132305500.1090@phoenix.kerstin.at>
2003-07-14  1:15               ` Jamie Lokier
2003-07-14  1:26                 ` Lyle Seaman
2003-07-14  1:43                   ` Jamie Lokier
2003-07-14  1:55                     ` Lyle Seaman
2003-07-14  1:57                       ` Nigel Cunningham
2003-07-14  2:17                       ` Lyle Seaman
2003-07-14 20:10           ` Vojtech Pavlik
2003-07-14 20:21             ` Nigel Cunningham
2003-07-14 20:29               ` Pavel Machek
2003-07-14 20:32                 ` Nigel Cunningham
2003-07-14 20:38                   ` Pavel Machek
2003-07-15 16:23         ` Kent Borg
2003-07-15 16:27           ` Pavel Machek
2003-07-15 17:27           ` Jamie Lokier
2003-07-15 19:05             ` Nigel Cunningham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200307140207.47711.mflt1@micrologica.com.hk \
    --to=mflt1@micrologica.com.hk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@clear.net.nz \
    --cc=pavel@suse.cz \
    --cc=swsusp-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).