Date: Mon, 13 Aug 2012 14:07:05 -0600 From: Brett Glass <brett@lariat.net> To: Michael Sierchio <kudzu@tenebras.com> Cc: questions@freebsd.org, Polytropon <freebsd@edvax.de> Subject: Re: How to keep freebsd-update from trashing custom kernel? Message-ID: <201208132007.OAA18078@lariat.net> In-Reply-To: <CAHu1Y71Mku5KXjavpEy5n_TebNA_ZYv-Sm_EtQR_Q8iUT=iRbg@mail.g mail.com> References: <201208130250.UAA08187@lariat.net> <20120813132405.8f912cab.freebsd@edvax.de> <201208131635.KAA15079@lariat.net> <CAHu1Y71Mku5KXjavpEy5n_TebNA_ZYv-Sm_EtQR_Q8iUT=iRbg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:33 AM 8/13/2012, Michael Sierchio wrote: >And it does, in my experience. If the hash of the kernel doesn't >match that of the distribution (or recent update), freebsd-update >leaves it alone. That is what I thought it would do, based on the docs. However, when I recently ran freebsd-update on a FreeBSD 9.0 machine with a module-less custom kernel at /boot/kernel/kernel, it fetched a GENERIC kernel and overwrote the custom kernel with it. Interestingly, it didn't bring in any modules; it just overwrote the one file. --Brett Glass
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201208132007.OAA18078>