User's Guide

With the –d option, you ca
n get instl_dbg to print out the expected size of the volumes it creates
and what the impacts are for each file system. The expected output of percent (%) used is also
shown with the file system type. If the disk does not contain enough space, the amount shy (KB)
column indicates the additional space needed.
# instl_dbg -D . -d
======= Disk and Volume allocation ======
Mount Size Usage Disk / impact amount
Directory (Mb) Group (MB / %) shy (KB)
----------------------------------------------------------------------
/stand 300 HFS vg00 21 7% 0
(swap_dump) 1280 SWAP_DUMP vg00 0 0% 0
/ 200 VxFS vg00 92 46% 0
/tmp 200 VxFS vg00 0 0% 0
/home 20 VxFS vg00 0 0% 0
/opt 976 VxFS vg00 723 74% 0
/usr 1296 VxFS vg00 1035 79% 0
/var 1780 VxFS vg00 229 12% 0
----------------------------------------------------------------------
Size unallocated from group: vg00: 2624Mb
* Expected physical allocation of volumes on disks:
* 0/8/0/0.2.0 (/dev/dsk/c0t2d0) (vg00)
* 3997 - 311197 KB /stand
* 311197 - 1621917 KB primary
* 1621917 - 1826717 KB /
* 1826717 - 2031517 KB /tmp
* 2031517 - 2051997 KB /home
* 2051997 - 3051421 KB /opt
* 3051421 - 4378525 KB /usr
* 4378525 - 6201245 KB /var
* 2686976 KB unallocated
The –l option to instl_dbg performs some lint type checks on the configuration. Variables that
are not assigned with the init keyword appear as follows:
# instl_dbg -D . -l
...
******* Variables assigned without init keyword *******
* _my_variable
Note:
Every variable used in an Ignite-UX configuration
file should be
initialized using the init keyword. If you do not want the variable to be
changed, use the visible_if keyword to prevent it from being displayed
by the Ignite-UX GUI. (See instl_adm(1M) for more information about the
init and visible_if keywords.)
# instl_dbg -D . -l
======= Lint-type Checks =======
******* Variables assigned without init keyword *******
All variables assigned with the init keyword.
37