Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Dave Korn" <dk AT artimi DOT com>
To:	"'Cygwin List'" <cygwin AT cygwin DOT com>
Subject:	RE: Problem with gzip
Date:	Wed, 14 Apr 2004 16:50:08 +0100
MIME-Version:	1.0
In-Reply-To:	<6.1.0.6.0.20040414110848.030a1830@127.0.0.1>
Message-ID:	<NUTMEGS2TRqf69aZbLA00000470@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	14 Apr 2004 15:50:08.0593 (UTC) FILETIME=[29ACF410:01C42238]

> -----Original Message-----
> From: Larry Hall 
> Sent: 14 April 2004 16:16

> >>  The above errors seem to indicate that gzip is correctly
> >> detecting a damaged .gz file.
> >
> >  Absolutely so.  Every $0a byte got a bogus $0d prepended 
> to it.  No wonder
> >it wouldn't unpack!
> 
> 
> Yeah?  So?  Next you're going to tell me that gzip won't 
> unpack a file that
> I've uuencrypted or run through 'tr'! Cygwin's no good.


  Yeh, Cygwin certainly sucks - there's been a persistent bug in
/src/winsup/cygwin/dwim.cc for as long as I can remember now! :)


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -