From owner-freebsd-security@FreeBSD.ORG  Wed May  1 03:03:23 2013
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 64FD92F3
 for <freebsd-security@FreeBSD.org>; Wed,  1 May 2013 03:03:23 +0000 (UTC)
 (envelope-from bakul@bitblocks.com)
Received: from mail.bitblocks.com (ns1.bitblocks.com [173.228.5.8])
 by mx1.freebsd.org (Postfix) with ESMTP id 4C13714D9
 for <freebsd-security@FreeBSD.org>; Wed,  1 May 2013 03:03:22 +0000 (UTC)
Received: from bitblocks.com (localhost [127.0.0.1])
 by mail.bitblocks.com (Postfix) with ESMTP id 3C68AB82A;
 Tue, 30 Apr 2013 19:55:32 -0700 (PDT)
To: Brett Glass <brett@lariat.org>
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-13:05.nfsserver
In-reply-to: Your message of "Tue, 30 Apr 2013 19:48:50 MDT."
 <201305010149.TAA07809@lariat.net>
References: <201304292055.r3TKtcEs039958@freefall.freebsd.org>
 <201304292208.QAA16119@lariat.net> <20130430034603.GF1588@glenbarber.us>
 <201304300416.WAA20729@lariat.net> <20130430042415.GG1588@glenbarber.us>
 <CADLo839_J40E4O2s7Af3r1stH98B-fjKtBwmNovaPfY7peqi7Q@mail.gmail.com>
 <201304301936.NAA02519@lariat.net> <20130430211531.GA1621@glenbarber.us>
 <201304302241.QAA05359@lariat.net> <20130430224850.GA1579@glenbarber.us>
 <201305010149.TAA07809@lariat.net>
Comments: In-reply-to Brett Glass <brett@lariat.org>
 message dated "Tue, 30 Apr 2013 19:48:50 -0600."
Date: Tue, 30 Apr 2013 19:55:32 -0700
From: Bakul Shah <bakul@bitblocks.com>
Message-Id: <20130501025532.3C68AB82A@mail.bitblocks.com>
Cc: freebsd-security@FreeBSD.org
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 03:03:23 -0000

On Tue, 30 Apr 2013 19:48:50 MDT Brett Glass <brett@lariat.org> wrote:
> 
> I will do that. BTW, I do not use freebsd-update(8) to update the kernel. But
> I do need it to update the kernel sources (so I can rebuild the kernel myself)

If you are tracking just the kernel sources, you can use svn
to track the releng/9.1 branch. If for some reason you really
really want to use freebsd-update, I'd suggest setting up a
virtual machine that exactly tracks a release.

> and the userland sources and binaries. After all, I can't rebuild the world
> on every production server each time there's a security fix to apply.

You can use a `staging' server where you can update, build and
check things out before a wider deployment. There are tools
that allow you to push your changes to the deployed machines.