Date: Sun, 14 Mar 1999 10:47:07 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: DJ Delorie <dj AT delorie DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: chroot patches v4
In-Reply-To: <199903121459.JAA14040@envy.delorie.com>
Message-ID: <Pine.SUN.3.91.990314104649.18100E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Fri, 12 Mar 1999, DJ Delorie wrote:

> Please, someone remind me why djgpp needs chroot.

It began when Alain Magloire said that inetutils need that (e.g., so
that the ftp client would not be able to access files outside ~ftp).

It is also a handy way to implement the DJGPP-specific Bash feature
whereby setting SYSROOT=c:/foo/bar/djgpp will cause hard-coded paths
like /bin/rm to magically work.

In the port of Bash 1.14.7, this feature requires Bash itself to
convert the file names back to their normal full form, since the
programs run by Bash don't know about SYSROOT.  And Bash has hard time
doing this correctly, because /bin/rm might not be a pathname, but a
string (e.g. in a Sed script).  Supporting this automatically in the
library is much better (IMHO).