7 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, or (experimentally) via a web browser. 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'.

16 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&section=ANY) how to install these packages.

20 Since DragonFly 2.1 the source repository is maintained with git instead of CVS. See [development(7)](http://leaf.dragonflybsd.org/cgi/web-man?command=development&section=ANY") for instructions how to clone the repository.

24 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.

26 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.