Date: Tue, 30 Apr 2013 19:55:32 -0700 From: Bakul Shah <bakul@bitblocks.com> To: Brett Glass <brett@lariat.org> Cc: freebsd-security@FreeBSD.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-13:05.nfsserver Message-ID: <20130501025532.3C68AB82A@mail.bitblocks.com> In-Reply-To: Your message of "Tue, 30 Apr 2013 19:48:50 MDT." <201305010149.TAA07809@lariat.net> 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> <201305010149.TAA07809@lariat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 30 Apr 2013 19:48:50 MDT Brett Glass <brett@lariat.org> wrote: > > I will do that. BTW, I do not use freebsd-update(8) to update the kernel. But > I do need it to update the kernel sources (so I can rebuild the kernel myself) If you are tracking just the kernel sources, you can use svn to track the releng/9.1 branch. If for some reason you really really want to use freebsd-update, I'd suggest setting up a virtual machine that exactly tracks a release. > and the userland sources and binaries. After all, I can't rebuild the world > on every production server each time there's a security fix to apply. You can use a `staging' server where you can update, build and check things out before a wider deployment. There are tools that allow you to push your changes to the deployed machines.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130501025532.3C68AB82A>