From owner-freebsd-current  Tue Apr 21 23:50:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA06429
          for freebsd-current-outgoing; Tue, 21 Apr 1998 23:50:02 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06364
          for <freebsd-current@FreeBSD.ORG>; Wed, 22 Apr 1998 06:49:49 GMT
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
	by time.cdrom.com (8.8.8/8.8.8) with ESMTP id XAA29632;
	Tue, 21 Apr 1998 23:48:53 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Terry Lambert <tlambert@primenet.com>
cc: ken@plutotech.com, syssgm@dtir.qld.gov.au, freebsd-current@FreeBSD.ORG
Subject: Re: NFS corruption 
In-reply-to: Your message of "Wed, 22 Apr 1998 06:34:22 -0000."
             <199804220634.XAA01160@usr06.primenet.com> 
Date: Tue, 21 Apr 1998 23:48:52 -0700
Message-ID: <29627.893227732@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Please integrate my write lease notifications, which I did for free,
> without it being my paying job, and see if it fixes the problem.

While I appreciate the pointer, I also have to say that the chances of
this fixing _all_ the serious problems with NFS are pretty remote,
don't you agree?  The original point stands, I think.

					Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message