Date: Tue, 30 Apr 2013 17:26:25 +0100 From: Chris Rees <utisoft@gmail.com> To: Glen Barber <gjb@freebsd.org>, Colin Percival <cperciva@freebsd.org> Cc: freebsd-security@freebsd.org, Brett Glass <brett@lariat.net> Subject: Re: FreeBSD Security Advisory FreeBSD-SA-13:05.nfsserver Message-ID: <CADLo839_J40E4O2s7Af3r1stH98B-fjKtBwmNovaPfY7peqi7Q@mail.gmail.com> In-Reply-To: <20130430042415.GG1588@glenbarber.us> References: <201304292055.r3TKtcEs039958@freefall.freebsd.org> <201304292208.QAA16119@lariat.net> <20130430034603.GF1588@glenbarber.us> <201304300416.WAA20729@lariat.net> <20130430042415.GG1588@glenbarber.us>
index | next in thread | previous in thread | raw e-mail
On 30 Apr 2013 05:24, "Glen Barber" <gjb@freebsd.org> wrote: > > On Mon, Apr 29, 2013 at 10:16:43PM -0600, Brett Glass wrote: > > At 09:46 PM 4/29/2013, Glen Barber wrote: > > > > >This has _always_ been the case with freebsd-update(8). > > > > Should it be? > > Yes. freebsd-update(8) does not, and cannot, know of custom kernel > configurations. > > > It seems to me that the current behavior > > > > a) Violates POLA; and > > > > Wrong. Users that build a custom kernel are responsible for maintaining > the custom kernel for upgrades. > > > b) Puts any system with a custom kernel at serious risk if > > surgery and/or a kernel rebuild is not done prior to the > > next reboot. If there's a power failure, the system may > > well not come up. > > Wrong. Previous statement applies. 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? Chrishelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo839_J40E4O2s7Af3r1stH98B-fjKtBwmNovaPfY7peqi7Q>