FreeBSD 9.1-RC3 Available...
The third release candidate of the 9.1-RELEASE release cycle is now available on the FTP servers for amd64, i386, powerpc64, and sparc64. The MD5/SHA256 checksums are at the bottom of this message. The ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.1/ (or any of the FreeBSD mirror sites). This is expected to be the last Release Candidate. Unless a major show-stopper is discovered within the next few days the final Release Builds will be started. If you notice any problems you can report them through the normal Gnats PR system or here on the -stable mailing list. If you want to do a source-based update to an existing system using SVN the branch to use is releng/9.1. If you would like to use CVS instead use RELENG_9_1. The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 9.0-RELEASE, 9.1-BETA1, 9.1-RC1, or 9.1-RC2 can upgrade as follows: # freebsd-update upgrade -r 9.1-RC3 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 7.X, 8.X) can also use freebsd-update to upgrade to FreeBSD 9.1-RC3, 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 7.X or FreeBSD 8.X and FreeBSD 9.X. Checksums: SHA256 (FreeBSD-9.1-RC3-amd64-bootonly.iso) = 86d57e699ae0e298a420ff168e6abe7b715e6dee8350149ed2f230885b1973ec SHA256 (FreeBSD-9.1-RC3-amd64-disc1.iso) = 11c7e4ab16294794bf950073901f9a4dc8f735de08b02a321b63c4702af60f98 SHA256 (FreeBSD-9.1-RC3-amd64-memstick.img) = ccd983a7e1f37c0bb4b87c6cacc3945d38be8add66ea0689c0b8e0a72c75ad58 MD5 (FreeBSD-9.1-RC3-amd64-bootonly.iso) = 278a0ee9e00dba88068f1ad1c509429c MD5 (FreeBSD-9.1-RC3-amd64-disc1.iso) = 78ea831eaf495e2f713d5cd5ffc5f083 MD5 (FreeBSD-9.1-RC3-amd64-memstick.img) = f37c7ff68025bc065465d3d647b6e7e0 SHA256 (FreeBSD-9.1-RC3-i386-bootonly.iso) = 8b944a3b263de04db2e0cb38b068a4ceca6e2fe4f8af5344567696e09b7df66a SHA256 (FreeBSD-9.1-RC3-i386-disc1.iso) = e7c19e2aadb0c6ce072265511d84fd0d39c6e60628231d8dc31023d410e285d6 SHA256 (FreeBSD-9.1-RC3-i386-memstick.img) = 1ebb2ebf6b20376df7c3719f5b1bbbdd47ae2054e3a23019d8fdc93734f78fe5 MD5 (FreeBSD-9.1-RC3-i386-bootonly.iso) = f14703b350e7f2357d23250c64ef MD5 (FreeBSD-9.1-RC3-i386-disc1.iso) = 13405032579c52182bedfcd84a294871 MD5 (FreeBSD-9.1-RC3-i386-memstick.img) = 515d0866470d2edd1d99867e83387c35 SHA256 (FreeBSD-9.1-RC3-powerpc64-bootonly.iso) = b46212dc2fa3308fc58465bb999b4ec857245826fd1cb122af758e8b340afaf4 SHA256 (FreeBSD-9.1-RC3-powerpc64-memstick) = bfda2bf019eb4c540d280608a81ba9d67402ab0248c38c33badb4548e725f657 SHA256 (FreeBSD-9.1-RC3-powerpc64-release.iso) = b5e0948df8d7f62a7e620647d90c3c47f89ad71cf310277d86ef139c8ba25961 MD5 (FreeBSD-9.1-RC3-powerpc64-bootonly.iso) = d474edb9aac9aa5e9ad226a1e345cbd9 MD5 (FreeBSD-9.1-RC3-powerpc64-memstick) = aa443c1ae88773cc6c0a070ca2c6784f MD5 (FreeBSD-9.1-RC3-powerpc64-release.iso) = 237aaf75f2f6b2192cf0e1f51c190dc8 SHA256 (FreeBSD-9.1-RC3-sparc64-bootonly.iso) = e1d61b01ba8d03c324f0a828527741542fd0b337d3281b1f943658f5f482ae9e SHA256 (FreeBSD-9.1-RC3-sparc64-disc1.iso) = 9b59c368f0572198ef9562c7f52a45ca33aa832d607c6331bd4ca796c5ca4d8f MD5 (FreeBSD-9.1-RC3-sparc64-bootonly.iso) = e3e10bc7ce2a0377053cb2d7eff22538 MD5 (FreeBSD-9.1-RC3-sparc64-disc1.iso) = ab754ee5361a4c9b8d451b0eee080732 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 9.1-RC2 Available...
) = 6fe6c7abf12bf6eafbefb4db03d2dcccd6af6bbd12311da1cf4fd821d4965219 SHA256 (FreeBSD-9.1-RC2-powerpc64-memstick) = 3218173781294b089a10ec65386ac140a78c7a9908e0912fe88ffc2df3317a66 SHA256 (FreeBSD-9.1-RC2-powerpc64-release.iso) = 03659f3493a79519ad31d8e19c4ac50755e58c573f9596244284b2d7ff70cc42 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 9.1-RC1 Available...
On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote: On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. Assuming the stupid question is the one you didn't ask, just to clarify: does this mean that c*sup won't work with these RCs in particular, or that CVS is dead and SVN becomes mandatory from 9.1-RELEASE? cheers, Ian The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 9.1-RC1 Available...
The first release candidate of the 9.1-RELEASE release cycle is now available on the FTP servers for amd64, i386, and powerpc64. The MD5/SHA256 checksums are at the bottom of this message. The ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.1/ (or any of the FreeBSD mirror sites). Current plans are for there to be one more RC build, followed by the release itself. The current target schedule is here: http://www.freebsd.org/releases/9.1R/schedule.html If you notice any problems you can report them through the normal Gnats PR system or here on the -stable mailing list. With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 9.0-RELEASE can upgrade as follows: # freebsd-update upgrade -r 9.1-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 7.X, 8.X) can also use freebsd-update to upgrade to FreeBSD 9.1-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 7.X or FreeBSD 8.X and FreeBSD 9.X. Checksums: MD5 (FreeBSD-9.1-RC1-amd64-bootonly.iso) = 370b1c7b5a816289c6822f577fbf59d5 MD5 (FreeBSD-9.1-RC1-amd64-disc1.iso) = a6d6bd8c47509e71af2b74a39d1ed6be MD5 (FreeBSD-9.1-RC1-amd64-memstick.img) = 320bbcb382bd335e835636278cdb168d MD5 (FreeBSD-9.1-RC1-i386-bootonly.iso) = 0e3bf9d6f233b0502bac54b45d8a8fe9 MD5 (FreeBSD-9.1-RC1-i386-disc1.iso) = 2d911a7c7e3ed6f93bf0a03d0696aab7 MD5 (FreeBSD-9.1-RC1-i386-memstick.img) = 64608c316269f38390501b331b954b44 MD5 (FreeBSD-9.1-RC1-powerpc64-bootonly.iso) = 4ea17dc932dad7632d7bea70af5e16a7 MD5 (FreeBSD-9.1-RC1-powerpc64-memstick) = f28d44cd7fec655d6944cdeabeca2d6c MD5 (FreeBSD-9.1-RC1-powerpc64-release.iso) = 08742f914353300917c92b339728b80e SHA256 (FreeBSD-9.1-RC1-amd64-bootonly.iso) = f080e8c7cecd9bb44240a52e17827a94ad178f040b16526d339c8d0f2f1cdfd7 SHA256 (FreeBSD-9.1-RC1-amd64-disc1.iso) = 27bc85ec853f590f19ece8ddd672d62bfe58f6d8de874afd71958bd42b48f8c9 SHA256 (FreeBSD-9.1-RC1-amd64-memstick.img) = d8312855a32dba9b22fd208c2426d136640421ccca459ce429f8a70edee9398c SHA256 (FreeBSD-9.1-RC1-i386-bootonly.iso) = 1c8c555aa700d2b3bda77748436a1a6c2497521aae0974a7cd97451a27a9e3e4 SHA256 (FreeBSD-9.1-RC1-i386-disc1.iso) = f16a310fe80a01555f5d3dd108bae3b8e08d01db18d7dd7d4e70e13f0bc0a7a8 SHA256 (FreeBSD-9.1-RC1-i386-memstick.img) = 0799b8efd6f8678c474fe8048a265e21b487665f70c6e4172087e3c76b28a798 SHA256 (FreeBSD-9.1-RC1-powerpc64-bootonly.iso) = e183acb6cbb5cdbba3b3830e773c4e49ecb315eb07bde5d91d2e9595ba679d5f SHA256 (FreeBSD-9.1-RC1-powerpc64-memstick) = afc19a57f8d7e8b8a49f863f817221d7639f1b78288cdb0a7b8ffa5b60632d64 SHA256 (FreeBSD-9.1-RC1-powerpc64-release.iso) = 71c8a2965ff1198894e84ce0260e801b9e7f234c560bbbe95bf49274d399166d -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 9.1-BETA1 Available...
The first test build of the 9.1-RELEASE release cycle is now available on the FTP servers for amd64, i386, powerpc64, and sparc64. The MD5/SHA256 checksums are at the bottom of this message. The ISO images and, for architectures, that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.1/ (or any of the FreeBSD mirror sites). We hope this will be the only BETA build, to be followed by two Release Candidate builds and then the release itself. The original schedule is available here: http://www.freebsd.org/releases/9.1R/schedule.html but we're a bit behind schedule already. I'll adjust the schedule within the next couple of days. If you notice any problems you can report them through the normal Gnats PR system or here on the -stable mailing list. If you would like to use csup/cvsup mechanisms to do a source-based update of an existing system the branch tag to use is RELENG_9. If you would like to use SVN instead use stable/9. Note that if you do an update that way the system will call itself 9.1-PRERELEASE. Checksums: MD5 (FreeBSD-9.1-BETA1-amd64-bootonly.iso) = ff296912b6b4135476d3012ff020a55e MD5 (FreeBSD-9.1-BETA1-amd64-disc1.iso) = 60c82350efa8a45cb6376fcefe4e1c84 MD5 (FreeBSD-9.1-BETA1-amd64-memstick.img) = 2baf4398cbcdd733cbef381b78fc1d88 MD5 (FreeBSD-9.1-BETA1-i386-bootonly.iso) = 483f2efb2ed46ded418a404d47bdf98d MD5 (FreeBSD-9.1-BETA1-i386-disc1.iso) = 244e526aa109b1dbbe1a0f25d40de4bf MD5 (FreeBSD-9.1-BETA1-i386-memstick.img) = 98f687ad1ef71b1bf3c8b82362b9bf49 MD5 (FreeBSD-9.1-BETA1-powerpc64-bootonly.iso) = 9dd0c70d52fab38a87d5fc01eb078af1 MD5 (FreeBSD-9.1-BETA1-powerpc64-memstick) = 4c4ec197755d5732788fc1c11d6baf7d MD5 (FreeBSD-9.1-BETA1-powerpc64-release.iso) = 44cbe2ea14e41cc23ee633cb8e619730 MD5 (FreeBSD-9.1-BETA1-sparc64-bootonly.iso) = f7cb375c6d941d62abd8260e6ce42d3d MD5 (FreeBSD-9.1-BETA1-sparc64-disc1.iso) = aa450e7772e09bfa79d6d19be6a0fba5 SHA256 (FreeBSD-9.1-BETA1-amd64-bootonly.iso) = babf94070c798e06d93923fa84e5d1c1fa37ab4bef7959d68c73bf40d1568418 SHA256 (FreeBSD-9.1-BETA1-amd64-disc1.iso) = f895c688dac933e13bfaa4c02ed73ac2e21752b257693cbbe416077fdf255331 SHA256 (FreeBSD-9.1-BETA1-amd64-memstick.img) = 977fa2772a86156c2c61f2b80173b15b95ebcf38f9ad5a7d2b78727f5bf13d0b SHA256 (FreeBSD-9.1-BETA1-i386-bootonly.iso) = 353ff599a55af0664f52ecaa8c7b5f497b94a9d3e043dc616107b5ddf46e53f2 SHA256 (FreeBSD-9.1-BETA1-i386-disc1.iso) = 29c36dfab60261f0823ca5620e838f8347a267d40af0b56f4d5a881c559cf2c2 SHA256 (FreeBSD-9.1-BETA1-i386-memstick.img) = 1b14bd8bd47be80bf3cb8b63e3ee27d74d00cb32a4c5203ee9fabef39a58d3a7 SHA256 (FreeBSD-9.1-BETA1-powerpc64-bootonly.iso) = e9deebc21bd815fd61162a419bcb01bd6c2ca254f8268c4858f168af5add3f58 SHA256 (FreeBSD-9.1-BETA1-powerpc64-memstick) = bda64320367c1ef5dac1a3e24d3f20979908cb7e23f0a80f17433b41f6a04601 SHA256 (FreeBSD-9.1-BETA1-powerpc64-release.iso) = 7171c7a1c14f06644ab6706af8afd0a0b8330bd32ce71d01d823aae8bdf90b73 SHA256 (FreeBSD-9.1-BETA1-sparc64-bootonly.iso) = c6a869beeb2d5afab8a93363c34c434751bf4252cc798e940bd1cb74786a14b4 SHA256 (FreeBSD-9.1-BETA1-sparc64-disc1.iso) = 5b04e7989d8ab26ad788f989009e2f5a493858e3b4e67256d3774e68e0073431 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
WARNING: stable/9 - 9.1-BETA1...
Through time we learned to try and avoid ever having a stable branch call itself BETA-anything. The reality is during every release the BETA builds do get built from what's in the stable branch (we typically don't create the releng/* branches until we hit the RC phase). But past experiences have shown us that not everybody knows that, and/or aren't paying attention to the fact a release is under way. And sorry to be so blunt but... Some people really freak out when they see BETA in anything. So, despite stable branches actually being what BETA builds get built from in the past we've avoided having BETA appear in the source code repositories. Instead we have named it PRERELEASE, and used a build knob to have the release build call itself the BETA. The new build infrastructure that got phased in as part of 9.0 doesn't have that build knob. So, I'm about to do what we've tried to avoid before which is do a commit that makes stable/9 call itself 9.1-BETA1. After we complete the BETA1 builds (likely 2 to 3 days for all of them to complete) I'll shift stable/9 to PRERELEASE and it should stay that way until the release process is over (the next scheduled build is RC1 and we'll create releng/9.1 as part of doing that...). -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
9.1-RELEASE target schedule
Just a quick note to say we have settled on a target schedule for the FreeBSD 9.1 Release. The schedule itself is here: http://www.freebsd.org/releases/9.1R/schedule.html The highlights: Code Freeze:July 2nd, 2012 BETA1: July 6th, 2012 RC1:July 20th, 2012 RC2:August 3rd, 2012 Release:August 13th, 2012 Those are the target dates for when builds start. The builds becoming available is usually a few days afterwards (except for the final release which is often times 4 days to a week after the builds start because there is more prep work involved...). Thanks. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
8.3-RC2 Available...
) = 8a1852a9178de99cfec6a8acfa72af94052fa8cf6021d71e2aee5c16771b16ef SHA256 (FreeBSD-8.3-RC2-i386-memstick.img) = 6078745475b88d51e65eb3602e97b2375d31e5d3eeb0c25cf7e9404c363222e7 SHA256 (FreeBSD-8.3-RC2-pc98-bootonly.iso) = 2c31c8bafeb75f4531a96a6adc3bb4eb4286cd362145538fcf25ff92df1c89ae SHA256 (FreeBSD-8.3-RC2-pc98-disc1.iso) = f86e102241828ef1f89f63f266470db13bd28ed3444e8931f1e8ddc9ab497ba0 SHA256 (FreeBSD-8.3-RC2-pc98-livefs.iso) = cb6ff8fd8c7c219c081d9dbd8faf44b5271d444ad4ca083e1302f72bd7d0819a SHA256 (FreeBSD-8.3-RC2-sparc64-bootonly.iso) = 6c2b79a02e9a05adbbd2c69decc79323a3c63cd98af5e6e313e76e6ad734e238 SHA256 (FreeBSD-8.3-RC2-sparc64-disc1.iso) = 181580752916ee5be6a277e201e372f7a082da6d4bd6162efd80b406a1f43ba3 SHA256 (FreeBSD-8.3-RC2-sparc64-dvd1.iso) = 1e87d7fd75747539c4b921a3426438701d091b36ea85d88054d3b7859807358b SHA256 (FreeBSD-8.3-RC2-sparc64-livefs.iso) = 518910b4094a37c0af2eb3b6f20b218e9ca67736b3b54a078fea30b1a84901f2 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 8.3-RC1 Available...
The first Release Candidate build of the 8.3-RELEASE release cycle is now available on the FTP servers for the amd64, i386, and pc98 architectures. The MD5/SHA256 sums are at the bottom of this message. The ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/8.3/ (or any of the FreeBSD mirror sites). We hope to have one more Release Candidate build, followed by the release itself. The schedule is available here: http://www.freebsd.org/releases/8.3R/schedule.html and so far we're not too far off. If you notice any problems you can report them through the normal Gnats PR system or here on the -stable mailing list. If you would like to use csup/cvsup mechanisms to do a source-based update of an existing system the branch tag to use is now RELENG_8_3. If you would like to use SVN instead use releng/8.3. As part of preparing for RC1 releng/8.3 was branched. The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 8.1-RELEASE, 8.2-RELEASE, or 8.3-BETA1 can upgrade as follows: # freebsd-update upgrade -r 8.3-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 7.x) can also use freebsd-update to upgrade to FreeBSD 8.3-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 7.x and FreeBSD 8.x. Checksums: MD5 (FreeBSD-8.3-RC1-amd64-bootonly.iso) = d3fee39afba719d0f47c0eea881a84ad MD5 (FreeBSD-8.3-RC1-amd64-disc1.iso) = cb38356833f43998510c5b496eac7917 MD5 (FreeBSD-8.3-RC1-amd64-dvd1.iso) = 043901211a0730242df482d83794c6fc MD5 (FreeBSD-8.3-RC1-amd64-livefs.iso) = 76a1c13fe4af6a9845e8ea13069a97d6 MD5 (FreeBSD-8.3-RC1-amd64-memstick.img) = a6b74511a2edccd98407c464b8781681 MD5 (FreeBSD-8.3-RC1-i386-bootonly.iso) = b3e9d11a41f54487f0ef077cb8f517ec MD5 (FreeBSD-8.3-RC1-i386-disc1.iso) = 2d3ddbe3c7256bc9df67b06a33e8be48 MD5 (FreeBSD-8.3-RC1-i386-dvd1.iso) = 2df8cf3af608afa983aa667e54a8de43 MD5 (FreeBSD-8.3-RC1-i386-livefs.iso) = e03f18a0a2c05b32692501e7012ed52f MD5 (FreeBSD-8.3-RC1-i386-memstick.img) = c46fe4e008edece737e7a31a076bff2a MD5 (FreeBSD-8.3-RC1-pc98-bootonly.iso) = 9de8c5e4dc516740af4dd2aa6cde759f MD5 (FreeBSD-8.3-RC1-pc98-disc1.iso) = c24d2270a8a9e8685ac82e096a131246 MD5 (FreeBSD-8.3-RC1-pc98-livefs.iso) = 80905bdfe7bd89a04068e0344d791ec4 SHA256 (FreeBSD-8.3-RC1-amd64-bootonly.iso) = d47d63b59465ac0254e770e6e3fa5a3959895dedce130250f26848306439d55d SHA256 (FreeBSD-8.3-RC1-amd64-disc1.iso) = 38b08f12f0b3e83045e46b7f09404a2f36e26f7e3c668bc4a01b8383ab72c48a SHA256 (FreeBSD-8.3-RC1-amd64-dvd1.iso) = 535547adcab0ff8cceb778674151323da015aefc6d8b36337d85f62a4fad87bc SHA256 (FreeBSD-8.3-RC1-amd64-livefs.iso) = 600b26d6c15946c88ffc516d3cce57eb2ee48149f8af96e9124ca478901e8a5c SHA256 (FreeBSD-8.3-RC1-amd64-memstick.img) = 53218723e35deba522bfbd87d8d5e1451705f6f386f2b004468190ae89fd0bc1 SHA256 (FreeBSD-8.3-RC1-i386-bootonly.iso) = 5c37eb5124fb057384d5828e8cc1e116f0b9c0a7efe6f3365f59ba87a50be83c SHA256 (FreeBSD-8.3-RC1-i386-disc1.iso) = 1fec8dc68433c12a9b24da1b7e35a6d4e6bb96cb1258fb809111572d1b16ebb9 SHA256 (FreeBSD-8.3-RC1-i386-dvd1.iso) = ec2f7f7c38d22726fcd9c95d4d7699068eeddbaa2b60eb235373a2eadd792931 SHA256 (FreeBSD-8.3-RC1-i386-livefs.iso) = 7a75e051ef26571621d2782f42e30d9f0f6552cbd8f0dfdb5dd9d6d2da853500 SHA256 (FreeBSD-8.3-RC1-i386-memstick.img) = 966ff5e1e9e561395083ebce110a6e9c07778a6e05f689bb94451efecaa15bf4 SHA256 (FreeBSD-8.3-RC1-pc98-bootonly.iso) = 0866dc444b92e5a03ad90da8e87f49e184aead6e2148af1f3cc35d4c74e14b35 SHA256 (FreeBSD-8.3-RC1-pc98-disc1.iso) = 5f6521693b1d0cf6b89af6783035afb58c75fb2be9e4b6c064b13c5e584bdcd0 SHA256 (FreeBSD-8.3-RC1-pc98-livefs.iso) = f1f6237364819a34f522f4d740e5c37db4bcd03cc254cf531584e3c5f7d59ac5 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 8.3-BETA1 Available...
The first BETA build of the 8.3-RELEASE release cycle is now available on the FTP servers for the amd64, i386, and pc98 architectures. The MD5/SHA256 sums are tacked on to the bottom of this message. The ISO and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/8.3/ (or any of the FreeBSD mirror sites). 8.3-BETA1 images have also been published for Amazon EC2. Since the stable/8 branch is relatively mature we hope there will only be one BETA build for this release cycle. If testing does not turn up any show-stopper caliber problems the next test build will be RC1. If you notice problems you can report them through the normal Gnats PR system or here on the -stable mailing list. If you would like to use csup/cvsup mechanisms to do a source-based update of an existing system the branch tag to use is RELENG_8. If you would like to use SVN instead use stable/8. The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 8.1-RELEASE or 8.2-RELEASE can upgrade as follows: # freebsd-update upgrade -r 8.3-BETA1 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 7.x) can also use freebsd-update to upgrade to FreeBSD 8.3-BETA1, 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 7.x and FreeBSD 8.x. Checksums: MD5 (FreeBSD-8.3-BETA1-amd64-bootonly.iso) = 7388a064ca3b0bc940689ba19e69cd6d MD5 (FreeBSD-8.3-BETA1-amd64-disc1.iso) = 27a802d54dc5bf7fa4048ee8aec99670 MD5 (FreeBSD-8.3-BETA1-amd64-dvd1.iso) = 231339687c8e0830b4bf94330dc6f1a2 MD5 (FreeBSD-8.3-BETA1-amd64-livefs.iso) = 006ef033296c7af3c0742a9740ff57c8 MD5 (FreeBSD-8.3-BETA1-amd64-memstick.img) = b366d83103944347a1334ea840864a90 MD5 (FreeBSD-8.3-BETA1-i386-bootonly.iso) = 5f4706c8bd618eaba404aa870dd7d5f7 MD5 (FreeBSD-8.3-BETA1-i386-disc1.iso) = e8772d8cc14eab349f061dc635f9e668 MD5 (FreeBSD-8.3-BETA1-i386-dvd1.iso) = f958c31608eed50a280e4330840b6c84 MD5 (FreeBSD-8.3-BETA1-i386-livefs.iso) = b5c86e5f1d71166d440323be7a846254 MD5 (FreeBSD-8.3-BETA1-i386-memstick.img) = d4fb497ceb71350ae601b5c8b7cc8304 MD5 (FreeBSD-8.3-BETA1-pc98-bootonly.iso) = 9b5b97c805cbdd74198523cb62db50c8 MD5 (FreeBSD-8.3-BETA1-pc98-disc1.iso) = 120117ba0ff961c6c6e1fbecc2981b80 MD5 (FreeBSD-8.3-BETA1-pc98-livefs.iso) = 8cd151d1a81c8c3b589214a8650ace61 SHA256 (FreeBSD-8.3-BETA1-amd64-bootonly.iso) = 8ce4221a7cffdf253ec5ccfec986ab4a7bbd5b15a628358087557a11c27dc7ae SHA256 (FreeBSD-8.3-BETA1-amd64-disc1.iso) = b9aa0aca927adb3b0fc552039ccc0814d0334c6b4036ce94423c92c240abc0dc SHA256 (FreeBSD-8.3-BETA1-amd64-dvd1.iso) = ac007c1c68cb3509d148361a2f4416950d065bd0769843232f478074bb6dad33 SHA256 (FreeBSD-8.3-BETA1-amd64-livefs.iso) = 0255be23addea15cdc04fc0a6e68ddf522ca7b414825fcf0dc26ccd88f361be6 SHA256 (FreeBSD-8.3-BETA1-amd64-memstick.img) = a50b3816aa92e07199b6f21488a20cb8a21ba15fb5fc6daff1d28511945676d4 SHA256 (FreeBSD-8.3-BETA1-i386-bootonly.iso) = a74e7427ee770f37b91a5087e636d5fff069ef1ec6e40971b9eee7f0f780d129 SHA256 (FreeBSD-8.3-BETA1-i386-disc1.iso) = 7994fe9293b8b5baab164cd985722b9392adc18471056bc24d75f63699ac SHA256 (FreeBSD-8.3-BETA1-i386-dvd1.iso) = e77903e9920d7b5231a1ac11e9e7edc9938e8ff2f72f2e15a158f952b4561723 SHA256 (FreeBSD-8.3-BETA1-i386-livefs.iso) = ea175a30dce0071c5f3e25d5bb73c467f4c143a55d367eb873922c91e11c703e SHA256 (FreeBSD-8.3-BETA1-i386-memstick.img) = a2d093be060a0f09a6c11376b2fb27fa38ebaf9892b30e771b465370230f50c0 SHA256 (FreeBSD-8.3-BETA1-pc98-bootonly.iso) = d353ae427f610c9d8346cbddbc2c5bae9a0b5929f4767041f0fe1b6f397a122c SHA256 (FreeBSD-8.3-BETA1-pc98-disc1.iso) = ff54d85eb982b64b3665a3b940be80447b9732f013f5997a78638ab74ee85bee SHA256 (FreeBSD-8.3-BETA1-pc98-livefs.iso) = a7a99525552c0771d84fdbdea49431e482ab854e327fe02b84d271eb5757dead -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
stable/8 - 8.3-PRERELEASE...
Just a quick note to say we have entered code freeze for the 8.3-RELEASE release cycle. As of a few minutes ago stable/8 will identify itself as 8.3-PRERELEASE. The target schedule for the release is available here: http://www.freebsd.org/releases/8.3R/schedule.html Thanks. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Schedule for 8.3-RELEASE...
Just a quick note to say the target schedule for 8.3-RELEASE has been set and is available here: http://www.freebsd.org/releases/8.3R/schedule.html The summary of the target dates is: Code Freeze:Feb 15, 2012 BETA1 builds: Feb 17, 2012 RC1 builds: Mar 2, 2012 RC2 builds: Mar 16, 2012 REL builds: Mar 23, 2012 The Security Officer has pushed back the estimated End of Life for 8.2-RELEASE to July 31, 2012. That will give three months between the release of 8.3-RELEASE and the EoL for 8.2-RELEASE. It is expected that 8.3-RELEASE will be an Extended Support release. See: http://www.freebsd.org/security/#sup for the full details of the currently supported releases. Thanks. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: dumpdev default
On Tue, 2012-01-17 at 18:37 +1100, Aristedes Maniatis wrote: The manual states that dumpdev AUTO is the default as of FreeBSD 6.0 [1] However: # uname -a FreeBSD xx 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # grep dumpdev /etc/defaults/rc.conf dumpdev=NO # Device to crashdump to (device name, AUTO, or NO). savecore_flags= # Used if dumpdev is enabled above, and present. It looks like NO is still the default. Is there a reason why this should not be turned on even for production machines? I haven't read about any side effects, but it seems to be off by default for some reason. Please cc me on any responses since I'm not currently subscribed. Cheers Ari If you use bsdinstall(8) to install a machine from scratch it explicitly asks you about whether you want crash dumps enabled or not. As long as you're aware that the crash dumps are happening and know that you might need to clean up after them (remove stuff from /var, etc) there are no dangers. You just need to make sure wherever the crash dumps will wind up going (/var by default) has enough space to handle both the crash dumps and anything else the machines need to do. We currently have no provision for preventing crash dumps from filling up the target partition. I keep advocating for the conservative side of this issue, preferring that crash dumps be an opt-in setting until we have infrastructure in place to prevent them from filling the target partition. I still picture there being people out there who don't know what crash dumps are, wouldn't know they might need to clean up after them, and may be negatively impacted if the target partition wound up full without them knowing why. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: FYI: 9.0-RELEASE announced...
On Fri, 2012-01-13 at 15:20 +0100, Claude Buisson wrote: On 01/13/2012 00:54, Ken Smith wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 JFYI for those of you who aren't subscribed to the announce@ mailing list... 9.0-RELEASE is, finally, announced. The announcement message is available here: http://www.freebsd.org/releases/9.0R/announce.html snip.. Do we have a chance of finding somewhere the RELNOTES.TXT, etc or do we have to build them ourself ?? Claude Buisson The announcement message provides this link for that: http://www.freebsd.org/releases/9.0R/relnotes.html There are a few other links in the announcement message that you might also want to take a look at. I didn't want to re-post the whole thing here. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: FYI: 9.0-RELEASE announced...
On Fri, 2012-01-13 at 16:14 +0100, Claude Buisson wrote:
On 01/13/2012 15:50, Ken Smith wrote:
On Fri, 2012-01-13 at 15:20 +0100, Claude Buisson wrote:
On 01/13/2012 00:54, Ken Smith wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
JFYI for those of you who aren't subscribed to the announce@ mailing
list... 9.0-RELEASE is, finally, announced. The announcement message
is available here:
http://www.freebsd.org/releases/9.0R/announce.html
snip..
Do we have a chance of finding somewhere the RELNOTES.TXT, etc or do we
have
to build them ourself ??
Claude Buisson
The announcement message provides this link for that:
http://www.freebsd.org/releases/9.0R/relnotes.html
There are a few other links in the announcement message that you might
also want to take a look at. I didn't want to re-post the whole thing
here.
This is NOT an answer to my question.
To be more precise: it WAS usual to find on the ftp mirrors the documents
RELNOTES.{HTM,TXT}, for immediate consumption without having to search the web
site. Furthermore the TXT documents could be read without having to use a
browser. I did not found any of these documents on the ftp mirrors.
I also note that the document relnotes-detailed.html have the date
2012-01-12
05:51:11Z and the files on the ftp site are at best dated from Jan 06, so I
doubt they contain an uptodate version of the release documentation.
I KNOW I am an old tart, but please try to understand the question before
answering.
Claude Buisson
Sorry, I hadn't intended to be offensive or passive aggressive or
whatever. To me your reference to somewhere included the possibility
of the web so you're right that I didn't understand your question but
that was why...
Looks like you need to build them yourself. Though doing that for 9.0
won't be useful I'm afraid. The release notes were not ready at the
point we started up the release builds so the online versions are the
only ones that have any useful information in them.
--
Ken Smith
- From there to here, from here to | kensm...@buffalo.edu
there, funny things are everywhere. |
- Theodor Geisel |
signature.asc
Description: This is a digitally signed message part
FYI: 9.0-RELEASE announced...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 JFYI for those of you who aren't subscribed to the announce@ mailing list... 9.0-RELEASE is, finally, announced. The announcement message is available here: http://www.freebsd.org/releases/9.0R/announce.html Lots of you noticed that the 9.0-RELEASE ISO and memstick images appeared on the FTP sites a while ago. But as pointed out this release turned out to be an example of why the official policy is that it's not truly released until the announcement email gets sent out. I had not tested using sysinstall(8) to install pre-built packages from the DVD during my initial testing since we're sorta moving away from sysinstall(8). I had just tested installing the pre-built packages using pkg_add(8). Someone noticed sysinstall(8) misbehaved before I got the images put up on Bittorrent and the fix was simply adding one file to the DVD image that the new build infrastructure omitted since bsdinstall(8) doesn't use it. So I went ahead with replacing the DVD images on the FTP site. That's also why we waited longer than normal between the images appearing on the FTP sites and the announcement - we gave extra time to try and make sure the updated images got to all the FTP mirrors. Sorry about the screw-up. If you downloaded the amd64 and/or i386 DVD images before now you might want to check the checksums with the ones posted in the release announcement. The fix to make sysinstall(8) happy about installing from the DVD images was the *only* change made to the updated images. The bad images were never available via Bittorrent so if you got the images that way you wouldn't have a bad image. On behalf of the Release Engineering Team and the FreeBSD Developers we hope you enjoy 9.0-RELEASE. - -- Ken Smith - - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8PcpsACgkQ/G14VSmup/aLFgCfar7x43ViPu44M3eF8MzvYhOU /z0AnRN1jXDT1fS0UA9J0Trd5sRQcwdy =oU1m -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: why is pkg_add on 9.0 stable still using packages from packages-9-current?
On Fri, 2012-01-06 at 19:37 +, miyamoto moesasji wrote: Thanks for the response Peter. Still seems strange that this change has not been made, but I'll indeed set it manually for now. Sorry for the delay cleaning that up. It should be fixed as of r229748. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 9.0-RC3 Available...
) = 5484765d3373c59372cdb53bbea2ab2d MD5 (FreeBSD-9.0-RC3-ia64-release.iso) = 7791f810dbe7d1ee7cf30510f0981424 MD5 (FreeBSD-9.0-RC3-powerpc-bootonly.iso) = 97a947ccd413371e24cfc83971bfd83a MD5 (FreeBSD-9.0-RC3-powerpc-memstick) = 2ebbdb2379d1f0e1a24a5ac31f22cf6f MD5 (FreeBSD-9.0-RC3-powerpc-release.iso) = e6c38096826b015eaa63a8109b809250 MD5 (FreeBSD-9.0-RC3-powerpc64-bootonly.iso) = 360383e1d7fca3d93be73f5aa8ce085c MD5 (FreeBSD-9.0-RC3-powerpc64-memstick) = 4b74c2d73b56f5f38590b0da2cf64054 MD5 (FreeBSD-9.0-RC3-powerpc64-release.iso) = 3e6e9519b3debb61047491ee700f683b MD5 (FreeBSD-9.0-RC3-sparc64-bootonly.iso) = 8f352714c2c4228623239491aee88e6a MD5 (FreeBSD-9.0-RC3-sparc64-disc1.iso) = b51648c80862f54d230cf13b4a34604b SHA256 (FreeBSD-9.0-RC3-amd64-bootonly.iso) = 06d609bb0d927b64221f1207542794870b56538fd3983355c9013d1f17fe7382 SHA256 (FreeBSD-9.0-RC3-amd64-disc1.iso) = 16792eb1e90070b8c5d1ea8df55b290534efba1543fb37950f8c7acd61839208 SHA256 (FreeBSD-9.0-RC3-amd64-memstick.img) = ae533e43e2390c5992c83acebfee35636baaa0694b7f1bae973fd4547a4e97ee SHA256 (FreeBSD-9.0-RC3-i386-bootonly.iso) = 88f417817eec36e183fdb832720664956486ac169fb5528e93423e4ccd52ba61 SHA256 (FreeBSD-9.0-RC3-i386-disc1.iso) = cdbf1ce5668444c88ea141bfaec0bd414c09b39969076915d2d9257c9f0802f2 SHA256 (FreeBSD-9.0-RC3-i386-memstick.img) = ea6e4ce993bc534a05d247bd65ccf2a41e5e12cd36c75ca2a2dfdf0d77e996b5 SHA256 (FreeBSD-9.0-RC3-ia64-bootonly.iso) = cebb6bacde53bc4bc69f9048447107c38f69d6c655fcc5a7778dcae8c7387dc1 SHA256 (FreeBSD-9.0-RC3-ia64-memstick) = 46960b6567e3dcfea65dbeef107573f5147f2ec74d555d0aae19a81629cb2434 SHA256 (FreeBSD-9.0-RC3-ia64-release.iso) = a484ac6ac87e9a9c524cde453838a15aebffcc6b5811dbaf85b3b37691cea149 SHA256 (FreeBSD-9.0-RC3-powerpc-bootonly.iso) = a2a98542d9668b18ef10b85d0e10026e15e9c6991bc09d9fa070e6eed34a93bb SHA256 (FreeBSD-9.0-RC3-powerpc-memstick) = 0320db4828122ef851e1a26f28bd1eccf1b4e45d476fe23ec627c2daa559220b SHA256 (FreeBSD-9.0-RC3-powerpc-release.iso) = ee480650db05998560f26016bfcf2c392da8a3eae94bec49a162f9f655aaa3f9 SHA256 (FreeBSD-9.0-RC3-powerpc64-bootonly.iso) = 7bd60e65929fd70133a21f8517715b22d992a45a29c2677e4c7a66a226bc492a SHA256 (FreeBSD-9.0-RC3-powerpc64-memstick) = 3fab51275ddf71016d9422c6bfb0806c51b0243d79f9f5011f9f2f78a631a607 SHA256 (FreeBSD-9.0-RC3-powerpc64-release.iso) = d48ec66421b9f74b8c11212a6b9d5240b20629e0685e0ee3485233e28eb3cfcd SHA256 (FreeBSD-9.0-RC3-sparc64-bootonly.iso) = 739a9430198b91cac1d625bcde202447fc47addc92430a72080dce224c3b5c67 SHA256 (FreeBSD-9.0-RC3-sparc64-disc1.iso) = 18a63e0cb420694172f49f7ad5a209d40f348b19d3c96e8ecaeef8517b52cc22 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 9.0-RC2 Available...
) = 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 | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 9.0-RC1 Available...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/23/11 2:20 PM, Andrey Fesenko wrote: On Sun, Oct 23, 2011 at 7:43 AM, Ken Smith kensm...@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 Correct, sorry about the hyphen sneaking in. still no actual information on this page. Branch status not actual. I updated the dates. If by Branch Status you're referring to the section with that title it is actual. We've created stable/9 but not releng/9.0 yet. That might come with RC2, sorta depends on how much people find wrong with RC1. When releng/9.0 gets created it will take one commit and two merges to get fixes into 9.0-RELEASE which is a bit of a pain if there is a lot of activity. - -- Ken Smith - - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6kZMQACgkQ/G14VSmup/amiACgj1mmb1TG+39IlZzQzFRTIcKi mGYAn2kdMJ5A8HEK6wBhE2RgrQmRKLzr =/j9J -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 9.0-RC1 Available...
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 | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 9.0-BETA3 Available...
On Wed, 2011-10-12 at 14:39 +0100, Bruce Cran wrote: On 29/09/2011 02:42, Ken Smith wrote: MD5 (FreeBSD-9.0-BETA3-amd64-bootonly.iso) = 2ce7b93d28fd7ff37965893f1af3f7fc MD5 (FreeBSD-9.0-BETA3-amd64-dvd1.iso) = 4affc701f2052edc548274f090e49235 MD5 (FreeBSD-9.0-BETA3-amd64-memstick.img) = e260f2f2122326cb9a93ac83eb006c1c The -dvd1.iso files seem to be less than a CD, at 610MB. Are they expected to contain more data over time, or could 'dvd' be removed? I was planning on them having package sets. The new installer doesn't support installing packages like sysinstall had but if I provide Gnome, KDE, and perhaps a small set of other stuff it would be useful to people with crummy network connectivity. They could install the packages from the DVD instead of needing to have everything downloaded. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 9.0-BETA3 Available...
On Tue, 2011-10-04 at 22:40 +0400, Andrey Fesenko wrote: On Thu, Sep 29, 2011 at 5:42 AM, Ken Smith kensm...@buffalo.edu wrote: The 9.0-RELEASE cycle will be tracked here: http://wiki.freebsd.org/Releng/9.0TODO though the schedule listed there is still way off. We'll re-work the schedule some time soon. Last updated: 16 August 2011. :( Hit refresh... -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 9.0-BETA3 Available...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/4/11 3:39 PM, Arnaud Lacombe wrote: you've got to be fraking kidding me, aren't you ? Code freeze has happened, no date set. BETA-1, BETA-2 have been released, no date set. stable/9 has been created, no date set. Branch status has not been updated. I'll get to more of it later tonight. At most, this edit is a bad joke, just like politician announcing a few millions dollars in saving when the yearly budget is in deficit by trillions... Or an edit done in the 5 minutes I had at the time so people who wanted to know the times of things that haven't happened already can get what they want to know. For the record, I would have made a much better job, if you had let me. I'd love to know what you would have put for the dates I filled in. - -- Ken Smith - - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6LY4IACgkQ/G14VSmup/btJACaAr3xKoUNxkMpNt6YEhV+hPDo wzUAn3cv3sHsMwZRiPcZ5yRN917IJYR5 =j4kk -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 9.0-BETA3 Available...
-9.0-BETA3-sparc64-bootonly.iso) = 6eddeb18514d063d809e5b675413de43b6aa72815ebbe9f72fe548507f1e03cd SHA256 (FreeBSD-9.0-BETA3-sparc64-dvd1.iso) = 8b56423ed00cf9902366eeb7fd51bf13f8702af51a8c031fbf295f68ca5df484 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 9.0-BETA3 Available...
On Wed, 2011-09-28 at 21:42 -0400, Ken Smith wrote: If you would like to use csup/cvsup mechanisms to access the source tree the branch tag to use is now RELENG_8, if you use . (head) you will get 10-CURRENT. Sigh. Sorry. It's late... RELENG_9... -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 9.0-BETA2 Available...
SHA256 (FreeBSD-9.0-BETA2-amd64-memstick.img) = ac5e08a1a7ed4e6e8f19c18fcd53306e9ab5b4636c1b390e7fccf271e2ffbbcc SHA256 (FreeBSD-9.0-BETA2-i386-bootonly.iso) = e31ca81caa14866c2f3eb837b346f1b853ddb9181a9aa7b8d45915a0ebebbfd1 SHA256 (FreeBSD-9.0-BETA2-i386-dvd1.iso) = 2ed439c308c874deb17f20682fa3d24ab64452912a1408d1b8c4220c29ef2728 SHA256 (FreeBSD-9.0-BETA2-i386-memstick.img) = bb8d8151863784c4147ba4e62f073fcdd4c9b194b55470d3133f7504c2bad5c6 SHA256 (FreeBSD-9.0-BETA2-powerpc-bootonly.iso) = 64d7fc1b97a00118b577103d9882f14b98523716c24d01c6498cce5b8b555154 SHA256 (FreeBSD-9.0-BETA2-powerpc-memstick) = 0fd99234ad81687d90f9cbffb375bf938444ca41e5f090d0c1cf86ce5b373422 SHA256 (FreeBSD-9.0-BETA2-powerpc-release.iso) = fbe44a2665f68f45c86e8f99a5e569ed5f9905e38c6f516472bac58e8e742be6 SHA256 (FreeBSD-9.0-BETA2-powerpc64-bootonly.iso) = e8ab1ece6460080951dfb7bac9de9e80703b0ccf7f684e8be82fd5a32405b093 SHA256 (FreeBSD-9.0-BETA2-powerpc64-memstick) = f9778f2c8d85709e027ceaf9d8b1c99cae8719bee0a363a29b0e97594a6b6b85 SHA256 (FreeBSD-9.0-BETA2-powerpc64-release.iso) = 92a754150b17eb8567fa3b9dd306dbb96f2476075ab646ba90840aa733364b7c SHA256 (FreeBSD-9.0-BETA2-sparc64-bootonly.iso) = 0ef5b1b41683bfa9047bbd556a81466ed5aa4609335380d611e63ad2d8517f51 SHA256 (FreeBSD-9.0-BETA2-sparc64-dvd1.iso) = 00477eaf46f93678a28878d87c4551f529915266aee96cbb7141445503efce8d -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 9.0-BETA1 Available...
-bootonly.iso) = 7e4a8a24cd94d4fce60294d444525d9aea6c8d3e0ee55e6a9dda84a5ee9f SHA256 (FreeBSD-9.0-BETA1-powerpc64-memstick) = ec7eb9d6f5a69a0f3fbafd433ac309dcafd411921c4c51f2886c39649d59ca07 SHA256 (FreeBSD-9.0-BETA1-powerpc64-release.iso) = 2721be511db390a95ddf3081afd8152be14f147d5d8a8213c4045875631950e7 SHA256 (FreeBSD-9.0-BETA1-sparc64-bootonly.iso) = 3db8cf663cd1722488277c5c63f8daa2cd04a1e1aeb8bd54932cbc30d507bc3e SHA256 (FreeBSD-9.0-BETA1-sparc64-disc1.iso) = c051b5b9fad2e3183c595b3e7f786afb181bce91c7ce1c869a2c593ab9d29205 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: 8.2/7.4-RELEASEs Announced...
On Tue, 2011-03-01 at 10:26 +0100, Patrick Lamaiziere wrote: Le Thu, 24 Feb 2011 16:26:23 -0500, Ken Smith kensm...@buffalo.edu a écrit : Hello, 8.2-RELEASE and 7.4-RELEASE have been announced. The announcement messages are available here: http://www.freebsd.org/releases/8.2R/announce.html There is a small typo in the name of the usb image: « memstick This can be written to an USB memory stick (flash drive) and used to do an install on machines capable of booting off USB drives. It also supports booting into a livefs based rescue mode. The documentation packages are provided but no other packages. ... # dd if=8.2-RELEASE-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync » should be FreeBSD-8.2-RELEASE-amd64-memstick.img Enjoy. :-) Thanks! Regards. Hmm, it's right in the message sent to announce@ but not in the Web version. I had made that typo in previous announcements but corrected it with 8.2's announcement. I'll see if it can be fixed in the Web version. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: 8.2/7.4-RELEASEs Announced...
On Tue, 2011-03-01 at 02:05 -0800, Jeremy Chadwick wrote: Not to mention, the block size specified doesn't jibe with what's in the FreeBSD Handbook (which uses bs=64k): http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html Other users have pointed this out to me on my blog, wondering exactly where bs=10240 came from. So, the release notes going forward should probably use bs=64k. I'll try to remember to adjust that for 8.3. I started off suggesting the 10240 value because that's what gets used in the script that builds the memstick images (and the block size there is used for some mathematics to determine file sizes so a larger size would potentially waste more space...). But as people with less patience than me have noticed 64k results in a much faster transfer... ;-) -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
8.2/7.4-RELEASEs Announced...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just a quick note for those of you who are not subscribed to the freebsd-announce mail list... 8.2-RELEASE and 7.4-RELEASE have been announced. The announcement messages are available here: http://www.freebsd.org/releases/8.2R/announce.html http://www.freebsd.org/releases/7.4R/announce.html Enjoy. :-) - -- Ken Smith - - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1mzP8ACgkQ/G14VSmup/ZnuQCfc2N5EcvKele/VmpqkhzoWZwR 1oIAniNIyI2Zy+eVTJ3q4joEd7wHGZD6 =mc7p -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 8.2-RC3/7.4-RC3 Available...
(FreeBSD-7.4-RC3-amd64-disc3.iso) = 867fa6dbce8b226d3b20706e735f35980f3b955035396918b852aabc9166f15f SHA256 (FreeBSD-7.4-RC3-amd64-docs.iso) = 19298c50fd0dbf45e425a40b0f520333a0d5678b5e030a12af7e8307e5c68a27 SHA256 (FreeBSD-7.4-RC3-amd64-dvd1.iso) = 664ec0c3af35c2709b64d5378458bda9c8a05da5ee61153fd28ffd949602c517 SHA256 (FreeBSD-7.4-RC3-amd64-livefs.iso) = f56f2d6349edfb8fafa3c86cd3a92f876748a5dc2df4bec441714d78228584e2 SHA256 (FreeBSD-7.4-RC3-amd64-dvd1.iso.gz) = 2ccf57ede436b25a9aa7a0fee86e32b2006f479f78e21302f39a8aa23ac1a126 SHA256 (FreeBSD-7.4-RC3-i386-bootonly.iso) = 6c1c686023e58bda7631b7f0c4936a3f6e9c2d5a8938f991ce792a5b84018618 SHA256 (FreeBSD-7.4-RC3-i386-disc1.iso) = e4f806dac80aa7289c8279a858527f5bfa4e155060ad27d12869c9e9564d0ee9 SHA256 (FreeBSD-7.4-RC3-i386-disc2.iso) = 3bfbc4f75134288910f3086a1251a81b69856e1695ce9e634ed97fe9b5c5c831 SHA256 (FreeBSD-7.4-RC3-i386-disc3.iso) = 7d9122a81c4289ac958c008aee0d53f944e40b51f22afd1678cd53e4c08270df SHA256 (FreeBSD-7.4-RC3-i386-docs.iso) = b2ca66fa6f0389b8e418f11fcbc642ad40b3303e6525c27f481e53dd4e7bdfb4 SHA256 (FreeBSD-7.4-RC3-i386-dvd1.iso) = 45e01afbfc4f3d42039ecaee2a18a330de45f9a2f0b7a15a2e074d4f38a23fdf SHA256 (FreeBSD-7.4-RC3-i386-livefs.iso) = 88fb34780f560bae32e72a84eac2e76e6676987011619f83832ac614b20ebbc9 SHA256 (FreeBSD-7.4-RC3-pc98-bootonly.iso) = ea328faeae190ba7628bec1122f2a753127b5d2324c99746e28e106c45950567 SHA256 (FreeBSD-7.4-RC3-pc98-disc1.iso) = 770030f599b588206abd77ae5ffa67c77e2947fba42aa6b6b3ce08b8540965b8 SHA256 (FreeBSD-7.4-RC3-pc98-livefs.iso) = 34349b1f088a51b751eb4c5fa1720da799160628cd7d088489eccdb518976296 SHA256 (FreeBSD-7.4-RC3-sparc64-bootonly.iso) = 78e28fbd5b3dd34f6cae84eb7d0a1f6529407315dd51fec5add8be4018dd403f SHA256 (FreeBSD-7.4-RC3-sparc64-disc1.iso) = a74ea0ff65024a790dbae7b6a62eac6cc42e74816a4204437655d77963c30fec SHA256 (FreeBSD-7.4-RC3-sparc64-disc2.iso) = 388961c18c13cdf1f8cfac8007bf69b32247ce603ed154edc8b540a70731b1d4 SHA256 (FreeBSD-7.4-RC3-sparc64-disc3.iso) = cf02123db05efca4d7a7fc135de68e57736d18948855274ae606dfa6a7a1509c SHA256 (FreeBSD-7.4-RC3-sparc64-docs.iso) = 92cd47924f18bcb1049715bb9b93ae7d8f2736d6bcaa6b0e4d380e5567942735 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 7.4-RC2 Available...
) = 29251bd67b1689d780ba071da74d425a401853570c738c5652281f28d3c4945d SHA256 (FreeBSD-7.4-RC2-i386-disc1.iso) = c9a5b8feced4198f7b99b1e649d8e3e8e1581a26ee8080b1da91fd72b1564396 SHA256 (FreeBSD-7.4-RC2-i386-disc2.iso) = 754f05d4d59caa64a136839f070c504eee8d50a25e1f953fbaaff2c4ba04cd0f SHA256 (FreeBSD-7.4-RC2-i386-disc3.iso) = d8ab9eff61ae178a169a8d584ceaa93a82cc68382f380095581a77127a575fa4 SHA256 (FreeBSD-7.4-RC2-i386-docs.iso) = e67a7f590ae6a14309510786bebd7b40961809eab2e01bc8f2caec47a15858ba SHA256 (FreeBSD-7.4-RC2-i386-dvd1.iso) = 6e51df8d55370a0d4c65a3ae67aa7955a1c4da419f0d16ff1cf6e102dfa3efd3 SHA256 (FreeBSD-7.4-RC2-i386-livefs.iso) = 523a37fd3df04e39c72edf969d519689c8c3231452a2e9b24384837638ee2ead SHA256 (FreeBSD-7.4-RC2-pc98-bootonly.iso) = 617509694de1f06f40de0e6ad3219b5b8ac5949487b927fd21724ada755f3066 SHA256 (FreeBSD-7.4-RC2-pc98-disc1.iso) = 11109af6b06020f48f51c5d217aeb56e10b195028ac894345cabd3aeba5b3bc6 SHA256 (FreeBSD-7.4-RC2-pc98-livefs.iso) = 0a9101f14dab2600aa1ef25dbb3a44b428fa8e19246521c29d44fb4035506557 SHA256 (FreeBSD-7.4-RC2-sparc64-bootonly.iso) = c2755e19b1d7cd410ad499d79721f9300ecda13119c88edc5210c86a47af0ed9 SHA256 (FreeBSD-7.4-RC2-sparc64-disc1.iso) = 6e6aea09f0da95ba198fdc88396812ce82ecad0746f268da1e907542bf188923 SHA256 (FreeBSD-7.4-RC2-sparc64-disc2.iso) = e2628df0ced05d9b9ac0cd7bed2c1d1c6ddb3c80fd275ec7a32ebf74f7fc3d04 SHA256 (FreeBSD-7.4-RC2-sparc64-disc3.iso) = e6598c5306db67a689d568d05b7c0df0e41fa275f6cf27e4392c02c1c5df8f5b SHA256 (FreeBSD-7.4-RC2-sparc64-docs.iso) = a0d6018fe5cbf97f55ae0e963ae00c2cd4e37f46b17fdcd85a8b509ce0dcb267 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 8.2-RC2 Available...
) = 82d80d924db8952ae5d6c8946cbf89a21f7457f761169aa963e24b03271a4f74 SHA256 (FreeBSD-8.2-RC2-i386-dvd1.iso) = 8a9b08423252860f30e4bc79a446062741fc55af329aa529ac4a1663d60d5ff7 SHA256 (FreeBSD-8.2-RC2-i386-livefs.iso) = 62764fa1ff654bb821741c8037d37b826c298842998665e2995d1bcfa8dfab38 SHA256 (FreeBSD-8.2-RC2-i386-memstick.img) = 0a1b8efc97aafa5e9c0a5ee4f18fa5f3c0af473f3f239455a9fd7dae56bd9964 SHA256 (FreeBSD-8.2-RC2-i386-dvd1.iso.xz) = 5f8f66162ab085eefe4e89845dcb3ea903757aec496e033de8c7ea7eb802f9a6 SHA256 (FreeBSD-8.2-RC2-pc98-bootonly.iso) = 28b97d7d0e1219bfad4308d06c94d7fa29da2cd41aab763e1ff83d8e09d4105c SHA256 (FreeBSD-8.2-RC2-pc98-disc1.iso) = 6f188a7dcc5b8966ea4082cfb1f2a4050c1624b74605ff53647d5dae98063536 SHA256 (FreeBSD-8.2-RC2-pc98-livefs.iso) = a6da702a151ce7f1794a7fa28ea0e4e07359de0169ef904eb0646c004b8c807b SHA256 (FreeBSD-8.2-RC2-sparc64-bootonly.iso) = 8c912deb11fed9ba17e12c99205cfd3dbe74ad6ce87454f54b325a8869f9f855 SHA256 (FreeBSD-8.2-RC2-sparc64-disc1.iso) = 009fdf506cab2dbe6f2f87950d4f572efcca8aec186d6160a3f71946d16fd4ce SHA256 (FreeBSD-8.2-RC2-sparc64-dvd1.iso) = 080b79a3ead845b8ba7c349c06ae1df10c055f2313a0b45156c9dfd3287d3db2 SHA256 (FreeBSD-8.2-RC2-sparc64-livefs.iso) = 95f3148704a475b5bd194e3acbcfa1678cdd02ab240c378779c049ee077dbb0e -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 7.4/8.2-RC1 Available...
) = 7a14c364a8d34f2202e1138a7625ec1862021e5b811d9d1314247e7accab26ab SHA256 (FreeBSD-8.2-RC1-sparc64-bootonly.iso) = 39570a25201795589b85dec35afbf79c2e5dfc157c588c569eebf15eda2fe26c SHA256 (FreeBSD-8.2-RC1-sparc64-disc1.iso) = dc086f83ae0478e86252130fe739042f8600cb9bccf92864621295e46853eac4 SHA256 (FreeBSD-8.2-RC1-sparc64-dvd1.iso) = b56703f4269927ff038e6bbaf1fed71d61482a1985b47189590bc1e6dd2c0b21 SHA256 (FreeBSD-8.2-RC1-sparc64-livefs.iso) = 3b1e39867bdf6b54ab7e0b67f9a00b745ebcc06126ec2ab40fc64a3f0fbe -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 8.2/7.4-BETA1 Available...
-pc98-bootonly.iso) = 87bb8f401b4aa90c81ac71457959cffd MD5 (FreeBSD-7.4-BETA1-pc98-disc1.iso) = bb835438f20f0104480586463bfd5611 MD5 (FreeBSD-7.4-BETA1-pc98-livefs.iso) = 12e0cc49c322ad3d0c8c5a0c231189d1 MD5 (FreeBSD-7.4-BETA1-sparc64-bootonly.iso) = eaeca01b3fd221cece696c6f460a35a2 MD5 (FreeBSD-7.4-BETA1-sparc64-disc1.iso) = dc4ff7b5564b8cfaee00672624feaaab MD5 (FreeBSD-7.4-BETA1-sparc64-docs.iso) = a6fba4a4e256c448d021cb6afa9ba04a SHA256 (FreeBSD-8.2-BETA1-amd64-bootonly.iso) = 151c8d0499c73bf128258cd33a2158013ce0df424e830e545613df5ca9ba1c4e SHA256 (FreeBSD-8.2-BETA1-amd64-disc1.iso) = ddbfb4b394924038ba5cfa27f0ba36370d75b3088a2b675797d2b723f7e3f0f2 SHA256 (FreeBSD-8.2-BETA1-amd64-dvd1.iso) = 6bfe00a7b0adbd346a2a2793501e28adf9241b36357fabdc81199047f52a12e2 SHA256 (FreeBSD-8.2-BETA1-amd64-livefs.iso) = 87f86255d0b0cbd22f07f0b43c4b900b05f2d2ed7c2b8abba3c9cdde7dc71689 SHA256 (FreeBSD-8.2-BETA1-amd64-memstick.img) = 2307c6dec0eb4a711e0f2b835a5d76714ae9230835d2e1087d62f7ee4f3ce914 SHA256 (FreeBSD-8.2-BETA1-i386-bootonly.iso) = e612b57208ed66ba49bb5e2059efb524684dd6f0b85f9e1d31273896492a293e SHA256 (FreeBSD-8.2-BETA1-i386-disc1.iso) = fb3607518a4d1770f700f41f5d1072d19e0cddb747e7462c866b0d52e97cfbd3 SHA256 (FreeBSD-8.2-BETA1-i386-dvd1.iso) = 88b0d11fc68207823b480adddb069344ffe2f3a19f50c4543fc9732a72f166e2 SHA256 (FreeBSD-8.2-BETA1-i386-livefs.iso) = 5c899fc83f5d60ca3369e1d8ee86bd87af375c72297a3365875492a4531819ea SHA256 (FreeBSD-8.2-BETA1-i386-memstick.img) = 29d586dfd47079ad645d60ed19df7a519615686ff3d88af63c631594fc4007fc SHA256 (FreeBSD-8.2-BETA1-ia64-bootonly.iso) = e121f883875a3568e35ba79911d0c3524a915139a015e5c58a2d790a5bfd8281 SHA256 (FreeBSD-8.2-BETA1-ia64-disc1.iso) = 95bb7ca6b689a216654a1cc1f7360b1eb161edee95423c33c3e3d3847b392483 SHA256 (FreeBSD-8.2-BETA1-ia64-disc2.iso) = 4fd80dbc9d7c306d31bf4c3dab96e2ec50c636d279decd9c520f8538572cf849 SHA256 (FreeBSD-8.2-BETA1-ia64-disc3.iso) = 8033599a49c79481af5be9e7dfe3926cf91ffe2b93ab8be8b2c3f28a45bfdc10 SHA256 (FreeBSD-8.2-BETA1-ia64-dvd1.iso) = 11c8f2224a29c69049e869187a9af7c31ad89aef1f4b47268e15f5042c4352ee SHA256 (FreeBSD-8.2-BETA1-ia64-livefs.iso) = c90ea4e7baa93eeaf34969172ed7f732d1aa247c08aa14cfa99141174743c23d SHA256 (FreeBSD-8.2-BETA1-pc98-bootonly.iso) = 4393234a743cfc2d2c6acc8c9f64433075a305a00e2ab8312aa13b316eb3d288 SHA256 (FreeBSD-8.2-BETA1-pc98-disc1.iso) = 089cc8242ac36f3eb959da290803335adb865be69cc00d1214f0abc740d23a6e SHA256 (FreeBSD-8.2-BETA1-pc98-livefs.iso) = dbdb09af5217e60b16ee223bf3f36089c8b8250f0d5ba129d03bc1299d168347 SHA256 (FreeBSD-8.2-BETA1-sparc64-bootonly.iso) = 2f42537be93e498573fca1d828426f4d6062f25a892e5ad24a633275006ecbe0 SHA256 (FreeBSD-8.2-BETA1-sparc64-disc1.iso) = 53efb7fbc6cce16749f12f2cc6815ef3e233c0b252c017971803017ad9a03948 SHA256 (FreeBSD-8.2-BETA1-sparc64-dvd1.iso) = b1fc68ae1ce6e56213d101dfa481a1354269481987d97fe4756a7b9a7e30e4a5 SHA256 (FreeBSD-8.2-BETA1-sparc64-livefs.iso) = fcd0eb9a5c778dc26e015405df9ff5c7bceafff9d549eaa0414eed170f57ba01 SHA256 (FreeBSD-7.4-BETA1-amd64-bootonly.iso) = b515fc999f01ef6a7d49ec9c38b67923b2c14ca47b519acbefab89d3bc3b4b9e SHA256 (FreeBSD-7.4-BETA1-amd64-disc1.iso) = 8742d2ca3e310f4a6dfb1222f81bd14dd572c256fe1bcaf6f29ee0cccd30bf59 SHA256 (FreeBSD-7.4-BETA1-amd64-docs.iso) = 2043e465d42f39b12e3cff1aeebd0dccb4fd62e2f5a8619613510f56ba4e3864 SHA256 (FreeBSD-7.4-BETA1-amd64-dvd1.iso) = 20e41f1bc78da0de2e2fab314c6de1a00312b4766c2f350a7dbe3d6f3b5d5e4e SHA256 (FreeBSD-7.4-BETA1-amd64-livefs.iso) = aa0caf56d92bc0e5cdd688e25bc39610ee176b1ad8882af9d5d1f9f97f3a12a0 SHA256 (FreeBSD-7.4-BETA1-i386-bootonly.iso) = 32162eb82235cd0e861b2c9ad28729dcdddf8edc9ed54dadf5bc81a7fd8769ef SHA256 (FreeBSD-7.4-BETA1-i386-disc1.iso) = 88768cf30c6ca5da5e5f8c6cb163d7c602abce1149f33054c0ff0c66244220f5 SHA256 (FreeBSD-7.4-BETA1-i386-docs.iso) = d997a2d7a4deda0eb7d990296c74bc4955b51de1dd2a313833f0eb919c4a092a SHA256 (FreeBSD-7.4-BETA1-i386-dvd1.iso) = 4ab482eacb14d6c250481e4d43b0d6df26ad9bab93008ba041ea5d5c33e4ed01 SHA256 (FreeBSD-7.4-BETA1-i386-livefs.iso) = 6b23b38583b195043c7cbbd12d477c3f3283c0b07da48144f6ee07607b66ae57 SHA256 (FreeBSD-7.4-BETA1-pc98-bootonly.iso) = faa866f7901c3bbd8d983337024b998314d650c16e57d062509e7e64ee46c93b SHA256 (FreeBSD-7.4-BETA1-pc98-disc1.iso) = 051066e1a919a477f4ee864d8f06e25e5ec4f1a35e21eb98443dc5e95b498ad3 SHA256 (FreeBSD-7.4-BETA1-pc98-livefs.iso) = 10ac082f0e13d373394b4c335ee4b21226bb25f1956f9c33d935f3f588ea8bfe SHA256 (FreeBSD-7.4-BETA1-sparc64-bootonly.iso) = b4176a2011d7b3fa34012aab1fbbbec2c9efc253e752f142db289ad2a83a87a3 SHA256 (FreeBSD-7.4-BETA1-sparc64-disc1.iso) = 4ac17f79caa97a6c5050a851029bca9c92aabb64f3b2d9d62e41a9bc69c50718 SHA256 (FreeBSD-7.4-BETA1-sparc64-docs.iso) = 7f2563bdf16446cb119b88f304359d6d96bf01e81058676747a5f3f89403a938 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere
8.2-PRERELEASE/7.4-PRERELEASE...
JFYI - we are a little under a week from Code Freeze for the upcoming 8.2-RELEASE/7.4-RELEASE release cycles. Often times that means the developers are a bit more active on what will become the release branches. Sometimes with the increased activity some nits pop up. As a bit of a heads-up for people who track stable/8 and/or stable/7 I changed those branches to identify themselves as -PRERELEASE today. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Last of the RELENG_6 Monthly Snapshots...
The 201011 (November 2010) Monthly Snapshots are done. Since the Security Team will be dropping support for RELENG_6 at the end of this month we will stop generating RELENG_6 snapshots for the set of architectures that survived this long (amd64, i386, pc98, and sparc64). I also placed a copy of just the 6.4-STABLE-201011 ISOs on the ftp-archive site: ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/snapshots/6-STABLE/ so they will remain available longer than the four months that they will stay on the primary FTP site. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Upcoming Release Schedule
Just a quick note to say the target schedule for the release of FreeBSD 7.4 and 8.2 has been worked out. We will be shooting for a dual release (same target dates for both releases). The major highlights are: Freeze: Nov. 28, 2010 BETA1: Dec. 3, 2010 RC1:Dec. 17, 2010 RC2:Jan 7, 2011 REL:Jan 21, 2011 It is expected that 7.4 will be the last of the 7.X releases. The schedules are available on the Web: http://www.freebsd.org/releases/7.4R/schedule.html http://www.freebsd.org/releases/8.2R/schedule.html as are the Wiki pages that will be used to track the progress of the releases: http://wiki.freebsd.org/Releng/7.4TODO http://wiki.freebsd.org/Releng/8.2TODO While on the topic of releases, branches, etc... On a slightly related note the November 2010 Monthly Snapshots will be the last to include stable/6 (RELENG_6, 6.X) since secteam support for that branch will end at the end of November. I'll make a separate, explicit announcement about that once the November 2010 Snapshots become available. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 8.1-RELEASE Available
For those of you who don't subscribe to the freebsd-announce list: http://www.freebsd.org/releases/8.1R/announce.html Enjoy. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 8.1-RC2 Available...
On Fri, 2010-07-02 at 10:38 -0400, Ken Smith wrote: At this time DVD images are not available. There was a fairly serious security issue with the png graphics package. We will generate DVD images when the rebuilt packages become available, that will be announced then the images are ready. I just finished uploading the DVD images for amd64 and i386 to the master FTP site. It will take a few hours for them to propagate to the mirrors. Checksums are: MD5 (FreeBSD-8.1-RC2-amd64-dvd1.iso) = 9b8f71cdfc8e9b9f7238a843b85cd24d MD5 (FreeBSD-8.1-RC2-i386-dvd1.iso) = 15f60953db9940551504193c4433c43f SHA256 (FreeBSD-8.1-RC2-amd64-dvd1.iso) = a003d660870602d7aa5c829aa1c450f406d09b03af66ba175dd8392523399110 SHA256 (FreeBSD-8.1-RC2-i386-dvd1.iso) = 0bfbcd222f45e60be4806f622fd9dbb74a2ebb0bd56612f3fff5bf7db07249e1 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: 8.x grudges
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/7/10 4:17 PM, Mikhail T. wrote: 07.07.2010 14:59, Jeremy Chadwick написав(ла): FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and thus not an option) -- the kernel-config files, that worked with 7.x, break without this option in them (in addition to all the nuisance, that's documented in UPDATING -- which, somehow, makes the breakage acceptable). config(8) would not warn about this, but kernel build fails. We don't use this option (meaning it's removed from our kernels). It's definitely not required. All it does is ensure your kernel can comprehend executables/binaries built on 7.x. Attached is the kernel config-file (i386), that worked fine under 7.x. The kernel-compile will break (some *freebsd7* structs undefined), without the COMPAT_FREEBSD7 option. Try it for yourself... Jeremy is correct. COMPAT_FREEBSD7 means, despite this being FreeBSD 8, set things that have changed up to work in a way that is compatible with FreeBSD 7 *wherever* *possible*. Since you are trying to use a FreeBSD 7 based kernel config file you need that option, but people not trying to hold on to the FreeBSD 7 ways of doing things do not need that option. I'm not quite sure why you find that surprising, though it may have to do with a mis-conception on your part described below. The way I do this is, when upgrading major releases (7.x-8.x), to start fresh using GENERIC as my base template and then adding/adjusting while comparing against the older kernels' config. Others do it differently, this is just how I do it. Yes, your way is fine. But so is mine. It is perfectly reasonable to expect my method to work just as well -- the 7-8 is not revolutionary, but simply the next step. I read the UPDATING file and, though annoyed a little, took care of things mentioned in there... The remaining things are enumerated here... Actually it's not perfectly reasonable to *expect* your method to work just as well given the general goals of the FreeBSD Project as a whole. Your method *may* work but it's by no means guaranteed, or even a major priority I'm afraid. Your method *may* work. But you can't *expect* it. We like many similar Projects have a wide variety of people involved (both developers and end-users) and an equally wide variety of needs those people have. On the one extreme we have developers who feel their hands are tied by not being able to make user-visible changes to stuff - they feel they could make the system better faster if they could change things in incompatible ways faster. On the other extreme we have people who hate change for reasons similar to what you are expressing here - it's a pain in the butt to need to change config files, it sucks if all the old executable files suddenly stop working, etc. So, there has been a long-standing compromise in place. For bumps in *minor* version numbers you can expect to be able to use your old config files, old executables continue to work, etc. This is, for example, moving from 7.2 to 7.3. However for bumps in *major* version numbers there can and likely will be changes made that cause exactly what you are seeing here. A 7.X kernel config file *might* work OK on 8.X but we do not guarantee that. If it does happen to work great, if not sorry. What you call simply the next step is a bump in minor version number. Depending on how active the developers have been and what they've focused on major version number bumps *can* qualify as what you call revolutionary. This general mode of operation has been in place for a very long time (it pre-dates my involvement on the Release Engineering Team). - -- Ken Smith - - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkw1Oc0ACgkQ/G14VSmup/bEiQCfdtr8UkPp/QRcwUpGTlpRtJ2f RNsAn3+cV4jDuyQ38Wvm5eTiVObJ4DLy =4Bm7 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 8.1-RC2 Available...
) = f6474a515a85a51a7e5dc8e033edf5d04caf186f5727dcd143d4060d7fbf61ef SHA256 (FreeBSD-8.1-RC2-i386-memstick.img) = 6795004759b253dcb0443ca8118714cd1e2ac12173ab7be6b35d45af61495f3b SHA256 (FreeBSD-8.1-RC2-ia64-bootonly.iso) = 501489d8eb78adb8518d0b060e8317a7e4ef3973119521f36a1ec7a95f8788fe SHA256 (FreeBSD-8.1-RC2-ia64-disc1.iso) = 2f70b137e90d9cc4352f3d537e02dcdbd5adf425e68185186e0a0355720416cd SHA256 (FreeBSD-8.1-RC2-ia64-disc2.iso) = b9d18d85b6bf36a38feb8af056724c56739be7738c1e67b8b22f9d25f2f4a29f SHA256 (FreeBSD-8.1-RC2-ia64-disc3.iso) = d155c16d0416f73fcc84449d28ee7dd9ad4a50f766a297bd522c73204f3fe45f SHA256 (FreeBSD-8.1-RC2-ia64-dvd1.iso) = 820778f864c0af8b4c564bbe1eac9690320e3f69073015f5c8bc36cb570cce20 SHA256 (FreeBSD-8.1-RC2-ia64-livefs.iso) = 24d4dfee814958cfb7072da341c03f0e349ef4b135e65277a61140632fa32cf3 SHA256 (FreeBSD-8.1-RC2-pc98-bootonly.iso) = b81d0277ab17ad3a2f5f89ab451fe784c8cfcdef2df3b9628cb068d7b911b7a4 SHA256 (FreeBSD-8.1-RC2-pc98-disc1.iso) = 1653e1fe1b3f8dbb13a5ad642ef6d107dd5269ef97af9c24f000e8033590cf93 SHA256 (FreeBSD-8.1-RC2-pc98-livefs.iso) = 66fd758e507e8c06c0f2c87345257b64e4201d8b7e9d4bed511b8a53105ca91d SHA256 (FreeBSD-8.1-RC2-powerpc-bootonly.iso) = e1506bd5a8408d9f50149436ced6964b638714ea8b6af1b62f01cd2e68d26010 SHA256 (FreeBSD-8.1-RC2-powerpc-disc1.iso) = 1df04962269e14654d9f23c45404c6e67d3ecdae7cece449b6b41c92b5ed38fe SHA256 (FreeBSD-8.1-RC2-powerpc-disc2.iso) = 5af170e5a16c72bbf5d52aa13536c5b30da0cfa5ae2161c4954b26f809a7291b SHA256 (FreeBSD-8.1-RC2-powerpc-disc3.iso) = d5b639b41c907be46a467885dc86269b42e0c33ee41e5b252d7519cf46dfc2d0 SHA256 (FreeBSD-8.1-RC2-sparc64-bootonly.iso) = 956105978f3759e2e510f1e3195b7f93da3f6ec2a8be749a8d53986bf79fe899 SHA256 (FreeBSD-8.1-RC2-sparc64-disc1.iso) = 79a66f53662e7a1d34c04f7470b44052eb44debede03a8a3ad900e9348d06836 SHA256 (FreeBSD-8.1-RC2-sparc64-livefs.iso) = aaebc4a306d14bffa0c1066301b2f7dc0af796586d23de2ccb5a0bc6239a5f6a -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 8.1-RC1 Available...
SHA256 (FreeBSD-8.1-RC1-i386-bootonly.iso) = 9c3a0924610fd807cb2c32ced11844f2978771c8cda12befc31678471198d065 SHA256 (FreeBSD-8.1-RC1-i386-disc1.iso) = 5110557c4707472265d2d5c46e3980dd2c172f59f1f8adf05a85d03b24f60187 SHA256 (FreeBSD-8.1-RC1-i386-dvd1.iso) = d9a01dde01b6a39a9b11530a219b4f910aca19b1ca77333f6cf872aa26a294ae SHA256 (FreeBSD-8.1-RC1-i386-livefs.iso) = 27fd5a3d6bbf55ade7c6fd0d7185d281ce8022e9b0c3fd843a2e141a496275ff SHA256 (FreeBSD-8.1-RC1-i386-memstick.img) = 5892b4722a207964117e433e2a1c32151d35cf7767d078a88cb4260f7dfa2e59 SHA256 (FreeBSD-8.1-RC1-ia64-bootonly.iso) = 5dd28388b640fc73fd50ab247bfcfeecaeea168e548fd47a23710b157bc4ae23 SHA256 (FreeBSD-8.1-RC1-ia64-disc1.iso) = 5df5cab408318bc34a6965761954dd5d5f9e13e21af84fab3041863061c0e298 SHA256 (FreeBSD-8.1-RC1-ia64-disc2.iso) = 6d6412a1fe10e1e93f143733c38609d9a167accf12fb753d31cd501ef6c359c9 SHA256 (FreeBSD-8.1-RC1-ia64-disc3.iso) = 18e4b1878d290da9228a6be247fc237ee19086df8b7691fd6985391e4e393f2b SHA256 (FreeBSD-8.1-RC1-ia64-dvd1.iso) = e68773c640565bb4f8aa0f542a13371500f3fc88440dd4c17b18759fb75c1473 SHA256 (FreeBSD-8.1-RC1-ia64-livefs.iso) = 743f1ae6b647fad311ccf820c0ad7091264250b17c1b79c063f2827abc852898 SHA256 (FreeBSD-8.1-RC1-pc98-bootonly.iso) = a6e833c64fb0e7fa7e425199106ce5f2ed131cc08b758286d87740539e327f50 SHA256 (FreeBSD-8.1-RC1-pc98-disc1.iso) = 31bb82cd4bd597e7c955fd61aab9a4092f4510c022230c8612d98b95587912d1 SHA256 (FreeBSD-8.1-RC1-pc98-livefs.iso) = 01a38477f09db8588e5d926bfd8ef532aad1b150140c450b2011889e16afa3e6 SHA256 (FreeBSD-8.1-RC1-powerpc-bootonly.iso) = ce669efc227ffc7647a42c87287abfc61b2f044be90f1329bfa1e0ad700d386e SHA256 (FreeBSD-8.1-RC1-powerpc-disc1.iso) = dee68ed0f17c1288e95677252d6e48011c326274ccf971747f74e17de681779a SHA256 (FreeBSD-8.1-RC1-powerpc-disc2.iso) = 6447b04da5f93f3b9008e71e3a0f8704552f06ee9e261529303dd2d9afdcf501 SHA256 (FreeBSD-8.1-RC1-powerpc-disc3.iso) = 0201c7c3edd75bc82c5f2da1183348eff14f8b4eb82a408158c0592f8015bb72 SHA256 (FreeBSD-8.1-RC1-sparc64-bootonly.iso) = 37f3dc5bdfd03ba196d40d677928f0e80c174d62744fa6774937416af7cea4ca SHA256 (FreeBSD-8.1-RC1-sparc64-disc1.iso) = 16ba7440a25c5c318dadcfd0b6239058e823d11428a04cb5160a3627df5b7efd SHA256 (FreeBSD-8.1-RC1-sparc64-disc2.iso) = b137c32a711b8f604d52f23405d0b2c9d5bb30f9582defccfcc9bc5ef4016510 SHA256 (FreeBSD-8.1-RC1-sparc64-disc3.iso) = 3b58425fcca261e61fa4351c49f90abf9c46d42e04cafe5da7b7bee21ef25bc4 SHA256 (FreeBSD-8.1-RC1-sparc64-dvd1.iso) = 884a8b49a5e87dc0e56cad1e03338004f4978e39776f34eb1c13dab50994b5b6 SHA256 (FreeBSD-8.1-RC1-sparc64-livefs.iso) = b6a927cdf6bdcdb18130a772213276c300a46d805bcc9f8817162dcf4e7640ed -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 8.1-BETA1 Available...
) = 92e36b2788f58569ae475d4ad3ec67a9a0c4167abe00b8370274f28505332c33 SHA256 (FreeBSD-8.1-BETA1-i386-bootonly.iso) = 07130310d0470accde8590f64b9ddd2620a19789df14ff0c823fad71962ebceb SHA256 (FreeBSD-8.1-BETA1-i386-disc1.iso) = 40fc6540f44324718e94ba2a3c4905b448b8e889cd65d4f5f82de905cf059d22 SHA256 (FreeBSD-8.1-BETA1-i386-disc2.iso) = f699f12449c84006994d46cc627c507af3c5947d604d6703d9d8563710ee62b8 SHA256 (FreeBSD-8.1-BETA1-i386-disc3.iso) = 1568781c01a30d4f3d59eb0ea2061d1e5df7d27db403443c3215f1da447ff6e3 SHA256 (FreeBSD-8.1-BETA1-i386-dvd1.iso) = f8c4a8ca9e5077d3690903dad652a4ec245bab3ec15176dad113b7e4ce90b239 SHA256 (FreeBSD-8.1-BETA1-i386-livefs.iso) = 1ae66cfd3c6fb6edf48f5a8d38d4097b4488b90025f0777a49307cccec04c2da SHA256 (FreeBSD-8.1-BETA1-i386-memstick.img) = 1cfc15def9d0c9c36a0394bc41d4e59d3d25612f10563b061df2e0d75e665557 SHA256 (FreeBSD-8.1-BETA1-ia64-bootonly.iso) = 6db5a2ba942526ff40dc36d2aa8847d56661fdaa62725500506f3b70b3c38be8 SHA256 (FreeBSD-8.1-BETA1-ia64-disc1.iso) = 4b1f87932658b156e093bbfede185a1965f892ac4d8a007e49252ab9efe256bb SHA256 (FreeBSD-8.1-BETA1-ia64-disc2.iso) = 38fd9cee73e29f6e3ec87cb8cebd3113fd4b37dc0de8fb6c5401c776c57799f9 SHA256 (FreeBSD-8.1-BETA1-ia64-disc3.iso) = a30c22fd983960ecd5c70939b31b09efe907ae8dc46b6dc830959998f0574d58 SHA256 (FreeBSD-8.1-BETA1-ia64-dvd1.iso) = 0cf2229ae748f8b4b33b3317b80d1fc1443a774b81acb42c08b06c8fb202a04d SHA256 (FreeBSD-8.1-BETA1-ia64-livefs.iso) = b99ca9fdb4c10c85f2ab3b71d4aed79419d95266af2b3b479cf522a72dedbc00 SHA256 (FreeBSD-8.1-BETA1-pc98-bootonly.iso) = 8a65b0e0db9f8cad6451a3e10d2af858d157f2def59d7006a1a5824d8a4d244b SHA256 (FreeBSD-8.1-BETA1-pc98-disc1.iso) = 8327a872f913d5a13fed73583e1ae757c1ec855a0addb009c1ffb23c2f345f59 SHA256 (FreeBSD-8.1-BETA1-pc98-livefs.iso) = 5dc9782a9181d54b50b636c9df7044834dfbffaa48ec156249765263c7732bd0 SHA256 (FreeBSD-8.1-BETA1-powerpc-bootonly.iso) = 5b26bb9d6890fb31cc2884d55340c65b6b41c0d37a9ce81853c10bc4f02c1d40 SHA256 (FreeBSD-8.1-BETA1-powerpc-disc1.iso) = 305560feb1e5cdfb06f47d743fc213f5c8bf534691013966898c0229d1a51701 SHA256 (FreeBSD-8.1-BETA1-powerpc-disc2.iso) = ee114228b8aaf7a5ff64c8e6fbec91afbe77591b463360cf5222cebb5d5ff6d8 SHA256 (FreeBSD-8.1-BETA1-powerpc-disc3.iso) = 090c8f23392cc84e6589fdda8b9cdfa784fe5462c0769162752f9b96c47e5b97 SHA256 (FreeBSD-8.1-BETA1-sparc64-bootonly.iso) = 68520bcb6b70d0185a30ba45bf5578efb0d350c417259a00fe256e06623211e5 SHA256 (FreeBSD-8.1-BETA1-sparc64-disc1.iso) = 9e87ef3cd679754b66d8e04116b11a958dc5e8f31fcbd466b9b2b80687bdba38 SHA256 (FreeBSD-8.1-BETA1-sparc64-dvd1.iso) = 3b006f87bb388cd0d9d6f90d86c12092d14d105fcd76144050a280f12fdece8e SHA256 (FreeBSD-8.1-BETA1-sparc64-livefs.iso) = 7df1d5e69209ec540982476f9f0d67ac98017482b15df274a75a71a9331fd8b8 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Release Cycle for 8.1-RELEASE...
Just FYI, we are about a week away from starting code freeze for the 8.1-RELEASE release cycle. Since sometimes that means stable/8 gets a little less reliable due to higher than normal levels of developer activity I'll adjust the branch to say it is 8.1-PRERELEASE now. The target schedule for the release cycle is available here: http://www.freebsd.org/releases/8.1R/schedule.html And the wiki page to track the current status of the release (started but not heavily used yet) is here: http://wiki.freebsd.org/Releng/8.1TODO The current target release date is July 9th, 2010. Thanks. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD Release 8.0 floppy images
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/10/10 12:36 PM, Julian H. Stacey wrote: I'd suggest it would be good to commit post a comment why removed. It will later affect rescue capability of some older servers when they get upgraded, (I guess many/most legacy production servers still are 7.*, at least till 8.1 comes out). When I started down the pathway to removing them it was with the intention of removing *all* mention of floppies as part of system installation. There are quite a few things it would be really nice to rip out of sysinstall (they're hindering other progress) that are there because of floppies. We figured it had reached the point progress on making sysinstall better (or at least less annoying) in various ways being hindered by floppy support wasn't in the majority of peoples' best interest. It turned out progressing on that isn't going as well as hoped, pc98 has stronger ties to floppies than was originally thought. So, after turning off the building of floppies things got a bit stalled on the removal of what I'll call floppy-isms in sysinstall. It's still the basic path we'd like to follow, it's just slowed down a bit. As for building them at all goes... It turns out that by mistake (a system doing automated release builds on a regular interval) we discovered that building them now fails due to another of the handful of reasons we wanted to abandon floppies goes (above mentioned ripping out of stuff was just one). Most of the floppies involved can go multi-volume if necessary (e.g. the mfs floppy can span more than one physical floppy) but the 'livefs' one can't and it recently started overflowing. Those reasons combined with the fact I can't even test them any more all combined to convince the developer community 8.0 was a reasonable point to let floppy support fall by the wayside. - -- Ken Smith - - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvoogwACgkQ/G14VSmup/bC3ACfbuczpAnz1FuC3gzzSWa3BM3I TPsAnRE/KnBwM2v9akXNuQJJmtJGnBF6 =p7a/ -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.1-RELEASE Preliminary Schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 For those of you who are wondering when 8.1-RELEASE might arrive, we have discussed it and come up with the initial target schedule. The highlights are: Freeze May 24th, 2010 BETA1 May 28th, 2010 RC1 June 11th, 2010 RC2 June 25th, 2010 RELEASE July 9th, 2010 As usual, that's subject to change but it's at least our current target. The schedule is posted to the Web: http://www.freebsd.org/releases/8.1R/schedule.html That page includes a link to the 8.1TODO wiki page: http://wiki.freebsd.org/Releng/8.1TODO Though we're just barely started so there really isn't anything interesting there yet - so far it just has the schedule... Thanks. - -- Ken Smith - - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAku5LlAACgkQ/G14VSmup/bQTQCeIaCLPuJoYVDjgB+rZDDsmjVz 49IAnjlgZ++ZJRMvfH9SkcGL1dcPTGuH =kP6w -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 6.4-RELEASE missing from mirrors
On Thu, 2010-04-01 at 11:07 -0400, David Boyd wrote: The link (actually file) called 6.4 moved to ftp-archive is missing from most/all mirrors. We have been using these files to follow the releases when they move. It works as long as the 6.4 moved to ftp-archive file is present. Please help. Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org Sorry about that, it should be fixed on ftp-master now and will propagate out to the mirrors as they do their next sync. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FYI - FreeBSD 7.3 has been released...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just a quick note for any of you who are not subscribed to the freebsd-announce@ mailing list. 7.3-RELEASE was announced today. The announcement message is available here: http://www.freebsd.org/releases/7.3R/announce.html Thanks. - -- Ken Smith - - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkupQM4ACgkQ/G14VSmup/ZXLgCdF63w0KJV6fU/NbeNWHAQ4lar 3TsAoIwRSTyijFSb8SiZh2+91WDr0Gh1 =CUdv -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
7.3-RC2 Available...
) = 7550dd764327ec8605eaa9f77c7c76a7b29bd709cee273100837f06c0f940997 SHA256 (FreeBSD-7.3-RC2-i386-disc1.iso) = f5e7198bae889825e929ae1e3f63d9da92b555fc982a9ac9d93d4cc66091505e SHA256 (FreeBSD-7.3-RC2-i386-disc2.iso) = c3f47da34f33787bf86c38ffe22bb5202ea1d9f298448c55a3daf106dffb3578 SHA256 (FreeBSD-7.3-RC2-i386-disc3.iso) = 00974ef1f74169cb5b4fdeb4dd04c0a10c5df675a185e8b3ba41719c5983dbfb SHA256 (FreeBSD-7.3-RC2-i386-docs.iso) = 5eb086a291d545a5518a51f28248b9fa35f166338eeeca701b332e8fb4618a97 SHA256 (FreeBSD-7.3-RC2-i386-dvd1.iso) = d5feab36c98da0a78926316deb3a702fecfaf1154777da5c3c36753b8c22673d SHA256 (FreeBSD-7.3-RC2-i386-livefs.iso) = 79fd8bf491ec715e133f0f24e8df8afc5be67bc6327d9a4c3dbd7f9c36cb7f88 SHA256 (FreeBSD-7.3-RC2-pc98-bootonly.iso) = 60e3c9a3c38cd61aa55c7b10c3bba87e9939d8ae72646473566632e8f2b3 SHA256 (FreeBSD-7.3-RC2-pc98-disc1.iso) = 96d8643c87e4fef99faa1a132b5def2f0dc45341837ec4a05e84ffa63a029523 SHA256 (FreeBSD-7.3-RC2-pc98-livefs.iso) = 94917e2104c9002599b7dce7c82aaff413852971d86e1b170833ad6004bd92c8 SHA256 (FreeBSD-7.3-RC2-sparc64-bootonly.iso) = 2b4e1b5ec1c0442dc05ec5c25ca88e4cb3971fc48e8cd325646a07f3a517fb8b SHA256 (FreeBSD-7.3-RC2-sparc64-disc1.iso) = 0ee98564151a077c1233ed3681dbb9517ff375a3baee7c8d269a9f33e30519b7 SHA256 (FreeBSD-7.3-RC2-sparc64-disc2.iso) = 390be0e347d599ef789f5da567ec40580088db42b9a18580da672a781c2d9bea SHA256 (FreeBSD-7.3-RC2-sparc64-disc3.iso) = 1c8ac66d90a08d0fb9eeb5d05b3ccce501d477b70384663f7ee4513f14835d53 SHA256 (FreeBSD-7.3-RC2-sparc64-docs.iso) = a0376f49693d791ec5356f9ac2bd3132010fa6e0d548545cc7757ff59a8f5b2e -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
7.3-RC1 Available...
-7.3-RC1-i386-disc1.iso) = 226153815575aa4e43e3772f1abdfc69084a825e4f269fbe953ffafb5be2112d SHA256 (FreeBSD-7.3-RC1-i386-disc2.iso) = 976172cf5c4c67c589c6f8234ab9616210509c34ab485e1384a7a589a6459d6a SHA256 (FreeBSD-7.3-RC1-i386-disc3.iso) = ddeaed4ef86d3c69d7096b6a363ca43226e0c923881e1a70846e87ce8f20782f SHA256 (FreeBSD-7.3-RC1-i386-docs.iso) = 4adcb739cf5d0ed54ac564129d3d972ff76439cba8e8027f80ea7242d5272bcb SHA256 (FreeBSD-7.3-RC1-i386-dvd1.iso) = f7f5663b1b2b7716edd96517c3f511ea7ec1605f46c453d58b0f31c6ab7df5be SHA256 (FreeBSD-7.3-RC1-i386-livefs.iso) = 42e28e767afe8ff8b51199a889141637576d939d3adf4566b07bb7360b7e98b2 SHA256 (FreeBSD-7.3-RC1-pc98-bootonly.iso) = 83f7e822e7e18794ff3a5b6f8b041c9dd3eb7d54a9b7b49803ceb49fee3c0113 SHA256 (FreeBSD-7.3-RC1-pc98-disc1.iso) = e9f0072b4f4f0053a1967fdc0b0456d156abc1df17481eac6083c1527331912e SHA256 (FreeBSD-7.3-RC1-pc98-livefs.iso) = f93258ea2f25fe84c9a69014ef66778585e1d34a18167d99bf7f59147544af2f SHA256 (FreeBSD-7.3-RC1-sparc64-bootonly.iso) = ef40738bc1f02d4d93a9846560fd553de52b8cd350eec0ba9377d3cf23ed2319 SHA256 (FreeBSD-7.3-RC1-sparc64-disc1.iso) = d922a754de7c826679281887eadd78fb520cc428fea6bc8f0c14178b01ab559d SHA256 (FreeBSD-7.3-RC1-sparc64-disc2.iso) = 5e99fc0d9324c5acfed3498b111b081f9b11a035457822fb1fee187a71abc74c SHA256 (FreeBSD-7.3-RC1-sparc64-disc3.iso) = 5e78718de7898753d2701f7ff27ea09d44544a0cfa4a7aba3bbaa855c22b0636 SHA256 (FreeBSD-7.3-RC1-sparc64-docs.iso) = 048e045a418ebea6cbe2a27c36f8d9e56de19c107a6ffc8d776bf3c4207eb6ae -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: 7.3-BETA1 Available... [memstick.img?]
On Sat, 2010-01-30 at 17:17 +1100, Ian Smith wrote: are there any plans afoot to release memstick.img/s for 7.3-R? If so, where should I look for information on how it may be done? If not, is there something about RELENG_7 precluding that? USB stack? No, no plans afoot for memsticks for the balance of the 7.X releases. The sysinstall support for installing from a USB based disk didn't get MFCed to stable/7. Even if it was we're already something of a heavyweight on images (both CDs-with-packages and DVD) so my plan all along had been to phase in the memstick image for stable/8 and at the same time drop CDs-with-packages. My search for information on the particular recipe/s used to make the 8.0-R memstick images has proven fruitless so far, despite several useful suggestions on ways to make various other sorts of bootable USB stick images. So far they seem to have been made out-of-band, somehow? My particular interest is in putting DVD release/s onto a 4GB(+) stick, hopefully on bootable slices rather than 'dangerously dedicated' form. I was more or less experimenting with the memsticks for 8.0 and never quite got around to packaging up what I do into a script. I'll try to get something along those lines into the tree some time soon. Release builds are done in two passes - the first pass creates all the directories needed but stops there giving me a chance to add stuff to those directories. That's where I put the packages into place if there are going to be any. After doing that the second pass runs which builds the ISO images. After the first pass I briefly put the packages directory that is supposed to be on disc1 (which is just the docs packages, sysinstall gets grumpy if those aren't present) into the dvd1 directory and do this: makefs foo.fs dvd1 dd if=/dev/zero of=8.0-RELEASE-amd64-memstick.img \ bs=10240 count=size mdconfig -a -t vnode -f 8.0-RELEASE-amd64-memstick.img fdisk -BIq /dev/md0 bsdlabel -B -w /dev/md0 dd if=foo.fs of=/dev/md0a bs=10240 conv=sync mdconfig -d -u 0 The size number should be calculated to be two blocks larger than the size of foo.fs so you've got room for round-up error and enough space for the label. After doing that I put the packages directory I'd used where it's supposed to be (disc1), put the proper set of packages for the DVD into the dvd1 directory, and then run the second pass of the release build to generate the ISO images. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
7.3-BETA1 Available...
7.3-BETA1, the first test build of the 7.3-RELEASE cycle, is now available for amd64, i386, pc98, and sparc64 architectures. The target schedule along with the current status of the release is available here: http://wiki.freebsd.org/Releng/7.3TODO For now we plan on BETA1 being followed by two Release Candidates, then the release itself. If you notice problems you can report them through the normal Gnats PR system or on the freebsd-stable mailing list. ISO images for the architectures listed above are available on the FTP mirror sites. For this BETA build no packages were included on any of the ISO images. An initial pass at providing packages will be done for the first Release Candidate. If you are using csup/cvsup methods to update an older system the branch tag to use is RELENG_7. The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.1-RELEASE or 7.2-RELEASE can upgrade as follows: # freebsd-update upgrade -r 7.3-BETA1 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.3-BETA1, 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 (FreeBSD-7.3-BETA1-amd64-bootonly.iso) = 0219e9e8ba1efecec9bba03239df1a36 MD5 (FreeBSD-7.3-BETA1-amd64-disc1.iso) = a4c49a5ad8eef58126201ba71a7b214f MD5 (FreeBSD-7.3-BETA1-amd64-docs.iso) = 78fd42619550e4369d8c7e3fb85715fc MD5 (FreeBSD-7.3-BETA1-amd64-dvd1.iso) = ed70bfbfeb028d495ecd4e2dbcca5d07 MD5 (FreeBSD-7.3-BETA1-amd64-livefs.iso) = 1853ddd3a0a474bb31fc9e534b76c952 MD5 (FreeBSD-7.3-BETA1-i386-bootonly.iso) = 9fdb08c372682ac1241f75f3c5c97b72 MD5 (FreeBSD-7.3-BETA1-i386-disc1.iso) = 92b97a266771e2be4dcfa7bf241ba006 MD5 (FreeBSD-7.3-BETA1-i386-docs.iso) = b0e0a588873d7b5393b0fd47ff9c820b MD5 (FreeBSD-7.3-BETA1-i386-dvd1.iso) = 4738e6947679f72f0e3401785d83d1ec MD5 (FreeBSD-7.3-BETA1-i386-livefs.iso) = 618ad406e788d91d408a87472eae7432 MD5 (FreeBSD-7.3-BETA1-pc98-bootonly.iso) = 38658cbf889e2599f288ec1eca628dd6 MD5 (FreeBSD-7.3-BETA1-pc98-disc1.iso) = ba5e65f1cca54c35d9933c9d27c6003c MD5 (FreeBSD-7.3-BETA1-pc98-livefs.iso) = 521a5add42a95b67c0470cd12b57a677 MD5 (FreeBSD-7.3-BETA1-sparc64-bootonly.iso) = bfd1081b69f225e66b16bdb332fbd832 MD5 (FreeBSD-7.3-BETA1-sparc64-disc1.iso) = 5bce58ebf4b9f10d06d522308f59a901 MD5 (FreeBSD-7.3-BETA1-sparc64-docs.iso) = 9e4d53695ad36eb5faab5e7e23a0c16d SHA256 (FreeBSD-7.3-BETA1-amd64-bootonly.iso) = b7b2d5c72e3aff3449a0fe8edfaace877a47b1bb6e9946f45f463a6a4bbec24c SHA256 (FreeBSD-7.3-BETA1-amd64-disc1.iso) = 4cc5d2a87d813f29a619225e9eda0ab05a5854e77ee1d3e84821b740c8c0e5ee SHA256 (FreeBSD-7.3-BETA1-amd64-docs.iso) = adbd636f39df3f9293cc431a1cbf992e3699da219955960c14dfba8b7a55a1b5 SHA256 (FreeBSD-7.3-BETA1-amd64-dvd1.iso) = cbc13a91a9ed5c135153a71c8d78e753f8907c0dbf3391c5c480ace3d3a75b78 SHA256 (FreeBSD-7.3-BETA1-amd64-livefs.iso) = 0703a4af2496f5a27d23325ca444d180c92e0f897c44a37a82a7ed4fa5c0cca1 SHA256 (FreeBSD-7.3-BETA1-i386-bootonly.iso) = 7552eb7d4d9646ee550339778f7041fb3170763e836dbd4e182dcc51b62662d2 SHA256 (FreeBSD-7.3-BETA1-i386-disc1.iso) = 69cc74ff3a37caffa055e28fb476db14b5cbac686a0b93a74b53c206852e663a SHA256 (FreeBSD-7.3-BETA1-i386-docs.iso) = 020ea6d2949f15289e9ecdb1edfff9d7857995a67fed41df5391f8af6a6ac7ab SHA256 (FreeBSD-7.3-BETA1-i386-dvd1.iso) = 90364c477d0c5bec05d13d69a01838b31575fcbc251eb9bc261557f0b3cad5ad SHA256 (FreeBSD-7.3-BETA1-i386-livefs.iso) = 6d17360bf9f358b5d9047de81da99f497a385a70899bfcb64ba48a98f72478ca SHA256 (FreeBSD-7.3-BETA1-pc98-bootonly.iso) = 25faeb8c4fa656260c511585f77c8ae520640b199cd6422698eabbcc0fabb524 SHA256 (FreeBSD-7.3-BETA1-pc98-disc1.iso) = 1799383fbd75868cebbe12204daf76477adcc9c90fa7e212d77021a718109642 SHA256 (FreeBSD-7.3-BETA1-pc98-livefs.iso) = ede5e5d079117cb78f36171bf0a4f0fc05828310a5f4d97a30cb399cd0a9cd63 SHA256 (FreeBSD-7.3-BETA1-sparc64-bootonly.iso) = 556364dc8a5c904f155ead9f5ed857e9dc4227b5530abbdb02f3444290fe3af9 SHA256 (FreeBSD-7.3-BETA1-sparc64-disc1.iso) = 1779a581ca0c0024b1fb1928befc71c78574309e83c3c1d4cb36a4053772a93e SHA256 (FreeBSD-7.3-BETA1-sparc64-docs.iso) = f017ac4e343246050732b86f8d5edeb186dd20ea6e23dd60644f244d9ad2bac6 -- Ken Smith - From there to here, from here
Beginning the 7.3-RELEASE release cycle...
Just a quick note to say we're beginning the release cycle for 7.3-RELEASE. Code freeze on stable/7 began now, and stable/7 has been adjusted to say that it is 7.3-PRERELEASE to reflect that. More details will follow but this is the current target schedule: 01/22: code freeze 01/25: BETA 02/08: RC1 02/22: RC2 03/01: RELEASE Thanks. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: Changing ISO filenames
On Tue, 2009-12-22 at 19:28 +0100, Oliver Pinter wrote: Do you have any plans, when comming out REL_6.5 and REL_7.3? There are no plans for 6.5-RELEASE, 6.4-RELEASE was the last of the official releases for the stable/6 branch. We just started working out a schedule for 7.3-RELEASE, I should be sending that out some time next week. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Changing ISO filenames
People who collect ISO images from more than just the FreeBSD Project have been mentioning it would be nice if FreeBSD was part of the filenames for a while now. I just committed a change to head that will add FreeBSD- to the beginning of the filenames. So for example 9.0-RELEASE-amd64-dvd1.iso becomes FreeBSD-9.0-RELEASE-amd64-dvd1.iso As part of the commit I set a 1-week MFC timer and at that point I will MFC the change to all of the branches we currently target for the Monthly Snapshots (so all the way back to stable/6). That way the filenames will be consistent for all the images generated for the January 2010 Monthly Snapshots. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
8.0-RELEASE completed...
Just a quick note in case there are people here who aren't subscribed to the freebsd-announce@ mailing list. We have completed the 8.0-RELEASE cycle. Details about the release are available from the main web site, in particular the announcement itself is available here: http://www.freebsd.org/releases/8.0R/announce.html Thanks for all the help with testing during the release process, as well as your continued support of FreeBSD. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
8.0-RC3 Available
) = 7a402ec8d17804bd6d16fad0969c9e52 MD5 (8.0-RC3-sparc64-livefs.iso) = 61c90ecce584c0c91f91e744f40a7d42 SHA256 (8.0-RC3-amd64-bootonly.iso) = fbf7c68cf81c300ec4e944ed6491f65d217168a85c1863c019cb41eec30cae94 SHA256 (8.0-RC3-amd64-disc1.iso) = 7e377f38cb6dc0ba1aa1fa13facf7e03f3cefad3d1490de797ed3a91680892e8 SHA256 (8.0-RC3-amd64-dvd1.iso) = fa4671d9b9b5b8208579d51cc2f72188a9537984ee28ba851236a52f32022597 SHA256 (8.0-RC3-amd64-livefs.iso) = c8c3728583b43e76d5e305b20fed578474adb5b14dbf2537b8ca9156b2d1c4cd SHA256 (8.0-RC3-amd64-memstick.img) = b8d90dbfca07160d9818bf6705b5dd99ba25fe1624cdda3f3f4919681d1b1af1 SHA256 (8.0-RC3-i386-bootonly.iso) = f514dbec335fbf72917b25c1e79f6bca4e9dd74e037f75ab30d810e7942ac2fc SHA256 (8.0-RC3-i386-disc1.iso) = 6b306af4a74df57d2c155891557878d747bac92a24c2b46947f89e7d9657addc SHA256 (8.0-RC3-i386-dvd1.iso) = 21794b11142eeb7eb56c8810b83dcd67230b0d26a0f0e5839866172d977a5626 SHA256 (8.0-RC3-i386-livefs.iso) = 3dfd45e0a5550913b29d19d989f19167159d1f926f1667d1622890a5f83be93b SHA256 (8.0-RC3-i386-memstick.img) = afc65bf14101ace1f069323678a8070ab84823bf191aeefa8fc9909d38e9306e SHA256 (8.0-RC3-ia64-bootonly.iso) = 1fefdd0b03c943162cbb66d507e11c3a2e541e97a0742471de49f17ae96b953c SHA256 (8.0-RC3-ia64-disc1.iso) = 67124c8101dd3fb06dbd3771c3eb18560207b42e46c331cc2ab02ba5284a72b7 SHA256 (8.0-RC3-ia64-disc2.iso) = 4eaa1125f98c5ed463f7577b9818dd57dbaee0bad01a1c7543ad4cc89c1770d0 SHA256 (8.0-RC3-ia64-disc3.iso) = c178a48004a12d6f178b478da146582742a88a27fcbf380029ae7fb3f6db6472 SHA256 (8.0-RC3-ia64-dvd1.iso) = d45a8e6ae622c1985d5b9c346c74f44884f3adba3c02d0b69bb58f19b359fa73 SHA256 (8.0-RC3-ia64-livefs.iso) = 9132340e15b75601017b0b57902fa48926e1d1a257f1f5149baa07c15e0dede8 SHA256 (8.0-RC3-pc98-bootonly.iso) = 42beee44af5859861718978a03de04e6a6fd0e63afec66a939830286fb73b22a SHA256 (8.0-RC3-pc98-disc1.iso) = 4b00447579349443d80082d1809b0d04688ea317a9bee3f551c13a35c82c549d SHA256 (8.0-RC3-pc98-livefs.iso) = 243306c98a9eade16d90994217fd89f0aba51cfd8399b1017754a3415f2e79e8 SHA256 (8.0-RC3-powerpc-bootonly.iso) = 4cfbcac5fc69bb10860ed2c511bcf175be730c2fd11e57ccd2c8c77322ea5172 SHA256 (8.0-RC3-powerpc-disc1.iso) = 6d7725d24c01d985590566eb168cde1e6d334a3cdc6bdc7a4508ea54c205c489 SHA256 (8.0-RC3-powerpc-disc2.iso) = ecfd22166dd411359d74a61c1724cfa747e4a7e9cb8b47776643795f6388942b SHA256 (8.0-RC3-powerpc-disc3.iso) = fc3c0c2823b36cc6530c7afdb73dbfa3cb1bf6a64a59fd4a55307e1e4d1541fe SHA256 (8.0-RC3-sparc64-bootonly.iso) = 44a641e1f3080112d6063f923d1e5d17f9d9eedd1004888aace77e08beca2fdf SHA256 (8.0-RC3-sparc64-disc1.iso) = e68eec5765f9313a9cbe4e94915b89d68caa4f4f65884be9e7b1d463862c17e3 SHA256 (8.0-RC3-sparc64-dvd1.iso) = e824cc316c520d29673c51e5ccf58aba9a79b17e7b61b67c1d13da7300911f7b SHA256 (8.0-RC3-sparc64-livefs.iso) = a4f0f8f02a9b1bad01088f5cb81a9a4d93ef6aad095afdd79cb5525b4a1e53b5 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
8.0-RC2 Available
) = 0c72b0248a689df99b3aa76b7ed148b7bd74a9de2577950231120ac4403bdb4c SHA256 (8.0-RC2-amd64-disc1.iso) = a20b72acf3990f6b4a71941c576d5dc395260a98287bdfe4455cbf1015e0 SHA256 (8.0-RC2-amd64-dvd1.iso) = f29f6a65d08190d946d38412cc199b7ad3d001ccd05e66b396cdb1339f45b3fd SHA256 (8.0-RC2-amd64-livefs.iso) = 59f3feb88ea35e8ec075b59ff1eeac8df36df219a375058966eab2b4deb1350a SHA256 (8.0-RC2-amd64-memstick.img) = 60a91e82223169fabf445b227f75cdc3495045a764285a0e7023bdf20478931a SHA256 (8.0-RC2-i386-bootonly.iso) = b160f47b2b7baa69acca8c5e5d45dccb8fa3582ade676f69b44638c956f92f38 SHA256 (8.0-RC2-i386-disc1.iso) = c7edabc1fe1429f396978b4699b41fff9e4a17574dfa2658499a6f9f2bd91a1d SHA256 (8.0-RC2-i386-dvd1.iso) = 34ae54a05ad5c0ac4a2d208edec95c218b0bf4e0a2458c97317f2cbebe4ce93b SHA256 (8.0-RC2-i386-livefs.iso) = e58b2b922ee1ee8fb56eeac36fe5e8eb35d7c9d7824535d770a7066faaafa8a4 SHA256 (8.0-RC2-i386-memstick.img) = aed885993e742a6c5ec17b4339ffab17449219e588d2e80457a0b7137d333f52 SHA256 (8.0-RC2-ia64-bootonly.iso) = 16967168e7eb1ea95d2aac1334d5046b307d06318613de329fc68fa65670e703 SHA256 (8.0-RC2-ia64-disc1.iso) = 6134adc5f124e397a5783a4d9ff8c94a3b942a06e2682e489ff484c8a87ea8d3 SHA256 (8.0-RC2-ia64-disc2.iso) = a4b471b71da9d4a047d6dbbdd2029ec2ec3ac6e7ebf96d993ded7917b0b8649b SHA256 (8.0-RC2-ia64-disc3.iso) = 4e44fb8dd42bab1775318ba6608656739533dfb60bccd5800877e1d693dd67a6 SHA256 (8.0-RC2-ia64-dvd1.iso) = db586139a60465d125ab89adcf28283528d0d62dd5ee6ef5dba6e90b0761107b SHA256 (8.0-RC2-ia64-livefs.iso) = 0a2d497a400166e4ea4a4191a92bb5d37959bedc53b2dea04b35c0cd0681ee66 SHA256 (8.0-RC2-pc98-bootonly.iso) = 62f4af328fbb3660b49b4ca75158731de457781b41f6f1fd15f8cb58c8e2769d SHA256 (8.0-RC2-pc98-disc1.iso) = 5551baa1205ad356c87ccc7685241d463dd8a26bde366fd8bdb4bde44188bf72 SHA256 (8.0-RC2-pc98-livefs.iso) = 2f195b71d73eaf4a76ac00522431e674f5a9b8272bb002c90c2c6d2a5491c4f5 SHA256 (8.0-RC2-powerpc-bootonly.iso) = d268f4cebd71bfbe7a6532270097b4934f49da518a51754429448ef30bf57db0 SHA256 (8.0-RC2-powerpc-disc1.iso) = b847889e72d5134b7ac6bf06244e7c919639d7d80a0001f6cfea5fc0c4c2847d SHA256 (8.0-RC2-powerpc-disc2.iso) = 2fe8a8f97821d2695b0f795eda62422433eae23dc1e6f5b7c38983e6c2431b25 SHA256 (8.0-RC2-powerpc-disc3.iso) = 24ccace776b897705ad10115287c9819bc3301aedaa4afd253addbc038178f0a SHA256 (8.0-RC2-sparc64-bootonly.iso) = ce24a908fce56afa6a7a29687d9fcc63ffe724d59014851344349702a1df5fd2 SHA256 (8.0-RC2-sparc64-disc1.iso) = d4b3974421b52ed89699422d9160396758249ddd8f82fa12a0339cbf023cf32e SHA256 (8.0-RC2-sparc64-dvd1.iso) = 999f52fe73d32be3008eb5b289882d50eee35f469e4bb122268dfacd2f1508f0 SHA256 (8.0-RC2-sparc64-livefs.iso) = 7e22429d82bce3c3b7e927a380c6ce136ce30811653fec94f369eef496810725 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
8.0-RC1 Available
) = 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) = abcc0c3d975df784eaa4840af1fc25f610f8699619142185c77b396e00aa 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) = 7cd4e68f0e6bdf95090121ffd89383134c7a6d1a18a800d58fb1dcd8d1c6 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 | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: 8.0-RC1 Available
On Mon, 2009-09-21 at 23:08 +0800, Chao Shin wrote: 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. Somebody is working on that, we hope to have it resolved before RC2. It's one of several things that is making having an RC3 likely, we would want there to be a reasonable amount of time for people to test the changes that would be involved in that fix (as well as the flowtable fix and a few other issues). -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
8.0-BETA4 Available
) = e2cc9393e0b596acdb36a8b07fbc480e MD5 (8.0-BETA4-sparc64-disc1.iso) = 706f2e57ff1502ccaac37dd4571d898a MD5 (8.0-BETA4-sparc64-dvd1.iso) = 9ac3509c8731874ae20009f170daf0e7 SHA256 (8.0-BETA4-amd64-bootonly.iso) = 3b4a1b964f64e68609f8010e43145c7a757c352e62b2b8128dff3947f08c330b SHA256 (8.0-BETA4-amd64-disc1.iso) = e42cb6a4d46fcc924615949fe9da4217f9c824e4c30fb6371787e28d5ec50ff8 SHA256 (8.0-BETA4-amd64-dvd1.iso) = 61bb39599c2b2b76de0643d677702683c4274901dbaaa3944b3a419402046dcf SHA256 (8.0-BETA4-amd64-livefs.iso) = f6b9fc2bfe74bb7bc730fa6786af09e4cca8d92a812ee1968283dff3eb6adc48 SHA256 (8.0-BETA4-amd64-memstick.img) = a930e419bed019114ddcf5833b3af1950f4ef32444bb02b1b84e84d91c754bda SHA256 (8.0-BETA4-i386-bootonly.iso) = c2adde76995cbc25ac16afb2c4cb46686df54435f64e98ae4701908f024a0102 SHA256 (8.0-BETA4-i386-disc1.iso) = 0bbee2a9ffd4c00070cae001652037c8b194502dfc1a35c3ac0da1172c26bfdd SHA256 (8.0-BETA4-i386-dvd1.iso) = 4dcd81040e977ff2f6c30aae04497416c2aec9eb8d4a5ac0dab6f2cd965bfaee SHA256 (8.0-BETA4-i386-livefs.iso) = fac4c8c08698c30801f4555d5127c8bb5d786d6bebe164fd27e66bea737526bf SHA256 (8.0-BETA4-i386-memstick.img) = 4a39d259b18f8d900a7bfc1878ed6ac4fda82812e13999da0265976eb1ba15e8 SHA256 (8.0-BETA4-ia64-bootonly.iso) = 5688b9c8bf13337835b2dce2fa7d6fb0ea17d397e927ef770d097a6728c8db23 SHA256 (8.0-BETA4-ia64-disc1.iso) = 33ddac157f6529bb31388d8c4ffdfb4824c989c0c0d843ecec071eb67ea36786 SHA256 (8.0-BETA4-ia64-disc2.iso) = ae71fd5d8d29666fa15689ddd8ffd45e3b6d354af9e1cb96b5a62280b452cbe5 SHA256 (8.0-BETA4-ia64-disc3.iso) = 330b43e5f81887de948257db46ed407a5c5a94c09e6d41155159e0617c0be53e SHA256 (8.0-BETA4-ia64-dvd1.iso) = 4324c3c08d625b92942424a1c6e14085593ee62237ddd4f2eac2f35d7fb0f27b SHA256 (8.0-BETA4-ia64-livefs.iso) = 860cad096ef74efa534bae3642dff5ec545ed47faa21a6cd65b197b12827885d SHA256 (8.0-BETA4-pc98-bootonly.iso) = 0ce882dd48863f2f4180cbdf5f17ff595d7942bf7ac84029adef27a65b1b5481 SHA256 (8.0-BETA4-pc98-disc1.iso) = 4815a84ef0e834d3d57f7420c1f25ff93d0e3b698cc6eecee8b587f9896edd01 SHA256 (8.0-BETA4-pc98-livefs.iso) = cb6ea4a931551c2220c739d66f05c120926a7c2650373fc72770a25ea5e10a3d SHA256 (8.0-BETA4-powerpc-bootonly.iso) = 6f97a8c061065661996e6efdad45bbbaaafc2e8f80717fa845b2bc3ae14d7212 SHA256 (8.0-BETA4-powerpc-disc1.iso) = 9b1fb4af1a9a53e5723fdfd897d8a57a4e815ada22637285b7360d24f512290c SHA256 (8.0-BETA4-powerpc-disc2.iso) = 8e82ccaca6673cb3177870748ffdcb891fb16904eacd98822cca31f9888656ae SHA256 (8.0-BETA4-powerpc-disc3.iso) = 651561d9021d5c68f266f21d6df31c87fec1368a428492274177810ea1333c3c SHA256 (8.0-BETA4-sparc64-bootonly.iso) = 35dd8a303df41cb7ca744c37aee104e18f441967a14a3c9eb36bc4bcaf78c01b SHA256 (8.0-BETA4-sparc64-disc1.iso) = 1d5ab4e67225a8640c9200424a140fff003203ab5edb855172d7030130974529 SHA256 (8.0-BETA4-sparc64-dvd1.iso) = 59ab2cca0fa637e9ef5007117f1005570c102cf4665009c6021992dd1b8bd77b -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
8.0-BETA3 Available
-pc98-livefs.iso) = d1c204282bd847a5f194fb9b70611bde MD5 (8.0-BETA3-powerpc-bootonly.iso) = 370566a1be53ec1098e246dd1a580d37 MD5 (8.0-BETA3-powerpc-disc1.iso) = 98a6b6ecfdad5c4b95c3c97d5a775d32 MD5 (8.0-BETA3-powerpc-disc2.iso) = 5ae8dd94f19a70d3c14c716cc2088ec6 MD5 (8.0-BETA3-powerpc-disc3.iso) = d9d4e3ae3b9e5b76ecbbe01e730056cd MD5 (8.0-BETA3-sparc64-bootonly.iso) = 70578049f21dfc3ab5728c2ad74ecce7 MD5 (8.0-BETA3-sparc64-disc1.iso) = 0eb834690e14254b432d0e4bc317b12e MD5 (8.0-BETA3-sparc64-dvd1.iso) = 49c468755c65c08bb08a7b112152dead SHA256 (8.0-BETA3-amd64-bootonly.iso) = 931982b67cfdb703398eaf4e1578b04be6d92f7fe10b39044f96396ac43f30b3 SHA256 (8.0-BETA3-amd64-disc1.iso) = 001fb1b22db7fbfe0b72cf1386ad7216e4116d05457d22a9177f52f9aaebff66 SHA256 (8.0-BETA3-amd64-dvd1.iso) = cb254b571c8b08de3d41b84bab4e3f5bce162e315441701951d3bc8e5b9241d5 SHA256 (8.0-BETA3-amd64-livefs.iso) = edb7e235d6da0493af7e292232c9f0b9034bb6bf670cbedee2f1d357de1f5dae SHA256 (8.0-BETA3-amd64-memstick.img) = f353979947b6c7ee792277daa64702f861979f0b04b6da9f50afe3529d519b8b SHA256 (8.0-BETA3-i386-bootonly.iso) = 15a074d80e3b5980febb85c920d51d74d8065cc6d005a4ec0c28d533a3533729 SHA256 (8.0-BETA3-i386-disc1.iso) = 131b08e65235295dc263e31d51d4ab9735a04497a99baa3ac3d1aca6e9053e46 SHA256 (8.0-BETA3-i386-dvd1.iso) = a1204d62b3569d84345ed3bc6fe2b24edb76df9aad550ea959d61e996710660e SHA256 (8.0-BETA3-i386-livefs.iso) = e5a73bf127ff0c5187270807e822c65a13975e6d622f2e61395176475378 SHA256 (8.0-BETA3-i386-memstick.img) = d87230eb92064088265f5f08fa927a11d8158bd930a36638c11240bf3521539f SHA256 (8.0-BETA3-ia64-bootonly.iso) = 5c7f22175bbdf21cb6116c7015e6fe49884d482dc09cee7fe3ad44f71651e6e6 SHA256 (8.0-BETA3-ia64-disc1.iso) = bf0f2bc9fe9d2f126ed54644a61ff689bdb0f9e5565db940ef53d5656ed59fc3 SHA256 (8.0-BETA3-ia64-disc2.iso) = 4e607da42eda1dac8c52039b37c04e1ed15820a97f7b3ffe9937956dd470ffa1 SHA256 (8.0-BETA3-ia64-disc3.iso) = a681b1dfd030604f40621dfddc1557a6bedc6b7d3ded85609f7ab41a574be70b SHA256 (8.0-BETA3-ia64-dvd1.iso) = 83d52c72d9f783cd0e1552bd9c3b9b84151fb0231e34a4f203694c8770258acf SHA256 (8.0-BETA3-ia64-livefs.iso) = c0bd93c28ba890d8d3160dabfaa24fd5dfe647f76ed3e4aafe4ea7f72bfe88dc SHA256 (8.0-BETA3-pc98-bootonly.iso) = cd6e0851931b39249bf8e472f5ec6734bb2d0a3f76d90e4fc534201bb29ecb79 SHA256 (8.0-BETA3-pc98-disc1.iso) = 0e61042a28c02ce391956073fab5230b1ec9e357e1ad374d068bd9a4eedc8985 SHA256 (8.0-BETA3-pc98-livefs.iso) = ba416b965c118c4e4add31ab83e12b65fa66427b0e2455b02e57d7582fd43616 SHA256 (8.0-BETA3-powerpc-bootonly.iso) = aed0212db2c5313345e843c258855c5a2bb1737b6c5a676b08cb993c6b125651 SHA256 (8.0-BETA3-powerpc-disc1.iso) = 12e774f12892f17c6a00d58694de71e462c73db22682d5866dac2b1972e6877c SHA256 (8.0-BETA3-powerpc-disc2.iso) = 86bf55b2cf3362e0c084e6f35fff18f43c19f64cf2680a4a98504e0b2e44853a SHA256 (8.0-BETA3-powerpc-disc3.iso) = 3157decf4700238719a963f6299c7264da223a845caef84b7d74e1f00f457e09 SHA256 (8.0-BETA3-sparc64-bootonly.iso) = 2f65aa2e0b61079dd806d997f25b3eb651e400d6797173b28b5e5ccec77f72fc SHA256 (8.0-BETA3-sparc64-disc1.iso) = 2d793f0ae01e54448f8111caefbb2baef32ac7ce4e8aee69aac9ed00f00aab9a SHA256 (8.0-BETA3-sparc64-dvd1.iso) = 1ae3a6b594867e1435f7d4e21893df75bb33ef5559979532698b01a79730edf3 -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
HEADS-UP: Shared Library Versions bumped...
First I want to apologize. This should have happened a bit sooner in our release cycle than now. To be honest I had slipped into We have symbol versioning for our libraries now mode. But only a few of the libraries currently have that turned on and I sorta forgot we still need to deal with all the shared libraries that do not have symbol versioning enabled yet. Sorry for the hassle this will cause. Today with svn commit 195767 I bumped the version number of all non-symbol-version-ed shared libraries in preparation for 8.0-REL. We do this just in case API/ABI changes occured in head between 7.0 and now, it lets us provide the older library versions as compatibility library ports in the ports tree. The problem is that as of the next time you update a machine that had been running -current you are best off reinstalling all ports or other applications you have on the machine. When you reboot after doing the update to the base system everything you have installed will still work because the old shared library versions will still be there. However anything you build on the machine after its base system gets updated would be linked against the newer base system shared libraries but any libraries that are part of ports or other applications (e.g. the Xorg libraries) would have been linked against the older library versions. You really don't want to leave things that way. The ports folks will be starting up a fresh package build now but it takes some time for full package runs like this to complete, get uploaded, and then propagate out to the mirrors. If you tend to use pre-built packages instead of building them as ports yourself you might want to just hold off on updating anything until they let us know a fresh set of packages is available. And BETA3 will definitely be scheduled for after the fresh set of packages becomes available. And again - sorry for the hassle. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: HEADS-UP: Shared Library Versions bumped...
On Sun, 2009-07-19 at 20:26 +0200, Thomas Backman wrote: On Jul 19, 2009, at 20:16, Ken Smith wrote: The problem is that as of the next time you update a machine that had been running -current you are best off reinstalling all ports or other applications you have on the machine. When you reboot after doing the update to the base system everything you have installed will still work because the old shared library versions will still be there. However anything you build on the machine after its base system gets updated would be linked against the newer base system shared libraries but any libraries that are part of ports or other applications (e.g. the Xorg libraries) would have been linked against the older library versions. You really don't want to leave things that way. So, to be clear: a fresh ports tree and portupgrade -af after building and installing r195767+ should be enough to solve any problems? (installkernel, installworld, reboot, portupgrade -af) Correct for those of you who let portupgrade do all the building for you (which the example command you give does). The reason I'm being careful is portupgrade can also be told to fetch pre-built packages. At the moment that will not work, if you use that approach please hold off until the ports folks let us know the packages have been rebuilt. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
8.0-BETA2 Available
) = 269ebf61580485eb8fc3abb063b5a309 SHA256 (8.0-BETA2-amd64-bootonly.iso) = c11389094ee73389eb3e3ad22e165f158cce0003431a88eb27ae253fd76b70a8 SHA256 (8.0-BETA2-amd64-disc1.iso) = 49121108535986690eebc7c894a56bdd1e4b5afc8ed1470afb0ebc79debb2c1e SHA256 (8.0-BETA2-amd64-dvd1.iso) = d3f36481fd022bad67cc020eeb19f261330c279592a0062c43804fdc32a0c08d SHA256 (8.0-BETA2-amd64-livefs.iso) = 35d02c1b6bdcc54721f955f3beb68c6e67b610554a2e28c28391041cdab75ddf SHA256 (8.0-BETA2-amd64-memstick.img) = 66eb336e4de03cc68f1929db233d3edb37fc05b814cde68fe8f618340b91cb66 SHA256 (8.0-BETA2-i386-bootonly.iso) = 904b8aa5380ea81604ea81c9c88b3bb3ade744a45cececa512fc78b07c1bbacd SHA256 (8.0-BETA2-i386-disc1.iso) = 5699c6e4f8a7084dc6d6fe835c1c40cc7b01614091b057df07d72537e8e33ef4 SHA256 (8.0-BETA2-i386-dvd1.iso) = f5cc663850f6e20ece9e7e2c6b9503b8f9599acfdd20e5a19ffad4541d33fc7f SHA256 (8.0-BETA2-i386-livefs.iso) = f2a50f00ba9f30c564fd7be320c7bcaf2b192a47e036cd97fa72092435e3 SHA256 (8.0-BETA2-i386-memstick.img) = 6d66fee850102d966b00123590f139fb38e6d33d818ff8c6ce58c4ae3853e209 SHA256 (8.0-BETA2-ia64-bootonly.iso) = 69da5d8fb3d17bade7b596f5bd81bacfb1c178bf184be462661786e99ac3f80d SHA256 (8.0-BETA2-ia64-disc1.iso) = c59b03585d364ad0b305eb3d71c168c0d1e0b100270802ed22efdc80de59f792 SHA256 (8.0-BETA2-ia64-disc2.iso) = 7f398777025c970f265446d18bb7f571a2078e147843bd1345827164a040b9f3 SHA256 (8.0-BETA2-ia64-disc3.iso) = cf4a0bb280892cc09af10f138aa3a8df7045380e63946427d582c8217ed3231c SHA256 (8.0-BETA2-ia64-dvd1.iso) = e1379d207a0659ab4397c1c84e7193e1efe0d04db96b21c712b1bdc9e86079ad SHA256 (8.0-BETA2-ia64-livefs.iso) = 3881e3eaba4988c23a3cf19d04c2e055b861288d938ad8c4352dacfd6a97c35a SHA256 (8.0-BETA2-pc98-bootonly.iso) = fc2f234ed68e0a3c1a254771485b012bf124009cb1a928e67204a2f1aad63519 SHA256 (8.0-BETA2-pc98-disc1.iso) = 7b5450fc0ae04ec80788a91b8d6caf449c22ed2e373ebf89263d2affebe74cf8 SHA256 (8.0-BETA2-pc98-livefs.iso) = cf9c823eb58fee48421c16900c270b97fefb61a1f90501791e88b74102862763 SHA256 (8.0-BETA2-powerpc-bootonly.iso) = 99d50bc3c35b36b41fe0871d3505d702c75a8025178dbc33603b77c9886d23af SHA256 (8.0-BETA2-powerpc-disc1.iso) = 4afdc4e8be4ea178ce791b5c3e1881538cc118b336c5337ce15d811e245a926d SHA256 (8.0-BETA2-powerpc-disc2.iso) = a7c21ffb213e0b73e24e5d9a317599445ac8c69cb37efa554768692622b176cc SHA256 (8.0-BETA2-powerpc-disc3.iso) = 6213f6a5e19a4146d6e20bffb36d6e1a7d3aa192db83f14f6ec599fa38472a6f SHA256 (8.0-BETA2-sparc64-bootonly.iso) = 998fcc77ec2675e7eb7d826ae87897bead56189cc79ede57b214d3357d56499d SHA256 (8.0-BETA2-sparc64-disc1.iso) = 22d61fc13dd544af390de56940e1a4c041abe18249cdc110ae02613d1f5d761a SHA256 (8.0-BETA2-sparc64-dvd1.iso) = 2478e8c3508e8b8f8b9f0ed6a9c67c0469375cb2ba224114583fe14da6fb237e -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 8.0-BETA1 Available
On Wed, 2009-07-08 at 22:01 +0200, Andreas Tobler wrote: I was successful in installing the image, although, a few packages did not install. I did a kern developer package. I guess the packages are missing on the .img? Correct, no packages with BETA1. It's probably the documentation packages it went looking for and couldn't find. I'll be providing at least the docs packages with BETA2. Not sure if I'll start trying to provide a larger set of packages for the DVD or wait for BETA3 for that (leaning towards waiting at the moment). -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 8.0-BETA1 Available
On Tue, 2009-07-07 at 16:05 +0300, Dan Naumov wrote: Just wanted a small clarification, does livefs based rescue mode mean fixit environment or not? Yes, that's what it means. It's known to not work at the moment but it's being worked on. I wanted to mention that because it might have been confusing given what I put onto it (the files needed for livefs mode are on it, sysinstall itself needs a bit more work though). But once that is working this is my guess as to what people would find most useful on such an image so I wanted to give people a feel for roughly how big they'll wind up being. It will basically be the dvd minus packages. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 8.0-BETA1 Available
) = b7561c27ea789447e368a1e2398249282ae46e8752a82bbb3614cb5db3d606e7 SHA256 (8.0-BETA1-ia64-bootonly.iso) = 6e9b9cc92a82b062cc5d9d51da7652a79097894b16e8c2cf8bcdb7b51c3aa576 SHA256 (8.0-BETA1-ia64-disc1.iso) = 52ca59f0129cda5651bf0aad3daa57a07a719580c3ece28be63178e40e6f0613 SHA256 (8.0-BETA1-ia64-disc2.iso) = f6e1bded3aec557e19ef0249b9c3b17ba3c5e0aca99d98ae697e6107c9bb3061 SHA256 (8.0-BETA1-ia64-disc3.iso) = b8b8e5ce0cca5eb3dd0dc8ea05b7de399cb937ecc4b960eb092e621cda22bbd5 SHA256 (8.0-BETA1-ia64-dvd1.iso) = 29d5852bef2d09c73075242ea2e2d35072a51b30b624d5229ed8aec6737cfbc5 SHA256 (8.0-BETA1-ia64-livefs.iso) = 0a92eb0f09dfd4f4ab0694fd94482e4682eded3425186737bd0e2440e957dd3b SHA256 (8.0-BETA1-pc98-bootonly.iso) = 5d77d1fb6a5d7e819b0d90d1848f7d029d64ce456ca550e3049d63eb5fc8891a SHA256 (8.0-BETA1-pc98-disc1.iso) = 5e11719fd24d8f8a9fd0fd4ce07c72509c197e48b1e45060d931b0f8bcad9335 SHA256 (8.0-BETA1-pc98-livefs.iso) = 271056add63d5e82f85a482cfd0efcfaaacb1b5941337fc459782e97577f3e0e SHA256 (8.0-BETA1-powerpc-bootonly.iso) = 60c984e47d8e71eb87ae382cb1bc19a0abd982095b5906dafb539e799ad0a51e SHA256 (8.0-BETA1-powerpc-disc1.iso) = 647b51471e71a8de9ab4a0c42fa94d869fae33a2f5f3a0aaa07592bb9854a49f SHA256 (8.0-BETA1-powerpc-disc2.iso) = 9a46aecda07f6b6fa040bf7c852c3a99eb27e8db529c8f26974d5a9a2ecf0b8d SHA256 (8.0-BETA1-powerpc-disc3.iso) = efe792cb535ea2a6ee821cdcd5fd1e5306e116e32b57e2f1e6d4309f672830ab SHA256 (8.0-BETA1-powerpc-livefs.iso) = 1b8e5c401bf5b14c0a14d91b21895ed2273287158e59a158313bcec43aead8ff SHA256 (8.0-BETA1-sparc64-bootonly.iso) = 2775ceec218f5fef0bc2d17ea80e1492f423307f27cec38df352b1e9ee6f96a4 SHA256 (8.0-BETA1-sparc64-disc1.iso) = 9eac5684c3c650e2cac01343c7933931aef0227bdb6e9a4931402ad0dd41b9c8 SHA256 (8.0-BETA1-sparc64-dvd1.iso) = 207268ec113811213d73b571c2322585c26cf6beae88e27e5680e77c93e249b2 -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 7.2-RELEASE Available
Just a quick note for those of you not subscribed to freebsd-annou...@. We finished up 7.2-RELEASE over the weekend. The announcement message is available here: http://www.freebsd.org/releases/7.2R/announce.html Thanks for all the help with testing during the release cycle. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: 7.2-RC2 Install Feedback
On Thu, 2009-04-30 at 08:55 -0500, Jon Loeliger wrote: Also, I banged my head against problems installing emacs (aborted with error -1), until I finally realized that xemacs-21.4 was already installed. I think there was some form of conflict (?) that prevented two versions from being installed. Seemed odd to me in any event, and not very evident why the (package) install was being rejected. This basic issue (package conflicts) has been becoming more and more of a problem. It's not likely we can do anything about it this time around but we'll think a bit more about what to include on the media going forwards. I also found Gnome2 and KDE4 are mutually exclusive due to package conflicts, you need to select one or the other. Just so you know - if there are issues with installing things and errors pop up you can often quickly find what the cause of the error was by pressing Alt-F2. You can get back to the primary screen with Alt-F1. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: Freebsd 7.2-RC boot problem
On Tue, 2009-04-28 at 09:52 -0300, Paulo Fragoso wrote: It doesn't print any message and after that short time BIOS try next device from boot order. First a question just to verify - is this i386 or amd64? I'm guessing i386. One more thing to try if you don't mind. Could you try booting one of the other bootable iso images (either bootonly or livefs), and if that succeeds when it reaches the first screen of sysinstall swap in disc1 before proceeding with a normal install. Thanks. Appreciate any testing you can do. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: Freebsd 7.2-RC boot problem
On Wed, 2009-04-29 at 11:33 -0300, Paulo Fragoso wrote: Hardware: MB: Gigabyte GA-M61PME-S2 acd0: DVDR HL-DT-STDVD-RAM GH22NS30/1.01 at ata3-master SATA150 ISO MEDIA BOOT 7.2-RC2-i386-dvd1.isoDVD-RW OK 7.2-RC2-i386-livefs.iso CD-RWOK! 7.2-RC2-amd64-disc1.iso CD-RWOK 7.2-RC2-i386-disc1.iso CD-RW,CD-R FAILS Thanks, greatly appreciate all the testing. As part of looking into this I went looking for another Gigabyte motherboard and through the past 2 days was able to test the same set of things with the same results. So far I haven't been able to reproduce this on anything but Gigabyte. This is such a bizarre problem I really needed someone else to confirm so thank you very much. Since there is a workaround I don't think I'll hold the release for this problem but we will need to mention this in the Errata (and possibly the announcement itself). -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: Freebsd 7.2-RC boot problem
On Tue, 2009-04-28 at 09:52 -0300, Paulo Fragoso wrote: Em 27/04/2009 14:16, Ken Smith escreveu: We need more information about how far it gets before it stops. Does it seem like it attempts the boot off the CD at all or does it just fall through to booting off the hard drive? It try boot from cdrom and after a little time it boots from next device. If it does attempt to boot off the CD does it lock up with no messages? If there are messages what are the last few things it says? It doesn't print any message and after that short time BIOS try next device from boot order. Thanks. That makes it sound like the BIOS doesn't think the CD is bootable but I'm not sure why. We'll need to try and collect more information from other sources to see if we can narrow it down (e.g. whether it happens on other vendors' motherboards or just Gigabyte, whether there are other combinations of SATA versus non-SATA optical drives that cause problems, etc). Just to collect as much information about this specific case as I can... Are you using CD media or DVD media? Is there a chance you could try the other type of media (e.g. if you're using CD media could you give DVD media a quick try?) just to eliminate that as one of the variables? -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.2-RC2 Available
On Tue, 2009-04-28 at 15:46 +0200, Matthias Andree wrote: Is there any schedule WRT the Release Notes? They[1] were still empty when I checked yesterday, and I find that makes it more difficult than necessary to actually test the RC. Nevermind the schedule, and release when it's done. [1] http://www.freebsd.org/relnotes/7-STABLE/relnotes/new.html They're being worked on now. I'm afraid the best place to get them might be /usr/src/release/doc/en_US.ISO8859-1/relnotes after a csup update (they've been updated after RC2 got built). -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: Freebsd 7.2-RC boot problem
On Mon, 2009-04-27 at 11:03 -0300, Paulo Fragoso wrote: I can't boot on cdrom sata, this problem doesn't exist in older releases. My motherboard is Gigabyte GA-M61PME-S2 On FreeBSD 7.1 my cdrom drive is detected this way: acd0: DVDR HL-DT-STDVD-RAM GH22NS30/1.01 at ata3-master SATA150 Just checking - is *everything* the same? For example is the media the same? Depending on a variety of things I've had issues with rewritable media versus write-once media, etc. The machine I test the release builds on before uploading them has a Gigabyte motherboard (G31M-ES2L) with a sata drive in it so it's not a generic sata doesn't work issue: acd0: DVDROM Optiarc DVD-ROM DDU1675S/1.10 at ata0-slave SATA150 If none of that helps we'd need more information about how far it gets before it stops. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: Freebsd 7.2-RC boot problem
On Mon, 2009-04-27 at 14:10 -0300, Paulo Fragoso wrote: Em 27/04/2009 12:05, Ken Smith escreveu: On Mon, 2009-04-27 at 11:03 -0300, Paulo Fragoso wrote: I can't boot on cdrom sata, this problem doesn't exist in older releases. My motherboard is Gigabyte GA-M61PME-S2 On FreeBSD 7.1 my cdrom drive is detected this way: acd0: DVDR HL-DT-STDVD-RAM GH22NS30/1.01 at ata3-master SATA150 Just checking - is *everything* the same? For example is the media the same? Depending on a variety of things I've had issues with rewritable media versus write-once media, etc. The machine I test the release builds on before uploading them has a Gigabyte motherboard (G31M-ES2L) with a sata drive in it so it's not a generic sata doesn't work issue: acd0: DVDROM Optiarc DVD-ROM DDU1675S/1.10 at ata0-slave SATA150 If none of that helps we'd need more information about how far it gets before it stops. I can say there is a problem to boot with cdrom since 7.2-BETA1. All system is same, all older version can boot in this machine: 6.1, 6.2, ...,7.1, etc. amd64 or i386. I've burnt 03 media to test 7.2-RC2, one cd-rw burnt with cdrecord and two cd-r burnt first with burncd and last was burnt with cdrecord. What I can do to help this release? We need more information about how far it gets before it stops. Does it seem like it attempts the boot off the CD at all or does it just fall through to booting off the hard drive? If it does attempt to boot off the CD does it lock up with no messages? If there are messages what are the last few things it says? -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: How do i fix the broken FTP structure of freebsd 7.0?
On Sun, 2009-04-26 at 01:42 -0700, wac wrote: vantline# pkg_add -r dkimproxy-1.1 Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7 .0-release/Latest/dkimproxy-1.1.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages- 7.0-release/Latest/dkimproxy-1.1.tbz' by URL vantline# ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/ packages 10/23/2006 12:00:00 AM packages-5-stable 4/4/2008 12:00:00 AM packages-6-stable 4/18/2009 6:16:00 PM packages-6.4-release 11/21/2008 1:33:00 PM packages-7-stable 4/18/2009 10:06:00 PM packages-7.1-release 12/22/2008 11:30:00 PM packages-7.2-release 4/21/2009 5:18:00 PM packages-8-current 4/16/2009 2:38:00 PM packages-current 2/9/2008 12:00:00 AM packages-stable 3/1/2008 12:00:00 AM packages-7.0-release is completely missing. Is there a way to fix this? How? What should I put in PACKAGESITE? Upgrading is unfortunately not an option for me. The old releases are available here, in roughly the normal layout: ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ The ports are in the ports/ sub-directory while the release bits themselves are in the old-releases/ sub-directory. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.2-RC2 Available
On Sat, 2009-04-25 at 15:21 +1000, Ian Smith wrote: On Fri, 24 Apr 2009, Ken Smith wrote: There is one known issue with 7.2-RC2. We switched from KDE3 to KDE4 Oh, I'd been kinda hoping that wouldn't happen till after release. I guess our KDE folks must reckon it's shaken out enough already now .. Yes, I contacted the two people who I was told most directly watch over the KDE ports and both preferred we shift to KDE4. Will kde3 still be able to be installed from packages? Will it be a big deal to prefer staying with kde3 (mostly re older small-memory laptops)? It will be available for install from packages through the net (FTP based install, or one of the other package tools that can be told to download the packages). I'm afraid I can't fit it on the ISO release media. Even with the DVD media we currently have a limit caused by the tool many of our mirror sites use for mirroring - files larger than 2Gb cause issues (that's why the DVD image is gzip-ed). We're slowly working to resolve that. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 7.2-RC2 Available
-RC2-pc98-disc1.iso) = 668f2fa947fec6a47eacdc5e60afce26 MD5 (7.2-RC2-pc98-livefs.iso) = f139461dc887e9c9a2cc37e72a3895a0 MD5 (7.2-RC2-powerpc-bootonly.iso) = 0d9f13f383bb3ca8ab203f074c9f52bf MD5 (7.2-RC2-powerpc-disc1.iso) = c8f0fd1ddc307b996be9634d4614fa9e MD5 (7.2-RC2-powerpc-disc2.iso) = 13afafea5edb6eab636ace3b484613e3 MD5 (7.2-RC2-powerpc-disc3.iso) = f98ac534b43da395588b7ecc9baa6e2c MD5 (7.2-RC2-powerpc-docs.iso) = b4d2198a14d4df52934a1a9945b21a5a MD5 (7.2-RC2-sparc64-bootonly.iso) = a23a0a1939512b0aabd2b1cd69965edf MD5 (7.2-RC2-sparc64-disc1.iso) = 7cda09bbc7fccb21eb8b1c53f3a0839c MD5 (7.2-RC2-sparc64-disc2.iso) = 84ab30153c090708c7a045d1d0ea948f MD5 (7.2-RC2-sparc64-disc3.iso) = 6a0580e55194c1106ac529154105bba7 MD5 (7.2-RC2-sparc64-docs.iso) = 9c2def8858cc9290cd8c888f9c123002 SHA256 (7.2-RC2-amd64-bootonly.iso) = f6db4b270a25f49403b032fd26917f84ec3a56ac130bebd2a2f5fe0d10dd3831 SHA256 (7.2-RC2-amd64-disc1.iso) = 0a9f053f0804fbb18f3e9ce4dd2233e762e83b5fe5fd3b968d85656fedc9 SHA256 (7.2-RC2-amd64-disc2.iso) = bc42569435d5ad3ffcc428b82ff9735bf4875f5a902a43a7467bc45b1d0b68cb SHA256 (7.2-RC2-amd64-disc3.iso) = 295ca90a67d01fa79b12fda4e2db88b1ed5317477d01c5d8c219b5cac011 SHA256 (7.2-RC2-amd64-docs.iso) = ad6f7f03e9d1a86e01869bf393e8a8d8d1ff6b66a430a5685631015a99335bc7 SHA256 (7.2-RC2-amd64-dvd1.iso) = 84a9c561fc11c64ce6cfcd98afa95a6e5e255ed4ad431672a1d39602f6c47921 SHA256 (7.2-RC2-amd64-livefs.iso) = 2cb6000b04905edc2dc3d3d9f892ef4d88373ab87ed2baa12b62713fb382356a SHA256 (7.2-RC2-i386-bootonly.iso) = 42e01823d398f00f8bc75223fdd332288074357e0d9dd276cc21a9deb6236a84 SHA256 (7.2-RC2-i386-disc1.iso) = c484d3c2b59238b1e3485b986c6c12e42abe73de66b6a8a2f0bc2a471b4d7850 SHA256 (7.2-RC2-i386-disc2.iso) = 9e500ec3a14434580a2f84afd3fd4e12cd70bde1b00258966c799353350bd856 SHA256 (7.2-RC2-i386-disc3.iso) = 6bb234ed16f0a013e042c2d3c3064a029c1d99e80e7df9f2e9fe58b10bec SHA256 (7.2-RC2-i386-docs.iso) = 3898d5782f8523fbc2840112f4fd8974aadbc0c3fde96f84254f911bb741a56c SHA256 (7.2-RC2-i386-dvd1.iso) = 8dc78e1009c04afe970cacf8ddc4d85a2ad60a8aee942159d7d59abd35f90e1d SHA256 (7.2-RC2-i386-livefs.iso) = a5a96df728b5a89353cdd6c96cdd31bcf3d2eb3f1a1986fa971d8ccaa2c23bc1 SHA256 (7.2-RC2-ia64-bootonly.iso) = 6e5aa2bcd0fcd12e6855d86885bf2bcb0921d621e63e091ce97d5e2f615e2feb SHA256 (7.2-RC2-ia64-disc1.iso) = a911d2683a1adb1c67625e20245bd96beaf933541ad158d6d91956eab3ea7b1e SHA256 (7.2-RC2-ia64-disc2.iso) = f1c163c1b723d16a81345de254a28c000d6c86770560a1031a652572ff9f58a6 SHA256 (7.2-RC2-ia64-disc3.iso) = ccef3f2a636b98c17ac97ac6a6aebe87f8bbc3317fd72c7d8e7cfbe179180101 SHA256 (7.2-RC2-ia64-docs.iso) = 086c423590302439ecdf90f6edf7ed8a07d137b01b8d8f94d2f70874fa968868 SHA256 (7.2-RC2-ia64-livefs.iso) = bdd30d85fbc4394249cefd52c4be3b3f4af4d30f4fee76f6f78f2cfab7da246c SHA256 (7.2-RC2-pc98-bootonly.iso) = 1b33d61bd84422c5f0678997636daba2c95a038345b6776851b1e6f52e4a4ceb SHA256 (7.2-RC2-pc98-disc1.iso) = 6bb6185bc86625bb7e40e1ab42b792d21c726590788ed4ffb2c7ab74b804b10f SHA256 (7.2-RC2-pc98-livefs.iso) = 1d0f45afb38db0c19616ace415e23123dc33ef733d9302a58ff1cf80a9003025 SHA256 (7.2-RC2-powerpc-bootonly.iso) = 98353ca2e0a33739ae482444f0411f691388bf4a167659a799427cb40b5a43e7 SHA256 (7.2-RC2-powerpc-disc1.iso) = 6a760fb61a8a1c93ac3e85a1be6a41595763dde98f69721f335296fdd15871c4 SHA256 (7.2-RC2-powerpc-disc2.iso) = e91e7a1e70141e8adc7b7a7619386d85a0c7615d2be98b9d2d69779b9fe83f5e SHA256 (7.2-RC2-powerpc-disc3.iso) = c570bf476bef53149bf044291e2be48801b49d1e7d8eea524cc6ddc66b1db42d SHA256 (7.2-RC2-powerpc-docs.iso) = 8bf88f3aede27dc6e0c5defa0e87284509a2639e8d1432a74d279e77d7f7f720 SHA256 (7.2-RC2-sparc64-bootonly.iso) = 1e7446441becf32bb8b3071e0e6ae2e9dee15e021d95155e8f7fbd09ce5cc31c SHA256 (7.2-RC2-sparc64-disc1.iso) = 2ef711d9f7113bd2bd8b6cd9b6ed19fb0ea0cff07bb496e5542d7b841893aacf SHA256 (7.2-RC2-sparc64-disc2.iso) = 5352a810264e07537a4792d2371eac72895930d85f30d9a4abf0761a89fc01b3 SHA256 (7.2-RC2-sparc64-disc3.iso) = 9dd96065af1a5819627aaf245bbb6ec98defc5636d339f4370f11b1b06b83729 SHA256 (7.2-RC2-sparc64-docs.iso) = 5a5fa0424bae677ec281b57e6594aee02c2cea62b8862f1beb1b106c2936ad68 -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.2-RC1 Available
On Sat, 2009-04-18 at 00:40 +0100, Pete French wrote: - 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. We will, and if we do wind up shipping 7.2-REL with lagg(4) broken (there is still time for a fix if we find it fast enough so that's not definite yet...) apologies in advance. At least as things stand now it seems like the current driver is noticably better than the previous one in most regards so deciding whether to ship with this breakage versus reverting to the older driver isn't a particularly easy decision. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.2 RC1 amd64 Installation
On Sat, 2009-04-18 at 19:04 -0400, Mehmet Erol Sanliturk wrote: Thanks for the testing and feedback. I have installed FreeBSD 7.2 amd64 RC1 from DVD .iso to test its installation issues . It detected hardware correctly and installed without any problems , but during installation of the packages the following errors occurred : Add of package ...name of package... aborted , error code 1 : apache-1.3.41 links-0.98,1 apache+mod_ssl-1.3.41+2.8.31 ghostscript7-nox11-7.07_20 emacs-22.3 Number of failed packages is significantly less than failed packages of Release 7.1 amd64 installation . Due to failed package installation , at the end Gnome in 7.1 Release and Stable was unusable , at least because terminal was not available in Gnome menus with nearly empty menus . To be honest it never occured to me that someone would attempt to install all of the packages (or at least as many as you indicated in your summary that you did). The package failures you mention were almost certainly caused by conflicts (e.g. apache-1.3.41 and apache +mod_ssl-1.3.41+2.8.31 failing because apache-2.2.11_4 got installed first). When deciding what packages to include on the media as of late I haven't been taking the issue of possible conflicts into mind. Like I said I'm afraid it just never occured to me someone would just select virtually all of them as you did. I'll take this into consideration moving forward but just so you know it likely won't be addressed as part of 7.2-REL. It's likely you would need to be at least a little more selective in what packages you install if you want to avoid these sorts of package install failures caused by conflicts. Other points may be the following : (1) During user definition password confirmation is not asked but in root password definition it is asked . For the user , the same password entry box may be re-used for password confirmation without changing screen design because entered password is not plainly visible and during password confirmation it is not necessary to keep it there , and it does not require much work to include it . ( During installation of 7.1 , I carefully first recorded password on paper , entered it , later it did not worked . ) (2) CD/DVD drive is NOT released when the message ... ( be sure to remove any floppies/CDs/DVDs from the drives ) . Those are both fixed in head (what will become 8.0). I chose to not MFC those changes because they rearrange questions which might throw off people who are used to the older behavior, it's best to phase in that sort of thing as part of a new branch. (3) When shutdown is selected from Gnome menu either by the first user or the root , within displayed dialog box there is no a Shutdown item . It is necessary for the root open a terminal console , and enter shutdown -p now command . That one is a question for the Gnome folks but I *think* that's the intended behavior unless you configure the machine to launch the graphical interface as part of booting up. :-) -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.2-RC1 Available
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 | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: problems with 7.2, vm_page_insert: page already inserted
On Sun, 2009-04-12 at 02:04 +0200, Raul wrote: I've rebuilt all ports twice without a glitch, except isc-dhcp30-server but that's another story. Can this double rebuilt help somehow with that sort of error?. I'm still out of ideas ... If the double rebuild did help somehow it's still an issue that would need to be addressed. Stuff user-level does shouldn't cause the kernel to panic - that's never a good thing. You're the second one to report this panic so it's caught our notice as something to watch over. One report of a panic like this is potentially issues with memory errors or any number of other possibilities given this area of code but more than that deserves us paying more attention to it. Mike, you were the first to report this - have you had recurrences? That said if there is a bug it's likely to be something fairly difficult to reproduce (lots of people are running 7.2-PRERELEASE and so far only two reports of this issue) so it's not a shock for you to have only had it happen once so far. Odds are it takes a rare sequence of events to trigger it. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: problems with 7.2, vm_page_insert: page already inserted
On Sat, 2009-04-11 at 23:35 -0400, Mike Tancsa wrote: I am wondering if it was an issue of not having swap. Raul, Any chance your machine might have somehow run low on available memory (either by not having swap enabled, or perhaps not enough swap space)? Thanks (and thanks Mike). -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.2-BETA1 Available
On Fri, 2009-04-03 at 00:43 -0400, Ken Smith wrote: The first of the test builds for the FreeBSD 7.2-RELEASE cycle is now available. Well, sort of. Sorry, it's been a couple months since I uploaded something bigger than 2Gb (the dvd images) and I forgot the mechanism that some mirrors use to sync with the master site chokes on files over 2Gb. So the mirrors that use that mechanism to sync won't have it for another couple of hours (I just gzip-ed the dvd images now). If the place you normally get it from doesn't have it at the point you want to download it I know ftp10.us.freebsd.org has got it. By tomorrow all the mirrors should have it. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 7.2-BETA1 Available
) = 1133fbb4d65afc242c44ea10dba13071d8254d9afb03e9b47668a40197233258 SHA256 (7.2-BETA1-amd64-livefs.iso) = 29d7de7cf139c6b9f1be459f0d7cc50767563d433db6a3eafda880dbfb8059c5 SHA256 (7.2-BETA1-i386-bootonly.iso) = b4d11881cb2209c0d2adab4b4e880ba978b19e38de2b9e78b263341194b6be8b SHA256 (7.2-BETA1-i386-disc1.iso) = 71375c06038a1e18ad769d6585a91449739aafc1e84fdce5d30d84992f6aaf99 SHA256 (7.2-BETA1-i386-disc2.iso) = 75c18bafcf7aae2fb805bd0457ee2bcf51649579e13357102af6dbec72bff450 SHA256 (7.2-BETA1-i386-disc3.iso) = 58e1feb8f84c80e884abec1a509575a96d346d6fd3eea505b61df4b90f0c4c93 SHA256 (7.2-BETA1-i386-docs.iso) = 6bded95d0dfa3dcb252364e4fdde757046bdcb30b6efd0b4d6d130dfec118762 SHA256 (7.2-BETA1-i386-dvd1.iso) = 14ad7e6f0b63fea970733786f2b7705771d06fe1ba980a02c45cf7357b263577 SHA256 (7.2-BETA1-i386-livefs.iso) = cbab873d5bd28ed59cc154bf92d7497546b9d1fb286391cf9e5b7de6fb9a0bb0 SHA256 (7.2-BETA1-ia64-bootonly.iso) = 7d102500543faaab90a5a5d30bec5f493cd4574785a7e33a8aaad2bf6bddd878 SHA256 (7.2-BETA1-ia64-disc1.iso) = 5d6ffec1a0da1b4d65e87ae658e12873ab7b979b77f83ff9090701234a2cce29 SHA256 (7.2-BETA1-ia64-disc2.iso) = 59914cc7514296ee116953bf9eb153e9be795c06e3b63eca52b2f7e89b9d2bbe SHA256 (7.2-BETA1-ia64-disc3.iso) = cd97b56a4a504f25dc3529ca403df9bb28e5cb066efb2820aeeff0421a9e23b4 SHA256 (7.2-BETA1-ia64-docs.iso) = 611ea6c453d4ee9e91bad7f491d53e994c4dabce487250af26e4a0d957abf2ca SHA256 (7.2-BETA1-ia64-livefs.iso) = 128751bcd2eaee9f723efc1cee20f19484e6d328bc0a6e2ade21b458f795058a SHA256 (7.2-BETA1-powerpc-bootonly.iso) = d6851b9b1503e69bdb2b585b9ed3f52f8c8ccf3c8067d37af7ac789149044e5c SHA256 (7.2-BETA1-powerpc-disc1.iso) = b51cf856031a7903d987d25c0a1dac7e4b40db948342f5e654a27b8194422032 SHA256 (7.2-BETA1-powerpc-disc2.iso) = b7a8d8ffa6a3b6e95f3dcdbb6fb4044755e595687c33112c91d9f8dd5e4df826 SHA256 (7.2-BETA1-powerpc-disc3.iso) = 4b6180318ea8874faf5b661b8de9ac1b1d310cc84a759e454530611ad525eb05 SHA256 (7.2-BETA1-powerpc-docs.iso) = 9df4fe36d4f020f2f0af1605f237b7fb454150477560f1cd9a92bb9aed30f2de SHA256 (7.2-BETA1-sparc64-bootonly.iso) = 348fcd9ca7f990247e84b964972be26441815e870676ccd10b1db9959b6a9a3d SHA256 (7.2-BETA1-sparc64-disc1.iso) = 72f4460eadd5509a0524bdd978fe6e4d348a9b8dc81c8ee66fa03945113c72e3 SHA256 (7.2-BETA1-sparc64-docs.iso) = dcf798bf11e792d2441a071cab96c81abf826dee18f31e21d9a4fa89c5f9e2f1 -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.2 Release process starting...
On Wed, 2009-03-18 at 10:23 +0100, kama wrote: Is it possible to get back the todo page during this release phase? During the last couple of releases I simply didn't have time to do everything and this was one of the things that fell by the wayside. After the dust from 7.1 settled we started to make arrangements for someone else to set this up and watch over it for us during the release. It might take him a little time to get rolling with it (as in it might not appear immediately upon the release cycle starting) but hopefully we will have something along these lines come back at some point during this release. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 7.2 Release process starting...
We're starting the release process for FreeBSD 7.2-RELEASE. The major highlights of the schedule are: Code Freeze:March 23rd BETA1 March 30th Branch April 10th RC1 April 13th RC2 April 20th Release:May 4th The full schedule is here: http://www.freebsd.org/releases/7.2R/schedule.html though most of the other events haven't been given specific dates yet. Since it's often the case that developers process quite a few outstanding MFCs during the last couple days before a code freeze starts I have changed RELENG_7 to say it is 7.2-PRERELEASE now as a bit of a heads-up that the release cycle is imminent. You might need to be a tiny bit more careful using RELENG_7 right now because the odds of you getting a snapshot of the tree taken part way through someone doing something that required multiple commits goes up during this phase of a release. Thanks. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: Big problems with 7.1 locking up :-(
On Mon, 2009-01-12 at 21:35 +0100, Tomas Randa wrote: I have similar problems. The last good kernel I have from stable brach, october the 8. Then in next upgrade, I saw big problems with performance. I tried ULE, 4BSD etc, but nothing helps, only downgrading system back. Now I am trying 7.1-p1 and problems are here again. Mysql is waiting a lot of time with status waiting for opening table or waiting for close tables I have 32bit FreeBSD with PAE, 1x xeon 5420, supermicro motherboard, areca SATA controller. Could not be problem in da device for example? Thanks Tomas Randa Could you give r186860 a try? It is an MFC into stable/7 so if the machine in question is something you can experiment with just updating to stable/7 would take care of it. Otherwise if you could just manually apply the patch to a 7.1 source tree and do a test build of the kernel that would also do it. I'm not experiencing lockups but this patch helped a lot on a machine I have with a particular disk I/O pattern that resulted in extremely poor performance with 7.1-RELEASE. This patch brought it back to its normal performance level. Thanks. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: 7.1 Live Filesystem CD
On Mon, 2009-01-05 at 20:53 -0800, Doug Hardie wrote: Is the Live Filesystem CD supposed to be bootable? 7.0's was but I can't get the 7.1 disc to boot. It works fine if I boot from CD 1 and then switch. Yes, it's supposed to be bootable. Works for me. Which architecture? -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 7.1-RELEASE Available...
Just a quick note for those of you not subscribed to freebsd-annou...@. FreeBSD 7.1 is (finally...) released. The announcement is here: http://www.freebsd.org/releases/7.1R/announce.html Sorry for the delays and thanks for your continued interest in and support of FreeBSD. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.1 svn186551
On Fri, 2009-01-02 at 21:09 +0100, Oliver Pinter wrote: Hi All! I have the question, why reverted the ICH10 support from 7.1? This is the svn commit: http://svnweb.freebsd.org/viewvc/base/releng/?pathrev=186551 What is the PR number of the base of this commit or what is the problem description? I have a motherboard with ich10r with 3 sata2 disc (hitachi) + 1 sata dvd-rw (samsung), without any problem. Sorry for bad spelling or english Unfortunately most of the email traffic related to this was off-list. There was one message here on list from Greg Miller saying his system locked up and giving a date for when the problem got introduced which was between 7.1-RC1 and 7.1-RC2 so it had been a regression that snuck in while we were in the RC phase. It turned out the MFC that brought in support for that chip was pulling in pieces of ATA from head that had been intertwined with other work and it seemed likely the MFC wasn't complete - more of the ATA pieces from head would need to be pulled in to stabilize it. Since we were already so far behind on getting 7.1 out we opted to back out the change rather than try to work out what else needed to be MFCed (which would have definitely required RC3 if we tried to do that). Sorry, it will just need to wait for 7.3 (though hopefully this plus the extra stuff needed to stabilize it will work its way into 7-STABLE in the not too distant future). -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 7.1-RC2 Available...
) = 3b25fe5c5f3dc2a3b388ebb0210c20c0 MD5 (7.1-RC2-ia64-disc3.iso) = 636bac3172ecd6ad55228365915a046c MD5 (7.1-RC2-ia64-docs.iso) = 8424225487159edbb3d6754b282f0430 MD5 (7.1-RC2-ia64-livefs.iso) = 47e0acc9f2011cf11756394ac4bfe16a MD5 (7.1-RC2-pc98-bootonly.iso) = bf2790bcb75096bf657a48f77fa33546 MD5 (7.1-RC2-pc98-disc1.iso) = 5d87d2c2924162acb125f5b1a46705ab MD5 (7.1-RC2-pc98-livefs.iso) = 46da1e7e223bf68b61f5c38a191ee865 MD5 (7.1-RC2-sparc64-bootonly.iso) = 97335ef101e32572757762a27e844769 MD5 (7.1-RC2-sparc64-disc1.iso) = 966090d9c70dcaadba6b00832d8b7533 MD5 (7.1-RC2-sparc64-disc2.iso) = f5e8780d0ba9f4f89f27cdf51eb17d5d MD5 (7.1-RC2-sparc64-disc3.iso) = 853a981ea3ffe95ef8cf82e9cd439e40 MD5 (7.1-RC2-sparc64-docs.iso) = 3001db73b78adc882c62a357d0a84422 SHA256 (7.1-RC2-amd64-bootonly.iso) = e1b6958a8f08748c1847312fab8bd2c9bc433d7c519e92495c35ea13c5cac64f SHA256 (7.1-RC2-amd64-disc1.iso) = 7da2bb04862608c4541cd907dcc5b802f84a4f7350ff1aeda6ec3a981e33f051 SHA256 (7.1-RC2-amd64-disc2.iso) = 620de9a6c57e309874d76cd08a0007845c19209b676d17a6c9930b7f16f87216 SHA256 (7.1-RC2-amd64-disc3.iso) = 6b796ff00a10ba5b0eb269a68a4a5370383d5daf2577f59b1ceefc303f97feab SHA256 (7.1-RC2-amd64-docs.iso) = c87064dd86ec849748f35a0de6e2e25f1b35f745351651d6f382781bfef99223 SHA256 (7.1-RC2-amd64-dvd1.iso) = df762671f0d2469612210b76d2feac0bf38d710f39c4914891180228fc8b5dcb SHA256 (7.1-RC2-amd64-livefs.iso) = 4598a0f8944fb177b289c9e4bd55bf353a2876ae90db585d8ba31daacd6f46b3 SHA256 (7.1-RC2-i386-bootonly.iso) = ee1da8333b57e51ecc73f643bee38356f40d18722d37b506c5b88baa19346d69 SHA256 (7.1-RC2-i386-disc1.iso) = 4a5c2e58a3d92fc344b92b8bf86b29f5a0925365c8c6bf08b444f70fda94f6d5 SHA256 (7.1-RC2-i386-disc2.iso) = 74eb1f29a82b8a44d4f91989f217f2ffadee0dd71458e7888c88dfe5a154b788 SHA256 (7.1-RC2-i386-disc3.iso) = f7ee665dd4f03feafa371db83cfa9d42845909788ade888a3115da738fa71d07 SHA256 (7.1-RC2-i386-docs.iso) = 352fbc6c231a0379c4b3a7612f47b9a283ea47af4d2237596fec5710bbab4029 SHA256 (7.1-RC2-i386-dvd1.iso) = 02a5eb11de9dd2fb6922802abdb385586f8e2e90628dbdef81c5373d67c25c78 SHA256 (7.1-RC2-i386-livefs.iso) = f0d788c045cc3c3e243048de022db63dc83db2ae8d9227f557d6d907b36f880d SHA256 (7.1-RC2-ia64-bootonly.iso) = 8bd8b31968406971784b225261524044c4409c9d0a6e28a649846dcce1a7adf2 SHA256 (7.1-RC2-ia64-disc1.iso) = 48ca1c5b0e5afc98849d3f11b6f7fac65ca0083d26409c1b9faf4963e5176baf SHA256 (7.1-RC2-ia64-disc2.iso) = 4e30b2eff68b3dc050d791d687968b5744335c13a2a1921b8d1730fa7c1d85cf SHA256 (7.1-RC2-ia64-disc3.iso) = c6f791f6cddef9fdd5964981916c28f093bdfcba3c00b8094a84e6c15a0e37ba SHA256 (7.1-RC2-ia64-docs.iso) = 011524d3f9fc0be1ef839a8648c31db457a3d2f1b6458949a71ec5bbb01d0cb4 SHA256 (7.1-RC2-ia64-livefs.iso) = 514bb8294a6ce6f8c82d6082d19d2a77c86bb7ff31950479e41b36fe6ae8495d SHA256 (7.1-RC2-pc98-bootonly.iso) = 3ed13c6dbb85665e0a34807ac6003cfcafe9b3ccd27beb6d9db0c59b0cf3764a SHA256 (7.1-RC2-pc98-disc1.iso) = 514691424950d431f91ad0b0e45563d8e81550016ac600d3d9a2eb42666a20ef SHA256 (7.1-RC2-pc98-livefs.iso) = e0a39d59c14727d2293a07a57e826ae5e921428f84bda8a320c4d19f03861633 SHA256 (7.1-RC2-sparc64-bootonly.iso) = 348fcf313f93dc78770ccc80a7b8a9b2bdf90de6f62c88f87f778c87bd1b9658 SHA256 (7.1-RC2-sparc64-disc1.iso) = 3474d05e71c43418d10c1327d013f7e0adf599b4cb92d31e333a804728422aa6 SHA256 (7.1-RC2-sparc64-disc2.iso) = e4097cb638be81e5ec4cc0ca685cfe9e8b5c09a1bb080adcfbd579422db4d27c SHA256 (7.1-RC2-sparc64-disc3.iso) = bc3558b1c0159381731012d2b4776e46719448df75d579c7f6a399712c671fdb SHA256 (7.1-RC2-sparc64-docs.iso) = 80e892dbdb51120347a40354fa1fff591f1ecb862d4cf966736f9d1849d5597b -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.1-RC1 Available...
On Mon, 2008-12-22 at 14:38 +0100, Patrick Lamaizière wrote: Le Tue, 09 Dec 2008 21:39:26 -0500, Ken Smith kensm...@cse.buffalo.edu a écrit : Hello, So... Two show-stoppers, one Security Advisory, and one Gee. Did we really implement that new interface that way? That needs a bit more work. later... Can we know what were these two show-stoppers? In the past there were some informations about show stoppers on the FreeBSD's web site but i can't find them. I'm asking because i run 7.1 since the -PRERELEASE and it looks solid as a rock. The two show-stoppers, which were worked through quite a while ago (like I said before its been a couple other issues since then not necessarily directly related to stability) were: - routing table locking issues, which would under the wrong set of circumstances cause panics, most often it seemed during boot. It seemed to depend on how active things like the arp entries were, etc (as in didn't always cause a panic for any given machine as it booted, it was somewhat random). - huge performance drop on certain things that got traced to changes made to malloc after 7.0. Sorry about the lack of something on the Web site. We're working on ways to fix issues like that during the next release. The past couple of releases we've known I have communication issues that I meant to try and fix when things quieted down after the release. But then things were quiet and that sorta never happened. So we're starting to work out what needs to be done differently during 7.2-RELEASE now while the list of things not being done is freshly in everyones' mind instead of waiting to talk about it later... -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.1 - Actual schedule?
On Mon, 2008-12-22 at 20:07 -0700, Brett Glass wrote: The schedule for release of FreeBSD 7.1 at http://www.freebsd.org/releases/7.1R/schedule.html is so woefully out of date that we've given up waiting and built a bunch of systems with 7.0-RELEASE, even though clients were asking us to put 7.1-RELEASE on them. Where can one track the actual progress toward a release? There appears to be no to do list (as there was for previous releases), and therefore no way to easily keep abreast of progress, snags, etc. Yeah, sorry. I've apologized a couple times here about the communication issues and indicated its actively being worked on for next time. This time is something of a lost cause at this point. I just sent out the request that the builds for 7.1-RC2 begin, which unless something *really* *really* catastrophic comes along will be the last of the public tests. If that's the way it goes 7.1-REL will happen about 1.5 to 2 weeks from now, maybe a bit less. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: visibility of release process
On Tue, 2008-12-09 at 15:19 -0600, Kevin Day wrote: [ Other points were not ignored, just nothing to really say about them other than Yes and/or Will try, etc. ] * More notice to hubs@ before the release notes are generated. The releases always come with a At the time of this writing, these mirrors have the full distribution list. If it was announced to us mirror operators before that list is made, we could make sure we were synced in time to be included. Maybe even a semi-shaming of These mirrors do not appear to have the required bits:. The difference in bandwidth we see on our public mirror (ftp3.us) is pretty extreme if we're listed there or not, which seems to be a 50/50 coin-toss on the last few releases. I'm honestly not sure why, since we can easily pull 50mbps from ftp-master. I have absolutely no clue how to fairly handle what needs to be done with this so, as you noted, its something of a coin toss at the moment. The issue is that the Release Announcement needs to include a list of FTP sites, but the list can't be too long (as in can't be every mirror site we've got). The Release Announcement should be relatively short and to the point. An exhaustive list of every mirror is a bit too much in that regard. Ideally we'd just say Its available on a mirror site, get it from there.. But people want easy so we need to include something to click on. With the 7.0 release I tried giving just the URL of the primary site (ftp.freebsd.org) but that proved people don't just want easy - they're lazy. For the most part they just clicked on that and didn't look around for a mirror. Hence your observation about the difference in bandwidth when you're listed versus when you're not listed. Since we don't have any sort of click here and automagically land on a nice fast mirror real close to you I basically make a quick survey of some FTP sites shooting for having several of the primary mirror sites (ftpX.freebsd.org) and a sampling of geographically diverse country mirrors (ftpX.au.freebsd.org, ftpX.ru.freebsd.org, etc.). If you're one of the ones I check and if you've got the right sparc64 checksum file (I'm looking for sites that carry everything, and since sparc64 is usually the last to get loaded on ftp-master ...) you make the list. Sorry, I know it sucks. Until we've got something automagic I'm not quite sure how to fairly handle having a list that's not too long for a release announcement but still providing a reasonable starting point for people who want something to click on in the release announcement. -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 7.1-RC1 Available...
So... Two show-stoppers, one Security Advisory, and one Gee. Did we
really implement that new interface that way? That needs a bit more
work. later...
FreeBSD 7.1-RC1 is now available, the first of the Release Candidates.
There will be at least one more Release Candidate before the release so
the release itself is likely around 3 weeks from now IF no new
show-stoppers are uncovered during testing.
In addition to general testing we're looking for information about
potential problems with the boot loader. There has been traffic here
about problems but the reports haven't helped narrow down the causes
yet. So far it seems to be related to USB keyboards and at least so far
systems with more than one processor in them. More data points like
cases where a USB keyboard was not involved as well as if possible
things like which motherboard it is might help us narrow down the cause.
Testing on a variety of motherboards, of varying ages and manufacturers
would help.
And a late arrival that's not possible to test without the packages,
sysinstall's issues with excessive disc swapping when installing large
sets of packages off the CDROMs should be fixed. Given the package
layout it should ask for a disc no more than once. Testing to make sure
that's working would be appreciated.
NOTE: If updating from a 7.0 or earlier system due to a change in the
Vendor's drivers certain Intel NICs will now come up as igb(4) instead
of em(4). We normally try to avoid changes like that in stable branches
but the vendor felt it necessary in order to support the new adapters.
See the UPDATING entry dated 20080811 for details. There are only 3 PCI
ID's that should have their name changed from em(4) to igb(4): 0x10A7,
0x10A9, and 0x10D6. You should be able to determine if your card will
change names by running the command pciconf -l, and for the line
representing your NIC (should be named em on older systems, e.g. em0 or
em1, etc) check the fourth column. If it says chip=0x10a7 (or one of
the other two IDs given above) you will have the adapter's name change.
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.1/
where ${arch} is one of amd64, i386, ia64, pc98, powerpc, or sparc64.
The ISOs for amd64, i386, and sparc64 include what is expected to be the
final package set. For all architectures the ISOs with disc in their
names are CDROM-sized, if you intend to install a variety of packages
during installation you will need all three. For amd64 and i386 there
is a gzip-ed iso with dvd in its name which is DVD-sized. It contains
everything (install bits, livefs, docs, and packages) and can be used if
your machine has a DVD drive in it.
If you would like to do a source-based update to 7.1-RC1 from an already
installed machine you can update your tree to RELENG_7_1 using normal
cvsup/csup methods. Note that due to an unfortunate side-effect of the
real source code repository now being in SVN it will look like all
files have a new version so mergemaster may be a bit tedious.
The freebsd-update(8) utility supports binary upgrades of i386 and amd64
systems running earlier FreeBSD releases. Systems running 7.0-RELEASE,
7.1-BETA, or 7.1-BETA2 can upgrade as follows:
# freebsd-update upgrade -r 7.1-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 Intel network interfaces which are changing their name from em to
igb should make necessary changes to configuration files BEFORE running
freebsd-update, since otherwise the network interface will not be configured
appropriately after rebooting for the first time.
Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update to
upgrade to FreeBSD 7.1, 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.
--
Ken Smith
- From there to here, from here to | [EMAIL PROTECTED]
there, funny things are everywhere. |
- Theodore Geisel |
signature.asc
Description: This is a digitally signed message part
Re: FreeBSD 7.1-RC1 Available...
-powerpc-disc3.iso) = 07eb57953c2f62e32320af835fbc27809c33ab1b9d07adeb90f4e94f89265815 SHA256 (7.1-RC1-powerpc-docs.iso) = fbe50671e2c49f83cd9aace1d008daed19a2a022536a27ffabb1b4d426cda633 SHA256 (7.1-RC1-sparc64-bootonly.iso) = 12d65300c950b6661d16715cdad902acafc5cf892731655082a2190707195225 SHA256 (7.1-RC1-sparc64-disc1.iso) = bc54c89619c3e99d57c94dc244fdc0fe71d57093bcf12041abe5bf8c9e6d63d2 SHA256 (7.1-RC1-sparc64-disc2.iso) = 1242751d9c0a2f82923904f09fca0f4a63041f3d68e3287963f1f48d81013ff2 SHA256 (7.1-RC1-sparc64-disc3.iso) = 216db6bf1123de281affa6d2ce1cea13f63fbe41bee0f825bc51d13b01411dcc SHA256 (7.1-RC1-sparc64-docs.iso) = c7a904e4897e8f5c16fbb2f66dd6e59c5436658f55c24648e5f3fb11e5986c8e -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
