Xref: utzoo comp.protocols.nfs:283 comp.sys.mac:35044 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!intercon!amanda@intercon.uu.net From: amanda@intercon.uu.net (Amanda Walker) Newsgroups: comp.protocols.nfs,comp.sys.mac Subject: Re: NFS and Mac IIs Message-ID: <1291@intercon.UUCP> Date: 20 Jul 89 15:56:28 GMT References: <5458@b11.ingr.com> <2596@mit-caf.MIT.EDU> <1272@intercon.UUCP> <8058@hoptoad.uucp> <1289@intercon.UUCP> Sender: news@intercon.UUCP Reply-To: amanda@intercon.uu.net (Amanda Walker) Organization: InterCon Systems Corporation Lines: 25 I'd like to add to an article I just posted, in which I responded to Tim Maroney and said that a good native Mac NFS client is possible, even if difficult. After discussion with one of my co-workers, it occurred to me that this article might have given the impression that I think that such a product would be a good thing. I do not. NFS is barely capable of supporting a UNIX workstation, and as long as that's what it is used for, it's not too annoying. However, it doesn't even provide full UNIX file system semantics, much less anything approaching the Macintosh file system. Granted, this can be worked around by putting more code into the client, but this has it's own disadvantages. Even though it provides a usable interim file service solution for Sun, I would not recommend that anyone use it for Macintosh file service, at least in any more serious way than as a convenient way to transfer files between machines. Just thought I'd set the record straight :-). -- Amanda Walker InterCon Systems Corporation -- amanda@intercon.uu.net | ...!uunet!intercon!amanda