Subject: Re: your mail
To: Andrew Foakes <netbsd@foakes.demon.co.uk>
From: Falk Stern <falk@frickel.sitecom.de>
List: port-mac68k
Date: 07/20/1998 13:03:43
On Sun, 19 Jul 1998, Andrew Foakes wrote:

> Hello,
> 
> This is the second time I've been part of this list.  Both times, I've 
> tried to run NetBSD on a Classic II.  The first time was with version 1.2 
> and the ADBTEST version 164 kernel, which was OK, but X was ill behaved 
> and there were some petty problems with the screen (vt220 emulation) and 
> the keyboard.  This time I'm using version 1.3.2 with Norikai Yamada's c2 
> kernel, and all is wonderful.  X now works as it should, the screen is 
> never caught out and there is even a ksh!  So first off, a big thank you 

I am glad to hear this :)
Now I can wipe the dust off my old Classic II and use it as an intelligent
terminal :)))
 

> 
> But, all this still makes it a stand alone box.  It would be ideal if I 
> could get my Classic to talk to the rest of my network.  Under MacOS, I 
> use a Farallon EtherWave adapter that connects via the printer port.  
> Given that I suspect the chip inside this is the same as other EtherWave 
> boxes and hence is supported, is there any way I can get NetBSD to squirt 
> TCP through the printer port?  Where do I start to look for 
> hints/tips/code etc?

Uhm, do you have another Un*x machine hooked up to the network?
You could use ppp to connect.. thats the way I hooked my Classic up to my
network.

Start pppd on the "remote" Computer (the one with ethernet):

pppd /dev/ttyXX 57600 <ip of the "ethernet" machine>:<ip of the classic>\
proxyarp

On the Classic: 
pppd /dev/tty01 (?) 57600 <classic's ip>:<remote ip>

Worked for me.

So far..
===============================================================================

Falk Stern
Sitecom - Agentur fuer neue Medien <http://www.sitecom.de>