The Kermit Project |
612 West 115th Street, New York NY 10025 USA • firstname.lastname@example.org
C-Kermit is a combined network and serial communication software package offering a consistent, transport-independent, cross-platform approach to connection establishment, terminal sessions, file transfer, file management, character-set translation, numeric and alphanumeric paging, and automation of file transfer and management, dialogs, and communication tasks through its built-in scripting language. C-Kermit includes:
And lots more -- CLICK HERE for specifications. C-Kermit is:
C-Kermit 8.0 is available for practically every known variation and version of Unix, past and present, on every architecture, and for DEC / Compaq / HP VMS / OpenVMS on VAX, Alpha, and IA64 / IPF. Earlier releases of C-Kermit remain available for other platforms and operating systems:
In Unix, C-Kermit can be thought of as a user-friendly and powerful alternative to cu, tip, minicom, uucp, ftp, ftpd, telnet, ktelnet, rlogin, ssh, find, grep, iconv, recode, expect, wget, sendpage, bc, and to some extent even Lisp, your shell, and/or Perl; a single package for both network and serial communications, offering automation, helpfulness, and language features not found in most of the other packages, and with most of the same features available on all its non-Unix platforms (such as VMS), as well as in Kermit 95 on Windows 9x/ME/NT/2000/XP/Vista.
C-Kermit is included in the following operating systems:
Also see:Top ] [ Documentation ] [ New Features ] [ Case Studies ] [ Download ]
As of version 9.0 (starting with the first Beta test), C-Kermit has an Open Source license, the Revised 3-Clause BSD License. Everybody can use it as they wish for any purpose, including redistribution and resale. It may be included with any operating system where it works or can be made to work, including both free and commercial versions of Unix and Hewlett-Packard (formerly DEC) VMS (OpenVMS). Technical support will be available from Columbia University only through 30 June 2011.
C-Kermit 8.0 and 7.0 have a more restrictive license, CLICK HERE to see it.Google ] [ Top ] [ License ] [ New Features ] [ Case Studies ] [ Download ]
The user manual for C-Kermit 8.0 is (still) the book
C-Kermit, Second Edition
[ INFO ],
which is current with C-Kermit 6.0. Features new
subsequent C-Kermit releases
in the supplements (see links just below).
If you don't have the manual, please order it. It explains step-by-step, with examples and sometimes pictures, how to use C-Kermit: how to make connections, how to troubleshoot connection and file-transfer problems, how to handle character-set translation, how to write script programs, and lots more; especially useful since live Kermit software support is no longer available from Columbia University after 30 June 2011. Beginning in 2011, the manual is also available as a Kindle E-Book.
Online Information Resources:
If there is sufficient demand, an updated edition of the manual can be produced for C-Kermit 9.0.
CLICK HERE to see the list of features that were new to C-Kermit 7.0.Top ] [ License ] [ Documentation ] [ New Features ] [ Download ]
CLICK HERE to view the C-Kermit Tutorial.
Case studies and tutorials are posted from time to time to the newsgroup news:comp.protocols.kermit.misc to showcase some of the new features of C-Kermit 7.0 and 8.0, with each posting also available on the website. Here's the index:
You have many choices for downloading:
Install packages and prebuilt binaries (including those on the CDROM) do NOT include C-Kermit's security features, due to USA export law. To obtain a version of C-Kermit that includes Kerberos, SSL, TLS, or SRP, you must download the source code and build it yourself. Address complaints to the US Department of Commerce.Source Code ] [ Individual Binaries ]
Install packages are contributed by Linux distributors, OS vendors, user groups, or users (we don't make them ourselves). The following install packages are presently available for C-Kermit 8.0. These were last checked 17 Aug 2004. Offsite package locations are liable disappear without notice.
CLICK HERE for a general discussion of C-Kermit package making. NOTE HOWEVER that the Unix version of C-Kermit 8.0 includes its own new installation procedure, built into the makefile. See Section 5 of the Unix C-Kermit installation guide.Top ] [ Unix Build ] [ VMS Build ]
You can download C-Kermit 8.0 source and text files directly from the Kermit Project in any of several archive formats by clicking on the following FTP links. The complete archives contain source code, build procedure, license, initialization files, CA certificates, manual page or help topic, initialization files, and plain-text information files extracted from the Web pages listed in the Documentation section: a complete distribution. The text archives contain everything but the source code; these can used when you download a prebuilt binary. The size of each archive file in megabytes is shown in each cell.
|Unix Complete||2.9 cku211.zip||11.7 cku211.tar||4.1 cku211.tar.Z||2.9 cku211.tar.gz|
|Unix Text Only||0.8 cku211txt.zip||2.7 cku211txt.tar||1.0 cku211txt.tar.Z||0.8 cku211txt.tar.gz|
|VMS Complete||2.8 ckv211.zip|
|VMS Text Only||0.6 ckv211txt.zip|
(Zip archives contain only text files, unzip them with "-a" or "-aa".)
Besides those, we also have C-Kermit 7.0 archives for the following platforms that have not been updated to C-Kermit 8.0:
If you want to monitor the day-to-day progress of C-Kermit development, you can find the current working source code HERE. Source code and text files are also available separately in the kermit/f/ directory. These include files for platforms other than Unix and VMS, such as Stratus VOS, Data General AOS/VS, OS-9, the Amiga, etc. All files in this directory are text files; transfer them in text mode. See the ckaaaa.txt file for details. NOTE: The Unix and VMS source files are at 8.0 level. The VOS, Amiga, OS-9, and AOS/VS versions remain at 7.0 level. Others (Macintosh, Atari ST) have not yet been updated in a long while due to lack or programmers and/or platforms; volunteers welcome. And of course anybody interested in porting C-Kermit to new platforms is more than welcome to contact us about it; we'll be happy to get you started.
$ mkdir kermit $ cd kermit
$ gunzip cku211.tar.gz $ uncompress cku211.tar.Z
$ tar xvf cku211.tar
If you downloaded a Zip archive, unzip it. Example:
$ unzip -a cku211.zip
$ rm cku211.tar (or rm cku211.zip)
$ make linux (Linux, almost any version) $ make freebsd44 (FreeBSD 4.4) $ make solaris8 (Solaris 8 with cc) $ make solaris8g (Solaris 8 with gcc) $ make irix62 (IRIX 6.2)
You can also download individual Unix binaries from the C-Kermit binaries table, but to avoid library or other version mismatches, it is better to build from source code if you can.Top ] [ VMS Hints & Tips ] [ VMS Installation Instructions ]
If you want to install a prebuilt VMS binary, then fetch the most appropriate VMS binary from the C-Kermit binaries table. Pick a VAX binary for a VAX or an Alpha binary for an Alpha. The VMS version number for the binary must be less than or equal to your VMS version. If you want to make TCP/IP connections, pick the binary for the appropriate TCP/IP product (TGV Multinet, DEC UCX, Process Software TCPware, etc), again with a version number less than or equal to yours; if none can be found, then try a UCX version (since most non-DEC TCP products include built-in UCX emulation). If you downloaded a prebuilt binary, also download the VMS C-Kermit text-file archive. Then read the installation instructions for VMS.
If you want to build from source code, fetch the VMS complete archive above if you have VMS-based unpacking tools, otherwise get the source files and text individually as described just below. NOTE: Unzip the Zip file with "unzip -a".
$ create/directory kermit $ set default [.kermit]
$ unzip -a ckv211.zip
If you have a pre-5.0 VMS release, use the "old" build procedure:
If you experience any trouble, read the comments at the top of the build procedure.
$ r wermit
The C-Kermit binaries table is HERE. Before visiting the table, you should read this section.
When you download a prebuilt-Kermit binary, you should also download the C-Kermit text files, unpack them if necessary, and install them as desired. NOTE: In Unix, you can still use "make install", even if if you did not use the makefile to build your Kermit binary (the makefile as well as all the text files you need are in the text archive).
In the binaries table, filenames start with "ck" for C-Kermit, then one letter or digit to indicate the platform ("u" for Unix, "d" for Data General AOS/VS, "v" for VMS, "i" for Amiga, "9" OS-9, "p" for Plan 9, etc). After that comes a three-digit edit number:
188: Version 5A(188), November 1992 through September 1993.Then a possible test-version designator: "a" for Alpha or "b" for Beta, followed by the 2-digit test number. Examples:
189: Version 5A(189), September 1993 through October 1994.
190: Version 5A(190), October 1994 through September 1996.
192: Version 6.0.192, September 1996 through December 1999.
193: Version 6.1.193, November 1996 through June 1998.
194: Version 6.1.194, June 1998 through December 1998.
195: Version 7.0.195, January 1999 through August 1999.
196: Version 7.0.196, September 1999 through final release 1 Jan 2000.
197: Version 7.0.197, January-February 2000.
200: Version 8.0.200, December 2001.
201: Version 8.0.201, February 2002.
206: Version 8.0.206, October 2002.
208: Version 8.0.208, 14 March 2003.
209: Version 8.0.209, 17 March 2003.
211: Version 8.0.211, 10 April 2004.
cku209.xxx C-Kermit 8.0.209 final release cku200b04.xxx C-Kermit 8.0.200 Beta.04 cku197.xxx C-Kermit 7.0.197 final release
Test versions are included here only for platforms that do not have a final build available (usually because the machine disappeared or had an OS upgrade before the final C-Kermit release).
Note that edits 193, 194, 195, 198, 199, and 202-05 were never formally released (191 was only for OS/2).
The rest of the name is platform-dependent; in Unix it's the name of the makefile target, optionally followed by specific hardware platform and/or OS version, when it makes a difference. In VMS it's the platform ("axp" (i.e. Alpha) or "vax"), then the VMS version number (e.g. "vms73"), and then TCP/IP product and version number (or "nonet" if TCP/IP support is not built in). And so on. VMS TCP/IP product codes are as follows:
ucx DEC / Compaq / HP TCP/IP
tgv TGV MultiNet
pst Process Software TCPware
twg The Wollongong Group WIN/TCP or PathWay
cmu Carnegie-Mellon University CMU/IP
REMEMBER: It's often better to build your own binary than to run a prebuilt one, due to the ever-increasing likelihood of OS and/or library version mismatch.
After downloading, rename to "kermit" or "kermit.exe" (etc), as appropriate for your operating system and, if necessary, give execute permission, e.g. (in Unix):
$ mv cku211.linux-i386-rh7.2 kermit $ chmod +x kermit
Also remember that before C-Kermit can be used to dial out from Unix, it will probably also be necessary to give the Kermit executable a certain owner and group, and to set it suid and/or sgid bits, to allow it access to the dialout device and/or lockfile directory (the same as any other dialout software, such as cu or minicom). Read Sections 10 and 11 of the Unix C-Kermit installation guide.
If you are able to make a binary not listed table
(or that is listed, but is not current"), please contribute it to the archive.
CLICK HERE to visit the C-Kermit binaries table.
Questions? Comments? -- Send e-mail.
KERMIT PROTOCOL : SECURE : SCRIPTABLE : TELNET : FTP : UNIX : VMS : LINUX : BSD : MAC OS X : SOLARIS : AIX : HP-UX : TRU64 : SCO : QNX : IRIX : UNICODE : KERBEROS : SSL : TLS : SRP : FTP SCRIPT : FILE TRANSFER : MODEM : DIAL : PAGER