Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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: Thu, 23 Dec 2004 11:35:40 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: ls -F // doesn't work
Message-ID: <20041223103540.GF317@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <0I9500151DGUTZ AT pmismtp01 DOT mcilink DOT com> <cqd0tt$hgt$1 AT sea DOT gmane DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cqd0tt$hgt$1@sea.gmane.org>
User-Agent: Mutt/1.4.2i

On Dec 22 15:47, Andrew DeFaria wrote:
> Mark Paulus wrote:
> 
> >When I do an ls -F, I get expected results:
> >$ ls -F /
> >bin/ cygwin.bat* home/ run.groff tmp1/ xfer/
> >cron_diagnose.sh* cygwin.ico* lib/ sbin/ usr/
> >cygdeb/ etc/ mountem* tmp/ var/
> >
> >However, when I do ls -F //, then I get bad results:
> >$ ls -F //
> >ls: //bin: No such file or directory
> >ls: //cron_diagnose.sh: No such file or directory
> >[...]
> >wanted to mention it, as I am having 
> >another problem where rmdir() is not finding a file called 
> >"//usr/share/doc/cygwin-base/README". (should probably return ENOTDIR 
> >instead of ENOENT)
> 
> In general, in Cygwin, "//" == "\\" which introduces a UNC path. So, in 
> a Windows CMD a "pushd \\server\share" is equivalent to "pushd 
> //server/share" in a bash shell. Therefore a path of 
> //user/share/doc/cygwin-base/README is saying "I want the file on the 
> machine 'usr' under the share point of 'share' with a path of 
> 'doc/cygwin-base/' and a filename of 'README'". I doubt that you have a 
> machine named "usr" hanging around... ;-)

While you're right, it's not a good thing that ls // returns these
error messages.  I found a buglet in Cygwin which results in scanning
the root directory accidentally in this situation.  


Corinna

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

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/