From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Douglas Gilbert <dougg@torque.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@osdl.org>,
Matthew Wilcox <matthew@wil.cx>, Bodo Eggert <7eggert@gmx.de>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Move SG_GET_SCSI_ID from sg to scsi
Date: Tue, 28 Mar 2006 09:37:47 +0200 [thread overview]
Message-ID: <4428E7CB.6030407@s5r6.in-berlin.de> (raw)
In-Reply-To: <44285929.4020806@torque.net>
Douglas Gilbert wrote:
> Alan Cox wrote:
[host/ channel/ target/ LU enumeration...]
>> is still a very visible reality if you work in a data centre or with
>> server kit, or if you have tape arrays or multi-CD towers. The LUN or
>> device number in particular are generally the number emblazoned on each
>> slot in the unit
...
> USB multi-card readers seem to like the concept of LUNs as well.
Sure. The h:c:i:l tuple does not provide the LUN though, only an ersatz.
--
Stefan Richter
-=====-=-==- --== ===--
http://arcgraph.de/sr/
next prev parent reply other threads:[~2006-03-28 7:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 19:28 [PATCH] Move SG_GET_SCSI_ID from sg to scsi Bodo Eggert
2006-03-26 19:51 ` Arjan van de Ven
2006-03-26 20:08 ` Matthew Wilcox
2006-03-26 20:41 ` Arjan van de Ven
2006-03-26 20:05 ` Matthew Wilcox
2006-03-27 10:11 ` Bodo Eggert
2006-03-27 15:20 ` Matthew Wilcox
2006-03-27 15:40 ` James Bottomley
2006-03-26 22:30 ` Linus Torvalds
2006-03-26 23:19 ` Jan Engelhardt
2006-03-27 0:06 ` Linus Torvalds
2006-03-27 11:42 ` Bodo Eggert
2006-03-28 9:43 ` Matthias Andree
2006-03-27 15:03 ` Douglas Gilbert
2006-03-27 17:15 ` Linus Torvalds
2006-03-27 17:25 ` Matthew Wilcox
2006-03-27 17:43 ` Linus Torvalds
2006-03-27 19:54 ` Alan Cox
2006-03-27 21:29 ` Douglas Gilbert
2006-03-28 7:37 ` Stefan Richter [this message]
2006-03-28 14:17 ` Jan Engelhardt
2006-03-26 23:09 ` Stefan Richter
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=4428E7CB.6030407@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=7eggert@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=torvalds@osdl.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).