Date: Fri, 14 Sep 2001 12:53:57 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-Id: <1190-Fri14Sep2001125357+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
In-reply-to: <4634-Fri14Sep2001114751+0300-eliz@is.elta.co.il>
Subject: Re: A new W2K problem: djtar
References:  <4634-Fri14Sep2001114751+0300-eliz AT is DOT elta DOT co DOT il>
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

> Date: Fri, 14 Sep 2001 11:47:52 +0300
> From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
> 
> There seems to be a new problem with W2K: djtar prints error messages
> about EBADF when  run on a .tar.gz archive.  I'm trying to debug this.

I found the reason for this.  Sigh...

First, my memory failed me: the problem is not with .tar.gz files,
it's with .zip files only.  To reproduce, try "djtar djdev203.zip".

The problem is that epunzip.c open()'s /dev/null, which is converted
by _put_path to just "nul", and that somehow fails.  Charles, didn't
you say that opening "nul" does work on W2K?

I can work around this problem in epunzip.c, but I'd like to look
closer on what happens in that open call.  Ideas welcome.