This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch] To handle Win32 pipe names

From: Corinna Vinschen <vinschen at redhat dot com>
To: cygwin-patches at cygwin dot com
Date: Wed, 19 May 2004 17:46:45 +0200
Subject: Re: [Patch] To handle Win32 pipe names
References: <BAY9-F265VSSFcl3imp0000784b@hotmail.com> <20040519085237.GA7011@cygbert.vinschen.de> <Pine.CYG.4.58.0405190959550.2628@fordpc.vss.fsi.com>
Reply-to: cygwin-patches at cygwin dot com

On May 19 10:08, Brian Ford wrote:
> On Wed, 19 May 2004, Corinna Vinschen wrote:
> 
> > So that explains your patch to symlink_info::check.  But it's not
> > exactly right to circumvent this only for pipes.  Any \\.\foo path
> > should get the same handling.  Wouldn't it be more straightforward to
> > use is_unc_share or a slightly modified version of is_unc_share?
> 
> I'm confused here.  Are you suggesting that UNC paths can't contain
> symlinks?

No.  It should be short-circuited for //./foo and //server/pipe/foo,
not for any other UNC path.


Corinna

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

References:
- [Patch] To handle Win32 pipe names
  - From: Stephen Cleary
- Re: [Patch] To handle Win32 pipe names
  - From: Corinna Vinschen
- Re: [Patch] To handle Win32 pipe names
  - From: Brian Ford

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]