From owner-freebsd-hardware  Fri Apr 25 04:36:21 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id EAA09234
          for hardware-outgoing; Fri, 25 Apr 1997 04:36:21 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (ala-ca33-03.ix.netcom.com [199.35.209.99])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA09229
          for <hardware@FreeBSD.ORG>; Fri, 25 Apr 1997 04:36:19 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id EAA28311; Fri, 25 Apr 1997 04:36:09 -0700 (PDT)
Date: Fri, 25 Apr 1997 04:36:09 -0700 (PDT)
Message-Id: <199704251136.EAA28311@silvia.HIP.Berkeley.EDU>
To: daveho@rstcorp.com
CC: hardware@FreeBSD.ORG
In-reply-to: <Pine.SUN.3.91.970424101327.3967A-100000@hazard> (daveho@rstcorp.com)
Subject: Re: building an NFS server
From: asami@vader.cs.berkeley.edu (Satoshi Asami)
Sender: owner-hardware@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * Also: are there any NFS-related issues that we should expect by
 * using FreeBSD as the NFS server?  We have a variety of client
 * OS's, including SunOS 4.1.x, Solaris 2.x, IRIX, and HP-UX.
 * For example, does FreeBSD support NFS locking?

If you are using NFS, I recommend using an NCR-based controller.
We have had lots of problems with Adaptec recently.

Satoshi