Simon ‘corecode’ Schubert has added his patch to allow separate volume controlÂ for each application.Â Also, Hasso Tepper has produced a patch for sound that includes changes taken from FreeBSD 6, which improves device support.
pkgsrc has a temporary freeze coming up, where only fixes will be committed in preparation for the 2007Q2 branch, for release this Saturday, June 16th.Â (No link, cause netbsd.org is apparently unreachable for me right now.)
Matthew Dillon asks that 1.9 users test using USB memory devices; he’s recently committed a large number of fixes related to physically removing mounted USB drives.Â Also, automatically mounting reconnected drives is a small, easy project enabled by this recent work.Â (See linked article for details.)
Hey look!Â netbsd.org has been redesigned.
NATA, the ‘new ATA’ disk system, will be in the next release of DragonFly, but it will still be called ‘NATA’, not renamed to ‘ATA’.Â Keep this in mind when eventually updating with a custom kernel file.
Do you have a leaf.dragonflybsd.org account?Â Now is a good time to clean it up.
Matthew Dillon, while investigating a separate problem, ended up improving the separation between CPUs in a multiprocessor system.Â The Big Giant Lock is still there, but it’s a move in the right direction.
OpenSound was previously available for DragonFly, though support for it was quietly dropped probably around the same time 4Front stopped supporting FreeBSD 4. In any case, it is possible it could go into contrib/ now, if it has benefits – hopefully they will make it available under a more BSD-style license.
Network driver code has been shared between the BSDs a great deal lately, with a flowering of available drivers and support.Â Having a shared sound model too would also lead to benefits greater than the sum of its parts.
Matthew Dillon wrote a long message on how things are progressing with DragonFly; some projects like improved SMP support and 64-bit processing are almost ready for prime time, and just need someone to step up and complete them. The track record so far for DragonFly has been astoundingly stable; major changes in threading and process management have gone into the tree and it’s happened completely without destabilizing the system – e.g. it’s been safe even to run bleeding-edge code.
Also: the upcoming release will be 1.10, and hopefully GCC4.x can be made the default by the time 2.0 arrives.
From the DragonFly mailing lists: Matthew Dillon posted a list of what will and won’t be in the next release.Â Rahul Siddharthan pointed out that there hasn’t been much user-visible improvement since FreeBSD-4, speaking specifically about 64-bit processors and SMP.Â Steve O’Hara-Smith added some less well known benefits we already have, while Michael TalonÂ described the speed boost a 64-bit operating system gives.Â Matthew Dillon said “someone just needs to do it“.Â I daresay the conversation is not over.
Alexander Motin wrote to the kernel@ mailing list about netgraph in DragonFly; it was getting difficult for him to maintain compatibility with mpd4 in the FreeBSD-4 style netgraph in DragonFly and also support netgraph in FreeBSD.Â Matthew Dillon said “Don’t wait up“.Â Anyone feel like updating netgraph?Â It’s probably not easy.
Preview, the version of DragonFly that is not-quite-bleeding-edge, has been updated so that everyone can try the latest version of NATA and virtual kernels.