phantom file "aux" under bash b19

[Jason Zions]

> : Unfortunately, the magic meaning of those names is 
> hardcoded into Win32.
> : There's no way to avoid the problem if you use Win32 APIs, 
> which cygwin
> : does.
> 
> Really? Although I haven't tried it, several people already 
> wrote on this
> list that the workaround is using UNC \\.\ prefix!
> Sorry, I've no time for integrating that transparently into 
> cygwin DLL!

I believe you're correct. My guess is that the Win32 path-examination code
is skipped if Win32 determines the pathname uses UNC; this make sense, since
the interpretation of a UNC pathname must be left to the actual provider of
the resource. (That's how things like Dfs work.)

Does NT 3.51 fully support UNC naming? If not, I'd bet the \\.\ prefix
doesn't work.

Jason
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".