Subject: Re: Serial console problems...
To: Mason Loring Bliss <mason@acheron.middleboro.ma.us>
From: Armen Babikyan <armenb@moof.ai.mit.edu>
List: port-mac68k
Date: 07/13/1997 01:09:37
At 11:57 AM -0400 7/6/97, Mason Loring Bliss wrote:
>On 07/05/1997 at 5:27 PM -0400, you wrote:
>
>> running ppp over the device is something else, but the getty driver can't
>> handle it. (from my experience, anyway, like trying to use slirp or zmodem
>> file xfers)
>
>Hm... That's good news, then.

why? SLiRP uses the getty. it doesn't directly talk to /dev/tty0*. SLiRP
was intended to be used over the net, connecting and routing it's
information through the shell account's ethernet connection, then through
the internet, and to your dialup server and then to you. running it through
serial port should work somehow, but the serial getty is really unreliable,
and error-prone.

>My project for today is to set up SLiRP on
>the beastie. From there, I'm going to try to use a Plus with some old
>VersaTerm terminal server software, so *hopefully* I'll be able to have
>anyone on the net use ADSP to come into the terminal server, and from there
>have the terminal server connect to the NetBSD box using a telnet-based CTB
>tool. (The only thing I'm not sure of is if the terminal server will allow
>for multiple incoming connections through one ADSP endpoint, but I'll find
>that out. If worse comes to worse, I'll just give each machine its own
>"entrace point" on the terminal server.) This is the easiest way I can
>think of to get the NetBSD box on the network right now, given that it has
>to talk to a bunch of LocalTalked machines. If anyone has a simpler
>solution, I'd love to hear it. Otherwise, Rube Goldberg it is! :)
>

Sorry for the e-mail delay, I had lots of work I needed to do, besides the
fact that the email server was down for a few days. :\
later,
  - a