Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Date: Mon, 6 Dec 2004 11:40:58 -0800 (PST)
From: "Peter A. Castro" <doctor AT fruitbat DOT org>
To: Andrew Markebo <andrew DOT markebo AT comhem DOT se>
cc: cygwin AT cygwin DOT com
Subject: Re: Firing up latest zsh with latest cygwin OOPS!
In-Reply-To: <m3vfbfmiy6.fsf@flognat.dyndns.org>
Message-ID: <Pine.LNX.4.53.0412061129420.11407@gremlin.fruitbat.org>
References: <m37jnvo7px DOT fsf AT flognat DOT dyndns DOT org> <m33byjo6nq DOT fsf AT flognat DOT dyndns DOT org> <m3vfbfmiy6 DOT fsf AT flognat DOT dyndns DOT org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-IsSubscribed: yes

On Mon, 6 Dec 2004, Andrew Markebo wrote:

> Some more questions.. Anyone else who can't read the written contents
> of the "Firing up latest zsh with latest cygwin" mails? Reading them
> with Gnus I only see:
>
> [1. Shortened logfile --- application/x-gzip; zshoutshort.txt.gz]...
> [2. text/plain]

One comment about your mail.  I've exmained the raw mail body and it
appears gnus didn't properly separate out your attachments via the
content boundary.  What I see in the body is this:
--------------------------------------------------------------------------
--=-=-=
Content-Type: application/x-gzip
Content-Disposition: attachment; filename=zshoutshort.txt.gz
Content-Transfer-Encoding: base64
Content-Description: Shortened logfile

H4sIAGVntEEAA+xd628aybL/Hin/w1xppSRHtume92B5dTBgm11jLCBOVmE1
msDYZgMDd2awk/Ph/u23unswPUwNNJjcc4+0K8Xref2qurpeXf3wP/6xy39v
...
J000dz7d/HZz+/kmRt444Z/tGfLr64foZvn99o+gVHy+WEWqfdv8YWeNJFCU
2DkCFP8bQzGENW+rV3qxvKYuBbteeBGsiwFz/WB/W11fVyf0z+Lp8/jR0WKX
HEAA/CCA87sP93cni7vV1YIhbBj13776Pw99gqfNUgEA

And cygcheck.out:

Cygwin Configuration Diagnostics
Current System Time: Mon Dec 06 14:46:59 2004
...
--------------------------------------------------------------------------

Obviously the base64 decoder doesn't like the text that follows the
actual end of the first attachment (zshoutshort.txt.gz).

In anycase, I have extracted the cygcheck.out and the short log from that
body.  I'd still like to get more info on just how the shell was started.
I will try and reproduce your environment myself.  In the mean time, I'd
suggest you try the latest Snapshot of the cygwin DLL and report on your
findings.
  Thanks!

>     /Andy

-- 
Peter A. Castro <doctor AT fruitbat DOT org> or <Peter DOT Castro AT oracle DOT com>
	"Cats are just autistic Dogs" -- Dr. Tony Attwood

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