From owner-freebsd-stable@FreeBSD.ORG Wed Oct 11 22:36:11 2006 Return-Path: X-Original-To: freebsd-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 DA84516A403; Wed, 11 Oct 2006 22:36:11 +0000 (UTC) (envelope-from jd@ugcs.caltech.edu) Received: from riyal.ugcs.caltech.edu (riyal.ugcs.caltech.edu [131.215.176.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7594C43D6E; Wed, 11 Oct 2006 22:36:11 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by riyal.ugcs.caltech.edu (Postfix, from userid 3640) id 7699F45806; Wed, 11 Oct 2006 15:36:10 -0700 (PDT) Date: Wed, 11 Oct 2006 15:36:10 -0700 From: Paul Allen To: Doug Barton Message-ID: <20061011223610.GA30707@riyal.ugcs.caltech.edu> References: <451F6E8E.8020301@freebsd.org> <20061011102106.GY1594@obiwan.tataz.chchile.org> <20061011151458.L97038@atlantis.atlantis.dp.ua> <20061011083021.C2780@treehorn.dfmm.org> <452D6CFD.4040905@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <452D6CFD.4040905@FreeBSD.org> Sender: jd@ugcs.caltech.edu Cc: Jason Stone , security-officer@freebsd.org, FreeBSD Stable , re@freebsd.org, freebsd security Subject: Re: [fbsd] HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon 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: Wed, 11 Oct 2006 22:36:12 -0000 Well, I suspect that most people with the resources to do what you ask have already moved on precisely because the EoL has been published. i.e., faced with that limited commitment, we had no choice but to (grudgingly and at the last minute) move on. I think the most likely path of success is, as you say, to make the 4.x userland more like 6.x. Without some prior commitment of project resources though, this is unlikely to fly with anyone. e.g., an agreement to EoL of 5.x and do port-cluster builds of a gcc 3.x variant of the 4.x kernel series. I recall that this was done in Dragonfly for a while. Paul