From owner-freebsd-hackers Thu Dec 14 16:11:21 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 16:11:19 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 46B2437B402 for ; Thu, 14 Dec 2000 16:11:19 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBF0Anw49221; Thu, 14 Dec 2000 16:10:49 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Alfred Perlstein Cc: "David E. Cross" , Axel Thimm , Carsten Urbach , freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd and true NFS locks? In-Reply-To: Message from Alfred Perlstein of "Thu, 14 Dec 2000 14:54:54 PST." <20001214145454.I4589@fw.wintelcom.net> Date: Thu, 14 Dec 2000 16:10:49 -0800 Message-ID: <49217.976839049@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [-current mailing list pruned; I think -hackers is enough] > I would like to see it in both -current and -stable. I think that would be wrong, at least given the current state of the lockd stuff. First off, as David himself points out, there are issues with this code and we'd be well off dealing with those *before* committing it to -stable. I also don't think that this would be achieved simply by having more eyes on it, as you intimate, but by actually having a coherent set of code to work on and the Right Developers(tm) hacking on it. I agree with Bill Joy's assertion that all bugs are NOT shallow through having enough eyes, as Linus likes to say, but through having one or two really bright people practically killing themselves to fix them. We've also had working NFS lockd code in the BSD/OS tree on builder, along with full permission to grab it, for some time now but that hasn't made it happen because the right developers have yet to take that active an interest. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message