Lots of tasks

Looking for things to do? Here’s Hiten Pandya’s list of possible merges from FreeBSD. There’s a lot of tasks there of varying length and difficulty, so if you feel like trying something out, go for it and post your patch to the dragonfly.submit list.

stable and release

Jonathon McKitrick asked about “last known stable” tags, and the June release date for 1.0. Matt Dillon replied that a known stable tag will appear once the networking code is stable, and that a late June release is still planned

More awk

Eirik Nygaard has updated the One True awk in DragonFly to version 20040207. This temporarily broke the buildworld process, so if you tried a buildworld this afternoon and it failed with awk, it should now work. (Fixed by David Rhodus.)

Boot-time nfs issue fixed

Matt Dillon found that using short-form names in /etc/fstab would cause the DNS resolver to return “host not found”, even if there was just a timeout (which should result in “try again”) when first looking up that name. This is now fixed. If you found you could not mount NFS volumes at boot, but they worked when done manually after boot, this should fix it.

diffutils upgraded

Eirik Nygaard has committed diffutils 2.8.1 into the tree. This is similar to previous third-party software additions in that DragonFly-specific changes are managed through additional patches to original code, not by creating a DragonFly-only version of diffutils. Future upgrades are made much more easy using this method.

Negative NFS caching

Matt Dillon has added negative caching for NFS, meaning that NFS will now cache failed lookups, not just successful ones. He details the benefits like so:

“This makes a HUGE difference for programs which search nfs directories, such as compilers (the header file search path), make, and a few other utilities. NFS packet traffic can be reduced upwards of 90%. For example, with /usr/src mounted via NFS, building libc a second time without negative caching generates 66000 packets of NFS traffic in each direction, building libc a second time with negative caching enabled generates 9500 packets worth of NFS traffic, in EACH DIRECTION. While it is true that negative lookups are cached on the NFS server, the huge reduction in network traffic and equivalent reduction in synchronous read latencies result in radically reduced overheads across the board for operations which generate a lot of negative hits. A buildworld test with the default 3 second negative caching timeout went from 2265 seconds to 1900 seconds.”