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
Message-ID: <017c01c361be$eff7a290$2201a8c0@harvey>
From: "Gary L. Feldman" <gaf_ml_01 AT comcast DOT net>
To: <cygwin AT cygwin DOT com>
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0308130909400 DOT 8046-101000 AT slinky DOT cs DOT nyu DOT edu>
Subject: Re: My setuplog.full
Date: Wed, 13 Aug 2003 13:18:35 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

>From: "Igor Pechtchanski" <pechtcha AT cs DOT nyu DOT edu>
>Sent: Wednesday, August 13, 2003 9:23 AM


> On Wed, 13 Aug 2003, Gary L. Feldman wrote:
> It is.  The general tradition is to not send private mail unless

Let me point out that you've been sending me private copies
causing me to get duplicates.  (I know about using
Reply-to, but the reality is that some many end users simply
can't set Reply-to and that's not going to change anytime soon.)

> it's a 700-*byte* attachment -- I doubt it'd add much to the list traffic.

I  wasn't concerned about the size so much as the protocol on many lists
is to prohibit binaries or attachments altogether, regardless of size.  For
one thing, they screw up a lot of digests.  My apologies for getting
it wrong with this list.

> Furthermore, IIRC, I requested the setup.log.full from the setup run that
> reproduced your problem.  This isn't it (in the attached run you've
> apparently canceled setup after getting the list of packages).

It was cancelled after running through the steps I indicated, i.e.
deselecting everything and then selecting bash.  However, this was
on an existing installation, so perhaps the behavior was different
there.

Therefore, I did a full uninstall of Cygwin (easier said than done),
and tried again.  This time I paid closer attention, but I also used
a different mirror.  (The previous one was nasa, but for some
reason I've started having a lot of trouble connecting to mirrors.)
This time it seems to work, so it's likely that my recollection is
wrong and I did deselect the other options leaving bash
selected as is.  Which means that it's behaving as expected, but it
is still problematic.  Getting back to my original pints, it shouldn't
allow such states (at least not without warning messages), and
until then, the documentation needs to be clearer that you can
break things by deselecting some items.

Gary



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