public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: (Jerry Heyman) <jerry@dev.tivoli.com>
To: cygwin@cygwin.com, "jorgens@coho.net" <jorgens@coho.net>
Subject: Re: Problem dereferencing with ls -L
Date: Tue, 17 Jul 2001 14:15:00 -0000	[thread overview]
Message-ID: <200107172115.QAA11712@devmail.dev.tivoli.com> (raw)
In-Reply-To: <01C10EC9.18AEAA80.jorgens@coho.net>

On 17 July 2001 at 14:02, Steve Jorgensen <jorgens@coho.net> wrote:
> When I run ls -L /usr/bin/awk, I get /usr/bin/awk.  Similarly, if I enter 
> ls -L /usr/bin/awk.exe, I get /usr/bin/awk.exe.  If, however, I enter ls -l 
> /usr/bin/awk, it tells me that /usr/bin/awk -> gawk.exe.  Why doesn't ls -L 
> show me the dereferenced file info?

Unless I misunderstand the question, the -L flag says follow any
symlinks and show me the file that I've requested.  Which means that
if foo is symlinked to bar and you do an:

ls -L foo

You will see foo on the output

-l is the long listing and if its a symlink will tell you what the
link is pointing to.  If you do:

ls -lL /usr/bin/*awk*

You should see all the different names for awk in the directory and
their size/date will all be the same, because they are actually giving
you the size of the same file.

jerry
-- 
Jerry Heyman   919.224.1442    | Tivoli Systems       |"Software is the 
Build Infrastructure Architect | 3901 S Miami Blvd    | difference between
Jerry.Heyman@tivoli.com        | Durham, NC  27703    | hardware and reality"
                          http://www.acm.org/~heymanj



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2001-07-17 14:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-17 13:53 Steve Jorgensen
2001-07-17 14:15 ` jerry [this message]
2001-07-18 11:41 Steve Jorgensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200107172115.QAA11712@devmail.dev.tivoli.com \
    --to=jerry@dev.tivoli.com \
    --cc=cygwin@cygwin.com \
    --cc=jorgens@coho.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).