From: David Brown <caml-list@davidb.org>
To: Ian Zimmerman <itz@buug.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] stat in Unix library
Date: Sun, 28 Nov 2004 22:18:05 -0800 [thread overview]
Message-ID: <20041129061805.GA18644@old.davidb.org> (raw)
In-Reply-To: <87y8glecwv.fsf@buug.org>
On Sun, Nov 28, 2004 at 04:06:56PM -0800, Ian Zimmerman wrote:
> The st_dev member of type Unix.stats is declared as int. But according
> to the Single Unix spec, the corresponding member of the C struct has
> a defined type, dev_t; and in fact recent Linux kernels define dev_t
> to a 64 bit type, even on 32 bit architectures. So it looks like
> the Ocaml function will lose the high order bits.
st_ino as an in is a more damning problem. Linux, with XFS can easily have
inode numbers that exceed a 32-bit integer (especially a 31-bit integer).
Practically, on Linux, st_dev is still only using 16-bits on Linux, but
people are still trying to increase that.
Unix.LargeFile almost fixes everything, except for the st_dev, st_rdev, and
st_ino fields still being too small. Increase those, and I would stop
having to put my own bindings to lstat in my programs :-)
Dave
prev parent reply other threads:[~2004-11-29 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 0:06 Ian Zimmerman
2004-11-29 6:18 ` David Brown [this message]
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=20041129061805.GA18644@old.davidb.org \
--to=caml-list@davidb.org \
--cc=caml-list@inria.fr \
--cc=itz@buug.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 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 NNTP newsgroup(s).