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 <[email protected]> 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 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 > _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[email protected]"
