DragonFly BSD images are 'live', meaning these images on whatever media will boot your system and let you log in as
root (no password). You can use this feature to check for hardware compatibility and play with DragonFly a little before actually installing it on your hard drive. The CD includes an installer that can be run at the console. To activate the installer, boot and login as
If you use a GUI DVD, you can login as
root and start a GUI with startx. Note that there is no GUI release for the current release. You will need to install Xorg directly. If you use a USB .img file, it needs to be copied to a USB key directly. Use dd on unix-like systems, or a similar program on Windows. You could also try Image Writer for Windows.
DragonFly BSD is 64-bit only, as announced during the 3.8 release.
USB: dfly-x86_64-4.6.0_REL.img as bzip2 file
ISO: dfly-x86_64-4.6.0_REL.iso as bzip2 file
Uncompressed ISO: dfly-x86_64-4.6.0_REL.iso (For use with VPS providers as an install image.)
Daily SNAPSHOT: here
Here is a list of worldwide mirrors offering DragonFly ISO images. Please use an appropriate mirror for best results!
For more details, read the 4.6 release notes.
Since DragonFly 2.1 the source repository is maintained with git instead of CVS. To clone the sources using git:
# cd /usr # make src-create
This will fetch all sources for you from a fast mirror. If the git-clone command is not available update your Makefile to a recent version. If you do not have git installed, install it from dports (
devel/git). See development(7) for further instructions how to work with the repository.
If you wish to check out the source repository manually, you can use
# git clone git://git.dragonflybsd.org/dragonfly.git dragonfly
All release CDs and images also have pkg installed for immediate download of packaged third-party software.
The DragonFly source can be browsed via the gitweb web interface.
Releases occur approximately twice a year. DragonFly release branches only contain bug and security fixes and are designed for people running production systems who don't want any surprises. Brand-new features often discussed on the mailing lists are typically not in release branches.
DragonFly systems based on releases are labeled RELEASE, for example, you might be running DragonFly X.Y.Z-RELEASE. If you run a daily snapshot or track git master, you'll see X.Y.Z-DEVELOPMENT as your system version.
A number of commercial sites selling DragonFly related material is here.