RE: qopensys etc.

["Dennis Lovelady" <iseries@xxxxxxxxxxxx>]

> There was a licpgm (Zend server, perhaps?) that wouldn't install
> properly if one or the other was a symlink.  Now I can't remember which
> way caused the problem...    but it failed to install to a symlinked
> directory, so you had to do the link in the other direction.
>
> It was annoying.

Yes, don't you love it when program products decide their own standards for
the way YOUR system should be set up?!?!

Well, unless Zend server (or whatever it was) has been made i-aware, it
wouldn't know about /QOpenSys.  So perhaps that tells us which symlink was a
problem.  Would that imply that it's safest to create /usr/local as a
directory, and /QOpenSys/usr/local as a symlink to that?  Then (worst case)
only i-specific programs might fail for this cause.  Something to ponder,
perhaps.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Guidelines for Bureaucrats:
 (1) When in charge ponder.
 (2) When in trouble delegate.
 (3) When in doubt mumble."
        -- James H. Boren