Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <41AB9E31.1020801@mysql.com> Date: Mon, 29 Nov 2004 23:09:53 +0100 From: Stefan Hinz Organization: MySQL AB User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) MIME-Version: 1.0 To: Bob Byrnes CC: cygwin AT cygwin DOT com Subject: Re: Piping problems with bk and ssh under Win XP SP2 References: <20041129173835 DOT 4C5BCE54B AT wildcard DOT curl DOT com> In-Reply-To: <20041129173835.4C5BCE54B@wildcard.curl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mailgate.mysql.com X-IsSubscribed: yes Bob Byrnes wrote: >>With my current installation (Win XP SP2, Cygwin 1.5.12) it looks like I >>cannot use BitKeeper via ssh since there is a piping problem with SP2 >>and Cygwin. > > > Could you please provide more details? Exactly what is going wrong, > and what makes you think it is due to a "piping problem"? I've asked before, and got an answer that told me my bk/ssh problems were related to Cygwin 1.5.11+/Win XP SP2 problems (which, from reading the archives, is what I had suspected): http://sources.redhat.com/ml/cygwin/2004-11/msg00968.html Executive summary: bk via ssh doesn't work with Cygwin 1.5.12 on Win XP SP2. bk via http works, and ssh itself works, too. The problem shows up on my Win XP SP2 box only; everything works smoothly on my Win 2000 SP4 box (I'm using 1.5.11 on that box). Regards, Stefan -- Stefan Hinz MySQL AB, Documentation Team Taunusstr. 27, 12161 Berlin, Germany Desk: +49 30 82702940 Fax: +49 30 82702941 Mobile: +49 177 7841069 -- 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/