Date:	Wed, 1 Apr 1998 11:31:05 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Martin Strömberg <martin DOT stromberg AT lu DOT erisoft DOT se>
cc:	DJGPP-WORKERS <djgpp-workers AT delorie DOT com>, DJ Delorie <dj AT delorie DOT com>
Subject:	Re: Where to get the latest sources for djtar
In-Reply-To:	<199804010130.DAA25229@father.ludd.luth.se>
Message-ID:	<Pine.SUN.3.91.980401113037.2919P-100000@is>
MIME-Version:	1.0

On Wed, 1 Apr 1998, Martin Str|mberg wrote:

> Good work, Eli!

Thanks.

> Your last proposed patch regarding djtar corrects the problems I've
> stumbled into.

Great!

DJ, do you need me to resend you the final patch (cc:'ed to workers a
few days ago), you do you have it already?

> kant:~> grep NOSPC /DOS/d/tmp/djlib/djlib202/src/utils/djtar/*.c
> /DOS/d/tmp/djlib/djlib202/src/utils/djtar/epunzip.c:    errno = ENOSPC;
> /DOS/d/tmp/djlib/djlib202/src/utils/djtar/untar.c:          errno = ENOSPC;
> /DOS/d/tmp/djlib/djlib202/src/utils/djtar/untar.c:    if (write_errno == ENOSPC)  /* target disk full: quit early */

This is because whoever wrote those parts didn't trust the DJGPP
library ;-).  (Or maybe it's a left-over from v1.x or early v2.0
days.)  Current versions of `write' set	`errno' to ENOSPC
automatically.

> And if you examine the output of djtar you see a printout about NOSPC
> scrolling past, when the disk becomes full. Alas, it scrolls past
> very fast because of a huge amount of EBADF or something similar.
> Perhaps there's another bug lurking somewhere?

What is the case where you see EBADF errors?  Is that with the
original djtar, before the patches in the last alpha release?  If not,
I'd like to know hoe to reproduce that problem.

- Raw text -