Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!ukc!mucs!els!dente
From: dente@els.ee.man.ac.uk (Colin Dente)
Newsgroups: comp.sys.apollo
Subject: Re: NFS 2.2 bombs
Message-ID: <2694@m1.cs.man.ac.uk>
Date: 14 Jun 91 15:02:25 GMT
References: <1991Jun11.233532.1920@chemsh.uucp> <1991Jun12.175533.2004@chemsh.uucp>
Sender: news@cs.man.ac.uk
Organization: Manchester Computer Centre, University of Manchester UK
Lines: 22

In article <1991Jun12.175533.2004@chemsh.uucp> dla@chemsh.uucp (Doug Acker) writes:
>In article <1991Jun11.233532.1920@chemsh.uucp>, dla@chemsh.uucp (Doug Acker) writes:
>|> I'm another person who found that NFS 2.2 bombs on a 425s ...
>|> Has anyone found a fix or has HP/Apollo Acknowledged the problem?
>
>Talking to Apollo, this problem is with csh ... if you run csh scripts over
>a mount point, it gets hosed and dies.  They are working on a patch.  Also
>with NFS2.3, it will support automounting ....

Does this mean that if I avoid csh scripts, then NFS2.2 should be
usable? (I don't mean good - just *usable* ;-/) - I was just getting
excited about the prospect of a usable version of NFS when all these
horror stories started appearing... might I actually dare to use
NFS2.2?

Colin

--
  Colin Dente                     | JANET: dente@uk.ac.man.ee.els
  Manchester Computing Centre     | ARPA:  dente@els.ee.man.ac.uk 
  University of Manchester, UK    | UUCP:  ...!mcsun!ukc!manchester!dente 
                 ... I am the one you warned me of ...