Minicom Manual
Cisco Configuration
minicom notes:
default config file (minicom -s):
/etc/minicom/minirc.dfl
When minicom starts, it first searches the MINICOM environment
variable for command-line arguments, which can be over-ridden on
the command line. Thus, command line arguments override arguments
defined in the MINICOM env variable:
MINICOM='-c on'
export MINICOM
To call minicom with a custom configuration file named
/etc/minicom/minirc.configname:
minicom configname
Configuration options with (*) can only be changed by root.
Misc:
CTRL+A C - clear the sceen
CTRL+A E - toggle local echo
CTRL+A F - send BREAK
CTRL+A J - jump to shell
CTRL+A L - turn capture file on off
CTRL+A O - puts minicom in config mode/menu
CTRL+A P - change com parameters: bps rate, parity, number of bits
CTRL+A T - choose terminal emulation
CTRL+A W - toggle linewrap on/off
CTRL+A X - exit minicom with reset
CTRL+A Q - exit minicom w/o reset
minicom man extracts:
minicom [-somMlwz8] [-c on|off] [-S script] [-d entry]
[-a on|off] [-t term] [-p pty] [-C capturefile] [configuration]
-o Do not initialize. Minicom will skip the initialization code.
This option is handy if you quitted from minicom without reset-
ting, and then want to restart a session. It is potentially dan-
gerous though: no check for lock files etc. is made, so a normal
user could interfere with things like uucp... Maybe this will be
taken out later. For now it is assumed, that users who are given
access to a modem are responsible enough for their actions.
-t Terminal type. With this flag, you can override the environment
TERM variable. This is handy for use in the MINICOM environment
variable; one can create a special termcap entry for use with
minicom on the console, that initializes the screen to raw mode so
that in conjunction with the -l flag, the IBM line characters are
displayed untranslated.
-w Turns linewrap on at startup by default.
-p Pseudo terminal to use. This overrides the terminal port defined
in the configuration files, but only if it is a pseudo tty. The
filename supplied must be of the form (/dev/)tty[p-z/][0-f],
(/dev/)pts[p-z/][0-f] or (/dev/)pty[p-z/][0-f]. For example,
/dev/ttyp1, pts/0 or /dev/ptyp2.
-C filename. Open capture file at startup.
configuration
The configuration argument is more interesting. Normally, minicom
gets its defaults from a file called "minirc.dfl". If you however
give an argument to minicom, it will try to get its defaults from
a file called "minirc.configuration". So it is possible to create
multiple configuration files, for different ports, different users
etc. Most sensible is to use device names, such as tty1, tty64,
sio2 etc. If a user creates his own configuration file, it will
show up in his home directory as '.minirc.dfl'.