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) = 35e667deaa7223e0829677c3762163d8 MD5 (FreeBSD-9.0-RC2-powerpc-memstick) = 01b06227124fc7f9ad224d0512940ea8 MD5 (FreeBSD-9.0-RC2-powerpc-release.iso) = 055e06744fa1b8c584cfda8be2352462 MD5 (FreeBSD-9.0-RC2-powerpc64-bootonly.iso) = 38d240e6cdfd5f986f0690ba1256eb0f MD5 (FreeBSD-9.0-RC2-powerpc64-memstick) = b820ed78bce87b69a04e9d473c63ecfc MD5 (FreeBSD-9.0-RC2-powerpc64-release.iso) = 44d550342db5090c1d0fb5f60705cb0c MD5 (FreeBSD-9.0-RC2-sparc64-bootonly.iso) = 7ffb3dc55bb02506cbc95d0f7a94edab MD5 (FreeBSD-9.0-RC2-sparc64-dvd1.iso) = fe4b87eff3f3cde33c2908b071e45c0f SHA256 (FreeBSD-9.0-RC2-amd64-bootonly.iso) = 81daa3aa92b8eb6f1bf0c6196c1cae138c881fe53dce22b9fbf2f19a8cf30551 SHA256 (FreeBSD-9.0-RC2-amd64-memstick.img) = fda9025bb8c3ee8c3a4f8db3a0144c669408707eab3dc7c5e2070342e979e33e SHA256 (FreeBSD-9.0-RC2-amd64-dvd1.iso) = d7071da7cf440f79a7368f8a8b26ba9b6e18dcb3785aec83df866ddf576ef418 SHA256 (FreeBSD-9.0-RC2-i386-bootonly.iso) = 200ac2b9e950548c873cba93f3b3c669e529720522897220d6b6dd438f806490 SHA256 (FreeBSD-9.0-RC2-i386-memstick.img) = 7888f9ed58da415a7356810c07768587c6d2b5d4734f9ca47c92bfc10dab1b0a SHA256 (FreeBSD-9.0-RC2-i386-dvd1.iso) = 41a1e12496ba5a44dba4c6e6cfb27c6dd5f49fb62378e05c1a61909a4f29d06c SHA256 (FreeBSD-9.0-RC2-ia64-bootonly.iso) = 059a05b4e779f94cb221fcb7ce261db13e45092510b1fbeac7e17d5f2f6c7c36 SHA256 (FreeBSD-9.0-RC2-ia64-memstick) = 3e9985eb02c0f8cd8e5d84356048a019c98d9628e5836ca777426a3abec3f83f SHA256 (FreeBSD-9.0-RC2-ia64-release.iso) = 49524a249f72ad6a8a21ba1ad0d1e738ddc09342c7086cf1a20c08ad06885539 SHA256 (FreeBSD-9.0-RC2-powerpc-bootonly.iso) = 3a584930ecfd772defa3d86879c62199b7a15f6e502bf4809a04a3fc8d10e10e SHA256 (FreeBSD-9.0-RC2-powerpc-memstick) = 06b2985c278362801e2c454d72a3ae0f873ad2e050a058e76f7b6da84f2d4812 SHA256 (FreeBSD-9.0-RC2-powerpc-release.iso) = 0402cca90eb4123fbf1d5dc46d9a36ba08b38c0e7b5e83a3a5c0cd7cd1095124 SHA256 (FreeBSD-9.0-RC2-powerpc64-bootonly.iso) = 7510745f1fbd3f1a4e1d7c9d0fed39f8ea3e2dc37de029e931f06856729e5183 SHA256 (FreeBSD-9.0-RC2-powerpc64-memstick) = a29bf56f7461be20b0fd15e6ff7ed08ea0a2baabcbf04430d337893113d19a68 SHA256 (FreeBSD-9.0-RC2-powerpc64-release.iso) = 54b1e14798839ced94863a5fb95b08c20a46474854effc022602cad018789b98 SHA256 (FreeBSD-9.0-RC2-sparc64-bootonly.iso) = 9e08825e9549d330384817296d832f9e00288357ccd1b2d6cce99d0f656b096b SHA256 (FreeBSD-9.0-RC2-sparc64-dvd1.iso) = f53810ff78e4015833e0ac9e81865c1abd93c622607d14aa2a74b918d2bc469c -- Ken Smith - From there to here, from here to | kensmith at buffalo.edu there, funny things are everywhere. | - Theodor Geisel | -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20111117/80b325f8/attachment.pgp