The first of two planned Release Candidates for the FreeBSD 7.2-RELEASE
cycle is now available. Testing of some of the recent work would be
particularly appreciated. This includes:
- bce(4) updated (there is a report that lagg(4) does
not work after the update, fixing that may need to be
done as an Errata Notice after the release)
- testing of the threading libraries
- amr(4) should be fixed
A fix for the "vm_page_insert: page already inserted" panics has been
committed to RELENG_7_1 this morning so it missed the 7.2-RC1 builds.
If you wind up being hit by that you can try a normal source based
update to the current state of RELENG_7_1 and that problem should go
away.
We have slipped by two days at this point but otherwise are on track
with the target release schedule which is here:
http://www.freebsd.org/releases/7.2R/schedule.html
We continue to watch for problems both on the mailing lists and in Gnats
but at this point we know of nothing we consider show-stopper calibre.
Unless something that bad does surface as a result of 7.2-RC1 testing we
should be sticking to the schedule.
The ISO images and FTP install trees are available on the FreeBSD Mirror
sites. Using the primary site as an example:
ftp://ftp.freebsd.org/pub/FreeBSD/releases/${arch}/ISO-IMAGES/7.2/
where ${arch} is one of amd64 i386, ia64, pc98, or sparc64. The
builds for powerpc are still in progress, it should become available
in a day or two.
Checksums for the ISO images are at the bottom of this message. The
amd64 and i386 sets include a *preliminary* set of packages.
If you would like to do a source-based update to 7.2-RC1 from an
already installed machine you can update your tree to RELENG_7_1 using
normal cvsup/csup methods.
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, or 7.2-BETA1 can upgrade as follows:
# freebsd-update upgrade -r 7.2-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.
# 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, and the system needs to be rebooted again:
# freebsd-update install
# shutdown -r now
Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update to
upgrade to FreeBSD 7.2-RC1, but will be prompted to rebuild all third-party
applications (e.g., anything installed from the ports tree) after the second
invocation of "freebsd-update install", in order to handle differences
in the
system libraries between FreeBSD 6.x and FreeBSD 7.x.
Checksums:
MD5 (7.2-RC1-amd64-bootonly.iso) = 2e4474ca4924ac589adf600b1d7d7168
MD5 (7.2-RC1-amd64-disc1.iso) = 47e1a823636dec2e8a88e2d4794d87da
MD5 (7.2-RC1-amd64-disc2.iso) = 6761b5cf2ac2d8399c28b58ccdddb2a5
MD5 (7.2-RC1-amd64-disc3.iso) = 02c798036ed43f4f346518d584783a72
MD5 (7.2-RC1-amd64-docs.iso) = ece13f382c308ce05f7dfc1aef4d0a62
MD5 (7.2-RC1-amd64-dvd1.iso) = 2a25cc807849fa2987c032c87053c8e9
MD5 (7.2-RC1-amd64-livefs.iso) = fbff690090c9cf3d5cf1b07b6c019b40
MD5 (7.2-RC1-i386-bootonly.iso) = 85783d47f3d03dcdd6859cbe94fa41e2
MD5 (7.2-RC1-i386-disc1.iso) = 4ef516f7fa88ab6a6f67f6fba3e9e86e
MD5 (7.2-RC1-i386-disc2.iso) = f5bf94273f64f4e4f968322990bd32eb
MD5 (7.2-RC1-i386-disc3.iso) = 634cce798ea17117a009f53e07dadda0
MD5 (7.2-RC1-i386-docs.iso) = 2b019c24576c03c382bd3748baeb473b
MD5 (7.2-RC1-i386-dvd1.iso) = ed88046ecae36fd1dd12157534243106
MD5 (7.2-RC1-i386-livefs.iso) = 81637ca4b1668ff44047fe4b6fc71447
MD5 (7.2-RC1-ia64-bootonly.iso) = 414bf45bbbae757dff03acea5484635f
MD5 (7.2-RC1-ia64-disc1.iso) = 0f26204eaa8c63a37b34ef0101dcb278
MD5 (7.2-RC1-ia64-disc2.iso) = cc206f814e5da015042485bfe5c30605
MD5 (7.2-RC1-ia64-disc3.iso) = 3888415a65514805546d8ad50cf0f650
MD5 (7.2-RC1-ia64-docs.iso) = 07c5c83f05248f7b7dec7e210e2cbf9e
MD5 (7.2-RC1-ia64-livefs.iso) = df5ffb89ae0a5e9aea8cc12a75c0d14a
MD5 (7.2-RC1-pc98-bootonly.iso) = b4b0b16bc0afa9ce734d1c4a303fc13c
MD5 (7.2-RC1-pc98-disc1.iso) = 33dd272b30bab2f1ad2a3455a177c3b5
MD5 (7.2-RC1-pc98-livefs.iso) = 7ffda81d7d91bb91db202de7c30afadd
MD5 (7.2-RC1-sparc64-bootonly.iso) = a220e5318eb10e4ff3b6c783d76a1b28
MD5 (7.2-RC1-sparc64-disc1.iso) = c23469659332723ce600073611497f52
MD5 (7.2-RC1-sparc64-docs.iso) = 96fc98f8ac071a5942fc25fa4ab940eb
SHA256 (7.2-RC1-amd64-bootonly.iso) =
9e4786270b12f5fff34e063edbc05b995f2b539c2931a26020153d5e603da9cd
SHA256 (7.2-RC1-amd64-disc1.iso) =
a4c707c20dc3b0e33ab8bdd5408e03b31481115147643bcd65c49a322b956e68
SHA256 (7.2-RC1-amd64-disc2.iso) =
5fde245f11064c2033bfbf1c40f8c62a1c204a8e0cadc7be2f105823b3c1da16
SHA256 (7.2-RC1-amd64-disc3.iso) =
85858d70199b1705d3e8d8e1770a65c64da63089dc122462a900040833e66479
SHA256 (7.2-RC1-amd64-docs.iso) =
620b57e6db73097755aacf73a2746a2ef70a1bcc3f054813caf95c0a3d8865c2
SHA256 (7.2-RC1-amd64-dvd1.iso) =
a24ce789c6f72d1189c70df4982bdc6eb79f5227a4706df0f784b001d30c68e1
SHA256 (7.2-RC1-amd64-livefs.iso) =
b2145383bac00cf73a81242dc89ee5c68ccb00c2011e57724e9e786d429b8c23
SHA256 (7.2-RC1-i386-bootonly.iso) =
1b56aca9f0647b2f321524326240f17b05cc9a4f5e83adde7f71a09b9b9d01ab
SHA256 (7.2-RC1-i386-disc1.iso) =
d96d670172fbc7405e529e9c47f4aa72c96c704bbdf8fac9ac77662f17f49888
SHA256 (7.2-RC1-i386-disc2.iso) =
b38cb7d48e8aae2fff142f8165c62fa61290d08e3fa75ce9c3fd035871f6e40c
SHA256 (7.2-RC1-i386-disc3.iso) =
bb4d39117210d9884fcef3c9936d1be72db06544ae696607ca9c082c6b4fdda7
SHA256 (7.2-RC1-i386-docs.iso) =
8b84fc57e727f7b085a909965c5d765bb23dea9828fff706e55068e997f8719c
SHA256 (7.2-RC1-i386-dvd1.iso) =
aca822e5b4dd096f4a7d51dc912cddca005ce0983853e99cf12506b40403289e
SHA256 (7.2-RC1-i386-livefs.iso) =
dddef3930777027de4b2faf09be83560266efe7b47e51ed62a630b683ca1acdb
SHA256 (7.2-RC1-ia64-bootonly.iso) =
7187248fc225b020177301fdc435e52b73a41ee0ab145aa0249770a1386fa891
SHA256 (7.2-RC1-ia64-disc1.iso) =
fac482f9bf93a0fac8f6ab89d8a89b047e4861a023b1f14d8067163560795c36
SHA256 (7.2-RC1-ia64-disc2.iso) =
95e182b4c0c6f7e8179e1fe568c0804a9f352c83beeea330a0664849071ff4d6
SHA256 (7.2-RC1-ia64-disc3.iso) =
2100105114f26421d90bf13d6d1f417b837835102635c8af5048baf3867b1da0
SHA256 (7.2-RC1-ia64-docs.iso) =
615cf4afdf30dbaa3fef58f0a15ff769502e1316b70c7657efd3d2af4d402385
SHA256 (7.2-RC1-ia64-livefs.iso) =
92f06a856143dd59108de23d23dcc49c04ee136d461630f1754d2455ebde0343
SHA256 (7.2-RC1-pc98-bootonly.iso) =
2dd4b6e61f7ed9d99cac26ed9ab3203d4ae7a2086cc4ac9efbe7260e8c94592e
SHA256 (7.2-RC1-pc98-disc1.iso) =
31de5cc66e5df83668d54ef8a1bc28cc85f4763bb955a516fb214333b2182062
SHA256 (7.2-RC1-pc98-livefs.iso) =
256a80ae9b19b3c766f1200e2ef127c7d6be5b2064e24b882c239746147cf922
SHA256 (7.2-RC1-sparc64-bootonly.iso) =
cd3575d870d85dce59a7c964798569c5b2b135a15697f914490260c90d854e25
SHA256 (7.2-RC1-sparc64-disc1.iso) =
f6464477b96eb79cac87fab60a311af2b59d7d685247e44beef24b32b45ce761
SHA256 (7.2-RC1-sparc64-docs.iso) =
51c97434a16c30169083a6220f7b6493c1404cacf7abb412caba24e88b686a21
--
Ken Smith
- From there to here, from here to | kensmith@cse.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/20090417/0547e465/attachment.pgp
Got it on Vista Home 64 & VMware server Two CPU's & two gigs of ram. Works grate so far. fast too On Fri, 17 Apr 2009 13:15:03 -0400 Ken Smith <kensmith@cse.Buffalo.EDU> wrote:> > The first of two planned Release Candidates for the > FreeBSD 7.2-RELEASE > cycle is now available. Testing of some of the recent > work would be > particularly appreciated. This includes: > > - bce(4) updated (there is a report that lagg(4) does > not work after the update, fixing that may need to be > done as an Errata Notice after the release) > - testing of the threading libraries > - amr(4) should be fixed > > A fix for the "vm_page_insert: page already inserted" > panics has been > committed to RELENG_7_1 this morning so it missed the > 7.2-RC1 builds. > If you wind up being hit by that you can try a normal > source based > update to the current state of RELENG_7_1 and that > problem should go > away. > > We have slipped by two days at this point but otherwise > are on track > with the target release schedule which is here: > > http://www.freebsd.org/releases/7.2R/schedule.html > > We continue to watch for problems both on the mailing > lists and in Gnats > but at this point we know of nothing we consider > show-stopper calibre. > Unless something that bad does surface as a result of > 7.2-RC1 testing we > should be sticking to the schedule. > > The ISO images and FTP install trees are available on the > FreeBSD Mirror > sites. Using the primary site as an example: > >ftp://ftp.freebsd.org/pub/FreeBSD/releases/${arch}/ISO-IMAGES/7.2/> > where ${arch} is one of amd64 i386, ia64, pc98, or > sparc64. The > builds for powerpc are still in progress, it should > become available > in a day or two. > > Checksums for the ISO images are at the bottom of this > message. The > amd64 and i386 sets include a *preliminary* set of > packages. > > If you would like to do a source-based update to 7.2-RC1 > from an > already installed machine you can update your tree to > RELENG_7_1 using > normal cvsup/csup methods. > > 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, or 7.2-BETA1 can upgrade as follows: > > # freebsd-update upgrade -r 7.2-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. > > # 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, and the system needs to be rebooted > again: > > # freebsd-update install > # shutdown -r now > > Users of earlier FreeBSD releases (FreeBSD 6.x) can also > use freebsd-update to > upgrade to FreeBSD 7.2-RC1, but will be prompted to > rebuild all third-party > applications (e.g., anything installed from the ports > tree) after the second > invocation of "freebsd-update install", in order to > handle differences in the > system libraries between FreeBSD 6.x and FreeBSD 7.x. > > > Checksums: > > MD5 (7.2-RC1-amd64-bootonly.iso) > 2e4474ca4924ac589adf600b1d7d7168 > MD5 (7.2-RC1-amd64-disc1.iso) > 47e1a823636dec2e8a88e2d4794d87da > MD5 (7.2-RC1-amd64-disc2.iso) > 6761b5cf2ac2d8399c28b58ccdddb2a5 > MD5 (7.2-RC1-amd64-disc3.iso) > 02c798036ed43f4f346518d584783a72 > MD5 (7.2-RC1-amd64-docs.iso) > ece13f382c308ce05f7dfc1aef4d0a62 > MD5 (7.2-RC1-amd64-dvd1.iso) > 2a25cc807849fa2987c032c87053c8e9 > MD5 (7.2-RC1-amd64-livefs.iso) > fbff690090c9cf3d5cf1b07b6c019b40 > > MD5 (7.2-RC1-i386-bootonly.iso) > 85783d47f3d03dcdd6859cbe94fa41e2 > MD5 (7.2-RC1-i386-disc1.iso) > 4ef516f7fa88ab6a6f67f6fba3e9e86e > MD5 (7.2-RC1-i386-disc2.iso) > f5bf94273f64f4e4f968322990bd32eb > MD5 (7.2-RC1-i386-disc3.iso) > 634cce798ea17117a009f53e07dadda0 > MD5 (7.2-RC1-i386-docs.iso) > 2b019c24576c03c382bd3748baeb473b > MD5 (7.2-RC1-i386-dvd1.iso) > ed88046ecae36fd1dd12157534243106 > MD5 (7.2-RC1-i386-livefs.iso) > 81637ca4b1668ff44047fe4b6fc71447 > > MD5 (7.2-RC1-ia64-bootonly.iso) > 414bf45bbbae757dff03acea5484635f > MD5 (7.2-RC1-ia64-disc1.iso) > 0f26204eaa8c63a37b34ef0101dcb278 > MD5 (7.2-RC1-ia64-disc2.iso) > cc206f814e5da015042485bfe5c30605 > MD5 (7.2-RC1-ia64-disc3.iso) > 3888415a65514805546d8ad50cf0f650 > MD5 (7.2-RC1-ia64-docs.iso) > 07c5c83f05248f7b7dec7e210e2cbf9e > MD5 (7.2-RC1-ia64-livefs.iso) > df5ffb89ae0a5e9aea8cc12a75c0d14a > > MD5 (7.2-RC1-pc98-bootonly.iso) > b4b0b16bc0afa9ce734d1c4a303fc13c > MD5 (7.2-RC1-pc98-disc1.iso) > 33dd272b30bab2f1ad2a3455a177c3b5 > MD5 (7.2-RC1-pc98-livefs.iso) > 7ffda81d7d91bb91db202de7c30afadd > > MD5 (7.2-RC1-sparc64-bootonly.iso) > a220e5318eb10e4ff3b6c783d76a1b28 > MD5 (7.2-RC1-sparc64-disc1.iso) > c23469659332723ce600073611497f52 > MD5 (7.2-RC1-sparc64-docs.iso) > 96fc98f8ac071a5942fc25fa4ab940eb > > SHA256 (7.2-RC1-amd64-bootonly.iso) >9e4786270b12f5fff34e063edbc05b995f2b539c2931a26020153d5e603da9cd> SHA256 (7.2-RC1-amd64-disc1.iso) >a4c707c20dc3b0e33ab8bdd5408e03b31481115147643bcd65c49a322b956e68> SHA256 (7.2-RC1-amd64-disc2.iso) >5fde245f11064c2033bfbf1c40f8c62a1c204a8e0cadc7be2f105823b3c1da16> SHA256 (7.2-RC1-amd64-disc3.iso) >85858d70199b1705d3e8d8e1770a65c64da63089dc122462a900040833e66479> SHA256 (7.2-RC1-amd64-docs.iso) >620b57e6db73097755aacf73a2746a2ef70a1bcc3f054813caf95c0a3d8865c2> SHA256 (7.2-RC1-amd64-dvd1.iso) >a24ce789c6f72d1189c70df4982bdc6eb79f5227a4706df0f784b001d30c68e1> SHA256 (7.2-RC1-amd64-livefs.iso) >b2145383bac00cf73a81242dc89ee5c68ccb00c2011e57724e9e786d429b8c23> > SHA256 (7.2-RC1-i386-bootonly.iso) >1b56aca9f0647b2f321524326240f17b05cc9a4f5e83adde7f71a09b9b9d01ab> SHA256 (7.2-RC1-i386-disc1.iso) >d96d670172fbc7405e529e9c47f4aa72c96c704bbdf8fac9ac77662f17f49888> SHA256 (7.2-RC1-i386-disc2.iso) >b38cb7d48e8aae2fff142f8165c62fa61290d08e3fa75ce9c3fd035871f6e40c> SHA256 (7.2-RC1-i386-disc3.iso) >bb4d39117210d9884fcef3c9936d1be72db06544ae696607ca9c082c6b4fdda7> SHA256 (7.2-RC1-i386-docs.iso) >8b84fc57e727f7b085a909965c5d765bb23dea9828fff706e55068e997f8719c> SHA256 (7.2-RC1-i386-dvd1.iso) >aca822e5b4dd096f4a7d51dc912cddca005ce0983853e99cf12506b40403289e> SHA256 (7.2-RC1-i386-livefs.iso) >dddef3930777027de4b2faf09be83560266efe7b47e51ed62a630b683ca1acdb> > SHA256 (7.2-RC1-ia64-bootonly.iso) >7187248fc225b020177301fdc435e52b73a41ee0ab145aa0249770a1386fa891> SHA256 (7.2-RC1-ia64-disc1.iso) >fac482f9bf93a0fac8f6ab89d8a89b047e4861a023b1f14d8067163560795c36> SHA256 (7.2-RC1-ia64-disc2.iso) >95e182b4c0c6f7e8179e1fe568c0804a9f352c83beeea330a0664849071ff4d6> SHA256 (7.2-RC1-ia64-disc3.iso) >2100105114f26421d90bf13d6d1f417b837835102635c8af5048baf3867b1da0> SHA256 (7.2-RC1-ia64-docs.iso) >615cf4afdf30dbaa3fef58f0a15ff769502e1316b70c7657efd3d2af4d402385> SHA256 (7.2-RC1-ia64-livefs.iso) >92f06a856143dd59108de23d23dcc49c04ee136d461630f1754d2455ebde0343> > SHA256 (7.2-RC1-pc98-bootonly.iso) >2dd4b6e61f7ed9d99cac26ed9ab3203d4ae7a2086cc4ac9efbe7260e8c94592e> SHA256 (7.2-RC1-pc98-disc1.iso) >31de5cc66e5df83668d54ef8a1bc28cc85f4763bb955a516fb214333b2182062> SHA256 (7.2-RC1-pc98-livefs.iso) >256a80ae9b19b3c766f1200e2ef127c7d6be5b2064e24b882c239746147cf922> > SHA256 (7.2-RC1-sparc64-bootonly.iso) >cd3575d870d85dce59a7c964798569c5b2b135a15697f914490260c90d854e25> SHA256 (7.2-RC1-sparc64-disc1.iso) >f6464477b96eb79cac87fab60a311af2b59d7d685247e44beef24b32b45ce761> SHA256 (7.2-RC1-sparc64-docs.iso) >51c97434a16c30169083a6220f7b6493c1404cacf7abb412caba24e88b686a21> > -- > Ken Smith > - From there to here, from here to | > kensmith@cse.buffalo.edu > there, funny things are everywhere. | > - Theodore Geisel | >
On Fri, 2009-04-17 at 13:15 -0400, Ken Smith wrote:> A fix for the "vm_page_insert: page already inserted" panics has been > committed to RELENG_7_1 this morning so it missed the 7.2-RC1 builds. > If you wind up being hit by that you can try a normal source based > update to the current state of RELENG_7_1 and that problem should go > away.> If you would like to do a source-based update to 7.2-RC1 from an > already installed machine you can update your tree to RELENG_7_1 using > normal cvsup/csup methods.Sorry, I had "RC*1*" on the brain... The proper branch tag is RELENG_7_2. Sorry about that. -- Ken Smith - From there to here, from here to | kensmith@cse.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/20090417/d0e6861f/attachment.pgp
On Fri, Apr 17, 2009 at 01:15:03PM -0400, Ken Smith wrote:> > The first of two planned Release Candidates for the FreeBSD 7.2-RELEASE > cycle is now available. Testing of some of the recent work would be > particularly appreciated. This includes: > > - bce(4) updated (there is a report that lagg(4) does > not work after the update, fixing that may need to be > done as an Errata Notice after the release) > - testing of the threading libraries > - amr(4) should be fixed > > A fix for the "vm_page_insert: page already inserted" panics has been > committed to RELENG_7_1 this morning so it missed the 7.2-RC1 builds. > If you wind up being hit by that you can try a normal source based > update to the current state of RELENG_7_1 and that problem should go > away.I assume that you mean 'RELENG_7_2' rather than 'RELENG_7_1' in the above paragraph? (As well as further down.)> > We have slipped by two days at this point but otherwise are on track > with the target release schedule which is here: > > http://www.freebsd.org/releases/7.2R/schedule.html > > We continue to watch for problems both on the mailing lists and in Gnats > but at this point we know of nothing we consider show-stopper calibre. > Unless something that bad does surface as a result of 7.2-RC1 testing we > should be sticking to the schedule. > > The ISO images and FTP install trees are available on the FreeBSD Mirror > sites. Using the primary site as an example: > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/${arch}/ISO-IMAGES/7.2/ > > where ${arch} is one of amd64 i386, ia64, pc98, or sparc64. The > builds for powerpc are still in progress, it should become available > in a day or two. > > Checksums for the ISO images are at the bottom of this message. The > amd64 and i386 sets include a *preliminary* set of packages. > > If you would like to do a source-based update to 7.2-RC1 from an > already installed machine you can update your tree to RELENG_7_1 using > normal cvsup/csup methods. > > 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, or 7.2-BETA1 can upgrade as follows: > > # freebsd-update upgrade -r 7.2-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. > > # 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, and the system needs to be rebooted again: > > # freebsd-update install > # shutdown -r now > > Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update to > upgrade to FreeBSD 7.2-RC1, but will be prompted to rebuild all third-party > applications (e.g., anything installed from the ports tree) after the second > invocation of "freebsd-update install", in order to handle differences in the > system libraries between FreeBSD 6.x and FreeBSD 7.x. >-- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
> - bce(4) updated (there is a report that lagg(4) does > not work after the update, fixing that may need to be > done as an Errata Notice after the release)[ this is http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/133756 ] I just tested again with a csup of RELENG_7_2 and this still has the lagg problem. I know it most likely won't be fixed before release, so we do need a big warning in the release notes to tell people with this setup not to update, as it will just kill all network connectivity. -pete.
Am 17.04.2009, 19:15 Uhr, schrieb Ken Smith <kensmith@cse.buffalo.edu>:> The first of two planned Release Candidates for the FreeBSD 7.2-RELEASE > cycle is now available. Testing of some of the recent work would be > particularly appreciated. This includes:Can one peek at the release notes already? The /relnotes.html main links point to empty documents, the snapshots point to 7.0 release notes. Particularly, can FreeBSD 7.2 support 256-byte inodes in ext2fs? -- Matthias Andree