Date: Fri, 30 Sep 2011 23:32:18 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Sean <sean@gothic.net.au> Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-11:05.unix Message-ID: <4E86B3F2.9040108@FreeBSD.org> In-Reply-To: <8AC5D3E0-B0D0-412C-BCDF-D531C0116043@gothic.net.au> References: <201110010410.p914Ap3F001617@chilled.skew.org> <4E86A12E.3070600@FreeBSD.org> <8AC5D3E0-B0D0-412C-BCDF-D531C0116043@gothic.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/30/2011 23:14, Sean wrote: > > On 01/10/2011, at 3:12 PM, Doug Barton wrote: > >> On 09/30/2011 21:10, Mike Brown wrote: >>> Eitan Adler wrote: >>>>> do I reboot for this one, or not? >>>> The kernel is changed, so yes. >>> >>> Thanks. I had guessed a reboot was needed, but the advisory only mentioned a >>> reboot in the context of building the kernel from sources. Hopefully, when a >>> reboot is required, future advisories will mention it in the freebsd-update(8) >>> instructions. >> >> When would a reboot not be needed for a kernel change? >> > > When it's a kernel module either not loaded, not compiled in, or can be unloaded/reloaded? I didn't say module, I said kernel. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E86B3F2.9040108>