From owner-freebsd-stable@FreeBSD.ORG Wed Oct 11 22:05:05 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 CFACD16A407 for ; Wed, 11 Oct 2006 22:05:05 +0000 (UTC) (envelope-from eol1@yahoo.com) Received: from web51906.mail.yahoo.com (web51906.mail.yahoo.com [206.190.48.69]) by mx1.FreeBSD.org (Postfix) with SMTP id D33FC43D49 for ; Wed, 11 Oct 2006 22:05:04 +0000 (GMT) (envelope-from eol1@yahoo.com) Received: (qmail 52807 invoked by uid 60001); 11 Oct 2006 22:05:03 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=wWLyiIbYGBCI1ybc8324OL34ElGcg7fH6a8YUn0ZizP4bN5QaaNlZjZlWMPanHUkuBRj7SNwITlMYyU9FKjJBEs6Sg2DeJMIKpe8k62rhyMn/CVuQz1owj4sTA6epXqxu8F0S1Qt3fA1gPJv5Qgx/G0z4Z644FrCIX7Xqy7iJc8= ; Message-ID: <20061011220502.52779.qmail@web51906.mail.yahoo.com> Received: from [65.106.146.230] by web51906.mail.yahoo.com via HTTP; Wed, 11 Oct 2006 15:05:01 PDT Date: Wed, 11 Oct 2006 15:05:01 -0700 (PDT) From: Peter Thoenen To: freebsd security In-Reply-To: <20061012052709.P897@epsplex.bde.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Wed, 11 Oct 2006 22:49:19 +0000 Cc: FreeBSD Stable 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 Reply-To: eol1@yahoo.com 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:05:05 -0000 Lots of knashing of the teeth on this one but lets face it, it had to die sometime. For all the 4.x users still out there (and plenty of them have deep pockets) no reason you can't just hire third party support (possibly even a current developer); hell get together and maybe pool your resources. Thats just how life is for legacy systems, we are all mature enough here in the tech world to know this. No reason you can't sell your CIO's on this when I am guessing they are shelling out millions on other vendors. -Peter