From: Nigel Cunningham <ncunningham@clear.net.nz>
To: Pavel Machek <pavel@suse.cz>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Jamie Lokier <jamie@shareable.org>,
Dmitry Torokhov <dtor_core@ameritech.net>,
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: Tue, 15 Jul 2003 08:30:08 +1200 [thread overview]
Message-ID: <1058214607.3987.14.camel@laptop-linux> (raw)
In-Reply-To: <20030714201804.GF902@elf.ucw.cz>
Hi.
I'm going to stand firm on this one, Pavel.
I think being able to cancel a suspend is a really useful feature, and
I'll be surprised if we don't see Microsoft including it in their next
version of Windows (perhaps I should take a patent out! :>)
That's not to say that I haven't listened to you, however. That's why I
tightened up the requirements for using it yesterday. As to the extra
proc entry, it's not a biggie: 2.4 swsusp now has it's own proc handling
code which is easily extensible. I did this to make it easier to
understand.
This...
[nigel@laptop-linux nigel]$ ls -l /proc/swsusp/
total 0
--w------- 1 root root 0 Jul 15 08:28 activate
-rw------- 1 root root 0 Jul 15 08:28 async_io_limit
-rw------- 1 root root 0 Jul 15 08:28 beeping
-rw------- 1 root root 0 Jul 15 08:28 checkpage
-rw------- 1 root root 0 Jul 15 08:28 debug_sections
-rw------- 1 root root 0 Jul 15 08:28 default_console_level
-rw------- 1 root root 0 Jul 15 08:28 enable_escape
-rw------- 1 root root 0 Jul 15 08:28 image_size_limit
-r-------- 1 root root 0 Jul 15 08:28 interface_version
-r-------- 1 root root 0 Jul 15 08:28 last_result
-rw------- 1 root root 0 Jul 15 08:28 log_everything
-rw------- 1 root root 0 Jul 15 08:28 no_async_reads
-rw------- 1 root root 0 Jul 15 08:28 no_async_writes
-rw------- 1 root root 0 Jul 15 08:28 no_output
-rw------- 1 root root 0 Jul 15 08:28 nopageset2
-rw------- 1 root root 0 Jul 15 08:28 pause_between_steps
-rw------- 1 root root 0 Jul 15 08:28 progressbar_granularity_limit
-rw------- 1 root root 0 Jul 15 08:28 reboot
-rw------- 1 root root 0 Jul 15 08:28 slow
-r-------- 1 root root 0 Jul 15 08:28 version
[nigel@laptop-linux nigel]$
is easier to understand and configure. The /proc/sys/kernel/swsusp
interface is still there to make it easy to save & restore them all at
once.
Regards,
Nigel
On Tue, 2003-07-15 at 08:18, Pavel Machek wrote:
> Hi!
>
> > > Having listened to the arguments, I'll make pressing Escape to cancel
> > > the suspend a feature which defaults to being disabled and can be
> > > enabled via a proc entry in 2.4. I won't add code to poll for ACPI (or
> > > APM) events :>
> >
> > I'd suggest making it a mappable function in the keymap, like reboot is
> > for example. Both for initiating and stopping the suspend. How about
> > that?
>
> Any user can load his own keymap, I believe... And I do not like
> having special /proc options for esc key...
> Pavel
--
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand
You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
-- Romans 5:6, NIV.
next prev parent reply other threads:[~2003-07-14 20:23 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 ` [Swsusp-devel] " Michael Frank
2003-07-13 19:29 ` 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 [this message]
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=1058214607.3987.14.camel@laptop-linux \
--to=ncunningham@clear.net.nz \
--cc=dtor_core@ameritech.net \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=swsusp-devel@lists.sourceforge.net \
--cc=vojtech@suse.cz \
/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