|
No, I don't see chroot as a useful solution to this. I frequently have
software that interacts with network file systems, the QSYS.LIB file
system, optical file systems... chroot would restrict access from
everything to /QOpenSys.
Not only that, but I use these tools from QShell as well as PASE..
QShell itself requires access to the root file system.
What is your problem with the symlink, exactly?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.