All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Voelkel <Stefan.Voelkel@millenux.com>
To: Kurt Garloff <garloff@suse.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: bus:id:lun to device name
Date: 15 Jul 2003 16:45:56 +0200	[thread overview]
Message-ID: <1058280356.3983.29.camel@lt-sv> (raw)
In-Reply-To: <20030708145007.GQ2601@nbkurt.garloff.de>

[-- Attachment #1: Type: text/plain, Size: 1768 bytes --]

On Tue, 2003-07-08 at 16:50, Kurt Garloff wrote:
> Hi Stefan,
> 
> On Wed, Jul 02, 2003 at 05:24:08PM +0200, Stefan Voelkel wrote:
> > I want to convert a bus:id:lun triple to something like "/dev/sda".
> > 
> > From userspace I can ioctl() /dev/s[d|cd|...]* or parse /proc/scsi/scsi.
> 
> Plain /proc/scsi/scsi does not help you.
> You may want to have a lok at the scsi-many patches that export this
> information via /proc/scsi/scsi though.
> http://www.suse.de/~garloff/linux/scsi-many/

I can not patch the middle layer.

> Host: scsi3 Channel: 00 Id: 10 Lun: 00
>   Vendor: IBM      Model: DDYS-T18350N     Rev: S84D
>   Type:   Direct-Access                    ANSI SCSI revision: 03
>   Attached drivers: sde(b:08:40) sg5(c:15:05)
> 
> > I do not like any of those solutions.
> 
> For non-removable harddisks, the ioctl() just works fine, BTW.
> I see no reason to dislike it.

Theoretically /dev/foobar might be a scsi device, meaning that I
must/should ioctl() all files under /dev/. Thats what I do not like
about ioctl() :).

> Another option is to use scsidev
> http://www.garloff.de/kurt/linux/scsidev/
> where the device nodes are dynamically created and (by default) have 
> names which contain this information.

AFAIR devfs does this too, depending on devfs would be an option.

regards
	Stefan
-- 
--------------------------------------------------------------------
Stefan Völkel                            stefan.voelkel@millenux.com
Millenux GmbH                              mobile: +49.170.79177.17
Lilienthalstraße 2                          phone: +49.711.88770.300
70825 Stuttgart-Korntal                       fax: +49.711.88770.349
     -= linux without limits -=- http://linux.zSeries.org/ =-

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-07-15 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 15:24 bus:id:lun to device name Stefan Voelkel
2003-07-08 14:50 ` Kurt Garloff
2003-07-15 14:45   ` Stefan Voelkel [this message]
2003-07-15 17:03     ` Bryan Henderson
2003-07-16  8:29       ` Stefan Voelkel
2003-07-17 10:29         ` Christoph Hellwig

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=1058280356.3983.29.camel@lt-sv \
    --to=stefan.voelkel@millenux.com \
    --cc=garloff@suse.de \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.