From owner-freebsd-questions@FreeBSD.ORG Sun Aug 23 15:37:38 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BA8C106568C for ; Sun, 23 Aug 2009 15:37:38 +0000 (UTC) (envelope-from taosecurity@gmail.com) Received: from mail-gx0-f227.google.com (mail-gx0-f227.google.com [209.85.217.227]) by mx1.freebsd.org (Postfix) with ESMTP id 4C0478FC1E for ; Sun, 23 Aug 2009 15:37:38 +0000 (UTC) Received: by gxk27 with SMTP id 27so2136314gxk.12 for ; Sun, 23 Aug 2009 08:37:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=C41S+Dgg3jNsGmudQXTLSN07qalkzym65d0L/c4UgOA=; b=w3RKC0YfTmXEd0m8j+iWDfxoriEVN2BboW5D7V2J0vn65KyMQwCX6Uv45N2vZhX5mU 4E1HWrD6r4+txEYKnOkpRyyJ5myY9ytrxF1aIa9cXIF2SEBBQAijFFGAgDkApFEcHdve KyLXOX7gZhDqfKM4BAuoja7R6vIr9jYnoUHNU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=AQM9YcvlgFX9bB6uzKsn2y6fNRggXeYOtG7wr31pvc5MpYfMcEEEYKEC243qFqg+qt hEkSC6xiL/gglor9S12vfC7RDtkg2EBd5AP0vXUjn9y5WJ6IbUxhLVKysysmEwBg1/UN KMK8E0HGRqNj2ZJX5b/o9jq9ZjXa6AlrN7gKQ= MIME-Version: 1.0 Received: by 10.91.143.16 with SMTP id v16mr3061212agn.97.1251040177635; Sun, 23 Aug 2009 08:09:37 -0700 (PDT) Date: Sun, 23 Aug 2009 11:09:37 -0400 Message-ID: <120ef0530908230809l36f661c9ra19d44ba8a82bb33@mail.gmail.com> From: Richard Bejtlich To: freebsd-questions@freebsd.org, freebsd@edvax.de Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: cvs tag usage X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Aug 2009 15:37:38 -0000 freebsd@edvax.de wrote: > If you are interested in the "bleeding edge" of FreeBSD's development, > you follow RELENG_7. This will then deliver the -CURRENT branch to you > with all modifications. It may happen that a -CURRENT of today doesn't > compile, but tomorrow, it will do. It's considered to be the experimental > branch where changes can appear and disappear. Hello, I think you are confusing RELENG_7 with "." (as the CVS tag says) or HEAD. RELENG_7 will "deliver" 7-STABLE, not CURRENT. CURRENT is the "bleeding edge." Also: > You follow the -STABLE branch of FreeBSD 7.2 and will always get > the latest *stable* 7.2 sources, but won't reach 7.3 with this setting. That's not quite right. 7.3 is just a point along the 7-STABLE path. For example, if you tracked STABLE via RELENG_7 starting with, say, FreeBSD 7.1, your system would have run 7.2 at some point, and then beyond it. Tracking STABLE isn't like using CVSup or Csup to reach RELENG_7_2_0 or RELENG_7_2, but you eventually get the 7.2 functionality by tracking RELENG_7. For example, start with 7.1 from CD: fbsd71toS# uname -a FreeBSD fbsd71toS.taosecurity.com 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 After Csup to RELENG_7, you get fbsd71toS# uname -a FreeBSD fbsd71toS.taosecurity.com 7.2-STABLE FreeBSD 7.2-STABLE #0: Sat Aug 22 23:02:30 EDT 2009 root@fbsd71toS.taosecurity.com:/usr/obj/usr/src/sys/FREEBSD7 i386 As you can see, it's not theoretical -- I ran this test this weekend. :) Thank you, Richard