The first of the Release Candidates for the FreeBSD 8.0 release cycle is
now available. How many RC's we have will depend on how well 8.0-RC1
does. At the moment only one more RC is on the schedule but odds are
fairly high we will wind up inserting at least one more RC. Between
BETA4 and RC1 a lot of work has gone into IPv6 issues as well as many
other issues that have been brought up from the public testing. And a
patch set was committed by the people who handle porting ZFS to FreeBSD
that they felt makes ZFS production-ready.
Details about the current target schedule along with much more detail
about the current status of the release is available here:
http://wiki.freebsd.org/8.0TODO
There are two known problems with 8.0-RC1. One known issue with the
8.0-RC1 build was discovered after the builds got started so is not part
of the ISO images or FreeBSD-Update builds. The issue is that local
IPv6 link-local addresses are not reachable. A fix for it has been
committed to RELENG_8 so if you install from the 8.0-RC1 media or update
using FreeBSD-Update you will then need to update using csup/cvsup
mechanisms if you need that fix for your environment. It should only
impact people using IPv6.
The other known issue is that the flowtable may direct packets to the
wrong interface under certain routing conditions. We feel confident that
this bug will be fixed so the flowtable is enabled in RC1 to maximize
testing. If you experience routing problems, please temporarily disable
the flowtable using the sysctl <XXXX>=0 and report the results to the
freebsd-current@ mailing list. If we are unable to resolve this issue by
RC2, we will disable the flowtable in 8.0-RELEASE.
If you notice problems you can report them through the normal Gnats PR
system or on the freebsd-current mailing list. I do cross-post
announcements to freebsd-stable because this particular release is
"about to become a stable branch" but when it comes to watching for
issues related to the release most of the developers pay more attention
to the freebsd-current list.
ISO images for all supported architectures are available on the FTP
sites, and a "memory stick" image is available for amd64/i386
architectures. For amd64/i386 architectures the cdrom and memstick
images include the documentation packages this time but no other
packages. The DVD image includes a rough pass at what packages will be
available on the official release media but is subject to change between
now and release. For sparc64 the DVD image has the set of packages that
currently build for sparc64, which is a sub-set of the set provided for
amd64/i386. The sparc64 disc1 does not have any packages on it because
I noticed a little too late that adding the doc packages to disc1 caused
it to overflow the target size. For 8.0-RC2 sparc64 will have the
livefs bits split out to a separate image (which is the way all the
other architectures have been for a while now) and the doc packages will
be provided on disc1. None of the other images include packages.
If you are using csup/cvsup methods to update an older system the branch
tag to use is RELENG_8.
The freebsd-update(8) utility supports binary upgrades of i386 and amd64
systems running earlier FreeBSD releases. Systems running 7.0-RELEASE,
7.1-RELEASE, 7.2-RELEASE, 8.0-BETA1, 8.0-BETA2, 8.0-BETA3, or 8.0-BETA4
can upgrade as follows:
# freebsd-update upgrade -r 8.0-RC1
During this process, FreeBSD Update may ask the user to help by merging
some configuration files or by confirming that the automatically
performed merging was done correctly. Systems running 8.0-BETA3 may
print the warning
INDEX-OLD.all: Invalid arguments
when downloading updates; this warning is a harmless bug (fixed in
8.0-BETA4) and can be safely ignored.
# freebsd-update install
The system must be rebooted with the newly installed kernel before continuing.
# 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.0-BETA2 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. See:
http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html
for mode details. 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 8.0-RC1:
# shutdown -r now
MD5/SHA256 checksums for the image files:
MD5 (8.0-RC1-amd64-bootonly.iso) = a84d43c8adaba3fee9a618098668154e
MD5 (8.0-RC1-amd64-disc1.iso) = fb4f75c74144239b4994dc3ad040af33
MD5 (8.0-RC1-amd64-dvd1.iso) = 5da3097634fbe049dd01ad4127d0f396
MD5 (8.0-RC1-amd64-livefs.iso) = 43a483ea73cbbe80f0ef068502594363
MD5 (8.0-RC1-amd64-memstick.img) = 9b1ffcab33ceed4dcdf1a0f3d862f811
MD5 (8.0-RC1-i386-bootonly.iso) = b569d950d6806c7c88a15d857bef6a02
MD5 (8.0-RC1-i386-disc1.iso) = 1cfecd1489b8be4a6d06040b07af941b
MD5 (8.0-RC1-i386-dvd1.iso) = 474b54e73a04a2f573b8a26ad00e3077
MD5 (8.0-RC1-i386-livefs.iso) = 7e5c3390c9f1e7915b9f229eb95f7e70
MD5 (8.0-RC1-i386-memstick.img) = 532736e255f069f7f891d6ed4f14970e
MD5 (8.0-RC1-ia64-bootonly.iso) = f53c920e46d3ceeb755617b2de20507a
MD5 (8.0-RC1-ia64-disc1.iso) = 504d3828b919563a83d7232d9a3a952b
MD5 (8.0-RC1-ia64-disc2.iso) = 5f22a63a89bff893038b32c0c53bf2eb
MD5 (8.0-RC1-ia64-disc3.iso) = bf17e84e9dfa62a6ce131e07bc701478
MD5 (8.0-RC1-ia64-dvd1.iso) = b8cf5cc2feab96c98da12b6fb1623136
MD5 (8.0-RC1-ia64-livefs.iso) = 2a83a1b32cfeb9a95f8ccc5e4cf36918
MD5 (8.0-RC1-pc98-bootonly.iso) = 60603f538db73c264ad7271da044e185
MD5 (8.0-RC1-pc98-disc1.iso) = 7c00a58b4b8f3e94b25a4539116542bd
MD5 (8.0-RC1-pc98-livefs.iso) = aa67b1f3d8246381764a4df867e23f67
MD5 (8.0-RC1-powerpc-bootonly.iso) = a498cafdb4118f2d33007c5f0cf6ca0d
MD5 (8.0-RC1-powerpc-disc1.iso) = 4448a906a36356c479623c8b4af7e685
MD5 (8.0-RC1-powerpc-disc2.iso) = bf9bf9e46da074a0787ca84da13251c8
MD5 (8.0-RC1-powerpc-disc3.iso) = 2f600348579d4adc87b2a32f565f3f03
MD5 (8.0-RC1-powerpc-livefs.iso) = 962f7d69cad7bb47e1cdfaf746b97f90
MD5 (8.0-RC1-sparc64-bootonly.iso) = 674724d0c2ddd997d86f91863c01ba20
MD5 (8.0-RC1-sparc64-disc1.iso) = 9e896ac68263ff816e3721b8b31e63bb
MD5 (8.0-RC1-sparc64-dvd1.iso) = 8451f6fee8523cd33e3e7e973922d2cf
SHA256 (8.0-RC1-amd64-bootonly.iso) =
0fcff1f76629c694be73133ad6ca5057a97a7030d824adb3a3a58bfe881528ab
SHA256 (8.0-RC1-amd64-disc1.iso) =
1b0246694012170ef83ce38395f4179c990d5689e1da2224a7cd2164770d1efb
SHA256 (8.0-RC1-amd64-dvd1.iso) =
63dec5385f549a22e6940a8d30d23be96dec0c27253550787107918631021bcc
SHA256 (8.0-RC1-amd64-livefs.iso) =
adda93a732168586272697d32824626898bee6c95ec2efc9e691e649489b99c2
SHA256 (8.0-RC1-amd64-memstick.img) =
d2d3f90d3fb3b11cb06734df3ff1eb8433e4184158c85d34c4bd41ba068e131c
SHA256 (8.0-RC1-i386-bootonly.iso) =
6b3f78fe556cb396cb1734fdcdfdd3619013b4318f94b1736349e641a0745dbb
SHA256 (8.0-RC1-i386-disc1.iso) =
06094f54d0b9141b571a8d22727a9c639a4ffb8a72dd05d12e995ef417eaaf37
SHA256 (8.0-RC1-i386-dvd1.iso) =
02009c487ce5a00f52e45d2ccefc5c7b47edea110d1922ff21fe05ee7b1c8cb3
SHA256 (8.0-RC1-i386-livefs.iso) =
abcc0c3d975df784eaa4840af15555fc25f610f8699619142185c77b396e00aa
SHA256 (8.0-RC1-i386-memstick.img) =
f6ed2716312b6fcdf4bea15e4290a122d34e569fda895fb8bdffa499eea6d9ce
SHA256 (8.0-RC1-ia64-bootonly.iso) =
c307cdfa5f98d84b367ac8ef939da6f42a2a0454c07ab0f7b7fe17b78c3f4c9e
SHA256 (8.0-RC1-ia64-disc1.iso) =
44612f9922e8ee2ca6453f9a54b81c01bf351486580fa7cc9cd031b2f0b132c6
SHA256 (8.0-RC1-ia64-disc2.iso) =
01eb3badf81e2e64ab4ddcfd4921f5bc6710c6eb5eba514c92985266fcb805e5
SHA256 (8.0-RC1-ia64-disc3.iso) =
31fd356921f9430233bc7bf0699676746c735ddde9dc4d6ad21438ba66124912
SHA256 (8.0-RC1-ia64-dvd1.iso) =
a5bbdf0b0a338ffdc744f1d47513ebede568e852c3e07062b7c0e2f2aafd108b
SHA256 (8.0-RC1-ia64-livefs.iso) =
a3a5633900decc819982c50d672cdd653503fe4edebcb566eb4b27784f073635
SHA256 (8.0-RC1-pc98-bootonly.iso) =
5d50fd76e3a1124189acaf54e5258b92383ab0ce8b44b3e5b506020e011b9938
SHA256 (8.0-RC1-pc98-disc1.iso) =
4007e728e8a51fa04663ce9a234db2c1e1f587ebacc45bdeee0ba86261a89345
SHA256 (8.0-RC1-pc98-livefs.iso) =
18f2d066e7fb31b7ea5d95fc70f1bb99e2a9c6c72a45335858e461b9d4cad205
SHA256 (8.0-RC1-powerpc-bootonly.iso) =
b3a63ef86773ea28c548082d46d7199d4838648dfa1ecec82c881d90bb0ce9ca
SHA256 (8.0-RC1-powerpc-disc1.iso) =
7cd4e68f0e6bdf95090121ffd89383134c44447a6d1a18a800d58fb1dcd8d1c6
SHA256 (8.0-RC1-powerpc-disc2.iso) =
65719abb58fc8d7904fcbd7052d807efbe44f137badbcfbe7cef623d738360c1
SHA256 (8.0-RC1-powerpc-disc3.iso) =
9ec803dd266e752dcafe2fd3c6d5bb37b3bb6ce00c1cb4683c84616f866ec44b
SHA256 (8.0-RC1-powerpc-livefs.iso) =
7ef3142568fc6c4837faa6cbbd371cf709ee8e1d65df24ea538fba94095eebb5
SHA256 (8.0-RC1-sparc64-bootonly.iso) =
91fb4fee46c0a68520ce97351774725ae95ad4479f06e5d0f3de3e07eeb422d9
SHA256 (8.0-RC1-sparc64-disc1.iso) =
99c74dc6fa9b3185e12fa5084589d1f48f540082c5166026deccf673be46c343
SHA256 (8.0-RC1-sparc64-dvd1.iso) =
777d8afc3330fae4089510d6b852ea1d1f9108a868b8ebb3d5a661b108a99196
--
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: 195 bytes
Desc: This is a digitally signed message part
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090921/e73b81c5/attachment.pgp
On Mon, 21 Sep 2009, Ken Smith wrote:> > The first of the Release Candidates for the FreeBSD 8.0 release cycle is > now available. How many RC's we have will depend on how well 8.0-RC1 > does. At the moment only one more RC is on the schedule but odds are > fairly high we will wind up inserting at least one more RC. Between > BETA4 and RC1 a lot of work has gone into IPv6 issues as well as many > other issues that have been brought up from the public testing. And a > patch set was committed by the people who handle porting ZFS to FreeBSD > that they felt makes ZFS production-ready. > > Details about the current target schedule along with much more detail > about the current status of the release is available here: > > http://wiki.freebsd.org/8.0TODO > > There are two known problems with 8.0-RC1. One known issue with the > 8.0-RC1 build was discovered after the builds got started so is not part > of the ISO images or FreeBSD-Update builds. The issue is that local > IPv6 link-local addresses are not reachable. A fix for it has been > committed to RELENG_8 so if you install from the 8.0-RC1 media or update > using FreeBSD-Update you will then need to update using csup/cvsup > mechanisms if you need that fix for your environment. It should only > impact people using IPv6. > > The other known issue is that the flowtable may direct packets to the > wrong interface under certain routing conditions. We feel confident that > this bug will be fixed so the flowtable is enabled in RC1 to maximize > testing. If you experience routing problems, please temporarily disable > the flowtable using the sysctl <XXXX>=0 and report the results to theThat should be sysctl net.inet.flowtable.enable=0> freebsd-current@ mailing list. If we are unable to resolve this issue by > RC2, we will disable the flowtable in 8.0-RELEASE. > > If you notice problems you can report them through the normal Gnats PR > system or on the freebsd-current mailing list. I do cross-post > announcements to freebsd-stable because this particular release is > "about to become a stable branch" but when it comes to watching for > issues related to the release most of the developers pay more attention > to the freebsd-current list. > > ISO images for all supported architectures are available on the FTP > sites, and a "memory stick" image is available for amd64/i386 > architectures. For amd64/i386 architectures the cdrom and memstick > images include the documentation packages this time but no other > packages. The DVD image includes a rough pass at what packages will be > available on the official release media but is subject to change between > now and release. For sparc64 the DVD image has the set of packages that > currently build for sparc64, which is a sub-set of the set provided for > amd64/i386. The sparc64 disc1 does not have any packages on it because > I noticed a little too late that adding the doc packages to disc1 caused > it to overflow the target size. For 8.0-RC2 sparc64 will have the > livefs bits split out to a separate image (which is the way all the > other architectures have been for a while now) and the doc packages will > be provided on disc1. None of the other images include packages. > > If you are using csup/cvsup methods to update an older system the branch > tag to use is RELENG_8. > > The freebsd-update(8) utility supports binary upgrades of i386 and amd64 > systems running earlier FreeBSD releases. Systems running 7.0-RELEASE, > 7.1-RELEASE, 7.2-RELEASE, 8.0-BETA1, 8.0-BETA2, 8.0-BETA3, or 8.0-BETA4 > can upgrade as follows: > > # freebsd-update upgrade -r 8.0-RC1 > > During this process, FreeBSD Update may ask the user to help by merging > some configuration files or by confirming that the automatically > performed merging was done correctly. Systems running 8.0-BETA3 may > print the warning > > INDEX-OLD.all: Invalid arguments > > when downloading updates; this warning is a harmless bug (fixed in > 8.0-BETA4) and can be safely ignored. > > # freebsd-update install > > The system must be rebooted with the newly installed kernel before continuing. > > # 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.0-BETA2 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. See: > > http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html > > for mode details. 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 8.0-RC1: > > # shutdown -r now > > MD5/SHA256 checksums for the image files: > > MD5 (8.0-RC1-amd64-bootonly.iso) = a84d43c8adaba3fee9a618098668154e > MD5 (8.0-RC1-amd64-disc1.iso) = fb4f75c74144239b4994dc3ad040af33 > MD5 (8.0-RC1-amd64-dvd1.iso) = 5da3097634fbe049dd01ad4127d0f396 > MD5 (8.0-RC1-amd64-livefs.iso) = 43a483ea73cbbe80f0ef068502594363 > MD5 (8.0-RC1-amd64-memstick.img) = 9b1ffcab33ceed4dcdf1a0f3d862f811 > > MD5 (8.0-RC1-i386-bootonly.iso) = b569d950d6806c7c88a15d857bef6a02 > MD5 (8.0-RC1-i386-disc1.iso) = 1cfecd1489b8be4a6d06040b07af941b > MD5 (8.0-RC1-i386-dvd1.iso) = 474b54e73a04a2f573b8a26ad00e3077 > MD5 (8.0-RC1-i386-livefs.iso) = 7e5c3390c9f1e7915b9f229eb95f7e70 > MD5 (8.0-RC1-i386-memstick.img) = 532736e255f069f7f891d6ed4f14970e > > MD5 (8.0-RC1-ia64-bootonly.iso) = f53c920e46d3ceeb755617b2de20507a > MD5 (8.0-RC1-ia64-disc1.iso) = 504d3828b919563a83d7232d9a3a952b > MD5 (8.0-RC1-ia64-disc2.iso) = 5f22a63a89bff893038b32c0c53bf2eb > MD5 (8.0-RC1-ia64-disc3.iso) = bf17e84e9dfa62a6ce131e07bc701478 > MD5 (8.0-RC1-ia64-dvd1.iso) = b8cf5cc2feab96c98da12b6fb1623136 > MD5 (8.0-RC1-ia64-livefs.iso) = 2a83a1b32cfeb9a95f8ccc5e4cf36918 > > MD5 (8.0-RC1-pc98-bootonly.iso) = 60603f538db73c264ad7271da044e185 > MD5 (8.0-RC1-pc98-disc1.iso) = 7c00a58b4b8f3e94b25a4539116542bd > MD5 (8.0-RC1-pc98-livefs.iso) = aa67b1f3d8246381764a4df867e23f67 > > MD5 (8.0-RC1-powerpc-bootonly.iso) = a498cafdb4118f2d33007c5f0cf6ca0d > MD5 (8.0-RC1-powerpc-disc1.iso) = 4448a906a36356c479623c8b4af7e685 > MD5 (8.0-RC1-powerpc-disc2.iso) = bf9bf9e46da074a0787ca84da13251c8 > MD5 (8.0-RC1-powerpc-disc3.iso) = 2f600348579d4adc87b2a32f565f3f03 > MD5 (8.0-RC1-powerpc-livefs.iso) = 962f7d69cad7bb47e1cdfaf746b97f90 > > MD5 (8.0-RC1-sparc64-bootonly.iso) = 674724d0c2ddd997d86f91863c01ba20 > MD5 (8.0-RC1-sparc64-disc1.iso) = 9e896ac68263ff816e3721b8b31e63bb > MD5 (8.0-RC1-sparc64-dvd1.iso) = 8451f6fee8523cd33e3e7e973922d2cf > > SHA256 (8.0-RC1-amd64-bootonly.iso) = 0fcff1f76629c694be73133ad6ca5057a97a7030d824adb3a3a58bfe881528ab > SHA256 (8.0-RC1-amd64-disc1.iso) = 1b0246694012170ef83ce38395f4179c990d5689e1da2224a7cd2164770d1efb > SHA256 (8.0-RC1-amd64-dvd1.iso) = 63dec5385f549a22e6940a8d30d23be96dec0c27253550787107918631021bcc > SHA256 (8.0-RC1-amd64-livefs.iso) = adda93a732168586272697d32824626898bee6c95ec2efc9e691e649489b99c2 > SHA256 (8.0-RC1-amd64-memstick.img) = d2d3f90d3fb3b11cb06734df3ff1eb8433e4184158c85d34c4bd41ba068e131c > > SHA256 (8.0-RC1-i386-bootonly.iso) = 6b3f78fe556cb396cb1734fdcdfdd3619013b4318f94b1736349e641a0745dbb > SHA256 (8.0-RC1-i386-disc1.iso) = 06094f54d0b9141b571a8d22727a9c639a4ffb8a72dd05d12e995ef417eaaf37 > SHA256 (8.0-RC1-i386-dvd1.iso) = 02009c487ce5a00f52e45d2ccefc5c7b47edea110d1922ff21fe05ee7b1c8cb3 > SHA256 (8.0-RC1-i386-livefs.iso) = abcc0c3d975df784eaa4840af15555fc25f610f8699619142185c77b396e00aa > SHA256 (8.0-RC1-i386-memstick.img) = f6ed2716312b6fcdf4bea15e4290a122d34e569fda895fb8bdffa499eea6d9ce > > SHA256 (8.0-RC1-ia64-bootonly.iso) = c307cdfa5f98d84b367ac8ef939da6f42a2a0454c07ab0f7b7fe17b78c3f4c9e > SHA256 (8.0-RC1-ia64-disc1.iso) = 44612f9922e8ee2ca6453f9a54b81c01bf351486580fa7cc9cd031b2f0b132c6 > SHA256 (8.0-RC1-ia64-disc2.iso) = 01eb3badf81e2e64ab4ddcfd4921f5bc6710c6eb5eba514c92985266fcb805e5 > SHA256 (8.0-RC1-ia64-disc3.iso) = 31fd356921f9430233bc7bf0699676746c735ddde9dc4d6ad21438ba66124912 > SHA256 (8.0-RC1-ia64-dvd1.iso) = a5bbdf0b0a338ffdc744f1d47513ebede568e852c3e07062b7c0e2f2aafd108b > SHA256 (8.0-RC1-ia64-livefs.iso) = a3a5633900decc819982c50d672cdd653503fe4edebcb566eb4b27784f073635 > > SHA256 (8.0-RC1-pc98-bootonly.iso) = 5d50fd76e3a1124189acaf54e5258b92383ab0ce8b44b3e5b506020e011b9938 > SHA256 (8.0-RC1-pc98-disc1.iso) = 4007e728e8a51fa04663ce9a234db2c1e1f587ebacc45bdeee0ba86261a89345 > SHA256 (8.0-RC1-pc98-livefs.iso) = 18f2d066e7fb31b7ea5d95fc70f1bb99e2a9c6c72a45335858e461b9d4cad205 > > SHA256 (8.0-RC1-powerpc-bootonly.iso) = b3a63ef86773ea28c548082d46d7199d4838648dfa1ecec82c881d90bb0ce9ca > SHA256 (8.0-RC1-powerpc-disc1.iso) = 7cd4e68f0e6bdf95090121ffd89383134c44447a6d1a18a800d58fb1dcd8d1c6 > SHA256 (8.0-RC1-powerpc-disc2.iso) = 65719abb58fc8d7904fcbd7052d807efbe44f137badbcfbe7cef623d738360c1 > SHA256 (8.0-RC1-powerpc-disc3.iso) = 9ec803dd266e752dcafe2fd3c6d5bb37b3bb6ce00c1cb4683c84616f866ec44b > SHA256 (8.0-RC1-powerpc-livefs.iso) = 7ef3142568fc6c4837faa6cbbd371cf709ee8e1d65df24ea538fba94095eebb5 > > SHA256 (8.0-RC1-sparc64-bootonly.iso) = 91fb4fee46c0a68520ce97351774725ae95ad4479f06e5d0f3de3e07eeb422d9 > SHA256 (8.0-RC1-sparc64-disc1.iso) = 99c74dc6fa9b3185e12fa5084589d1f48f540082c5166026deccf673be46c343 > SHA256 (8.0-RC1-sparc64-dvd1.iso) = 777d8afc3330fae4089510d6b852ea1d1f9108a868b8ebb3d5a661b108a99196 > >-- Bjoern A. Zeeb What was I talking about and who are you again?
> > The first of the Release Candidates for the FreeBSD 8.0 release cycle is > now available. How many RC's we have will depend on how well 8.0-RC1 > does. At the moment only one more RC is on the schedule but odds are > fairly high we will wind up inserting at least one more RC. Between > BETA4 and RC1 a lot of work has gone into IPv6 issues as well as many > other issues that have been brought up from the public testing. And a > patch set was committed by the people who handle porting ZFS to FreeBSD > that they felt makes ZFS production-ready. > > Details about the current target schedule along with much more detail > about the current status of the release is available here: > > http://wiki.freebsd.org/8.0TODO > > There are two known problems with 8.0-RC1. One known issue with the > 8.0-RC1 build was discovered after the builds got started so is not part > of the ISO images or FreeBSD-Update builds. The issue is that local > IPv6 link-local addresses are not reachable. A fix for it has been > committed to RELENG_8 so if you install from the 8.0-RC1 media or update > using FreeBSD-Update you will then need to update using csup/cvsup > mechanisms if you need that fix for your environment. It should only > impact people using IPv6. > > The other known issue is that the flowtable may direct packets to the > wrong interface under certain routing conditions. We feel confident that > this bug will be fixed so the flowtable is enabled in RC1 to maximize > testing. If you experience routing problems, please temporarily disable > the flowtable using the sysctl <XXXX>=0 and report the results to the > freebsd-current@ mailing list. If we are unable to resolve this issue by > RC2, we will disable the flowtable in 8.0-RELEASE. > > If you notice problems you can report them through the normal Gnats PR > system or on the freebsd-current mailing list. I do cross-post > announcements to freebsd-stable because this particular release is > "about to become a stable branch" but when it comes to watching for > issues related to the release most of the developers pay more attention > to the freebsd-current list. > > ISO images for all supported architectures are available on the FTP > sites, and a "memory stick" image is available for amd64/i386 > architectures. For amd64/i386 architectures the cdrom and memstick > images include the documentation packages this time but no other > packages. The DVD image includes a rough pass at what packages will be > available on the official release media but is subject to change between > now and release. For sparc64 the DVD image has the set of packages that > currently build for sparc64, which is a sub-set of the set provided for > amd64/i386. The sparc64 disc1 does not have any packages on it because > I noticed a little too late that adding the doc packages to disc1 caused > it to overflow the target size. For 8.0-RC2 sparc64 will have the > livefs bits split out to a separate image (which is the way all the > other architectures have been for a while now) and the doc packages will > be provided on disc1. None of the other images include packages. > > If you are using csup/cvsup methods to update an older system the branch > tag to use is RELENG_8. > > The freebsd-update(8) utility supports binary upgrades of i386 and amd64 > systems running earlier FreeBSD releases. Systems running 7.0-RELEASE, > 7.1-RELEASE, 7.2-RELEASE, 8.0-BETA1, 8.0-BETA2, 8.0-BETA3, or 8.0-BETA4 > can upgrade as follows: > # freebsd-update upgrade -r 8.0-RC1 > During this process, FreeBSD Update may ask the user to help by merging > some configuration files or by confirming that the automatically > performed merging was done correctly. Systems running 8.0-BETA3 may > print the warning > > INDEX-OLD.all: Invalid arguments > > when downloading updates; this warning is a harmless bug (fixed in > 8.0-BETA4) and can be safely ignored. > > # freebsd-update install > The system must be rebooted with the newly installed kernel before > continuing. > # 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.0-BETA2 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. See: > > http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html > > for mode details. 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 8.0-RC1: > # shutdown -r now > > MD5/SHA256 checksums for the image files: > > MD5 (8.0-RC1-amd64-bootonly.iso) = a84d43c8adaba3fee9a618098668154e > MD5 (8.0-RC1-amd64-disc1.iso) = fb4f75c74144239b4994dc3ad040af33 > MD5 (8.0-RC1-amd64-dvd1.iso) = 5da3097634fbe049dd01ad4127d0f396 > MD5 (8.0-RC1-amd64-livefs.iso) = 43a483ea73cbbe80f0ef068502594363 > MD5 (8.0-RC1-amd64-memstick.img) = 9b1ffcab33ceed4dcdf1a0f3d862f811 > > MD5 (8.0-RC1-i386-bootonly.iso) = b569d950d6806c7c88a15d857bef6a02 > MD5 (8.0-RC1-i386-disc1.iso) = 1cfecd1489b8be4a6d06040b07af941b > MD5 (8.0-RC1-i386-dvd1.iso) = 474b54e73a04a2f573b8a26ad00e3077 > MD5 (8.0-RC1-i386-livefs.iso) = 7e5c3390c9f1e7915b9f229eb95f7e70 > MD5 (8.0-RC1-i386-memstick.img) = 532736e255f069f7f891d6ed4f14970e > > MD5 (8.0-RC1-ia64-bootonly.iso) = f53c920e46d3ceeb755617b2de20507a > MD5 (8.0-RC1-ia64-disc1.iso) = 504d3828b919563a83d7232d9a3a952b > MD5 (8.0-RC1-ia64-disc2.iso) = 5f22a63a89bff893038b32c0c53bf2eb > MD5 (8.0-RC1-ia64-disc3.iso) = bf17e84e9dfa62a6ce131e07bc701478 > MD5 (8.0-RC1-ia64-dvd1.iso) = b8cf5cc2feab96c98da12b6fb1623136 > MD5 (8.0-RC1-ia64-livefs.iso) = 2a83a1b32cfeb9a95f8ccc5e4cf36918 > > MD5 (8.0-RC1-pc98-bootonly.iso) = 60603f538db73c264ad7271da044e185 > MD5 (8.0-RC1-pc98-disc1.iso) = 7c00a58b4b8f3e94b25a4539116542bd > MD5 (8.0-RC1-pc98-livefs.iso) = aa67b1f3d8246381764a4df867e23f67 > > MD5 (8.0-RC1-powerpc-bootonly.iso) = a498cafdb4118f2d33007c5f0cf6ca0d > MD5 (8.0-RC1-powerpc-disc1.iso) = 4448a906a36356c479623c8b4af7e685 > MD5 (8.0-RC1-powerpc-disc2.iso) = bf9bf9e46da074a0787ca84da13251c8 > MD5 (8.0-RC1-powerpc-disc3.iso) = 2f600348579d4adc87b2a32f565f3f03 > MD5 (8.0-RC1-powerpc-livefs.iso) = 962f7d69cad7bb47e1cdfaf746b97f90 > > MD5 (8.0-RC1-sparc64-bootonly.iso) = 674724d0c2ddd997d86f91863c01ba20 > MD5 (8.0-RC1-sparc64-disc1.iso) = 9e896ac68263ff816e3721b8b31e63bb > MD5 (8.0-RC1-sparc64-dvd1.iso) = 8451f6fee8523cd33e3e7e973922d2cf > > SHA256 (8.0-RC1-amd64-bootonly.iso) = > 0fcff1f76629c694be73133ad6ca5057a97a7030d824adb3a3a58bfe881528ab > SHA256 (8.0-RC1-amd64-disc1.iso) = > 1b0246694012170ef83ce38395f4179c990d5689e1da2224a7cd2164770d1efb > SHA256 (8.0-RC1-amd64-dvd1.iso) = > 63dec5385f549a22e6940a8d30d23be96dec0c27253550787107918631021bcc > SHA256 (8.0-RC1-amd64-livefs.iso) = > adda93a732168586272697d32824626898bee6c95ec2efc9e691e649489b99c2 > SHA256 (8.0-RC1-amd64-memstick.img) = > d2d3f90d3fb3b11cb06734df3ff1eb8433e4184158c85d34c4bd41ba068e131c > > SHA256 (8.0-RC1-i386-bootonly.iso) = > 6b3f78fe556cb396cb1734fdcdfdd3619013b4318f94b1736349e641a0745dbb > SHA256 (8.0-RC1-i386-disc1.iso) = > 06094f54d0b9141b571a8d22727a9c639a4ffb8a72dd05d12e995ef417eaaf37 > SHA256 (8.0-RC1-i386-dvd1.iso) = > 02009c487ce5a00f52e45d2ccefc5c7b47edea110d1922ff21fe05ee7b1c8cb3 > SHA256 (8.0-RC1-i386-livefs.iso) = > abcc0c3d975df784eaa4840af15555fc25f610f8699619142185c77b396e00aa > SHA256 (8.0-RC1-i386-memstick.img) = > f6ed2716312b6fcdf4bea15e4290a122d34e569fda895fb8bdffa499eea6d9ce > > SHA256 (8.0-RC1-ia64-bootonly.iso) = > c307cdfa5f98d84b367ac8ef939da6f42a2a0454c07ab0f7b7fe17b78c3f4c9e > SHA256 (8.0-RC1-ia64-disc1.iso) = > 44612f9922e8ee2ca6453f9a54b81c01bf351486580fa7cc9cd031b2f0b132c6 > SHA256 (8.0-RC1-ia64-disc2.iso) = > 01eb3badf81e2e64ab4ddcfd4921f5bc6710c6eb5eba514c92985266fcb805e5 > SHA256 (8.0-RC1-ia64-disc3.iso) = > 31fd356921f9430233bc7bf0699676746c735ddde9dc4d6ad21438ba66124912 > SHA256 (8.0-RC1-ia64-dvd1.iso) = > a5bbdf0b0a338ffdc744f1d47513ebede568e852c3e07062b7c0e2f2aafd108b > SHA256 (8.0-RC1-ia64-livefs.iso) = > a3a5633900decc819982c50d672cdd653503fe4edebcb566eb4b27784f073635 > > SHA256 (8.0-RC1-pc98-bootonly.iso) = > 5d50fd76e3a1124189acaf54e5258b92383ab0ce8b44b3e5b506020e011b9938 > SHA256 (8.0-RC1-pc98-disc1.iso) = > 4007e728e8a51fa04663ce9a234db2c1e1f587ebacc45bdeee0ba86261a89345 > SHA256 (8.0-RC1-pc98-livefs.iso) = > 18f2d066e7fb31b7ea5d95fc70f1bb99e2a9c6c72a45335858e461b9d4cad205 > > SHA256 (8.0-RC1-powerpc-bootonly.iso) = > b3a63ef86773ea28c548082d46d7199d4838648dfa1ecec82c881d90bb0ce9ca > SHA256 (8.0-RC1-powerpc-disc1.iso) = > 7cd4e68f0e6bdf95090121ffd89383134c44447a6d1a18a800d58fb1dcd8d1c6 > SHA256 (8.0-RC1-powerpc-disc2.iso) = > 65719abb58fc8d7904fcbd7052d807efbe44f137badbcfbe7cef623d738360c1 > SHA256 (8.0-RC1-powerpc-disc3.iso) = > 9ec803dd266e752dcafe2fd3c6d5bb37b3bb6ce00c1cb4683c84616f866ec44b > SHA256 (8.0-RC1-powerpc-livefs.iso) = > 7ef3142568fc6c4837faa6cbbd371cf709ee8e1d65df24ea538fba94095eebb5 > > SHA256 (8.0-RC1-sparc64-bootonly.iso) = > 91fb4fee46c0a68520ce97351774725ae95ad4479f06e5d0f3de3e07eeb422d9 > SHA256 (8.0-RC1-sparc64-disc1.iso) = > 99c74dc6fa9b3185e12fa5084589d1f48f540082c5166026deccf673be46c343 > SHA256 (8.0-RC1-sparc64-dvd1.iso) = > 777d8afc3330fae4089510d6b852ea1d1f9108a868b8ebb3d5a661b108a99196 >Hi Ken, I don't know whether USB stick can't boot issue is a show stoper, but it really a big problem for me. I hope it can resolve before 8.0-RELEASE. -- The Power to Serve