Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: symlink destination
- To: tlug@example.com
- Subject: Re: symlink destination
- From: John Seebach <jseebach@example.com>
- Date: Wed, 25 Oct 2000 14:41:14 -0400
- Content-Disposition: inline
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <14838.29947.837620.510820@example.com>; from vp@example.com on Wed, Oct 25, 2000 at 02:51:55PM +0900
- Mail-Followup-To: tlug@example.com
- References: <14838.29947.837620.510820@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <h6gS2B.A.h9B.4h195@example.com>
- Resent-Sender: tlug-request@example.com
- User-Agent: Mutt/1.2.4i-jp0
> A shell programming question: > > Is there a way to find out the destination of a symbolic link (the > file it links to) from a sh script? Parsing the output of `ls -l' is a > possibility but it doesn't feel right. Not part of any shell per se, but there's a tiny program called "chase" that does exactly this. Mine was included with my debian distribution, but you can probably find/download it somewhere (try ftp://ftp.jyu.fi/private/antkaij/ -- it's what was listed in the copyright documentation) If nothing else, you can download the source from debian.org. cheers, john -- ~ The moon a boat ~ the stars white waves john seebach ~ the clouds an ocean. jseebach@example.com ~ And the laurel man ~ rows all alone -- ~ how will he ever make his way? ~ -- Ryoujin Hishou --
- References:
- symlink destination
- From: Viktor Pavlenko <vp@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: NTT-ME was (Re: Metallic DSL in Tokyo)
- Next by Date: ZV port programming
- Prev by thread: Re: symlink destination
- Next by thread: nohup
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links