Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <004301c23afa$ad6afc60$0100a8c0@wdg.uk.ibm.com>
From: "Max Bowsher" <maxb AT ukf DOT net>
Cc: <cygwin AT cygwin DOT com>
References: <3D4B5AEF DOT 32421 DOT 3651B0CF AT localhost><1028370295 DOT 8690 DOT 117 DOT camel AT lifelesswks> <00b601c23ae5$209913e0$0100a8c0 AT wdg DOT uk DOT ibm DOT com> <1028377672 DOT 8690 DOT 120 DOT camel AT lifelesswks>
Subject: Re: Pathname context
Date: Sat, 3 Aug 2002 15:32:39 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

Robert Collins wrote:
> On Sat, 2002-08-03 at 21:41, Max Bowsher wrote:
>> I can see why this _is_ happening, but is this:
>>
>> max AT POMELLO [~] $ cygpath -wa c:/cygwin/usr/lib
>> C:\cygwin\lib
>>
>> actually what _should_ happen?
>>
>> Shouldn't a DOS-style path be taken as-is? I can understand the /usr/bin ->
>> /bin, /usr/lib -> /lib mappings, and have even added my own /usr/sbin ->
/sbin,
>> but, to me, a DOS-style path should taken literally.
>
> At a guess (check the source for an authoritative answer):
>
> c:/cygwin/usr/lib -> /usr/lib (based on / mount point)
> /usr/lib -> c:\cygwin\lib

Very believable... but I was proposing a change in behaviour so that DOS paths
refer to what they look like, and don't get redirected, on the grounds that if
that is what you type, then that is what you mean.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/