🚀 go-pugleaf

In <1993Jan23.032758.7492@netcom.com> proact@netcom.com (Proactive Software) writes:

>Our company has an application that runs on multiple platforms and we
>would like to be able to share the source code.  Currently we use NFS
>so our Sun machines and MS-DOS machines can access the same source code.
>How can we hook up our Macintoshes into this environment?  Is there a NFS
>product for the Macintosh that uses the MacTCP drivers and etherTalk?

There are a few: Wollongong Pathway NFS;  Intercon Mac NFS (?); .... 
But convince yourself that they do what you want.
I need a product that does *automatic* translations of Unix EOLs
(end-of-lines) to Mac EOLs.  I need that capability ``in both directions'': 
i.e. for files copied to the Mac from a Unix disk, and vice versa.
More than a year ago the Mac NFS packages I've heard of could not do that.
Maybe the latest releases can...

>Is the CAP software my solution?  Can CAP give my macs access to my 
>directories on the Unix machine?  

I think you will like it: it does EOL translations of text files
in both directions.
It also allows you to specify mappings of Unix filename extensions to
Mac file types/creators.  You can also specify a default file type/creator
(I've set that to "MPW Shell text files").
The only problem I have has to do with file dates/times after a
copy from Mac to Unix.  You can configure CAP such that the Unix-resident
file (when viewed from the Mac  with Get Info for example) 
still has the same date/time as its original on the Mac, but when
viewed from Unix (ls -l) the file's modification date/time is that of the
copy action.  That can give some problems with make files, but not
if you do all editing on the Mac (as I tend to do).

Good luck,
-----------------------------------------------------------------------------
Fred Walsteijn                                | Internet: walsteyn@fys.ruu.nl
Institute for Marine and Atmospheric Research | FAX:      31-30-543163
Utrecht University, The Netherlands           | Phone:    31-30-533169