Date: Sat, 8 Jun 1996 11:30:20 +0900 (JST) From: Michael Hancock <michaelh@cet.co.jp> To: Nate Williams <nate@sri.MT.net> Cc: Terry Lambert <terry@lambert.org>, hackers@FreeBSD.org, freebsd-stable@FreeBSD.org, FreeBSD-current@FreeBSD.org Subject: Re: The -stable problem: my view Message-ID: <Pine.SV4.3.93.960608112739.15024A-100000@parkplace.cet.co.jp> In-Reply-To: <199606080221.UAA02108@rocky.sri.MT.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 7 Jun 1996, Nate Williams wrote:
> >
> > Terry proposes a set of tools to help enforce the policy of always having
^^^^^^
I said help not guarantee. The tools would help resolve reads while
commits are being done. Multiple reader/single writer locks are a cheap
effective way to do this.
-mh
> > a buildable tree. Would this make the commit process too cumbersome?
>
> Because these tools are unattainable. Saying 'it would be nice if we
> could guarantee that the tree was always buildable' is like saying 'it
> would be nice if everyone liked everyone'. It's a wonderful goal, but
> it's unattainable given the current resources.
>
>
> Nate
>
--
michaelh@cet.co.jp http://www.cet.co.jp
CET Inc., Daiichi Kasuya BLDG 8F 2-5-12, Higashi Shinbashi, Minato-ku,
Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.93.960608112739.15024A-100000>