|
The only way I'm aware of is by checking at the console (>>> show dev)
*before* booting from the CDROM. But for all I know, mini-root may
write a log file somewhere (in / ?) which provides the startup
information similar to that which you get in the syslog{.dated} log
files (same as uerf). You could also brute force it by just ./MAKEDEV
rz{0,1,2,...,n} and see if any of them mount. If they exist you'll get
an "invalid device" message.
|
| To: thomson
Cc: lct, may
Subject: DECnotes Reply 489 (dec_mls_plus)
Date: Fri, 25 Apr 97 12:29:29 -0400
From: lct
X-Mts: smtp
1) I believe that with MLS+ V4.0a _all_ boots (including
the cdrom boot) automatically make device files in
/dev for any scsi devices that are on the system at
boot time.
2) An easier way to see if a device is actually "attached"
relative to a device file in /dev is to use the file
command on the RAW device:
file /dev/rrz*a
This can be done with devices that already exist (see
#1 above) or on MLS+ V3.1a systems, do a MAKEDEV for
scsi devices covering all controllers that you have and
want to check.
This method is usually better than trying mounts, which
require proper disklabel and file systems on the disk
that you want to mount.
I think there is another command or two that let you do this,
but I can't remember what they are. If I find them, I'll let
you know.
OK - I found one:
scu:
>scu
scu> scan edt
Scanning all available buses, please be patient...
scu> show edt
CAM Equipment Device Table (EDT) Information:
Device: RZ26L Bus: 0, Target: 0, Lun: 0, Type: Direct Access
Device: RZ26L Bus: 0, Target: 0, Lun: 1, Type: (not present)
Device: RZ26L Bus: 0, Target: 0, Lun: 2, Type: (not present)
Device: RZ26L Bus: 0, Target: 0, Lun: 3, Type: (not present)
...
Device: RZ26N Bus: 0, Target: 1, Lun: 7, Type: (not present)
Device: RRD43 Bus: 0, Target: 4, Lun: 0, Type: Read-Only Direct Access
Device: RRD43 Bus: 0, Target: 4, Lun: 1, Type: (not present)
Device: RRD43 Bus: 0, Target: 4, Lun: 2, Type: (not present)
...
scu>
(... implies that I've clipped out some lines)
- -lee
|
| To: thomson
Cc: lct, may
Subject: scu - continued
Date: Fri, 25 Apr 97 12:40:46 -0400
From: lct
X-Mts: smtp
It seems that after 'scan edt' a reduced form of the info
can be had by using 'show edt lun 0' instead of show edt.
scu> show edt lun 0
CAM Equipment Device Table (EDT) Information:
Device: RZ26L Bus: 0, Target: 0, Lun: 0, Type: Direct Access
Device: RZ26N Bus: 0, Target: 1, Lun: 0, Type: Direct Access
Device: RRD43 Bus: 0, Target: 4, Lun: 0, Type: Read-Only Direct Access
Device: TLZ06 Bus: 0, Target: 5, Lun: 0, Type: Sequential Access
scu>
|
| From: US2RMC::"Becker@mail.dec.com" "Philip Becker" 25-APR-1997 13:24:32.94
To: "'BAT@smurf.enet.dec.com'" <smurf::BAT>
CC:
Subj: Followup to an answer to TCS
Barb,
Attached is a followup from TCS on the question of how to show devices.
Turns out they are trying to automate something. Anything else you can
add?
Thanks,
Phil
>----------
>From: Susan A. Heath[SMTP:sheath@tcs-sec.com]
>Sent: Friday, April 25, 1997 10:55 AM
>To: Philip Becker
>Subject: Re: Response to one of your questions
>
>I guess I need to phrase my questions better. We are trying to write a C
>program to restore a complete system from tape for the user so they don't
>have to do it by hand. I was wondering if there is a system call or
>something to tell what is in the SCSI chain so we can present the user with
>a list of disk choices to restore to rather than them having to just know.
>
>At 08:53 AM 4/25/97 -0400, you wrote:
>>Sue,
>>
>>This is an answer from engineering.
>>
>>Phil
>>
>>>
>>> The only way I'm aware of is by checking at the console (>>> show dev)
>>> *before* booting from the CDROM. But for all I know, mini-root may
>>> write a log file somewhere (in / ?) which provides the startup
>>> information similar to that which you get in the syslog{.dated} log
>>> files (same as uerf). You could also brute force it by just ./MAKEDEV
>>> rz{0,1,2,...,n} and see if any of them mount. If they exist you'll get
>>> an "invalid device" message.
>>>
>==========================================================================
>Susan A. Heath sheath@tcs-sec.com
>Trusted Computer Solutions, Inc. Phone: 703-318-7134
>13873 Park Center Road Fax: 703-318-5041
>Suite 225
>Herndon, VA 20171
>==========================================================================
|