From owner-svn-doc-all@FreeBSD.ORG Wed Aug 8 03:50:07 2012 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6FC811065670; Wed, 8 Aug 2012 03:50:07 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 3255E8FC0C; Wed, 8 Aug 2012 03:50:07 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:1205:2:2:0:44]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 131A123F665; Tue, 7 Aug 2012 23:50:04 -0400 (EDT) Date: Tue, 7 Aug 2012 23:50:00 -0400 From: Glen Barber To: Jason Helfman Message-ID: <20120808035000.GB1368@glenbarber.us> References: <201207222219.q6MMJeAL032049@svn.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: svn-doc-head@freebsd.org, Robert Watson , svn-doc-all@freebsd.org, doc-committers@freebsd.org Subject: Re: svn commit: r39249 - head/en_US.ISO8859-1/books/faq X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Aug 2012 03:50:07 -0000 On Tue, Aug 07, 2012 at 08:41:52PM -0700, Jason Helfman wrote: > On Sun, Aug 5, 2012 at 12:52 PM, Eitan Adler wrote: > > > On 28 July 2012 03:07, Robert Watson wrote: > > > On Sun, 22 Jul 2012, Eitan Adler wrote: > > > A further consideration in the source code-related sections is that > > building > > > your own {world, kernel} will bump you off the support path for binary > > > updates and upgrades with freebsd-update. This is increasingly a > > > consideration for our default kernel configuration: kernel options that > > > require recompilation force users not to use the most user-friendly > > upgrade > > > path we have. > > > > I've committed some text to this effect. > > > > And the other side of this, is if you decided to run your own custom > kernel, you can run your own update server, and follow the patches from > upstream security. Here is an article I wrote to this affect. > > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/freebsd-update-server/ > Just a random thought as I am sitting here trying to reproduce some release build issues on -CURRENT: Does this article require any significant change to keep in sync with the changed 'make release' process starting with 9.0-RELEASE? Glen