DragonFly 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 the DVD, you can login as
root and start a GUI with startx. 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.
Be sure to check the release notes.
The i386 architecture has significant limitations compared to x86_64. These images are only recommended for use with legacy computers incapable of running 64-bit software
Daily SNAPSHOT: here Snapshots use the new packaging system 'dports'.
Here is a list of worldwide mirrors offering DragonFly ISO images. Please use an appropriate mirror for best results!
To limit disk space requirements all mirrors carry only the ISO images/packages of the current and the last release. ISO images of older releases are available here.
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
pkgsrc/devel/scmgit. 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 contain a base git repo for pkgsrc and a populated /usr/pkg containing the git tools and may be used to bootstrap pkgsrc support in your system if you desire.
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.