From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 1 10:50:25 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7AC9316A405 for ; Thu, 1 Mar 2007 10:50:25 +0000 (UTC) (envelope-from ah@crypta.net) Received: from mail.crypta.net (mail.crypta.net [83.136.131.3]) by mx1.freebsd.org (Postfix) with ESMTP id 436CD13C4AA for ; Thu, 1 Mar 2007 10:50:25 +0000 (UTC) (envelope-from ah@crypta.net) Received: by mail.crypta.net (cryptobank/eProtect-smtpd, from userid 1001) id 020EAECD477; Thu, 1 Mar 2007 11:50:24 +0100 (CET) Date: Thu, 1 Mar 2007 11:50:23 +0100 From: Andy Hilker To: freebsd-hackers@freebsd.org Message-ID: <20070301105023.GA62748@mail.crypta.net> References: <20070228221612.GA14358@mail.crypta.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070228221612.GA14358@mail.crypta.net> User-Agent: Mutt/1.4.2.2i X-PGP-Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0xEC6E1071 X-PGP-Fingerprint: 9B2E 5892 AD93 D5C5 FB8E 3912 35D6 951B EC6E 1071 Organization: cryptobank - Andy Hilker Cc: Colin Percival Subject: Re: freebsd-update ignores /boot/kernel/kernel sometimes!? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2007 10:50:25 -0000 You (Andy Hilker) wrote: > Hi, > > i have a strange thing here, maybe someone can give me a hint. > > Somehow freebsd-update find /boot/kernel/kernel on some servers and > patches it and on others not. Both kernels are installed from CD > (GENERIC). > > On those servers where it does not display /boot/kernel/kernel, > i can fix this by creating a symlink: ln -s /boot/kernel /boot/GENERIC > Then it will display and patch /boot/GENERIC/kernel. Other ways > to fix it is nextboot or kernel variable in /boot/loader.conf, but > i do not want a workaround on some servers. Any idea why this can > happen? > > Maybe it is related to the way how the "broken" kernel has been installed: > > >From RELEASE CD: > cd kernels > ./install.sh GENERIC > mv /boot/GENERIC /boot/kernel Additional info: it seems that all machines where it does not work, have an SMP-GENERIC (i386) installed. bye, Andy