From: Markus Gaugusch <markus@gaugusch.at>
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 13:11:09 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.53.0307151305270.30306@dynast.gaugusch.at> (raw)
In-Reply-To: <20030715100842.GB3279@zaurus.ucw.cz>
On Jul 15, Pavel Machek <pavel@suse.cz> wrote:
> ... and so I believe right thing is to make magic sysrq combination for
> aborting suspend...
Pavel,
SWSusp is mainly useful for desktop users. Although there may be cases
where it is enabled on production machines, it should be aimed at desktop
users as much as possible. The features to toggle reboot and abort suspend
are really, really cool. And combining them with sysrq would just make
them very very ugly. Someone mentioned the Gnome2 disaster, and I can only
second that. Configurability IS important. And it should be easy as well
(/proc is easy enough, good people or distributors can write a script and
provide it to end users, etc.).
To make the abort of swsusp configurable is the best compromise you can
have, IMHO. I don't know why you are so stubborn and don't try to see the
'normal' people (I'm not one of those, but I'm trying to understand!!).
Markus
--
__________________ /"\
Markus Gaugusch \ / ASCII Ribbon Campaign
markus@gaugusch.at X Against HTML Mail
/ \
next prev parent reply other threads:[~2003-07-15 10:57 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
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 [this message]
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=Pine.LNX.4.53.0307151305270.30306@dynast.gaugusch.at \
--to=markus@gaugusch.at \
--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;
as well as URLs for NNTP newsgroup(s).