Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!cory.Berkeley.EDU!stan
From: stan@cory.Berkeley.EDU (See-Mong Tan)
Newsgroups: comp.protocols.nfs
Subject: Re: PC NFS
Summary: DOS file server and Unix
Keywords: Integration of PCs and SUNs
Message-ID: <14359@pasteur.Berkeley.EDU>
Date: 4 Jun 89 19:09:43 GMT
References: <17676@vrdxhq.verdix.com> <577@eagle_snax.UUCP> <16545@paris.ics.uci.edu>
Sender: news@pasteur.Berkeley.EDU
Reply-To: stan@cory.Berkeley.EDU.UUCP (See-Mong Tan)
Followup-To: comp.protocols.nfs
Distribution: na
Organization: University of California, Berkeley
Lines: 26

In article <16545@paris.ics.uci.edu% Alastair Milne <milne@ics.uci.edu% writes:
%
%%... SOS, a DOS NFS server written by See-Mong Tan at LBL.
%%You can FTP it from lbl-csam.arpa in /pub/sos.tar.Z.
%
%    A great tip, thanks!  I have ftp'd it already.  I tried running it, just
%    for fun, on one of the Tandy's, but it just reported 4 things it couldn't
%    do, and gave up.  I suspect it needs PC-NFS disabled first.  I need a
%    closer look at the man sections.  (If it's for DOS, why is it so UNIX
%    oriented?)

The server program works with PC-NFS's socket libraries, courtesy of
Geoff Arnold.  There are some things you must set up first, like a file
with a list of exported filesystems, etc., and I don't think you want
to *disable* PC-NFS.

Why is it so Unix oriented?  I can think of a few reasons:

1.  I'd never worked with a PC before.  So when I did the docs, the
best choice was troff for me, since...

2.  It's Berkeley here, I grew up on BSD Unix.  :-).

---
stan@lbl-csam.arpa
stan@csam.lbl.gov