From owner-freebsd-newbies Sat Aug 10 16: 1:16 2002 Delivered-To: freebsd-newbies@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8307737B400 for ; Sat, 10 Aug 2002 16:01:13 -0700 (PDT) Received: from spork.pantherdragon.org (spork.pantherdragon.org [206.29.168.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id F369743E72 for ; Sat, 10 Aug 2002 16:01:11 -0700 (PDT) (envelope-from dmp@pantherdragon.org) Received: from sparx.pantherdragon.org (evrtwa1-ar10-4-61-252-210.evrtwa1.dsl-verizon.net [4.61.252.210]) by spork.pantherdragon.org (Postfix) with ESMTP id 5980FFF3D; Sat, 10 Aug 2002 16:00:55 -0700 (PDT) Received: from pantherdragon.org (speck.techno.pagans [172.21.42.2]) by sparx.pantherdragon.org (Postfix) with ESMTP id CE172AB04; Sat, 10 Aug 2002 16:00:53 -0700 (PDT) Message-ID: <3D559B25.B1FB333F@pantherdragon.org> Date: Sat, 10 Aug 2002 16:00:53 -0700 From: Darren Pilgrim X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jim McAtee Cc: freebsd-newbies@freebsd.org Subject: Re: Using CVSup References: <019d01c23fd7$2d44d740$272fa8ce@jim> <01c101c23fd8$78b4b5f0$272fa8ce@jim> <3D54162F.1000502@xmission.com> <3D541E31.C8A0EB52@pantherdragon.org> <023101c23fe2$22b10320$272fa8ce@jim> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-newbies@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Jim McAtee wrote: > > ----- Original Message ----- > From: "Darren Pilgrim" > To: "Jason Porter" > Cc: > Sent: Friday, August 09, 2002 1:55 PM > Subject: Re: Using CVSup > > > Jason Porter wrote: > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > Stable has more fixes in it than Release. Release means that it's > > > release quality. They can safely box it and ship it out. Stable has > > > the same base as the Release version but contains fixes and is okay to > > > use on a production server (in theory). > > > > Not true. If you read the Handbook section on -stable, it says in > > implied huge, red, flashing letters that there is absolutely no > > guarantee that stable will even compile. > > > > Yes, a lot of people use -stable on production servers. I'm one of > > them. But the tricks to do this safely, the list of gotchas, and the > > constant list monitoring needed to no screw the machine up is not > > something I would consider a habit a beginner should be getting into > > just yet. > > > > A happy medium between the RELEASE tags and -STABLE are the RELENG_4_x > > tags. It's the release (RELENG_4_6 == 4.6) source with all the > > relevant patches from the SA's applied. I would consider this a safe > > way to get your feet wet with cvsup and the make world process, as > > there's very little to trip over with the mergemaster process (perhaps > > the most dangerous part of the whole deal). > > Thanks. I think this may answer my other question regarding the difference > between the tags. So, would the tag RELENG_4_6 actually pull the source for > 4.6.1 (plus patches) if the latest RLEASE is RELENG_4_6_1_RELEASE? RELENG_4_6 would pull down the 4.6-R sources plus all the security patches that apply to it. Currently, the OS version on RELENG_4_6 is 4.6.1-RELEASE-p10. 4.6 and 4.6.1 are the same primary release of 4.6. 4.6.1 is what's called an interim release. They're made when there's something majorly broken, or a nasty bug or vulnerability is found well before the next release is due out. The main benefit of doing this is the release engineer(s) can then create a RELEASE ISO that contains the security branch updates for the primary release. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message