Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!tut.cis.ohio-state.edu!bgsuvax!gantzm From: gantzm@gantz.bowlgreen.oh.us (gantzm) Newsgroups: comp.unix.sysv386 Subject: Re: AT&T SysV Rel 4.0 - SCSI Complaints Message-ID: <767u21w164w@gantz.bowlgreen.oh.us> Date: 13 May 91 02:52:29 GMT References: <1991May11.180401.28483@virtech.uucp> Organization: Michael L. Gantz - Consultant Lines: 31 cpcahil@virtech.uucp (Conor P. Cahill) writes: > brando@uicsl.csl.uiuc.edu (Brandon Brown) writes: > > >also. It seems that AT&T looks for the SCSI ident string on the drive, and > >that is how it determines whether or not it is a supported device. This also [stuff deleted] > 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). > > -- > Conor P. Cahill (703)430-9247 Virtual Technologies, Inc. As the original poster of this wonderful mess, is this modification easy? I'm a new system administrator, and sort of know what I'm doing, enough to be dangerous I guess. The saga continues.... --- Michael L. Gantz | gantzm@gantz.bowlgreen.oh.us 213 Napoleon Rd. | osu-cis!bgsuvax!gantz!gantzm Bowling Green, Oh 43402 | Mellon! I had only to speak the Elvish word for (419) 353-5029 | friend and the doors opened. - J.R.R. Tolkien