From owner-freebsd-questions@FreeBSD.ORG Wed Jan 2 17:46:00 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3D6F12D31 for ; Wed, 2 Jan 2013 17:46:00 +0000 (UTC) (envelope-from ascherrer@gmail.com) Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by mx1.freebsd.org (Postfix) with ESMTP id C645618CC for ; Wed, 2 Jan 2013 17:45:59 +0000 (UTC) Received: by mail-ee0-f44.google.com with SMTP id b47so7253823eek.31 for ; Wed, 02 Jan 2013 09:45:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type:content-transfer-encoding; bh=cyO+YNWxWA/8o/2XdMPESsyKBlZZrqi4varA4/eoSNQ=; b=QbIAgeEZZgNjrnDM2TN8MRi94uL76COUtjfvzCN7pQYenQqBeViNC6AoiDYqAxZhlW ZcHjC8k9NWFy6nm1iYxoodboLnqqt6Jy6T19IUgVfqkMJQ20k4BFwX/pnctssUn76dRy 6eW9ORWitFKOedGv0AEyq8662BVHImWzBcshg1abjAId7CFb6nMUjjqMP/B/6LyPyINR 4fLLiYwwUZJ2dm9xoJyCRVPi5XlTu7Ydq858ty5JTSztjFbYX23BDl/+vPIG8qkc95GO PqLxPUPxrIW9bAOW/ktEainvLfF2yHW72ktdu31DU8D2S4PlTE4J8RBqy/eV7ZxaxxrQ zhRA== X-Received: by 10.14.184.134 with SMTP id s6mr126313158eem.43.1357148753027; Wed, 02 Jan 2013 09:45:53 -0800 (PST) Received: from manzana.hws.homeip.net ([2001:470:b71d:1:225:ff:fef2:447f]) by mx.google.com with ESMTPS id b2sm98818694eep.9.2013.01.02.09.45.51 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 02 Jan 2013 09:45:52 -0800 (PST) Message-ID: <50E4724E.9050706@gmail.com> Date: Wed, 02 Jan 2013 18:45:50 +0100 From: andreas scherrer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: freebsd-update patches custom /boot/kernel/kernel which it should not X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2013 17:46:00 -0000 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? By the way there is a post on superuser.com describing the same issue (see [2]). Best Regards andreas [1] http://freebsd.1045724.n5.nabble.com/How-to-keep-freebsd-update-from-trashing-custom-kernel-tt5733932.html#none [2] http://superuser.com/questions/507322/freebsd-update-patches-custom-boot-kernel-kernel-which-breaks-remote-access [3] # md5 /boot/kernel/kernel MD5 (/boot/kernel/kernel) = 5757af02283522328c3537b8550a286a # sha1 /boot/kernel/kernel SHA1 (/boot/kernel/kernel) = a513c6d0d0a71fa5d74156c000952a5211e41465 # md5 /boot/GENERIC/kernel MD5 (/boot/GENERIC/kernel) = 3795c8766abf8e16088b5f1305931483 # sha1 /boot/GENERIC/kernel SHA1 (/boot/GENERIC/kernel) = 3a32246b3ce5f13ddeef336c010adf8f354443da