Re: CVSUP of 4.7 only?
On 2003-02-22 01:26, Tuc [EMAIL PROTECTED] wrote: RELENG_4_7 - More current than _RELEASE, but only with critical updates. What you describe, in slightly different words, is EXACTLY what the tag RELENG_4_7 is :-))) I thought it was 4.7 with **ONLY** security and **ONLY** critical updates, NOT anything else. That's exactly what it is. It is a security branch[3]. No new features are added to it. Not even manpage updates. The security branches *only* receive absolutely minimal changes to fix any problems related to security they might have. My impression was 4_7 was just those items, 4 was those plus other non-important and things to get us to the next level. No, that's RELENG_4. The security branches[3] like RELENG_4_7 *only* receive critical security related fixes. That's it. Nothing more. They are not the same as RELENG_4. So your telling me that if I CVSUP 4_7, I technically will get the same tree as 4 up until the day the uname banner changed to 4.8-PRERELEASE? Thats not my impression of what 4_7 is. I don't know what you mean by 4_7. In fact, before this turns out a very confusing thing for both of us, since you seem to mean different things by saying critical fixes than I do, please, if you still feel confused about tags their meaning and what the release process of FreeBSD is, refer to the following documents: [1] FreeBSD Release Engineering. http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/article.html [2] The FreeBSD Handbook. Staying STABLE with FreeBSD. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html#STABLE [3] FreeBSD Security Advisories http://www.freebsd.org/security/#adv If, after reading these you still have questions about the meaning of every tag, then it's a bug in the documentation and we should do something about it :) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CVSUP of 4.7 only?
On Friday 21 February 2003 06:08 am, Tuc wrote: Hi, I have : *default release=cvs tag=RELENG_4 in my stable-supfile, and on one machine all of a sudden on the last update I have : FreeBSD vjofn.ttsg.com 4.8-PRERELEASE FreeBSD 4.8-PRERELEASE #1: Thu Feb 20 13:5 2:11 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VJOFN i386 Heres my problem. I've been CVSUPing machines with RELENG_4, is there a way I can continue only with the 4.7 tree? I tried : *default release=cvs tag=RELENG_4_7 and it looked like it was re-checking out everything. Does that mean it was getting 4.7 as it was first released, and when I did RELENG_4 it was 4.X as current as it was? Is there another tag for 4.7 most current? That is what it was doing. You were checking out 4.7-release plus security fixes. There is no more 4.7 most current. You could set the date on your cvsup but there won't be any more changes to 4.7-stable. It doesn't exist in the current tree. In a while, RELENG_4 will be 4.8-release and then 4.8-stable. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: CVSUP of 4.7 only?
Hi, CVS Tag list: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html Phil. -Original Message- From: Tuc [mailto:[EMAIL PROTECTED]] Sent: 21 February 2003 14:08 To: [EMAIL PROTECTED] Subject: CVSUP of 4.7 only? Hi, I have : *default release=cvs tag=RELENG_4 in my stable-supfile, and on one machine all of a sudden on the last update I have : FreeBSD vjofn.ttsg.com 4.8-PRERELEASE FreeBSD 4.8-PRERELEASE #1: Thu Feb 20 13:5 2:11 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VJOFN i386 Heres my problem. I've been CVSUPing machines with RELENG_4, is there a way I can continue only with the 4.7 tree? I tried : *default release=cvs tag=RELENG_4_7 and it looked like it was re-checking out everything. Does that mean it was getting 4.7 as it was first released, and when I did RELENG_4 it was 4.X as current as it was? Is there another tag for 4.7 most current? Thanks, Tuc/TTSG Internet Services, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CVSUP of 4.7 only?
Hi, CVS Tag list: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html So if I read it right: RELENG_4_7_0_RELEASE - First ever 4.7 release. Oldest and never updated past that day it was tagged RELENG_4_7 - More current than _RELEASE, but only with critical updates. RELENG_4 - More current than 4_7, has non critical updates and tweaks, but doesn't guarantee it being 4_7 branch. So there isn't a way to make sure I stay in 4.7, but get all the fixes, right? Thanks, Tuc/TTSG Internet Services, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: CVSUP of 4.7 only?
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs- tags.html So if I read it right: RELENG_4_7_0_RELEASE - First ever 4.7 release. Oldest and never updated past that day it was tagged RELENG_4_7 - More current than _RELEASE, but only with critical updates. RELENG_4 - More current than 4_7, has non critical updates and tweaks, but doesn't guarantee it being 4_7 branch. Sounds right. So there isn't a way to make sure I stay in 4.7, but get all the fixes, right? Well... that would surely be RELENG_4_7 i.e. the 4.7 release + security fixes required. As soon as you want general updates to the system then you're talking about moving from 4.7-Release onto the 4-Stable branch. I'm no FreeBSD developer so if someone wants to explain better what each of the tags means feel free. Phil. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CVSUP of 4.7 only?
On Friday 21 February 2003 03:16 pm, Kent Stewart wrote: On Friday 21 February 2003 06:08 am, Tuc wrote: Hi, I have : *default release=cvs tag=RELENG_4 in my stable-supfile, and on one machine all of a sudden on the last update I have : FreeBSD vjofn.ttsg.com 4.8-PRERELEASE FreeBSD 4.8-PRERELEASE #1: Thu Feb 20 13:5 2:11 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VJOFN i386 Heres my problem. I've been CVSUPing machines with RELENG_4, is there a way I can continue only with the 4.7 tree? I tried : *default release=cvs tag=RELENG_4_7 That is correct to continue with the 4.7 release branch. See below and it looked like it was re-checking out everything. That is what it was doing. You were checking out 4.7-release plus security fixes. correct. Tuc, you were in essence reverting to 4.7 release plus the security fixes, which is behind in the development tree from 4-stable (4.x) which is rapidly approaching 4.8-release. Does that mean it was getting 4.7 as it was first released, No, it is the release branch. It is possible to get it as it was first released with a different tag, but why would you unless one of the security fixes broke something for you? and when I did RELENG_4 it was 4.X as current as it was? yes Is there another tag for 4.7 most current? There is no more 4.7 most current. Kent, that is not correct. That is what the release branch *is*. 4.7 release plus security fixes. and the tag for it is as above. see: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html You could set the date on your cvsup but there won't be any more changes to 4.7-stable. There is no such thing as 4.7-stable It doesn't exist in the current tree. In a while, RELENG_4 will be 4.8-release and then 4.8-stable. That's a way of thinking of it, but a confusing one, and not the one used by the project. The stable tree only has a major number like 4-stable or eventually 5-stable. The releases are static points along the moving stable development track like this --\\\-4.x stable \ \ \ \-4.6Rel \-4.7Rel \-4.8Rel (soon) \ \-4.7Rel-p1 \ \-4.7Rel-p2 etc 4-stable is called 4-stable throughout the process of branching off releases, to avoid confusion. (which changing the name of 4-stable after every release could cause.) It's just the way it's done. Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CVSUP of 4.7 only?
On Friday 21 February 2003 10:10 am, taxman wrote: On Friday 21 February 2003 03:16 pm, Kent Stewart wrote: On Friday 21 February 2003 06:08 am, Tuc wrote: Hi, I have : *default release=cvs tag=RELENG_4 in my stable-supfile, and on one machine all of a sudden on the last update I have : FreeBSD vjofn.ttsg.com 4.8-PRERELEASE FreeBSD 4.8-PRERELEASE #1: Thu Feb 20 13:5 2:11 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VJOFN i386 Heres my problem. I've been CVSUPing machines with RELENG_4, is there a way I can continue only with the 4.7 tree? I tried : *default release=cvs tag=RELENG_4_7 That is correct to continue with the 4.7 release branch. See below and it looked like it was re-checking out everything. That is what it was doing. You were checking out 4.7-release plus security fixes. correct. Tuc, you were in essence reverting to 4.7 release plus the security fixes, which is behind in the development tree from 4-stable (4.x) which is rapidly approaching 4.8-release. Does that mean it was getting 4.7 as it was first released, No, it is the release branch. It is possible to get it as it was first released with a different tag, but why would you unless one of the security fixes broke something for you? and when I did RELENG_4 it was 4.X as current as it was? yes Is there another tag for 4.7 most current? There is no more 4.7 most current. Kent, that is not correct. That is what the release branch *is*. 4.7 release plus security fixes. and the tag for it is as above. see: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.ht ml Not true. See the following RELENG_4_7 The release branch for FreeBSD-4.7, used only for security advisories and other seriously critical fixes. The release is RELENG_4_7_0_RELEASE FreeBSD 4.7 Kent You could set the date on your cvsup but there won't be any more changes to 4.7-stable. There is no such thing as 4.7-stable It doesn't exist in the current tree. In a while, RELENG_4 will be 4.8-release and then 4.8-stable. That's a way of thinking of it, but a confusing one, and not the one used by the project. The stable tree only has a major number like 4-stable or eventually 5-stable. The releases are static points along the moving stable development track like this --\\\-4.x stable \ \ \ \-4.6Rel \-4.7Rel \-4.8Rel (soon) \ \-4.7Rel-p1 \ \-4.7Rel-p2 etc 4-stable is called 4-stable throughout the process of branching off releases, to avoid confusion. (which changing the name of 4-stable after every release could cause.) It's just the way it's done. Tim -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CVSUP of 4.7 only?
On Friday 21 February 2003 10:10 am, taxman wrote: On Friday 21 February 2003 03:16 pm, Kent Stewart wrote: On Friday 21 February 2003 06:08 am, Tuc wrote: Hi, I have : *default release=cvs tag=RELENG_4 in my stable-supfile, and on one machine all of a sudden on the last update I have : FreeBSD vjofn.ttsg.com 4.8-PRERELEASE FreeBSD 4.8-PRERELEASE #1: Thu Feb 20 13:5 2:11 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VJOFN i386 Heres my problem. I've been CVSUPing machines with RELENG_4, is there a way I can continue only with the 4.7 tree? I tried : *default release=cvs tag=RELENG_4_7 That is correct to continue with the 4.7 release branch. See below and it looked like it was re-checking out everything. That is what it was doing. You were checking out 4.7-release plus security fixes. correct. Tuc, you were in essence reverting to 4.7 release plus the security fixes, which is behind in the development tree from 4-stable (4.x) which is rapidly approaching 4.8-release. Does that mean it was getting 4.7 as it was first released, No, it is the release branch. It is possible to get it as it was first released with a different tag, but why would you unless one of the security fixes broke something for you? Never mind what I said. I was in a hurry and didn't read it properly. He was following stable and none of the above will get that back for him. As a current version, 4.7-stable is gone, since RELENG_4 is now called FreeBSD ruby 4.8-PRERELEASE FreeBSD 4.8-PRERELEASE #30: Tue Feb 18 20:10:15 PST 2003 [EMAIL PROTECTED]:/usr2/obj/usr/src/sys/RUBY i386 Kent and when I did RELENG_4 it was 4.X as current as it was? yes Is there another tag for 4.7 most current? There is no more 4.7 most current. Kent, that is not correct. That is what the release branch *is*. 4.7 release plus security fixes. and the tag for it is as above. see: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.ht ml You could set the date on your cvsup but there won't be any more changes to 4.7-stable. There is no such thing as 4.7-stable It doesn't exist in the current tree. In a while, RELENG_4 will be 4.8-release and then 4.8-stable. That's a way of thinking of it, but a confusing one, and not the one used by the project. The stable tree only has a major number like 4-stable or eventually 5-stable. The releases are static points along the moving stable development track like this --\\\-4.x stable \ \ \ \-4.6Rel \-4.7Rel \-4.8Rel (soon) \ \-4.7Rel-p1 \ \-4.7Rel-p2 etc 4-stable is called 4-stable throughout the process of branching off releases, to avoid confusion. (which changing the name of 4-stable after every release could cause.) It's just the way it's done. Tim -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CVSUP of 4.7 only?
sorry I missed this part of the thread. see my other post too. On Friday 21 February 2003 03:58 pm, Tuc wrote: CVS Tag list: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html So if I read it right: RELENG_4_7_0_RELEASE - First ever 4.7 release. Oldest and never updated past that day it was tagged I think so. *Critical* fixes used to go into the release itself, which got confusing and I think that is why the release branches were made. RELENG_4_7 - More current than _RELEASE, but only with critical updates. yep basically. It results in point releases along the release branch. I think there are like 15 on the 4.7 brnach now. I can't figure out how ot tell without upgrading or if there is a way to upgrade to a specific one. RELENG_4 - More current than 4_7, has non critical updates and tweaks, but doesn't guarantee it being 4_7 branch. yes, see my other post. So there isn't a way to make sure I stay in 4.7, but get all the fixes, right? That's true. FreeBSD is a fast moving target and to add both features and bug fixes you have to move on, which is what 4-stable does. Personally I'd like to see the release branches have a lot more stability fixes along with the security fixes. But this could require massive amounts of work and there are only so many people and resources to go around. Maintaining the release branches with only security fixes is I'm sure already a great deal of work, and is a great step in the right direction I believe. I dunno, maybe it would be possible for only the last release branch to get stability fixes along with security fixes. That may just work. I've wanted something like that for years. It would bring FreeBSD farther along in being the most stable free OS out there and satisfy the needs of the super conservative. Personally I'd rather have a super super stable OS, I don't really care about performance beyond a reasonable point. I'd like to get to the point where there are FreeBSD releases as bug free as Tex. I think that is possible with the release branches. Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CVSUP of 4.7 only?
On 2003-02-21 09:58, Tuc [EMAIL PROTECTED] wrote: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html So if I read it right: RELENG_4_7_0_RELEASE - First ever 4.7 release. Oldest and never updated past that day it was tagged RELENG_4_7 - More current than _RELEASE, but only with critical updates. RELENG_4 - More current than 4_7, has non critical updates and tweaks, but doesn't guarantee it being 4_7 branch. So there isn't a way to make sure I stay in 4.7, but get all the fixes, right? joke *cough* .. don't you read what you paste? :-P /joke What you describe, in slightly different words, is EXACTLY what the tag RELENG_4_7 is :-))) - Giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CVSUP of 4.7 only?
RELENG_4_7 - More current than _RELEASE, but only with critical updates. joke *cough* .. don't you read what you paste? :-P /joke Actually, yes, I do. What you describe, in slightly different words, is EXACTLY what the tag RELENG_4_7 is :-))) I thought it was 4.7 with **ONLY** security and **ONLY** critical updates, NOT anything else. My impression was 4_7 was just those items, 4 was those plus other non-important and things to get us to the next level. So your telling me that if I CVSUP 4_7, I technically will get the same tree as 4 up until the day the uname banner changed to 4.8-PRERELEASE? Thats not my impression of what 4_7 is. Tuc/TTSG Internet Services, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
