From owner-freebsd-questions@FreeBSD.ORG Tue Jan 15 06:03:09 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B256B16A41A for ; Tue, 15 Jan 2008 06:03:09 +0000 (UTC) (envelope-from zbigniew@szalbot.homedns.org) Received: from lists.lc-words.com (lists.lc-words.com [83.19.156.210]) by mx1.freebsd.org (Postfix) with ESMTP id 7754B13C442 for ; Tue, 15 Jan 2008 06:03:09 +0000 (UTC) (envelope-from zbigniew@szalbot.homedns.org) Received: from localhost (localhost.szalbot.homedns.org [127.0.0.1]) by lists.lc-words.com (Postfix) with ESMTP id 27E013F442 for ; Tue, 15 Jan 2008 07:03:07 +0100 (CET) Received: from lists.lc-words.com ([127.0.0.1]) by localhost (szalbot.homedns.org [127.0.0.1]) (amavisd-maia, port 10026) with ESMTP id 01004-01 for ; Tue, 15 Jan 2008 07:03:06 +0100 (CET) Received: from [192.168.11.4] (unknown [192.168.11.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.lc-words.com (Postfix) with ESMTP id E30233F405 for ; Tue, 15 Jan 2008 07:03:05 +0100 (CET) Message-ID: <478C4C94.8080504@szalbot.homedns.org> Date: Tue, 15 Jan 2008 07:03:00 +0100 From: zbigniew szalbot User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: newest security patch and 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: Tue, 15 Jan 2008 06:03:09 -0000 Hello, Using freebsd-update I applied the latest security patches which were announced yesterday. However, I then notice this message: The following files will be updated as part of updating to 6.2-RELEASE-p10: /boot/GENERIC/kernel My question is whether my update missed the point because I have a custom kernel? If so, do I need to apply it manually as described in the security advisory? If I still want to go down the binary road, how can I make sure my custom kernel gets patched, too? Thank you very much! Zbigniew Szalbot