Ignite-UX Custom Configuration files

Using the instl_dbg command
Introduction
The instl_dbg command is often overlooked but offers valuable functionality in testing the effect
of a change in a configuration file. This section introduces some of the useful functionality of
instl_dbg and how it can be combined with the itool command to rapidly prototype and test
configuration changes.
Requirements
The instl_dbg command requires some information that can only be created during an
installation session either by adding a new client to an Ignite-UX server, by running
make_net_recovery, or by running make_tape_recovery with the –s option. The files that
are most needed are hw.info
13
, host.info, and config.sys.
/opt/ignite/bin/instl_dbg -D client_directory [-f file] [-v] [-a {l|r}]
[-cdls|-A] [-V var[=value]] [-S swsel[=TRUE|=FALSE]]
[-U use_model[=TRUE|=FALSE]] [-?]
The one command-line option required by instl_dbg is the –D option. This would usually point to
a per-client directory on an Ignite-UX server. It must contain all of the information that instl_dbg
needs to run. If you add a new client to an Ignite-UX server, the information you need is created
automatically. However, this does not help when you have a new client that has never had an
operating system installed.
Using the itool command
The itool command provides the Wizard and Advanced interfaces during recovery and
installation. It is not well known that the itool command can be run from the command line on an
Ignite-UX server to manipulate the configuration for a client. The itool command accepts the
following options
14
:
# itool -?
itool: illegal option -- ?
usage itool [ arguments ]
-d <directory path>
-i <client name>
-m 'demo', 'push', 'pull', 'quick', or 'wiz'
-w show welcome screen in push mode
(The default is -m pull)
The only method you really need to worry about when using itool is as follows:
# itool –d <client dir> -m pull
13
As of Ignite-UX C.7.0 the io.info file is also required.
14
HP does not recommend the use of itool outside of its normal use (running on a client system during installation or
recovery or via the Ignite user interface).ignite(1)). This information is presented here so itool can be run in
conjunction with instl_dbg for rapid prototyping of configurations.
35