Date: Wed, 4 Sep 1996 11:52:13 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: nate@mt.sri.com (Nate Williams) Cc: terry@lambert.org, current@freebsd.org Subject: Re: Latest Current build failure Message-ID: <199609041852.LAA07039@phaeton.artisoft.com> In-Reply-To: <199609041739.LAA00876@rocky.mt.sri.com> from "Nate Williams" at Sep 4, 96 11:39:13 am
next in thread | previous in thread | raw e-mail | index | archive | help
> [ 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. It solves a problem in the suggested replacement for the existing system. Replacing the existing system solves the problems experienced by FreeBSD. I have never claimed writer locks to be anything other than supporting infrastructure for a more general soloution to a problem that is not, in current implementation, related to lack or existance of writer locks. By examining writer locks in the context of the current framework, you are doing me an injustice. Please quit assuming context for me. When I speak of writer locks, I am not speaking in the context of the existing system (which I believe has a sufficient volume of evidence noting its flaws). Like Richard's suggested build process reorganization, I expected there to be requirements that I provide a working example of a replacement. The working example I chose included writer locks as a necessary, *not* sufficient, condition. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609041852.LAA07039>