Date: Wed, 1 May 2013 04:47:48 +0200 (CEST) From: Melanie Schulte <m-freebsd@fuglos.org> To: freebsd-security@FreeBSD.org Cc: Glen Barber <gjb@FreeBSD.org> Subject: Re: FreeBSD Security Advisory FreeBSD-SA-13:05.nfsserver Message-ID: <alpine.BSF.2.00.1305010443140.76122@m.fuglos.org> In-Reply-To: <20130430224850.GA1579@glenbarber.us> 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> <201304301936.NAA02519@lariat.net> <20130430211531.GA1621@glenbarber.us> <201304302241.QAA05359@lariat.net> <20130430224850.GA1579@glenbarber.us>
index | next in thread | previous in thread | raw e-mail
Hi, > I disagree that there is a problem, however, since users building a > custom kernel should _not_ use freebsd-update(8) for kernel > upgrades. Could you please elaborate on that? I have also built my own kernel on my servers and I must have missed the section in the handbook saying that running a custom kernel implies that freebsd-update should not be used. Given a security problem, I don't want to spend hours recompiling my base system whereas freebsd-update fixed the problem in seconds. Thanks, melaniehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1305010443140.76122>