Message-id: <4B4E93A3.6060202@jackson.io>
Date: Wed, 13 Jan 2010 22:46:43 -0500
From: Ken Jackson <cygwin@jackson.io>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5)  Gecko/20091209 Fedora/3.0-4.fc12 Thunderbird/3.0
MIME-version: 1.0
To: cygwin@cygwin.com
Subject: Re: various problems resulting from version 1.7.1
References: <20100113110947.GY14511@calimero.vinschen.de>  <2BF01EB27B56CC478AD6E5A0A28931F2979795@A1DAL1SWPES19MB.ams.acs-inc.net>  <4B4DF9EA.706@bopp.net>
In-reply-to: <4B4DF9EA.706@bopp.net>
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 01/13/2010 11:50 AM, Jeremy Bopp wrote:
>  Maybe I missed your reasoning in an earlier message, but why not use
>  Cygwin-based Telnet and FTP programs?  You already have Cygwin
>  installed, so adding two more packages should not be a problem.
>  That way locale and terminal handling would just work without any
>  need to try spawning cmd windows from Mintty.

I'm in the same boat.

The telnet in cygwin 1.5 seemed to always come up in line mode, even though
I put " mode character" under the appropriate machine name in my 
~/.telnetrc file.

Windows telnet seems to come up in character mode by default, which is what
the embedded hardware remote host needs for proper operation.  So, 
sadly, the
least hassle is to just use Windows telnet in a CMD window.

I haven't installed or tried telnet since upgrading to 1.7, but I'll 
certainly do
that if anything has changed, or if there's a trick I missed.

-Ken Jackson

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