From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: not all volume types export UUIDs (was: /dev/disk/by-id
Date: Thu, 03 Jul 2008 15:36:59 +0000 [thread overview]
Message-ID: <1215099419.9721.97.camel@linux.site> (raw)
In-Reply-To: <20080702102820.GB16076@piper.oerlikon.madduck.net>
On Thu, 2008-07-03 at 08:33 -0700, Matthew Dharm wrote:
> On Thu, Jul 03, 2008 at 05:12:57PM +0200, Kay Sievers wrote:
> > On Thu, 2008-07-03 at 06:42 -0700, Matthew Dharm wrote:
> > > On Thu, Jul 03, 2008 at 11:02:46AM +0200, Kay Sievers wrote:
> > > > On Thu, 2008-07-03 at 07:30 +0200, martin f krafft wrote:
> > > > > also sprach Kay Sievers <kay.sievers@vrfy.org> [2008.07.02.1806 +0200]:
> > > > > > All are only unique per namespace/bus, and should better not be
> > > > > > mixed.
> > > > >
> > > > > Well, but that's my point I suppose. Why do we have to treat the
> > > > > same drive differently, whether it's on the ATA bus or the USB bus?
> > > > >
> > > > > My reason for bringing this up was that I was trying to boot off
> > > > > a harddrive via USB and had to change all the links, rather than
> > > > > just watching the system boot off the same disk it has always booted
> > > > > from.
> > > >
> > > > So, what id's/symlinks is the same disk showing for ATA and USB in your
> > > > case?
> > > >
> > > > Only advanced USB bridges read the number from the actual disk, I have a
> > > > bunch of enclosures here, which show all different id's for the same
> > > > disk inserted. Also usb-storage needs to encode the target and lun
> > > > number in the id, for multi-slot devices, so I do not think that will
> > > > work.
> > >
> > > Isn't devlabel the technology that is supposed to be used for this sort of
> > > scenario?
> >
> > No, that is replaced by /dev/disk/by-label/*
>
> Well, yes... I mean, you can *use* the label on the partition in a number
> of ways.
>
> But, my point was that instead of trying to ID a disk by some name which
> may change depending on how it's attached to the system, use the devlabel
> (via /dev/disk/by-label or mount options or whatever), which doesn't change
> regardless of how the disk is attached to the system.
Sure, symlinks based on filesystem metadata are the way to go here.
Usually the fs UUID is used in fstab and such, and works pretty well.
Thanks,
Kay
next prev parent reply other threads:[~2008-07-03 15:36 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
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 ` Kay Sievers [this message]
2008-07-05 11:55 ` not all volume types export UUIDs (was: /dev/disk/by-id 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=1215099419.9721.97.camel@linux.site \
--to=kay.sievers@vrfy.org \
--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).