Ignite-UX Reference (March 2010, B3921-90005)

instl_adm(4) instl_adm(4)
Because Ignite-UX does not control kernel boot inventory, some inventory information
for blocked devices may be collected. All blocked devices will be hidden and not avail-
able for selection during install. To take effect, this variable must be set in the
*INSTALLFS file using instl_adm.
inventory_block_protocols = { "protocol"[,"protocol" ]... }
This keyword is used to control Ignite-UX inventory functionality. Ignite-UX will not
collect inventory information for devices connected to I/O adapters of listed I/O protocol
types. Restricting the Ignite-UX inventory process reduces the time required to collect
I/O configuration information but will result in some I/O information not being available
for install and recovery processing. Because Ignite-UX does not control kernel boot
inventory, some inventory information for blocked devices may be collected. All blocked
devices will be hidden and not available for selection during install. To take effect, this
variable must be set in the *INSTALLFS file using instl_adm.
io_info = io.info_entry
io_info += io.info_entry
This keyword is used to record details about hardware configuration for use during recov-
ery. Each value corresponds to a complete io.info entry and together they form a com-
plete saved io.info configuration file. These values are intended for Ignite-UX internal
use and should not be modified.
File System Configuration
The default disk and file system configuration may be specified as a partitioned_disk or a vol-
ume_group.Inapartitioned_disk configuration, each disk may have a maximum of two parti-
tions. One partition is a file system and the other is swap space. This configuration is also referred to as the
"whole disk" layout. The volume_group configuration allows one or more disks to be configured into a
Logical Volume Manager (LVM) volume group or VxVM disk group. That volume group may then be
split into one or more logical volumes. Each logical volume may be used for either file system, swap or
dump space. An LVM volume group may also be split into one or more physical volume groups, with at
least one disk in each physical volume group.
The general syntax of the disk and file system configuration is:
partitioned_disk
{
physical_volume disk[hw_path|index|dev_spec]
{
physical_volume-attributes...
}
fs_partition
{
file-system-attributes...
}
swap_partition
{
swap-attributes...
}
}
volume_group group_name
{
volume_group-attributes...
physical_volume group "pvgname"
{
physical_volume disk[hw_path|index|dev_spec]
{
physical_volume-attributes...
16