http://kerneltrap.org/taxonomy/term/1195/0 en-local http://kerneltrap.org/DragonFlyBSD/1.12_A_Maintenance_Update <div class="taxonomy-images"><a href="/news/dragonflybsd" class="taxonomy-image-links"><img src="http://kerneltrap.org/files/category_pictures/K-FlyBSD_1.gif" alt="DragonFlyBSD" title="DragonFlyBSD" width="75" height="75" /></a></div><!-- google_ad_section_start --><p>"Hello everyone! We are happy to say that the 1.12 release is now available!" began Matthew Dillon, <a href="http://kerneltrap.org/mailarchive/dragonflybsd-user/2008/2/26/993954">announcing the latest stable version of DragonFly BSD</a>. The project's home page explains, "<i>DragonFly is an operating system and environment originally based on FreeBSD. DragonFly branched from FreeBSD in 2003 in order to develop a radically different approach to concurrency, SMP, and most other kernel subsystems.</i>" Regarding the latest release, Matt explained:</p> <blockquote><p>"This release is primarily a maintenance update. A lot of work has been done all over the kernel and userland. There are no new big-ticket items though we have pushed the MP lock further into the kernel. </p> <p>"The 2.0 release is scheduled for mid-year. Of the current big-ticket item work, the new <a href="http://kerneltrap.org/HAMMER">HAMMER filesystem</a> is almost to the alpha stage of development and is expected to be production ready by the mid-year 2.0 release."</p></blockquote> <!-- google_ad_section_end --><p><a href="http://kerneltrap.org/DragonFlyBSD/1.12_A_Maintenance_Update" target="_blank">read more</a></p> http://kerneltrap.org/DragonFlyBSD/1.12_A_Maintenance_Update#comments 1.12 DragonFlyBSD HAMMER Matthew Dillon release DragonFlyBSD Thu, 28 Feb 2008 15:17:37 +0000 Jeremy 15626 at http://kerneltrap.org http://kerneltrap.org/DragonFlyBSD/2.0_Becomes_1.12_While_HAMMER_Matures <div class="taxonomy-images"><a href="/news/dragonflybsd" class="taxonomy-image-links"><img src="http://kerneltrap.org/files/category_pictures/K-FlyBSD_1.gif" alt="DragonFlyBSD" title="DragonFlyBSD" width="75" height="75" /></a></div><!-- google_ad_section_start --><p>"<i>HAMMER won't be ready for sure (things take however long they take), but the hardest part is working and stable and I'm just down to garbage collection and crash recovery,</i>" noted Matthew Dillon, discussing the status of what is ultimately intended to be a highly available clustering filesystem. The upcoming DragonFlyBSD release this month was originally intended to be 2.0 with a beta quality HAMMER, but the decision was recently made to call the release 1.12 while HAMMER continues to stabilize. Matt continued, "<i>HAMMER is really shaping up now. Here's what works now: all filesystem operations; all historical operations; all Pruning features</i>". During the discussion, he was asked how he planned to support multi-master replication, in reply to which he began:</p> <blockquote><p>"My current plan is to use a quorum algorithm similar to the one I wrote for the backplane database years ago. But there are really two major (and very complex) pieces to the puzzle. Not only do we need a quorum algorithm, but we need a distributed cache coherency algorithm as well. With those two pieces individual machines will be able to proactively cache filesystem data and guarantee transactional consistency across the cluster."</p></blockquote> <!-- google_ad_section_end --><p><a href="http://kerneltrap.org/DragonFlyBSD/2.0_Becomes_1.12_While_HAMMER_Matures" target="_blank">read more</a></p> http://kerneltrap.org/DragonFlyBSD/2.0_Becomes_1.12_While_HAMMER_Matures#comments 1.12 cluster