About The Burn-In Desk

This page exists because of a collision. The domain carried the name of a Linux distribution, the distribution stopped releasing, and the pages now sitting here cover hardware stability and diagnostics. The name stayed and everything else changed. What follows is what this publication is, who signs its pages, and where it stands against the project it is named after.

A name the distribution left behind

Overclockix is the name of a live distribution first released in November 2003 and last released on June 1, 2015. DistroWatch keeps its record and carries the field that closes it: status Discontinued. This desk is not that project and does not speak for it. It is a working reference on load, memory errors, sensor readings and failed boots, and it sits on the address the distribution left behind.

What the desk publishes instead

Four subject sections and a dated log, plus the furniture a reference desk needs: stability testing and burn-in; hardware diagnostics for memory, storage and sensors; live systems and bootable toolkits; overclocking, treated as vocabulary and as risk rather than as settings. Around them sit a test matrix arranged by subsystem, a glossary, a dated log, and the Overclockix release record, the page that justifies the name. The desk republishes records and explains methods. It distributes no software, hosts no images, and announces no version.

Who writes these pages?

Pages are signed The Burn-In Desk editors, a collective byline rather than a name. What vouches for them is the method, not a biography. A figure carries its source and the date that source was consulted; the four numbers on the front page come from the DistroWatch record read on September 5, 2026, corroborated by the Internet Archive capture index of this domain. Where a document stops short of a number, the page says so instead of filling the gap. The procedure is written out in sources and method.

Is this the Overclockix project?

No, and on this domain the distinction is the point. The project has a history that the desk records without continuing it: Arkaine23 built the first versions on a Knoppix base in 2003, the work went dormant in 2005, mbentley revived it in 2011 on a Debian base, and the last change to its code went up on May 31, 2015. The code itself sits in a public archive on GitHub, and the project's repository is where a search for the project itself resumes. The desk claims no voice in it. It never announces a release and serves no mirror.

The record, version by version

Twelve years of releases, one change of base and desktop in the middle, and a stop: the table is the shortest honest shape of the project.

The same page fixes the setting: category Live Medium, release model Fixed, origin USA, an image size of 700 MB recorded for 7.8.0. Nothing in those fields has moved since 2015, and the stillness is the finding.

What the archive still shows

The Internet Archive's capture index for this domain lists 1,513 distinct addresses. A slice captured between 2005 and 2016 is the project's own tree: a releases directory split by architecture and by image type, torrents beside the images, an RSS feed, a sources page, and image filenames running from the .012 series to 7.8.0. Roughly 1,300 addresses date from 2019, 2020, 2023 and 2025 and belong to the occupants who held the domain in between, with no relation to the distribution. The desk republishes that record and none of the files: no image, no checksum, no torrent, no mirror, and no pointer to one.

Where should a reader start?

If the name brought you here for an image to boot, this desk has none, and the repository named above is where that search resumes. If the desk's subject is what you came for, begin with what a stress test proves, then read every result the way this desk reads its own records: for what it covers, and for what it leaves out.