From owner-freebsd-hackers  Tue Mar 11 08:04:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA14966
          for hackers-outgoing; Tue, 11 Mar 1997 08:04:07 -0800 (PST)
Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA14907
          for <hackers@freebsd.org>; Tue, 11 Mar 1997 08:04:00 -0800 (PST)
Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.5/8.8.2) with ESMTP id LAA04245; Tue, 11 Mar 1997 11:03:25 -0500 (EST)
Message-Id: <199703111603.LAA04245@bmcgover-pc.cisco.com>
To: hackers@freebsd.org, jkh@time.cdrom.com
Subject: Re: NFS problem...
Date: Tue, 11 Mar 1997 11:03:25 -0500
From: Brian McGovern <bmcgover@cisco.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I've come in a bit late to this, so please slap me if I'm wrong, and tell
me what the real problem is, but...

I've used FreeBSD 2.2-GAMMA (1st release) and 3.0-CURRENT as NFS clients
to Sun, QNX, and FreeBSD. All of them work fine. The only FreeBSD server
I'm running is to other FreeBSD machines.

If this isn't the case you're seeing the problem, let me know what the real
bug report is, and I'll be happy to take it in to the lab, and try it.
	-Brian