From: "L. C. Robinson" <lcr@onewest.net>
To: blinux-list@redhat.com
Subject: Re: Making Device Fiiles
Date: Wed, 30 Jan 2002 15:24:00 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.4.44.0201301437240.2184-100000@rupin.localnet> (raw)
In-Reply-To: <Pine.LNX.4.33.0201291747110.3246-100000@localhost.localdomain>
On Tue, 29 Jan 2002, John J. Boyer wrote:
> ... However, minicom still won't create the /etc/minicomrc.dfl
> file. Incidentally, it has an attrocious interface. Instead of
> just using a plain text interface it is doing something fancy.
Yes, minicom uses a text windowing interface library known as
ncurses, with line drawing characters around sub windows, and
cursor placement escape codes, and the like. For a more basic
text interface you might like to try:
ftp://mirrors.kernel.org/ibiblio/apps/serialcomm/dialout/xc-4.3.2.tar.gz
This is on an ibiblio (formerly metalab) mirror.
Short description at:
ftp://mirrors.kernel.org/ibiblio/apps/serialcomm/dialout/xc-4.3.2.lsm
I don't use the thing much anymore as a terminal program (ppp
internet access trumps that easily), but I constantly use the
included voice "call" script (highly modified by me), to
automatically look up voice phone numbers numbers I have typed
into a text file, and dial them for me, then drop the line so I
can talk by voice. This is a pure text interface that accepts a
search string (key) on the command line.
LCR
--
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid
People buy MicroShaft for compatibility, but get incompatibility and
instability instead. This is award winning "innovation". Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
John J. Boyer
` Rafael
` Janina Sajka
` John J. Boyer
` Rafael
` John J. Boyer
` Nicolas Pitre
` Rafael
` L. C. Robinson [this message]
` Janina Sajka
` Cheryl Homiak
` Nicolas Pitre
` A. R. Vener
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0201301437240.2184-100000@rupin.localnet \
--to=lcr@onewest.net \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).