This is the mail archive of the
mailing list for the Cygwin project.
Re: UNC and POSIX paths
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 17 Jun 2013 17:15:27 +0200
- Subject: Re: UNC and POSIX paths
- References: <003501ce6b5f$b41f2c10$1c5d8430$%fedin at samsung dot com>
- Reply-to: cygwin at cygwin dot com
On Jun 17 17:36, Fedin Pavel wrote:
> I decided to pay attention to one more problem. Lots of not very well
> written configure scripts and makefiles like to access things like
> '//usr/bin'. Under Cygwin this causes problem because Cygwin treats '//' in
> Windows-style as access to network shares.
> What if we change this ? We could have a mount entry, something like '/unc'
> (or /smb, /net, whatever) and access it like '/smb/computername/sharename'.
> I think this would improve POSIX compatibility a lot.
Maybe there has been said enough in this thread already, but I have
to add this: Cygwin's behaviour *is* POSIX compatible. Consider
this excerpt from SUSv4 Base specifications, section 4.12 "Pathname
A pathname consisting of a single <slash> shall resolve to the root
directory of the process. [...] If a pathname begins with two
successive <slash> characters, the first component following the
leading <slash> characters may be interpreted in an
implementation-defined manner, although more than two leading <slash>
characters shall be treated as a single <slash> character.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple