Path: utzoo!attcan!uunet!husc6!uwvax!vanvleck!uwmcsd1!ig!agate!ucbvax!decwrl!muscat!jfcl.dec.com!decvax!eagle_snax!geoff
From: geoff@eagle_snax.UUCP ( R.H. coast near the top)
Newsgroups: comp.sys.apollo
Subject: Re: Apollo's NFS !!
Summary: different product, NOT different protocols
Message-ID: <308@eagle_snax.UUCP>
Date: 14 Jun 88 13:51:51 GMT
References: <3c80c931.4653@apollo.uucp> <1994@ssc-vax.UUCP> <1825@stpstn.UUCP>
Lines: 29

In article <1825@stpstn.UUCP>, aad@stpstn.UUCP (Anthony A. Datri) writes:
> > theoretically since it is a fully functional NFS this should be 
> > possible..right?
> 
> Whoa!  The pcnfs stuff I've seen from Sun seems to regard pcnfs as
> a separate but related system, not a part of nfs (sorta like tftp/ftp).
> You don't always get pcnfs with nfs -- different daemons.

[Wot? A Sun person posting to comp.sys.apollo?! Oh, well...]

This is a very misleading characterization of PC-NFS. PC-NFS is
a complete client-only implementation of the NFS protocols, and will
interoperate with any correct NFS server implementation "as is", with
no additional daemons. To improve the usability of the PC-NFS product
we supply an additional daemon which provides network authentication and
print services, but this is not required for correct NFS operation. (You
can think of PCNFSD as an alternative to "lpd" plus an authentication
daemon, rolled into one.)

It's correct that you don't "get" pcnfs with nfs. It's a product which
we sell, just like many NFS vendors sell their NFS implementations.
Others bundle NFS into the base OS. It's a marketing choice which has
nothing to do with protocols, interoperability, or daemons....

-- 
Geoff Arnold, Sun Microsystems     | "We didn't set out to kill anyone"
TOPS at ECD (home of PC-NFS)       | [Reagan on the Libyan air raid, included
UUCP:{ihnp4,decwrl...}!sun!garnold | in "Quotations of Chairman Ron" along
ARPA:garnold@sun.com               | with other insightful observations.]