X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 	tests=BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <20100128175832.EQMY3.324473.root@cdptpa-web04-z01>
Date: Thu, 28 Jan 2010 12:58:32 -0500
From: <jenniferlee AT nc DOT rr DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.1 "Bad Address" when running cmd.exe on 64 bit windows         server  2008
Cc: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
In-Reply-To: <20100127092334.GA20008@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Sensitivity: Normal
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

Hi Corinna - nothing like that. The product I work with simply uses ssh to issue 
cmd.exe on remote windows hosts. Some of our customers install cygwin on their 
Windows boxes to enable the ssh connection, we do not dictate what they use nor 
do we help them obtain any product, they just need to allow us an ssh session in 
whatever manner they choose. I just need to know what to tell them if they are 
using Cygwin, since cmd.exe is no longer working with cygwin 1.7.1.  I can just 
tell them cygwin 1.7.1 does not work and they need to find some other method to 
allow ssh, or change my code to use the upper case c instead, but if I can point 
them to a fix on the cygwin end seems like it would be a better answer. 
 
Sorry for the confusion and thanks for your help! 
 
Jennifer 

---- Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote: 
> On Jan 26 23:29, jenniferlee AT nc DOT rr DOT com wrote:
> > Wow, thank you so much, that was very fast!  
> > 
> > Is there a way I can refer my customers to this patch? Or should I put the workarounds in my code for now until this is in an official release?
> 
> Customers?  You're not, by any chance, providing a product running under
> Cygwin without providing the sources of the product *and* Cygwin?  Are
> you aware that Cygwin is GPL licensed with a specific buyout clause:
> http://cygwin.com/license.html
> 
> This mailing list is not for commercial support, btw.  Red Hat provides
> support contracts for that purpose, see
> http://www.redhat.com/services/custom/cygwin/
> 
> 
> Corinna
> 
> -- 
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Project Co-Leader          cygwin AT cygwin DOT com
> Red Hat
> 
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> 


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