Re: FreeBSD 9.0-RC2 Available...
On 18/11/2011 10:53, Thomas Mueller wrote: *default release=cvs tag=RELENG_9 Am I screwed, am I OK, or do I simply have to rerun csup with RELENG_9_0 instead of RELENG_9 ? Not screwed, but you'll be running 9.0-PRERELEASE rather than 9.0-RC2. If you want to switch to the 9.0-RELEASE branch, change the tag to RELENG_9_0 and cvsup again. Then redo the whole buildworld dance. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. Good to know I'm not screwed, that I can recover simply by rerunning csup, this time with RELENG_9_0 instead of RELENG_9. But I hadn't got to making buildworld yet on this update. Possibly there may be no serious difference between 9.0-PRERELEASE and 9.0-RC2 at this stage. As for the difference between STABLE and RELEASE, I believe STABLE is a sort of POSTRELEASE, like the post-release update to NetBSD 5.1 that permitted access to Linux ext2fs partition that didn't work previously with NetBSD; inode was 256 bytes. I think FreeBSD 9-STABLE (RELENG_9) would be development work toward FreeBSD 9.1, after FreeBSD 9.0 is released, but stabler than current/head. I looked in /usr/src/sys/conf/newvars.sh and indeed found that I had 9.0-PRERELEASE rather than RC2. Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 9.0-RC2 Available...
If you would like to use csup/cvsup mechanisms to access the source tree the branch tag to use is now RELENG_9_0, if you use . (head) you will get 10-CURRENT. If you would like to access the source tree via SVN it is svn://svn.freebsd.org/base/releng/9.0/. We still have the nit that the creation of a new SVN branch winds up causing what looks like a check-in of the entire tree in CVS (a side-effect of the svn2cvs exporter) so mergemaster -F is your friend if you are using csup/cvsup. About a couple days before seeing this message, or the message on the FreeBSD web site, but after seeing RC2 on the ftp.freebsd.org server, I already ran csup with *default release=cvs tag=RELENG_9 Am I screwed, am I OK, or do I simply have to rerun csup with RELENG_9_0 instead of RELENG_9 ? Again, I can't find that file (needle in the haystack) in /usr/src tree that shows version number such as RC2. Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 9.0-RC2 Available...
On Fri, Nov 18, 2011 at 10:53:38AM +, Thomas Mueller wrote: If you would like to use csup/cvsup mechanisms to access the source tree the branch tag to use is now RELENG_9_0, if you use . (head) you will get 10-CURRENT. If you would like to access the source tree via SVN it is svn://svn.freebsd.org/base/releng/9.0/. We still have the nit that the creation of a new SVN branch winds up causing what looks like a check-in of the entire tree in CVS (a side-effect of the svn2cvs exporter) so mergemaster -F is your friend if you are using csup/cvsup. About a couple days before seeing this message, or the message on the FreeBSD web site, but after seeing RC2 on the ftp.freebsd.org server, I already ran csup with *default release=cvs tag=RELENG_9 Am I screwed, am I OK, or do I simply have to rerun csup with RELENG_9_0 instead of RELENG_9 ? Again, I can't find that file (needle in the haystack) in /usr/src tree that shows version number such as RC2. Take a look at /sys/conf/newvers.sh pgpdhDwedUXHg.pgp Description: PGP signature
Re: FreeBSD 9.0-RC2 Available...
On 18/11/2011 10:53, Thomas Mueller wrote: *default release=cvs tag=RELENG_9 Am I screwed, am I OK, or do I simply have to rerun csup with RELENG_9_0 instead of RELENG_9 ? Not screwed, but you'll be running 9.0-PRERELEASE rather than 9.0-RC2. If you want to switch to the 9.0-RELEASE branch, change the tag to RELENG_9_0 and cvsup again. Then redo the whole buildworld dance. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: FreeBSD 9.0-RC2 Available...
On 18/11/2011 12:53, Thomas Mueller wrote: If you would like to use csup/cvsup mechanisms to access the source tree the branch tag to use is now RELENG_9_0, if you use . (head) you will get 10-CURRENT. If you would like to access the source tree via SVN it is svn://svn.freebsd.org/base/releng/9.0/. We still have the nit that the creation of a new SVN branch winds up causing what looks like a check-in of the entire tree in CVS (a side-effect of the svn2cvs exporter) so mergemaster -F is your friend if you are using csup/cvsup. About a couple days before seeing this message, or the message on the FreeBSD web site, but after seeing RC2 on the ftp.freebsd.org server, I already ran csup with *default release=cvs tag=RELENG_9 Am I screwed, am I OK, or do I simply have to rerun csup with RELENG_9_0 instead of RELENG_9 ? RELENG_9 (cvs) = stable/9 (svn) = 9.N-STABLE (newvers.sh, `uname -r`) RELENG_9_0 (cvs) = releng/9.0 (svn) = 9.0-RELEASE (newvers.sh, uname) In short, if you want to use the 9.0-RELEASE (when it finally gets ready), then you need to switch to RELENG_9_0. If you prefer using -STABLE for your systems, then you're OK with RELENG_9. In case you don't know or are not quite sure about the differences between -RELEASE and -STABLE, I'd recommend switching to RELENG_9_0. Again, I can't find that file (needle in the haystack) in /usr/src tree that shows version number such as RC2. This has already been answered, but just a quick note. If you've recently updated your sources using the RELENG_9 tag, you'll most likely see the version in newvers.sh as: REVISION=9.0 BRANCH=PRERELEASE If you switch to RELENG_9_0 and update your sources again, you should see the familiar: REVISION=9.0 BRANCH=RC2 HTH, Luchesar -- i.dea.is/luchesar ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 9.0-RC2 Available...
On Fri, Nov 18, 2011 at 1:35 PM, Luchesar V. ILIEV luchesar.il...@gmail.com wrote: On 18/11/2011 12:53, Thomas Mueller wrote: If you would like to use csup/cvsup mechanisms to access the source tree the branch tag to use is now RELENG_9_0, if you use . (head) you will get 10-CURRENT. If you would like to access the source tree via SVN it is svn://svn.freebsd.org/base/releng/9.0/. We still have the nit that the creation of a new SVN branch winds up causing what looks like a check-in of the entire tree in CVS (a side-effect of the svn2cvs exporter) so mergemaster -F is your friend if you are using csup/cvsup. About a couple days before seeing this message, or the message on the FreeBSD web site, but after seeing RC2 on the ftp.freebsd.org server, I already ran csup with *default release=cvs tag=RELENG_9 Am I screwed, am I OK, or do I simply have to rerun csup with RELENG_9_0 instead of RELENG_9 ? RELENG_9 (cvs) = stable/9 (svn) = 9.N-STABLE (newvers.sh, `uname -r`) RELENG_9_0 (cvs) = releng/9.0 (svn) = 9.0-RELEASE (newvers.sh, uname) In short, if you want to use the 9.0-RELEASE (when it finally gets ready), then you need to switch to RELENG_9_0. If you prefer using -STABLE for your systems, then you're OK with RELENG_9. In case you don't know or are not quite sure about the differences between -RELEASE and -STABLE, I'd recommend switching to RELENG_9_0. Again, I can't find that file (needle in the haystack) in /usr/src tree that shows version number such as RC2. This has already been answered, but just a quick note. If you've recently updated your sources using the RELENG_9 tag, you'll most likely see the version in newvers.sh as: REVISION=9.0 BRANCH=PRERELEASE If you switch to RELENG_9_0 and update your sources again, you should see the familiar: REVISION=9.0 BRANCH=RC2 HTH, Luchesar -- i.dea.is/luchesar ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Correct me if I am wrong but up until 9.0 is released there isn't any practical difference between RELENG_9 RELENG_9_0 -- George Kontostanos Aicom telecoms ltd http://www.barebsd.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 9.0-RC2 Available...
On 18/11/2011 18:21, George Kontostanos wrote: On Fri, Nov 18, 2011 at 1:35 PM, Luchesar V. ILIEV luchesar.il...@gmail.com wrote: On 18/11/2011 12:53, Thomas Mueller wrote: If you would like to use csup/cvsup mechanisms to access the source tree the branch tag to use is now RELENG_9_0, if you use . (head) you will get 10-CURRENT. If you would like to access the source tree via SVN it is svn://svn.freebsd.org/base/releng/9.0/. We still have the nit that the creation of a new SVN branch winds up causing what looks like a check-in of the entire tree in CVS (a side-effect of the svn2cvs exporter) so mergemaster -F is your friend if you are using csup/cvsup. About a couple days before seeing this message, or the message on the FreeBSD web site, but after seeing RC2 on the ftp.freebsd.org server, I already ran csup with *default release=cvs tag=RELENG_9 Am I screwed, am I OK, or do I simply have to rerun csup with RELENG_9_0 instead of RELENG_9 ? RELENG_9 (cvs) = stable/9 (svn) = 9.N-STABLE (newvers.sh, `uname -r`) RELENG_9_0 (cvs) = releng/9.0 (svn) = 9.0-RELEASE (newvers.sh, uname) In short, if you want to use the 9.0-RELEASE (when it finally gets ready), then you need to switch to RELENG_9_0. If you prefer using -STABLE for your systems, then you're OK with RELENG_9. In case you don't know or are not quite sure about the differences between -RELEASE and -STABLE, I'd recommend switching to RELENG_9_0. Again, I can't find that file (needle in the haystack) in /usr/src tree that shows version number such as RC2. This has already been answered, but just a quick note. If you've recently updated your sources using the RELENG_9 tag, you'll most likely see the version in newvers.sh as: REVISION=9.0 BRANCH=PRERELEASE If you switch to RELENG_9_0 and update your sources again, you should see the familiar: REVISION=9.0 BRANCH=RC2 HTH, Luchesar -- i.dea.is/luchesar ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Correct me if I am wrong but up until 9.0 is released there isn't any practical difference between RELENG_9 RELENG_9_0 Yes, but it's never a nice feeling to realize you've taken the wrong train only when you see it going not quite your way, isn't it? ;) Cheers, Luchesar ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
FreeBSD 9.0-RC2 Available...
The second of the Release Candidate builds for the 9.0-RELEASE release cycle is now available. Since this is the first release of a brand new branch I cross-post the announcements on both -current and -stable. But just so you know most of the developers active in head and stable/9 pay more attention to the -current mailing list. If you notice problems you can report them through the normal Gnats PR system or on the -current mailing list. At the current plans are for one more RC build, which will be followed by the release. The 9.0-RELEASE cycle will be tracked here: http://wiki.freebsd.org/Releng/9.0TODO NOTE: The location of the FTP install tree and ISOs is the same as it had been for BETA2/BETA3/RC1, though we are still deciding if this will be the layout we switch to for the release. ISO images for the following architectures are available, with pathnames given relative to the top-level of the FTP site: amd64: .../releases/amd64/amd64/ISO-IMAGES/9.0/ i386: .../releases/i386/i386/ISO-IMAGES/9.0/ ia64: .../releases/ia64/ia64/ISO-IMAGES/9.0/ powerpc: .../releases/powerpc/powerpc/ISO-IMAGES/9.0/ powerpc64: .../releases/powerpc/powerpc64/ISO-IMAGES/9.0/ sparc64: .../releases/sparc64/sparc64/ISO-IMAGES/9.0/ MD5/SHA256 checksums are tacked on below. If you would like to use csup/cvsup mechanisms to access the source tree the branch tag to use is now RELENG_9_0, if you use . (head) you will get 10-CURRENT. If you would like to access the source tree via SVN it is svn://svn.freebsd.org/base/releng/9.0/. We still have the nit that the creation of a new SVN branch winds up causing what looks like a check-in of the entire tree in CVS (a side-effect of the svn2cvs exporter) so mergemaster -F is your friend if you are using csup/cvsup. FreeBSD Update -- The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.[34]-RELEASE, 8.[12]-RELEASE, 9.0-BETA[123], or 9.0-RC1 can upgrade as follows: First, a minor change must be made to the freebsd-update code in order for it to accept file names appearing in FreeBSD 9.0 which contain the '%' and '@' characters; without this change, freebsd-update will error out with the message The update metadata is correctly signed, but failed an integrity check. # sed -i '' -e 's/=_/=%@_/' /usr/sbin/freebsd-update Now freebsd-update can fetch bits belonging to 9.0-RC2. During this process freebsd-update will ask for help in merging configuration files. # freebsd-update upgrade -r 9.0-RC2 Due to changes in the way that FreeBSD is packaged on the release media, two complications may arise in this process if upgrading from FreeBSD 7.x or 8.x: 1. The FreeBSD kernel, which previously could appear in either /boot/kernel or /boot/GENERIC, now only appears as /boot/kernel. As a result, any kernel appearing in /boot/GENERIC will be deleted. Please carefully read the output printed by freebsd-update and confirm that an updated kernel will be placed into /boot/kernel before proceeding beyond this point. 2. The FreeBSD source tree in /usr/src (if present) will be deleted. (Normally freebsd-update will update a source tree, but in this case the changes in release packaging result in freebsd-update not recognizing that the source tree from the old release and the source tree from the new release correspond to the same part of FreeBSD.) # freebsd-update install The system must now be rebooted with the newly installed kernel before the non-kernel components are updated. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install At this point, users of systems being upgraded from FreeBSD 8.2-RELEASE or earlier will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries. After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries: # freebsd-update install Finally, reboot into 9.0-RC2: # shutdown -r now Checksums: MD5 (FreeBSD-9.0-RC2-amd64-bootonly.iso) = 0165f0a2a1141a4c69413ec0c0b7d754 MD5 (FreeBSD-9.0-RC2-amd64-memstick.img) = 84713f2f556cdd58aa18e36093525e6c MD5 (FreeBSD-9.0-RC2-amd64-dvd1.iso) = 59792b2012e6feff6981d3cf58c0b901 MD5 (FreeBSD-9.0-RC2-i386-bootonly.iso) = ed3e7b8ac2fdadd2c41c0d5c8b26943c MD5 (FreeBSD-9.0-RC2-i386-memstick.img) = f396728fbd72c61078a7f9511b0c71ff MD5 (FreeBSD-9.0-RC2-i386-dvd1.iso) = cacc9962fa80a6b9a5067c907f127e8b MD5 (FreeBSD-9.0-RC2-ia64-bootonly.iso) = faaf6f0c529b8ec59b9d4252ae666dc7 MD5 (FreeBSD-9.0-RC2-ia64-memstick) = b937883e7634334bef1ddf3eb1e06ffb MD5 (FreeBSD-9.0-RC2-ia64-release.iso) = c1f5623734132ea80a9fa2298262884c MD5 (FreeBSD-9.0-RC2-powerpc-bootonly.iso) =
