Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!cs.utexas.edu!rice!sun-spots-request
From: geof@aurora.com (Geoffrey H. Cooper)
Newsgroups: comp.sys.sun
Subject: Re: Problems installing CDC Wren VI
Keywords: Hardware
Message-ID: <4786@brazos.Rice.edu>
Date: 7 Feb 90 19:23:00 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 21
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n23
X-Sun-Spots-Digest: Volume 9, Issue 32, message 3

In article <4673@brazos.Rice.edu> S1.FXK@isumvs.iastate.edu (FRITZ KEINERT) writes:
>X-Sun-Spots-Digest: Volume 9, Issue 23, message 9 of 14
>
>The  relationship  between minor device numbers (as far as the Sun OS is
>concerned) and the device number that the drive is jumpered to is this:
>minor  device  number  =  8  * drive number. Thus, the Wren VI jumpered
>to position 1 should be major device 7 (or whatever), minor device  8.
>During boot, our machine shows something like "device sd2 master 7 slave
>8" or whatever it is. Anyway, our Wren VI, jumpered to position 1, is
>known to the system as sd2.

I also noticed this sort of behavior.  I believe it is because Sun is
mapping the internal drives to sd0 and sd1, leaving sd2 and sd3 for
external.  Our Wren VI's are jumpered to zero, and I was surprised to find
that this caused them to be sd3.  It looks like Sun is internally mapping
the drive numbers to 3-drive#.

Anyway, my SS1 monitor is perfectly content to boot off sd3a, so there is
really no problem (setenv boot-from sd(0,3,0)vmunix).

geof@aurora.com / aurora!geof@decwrl.dec.com / geof%aurora.com@decwrl.dec.com