public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: mapping root directory to SystemDrive / CurrentDrive
Date: Tue, 03 Aug 2004 11:50:00 -0000	[thread overview]
Message-ID: <20040803115006.GR31522@cygbert.vinschen.de> (raw)
In-Reply-To: <200408031317.20267.gernot.hillier@siemens.com>

On Aug  3 13:17, Gernot Hillier wrote:
> Hi Corinna!
> 
> Thx for your quick reply!
> 
> Am Dienstag, 3. August 2004 12:51 schrieb Corinna Vinschen:
> > > 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.  
> 
> Ok, so there's no easy way to switch to the old behaviour. Bad for us, but 
> well - our problem... :-(
> 
> But still there's one open question for me: are there plans to change the 
> behaviour of stat(), too?
> 
> Because I think it's not good when in such a situation open("/a/b") refers to 
> another file than stat("/a/b").

Actually it doesn't in the first place.  stat() tries to open the file first,
the same as when calling open().  But since the file doesn't exist, opening
it fails and stat() falls back to standard Win32 calls which treat the path
differently, as you observed.  If we wouldn't do that, another problem would
occur; stat() would fail in cases where it shouldn't.  Ok, there might be a
way to workaround that, but it would require somebody interested to patch it.
http://cygwin.com/acronyms/#PTC

> I can imagine quite some problems caused in Linux programs by such behaviour 
> of the system...

Keep in mind that this only happens if / isn't mounted -> back to undocumented
behaviour.

> > I'm sorry but we won't revert to Win32 calls just to keep an undocumented
> > behaviour running. 
> 
> Hmmm, is there any other way how one can use two different Cygwin 
> installations in parallel beside using no mounts?

I'm sorry, but that's generally not supported.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader          mailto:cygwin@cygwin.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/

  reply	other threads:[~2004-08-03 11:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 12:52 Gernot Hillier
2004-08-03 10:51 ` Corinna Vinschen
2004-08-03 11:17   ` Gernot Hillier
2004-08-03 11:50     ` Corinna Vinschen [this message]
2004-08-03 12:00       ` Gernot Hillier
2004-08-03 13:45         ` mapping root directory to SystemDrive / CurrentDrive (documentation change needed) Christopher Faylor
2004-12-27 18:09           ` Joshua Daniel Franklin
2004-12-27 21:08             ` Pierre A. Humblet
2004-12-28  0:13               ` Joshua Daniel Franklin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040803115006.GR31522@cygbert.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).