> 
> Hi all:
> 
> I've read the posts telling of the lower priority for localtalk/ethertalk
> implementation, but let me please cast another vote for implementing this
> soon.
> 
> So far I have netbsd up and running (despite slow hard drives) and have
> gotten apache, perl and msql running together. The biggest problem now,
> wishing to program and test web cgi apps, is having to reboot every time I
> want to load a new script or whatever onto the macunix box.

Where are these files coming from that you have to reboot?

> Using a mac only system I link up a couple machines locally through mactcp
> and PPP, communicating to a machttp server and macperl.  It runs great and
> is very handy for web development, and no ethernet is necessary (although
> of course etalk is faster and mo' better.)
>
> If only I could talk to my macbsd box as easily, I can control my entire
> system (including a win95 portable) and my remote sparcstation from a
> single inhouse computer - cheap!

I'm confused. You asked about LocalTalk support, but AFAIK, win95 and
SPARC boxes don't support LocalTalk. Also, they don't naturally support
AppleTalk; they seem to like IP better (well, the SPARC anyway). We have
IP support now.

Just hook up a serial line and fire ppp up over a serial port. It's not
as fast as LocalTalk (by a factor of 4), but is lighter weight and works
now.

> Does anyone else out there want tcp/ip through a localtalk connection? ==Don

Yes. It would be the second stage of LocalTalk support. But I've not found
any documentation on how to run IP over DDP (well, how Apple does it).

Take care,

Bill