Ignite-UX Administration Guide for HP-UX 11i (B3921-90079, October 2013)
you can further customize the configuration using the GUI, or accept the configuration defaults to
begin the installation immediately.
The order of the configuration files within a cfg clause is significant; attributes specified in a later
configuration file can override the same attributes specified in an earlier configuration file. Two
configuration files are used implicitly every time:
• Any information stored in the first 8 KB of
/opt/ignite/boot/Rel_release/[W|V|I]INSTALLFS is implicitly prepended to each
configuration list and is the first configuration data processed.
• The client-specific configuration file /var/opt/ignite/clients/client/config, if it
exists, is implicitly added as the last configuration file for each configuration.
A default cfg clause for each release is shipped as part of Ignite-UX. Additional cfg clauses are
added when you:
• Save a named configuration from the GUI with the Save As button.
• Create a configuration by modifying the /var/opt/ignite/data/INDEX file directly.
• Use the manage_index command to automate /var/opt/ignite/data/INDEX file
modifications.
NOTE: To facilitate client recovery configurations, a CINDEX configuration file, similar to
an installation INDEX file, is created. For more information, see Chapter 15: “Recovery”
(page 188) or see manage_index(1M) and make_net_recovery(1M).
Additionally, you can specify how installation software is handled by Ignite-UX using the following
three constructs:
• A sw_source clause specifies an SD depot or an access method to a server containing
software depots.
• The sw_sel clause specifies the software contained in the SD depot or specifies the path to
a depot on the server or media. Typically there is one sw_sel definition per software bundle
or depot.
• The sw_category clause is simply a mechanism for grouping sw_sel definitions.
See the clauses in Defining an Installation Depot for example usage of the above constructs. For
more information, see instl_adm(1M).
Be sure to pass all user-generated configuration files through the following command to check for
syntax errors:
instl_adm -T -f cfg_file
Example Configuration Files
This section shows a few example configuration files to give you an idea of their look and
capabilities. For a complete description of Ignite-UX configuration files, see instl_adm(4).
For additional examples of configuration files, see the document, Ignite-UX Custom Configuration
Files available at
http://www.hp.com/go/ignite-ux-docs
Defining Disks
This example shows how a disk might be defined. Here, the disk is located at hardware address
2/0/1.6.0 and does not use Logical Volume Manager (LVM) or Veritas Volume Manager by
Symantec (VxVM). The disk contains the root ( / ) file system and a swap area. The swap area
takes up 512 MB and the root file system assumes the remainder:
partitioned_disk
{
Using Configuration Files 163