Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!rpi!batcomputer!eric
From: eric@batcomputer.tn.cornell.edu (Eric Fielding)
Newsgroups: comp.sys.dec
Subject: Re: DEC TCP/IP
Message-ID: <9963@batcomputer.tn.cornell.edu>
Date: 23 Mar 90 16:35:41 GMT
Reply-To: fielding@geology.tn.cornell.edu
Distribution: na
Organization: Department of Geological Sciences, Cornell University
Lines: 27

In a recent article evans@decvax.DEC.COM wrote:
>In article <8240001@hp-lsd.COS.HP.COM>, harmon@hp-lsd.COS.HP.COM (Bruce
>Harmon) writes:
>> I may be interested in making the transition from Wollongong's
>> TCP/IP (VMS hosted) to the new DEC product.  I also need two-way
>> NFS support VMS to/from a non-DEC Unix platform.  
>> be interesting.

>NFS under VMS works reasonably. There are a few gotchas, especially if you are
>trying to use it in a mixed access (VMS/*ix) environment. In this case, file
>names and other nits need to use the most common method. 
>- Marc (An unbiased contract software hacker)

We have been using the DEC VMS/Ultrix connection to do NFS serving of disks
from our VAXcluster to a DECstation.  It works very well. Unfortunately the
present version (1.2) does *not* allow a VMS machine to be a NFS client, so
it is a one-way only system (unless Marc has a newer version that works both
ways and can't tell us because of non-disclosure agreements).  The two 
problems that we have xD encountered are that the NFS$SERVER process likes to
grab about 6000 pages of physical memory which is a lot on a server with not
too much memory, and the other is the almost infinite variety of VMS file
types that are not very readable xD under U*ix.  Usually we have to use FTP
to transfer the files to U*ix and do the file format conversion. VMS  especially
C has no problem reading the 'Stream_LF' files from the shared disks. The
VMS editors seem pretty happy too.

					++Eric FIelding