Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 24 Jun 2001 12:00:59 +1200
From:      "Juha Saarinen" <juha@saarinen.org>
To:        "'Joe Kelsey'" <joe@zircon.seattle.wa.us>, "'Stable'" <stable@FreeBSD.ORG>
Subject:   RE: Staying *really stable* in FreeBSD
Message-ID:  <00cf01c0fc40$c0348db0$0a01a8c0@den2>
In-Reply-To: <15157.11221.593513.478892@zircon.zircon.seattle.wa.us>

next in thread | previous in thread | raw e-mail | index | archive | help
:: The tracking of stable is not for everyone.  Noone *needs* to track
:: stable.  

Well, that isn't what the Handbook says:

"19.2.2.2. Who needs FreeBSD-STABLE?
If you are a commercial user or someone who puts maximum stability of
their FreeBSD system before all other concerns, you should consider
tracking FreeBSD-STABLE. This is especially true if you have installed
the most recent release (4.3-RELEASE at the time of this writing) since
the FreeBSD-STABLE branch is effectively a bug-fix stream relative to
the previous release."

Reading that para (plus the ones before that), effectively tells you
that -STABLE is what you should use for err.... maximum stability. You
get the bugfixes and security fixes that aren't in -RELEASE.


:: current with stable.  You will miss the security upgrades 
:: unless there
:: is a relatively easy way to incorporate those without 
:: recompiling from
:: source.

So... you need to track -STABLE, right?

:: the peculiar make used by FreeBSD.  What we need is an apt-get-like
:: upgrade path for security fixes that solves the problem of people
:: tracking one version of stable or another.  Remove the necessity of
:: recompiling from source and we remove almost all reasons for 
:: people to
:: complain about the stableness of stable just because they ran into a
:: minor problem of timing WRT cvsup and updates to the source tree.

Now this is I agree with. Binary patches, please.


-- Juha


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00cf01c0fc40$c0348db0$0a01a8c0>