site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Sep 19, 2006, at 15:14 , David Hoerl wrote: Here is what I did to test this: $ cd /tmp $ cat > goop hello world $ ln -s /tmp/goop /tmp/foop $ file foop foop: symbolic link to `/tmp/goop' $ ls -L foop foop $ ls -L goop goop The same thing happens with hard links. For symlinks, you find the linked-to file by "ls -l", for example.\ $ ls -l foop lrwxr-xr-x 1 justin wheel 9 Sep 19 18:59 foop -> /tmp/goop Regards, Justin -- Justin C. Walker, Curmudgeon-at-Large () The ASCII Ribbon Campaign /\ Help Cure HTML Email _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I recently had cause to try and use "ls -L file" to find the linked file. Its not working (I wanted to use the return string in a shell program). Is this a known problem (ie should I create a bug report on it)? It's not a bug; it is the way links work. A link between files lets you reference the second (linked-to) file by the name of the first (linked from) file. This isn't shell-specific, since it's "ls" that is doing the work. The shell dutifully passes 'foop' to "ls". This email sent to site_archiver@lists.apple.com