[2182] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

Re: More than one SCSI controler & SCSI_IOCTL_GET_IDLUN

daemon@ATHENA.MIT.EDU (Leonard N. Zubkoff)
Sat Jul 19 17:54:51 1997

Date: 	Sat, 19 Jul 1997 14:52:17 -0700
From: "Leonard N. Zubkoff" <lnz@dandelion.com>
To: schilling@fokus.gmd.de
CC: eric@andante.jic.com, tn@bv.rz.fh-muenchen.de, linux-scsi@vger.rutgers.edu,
        schilling@fokus.gmd.de
In-reply-to: <199707181058.MAA01020@sherwood.fokus.gmd.de>
	(schilling@fokus.gmd.de)

  Date: 	Fri, 18 Jul 1997 12:58:54 +0200
  From: schilling@fokus.gmd.de (Joerg Schilling)

  Here is the version of the patch, I will include in the cdrecord-1.5a5
  release. I modified the Bus # to be an integer and the directory to
  be 'linux' to allow most users to patch their kernels.

  I have currently no Linux with SCSI at all and would be happy to
  get test results from people who have more SCSI busses.

  I put the new cdrecord alpha out this moment. It os located on:

  ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/alpha


I must be missing something here, but I'd like to know why a user program needs
to know the SCSI bus number at all.  The LUN is necessary because it must go in
the CDB, but I don't see how the SCSI bus number matters to a user program.
The user must specify the /dev/sg<x> SCSI generic device, which makes the
mapping to bus and Target ID automatic.

Please clarify.

		Leonard

home help back first fref pref prev next nref lref last post