Date: Thu, 09 Mar 2006 21:15:52 -0800 From: Chris Maness <chris@chrismaness.com> To: Derek Ragona <derek@computinginnovations.com>, freebsd-questions@freebsd.org Subject: Re: To track or not to track Message-ID: <44110B88.4050800@chrismaness.com> In-Reply-To: <6.0.0.22.2.20060308150946.027fc3e0@mail.computinginnovations.com> References: <20060308120036.5784916A423@hub.freebsd.org> <20060308100648.U67765@ns1.internetinsite.com> <6.0.0.22.2.20060308150946.027fc3e0@mail.computinginnovations.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >> I just wanted to get pros and cons for tracking the whole port tree >> on a production server. >> >> Any opinions? >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" Derek Ragona wrote: > Chris, > > I will use a CVS tag to update a release for any officially reported > security issues. You can look up the right tags here: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html > > However, with production boxes, I have either non-production boxes I > update first to test the release, or secondary production boxes I > update first. > > I only update these systems if the security issue will effect the > use. For instance, if it is an issue with ipfw, but I am not using > that on a box, I don't bother to update it. > > Hope this helps, > > -Derek Are you using these tags for the ports or the base system + userland? I love the way that I can track the security/bug fixes by tracking a branch of the code for the src directory. It would be nice if ports forked too.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44110B88.4050800>