Date: Thu, 3 Nov 2011 09:42:12 -0700 From: Michael Sierchio <kudzu@tenebras.com> To: Jason Helfman <jhelfman@e-e.com> Cc: masayoshi <rockstar01@y7mail.com>, freebsd-questions@freebsd.org Subject: Re: freebsd-update (custom kernel) Message-ID: <CAHu1Y73kgrS-C5NHbNc3P0FLU-fuADON_iMiuRNUbPxGZRF_xQ@mail.gmail.com> In-Reply-To: <20111103162654.GD25517@eggman.experts-exchange.com> References: <1320335356.50710.YahooMailClassic@web122206.mail.ne1.yahoo.com> <20111103161340.GC25517@eggman.experts-exchange.com> <CAHu1Y71q3vTy6ZHA68mc9hDbc7TqRw%2BbiB_tdwtbNTm8Vn7dxQ@mail.gmail.com> <20111103162654.GD25517@eggman.experts-exchange.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhelfman@e-e.com> 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHu1Y73kgrS-C5NHbNc3P0FLU-fuADON_iMiuRNUbPxGZRF_xQ>