|
Questions and Answers
Jim McKinstry and Amy Rich
I recently answered a Solaris question and said that you should get
to an "ok" prompt to set an eeprom variable. I received
a couple of emails letting me know that a "better way" is to use the
eeprom command (e.g., eeprom boot-device='disk1:a disk net').
Todd A. Fiedler sent me a better, well-written explanation than what I originally
provided:
The fourth question deals with determining the logical name (of a disk) from
the instance name. While the author's answer was correct, I don't
feel that it was really the answer the writer was looking for. A better way
to illustrate this is to point out the relationship between the devices under
/dev/dsk and the path into/devices that the
symbolic links point to. An example is outlined below (some elements of the
p output are omitted):
$ ls -l c*t*d*s2
c0t0d0s2 -> ../../devices/pci@1f,0/pci@1,1/ide@3/dad@0,0:c
c0t1d0s2 -> ../../devices/pci@1f,0/pci@1,1/ide@3/dad@1,0:c
c0t2d0s2 -> ../../devices/pci@1f,0/pci@1,1/ide@3/sd@2,0:c
You can then look in the /etc/path_to_inst file for the disk in question.
$ grep dad@0,0 /etc/path_to_inst
"/pci@1f,0/pci@1,1/ide@3/dad@0,0" 0 "dad"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^ ^^^
physical path | |
| +--< device type
|
^
instance number
You can see that the instance name for the logical device c0t0d0
is therefore dad0. The instance name is useful when viewing the output
of commands like iostat -x and sar -d. Listing 1 is
a script I like to use for determining this relationship between disks.
|
