Ignite-UX Frequently Asked Questions

client on which the archive was created.
The first error, "pax_iux: X: Cross-device link", is caused when
two files exist as hard links in the archive, and if these two files
would reside in separate file systems. For example, if you created
an archive on a client that did not use LVM the root file system is
all one file system and the files, /usr/local/bin/f1 and
/opt/myprod/bin/f2, are hard linked. If you make an archive of this
client then try to apply it to a client that uses LVM and has /usr
and /opt as separate file systems this error occurs.
The second and third errors, "pax_iux: X: File exists and pax_iux:
X : Device busy", can occur when the archive has a symbolic link
(symlink), or regular file that is named the same as a directory or
mount point that exists when the archive is installed. For example
if the original client on which the archive was made has a symlink
like /opt/myprod -> /extra/space, and when you are installing a
client from the archive you decide to create a mounted file system as
/opt/myprod. The pax command fails to create the symlink because a
directory exists in its place.
You can recover from this failure when the error happens because, on
the client's console, you are asked if you want to push a shell.
Answering yes, and then typing exit 2 from the shell you can ignore
the error and continue the installation.
Once the client is up, you can more easily determine what to do with
the paths that created the errors.
To avoid the errors, the client that the archive is created from
should not contain soft links between directories that are likely to
be created as separate file systems.
===============================================================================
----------------------------------------
9. Obtaining Ignite-UX
----------------------------------------
9.1
Q: What is different about the Web version?
A: Usually nothing, other than the software may 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.
===============================================================================
9.2
Q: Is Ignite-UX available on media?
A: 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.
===============================================================================
9.3
Q: How do I update my Ignite-UX server to a new version?
A: 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 remove the old version. If you are unsure of exactly what
to install to perform the update please read the white paper
"Installing and Updating Ignite-UX" available from the following URL:
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: