minicom.1

小型通讯程序的C语言源程序的C语言源程序库

Which specific dial string you want to use to connect. There are three
different dial strings (prefixes and suffixes) that can be configured
in the \fBModem and dialing\fP menu.
.TP 1.0i
.B D - Local echo
can be on or off for this system (if your version of minicom supports it).
.TP 1.0i
.B E - Script 
The script that must be executed after a succesfull connection is made
(see the manual for runscript)
.TP 1.0i
.B F - Username
The username that is passed to the runscript program.  It
is passed in the environment string "$LOGIN".
.TP 1.0i
.B G - Password
The password is passed as "$PASS".
.TP 1.0i
.B H - Terminal Emulation
Use MINIX, ANSI or VT100 emulation.
.TP 1.0i
.B I - Line settings
Baudrate, bits and parity to use for this connection.
.PD 1
.PP
.SH CONFIGURATION
By pressing C-A O you will be thrown into the setup menu. Most
settings there can be changed by everyone, but some are restricted
to root only. Those priviliged settings are marked with a star (*) here.
.PP
.PD 0
.B "Filenames and paths"
.PP
.RS 0.25i
This menu defines your default directories.
.TP 0.5i
.B A - upload
where the uploaded files go to.
.TP 0.5i
.B B - download
Yup, you guessed it.
.TP 0.5i
.B C - script
Where you keep your login scripts.
.TP 0.5i
.B D - Script program
Which program to use as the script interpreter. Defaults to the
program "runscript", but if you want to use something else (eg,
/bin/sh or "expect") it is possible.  Stdin and stdout are connected
to the modem, stderr to the screen.
.RS 0.5i
If the path is relative (ie, does not start with a slash) then it's
relative to your home directory, except for the script interpreter.
.RE
.TP 0.5i
.B E - Kermit program
Where to find the executable for kermit, and it's options. Some simple
macro's can be used on the command line: '%l' is expanded to the
complete filename of the dial out-device, and '%b' is expanded to
the current baudrate.
.RE
.RE
.PD 1
.PP
.B "File Transfer Protocols"
.PD 0
.PP
.RS 0.25i
Protocols defined here will show up when C-A s/r is pressed.
"Name" is the name that will show up in the menu. "Program" is
the path to the protocol. "NeedName" defines if the program needs an
argument, eg. a file to be transmitted. Up/Down defines
if this entry should show up in the upload or the download menu.
Fullscr defines if the program should run full screen, or that
minicom will only show it's stderr in a window. Finally, IO-Red
defines if minicom should attach the program's standard in and output
to the modem port or not. The old sz and rz are not full screen, and
have IO-Red set. However, there are curses based versions of at least
rz that do not want their stdin and stdout redirected, and run full
screen.
All file transfer protocols are run with the UID of the user, and
not with UID=root. '%l' and '%b' can be used on the command line as
with kermit.
.RE
.PD 1
.PP
.B "Serial port setup"
.RS 0.25i
.PD 0
.TP 0.5i
.B *A - Serial device
/dev/tty1 for most people, or maybe /dev/tty64 if you use the VC
package under minix.  /dev/cua<n> or /dev/modem under linux.
.TP 0.5i
.B *B - Lock file location
This should be /usr/spool/uucp. If this directory does not exist,
minicom will not attempt to use lockfiles.
.TP 0.5i
.B *C - Callin program
If you have a uugetty or something on your serial port, it could be
that you want a program to be run to switch the modem cq. port into
dialin/dialout mode. This is the program to get into dialin mode.
.TP 0.5i
.B *D - Callout program
And this to get into dialout mode.
.TP 0.5i
.B E - Baud/Par/Bits
Default parameters at startup.
.PD 1
.PP  
If one of the entries is left blank, it will not be used. So if you
don't care about locking, and don't have a getty running on your
modemline, entries B - D should be left blank.  Be warned! The callin
and callout programs are run with the effective user id of "root", eg
0!
.RE
.PP
.B "Modem and Dialing"
.PD 0
.PP
.RS 0.25i
Here, the parameters for your modem are defined. I will not explain
this further because the defaults are for generic Hayes modems, and
should work always. This file is not a Hayes tutorial :-) The only
thing worth noticing is that control characters can be sent by
prefixing them with a '^', in which '^^' means '^' itself.  Some
options however, don't have much to do with the modem but more with
the behaviour of minicom itself:
.PP
.TP 0.5i
.B M - Dial time
The number of seconds before minicom times out if no connection is
established.
.TP 0.5i
.B N - Delay before redial
Minicom will redial if no connection was made, but it first waits some
time.
.TP 0.5i
.B O - Number of tries
Maximum number of times that minicom attempts to dial.
.TP 0.5i
.B P - Autobaud detect
If this is on, minicom tries to match
the dialed party's speed.
.TP 0.5i
.B Q - Drop DTR to hangup
Normally minicom hangs up by sending a Hayes-type hangup sequence but
if your Minix supports it, it can also hangup by dropping the DTR
line.
.TP 0.5i
.B R - Modem has DCD line
If your modem, and your O/S both support the DCD line (that goes 'high'
when a connection is made) minicom will use it.
.PD 1
.PP
.RE
.RS 0.5i
.B Note that a special exception is made for this menu: every user
.B can change all parameters here, but they will not be saved.
.RE
.PP
.B "Screen and keyboard"
.RS 0.25i
.PD 0
.TP 0.5i
.B A - Command key is
the 'Hot Key' that brings you into command mode. If this is set
to 'ALT' or 'meta key', you can directly call commands
by alt-key instead of HotKey-key.
.TP 0.5i
.B B - Backspace key sends
There still are some systems that want a VT100 to send DEL instead of
BS. With this option you can enable that stupidity.  (Eh, it's even on
by default...)
.TP 0.5i
.B C - Status line is
Enabled or disabled. Some slow terminals (for example, X-terminals)
cause the status line to jump "up and down" when scrolling, so you can
turn it off if desired. It will still be shown in command-mode.
.RE
.PD 1
.TP 0.25i
.B "Save setup as dfl"
Save the parameters as the default for the next time the program is
started. Instead of dfl, any other parameter name may appear, depending
on which one was used when the program was started.
.TP 0.25i
.B "Save setup as.."
Save the parameters under a special name. Whenever Minicom is started
with this name as an argument, it will use these parameters. This
option is of course priviliged to root.
.TP 0.25i
.B "Exit"
Escape from this menu without saving.  This can also be done with ESC.
.TP 0.25i
.B "Exit from minicom"
Only root will see this menu entry, if he/she started minicom with the '-s'
option. This way, it is possible to change the configuration without
actually running minicom.
.PD 1
.SH "STATUS LINE"
The status line has several indicators, that speak for themselves.
The mysterious APP or CUR indicator probably needs explanation. The
VT100 cursor keys can be in two modes: applications mode and cursor
mode. This is controlled by an escape sequence. If you find that
the cursor keys do not work in, say, vi when you're logged in using
minicom then you can see with this indicator whether the cursor keys
are in applications or cursor mode. You can toggle the two with the
C-A I key. If the cursor keys then work, it's probably an error in
the remote system's termcap initialization strings (is).
.PD 1
.SH "SECURITY ISSUES"
Since Minicom runs setuid root, you probably want to restrict access to
it. This is possible by using a configuration file in the same directory
as the default files, called "minicom.users". The syntax of this file
is as following:
.PP
.RS 0.5i
<username> <configuration> [configuration...]
.RE
.PP
To allow user 'miquels' to use the default configuration, enter the 
following line into "minicom.users":
.PP
.RS 0.5i
miquels dfl
.RE
.PP
If you want users to be able to use more than the default
configurations, just add the names of those configurations behind the
user name. If no configuration is given behind the username, minicom
assumes that the user has access to all configurations.
.PD 1
.SH MISC
If minicom is hung, kill it with SIGTERM . (This means kill -15, or
since sigterm is default, just plain "kill <minicompid>". This will
cause a graceful exit of minicom, doing resets and everything.
.PP
Since a lot of escape sequences begin with ESC (Arrow up is ESC [ A),
Minicom does not know if the escape character it gets is you pressing
the escape key, or part of a sequence.
.PP
An old version of Minicom, V1.2, solved this in a rather crude way:
to get the escape key, you had to press it 
.IR twice .
Support for timing (with select) was already built in to minicom
(see file wkeys.c) and works great under BSD, but alas, not under Minix.
The same problem, but worse, was with Televideo type terminals. Since they
use a lot of escape sequences that start with 'C-A', you had to
press 'C-A' twice when you want to pop up a window or something...
.PP
As of release 1.3 this has bettered a little: now a 1-second timeout
is builtin, like in vi. And... surprise: a special Minix and Linux-dependant
.BR hack " :-) was added. Now, minicom can separate the escape key and"
escape-sequences. To see how dirty this was done, look into wkeys.c.
But it works like a charm!
.SH AUTHORS
The author of minicom and the minicom manual is Miquel van
Smoorenburg ([e-mail])
.PP
Most of this man page is copied, with corrections, from the minicom
manual, but some pieces and the corrections are by Michael K. Johnson
([e-mail]).