Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bbs!karl
From: karl@naitc.naitc.com (Karl Denninger)
Newsgroups: comp.protocols.nfs
Subject: Re: Enduring PC-NFS Annoyances
Summary: Get Beame and Whiteside NFS; it doesn't have these problems
Message-ID: <1990Oct31.213006.12428@naitc.naitc.com>
Date: 31 Oct 90 21:30:06 GMT
References: <10083@uhccux.uhcc.Hawaii.Edu>
Reply-To: karl@bbs.naitc.com (Karl Denninger)
Organization: A.C. Nielsen Co.
Lines: 74

In article <10083@uhccux.uhcc.Hawaii.Edu> pilger@uhunix1.uhcc.Hawaii.Edu (Eric Pilger) writes:
>From: A Dedicated User of PC-NFS
>To: The Fine, Upstanding Programmers at Sun
>Re: When Will It Be Fixed?
>
>- Why do I, as often as not, have to use <Ctrl-Break> to unstick a
>"net ypset *" and continue?
>
>- When will I be able to open more than 6 Windows on my X server
>software (eg. fix the socket overload bug AND provide more sockets)?
>
>- Will you (or do you) get together with some of these people writing
>X servers and help them optimize and debug their code (and yours?)
>This would only further my commitment to PC-NFS.  If PC-NFS doesn't
>keep up, I'll be forced to find a solution that does, as much as I
>like what PC-NFS has to offer.
>
>- Why is there such a stiff penalty for reads and writes on a socket
>(order of 1/5 second of overhead?)  Is this the fault of using a DOS
>device driver?  Would send() and rcv() be faster? (Note: rpc's display
>none of this overhead.  Do they use send() and rcv()?)

Try Beame and Whiteside.

We're using it here.  It has the following nicities:

1)	It isn't serialized.  This isn't a license to cheat; rather, it's
	a way to keep control reasonable (do YOU want a filing cabinet full
	of 300 licenses and disks for same?!)

2)	It works with packet drivers out of the box.

3)	It's fast.

4)	It's solid, knows how to do printer redirection, and WORKS WITH
	WINDOWS 3, including printer support.  NO PHANTOM DRIVES and NO
	crashes!

5)	Coexists with QEMM for 590K free TPA under MSDOS (finally!)

6)	Knows what YP is and can use it.

7)	Avoids the nasty SUN rpc.lockd bugs if needed (or can be compatible
	with rpc.lockd, your choice on a drive-by-drive basis).

8)	Has available an INT14 redirector -- virtualize a terminal
	connection!  This is beautiful; net-aware terminal programs like
	Kermit can hit a host with "ATDT hostname" and the system will
	figure out what you need and get you there.  Works JUST like a
	hayes modem..... works through Telnet connections..... one of the
	best features in the package.

9)	Requires only ONE daemon for all systems if you want, or allows you
	to run many daemons and distribute authorization authority.

10)	Comes with a Telnet that knows what tn3270 is, and uses it if
	appropriate.

11)	Has lots of other nice things including, including ypcat, nslookup,
	traceroute (!) and a few others.

12)	MOST IMPORTANT:
	An author who is reachable and fixes things RIGHT NOW if they are
	even broken.  The support is absolutely A-1 grade.  That's something 
	I'll never be able to say about Sun.

Try B&W NFS -- you'll like it.

--
Karl Denninger	AC Nielsen
kdenning@ksun.naitc.com
(708) 317-3285
Disclaimer:  Contents represent opinions of the author; I do not speak for
	     AC Nielsen on Usenet.