Re: Telnet script problem
From: Alan Connor (zzzzzz_at_xxx.yyy)
Date: Tue, 02 Mar 2004 04:28:19 GMT
On 02 Mar 2004 03:09:38 GMT, those who know me have no need of my name <email@example.com> wrote:
> in comp.unix.shell i read:
>>Netcat (nc) is much better for scripts than telnet.
> and ksh93 has no need of even that. but scripted telnet sessions are often
> easier to write, at least for anything non-trivial, using kermit.
You can do it with Bash alone, too, but I prefer netcat.
Kermit Telnet scripts are NOT easier to write than Netcat Telnet scripts.
That simply isn't possible.
I've never used Kermit, and I suggest that you admit that you don't
have any real experience with Netcat.
Maintainer: Decklin Foster <firstname.lastname@example.org>
Depends: libc6 (>= 2.2.4-2)
Description: TCP/IP swiss army knife
A simple Unix utility which reads and writes data across network
connections using TCP or UDP protocol. It is designed to be a reliable
"back-end" tool that can be used directly or easily driven by other
programs and scripts. At the same time it is a feature-rich network
debugging and exploration tool, since it can create almost any kind of
connection you would need and has several interesting built-in
Maintainer: Vaidhyanathan G Mayilrangam <email@example.com>
Depends: libc6 (>= 2.1.2)
Description: A serial and network communications package.
Gkermit is a GPL'd kermit package. It offers medium-independent terminal
session and file transfer. The non-free package ckermit adds connection
establishment, charecter-set translation and scripting features.