Ignite-UX Custom Configuration files

manually cha

nge the io.info file, this file is considerably more complex than the hw.info file and

manual changes are likely to leave the file unusable.

Miscellaneous configuration tips

 In Ignite-UX configuration files, TRUE and FALSE should be stated only in upper- or lower-case

and never in mixed case. Ignite-UX does not understand TRUE or FALSE when they are in mixed

case. This applies to other keywords as well.

 Be careful when deciding to use the = or += operators. The += operator enables you to add to

something, while the = operator removes any current value for a variable and replaces it with the

new value being assigned. See the "_hp_disk_layout" section on page 88 for information

abou

t how = and += can be used to replace existing disk layouts or add more layout choices.

The error keyword is a good example of the need to use += at times. If you use =, you remove

any previous error messages that may have been encountered. If you use +=, all of the error

messages, both previous and new, can be shown to the user.

 When you are using the Ignite-UX GUI to add new logical volumes, you might want to consider

choosing the logical volume that is most similar to what you want to create and use that as a

starting point. Change the attributes and instead of selecting Modify, then select Add to create

your new logical volume.

 When setting a network configuration, review instl_adm(4) to verify whether the modifier

final (placed before a keyword, such as dns_domain) is required to retain the configuration

when the system is installed. If it is required and you do not provide this modifier, the

configuration is only kept for the duration of the installation and is discarded at the final system

reboot.

 If you do not want to preserve instance numbers when cloning a system, you should remove all of

the hw_instance_num lines from the system_cfg file. Unlike network recovery archives,

you cannot remove hw_instance_num lines from a recovery tape after creation. Instead, if

you use a recovery tape for cloning and do not want to preserve instance numbers, you must

preview using make_tape_recovery with the -p option, edit the associated configuration file

(/var/opt/ignite/recovery/latest/system_cfg), and then resume creation of the

recovery tape using make_tape_recovery with the -r option. For a network recovery

archive, you would find the system_cfg file in the following location:

/var/opt/ignite/clients/<MAC>/recovery/<DATE-TIME>/system_cfg

 If you need to create swap spaces larger than 32GB with HP-UX 11i v2 or later releases of HP-

UX, you should be running Ignite-UX version C.7.0 or later - previous versions of Ignite-UX do not

allow you to do this.

Analyzing the HP-UX default B.11.11 cfg clause

The following is from a default /var/opt/ignite/INDEX showing the configuration files

referenced by the HP-UX B.11.11 cfg clause:

cfg "HP-UX B.11.11 Default" {

description "This selection supplies the default system configuration

that HP supplies for the B.11.11 release."

"/opt/ignite/data/Rel_B.11.11/config"