[forwarded from Patrick P. Murphy] Re: [daip] ZMOUN2 (linux)

Patrick P. Murphy pmurphy at nrao.edu
Sat Apr 29 12:33:33 EDT 2000


------- start of forwarded message (RFC 934 encapsulation) -------
Content-Length: 2529
Return-Path: <pmurphy at orangutan.cv.nrao.edu>
Received: (from pmurphy at localhost)
	by orangutan.cv.nrao.edu (8.9.3/NRAO/CV-2.0/PPM-1.0) id MAA19123;
	Sat, 29 Apr 2000 12:28:08 -0400
X-Authentication-Warning: orangutan.cv.nrao.edu: pmurphy set sender to pmurphy at orangutan.cv.nrao.edu using -f
References: <200004282121.RAA09656 at primate.cv.nrao.edu>
X-Mailer: VM 6.75 under Emacs 20.4.1
From: "Patrick P. Murphy" <pmurphy at nrao.edu>
To: Eric Greisen <egreisen at nrao.edu>
Subject: Re: [daip] ZMOUN2 (linux) 
Date: Sat, 29 Apr 2000 12:28:08 -0400 (EDT)
Message-ID: <14603.3480.198684.780102 at orangutan.cv.nrao.edu>

There's got to be a way of reporting this... I do see that on valen,

  valen_pmurphy<1001> cat /proc/scsi/scsi    
  Attached devices: 
  Host: scsi0 Channel: 00 Id: 03 Lun: 00
    Vendor: SEAGATE  Model: ST410800N        Rev: 0016
    Type:   Direct-Access                    ANSI SCSI revision: 02
  Host: scsi0 Channel: 00 Id: 06 Lun: 00
    Vendor: MICROP   Model: 1924-21MZ1077810 Rev: HZ2P
    Type:   Direct-Access                    ANSI SCSI revision: 01 CCS
  Host: scsi1 Channel: 00 Id: 00 Lun: 00
    Vendor: SEAGATE  Model: ST19101W         Rev: 0014
    Type:   Direct-Access                    ANSI SCSI revision: 02
  Host: scsi1 Channel: 00 Id: 01 Lun: 00
    Vendor: SONY     Model: SDT-9000         Rev: 0400
    Type:   Sequential-Access                ANSI SCSI revision: 02

and on vulcan:

  vulcan_pmurphy<884> cat /proc/scsi/scsi    
  Attached devices: 
  Host: scsi0 Channel: 00 Id: 00 Lun: 00
    Vendor: QUANTUM  Model: ATLAS 10K 18WLS  Rev: UCH0
    Type:   Direct-Access                    ANSI SCSI revision: 03
  Host: scsi0 Channel: 00 Id: 01 Lun: 00
    Vendor: QUANTUM  Model: ATLAS 10K 18WLS  Rev: UCH0
    Type:   Direct-Access                    ANSI SCSI revision: 03
  Host: scsi0 Channel: 00 Id: 02 Lun: 00
    Vendor: QUANTUM  Model: ATLAS 10K 18WLS  Rev: UCH0
    Type:   Direct-Access                    ANSI SCSI revision: 03
  Host: scsi0 Channel: 00 Id: 03 Lun: 00
    Vendor: QUANTUM  Model: ATLAS 10K 18WLS  Rev: UCH0
    Type:   Direct-Access                    ANSI SCSI revision: 03
  Host: scsi1 Channel: 00 Id: 02 Lun: 00
    Vendor: SONY     Model: SDT-9000         Rev: 0400
    Type:   Sequential-Access                ANSI SCSI revision: 02
  Host: scsi1 Channel: 00 Id: 05 Lun: 00
    Vendor: NEC      Model: CD-ROM DRIVE:466 Rev: 1.06
    Type:   CD-ROM                           ANSI SCSI revision: 02
  Host: scsi1 Channel: 00 Id: 06 Lun: 00
    Vendor: EXABYTE  Model: EXB-85058SQANXR1 Rev: 0808
    Type:   Sequential-Access                ANSI SCSI revision: 02

so the info is accessible in the kernel.  It's annoying that it's not
readily accessible through an ioctl or something.

We could perhaps use /proc/scsi/... but that leads to the problem of how
to associate /dev/nst1 with a particular SCSI bus and a target on that.

I don't have time right now to delve into this further (grass needs cut)
but I still believe there are possibilities.  Even the possibility of
modifying the driver and contributing it back to the main development
tree... 
				- Pat
------- end -------




More information about the Daip mailing list