From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id: <199804010130.DAA25229@father.ludd.luth.se>
Subject: Re: Where to get the latest sources for djtar
To: djgpp-workers AT delorie DOT com (DJGPP-WORKERS)
Date: Wed, 1 Apr 1998 03:30:38 +0200 (MET DST)
Cc: eliz AT is DOT elta DOT co DOT il
Reply-To: martin DOT stromberg AT lu DOT erisoft DOT se (Martin Strömberg)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

Good work, Eli!

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

I happened to see signs of that there is some support for full disk
error handling in djtar 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 */

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?


Thanks,

							MartinS