From: martin f krafft <madduck@debian.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#484512: not all volume types export UUIDs (was:
Date: Tue, 08 Jul 2008 12:56:59 +0000 [thread overview]
Message-ID: <20080708125659.GA4196@lapse.rw.madduck.net> (raw)
In-Reply-To: <20080702110347.GS7212@baikonur.stro.at>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
also sprach Kay Sievers <kay.sievers@vrfy.org> [2008.07.03.1102 +0200]:
> So, what id's/symlinks is the same disk showing for ATA and USB in your
> case?
I failed to reproduce this for lack of time and am now on the road
again without the ability to swap my laptop's drive.
> 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.
All this makes sense, and it's starting to dawn on me that in fact,
the bus type is needed. Thanks for your patience and sorry to be so
stubborn^W purist about it.
Bug closed.
--
.''`. martin f. krafft <madduck@debian.org>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-07-08 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 11:03 Bug#484512: not all volume types export UUIDs (was: /dev/disk/by-id symlinks should not include maximilian attems
2008-07-02 12:10 ` Bug#484512: not all volume types export UUIDs (was: martin f krafft
2008-07-08 12:56 ` martin f krafft [this message]
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=20080708125659.GA4196@lapse.rw.madduck.net \
--to=madduck@debian.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).