Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <512EBEF97F02D311B89900A0C9D1776009D597@thor.operations.bluestone.com>
From: "Halim, Salman" <salman AT bluestone DOT com>
To: "'Donald E. Hammond'" <dhammond AT nac DOT net>
Cc: "'cygwin AT sourceware DOT cygnus DOT com '" <cygwin AT sourceware DOT cygnus DOT com>
Subject: RE: resolving symbolic links
Date: Wed, 10 Nov 1999 09:32:14 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"

yes; ls -L just displays it as /tmp/ instead of /tmp@ :) not really
resolving it.

the find works for /tmp, but not for /tmp/<somefile> -- basically, %l
returns the empty string if the item in question isn't a symbolic link in
and of itself.  so /windows returns nothing.  what i'm looking for is
something that will resolve all symbolic links in a path name, leaving the
non-symbolic bits untouched.

thanks again :)

--
   =========================================================
   Salman Halim                 Advanced Technology Group   
                                                            
   Bluestone Software           Phone:  (856) 727-4600      
   1000 Briggs Rd.                       ext. 1085          
   Mt. Laurel, NJ 08054         Email:  salman AT bluestone DOT com
   =========================================================
   Would you  care for a drink?   I mean, if it  were, like,
   disabled and you had to look after it?


> -----Original Message-----
> From: Donald E. Hammond [mailto:dhammond AT nac DOT net]
> Sent: Wednesday, November 10, 1999 9:11 AM
> To: Halim, Salman
> Cc: 'cygwin AT sourceware DOT cygnus DOT com '
> Subject: Re: resolving symbolic links
> 
> 
> 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 AT sourceware DOT cygnus DOT com
> 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com