Date: Sun, 28 Feb 1999 14:15:56 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT usa DOT net>
cc: djgpp-workers AT delorie DOT com
Subject: Re: updated chroot
In-Reply-To: <199902252259.WAA06048@out4.ibm.net>
Message-ID: <Pine.SUN.3.91.990228141534.5950N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com


On Thu, 25 Feb 1999, Mark E. wrote:

> > Static/global variables like these that cache information need to be
> > reinitialized if the program is restarted (like Emacs, after it dumps its
> > own image). 
> 
> I don't understand why. If the startup routine is modified to read the 
> environmental variables produced by chroot and then call chroot, then 
> wouldn't these variables be taken care of during a restart?

If the code in the startup initializes these static variables, even in
the case that SYSROOT (or whatever it will be called) is not defined,
then that's an alternative solution.