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
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Fri, 14 Nov 2003 11:22:15 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Thomas Hammer <thammer AT sim DOT no>
cc: cygwin AT cygwin DOT com
Subject: RE: Bug in gzip's stdout handling
In-Reply-To: <GPEILLHCKKGPIGFLPKIOEEKIENAA.thammer@sim.no>
Message-ID: <Pine.GSO.4.56.0311141102550.10744@slinky.cs.nyu.edu>
References: <GPEILLHCKKGPIGFLPKIOEEKIENAA DOT thammer AT sim DOT no>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine DOT GSO DOT 4 DOT 56 DOT 0311141102552 DOT 10744 AT slinky DOT cs DOT nyu DOT edu>

I've removed <support at gzip dot org> from this discussion.  So far this
is Cygwin-related, and you can update them later on the results if it
turns out to be a generic gzip issue.

On Fri, 14 Nov 2003, Thomas Hammer wrote:

> > -----Original Message-----
> > From: Igor Pechtchanski [mailto:pechtcha AT cs DOT nyu DOT edu]
> > Sent: 14. november 2003 16:28
> > To: Thomas Hammer
> > Cc: support AT gzip DOT org; cygwin AT cygwin DOT com
> > Subject: Re: Bug in gzip's stdout handling
> >
>
> Hi Igor.
>
> Thanks for responding so promptly :).
>
> <...>
>
> >
> > I bet you have a text mount.  Please *attach* the output of "cygcheck
> > -svr", as per <http://cygwin.com/problems.html> - this will confirm the
> > guess.
>
> cygcheck.out attached.
>
> I didn't find anything about any drives being mounted as text, though.
>
> Two small bits of info that might or might not have some value:
>
> 1) I believe this has worked earlier (i.e. 6 months ago) for a colleague of
> mine, running a recent version of cygwin. Which means that something could
> have been broken in cygwin after that, or (more likely) that something for
> some reason is configured differently on my system.
>
> 2) When I installed cygwin, I was asked if I wanted the tools to support
> Unix-style newlines or DOS-style newlines. I answered "DOS-style". I did
> reinstall cygwin, specifying "Unix-style" newlines this time, and had the
> same problem though.
>
> .Thomas

(2) shows that you used to have text mounts.  Your cygcheck.out shows
binary mounts, so that's probably not the problem.

Please try the following:  "sed '' binaryfile.bin > acopy.bin" and compare
the files.  Also "echo | sed '' > test.out; od -c test.out" and "perl -e
'print q{ }x2560' | gzip -c > test.gz; od -c test.gz".
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

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