Re: CVS tags
Josef Grosch wrote: I have been spending a lot of time building machines at work. Our engineers want to have the machine in question to have a specific version of FreeBSD, ie. FreeBSD 4.11-RELEASE-p11 for example. I have noticed that there is not a CVS tag for this in the tree. Is there a specific reason why we do not tag the tree for the patch levels? Josef Wouldn't that be Releng_4_11 or Releng_4_11p11? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVS tags
I have been spending a lot of time building machines at work. Our engineers want to have the machine in question to have a specific version of FreeBSD, ie. FreeBSD 4.11-RELEASE-p11 for example. I have noticed that there is not a CVS tag for this in the tree. Is there a specific reason why we do not tag the tree for the patch levels? Although it should never be necessary to use -p11 explicitely, you can get it if you use RELENG_4_11 and the date 2005/06/30 00:00:00 for example. The appropriate line in your supfile looks like this: *default release=cvs tag=RELENG_4_11 date=2005.06.30.00.00.00 The file src/sys/conf/newvers.sh contains the version number. You can determine the date in the CVS repository. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/conf/newvers.sh?f=uonly_with_tag=RELENG_4_11logsort=date Regards Björn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
CVS tags
I have been spending a lot of time building machines at work. Our engineers want to have the machine in question to have a specific version of FreeBSD, ie. FreeBSD 4.11-RELEASE-p11 for example. I have noticed that there is not a CVS tag for this in the tree. Is there a specific reason why we do not tag the tree for the patch levels? Josef -- Josef Grosch | Another day closer to a | FreeBSD 6.2 [EMAIL PROTECTED] | Micro$oft free world | Berkeley, Ca. pgp7Di4Lgn0YR.pgp Description: PGP signature
Re: CVS tags
Josef Grosch wrote: I have been spending a lot of time building machines at work. Our engineers want to have the machine in question to have a specific version of FreeBSD, ie. FreeBSD 4.11-RELEASE-p11 for example. I have noticed that there is not a CVS tag for this in the tree. Is there a specific reason why we do not tag the tree for the patch levels? Yes; two reasons in fact: 1. Tagging the tree for every security update isn't feasible in CVS. 2. There is a branch available for RELEASE plus the all available security and critical errata fixes (RELENG_X_Y for X.Y-RELEASE), and you should never not install all available security and critical errata fixes. Colin Percival FreeBSD Security Officer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Where are CVS Tags Announced
I was looking forward to the tagging of RELEASE_6_2 in the ports tree. I surfed around cvsweb but didn't see anything that looked like a tag announcement. Where do I look to determine if the sources have been tagged with a new release? Thanks, Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Where are CVS Tags Announced
Jason C. Wells wrote: I was looking forward to the tagging of RELEASE_6_2 in the ports tree. I surfed around cvsweb but didn't see anything that looked like a tag announcement. Where do I look to determine if the sources have been tagged with a new release? Thanks, Jason ___ this is where i check for them: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Where are CVS Tags Announced
On Wed, Oct 25, 2006 at 10:41:16AM -0700, Jason C. Wells wrote: I was looking forward to the tagging of RELEASE_6_2 in the ports tree. I surfed around cvsweb but didn't see anything that looked like a tag announcement. Where do I look to determine if the sources have been tagged with a new release? Sign up for the freebsd-announce Email list. It only gets messages when something is officially announced so it won't add much traffic to your Email. jerry Thanks, Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
what's different between src CVS Tags RELENG_*_BP and RELENG_*?
hey all, i just know the release src tag is RELENG_*_RELEASE. lveax ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
CVS Tags for 5.x
I have been reading all the documentation I can find concerning cvsup. My supfile specifies CVS tag RELENG_5_1 *default release=cvs tag=RELENG_5_1 *default delete use-rel-suffix *default compress *default tag=. src-all When I type uname -a, I get: FreeBSD skrap-node.skrap.net 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Thu Jan 29 23:48:04 CST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 I would assume given the above cvs supfile, that my Kernel would compile and report 5.1 build. Am I splitting hairs, or should I change my supfile cvs tag to something different. Jack ** The information contained in this message, including attachments, may contain privileged or confidential information that is intended to be delivered only to the person identified above. If you are not the intended recipient, or the person responsible for delivering this message to the intended recipient, ALLTEL requests that you immediately notify the sender and asks that you do not read the message or its attachments, and that you delete them without copying or sending them to anyone else. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Clarification on CVS Tags
Good morning everyone. I was hoping to get some verification regarding CVS Tags. I'm pretty sure I understand, but just wanted to have my thoughts validated for me. In reading the CVS Tag page in the handbook, I understand the basics of what is going on. If I specify this in my cvsup file: RELENG_4_8 I will follow the Release Branch of 4.8, plus security patches. This would be a good choice for production servers. RELENG_4 For this, you are following the entire 4.x stable branch. In theory, if I install 4.5 and set this up in my cvsup file and run it, I will have the source tree going all the way to 4.9rc# correct? From here, you could build world? Finally: RELENG_4_8_0_RELEASE This would follow just the source, ports and docs tree up to 4.8, the frozen section, correct? Why would someone want to use this particular setup? What are the benefits? Drawbacks? Would it work in a sense that if I installed 4.4 on a server, set this up in my cvsup file to RELENG_4_8_0_RELEASE, ran the update to update sources, ports and docs, then make world: That then would make my box 4.8 ? I appreciate everyones help and insight. Just want to make sure I understand this correctly. Thanks. Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clarification on CVS Tags
On Tue, Oct 28, 2003 at 09:43:20AM -0800, Jason Williams wrote: Good morning everyone. I was hoping to get some verification regarding CVS Tags. I'm pretty sure I understand, but just wanted to have my thoughts validated for me. In reading the CVS Tag page in the handbook, I understand the basics of what is going on. If I specify this in my cvsup file: RELENG_4_8 I will follow the Release Branch of 4.8, plus security patches. This would be a good choice for production servers. Correct. RELENG_4 For this, you are following the entire 4.x stable branch. In theory, if I install 4.5 and set this up in my cvsup file and run it, I will have the source tree going all the way to 4.9rc# correct? From here, you could build world? Correct. At the moment, RELENG_4 will get you 4.9-RC4, which will shortly become 4.9-RELEASE for a few minutes while the RELENG_4_9 branch is created, and then 4.9-STABLE. If you're willing to wait for a few days RELENG_4_9 would also be a good choice for a production server. Finally: RELENG_4_8_0_RELEASE This would follow just the source, ports and docs tree up to 4.8, the frozen section, correct? Why would someone want to use this particular setup? What are the benefits? Drawbacks? Would it work in a sense that if I installed 4.4 on a server, set this up in my cvsup file to RELENG_4_8_0_RELEASE, ran the update to update sources, ports and docs, then make world: That then would make my box 4.8 ? Not so correct. RELENG_4_8_0_RELEASE marks the state of the system sources at the point that the RELENG_4_8 branch was created, and what went onto the release CDs. Yes, you can use this tag to download sources and building world from there will get you 4.8-RELEASE. However, it's not generally useful to put this tag into a cvsup sup-file -- principally because it marks a point in time, and once you've downloaded it, there won't be any updates. So: no security patches etc. If you're tempted to use this tag, then you probably really want to use RELENG_4_8 or RELENG_4_9 instead. Note that the RELENG_4_x and RELENG_5_x tags apply only to the system sources. The one important tag you've not mentionned is '.', also known as the HEAD in cvs terms. When applied to the system sources, this gets you 5-CURRENT, but unless you're a high powered system hacker type, you don't want that. Ports and docs however, are a different matter. For those collections '.' is the only game in town. The RELENG_x_y tags simply don't exist, and if you accidentally try and cvsup ports using one of them, you'll end up deleting your whole ports tree. [The RELENG_x_y_0_RELEASE tags do exist, but exactly like the system sources they just serve to mark what goes onto the CD Roms.] Cheers, Matthew -- 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: Clarification on CVS Tags
Thanks Matthew for your explanation. You answered a lot of my questions. Makes sense now really. Just out of curiosity, why would someone want to use: RELENG_4_8_0_RELEASE? Is there some type of benefit? One would think that the best option for production servers is: RELENG_4_8 THanks for your insight. Jason At 06:37 PM 10/28/2003 +, you wrote: On Tue, Oct 28, 2003 at 09:43:20AM -0800, Jason Williams wrote: Good morning everyone. I was hoping to get some verification regarding CVS Tags. I'm pretty sure I understand, but just wanted to have my thoughts validated for me. In reading the CVS Tag page in the handbook, I understand the basics of what is going on. If I specify this in my cvsup file: RELENG_4_8 I will follow the Release Branch of 4.8, plus security patches. This would be a good choice for production servers. Correct. RELENG_4 For this, you are following the entire 4.x stable branch. In theory, if I install 4.5 and set this up in my cvsup file and run it, I will have the source tree going all the way to 4.9rc# correct? From here, you could build world? Correct. At the moment, RELENG_4 will get you 4.9-RC4, which will shortly become 4.9-RELEASE for a few minutes while the RELENG_4_9 branch is created, and then 4.9-STABLE. If you're willing to wait for a few days RELENG_4_9 would also be a good choice for a production server. Finally: RELENG_4_8_0_RELEASE This would follow just the source, ports and docs tree up to 4.8, the frozen section, correct? Why would someone want to use this particular setup? What are the benefits? Drawbacks? Would it work in a sense that if I installed 4.4 on a server, set this up in my cvsup file to RELENG_4_8_0_RELEASE, ran the update to update sources, ports and docs, then make world: That then would make my box 4.8 ? Not so correct. RELENG_4_8_0_RELEASE marks the state of the system sources at the point that the RELENG_4_8 branch was created, and what went onto the release CDs. Yes, you can use this tag to download sources and building world from there will get you 4.8-RELEASE. However, it's not generally useful to put this tag into a cvsup sup-file -- principally because it marks a point in time, and once you've downloaded it, there won't be any updates. So: no security patches etc. If you're tempted to use this tag, then you probably really want to use RELENG_4_8 or RELENG_4_9 instead. Note that the RELENG_4_x and RELENG_5_x tags apply only to the system sources. The one important tag you've not mentionned is '.', also known as the HEAD in cvs terms. When applied to the system sources, this gets you 5-CURRENT, but unless you're a high powered system hacker type, you don't want that. Ports and docs however, are a different matter. For those collections '.' is the only game in town. The RELENG_x_y tags simply don't exist, and if you accidentally try and cvsup ports using one of them, you'll end up deleting your whole ports tree. [The RELENG_x_y_0_RELEASE tags do exist, but exactly like the system sources they just serve to mark what goes onto the CD Roms.] Cheers, Matthew -- 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clarification on CVS Tags
On Tue, 28 Oct 2003 11:00:32 -0800, Jason Williams [EMAIL PROTECTED] said: Thanks Matthew for your explanation. You answered a lot of my questions. Makes sense now really. Just out of curiosity, why would someone want to use: RELENG_4_8_0_RELEASE? Is there some type of benefit? One would think that the best option for production servers is: RELENG_4_8 THanks for your insight. Releases are thoroughly tested through multiple release candidate stages, but bugs occasionally slip through even there. The security/bugfix branch is not as widely tested, but is reliable to the extent that a few isolated fixes shouldn't break anything and can undergo fairly thorough testing by relatively fewer people. There are those who will trust the thorough testing theory more than the few-isolated-fixes theory. Also, particular production servers may not be running the piece of the base system in which a security hole is found, e.g., sendmail. Both are legitimate reasons to stick with the release rather than the security branch. Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clarification on CVS Tags
Jason Williams [EMAIL PROTECTED] writes: Just out of curiosity, why would someone want to use: RELENG_4_8_0_RELEASE? Is there some type of benefit? One would think that the best option for production servers is: RELENG_4_8 Basically, yes. Tags are used for a number of reasons besides indicating what end-users should cvsup. It is very important to be able to reproduce exactly what was in a given release, even if you're not recommending that any new installations of that release. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clarification on CVS Tags
At 11:00 AM -0800 10/28/03, Jason Williams wrote: Thanks Matthew for your explanation. You answered a lot of my questions. Makes sense now really. Just out of curiosity, why would someone want to use: RELENG_4_8_0_RELEASE? Is there some type of benefit? One would think that the best option for production servers is: RELENG_4_8 Thanks for your insight. The security or safe branches (such as RELENG_4_8) are relatively new. We still have to have tags such as RELENG_4_8_0_RELEASE for the release process, and you can use any tag for cvsup. Before the security branches existed, we used to encourage people to upgrade to those release-tags instead of upgrading to stable. There are still times when you might want to cvsup to a release point. Of course, once you do the buildworld for that point, then you'll never see any new changes until you switch to a different tag for cvsup. For instance, it might be quite reasonable to cvsup to a release tag, and once you know that worked you would then cvsup to some later release tag, or to RELENG_4 (stable). -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
