Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <38297D07.3057A44F@nac.net> Date: Wed, 10 Nov 1999 09:11:19 -0500 From: "Donald E. Hammond" X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: "Halim, Salman" CC: "'cygwin AT sourceware DOT cygnus DOT com '" Subject: Re: resolving symbolic links References: <512EBEF97F02D311B89900A0C9D1776009D590 AT thor DOT operations DOT bluestone DOT 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 AT sourceware DOT cygnus DOT com