From owner-freebsd-hackers Tue Jul 9 11:18: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACBE537B400 for ; Tue, 9 Jul 2002 11:17:57 -0700 (PDT) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC5AF43E31 for ; Tue, 9 Jul 2002 11:17:56 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from go.cs.rpi.edu (go.cs.rpi.edu [128.213.12.7]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA00546 for ; Tue, 9 Jul 2002 14:17:55 -0400 (EDT) Received: from go.cs.rpi.edu (crossd@localhost) by go.cs.rpi.edu (8.11.6+Sun/8.9.3) with ESMTP id g69IHtH17743 for ; Tue, 9 Jul 2002 14:17:55 -0400 (EDT) Message-Id: <200207091817.g69IHtH17743@go.cs.rpi.edu> X-Authentication-Warning: go.cs.rpi.edu: crossd owned process doing -bs To: hackers@freebsd.org Subject: rpc.lockd Date: Tue, 09 Jul 2002 14:17:54 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Once, long ago, some people emailed me a set of issues regarding our lockd implementation. Would people be willing to re-email me those, or take a fresh look? I once again have time and people to do development on this; and it was 99% there last time; the only issues being some byte-swapping in the RPC code under 64bits... but I don't remember where. And perhaps some other minor problems that I forget. Of particular interest would be little-endian 64 to little-endian 64 testing. The code is at http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2a.tar.gz Thank you -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message