Date: Mon, 13 Aug 2012 10:35:12 -0600 From: Brett Glass <brett@lariat.net> To: Polytropon <freebsd@edvax.de> Cc: questions@freebsd.org Subject: Re: How to keep freebsd-update from trashing custom kernel? Message-ID: <201208131635.KAA15079@lariat.net> In-Reply-To: <20120813132405.8f912cab.freebsd@edvax.de> References: <201208130250.UAA08187@lariat.net> <20120813132405.8f912cab.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
At 05:24 AM 8/13/2012, Polytropon wrote: >That seems to be the default behaviour, as freebsd-update is >not supposed to be used with a custom kernel. It works with >GENERIC kernels (because it updates them by overwriting). Actually, freebsd-update is claimed to respect custom kernels. See the FreeBSD Handbook at 25.2.2: http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html "The freebsd-update utility can automatically update the GENERIC kernel only. If a custom kernel is in use, it will have to be rebuilt and reinstalled after freebsd-update finishes installing the rest of the updates. However, freebsd-update will detect and update the GENERIC kernel in /boot/GENERIC (if it exists), even if it is not the current (running) kernel of the system." But in fact, freebsd-update did not update the kernel in /boot/GENERIC on my system. Instead, it trashed the customer kernel in /boot/kernel, and did so with no warning. If there had been a power outage or other problem before I could rebuild, the system would have been disabled. --Brett Glass
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201208131635.KAA15079>