As of 12 Dec 2001, C-Kermit 8.0 is
released and supersedes C-Kermit 7.0. Sources and binaries are
available now.
The website and various accompanying files are still being updated. The
remainder of this page still applies to version 7.0.

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,
find, grep, iconv, recode, expect, wget, sendpage, bc, maybe even 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, as well as in Kermit 95
on Windows 9x/NT/2000/XP.

Personal or Internal Use:
C-Kermit is freely downloadable by individuals for their own
use and by organizations (companies, universities, government agencies,
hospitals, etc) for internal use. In this case,
we ask (but do not require) you to
also purchase the user manual to (a) let
you get the most out of the software; (b) reduce the load on our help
desk; and (c) contribute some revenue to the nonprofit and entirely
self-supporting Kermit Project.

Free Unix Distributions:
C-Kermit may be included in "free Unix" distributions such as GNU/Linux,
FreeBSD, NetBSD, and OpenBSD. See
the license
for details.

Redistribution: Redistribution of C-Kermit except as in (2)
must be licensed.
CLICK HERE for terms and conditions.

The user manual for C-Kermit 7.0 is the book
Using C-Kermit, Second Edition,
which is current with C-Kermit 6.0. Features new to version 7.0 are documented
in the online
Supplement to Using C-Kermit,
Second Edition, which should serve as a supplement to the book until
the Third Edition is ready in 2001.

If you don't have the manual, please order it.
It explains 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. It lets you get the
most out of your software, it reduces the load on our help desk, and sales of
the manual are the primary source of funding for continued C-Kermit
development and support.

You can download it from the Kermit website in source-code and/or
binary form. Install packages are also available for selected platforms.
CLICK HERE to go to the download section.

It comes with certain operating systems, such as
FreeBSD 4.0 (on first CD)
and
Red Hat Linux 6.2 (on Power Tools CD)
as an optional install package. It will also be included
with forthcoming releases of some of the popular Linux distributions such
as
Slackware,
Caldera,
SuSE,
TurboLinux,
and
Mandrake.
C-Kermit 6.0 is preinstalled on HP-UX 10.00 and later.

You can order it on CDROM. The C-Kermit
7.0 CDROM includes all C-Kermit 7.0 and
G-Kermit 1.00
sources and binaries, the C-Kermit 7.0 Update
Notes and other auxiliary documentation (everything listed on this
web page that was available as of mid-March 2000). The CDROM is in ISO 9660
(DOS) format, and should be readable on any computer that has a CDROM drive.
CLICK HERE for the C-Kermit 7.0 CDROM order form.

The C-Kermit 7.0 CDROM (previous item) is included with
Kermit 95 1.1.20 and later, in the retail shrinkwrapped
package.

If you wish to redistribute C-Kermit to customers or clients or
bundle it with a product, CLICK HERE for
terms and conditions.

If you already have the software but need the manual,
CLICK HERE to order it.

C-Kermit is supported as described in the Kermit Project
Technical Support page. For companies that
require a more formal commitment, a support contract is
available; CLICK HERE for details.

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, with each posting also
available on the website. Here's the index:

Version 7.0.197 of 8 February 2000 is a minor update to version 7.0.196
of 1 January 2000 to make C-Kermit 7.0 build successfully on certain platforms
where version 7.0.196 did not. There are no functional changes
whatsoever. C-Kermit 7.0.197 programs are functionally identical with 7.0.196.

Features that show up as links are described in greater detail below. The
others (and many more) are described in the text file,
ckermit2.txt,
also available on the Web as
ckermit2.html.

This is just a brief list; the complete story runs to more than 200 printed
pages, and can be found in the
ckermit2.txt file, which is a supplement to
Using C-Kermit, 2nd Edition.
Also available on the Web as
ckermit2.html.

For even more detail, you can read the day-by-day edit history in the
ckc197.txt file, as well as all the Alpha and Beta test
announcements in the ck61*.txt and ck70*.txt files in the
kermit/f/
directory.

The following sections present an overview of several of C-Kermit 7.0's new
features. After these come links to the software itself.

In UNIX and Windows 9x/NT, C-Kermit 7.0 can be set up as an Internet service
under inetd, similar to an FTP server, using a TCP port and Telnet options
assigned for this purpose by the Internet Assigned Number Authority (IANA) and
described in Internet RFCs
2839 and
2840.

The Internet Kermit Service Daemon (IKSD) can be accessed in client/server
mode from any Kermit client (similar to how FTP works), but can also be
accessed directly at its prompt, which opens up a whole new world of
automation possibilities. Other advantages over FTP include:

File transfer through a combination of transports (e.g. terminal servers)

Configurability as a secure server with Kerberos, SRP, or SSL/TLS (*).

Realtime monitoring by system manager.

(*) Some FTP servers also support this. Kerberos and SRP available only
in the USA and Canada.

Note that timestamps, permissions, text/binary mode switching, and directory
tree transfer are not restricted to UNIX-to-UNIX connections, but also work
with Kermit clients on other platforms including Windows 95/98/NT, OS/2, and
VMS (as appropriate -- e.g. permissions don't apply to Windows).

When you use C-Kermit 7.0 itself as the client, you will have a new "tight
coupling" between client and server, in which each partner tracks the "mode"
of the other (prompt, connect, server, etc). When you make an anonymous
connection to this server, you will find yourself in the /pub/ftp tree, and
can access any directories or files you could access with anonymous FTP to
same server.

The UNIX version of C-Kermit 7.0 can now be used through any other
communications program whose user interface goes through standard input and
standard output. In addition, most of the UNIX versions can also control
external programs via pseudoterminals, like 'expect' can.

This allows you (for example) to use all the scripting and file transfer
features of C-Kermit through clients of various services that C-Kermit might
not support directly like ftp, an ssh client, tn3270 (for connecting to IBM
mainframes), tn5250 (for AS/400 connections), various SOCKS Telnet clients, a
cu or tip program that has access to a dialout device that Kermit does not,
rlogin connections without being root. The commands are PIPE (for standard
i/o redirection) and PTY (for pseudoterminals). Examples:

PIPE is more portable but won't work with applications that don't use
standard i/o, and it bypasses the terminal driver, which can result in
CR/LF/CRLF confusion, inappropriate keyboard handing or echoing, etc. PTY is
less widely available, but it allows you to control any text-mode application
at all, and it does so through the terminal driver, thus bypassing the
problems with PIPE.

UNIX C-Kermit 7.0 can be built with support for MIT's
Kerberos IV or Kerberos V,
Stanford University's Secure Remote
Password (SRP) protocol, or SSL/TLS
security.
These protocols allow for mutually authenticated Telnet connections
without sending passwords over the network, and optionally also for fully
encrypted sessions.

A secure client needs a secure server on the other end. For a survey of
secure Telnet servers for UNIX, CLICK HERE.

The encryption modules are not part of the regular C-Kermit package
due to USA export law. If you are in the USA or Canada and you
would like to download the secure version of C-Kermit (source code only)
CLICK HERE
or send us e-mail.

SSL/TLS is the IETF-approved form of public-key security, an
alternative to SSH that is free of patent restrictions and that addresses the
key-management and revocation issues that SSH presents. C-Kermit 7.0
supports the OpenSSL implementation of
SSL/TLS, which allows pure SSL or TLS based connections with Tim Hudson's
Telnet AUTH SSL and the IETF's Telnet START_TLS protocols, including
verification of certificate chains for both client and server, and support for
certificate revocation lists. A Unix telnet server that supports Telnet
START_TLS is available from:

A new suite of HTTP commands lets you manage Web servers with C-Kermit using
HTTP 1.0 protocol. You can get and put files, obtain information about them,
and so on, even when you could not ordinarily do so with FTP or Kermit (for
example, because no FTP or IKSD server is installed on the Web server),
and when you have the SSL/TLS option installed, you
can do so securely.

The new EXEC command (Unix only) lets Kermit overlay itself in memory with an
external program, starting this program with command-line options of your
choice. EXEC /REDIRECT takes this one step further, redirecting the external
program's standard i/o to Kermit's communications connection. You can use
this feature to turn Kermit into your PPP dialer, which gives you all the
advantages of C-Kermit's knowledge of modems, phone numbers, area and country
codes, etc, and its dialing-directory and redialing capabilities. Example:

A switch is a keyword beginning with a slash (/). Some switches
accept values as operands. Switches affect only the command with which
they are included; thus their affect is local, not global like SET
commands. Here are some examples:

or whether to pass the file through a filter, or to descend directories
recursively, or to recover an interrupted transfer from the point of failure,
and so on, in any sensible combination.

Switches have been added not only to the SEND command, but also to most other
file-transfer commands, as well as to the CONNECT, SET LINE, SET HOST,
DIRECTORY, DELETE, PURGE, TYPE, RENAME, COPY, STATISTICS, and others. Certain
commands including DIRECTORY, DELETE, PURGE, and TYPE let you set default
switches to match your preferences so you don't have to type them each time.

A pattern is a string that includes special notation for matching classes or
sequences of characters. C-Kermit 7.0 / K95 1.1.18 support patterns
in several places:

Filenames

INPUT and MINPUT search strings

SWITCH case labels

The new IF MATCH statement

Patterns are also called wildcards, especially when used for
filename matching, as they are in the UNIX version and in K-95 1.1.18.
C-Kermit 7.0 supports the following notation:

*

Matches any sequence of zero or more characters. For example:
"ck*.c" matches all files whose names start with "ck" and end with ".c",
including "ck.c".

?

Matches any single character. For example, "ck?.c" matches all files
whose names are exactly 5 characters long and start with "ck" and end with
".c". When typing commands at the prompt, you must precede any question mark
to be used for matching by a backslash (\) to override the normal function of
question mark, which is providing menus and file lists.

[abc]

Square brackets enclosing a list of characters matches any single
character in the list. Example: ckuusr.[ch] matches ckuusr.c and ckuusr.h.

[a-z]

Square brackets enclosing a range of characters; the hyphen separates the
low and high elements of the range. For example, [a-z] matches any
character from a to z.

{string1,string2,...}

Braces enclose a list of strings to be matched. For example:
ck{ufio,vcon,cmai}.c matches ckufio.c, ckvcon.c, or ckcmai.c. The strings
may themselves contain metacharacters, bracket lists, or indeed, other
lists of strings.

C-Kermit 7.0 and its derivatives (including Kermit 95 1.1.18 and later) go to
extraordinary lengths to transfer every file in the most
appropriate mode, text or binary, automatically. Only in a few rare cases
will the automatic methods fail to determine the appropriate mode for a
particular file. When they do, however, it is almost always better to use
binary mode, since this leaves the file intact and unchanged, rather than
changing its characters or record format, allows for recovery in case of
broken transmissions, and in any case is more appropriate now that the majority
of files being transferred are compressed tar archives, graphics images, and
so forth. For this reason, the default file type (that is,
the one that is used in the absence of any other information or instructions)
in C-Kermit 7.0 has been changed from text to binary.

Of course you can change the default back to text simply by giving a SET FILE
TYPE TEXT command (or putting it in your C-Kermit customization file) and you
can also override the default and/or the automatic methods on a per-transfer
basis (by using the new /BINARY and /TEXT switches on the
SEND and GET commands) or even a per-file basis (by creating a SEND-LIST).

Also with this change comes the new SET FILE INCOMPLETE AUTO command, also
the new default, which causes incompletely received files to be kept for
binary-mode transfers and discarded for text-mode ones, since the main reason
to keep incompletely received files is to allow recovery, which is possible
only for binary-mode transfers.

C-Kermit 7.0 (and Kermit 95 1.1.16 and later) automatically choose
the appropriate transfer mode, text or binary, for each file they send by
following a rather complex procedure, which includes end-to-end "like system"
recognition, whether character-set translation has been requested, and other
factors. When the two ends recognize each other as "alike" (e.g. both are
some form of UNIX) and character-set translation has not been
requested, all files are transferred in binary mode. This improves
performance, removes any possibility of "corruption" by inappropriate
character-set or record-format conversions, and allows for recovery of
interrupted transfers.

When the two systems do not recognize each other as alike, or character-set
translation has been requested, the file sender chooses
text and binary mode on a per-file basis by
matching each file's name with a list of patterns. For example, if a file's
name matches the pattern "*.txt" it is sent in text mode, whereas if
it matches "*.zip" it is sent in binary mode. A comprehensive list
of patterns is preconfigured, and commands are provided for you to edit the
list, as well as to disable or re-enable this feature.

Filename pattern matching allows a file group to be sent between unlike
systems (e.g. from UNIX to VMS) without having to separate the text and binary
files, with full record-format and character-set conversion performed on text
files, and binary files transferred without conversion, automatically. (NOTE:
The filename pattern-matching feature is not used by VMS C-Kermit, which has a
different method of accomplishing the same thing.)

The UNIX and VMS versions of C-Kermit 7.0 now include each file's permissions
(protection code) among the transmitted file attributes. This is useful
mainly in UNIX to avoid loss of "execute" permission for programs or shell
scripts during transfer. However, the mechanism also works across platforms
so, for example, a UNIX file with execute permission will also have execute
permission after being transferred to VMS (and vice-versa).

C-Kermit 7.0, when used in conjunction with
Kermit 95 1.1.16
or later,
MS-DOS Kermit 3.16
or later, or C-Kermit 7.0 itself, can perform "recursive"
file transfers, in which all the (selected) files in the given directory are
sent, plus all the files in all the subdirectories of the given directory,
and all the files in their subdirectories, and so on.

Such transfers can take place not only between computers with similar file
systems (such as Solaris and AIX), but also between dissimilar systems (like
Windows 95 and HP-UX or VMS). Directories are created as needed during
the transfer process.

Furthermore, any mixture of text and binary files can be accommodated via
filename-pattern matching, as described above. This
allows, for the first time anywhere (as far as we know) transfer of entire
directory trees (entire file systems if you start at the root) between
dissimilar computers in a single operation without the use of intermediate
archives such as tar or ZIP.

In some versions of C-Kermit 7.0 (notably the UNIX version) it is now possible
to pass outbound or incoming files through a "filter" as part of the transfer
process. Similarly, it is now possible to send the output of an arbitrary
command or program, or to receive into the standard input of a command or
program. For example, you may now tell C-Kermit to send the output of a
pipeline composed of tar and gzip, and another C-Kermit on the other end to
receive to a pipeline composed of gunzip and tar. Or in case you have a text
file written in a character set that C-Kermit doesn't know about, you can pass
it through a translation filter. You can even use this feature to accomplish
encrypted file transfers on connections that are not already encrypted
otherwise.

When full unprefixing and streaming are used with a large packet length,
C-Kermit's file-transfer throughput is comparable with FTP; here are some
typical text and binary file transfers between two UNIX workstations with
the new C-Kermit over a local 10Mbps Ethernet (note the new brief file-transfer
display option, the automatic switching between binary and text mode, and the
new more-accurate statistics):

C-Kermit has included performance features like long packets for more over
a decade, with others (sliding windows, control-character unprefixing, and now
streaming) added over the years. Nevertheless, the popular perception is still
that "Kermit is slow". This is due in part to the many third-party
implementations that, indeed, are slow, as well to the persistence of
fifteen-year-old Kermit programs from the Kermit project itself.

Of course modern Kermit protocol and software (since about 1990) can go as
fast as you care to make it go, but its default tuning has always been for
robustness rather than speed. It turns out, unfortunately, that first
impressions matter most. If it's slow out of the box, few will make the
effort to learn how to make it go fast, or to understand why it is
delivered with slow tuning.

Therefore C-Kermit 7.0 is delivered with fast tuning:

Today's connections are more reliable than those of the early years;
most connections nowadays are over networks or error-correcting,
flow-controlled modems.

If file transfer fails to work because of the new default fast tuning,
users are more likely to inquire about it or read the documentation than they
were to do so when transfers did work, but worked slowly.

Kermit software, a pioneer in international text transfer since the 1980s,
now adds
Unicode
(ISO 10646) -- the Universal Character Set (UCS) -- to its
already large repertoire of character sets. Unlike traditional character
sets, the UCS encodes all of the world's major scripts, and therefore allows
true multilingual text.

Kermit protocol and software has included character-set translation
capabilities for more than a decade, allowing conversion of text among the many
"traditional" standard and proprietary character sets like the ISO 8859 Latin
Alphabets, PC code pages, IBM mainframe EBCDIC code pages, ISO 646 national
character sets, JIS, DEC, HP, DG, Macintosh, NeXT, etc.

With growing acceptance of Unicode, there is increasing need for
importation of text in "traditional" encodings into Unicode platforms
and applications, and also for export of Unicode text to
non-Unicode environments. C-Kermit now offers these services over a
wide range of platforms and communication methods.

UCS-2 and UTF-8 are now supported as transfer character sets (the
small number of international standard character sets allowed "on
the wire" in Kermit file transfer; each Kermit file-transfer
partner converts between its local encoding and the transfer
encoding) (UCS-2 and UTF-8 are two different representations of
Unicode / ISO 10646).

UCS-2 and UTF-8 are now supported as file character sets.
Incoming text can be stored in either UTF-8 or UCS-2, and
UCS-2 or UTF-8 text can be sent with conversion to any appropriate
file character set (including conversion of UCS-2 to UTF-8 or
vice-versa). Full "endianness" detection and control is included
for UCS-2.

C-Kermit's TRANSLATE command can now be used to convert
traditional files to UCS-2 or UTF-8 (and, to the degree possible)
vice versa on the local computer.

C-Kermit now supports UTF-8 on either end (or both) of a terminal
session, allowing (for example) a Latin-1 xterm or a PC with Code Page 850
to connect to a remote UTF-8 platform such as Plan 9 and send and
receive accented Roman letters (ditto for Greek, Cyrillic, etc), and it also
allows a UTF-8 platform to connect to a "traditional" one.
CLICK HERE for UTF-8 sample text in many languages
(which will look right only if your Web browser supports UTF-8 and has a
well-populated Unicode font).

C-Kermit's TRANSMIT command can perform "ASCII" (nonprotocol)
uploads of text files, converting them to UTF-8 on the fly.
Or it can upload UTF-8 or UCS-2, converting it to some other set,
etc etc. Similarly, remote text files can be "captured" in the terminal
session with full translation.

Obviously when translating from Unicode to a smaller set, Unicode
characters that are not in the smaller set are lost.

You can download C-Kermit source and/or binaries in tar, zip, or other archive
format or as separate files. Install packages for selected platforms are also
available. You can also get everything at once on CDROM; CLICK HERE to order.

For maximum convenience, install packages are available for the
platforms listed below (C-Kermit 7.0 except where noted). All install packages
were built elsewhere and contributed to the Kermit archive; the exact contents,
configuration, build and installation options are determined by whoever made
each package.

(*) When you visit the Debian page, note that "Stable" and "Unstable" refer
to the Debian Linux release, not the C-Kermit release.
Choose 7.0.196, which currently happens to be marked "unstable", because it is
part of the next (stable) Debian Linux release.
(**) Up to date for most architectures; others will follow.
(***) Not yet updated to C-Kermit 7.0.

See the
ckuins.txt
file for greater detail (for example, instructions on how to install the
binary so it can access your dialout devices and UUCP lockfiles). See the
ckccfg.txt
file for information about compile-time options for customizing the feature set.

You can also download individual UNIX binaries from the
list below, but
in case of library or other version mismatches, it is better to build from
source if you can.

VMS instructions:

First fetch the most appropriate VMS binary from the
list below;
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).
After downloading the chosen binary, read the
ckvins.txt file.

If you want to build from source code, fetch the VMS ZIP archive
above if you have VMS-based unpacking tools,
otherwise get the source files individually as described just below.

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, etc. See the
ckaaaa.txt
file for details.

NOTE: The UNIX, VMS, VOS, Amiga, OS-9, and AOS/VS source files are all
at 7.0 level. The others (Macintosh, Atari ST) have not yet been
upgraded to 7.0. Volunteers welcome. And of course anybody interested
in porting C-Kermit to new platforms such as the IBM AS/400, Tandem, HP3000,
etc, are more than welcome to
contact us about it; we'll be
happy to get you started.

Individual binaries are available from the
kermit/bin/
directory for those who can not build from source code. A C-Kermit binary is
not a complete package; various text files (command and initialization files,
scripts, and documentation) are also needed. These are included in the
Zip and Tar archives.

Be sure to download C-Kermit binaries in binary (not ASCII or text)
mode. Those marked with "+" are current; those without the
"+" are from C-Kermit 7.0 test releases or, in some cases, C-Kermit
5A or 6.0; the C-Kermit edit number is visible in the first
part of the file name.

IMPORTANT: These files are not Windows files and do not follow
Windows naming conventions. You might need to right-click and choose "Save
Link As..." in your web browser to force download rather than some other
undesired action.

Naming Conventions:
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.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.

Then a possible test-version designator:
"a" for Alpha or "b" for Beta, followed by the 2-digit test number. Examples:

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 191, 193, 194, and 195 were never formally released.

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. "vms71"), and then
TCP/IP product and version number (or "nonet" if TCP/IP support is not built
in). And so on.

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 cku197.linux-i386-rh6.1 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).

Note that any executable C-Kermit 7.0 binary should also be accompanied
by an assortment of text files -- documentation updates, installation
instructions, hints and tips, etc; these are included in the tar and zip
archives listed in the previous section.

Notes on the Binaries:

"curses" refers to the fullscreen file-transfer display, used when
transferring files over dialout or network connections. It's nice but it
adds size and sometimes causes problems so if a "curses" version gives you
trouble, try a no-curses version. On platforms that have a choice between
"traditional curses" and "new curses" (ncurses), you might also have a choice
of binaries -- if one doesn't work, try the other.

Likewise, some binaries come in TCP/IP and non-TCP/IP versions. If you
don't need to make TCP/IP connections with C-Kermit, choose the non-TCP/IP
version (if available). A TCP/IP-enabled binary might not run on
platforms that don't have TCP/IP installed.

And some binaries come in optimized and non-optimized versions; this
refers to compile-time optimization. Choose the optimized version, but if it
gives you trouble, try the corresponding non-optimized one, if available (some
optimizers have bugs).

Some binaries are available in gcc and non-gcc versions; that is, versions
built using two different compilers. If one gives you trouble, try the other
if available. Some compilers have bugs; some compilers support features that
other ones don't.

Some HP-UX binaries (notably, the HP-UX 7.00 ones) are built for long
filename (255 chars) file systems, others for short-filename (14 chars)
systems. Choose the one that is appropriate for your file system.

Some Linux binaries are linked with libc, some with glibc. Pick the one
that is appropriate for your Linux system. Better yet, just build from source
("make linux" should work on any Linux system).

If you are able to make a binary not listed below
(or that is listed below, but without the "+"), please
contact us.

Stratus VOS binaries are structured objects
unsuitable for FTP. Those listed here have been encoded in text form; the
cklxtr.cm
macro extracts the binaries from the encoded versions. This can take a long
time, so more-efficient platform-specific decoder programs, also encoded in
hex format, can be downloaded, dehexified with cklxtr.cm, and then run to dehexify the larger VOS C-Kermit binary:
cklxtr-7100.hex,
cklxtr-i860.hex, and
cklxtr-m68k.hex.
You can also download VOS C-Kermit binaries in .save.evf.gz format
here.

C-Kermit 6.0 was the last version to be built in a
usable form on 2.11BSD. C-Kermit 7.0 is just too big. However, a small and
rather snappy remote-only version of G-Kermit is
now available for 2.11BSD. The cku192.sr file is the strings module for
C-Kermit 6.0; you need to get both files (in binary mode). See the
ckubs2.mak
file for details.

C-Kermit 7.0 is too big for the Tandy 16/6000; Version
6.0 works fine there. For remote-mode file transfers, use
G-Kermit, which loads much faster.

Works in remote mode; it is not known if it can dial
out. Does not include network or curses support.

Built on Sunsoft Interactive UNIX SV/386 R3.2 V4.1.1,
and identical to that version except that no dup2() system calls are
included, which cause core dumps on non-Interactive SV/386 R3.2 systems.
Therefore REDIRECT, EXEC, and similar functions are missing.