From owner-freebsd-hackers Mon Aug 23 18:33:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (Postfix) with ESMTP id B225614FC3; Mon, 23 Aug 1999 18:33:22 -0700 (PDT) (envelope-from vanderh@ecf.toronto.edu) Received: from ppp18344.on.bellglobal.com (ppp6631.on.bellglobal.com [206.172.208.223]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id VAA03089; Mon, 23 Aug 1999 21:36:27 -0400 (EDT) Received: (from tim@localhost) by ppp18344.on.bellglobal.com (8.9.3/8.9.1) id VAA99468; Mon, 23 Aug 1999 21:35:13 -0400 (EDT) (envelope-from tim) Date: Mon, 23 Aug 1999 21:35:13 -0400 From: Tim Vanderhoek To: Garance A Drosihn Cc: Greg Lehey , Matthew Dillon , Poul-Henning Kamp , FreeBSD Hackers , FreeBSD Committers , Garrett Wollman Subject: Re: Mandatory locking? Message-ID: <19990823213512.A99022@ppp18344.on.bellglobal.com> References: <19990823122719.G83273@freebie.lemis.com> <7071.935386172@critter.freebsd.dk> <19990823095310.A83273@freebie.lemis.com> <199908230031.RAA00909@apollo.backplane.com> <19990823100654.B83273@freebie.lemis.com> <199908230504.WAA01860@apollo.backplane.com> <19990823152849.H83273@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Garance A Drosihn on Mon, Aug 23, 1999 at 03:28:01PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 23, 1999 at 03:28:01PM -0400, Garance A Drosihn wrote: > > Anyway, I am also puzzled as to why there would be much objection > to the option of mandatory locking. My initial systems-programming If you provide mandatory locks that can be broken, then many of the objections may disappear... Providing mandatory locks that can be broken would be rather useful, I think. Mandatory locks that cannot be broken are another matter... -- This is my .signature which gets appended to the end of my messages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message