From: Lee_Maschmeyer@wayne.edu
To: blinux-list@redhat.com
Subject: Re: debian install issue solved
Date: Mon, 8 Dec 2003 08:36:10 -0500 [thread overview]
Message-ID: <20031208133610.GA7995@wayne.edu> (raw)
In-Reply-To: <16336.45197.4719.348717@localhost.localdomain>
But what's the operative principle here? Apparently the VT100 was
sending an inappropriate response, but I don't see how the terminal
version can in and of itself make a difference - waiting for input is
waiting for input. Could it be something in end-of-line or echo or
something?
Lee
On Fri, Dec 05, 2003 at 11:21:33AM -0500, Dave Hunt wrote:
> Thanks for sharing your solution to this. I find it timely, as I'm
> considering a Debian install, using either Speakup or an external
> terminal as a serial console. If I go with Speakup, my external
> doubletalk would be the synthesizer. For the serial console option,
> I'd run a terminal emulator on my braillenspeak 640. This box now has an old version of RH,
> but, I may want to try another distro, and, Debian looks like a worthy
> candidate.
>
>
> -Dave
>
>
>
>
>
> John> I've been stuck since last weekend on a debian install via a
> John> serial console.
>
> John> I'm using Hyperterminal on a Windows PC as the terminal. And
> John> I found that the problem went away if I switched the
> John> emulation from VT100 to ANSI. So it didn't have anything to
> John> do with the baud rate or the flow control. When I left it
> John> last night it was downloading packages so by now I may have
> John> a functioning system.
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
John Heim
` Dave Hunt
` Lee_Maschmeyer [this message]
` John Heim
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=20031208133610.GA7995@wayne.edu \
--to=lee_maschmeyer@wayne.edu \
--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).