RE: 7Zip Problem

I regularly download and try to use software that was compiled for AIX.
Frequently, that software expects files to be in their standard Unix
locations /usr/local/bin, /usr/local/lib, /usr/local/share, et al.
But
the IBM tools expect them to be in /QOpenSys/usr/local -- thus creating
a conflict and breaking the software.

So I always have /usr/local and /qopensys/usr/local symlinked.

This can be solved with chroot. Have you looked into that?

are all careful to maintain case, but that doesn't /hurt/ anything if
they're running in a case-insensitive filesystem... it's just not
necessary. Granted, if one of them had files that had the same name
where the only diff was the upper vs. lower case characters, then
something would break.

At a former client, we had a software package that had its configuration
file in the same directory as the script (so, /usr/local/something). That
file had to be named CONFIG. No problem there. But there were additional
parameters that could be specified (sort of like overrides for this
installation), and they had to be in a file named config (note the case
difference) in the same directory. These two files had different formats
for their entries (one was a colon-separated list; the other was more like a
properties file with X = Y entries).

I did not make this design; I only used it. My point is that if you link
/usr/local to /QOpenSys/anything a package like this will not work. But you
could link the opposite direction (so that the actual files reside within
QOpenSys and you'd be OK.

But chroot is far better.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Transmitted on 100% recycled electrons