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: <38299073.4C14B820@ece.gatech.edu> Date: Wed, 10 Nov 1999 10:34:11 -0500 From: "Charles S. Wilson" X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "Halim, Salman" CC: "'David O'Riva'" , cygwin AT sourceware DOT cygnus DOT com Subject: Re: resolving symbolic links References: <512EBEF97F02D311B89900A0C9D1776009D598 AT thor DOT operations DOT bluestone DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Check out the code in "run". It's available from http://cygutils.netpedia.net/. While "run" does not do what you want, it contains code to recursively resolve symlinks and it shouldn't be too hard to adapt to your purposes. --Chuck "Halim, Salman" wrote: > > that turns /tmp into c:\tmp; i need it to turn into c:\temp, which is what > the actual directory is. basically, i would like to be able to call > non-cygwin programs from my command line with something like: > > runCommand ' /tmp/' and have it change the > /tmp to c:\temp and then run the command. but i need the link to be > resolved. > > regards, > > -- > ========================================================= > 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: David O'Riva [mailto:oriva AT agames DOT com] > > Sent: Wednesday, November 10, 1999 9:45 AM > > To: Halim, Salman > > Cc: cygwin AT sourceware DOT cygnus DOT com > > Subject: Re: resolving symbolic links > > > > > > "Halim, Salman" wrote: > > > > > > 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. . > > > > > > > Specifically for cygwin, you can use "cygpath -w /tmp". Very > > handy for > > using ancient editors ( function q { \q `cygpath -w $*` ; } ) > > > > -- > > -dave _________________________ > > ------------/ David O'Riva \-------------- > > 408- | Staff Software Engineer | oriva@ > > 473-9413 | Atari Games, Inc. | agames.com > > \_________________________/ > > > > -- > 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