From owner-freebsd-current Wed Sep 4 23:44:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA26126 for current-outgoing; Wed, 4 Sep 1996 23:44:31 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA26098 for ; Wed, 4 Sep 1996 23:44:27 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA00876; Wed, 4 Sep 1996 11:39:13 -0600 (MDT) Date: Wed, 4 Sep 1996 11:39:13 -0600 (MDT) Message-Id: <199609041739.LAA00876@rocky.mt.sri.com> From: Nate Williams To: Terry Lambert Cc: current@freebsd.org Subject: Re: Latest Current build failure In-Reply-To: <199609041634.JAA06605@phaeton.artisoft.com> References: <10860.841793798@time.cdrom.com> <199609041634.JAA06605@phaeton.artisoft.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ One more time... ] > This assumes that the writer lock is held over the build process; if it > were a nightly build run by cron on another box, then it would work as > well as the engineer's personal box. Writer lock won't solve any problems experienced in FreeBSD. It's been discussed to death. It's a solution waiting for a problem that doesn't exist. The problem doesn't exist in FreeBSD. Quit wasting everyones time and mailboxes with your solution to a non-existant problem. Nate