From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10109261543.AA19758@clio.rice.edu>
Subject:	Re: fixpath patch (fixes rm -rf disaster, retains deep directory usage)
To:	eliz AT is DOT elta DOT co DOT il
Date:	Wed, 26 Sep 2001 10:43:59 -0500 (CDT)
Cc:	djgpp-workers AT delorie DOT com
In-Reply-To:	<6480-Wed26Sep2001103457+0300-eliz@is.elta.co.il> from "Eli Zaretskii" at Sep 26, 2001 10:34:58 AM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> > Here's an alternative patch which also seems to work on Win2K.  It allows
> > you to use long directories without any problems I've observed.  It's a
> > quick change to fixpath (which is called a bunch of places) to not call
> > getcwd and use truename instead.
> 
> We cannot simply replace getcwd with _truename here: _truename returns
> a UNC for directories on networked drives, and some DOS calls on some
> supported systems, notably on plain DOS, don't support UNC's.
> 
> _fixpath uses getcwd precisely for this reason.

Please help me figure out which we should use when.  getcwd is the problem
here for both Win2K and long paths with LFN=n  - and this fixes that 
problem.  Since getcwd has it's limits, it breaks things that don't need
to be broken.  Why do we have to convert to absolute paths?

- Raw text -