Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!att!cbnewsc!dcon
From: dcon@cbnewsc.att.com (david.r.connet)
Newsgroups: comp.unix.sysv386
Subject: Re: AT&T SysV Rel 4.0 - SCSI Complaints
Message-ID: <1991May13.173321.26626@cbnewsc.att.com>
Date: 13 May 91 17:33:21 GMT
References: <1991May11.180401.28483@virtech.uucp> <767u21w164w@gantz.bowlgreen.oh.us>
Distribution: usa
Organization: AT&T Bell Laboratories
Lines: 24

In article <767u21w164w@gantz.bowlgreen.oh.us> gantzm@gantz.bowlgreen.oh.us (gantzm) writes:
>cpcahil@virtech.uucp (Conor P. Cahill) writes:
>> brando@uicsl.csl.uiuc.edu (Brandon Brown) writes:
>> You can fix this several ways.  
>> 
>> 	1. use a binary editor to replace the AT&T strings on the boot
>> 	   disketttes so that it recognizes your devices.
>> 
>> 	2. Get the system loaded on a supported device and then change the
>> 	   SCSI id tables in /etc/conf/pack.d/{scsi driver directories}.  There
>> 	   are two directories (one for tapes and one for disks).
>> 
>        As the original poster of this wonderful mess, is this modification
>easy?<Don't laugh too hard>  I'm a new system administrator, and sort
>of know what I'm doing, enough to be dangerous I guess.  

Quite easy.  For #2, edit /etc/conf/pack.d/scsi/space.c and then idbuild
and reboot.  Also edit /etc/scsi/tc.index (used for mkfs, and other commands).
What I do is to copy an entry for a similar device (someone tells me what
is similar).  Beware, in the tc.index file, there are trailing blanks.
These are critical.

Dave Connet
dcon@iwtng.att.com