Thanks to those that responded with instructions for a smooth install and other info.
"Sean O'Connell" <sean_at_stat.Duke.EDU>
"Dr. Tom Blinn, 603-884-0646" <tpb_at_doctor.zk3.dec.com>
"Monroe, David" <David_at_psds.com>
Girish Phadke <pgirish_at_binariang.maxisnet.com.my>
The original question follows the responses.
Scott Taylor
smt_at_gamma.physics.uiowa.edu
--------------------------------------------------------------------------------
Sean O'Connell --
Hi-
msb0 is the microsoft sound board compatible sound card for
use w/ mme (multi-media extensions).
__________________________________________________________________________________
Dr. Tom Blinn --
Plug in the drive.
Use scu to verify that it's spun up and at the address you expected.
If you didn't already create the device special files, you will need
to use the explicit addressing modes scu supports, otherwise you can
use the device files to address the drive.
Disklabel the device and start using it.
You don't need to reboot with genvmunix, you don't need to change the
configuration file or build a new kernel. That's all old stuff. The
V4.0x SCSI subsystem works without explicit device data structures in
the kernel.
The "msb" is for a MicroSoft sound board, which you might not have; I
have no idea why that line was present in your kernel config file, but
perhaps sizer put it there.
____________________________________________________________________________________
David Monroe --
All that we usually do to add a new drive is to type "cd /dev", then
"./MAKEDEV rz1" (if the new drive is SCSI ID 1). At that point, we can
label, partition, and format the disk.
____________________________________________________________________________________
Girish Phadke --
Hello
If the SCSI controller is allready configed there is no need to reboot
the system. scu scan edt command can be given so SCSI table is updated.And then you MAKEDEV
the device.
While reboot takes care of both the above actions.
______________________________________________________________________________________
Original post:
I have an alphastation 600 with DU 4.0D and just added a Seagate 18.2 GB ultra-SCSI external
disk drive -- my first such experience. I installed and partitioned the disk and can use it
now, but the installation was less than smooth as it wasn't clear to me -- and still isn't -- as
to where the Dynamic Device Recognition leaves off and where I get involved. The documentation
isn't clear on this issue. This is what I did:
1. After I installed the drive and powered up ( external drive was turned on first), the disk
wasn't initially recognized by the system. It should have been, right? I ended up rebooting
using genvnumix, and when I did the disk was recognized and the MAKEDEV had been done. The
DEC System docs say that a reboot isn't necessary with DDR. What am I missing?
2. Since I rebooted with genvmunix, I thought I might have to edit the configuration file DELTA
to include the new device. I ran sizer and found the entry
#UNSUPPORTED msb0 at eisa0 slot 4 in /tmp/DELTA
I changed this to: device disk msb0 at eisa0 slot 4 (in DELTA)
and tried to rebuild the kernel with doconfig -c DELTA. This didn't get far so I took out
the new device entry and tried again, this time successfully. Apparently the
configuration file doesn't need the new entry since the device was already recognized.
3. I went on to label and partition the drive with the widget, then made a file system with
newfs and mounted it.
Although the disk is working, my experience has left me wondering how a "proper" installation
should go. I'd appreciate any advice on how to procede with my next disk installation, and
comments on exactly what DDR does.
Received on Fri Sep 18 1998 - 13:48:22 NZST