Skip to content
The Burn-In DeskStability testing, hardware diagnostics and live toolkits.

Section 05

The Log

Dated notes from the desk: documents read, figures corrected, pages revised and the questions still open.

A ruled notebook open beside a keyboard on a workbench, pencil annotations down the margin and a coil of test leads at the edge of the page

The Log is where this publication speaks in the present tense. It carries short dated notes rather than articles: a document that has been read, a row of the test matrix that has been corrected, a term added to the glossary, or something about this domain's own history that a reader should know.

It also exists for a less obvious reason. A correction here is never a silent edit. When a figure changes, three things happen together: the page carries the new source and the new date of reading, the claim behind it is updated in the evidence file, and a dated note appears on this page saying what changed and why. That procedure is set out in sources and method, and this page is the visible half of it.

The other sections of the desk: Stability Testing, Diagnostics, Live Systems and Overclocking. Every one of them comes back to the test matrix.

05

Dated notes

Readings, corrections and open questions, newest first.

  1. The archive index of this domain, read end to end

    Reading

    The Internet Archive capture index for overclockix.com returns 1513 distinct addresses that once answered with a 200. Only about 110 of them belong to the distribution itself, captured between 2005 and 2016. The remaining thirteen hundred were produced while the domain was held by other people, in 2019, 2020, 2023 and 2025. That reading is what the address policy of this site is built on, and it is why an unknown address here answers 404 rather than sliding onto the front page.

  2. This desk is not the Overclockix project

    Disclosure

    The Burn-In Desk publishes at overclockix.com and has no connection to the people who built the Overclockix live distribution. We do not maintain it, we do not speak for it, and we serve no disk image, checksum or torrent. Its source is published on GitHub under mbentley, and that is where anyone looking for the project itself should go. The release record on this site documents what was published and when, from public archives, and says so on the page rather than in a footer.

  3. What the four figures on the front page count

    Method

    The band on the front page carries four figures: the year of the first Overclockix release, the year of the last one, the number of releases DistroWatch records, and the number of disk images this site serves, which is zero. The first three are read on the DistroWatch page for the distribution, whose own last update is dated February 8, 2026. A column is only published there when its figure has a document behind it and a date of reading. There is no fifth column because there is no fifth sourced figure yet.

  4. Corrections are dated, never silent

    Correction policy

    When a figure on this site changes, three things happen at once. The page carries the new source and the new date of reading. The claim behind it is updated in the evidence file that sits with the research for that page. And a dated note appears on this log saying what changed and why. A quiet edit would leave a reader who quoted the old figure with no way to find out. Anyone who spots an error can write to the desk, and the correction gets the same treatment whether it came from inside or outside.

  5. Release dates rest on a secondary source

    Open question

    The release dates in the record come from DistroWatch, which is a database compiled by other people rather than a primary document from the project. The archive index of this domain corroborates the file names and the periods they were online, but it does not date the releases themselves. That gap is stated on the page. If a primary announcement turns up, in the source repository or in the release thread that accompanied each version, the row gets rewritten and this log gets a note.

  6. Why no settings are published on this site

    Method

    You will not find a voltage table, a frequency target or a set of firmware values here. Two parts with the same model number do not behave the same way, the board and its firmware change what a setting means, and cooling changes it again. A value copied from a web page onto a different machine is the most reliable way to damage hardware slowly. What a page can do is explain the mechanism, name the limit that will bite first, and describe how to find your own answer one variable at a time.