4 The DragonFly 3.0 release is here! This release was delayed from our regular schedule for tracking down [what appears to be a AMD CPU bug](http://gitweb.dragonflybsd.org/dragonfly.git/commit/8e32ecc0a77082f1e232a3e6d12e2f163f9667a4). As a pleasant side effect, the giant kernel lock has been removed from much of the system and this release performs significantly better on multi-core systems than previous DragonFly versions.

10 Previously the majority of the VM was under a single token, the vm_token; now vm_objects (mappable entities) are each under a private token, concurrent page faults in the same object can proceed, and VM SMP scalability overall is improved. Results for Postgres and MySQL, among others, are excellent.

12 Francois Tigeot [worked on benchmarks](http://leaf.dragonflybsd.org/mailarchive/kernel/2011-11/msg00004.html) comparing DragonFly 2.10 and DragonFly 2.13, among other operating systems. The resulting graphs show how well DragonFly responds to multiple CPUs on a 24-threads Xeon system. (2.13 is the development version of DragonFly that became 3.0.)

18 A new [time domain multiplexing method](http://leaf.dragonflybsd.org/mailarchive/commits/2011-07/msg00086.html) has been added to balance storage operation types over long time periods. HAMMER fairness and throughput under heavy storage loads has significantly improved.

20 HAMMER's behavior in very low memory configurations has also improved; it will no longer readily starve a system of kernel allocation space. HAMMER should work on systems with as little as 256MB of RAM.

28 DragonFly now has [tcplay(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=tcplay&section=8), a tool for creating and managing encrypted disk volumes. It is 100% [TrueCrypt](http://www.truecrypt.org/) compatible and BSD licensed.

39 The release ISO images should be available on most of the [[mirrors|mirrors]]. If the ISO is not available on a certain mirror, please try another one or download it from the DragonFly master site. Each image is in the "Live CD" format, meaning that it boots into a running and fully functional DragonFly system, which can be used for testing or system recovery tasks as well as installation. Check the [hardware page](http://www.dragonflybsd.org/docs/supportedhardware/) or boot a Live CD to check for compatibility.

41 The GUI bootable USB image also contains the DragonFly git repo in /usr/src and the pkgsrc git repo in /usr/pkgsrc. The code can be trivially checked out using these repos and can be incrementally updated from master sites, post-install.

69 We offer roughly 10,000 pre-built [pkgsrc](http://www.pkgsrc.org) packages for this release. The [pkg_radd(1)](http://leaf.dragonflybsd.org/cgi/web-man?command=pkg_radd&section=ANY) utility may be used to download pre-built binary packages. The path can be overridden by setting BINPKG_BASE in `/etc/pkg_radd.conf`.

75 We supply a Makefile in `/usr` to track the pkgsrc tree and we supply a Git mirror of the NetBSD pkgsrc CVS repo at `git://git.dragonflybsd.org/pkgsrcv2.git`. We recommend that users use it, instead of pulling from NetBSD with CVS. Our Git mirror is updated several times a day. Type 'make' in /usr to see the available commands for performing these actions.

79 **Disk size warning** - Unless your hard disk is 50G or larger, we recommend doing a UFS install and not the default HAMMER install. We also recommend installing from the CD ISO, not the GUI .img, for smaller drives. A more serious installation should use HAMMER with at least 50G of disk space and can install from the GUI .img. HAMMER on smaller disk drives is possible but requires careful pruning to keep from filling the disk with file history.

81 **Virtual PC users** - Virtual PC does not supply serial numbers for the virtual disks. The system may need to be manually directed in the boot loader if the disk identifier changes. (Hit ? in the boot loader for a list of available volumes.)

83 **Installer Crypt Options** - The installer can encrypt the root volume and the swap volume. It will not work properly for other volumes despite any additional check-boxes you might see. Installer and boot-time support works but is still a bit rough around the edges. Performance will be relatively high on multi-core machines.

85 **ISA driver removal** - A number of ISA hardware drivers have been removed. One of these drivers, ie(4), was in our GENERIC config. Another driver, aha(4), was in both our GENERIC and our X86_64_GENERIC kernel configuration files. If you are using a kernel config based on a previous release's GENERIC config file, you may need to remove these drivers in order to successfully compile the kernel.

89 **Remaining issues** - The DragonFly bug tracker mentions some issues still known but not fully diagnosed at time of release. Specifically, building world with more than 4 processes (-j 5) may cause issues on i386, and some users have seen issues with NFS. Check the [3.0 release ticket](http://bugs.dragonflybsd.org/issues/2286) for details.

151 * libdm, a simple BSD-licensed device mapper library that is API-compatible with libdevicemapper has been added.

152 * tcplay(8), a simple BSD-licensed tool that allows creation, managing and mapping of TrueCrypt volumes has been added. It is fully integrated with initrd and cryptdisks and 100% compatible with TrueCrypt.

153 * tcplay(3), a library based on tcplay(8) that allows access to TrueCrypt volumes, has been added.

154 * POSIX 2008 fmemopen(3) and open_memstream(3) routines have been added to libc

155 * Bug in socket timeouts has been fixed, allowing Varnish to run w/ default configuration.

156 * The jail rc.d script can now automatically mount a devfs inside the jails.

157 * Minor fix in hammer(8) for snapshot count in the info directive.