HDTenEightyP/NetNews huggingface dataset:
From: john@iastate.edu (John Hascall)
Subject: Re: Use of reserved port (on Ultrix)
Organization: Iowa State University, Ames, IA
Date: Mon, 9 Nov 1992 21:34:44 GMT

luigi@pical2.uucp (Luigi Rizzo) writes:
}
}I have troubles with 386BSD in mounting a disk from a Decstation
}(running Ultrix 4.1 for what it matters). The server keeps replying
}
}Bad MNT RPC: RPC: Authentication error; why = Invalid client credential
}
  As I recall, Ultrix 4.1 NFS gags on mount requests from clients
  presenting more than 8 groups in the credentials.

  Fixes include:
        * reduce group count of client
        * install Ultrix 4.2 or later mount daemon
          (probably could use a BSD4.2 mount daemon too)
        * upgrade to Ultrix 4.2 or newer

John
-- 
John Hascall                   ``An ill-chosen word is the fool's messenger.''
Systems Software Engineer
Project Vincent
Iowa State University Computation Center  +  Ames, IA  50011  +  515/294-9551
Newsgroups: comp.protocols.nfs
From: beame@maccs.dcss.mcmaster.ca (Carl Beame)
Subject: Re: Apparent bug with DOS 5 XCOPY.EXE and PC-NFS
Keywords: xcopy dos nfs
Organization: McMaster University, Hamilton, Ontario, Canada.
Date: Fri, 6 Nov 1992 04:27:08 GMT

In article <1992Nov5.045412.20596@kirk.bu.oz.au> bambi@bu.oz.au (David J. Hughes) writes:
>roff@felon.icsl.ucla.edu (David Roff) writes:
>
>>We've discovered an apparent bug involving the interaction of DOS 5.0's 
>>XCOPY command and PC-NFS.  When running a batch file containing several
>>XCOPY statements in succession, copying files from a local hard disk to
>>a network drive, DOS will occasionally report it can't find selected files.
>>Issuing the same XCOPY statements via command line, however, works fine.
>>Moreover, using COPY instead also works.  Is this a well known bug?  Any
>>fixes?
>
>If you are using XCOPY to do large recursive copies then you will often
>run into problems (not sure if this is the case as the original posting
>doesn't contain many details).  The cause of this is the redirector used
>to access a remote volume often runs out of internal buffers if the
>recursion is too deep.
>

	Basically, the problem has to due with the DOS Findfirst/Findnext
functions and their mapping to NFS calls. The firstfirst function returns
to the users a structure which contains the filename and 21 bytes of
reserved data which define where a findnext will start in the directory
search. The findnext can be called at ANY point in the future (immediatly
or maybe in an hour or so ... :-) ). To perform a "findnext", the NFS client
must pass to the NFS server, a 32 byte directory handle and a 4 byte "cookie"
as well as have stored the filename matching information passed in the findfirst
call. This information does not fit the 21 byte DOS reserved area and
therefore the client NFS must allocate an internal buffer to place this
information and put a pointer to it in the 21 byte DOS structure.

	An XCOPY will usually have 1 outstanding findnext for every level
of directory. Under DOS 5.0 there can be 32 directory levels. In our
NFS (BWNFS) several versions ago, we HAD a problem which a program which
used the C stat() call on all files. The stat() call uses Findfirst with out
any findnexts.  

	After all this, I don't think this is the problem with copying files
from the PC to the server as XCOPY does many findfirst/findnext on the
destination of the copy. The finds are done on the source.

Carl Beame
Beame & Whiteside Software
tech@bws.com
From: sxn@eng.sun.com (Steve Nahm)
Newsgroups: comp.protocols.nfs
Subject: Re: Source of RPC !!!
Date: 7 Nov 92 04:46:03 GMT
Organization: Sun Microsystems Inc., Mountain View, CA
NNTP-Posting-Host: rand

aaraya@tolten.puc.cl (Arnoldo Araya Flores) writes:

>Hello.

>Does anybody know where the sources of RPC's are ?

Here are two messages.  The first tells how to get RPCSRC 4.0 (the old
transport-specific UDP/TCP interfaces), while the second talks about TIRPCSRC
1.0 (the flavor of RPC that's in SVR4 and Solaris 2.x).

Steve
-----
RPCSRC 4.0:

Sun's freely licensed RPC/XDR implementation, RPCSRC 4.0, is now
available via anonymous ftp from bcm.tmc.edu and by email from the
archive-server@bcm.tmc.edu.

If you use the archive server, send mail to archive-server@bcm.tmc.edu
with a Subject of "send nfs index" to see all the names of the files.
Sending a message with the Subject "help" will return to you more
information about the archive server itself.

To use anonymous FTP, use the ftp program to connect to bcm.tmc.edu.
When prompted for a user name, enter "anonymous".  When prompted for
a password, enter your user ID (such as "joeuser@sun.com").  Then
change directories (cd) to the "nfs" directory, where you will find
the RPCSRC files.

There are 17 shar files in the main library and 4 shar files for
secure rpc.

(RPCSRC 4.0 is also available from the sun-spots archive; use titan.rice.edu
for FTP and archive-server@rice.edu for email.)


TIRPCSRC 1.0:

Sun's freely licensed implementation of Transport Independent RPC
(TIRPC), is now available as source code via anonymous ftp from
ftp.uu.net in the directory "networking/rpc" as the file named
tirpcsrc.tar.Z.  This is a compressed tar file.  This implementation of
TIRPC is compatible with SunOS 4.1 *only*, and requires root
priviledges for installation.

TIRPC is the version of Sun RPC that is part of System V Release 4
(SVR4).  See the "README" file in the distribution, as well as the
files in the doc and man directories, for further information.

To use anonymous FTP, use the ftp program to connect to ftp.uu.net.
When prompted for a user name, enter "anonymous".  When prompted for a
password, enter your user ID (such as "joeuser@sun.com").  Then change
directories (cd) to the "networking/rpc" directory, where you will find
tirpcsrc.tar.Z.

Also, TIRPC can be obtained on 1/4-inch tape from Sun for a $100 media
fee.  The tape also includes Sun's older sockets-based RPC (RPC Source
4.0) as well as a Beta version of TIRPC Source from SunSoft's upcoming
Solaris 2.0 (SVR4).  Send a check payable to SunSoft, Inc. to:

Dennis Freeman
ONC/NFS Technology Marketing Manager	
SunSoft (a Sun Microsystems Company)
2550 Garcia Ave., MTV08-111
Mountain View 94043
Voice (415) 336-0955; Fax (415) 336-5620
Email: dennis.freeman@Eng.Sun.Com
--
Steve Nahm                              sxn@sun.COM or sun!sxn
Sun RPC Project Lead
From: kaz@uni-paderborn.de (Kay Mueller)
Newsgroups: comp.protocols.nfs
Subject: Re: PC-NFS and Novell 2.2
Date: 6 Nov 92 14:43:15
Organization: Uni-GH Paderborn, Germany
NNTP-Posting-Host: honi.uni-paderborn.de
In-reply-to: dan@willamette.edu's message of 2 Nov 92 23:16:11 GMT

>>>>> Ueber PC-NFS and Novell 2.2 sagte Dan Revel:
Dan> Article-I.D.: willamet.Bx43B2.CIq

Dan> Is it possible to run a PC as both a Netware and a PC-NFS client at the
Dan> same time?  How would I go about doing that?  I am familiar with PC-NFS
Dan> and TCP/IP but am unsure how to go about getting that to co-exist with
Dan> Novell.

Dan> Thanks,
Dan> -- 
Dan> Dan Revel (dan@willamette.edu)					Nullum
Dan> Network and Technical Services					Gratuitum
Dan> Willamette University						Prandium

Hi Dan,

it is, I've just installed it.
You need the clarkson package drivers, intelpd.zip (which provides you with
an extended version of the clarkson ipx.com) and ipxpkt.com and net5.exe
(ask archie where to get them, I don't know)
With PCNFS 3.5 it works fine.

CU
Kay
From: guy@Auspex.COM (Guy Harris)
Newsgroups: comp.protocols.nfs
Subject: Re: wierd uid src code in pcnfsd v2
Date: 12 Nov 92 06:46:06 GMT
Organization: Auspex Systems, Santa Clara

>#on aix for example, uid's are LONG, so they can go up to 4gazillion
>#or whatever.  what's the deal?

...

>Now, on Solaris 1 and Solaris 2, UID_MAX is explicitly
>defined as 60002.

Note, though, that UID's are 32 bits in SVR4 32-bit systems (including
Solaris 2.x), although that's Phase 1 of Lumpy Gravy^H^H^H^H^H^H^H the
big Ex{pand,tend}ed Fundamental Types conversion, so the OS is supposed
to limit UID (and GID) values to those values that fit in the old 16-bit
fields.  Future SV releases will, presumably, lift that limitation.
From: curt@ekhadafi.austin.ibm.com (Curt Finch 903 2F021 curt@aixwiz.austin.ibm.com 512-838-2806)
Newsgroups: comp.protocols.nfs
Subject: wierd uid src code in pcnfsd v2
Date: 10 Nov 92 16:04:21 GMT
Organization: IBM AWD, Austin

what is the deal w/ this routine?
y is it unreasonable to have a uid outside of the range 101-60002?

on aix for example, uid's are LONG, so they can go up to 4gazillion
or whatever.  what's the deal?

 
 /*
 ** val_uid(u)
 **
 ** Return non-zero if the uid is legal - within range
 ** and zero otherwise.
 **
 ** If uid_range is NULL, check for 101-60002. Otherwise
 ** check against ranges.
 */
 int
 val_uid(u)
 int u;
 {
       int i;
 
       if(uidrsize == 0)
               return(u >= 101 && u <= 60002);
 
       for (i = 0; i < uidrsize; i++)
               if (u >= uidrlo[i] && u <= uidrhi[i])
                       return(1);
       return(0);
 }

-- 
--
curt@aixwiz.austin.ibm.com (Curt L. Finch) | AIX NFS/NIS Field Quality 
My views are unrelated to those of IBM     |        Austin, TX
- FICA isn't a retirement plan. Your money's already spent. You'll get zilch.-
Newsgroups: comp.protocols.nfs,comp.protocols.tcp-ip.ibmpc
From: scott@ethome.et.iupui.edu (Scott Orr)
Subject: Re: Can you chmod 111 in a DOS NFS redirector? 
Reply-To: scott@ethome.et.iupui.edu	
Organization: Purdue University's School of Engineering & Technology @ Indianapolis
Date: Wed, 11 Nov 92 17:01:18 GMT

There is another "trick" you can try.  If the .exe file needs to read itself
when it runs, mark the file as hidden.  I can't speak for PCNFS, but setting
the setuid bit on the executable hides the file when using BWNFS.  This
prevents msdos from seeing it when using its resident commands like DIR and
COPY.   Unfortunately, if users connect to your machine on the unix end, they
can still cp the file over.

Scott Orr
scott@cnc.iupui.edu
From: martinher@urvax.urich.edu
Newsgroups: comp.protocols.nfs
Subject: Re: B&W TCP/NFS performance query
Date: 9 Nov 92 01:55:01 GMT
Reply-To: martinher@urvax.urich.edu
Organization: University of Richmond

>Given a choice of ethernet boards drivers (e.g. B&W's native driver, packet
>drivers - PD or Crynwyr, NDIS drivers, or ODI drivers) and the fact that
>B&W TCP/NFS is the only thing we run (so we don't have to worry about
>interoperability), which should I choose from a purely performance point of
>view?
>

Beame (I can't remember his first name) and I discussed this at Interop 
and I believe that he will gladly (and rightly) recommend the 3Com 3C509.

This is the new 3Com card they are bragging about and Beame claimed that
they were able to take full advantage of this card.

Herb Martin
Newsgroups: comp.protocols.nfs
From: mike@msc.cornell.edu (Mike Heisler)
Subject: IBM TCP/IP 1.2.1 for OS/2 problems with PCNFS
Organization: Cornell-Materials-Science-Center
Date: Mon, 9 Nov 1992 18:19:16 GMT

Geoff discusses:
> Quoth chf@cbnewsm.cb.att.com (charles.h.foster) (in <1992Nov6.140330.29707@cbnewsm.cb.att.com>):
> #
> #I am trying to access an OS/2 2.0 NFS server (IBM TCP/IP 1.2.1 for OS/2)
> #from a DOS 5.0 PC running Sun PC-NFS 4.0. I can mount drives from the
> #OS/2 server, but when I do a dir I get names that look like...
> #
> #	WINWO~7A     <DIR>     04-14-92   9:06a
> #
> #when they should look like...
> #
> #	WINWORD  DSK <DIR>     04-14-92   2:06a 
> #
> #(notice the time stamp is wrong also)
> 
....
> 
> This is because the OS/2 NFS server silently converts all incoming names
> into uppercase form.

NO.  OS/2 accepts mixed case and names the files EXACTLY as you specify
HOWEVER it will access the file case-insensitive.  I can access an os/2
server with the file NotNow on it as:
  notnow, NOTNOW, Notnow, .....

> 
> #You cannot execute .exe files but you can type autoexec.bat, for example.
> #You can copy files from DOS to NFS server, but you cannot copy from the
> #NFS server to DOS (says file not found).
> #
> #Can anyone shed some light on this problem. When I called Sun, all I got
> #was a "we didn't test with that software" answer.
> 
> We certainly didn't have that combination available when we tested
> PC-NFS 4.0. I'll check on how things are looking for the next release.
> There *IS* going to be a NET USE switch (though not a Windows option
> :-( to allow you to turn off all name mapping on a drive (the server
> had better be using uppercase 8.3 names, or all bets are off), but from
> the behaviour that you describe there may be other incompatibilities.

UPPERCASE, I certainly hope not.  PC-NFS puts files on our UNIX server
in lower case.  Turning off the mapping to funny character is a good
idea.  However forcing it to uppercase would then break all the files
we have had out on the server forever.  How about a compromise, create
files in lower case, 8.3, on UNIX side; map to uppercase and truncate to 8.3
as needed on DOS side.  You can't have Foo, foo and FOO in DOS anyway.

--

Mike Heisler		607-255-7344	    mike@msc.cornell.edu
Materials Science Ctr.	302 Thurston Hall   Cornell Univ, Ithaca, NY 14853-1503
-- 
Mike Heisler		607-255-7344	    mike@msc.cornell.edu
Materials Science Ctr.	302 Thurston Hall   Cornell Univ, Ithaca, NY 14853-1503
Newsgroups: comp.protocols.nfs
From: tito@di.unipi.it (Tito Flagella)
Subject: Re: PC-NFS and Novell 2.2
Organization: Dipartimento di Informatica, Universita' di Pisa
Date: Tue, 10 Nov 1992 16:09:50 GMT


>>>>> Ueber PC-NFS and Novell 2.2 sagte Dan Revel:
Dan> Article-I.D.: willamet.Bx43B2.CIq

Dan> Is it possible to run a PC as both a Netware and a PC-NFS client at the
Dan> same time?  How would I go about doing that?  I am familiar with PC-NFS
Dan> and TCP/IP but am unsure how to go about getting that to co-exist with
Dan> Novell.

I would like to understand what is the reason to do that. What are the problem to use only PC/NFS. Are there things that you can do with Novell you can't do
with a Unix NFS server? 
Many people say that a Novell server can handle more clients than a Unix server. I would like to get data and experiences from people who have experienced that.

Any contribution will be really appreciated.

Tito Flagella
-------------------------------------------------------------------
Tito Flagella			  Information Technology Consultant
Universita' di Pisa		  ---------------------------------
Dipartimento Informatica	  email:   tito@di.unipi.it
Corso Italia 40 		  fax  :   +39 (50) 510226
I-56125 Pisa    		  tel  :   +39 (50) 510263
-------------------------------------------------------------------

--
------------------------------------------------------------------
Tito Flagella	             email:   tito@di.unipi.it

work address:
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.protocols.nfs
Subject: Re: Help with NFS file handles
Date: 10 Nov 1992 20:41:16 GMT
Organization: Thinking Machines Corporation, Cambridge MA, USA
NNTP-Posting-Host: telecaster.think.com
Keywords: BFS, file handle

In article <1992Nov7.221718.9368@hubcap.clemson.edu> ksundar@hubcap.clemson.edu (Komal Sundaram) writes:
>I am trying to map NFS file handles to file names on the NFS server.
>A program called "showfh" exists but it needs eight parameters and 
>there is no documentation on what these parameters are?  Can any
>NFS gurus help?

A file handle is eight words long, and the eight parameters are the hex
representations of those eight words.  Normally this is used when the
kernel includes a file handle in an NFS error message; you just use the
file handle from the error message.
-- 
Barry Margolin
System Manager, Thinking Machines Corp.

barmar@think.com          {uunet,harvard}!think!barmar
From: beepy@ennoyab.Eng.Sun.COM (Brian Pawlowski)
Newsgroups: comp.protocols.nfs
Subject: Re: SPEC PRE-LADDIS benchmark wanted
Date: 5 Nov 1992 15:50:33 GMT
Organization: Sun Microsystems Inc., Mountain View, CA
NNTP-Posting-Host: ennoyab
Summary: nhfsstone pre-laddis

In article <1992Nov4.221431.11603@newshost.lanl.gov>, jxc@lanl.gov (Jeff Chow) writes:
> We would like to try this benchmark for our NFS studies.  
> Unfortunately, the beta test period has ended and we cannot 
> get it from spec-preladdis-beta-test@riscee.pko.dec.com.
> Can someone help?

Though I'm not the SPEC PRE-LADDIS police, perhaps I should point
out that anyone who has the PRE-LADDIS benchmark received it
either under a SPEC member agreement or a SPEC beta test
evaluation agreement, both of which I believe prevent transmission
of said benchmark to a third party. If someone has a version of
the PRE-LADDIS benchmark not obtained through one of these two avenues:
shame, shame, shame. And don't confess to me--I don't want to be
put in a moral dilemna.

I have three suggestions:

1. Voice your concern over availability/unavailability of
   benchmark to the above address and the beta test period,
   etc.

   We live in a democracy and free speech prevails.

2. The alternative nhfsstone benchmark from Legato, upon which
   PRE-LADDIS was based (a long time ago), is available I believe
   from a mail archive server at Legato. See instructions below.

3. A more interesting alternative is to join SPEC. I've heard
   tell that you can join at some low level of membership and
   have access to the benchmarks (including post-beta versions
   of PRE-LADDIS). I may be wrong (it may only be for educational
   or non-profit institutions?). As far as I can tell, the e-mail
   address and other stuff for information is: 

	Systems Performance Evaluation Corporation [SPEC]
	c/o NCGA
	Suite 200
	Fairfax, VA, 22031

	Ph:  703-698-9600 x318
	FAX: 703-560-2752
	spec-ncga@cup.portal.com

   In addition to access to SPEC benchmarks (including PRE-LADDIS)
   you get added to nifty discussion aliases? If I'm wrong in
   some details, forgive me.

Brian Pawlowski
LADDIS member-at-large

===============================================================
Getting nhfsstone:

You can get it from our mail request server by sending mail to:
        request@legato.com
with the subject line:
        send unsupported nhfsstone
From: grover@ccai.clv.oh.us (grover davidson)
Newsgroups: comp.protocols.nfs
Subject: Re: AIX-PCNFSLPD
Date: 5 Nov 92 11:12:22 GMT
Distribution: comp
Organization: CCAI
NNTP-Posting-Host: skybridge.scl.cwru.edu
X-Post-Machine: ccai.clv.oh.us.scl.cwru.edu

In article <WFORD.92Nov4155207@arrirs04.uta.edu> wford@arrirs04.uta.edu (William A. Ford) writes:
>Hello All:
>
>Hardware:
>AIX 3.2.0  with IBM APAR  for PCNFSD ver 2
>PC-AT  running Sun PC-NFS 4.0a  printlpd  " In Server Mode "
>
>The system sends me mail notes:
>Message from queuing system:
>0781-088 Device ps3rd:pc_3rd died running request nfsxxxxx which is still queued
>
>Next message:
>Message from queueing system:
>rembak: (FATAL ERROR): 0781-288 Could not send datafile /var/spool/pcnfs/xxxx/xxxx.spl
>rembak: errno = 9:  A file descriptor does not refer to an open file.
>
>This just started.
>

We have had the same problem. I have looked a the message log and found
that pcnfslpd is having trouble binding to a socket! Look at your 
machine when this happens. Do you have ALOT of defunct processes 
that belong to pcnfsd on the RS/6000? That seems to be the most common
situation here. My solution have been to monitor the spool q and restart
pcnfsd on the rs/6000 when needed. I have been tryin to get the source 
for pcnfsd on the rs/6000 so that I could try and explore/fix the problem
but no luck yet.

If you find out anything else, let me know.

grover

-- 
Grover Davidson II               | The opinions expressed here are solely mine
Conley, Canitano, & Assoc., Inc. | and in no way reflect any opinions or 
voice: 216-831-6240              | policies of my employer, even if they may
internet: grover@ccai.clv.oh.us  | agree with them, and especially if they
Newsgroups: comp.protocols.nfs
From: rich@progress.COM (Rich Lenihan)
Subject: SysV printing under PC-NFS
Keywords: printing lp lpr
Organization: Progress Software Corp.
Date: Mon, 9 Nov 1992 23:20:05 GMT

I've been given the task of changing a print server's OS from
BSD-ish to SysV-ish.  Do I have to do anything special on the
PC-NFS clients to get them to use the new "lp" print service,
rather than the old "lpr" print service?

Thanks...

-Rich

--
Rich Lenihan                 UUCP: mit-eddie!progress!rich
Progress Software Corp.      Internet: rich@progress.com
From: matt@centerline.com (Matt Landau)
Newsgroups: comp.protocols.nfs
Subject: Re: SUMMARY - eNFS/Cache
Date: 10 Nov 92 17:18:58 GMT
Organization: CenterLine Software, Inc.
NNTP-Posting-Host: 140.239.1.32

Well, we also used eNFS/cache (1.0.1, as well as a more recent patch that
Interstream gave us to test) on a number of machines for a while.  It 
showed real promise for reducing the network load, if used on all of our
machines (but then, our network is seriously overloaded, as are many of
the servers), but we had to give up on it because of recurring corrupted
data problems.  

Our clients would see old versions of files that had been replaced on the 
server hours beforehand, and would sometimes see what looked like badly 
corrupted directory contents.  This introduced enough instability into 
the development environment that we eventually decided to back out the 
eNFS/cache software and wait for a more robust release.

The Interstream folks themselves were great -- willing to be very helpful
in solving problems, providing patch releases, etc. -- but the software
just didn't quite seem "there" yet.  I expect that when it gets "there",
it will be a real win.

Standard Disclaimer:  These are my own remarks, not intended to reflect
		      the views of CenterLine Software Inc. or any of 
		      its other employees.
--
 Matt Landau			Waiting for a flash of enlightenment
 matt@centerline.com			  in all this blood and thunder
Newsgroups: comp.protocols.nfs
From: sys0002@dircon.co.uk (Julian Hayward)
Subject: PC NFS 4.0 and Windows for Workgroups
Date: Wed, 11 Nov 1992 22:14:02 GMT


I run Windows 3.1 with PC NFS to a Unix server. I am about to 
upgrade to Windows for Workgroups. Will I be able to run both
'networks' concurrently? I run PCNFS through a packet driver 
to a Western Digital ethernet card.
 
BTW: Does anyone else find the enormous RTM overlay thingy a 
right pain to load before Windows. Due to its size I can't spare 
the space to load it high. It is'nt critical to Windows it just 
seems to allow network configuration from within Windows.
 
Julian
-- 
-----------------------------------------------------------------
()_()   JULES                          |  sys0002@dircon.co.uk
 (_)    a.k.a. Julian Hayward          |  
-----------------------------------------------------------------
Xref: sparky comp.protocols.nfs:2727 comp.sys.sun.admin:8099
From: cullhane@itc.gu.edu.au (cullhane)
Subject: Packet driver for 3c509 (3com) ethernet card
Organization: Griffith University
Date: Thu, 5 Nov 92 07:29:14 GMT

Greetings,

	I'm looking for a packet driver for the above card for use with
pktd.sys with PCNFS - does anyone know where I can find one. I've downloaded
some stuff from sun.soe.clarkson.edu but can't find one for 3c509 - are
3c507 drivers compatible with 3c509 perhaps?

		Thanx in advance

				Cully
From: jbvb@vax.ftp.com (James B. VanBokkelen)
Newsgroups: comp.protocols.nfs
Subject: Re: Caching NFS client -- a quest
Date: 10 Nov 92 18:13:24 GMT
Reply-To: jbvb@ftp.com
Organization: FTP Software, Inc., Wakefield, MA
Nntp-Software: PC/TCP NNTP

In article <jpe.720458520@ee.egr.duke.edu> jpe@ee.egr.duke.edu (John P. Eisenmenger) writes:

    I know I've heard of caching NFS client software being produced by
    some company.  Unfortunately I do not remember what company it was...

Interstream, 1301 Reedsdale St, Pittsburgh, PA  15233-2329 (412-323-8000)
has an NFS caching product for Solaris 1.0 called eNFS/Cache.

James B. VanBokkelen		2 High St., North Andover, MA  01845
FTP Software Inc.		voice: (508) 685-4000  fax: (508) 794-4488
Xref: sparky comp.protocols.nfs:2747 comp.protocols.tcp-ip.ibmpc:6218