From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: [9fans] FAX (bis)
Date: Sun, 3 Apr 2005 08:16:15 +0200 [thread overview]
Message-ID: <fa9afd486bcb4ed2f97fe527fdcf6a11@proxima.alt.za> (raw)
Something struck me a while back, but I never found occasion to bring
it up. Many years ago, when I was still using my 3B1 and learning to
use Unix, I encountered modemcap. I don't have any details handy,
although I could start up one of my relics and do some digging. What
seemed like a good idea at the time was obviously lost to humankind.
Would it be worth revisiting?
The following quote from man telco is apt:
The modem specific information is currently built into the
source. This should be in a user modifiable file.
I appreciate that "cap" style files are a little obsolete, but perhaps
not totally so. I'm really looking for opinions (not a flame war), I
suppose.
++L
reply other threads:[~2005-04-03 6:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fa9afd486bcb4ed2f97fe527fdcf6a11@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).