Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!uunet!intercon!amanda@intercon.com From: amanda@intercon.com (Amanda Walker) Newsgroups: comp.protocols.nfs Subject: Re: NFS on a mac Message-ID: <1505@intercon.com> Date: 20 Oct 89 17:13:17 GMT References: <1989Oct19.020908.24069@terminator.cc.umich.edu> <10165@encore.Encore.COM> <940@east.East.Sun.COM> Sender: news@intercon.com Reply-To: amanda@intercon.com (Amanda Walker) Organization: InterCon Systems Corporation Lines: 23 In article <940@east.East.Sun.COM>, geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes: > Can anyone who's worked extensively with A/UX (did I get the slash in > the right place?) comment on how well Apple handled the problems of viewing > the Mac FS from Unix and vice versa? In A/UX 1.1, they did a pretty good job of mapping the file system itself (using AppleDouble files), but it's only basic HFS--no desktop manager, etc. The biggest problem is that a lot of things that are cheap on a local file system involve lots of NFS transactions (like directory lookups). File operations are some of the simpler ones to map... Concerning MacNFS in particular, I am wondering how much of the alleged delay in its release is due to Apple's evident dislike for distributing code that other people have rights to? If the CITI folks used a lot of the Sun NFS client code, I can see how Apple's lawyers could be raising, um, heck :-). -- Amanda Walker "Tobacco is the only drug in America that will kill you if it's taken as directed." --Dr. C. Everett Koop, former U.S. Surgeon General