manual.mnc

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

	       expanded to the current baudrate.

       File Transfer Protocols
	  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.

       Serial port setup
	  *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.



Cohesive Systems	    9 Oct 1993				5





MINICOM(1)	  Linux Programmer's Manual	  MINICOM(1)


	  *B - Lock file location
	       This  should be /usr/spool/uucp. If this directory
	       does not exist, minicom will not	attempt  to  use
	       lockfiles.
	  *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.
	  *D - Callout program
	       And this to get into dialout mode.
	  E - Baud/Par/Bits
	       Default parameters at startup.

	  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  call-
	  out  programs	are  run  with	the effective user id of
	  "root", eg 0!

       Modem and Dialing
	  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 notic-
	  ing 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:
	  M - Dial time
	       The  number of seconds before minicom times out if
	       no connection is established.
	  N - Delay before redial
	       Minicom will redial if no connection was made, but
	       it first waits some time.
	  O - Number of tries
	       Maximum	number	of times that minicom attempts to
	       dial.
	  P - Autobaud detect
	       If this is on, minicom tries to match  the  dialed
	       party's speed.
	  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.
	  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.

	    Note  that a special exception is made for this menu:
	    every user can change all parameters here,	but  they



Cohesive Systems	    9 Oct 1993				6





MINICOM(1)	  Linux Programmer's Manual	  MINICOM(1)


	    will not be saved.

       Screen and keyboard
	  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.
	  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...)
	  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  com-
	       mand-mode.

	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.

	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.

	Exit
	  Escape from this menu without saving.	This can also be
	  done with ESC.

	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.

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  con-
       trolled 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  term-
       cap initialization strings (is).



Cohesive Systems	    9 Oct 1993				7





MINICOM(1)	  Linux Programmer's Manual	  MINICOM(1)


SECURITY ISSUES
       Since  Minicom  runs  setuid  root,  you	probably want to
       restrict access to it. This is possible by using a config-
       uration	file  in the same directory as the default files,
       called "minicom.users". The syntax of this file is as fol-
       lowing:

	    <username> <configuration> [configuration...]

       To  allow user 'miquels' to use the default configuration,
       enter the following line into "minicom.users":

	    miquels dfl

       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.

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.

       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.

       An old version of Minicom, V1.2, solved this in	a  rather
       crude  way:  to	get  the  escape key, you had to press it
       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...

       As of release 1.3 this has bettered a little: now a 1-sec-
       ond  timeout  is	builtin,  like in vi. And... surprise: a
       special Minix and Linux-dependant 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!

AUTHORS
       The author of minicom and the minicom manual is Miquel van
       Smoorenburg ([e-mail])

       Most of this man page is copied,	with  corrections,  from
       the  minicom  manual,  but some pieces and the corrections



Cohesive Systems	    9 Oct 1993				8





MINICOM(1)	  Linux Programmer's Manual	  MINICOM(1)


       are by Michael K. Johnson ([e-mail]).
























































Cohesive Systems	    9 Oct 1993				9