Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!aero-c!usasoc.soc.mil!news
From: ted@arsocomvax.socom.mil (Ted Nolan)
Newsgroups: comp.protocols.nfs
Subject: Re: PCNFS, NCSA and Clarkson drivers
Message-ID: <1991Apr19.145051.11844@usasoc.soc.mil>
Date: 19 Apr 91 14:50:51 GMT
References: <7474@einstein>
Reply-To: ted@usasoc.soc.mil (Ted Nolan)
Organization: SRI International, Ft. Bragg NC
Lines: 22

This has come up before, and packet drivers are sort of a red herring
in that they obscure what you really need.

The two issues involved (Running PC-NFS with packet drivers, and running
Clarkson's modified NCSA telnet on PC-NFS) are really separate.

It is difficult (though possible) to run the packet driver version of
the Clarkson cutcp telnet with PC-NFS, since both telnet and PC-NFS
(even with the packet driver interface) both want all the packets.
What is (easily) possible is to run the version of cutcp telnet which
was built with the PC-NFS toolkit, and uses PC-NFS to do it's network
i/o.  This version will use whatever ethernet driver PC-NFS uses,
whether it is the packet driver driver or not.

The toolkit version of telnet was v2.2-A and is available on
omnigate.clarkson.edu in pub/cutcp/v2.2-A/pc-nfs.cutcp.zoo.  There is a
bug in the tn3270 provided in that "auto skip fields" do not work properly,
but we have been using the vanilla telnet with general success.

		
				Ted Nolan
				ted@usasoc.soc.mil