Date:	Wed, 8 Aug 2001 17:47:06 +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, djgpp-workers AT delorie DOT com
Subject:	Re: GNU ls bug on DJGPP with large files
In-Reply-To:	<200108081427.f78ER1m28155@sic.twinsun.com>
Message-ID:	<Pine.SUN.3.91.1010808174034.27069A-100000@is>
MIME-Version:	1.0
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

On Wed, 8 Aug 2001, Paul Eggert wrote:

> > Date: Wed, 8 Aug 2001 09:57:15 +0300 (IDT)
> > From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
> > 
> > FAT32 volumes don't support files larger than 4GB anyway, at least for
> > the system calls that DJGPP programs can use
> 
> That sounds like a real problem to me.  I regularly deal with files
> larger than that these days.

What can we do? DJGPP doesn't include the OS, it uses the system calls 
available from the underlying OS.  There simply isn't a system call that 
can support files larger than 4GB - 2 bytes.  So we cannot support larger 
files.

> DJGPP can't deal with disk files that cost only $8?

DJGPP is free, so $8 files are too expensive for us ;-)

> The patch doesn't fix the problem for
> gzip, tar, find, or any of the dozens of other programs that have to
> deal with large files in normal use.

It's possible that more programs are affected, but each case should be 
examined individually.  The only programs which will have problems like 
`ls' are those which print the value of st_size.  Programs that store 
the values only to pass them to some system call later will not be 
affected.

- Raw text -