From: Nigel Cunningham <ncunningham@clear.net.nz>
To: Lyle Seaman <lws@o-o.yi.org>
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 13:57:42 +1200 [thread overview]
Message-ID: <1058147861.2400.13.camel@laptop-linux> (raw)
In-Reply-To: <20030714015531.7F1CF14829@o-o.yi.org>
Of course there's also the possibility that suspending might abort due
to, say, being unable to freeze all the processes or having no swap
available.
In a situation like that, I wouldn't walk away until I saw it power
down. Besides, we're only talking about waiting 10 or 20 seconds in most
cases (depending on the system's configuration). If you care that much
about the security of your system, you'll be willing to wait.
Regards,
Nigel
On Mon, 2003-07-14 at 13:55, Lyle Seaman wrote:
> > Haven't you ever pressed the "off" or "lock" button on a computer in a
> > lab and walked away?
>
> Yes, I have, but that's not what I was driving at. The question is, what do
> you think is the difference between :
>
> (a) pressing "suspend" and walking away, while being assured that suspend will
> complete and leave the system ... suspended, until someone triggers a "resume"
>
> and
>
> (b) pressing "suspend" and walking away, while allowing the possibility that
> someone might interrupt the suspend operation.
>
> ??
>
> Personally, I don't see any difference.
>
>
>
> -
> 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/
--
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 1:45 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
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 [this message]
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=1058147861.2400.13.camel@laptop-linux \
--to=ncunningham@clear.net.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=lws@o-o.yi.org \
--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