Re: chroot, Doctrine, ZendFrameWork

Thanks, Pete - and others who responded. I think I have a better
understanding of chroot now. In addition to reading the responses and
following the links in this thread, I have reviewed other resources on the
Internet as well.

The mechanics of limiting and granting authorities under IBM i are
significantly different than *nix environments, but I understand the
overall objective of restricting users and protecting "system" objects is
the same.

If I understand correctly, the idea is more than just restricting a user's
"command line access" to the "root" directory. The idea is to use "scripts"
to copy *nix binaries (executables) and data objects to user directories to
create a sand-boxed runtime environment for the user. That's kind of like
creating a VM at AWS from an "image"; Of course there are differences too.

As a follow-up to Vern's question regarding access to /qsys.lib; Without a
chroot setup, would users of the *SSHD daemon be able to access /qsys.lib/*
objects otherwise, from remote *nix shells?