Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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: Tue, 3 Aug 2004 12:51:43 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: mapping root directory to SystemDrive / CurrentDrive
Message-ID: <20040803105143.GQ31522@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <200408021452 DOT 34000 DOT gernot DOT hillier AT siemens DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200408021452.34000.gernot.hillier@siemens.com>
User-Agent: Mutt/1.4.2i

On Aug  2 14:52, Gernot Hillier wrote:
> Hi!
> 
> We use some Cygwin tools without Cygwin mounts. The reason for this is (was) 
> that we use several Cygwin versions from different network shares in parallel 
> (i.e. we have different \Cygwin trees on different drives on our Windows 
> hosts).
> 
> With earlier Cygwin versions, this worked without any problem as Cygwin always 
> mapped "/" to the CurrentDrive (not the SystemDrive, as it is documented in 
> http://www.cygwin.com/cygwin-ug-net/using.html). With the current Cygwin 
> version, this seems to be mixed: the open() call seems to map "/" to the 
> SystemDrive while stat() maps "/" to the current drive.
> 
> I can certainly understand that it was our fault to rely on something which 
> was not documented. Nevertheless, this was a real nice workaround for us to 
> be able to use different Cygwin tools based on different Cygwin trees easily 
> (it was even possible to let them run in parallel).
> 
> And anyway, I assume that it is a bug that both system calls behave different, 
> right?

That's a result of using NtCreateFile instead of CreateFile.  Native NT
calls behave slightly different than Win32 calls.  However, as you said,
you're relying on undocumented behaviour.  I'm sorry but we won't revert
to Win32 calls just to keep an undocumented behaviour running.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/