Date: Tue, 30 Apr 2013 13:36:52 -0600 From: Brett Glass <brett@lariat.org> To: Chris Rees <utisoft@gmail.com>, Glen Barber <gjb@freebsd.org>, Colin Percival <cperciva@freebsd.org> Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-13:05.nfsserver Message-ID: <201304301936.NAA02519@lariat.net> In-Reply-To: <CADLo839_J40E4O2s7Af3r1stH98B-fjKtBwmNovaPfY7peqi7Q@mail.g mail.com> References: <201304292055.r3TKtcEs039958@freefall.freebsd.org> <201304292208.QAA16119@lariat.net> <20130430034603.GF1588@glenbarber.us> <201304300416.WAA20729@lariat.net> <20130430042415.GG1588@glenbarber.us> <CADLo839_J40E4O2s7Af3r1stH98B-fjKtBwmNovaPfY7peqi7Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is one of several reasons why one would expect freebsd-update(8) to be considerate of a custom kernel: it is documented as knowing about /boot/GENERIC as the place to put he GENERIC kernel if one builds a custom one. Also, I don't think that freebsd-update(8) should, in the course of a normal update, create a situation where the system is not be able to reboot. This would have been the case with the system I updated, had I not caught the problem. I daresay that a system that stops working after a routine update is a violation of POLA. ;-) In my case, the GENERIC kernel was installed in place of the custom one, without modules the system needed -- in either loadable or built-in form. It's easy to prevent this by modifying /boot/GENERIC (which freebsd-update is supposed to know about) instead of overwriting the custom kernel... and then advising the administrator that a new build might be needed. --Brett Glass At 10:26 AM 4/30/2013, Chris Rees wrote: >I agreed with Glen, but when checking the docs it turns out that they say >that freebsd-update will detect a kernel in /boot/GENERIC: > >http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html > >Are the docs wrong, or is this only in new freebsd-update? > >Chris >_______________________________________________ >freebsd-security@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-security >To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201304301936.NAA02519>