From owner-freebsd-current@FreeBSD.ORG Thu Dec 22 21:14:34 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED38416A420; Thu, 22 Dec 2005 21:14:34 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7588E43D5E; Thu, 22 Dec 2005 21:14:34 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jBMLERQV081351; Thu, 22 Dec 2005 13:14:30 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jBMLE3UW046805; Thu, 22 Dec 2005 13:14:03 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jBMLE2hP046803; Thu, 22 Dec 2005 13:14:02 -0800 (PST) (envelope-from jrhett) Date: Thu, 22 Dec 2005 13:14:02 -0800 From: Jo Rhett To: K?vesd?n G?bor Message-ID: <20051222211402.GJ39174@svcolo.com> References: <43A266E5.3080103@samsco.org> <20051217215434.GB92180@svcolo.com> <20051217220807.GA28741@freebie.xs4all.nl> <43A492B6.6050305@t-hosting.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43A492B6.6050305@t-hosting.hu> Organization: svcolo.com User-Agent: Mutt/1.5.9i X-Mailman-Approved-At: Thu, 22 Dec 2005 21:15:32 +0000 Cc: Wilko Bulte , stable@freebsd.org, current Subject: Re: HEADS UP: Release schedule for 2006 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2005 21:14:35 -0000 On Sat, Dec 17, 2005 at 11:35:34PM +0100, K?vesd?n G?bor wrote: > I agree. And after all, tracking a security branch isn't too difficult, > but the most people think that they have to do a complete "make > buildworld" after a security advisory, but this isn't true. For example > there was that cvsbug issue in September: .. > # make obj && make depend && make && make install > > Is that difficult? I don't think so. No reboot required and it doesn't > take more than 5 minutes even on a slower machine. This comment demonstrates that you are again talking about home computers, while all of my comments indicated that I was talking about production systems. Ones that may not have sufficient memory to compile code, or local disks, or... In any case, you are right. This kind of patch is easy to apply. You can build it on a central server and synchronize it outwards to the others. The existing binary update mechanisms can handle this situation fairly well. But more "core OS" upgrades means less of these patches and more requirement for a full binary upgrade. Which is NOT easy like this. -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation