All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Padraig Brady <Padraig@AnteFacto.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Documenting stat(2)
Date: 19 Jan 2001 11:18:56 +0100	[thread overview]
Message-ID: <jer91zsv3j.fsf@hawking.suse.de> (raw)
In-Reply-To: <20010118020528.A16871@jhereg.dmeyer.net> <3A66D93C.8090500@AnteFacto.com>
In-Reply-To: <3A66D93C.8090500@AnteFacto.com>

Padraig Brady <Padraig@AnteFacto.com> writes:

|> dmeyer@dmeyer.net wrote:
|> 
|> > In article <9463fj$gsq$1@penguin.transmeta.com> you write:
|> >
|> >> Basically, the _only_ think you should depend on is that st_size
|> >> contains:
|> >>  - for regular files, the size of the file in bytes
|> >>  - for symlinks, the length of the symlink.
|> > I don't think this is right - for a symlink, stat should return the
|> > size of the file; lstat should return the size of the symlink.
|> 
|> Nope stat should return the details of the symlink
|> whereas lstat should return the details of the symlink target.

Nope, check the facts.

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-19 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-18  7:05 Documenting stat(2) dmeyer
2001-01-18 11:53 ` Padraig Brady
2001-01-18 15:54   ` dmeyer
2001-01-18 20:52   ` Igmar Palsenberg
2001-01-19  1:00     ` Mike Castle
2001-01-20 19:39       ` Igmar Palsenberg
2001-01-19 10:18   ` Andreas Schwab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-18  5:28 Eric S. Raymond
2001-01-18  6:46 ` Linus Torvalds
2001-01-18 12:56 ` Felix von Leitner

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=jer91zsv3j.fsf@hawking.suse.de \
    --to=schwab@suse.de \
    --cc=Padraig@AnteFacto.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.