Date: Thu, 11 Oct 2001 09:50:37 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: djgpp-workers AT delorie DOT com, tim DOT van DOT holder AT pandora DOT be
Subject: Re: First round of XP tests
In-Reply-To: <10110102128.AA17732@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.1011011095003.18580J-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 10 Oct 2001, Charles Sandmann wrote:

> For example, the new executable:
>  find . -name '*cvs*'
> does not find .cvsignore or .cvs but does find !.cvs (on NT 4.0 with lfn tsr).
> 
> I see the exact same behavior on Win2K.  Same behavior on XP RC1. I see the 
> same behavior with the simtel binary.  
> 
> I don't have any Win 9x systems to test on.  

I just did, and I see the same behavior.  Which is what I'd expect: by
default, files with the initial dot are not found by `find' (they are
``hidden'' in Unix, remember?).  You need to use -path instead of
-name to override that, or mention the dot explicitly, as in

   find -name '.*cvs*'

> What exactly is the expected behavior and which systems show it?

What you see is the expected behavior.  What Tim reported is something
strange, which is either a bug or due to real differences in file
names as recorded on disk.