From owner-freebsd-questions@FreeBSD.ORG Wed Jan 2 18:16:52 2013 Return-Path: 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 9ADB761D for ; Wed, 2 Jan 2013 18:16:52 +0000 (UTC) (envelope-from prvs=707b37d7b=pschmehl_lists@tx.rr.com) Received: from ip-002.utdallas.edu (ip-002.utdallas.edu [129.110.20.108]) by mx1.freebsd.org (Postfix) with ESMTP id 737881AD1 for ; Wed, 2 Jan 2013 18:16:40 +0000 (UTC) X-Group: None X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Apw2ABp45FCBbgog/2dsb2JhbABFgX+7WHOCHgEBBAE4AkQLC0YhNgYBEhuHZgMJBrBDDYhAi21qg2JhA4hii1SNDYURgxM X-IronPort-AV: E=Sophos;i="4.84,397,1355119200"; d="scan'208";a="113148609" Received: from zxtm01.utdallas.edu (HELO utd71538.utdallas.edu) ([129.110.10.32]) by ip-002.utdallas.edu with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Jan 2013 12:15:30 -0600 Date: Wed, 02 Jan 2013 12:15:27 -0600 From: Paul Schmehl To: andreas scherrer , freebsd-questions@freebsd.org Subject: Re: freebsd-update patches custom /boot/kernel/kernel which it should not Message-ID: In-Reply-To: <50E4724E.9050706@gmail.com> References: <50E4724E.9050706@gmail.com> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=1603 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Paul Schmehl List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2013 18:16:52 -0000 --On January 2, 2013 6:45:50 PM +0100 andreas scherrer wrote: > Hi > > This can be considered a follow up to the message "How to keep > freebsd-update from trashing custom kernel?" sent to this list by Brett > Glass on August 13th 2012 (see [1]). Unfortunately there is no solution > to the problem in that thread (or I cannot see it). > > I am running currently running 9.0-RELEASE-p4 and freebsd-update > recommends to update to p5. It states: > > ----- > The following files will be updated as part of updating to 9.0-RELEASE-p5: > /boot/kernel/kernel > > ----- > > And from experience this is what it will do: replace /boot/kernel/kernel > which is my custom kernel with a GENERIC kernel. > > As it seems that freebsd-update works by comparing a hash of > /boot/kernel/kernel with the GENERIC kernel's hash I checked the md5 and > sha1 hash of /boot/kernel/kernel and /boot/GENERIC/kernel. They differ > (see [3]). > > So why is freebsd-update going to overwrite my custom kernel? And how > can I prevent it from doing so? > Read man (5) freebsd-update.conf. Particularly the COMPONENTS portion that explains how to update world without changing kernel. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell