On 3/22/07, der Mouse <mouse at rodents.montreal.qc.ca> wrote:
David Betz wrote:
I also have a TD Systems Viking SCSI controller
in the system with a
CD-ROM drive attached. What device name would I use for that?
I don't know; I'm not familiar with Ultrix naming conventions for CD
drives. Probably ra1 or cd0 or some such.
I don't know about Ultrix 4.3 in particular, but my memories of Ultrix
1 and 2, you might have to inspect the results of the kernel rebuilt
to see what device major/minor numbers map to the CD-ROM drive, or
more specifically, to the secondary MSCP controller. It really
doesn't matter to the kernel what the device files are named in /dev,
just the major/minor numbers tacked onto those device files. You can
also inspect, IIRC, /dev/MAKENOD or something similar, the script that
goes out and creates device files as required. There might be some
mention of CD-ROM drives under an Ultrix as new as 4.3.
I'd also
like to know how to address that drive from the MVII boot
prompt so that I can boot directly off of the CD-ROM.
This is another issue entirely; the naming used by the ROMs does not
bear much relation to the names used by Ultrix. I also don't know that
SCSI controller; it might or might not be bootable, and if not, there
is no name you can use to boot from it. It probably needs to speak
MSCP to be bootable, though it's been too long for me to remember the
ROM naming scheme for MSCP devices.
In general, booting an MSCP device from the "lazy sargent" prompt
(>>>), you'd have to know details about the specific machine to be
exactly right, but I'd start with "B DUB0", for the "DU" device,
second controller, drive 0. If the CD-ROM happens to be numbered 6,
which was common in Sun boxes (in case you borrowed such a drive), you
might also try "B DUB6". In newer MicroVAXen than I've ever owned, I
think there's a way to get the ROMs to dump out what MSCP unit
names/numbers respond to some sort of probe. With older machines, you
just have to "know" what device names are going to be valid.
-ethan