From owner-freebsd-questions@FreeBSD.ORG  Wed Jan  2 18:28:33 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])
 by hub.freebsd.org (Postfix) with ESMTP id 94C43E5C
 for <freebsd-questions@freebsd.org>; Wed,  2 Jan 2013 18:28:33 +0000 (UTC)
 (envelope-from kudzu@tenebras.com)
Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com
 [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 63B0A1C30
 for <freebsd-questions@freebsd.org>; Wed,  2 Jan 2013 18:28:32 +0000 (UTC)
Received: by mail-oa0-f54.google.com with SMTP id n9so13363887oag.13
 for <freebsd-questions@freebsd.org>; Wed, 02 Jan 2013 10:28:20 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=google.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type:x-gm-message-state;
 bh=+MQeS0nB8B149B3jEjHos1ngtR6cQM5l/da8q3XalXs=;
 b=EpYnB4Ntouny0gYdbQwrMNnzcjrHPfSTr33yXthwhAgMNW2gQMhpBTojvqmkxa0rVe
 W00GK5Yzp+2DDmK8qRTC0AABPm27PTJMDRps5G0pv3IN9TfC04LNcOJLUvCl9fmojFtk
 WaxkzSDumJCEiS6Ri5On929Vr/9BiWNNI/sl1utpwI/D5qOW07jsjEG47e+TfJJXMwY0
 4hHsBB5CoSO8nv5fF2+wU6r2KOYSxQja4j96AgErlOmQ3sJqJMJrvNzsG1JvLP392TTu
 ewDvmHRVfIaB4yljZKbMBTZ96+Hv++/wRFuz+dWraJMf9DchVG53o8h45gWhrrVfDd9H
 i89w==
MIME-Version: 1.0
Received: by 10.182.157.82 with SMTP id wk18mr37314205obb.26.1357151300184;
 Wed, 02 Jan 2013 10:28:20 -0800 (PST)
Received: by 10.60.119.9 with HTTP; Wed, 2 Jan 2013 10:28:20 -0800 (PST)
In-Reply-To: <FE07BE5C4AC64D520798F214@utd71538.campus.ad.utdallas.edu>
References: <50E4724E.9050706@gmail.com>
 <FE07BE5C4AC64D520798F214@utd71538.campus.ad.utdallas.edu>
Date: Wed, 2 Jan 2013 10:28:20 -0800
Message-ID: <CAHu1Y71AbmkgKm6N8VtRFYDq7z1Gi8vVy75dRfON5CB96RqUmA@mail.gmail.com>
Subject: Re: freebsd-update patches custom /boot/kernel/kernel which it should
 not
From: Michael Sierchio <kudzu@tenebras.com>
To: Paul Schmehl <pschmehl_lists@tx.rr.com>
X-Gm-Message-State: ALoCoQlbKcN8rcTmhE7IPVNJZOokgUBajmxEGOQf/XLdMtiTvDV44QXyVbKx+pu8eJme3qVf45xj
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: freebsd-questions@freebsd.org, andreas scherrer <ascherrer@gmail.com>
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
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: Wed, 02 Jan 2013 18:28:33 -0000

The confusion comes from the fact that the original behavior of
freebsd-update was NOT to update the kernel binaries if a custom kernel was
detected.

FYI my /etc/freebsd-update.conf has

# Components of the base system which should be kept updated.
#Components src world kernel
Components src world