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