Date: Mon, 13 Aug 2012 17:52:29 -0700 From: Michael Sierchio <kudzu@tenebras.com> To: questions@freebsd.org Subject: Re: How to keep freebsd-update from trashing custom kernel? Message-ID: <CAHu1Y71gifZOvxc2CEHN4bk9eAJpbDf9y3Zxjt8bOC1tLGS8=A@mail.gmail.com> In-Reply-To: <201208132007.OAA18078@lariat.net> References: <201208130250.UAA08187@lariat.net> <20120813132405.8f912cab.freebsd@edvax.de> <201208131635.KAA15079@lariat.net> <CAHu1Y71Mku5KXjavpEy5n_TebNA_ZYv-Sm_EtQR_Q8iUT=iRbg@mail.gmail.com> <201208132007.OAA18078@lariat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 13, 2012 at 1:07 PM, Brett Glass <brett@lariat.net> wrote: > 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. I am skeptical, since this is counter to design and experience. I'm not saying it isn't possible, but so far it's not reproducible. When you say you updated a FreeBSD 9.0 machine, was it... 9.0-RELEASE? 9.0-RELEASE-pX ? i386? amd64? - M
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHu1Y71gifZOvxc2CEHN4bk9eAJpbDf9y3Zxjt8bOC1tLGS8=A>