From owner-freebsd-hackers  Mon Mar 10 22:50:22 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA01488
          for hackers-outgoing; Mon, 10 Mar 1997 22:50:22 -0800 (PST)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA01481
          for <hackers@FreeBSD.ORG>; Mon, 10 Mar 1997 22:50:19 -0800 (PST)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA01718; Mon, 10 Mar 1997 22:50:29 -0800 (PST)
To: Jaye Mathisen <mrcpu@cdsnet.net>
cc: hackers@FreeBSD.ORG
Subject: Re: Maybe a showstopper, maybe not. 
In-reply-to: Your message of "Mon, 10 Mar 1997 21:23:14 PST."
             <Pine.NEB.3.95.970310211652.24717A-100000@mail.cdsnet.net> 
Date: Mon, 10 Mar 1997 22:50:29 -0800
Message-ID: <1713.858063029@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> If I'm the only person having problems with it, then I won't worry about
> it too much, other than to not use FreeBSD on the boxes that will be 
> accessing it.  But I was curious if anybody else was seeing problems with
> it.

I'd very much like to know if others can reproduce this - my only test
environment for NFS here involves other FreeBSD boxes, and they appear
to work just fine with NFS.  If we've broken interoperability with
everything else, however, then you're definitely right about this
being a show-stopper - I wouldn't want to roll 2.2-RELEASE with a bug
of that magnitude in NFS.

Any others?

					Jordan