From owner-freebsd-questions@FreeBSD.ORG Mon Aug 13 16:35:23 2012 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D99A3106566C for ; Mon, 13 Aug 2012 16:35:23 +0000 (UTC) (envelope-from brett@lariat.net) Received: from lariat.net (lariat.net [66.62.230.51]) by mx1.freebsd.org (Postfix) with ESMTP id 905FE8FC12 for ; Mon, 13 Aug 2012 16:35:23 +0000 (UTC) Received: from WildRover.lariat.net (IDENT:ppp1000.lariat.net@lariat.net [66.119.58.2] (may be forged)) by lariat.net (8.9.3/8.9.3) with ESMTP id KAA15079; Mon, 13 Aug 2012 10:35:15 -0600 (MDT) Message-Id: <201208131635.KAA15079@lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 13 Aug 2012 10:35:12 -0600 To: Polytropon From: Brett Glass In-Reply-To: <20120813132405.8f912cab.freebsd@edvax.de> References: <201208130250.UAA08187@lariat.net> <20120813132405.8f912cab.freebsd@edvax.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: questions@freebsd.org Subject: Re: How to keep freebsd-update from trashing custom kernel? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2012 16:35:23 -0000 At 05:24 AM 8/13/2012, Polytropon wrote: >That seems to be the default behaviour, as freebsd-update is >not supposed to be used with a custom kernel. It works with >GENERIC kernels (because it updates them by overwriting). Actually, freebsd-update is claimed to respect custom kernels. See the FreeBSD Handbook at 25.2.2: http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html "The freebsd-update utility can automatically update the GENERIC kernel only. If a custom kernel is in use, it will have to be rebuilt and reinstalled after freebsd-update finishes installing the rest of the updates. However, freebsd-update will detect and update the GENERIC kernel in /boot/GENERIC (if it exists), even if it is not the current (running) kernel of the system." But in fact, freebsd-update did not update the kernel in /boot/GENERIC on my system. Instead, it trashed the customer kernel in /boot/kernel, and did so with no warning. If there had been a power outage or other problem before I could rebuild, the system would have been disabled. --Brett Glass