Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

• 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 website, 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 must 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, you require
Ignite-UX.MinimumRuntime.
Installing a combination of different versions of Ignite-UX filesets on a client is not recommended.
Hence, if you decide to update only a subset of Ignite-UX, use swremove to delete the updates
that are not required.
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?
The media versions of Ignite-UX have the os_release attribute set to match the revision of the
media (that is, B.11.11 or B.11.23 or B.11.31). A user might 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 (that is, it will then be applicable on all HP-UX B.11.* systems).
See the sample script at: /opt/ignite/data/scripts/examples/open_media_iux
40 Obtaining Ignite-UX