Ignite-UX Administration Guide for HP-UX 11i (B3921-90079, October 2013)

installation process when this area is available. Boot control parameters are detailed in the
Control Parameters section of instl_adm(4).
You must use instl_adm(1M) to add, change, or delete these boot control and network
definitions.
NOTE: Before upgrading to a new version of Ignite-UX, consider retaining the current control
parameters, located in the first 8 KB of your install file system, so that you can reapply them
after you have successfully updated your Ignite-UX server.
Extract the current parameters into a file, with the following command:
instl_adm -d -F [W|V|I]INSTALLFS > first8k_param_file
Edit the first8K_param_file to define your control parameters. Check your syntax with
the following command:
instl_adm -T -f first8k_param_file
If you want to reapply these control parameters to all install file systems on your Ignite-UX, use
the following command:
instl_adm -f first8k_param_file
If you want these control parameters applied to only one specific install file system, use the
-F option. For more information, see instl_adm(1M).
2. Default disk and file system layout - The capabilities of each operating system release differ
somewhat so HP supplies a different set of disk and file system layout configuration defaults
for each release. These configuration files are located in:
/opt/ignite/data/Rel_release/config
Enter uname -r on the command line to determine the release. For example, the file that
contains the default disk layout for HP-UX 11.11 would be in:
/opt/ignite/data/Rel_B.11.11/config
as revealed by the uname -r command.
3. Software description of a single SD depot - Configuration files that describe software available
from SD depots can be automatically generated using the make_config tool within Ignite-UX.
This tool produces one configuration file per SD depot. Software description configuration
files are located in:
/var/opt/ignite/data/Rel_release/*
4. Software description of an archive — You can create configuration files to enable access to
archives (templates are provided with Ignite-UX in /opt/ignite/data/examples/ to give
you a good starting point). Archive software description configuration files are also located
in: /var/opt/ignite/data/Rel_release/
5. Local configuration overrides that apply to all clients - It is often convenient to specify defaults
to be applied to every client, in addition to the necessary operating system configuration
installed from a particular Ignite-UX server. For example, you might want to specify the same
NIS domain for all systems. You must include this type of configuration override information
in:
/var/opt/ignite/config.local
This file is not overwritten when the operating system is updated.
6. Client-specific configuration file - This file contains specific directives appropriate for a specific
system to override what may have been defined as general defaults for all systems in earlier
configuration files. For example, you might want to customize the disk layout beyond what
the operating system release defaults allow in:
/opt/ignite/data/Rel_release/config
160 Customizing Your Installation