# Obtaining DragonFly for your system [[!toc levels=3]] ## CD Images DragonFly CDs are 'live', meaning these CDs 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. Make sure you read the [README](http://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/nrelease/root/README") file for more information. To activate the installer, boot the CD and login as 'installer'. If you use the DVD, you can login as root and start a GUI with 'startx'. * **Current RELEASE - 2.4.1**: CD DVD USB AMD64-ISO * Daily **SNAPSHOT**: here Here is a list of [[**worldwide mirrors**|/mirrors]] offering DragonFly ISO images. *Please use an appropriate mirror for best results!* ## 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 man page of [pkg_radd(1)](http://leaf.dragonflybsd.org/cgi/web-man?command=pkg_radd§ion=ANY) 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. To obtain the pkgsrc tree via git: # cd /usr # 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. 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. ## 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]].