Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Tue, 15 Oct 2002 15:48:10 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: paths like //usr/local Message-ID: <20021015194810.GA14116@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20021015181721 DOT GB11463 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i On Tue, Oct 15, 2002 at 09:09:27PM +0200, Sven K?hler wrote: >>>a path like //usr/local is treated as an UNC path. >>>this might leads to problems when an application is using //usr/local as >>>a normal "unix"-path. >>> >>>i don't know how to overcome the problem, but one might think of a path >>>like /unc/computer/share instead of using the path //computer/share >>> >>>what was the idea behind the current behaviour? >> >>Do you think that Microsoft employees read this mailing list? I'm sure >>that there are one or two but I doubt that they could speak definitively >>about why Microsoft chose this behavior. > >cygwin translates paths like /usr/local to c:\cygwin\usr\local and >manages mount-points etc... >cygwin opffers a complete "virtual filesystem" > >the cygwin-developers chose, to NOT convert //usr/local to >c:\cygwin\usr\local > >i would like to know why. Think of it another way: cygwin allows the user to specify paths like: c:\foo\bar and c:/foo/bar. Similarly, it allows //foo/bar and \\foo\bar . If that doesn't satisfy you then you can go back to the "Because we're mean" argument. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/