Date: Wed, 8 Aug 2001 09:57:15 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Paul Eggert <eggert AT twinsun DOT com>
cc: rich AT phekda DOT freeserve DOT co DOT uk, jim AT meyering DOT net, djgpp-workers AT delorie DOT com
Subject: Re: GNU ls bug on DJGPP with large files
In-Reply-To: <200108071753.f77HrOI08852@shade.twinsun.com>
Message-ID: <Pine.SUN.3.91.1010808095610.23412D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 7 Aug 2001, Paul Eggert wrote:

> Patching GNU 'ls' is a band-aid.  The patch will cause GNU 'ls' to do
> the right thing for files between 2 GB and 4 GB, but files larger than
> 4 GB will still be mishandled.  So DJGPP really needs to get fixed.

FAT32 volumes don't support files larger than 4GB anyway, at least for
the system calls that DJGPP programs can use (it's basically the same
32-bit interface, they just use 32-bit unsigned values instead of
signed values).  Introducing a new large-file feature, and a
compile-time feature on top of that (which means you need 2 versions
of every library and elaborate configury stuff to choose the right one
when you build packages)--to me this sounds like using a sledgehammer
where a simple, if somewhat kludgey, type-cast in a single program would 
have put this issue to rest.