From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Matt Sealey <matt@genesi-usa.com>
Cc: suspend-devel@lists.sourceforge.net, linux-pm@osdl.org,
Stefan Seyfried <seife@suse.de>
Subject: Re: [linux-pm] Dangers of touching disk between suspend and resume
Date: Wed, 06 Dec 2006 11:10:06 +1100 [thread overview]
Message-ID: <1165363806.19284.8.camel@nigel.suspend2.net> (raw)
In-Reply-To: <45755D4D.3090900@genesi-usa.com>
Hi again.
On Tue, 2006-12-05 at 11:51 +0000, Matt Sealey wrote:
> Nigel Cunningham wrote:
> >
> >> 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?
>
> /dev/hda2 may move if they move the disk.. I think the preferred way (since
> it seems fairly hard to 'fix' a disk in the /dev tree under Linux, not so
> easy as - say - FreeBSD or NetBSD) is to mount disks from disk labels these
> days (ext2 and xfs supports it at least) as then you can move the disk
> around. USB, Firewire, external SATA disks will fall under this trap, but
> perhaps not internal IDE.. however you can't have both ways :D
Thanks for the reply.
Is all the converting of uuids to device nodes done in userspace? I
haven't noticed anything in the kernel to handle uuids, but I don't look
at filesystem code much.
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-06 0:10 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
2006-12-05 11:51 ` Matt Sealey
2006-12-06 0:10 ` Nigel Cunningham [this message]
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=1165363806.19284.8.camel@nigel.suspend2.net \
--to=ncunningham@linuxmail.org \
--cc=linux-pm@osdl.org \
--cc=matt@genesi-usa.com \
--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