From owner-freebsd-questions@FreeBSD.ORG  Mon Aug 20 14:40:58 2012
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 05F89106564A
	for <freebsd-questions@freebsd.org>;
	Mon, 20 Aug 2012 14:40:58 +0000 (UTC) (envelope-from jamie@kode5.net)
Received: from kontrol.kode5.net (kontrol.kode5.net [80.229.5.32])
	by mx1.freebsd.org (Postfix) with ESMTP id 60ABA8FC1C
	for <freebsd-questions@freebsd.org>;
	Mon, 20 Aug 2012 14:40:57 +0000 (UTC)
Received: from kontrol.kode5.net (localhost [127.0.0.1])
	by kontrol.kode5.net (8.14.5/8.14.5) with ESMTP id q7KEetL4029699
	for <freebsd-questions@freebsd.org>;
	Mon, 20 Aug 2012 15:40:56 +0100 (BST) (envelope-from jamie@kode5.net)
Received: (from jamie@localhost)
	by kontrol.kode5.net (8.14.5/8.14.5/Submit) id q7KEetNU029698
	for freebsd-questions@freebsd.org; Mon, 20 Aug 2012 15:40:55 +0100 (BST)
	(envelope-from jamie@kode5.net)
X-Authentication-Warning: kontrol.kode5.net: jamie set sender to
	jamie@kode5.net using -f
Date: Mon, 20 Aug 2012 15:40:55 +0100
From: Jamie Paul Griffin <jamie@kode5.net>
To: freebsd-questions@freebsd.org
Message-ID: <20120820144055.GB29643@kontrol.kode5.net>
Mail-Followup-To: freebsd-questions@freebsd.org
References: <CAJKy0h52hQV61cVk+1WwxCZDzMWKPf36r043dKQLP9m4RBij5Q@mail.gmail.com>
	<CA+8gk9_k+Y2Khha80h96jCP1T3Ymhgz78MQ4manYd5FD8avfNA@mail.gmail.com>
	<CAJKy0h5iQtfU4t0nmm9mPTdVN60Ea62XVMa9Q11_tWzP2C_fBA@mail.gmail.com>
	<20120820142755.573029da.freebsd@edvax.de>
	<CAJKy0h7S=8nA4DNT8xucGD-UyOWiF4K-4TLK2oGCoEt9ix9Dqg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAJKy0h7S=8nA4DNT8xucGD-UyOWiF4K-4TLK2oGCoEt9ix9Dqg@mail.gmail.com>
x-operating-system: FreeBSD 9.1-PRERELEASE amd64
x-pgp-fingerprint: A4B9 E875 A18C 6E11 F46D  B788 BEE6 1251 1D31 DC38
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: freebsd-update fetch trying to update custom kernel
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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, 20 Aug 2012 14:40:58 -0000

== Denis wrote on Mon 20.Aug'12 at 16:41:56 +0400 ==

> > Then why not follow my suggestion of _letting_ freebsd-update
> > update the kernel, but _use_ a different one instead which it
> > won't touch? In /boot/loader.conf:
> >
> >         kernel="mykernel"
> >         bootfile="/boot/mykernel/kernel"
> >
> > Now freebsd-update can happily alter the default kernel without
> > affecting yours. Note that this implies that _you_ have to take
> > care of kernel changes and recompiling if needed.
> >
> > I know, it's just a workaround and doesn't address the problem
> > directly, but it should get you away from any related trouble.
> 
> Yes, I saw your advice, and will follow it.
> The main idea - may be I missed something and there will be an easy
> fix to my problem. I want to make sure that the problem exists, and
> I'm not the only person faced with this error. And also I have a small
> hope that problem will be fixed by freebsd team :-).
> 
> Best regards,
> Denis

If you're building your own customised kernel, why don't you just build the entire system from source? I've not used freebsd-update yet and probably won't. Is it just a matter of time, i.e. waiting for the compilation to finish?