From owner-freebsd-current  Tue Oct 29 17:50:16 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA18858
          for current-outgoing; Tue, 29 Oct 1996 17:50:16 -0800 (PST)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA18841
          for <current@FreeBSD.org>; Tue, 29 Oct 1996 17:50:09 -0800 (PST)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.2/CET-v2.1) with SMTP id BAA09530; Wed, 30 Oct 1996 01:49:57 GMT
Date: Wed, 30 Oct 1996 10:49:57 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: Mark Crispin <MRC@CAC.Washington.EDU>
cc: current@FreeBSD.org
Subject: Re: /var/mail (was: re: Help, permission problems...)
In-Reply-To: <MailManager.846626367.13515.mrc@Tomobiki-Cho.CAC.Washington.EDU>
Message-ID: <Pine.SV4.3.93.961030104126.9177B-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 29 Oct 1996, Mark Crispin wrote:

> So, FreeBSD is going to make the same mistake with the lockd kludge that SVR4
> did?

I think we will learn from the kludge that SVR4 did.  The UoG NFS code has
some interesting experimental code that manages state using leases.  I
think we can lease locking state in the same way.

The assumptions you can make with this method greatly simplifies things
and is a cool way of adding state to systems designed to be stateless. 

Regards,


Mike Hancock