From owner-freebsd-questions@FreeBSD.ORG  Mon Aug 19 03:31:18 2013
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 094BD729
 for <freebsd-questions@freebsd.org>; Mon, 19 Aug 2013 03:31:18 +0000 (UTC)
 (envelope-from freebsd@edvax.de)
Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id C0C7E2E13
 for <freebsd-questions@freebsd.org>; Mon, 19 Aug 2013 03:31:14 +0000 (UTC)
Received: from r56.edvax.de (port-92-195-92-43.dynamic.qsc.de [92.195.92.43])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx01.qsc.de (Postfix) with ESMTPS id B0D9B3C7A4;
 Mon, 19 Aug 2013 05:31:12 +0200 (CEST)
Received: from r56.edvax.de (localhost [127.0.0.1])
 by r56.edvax.de (8.14.5/8.14.5) with SMTP id r7J3V7Qv005995;
 Mon, 19 Aug 2013 05:31:07 +0200 (CEST)
 (envelope-from freebsd@edvax.de)
Date: Mon, 19 Aug 2013 05:31:07 +0200
From: Polytropon <freebsd@edvax.de>
To: freebsd-lists@freebsd.org
Subject: Re: freebsd 9.2 via svn
Message-Id: <20130819053107.511189ba.freebsd@edvax.de>
In-Reply-To: <20130819032215.GA2464@potato.growveg.org>
References: <20130819012825.GA2420@potato.growveg.org>
 <20130819041702.d9f1ce38.freebsd@edvax.de>
 <20130819032215.GA2464@potato.growveg.org>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: John <freebsd-lists@potato.growveg.org>, freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: Polytropon <freebsd@edvax.de>
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 03:31:18 -0000

On Mon, 19 Aug 2013 04:22:15 +0100, John wrote:
> > If you don't use a custom kernel, why not use freebsd-update
> > and follow the 9.2-RELEASE path with the security updates?
> 
> Not sure if this is logic or "religon", but freebsd-update makes me
> nervous. I'm allergic to automatic anything unless I've written it. The only
> times I've run generic is when installing a new system, to see what I
> need and what I don't. Maybe I'm just old.

You demonstrated a valid argument for building from source.
Using freebsd-update, a binary method is used for updating
the _default_ system and the GENERIC kernel. If you have
custom settings and therefore _intend_ to build from source,
changing the version in your "svn co" command to the new
-RELEASE-pX branch (security update branch) is safe.

I've been using a similar approach with CVS to follow the
-STABLE branch with a custom kernel and custom settings for
building the system. If this makes me old, I should deserve
several birthday parties per year. ;-)



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...