From owner-freebsd-stable Sat Jun 23 17: 1: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 14B5537B401 for ; Sat, 23 Jun 2001 17:01:06 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15DxKo-0003Oe-00; Sun, 24 Jun 2001 12:01:02 +1200 From: "Juha Saarinen" To: "'Joe Kelsey'" , "'Stable'" Subject: RE: Staying *really stable* in FreeBSD Date: Sun, 24 Jun 2001 12:00:59 +1200 Message-ID: <00cf01c0fc40$c0348db0$0a01a8c0@den2> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <15157.11221.593513.478892@zircon.zircon.seattle.wa.us> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :: 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