On Wed, 2004-03-03 at 18:37, Steve Langasek wrote: > On Wed, Mar 03, 2004 at 03:24:08PM -0800, Oliver Kurth wrote: > > Package: wnpp > > Severity: wishlist > > > * Package name : picocom > > Version : 1.1 > > Upstream Author : Nick Patavalis (npat@efault.net) > > * URL : http://efault.net/npat/hacks/picocom/ > > * License : GPL > > Description : minimal dumb-terminal emulation program > > picocom was designed to serve as a simple, manual, modem > > configuration, testing, and debugging tool. It has also served (quite > > well) as a low-tech "terminal-window" to allow operator intervention > > in PPP connection scripts (something like the ms-windows "open > > terminal window before / after dialing" feature). It could also prove > > useful in many other similar tasks. It is ideal for embedded systems > > since its memory footprint is minimal. > > In what cases do you find that minicom is not small enough? Hm... nimrod:~# ls -l /usr/bin/picocom -rwxr-xr-x 1 root root 22712 Jan 20 03:10 /usr/bin/picocom nimrod:~# ls -l /usr/bin/minicom -rwxr-xr-x 1 root root 166328 Nov 12 10:22 /usr/bin/minicom nimrod:~# If that is not enough: I have much less problems with picocom than I have with minicom. I can give the port to use on the cmd line: picocom /dev/ttyS0 which is much more intuitive for me than modifying the minicom configuration (maybe you can do that with minicom, but I haven't yet figured out how - so far I always relinked /dev/modem). Also, I am using Debian on a small PowerPC device with 64MB flash, so every byte is a crucial ressource there. And I do not need any nifty curses interface. picocom does exactly what I want: connect to a serial port. And nothing more. Greetings, Oliver
Attachment:
signature.asc
Description: This is a digitally signed message part