From: fabio AT joplin DOT colorado DOT edu (Fabio Somenzi)
Subject: Re: gunzip question
22 Mar 1997 14:59:49 -0800
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199703221829.LAA13649.cygnus.gnu-win32@joplin.colorado.edu>
References: <33336C35 DOT 2136 AT netcom DOT com>
	<Pine DOT LNX DOT 3 DOT 91 DOT 970322062505 DOT 15981A-100000 AT spartan DOT pei DOT edu>
Reply-To: Fabio AT Colorado DOT EDU
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Original-To: gnu-win32 AT cygnus DOT com
In-Reply-To: <Pine.LNX.3.91.970322062505.15981A-100000@spartan.pei.edu>
Original-Sender: owner-gnu-win32 AT cygnus DOT com

>>>>> "S" == Sheik  <sheikyy AT spartan DOT pei DOT edu> writes:

 S> On Fri, 21 Mar 1997, Jim Balter wrote:

 >> Trey Jackson wrote: > > e.g. This is what I encounter: > >
 >> C:\cygnus\H-i386-cygwin32\bin>gunzip resume.txt.gz > GUNZIP.EXE:
 >> resume.txt.gz already has .gz suffix -- unchanged
 >> 
 >> Subtle.  What command processor are you using?  For some reason it
 >> is passing the command name as "GUNZIP.EXE" instead of "gunzip",

 S>  I have noticed this too, whats even odder still... run this puppy
 S> in bash, and the problem goes away.

gzip compares argv[0] to "gzip, "gunzip", and "zcat" and sets the -d
and -c options accordingly. At least this is my recollection from
several years ago. Under Unix, gunzip and zcat are normally hard links to
gzip. Bash passes the name correctly in argv[0], and therefore it works.

Fabio

-- 
Fabio Somenzi          | Phone: 303-492-3466
University of Colorado | Fax:   303-492-2758
ECE Dept.              | Email: Fabio AT Colorado DOT EDU
Boulder CO 80309-0425  | WWW:   http://vlsi.colorado.edu/~fabio
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".