From: Pat Gilliland <gilliland@sympatico.ca>
To: "Linux-8086@vger.kernel.org" <Linux-8086@vger.kernel.org>
Subject: Re: Serial terminal help
Date: Mon, 11 Nov 2002 07:43:18 -0500 [thread overview]
Message-ID: <3DCFA5E6.17B78B48@sympatico.ca> (raw)
In-Reply-To: Pine.LNX.4.21.0211061143490.6466-100000@acid.ch.pw.edu.pl
Well 2 emails to Jacek directly have failed after sitting for 4 days on
the server so I'll say it here.
Thanks very much for st it works very well except that all i/o appears
on one line. e.g. "ls" will print everything on one line "vi xyz" will
print the whole file on one line in the vi window (most of the time,
once or twice it has seemed to work properly) BUT just "vi" will open
normally with the usual screen and allow normal full page editing. I
suspect it's a problem with the terminal setup on the remote box rather
than st. I will post back when I get it figured out.
Jacek Lipkowski wrote:
>
> On Tue, 8 Oct 2002, Pat Gilliland wrote:
>
> > http://www.sorgonet.com/8086/8088_linux_dumb_terminal/ describes how to
> > do this using dos and kermit terminal emulator on the 8088. I have
> > done this proving the linux setup is good but I would much prefer an
> > ELKS solution for the laptop side.
>
> you don't need a terminal emulator, just a a program to talk to the
> serial port, since elks can do vt52 emulation well
>
> > I suspect this should be simple to do but rtfm and google have just left
> > me confused.
>
> thats strange, enter +elks +serial +terminal into google :)
>
> http://acid.ch.pw.edu.pl/~sq5bpf/elks/ has a serial terminal. use version
> 0.2 if you have a recent elks kernel with select(), or 0.1 if you don't.
>
> jacek
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
This communication is intended to be received only by the individual
or entity to whom or to which it is addressed and contains information
that is privileged and confidential. Any unauthorized use, copying,
review or disclosure is prohibited. Please notify the sender
immediately
if you have received this communication in error.
Contents of this message Copyright 2002 Patrick Gilliland
prev parent reply other threads:[~2002-11-11 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 13:01 Serial terminal help Pat Gilliland
[not found] ` <20021010081046.GD2251@raq465.uk2net.com>
2002-10-10 11:18 ` Pat Gilliland
2002-10-10 12:17 ` Paul Nasrat
2002-11-06 11:01 ` Jacek Lipkowski
2002-11-08 11:31 ` assembling programs under as86 Seemanta Dutta
2002-11-10 9:37 ` assembling_programs_under_as86 tom potts
2002-11-13 8:49 ` assembly under as86 Seemanta Dutta
2002-11-13 8:45 ` tom potts
2002-11-11 12:43 ` Pat Gilliland [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=3DCFA5E6.17B78B48@sympatico.ca \
--to=gilliland@sympatico.ca \
--cc=Linux-8086@vger.kernel.org \
/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