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

10 Obtaining Ignite-UX
Frequently asked questions
Following are the frequently asked questions in obtaining Ignite-UX (IUX), which is a compilation
of all the available feedback from the users.
What is different about the Web version?
Usually nothing, other than the software might be available prior to the media release. Additionally,
you can download one depot containing all supported operating system releases. On some
occasions, the Web release will contain additional fixes not present in the media release.
Is Ignite-UX available on media?
If you have subscription service for the Application Media Release then, Ignite-UX is available to
you on the media without a codeword. In other words, free.
How do I update my Ignite-UX server to a new version?
In general, each new version of Ignite-UX is compatible with any scripts or configuration files that
were delivered with older versions.
If you follow some simple guidelines, updating to a new version of Ignite-UX involves running
swinstall to install the new version; this is the same procedure as installing it for the first time.
There is no need to uninstall the old version. For more information about updates to be performed
see the white paper Installing and Updating Ignite-UX available at http://www.docs.hp.com/en/
IUX/infolib.html
Updating to a new version of Ignite-UX preserves any changes you have made to files under the
/var/opt/ignite and /etc/opt/ignite directories. Changes to any files under /opt/
ignite are lost during the update. HP does not recommend changes to any files under /opt/
ignite.
Guidelines for ensuring easy updates:
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.
Ensure that you install all of the Ignite-UX filesets you had previously installed, so that no version
mismatch of fileset must occur.
How much of Ignite-UX do I need to install?
Depending on what you are using Ignite-UX for, you might 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 disk space is not a limitation, install all the required bundles for the HP-UX releases.
For all cases the IUX.IGNT-ENG-A-MAN fileset can be omitted or removed if on-line documentation
is not required.
• 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 might be 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.
Frequently asked questions 39