Ignite-UX Custom Configuration files

(
_my_command_c_option ! ~ "^(ab|cd|gh)[[:digit:]]+[[:digit:]]$") {
error+=”The user must start with ab, cd, or gh followed by only digits”
} else {
note+=”The user chosen was “ + ${_my_command_c_option}
}
Try to restrict yourself to simple regular expressions. If complex regular expressions are needed, test
them extensively against large amounts of potential values to ensure they behave the way you
expect.
Configuration parameters in the installation file system
This section discusses configuration parameters that are most suited to being placed in an
installation file system using instl_adm. The most likely reason you would place them in the
installation file system would be that they need to be seen by Ignite-UX to control the way Ignite-UX
works before it attempts to mount the client's directory from an Ignite-UX server (in a network
installation).
For more information regarding the configuration parameters discussed in this section, see
"Configuration examples" and "Example Three (be careful what you a
sk for, you just might get it).”
Networking
The information in this section only applies to the usage of Ignite-UX after the installation kernel has
started running AND after the installation file system has been loaded (since the configuration is
stored in the first 8KB of the installation file system).
The following networking configuration parameters are covered elsewhere in this document. For
more information, see the following:
_hp_lanadmin_args (see "_hp_lanadmin_args")
_hp_nfs_mount_opts (see "_hp_nfs_mount_opts")
_hp_nfs_mount_retries (see "_hp_nfs_mount_retries")
_hp_tftp_cmds (see "_hp_tftp_cmds")
The following networking options are best set within an installation file system since Ignite-UX must
be aware of them either before it contacts the Ignite-UX server or when it is attempting to start
networking.
The DHCP configuration parameters are mentioned here because Ignite-UX requests an IP address
using DHCP when it starts and before it first attempts to make contact with the Ignite-UX server.
 dhcp_class_id—this configuration item can be used "as is" (for example, applies to every
LAN interface) or can be given optional LAN information so the DHCP class id is only expected
to be used with one particular LAN interface, for example,
dhcp_class_id[0/0/0]="Ignite_clients".
This item is extremely useful if you have no control over the other DHCP servers on the network
and do not want to accept temporary IP addresses from those servers. For example, the
following configuration splits Itanium®-based and PA-RISC clients into two different DHCP
classes:
148