Ignite-UX Custom Configuration files

If _hp_locale is not set, it is set int
ernally to the first value of the locale keyword for a selected
sw_sel. If multiple selected sw_sels contain locale keywords, the _hp_locale variable is set
to the first value of the locale of the first selected sw_sel.
The geocustoms
54
application is used to manage the default locale on a system. If a locale is not
important, do not set one. If you set _hp_locale, set it to a locale that exists on the final
installed system, it should be visible in the output of locale –a.
You can run the geocustoms command at any time to manage the languages installed on your
system (for example, you can remove some or change the default locale). You cannot use the
geocustoms command to install non-existent locales back again.
The geocustoms program modifies /etc/rc.config.d/LANG to set a locale. The value of
SET_NULL_LOCALE for _hp_locale leaves /etc/rc.config.d/LANG with no locale set.
The geocustoms program is easy to use because it provides a full-screen menu-driven interface for
managing locale support. It does have command line options if you prefer not to use the user
interface.
The standard configuration files set the variable _hp_locale visible_if false to prevent
this variable from being visible or changeable when using the Additional button in the Ignite-UX
GUI. The locale is chosen using the Languages button on the Basic tab in the Ignite-UX GUI.
_hp_cfg_detail_level
This internal string variable is fundamental to the configuration file management done by Ignite-UX.
It is used primarily in client-specific configuration files. It contains a list of option characters that
represent which aspects of the configuration file are modified by the user interface. This represents
the areas of information that the configuration file, written by the UI, contains.
The Ignite-UX process uses this information in case it needs to rewrite the configuration file. The
configuration file is rewritten both by the user interface and by the client installation process. In
these cases, the process uses _hp_cfg_detail_level to determine how much information is
represented by the configuration file and so it can write out just the minimal amount of information
and let the rest be supplied by the other configuration files in the INDEX file.
The option characters recognized in the _hp_cfg_detail_level string that is found in a client-
specific config file are as follows:
-i INDEX cfg clause selection (file contains the line telling which INDEX file entry should be
used).
-v Variable and use model settings.
-s Software selection settings.
-S Modified software selection definitions.
-r Modified software source definitions (depot information).
-f Modified file system information.
-p System identity information.
-T The post_config_script selections settings.
-h Hardware control information (hw_instance_num statements).
-l Other control information (global mod_kernel statements for example).
54
The geocustoms command is deprecated and is planned for obsolescence in a future release of HP-UX.
86