The first of the Release Candidate builds of 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.
The 9.0-RELEASE cycle will be tracked here:
http://wiki.freebsd.org/Releng/9.0-TODO
Wrapping up RC1 was a bit delayed due to a bug found during the initial
testing of the RC1 images and a few glitches that came up as part of
making FreeBSD-Update available. We'll update the schedule soon.
NOTE: The location of the FTP install tree and ISOs is the same as it
had been for BETA2/BETA3, 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", 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/stable/9/". 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, or 9.0-BETA[123] 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-RC1. During this process
freebsd-update will ask for help in merging configuration files.
# freebsd-update upgrade -r 9.0-RC1
Due to changes in the way that FreeBSD is packaged on the release media, two
complications may arise in this process:
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-RC1:
# shutdown -r now
Checksums:
MD5 (FreeBSD-9.0-RC1-amd64-bootonly.iso) = 625d64340f952de2fca7102dac7f180f
MD5 (FreeBSD-9.0-RC1-amd64-dvd1.iso) = 5cccbb21a8448e54e4d631619b5f4861
MD5 (FreeBSD-9.0-RC1-amd64-memstick.img) = 07f83c8015a1907953b826b0c65069f0
MD5 (FreeBSD-9.0-RC1-i386-bootonly.iso) = 59f1c057eaa6bff6c69d8e411adeb13c
MD5 (FreeBSD-9.0-RC1-i386-dvd1.iso) = 0f168bcfa832282cf6e3914ffc5a5014
MD5 (FreeBSD-9.0-RC1-i386-memstick.img) = ccbc2db07a19b3e77e75958cd7470643
MD5 (FreeBSD-9.0-RC1-ia64-bootonly.iso) = e2e80ffae14950d0437c067e7c6553f1
MD5 (FreeBSD-9.0-RC1-ia64-memstick) = 997bb23954682d503ba10fc3f1a2d624
MD5 (FreeBSD-9.0-RC1-ia64-release.iso) = 3703dc72d55fb9c66450e800b123cffe
MD5 (FreeBSD-9.0-RC1-powerpc-bootonly.iso) = 2a651f4af37af85e49b6a8fcaa42a77f
MD5 (FreeBSD-9.0-RC1-powerpc-memstick) = a2c33dfab3f98b0d83db382d73cdd87a
MD5 (FreeBSD-9.0-RC1-powerpc-release.iso) = af4afc51149dcd61488b44ecbbf96fc5
MD5 (FreeBSD-9.0-RC1-powerpc64-bootonly.iso) = 96f2bce40f2974be55578bf9cc7318a1
MD5 (FreeBSD-9.0-RC1-powerpc64-memstick) = e4647934091f4c72b4df331eb1134eb3
MD5 (FreeBSD-9.0-RC1-powerpc64-release.iso) = b6989f2e4285b7479a72f4503dc420cf
MD5 (FreeBSD-9.0-RC1-sparc64-bootonly.iso) = df7146d2497a16b502e92e35ae24921e
MD5 (FreeBSD-9.0-RC1-sparc64-dvd1.iso) = 6cd56a20a6d907525077424c55a163a4
SHA256 (FreeBSD-9.0-RC1-amd64-bootonly.iso) =
ec44fefd1c54fb724079b83951cfe721404ecb76a4a861a2ef4c2a1b63b88aff
SHA256 (FreeBSD-9.0-RC1-amd64-dvd1.iso) =
6558689957ce2a48f3aa235ab11cd4613db7afe11f102b0ae5d566b22e30c132
SHA256 (FreeBSD-9.0-RC1-amd64-memstick.img) =
c04abe37f83c8ed07e3645cbaff8cfa21d223f94cda059a053bd1a469c6b753c
SHA256 (FreeBSD-9.0-RC1-i386-bootonly.iso) =
9e720cb8306171b137ae50d3887abf09f90fab6f953b39a9f552c87c3221d441
SHA256 (FreeBSD-9.0-RC1-i386-dvd1.iso) =
488599d5328b20278e90d5489b8d2afd49bf466a5d7a31694f3c0eb66d97c6f1
SHA256 (FreeBSD-9.0-RC1-i386-memstick.img) =
9eadded30ee684840bb6ead60f98d8d8e455e690148491b55dec9b657ab7ac10
SHA256 (FreeBSD-9.0-RC1-ia64-bootonly.iso) =
b4b33ecc30555b532be4ebcc3a5f566189265066141b852a3a912ddc8e1aa203
SHA256 (FreeBSD-9.0-RC1-ia64-memstick) =
f437f5af4c8dd780d329bb90f5189c7bb1b270df1b05bff979e7fbcc7cf819d6
SHA256 (FreeBSD-9.0-RC1-ia64-release.iso) =
aaa21f0244d1238b11f5af267935c7cbea20f0d5fb393bef7534011ab7f017f1
SHA256 (FreeBSD-9.0-RC1-powerpc-bootonly.iso) =
5a45de1a72fd2c15f58c7306802533d48a5dee512b5e6f0377e859bf4a25200e
SHA256 (FreeBSD-9.0-RC1-powerpc-memstick) =
fe85b8232123a510468658380117e51a2ca3737e92cacb525717cefb73b9740c
SHA256 (FreeBSD-9.0-RC1-powerpc-release.iso) =
8024a84ccf4962fe8ec7e030421a476f96c410fe67c9c9b25935248304029682
SHA256 (FreeBSD-9.0-RC1-powerpc64-bootonly.iso) =
43e97f229ccf823378078348390b6b75b3ca5c95db107a48087d6a5fc3980e92
SHA256 (FreeBSD-9.0-RC1-powerpc64-memstick) =
7323eb46e90849bab53c3b158753b1824ae9e464c63ffe7bb33fe726c6a7c415
SHA256 (FreeBSD-9.0-RC1-powerpc64-release.iso) =
6c0643f2de33a04426d168dd23187a71c971d3e4bfd222eb32bdbaa65f2c0368
SHA256 (FreeBSD-9.0-RC1-sparc64-bootonly.iso) =
8664ed9a0282b80341c6e243643011c84b058f4c8450a5e6e2b3f99bd9df469c
SHA256 (FreeBSD-9.0-RC1-sparc64-dvd1.iso) =
5220f817e078024208b9ab3060518911c4e0ed0693575ca101a97608b73121af
--
Ken Smith
- From there to here, from here to | kensmith@buffalo.edu
there, funny things are everywhere. |
- Theodore 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/20111023/461953b1/attachment.pgp
On Sun, Oct 23, 2011 at 6:43 AM, Ken Smith <kensmith@buffalo.edu> wrote:> > The first of the Release Candidate builds of 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. > > The 9.0-RELEASE cycle will be tracked here: > > ? ? ? ?http://wiki.freebsd.org/Releng/9.0-TODOIs that http://wiki.freebsd.org/Releng/9.0TODO or a new page will be created?> > Wrapping up RC1 was a bit delayed due to a bug found during the initial > testing of the RC1 images and a few glitches that came up as part of > making FreeBSD-Update available. ?We'll update the schedule soon. > > NOTE: The location of the FTP install tree and ISOs is the same as it > had been for BETA2/BETA3, 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", 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/stable/9/". ?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, or 9.0-BETA[123] 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-RC1. ?During this process > freebsd-update will ask for help in merging configuration files. > > # freebsd-update upgrade -r 9.0-RC1 > > Due to changes in the way that FreeBSD is packaged on the release media, two > complications may arise in this process: > 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-RC1: > > # shutdown -r now > > Checksums: > > MD5 (FreeBSD-9.0-RC1-amd64-bootonly.iso) = 625d64340f952de2fca7102dac7f180f > MD5 (FreeBSD-9.0-RC1-amd64-dvd1.iso) = 5cccbb21a8448e54e4d631619b5f4861 > MD5 (FreeBSD-9.0-RC1-amd64-memstick.img) = 07f83c8015a1907953b826b0c65069f0 > > MD5 (FreeBSD-9.0-RC1-i386-bootonly.iso) = 59f1c057eaa6bff6c69d8e411adeb13c > MD5 (FreeBSD-9.0-RC1-i386-dvd1.iso) = 0f168bcfa832282cf6e3914ffc5a5014 > MD5 (FreeBSD-9.0-RC1-i386-memstick.img) = ccbc2db07a19b3e77e75958cd7470643 > > MD5 (FreeBSD-9.0-RC1-ia64-bootonly.iso) = e2e80ffae14950d0437c067e7c6553f1 > MD5 (FreeBSD-9.0-RC1-ia64-memstick) = 997bb23954682d503ba10fc3f1a2d624 > MD5 (FreeBSD-9.0-RC1-ia64-release.iso) = 3703dc72d55fb9c66450e800b123cffe > > MD5 (FreeBSD-9.0-RC1-powerpc-bootonly.iso) = 2a651f4af37af85e49b6a8fcaa42a77f > MD5 (FreeBSD-9.0-RC1-powerpc-memstick) = a2c33dfab3f98b0d83db382d73cdd87a > MD5 (FreeBSD-9.0-RC1-powerpc-release.iso) = af4afc51149dcd61488b44ecbbf96fc5 > > MD5 (FreeBSD-9.0-RC1-powerpc64-bootonly.iso) = 96f2bce40f2974be55578bf9cc7318a1 > MD5 (FreeBSD-9.0-RC1-powerpc64-memstick) = e4647934091f4c72b4df331eb1134eb3 > MD5 (FreeBSD-9.0-RC1-powerpc64-release.iso) = b6989f2e4285b7479a72f4503dc420cf > > MD5 (FreeBSD-9.0-RC1-sparc64-bootonly.iso) = df7146d2497a16b502e92e35ae24921e > MD5 (FreeBSD-9.0-RC1-sparc64-dvd1.iso) = 6cd56a20a6d907525077424c55a163a4 > > SHA256 (FreeBSD-9.0-RC1-amd64-bootonly.iso) = ec44fefd1c54fb724079b83951cfe721404ecb76a4a861a2ef4c2a1b63b88aff > SHA256 (FreeBSD-9.0-RC1-amd64-dvd1.iso) = 6558689957ce2a48f3aa235ab11cd4613db7afe11f102b0ae5d566b22e30c132 > SHA256 (FreeBSD-9.0-RC1-amd64-memstick.img) = c04abe37f83c8ed07e3645cbaff8cfa21d223f94cda059a053bd1a469c6b753c > > SHA256 (FreeBSD-9.0-RC1-i386-bootonly.iso) = 9e720cb8306171b137ae50d3887abf09f90fab6f953b39a9f552c87c3221d441 > SHA256 (FreeBSD-9.0-RC1-i386-dvd1.iso) = 488599d5328b20278e90d5489b8d2afd49bf466a5d7a31694f3c0eb66d97c6f1 > SHA256 (FreeBSD-9.0-RC1-i386-memstick.img) = 9eadded30ee684840bb6ead60f98d8d8e455e690148491b55dec9b657ab7ac10 > > SHA256 (FreeBSD-9.0-RC1-ia64-bootonly.iso) = b4b33ecc30555b532be4ebcc3a5f566189265066141b852a3a912ddc8e1aa203 > SHA256 (FreeBSD-9.0-RC1-ia64-memstick) = f437f5af4c8dd780d329bb90f5189c7bb1b270df1b05bff979e7fbcc7cf819d6 > SHA256 (FreeBSD-9.0-RC1-ia64-release.iso) = aaa21f0244d1238b11f5af267935c7cbea20f0d5fb393bef7534011ab7f017f1 > > SHA256 (FreeBSD-9.0-RC1-powerpc-bootonly.iso) = 5a45de1a72fd2c15f58c7306802533d48a5dee512b5e6f0377e859bf4a25200e > SHA256 (FreeBSD-9.0-RC1-powerpc-memstick) = fe85b8232123a510468658380117e51a2ca3737e92cacb525717cefb73b9740c > SHA256 (FreeBSD-9.0-RC1-powerpc-release.iso) = 8024a84ccf4962fe8ec7e030421a476f96c410fe67c9c9b25935248304029682 > > SHA256 (FreeBSD-9.0-RC1-powerpc64-bootonly.iso) = 43e97f229ccf823378078348390b6b75b3ca5c95db107a48087d6a5fc3980e92 > SHA256 (FreeBSD-9.0-RC1-powerpc64-memstick) = 7323eb46e90849bab53c3b158753b1824ae9e464c63ffe7bb33fe726c6a7c415 > SHA256 (FreeBSD-9.0-RC1-powerpc64-release.iso) = 6c0643f2de33a04426d168dd23187a71c971d3e4bfd222eb32bdbaa65f2c0368 > > SHA256 (FreeBSD-9.0-RC1-sparc64-bootonly.iso) = 8664ed9a0282b80341c6e243643011c84b058f4c8450a5e6e2b3f99bd9df469c > SHA256 (FreeBSD-9.0-RC1-sparc64-dvd1.iso) = 5220f817e078024208b9ab3060518911c4e0ed0693575ca101a97608b73121af > > -- > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Ken Smith > - From there to here, from here to ? ? ?| ? ? ? kensmith@buffalo.edu > ?there, funny things are everywhere. ? | > ? ? ? ? ? ? ? ? ? ? ?- Theodore Geisel | >
On 10/22/11, Ken Smith <kensmith@buffalo.edu> wrote:> > The first of the Release Candidate builds of the 9.0-RELEASE release > cycle is now available. Since this is the first release of a brandNew in RC1, with GENERIC: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=native -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mno-sse -mcmodel=kernel -mno-red-zone -mno-mmx -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/fs/devfs/devfs_devs.c cc1: warnings being treated as errors /usr/src/sys/fs/devfs/devfs_devs.c: In function 'devfs_free': /usr/src/sys/fs/devfs/devfs_devs.c:174: warning: implicit declaration of function 'devfs_free_cdp_inode' /usr/src/sys/fs/devfs/devfs_devs.c:174: warning: nested extern declaration of 'devfs_free_cdp_inode' [-Wnested-externs] /usr/src/sys/fs/devfs/devfs_devs.c: At top level: /usr/src/sys/fs/devfs/devfs_devs.c:689: warning: no previous prototype for 'devfs_alloc_cdp_inode' [-Wmissing-prototypes] /usr/src/sys/fs/devfs/devfs_devs.c:696: warning: no previous prototype for 'devfs_free_cdp_inode' [-Wmissing-prototypes] /usr/src/sys/fs/devfs/devfs_devs.c:696: warning: conflicting types for 'devfs_free_cdp_inode' /usr/src/sys/fs/devfs/devfs_devs.c:174: warning: previous implicit declaration of 'devfs_free_cdp_inode' was here *** Error code 1
On Sat, Oct 22, 2011 at 10:45 PM, Greg Miller <greglmiller@gmail.com> wrote:> On 10/22/11, Ken Smith <kensmith@buffalo.edu> wrote: >> >> The first of the Release Candidate builds of the 9.0-RELEASE release >> cycle is now available. ?Since this is the first release of a brand > > New in RC1, with GENERIC:Was r226041 MFCed properly? -Garrett
Ken Smith <kensmith@buffalo.edu> writes:> The first of the Release Candidate builds of 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. > > The 9.0-RELEASE cycle will be tracked here: > > http://wiki.freebsd.org/Releng/9.0-TODOIs anybody *EVER* going to update the official web page? http://www.freebsd.org/releases/9.0R/schedule.html is now almost 3 months out of date, and it is the web page that people will find when navigating from the main page. -- Carl Johnson carlj@peak.org
On Sun, Oct 23, 2011 at 7:43 AM, Ken Smith <kensmith@buffalo.edu> wrote:> > The 9.0-RELEASE cycle will be tracked here: > > ? ? ? ?http://wiki.freebsd.org/Releng/9.0-TODO >link error, need http://wiki.freebsd.org/Releng/9.0TODO still no actual information on this page. Branch status not actual.