Download DCC 3.0 via mirror sites here.
DCC 3.0 Release Notes
Welcome to the DCC Common Core, version 3.0 ("DCC 3.0"). DCC 3.0 is an LSB 3.0-compliant, Debian 3.1 ("sarge") based common core designed to serve as the basis for Debian-based derivative distributions. It is produced by the DCC Alliance, a diverse group of Linux vendors and nonprofits with strong Debian ties that have partnered to assemble a common, standards-based core for Debian-based distributions. Founding members are credativ, Knoppix, LinEx, Linspire, MEPIS, Progeny, Sun Wah, UserLinux, and Xandros, with membership open to additional organizations with an interest in a strong commercial presence for Debian and Debian-based solutions. For more information about the DCC Alliance or membership, please visit dccalliance.org.
The DCC is not a complete Linux distribution -- it is an LSB-compliant common core comprised of essential programs or "packages" from Debian GNU/Linux, combined with member-contributed additions to attain LSB compliance and achieve broad commercial acceptance and support.
In other words, as a user, you won't install the DCC directly; rather, you'll install the Linux distribution of your choice from one of the DCC Alliance members. The Alliance will guarantee application compatibility across these Linux distributions, as well as provide a single certification for independent software vendors (ISVs) and independent hardware vendors (IHVs) that applies to all member distributions.
Alliance members plan to integrate the DCC into their products, with varying release dates.
In addition to the DCC Common Core itself, the DCC Alliance has produced a DCC Reference Implementation (DCCRI), which is a minimal Debian-derived Linux distribution that includes the complete backport of X.org (the DCC itself only contains the subset of X.org necessary for LSB 3.0 compliance), hotplug, and hardware detection support (normally provided by Alliance member distributions), as well as installable ISO images built using the Debian installer. The DCCRI is designed to serve as a vehicle for experimentation and integration testing, as well as the baseline for the DCC certification program.
If you wish to get involved in the development of the common core or find out more about building a DCC-based distribution, please sign up for the membership lists at http://dccalliance.org/contact.html.
Check back later this week for information on how to develop a DCC-based distribution.
The DCC 3.0 and the DCC 3.0 Reference Implementation are available for
download at the following URLs:
(*) FTP and rsync access also available.
* DCC 3.0 supports the IA-32, IA-64, AMD64, and EM64T architectures.
* DCC 3.0 contains 237 packages (239 for IA-64, AMD64, and EM64T). All Debian security updates through DSA-915 are fully integrated. Of the 237 packages, 200 are binary packages taken from Debian
sarge unmodified (84%).
* Of the remaining 37 packages, 5 are the LSB 3.0 compatibility
environment, which adds LSB 3.0 compliance in such a way that
the sarge glibc and pam packages don't need to be modified
(the sarge versions aren't LSB 3.0 compliant -- see  and 
for details). Note that the only applications that use the LSB
compatibility environment are LSB applications--the default
application environment (i.e., the default
environment is 100% compatible with standard Debian sarge).
* Of the remaining 32 packages, 25 are a backport of X.org from etch.
As above, the DCC 3.0 X.org environment is fully compatible with the
standard Debian XFree86 environment--in other words, packages built
on DCC-based distros will install and run on standard Debian sarge
unless they use X.org-specific features (in which case they will
link to one of the new X.org packages, such
as libxcomposite1 or libxdamage1 not shipped in the DCC itself).
* Of the remaining 7 packages, 6 are backports of the LSB 3.0
packages from etch (lsb, lsb-base, lsb-core, lsb-cxx, lsb-graphics,
and lsb-release) modified to not manage the LSB dynamic linker
symlinks (these are managed by the LSB 3.0 compatibility environment).
* DCC 3.0 also includes a backport of the etch version of
module-init-tools and does *not* include hotplug or udev, which
allows DCC-based distros to choose between providing removable
device support either via the sarge hotplug package or the etch