This is the mail archive of the
mailing list for the Cygwin project.
Re: Re: Problems with find
- From: Randall R Schulz <rrschulz at cris dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 05 Feb 2003 08:53:38 -0800
- Subject: Re: Re: Problems with find
At 08:35 2003-02-05, email@example.com wrote:
firstname.lastname@example.org schrieb am 31.01.03 16:47:10:
What bug are you suggesting? There's a directory named "1000" and it
contains a file called "1000.zip". That's all very clear by what's
shown here. Perhaps this situation arose earlier in your confusion
about shell glob characters, find and whatnot.
> For the archives: No. This is not going to do what the OP wants at all.
> In fact, if there's more than one file named 1000.*, it won't even work
> (find will produce a "find: paths must precede expression" error). For
> details, "info find" and "info bash".
> To the OP: Is your 1000 directory a symbolic link, by any chance? If it
> is, try the "-follow" option. For details, "info find".
Thanks for the hint with -follow it worked, but the directory 1000 is
not a symbolic link as you can see
$ find . -name 1000\* -follow
$ ls -ld 1000
drwxr-xr-x 2 f.braunb unknown 0 Jan 31 08:33 1000
$ ls -l 1000*
-rw-r--r-- 1 f.braunb unknown 162114808 Jan 30 14:57 1000.zip
-rw-r--r-- 1 f.braunb unknown 162114808 Jan 31 08:33 1000.zip
Could this be a bug?
Sometimes in circumstances like this, confusion can be reduced by using
the "-i" option to ls. This will cause ls to include the "inode number"
in its output. (This is not quite the same thing in Cygwin as in real
Unix file systems, but it's there and serves the purpose of this hint.)
Distinct files that are otherwise identical and, beyond their full path
names, indistinguishable (same name, size, modes, owners, etc.) will
have different inode numbers. Likewise, hard links (possible with NTFS
but not FATn) will have identical inode numbers even if their names are
different. However, given that hard links are just multiple names for
the same file, it's impossible to have any other file attribute differ
between two hard links to the same file.
One last wrinkle to note is that if you attempt to create a hard link
on a FAT file system volume, Cygwin will copy the file for you. That's
its best-effort attempt to comply with a request that cannot literally
be fulfilled but which is nonetheless required by POSIX compliance.
(I'm presuming a bit here as to motivation for the fallback behavior
for hard linking on FAT file systems.)
> On Fri, 31 Jan 2003, Carlo Florendo wrote:
> > find . -name 1000.*
> > ----- Original Message -----
> > From: <email@example.com>
> > To: <firstname.lastname@example.org>
> > Sent: Friday, January 31, 2003 5:57 PM
> > Subject: Problems with find
> > Hi folks,
> > I trie to search file with find an didn't find all the file which
> > found
> > I search for all file starting with 1000 an the file 1000.zip in the
> > diretory 1000 is not found
> > $ find . -name 1000\*
> > ./1000.zip
> > ./1000
> > but when I ls the directory 1000 the file is listed
> > $ ls 1000
> > 1000.zip
> > As you can see I use the find installed in /usr/bin
> > $ which find
> > /usr/bin/find
> > $ type find
> > find is hashed (/usr/bin/find)
> > what is wrong? Is it a bug or my fault?
> > Thanks for any help and hint
> > Franz
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html