From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] libbio and large files
Date: Thu, 15 May 2008 08:30:19 -0500 [thread overview]
Message-ID: <47FD9EF1-7EE5-4624-8FE7-55F5BA21184A@corpus-callosum.com> (raw)
This question may be more applicable when addressing p9p on other
systems:
I'm seeking a little clarification about Bopen and reading through
files larger than (2^31 bytes). Other host systems where p9p works
(very well I might add) tend to have different definitions for off_t
depending on 32/64 bit support (some require off64_t while others do
contortions around redefining off_t depending on the joy of compiler
flags, both leading to other incantations that may require
orthodontia), how does one go about ensuring that their host OS does
properly access large files properly when using libbio?
Also--shouldn't binit.c:125 in p9p be updated to the changes found on
sources?
cpu % history -D binit.c
...
/n/sourcesdump/2008/0430/plan9/sys/src/libbio/binit.c:108 c /n/
sourcesdump/2005/0829/plan9/sys/src/libbio/binit.c:108
< f = open(name, mode);
---
> f = open(name, OREAD);
...
-jas
next reply other threads:[~2008-05-15 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 13:30 Jeff Sickel [this message]
2008-05-19 19:22 ` Russ Cox
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=47FD9EF1-7EE5-4624-8FE7-55F5BA21184A@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.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 NNTP newsgroup(s).