Hi

This can be considered a follow up to the message "How to keep
freebsd-update from trashing custom kernel?" sent to this list by Brett
Glass on August 13th 2012 (see [1]). Unfortunately there is no solution
to the problem in that thread (or I cannot see it).

I am running currently running 9.0-RELEASE-p4 and freebsd-update
recommends to update to p5. It states:

-----
The following files will be updated as part of updating to 9.0-RELEASE-p5:
/boot/kernel/kernel
<snip>
-----

And from experience this is what it will do: replace /boot/kernel/kernel
which is my custom kernel with a GENERIC kernel.

As it seems that freebsd-update works by comparing a hash of
/boot/kernel/kernel with the GENERIC kernel's hash I checked the md5 and
sha1 hash of /boot/kernel/kernel and /boot/GENERIC/kernel. They differ
(see [3]).

So why is freebsd-update going to overwrite my custom kernel? And how
can I prevent it from doing so?

By the way there is a post on superuser.com describing the same issue
(see [2]).


Best Regards
andreas


[1]
http://freebsd.1045724.n5.nabble.com/How-to-keep-freebsd-update-from-trashing-custom-kernel-tt5733932.html#none

[2]
http://superuser.com/questions/507322/freebsd-update-patches-custom-boot-kernel-kernel-which-breaks-remote-access

[3]
# md5 /boot/kernel/kernel
MD5 (/boot/kernel/kernel) = 5757af02283522328c3537b8550a286a
# sha1 /boot/kernel/kernel
SHA1 (/boot/kernel/kernel) = a513c6d0d0a71fa5d74156c000952a5211e41465

# md5 /boot/GENERIC/kernel
MD5 (/boot/GENERIC/kernel) = 3795c8766abf8e16088b5f1305931483
# sha1 /boot/GENERIC/kernel
SHA1 (/boot/GENERIC/kernel) = 3a32246b3ce5f13ddeef336c010adf8f354443da
_______________________________________________
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"

Reply via email to