3 .CD "kermit \(en transfer a file using the kermit protocol"
6 .EY "kermit" "Start kermit"
8 This is a slightly lobotomized \fIkermit\fR.
9 The help command, the script facility, and the automatic dial support
11 The ? and ESC commands still work, so there is still reasonable built-in help.
12 The only V7 \fIkermit\fR feature that does not work is the ability to see
13 whether there are input characters waiting. This means that you will not
14 be able to ask for status during a file transfer (though
15 this is not critical, because \fIkermit\fR prints a dot every so often and
16 other special characters whenever there is an error or timeout).
18 Start \fIkermit\fR, and then type the following to open a 2400 baud session,
22 .Cx "set line /dev/tty1"
27 (It is more convenient if you put these commands in \fI.kermrc\fR in your
28 home directory, so that they get done automatically whenever you
29 run \fIkermit\fR.) This will connect you to the modem or whatever on
30 the serial port. Now log into the other system.
32 When you want to transfer files, run \fIkermit\fR on the other system.
37 This puts its \fIkermit\fR into a sort of \*(OQslave mode\*(CQ where it expects
38 commands from the \fIkermit\fR running on your \s-2MINIX\s0 system. Now come back
39 to the command level on \s-2MINIX\s0 \fIkermit\fR, by typing the escape character
40 followed by \fIc\fR. (\fIKermit\fR will tell you
41 the current escape character when
42 you do the connect command.) At this point you can issue various
44 Your \fIkermit\fR will coordinate things with \fIkermit\fR on the other
45 machine so that you only have to type commands at one end. Common
48 .Cx "get \fI\s+2filename\fP\s0"
50 .Cx "put \fI\s+2filename\fP\s0"
52 .Cx "remote \fI\s+2dir\fP\s0"
54 \fRFilenames can include wildcards. By default, \fIkermit\fR works in a
55 system-independent, text mode. (In effect it assumes that the
56 whole world is \s-2MS-DOS\s0 and converts end of line and file names
57 accordingly.) To send binary files, you will want to type
59 .Cx "set file type bin"
61 on both ends before starting any transfers. This disables
62 CR LF to newline conversion. If both of your systems are some
63 flavor of \s-2UNIX\s0, you might as well put this in \fI.kermrc\fR on both
64 ends and run in binary mode all the time. Also, if both systems
65 are \s-2UNIX\s0 it is recommended that you use
67 .Cx "set file name lit"
69 on both ends. This causes it to keep file names unchanged,
70 rather than mapping to legal \s-2MS-DOS\s0 names.
72 Here is a typical \fI.kermrc\fR for use on
76 .Cx "set line /dev/tty1"
79 .Cx "set file type bin"
80 .Cx "set file name lit"
82 .Cx "set prompt MINIX kermit>"
86 On the other end of the line, for example, the host at your local computer
87 center to which you want to transfer files, a typical profile might be:
90 .Cx "set rec packet 1000"
91 .Cx "set fil name lit"
92 .Cx "set fil type bin"
97 \fIKermit\fR has many other options and features. For a pleasant and
98 highly readable description of it, see the following book:
102 Title: Kermit: A File Transfer Protocol
103 Author: Frank da Cruz
104 Publisher: Digital Press
111 For information about recent \fIkermit\fR developments, versions for other
112 systems, and so forth, please contact:
117 Manager, Kermit Development and Distribution
118 University Center for Computing Activities
120 612 West 115th Street
125 Over 400 versions of \fIkermit\fR are available, so it is likely there is one
126 for any computer your
128 system might want to talk to.
129 Columbia University also publishes a newsletter about \fIkermit\fR that can be
130 requested from the above address.