Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!ns-mx!iowasp.physics.uiowa.edu!maverick.ksu.ksu.edu!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!fcom.cc.utah.edu!npd.novell.com!newsun!donp
From: donp@na.excelan.com (don provan)
Newsgroups: comp.sys.novell
Subject: Re: NFS Support in NetWare
Message-ID: <1991Mar9.230016.3431@novell.com>
Date: 11 Mar 91 15:22:37 GMT
Sender: news@novell.com (
Lines: 31

The News Manager)
Nntp-Posting-Host: na
Reply-To: donp@novell.com (don provan)
Organization: Novell, Inc., San Jose, California
References: <6807@spdcc.SPDCC.COM>
Date: Sat, 9 Mar 1991 23:00:16 GMT

In article <6807@spdcc.SPDCC.COM> rbraun@spdcc.COM (Rich Braun) writes:
>I wrote:
>>>Is the Novell solution also going to offer a DOS _client_ NFS package?
>
>From Novell, donp@na.excelan.com (don provan) writes:
>>Novell provides a DOS *NetWare* client with their server.  What would
>>be the point of also offering a DOS NFS client in the same package?  I
>>dare say the NetWare client provides much better connectivity with the
>>NetWare server than an NFS client could.
>
>What would be the point?  My friend, interoperability's the point.

Providing interoperability would be a justification for providing a
DOS NFS client as a separate product, but it provides very little
value as a piece of an NFS product built on top of NetWare.

>But DOS users are still stuck with accessing only files on the Novell
>servers, unless Portable Netware is installed on the Unix systems.

But you just told us that all those other NFS systems come with a DOS
NFS, so they're already set.  They *have* to provide DOS NFS to
provide themselves DOS connectivity.  My point was that NetWare
already has better DOS connectivity, so an NFS DOS client would be
redundant for NetWare's NFS product.
						don provan
						donp@novell.com