Ignite-UX Custom Configuration files

option to give
explicit installation file system names. However, you should try to keep the various
installation file systems consistent.
This issue creates difficulties when you mix system types that are running at different duplexes and
speeds, rather than setting the systems to autonegotiate both. To avoid this situation, you should
develop and follow a consistent approach to speed and duplex settings.
If you have a gigabit switch set to only operate at 1000FD (gigabit speed with full duplex) and the
gigabit interface on system is attempting to autonegotiate the speed and duplex, a 1000FD link
will be achieved. This is because the only duplex supported at gigabit speeds is full duplex.
However, this is only true of 1000Base-T interfaces so 1000Base-SX interfaces must autonegotiate
or they will fail to form a link.
Note that if you are using 1000Base-T interfaces and the switch is autonegotiating link speed and
duplex or it is hard set to use 1000FD, you should not need to use _hp_lanadmin_args to force
any speed/duplex values.
Control
The _hp_keyboard (see the "_hp_keyboard" section) control configuration item although not
strictly an installation file system variable, it is a good idea to set this to a keyboard type if all of
the systems that have keyboards are the same type. This prevents HP-UX from asking for a
keyboard type when you have a graphics console.
The following control options are best set within an installation file system because Ignite-UX must
be aware of them before it contacts either the Ignite-UX server or when it is attempting to start
networking:
 run_ui—this configuration item controls whether the installation process should be interactive or
not. If set to FALSE, the Ignite-UX GUI does not run and it is assumed that the configuration files
provide the complete configuration required to install the system. If this is not true and there is
not enough information, the installation changes to become interactive.
Be careful when setting this item to FALSE as it is possible (if the system is booted from the
network) to reinstall the system without any way to prevent it (except using the console, powering
off, or resetting the system). This is regardless of how you set control_from_server (see next
configuration item).
 control_from_server—this configuration item is used to determine if the Ignite-UX server that
Ignite-UX has connected to should control the session or not. If set to TRUE, you must run
ignite (the command) on the server and then manage the client remotely (you can break out of
server control on the client console).
 use_expert_ui—this configuration item is very useful if you are an advanced user of Ignite-UX
and want to run the Ignite-UX GUI most of the time instead of using "Wizard" mode. Using the
Ignite-GUI, provides a much finer level of control over the system to be installed than Wizard
mode does. To make the Ignite-UX GUI the default, add the following line to the installation file
system:
use_expert_ui = true
151