From: Egor Duda <deo@logos-m.ru>
To: Paul Stodghill <stodghil@cs.cornell.edu>
Cc: cygwin@sources.redhat.com
Subject: Re: Symlink'ed current directory and FIND
Date: Wed, 15 Nov 2000 07:20:00 -0000 [thread overview]
Message-ID: <3123725845.20001115181933@logos-m.ru> (raw)
In-Reply-To: <706871B20764CD449DB0E8E3D81C4D43CE8D17@opus.cs.cornell.edu>
Hi!
Wednesday, 15 November, 2000 Paul Stodghill stodghil@cs.cornell.edu wrote:
it's a feature :) i don't know if any standard says that linux
behavior is correct while cygwin isn't. it is possible (and imho
desirable too) to make cygwin work like linux in this case, but it
requires some changes in cygwin's path handling, and should be done
with appropriate care.
PS> Why doesn't FIND find files in the current directory when the current
PS> directory is accessed via a symlink?
PS> milhouse$ hash -r
PS> milhouse$ vdir -d a b
PS> drwxr-xr-x 2 stodghil None 0 Nov 15 09:03 a
PS> lrwxrwxrwx 1 stodghil None 12 Nov 15 09:02 b -> a
PS> milhouse$ cd a
PS> milhouse$ find -type f
PS> ./f1
PS> ./f2
PS> ./f3
PS> milhouse$ cd ../b
PS> milhouse$ find -type f
PS> milhouse$ ls
PS> f1 f2 f3
PS> milhouse$ type -p find
PS> /usr/bin/find
it's a feature :) i don't know if any standard says that linux
behavior is correct while cygwin isn't. it is possible (and imho
desirable too) to make cygwin work like linux in this case, but it
requires some changes in cygwin's path handling, and should be done
with appropriate care.
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-11-15 7:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 6:19 Paul Stodghill
2000-11-15 7:20 ` Egor Duda [this message]
2000-11-15 6:35 Earnie Boyd
2000-11-15 7:14 ` Lassi A. Tuura
2000-11-15 6:51 Paul Stodghill
2000-11-15 6:59 Earnie Boyd
2000-11-15 7:28 Earnie Boyd
2000-11-15 8:11 ` Christopher Faylor
2000-11-17 5:55 ` David Starks-Browning
2000-12-21 22:41 Philip Sainty
2000-12-22 1:06 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3123725845.20001115181933@logos-m.ru \
--to=deo@logos-m.ru \
--cc=cygwin@sources.redhat.com \
--cc=stodghil@cs.cornell.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).