Date: Thu, 3 Nov 2011 09:26:54 -0700 From: Jason Helfman <jhelfman@e-e.com> To: Michael Sierchio <kudzu@tenebras.com> Cc: masayoshi <rockstar01@y7mail.com>, freebsd-questions@freebsd.org Subject: Re: freebsd-update (custom kernel) Message-ID: <20111103162654.GD25517@eggman.experts-exchange.com> In-Reply-To: <CAHu1Y71q3vTy6ZHA68mc9hDbc7TqRw%2BbiB_tdwtbNTm8Vn7dxQ@mail.gmail.com> References: <1320335356.50710.YahooMailClassic@web122206.mail.ne1.yahoo.com> <20111103161340.GC25517@eggman.experts-exchange.com> <CAHu1Y71q3vTy6ZHA68mc9hDbc7TqRw%2BbiB_tdwtbNTm8Vn7dxQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 03, 2011 at 09:19:29AM -0700, Michael Sierchio thus spake: >On Thu, Nov 3, 2011 at 9:13 AM, Jason Helfman <jhelfman@e-e.com> wrote: > >> I does work fine with a custom kernel, as long as you are running and >> maintaining the actual update server that distributes. > >I don't think that's relevant. It works fine with the public servers. > 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 custom 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 patches 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 4342 5E92 AD66 8C8C FBA5
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111103162654.GD25517>