Re: Best upgrade strategy
jason henson <[EMAIL PROTECTED]> writes: > Glyn Millington wrote: > >>Greetings! >> >>I'm a newcomer to FreeBSD, an immigrant from the wonderful world of >>Slackware Linux. Finished installing on Sunday! >> >>I wanted to make sure the system was up to date with regard to security >>fixes etc so used cvsup to upgrade source and re-built the kernel - it >>all went like a dream - what a system!! What documentation!! >> >> > Hold on, just the kernel or the kernel and world. You have to keep > these in sync on FreeBSD. > Just checking because I hear you can just upgrade the linux kernel to > your hearts content without messing with the other stuff on the system. Bless you, no, I did the lot! Buildworld, installworld, the works as described in the handbook. And was staggered by how straightforward it was, to be honest. No, my question was about swapping the target for cvsup at the point when 5.4 becomes a "production release" - can I then simply track 5.4 for security releases etc or will that cause complications with a system that has tracked 5-stable for the few days it has been in existence. It sems form the various replies I've had that there should be no problem. Many thanks Glyn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Best upgrade strategy
Glyn Millington wrote: Greetings! I'm a newcomer to FreeBSD, an immigrant from the wonderful world of Slackware Linux. Finished installing on Sunday! I wanted to make sure the system was up to date with regard to security fixes etc so used cvsup to upgrade source and re-built the kernel - it all went like a dream - what a system!! What documentation!! Hold on, just the kernel or the kernel and world. You have to keep these in sync on FreeBSD. Just checking because I hear you can just upgrade the linux kernel to your hearts content without messing with the other stuff on the system. Enough rapture! Here's the question Having installed 5.3 from cd, I performed the above upgrade once and found that I was at version 6 Current! Back to the drawing board and started again with the following line in my cvsup file *default release=cvs tag=RELENG_5 Better - I only find myself with a pre-release 5.4 :-) That is fine, but at the point when 5.4 becomes the production release, I would like simply to track that for security fixes etc rather than follow the stable developement branch. Can I acheive that simply by putting *default release=cvs tag=RELENG_5_4 into my cvsup file, at the right time -ie as soon as 5.4 becomes a production release? ? Or will there be such complications that it would be best to perform yet another install (which is smooth but slow on my set-up). Thanks in advance Glyn ___ 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]"
Re: Best upgrade strategy
"Andrew P." <[EMAIL PROTECTED]> writes: > Glyn Millington wrote: >> That is fine, but at the point when 5.4 becomes the production release, I >> would like simply to track that for security fixes etc rather than follow >> the stable developement branch. >> Can I acheive that simply by putting >> *default release=cvs tag=RELENG_5_4 >> into my cvsup file, at the right time -ie as soon as 5.4 becomes >> a production release? ? Or will there be such >> complications that it would be best to perform yet another install (which >> is smooth but slow on my set-up). > > > Yes, you can use RELENG_5_4 tag to track > security fixes when 5.4 is released. It > goes smoothly most of the times, some > people even managed to upgrade from > 4.x to 5.x without reinstalling (ok, > _that_ wasn't smooth). Just look through > release notes, src/UPDATING and so on, > and use mergemaster carefully. Thanks Andrew - just needed to check this with those who know, to make sure I had not miscontrued the Handbook! atb Glyn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Best upgrade strategy
Glyn Millington wrote: That is fine, but at the point when 5.4 becomes the production release, I would like simply to track that for security fixes etc rather than follow the stable developement branch. Can I acheive that simply by putting *default release=cvs tag=RELENG_5_4 into my cvsup file, at the right time -ie as soon as 5.4 becomes a production release? ? Or will there be such complications that it would be best to perform yet another install (which is smooth but slow on my set-up). Yes, you can use RELENG_5_4 tag to track security fixes when 5.4 is released. It goes smoothly most of the times, some people even managed to upgrade from 4.x to 5.x without reinstalling (ok, _that_ wasn't smooth). Just look through release notes, src/UPDATING and so on, and use mergemaster carefully. Best wishes, Andrew P. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Best upgrade strategy
Greetings! I'm a newcomer to FreeBSD, an immigrant from the wonderful world of Slackware Linux. Finished installing on Sunday! I wanted to make sure the system was up to date with regard to security fixes etc so used cvsup to upgrade source and re-built the kernel - it all went like a dream - what a system!! What documentation!! Enough rapture! Here's the question Having installed 5.3 from cd, I performed the above upgrade once and found that I was at version 6 Current! Back to the drawing board and started again with the following line in my cvsup file *default release=cvs tag=RELENG_5 Better - I only find myself with a pre-release 5.4 :-) That is fine, but at the point when 5.4 becomes the production release, I would like simply to track that for security fixes etc rather than follow the stable developement branch. Can I acheive that simply by putting *default release=cvs tag=RELENG_5_4 into my cvsup file, at the right time -ie as soon as 5.4 becomes a production release? ? Or will there be such complications that it would be best to perform yet another install (which is smooth but slow on my set-up). Thanks in advance Glyn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
