Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-ID: <38297D07.3057A44F@nac.net>
Date: Wed, 10 Nov 1999 09:11:19 -0500
From: "Donald E. Hammond" <dhammond@nac.net>
MIME-Version: 1.0
To: "Halim, Salman" <salman@bluestone.com>
CC: "'cygwin@sourceware.cygnus.com '" <cygwin@sourceware.cygnus.com>
Subject: Re: resolving symbolic links
References: <512EBEF97F02D311B89900A0C9D1776009D590@thor.operations.bluestone.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Salman -

ls -L should work, I think, but doesn't seem to in my 1.0 CD
installation.  Don't know if it's a bug, or misunderstanding on my
part.  Try: 'find /tmp -printf %l'  (or -printf "%l\n"), which seems to
work.

Hope that helps.

 - Don


Halim, Salman wrote:
> 
> hi,
> 
> what's a good way to find out (programmatically; either through a command or
> a piped series of commands or a function), in bash (if relevant), the actual
> path pointed to by a symbolic link.  for example, i have /tmp pointing to
> c:\temp -- how can i get 'c:\temp' as output given '/tmp' as input?  i
> thought of ls -al /tmp | cut -d'>' -f 2- but that seems a bit of a kludge. .
> .
>

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com