From: Stefan Seyfried <seife@suse.de>
To: Peter Jones <pjones@redhat.com>
Cc: suspend-devel@lists.sourceforge.net, linux-pm@osdl.org,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [linux-pm] Dangers of touching disk between suspend and resume
Date: Thu, 30 Nov 2006 21:13:11 +0100 [thread overview]
Message-ID: <20061130201311.GK2227@suse.de> (raw)
In-Reply-To: <1164916843.6031.9.camel@localhost.localdomain>
On Thu, Nov 30, 2006 at 03:00:43PM -0500, Peter Jones wrote:
> On Tue, 2006-11-28 at 17:37 +0100, Stefan Seyfried wrote:
>
> > So it is a good idea to tell the engineer to do "mkswap" on the swap
> > partition before putting the disk into the replacement hardware.
>
> Ugh, no it's not. You really want the UUID on the swap area to remain
> the same.
Well, but the system won't care because it won't resume?
Or am i missing something?
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-11-30 20:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 15:21 Dangers of touching disk between suspend and resume Daniel Drake
2006-11-28 15:43 ` [linux-pm] " Alan Stern
2006-11-28 16:37 ` Stefan Seyfried
2006-11-28 19:43 ` Daniel Drake
2006-11-30 20:00 ` Peter Jones
2006-11-30 20:13 ` Stefan Seyfried [this message]
2006-11-30 22:17 ` Peter Jones
2006-12-01 7:39 ` Stefan Seyfried
2006-12-02 4:41 ` Nigel Cunningham
2006-12-04 8:10 ` Stefan Seyfried
2006-12-05 11:28 ` Nigel Cunningham
2006-12-05 11:44 ` Stefan Seyfried
2006-12-05 11:51 ` Matt Sealey
2006-12-06 0:10 ` Nigel Cunningham
2006-12-09 15:25 ` Matthew Garrett
2006-11-30 20:42 ` Daniel Drake
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=20061130201311.GK2227@suse.de \
--to=seife@suse.de \
--cc=linux-pm@osdl.org \
--cc=pjones@redhat.com \
--cc=stern@rowland.harvard.edu \
--cc=suspend-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