From owner-freebsd-questions@FreeBSD.ORG Thu Nov 3 16:42:13 2011 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 B12941065673 for ; Thu, 3 Nov 2011 16:42:13 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4DB018FC17 for ; Thu, 3 Nov 2011 16:42:12 +0000 (UTC) Received: by wyg36 with SMTP id 36so1953126wyg.13 for ; Thu, 03 Nov 2011 09:42:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.202.70 with SMTP id fd6mr12938950wbb.27.1320338532127; Thu, 03 Nov 2011 09:42:12 -0700 (PDT) Received: by 10.180.81.193 with HTTP; Thu, 3 Nov 2011 09:42:12 -0700 (PDT) In-Reply-To: <20111103162654.GD25517@eggman.experts-exchange.com> References: <1320335356.50710.YahooMailClassic@web122206.mail.ne1.yahoo.com> <20111103161340.GC25517@eggman.experts-exchange.com> <20111103162654.GD25517@eggman.experts-exchange.com> Date: Thu, 3 Nov 2011 09:42:12 -0700 Message-ID: From: Michael Sierchio To: Jason Helfman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: masayoshi , freebsd-questions@freebsd.org Subject: Re: freebsd-update (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: Thu, 03 Nov 2011 16:42:13 -0000 This is simply not the case. freebsd-update works on the basis of cryptographic hashes on the binaries. It is, after all, a binary update program. If it detects a custom kernel, it will not update the kernel, but updates userland programs. It doesn't *care* what your kernel config name is, it really doesn't matter. Kernel update becomes a manual operation, which requires fetching sources from the SECURITY branch. On Thu, Nov 3, 2011 at 9:26 AM, Jason Helfman wrote: >> > I beg to differ. If you run a kernel called CUSTOM, it won't work. And if > you run a custom kernel called GENERIC, the moment you upgrade, you custo= m > kernel is no longer custom. > > All of this aside, I would be interested in hearing how you are able to > avoid non-custom updates to your custom kernel when the kernel or os patc= hes > are distributed by the update servers. > > > -- > Jason Helfman > System Administrator > experts-exchange.com > http://www.experts-exchange.com/M_4830110.html > E4AD 7CF1 1396 27F6 79DD =A04342 5E92 AD66 8C8C FBA5 >