From owner-freebsd-questions@FreeBSD.ORG Mon Aug 13 02:50:58 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 4955E106566B for ; Mon, 13 Aug 2012 02:50:58 +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 DED928FC08 for ; Mon, 13 Aug 2012 02:50:57 +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 UAA08187 for ; Sun, 12 Aug 2012 20:50:47 -0600 (MDT) Message-Id: <201208130250.UAA08187@lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 12 Aug 2012 20:50:43 -0600 To: questions@freebsd.org From: Brett Glass Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: 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 02:50:58 -0000 Everyone: Just ran freebsd-update (fetch, then install) on a system on which I run a customized kernel, and discovered that it has overwritten my custom kernel... even though I'd copied the original to /boot/GENERIC when I first installed the system. I was under the impression that creating /boot/GENERIC, and putting the GENERIC kernel in it, would cause freebsd-update to update that directory rather than one's custom kernel. I now must rebuild the kernel to keep the machine working. What went wrong, and how do stop it from recurring? --Brett Glass