From: Stefan Seyfried <seife@suse.de>
To: Nigel Cunningham <ncunningham@linuxmail.org>
Cc: suspend-devel@lists.sourceforge.net, linux-pm@osdl.org
Subject: Re: [linux-pm] Dangers of touching disk between suspend and resume
Date: Tue, 5 Dec 2006 12:44:56 +0100 [thread overview]
Message-ID: <20061205114456.GA12676@suse.de> (raw)
In-Reply-To: <1165318090.15384.15.camel@nigel.suspend2.net>
On Tue, Dec 05, 2006 at 10:28:08PM +1100, Nigel Cunningham wrote:
> 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.
Try updating a system using, say, the piix driver for the harddisk to the
new libata drivers (ata_piix). /dev/hda2 will (probably) become /dev/sda2,
but it depends on many factors. The UUID or a label will stay the same,
though.
Best regards,
Stefan
--
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-12-05 11:44 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
2006-12-05 11:44 ` Stefan Seyfried [this message]
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=20061205114456.GA12676@suse.de \
--to=seife@suse.de \
--cc=linux-pm@osdl.org \
--cc=ncunningham@linuxmail.org \
--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