On Fri, Sep 02, 2005 at 11:14:57AM -0700, Bill Studenmund wrote:
> On Thu, Sep 01, 2005 at 10:19:15PM -0500, Eric Haszlakiewicz wrote:
> > 3) Directory within the /emul tree.  New getcwd acts differently.
> > 	3b) Non-emul processes passing paths into an emul-process should
> > 	    also work fine since the emul-process can use the /emul paths.
> > 	    If it does a chdir then a getcwd the paths will be different
> > 	    but that happens anyway if there's a symlink in the path.
> > 	    A program that explicitly looks for those symlinks might get
> > 	     confused, but I don't think that's very likely.
> > 	    This is the case that breaks currently with acroread b/c
> > 	     acroread does a chdir, getcwd, then uses that path to build
> > 	     a new path to the file.
> > 	    I believe this is also the case that affects realpath() when
> > 		 called with a relative path.
>
> Ok, I'm puzzled. What case did you actually make better?

	3b.  The getcwd change allow emul'd programs to use getcwd and
be able to build working paths.

eric