Domain: freebsdmirrors.org
Stories and comments across the archive that link to freebsdmirrors.org.
Comments · 5
-
Of course...
If you wanted to be nice to those folks at the FreeBSD project, you could always use a mirror.
In fact, in the future it might not be a bad idea to have Slashdot only link to freebsdmirrors.org. I know that the FreeBSD people have gotten pissed in the past about that... -
Re:A few mirros
http://www.freebsdmirrors.org/ also is supposed to show you a single view of what mirrors carry what files. It appears to be a bit behind right now, but bookmark the page for future reference.
-
Mirrors
Instead of pointing to the front page, it may be more useful to point at the mirror list.
-
Mirror site speed... no complaints!One benefit of being up early (not by choice) is that I'm getting some damn good download speeds from the official FreeBSD mirror sites, as in 773KB/s... that's over 6 megabits!
Not all of the sites have the full set of files (yet), I had to hunt around a bit to find the '4.5-install.iso'.
Don't trust my math on transfer speeds?
local: 4.5-disc2.iso remote: 4.5-disc2.iso
(Yes, that transfer went via a proxy firewall)
227 Entering Passive Mode (192.168.1.1,162,179)
150 Opening BINARY mode data connection for '4.5-disc2.iso' (631341056 bytes).
602 MB 00:00 ETA
226 Transfer complete.
631341056 bytes received in 796.65 seconds (773.92 KB/s) -
Lower-profile changes that made it inI administer a large cluster (please no jokes) of FreeBSD systems at work, and I was pleased to see that several changes that I had been tracking in the -STABLE branch finally made it into a release. Among them:
- Code path optimizations. One particularly interesting change was that data destined for loopback interfaces (e.g. 127.0.0.1) bypass congestion control and the TCP sequencing code. Likewise for UDP - ICMP port unreachable messages and the like are actually determined within the syscall now, rather than being discrete messages that are bounced around in the kernel.
- Filesystem fixes. We had been having some trouble with devfs and freevxfs on several machines, and the fixes that were checked into CVS a few weeks back fixed them. It is with pleasure that I note that those changes made it into 4.5-RELEASE.
- Stability fixes. There were some minor issues with the use of -llinfo and the route syscall that would sometimes cause kernel panics. Since we use shell scripts to update routing tables many times an hour, we ran into this from time to time, and it is fixed now.
- Usability improvements. The core team has emphasized the need
to provide a more useful
/proc filesystem, so that it can contain many discrete pieces of valuable system information like it does in Linux. Thus, new handlers for registering and unregistering nodes under /proc have been implemented (although they are not used yet).
</evangelism>
freebsd guy