ckuker.cpp

C-Kermit源码。是使用串口/Modem和网络通讯的程序

.\" @(#) kermit.1 7.0.196 2000/01/01 Columbia University
#ifdef COMMENT
This man page must be run through the C-Kermit makefile before it can
be used: "make manpage".  Or you can do the following:
  cc -E ckuker.cpp | grep -v ^$ | grep -v ^\# > ckuker.nr
to produce the nroff source file.  THIS FILE MUST NOT CONTAIN ANY BLANK LINES!
Use .sp or similar commands to produce blank lines in the nroff output.
#endif /* COMMENT */
#ifdef SUNOS4
#define SUNOS
#else
#ifdef SUNOS41
#define SUNOS
#else
#ifdef SOLARIS
#define SUNOS
#endif
#endif
#endif
#ifdef HPUX10
.TH KERMIT 1 "1 Jan 2000" "HP-UX C-Kermit"
#define DIALOUT /dev/cul0p0
#define HARDWIRE /dev/tty0p0
#else
.TH KERMIT 1C "1 Jan 2000" "UNIX C-Kermit"
#ifdef LINUX
#define DIALOUT /dev/ttyS0
#else
#define DIALOUT /dev/cua
#endif
#define HARDWIRE /dev/tty01
#endif
.SH NAME
kermit \- C-Kermit 7.0 communications software for serial and network
connections: modem dialing, file transfer and management, terminal connection,
character-set translation, numeric and alpha paging, and script programming.
.SH SYNOPSIS
.B kermit
[ command-file ] [ options ... ]
.SH DESCRIPTION
.I Kermit
is a family of file transfer, management, and communication software programs
from the Kermit Project at Columbia University available for most computers
and operating systems.
#ifdef HPUX10
The version of Kermit for Hewlett-Packard HP-UX, called
#else
#ifdef SUNOS
The version of Kermit for SunOS and Solaris, called
#else
The UNIX version of Kermit, called
#endif
#endif
.IR "C-Kermit",
#ifdef HPUX10
supports both serial connections (direct or dialed) and TCP/IP connections.
#else
#ifdef SUNOS
supports serial connections (direct or dialed),
TCP/IP connections, and on systems equipped with
SunLink X.25, C-Kermit can also make X.25 connections.
#else
supports serial connections (direct or dialed) and, in most UNIX
implementations, also TCP/IP connections.  On certain platforms,
C-Kermit can also make X.25 connections.
#endif
#endif
C-Kermit can be thought of as a user-friendly and powerful alternative to cu,
tip, uucp, ftp, telnet, rlogin, expect, and even your shell; a single package
for both network and serial communications, offering automation, convenience,
and language features not found in the other packages, and having a great deal
in common with its cousins, C-Kermit on other UNIX platforms, Kermit 95 for
Windows 95, Windows 98, Windows NT and 2000, and OS/2; MS-DOS Kermit for PCs
with DOS and Windows 3.x, and IBM Mainframe Kermit-370 for VM/CMS, MVS/TSO,
and CICS.  C-Kermit itself also runs on Digital VMS, Data General AOS/VS,
Stratus VOS, OS-9, QNX, Plan 9, the Commodore Amiga, and elsewhere.
Together, C-Kermit, Kermit 95, MS-DOS Kermit, and IBM Mainframe Kermit offer a
consistent and nearly universal approach to inter-computer communications.
.PP
C-Kermit 7.0 is Copyright (C) 1985, 2000 by the Trustees of Columbia
University in the City of New York.  For use and redistribution rights,
see the C-Kermit COPYING.TXT file or give the C-Kermit COPYRIGHT command
(summary: no license is required for own use;
no license is required for distribution with Open Source operating systems;
a license is required for certain other forms of redistribution).
.PP
#ifdef HPUX10
C-Kermit 7.0 is included with HP-UX 10.00 and later by Hewlett-Packard in
partnership with the Kermit Project at Columbia University.
#endif
.PP
C-Kermit 6.0 is thoroughly documented in the book
.IR "Using C-Kermit"
by Frank da Cruz and Christine M. Gianone, Digital Press, Second Edition,
1997; see REFERENCES
at the end of this manual page.  This manual page is not a substitute for the
book.  If you are a serious user of C-Kermit, particularly if plan to write
C-Kermit script programs, you should purchase the manual.  Book sales are the
primary source of funding for the nonprofit Kermit Project.
.PP
Any new features added since the second edition of the book was
published are documented in the online file
.IR "ckermit2.upd"
until such time as the Third Edition of the book is ready.
Hints, tips, limitations, restrictions are listed in
.IR "ckcbwr.txt"
(general C-Kermit) and
.IR "ckuker.bwr"
(UNIX-specific); see FILES below.  Please consult all of these references
before reporting problems or asking for technical support.
.PP
Kermit software is available for hundreds of different computers and operating
systems from Columbia University.  For best file-transfer results, please use
C-Kermit in conjunction with real Columbia University Kermit software on other
computers, such as Kermit 95 for Windows 95 and NT or MS-DOS Kermit for DOS
3.x or Windows.  See CONTACTS below.
.SH "MODES OF OPERATION"
C-Kermit can be used in two "modes": remote and local.  In
.IR "remote mode",
you connect to the
#ifdef HPUX10
HP-UX
#else
UNIX
#endif
system from a desktop computer
and transfer files between your desktop computer and
#ifdef HPUX10
HP-UX
#else
UNIX
#endif
C-Kermit.  In that
case, connection establishment (dialing, TELNET connection, etc) is handled
by the Kermit program on your desktop computer.
.PP
In
.IR "local mode",
C-Kermit establishes a connection to another computer
by direct serial connection, by dialing a modem, or by making a network
connection.  When used in local mode, C-Kermit gives you a terminal connection
to the remote computer, using your actual terminal, emulator, or UNIX
workstation terminal window or console driver for specific terminal emulation.
.PP
C-Kermit also has two commands interfaces: the familiar UNIX-style command-line
options, and an interactive dialog with a prompt.
.IR "Command-line options"
give
you access to a small but useful subset of C-Kermit's features for terminal
connection and file transfer, plus the ability to pipe files into or out of
Kermit for transfer.
.PP
.IR "Interactive commands"
give you access to dialing, script programming,
character-set translation, and, in general, detailed control and display, as
well as automation, of all C-Kermit's features.  Interactive commands can also
be collected into command files or macros.  C-Kermit's command and script
language is portable to many and diverse platforms.
.PP
.SH "STARTING C-KERMIT"
.PP
#ifdef HPUX10
You can start C-Kermit by typing "/usr/bin/kermit", or just "kermit" if your
PATH includes "/usr/bin", possibly followed by command-line options.
#else
C-Kermit should be available as "kermit" somewhere in your PATH, perhaps as
/usr/local/bin/kermit, in which case you can
start C-Kermit just by typing "kermit", possibly followed by command-line
options.
#endif
If there are no "action options" on the command line (explained
below), C-Kermit starts in interactive command mode; you will see a greeting
message and then the "C-Kermit>" prompt.  If you do include action options on
the command line, C-Kermit takes the indicated actions and then exits directly
back to UNIX.  Either way, C-Kermit executes the commands in its
initialization file,
#ifdef HPUX10
.IR "/usr/share/lib/kermit/ckermit.ini" ,
#else
.IR ".kermrc" ,
in your home directory (or a system-wide directory if C-Kermit was built to
do this)
#endif
before it executes any other commands, unless you have
included the `\|\c
.B \-Y\c
\&\|' (uppercase) command-line option, which means to skip the
initialization file, or you have included the `\|\c
.B -y \c
\&\|
.IR "filename" \c
\&\|'
option to specify an alternative initialization file.
.PP
.SH "FILE TRANSFER"
.PP
Here is the most common scenario for Kermit file transfer.  Many other
methods are possible, most of them more convenient, but this basic method
should work in all cases.
.PP
.in +0.5i
.ll -0.5i
.ta +0.2i
.ti -0.2i
\(bu	Start Kermit on your local computer and establish a connection to the
remote computer.  If C-Kermit is on your local
computer, use the sequence SET MODEM TYPE
.IR "modem-name" \c
\&\|, SET LINE
.IR "device-name" \c
\&\|, SET SPEED
.IR "bits-per-second" \c
\&\|, and DIAL
.IR "phone-number"
if you are dialing; SET LINE and SPEED for direct connections;
SET NETWORK
.IR "network-type"
and SET HOST
.IR "host-name-or-address"
for network connections.
.sp
.ti -0.2i
\(bu	SET any other necessary communication parameters, such as PARITY,
DUPLEX, and FLOW-CONTROL.
.sp
.ti -0.2i
\(bu	Give the CONNECT command.
.sp
.ti -0.2i
\(bu	Log in to the remote computer.
.sp
.ti -0.2i
\(bu	Start Kermit on the remote computer, give it any desired SET commands
for file-, communication-, or protocol-related parameters.  If you will be
transferring binary files, give the command SET FILE TYPE BINARY to the
Kermit program that will be sending them.
.sp
.ti -0.2i
\(bu	To
.IR download
a file or file group, give the remote Kermit a SEND command, following by
a filename or "wildcard" file specification, for example:
.nf
.sp
  send oofa.txt            (send one file)
.sp
.fi
or:
.nf
.sp
  send oofa.*              (send a group of files)
.sp
.fi
To
.IR upload
a file or files, give the remote Kermit a RECEIVE command.  The sending Kermit
will tell the receiving Kermit the name (and other attributes) of each file.
.sp
.ti -0.2i
\(bu	Escape back to the Kermit program on your local (desktop) computer.  If
your local computer is running C-Kermit, type Ctrl-\\ c (Control-backslash
followed by the letter 'c') (on NeXT workstations, use Ctrl-] c).  If MS-DOS
Kermit or Kermit 95, use Alt-x (hold down the Alt key, press 'x').  Now
you should see your local Kermit program's prompt.
.sp
.ti -0.2i
\(bu	If you will be transferring binary files, give the command SET FILE
TYPE BINARY to the Kermit program that is sending the files.
.sp
.ti -0.2i
\(bu	If you are
.IR downloading
files, tell the local Kermit program to RECEIVE.  If you are
.IR "uploading",
give your local Kermit program a SEND command, specifying a filename
or wildcard file specification.  In other words, tell the
.IR remote
Kermit program what to do first, SEND or RECEIVE, then escape back to
the
.IR local
Kermit and give it the opposite command, RECEIVE or SEND.
.sp
.ti -0.2i
\(bu When the transfer is complete, give a CONNECT command.  Now you are
talking to Kermit on the remote computer again.  Type EXIT to get back to the
command prompt on the remote computer.  When you are finished using the remote
computer, log out and then (if necessary) escape back to Kermit on your local
computer.  Then you can make another connection or EXIT from the local Kermit