|
Scott, I don't believe you *can* use chroot from software that interacts
with the network filesystems (QSYS.LIB et al) as you suggest. How are you
doing that exactly?
You misread me. You mentioned that these packages like to install under
/usr/local. If you use chroot properly, you can (fairly easily) have the
package installed under /QOpenSys/usr/local...
I use symlink all the time; I have no problems with it per se. I do not
like it as a crutch to avoid something as simple as modifying the system
PATH.
I don't use it to appear to join unlike filesystems (tantamount to
installing all your software into a VFAT filesystem and making that part of
your PATH). I like a pure system (as much as possible). You're a purist
when it comes to your area of expertise; this is one of my strong areas.
You agreed (I think) that some of these programs won't run under QSH and yet
you install them under QSH because it's easier (that's the way I read your
post).
I am presenting an alternative that allows you to do it right,
keeping the Hatfields and McCoys on their own properties.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.