Contact the Desk

Mail to a reference desk splits in two before anyone can answer it: mail about the desk's own pages, and mail about the software the desk writes about. Overclockix produces the second kind. This page describes where each kind goes, what a correction can change, and what it cannot.

What this desk answers for

The Burn-In Desk writes about stability testing, diagnostics, live systems and the words used around them, and it keeps a single record, the Overclockix release history. It is a record of publications, not a publication of software. The desk did not create Overclockix, does not maintain it, does not distribute it and does not speak for it. The history is short to state: first released in 2003 on a Knoppix base, inactive from 2005, taken over in 2011 on a Debian base, and last published as version 7.8.0 on June 1, 2015 according to DistroWatch.

Which correction goes where?

A correction has to be routed before it can be read, and the routing follows whoever holds the fact.

One row needs a sentence of its own. The README in the repository tells readers to visit this domain for project information and downloads, and some of them do. That pointer belongs to the README. This desk is not the project it points at, serves nothing, and names no mirror.

Where a correction about the software lands

A bug in a build script, a wrong step in a README, a file that should be linked to another and is not: none of that is the desk's to fix. The distro's source is published in the Overclockix repository, labeled a public archive, showing 86 commits on a master branch, 7 stars and no forks. The tree separates i386 from amd64 and iso-hybrid from usb-hdd, with a shared common tree, a scripts directory, a Dockerfile and a run.sh alongside. The README documents its own quirks: hard links do not survive a move to GitHub and do not work with live-build, so a script recreates them after a clone, and a file that still shows a single link after that is a file no build uses. That is the level a code correction lives at, and it lives there, not here.

What can this desk actually change?

Its own sentences, and nothing besides. A correction against a page here is read against the source that page cites. If the desk misquoted the source, the page changes. If the desk quoted the source correctly and the source itself is at issue, the desk holds no authority over the source; it can only state, on its own page, what the source says and when it was read. The Overclockix release record is DistroWatch's, a page showing a last update of February 8, 2026, read here on September 5, 2026. Neither that page nor the dates on it can be amended from a bench that does not own them.

How long does a correction take?

This page publishes no response time, and none will be invented to fill the space. What can be described is the order of the work: the sentence is located, the source it cites is read again, and the page either stands or changes. Whatever channel carries the correction, that part does not vary. A correction that names no page starts the work late, because a release record is a document of dates, and a claim about a date that arrives without the page it sits on has to be found before it can be checked.

What a usable correction contains

Three things, all small: the page, the sentence, and what the desk should read instead. "The release count is wrong" sends the desk hunting. "The releases page states 8, the record I read states 9, and I read it here" hands the desk a check it can run. How a source is weighed is written down in sources and method, and what the desk accepts and declines is in the editorial policy. A correction with a page, a sentence and a source moves. A complaint about a project this desk does not maintain does not, because there is nothing here to move it with.