From owner-freebsd-questions@FreeBSD.ORG Wed Apr 17 20:37:10 2013 Return-Path: Delivered-To: freebsd-questions@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 75E9CD46 for ; Wed, 17 Apr 2013 20:37:10 +0000 (UTC) (envelope-from ascherrer@gmail.com) Received: from mail-ea0-x232.google.com (mail-ea0-x232.google.com [IPv6:2a00:1450:4013:c01::232]) by mx1.freebsd.org (Postfix) with ESMTP id 142AF607 for ; Wed, 17 Apr 2013 20:37:09 +0000 (UTC) Received: by mail-ea0-f178.google.com with SMTP id o10so963697eaj.9 for ; Wed, 17 Apr 2013 13:37:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=rx+iBI9jnE3ZsCrTQjd2MKzaAomhwWRh3b7FtmtyoiM=; b=haEQlueftgSYrG2dp2UqjEBowO3wcQZP5syWsfOHjyACiqqCbsrnm3jkbcZpJ3Y1JQ XA9PvKfqLmpc2/cIoDzmORMVIBsWIDnxD7rRCgfBvd+urhnL4YPHb6uIoaz5a//7k1hZ jMH6dnqZGYBnqIXnGpNW49JfBHLj4oHVw4kNXecmade+S0vM6FGg500ZkB+YZkwUBoJ2 sLJKV+SDBlQd0fsDyiKf/C8FULNSu11grSX4XGePlon4qaERK8L8pSgziKfdit4ZvPZm QU3WpEfBJeEJvLsV5ZPKuWksKMAbdBKlEFyc/4Bgm52wl8PEvCbZ6BycmcReaRGho5X3 f/hw== X-Received: by 10.15.43.73 with SMTP id w49mr22214304eev.12.1366231029135; Wed, 17 Apr 2013 13:37:09 -0700 (PDT) Received: from manzana.hws.homeip.net ([2001:470:b71d:1:225:ff:fef2:447f]) by mx.google.com with ESMTPS id a2sm11311636eem.11.2013.04.17.13.37.07 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 17 Apr 2013 13:37:08 -0700 (PDT) Message-ID: <516F07F2.7020201@gmail.com> Date: Wed, 17 Apr 2013 22:37:06 +0200 From: andreas scherrer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: Polytropon Subject: Re: Keeping FreeBSD with custom kernel up to date: freebsd-update no option? References: <516DA8A8.5040305@gmail.com> <20130416221851.5d898701.freebsd@edvax.de> In-Reply-To: <20130416221851.5d898701.freebsd@edvax.de> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Apr 2013 20:37:10 -0000 Thank you very much for your detailed answer! on 16.4.13 22:18 Polytropon said the following: > On Tue, 16 Apr 2013 21:38:16 +0200, andreas scherrer wrote: >> I am (still) struggling to understand how to keep my FreeBSD system up >> to date ("world"/system, not ports). I want to "track" RELEASE (not a >> development branch) and I want to receive security related updates. And >> I want to run a custom kernel. > > Without actually havint tested it, it seems that if you want > to use freebsd-update (binary updating), you should note this: > > In /etc/freebsd-update.conf, you should have the line for what > to update as "Components src world". That's what I thought (and currently have). > This should prevent overwriting of the kernel, but you need to > compile your kernel and install it. The component "src" will > make sure you have the proper kernel sources. I assume a custom > kernel configuration file in /usr/src/sys/{i386|amd64}/conf/ > is _not_ being overwritten by freebsd-update. A custom kernel configuration file is *not* overwritten by freebsd-update, I can confirm this. Of course I will have to compile and install my custom kernel manually. For some reason I was under the impression that /usr/src/sys is not being updated by freebsd-update if I remove "kernel" from the "Components" directive in freebsd-update.conf. But I might be wrong (I will check). Maybe related to this: how does freebsd-update "know" what sources/binaries to get when I don't use the "-r" switch? Does it rely on /usr/src/sys/conf/newvers.sh? Could it be that I never saw a change to my kernel sources (/usr/src/sys) because freebsd-update was tracking some static sources? [snip] >> I'm on a low powered consumer >> device and it takes considerable amount of time to build the world and >> kernel (plus I still don't feel comfortable doing such tasks remotely). > > In this case, use freebsd-update as explained at the beginning of > my message: Update components "world" and "src", leave out "kernel", > the rebuild the kernel by source and install it. Then reboot. That's what I am planning to do. Let's see. As I currently have a checkout from SVN in /urs/src I need to get rid of this. Can I just copy (read: move) back my previous /usr/src directory and continue to use freebsd-update? I think this should work, right? I am just not sure if freebsd-update still "knows" what sources/binaries to track (see my previous comment about how freebsd-update knows what source to use). Cheers andreas