From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Stefan Seyfried <seife@suse.de>
Cc: suspend-devel@lists.sourceforge.net, linux-pm@osdl.org
Subject: Re: [linux-pm] Dangers of touching disk between suspend and resume
Date: Tue, 05 Dec 2006 22:28:08 +1100 [thread overview]
Message-ID: <1165318090.15384.15.camel@nigel.suspend2.net> (raw)
In-Reply-To: <20061204081049.GA12174@suse.de>
Hi.
On Mon, 2006-12-04 at 09:10 +0100, Stefan Seyfried wrote:
> On Sat, Dec 02, 2006 at 03:41:52PM +1100, Nigel Cunningham wrote:
> > Hi.
> >
> > On Fri, 2006-12-01 at 08:39 +0100, Stefan Seyfried wrote:
> > > So if somebody submits a patch that implements a "reset_signature" program,
> > > i'll include that in the suspend package.
> >
> > I don't know if you care (you might not want to support Suspend2), but
>
> Wrong, if i was to write such a "restore_signature" program, i'd want it
> to support all known ways of screwing up your SWAP partition :-)
>
> > for Suspend2 enabled kernels, you can just do:
> >
> > [ -f /sys/power/suspend2/image_exists ] && echo 0 > /sys/power/suspend2/image_exists
> >
> > You can cat the file to find out if an image exists, if you prefer (eg
> > from an initrd/ramfs). Return values are:
>
> But you need a suspend2-enabled kernel.
Everyone should have one of those! :)
> For rescue purposes ("engineer on-site to repair the hardware, diagnosing with
> a rescue CD first" scenario), a standalone binary that resets the signature is
> probably better.
Yeah, that makes sense.
> But this engineer should also know if he depends on the UUID of the swap
> partition to find it. If he does not, he can simply do a "mkswap" to reset
> the signature.
Since you mentioned it, what's they point to using these ugly, looong
uuids? /dev/hda2 is so much simpler and easier to read for mere humans.
I guess it might be useful for USB and so on with the hotplug messiness,
but when I look in /etc/fstab after some upgrade and stuff that's
irrelevant to hotplugging is changed into uuids,... why?
Regards,
Nigel
-------------------------------------------------------------------------
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-12-05 11:28 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
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 [this message]
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=1165318090.15384.15.camel@nigel.suspend2.net \
--to=ncunningham@linuxmail.org \
--cc=linux-pm@osdl.org \
--cc=seife@suse.de \
--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