# Obtaining DragonFly for your system
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 `installer`.
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](http://www.chrysocome.net/dd) on Windows. You could also try [Image Writer for Windows](http://sourceforge.net/projects/win32diskimager/files/).
Be sure to check the [[release notes|release34]].
**i386:** [CD](http://mirror-master.dragonflybsd.org/iso-images/dfly-i386-3.4.1_REL.iso.bz2) | [USB](http://mirror-master.dragonflybsd.org/iso-images/dfly-i386-3.4.1_REL.img.bz2) | [GUI ISO](http://mirror-master.dragonflybsd.org/iso-images/dfly-i386-gui-3.4.1_REL.iso.bz2) | [GUI USB](http://mirror-master.dragonflybsd.org/iso-images/dfly-i386-gui-3.4.1_REL.img.bz2)
**x86_64:** [CD](http://mirror-master.dragonflybsd.org/iso-images/dfly-x86_64-3.4.1_REL.iso.bz2) | [USB](http://mirror-master.dragonflybsd.org/iso-images/dfly-x86_64-3.4.1_REL.img.bz2)| [GUI ISO](http://mirror-master.dragonflybsd.org/iso-images/dfly-x86_64-gui-3.4.1_REL.iso.bz2) | [GUI USB](http://mirror-master.dragonflybsd.org/iso-images/dfly-x86_64-gui-3.4.1_REL.img.bz2)
Daily **SNAPSHOT**: [here](http://mirror-master.dragonflybsd.org/snapshots/) Snapshots use the new packaging system 'dports'.
Here is a list of [[**worldwide mirrors**|/mirrors]] offering DragonFly ISO images. *Please use an appropriate mirror for best results!*
### Legacy Releases
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](http://island.quantumachine.net/archive/).
## Binary pkgsrc packages
We offer a reasonable number of binary pkgsrc packages for every stable release of DragonFly. Look at the [[list|mirrors]] of worldwide mirrors to find a mirror near you carrying binary packages. See the [[pkgsrc page|docs/howtos/HowToPkgsrc/]] how to install these packages.
Pkgsrc sources can now be obtained via git instead of CVS, and we recommend that our git mirror be used instead of loading down NetBSD's CVS servers. The pkgsrc git uri which mirrors the NetBSD pkgsrc cvs repo is: `git://git.dragonflybsd.org/pkgsrcv2.git`
To obtain the pkgsrc tree via git:
# cd /usr
# make pkgsrc-create
Beware of pkgsrc git repository change, with release 2.6.3 you will need to update the address in the Makefile:
# cd /usr
# chmod u+w Makefile
# perl -i -ne 's/pkgsrc\.git/pkgsrcv2.git/;print' Makefile
# chmod u-w Makefile
# make pkgsrc-create
## Obtaining source via git
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)](http://leaf.dragonflybsd.org/cgi/web-man?command=development§ion=ANY") 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.
## Browsing source via web interface
The DragonFly source can be browsed via the [gitweb](http://gitweb.dragonflybsd.org/dragonfly.git) web interface.
## DragonFly Releases
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.
## Commercial Sites
A number of commercial sites selling DragonFly related material is [[here|commercial]].