From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: large file support?
Date: Thu, 31 Jul 2003 13:58:28 +0200 [thread overview]
Message-ID: <3F290464.7030902@imc-berlin.de> (raw)
In-Reply-To: <20030731113724.CB20BC602D@atlas.denx.de>
Wolfgang Denk wrote:
> In message <3F28EFD6.3070803@imc-berlin.de> you wrote:
>
>>how could I find out if the kernel and the glibc I am using will
>>correctly supprot large files (>2GB)?
>
>
> char buf[4096];
> for (;;)
> write (fd, buf, sizeof(buf));
>
:o)
But what will happen if I (or my application) have no large file
support, i.e. is the failure deterministic? And will it be obvious?
Just by do "ls -l"????
:-)
Thanks anyway!
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-31 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 10:30 large file support? Steven Scholz
2003-07-31 11:37 ` Wolfgang Denk
2003-07-31 11:58 ` Steven Scholz [this message]
2003-07-31 12:01 ` Steven Scholz
2003-07-31 12:50 ` Wolfgang Denk
2003-07-31 12:59 ` Steven Scholz
2003-07-31 14:30 ` Steven Scholz
[not found] <00001C9A.C22236@denx.de>
2003-07-31 13:00 ` Jerry Van Baren
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=3F290464.7030902@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linuxppc-embedded@lists.linuxppc.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).