[BUGS] question on up keeping of a production server

[goku -]

interesting... so you don't recommend using the freebsd-update. so if there
is any minor or major security fixes, you would recommend just to cvsup then
do a make build world and make install world.  or would you just update the
patches one at a time.

thanks for your prompt reply.


On Wed, Jun 4, 2008 at 10:50 PM, Jerahmy Pocott <quakenet1 at optusnet.com.au>
wrote:

>
> On 05/06/2008, at 6:19 PM, goku - wrote:
>
>  Now here is my question.  I've read that a safe method of updating the
> system's binaries is using a utility called freebsd-update.  I have read
> that it does not update –STABLE .  It only tracks the release tag.  So do
> I change the RELENG_7 to RELENG_7_0_0_RELEASE ?  also when freebsd 7.1R
> becomes available and I decide not to upgrade.  Will the freebsd-update
> still update the system's binaries? Or do I have to upgrade to freebsd 7.1R
> and change the RELENG_7_0_0_RELEASE  to RELENG_7_1_0_RELEASE
>
>
> I think what you're asking is "how do I track the security branch for a
> release?
>
> The answer to that is, assuming you want 7.0 would be to track RELENG_7_0,
> this would then get anything with 7.0 in the tag (eg 7.0.1, 7.0.2, etc).
>
> Doing a binary update isn't always the best procedure, since you can't
> compile with cpu specific optimizations (mtune) or use -O2 or any other
> flags you might want to compile with or pass to make.. There isn't really
> anything dangerous about compiling your own sources..
>
> _______________________________________________
> BUGS mailing list
> BUGS at bugs.au.freebsd.org
> http://mailman.barnet.com.au/mailman/listinfo/bugs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.barnet.com.au/pipermail/bugs/attachments/20080604/12f50d15/attachment-0001.html