Ignite-UX (IUX) Frequently Asked Questions (July 2013)

unset SW_INITIAL_INSTALL
/usr/sbin/mk_kernel -f -o /stand/vmunix
"
=============================================================================
==
1.14
Q: Does HP support Ignite-UX through a firewall?
A: HP has not tested Ignite-UX through a firewall.
It should be possible to configure a firewall such that Ignite-UX
functions properly. For more information, see the section on
modifying a Bastille-hardened system for Ignite-UX in the security
chapter of the Ignite-UX Administration Guide available on
http://www.docs.hp.com.
HP does support Ignite-UX in conjunction with Bastille on HP-UX 11i
systems. The Ignite-UX Administration Guide describes how to
configure Bastille on both Ignite-UX servers and clients.
=============================================================================
==
1.15
Q: What do I do when I get file system full messages during installation
or recovery when '_hp_ignore_sw_impacts' is set to 1?
A: When installing or recovering a system, Ignite-UX takes a small
amount of space (a few MB) in each of the / and /usr file systems to
hold some commands that Ignite-UX will use. Some of these commands
are used during the installation or recovery of HP-UX, and some are
used after the first reboot.
If the / or /usr file systems are nearly full when creating a golden
image (and configuration) or recovery archive, or when installing an
SD depot where the impacts will leave file systems nearly full, and
you have set '_hp_ignore_sw_impacts' to 1 as follows:
init _hp_ignore_sw_impacts=1
It is possible that you may encounter a file system full problem
during recovery or installation. Normally, the configuration
variable that controls how much free space should be in a file system
increases the size of a file system so there is at least 10% free;
10% being the default value. This default value guarantees that
there is enough free space for an installation or recovery.
Setting '_hp_ignore_sw_impacts' to 1 means that Ignite-UX will not
resize the file systems according to impacts to guarantee some free
space. If you set '_hp_ignore_sw_impacts' to 1, you must ensure that
there is some free space available in / and /usr during installation
or recovery (at least 20MB) to avoid file system full issues.
If you do not set '_hp_ignore_sw_impacts' to 1, you can ignore this
information. This issue is most likely to affect you if you create a
recovery archive in which you have set '_hp_ignore_sw_impacts' to 1