🚀 go-pugleaf

In article <1992Aug14.151242.6333@ldp.com> rolfe@ldp.com writes:
>In article <1992Aug13.041127.8872@cubetech.com> andrew@cubetech.com (Andrew  
>Loewenstern) writes:
>> In article <1992Aug12.140612.10627@ldp.com> rolfe@ldp.com writes:
>(Original question about NeXT serving Macs delted)
>
>> >You can install CAP, although currently it requires an Ethernet/Localtalk  
>> >router like a Fastpath or Gatorbox.  I don't know whether 3.0's support  
>for  
>> >Appletalk in the kernel will change this, but I would think it should.   
>Other 
>> >than that glitch, CAP works great and is fairly mature at this point.
>> 
>> No, 3.0 only lets you become an AppleShare _client_ and not a
>> sever.  You'll need something like uShare to get the Macs talking
>> TCP/IP and NFS to let the NeXT be a server.
>> 
>
>Yes, I realize that, but my point was that NeXT has obviously put Appletalk  
>support in the kernel in order to support the Appleshare client stuff that  
>ships with 3.0.  With that in place, I would think the CAP maintainers could  
>come up with the patches to support Ethertalk.  Currently this support only  
>exists for Suns and DecStations, although CAP runs on a whole slew of  
>hardware.

3.0 does run ethertalk, but there is no server support or API to
AppleTalk.  It would be way better to port the entire CAP package and
not run the 3.0 client than to try and hot-wire portions af CAP in
without stepping on the toes of the NeXT AT client.


andrew
-- 
andrew@cubetech.com     | "We shall not cease from exploration
Andrew Loewenstern      |  And the end of our exploring
Cube Technologies, Inc. |  Will be to arrive where we started
                        |  And know the place for the first time." -T.S. Eliot