Re: cvs tag usage
free...@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 r...@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 r...@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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
On Tue, Aug 4, 2009 at 5:32 PM, b. f.bf1...@googlemail.com wrote: He has _7_2_0_RELEASE, not RELENG_7_0_2_RELEASE. Well, neither actually. :) s/0_2/2_0/ . But I inferred from the context -- it seemed obvious, particularly from what he wrote later -- that he meant those choices as suffixes to RELENG, which he omitted for the sake of brevity. I assumed you also made this inference. Agreed, but IMHO, it's better to be precise and not assume too much. :-) OK guys this has now reached the point where I am again confudes -- here is my original posting amended to ensure there is no ambiguity I am confused about the usage of the tag for src. I took a look at the web pages and found the following choices: RELENG_7_BP RELENG_7_2_BP RELENG_7_2_0_RELEASE RELENG_7_2 But could not find anything that told me where -p2 fits into this!! # uname -a 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 To synchronize src and keep up to date do I use: *default release=cvs tag=RELENG_7_2 will this automatically track the latest version in 7_2 and therefore keep track with 7.2-RELEASE-p2 or later?? or do I need to use something like: *default release=cvs tag=RELENG_7_2-p2 or something else!! Where can I find some explanation on this? Maybe something from this discussion could be added to the handbook/synching.html page so the choice of suffix for configuring cvsup could be made easier for those who are not familiar with the meaning of undocumented suffixing such as -p2 !!. Another could there possibly be some consistency between the output from uname -a and the suffixing used for synching of the src be practicable. Please do not bite my head off if it is not practical -- I acknowledge it is a question born of ignorance and confusion chuckles david Thanks in advance David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
On Tue, Aug 4, 2009 at 5:32 PM, b. f.bf1...@googlemail.com wrote: He has _7_2_0_RELEASE, not RELENG_7_0_2_RELEASE. Well, neither actually. :) s/0_2/2_0/ . But I inferred from the context -- it seemed obvious, particularly from what he wrote later -- that he meant those choices as suffixes to RELENG, which he omitted for the sake of brevity. I assumed you also made this inference. Glen You hit the sweet spot!! David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
On Wed, 5 Aug 2009 10:00:09 +0100, David Southwell da...@vizion2000.net wrote: I took a look at the web pages and found the following choices: RELENG_7_BP RELENG_7_2_BP RELENG_7_2_0_RELEASE RELENG_7_2 But could not find anything that told me where -p2 fits into this!! The -p2 is appended when you follow RELENG_7_2, which is the security branch (release branch) of FreeBSD 7.2. You will get ONLY the patches. For example, when the second patch is applied and you download, compile and install the OS, uname will give 7.2-RELEASE-p2. If you follow RELENG_7, you get the stable branch. Here, more than just the patches are delivered to you when updating the sources. So you won't get -p2, but something like 7.0-STABLE together with your compile date. As far as I know, /etc/motd will be updated and then show 7.2-STABLE-20090101 (the proper date of course). The -STABLE branch is a bit experimental, allthough it includes those things that are considered to be running well. 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. To synchronize src and keep up to date do I use: *default release=cvs tag=RELENG_7_2 will this automatically track the latest version in 7_2 and therefore keep track with 7.2-RELEASE-p2 or later?? Exactly. 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. or do I need to use something like: *default release=cvs tag=RELENG_7_2-p2 No. As far as I know, you can't update to a specific patchlevel in this way. But using CVS correctly - don't ask me how to do this :-) - you can update your system to any point of time in development. or something else!! Or else. :-) Where can I find some explanation on this? The handbook mentions it in its comparison between RELEASE and STABLE. Maybe something from this discussion could be added to the handbook/synching.html page so the choice of suffix for configuring cvsup could be made easier for those who are not familiar with the meaning of undocumented suffixing such as -p2 !!. Good idea. Another could there possibly be some consistency between the output from uname -a and the suffixing used for synching of the src be practicable. The problem is that there are different naming conventions. Please do not bite my head off if it is not practical -- I acknowledge it is a question born of ignorance and confusion chuckles I already had horsehead goulash with sauerkraut, thanks. :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
David Southwell wrote: I am confused about the usage of the tag for src. I took a look at the web pages and found the following choices: _7_BP _7_2_BP _7_2_0_RELEASE _7_2 But could not find anything that told me where -p2 fits into this!! # uname -a 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 To synchronize src do I use: *default release=cvs tag=RELENG_7_2 will this automatically track the latest version in 7_2 and therefore keep track with 7.2-RELEASE-p2 or later?? Yes. RELENG_7_2 is the security patched update of Release. The -p2 means there have been two security patches applied to the source code. The actual release (RELENG_7_2_0_RELEASE) is static and will never change. The only thing that changes with _7_2 is the addition/inclusion of the patches you see in the security announcements. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
David Southwell wrote: I am confused about the usage of the tag for src. I took a look at the web pages and found the following choices: _7_BP _7_2_BP _7_2_0_RELEASE _7_2 But could not find anything that told me where -p2 fits into this!! # uname -a 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 To synchronize src do I use: *default release=cvs tag=RELENG_7_2 will this automatically track the latest version in 7_2 and therefore keep track with 7.2-RELEASE-p2 or later?? Yes. RELENG_7_2 is the security patched update of Release. The -p2 means there have been two security patches applied to the source code. The actual release (RELENG_7_2_0_RELEASE) is static and will never change. The only thing that changes with _7_2 is the addition/inclusion of the patches you see in the security announcements. -Mike Thanks for being helpful.. it might be useful if these designations appeared somewhere in the documentation-- but I guess there is enough for people to do!!! From what you are saying using *default release=cvs tag=RELENG_7_2 will work for me Thanks again David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
On Tue, Aug 4, 2009 at 1:43 PM, David Southwellda...@vizion2000.net wrote: I am confused about the usage of the tag for src. I took a look at the web pages and found the following choices: _7_BP _7_2_BP BP ? _7_2_0_RELEASE Should be RELENG. Don't blindly follow how-tos. _7_2 But could not find anything that told me where -p2 fits into this!! http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html # uname -a 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 To synchronize src do I use: *default release=cvs tag=RELENG_7_2 will this automatically track the latest version in 7_2 and therefore keep track with 7.2-RELEASE-p2 or later?? or do I need to use something like: *default release=cvs tag=RELENG_7_2-p2 No. Read the link I posted above. Where can I find some explanation on this? Thanks in advance -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
Glen Barber glen.j.barber at gmail.com wrote: On Tue, Aug 4, 2009 at 1:43 PM, David Southwelldavid at vizion2000.net wrote: I am confused about the usage of the tag for src. I took a look at the web pages and found the following choices: _7_BP _7_2_BP BP ? It is the branchpoint tag, made when a release branch is first created: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/release-proc.html It is not documented in most places because it is primarily of interest to developers. _7_2_0_RELEASE Should be RELENG. Don't blindly follow how-tos. RELENG_7_2_0_RELEASE is a valid tag. Don't make pronouncements if you haven't verified them. _7_2 But could not find anything that told me where -p2 fits into this!! http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html More to the point is the following page in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
On Tue, Aug 4, 2009 at 3:54 PM, b. f.bf1...@googlemail.com wrote: Glen Barber glen.j.barber at gmail.com wrote: On Tue, Aug 4, 2009 at 1:43 PM, David Southwelldavid at vizion2000.net wrote: I am confused about the usage of the tag for src. I took a look at the web pages and found the following choices: _7_BP _7_2_BP BP ? It is the branchpoint tag, made when a release branch is first created: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/release-proc.html I see. Noted. It is not documented in most places because it is primarily of interest to developers. _7_2_0_RELEASE Should be RELENG. Don't blindly follow how-tos. RELENG_7_2_0_RELEASE is a valid tag. Don't make pronouncements if you haven't verified them. He has _7_2_0_RELEASE, not RELENG_7_0_2_RELEASE. _7_2 But could not find anything that told me where -p2 fits into this!! http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html More to the point is the following page in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
On Tue, Aug 04, 2009 at 03:07:20PM -0400, Glen Barber wrote: On Tue, Aug 4, 2009 at 1:43 PM, David Southwellda...@vizion2000.net wrote: I am confused about the usage of the tag for src. I took a look at the web pages and found the following choices: _7_BP _7_2_BP BP ? BP = Branch Point. It is a tag which marks the place where the corresponding branch was created. _7_2_0_RELEASE Should be RELENG. Don't blindly follow how-tos. _7_2 But could not find anything that told me where -p2 fits into this!! http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html # uname -a 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 To synchronize src do I use: *default release=cvs tag=RELENG_7_2 will this automatically track the latest version in 7_2 and therefore keep track with 7.2-RELEASE-p2 or later?? or do I need to use something like: *default release=cvs tag=RELENG_7_2-p2 No. Read the link I posted above. Where can I find some explanation on this? Thanks in advance -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Insert your favourite quote here. Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
On Tuesday 04 August 2009 12:52:54 Erik Trulsson wrote: On Tue, Aug 04, 2009 at 03:07:20PM -0400, Glen Barber wrote: On Tue, Aug 4, 2009 at 1:43 PM, David Southwellda...@vizion2000.net wrote: I am confused about the usage of the tag for src. I took a look at the web pages and found the following choices: _7_BP _7_2_BP BP ? BP = Branch Point. It is a tag which marks the place where the corresponding branch was created. And for developers or interesting parties, one can create cvs diff using -rRELENG_7_2_BP -rRELENG_7_2_RELEASE to see how many fixes hit the tree during the final release stage. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
On 8/4/09, Glen Barber glen.j.bar...@gmail.com wrote: _7_2_0_RELEASE Should be RELENG. Don't blindly follow how-tos. RELENG_7_2_0_RELEASE is a valid tag. Don't make pronouncements if you haven't verified them. He has _7_2_0_RELEASE, not RELENG_7_0_2_RELEASE. Well, neither actually. :) s/0_2/2_0/ . But I inferred from the context -- it seemed obvious, particularly from what he wrote later -- that he meant those choices as suffixes to RELENG, which he omitted for the sake of brevity. I assumed you also made this inference. ... Mel Flynn wrote: And for developers or interesting parties, one can create cvs diff using -rRELENG_7_2_BP -rRELENG_7_2_RELEASE to see how many fixes hit the tree during the final release stage. How many interesting parties have you been to, Mel, where such a listing came in handy? ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
On Tue, Aug 4, 2009 at 5:32 PM, b. f.bf1...@googlemail.com wrote: He has _7_2_0_RELEASE, not RELENG_7_0_2_RELEASE. Well, neither actually. :) s/0_2/2_0/ . But I inferred from the context -- it seemed obvious, particularly from what he wrote later -- that he meant those choices as suffixes to RELENG, which he omitted for the sake of brevity. I assumed you also made this inference. Agreed, but IMHO, it's better to be precise and not assume too much. :-) -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
