X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=sYfpx47InM09mSa3bUGW+M4jsmuIkV0Uv9sUPThoydsI7RxFx/2zX eGEZ+o7Ze22ZPBq4NltufFgUTWemR+6KC3ybzEQiR0g8Z8koXyEC0IFfN8mYvAao 8SUpuso+leEEwx81IxIPgK7IqJq60z7lILrKm8ViANTtpVLbqJLI9o= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=2Bufwd/T0TiLG3WI0Dyb0tb8nlY=; b=LfyTUMJ1FsJkvug02iFjY67wD6Zt 5/CL/1XS1ENFT4ranXy638n9oZMCjJsyBbgE9zeW1DhkoKoX3B25sU9+bcgtrL7u rtcze3/73Rg4ig0veihS0akPT/ruFBs9EqY8HLT10nYHGOVhV3zhepvhfnCxIeLV ii3nCm5cbcH4Efw= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 Date: Mon, 17 Jun 2013 17:15:27 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: UNC and POSIX paths Message-ID: <20130617151527.GA13457@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <003501ce6b5f$b41f2c10$1c5d8430$%fedin AT samsung DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <003501ce6b5f$b41f2c10$1c5d8430$%fedin@samsung.com> User-Agent: Mutt/1.5.21 (2010-09-15) On Jun 17 17:36, Fedin Pavel wrote: > Hello! > > 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 Resolution" (1): A pathname consisting of a single shall resolve to the root directory of the process. [...] If a pathname begins with two successive characters, the first component following the leading characters may be interpreted in an implementation-defined manner, although more than two leading characters shall be treated as a single character. Corinna (1) http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple