Xref: utzoo comp.protocols.nfs:1306 comp.protocols.tcp-ip.ibmpc:3850
Path: utzoo!attcan!uunet!aplcen!samsung!know!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!cassius.cs.uiuc.edu!stan
From: stan@cassius.cs.uiuc.edu (Seemong Tan)
Newsgroups: comp.protocols.nfs,comp.protocols.tcp-ip.ibmpc
Subject: Re: sos_pkt.exe ?
Message-ID: <1990Sep26.194148.2891@julius.cs.uiuc.edu>
Date: 26 Sep 90 19:41:48 GMT
References: <1990Sep25.185928.25086@usasoc.soc.mil>
Sender: news@julius.cs.uiuc.edu (USENet News)
Reply-To: stan@cassius.cs.uiuc.edu (Seemong Tan)
Organization: UIUC Systems Research Group
Lines: 16

In article <1990Sep25.185928.25086@usasoc.soc.mil>, ted@usasoc.soc.mil
(Ted Nolan) writes:
|> I snarfed the SOS NFS server from the Baylor archives last week and
|> played with it a little.  It's interesting, but it would be nicer if
|> you didn't have to set up PCNFS first to run it.  I saw something called

It doesn't really need PC-NFS specifically, just something that will provide
a socket type abstraction for it to sit on.  SOS was actually written with
the Excelan card and libraries, and Geoff Arnold later did it for PC-NFS.
If you have something like that already, try modifying socket.c to your
specifications.

|> 				Ted Nolan
|> 				ted@usasoc.soc.mil

stan