From owner-freebsd-current Fri Jul 14 13:44:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA26042 for current-outgoing; Fri, 14 Jul 1995 13:44:15 -0700 Received: from mpp.minn.net (mpp.Minn.Net [204.157.201.242]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA26035 for ; Fri, 14 Jul 1995 13:44:06 -0700 Received: (from mpp@localhost) by mpp.minn.net (8.6.11/8.6.9) id PAA19465; Fri, 14 Jul 1995 15:40:04 -0500 From: Mike Pritchard Message-Id: <199507142040.PAA19465@mpp.minn.net> Subject: Re: i can help To: imp@village.org (Warner Losh) Date: Fri, 14 Jul 1995 15:40:03 -0500 (CDT) Cc: mbailey@gnu.ai.mit.edu, current@FreeBSD.ORG In-Reply-To: <199507142002.OAA10445@rover.village.org> from "Warner Losh" at Jul 14, 95 02:02:03 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1385 Sender: current-owner@FreeBSD.ORG Precedence: bulk Warner Losh wrote: > > : Well a rpc.lockd and rpc.statd would be helpful.... :) > > No current RFCs exist on these protocols, to the best of my knowledge. > They are a Sun value added feature on top of NFS. Neither one of them > is described in detail in either of the Stevens books. However, he > does provide a pointer to Chapters 9, 10, 11 of [X/Open 1991] that > supposedly provide details of the lock manager. > >... > > However, I know from contacts that I have that used to maintain > Solbourne's OS/MP that the lock protocol has changed several times, > even in "mere" patches, and I've had these conversations since 1991, > so I'm not sure how helpful this document will be in defining the > current state of the art. Has anyone considered the idea of simply sitting down an implementing a FreeBSD specific NFS locking protocol? That would at least help out those people who are only running FreeBSD machines. Probably even better would be to work with the NetBSD, BSDI, and Linux (although I would rather not see the whole thing GPLed) groups and implement something acceptable to all parties. It would be better than having nothing at all. Properly implemented, it would simply appear to a Sun lockd/statd machine that there was no file locking available. -- Mike Pritchard mpp@legarto.minn.net "Go that way. Really fast. If something gets in your way, turn"