Message-Id: <199902252259.WAA06048@out4.ibm.net>
From: "Mark E." <snowball3 AT usa DOT net>
To: djgpp-workers AT delorie DOT com
Date: Thu, 25 Feb 1999 17:59:28 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: updated chroot
References: <199902250602 DOT GAA34258 AT out1 DOT ibm DOT net>
In-reply-to: <Pine.SUN.3.91.990225150526.19118A-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.01d)
Reply-To: djgpp-workers AT delorie DOT com

> 
> On Thu, 25 Feb 1999, Mark E. wrote:
> 
> > char __djgpp_root [PATH_MAX+1] = { '\0' };
> > int __djgpp_root_len = 0;
> > unsigned int __chroot_flags = __CHROOT_UNIX_EMU_FLAG;
> 
> 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?

Mark

--- 
Mark Elbrecht
snowball3 AT usa DOT net http://members.xoom.com/snowball3/