From owner-freebsd-stable@FreeBSD.ORG Fri May 5 18:54:30 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 089FA16A409; Fri, 5 May 2006 18:54:30 +0000 (UTC) (envelope-from jd@ugcs.caltech.edu) Received: from regurgitate.ugcs.caltech.edu (regurgitate.ugcs.caltech.edu [131.215.176.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id E700E43D49; Fri, 5 May 2006 18:54:24 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by regurgitate.ugcs.caltech.edu (Postfix, from userid 3640) id 79147E8AC; Fri, 5 May 2006 11:54:24 -0700 (PDT) Date: Fri, 5 May 2006 11:54:24 -0700 From: Paul Allen To: Mike Jakubik Message-ID: <20060505185424.GD31769@regurgitate.ugcs.caltech.edu> References: <35c231bf0605031821s582b6d03j3ee9d434a596f62a@mail.gmail.com> <20060504021908.GA714@soaustin.net> <35c231bf0605032011s65fbb1aby742438465ee98ee7@mail.gmail.com> <20060504033300.GA39935@xor.obsecurity.org> <44598615.3040400@rogers.com> <20060504044758.GA41047@xor.obsecurity.org> <44599732.1050905@rogers.com> <20060505080543.GD5466@garage.freebsd.pl> <35c231bf0605051049t2761281ar97b9634b8279b1fd@mail.gmail.com> <445B991F.3050600@rogers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <445B991F.3050600@rogers.com> Sender: jd@ugcs.caltech.edu Cc: stable@freebsd.org, Pawel Jakub Dawidek , Mark Linimon , Robert Watson , Kris Kennaway , David Kirchner Subject: Re: quota deadlock on 6.1-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 18:54:30 -0000 One detail of this has to do with version numbering. The FreeBSD version number says a lot more about the userland than it does about the kernel per se. If we were to version the kernel arch, I think it would look more like this: '94 1.1.5.1 (Last Net/2) Version 0 Nov '94 2.0.5 (First unencumbered release) Aug '96 2.1.5 Nov '96 2.2 Version 1 Oct '98 3.0 Major VM changes... Version 2 Mar '00 4.0 refinement of 3.x Jan '03 5.0 Major SMP changes Version 3 Jul '05 6.0 refinement of 5.x ??? 7.0 refinement of 5.x,6.x ??? 8.0 ??? Version 4 As you can see... major version numbers come and go, but that doesn't say very much about the kernel. Given that it took at least three years for the "Version 2" arch to mature after it was initially released, is it any surprise that now at not quite 3 years after "Version 3" was released it isn't yet mature? Esp given how radical the differences are between 2 and 3? "STABLE" is a comment mostly about API/ABI and somewhat (more as merely a matter of pride in craft) about the kernel. (The latter also shows itself in the extensive testing done outside of the treer in the usability of -CURRENT, etc) Paul * This concept of versions represents only my personal opinions.