From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-pm@lists.osdl.org
Cc: richard@hughsie.com
Subject: Re: suspend and hibernate nomenclature
Date: Sun, 14 May 2006 23:17:16 +0200 [thread overview]
Message-ID: <200605142317.16823.rjw@sisk.pl> (raw)
In-Reply-To: <20060514153929.GE2438@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
On Sunday 14 May 2006 17:39, Pavel Machek wrote:
> On Ne 14-05-06 16:32:24, Richard Hughes wrote:
> > On Mon, 2006-05-08 at 20:01 +0000, Pavel Machek wrote:
> > > Hi!
> > >
> > > > First, sorry for the random mail to this mailing list.
> > > >
> > > > I'm the developer of gnome-power-manager. The latest mini-project of
> > > > mine is to fix the suspend-hibernate nomenclature used by OSS projects.
> > > >
> > > > This might not effect the lowest layers of the stack (i.e. I want to
> > > > focus on the stuff used by *users*), so this might not be applicable to
> > > > you guys. Please keep me cc'd if you discuss, as I'm not subscribed to
> > > > this list.
> > > >
> > > > Full description of the problem is here:
> > > > http://live.gnome.org/GnomePowerManager/SleepNames and I would encourage
> > > > you guys to add comments to the end of the wiki if required.
> > >
> > > Please do not use word 'thaw'. We already freeze processes during
> > > suspend, and we thaw them during resume.
> >
> > Got any better ideas? It needs to *just* apply to hibernation, not a
> > generic term like wake.
>
> reanimate? As you said, users are unlikely to see this one.
>
> Alternatives:
>
> dehibarnate (unhibernate?), resume-from-disk :-), ressurect,
> resuscitate (particulary useful if s-2-disk is buggy :-), revive, ...
Maybe "wake up"? :-)
Rafael
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-05-14 21:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 18:02 suspend and hibernate nomenclature Richard Hughes
2006-05-08 15:05 ` Jordan Crouse
2006-05-08 16:09 ` Richard Hughes
2006-05-08 20:01 ` Pavel Machek
2006-05-14 15:32 ` Richard Hughes
2006-05-14 15:39 ` Pavel Machek
2006-05-14 21:17 ` Rafael J. Wysocki [this message]
2006-05-08 23:47 ` David Brownell
2006-05-09 7:38 ` Richard Hughes
2006-05-09 15:57 ` David Brownell
2006-05-16 20:40 ` Pavel Machek
2006-05-18 19:56 ` David Brownell
2006-05-18 20:50 ` Pavel Machek
2006-05-19 2:25 ` David Brownell
2006-05-20 17:20 ` Pavel Machek
2006-05-20 19:23 ` Alan Stern
2006-05-20 20:47 ` David Brownell
2006-05-20 20:55 ` Pavel Machek
2006-05-21 15:35 ` Alan Stern
2006-05-20 20:54 ` David Brownell
2006-05-20 22:39 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-05-16 20:47 Scott E. Preece
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=200605142317.16823.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-pm@lists.osdl.org \
--cc=richard@hughsie.com \
/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