Re: update confusion 4.8-STABLE to STABLE = 4.9-PRERELEASE !?
On Thu, Oct 02, 2003 at 12:29:20PM +0300, Alin-Adrian Anton wrote: Hey guys, Look what happened to me. I had a nice (cute) 4.8-STABLE. From time to time, I update it via cvsup. Ports to CURRENT, system sources to STABLE. Last time I updated from cvsup2.freebsd.org (I tried another one closer too, same result), and hah , after a buildworld, i had a brand new 4.9-PRERELEASE installed. This question gets asked several times for each release cycle - the short answer is that you are confused about the FreeBSD branch structure. I recommend you consult the archives and the FreeBSD handbook for extensive discussion. Kris pgp0.pgp Description: PGP signature
update confusion 4.8-STABLE to STABLE = 4.9-PRERELEASE !?
I just want to say Thank You for posting this: http://lists.freebsd.org/mailman/htdig/freebsd-questions/2003-October/02 1196.html I've read two books on FreeBSD and a lot of the Handbook, but I was still confused about this issue. The exact same thing happened to me that happned to the original poster of that message. Your reply clarified the issue perfectly for me. Thanks for taking the time. Luke Sheppard, CCNP, CCDA, CCSE Senior Security Consultant [EMAIL PROTECTED] Network Presence, LLC 310-216-6850, x15 5959 W. Century Blvd, Ste 734 310-216-6905 FAX Los Angeles, CA 90045-6508 www.netpr.com PGP Key: www.netpr.com/contact/pgpkeys/lukekey.asc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
update confusion 4.8-STABLE to STABLE = 4.9-PRERELEASE !?
Hey guys, Look what happened to me. I had a nice (cute) 4.8-STABLE. From time to time, I update it via cvsup. Ports to CURRENT, system sources to STABLE. Last time I updated from cvsup2.freebsd.org (I tried another one closer too, same result), and hah , after a buildworld, i had a brand new 4.9-PRERELEASE installed. I guess this might be a bug in cvsup, because this is how my cvsup file looks: --- *default host=cvsup10.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4 #*default release=cvs tag=. *default delete use-rel-suffix src-all #ports-all --- Is the updating to 4.9-PRERELEASE a normal behaviour intended by the Team, or is it a bug in cvsup client make it interpret commented line #*default release=cvs tag=. (though I don't think that would have 4.9-PRERELEASE as a result from 4.8-STABLE). Anyone help me clue this out, thanks in advance! Regards, Alin. smime.p7s Description: S/MIME Cryptographic Signature
Re: update confusion 4.8-STABLE to STABLE = 4.9-PRERELEASE !?
RELENG_4 has had various names over the past year or so... The name changes over time. If you think about it 4.9-PRERELEASE and 4.9-RELEASE for that matter are just snapshots/images of the 4.x branch at a certian date. 4.7-RC ... 4.7-PRERELEASE ... 4.7-STABLE 4.8-RC and so on On Thu, 2 Oct 2003 07:29 pm, Alin-Adrian Anton wrote: *default release=cvs tag=RELENG_4 #*default release=cvs tag=. Is the updating to 4.9-PRERELEASE a normal behaviour intended by the Team, or is it a bug in cvsup client make it interpret commented line _ JacobRhoden -- http://rhoden.id.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: update confusion 4.8-STABLE to STABLE = 4.9-PRERELEASE !?
JacobRhoden wrote: RELENG_4 has had various names over the past year or so... The name changes over time. If you think about it 4.9-PRERELEASE and 4.9-RELEASE for that matter are just snapshots/images of the 4.x branch at a certian date. 4.7-RC ... 4.7-PRERELEASE ... 4.7-STABLE 4.8-RC and so on On Thu, 2 Oct 2003 07:29 pm, Alin-Adrian Anton wrote: *default release=cvs tag=RELENG_4 #*default release=cvs tag=. Is the updating to 4.9-PRERELEASE a normal behaviour intended by the Team, or is it a bug in cvsup client make it interpret commented line _ JacobRhoden -- http://rhoden.id.au/ Ok got it. So the name -STABLE does not necessary mean the system is more stable than a PRERELEASE? I don't think a few security patches shall bring the system in an unstable state. And if the pathes are installed, the system name will remain 4.8-STABLE, not 4.9-PRERELEASE. The advisories said to update to STABLE, so I did, and I got 4.9-PRERELEASE. That is the new 'name' for STABLE? Thanks, Alin. smime.p7s Description: S/MIME Cryptographic Signature
Re: update confusion 4.8-STABLE to STABLE = 4.9-PRERELEASE !?
On Thu, Oct 02, 2003 at 12:29:20PM +0300, Alin-Adrian Anton wrote: Look what happened to me. I had a nice (cute) 4.8-STABLE. From time to time, I update it via cvsup. Ports to CURRENT, system sources to STABLE. Last time I updated from cvsup2.freebsd.org (I tried another one closer too, same result), and hah , after a buildworld, i had a brand new 4.9-PRERELEASE installed. I guess this might be a bug in cvsup, because this is how my cvsup file looks: --- *default host=cvsup10.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4 #*default release=cvs tag=. *default delete use-rel-suffix src-all #ports-all --- Is the updating to 4.9-PRERELEASE a normal behaviour intended by the Team, or is it a bug in cvsup client make it interpret commented line #*default release=cvs tag=. (though I don't think that would have 4.9-PRERELEASE as a result from 4.8-STABLE). This is entirely normal. You're tracking RELENG_4 a.k.a 4-STABLE. That started out with 'uname -r' saying 4.0-STABLE and over time, it has periodically mutated and continues to mutate into the each successive system version number -- in fact, that happens approximately every 4 months. Go look at the archives: you'll see posts saying much the same as you have at 4 month intervals right back to the inception of the 4-STABLE branch. The fact that from time to time the RELENG_4 sources may get labelled 4.9-PRERELEASE or some such is neither here nor there. It's all 4-STABLE. The name has little bearing on the actual stability of the system -- in fact, if the release process is working properly, the -PRERELEASE and -RCn and indeed the -RELEASE[*] versions should be, if anything, slightly *more* stable than the run of the mill -STABLE code. Of course, the course of software releases never does run quite that smoothly, but such is life. Cheers, Matthew [*] Which is identical to -STABLE for some vanishingly small amount of time right when the release gets cut. -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: update confusion 4.8-STABLE to STABLE = 4.9-PRERELEASE !?
On Thu, 2 Oct 2003 07:55 pm, Alin-Adrian Anton wrote: Ok got it. So the name -STABLE does not necessary mean the system is more stable than a PRERELEASE? I don't think a few security patches shall bring the system in an unstable state. And if the pathes are installed, the system name will remain 4.8-STABLE, not 4.9-PRERELEASE. The advisories said to update to STABLE, so I did, and I got 4.9-PRERELEASE. That is the new 'name' for STABLE? If I understand things correctly, There is a code branch for each major version of freebsd, ie RELENG_3, RELENG_4, etc, etc. Updates get applied to RELENG_4, and then snapshots are taken from that, so from RELENG_4, you get RELENG_4_8 and upcoming RELENG_4_9 and so on. You may wish to read http://www.freebsd.org/releases/4.9R/schedule.html for details of how the STABLE (that is RELENG_4) turns into the upcoming 4.9-RELEASE. Regards, Jacob _ JacobRhoden -- http://rhoden.id.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: update confusion 4.8-STABLE to STABLE = 4.9-PRERELEASE !?
Okay, thank you all! Alin. smime.p7s Description: S/MIME Cryptographic Signature
