DragonFly CDs are 'live', which means that the CD 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 file for more information. To activate the installer, boot the CD and login as 'installer'.
As of this release the installer has a Netboot server option. You can boot the CD on one machine, enable the feature via the installer, and then PXEBoot other systems and do a network based install. System operators should be aware that running the netboot server hardwires a 10.1.0.X network and runs a DHCP server which might interfere with other DHCP servers on your LAN.
See the 'Download Site' list below for a list of download locations.
The MD5 for the release is:
MD5 (dfly-1.2.0_REL.iso.gz) = e0faf2e1dd31763cad5eda2dd8e56ef8
DragonFly releases are meant to be stable, dependable entities. We backport compatible bug fixes from current development into release branches but we do not generally backport new features. The release CD is always a '.0', e.g. 1.2.0. The most common way to track a release is to use cvsup to track the release sources and then build and install a new world and kernel to keep your system updated.
|1.2.2||09-May-2005||A kernel TLS support bug was fixed.|
|1.2.3||29-Jun-2005||Compiler, bootstrap, security, fork/^Z race, nfile limit, token, and packet filter fixes.|
|1.2.4||07-Jul-2005||Wildcard expansion bug in /bin/sh, bzip2 security issue, core dumping to NFS mounts, updated leapseconds, bridging fixes.|
|1.2.5||31-Jul-2005||Numerous critical SMP fixes: critical section and spl code, IPI messaging, LWKT tokens, and a ktrace fix. Also a security fix for a libz overflow.|
A detailed commit history is available.
|Organization||Mirrored Data||Access methods|
|GoBSD.COM (USA)||1.2.0_REL image||HTTP FTP|
|Chlamydia.fs.ei.tum.de (Germany)||1.2.0_REL image||HTTP FTP|
|Starkast.net (Sweden)||1.2.0_REL image||HTTP FTP|
|BGP4.net (USA)||1.2.0_REL image||HTTP FTP|
|TheShell.com||1.2.0_REL image||HTTP FTP|
|FictionPress.com (USA)||1.2.0_REL image||HTTP|
|SourceForge (USA)||1.2.0_REL image||HTTP|
|Hup.hu (Hungary)||1.2.0_REL image||HTTP|
|Bit Torrent||1.2.0_REL image||TORRENT|
|Dragonflybsd.org (USA)||1.2.0_REL image||FTP (try to find another site first)|
1.2.x is our second major DragonFly release and the first one which we have created a separate CVS branch for. DragonFly's policy is to only commit bug fixes to release branches.
This release represents a significant milestone in our efforts to improve the kernel infrastructure. DragonFly is still running under the Big Giant Lock, but this will probably be the last release where that is the case.
The greatest progress has been made in the network subsystem. The TCP stack is now almost fully threaded (and will likely be the first subsystem we remove the BGL from in coming months). The TCP stack now fully supports the SACK protocol and a large number of bug and performance fixes have gone in, especially in regard to GigE performance over LANs.
The namecache has been completely rewritten and is now considered to be production-ready with this release. The rewrite will greatly simplify future filesystem work and is a necessary precursor for our ultimate goal of creating a clusterable OS.
This will be last release that uses GCC 2.95.x as the default compiler. Both GCC 3.4.x and GCC 2.95.x are supported in this release through the use of the CCVER environment variable ('gcc2' or 'gcc34'). GCC 2.95.x is to be retired soon due to its lack of TLS support. The current development branch will soon start depending heavily on TLS support and __thread both within the kernel and in libc and other libraries. This release fully supports TLS segments for programs compiled with gcc-3.4.x.
It goes without saying that this release is far more stable then our 1.0A release. A huge number of bug fixes, performance improvements, and design changes have been made since the 1.0A release.
Other minor or incremental improvements: