Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!ukc!icdoc!qmw-cs!liam
From: liam@cs.qmw.ac.uk (William Roberts)
Newsgroups: comp.protocols.appletalk
Subject: Re: A Mac to Unix File System (like NFS)
Message-ID: <1716@sequent.cs.qmw.ac.uk>
Date: 28 Feb 90 21:18:16 GMT
References: <1990Feb26.212826.13117@uunet!unhd> <1990Feb27.130756.1343@uunet!unhd>
Reply-To: liam@cs.qmc.ac.uk (William Roberts)
Organization: Computer Science Dept, Queen Mary and Westfield College, U of London, UK.
Lines: 58
Summary:
Expires:
Sender:
Followup-To:
Distribution:
Keywords:

In article <1990Feb27.130756.1343@uunet!unhd>  writes:
>I would also like to add that I don't want to give up my TCP/IP
>connectivity.  I read here that CAP does work without KIP, but I don't
>want to have my ethernet card doing EtherTalk all the time and not TCP/IP.
> Can you do both at the same time?  What I need is NFS-like.  Again,
>thanks for any information possible.

To clarify this (I hope):

1. KIP is about getting AppleTalk protocols around TCP/IP
networks and to hosts (unusally UNIX) that only understand IP.

2. CAP is software for UNIX boxes that implements the AppleTalk
protocol stacks, plus some applications such as being an
AppleShare file server.

3. EtherTalk is a registered Ethernet packet type, used by
Apple to ship AppleTalk protocol datagrams over Ethernets directly.


If your UNIX boxes need KIP, then CAP will be set up to send
and receive its AppleTalk datagrams via KIP (i.e. in UDP/IP
packets).

If you have the right UNIX boxes (Suns basically), then uab is
another chunk of software that will enable your UNIX box to
receive EtherTalk directly, and so you can build CAP on top of
that. KIP is then unnecessary and you don't need surplus
FastPath boxes etc.

As for TCP/IP from your Mac with an Ethernet interface: no
problem! EtherTalk packets drop out of the bottom of things
which use AppleTalk protocols (basically printing and
AppleShare), and the TCP/IP implementation sits alongside with
no conflicts at all. It makes no differences whose TCP/IP you
use either; MacTCP, TCPPort(?) or even then DIY stuff in early
NCSA Telnet.


Bottom Line(s):

* You can have both TCP/IP and EtherTalk on your Mac
* CAP gives you an AppleShare fileserver using UNIX filestore.

Does that answer your questions?


(PS for pedants: the code called KIP which loads into a FastPath
has another TCP/IP related function, namely to handle transfer
of IP packets over LocalTalk cables. If you have LocalTalk Macs
then you'll still need a gateway, but this is a separate issue
from how you arrange CAP).
-- 

William Roberts                 ARPA: liam@cs.qmw.ac.uk
Queen Mary & Westfield College  UUCP: liam@qmw-cs.UUCP
Mile End Road                   AppleLink: UK0087
LONDON, E1 4NS, UK              Tel:  01-975 5250 (Fax: 01-980 6533)