OS Revolution

Living in a matrix

DragonFlyBSD

DragonFly 2.2.1

Matthew Dillon announced the new DragonFly 2.2.1 sub-release.
that brings several improvements and bug-fixes.

Download

Release Date: 
Wed, 2009-04-29

Chronology

  • July 12, 2004 - DragonFly 1.0
  • April 8, 2005 - DragonFly 1.2
  • January 7, 2006 - DragonFly 1.4
  • July 25, 2006 - Dragon Fly 1.6
  • March 27, 2007 - Dragon Fly 1.8
  • August 6, 2007 - DragonFly 1.10
  • February 26, 2008 - DragonFly 1.12
  • July 21, 2008 - DragonFly 2.0
  • February 17, 2009 - DragonFly 2.2

DragonFly 2.2

Released on February 17, 2009, HAMMER is now considered "production-ready", and this version includes "major stability improvements across the board". Besides the CD ISO release, this version has a DVD ISO release with "a fully operational X environment," as well as a bootable USB key image.

Release Date: 
Tue, 2009-02-17

DragonFly 2.0

Released on July 21, 2008, DragonFly 2.0 included several bug fixes, support for more devices, and updated userland applications. Its main focus was the first official release of the HAMMER filesystem. 2.0.1 was released on September 27, 2008 with driver updates and minor fixes and updates for HAMMER.

Release Date: 
Mon, 2008-07-21

DragonFly 1.12

Released on February 26, 2008, DragonFly 1.12 was described as a maintenance update focusing mainly on code cleanups and updates; however, some user visible changes became available. The USB and WiFi stacks were extensively reworked, increasing stability and supporting new hardware. The Hardware Sensors Framework originally developed for the OpenBSD Project was imported (via FreeBSD). SATA ATAPI support for AHCI controllers was also added. An experimental Bluetooth stack was included for testing. The version of GCC used in DragonFly was updated to version 4.1, though the older version was also available. A first version of the DragonFly Mail Agent (called dma), intended as a future replacement for sendmail, was added to the base. Older networking technologies such as ARCnet, FDDI and Token Ring support has been removed. Finally support for the 386 CPU was officially dropped.

Also of note, supporting code for the AMD64 Architecture was added, but the system still did not run in 64-bit mode. From the release notes: "Progress has been made on making more of the kernel MP safe. The network path has a good chance of getting there by the end of the year. The I/O path still needs a lot of work." Preliminary work on the new clustering file system, called HAMMER, was added, but it was not enabled.

Release Date: 
Tue, 2008-02-26

DragonFly 1.10

DragonFly 1.10 was released on August 6, 2007. New to this release was the near completion of the new userland threading system, and native support for the protocol used by SATA controllers (which was imported from FreeBSD). SMP support for virtual kernels was also enabled as a testbed for the various new multiprocessing features. Additionally many cleanups were done in the disk layer, many wireless drivers, and the USB subsystem. An example of what the improvements in the VFS layer in combination with the USB cleanups allow is that the system is much more stable and unlikely to panic if mounted USB media is suddenly removed. The FreeBSD 4 derived ports system for installing third party applications was also retired. A fairly serious mbuf memory leak was discovered soon after the release and corrected, though there was not an immediate release of a new installation disk. The updated version 1.10.1 was released on August 22, 2007, complete with fixes for the issues in 1.10.0.

Release Date: 
Mon, 2007-08-06

DragonFly 1.8

With the 1.8 release, DragonFly improved several kernel features and implemented a virtual kernel (similar to User Mode Linux or Linux KVM). Version 1.8.1 was released on March 27, 2007, primarily to provide security updates and bugfixes, including to the dynamic loader and virtual kernel.

Release Date: 
Tue, 2007-03-27

DragonFly 1.6

The fourth major release of DragonFly, on July 25, 2006. The biggest user-visible changes in this release were a new random number generator, a massive reorganization of the 802.11 (wireless) framework, and extensive bug fixes in the kernel. It also made significant progress in pushing the big giant lock inward and made extensive modifications to the kernel infrastructure with an eye towards DragonFly's main clustering and userland VFS goals. DragonFly's team considered 1.6 to be more stable than 1.4.

Release Date: 
Tue, 2006-07-25

DragonFly 1.4

The third release of DragonFly was made available on January 7, 2006. Many new drivers and bug fixes were integrated into the system. GCC version 3.4 was now required to build the system, because the older compiler suite would no longer work, due to the increasing use of TLS support. NetBSD's pkgsrc was made the default packaging system, although the buildtools were not yet included in DragonFly's CVS repository. An official set of prebuilt packages made specifically for this release was not available, and many packages (KDE and GNOME most notably) in the pkgsrc snapshot did not build cleanly on the system. Citrus from the NetBSD project was also imported.

Release Date: 
Sat, 2006-01-07

DragonFly 1.2

The second release of DragonFly, on April 8, 2005, contained many bug fixes and new features. New to this release were TCP SACK, ALTQ and PF (OpenBSD's firewall), TLS (thread-local storage) support, DCONS support (console over firewire), IPv6 improvements, and the rewritten namecache infrastructure, which is now distinct from the VFS code, and now capable of allowing the DragonFly developers to implement namecache based security mechanisms.

Like the first release, 1.2 used the FreeBSD ports system for third party packages, but added NetBSD's "pkgsrc" as an option, after modifications allowed it to natively supports DragonFly.

Dillon has stated that this would be the last release of DragonFly that employs the MP lock in common code paths.

Release Date: 
Fri, 2005-04-08
Syndicate content

Who's online

There are currently 0 users and 3 guests online.