From: Martin Stromberg <Martin DOT Stromberg AT lu DOT erisoft DOT se>
Message-Id: <199804020852.KAA20190@propus.lu.erisoft.se>
Subject: Re: Where to get the latest sources for djtar
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Thu, 2 Apr 1998 10:52:44 +0200 (MET DST)
Cc: djgpp-workers AT delorie DOT com (DJGPP-WORKERS)
In-Reply-To: <Pine.SUN.3.91.980401113037.2919P-100000@is> from "Eli Zaretskii" at Apr 1, 98 11:31:05 am
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

> > 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.

No it's the latest with your latest patch. I don't remember if I saw them 
with the original djtar; that's possible.

Well, the setup is something like you have a large tar.gz file (like the
linux kernel source), it will fill up the disk while untarring and you
do the "djtar -x" three or four directory levels down (like your are in
/a/b/c/d when you do "djtar -x").

I'll pipe a run to a file and mail it to you Eli if you want.


Right,

							MartinS