Xref: utzoo comp.sys.att:11978 comp.periphs.scsi:2092
Path: utzoo!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!att!cbnews!mvadh
From: mvadh@cbnews.att.com (andrew.d.hay)
Newsgroups: comp.sys.att,comp.periphs.scsi,u3b.conf
Subject: Re: SCSI disk on a 3B2
Keywords: 3B2, SCSI Disk, System V
Message-ID: <1991Mar12.124623.29326@cbnews.att.com>
Date: 12 Mar 91 12:46:23 GMT
References: <1991Mar11.210006.15458@pslu1.psl.wisc.edu>
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 24

In article <1991Mar11.210006.15458@pslu1.psl.wisc.edu> dhoyman@fammed.wisc.edu writes:
"We would like to accquire a 3rd party SCSI disk, such as a Fuji, for our 3B2. 
"In order to use this, the System V device drivers must recognize this "foreign"
"disk.  Without buying the driver from AT&T, how can we do this configuration
"ourselves?
"
"Of course, this would not be a problem if AT&T System V would just go out and
""see" who's on the bus, like a Sun does.  But, no-o-o, the kernel must know
"about each disk drive.

you can't get away without the scsi disk driver; if you're not already
running scsi disks, you'll have to get the 'scsi disk driver
utilities' disk.  you'll also have to do an /etc/scsi/edittbl and edit
/usr/lib/scsi/tc.index with the particulars for your drive.

i know exactly how it's done because i've just added 2
seagate/imprimis st2502n hh drives internally (in place of 1 fh esdi)
but i'm not sure how much detail i can legally go into...

-- 
Andrew Hay		+------------------------------------------------------+
Ragged Individualist	| 			JAAAAAAANE!		       |
AT&T-BL Ward Hill MA	|	    HOW DO YOU STOP THIS CRAZY THING?	       |
a.d.hay@att.com		+------------------------------------------------------+