From owner-freebsd-hackers  Sun Aug 20 12:48:57 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id MAA14415
          for hackers-outgoing; Sun, 20 Aug 1995 12:48:57 -0700
Received: from cs.weber.edu (cs.weber.edu [137.190.16.16])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id MAA14409
          for <hackers@freefall.freebsd.org>; Sun, 20 Aug 1995 12:48:55 -0700
Received: by cs.weber.edu (4.1/SMI-4.1.1)
	id AA23079; Sun, 20 Aug 95 13:50:25 MDT
From: terry@cs.weber.edu (Terry Lambert)
Message-Id: <9508201950.AA23079@cs.weber.edu>
Subject: Re: Making a FreeBSD NFS server
To: dima@bog.msu.su (Dmitry Khrustalev)
Date: Sun, 20 Aug 95 13:50:24 MDT
Cc: davidg@Root.COM, hackers@freefall.freebsd.org
In-Reply-To: <Pine.SOL.3.91.950820111605.552D-100000@sunny.bog.msu.su> from "Dmitry Khrustalev" at Aug 20, 95 11:22:59 am
X-Mailer: ELM [version 2.4dev PL52]
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

> >    If there is interest, I'll implement an NFS_ASYNC kernel option for both
> > FreeBSD 2.1 and 2.2.

I'm interested.  8-).

> Kernel option or per filesystem option? Switching it on for all 
> filesystems at once is evil. And if nfs3 data corruption problems are 
> resolved, this option will not have any real value.

Per FS switch.

And what about a non-homogenous environment (ie: NFSv2 servers you can't
upgrade to v3)?

I think it'll stay useful for a long time.


					Terry Lambert
					terry@cs.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.