Re: how to track 6.0 increments ?
On Sunday 04 December 2005 17:20, ke.han wrote: I don't want to follow current or stable (I don't think). I just want security fixes and other changes that might be termed 6.01 if there were such a thing. I've always wondered this. Is there a reason why the FreeBSD team put security updates into a branch rather than a 6_0_x release tag? Ashley ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to track 6.0 increments ?
On Monday 05 December 2005 10:56, Ashley Moran wrote: On Sunday 04 December 2005 17:20, ke.han wrote: I don't want to follow current or stable (I don't think). I just want security fixes and other changes that might be termed 6.01 if there were such a thing. I've always wondered this. Is there a reason why the FreeBSD team put security updates into a branch rather than a 6_0_x release tag? If you are asking why they don't use a different tag for each point release, then I think the answer is that it would require you to know precisely what the latest release is and edit the cvsup file each time. With RELENG_6_0 you get the latest point release automatically. Incidently in 6.0.x, x is not the point release number, it's a number that's only rarely used. The 5.2 release had some substantial fixes, and the FreeBSD version was bumped up to 5.2.1, though the tag was still RELENG_5_2. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to track 6.0 increments ?
Ashley Moran [EMAIL PROTECTED] writes: On Sunday 04 December 2005 17:20, ke.han wrote: I don't want to follow current or stable (I don't think). I just want security fixes and other changes that might be termed 6.01 if there were such a thing. I've always wondered this. Is there a reason why the FreeBSD team put security updates into a branch rather than a 6_0_x release tag? It's more convenient for the RE folks, usually more convenient for end-users, and uses fewer resources in propagating the repository changes. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to track 6.0 increments ?
ke.han wrote: I have installed 6.0 and would like to follow important changes before something labeled 6.1 comes out. What is the prescribed method for this? I don't want to follow current or stable (I don't think). I just want security fixes and other changes that might be termed 6.01 if there were such a thing. To add to the question, while playing with my system, I did: cvsup -L 2 -h cvsup.FreeBSD.org /usr/share/examples/cvsup/standard-supfile ...and then later... cvsup -L 2 -h cvsup.FreeBSD.org /usr/share/examples/cvsup/stable-supfile I have not recompiled the kernel or anything. Just sync'd the source. So, how do I get things back to the 6.0 install source? and how do I track things from this point? I have read all the handbook has to offer. Unfortunately, it is mostly general information. I need a simple clear recipe. thanks, ke han Create your own - something like this: # Development branch for 6-STABLE. (RELENG_6) # # This file contains all of the CVSup collections that make up the # FreeBSD-stable source tree. # *default host=cvsup2.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_6 *default delete use-rel-suffix src-all # Security branch for 6.0-RELEASE-px. (RELENG_6_0) # # This file contains all of the CVSup collections that make up the # FreeBSD-Security branch source tree. # *default host=cvsup2.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_6_0 *default delete use-rel-suffix src-all -- Best regards, Chris There is always more dirty laundry then clean laundry. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to track 6.0 increments ?
On Mon, Dec 05, 2005 at 01:20:06AM +0800, ke.han wrote: I have installed 6.0 and would like to follow important changes before something labeled 6.1 comes out. What is the prescribed method for this? I don't want to follow current or stable (I don't think). I just want security fixes and other changes that might be termed 6.01 if there were such a thing. Create a cvsup-file with *default release=cvs tag=RELENG_6_0 This will only give you important security fixes. If there are fixes, you can find them on the FreeBSD homepage, under SECURITY ADVISORIES. If a advisory has come out, use cvsup to update the sources, and rebuild your kernel and userland as documented at the end of /usr/src/UPDATING under the heading 'To rebuild everything and install it on the current system. Note; you have to be in /usr/src to build world+kernel. Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt pgpGpKO4AIEb4.pgp Description: PGP signature
Re: how to track 6.0 increments ?
Roland Smith wrote: On Mon, Dec 05, 2005 at 01:20:06AM +0800, ke.han wrote: I have installed 6.0 and would like to follow important changes before something labeled 6.1 comes out. What is the prescribed method for this? I don't want to follow current or stable (I don't think). I just want security fixes and other changes that might be termed 6.01 if there were such a thing. Create a cvsup-file with *default release=cvs tag=RELENG_6_0 thanks...so now that I have sync'd my source incorrectly by using stable-supfile and standard-supfile, can I get things back to where I want just by sync'ing again with the RELENG_6_0 tag ?? thanks ke han This will only give you important security fixes. If there are fixes, you can find them on the FreeBSD homepage, under SECURITY ADVISORIES. If a advisory has come out, use cvsup to update the sources, and rebuild your kernel and userland as documented at the end of /usr/src/UPDATING under the heading 'To rebuild everything and install it on the current system. Note; you have to be in /usr/src to build world+kernel. Roland ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to track 6.0 increments ?
On Mon, Dec 05, 2005 at 01:39:34AM +0800, ke.han wrote: Roland Smith wrote: On Mon, Dec 05, 2005 at 01:20:06AM +0800, ke.han wrote: I have installed 6.0 and would like to follow important changes before something labeled 6.1 comes out. What is the prescribed method for this? I don't want to follow current or stable (I don't think). I just want security fixes and other changes that might be termed 6.01 if there were such a thing. Create a cvsup-file with *default release=cvs tag=RELENG_6_0 thanks...so now that I have sync'd my source incorrectly by using stable-supfile and standard-supfile, can I get things back to where I want just by sync'ing again with the RELENG_6_0 tag ?? Yes. Be sure to make good backups before you rebuild world+kernel, in case you screw it up. This goes especially for the settings in the files in /etc and /usr/local/etc. I tend to keep a copy of the files in those directories in my home directory under revision control, with an install script. So I can easily install my changed configuration files. Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt pgpYcgcdOiCBM.pgp Description: PGP signature
Re: how to track 6.0 increments ?
ke.han wrote: Roland Smith wrote: On Mon, Dec 05, 2005 at 01:20:06AM +0800, ke.han wrote: I have installed 6.0 and would like to follow important changes before something labeled 6.1 comes out. What is the prescribed method for this? I don't want to follow current or stable (I don't think). I just want security fixes and other changes that might be termed 6.01 if there were such a thing. Create a cvsup-file with *default release=cvs tag=RELENG_6_0 thanks...so now that I have sync'd my source incorrectly by using stable-supfile and standard-supfile, can I get things back to where I want just by sync'ing again with the RELENG_6_0 tag ?? thanks ke han why incorrectly? those files come as cvsup examples. and they're correct, you only need to specify your nearest mirror (*default host=) and if you want to follow the security branch, just change tag=RELENG_6 to tag=RELENG_6_0 martin This will only give you important security fixes. If there are fixes, you can find them on the FreeBSD homepage, under SECURITY ADVISORIES. If a advisory has come out, use cvsup to update the sources, and rebuild your kernel and userland as documented at the end of /usr/src/UPDATING under the heading 'To rebuild everything and install it on the current system. Note; you have to be in /usr/src to build world+kernel. Roland ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
