This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Telnet in latest Cygwin
- From: Paul Allen <pla16021 at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 9 Aug 2013 15:42:23 +0100
- Subject: Re: Telnet in latest Cygwin
- References: <E66E8CB243656F4D9A91EFB81580C8C2405AE1AE at DB3PRD0710MB368 dot eurprd07 dot prod dot outlook dot com> <5202BDED dot 9030801 at cygwin dot com> <20130808070854 dot GA19486 at calimero dot vinschen dot de> <1326593020 dot 20130808150801 at mtu-net dot ru> <5203E3D9 dot 2090509 at etr-usa dot com>
On Thu, Aug 8, 2013 at 7:30 PM, Warren Young wrote:
> On 8/8/2013 05:08, Andrey Repin wrote:
>>
>>
>> Though, I fail to see, how Cygwin telnet is different from, say PuTTY. Or
>> native Windows telnet.
>
>
> Windows 8 doesn't come with telnet.exe installed by default, and when you install it from
> Programs and Features, it's invisible to Cygwin 32, apparently due to the SxS madness.
Have you tried sysnative in case installing telnet gives you a 32-bit
version as well as a 64-bit one?
> Windows' telnet.exe doesn't even run particularly well within cmd.exe. Telnetting to a local web
> server here, it didn't do local echo properly, so I couldn't see whether I'd typed "GET /
> HTTP1.0" correctly.
Different versions of Windows have come with one of two telnets.
Early and late versions came
with the white-on-black, no-local-echo you have. The others came with
black-on-white,
with-local-echo, window-closes-when-connection-closes. IIRC, the one
that closed when the
connection closed was dropped from Windows prior to HTTP persistent
connections being widely
supported, so was never useful for diagnosing HTTP.
Basically, Windows telnet (both versions) is proof that MIC. Microsoft Is Crap.
--
Paul
--
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