Subject: Re: Minimum MicroVAX 3100/20 kernel config?
To: None <nbsdbob@weedcon1.cropsci.ncsu.edu>
From: maximum entropy <entropy@tardis.bernstein.com>
List: port-vax
Date: 11/05/1999 11:21:07
>From: NetBSD Bob <nbsdbob@weedcon1.cropsci.ncsu.edu>
>Date: Fri, 5 Nov 1999 10:52:03 -0500 (EST)
>
>Bingo!   For some reason sd2 was labelled as an RX33?  Yikes.....

Glad to be of assistance...

>The controller seems to reside at scsi ID 6, so I am assuming I can
>easily use ID's 0-5 on each bus, and makedev sufficient points 
>appropriately, to match.  What about ID 7?  What is that used for,
>if anything?

There's nothing special about ID 7.  You can put a normal SCSI device on
any unused ID.

>Question on the MicroVAX 3100/20 boxes.... the internal scsi controller 0
>bus only has a strange looping cable with what looks like a 100 pin
>connector.  I am assuming DEC would not loop the scsi bus, even on  that
>short a cable (8 inch or so), although they might.  The VS3100/30
>has a similar cable but much longer by about 3 feet.  Is it using each
>side of the 100 pin connector for the near and far ends of the scsi
>controller 0 bus?  IFF that is the case, is there a source for those
>connectors so I can lengthen it to use a cable long enough go service
>all 5 internal drive bays off the scsi controller 0 bus?  That would
>leave the entire second scsi 1 controller bus for external use.
>Just curious and thinking out loud..... and wondering, just how many
>actual drives I can hang on the beast......(:+}}...

That should be just a normal 50-pin SCSI cable.  It doesn't actually
"loop" back and connect to itself.  It's just connected that way to
ensure that both ends of the cable are terminated.  A longer cable
wired the same way should work, but I don't know where you would find
such a cable.

--
entropy