linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Douglas Gilbert <dougg@torque.net>, 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: Mon, 27 Mar 2006 10:25:30 -0700	[thread overview]
Message-ID: <20060327172530.GH3486@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603270854570.15714@g5.osdl.org>

On Mon, Mar 27, 2006 at 09:15:35AM -0800, Linus Torvalds wrote:
> On Mon, 27 Mar 2006, Douglas Gilbert wrote:
> >
> > There are two things that really count:
> >   1) the identifier (preferably a world wide unique name)
> >      of the logical unit that is being addressed
> >   2) a topological description of how that logical unit
> >      is connected
> 
> And "SCSI ID" doesn't describe either.
> 
> > Linux's <hctl> may be a ham fisted way of describing
> > a path through a topology, but it easily beats /dev/sdabc
> > and /dev/sg4711 .
> 
> Sure, you can easily beat it by selecting what you compare it against.
> 
> But face it, /dev/sdabc or /dev/sg4711 simply isn't what you should 
> compare against. What you should compare against is
> 
> 	/dev/cdrom
> 	/sys/bus/ide/devices/0.0/block:hda/dev
> 	/dev/uuid/3d9e6e8dfaa3d116
> 	..
> 
> and a million OTHER ways to specify which device you're interested in.
> 
> The fact is, they can potentially all do the SCSI command set. And a "SCSI 
> ID" makes absolutely zero sense for them (those three devices may be the 
> same device, they may not be, they might be on another machine, who 
> knows..)

If this ioctl is generally supported, then you'll be able to find out if
they're all the same ;-)

  reply	other threads:[~2006-03-27 17:25 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 [this message]
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
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=20060327172530.GH3486@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=7eggert@gmx.de \
    --cc=dougg@torque.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --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).