leaf.dragonflybsd.org is moving to the most recent version of DragonFly (HEAD) so as to serve as a test for some SATA fixes.
Matthew Dillon reported a hard disk failure knocked out the DragonFly website and mailing lists over the weekend; there’s a new disk, filled from backups, back in place now.
Matthew Dillon has added code that should hopefully fix the long-standing timer bug some people have seen.
Oliver Fromme suggested a way to make it possible to boot a CD into a variety of operating systems – specifically either FreeBSD or DragonFly.
A big was found in SACK; it could cause downloaded file corruption – it’s fixed now.
Matthew Dillon did an update of checkpointing, as apparently someone had expressed interest in porting it.
A vulnerability was found in FreeBSD’s fetch, which also affected the DragonFly version. Jeroen Ruigrok has already fixed it.
‘Rum’ noted he has a dfport of Firefox 1.0.1 available.
Freddie Cash described on kernel@ how he got his atheros card working, using a FreeBSD driver.
Joerg Sonneberger followed up on his own commit message saying that Perl seems to be out of the base system.
Read an interesting conversation that I don’t understand.
Andreas Hauser detailed his X.org 6.8.1 packages and caveats in a recent post to the submit@ mailing list.
Is anyone even using a 386 processor anymore? If you are, go look for some pocket change and buy a faster computer.
Matthew Dillon noted that all chronic bugs appear to have been fixed, this week.
Joerg Sonneberger detailed the changes inherent in using OpenNTPd, which will be in the system momentarily.
Matthew Dillon’s committed the next big stage of his VFS work; the commit message includes a lengthy explanation of what it touches.
No, I’m not branching out. :) Hubert Feyrer is running an unadorned blog similar to this one, but concentrating on NetBSD.
There’s also a similar page at undeadly.org for OpenBSD. I suppose KernelTrap is in the same vein mostly for Linux, and the FreeBSD Project has src summaries.
A question about programming brought some interesting tips on how to deal with source code and other issues. There was quite a lot of suggestions, in fact.