![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to kermit CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [MW Coherent from dump] / coherent / a / usr / man / COHERENT|
Return to kermit CVS log | Up to [MW Coherent from dump] / coherent / a / usr / man / COHERENT |
1.1 root 1:
2:
3: kermit Command kermit
4:
5:
6:
7:
8: Remote system communication and file transfer
9:
10: kkeerrmmiitt cc[bbeell _b_a_u_d _e_s_c _l_i_n_e]
11: kkeerrmmiitt rr[bbddffhhiilltt _b_a_u_d _l_i_n_e]
12: kkeerrmmiitt ss[aabbddffhhiillmmttxx _b_a_u_d _l_i_n_e] _f_i_l_e ...
13:
14: kermit allows the user to communicate with a remote computer sys-
15: tem and to transfer files between the local and remote systems.
16: kermit can transfer ASCII or binary files of any length in either
17: direction. The two computers must be able to contact each other,
18: such as through a serial line or by modem over a telephone line,
19: and both systems must have kkeerrmmiitt available. The user must have
20: login privileges on both systems and appropriate permissions in
21: directories used for file transfer.
22:
23: The kermit command line specifies a mode, followed without inter-
24: vening spaces by optional flags, perhaps followed by additional
25: arguments and files. The three possible modes are as follows:
26:
27:
28: cc Connect the two systems so they can communicate
29: rr Receive files from the other system
30: ss Send each _f_i_l_e to the other system.
31:
32:
33: kermit normally uses a default communication line at a default
34: baud rate; the defaults vary from system to system. kermit norm-
35: ally strips leading directory information from the path name of
36: each file it sends and converts the name to upper case; it con-
37: verts the file name to lower case when receiving.
38:
39: The following flags modify kkeerrmmiitt's normal behavior.
40:
41: aa Specify complete path names for sending and receiving
42: files. Used only with s mode. The a flag requires file
43: names in pairs: first the file to be sent, then the
44: receiving file. For example, the command
45:
46: kermit sa /usr/joe/stuff.c /usr/tom/src/thing.c
47:
48: sends the file /usr/joe/stuff.c but specifies its name as
49: /usr/tom/src/thing.c for the receiving system. The tar-
50: get directory must exist on the receiving system. The a
51: flag implies the use of the f and x flags described
52: below.
53:
54: bb _b_a_u_d Set the baud rate of the port to baud.
55:
56: dd Debug mode. Tell kermit to print messages that describe
57: its actions. Message appear on the standard output, not
58: the standard error.
59:
60: ee _e_s_c Change the escape character from the default `^' to esc;
61: used only with c mode. The escape character marks com-
62:
63:
64: COHERENT Lexicon Page 1
65:
66:
67:
68:
69: kermit Command kermit
70:
71:
72:
73: mands to kermit c while it is running, as described
74: below.
75:
76: ff Suppress conversion of the case of file names.
77:
78: hh Host mode. Tell kermit to use the same line for file
79: transfer and for communication; used with either r or s
80: mode on the remote system only. When invoked with the h
81: flag, kermit resets the line modes properly when it com-
82: pletes a file transfer. If you do not use the h flag,
83: kermit will probably leave the remote system line in raw,
84: no-echo mode.
85:
86: ii Image mode. Tell kermit to send a full eight-bit byte
87: for each character; this is necessary to transfer binary
88: (non-ASCII) files. If you use i flag when sending, also
89: use it on the receiving system.
90:
91: LL Log all kermit commands into file Log.
92:
93: ll _l_i_n_e Use line. For example, the command
94: kermit clb /dev/tty50 1200
95:
96: tells kermit to use line tty50 at 1200 baud instead of
97: the default line and baud rate.
98:
99: mm Macintosh mode. Necessary when sending files to an Apple
100: Macintosh; used only with s mode.
101:
102: tt Tymnet mode. Allows Tymnet to keep up with file
103: transmission.
104:
105: xx Allows the specification of a complete pathname for the
106: receiving file; used only with s mode. For example, the
107: command
108:
109: kermit sx mydir/stuff
110:
111: sends the file mydir/stuff to mydir/stuff on the
112: receiving system. The target directory must exist on the
113: receiving system and the user must have write permission
114: in it.
115:
116: kermit c recognizes two escape sequences. The default escape
117: character `^' can be changed with the e flag, as noted above.
118:
119: ^cc Exit from kermit and break the connection between the two
120: systems. This notation does _n_o_t mean <ccttrrll-CC>; rather,
121: you must literally type the escape character (by default,
122: a carat `^') and then the letter `c'.
123:
124: ^ss Suspend kermit on the host system but do not hang up the
125: line.
126:
127:
128:
129:
130: COHERENT Lexicon Page 2
131:
132:
133:
134:
135: kermit Command kermit
136:
137:
138:
139: Unlike some file transfer protocols, kermit requires that you in-
140: voke it on both the sending and receiving systems to transfer a
141: file. As shown in the example below, you normally use kermit c
142: to connect to the remote system, invoke kermit with the h flag in
143: either send or receive mode on the remote system only, type
144: ``^s'' to suspend the local kermit c, and finally invoke kermit
145: in receive or send mode on the local system.
146:
147: The following example demonstrates the use of kermit. The ex-
148: ample assumes the user is already logged in on the local system.
149: The communication line is /dev/com2 and runs at 2400 baud. The
150: user wants to transfer locfile to the remote system and remfile
151: from the remote system. System names are in italics on the left,
152: user input is in Roman, system responses are in bold, and remarks
153: are in parentheses.
154:
155:
156: _l_o_c_a_l kermit clb /dev/com2 2400(connect to remote system)
157: _l_o_c_a_l kkeerrmmiitt: ccoonnnneecctteedd... (type a carriage return)
158:
159:
160:
161: _r_e_m_o_t_e CCoohheerreenntt llooggiinn: (perform login procedure)
162: _r_e_m_o_t_e kermit shi remfile (send from remote)
163: _r_e_m_o_t_e )SS~_@XX#TT (part of protocol, ignore)
164: _r_e_m_o_t_e ^s (suspend local kkeerrmmiitt)
165:
166:
167:
168: _l_o_c_a_l kkeerrmmiitt: ssuussppeennddeedd.
169: _l_o_c_a_l kermit rilb /dev/com2 2400(receive on local)
170: _l_o_c_a_l kkeerrmmiitt: RReecceeiivviinngg RREEMMFFIILLEE aass rreemmffiillee
171: _l_o_c_a_l kkeerrmmiitt: ddoonnee.
172: _l_o_c_a_l kermit clb /dev/com2 2400(connect again)
173:
174:
175:
176: _r_e_m_o_t_e kermit rhi (receive on remote)
177: _r_e_m_o_t_e ^s (suspend local kkeerrmmiitt)
178:
179:
180:
181: _l_o_c_a_l kkeerrmmiitt: ssuussppeennddeedd.
182: _l_o_c_a_l kermit silb /dev/com2 2400 locfile(send from local)
183: _l_o_c_a_l kkeerrmmiitt: SSeennddiinngg llooccffiillee aass LLOOCCFFIILLEE
184: _l_o_c_a_l kkeerrmmiitt: ddoonnee.
185: _l_o_c_a_l kermit clb /dev/com2 2400(connect again)
186:
187:
188:
189: _r_e_m_o_t_e <ctrl-D> (log off the remote system)
190: _r_e_m_o_t_e CCoohheerreenntt llooggiinn:
191: _r_e_m_o_t_e ^c (disconnect local kkeerrmmiitt)
192:
193:
194:
195:
196: COHERENT Lexicon Page 3
197:
198:
199:
200:
201: kermit Command kermit
202:
203:
204:
205:
206:
207: _l_o_c_a_l kkeerrmmiitt: ddiissccoonnnneecctteedd.
208:
209:
210: ***** See Also *****
211:
212: commands
213: Kermit: A file-transfer protocol for universities, BYTE, June
214: 1984 pp. 255_f_f, July 1984 pp. 143_f_f
215:
216: ***** Diagnostics *****
217:
218: kermit may print the following error messages:
219:
220: Aborting with following error from remote host
221: Problem appeared on receiving system.
222:
223: Bad line speed
224: Transmission was attempted at an illegal baud rate.
225:
226: Cannot create _n_a_m_e
227: The receiving system cannot create _n_a_m_e. Confirm that you
228: have write permission on the receiving system.
229:
230: Cannot open file _n_a_m_e
231: The sending system cannot open _n_a_m_e. Either you do not have
232: read permission on the sending system, or the file is not
233: present in the named directory.
234:
235: Cannot open _l_i_n_e
236: An incorrect _l_i_n_e number was specified.
237:
238: No line specified for connection
239: The _l_i_n_e argument missing after the -ll option.
240:
241: Receive failed
242: The file being sent was not received; this could be due to
243: any one of a number of reasons. Check that everything is
244: functioning normally, and then try to send the file again.
245:
246: Send failed
247: The requested file was not sent.
248:
249: Speed setting not implemented
250: An unimplemented baud rate was selected for the -bb option.
251:
252: Yes, I'm still here...
253: The connect command was repeated.
254:
255: ***** Notes *****
256:
257: If you type kermit c and get the message kkeerrmmiitt ccoonnnneecctteedd but the
258: remote system does not respond, check the line that connects the
259: two systems and the ability of the remote system to accept a
260:
261:
262: COHERENT Lexicon Page 4
263:
264:
265:
266:
267: kermit Command kermit
268:
269:
270:
271: login on the line.
272:
273: The file transfer protocol uses small (96-character) checksummed
274: packets, with ACK/NAK responses from the receiving system. The
275: timeout period is five seconds, and kermit does ten retries
276: before it abandons an attempted file transfer.
277:
278: The kermit protocol was developed at the Columbia University
279: Center for Computing Activities. Tymnet is a trademark of Tym-
280: share, Inc.
281:
282:
283:
284:
285:
286:
287:
288:
289:
290:
291:
292:
293:
294:
295:
296:
297:
298:
299:
300:
301:
302:
303:
304:
305:
306:
307:
308:
309:
310:
311:
312:
313:
314:
315:
316:
317:
318:
319:
320:
321:
322:
323:
324:
325:
326:
327:
328: COHERENT Lexicon Page 5
329:
330:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.