Ignite-UX Frequently Asked Questions

- Do not modify any files under the /opt/ignite directory. If you
need to modify any configuration files under /opt/ignite, copy them
to an equivalent directory under /var/opt/ignite then modify the
INDEX file to use them in the new location instead. Some files and
scripts contain comments that describe the recommended modification
procedure to use.
If you must modify files under /opt/ignite, then save a copy of
your changes so you can restore the changes to the new files after
updating Ignite-UX if necessary.
- Make sure you install all of the Ignite-UX filesets you had
previously so you do not end up with a combination of old filesets
and new filesets.
===============================================================================
9.4
Q: How much of Ignite-UX do I need to install?
A: Depending on what you are using Ignite-UX for, you may be able to
reduce the disk space usage by not installing the full product.
Below is a list of typical usages and a list of what parts of
Ignite-UX you need. If you are not concerned with disk space, it is
easiest just to install the bundles for the HP-UX releases you plan
to work with. For all cases the IUX.IGNT-ENG-A-MAN fileset can be
omitted or removed if you do not want on-line documentation.
- Ignite-UX server to install HP-UX on clients - Install the
Ignite-UX bundles for each HP-UX release which you plan to install
onto clients.
- Ignite-UX server to support network recovery for clients - Install
the full Ignite-UX bundle for each version of HP-UX that your
clients are running. It maybe easier to install the B5725AA bundle
(for versions of Ignite-UX before C.7.0) or IGNITE (for versions of
Ignite-UX from C.7.0). Note that the IGNITE bundle is the same as
the B5725AA bundle - it is only a new name.
- Using only make_tape_recovery on clients create the recovery
commands depot on your Ignite server and install the HP-UX release
specific bundle applicable to your system or if you have downloaded
Ignite-UX from the web install the release specific version of
Ignite-UX from that depot. That bundle contains everything
required to create a recovery tape.
- Using only make_net_recovery on a client - The filesets a client
needs are normally installed by the Ignite-UX GUI to each client
from the depot created by pkg_rec_depot. The bundle IUX-Recovery
should be installed from the recovery commands depot to support
make_net_recovery.
- A network boot helper system - To setup a client on a remote subnet
that is used just to allow clients to boot from the network, and
then contact a remote Ignite-UX server, all you need is
Ignite-UX.MinimumRuntime.
Keep in mind that it is not a good idea to install a combination of
different versions of Ignite-UX filesets on a client. So if you
decide to update just a subset of Ignite-UX, you may want to use
swremove to remove the portions you no longer need.
===============================================================================
9.5
Q: How can I copy Ignite-UX from media to a local depot such that
Ignite-UX from this new local depot will be installable on all HP-UX
B.11.* systems?
A: The media versions of Ignite-UX have the "os_release" attribute set
to match the revision of the media (i.e., B.11.11 or B.11.23 or
B.11.31). A user may copy the Ignite-UX bundles from media into a
local depot and run swmodify to change the value of the "os_release"
attribute to be "wide open" (i.e., it will then be installable on all
HP-UX B.11.* systems).
See the sample script at: /opt/ignite/data/scripts/examples/open_media_iux
===============================================================================
----------------------------------------
10. Loading Patches
----------------------------------------