From owner-freebsd-fs Tue Sep 18 0:55: 8 2001 Delivered-To: freebsd-fs@freebsd.org Received: from hagbard.io.com (hagbard.io.com [199.170.88.13]) by hub.freebsd.org (Postfix) with ESMTP id 043E637B407 for ; Tue, 18 Sep 2001 00:55:06 -0700 (PDT) Received: from localhost (andrewl@localhost) by hagbard.io.com (8.11.2/8.11.2) with ESMTP id f8I7t5l08292 for ; Tue, 18 Sep 2001 02:55:05 -0500 X-Authentication-Warning: hagbard.io.com: andrewl owned process doing -bs Date: Tue, 18 Sep 2001 02:55:05 -0500 (CDT) From: "Andrew P. Lentvorski" To: Subject: Patches for NFS lockmanager Version 4 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Folks, I have made a set of changes to the -CURRENT rpc.lockd which enables it to pass the Connectathon 2001 regression suites when being run from a Solaris client to a FreeBSD server. The patches enable proper lock testing on file byte ranges. I'd like to get someone on the main FreeBSD team to look at it and get it committed (or at least give me a reason why they rejected it) before embarking on the more significant task of enabling some of the nastier cases of file range locking and unlocking. Also, I'd love to talk to someone more in the know about implementing NFS and NFS lock manager protocols. A better set of regression tests than the Connectathon suite would also be useful if they exist. Let me know who I should talk to and what I should do. Thanks, Andy Lentvorski To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message