From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <9710121843.AA16640@clio.rice.edu>
Subject: Re: Should off_t become unsigned?
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Sun, 12 Oct 1997 13:43:09 -0600 (CDT)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.971012192522.9526A-100000@is> from "Eli Zaretskii" at Oct 12, 97 07:26:49 pm
Content-Type: text
Precedence: bulk

> So it means that DJGPP won't support files larger than 2GB on FAT32 
> volumes.  Or am I missing anything?

I think the need for files > 2Gb on a DJGPP program is very limited.
About the only thing I know of which would use something this large 
would be a database.  Let's suppose someone really needs this database.
They are forced to compile with -DUSE_64BIT_OFF_T (or something) which
defines lseek to be lseek64, other routines to be consistent.  Or maybe
this is in an alternate libc if there are a bunch of routines changed.

In any case I wouldn't mess with the current working sizing/behavior.
And I would wait for the first screams of agony about missing 2.1Gb
file support before coding something...