Xref: utzoo comp.protocols.nfs:2034 comp.windows.ms:10488 comp.protocols.tcp-ip.ibmpc:5219 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac,att!emory!wuarchive!mit-eddie!uw-beaver!ubc-cs!alberta!cpsc.ucalgary.ca!ajfcal!napc!rasmus From: rasmus@napc.uucp (Rasmus Lerdorf) Newsgroups: comp.protocols.nfs,comp.windows.ms,comp.protocols.tcp-ip.ibmpc Subject: Re: Sun PC-NFS deficiencies Message-ID: <1991Mar18.012523.4241@napc.uucp> Date: 18 Mar 91 01:25:23 GMT References: <1991Mar13.180625.14540@amd.com> <1541@fs1.ee.ubc.ca> <1991Mar16.015158.20566@amd.com> Organization: NovAtel Communications Lines: 14 In <1991Mar16.015158.20566@amd.com> phil@brahms.amd.com (Phil Ngai) writes: >I could disagree, but you are getting distracted. My point is this: >Sun PC-NFS is NO NETWORK to Microsoft Windows. And Novell is NO NETWORK to my Unix boxex boxes running TCP/IP. What's the fuss? Novell and PC/NFS are geared towards different environments. Right now I am running both. I wish there was one package that did it all, but there isn't, so one must live with the deficiencies of both in order to gain the benefits of both. -- Rasmus Lerdorf calgary!ajfcal!napc!rasmus 1020-64 Ave NE, Calgary NovAtel Advanced Product Concept Development Alberta, Canada T2E 7V8