From owner-freebsd-hackers Thu Jun 10 14:31: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mag.ucsd.edu (mag.ucsd.edu [132.239.34.96]) by hub.freebsd.org (Postfix) with ESMTP id 08CF014DE4 for ; Thu, 10 Jun 1999 14:31:04 -0700 (PDT) (envelope-from billh@mag.ucsd.edu) Received: (from billh@localhost) by mag.ucsd.edu (8.8.8/8.8.8) id OAA28416; Thu, 10 Jun 1999 14:25:49 -0700 (PDT) From: Bill Huey Message-Id: <199906102125.OAA28416@mag.ucsd.edu> Subject: Re: linux and freebsd kernels conceptually different? To: imp@harmony.village.org (Warner Losh) Date: Thu, 10 Jun 1999 14:25:49 -0700 (PDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199906102020.OAA45046@harmony.village.org> from "Warner Losh" at Jun 10, 99 02:20:12 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : This is always good, assuming that this is done properly with peer review > : and that folks listen to it. > > Linux isn't peer reviewed in the traditional sense of this meaning, so > your whole argument fails because of that. I'd agree if it was > entensively peer reviewed, it might be a good thing. It isn't. Well, first of all it wasn't a "constructed arguement" so it can't fail in the traditional sense of arguements failing. And I do qualify having open discussions with various folks "peer review" even if Linus himself has sole primary control over the source tree. This is something that I've seen done pretty cooperatively on linux-kernel. There definite technical problems with Linux, but it doesn't seem to measure up to the level of criticism that I've seen directed at it because the source tree is a consistently moving target. > Linux gets to where it is going by doing things many times quickly, > but not necessarily correctly. While there is some value in this > approach, it can be quite wasteful. I gave up maintaining my port of > Linux to my rPC44 because the internal internal interfaces kept > changing at a rate that makes the recent -current newbus integration > look and feel stable. Yeah, that's problematic and short sighted on their part. It's certainly not a question of expertise from what I've seen since there are very competent technical folks with strong acedemic CS backgrounds hanging out on the list. It seems like more of an implementation issues than and acedemic knowledge issue. I don't know what to think about this at this time, since I'm just now getting into understand the Linux source tree. > Warner bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message