From owner-freebsd-current Mon Mar 25 09:17:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA13208 for current-outgoing; Mon, 25 Mar 1996 09:17:24 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA13196 for ; Mon, 25 Mar 1996 09:17:19 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA12155; Mon, 25 Mar 1996 10:08:44 -0700 From: Terry Lambert Message-Id: <199603251708.KAA12155@phaeton.artisoft.com> Subject: Re: Patch to talkd To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 25 Mar 1996 10:08:44 -0700 (MST) Cc: terry@lambert.org, imp@village.org, freebsd-current@FreeBSD.ORG In-Reply-To: <24374.827716630@time.cdrom.com> from "Jordan K. Hubbard" at Mar 24, 96 05:17:10 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Guys! Guys! Is talkd really such a burning issue? Why is it that > the most trivial frazzola gets talked to death yet nobody discusses > really burning issues like our total lack of NFS file locking? :-) I submitted the kernel patches for NFS file locking once; I assume you lost them? I can do the (fairly trivial) code in the rpc.lockd that goes with those patches after I verify one or two more things with Andrew (I assume that it's Andrew's rpc.lockd that is now in the source tree? I saw it go by on a SUP a while back...). Client locking is a bigger problem. It is nearly impossible without the VOP_LOCK changes I have been consistently advocating. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.