- 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.
DOCUMENTATION
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 continuted C-Kermit development and support.
Other resources:
- Security Features Documentation
- Telnet Client Documentation
- Internet Kermit Service User Documentation
- Internet Kermit Service Administrator Documentation
- C-Kermit 7.0 Bug List
- General C-Kermit "Beware File"
- UNIX Installation Instructions
- UNIX Beware File
- VMS Installation Instructions
- VMS Beware File
- VOS Installation Instructions
- VOS Beware File
HOW TO GET IT
There are several ways to get C-Kermit 7.0:
- 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 auxilliary 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
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:
- Cleaning Out Beta-Test Binaries (file management)
- Kerbang Scripts (script construction and argument passing)
- Autodownload (file transfer)
- Automatic Text/Binary Mode Switching (file transfer)
- Directory Recursion (file transfer and management)
- Streaming (file transfer)
- Internet Kermit Service (file transfer and management)
- Unicode (character sets)
- Printing (file transfer and management)
- Atomic File Movement (file transfer and management)
- C-Kermit Meets SSH (networking and security)
- C-Kermit's Telnet Client (networking)
- PPP Dialing (networking)
- Character Sets (file transfer)
- File Selection (file transfer and management)
- Bootstrapping (installation)
- Fun with Dates and Times (script programming)
- File Timestamps and Permissions (file transfer)
- An Easy Way to Get Files from IKSD (file transfer)
- Lynx/Kermit Coordination (Part I)
- Secure Telnet Using C-Kermit 7.1 With Stunnel
- More Fun with Dates
- Modem Pool Statistics
- (Check back later for more as we add new ones)
SUMMARY OF NEW FEATURES
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.
- Internet
- Internet Kermit Service Daemon (IKSD)
- IKSD active-session monitoring
- Kerberos IV, Kerberos V, and Secure Remote Password security
- SSL/TLS security
- HTTP client commands
- Connections via external programs like ssh or tn3270
- A new and improved Telnet protocol engine
- TELNET protocol option debugging
- Support for multihomed IP hosts / host pools
- Ability to accept incoming TCP connections in VMS and OS-9 (the UNIX version already could).
- General
- Command modifiers (switches).
- Patterns for filename and string matching.
- Command-line personalities (e.g. acts like telnet if called telnet).
- Autoup/download at the command prompt
- New built-in DIRECTORY command with numerous options.
- New SET OPTIONS command to customize directory-listing preferences.
- New PURGE command to remove (excess or all) backup files (UNIX).
- Consistent file-selection switches for SEND, DIR, DELETE, PURGE, etc.
- New notation for relative dates (+3days, -6months, yesterday, tomorrow) now accepted in any command where a date can be given, e.g. "delete /before:-5days *.txt" (or SEND, or DIR, etc).
- Editor and web browser interfaces.
- Base-64 file conversion
- New MANUAL command to access online man page, help topic, or manual.
- Updated installation instructions, hints & tips, etc, for each platform.
- Improved 'install' target in UNIX makefile.
- Making and Using Connections
- External communication program interface
- PPP dialing in UNIX
- Now you can give more than one number to the DIAL command
- Support for IBM AIXLink/X.25
- New support for 8 data bits + parity on serial connections (*).
- New ability to select number of stop bits on serial connections (*).
- Test dial procedures without actually dialing.
- Dialing improvements (10-digit dialing, blind dialing, PBXs, etc)
- SET DIAL MACRO for last-minute phone number manipulations (sample script)
- New all-purpose "generic-high-speed" modem type.
- SET DIAL METHOD AUTO defaults tone or pulse by country code.
- Better support for dialing without flow control.
- Automatic redial no longer unnecessarily re-initializes the modem.
- SET CLOSE-ON-DISCONNECT { ON, OFF } for serial connections.
- Transparent (host-controlled) printing in CONNECT mode.
- Improved reaction to carrier loss in VMS and UNIX.
- Higher serial speeds in VMS, IRIX, SCO, BSDI, Linux, . . .
- Hardware flow control for IRIX
- Streamlining and increased bulletproofing of Kermit/Modem dialog.
- Major improvements in UNIX UUCP lockfile handling for Linux, SCO, AIX, *BSD, . . .
(*) K95 and POSIX or SVR4-based UNIX versions only.
- New Built-In Modem Types
- "Generic High-Speed" modem with AT command set
- AT&T Keepintouch Card Modem.
- AT&T Secure Data STU III 1900 and 1910
- Atlas Newcom ixfC 33.6
- Best Data Fax Modem
- Compaq Data+Fax Modem
- Diamond SupraSonic 288V+
- Fujitsu Fax/Modem Adapter
- ITU-T (CCITT) V.250 (V.25ter) Command Set
- Megahertz AT&T V.34
- Megahertz X-Jack
- Multitech MT5634ZPX
- MicroLink 14.4, 28.8, 33.6, 56K
- MicroLink V.250
- Motorola Codex 326X Series
- Motorola Montana
- QuickComm Spirit II
- Rockwell V.90
- Rolm data phone with AT command set
- Supra Express V.90
- File Transfer and Management
- FAST Kermit protocol settings are now the default.
- Binary mode is now the default for file transfer, rather than text.
- File-transfer command switches (e.g. for file selection)
- File-transfer pipes and filters
- Automatic per-file text/binary mode switching (by name)
- Transfer and preservation of file permissions
- Ability to transfer directory trees even between unlike systems
- Longer wildcard expansion lists
- Improved performance and responsiveness
- Ability to move or rename each file after successful send or receive.
- Ability to in/exclude dot-files and backup files from file-transfer groups (UNIX).
- High-precision timers and statistics
- New display and log formats
- New options for coping with broken Kermit protocol partners
- Client/server
- New keepalive during long-running REMOTE HOST commands prevents timeouts.
- Longer REMOTE commands allowed.
- Server CD messages a`la FTP, local too.
- Additional GET options and combinations.
- REMOTE EXIT, REMOTE SET FILE CHARACTER-SET.
- R-command shortcuts for REMOTE commands (e.g. RCD for REMOTE CD).
- Numerous new file management commands and features
- Character Sets
- Automatic transfer/file character-set matching in file transfer.
- Unicode / ISO-10646 Universal Character Set
- Full conversion between Japanese character sets and Unicode
- KOI8-R (Russian) and KOI8-U (Ukrainian) character sets
- ISO 8859-7 Latin/Greek Alphabet (= ELOT 928)
- CP869 Greek code page (8 bit)
- ELOT 927 Greek (7 bit)
- ISO 8859-15 Latin Alphabet 9 (includes Euro and OE)
- Bulgaria-PC (code page)
- Mazovia (Polish PC code page)
- CP855 (Cyrillic PC code page)
- CP858 (West European PC code page, includes Euro)
- CP1250, 1251, 1252 (Windows code pages, include Euro)
- Logs
- New syslogging option for UNIX
- New connection log
- New brief transaction-log format option
- New FTPD-like transaction-log format option
- Time-critical debugging with millisecond timestamps.
- Unbuffered transaction log (e.g. for UNIX "tail -f")
- Script Programming
- A new general-purpose file i/o package added supporting multiple files open at once; character, line, and block i/o; sequential and random access; read, write, update, and append modes; absolute and relative seeks by line or byte, etc. (CLICK HERE for a sample script)
- Floating-point numbers and arithmetic (CLICK HERE for a sample script)
- Associative arrays (CLICK HERE for a sample script)
- Ability pass arguments to command files as well as macros
- Pattern matching in the [M]INPUT command
- Ability to pass more than ten arguments to a macro or command file
- Expanded command buffer length to allow bigger macros, variables, etc.
- Maximum number of macros increased.
- New support for compound Boolean expressions.
- "kerbang" scripts now take arguments from the command line.
- New built-in Array operations: COPY, RESIZE, CLEAR, SET, SORT, . . .
- SEND an array as if it were a file
- IF and XIF merged (so ugly XIF is no longer needed).
- Loading of arrays from DIRECTORY command file lists.
- New functions to load arrays with file or directory lists.
- New SCREEN command for screen clearing & cursor positioning.
- Date conversion functions (Julian dates, etc)
- New and improved built-in variables and functions
- Built-in help for functions
- Function and variable diagnostics
- Timed ASK commands
- New IF conditions
- Autodownload during INPUT command execution
- New OUTPUT command options
- Automatic arrays
- Array initializers
- Assignment operators
- New TRACE and SHOW STACK commands for debugging scripts.
- Visit the C-Kermit script library for samples
- Bug fixes
- Assorted problems with serial ports in UNIX and VMS
- Batch log echoing in VMS
- Problems with UNIX (UUCP) lockfiles, especially in HP-UX and AIX
- Broken CD command in VMS 6.2 and later on Alpha
- Failure to return proper exit status code under some conditions
- Failure to report exit status of external programs or commands
- Incorrect transfer of various oddball file formats in VMS
- Assorted problems with fullscreen file-transfer display
- Macro parameter substitution by empty values did not work
- Overzealous exit warnings
- Lots more
- New platforms
- IRIX 6.2, 6.3, 6.4, and 6.5
- AIX 4.2, 4.3 (including X.25 support)
- BeOS 4.5
- DG/UX 5.4R4.11
- Solaris 2.6 (including X.25 support)
- Solaris 7 and 8
- SCO OpenServer R5.0.0 through 5.0.5
- SCO Unixware 7
- HP-UX 10.01, 10.10, 10.20, 10.30, 11.00
- Trusted HP-UX
- Mac OS/X
- OPENSTEP 4.2
- Red Hat Linux 5.1 through 6.1
- Slackware Linux 3.5 through 7.0
- SuSE Linux 6.0
- MkLinux
- LinuxPPC
- Linux/390 on IBM mainframes
- New OpenBSD/NetBSD/FreeBSD versions
- Siemens Nixdorf Reliant UNIX 5.43 and 5.44
- Sequent DYNIX/ptx 4.4
- Stratus VOS with TCP/IP and X.25 support
- VMS 7.2
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.
INTERNET KERMIT SERVICE
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:
- Character-set translation
- Flexible file selection mechanisms (date, size, exception lists, etc)
- Preservation of timestamps and permissions
- Automatic per-file text/binary mode switching
- Cross-platform directory-tree transfer
- Filename collisions options (e.g. backup, update).
- Atomic file movement (delete or move source file iff transfer successful)
- Recovery of interrupted binary-mode transfers (*)
- File transfer through firewalls, proxies, or network address translators
- 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.
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).
The Kermit Project's IKSD is available for public access at:
kermit.columbia.edu 1649
Anonymous logins are welcome: give a user ID of "anonymous" or "ftp", and supply your email address as the password. You may log in interactively on a Telnet connection:
telnet kermit.columbia.edu 1649 Username: anonymous Password: abc@xyz.com
Or you can make a client/server connection as follows:
set host kermit.columbia.edu 1649 remote login anonymous abc@xyz.com
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.
Links:
EXTERNAL COMMUNICATION PROGRAM INTERFACE
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 cu -l tty04 pipe rlogin xyzcorp.com pipe srp-telnet xenon.stanford.edu pty ssh abccorp.com pty tn3270 cics.bigiron.com pty ftp hq.mycompany.com
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.
In fact, the PTY interface lets you script interactions with any local text-mode program: ftp, your shell, lpc, Lynx, IRC, various text editors, and so on. This feature is available in FreeBSD, NetBSD, OpenBSD, BSDI, Mac OS X, AIX 4.1 and later, DG/UX 5.4R4.11, Digital UNIX 3.2 and 4.0, HP-UX 9.00 and later, IRIX 6.0 and later, Linux, NeXTSTEP 3.x, QNX 4.25, SCO OSR5.0.5, SCO Unixware 7, SINIX 5.42, Solaris 2.x and 7, and SunOS 4.1.3.
[ Top ] [ Case Study ] [ Download ]
SECURITY AND PRIVACY
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:
ftp://ftp.runestig.com/pub/starttls/inetutils-1.3.2-tls.tar.gz
SSL/TLS connections may also be used to connect to Secure Web Servers for use with the new HTTP commands:
SET HOST host https /SSL SET HOST host https /TLS
or between two C-Kermits to establish a private connection:
SET HOST * port /SSL <--- Server SET HOST host port /SSL <--- Client
[ Top ] [ Download ] [ Documentation of security features ]
HTTP CLIENT COMMANDS
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.
NEW TELNET ENGINE
C-Kermit 7.0 includes a new Telnet protocol engine incorporating:
- Proper treatment of required replies
- Support for authentication and encryption
- Negotiations now done at SET HOST time allow testing by IF SUCCESS
- Telnet negotiations now handled during file transfer
- New Telnet protocol options
- Settable policies for each Telnet option in each direction
- Server-side Telnet protocol for incoming connections
- Realtime monitoring of Telnet protocol options
Links:
[ Top ] [ Case Study ] [ Download ]
PPP DIALING
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:
ask \%u { User: }
askq \%p { Password: }
set modem type usr ; Specify the kind of modem you have
set line /dev/ttyS1 ; Specify the device it's connected to
set speed 57600 ; and the speed
set flow rts/cts ; and flow control.
set dial retries 100 ; Try the dial sequence up to 100 times.
dial {{9-212-555-1212}{9-212-555-1213}{9-212-555-1214}{9-212-555-1215}}
if fail exit 1
for \%i 1 16 1 { ; Try up to 16 times to get login prompt
input 10 Login: ; Wait 10 sec for it to appear
if success break ; Got it - proceed...
output \13 ; Send a carriage return and try again
}
if ( > \%i 16 ) stop 1 NO LOGIN PROMPT
lineout \%u ; Send user ID
input 30 assword: ; Wait for Password prompt
if fail stop 1 NO PASSWORD PROMPT
lineout \%p ; Send the password.
exec /redirect pppd ; Replace ourselves with pppd.
Notice the advantages over the well-known PPP "chat script":
- You don't have to control the modem itself with AT commands; Kermit's
DIAL command does this for you.
- You can have Kermit automatically redial as many times as you want
until it gets a connection (if this is legal in your country).
- You can have Kermit fetch the number or numbers from a dialing directory.
- You can have Kermit cycle through a list of phone numbers (another new
feature of C-Kermit 7.0) without having to enter the numbers in a dialing
directory first.
- Dialing is location-independent; you can use the same script to dial from
different areas or countries.
Changing modem types is a simple matter of changing the name in the "set modem type" command.
- Once the connection is made, the full power of Kermit's script language is available to manage the dialog with the terminal server or other device that answers the phone call.
[ Top ] [ Case Study ] [ Download ]
COMMAND SWITCHES
C-Kermit 7.0 allows for optional command modifiers called switches.
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:
send oofa.txt ; No switches send /binary oofa.zip ; A switch without a value send /protocol:zmodem oofa.zip ; A switch with a value send /text /delete /as-name:x.x oofa.txt ; Several switchesSwitches bring a new level of flexibility to Kermit's command language. For example, they can be used for file selection in file-transfer commands:
send /after:8-Feb-1998_10:28:01 /larger-than:10000 /except:*.log *.*or for disposition of the source file after transfer:
send /binary /delete *.zipor for mailing or printing:
send /mail /subject:{Here is the recipe you wanted} lasagna.txt
send /print:{-PLaserWriter2 -#3} lasagna.ps
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.
PATTERN MATCHING
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.
BINARY MODE IS NOW DEFAULT
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.
AUTOMATIC TEXT/BINARY-MODE SWITCHING
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.)
[ Top ] [ Case Study ] [ Download ]
PRESERVATION OF FILE PERMISSIONS
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).
[ Top ] [ Case Study ] [ Download ]
DIRECTORY-TREE TRANSFER
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.
[ Top ] [ Case Study ] [ Download ]
FILE-TRANSFER PIPES AND FILTERS
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.
PERFORMANCE
File-transfer performance has been improved in several ways:
- Internal tuning
- A new ability to "unprefix" the ASCII NUL (0) character
- A new "streaming" form of the Kermit protocol for use over reliable connections
- Quicker startup of autodownloads
- Fast Kermit protocol settings (long packets, sliding windows, conservative control-character unprefixing) are now the default
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):
SENDING wart (binary) (23985 bytes): OK (0.040 sec, 599625 cps) SENDING wermit (binary) (1323517 bytes): OK (4.490 sec, 294769 cps) SENDING ckcnet.c (text) (269168 bytes): OK (0.790 sec, 340718 cps) SENDING ckwart.o (binary) (25332 bytes): OK (0.040 sec, 633299 cps) SENDING ckufio.c (text) (112341 bytes): OK (0.290 sec, 387382 cps) SENDING ckuusr.o (binary) (132340 bytes): OK (0.180 sec, 735222 cps) SENDING ckuus2.o (binary) (183168 bytes): OK (0.300 sec, 610559 cps) SENDING ckuus3.o (binary) (154492 bytes): OK (0.200 sec, 772459 cps) SENDING ckuus6.o (binary) (133128 bytes): OK (0.180 sec, 739599 cps)
C-Kermit 7.0 also responds much more quickly to connection loss and external interruptions during file transfer.
FAST OUT OF THE BOX
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.
UNICODE
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.
[ Top ] [ Case Study ]
DOWNLOAD
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.
INSTALL PACKAGES
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.
- Red Hat Linux 6.0 and later RPM for Intel CPUs (PCs)
- Red Hat Linux 6.0 and later RPM for Alpha CPUs
- Red Hat Linux 6.0 and later RPM for Sparc CPUs
- Red Hat Linux 6.0 and later RPM for the IBM System/390
- Red Hat Linux C-Kermit 7.0 source archive RPM
- SuSE Linux 6.4 for Intel (glibc)
- SuSE Linux 6.4 for Alpha (glibc)
- SuSE Linux 6.3 for Intel (glibc)
- SuSE Linux 6.3 for Alpha (glibc)
- SuSE Linux 6.3 for PowerPC (glibc)
- SuSE Linux 6.2 for Intel (glibc)
- SuSE Linux 6.1 for Intel (glibc)
- SuSE Linux 6.1 for Alpha (glibc)
- SuSE Linux 5.3 for Intel (libc5)
- The FreeBSD ports collection
- Debian GNU/Linux packages (*)
- The NetBSD packages collection (**)
- The OpenBSD CVS Repository (***)
- MacOS X Server 1.0
- OPENSTEP 4.2 Mach/SPARC
- Stratus VOS Binaries Bundle
in save.evf.gz format: C-Kermit 7.0 binaries for VOS 13.3.3 on Continuum, i860, and mc68k.
(*) 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.
CLICK HERE for guidelines on making C-Kermit install packages.
SOURCE-CODE ARCHIVES
You can also download C-Kermit 7.0 directly from the Kermit Project in any of several archive formats via anonymous ftp by clicking on the following links:
- cku197.tar.Z
- Source code and text files for UNIX, UNIX tar archive, compress format.
- cku197.tar.gz
- Source code and text files for UNIX, UNIX tar archive, gzip format.
- cku197.zip
- Source code and text files for UNIX, ZIP archive (text files in DOS format).
- ckv197.zip
- Source code and text files for VMS, ZIP archive (text files in DOS format).
- ckl197.zip
- Source code and text files for Stratus VOS, ZIP archive (text files in DOS format).
- ck9197.zip
- Source code and text files for Microware OS-9, ZIP archive (text files in DOS format).
- Secure version
- Kerberos, SSL/TLS, and SRP enabled version, UNIX only, source-code archive, tar.gz format, USA and Canada only.
These archives contain complete source code for the platforms indicated as well as documentation updates, installation instructions, hints and tips files, initialization files, scripts, demos, etc.
- Trouble with FTP?
- o CLICK HERE for FTP hints and tips; or:
- o Forget FTP -- Use Kermit!
- UNIX instructions:
- Download the desired zip or compressed tar archive from the
list above into an empty directory. Then:
- uncompress (uncompress, gunzip, unzip, etc, as appropriate)
- if it's a tar file, untar ("tar xvf cku197.tar");
- "make xxx", where xxx is the appropriate target from the makefile for your platform (read the comments at the top of the makefile).
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.
[ Top ]
INDIVIDUAL BINARIES
[ Go straight to binaries list ]
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.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.
cku196.xxx C-Kermit 7.0.196 final release cku197.xxx C-Kermit 7.0.197 (a platform added after 7.0.196 came out) cku196b11.xxx C-Kermit 7.0.196 Beta.11 cku192.xxx C-Kermit 6.0.192 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 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.
Filename Description ---------------------------------------------------------------------- + ck9196.os9-2.3-nonet OS-9/68K 2.3 (no TCP/IP) + ck9196.os9-3.0.3-net OS-9/68K 3.0.3 (with TCP/IP), 68020 or higher ck9192.os9-2.4 OS-9/68K 2.4 ck9192.os9-2.4-nocsl OS-9/68K 2.4 ck9193a13-os9-2.4-net OS-9/68K 2.4 (with TCP/IP) ck9192.os9-3.0 OS-9/68K 3.0 ---------------------------------------------------------------------- + ckd196-aosvsii-2.20.73.pr DG MV 2500 AOS/VS-II 2.20.73 ckd192-aosvs-07.69.00.13.pr DG MV xxxx AOS/VS Classic 07.69.00.13 ---------------------------------------------------------------------- + ckl196-i860-vos1333.hex Stratus XA/R (Intel 860) VOS 13.3.3 + ckl196-m68k-vos1333.hex Stratus XA2000 (Motorola 680x0) VOS 13.3.3 + ckl196-7100-vos1333.hex Stratus Continuum (PA-RISC) VOS 13.3.3 + ckl196-7100-vos1401.hex Stratus Continuum VOS 14.0.1 + ckl196-7100-vos1402g.hex Stratus Continuum VOS 14.0.2g + ckl196-7100-vos1410ac.hex Stratus Continuum VOS 14.1.0ac + ckl196-7100-vos1420aa.hex Stratus Continuum VOS 14.2.0aa cklxtr.cm Decoder macro for Stratus binaries (1) ---------------------------------------------------------------------- cku192.bebox BeBox, BeOS DR7 + cku196.beos45-bebox BeBox, BeOS 4.5 (4) + cku196.beos45-i386 PC, BeOS 4.5 (4) ---------------------------------------------------------------------- + cki196.exe Commodore Amiga, AmigaDOS 3.1 or higher ---------------------------------------------------------------------- cks189.ttp Atari ST Interactive Version cks189ncp.ttp Atari ST Command-Line Only ---------------------------------------------------------------------- + ckp196.plan9-m68k Plan 9 from Bell Labs on Motorola 680x0 + ckp196.plan9-i386 Plan 9 from Bell Labs on PC + ckp196.plan9-mips Plan 9 from Bell Labs on MIPS + ckp196.plan9-sparc Plan 9 from Bell Labs on Sparc ---------------------------------------------------------------------- cku188.aegis Apollo Domain, Aegis cku193a05.apollo-sr10-s5r3 Apollo Domain, SR10.0/SVR3 cku188.auxc Apple Macintosh, AUX (with curses) + cku196.macosx10-ppc-1.0 Apple PowerBook G3, Mac OS X 1.0 (no curses) + cku196.macosx10c-ppc-1.0 Apple PowerBook G3, Mac OS X 1.0 (curses) cku196b10.macosx10nc-ppc-1.0 Apple PowerBook G3, Mac OS X 1.0 (ncurses) + cku196.linux-ppc-db2.2 Apple Power Mac, Linux Debian 2.2 + cku197.linux-ppc-su6.3 Apple Power Macintosh, Linux, SuSE 6.3 (glibc) + cku196.linuxppc-ppc-1999q2 Apple PowerBook G3, LinuxPPC 1999 Q2 cku195b06.mklinux-ppc-dr3 Apple Power Macintosh, MkLinux DR3 + cku196.mklinux-ppc-pre-r1 Apple Power Macintosh, MkLinux Pre-R1 + cku196.att3b2 AT&T 3B/300 System V R3 + cku196.att3bx1 AT&T 3B/300 System V R3 (charsets but no curses) + cku196.att3bxc3 AT&T 3B/300 System V R3 (curses but no charsets) + cku196.sys3upcg AT&T 7300 UNIX PC (no curses) + cku196.sys3upcgm AT&T 7300 UNIX PC (no curses, minimum features) + cku196.sys3upcgc AT&T 7300 UNIX PC (with curses) + cku196.sys3upcgfd AT&T 7300 UNIX PC (with curses, compact version) + cku196.att351gm AT&T 7300 UNIX PC (hardware flow control) cku190.svr4amiganet Commodore Amiga, System V R4 + TCP/IP cku193b05.linux-2.0.33-m68k Commodore Amiga, Linux 2.0.33 RH 5.0 cku189.unicos7c Cray C90, Unicos 7 cku189.unicos7y Cray YMP, Unicos 7 cku192.dgux540c-88k Data General AViioN 88xxx, DG/UX 5.40 + cku196.dgux54310-m88k Data General AViiON 88110, DG/UX 5.4R3.10 + cku196.dgux54411-m88k Data General AViiON 88110, DG/UX 5.4R4.11 + cku196.dec-osf13 DEC Alpha OSF/1 1.3 cku190.dec-osf20 DEC Alpha OSF/1 2.0 cku192.dec-osf30 DEC Alpha OSF/1 3.0 cku196b10.dec-osf30 DEC Alpha OSF/1 3.0 + cku196.du32 DEC Alpha Digital UNIX 3.2 cku192.du40 DEC Alpha Digital UNIX 4.0 + cku196.du40-4.0b DEC Alpha Digital UNIX 4.0B + cku196.du40-4.0c DEC Alpha Digital UNIX 4.0C + cku196.du40-4.0d DEC Alpha Digital UNIX 4.0D + cku196.tru64-4.0e DEC Alpha Compaq Tru64 UNIX 4.0E + cku196.tru64-4.0f DEC Alpha Compaq Tru64 UNIX 4.0F + cku196.tru64-4.0g DEC Alpha Compaq Tru64 UNIX 4.0G + cku196.tru64-5.0 DEC Alpha Compaq Tru64 UNIX 5.0 + cku196.freebsd-alpha-3.4 DEC Alpha FreeBSD 3.4 + cku196.netbsd-alpha-1.4 DEC Alpha NetBSD 1.4 + cku196.linux-alpha-db2.2 DEC Alpha, Linux, Debian 2.2 + cku196.linux-alpha-rh5.2 DEC Alpha, Linux, Red Hat 5.2 + cku196.linux-alpha-rh6.1 DEC Alpha, Linux, Red Hat 6.1 + cku197.linux-alpha-su6.1 DEC Alpha, Linux, SuSE 6.1 + cku197.linux-alpha-su6.3 DEC Alpha, Linux, SuSE v6.3 + cku197.linux-alpha-su6.4 DEC Alpha, Linux, SuSE 6.4 cku192.bsd211 DEC PDP-11, 2.11BSD (interactive) (2) cku192.sr DEC PDP-11, 2.11BSD (strings module) (2) + cku196.netbsd-mips-1.4.1 DECstation 5000, NetBSD 1.4.1 + cku196.ultrix43-mips DECstation 5000, Ultrix 4.3 + cku196.ultrix43notcp-mips DECstation 5000, Ultrix 4.3, no TCP/IP + cku196.ultrix44-mips DECstation 5000, Ultrix 4.4 cku192.ultrix45-mips DECstation 5000, Ultrix 4.5 cku192.bellv10-vax DEC MicroVAX-II, Bell Research UNIX V10 + cku196.bsd42c-vax DEC VAX, 4.2BSD, full interactive, TCP/IP, curses + cku196.bsd43c-vax DEC VAX, 4.3BSD, full interactive, TCP/IP, curses + cku196.bsdm-vax DEC VAX, 4.3BSD, command-line only, TCP/IP + cku197.ultrix3x-vax-3.0 DEC VAX, Ultrix 3.0, TCP/IP + cku197.ultrix45-vax DEC VAX, Ultrix 4.5, TCP/IP cku192.bsd44c-hp9000-300 HP-9000/300 4.4BSD-Lite cku193b05.bsd44-hp9000-300 HP-9000/300 4.4BSD-Lite + cku196.hpux500-s550-5.21 HP-9000/550 HP-UX 5.21 no TCP/IP + cku196.hpux500wintcp-s550-5.21 HP-9000/550 HP-UX 5.21 TWG-TCP/IP 1.2 + cku196.hpux65-s300-6.5 HP-9000/3xx HP-UX 6.5 + cku196.hpux65c-s300-6.5 HP-9000/3xx HP-UX 6.5, curses + cku196.hpux65o-s300-6.5 HP-9000/3xx HP-UX 6.5, optimized + cku196.hpux65oc-s300-6.5 HP-9000/3xx HP-UX 6.5, curses, optimized + cku196.hpux70lfn-s300-7.05 HP-9000/3xx HP-UX 7.05, long filenames (LFN) + cku196.hpux70lfnc-s300-7.05 HP-9000/3xx HP-UX 7.05, LFN, curses + cku196.hpux70olfn-s300-7.05 HP-9000/3xx HP-UX 7.05, LFN, optimized + cku196.hpux70olfnc-s300-7.05 HP-9000/3xx HP-UX 7.05, LFN, curses, optimized + cku196.hpux70sf-s300-7.05 HP-9000/3xx HP-UX 7.05, short filenames (SFN) + cku196.hpux70sftcpc-s300-7.05 HP-9000/3xx HP-UX 7.05, SFN, TCP + cku196.hpux70osf-s300-7.05 HP-9000/3xx HP-UX 7.05, SFN, optimized + cku196.hpux70osftcpc-s300-7.05 HP-9000/3xx HP-UX 7.05, SFN, TCP, optimized + cku196.hpux80notcp-s300-8.00 HP-9000/3xx HP-UX 8.00, no TCP/IP + cku196.hpux80notcp-s400-8.00 HP-9000/4xx HP-UX 8.00, no TCP/IP + cku196.hpux80onotcp-s400-8.00 HP-9000/4xx HP-UX 8.00, optimized, no TCP/IP + cku196.hpux80-s300-8.00 HP-9000/3xx HP-UX 8.00, no curses + cku196.hpux80-s400-8.00 HP-9000/4xx HP-UX 8.00, no curses + cku196.hpux80c-s400-8.00 HP-9000/4xx HP-UX 8.00, curses + cku196.hpux80c-s300-8.00 HP-9000/3xx HP-UX 8.00, curses + cku196.hpux80o-s300-8.00 HP-9000/3xx HP-UX 8.00, no curses, optimized + cku196.hpux80o-s400-8.00 HP-9000/4xx HP-UX 8.00, no curses, optimized + cku196.hpux80oc-s300-8.00 HP-9000/3xx HP-UX 8.00, curses, optimized + cku196.hpux80oc-s400-8.00 HP-9000/4xx HP-UX 8.00, curses, optimized + cku196.hpux90-s300-9.03 HP-9000/340 HP-UX 9.03 + cku196.hpux90m68ko-s300-9.03 HP-9000/340 HP-UX 9.03 cku195b07.hpux90-s800-9.04 HP-9000/8xx HP-UX 9.04 + cku196.hpux90-s700-9.05 HP-9000/712 HP-UX 9.05 + cku196.hpux90o-s700-9.05 HP-9000/712 HP-UX 9.05, optimized + cku196.hpux90o700-s700-9.05 HP-9000/712 HP-UX 9.05, optimized for s700 + cku196.hpux90-s300-9.10 HP-9000/340 HP-UX 9.10 + cku196.hpux90m68ko-s300-9.10 HP-9000/340 HP-UX 9.10 + cku196.hpux100-s700-10.01 HP-9000/735 HP-UX 10.01 + cku196.hpux100o-s700-10.01 HP-9000/735 HP-UX 10.01, optimized cku195b08.hpux100-s800-10.10 HP-9000/847 HP-UX 10.10 cku192.hpux100-s700-10.10 HP-9000/7xx HP-UX 10.10 + cku196.hpux100-s800-10.10 HP-9000/8xx HP-UX 10.10 cku192.hpux100o-s700-10.10 HP-9000/7xx HP-UX 10.10, optimized cku192.hpux100o-s800-10.10 HP-9000/8xx HP-UX 10.10, optimized + cku196.hpux100-s700-10.20 HP-9000/715 HP-UX 10.20 + cku196.hpux100o-s700-10.20 HP-9000/715 HP-UX 10.20, optimized + cku197.hpux100o+s700-10.20 HP-9000/725 HP-UX 10.20, highly optimized + cku196.hpux100-s800-10.20 HP-9000/8xx HP-UX 10.20 + cku196.hpux100o-s800-10.20 HP-9000/8xx HP-UX 10.20, optimized + cku196.hpux100o+-s800-10.20 HP-9000/8xx HP-UX 10.20, highly optimized + cku196.hpux100o+nolimit-s800-10.20 HP-9000/8xx HP-UX 10.20, very highly optimized + cku196.hpux100t-s800-10.20 HP-9000/8xx Trusted HP-UX 10.20 + cku196.hpux100to-s800-10.20 HP-9000/8xx Trusted HP-UX 10.20, optimized + cku196.hpux100to+-s800-10.20 HP-9000/8xx Trusted HP-UX 10.20, highly optimized + cku196.hpux100to+nolimit+s800-10.20 HP-9000/8xx Trusted HP-UX 10.20, very highly optimized cku192.hpux100o-s800-10.30 HP-9000/7xx HP-UX 10.30, optimized cku195b07.hpux100-s700-10.30 HP-9000/G70 HP-UX 10.30 cku195b07.hpux100o+s700-10.30 HP-9000/G70 HP-UX 10.30, highly optimized + cku196.hpux1100-s700-11.00 HP-9000/715 HP-UX 11.00 + cku196.hpux1100-s800-11.00 HP-9000/8xx HP-UX 11.00 + cku196.ps2aix-1.2.1 IBM PS/2 AIX 1.2.1 + cku196.rtaixc-2.2.1 IBM RT PC AIX 2.2.1 cku192.rs6000c-3.1.5 IBM RS/6000 AIX 3.1.5 + cku196.aix32-3.2.0 IBM RS/6000 AIX 3.2.0 cku192.rs6aix32c-3.2.2 IBM RS/6000 AIX 3.2.2 cku190.rs6aix32c-3.2.4 IBM RS/6000 AIX 3.2.4 + cku196.aix32-3.2.5 IBM RS/6000 AIX 3.2.5 + cku196.aix41-4.1.3 IBM RS/6000 AIX 4.1.3 cku192.rs6aix41c-4.1.4 IBM RS/6000 AIX 4.1.4 + cku196.rs6aix41c-4.1.5 IBM RS/6000 AIX 4.1.5 cku192.rs6aix41c-4.2 IBM RS/6000 AIX 4.2 + cku196.aix42-4.2.1 IBM RS/6000 AIX 4.2.1 cku195b04.aix43-4.3.0 IBM RS/6000 AIX 4.3.0 + cku196.aix43-4.3.1 IBM RS/6000 AIX 4.3.1 + cku196.aix43-4.3.2 IBM RS/6000 AIX 4.3.2 + cku196.aix43-4.3.3 IBM RS/6000 AIX 4.3.3 + cku196.linux-s390-linux390 IBM System/390, Linux/390 cku196b10.iclsys5r4m+ ICL DRS6000 (Sparc) UNIX 4.2MP 7MPLUS.11.2 + cku196.clix-3.1 Intergraph Clipper CLIX 3.1 (no TCP/IP) + cku196.clixnet-3.1 Intergraph Clipper CLIX 3.1 (with TCP/IP) + cku196.linux-m68k-db2.1 Motorola 680x0, Linux Debian 2.1 + cku196.linux-m68k-db2.2 Motorola 680x0 (Amiga 3000), Linux Debian 2.2 + cku196.netbsd-m68k-1.4.2a Motorola 680x0, NetBSD 1.4.2-Alpha + cku196.sv68r3v6 Motorola MVME 147 68K, System V/68 R3V6 cku192.sv88r32 Motorola MVME 197 88K, System V R4 V3.2 + cku196.sv88r40-4.3 Motorola MVME 197 88K, System V R4 V4.3 + cku196.sv88r40-4.4 Motorola MVME 197 88K, System V R4 V4.4 + cku196.next-m68k-3.1 NeXT 68040 NeXTSTEP 3.1 cku193b05.next-3.2-m68k NeXT 68040 NeXTSTEP 3.2 + cku196.next33-m68k-3.3 NeXT 68040 NeXTSTEP 3.3 + cku196.openstep42-m68k NeXT 68040 OPENSTEP 4.2 + cku196.ps2aixnetc-1.2.1 PC (IBM PS/2) AIX 1.2.1 + TCP/IP + curses + cku197.sys5r32is PC, AT&T System V/386 R3.2 (no TCP/IP) (5) + cku197.sys5r32isnet PC, AT&T System V/386 R3.2 (with TCP/IP) (5) cku190.bsdi-1.0 PC, BSDI 1.0 cku192.bsdi2-2.1 PC, BSDI 2.1 cku193a10.bsdi2-2.1 PC, BSDI 2.1 cku193a10.bsdi2-3.0 PC, BSDI 3.0 cku196b10.bsdi3-3.1 PC, BSDI 3.1 + cku196.bsdi4-4.0.1 PC, BSDI 4.0.1 + cku197.bsdi4-4.1 PC, BSDI 4.1 + cku196.coherent42 PC, Coherent 4.2.10 cku192.dgux540i PC, DG/UX 5.40, no curses cku192.dgux540ic PC, DG/UX 5.40, curses cku195b05.dgux54411-i386 PC, DG/UX 5.4R4.11 + cku196.dgux54420-i386 PC, DG/UX 5.4R4.20 cku196b10.dynixptx20c PC/486, Sequent DYNIX/ptx 2.0 cku196b10.dynixptx216c-i486 PC/486, Sequent DYNIX/ptx 2.1.6 cku196b10.dynixptx216cgcc-i386 PC/386, Sequent DYNIX/ptx 2.1.6 cku196b10.dynixptx216cgcc-i486 PC/486, Sequent DYNIX/ptx 2.1.6 + cku196.dynixptx44-i386-4.4.2 PC/386, Sequent DYNIX/ptx 4.4.2 cku192.esix PC, ESIX 4.0.4 cku196b11.freebsd2-i386-2.2.7 PC, FreeBSD 2.2.7 (ncurses) cku196b11.freebsd2c-i386-2.2.7 PC, FreeBSD 2.2.7 (curses) + cku196.freebsd2-i386-2.2.8 PC, FreeBSD 2.2.8 (ncurses) + cku196.freebsd2c-i386-2.2.8 PC, FreeBSD 2.2.8 (curses) + cku196.freebsd3-i386-3.1 PC, FreeBSD 3.1 (ncurses) + cku196.freebsd3-i386-3.3 PC, FreeBSD 3.3 (ncurses) + cku196.freebsd3c-i386-3.3 PC, FreeBSD 3.3 (curses) + cku197.freebsd3-i386-3.4 PC, FreeBSD 3.4 (ncurses) + cku196.freebsd3-i386-4.0 PC, FreeBSD 4.0 (ncurses) cku192.iclsys5r4 PC, ICL System V R4 cku190.is5r3jc PC, Interactive UNIX System V/386 R3.2v2.2 (no TCP/IP) cku192.is5r3jc PC, Interactive UNIX System V/386 R3.2v4.1a (no TCP/IP) cku192.is5r3netjc PC, Interactive UNIX System V/386 R3.2v4.1a (TCP/IP) + cku197.is5r3jc PC, Interactive UNIX System V/386 R3.2v4.1.1 (no TCP/IP) + cku197.is5r3netjc PC, Interactive UNIX System V/386 R3.2v4.1.1 (TCP/IP) + cku196.linux-i386-db2.1 PC, Linux Debian 2.1 cku193b05.linux-i386-rh3.0.3 PC, Linux Red Hat 3.0.3 cku195b03.linux-i386-rh4.2 PC, Linux Red Hat 4.2 (libc5) + cku196.linux-i386-rh5.1 PC, Linux Red Hat 5.1 (glibc, ncurses) + cku196.linux-i386-rh5.2 PC, Linux Red Hat 5.2 (glibc, ncurses) + cku196.linuxc-i386-rh5.2 PC, Linux Red Hat 5.2 (glibc, curses) + cku196.linuxnc-i386-rh5.2 PC, Linux Red Hat 5.2 (glibc, no curses) + cku196.linuxnotcp-i386-rh5.2 PC, Linux Red Hat 5.2 (glibc, no TCP/IP) + cku197.linux-i386-rh6.0 PC, Linux Red Hat 6.0 (glibc, ncurses) + cku196.linux-i386-rh6.1 PC, Linux Red Hat 6.1 (glibc, ncurses) + cku196.linuxc-i386-rh6.1 PC, Linux Red Hat 6.1 (glibc, curses) + cku196.linuxnc-i386-rh6.1 PC, Linux Red Hat 6.1 (glibc, no curses) + cku196.linux-i386-sw3.5 PC, Linux Slackware 3.5 (libc5) + cku196.linux-i386-sw3.6 PC, Linux Slackware 3.6 (libc5) + cku196.linux-i386-sw4.0 PC, Linux Slackware 4.0 (libc5) + cku196.linux-i386-sw7.0 PC, Linux Slackware 7.0 (glibc) + cku197.linux-i386-su5.3 PC, Linux SuSE 5.3 (libc5) + cku197.linux-i386-su6.1 PC, Linux SuSE 6.1 (glibc) + cku197.linux-i386-su6.2 PC, Linux SuSE 6.2 (glibc) + cku197.linux-i386-su6.3 PC, Linux SuSE 6.3 (glibc) + cku197.linux-i386-su6.4 PC, Linux SuSE 6.4 (glibc) cku144.mpsysv PC, Microport UNIX + cku196.minix20 PC, Minix 2.0.2 (32-bit) + cku196.mpras-i386-2.03 PC, NCR MP-RAS 2.03 + cku196.mprastcpc-i386-2.03 PC, NCR MP-RAS 2.03 + curses + TCP/IP + cku196.mpras-i386-3.02 PC, NCR MP-RAS 3.02 + cku196.mpras-i386-3.02-gcc PC, NCR MP-RAS 3.02 (gcc) + cku196.mprastcpc-i386-3.02 PC, NCR MP-RAS 3.02 + curses + TCP/IP + cku196.mprastcpc-i386-3.02-gcc PC, NCR MP-RAS 3.02 + curses + TCP/IP (gcc) cku192.netbsd-i386-1.2 PC, NetBSD 1.2 cku196b10.netbsd-i386-1.3.3 PC, NetBSD 1.3.3 cku196b10.netbsd14-i386-1.4 PC, NetBSD 1.4 + cku196.netbsdn-i386-1.4p PC, NetBSD 1.4P (ELF binary) + cku196.netbsd-i386-1.4.2a PC, NetBSD 1.4.1-Alpha + cku196.netbsd-i386-1.4.1 PC, NetBSD 1.4.1 (curses) + cku196.netbsdnoiksd-i386-1.4.1 PC, NetBSD 1.4.1 (no IKSD) + cku196.netbsdn-i386-1.4.1 PC, NetBSD 1.4.1 (ncurses) cku190.next-i486 PC, NeXTSTEP 3.1 cku195b04.openbsd-i386-2.3 PC, OpenBSD 2.3 cku195b07.openbsd-i386-2.4 PC, OpenBSD 2.4 + cku196.openbsd-i386-2.5 PC, OpenBSD 2.5 + cku196.openstep42-i386 PC, OPENSTEP 4.2 cku192.qnx16-4.21 PC, QNX 4.21 16-bit cku192.qnx32-4.21 PC, QNX 4.21 32-bit + cku195b10+.qnx16-4.25 PC, QNX 4.25 16-bit + cku196.qnx32-4.25 PC, QNX 4.25 32-bit + cku196.qnx32nonet-4.25 PC, QNX 4.25 32-bit, no TCP/IP + cku197.qnx-nto2+ PC, QNX Neutrino 2+ cku192.sco286 PC, SCO XENIX/286 2.2.1 cku190b02.sco386netc-2.2.3 PC, SCO XENIX/386 2.2.3 + Excelan TCP/IP cku192.sco3r2lai PC, SCO XENIX/386 2.3.3 (+ SCO TCP/IP) + cku196.sco234 PC, SCO XENIX/386 2.3.4 (no TCP/IP or curses) + cku196.sco234c PC, SCO XENIX/386 2.3.4 (curses but no TCP/IP) + cku196.sco234netc PC, SCO XENIX/386 2.3.4 (curses + SCO TCP/IP) cku190.sco3r2 PC, SCO UNIX/386 3.2.0 (no TCP/IP) cku190.sco3r2netnd PC, SCO UNIX/386 3.2.0 (with SCO TCP/IP) + cku196.sco32v4ns-4.0 PC, SCO UNIX/386 3.2v4.0 (no TCP/IP) + cku196.sco-odt20 PC, SCO ODT 2.0 (SCO UNIX 3.2v4.0 with SCO TCP/IP) cku192.sco-odt30 PC, SCO ODT 3.0 (SCO UNIX 3.2v4.2 with SCO TCP/IP) + cku196.sco32v4-4.2 PC, SCO UNIX/386 3.2v4.2 (no TCP/IP) + cku196.sco32v4ns-4.2 PC, SCO UNIX/386 3.2v4.2 (definitely no TCP/IP) + cku196.sco32v4net-4.2 PC, SCO UNIX/386 3.2v4.2 (with TCP/IP) + cku196.sco32v4gcc-4.2 PC, SCO UNIX/386 3.2v4.2 (gcc, no TCP/IP) + cku196.sco32v4netgcc-4.2 PC, SCO UNIX/386 3.2v4.2 (gcc, with TCP/IP) + cku196.sco32v500 PC, SCO OpenServer 5.0.0 (no TCP/IP) + cku196.sco32v500net PC, SCO OpenServer 5.0.0 + TCP/IP cku192.sco32v500gcc PC, SCO OpenServer 5.0.0 (no TCP/IP) (gcc) cku192.sco32v500netgcc PC, SCO OpenServer 5.0.0 + TCP/IP (gcc) + cku196.sco32v502 PC, SCO OpenServer 5.0.2 (no TCP/IP) + cku196.sco32v502net PC, SCO OpenServer 5.0.2 (with TCP/IP) + cku196.sco32v504 PC, SCO OpenServer 5.0.4 (no TCP/IP) + cku196.sco32v504gcc PC, SCO OpenServer 5.0.4 (gcc, no TCP/IP) + cku196.sco32v504net PC, SCO OpenServer 5.0.4 (with TCP/IP) + cku196.sco32v504netgcc PC, SCO OpenServer 5.0.4 (gcc, TCP/IP) + cku196.sco32v505 PC, SCO OpenServer 5.0.5 (no TCP/IP) + cku196.sco32v505gcc PC, SCO OpenServer 5.0.5 (gcc, no TCP/IP) + cku196.sco32v505net PC, SCO OpenServer 5.0.5 (with TCP/IP) + cku196.sco32v505netgcc PC, SCO OpenServer 5.0.5 (gcc, TCP/IP) + cku196.sinix541i PC, Siemens Nixdorf SINIX-L 5.41 cku192.sinix542 PC, Siemens Nixdorf SINIX-L 5.42 + cku196.solaris24-i386 PC, Solaris 2.4 + cku196.solaris2x25-i386 PC, Solaris 2.4 + SunLink X.25 cku192.solarisx-i386-2.5 PC, Solaris 2.5 + cku196.solaris25g-i386 PC, Solaris 2.5.1 (gcc) + cku197.solaris26g-i386 PC, Solaris 2.6 (gcc) + cku196.solaris7-i386 PC, Solaris 7 (cc) + cku196.solaris7g-i386 PC, Solaris 7 (gcc) + cku197.solaris8-i386 PC, Solaris 8 (cc) + cku196.solaris8g-i386 PC, Solaris 8 Beta (gcc) cku192.sys5r3-unisys6000 PC, Unisys 6000 System V R3 cku192.sys5r3-unisys6000c PC, Unisys 6000 System V R3 + curses cku190.unixware-1.0 PC, Unixware 1.0 (no TCP/IP) cku190.unixwarenetc-1.0 PC, Unixware 1.0 + cku197.unixware-1.1.2 PC, Unixware 1.1.1 (no TCP/IP) + cku197.unixwarenetc-1.1.2 PC, Unixware 1.1.1 cku192.unixwarenetc-1.1.2 PC, Unixware 1.1.2 cku193b03.unixware-1.1.2 PC, Unixware 1.1.2 cku192.unixwarenetc-1.1.4 PC, Unixware 1.1.4 + cku196.uw20-2.0.3 PC, Unixware 2.0.3 + cku196.uw21-2.1.0 PC, Unixware 2.1.0 cku193a13.unixware2-2.1.1 PC, Unixware 2.1.1 cku193b05.unixware2-2.1.2 PC, Unixware 2.1.2 + cku196.uw21-2.1.3 PC, Unixware 2.1.3 + cku196.uw7-7.0.1 PC, Unixware 7.0.1 + cku196.uw7iksd-7.0.1 PC, Unixware 7.0.1 (+ IKSD) + cku196.uw7-7.1.0 PC, Unixware 7.1.0 + cku196.uw7iksd-7.1.0 PC, Unixware 7.1.0 (+ IKSD) cku192.netbsd-pmax-1.2 PMAX, NetBSD 1.2 cku192.mips-prime-exl7000-4.52 Prime EXL7000 MIPS RISC/os 4.52.p3.2 cku192.mipstcpc-prime-exl7000-4.52 Prime EXL7000 MIPS RISC/os 4.52.p3.2 + TCP/IP + curses cku192.pyramid-hdb Pyramid MIS-12/06 OSx5.1a-93a080 cku193b05.pyramid Pyramid MIS-12/06 OSx5.1a-93a080 + cku196.pyrdcosx Pyramid MIS-ES6/1024 SMP_DC-OSx1.1-95c087.4 cku190.irix40 SGI IRIX 4.0 cku190.irix51 SGI IRIX 5.1 + cku196.irix53 SGI Personal Iris 4/35 IRIX 5.3 (MIPS-1) cku190.irix60 SGI IRIX 6.0 + cku196.irix62 SGI R5000 Indy IRIX 6.2 (MIPS-2) + cku196.irix62-n32 SGI IRIX 6.2 N32 (MIPS-3) + cku196.irix63 SGI IRIX 6.3 cku195b06.irix64 SGI IRIX 6.4 + cku196.irix65-6.5.2 SGI IRIX 6.5.2 + cku196.irix65indy-6.5.4f SGI IRIX 6.5.4f (Indy) cku195b06.irix65-o2-6.5.3m SGI IRIX 6.5.3m (O-2) cku196b10.irix65-o200-6.5.4f SGI IRIX 6.5.4f (Origin 200) + cku196.irix65-o200-6.5.6f SGI IRIX 6.5.6f (Origin 200) + cku196.sinix542 SNI SINIX-N 5.42 MIPS (RM200) + cku196.sni543 SNI Reliant UNIX (SINIX-Y) 5.43 MIPS (RM600) + cku196.sni544 SNI Reliant UNIX (SINIX-Y) 5.44 MIPS (RM600) cku192.stratus-ftx3.01c Stratus Continuum, FTX 3.01C + cku196.sys5r4sx-ftx-3.4 Stratus Continuum, FTX 3.4, no TCP/IP + cku196.sys5r4sxtcp-ftx-3.4 Stratus Continuum, FTX 3.4, with TCP/IP + cku196.sunos41-sun3-4.1.1 Sun 3, SunOS 4.1.1_U1 + cku196.sunos41-sun4-4.1.3 Sun 4, SunOS 4.1.3_U1 cku190.sunos41x25c-4.1.3 Sun Sparc, SunOS 4.1.3 + SunLink X.25 7.00 + cku196.sunos41-4.1.3 Sun Sparc, SunOS 4.1.3_U1 + cku196.sunos41g-4.1.3 Sun Sparc, SunOS 4.1.3_U1 (gcc) + cku196.sunos41gcc-4.1.4 Sun Sparc, SunOS 4.1.4 (gcc) + cku196.linux-sparc-db2.2 Sun Sparc, Linux Debian 2.2 + cku196.linux-sparc-rh6.1 Sun Sparc, Linux Red Hat 6.1 cku196b10.netbsd-sparc-1.3.3 Sun Sparc, NetBSD 1.3.3 cku196b10.netbsd14-sparc-1.4 Sun Sparc, NetBSD 1.4 + cku196.netbsd-sparc-1.4.1 Sun Sparc, NetBSD 1.4.1 + cku196.netbsdnoiksd-sparc-1.4.1 Sun Sparc, NetBSD 1.4.1 + cku196.openbsd-sparc-2.3 Sun Sparc, OpenBSD 2.3 + cku196.openstep42-sparc Sun Sparc, OPENSTEP 4.2 + cku196.sunos41c-sb2-1.0.1 Sun (Tadpole) SparcBook2, Solaris 1.0.1 + cku196.solaris24-sparc-2.3 Sun Sparc, Solaris 2.3 cku190.solaris2xg-sparc-2.3 Sun Sparc, Solaris 2.3, gcc + cku196.solaris24x25-sparc-2.3 Sun Sparc, Solaris 2.3 + SunLink X.25 cku190.solaris2x-sparc-2.3.3 Sun Sparc, Solaris 2.4 (gcc) cku195b05.solaris23g-sparc-2.3 Sun Sparc, Solaris 2.4 (gcc) + cku196.solaris24-sparc-2.4 Sun Sparc, Solaris 2.4 cku195b09.solaris24g-sparc-2.4 Sun Sparc, Solaris 2.4 (gcc) cku195b02.solaris24x25-sparc-2.4 Sun Sparc, Solaris 2.4, SunLink X.25 + cku196.solaris25-sparc-2.5.1 Sun Sparc, Solaris 2.5.1 + cku196.solaris25g-sparc-2.5.1 Sun Sparc, Solaris 2.5.1 + cku196.solaris26-sparc Sun Sparc, Solaris 2.6 + cku196.solaris25x26-sparc-2.6 Sun Sparc, Solaris 2.6 + SunLink X2.5 9.00 + cku196.solaris7-sparc Sun Sparc, Solaris 7 + cku196.solaris7g-sparc Sun Sparc, Solaris 7 (gcc) + cku196.solaris8g-sparc Sun Sparc, Solaris 8 Beta (gcc) cku192.trs16 Tandy 16/6000 XENIX 3.0 (3) cku192.sys5r3-unisys640 Unisys 640 mc68020 System V R3 CTIX cku192.sys5r3c-unisys640 Unisys 640 mc68020 System V R3 CTIX + curses ---------------------------------------------------------------------- ckv192-axp-vms10-nonet.exe Alpha CPU, VMS 1.0, no TCP/IP ckv192-axp-vms10-pstxx.exe Alpha CPU, VMS 1.0, TCPware ?.? ckv192-axp-vms10-tgvxx.exe Alpha CPU, VMS 1.0, MultiNet ?.? ckv192-axp-vms10-twgxx.exe Alpha CPU, VMS 1.0, Wollongong ?.? ckv192-axp-vms10-ucxxx.exe Alpha CPU, VMS 1.0, UCX ?.? ckv192-axp-vms61-nonet.exe Alpha CPU, VMS 6.1, no TCP/IP ckv192-axp-vms61-tgv35b.exe Alpha CPU, VMS 6.1, MultiNet 3.5B ckv192-axp-vms61-ucx32.exe Alpha CPU, VMS 6.1, UCX 3.2 ckv192-axp-vms61-ucx33.exe Alpha CPU, VMS 6.1, UCX 3.3 + ckv196-axp-vms62-nonet.exe Alpha CPU, VMS 6.2, no TCP/IP ckv196b11-axp-vms62-ucx33.exe Alpha CPU, VMS 6.2, UCX 3.3 + ckv196-axp-vms62-ucx40.exe Alpha CPU, VMS 6.2, UCX 4.0 ckv192-axp-vms62-ucx41.exe Alpha CPU, VMS 6.2, UCX 4.1 + ckv196-axp-vms62-ucx42.exe Alpha CPU, VMS 6.2, UCX 4.2 ckv192-axp-vms62-tgv25.exe Alpha CPU, VMS 6.2, MultiNet 2.5 ckv192-axp-vms62-tgv35.exe Alpha CPU, VMS 6.2, MultiNet 3.5 ckv193a10-axp-vms62-tgv40.exe Alpha CPU, VMS 6.2, MultiNet 4.0 ckv193b09-axp-vms62-tgv40b.exe Alpha CPU, VMS 6.2, MultiNet 4.0B + ckv196-axp-vms62-tgv42a.exe Alpha CPU, VMS 6.2, MultiNet 4.2A ckv192-axp-vms62-pst51.exe Alpha CPU, VMS 6.2, TCPware 5.1 ckv192-axp-vms70-nonet.exe Alpha CPU, VMS 7.0, no TCP/IP ckv192-axp-vms70-ucx40.exe Alpha CPU, VMS 7.0, UCX 4.0 ckv192-axp-vms70-ucx41.exe Alpha CPU, VMS 7.0, UCX 4.1 ckv192-axp-vms70-pst51.exe Alpha CPU, VMS 7.0, TCPware 5.1 + ckv196-axp-vms71-nonet.exe Alpha CPU, VMS 7.1, no TCP/IP + ckv196-axp-vms71-tgv40a.exe Alpha CPU, VMS 7.1, MultiNet 4.0A + ckv196-axp-vms71-tgv40b.exe Alpha CPU, VMS 7.1, MultiNet 4.0B + ckv196-axp-vms71-tgv41a.exe Alpha CPU, VMS 7.1, MultiNet 4.1A ckv195b04-axp-vms71-tgv41b.exe Alpha CPU, VMS 7.1, MultiNet 4.1B ckv195b09-axp-vms71-tgv42a.exe Alpha CPU, VMS 7.1, MultiNet 4.2A + ckv196-axp-vms71-pst53.exe Alpha CPU, VMS 7.1, TCPware 5.3 + ckv196-axp-vms71-pst54.exe Alpha CPU, VMS 7.1, TCPware 5.4 + ckv196-axp-vms71-ucx41.exe Alpha CPU, VMS 7.1, UCX 4.1 ckv195b04-axp-vms71-ucx42.exe Alpha CPU, VMS 7.1, UCX 4.2 + ckv196-axp-vms72-nonet.exe Alpha CPU, VMS 7.2, no TCP/IP + ckv196-axp-vms72-tgv42a.exe Alpha CPU, VMS 7.2, MultiNet 4.2A + ckv196-axp-vms72-ucx50.exe Alpha CPU, VMS 7.2, UCX 5.0 ---------------------------------------------------------------------- ckv192-vax-vms44-nonet.exe VAX CPU, VMS 4.4, no TCP/IP ckv193b05-vax-vms44-nonet.exe VAX CPU, VMS 4.4, no TCP/IP ckv192-vax-vms44-twg32.exe VAX CPU, VMS 4.4, Wollongong 3.2 ckv193b05-vax-vms44-twg32.exe VAX CPU, VMS 4.4, Wollongong 3.2 ckv196b10-vax-vms45-nonet.exe VAX CPU, VMS 4.5, no TCP/IP + ckv196-vax-vms47-nonet.exe VAX CPU, VMS 4.7, no TCP/IP + ckv196-vax-vms54-nonet.exe VAX CPU, VMS 5.4, no TCP/IP ckv192-vax-vms54-tgv33d.exe VAX CPU, VMS 5.4, MultiNet 3.3D + ckv196-vax-vms55-nonet.exe VAX CPU, VMS 5.5-2, no TCP/IP + ckv196-vax-vms55-ucx20.exe VAX CPU, VMS 5.5-2, UCX 2.0 ckv192-vax-vms55-ucx33.exe VAX CPU, VMS 5.5-2, UCX 3.3 ckv192-vax-vms55-ucx41.exe VAX CPU, VMS 5.5-2, UCX 4.1 ckv192-vax-vms55-cmu12.exe VAX CPU, VMS 5.5-2, CMU/IP 1.2 ckv192-vax-vms55-pst50.exe VAX CPU, VMS 5.5-2, TCPware 5.0 + ckv196-vax-vms55-pst53.exe VAX CPU, VMS 5.5-2, TCPware 5.3 ckv192-vax-vms55-tgv40a.exe VAX CPU, VMS 5.5-2, MultiNet 4.0A + ckv196-vax-vms55-tgv41b.exe VAX CPU, VMS 5.5-2, MultiNet 4.1B ckv195b04-vax-vms55-cmuip.exe VAX CPU, VMS 5.5-2, CMU/IP ckv192-vax-vms61-nonet.exe VAX CPU, VMS 6.1, no TCP/IP ckv195b08-vax-vms61-nonet.exe VAX CPU, VMS 6.1, no TCP/IP ckv192-vax-vms61-tgv40a.exe VAX CPU, VMS 6.1, MultiNet 4.0AX ckv195b08-vax-vms61-tgv40a.exe VAX CPU, VMS 6.1, MultiNet 4.0AX ckv192-vax-vms61-ucx40.exe VAX CPU, VMS 6.1, UCX 4.0 + ckv196-vax-vms62-nonet.exe VAX CPU, VMS 6.2, no TCP/IP + ckv196-vax-vms62-ucx33.exe VAX CPU, VMS 6.2, UCX 3.3 ckv192-vax-vms62-ucx41.exe VAX CPU, VMS 6.2, UCX 4.1 ckv192-vax-vms62-tgv40a.exe VAX CPU, VMS 6.2, MultiNet 4.0A ckv192-vax-vms62-twg25.exe VAX CPU, VMS 6.2, Wollongong 2.5 + ckv196-vax-vms62-ucx33.exe VAX CPU, VMS 6.2, UCX 3.3 + ckv197-vax-vms62-ucx42.exe VAX CPU, VMS 6.2, UCX 4.2 + ckv196-vax-vms71-nonet.exe VAX CPU, VMS 7.1, no TCP/IP ckv195b04-vax-vms71-pst32.exe VAX CPU, VMS 7.1, TCPware 3.2 ckv195b04-vax-vms71-pst53.exe VAX CPU, VMS 7.1, TCPware 5.3 + ckv196-vax-vms71-tgv40b.exe VAX CPU, VMS 7.1, MultiNet 4.0B + ckv196-vax-vms71-tgv42a.exe VAX CPU, VMS 7.1, MultiNet 4.2A + ckv196-vax-vms71-twg35.exe VAX CPU, VMS 7.1, Wollongong 3.5 + ckv196-vax-vms71-ucx42.exe VAX CPU, VMS 7.1, UCX 4.2 + ckv196-vax-vms72-nonet.exe VAX CPU, VMS 7.2, No TCP/IP + ckv196-vax-vms72-ucx50.exe VAX CPU, VMS 7.2, UCX 5.0 ----------------------------------------------------------------------
Notes:
- 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.
Questions? Comments? -- Send e-mail.
[ Top ]
C-Kermit 7.0 / Columbia University / kermit@columbia.edu / 11 September 2001