mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: root@chaos.analogic.com, Matti Aarnio <matti.aarnio@zmailer.org>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Large files
Date: Tue, 10 Jun 2003 18:12:50 -0400	[thread overview]
Message-ID: <200306101812.50632.rob@landley.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0306101057020.4326@chaos>

On Tuesday 10 June 2003 11:12, Richard B. Johnson wrote:
> On Tue, 10 Jun 2003, Matti Aarnio wrote:
> > On Tue, Jun 10, 2003 at 09:57:57AM -0400, Richard B. Johnson wrote:
> > > With 32 bit return values, ix86 Linux has a file-size limitation
> > > which is currently about 0x7fffffff. Unfortunately, instead of
> > > returning from a write() with a -1 and errno being set, so that
> > > a program can do something about it, write() executes a signal(25)
> > > which kills the task even if trapped. Is this one of those <expletive
> > > deleted> POSIX requirements or is somebody going to fix it?
> >
> >   http://www.sas.com/standards/large.file/

Is anybody indexing these suckers?  I've got a directory full of downloaded 
PDFs of things like the el-torito spec and bits of posix and sus, and I was 
just wondering if there's some kind of master list of all these things that 
Linux actually implements.

I suspect the answer is "probably not", but i thought I'd ask...

Rob

Rob

  parent reply	other threads:[~2003-06-10 21:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-10 13:57 Richard B. Johnson
2003-06-10 14:16 ` ZCane, Ed (Test Purposes)
2003-06-10 14:17 ` Matti Aarnio
2003-06-10 15:12   ` Richard B. Johnson
2003-06-10 17:25     ` Martin Mares
2003-06-10 18:14     ` Andreas Dilger
2003-06-10 22:12     ` Rob Landley [this message]
2003-06-10 20:14 ` David Schwartz
2003-06-10 20:31   ` Richard B. Johnson
2003-06-10 22:38 Ray Lee

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=200306101812.50632.rob@landley.net \
    --to=rob@landley.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.aarnio@zmailer.org \
    --cc=root@chaos.analogic.com \
    /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

all inboxes | Powered by JetHome®