All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Problems with /proc/mounts and statvfs (implementing df).
Date: Sat, 28 Oct 2006 16:28:58 -0400	[thread overview]
Message-ID: <200610281628.58174.rob@landley.net> (raw)
In-Reply-To: <200610281537.07145.rob@landley.net>

On Saturday 28 October 2006 3:37 pm, Rob Landley wrote:
> Problem #2: statfs() and statvfs() are returning 0 in the f_fsid.

Which is apparently a known issue, the field has never worked and is useless, 
and what you're supposed to do is a normal stat() on the sucker and and use 
st_dev, which has been horribly abused to perform the function of uniquely 
identifying things like tmpfs instances and /proc. :)

A fix to problem #1 would still be nice, but I can work around most of it...

Thanks,

Rob
-- 
"Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away." - Antoine de Saint-Exupery

  reply	other threads:[~2006-10-28 20:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-28 19:37 Problems with /proc/mounts and statvfs (implementing df) Rob Landley
2006-10-28 20:28 ` Rob Landley [this message]
2006-11-02 10:07 ` Ian Kent
2006-11-02 20:53   ` Rob Landley

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=200610281628.58174.rob@landley.net \
    --to=rob@landley.net \
    --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.