command or program. The built-in command might not behave the way
the platform-specific external one did, but many options are
available for customization. Of course the underlying
- platform-specific command can still be accessed with "!", "@", or
+ platform-specific command can still be accesssed with "!", "@", or
"RUN" wherever the installation does not forbid. In UNIX, the "ls"
- command can be accessed directly as "ls" in C-Kermit.
+ command can be accesssed directly as "ls" in C-Kermit.
* SEND ? prints a list of switches rather than a list of filenames.
If you want to see a list of filenames, use a (system-dependent)
construction such as SEND ./? (for UNIX, Windows, or OS/2), SEND
them easily, since all Telnet negotiations lines begin with (uppercase)
"TELNET".
+The SSH Client
+
+ C-Kermit does not have its own built-in SSH client; instead, in the
+ Unix tradition, uses the external SSH client to do the SSH part, and
+ Kermit does its thing on top -- file transfer, scripting, etc. Under
+ certain circumstances that have not yet been identified, it sometimes
+ happens that after making an SSH connection from C-Kermit, logging out
+ from the remote host, and popping back to the local C-Kermit program,
+ subsequent SSH commands file with a message like "Network type not
+ supported". Starting a new copy of C-Kermit is the workaround.
+
5. MODEMS AND DIALING
[ [55]Top ] [ [56]Contents ] [ [57]Next ] [ [58]Previous ]
GENERIC-HIGH-SPEED has become the default modem type, so now it is
usually possible to SET LINE, SET SPEED, and DIAL without having to
identify your modem. If this doesn't work, of course, then you might
- have to fall back to the tradiational method: Give a SET MODEM TYPE for
+ have to fall back to the traditional method: Give a SET MODEM TYPE for
a specific modem first, then SET LINE, SET SPEED, and DIAL.
An important change in C-Kermit 6.0 is that when you give a SET MODEM
watch the dialing interactions between C-Kermit and your modem. Consult
Chapters 3-4 of [63]Using C-Kermit (2nd Ed) for modem-dialing
troubleshooting instructions. The following sections offer some
- addtional hints and tips.
+ additional hints and tips.
6.1. Syntax
a reverse terminal server, was contributed by an Annex terminal server
user:
- Using C-Kermit on an HP 9000 712/80 running the HP-UX 10.0 operating
- system. The HP was connected to a Xylogics Annex MICRO-ELS-UX R7.1 8
- port terminal server via ethernet. On the second port of the
- terminal server is an AT&T Paradyne 3810 modem, which is connected
- to a telephone line. There is a program which runs on the HP to
- establish a Telnet connection between a serial line on the Annex and
- a character special file on the HP (/dev file). This is an Annex
- specific program called rtelnet (reverse telnet) and is provided
- with the terminal server software. The rtelnet utility runs on top
- of the pseudo-terminal facility provided by UNIX. It creates
- host-originiated connections to devices attached ot Annex serial
+ Using C-Kermit on an HP 9000 712/80 running the HP-UX 10.00
+ operating system. The HP was connected to a Xylogics Annex
+ MICRO-ELS-UX R7.1 8 port terminal server via ethernet. On the second
+ port of the terminal server is an AT&T Paradyne 3810 modem, which is
+ connected to a telephone line. There is a program which runs on the
+ HP to establish a Telnet connection between a serial line on the
+ Annex and a character special file on the HP (/dev file). This is an
+ Annex specific program called rtelnet (reverse telnet) and is
+ provided with the terminal server software. The rtelnet utility runs
+ on top of the pseudo-terminal facility provided by UNIX. It creates
+ host-originated connections to devices attached ot Annex serial
ports. There are several command line arguments to be specified with
this program: the IP address of the terminal server, the number of
the port to attach to, and the name of the pseudo-device to create.
a terminal emulator, etc, or (in the case of a self-contained
workstation) your console driver, a terminal window, xterm, etc.
- Kermit is semitrantsparent rather than fully transparent in the
+ Kermit is semitransparent rather than fully transparent in the
following ways:
* During a TELNET ("set host") session, C-Kermit itself executes the
an escape sequence like "<ESC> O p"). In both cases, C-Kermit has no
way to tell the difference between such multibyte key values, and the
corresponding series of single-byte key values. This could only be done
- by accessing the keyboard at a much lower level in a highly
+ by accesssing the keyboard at a much lower level in a highly
platform-dependent manner, probably requiring tens of thousands of
lines of code to support even a sampling of the most popular
workstation / OS combinations.
transfer fails because Kermit will not rename a directory. Send the
file with another name, or use SET FILE COLLISION RENAME.
* If the directory lacks write permission, the file transfer fails
- even if you have write access to the file that is being backed up;
+ even if you have write accesss to the file that is being backed up;
in that case, switch to SET FILE COLLISION OVERWRITE or APPEND, or
send to a different directory.
projects / ckermit.git / blobdiff