This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Minicom | |
|---|---|
| Name | Minicom |
| Caption | Terminal-based serial communication program |
| Developer | Thomas S. Dickey, originally by Miquel van Smoorenburg |
| Released | 1991 |
| Programming language | C (programming language) |
| Operating system | Unix-like systems, Linux, FreeBSD |
| Platform | Terminal |
| Genre | Terminal emulator, Serial communication |
| License | GNU General Public License |
Minicom
Minicom is a text-based serial communication program widely used on Unix-like systems such as Linux, FreeBSD, and NetBSD. It provides a terminal-oriented interface for interacting with serial devices including modems, routers, and embedded systems like Raspberry Pi peripherals and Arduino boards. Originating in the early 1990s, it remains a staple in system administration workflows alongside tools from projects such as GNU Project and packages maintained by distributions like Debian and Red Hat Enterprise Linux.
Minicom was created in 1991 as a free-software alternative to proprietary terminal programs prevalent in the era of dial-up networking and early personal computing. Its development was influenced by terminal utilities such as Procomm, Kermit (protocol), and terminal handling libraries like ncurses. Early adopters included sysadmins managing equipment from vendors such as Cisco Systems and 3Com, and researchers using serial consoles on machines from Sun Microsystems and DEC. Over time, stewardship passed through contributors from communities around projects such as GNU Project, Free Software Foundation, and individual maintainers active in distributions including Debian and Gentoo. Its roadmap and bug reports have historically intersected with coordination on platforms like SourceForge and later GitHub.
Minicom offers character-oriented terminal emulation with support for VT100 and related control sequences used by terminals from vendors like Digital Equipment Corporation and Xerox. It includes dialing directory features suitable for legacy Hayes command set modems, scripting hooks comparable to those in Expect (software), and file-transfer support for protocols such as XMODEM, YMODEM, and ZMODEM. The program implements menu-driven configuration, session logging, and file capture for troubleshooting environments interfacing with hardware from Juniper Networks or devices running OpenWrt. Integration with terminal control libraries like ncurses enables windowed terminal manipulation used in tools such as tmux and screen.
Users typically invoke Minicom from shells such as Bash (Unix shell), Zsh, or Fish (shell) to open serial connections to device nodes like /dev/ttyS0 on Linux or /dev/cu.* on Darwin (operating system). System administrators use it to access boot consoles on servers from Dell EMC and Hewlett-Packard, while network engineers employ it for console access to equipment from Cisco Systems, Arista Networks, and Juniper Networks. Embedded developers connect to microcontrollers from vendors like Atmel and STMicroelectronics and to single-board computers such as BeagleBone and Raspberry Pi. Common workflows include capturing boot logs, issuing firmware update commands, and debugging kernel messages from Linux kernel instances.
Minicom’s configuration is managed through an interactive setup that stores settings in user-readable files located in system directories used by distributions like Debian and Arch Linux. Options include baud rate selection corresponding to standards defined by Institute of Electrical and Electronics Engineers terms, flow control settings compatible with hardware from Texas Instruments and Intel Corporation, and device selection matching serial adapters built around chipsets from Prolific Technology and FTDI. Advanced users integrate Minicom configuration into automation systems using orchestration tools from projects such as Ansible (software), Puppet (software), and SaltStack to provision serial-console access on fleets of machines managed by service providers like Amazon Web Services and Google Cloud Platform.
Minicom supports classical file-transfer and communication protocols originally developed for modem-era interoperability, including XMODEM, YMODEM, ZMODEM, and terminal control sequences used by VT220 and ANSI.SYS-based terminals. These protocols interact with modem command sequences standardized by the Hayes command set and are relevant when bridging to cellular modems from manufacturers like Huawei or satellite modems used in Iridium Communications deployments. Minicom’s handling of parity, stop bits, and data bits aligns with serial standards historically promulgated by organizations such as EIA.
Minicom is often compared with other terminal and serial communication utilities including screen (software), cu (Unix), picocom, PuTTY, and HyperTerminal. For scripting-oriented interactions, tools like Expect (software) or language libraries such as Python’s pySerial and Ruby’s ruby-serialport provide programmatic alternatives. Graphical front-ends and cross-platform clients like Tera Term, MobaXterm, and gtkterm offer GUI-based workflows contrasted with Minicom’s terminal-centric design favored by practitioners at organizations like NASA, European Space Agency, and research labs at universities such as MIT and Stanford University.
Minicom’s source code, written primarily in C (programming language), has been maintained by volunteers and contributors associated with free-software communities and distribution maintainers from Debian, Gentoo, and OpenBSD. Issue tracking and patches have historically been coordinated via platforms utilized by open-source projects including SourceForge and GitHub. Its license under the GNU General Public License ensures continued redistribution and modification by contributors from academic and corporate environments such as IBM and Oracle Corporation.
Category:Terminal emulators Category:Free software