From owner-freebsd-current  Wed Jan 28 00:55:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA21041
          for current-outgoing; Wed, 28 Jan 1998 00:55:51 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21035;
          Wed, 28 Jan 1998 00:55:47 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA29752;
	Wed, 28 Jan 1998 19:52:21 +1100
Date: Wed, 28 Jan 1998 19:52:21 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199801280852.TAA29752@godzilla.zeta.org.au>
To: dyson@FreeBSD.ORG, ken@plutotech.com
Subject: Re: Another observation on -current and NFS
Cc: current@FreeBSD.ORG, grog@lemis.com, wpaul@skynet.ctr.columbia.edu
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk

>	Well, FWIW, I'll share my experiences with -current's NFS today.  I
>have noticed the 'strip' problem happening as well for the past couple of
>months at least.  In my experience, the client machine (i.e. the one doing
>the strip) wouldn't hang, but the kernel it generated wouldn't boot.

Strip on the client often gave different file contents than strip on the
server.

>	There is one interesting NFS problem I can report, though.
>Apparantly there is a problem with access(2) and files on NFS mounted
>filesystems.  (one of my co-workers discovered it)

This look like the nfsv3 bug fixed (?) in PR5148.  nfsv2 doesn't have it.

Bruce