Date: Sun, 3 Mar 2002 06:36:39 -0600 From: "Maildrop" <maildrop@qwest.net> To: "Kevin Golding" <kevin@caomhin.demon.co.uk> Cc: freebsd-newbies@freebsd.org Subject: RE: Release, Stable, Current Message-ID: <NGBBIILBAKIFGHHCHOHPEECNCDAA.maildrop@qwest.net> In-Reply-To: <Xs8hoCCxkgg8EwJw@caomhin.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Nice, this worked. Was using the example "stable-supfile" (/usr/share/examples/cvsup ?) and had RELENG_4, changed to RELENG_4_5, deleted /usr/src, synced up and got the 4.5 "production patch" (whatever it is called)... has a Newer (than before) UPDATING file which appears to be the "real" erata file :) Have to read over it a bit, but this feels like it is the right track: /usr/src/UPDATING: : This is for the 4.5 release branch. All entries since 4.5 are an : itemized list of commits to this branch, numbered from the beginning. : By this count, we're at 4.5.0p1. Thanks! Jack -----Original Message----- From: owner-freebsd-newbies@FreeBSD.ORG [mailto:owner-freebsd-newbies@FreeBSD.ORG]On Behalf Of Kevin Golding Sent: Sunday, March 03, 2002 5:30 AM To: Maildrop Cc: freebsd-newbies@freebsd.org Subject: Re: Release, Stable, Current In message <NGBBIILBAKIFGHHCHOHPGECLCDAA.maildrop@qwest.net>, Maildrop <maildrop@qwest.net> writes > >Doh! There was even a link on the main page. > >Just found this: >http://www.freebsd.org/releases/4.5R/errata.html > >This is all I should have to worry about, correct? Not really, although it's stuff you should be aware of. Basically you need to update your sources to follow the RELEASE tree. This is the tree that adds just security fixes and critical patches. You obviously seem comfortable with cvsup so just set the tag to RELENG_4_5 instead of RELENG_4 Once you get more confident you may decide to track -stable but by then you'll have learnt some of the kickers and things to watch out for. That said a lot of people who very much know what they're doing still only track release for production machines. It's a bit of a judgement call you need to make, but if ever you're unsure stick to release. Oh, and I don't know anyone who uses -current on a production machine, there's probably one or two but I think that's it. It should only be used on a machine that can afford downtime. Kevin >-----Original Message----- >From: owner-freebsd-newbies@FreeBSD.ORG >[mailto:owner-freebsd-newbies@FreeBSD.ORG]On Behalf Of Maildrop >Sent: Sunday, March 03, 2002 5:16 AM >To: freebsd-newbies@freebsd.org >Subject: Release, Stable, Current > > > >Have a quick question in regards to FreeBSD releases. > >The way I am understanding it, is that: > >Release (4.5) is the Production quality release >Stable (4.5.X) is the "Beta" (?) quality release >Current (5.0) is the Alpha (high development still going on) quality release > >If my assumation above are right, what would be the Production quality >release that includes only major bug fixes/security holes? > >Say 4.5 is released, in the Production world for awhile and someone finds a >XYZ expliot in it. If I cvs down stable, that should include the fix right >(?), but am I also getting a bunch of development / fearture code included >with it that may not be suitable for a production envoriment? > >Are all security holes/major bug fixes avaiable via CVS, or does each one of >them have to be applied manually? > >Is there a web page, etc that contains all the known issuses since the >Release (4.5) release? > >For example, today I installed 4.5 release and after install, synced >/usr/src up with 4.5 Stable just to see how much has changed... anyways >there was some changes to chmod for example... but not sure if this is a >require patch (ie. major security issuse with it) or if it is a bunch of >"beta" quality development/ fearture added that shouldn't be floating around >in a production envoirment. > >Is there a 4.5 "bugfix only" release floating around out there? > >Thanks, >Jack > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-newbies" in the body of the message > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-newbies" in the body of the message -- kevin@caomhin.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NGBBIILBAKIFGHHCHOHPEECNCDAA.maildrop>