Block a user
fc057820fa
store: refuse a store that cannot be read — and the proof that the refusal is not the whole defect
9fb4169e52
store: refuse a device that does not carry the packed image's magic (inert, NOT installed)
74bd2bc5ba
the store on the dongle: this CUBE writes to removable media and reads it back off the device
c2b85a715a
the write's durability: the gate was right, my first attribution of it was not, and the wall is 26 of 26
3d1124616d
flags: §7 said the arrangement vocabulary was not built — it is, and it has run on the box, so the paragraph now says what exists and what still does not
c720cb142e
site: the fsync price, measured rather than estimated — 4.321 ms for one pwrite+fsync, 8.630 ms for append's two, 8.202 ms for the whole kernel put, so a durable write is fsyncs and almost nothing else
a7463bed89
flags: §7.2 tests the alignment hypothesis — the redundancy is the slot pair, 100% of slot 1's non-zero chunks appear in slot 0, and the first whole-image figure was mostly zeros
fad1ef2786
flags: §7.1 puts the chain's value where it was measured — nothing for a compressed build artefact, ~a factor of 3 for the store's own snapshots, and fixed slices beat CDC here because the format is aligned
9a0408b58d
flags: §7 fixes the arrangement vocabulary's semantics before anyone writes code — consecutive z, the caller splits, the kernel joins, and a chain that does not terminate fails loudly
b3dc55392e
read: the log window is cached with the table — the last device read a read made for nothing
81049c9df6
flags: the boot class bit was never in WordFlags' field — the collision is latent, and resolved by declaring the field rather than moving the bit (WordFlags has no spare bit to move it to)