Date: Mon, 20 Aug 2012 16:41:56 +0400 From: Denis <piloyder@gmail.com> To: Polytropon <freebsd@edvax.de> Cc: questions@freebsd.org Subject: Re: freebsd-update fetch trying to update custom kernel Message-ID: <CAJKy0h7S=8nA4DNT8xucGD-UyOWiF4K-4TLK2oGCoEt9ix9Dqg@mail.gmail.com> In-Reply-To: <20120820142755.573029da.freebsd@edvax.de> References: <CAJKy0h52hQV61cVk%2B1WwxCZDzMWKPf36r043dKQLP9m4RBij5Q@mail.gmail.com> <CA%2B8gk9_k%2BY2Khha80h96jCP1T3Ymhgz78MQ4manYd5FD8avfNA@mail.gmail.com> <CAJKy0h5iQtfU4t0nmm9mPTdVN60Ea62XVMa9Q11_tWzP2C_fBA@mail.gmail.com> <20120820142755.573029da.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> Then why not follow my suggestion of _letting_ freebsd-update > update the kernel, but _use_ a different one instead which it > won't touch? In /boot/loader.conf: > > kernel="mykernel" > bootfile="/boot/mykernel/kernel" > > Now freebsd-update can happily alter the default kernel without > affecting yours. Note that this implies that _you_ have to take > care of kernel changes and recompiling if needed. > > I know, it's just a workaround and doesn't address the problem > directly, but it should get you away from any related trouble. Yes, I saw your advice, and will follow it. The main idea - may be I missed something and there will be an easy fix to my problem. I want to make sure that the problem exists, and I'm not the only person faced with this error. And also I have a small hope that problem will be fixed by freebsd team :-). Best regards, Denis
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJKy0h7S=8nA4DNT8xucGD-UyOWiF4K-4TLK2oGCoEt9ix9Dqg>