From: "Karl O. Pinc" <kop@meme.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: not all volume types export UUIDs (was: /dev/disk/by-id
Date: Wed, 02 Jul 2008 16:17:17 +0000 [thread overview]
Message-ID: <1215015437l.20934l.5l@mofo> (raw)
In-Reply-To: <20080702102820.GB16076@piper.oerlikon.madduck.net>
On 07/02/2008 10:56:31 AM, Greg KH wrote:
> Because UUIDs are not guaranteed to be unique, except by bus type.
That seems a shame, given that they are
named Universally Unique IDentifiers and
are all supposed to reside in a single
namespace. At least that's what I've
thought UUIDs are. Oh well.
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
next prev parent reply other threads:[~2008-07-02 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 10:28 not all volume types export UUIDs (was: /dev/disk/by-id symlinks martin f krafft
2008-07-02 14:19 ` not all volume types export UUIDs (was: /dev/disk/by-id Kay Sievers
2008-07-02 15:49 ` martin f krafft
2008-07-02 15:56 ` Greg KH
2008-07-02 16:06 ` Kay Sievers
2008-07-02 16:17 ` Karl O. Pinc [this message]
2008-07-02 16:28 ` not all volume types export UUIDs (was: /dev/disk/by-id symlinks should not include bus) type Kay Sievers
2008-07-03 5:30 ` not all volume types export UUIDs (was: /dev/disk/by-id martin f krafft
2008-07-03 9:02 ` Kay Sievers
2008-07-03 13:42 ` not all volume types export UUIDs (was: /dev/disk/by-id symlinks should not include bus) type Matthew Dharm
2008-07-03 15:12 ` not all volume types export UUIDs (was: /dev/disk/by-id Kay Sievers
2008-07-03 15:33 ` not all volume types export UUIDs (was: /dev/disk/by-id symlinks should not include bus) type Matthew Dharm
2008-07-03 15:36 ` not all volume types export UUIDs (was: /dev/disk/by-id Kay Sievers
2008-07-05 11:55 ` martin f krafft
2008-07-05 12:32 ` Kay Sievers
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=1215015437l.20934l.5l@mofo \
--to=kop@meme.com \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).