From: Greg KH <greg@kroah.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 15:56:31 +0000 [thread overview]
Message-ID: <20080702155631.GA2372@kroah.com> (raw)
In-Reply-To: <20080702102820.GB16076@piper.oerlikon.madduck.net>
On Wed, Jul 02, 2008 at 05:49:32PM +0200, martin f krafft wrote:
> also sprach Kay Sievers <kay.sievers@vrfy.org> [2008.07.02.1619 +0200]:
> > What kind of id's do you have in mind, which would be the same across
> > buses?
>
> I don't. I am trying to understand why the bus type is an integral
> part of the /dev/disk/by-id/* links.
Because UUIDs are not guaranteed to be unique, except by bus type. So
if you place them all in the same namespace, you need to add the bus
type to ensure there are no collisions.
thanks,
greg k-h
next prev parent reply other threads:[~2008-07-02 15:56 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 [this message]
2008-07-02 16:06 ` Kay Sievers
2008-07-02 16:17 ` Karl O. Pinc
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=20080702155631.GA2372@kroah.com \
--to=greg@kroah.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).