From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <946860799ffc675cc795c4315cafbbbc@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] x10
From: rog@vitanuova.com
In-Reply-To: <2551C921.76D09E44@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Thu,  8 Apr 2004 21:42:25 +0100
Topicbox-Message-UUID: 56ebce82-eacd-11e9-9e20-41e7f4b1d025

the reason this is a problem in unix is the setuid bit.  various setuid
programs expect to see files (e.g./etc/passwd) in their expected
place.  if you can replace 'em, you can break the system.  hence
chroot is a superuser-only system call.

if you don't have setuid programs, it's not a problem.

as far as i can see, this was one of the major "too deep to fix"
problems with unix.