From: Travis Siegel <tsiegel@softcon.com>
To: blinux-list <blinux-list@redhat.com>
Subject: Re: A beginner's question (fwd)
Date: Mon, 22 Jun 1998 13:37:23 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.980622133426.11200A-100000@softcon.com> (raw)
In-Reply-To: <Pine.LNX.3.96.980622171547.4348J-100000@goldfish.cube.net>
On Mon, 22 Jun 1998, Hans Zoebelein wrote:
> Does Telix require any modification to directly connect a terminal machine
> with Linux box?
None at all. You will need either a null modem cable, or a straight
through cable with a null modem adapter tacked on one end of it. But
other than that, absolutely nothing is required to hook any communications
program to a linux box via serial ports. This is exactly how I'm using my
linux box right now. And it's my recomendation for all blind users if you
can swing the cost of a separate linux box, since then you can use your
own speech software that you're already familiar with, and there's no
learning curve associated with learning a new speech package under linux
as well as the os itself.
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Hans Zoebelein
` Travis Siegel [this message]
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.3.96.980622133426.11200A-100000@softcon.com \
--to=tsiegel@softcon.com \
--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).