rbraun@spdcc.COM (Rich Braun) (05/17/91)
SOSS Version 3.2 - An NFS server for DOS
----------------------------------------
SOSS is a file server conforming to SUN Microsystems' NFS protocol
version 2. It will run on IBM-PC compatibles under Microsoft
MS-DOS, using any Ethernet interface supported by Clarkson
University's packet drivers.
Version 3.2 has the following improvements over version 3.1:
- I/O requests can be up to 1024 bytes long; the old limit
was 512.
- Writing to a file now sets the correct modification time.
- A filesystem with 0 bytes free can now be mounted.
- A detailed installation guide has been written.
It can be used in a standalone environment as a file server for
DOS or Unix users running client NFS (e.g., Sun PC-NFS), or it can
be used within a Novell NetWare environment to provide transparent
access to files on Novell servers via NFS.
SOSS relies on source code taken from PC/IP, a public-domain TCP/IP
package developed at CMU and MIT. It also relies on packet drivers
collected and distributed by Clarkson University. These drivers
allow you to set up a dual-protocol stack, allowing simultaneous
access to TCP/IP and NetWare using a single Ethernet interface card.
(They are in a file called drivers.zip on sun.soe.clarkson.edu and
on many of the same systems which carry SOSS.)
SOSS is free software. You may use it within your organization for
any purpose desired. You may redistribute it to other organizations,
provided you do not earn a profit when doing so, that you make source
code available, and that you abide by the terms of the Gnu General
Public License (see the file COPYING).
The following systems currently distribute SOSS via anonymous ftp:
System Directory Contact
------------ --------- -------
spdcc.com pub/sos rbraun (MA)
sun.soe.clarkson.edu pub/ka9q nelson (NY)
grape.ecs.clarkson.edu pub/msdos/tcpip nelson (NY)
cs.ep.utexas.edu pub/sos pwesley (TX)
garbo.uwasa.fi pc/connect hv (Finland)
kirk.bu.oz.au pub/pc/net/soss bambi (Australia)
nestroy.wu-wien.ac.at pub/src/PCtcp/soss mah (Austria)
The following system currently distributes SOSS via anonymous uucp or
via a BBS download:
System Phone Number Directory Contact
------------ ------------ --------- -------
sir-alan.UUCP 812 333 0450 /u/pubdir/SOSS mikes@iuvax.cs.
indiana.edu
For more information on uucp/BBS sites contact the SYSOP directly.
BITNET access:
Bitnet sites can access a mail-server called BITFTP@PUCC.BITNET;
just send a message HELP to that address to get just that (i.e
help). Example of a connection to sun.soe.clarkson.edu follows:
FTP sun.soe.clarkson.edu UUENCODE
USER anonymous
CD pub/ka9q
DIR
BINARY
GET driverss.zip
QUIT
E-mail retrieval:
Send mail to archive-server@sun.soe.clarkson.edu with a body
containing the single word "help". That works for everybody,
BITNET, UUCP, whatever.
Direct modem retrieval:
You can phone in to grape.ecs.clarkson.edu at (315) 268-6667,
and download pub/msdos/tcpip/soss.zoo.
When in doubt:
Or send $10 for a floppy diskette. Be sure to say what disk
density you want.
Russell Nelson
11 Grant St.
Potsdam, NY 13676
SOSS was written by See-Mong Tan, Harvard Holmes, Craig Eades, and
Richard Braun.
[You may repost this for the benefit of others.]gtoal@tardis.computer-science.edinburgh.ac.uk (05/18/91)
In article <7539@spdcc.SPDCC.COM> rbraun@spdcc.COM (Rich Braun) writes: > > SOSS Version 3.2 - An NFS server for DOS > ---------------------------------------- > > SOSS is a file server conforming to SUN Microsystems' NFS protocol > version 2. It will run on IBM-PC compatibles under Microsoft > MS-DOS, using any Ethernet interface supported by Clarkson > University's packet drivers. > > Version 3.2 has the following improvements over version 3.1: > > - I/O requests can be up to 1024 bytes long; the old limit > was 512. I recently put up the previous version of Soss on a Dos PC to talk to my Acorn Archimdes using NFS. It's a *great* product - thanks for writing it and especially thanks for distributing it with source. However, I have a problem: the archimedes isn't a Unix machine (far from it), and the mount command doesn't have the option of changing block sizes. This isn't a problem on server->client data transfers, as the client asks for an 8K packet and is turned down, with the result that in future it asks for smaller and smaller packets until it gets one that works. *But*... this doesn't work in reverse, because any time I try to copy a file from the Archimedes client to the server, the server crashes - having been sent an 8K block. I suspect that the new code with 1K blocks might do the same - is the fault at the packet-driver level rather than soss itself? I *did* try recompiling soss with a mega-large packet size (9KI think i tried) but it didn't help, although it didn't crash - gave a protocol error instead. Any suggestions? I know it's not Soss's problem, but fixing the problem in the Client nfs isn't an option :-( [One day manufacturers will give their sources out too, if they can get over their embarrassment] Graham Toal <gtoal@ed.ac.uk>
geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) (05/20/91)
Quoth gtoal@tardis.computer-science.edinburgh.ac.uk (in <9105180950.AA22237@ucbvax.Berkeley.EDU>): #However, I have a problem: the archimedes isn't a Unix machine (far #from it), and the mount command doesn't have the option of changing #block sizes. This isn't a problem on server->client data transfers, #as the client asks for an 8K packet and is turned down, with the #result that in future it asks for smaller and smaller packets #until it gets one that works. # #*But*... this doesn't work in reverse, because any time I try to #copy a file from the Archimedes client to the server, the server #crashes - having been sent an 8K block. I suspect #that the new code with 1K blocks might do the same - is the fault #at the packet-driver level rather than soss itself? # #I *did* try recompiling soss with a mega-large packet size (9KI think #i tried) but it didn't help, although it didn't crash - gave a protocol #error instead. # #Any suggestions? I know it's not Soss's problem, but fixing the problem #in the Client nfs isn't an option :-( [One day manufacturers will #give their sources out too, if they can get over their embarrassment] I assume that SOSS is advertising a TSIZE of 1024 in the "statfs" call, in which case Acorn is violating the spec by sending more than 1K of data. Acorn should DEFINITELY fix this. Are they on the net? Geoff -- Geoff Arnold, PC-NFS architect, Sun Microsystems. (geoff@East.Sun.COM) -- ------------------------------------------------------------------------------ -- Sun Microsystems PC Distributed Systems ... -- -- ... soon to be a part of SunTech (stay tuned for details) --