Xref: utzoo comp.protocols.tcp-ip.ibmpc:981 comp.protocols.nfs:64
Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!gatech!purdue!decwrl!decvax!eagle_snax!geoff
From: geoff@eagle_snax.UUCP ( R.H. coast near the top)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.nfs
Subject: Re: Public Domain NFS
Message-ID: <437@eagle_snax.UUCP>
Date: 19 Dec 88 16:41:05 GMT
References: <8812161212.aa12957@Louie.UDEL.EDU> <8812170248.AA03407@asylum.sf.ca.us>
Reply-To: geoff@eagle_snax.UUCP (Geoff Arnold @ Sun ECD - R.H. coast near the top)
Organization: Sun Microsystems - East Coast Division
Lines: 22

In article <8812170248.AA03407@asylum.sf.ca.us> romkey@asylum.sf.ca.us writes:
>Yeah, unfortunately the worst part of an NFS implementation on an IBM
>PC is writing the redirector,
>[...]
>Next to this, I expect the implementation of the NFS protocol itself
>to be almost a non-issue.
>			- john

Almost true, but there are still many problems related to the
NFS protocol implementation. Things like how and where you cache
things to avoid unnecessary network traffic (directory searching is a good
example); how you manage 32-byte file handles (you certainly can't
store them in the FCB!); and how you map the various error
conditions into the DOS error-handling framework (and coping with all those
bugs - especially in DOS 3.0 and 4.0). Lots of good(?) stuff to keep
engineers busy during the long winter nights...

-- 
Geoff Arnold, Sun Microsystems Inc.  +--------------------------------------+ 
PC Dist. Sys. Group (home of PC-NFS) |When you're fresh out of lawyers, you |
UUCP: {hplabs,decwrl...}!sun!garnold |don't know how good it's going to feel|
ARPA: garnold@sun.com                +--------------------------------------+