On Wed, 2002-10-16 at 07:44, Philippe Troin wrote:
> > Is there a reason besides standards compliance that chroot() does not
> > already change directory to the chroot'd directory for root processes?
> > Would it actually break existing apps if it did change the directory?
>
> Probably not. Make that: change the directory to chroot'd directory if
> the current working directory is outside the chroot. That is, leave
> the cwd alone if it is already inside the chroot.
Last time it was tried real apps broke.
chroot is not jail chroot is not a sandbox. Do the job right (eg the
vroot work) and it'll get a lot further
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:00:54 EST