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
Date: Sun, 2 Jun 2002 12:54:49 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: problem with handle_to_fn ?
Message-ID: <20020602165449.GA13484@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <002f01c20a20$0064c330$0100a8c0 AT advent02>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002f01c20a20$0064c330$0100a8c0@advent02>
User-Agent: Mutt/1.3.23.1i

On Sun, Jun 02, 2002 at 11:26:47AM +0100, Chris January wrote:
>With the recent changes in grabbing the path of a file from its open file
>handle I'm seeing the following:
>Initially the path is as follows:
>\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\......
>but later it gets translated to:
>/cygdrive/c/Device/HarddiskDmVolumes/PhysicalDmVolumes/BlockVolume1/...
>which then gets translated back to:
>c:\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\....
>which AFAIK is an invalid path...

Even if this function fails, the net result should be no different than
what cygwin used to do.  It always used an invalid path in that scenario.

Are you actually seeing failures related to this?

cgf

--
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/