_hp_disk_layout+={"Modified LVM Layout"} init _hp_disk_layout="Modified LVM Layout" (_hp_disk_layout=="Modified LVM Layout") {

#Disk/File system Layout: volume_group "vg00" {

usage=LVM

physical_volume disk[_hp_root_disk] { } # end pv_options max_physical_extents=2500 logical_volume {

mount_point="/stand" disk[_hp_root_disk] usage=HFS size=307200K

FILE_LENGTH=LONG FRAGSIZE=8192 BLKSIZE=65536 bad_block_relocate=FALSE contiguous_allocation=TRUE

} # end logical_volume

...

logical_volume { mount_point="/var" usage=VxFS

size=73728K remaining 1822720K BLKSIZE=8192

largefiles=TRUE

}# end logical_volume

}# end volume_group "vg00"

}# end "Modified LVM Layout"

Other instl_dbg options

The –vvvoption (very verbose) lists all the selections and values of all variables. You can select use models (for example, "Logical Volume Manager (LVM) with VxFS") and set values for variables to test the impact that a change has on the configuration.

Refer to instl_dbg(1M) for more information on other options available.The hw.info and host.info filesBoth the hw.info and host.info files can be created in either of two ways:

∙When you add a new client to the Ignite-UX server for recovery, the add_new_client script creates these two files (indirectly).

∙When a new client boots from the Ignite-UX server and creates a directory for itself, information about the client hardware is written to the hw.info file.

As of Ignite-UX version C.7.0, the io.info file is also created. This is used by Ignite-UX instead of the hw.info file.

Creating both files

You can easily create both host.info and hw.info16 files on a system by using the same method as the add_new_client script. The following example, run on the client system as root, places the host.info and hw.info files in the current working directory:

16As of Ignite-UX version C.7.0, you will require the io.info file.

41