freeze: one register for everything half-built, and the corners cleared
The failure this is against is not scope creep. It is abandonment by promotion:
a thing gets built to the point where it works, the next thing becomes more
interesting, and the first is left in a corner -- in the tree, not finished, not
deleted, and not in any list. Enough of those and the tree stops matching its
own documentation.
docs/plan/1.0.md now holds the register, and it is the only place anything
half-built is listed. Four sections, because the kinds are genuinely different:
built and connected to nothing (the text layer, a font from disk, socket
activation, wait_vblank); started and stopped part-way (foundations 2-5, hybrid
H2, Schcom v0, a released PCI device that nothing brings back); named in a "what
it does not do" and still true; and frozen -- scoped, unstarted, not to be
started. The rule is that nothing enters except by being finished or deleted,
and that adding a row requires closing one.
1.0.md already said "two things in flight, never three". It was right and it was
not being followed.
Then the corners themselves, because a register written over a tree full of them
is just a longer list:
- cmd/init is deleted. Nothing had execed /bin/init since initcode.S changed
to /bin/schinit; it was built and installed on every image as an unreachable
fallback, and an unreachable fallback rots rather than saves.
- projects/schwm/ and projects/schde/ are deleted. Both said "to be deleted"
in their own first paragraph, which proves only that a directory marked for
deletion is not deleted by being marked. README-only, no code lost, and the
arguments each made are moved into wayland.md where they are still true.
- projects/schcom/schcom and schcom-demo were tracked binaries. Untracked, and
.gitignore'd.
Three code comments and one document described a boot that has not happened
since 7d44eb7. cons_serial_only starts set, but kmain clears it on its first
lines now, so the splash does not survive the boot and the kernel log is on
screen from the start. That reversal was earned by a Chromebox with no serial
port freezing at boot showing nothing at all, and the comments still argued the
losing side of it.
The site:
- a download page. One ISO, what it has actually been run on -- one machine,
under test -- Ventoy and dd, what the first boot looks like step by step,
and the build if you would rather. The support table names one Chromebox
rather than listing hardware, because one Chromebox is the entire bare-metal
record and a list would be fiction.
- Assets/usb.svg, drawn to the same rule as the other marks: two tones,
geometry only, the accent spent in one place, and that place is the activity
light because it is the part that tells you something is happening.
- Download is in both navs and is the hero's primary action; a closing band
ends the front page on it.
- the uberblock-slots and drivers-outside-the-kernel figures are gone. Three
numbers left, including the fastfetch one, which stays because it is funny.
Two things caught by rendering the pages instead of assuming: .hero p was
beating .filemeta on specificity and the file line was coming out at body size,
and the dd command was one line long enough that the card clipped it at `conv=`
-- a destructive command that can scroll half of itself out of view is a good
way to take somebody's disk. It is two lines now.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VQ7Qx8E1q1M1bbCq8QLHS2
This commit is contained in:
Nexoniarz
parent
d3c37f82b6
commit
c0ed23cc56
24 changed files with 586 additions and 257 deletions
226
docs/Website/download.html
Normal file
226
docs/Website/download.html
Normal file
|
|
@ -0,0 +1,226 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<title>Download — SchOS</title>
|
||||
<meta name="description" content="Get SchOS: a bootable ISO for a USB stick, what it needs, what it does on first boot, and how to build one yourself.">
|
||||
<link rel="icon" href="Assets/shift.svg" type="image/svg+xml">
|
||||
<link rel="stylesheet" href="style.css">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<header class="top">
|
||||
<div class="wrap">
|
||||
<a class="brand" href="index.html">
|
||||
<img src="Assets/shift.svg" alt="">
|
||||
SchOS
|
||||
</a>
|
||||
<a class="pride" href="#pride-note" title="SchOS stands with the LGBTQIAP+ community — every month of the year">
|
||||
<img src="Assets/pride.svg" alt="Progress Pride flag">
|
||||
</a>
|
||||
<nav>
|
||||
<a href="index.html">Home</a>
|
||||
<a href="download.html" class="on">Download</a>
|
||||
<a href="docs.html">Docs</a>
|
||||
</nav>
|
||||
</div>
|
||||
</header>
|
||||
|
||||
<main id="top">
|
||||
|
||||
<section class="hero getit">
|
||||
<div class="wrap">
|
||||
<div>
|
||||
<p class="eyebrow">Download</p>
|
||||
<h1><img class="mark" src="Assets/usb.svg" alt="">Put it on a stick</h1>
|
||||
<p>
|
||||
SchOS ships as one bootable ISO. It boots on UEFI, runs entirely from
|
||||
RAM, and touches nothing on the machine unless you tell it to — there is
|
||||
no installer yet, and that is the point of trying it this way.
|
||||
</p>
|
||||
<div class="cta">
|
||||
<a class="btn primary" href="releases/schos.iso" download>Download the ISO</a>
|
||||
<a class="btn" href="#build">Build it yourself</a>
|
||||
</div>
|
||||
<p class="filemeta">
|
||||
<code>schos.iso</code> · about 62 MB · UEFI x86-64 · nothing is written
|
||||
to your disks
|
||||
</p>
|
||||
</div>
|
||||
|
||||
<div class="getpanel">
|
||||
<p class="eyebrow">Before you do</p>
|
||||
<h2 class="small">This has booted on exactly one real machine</h2>
|
||||
<p>
|
||||
Everything below QEMU is honest reporting rather than a compatibility
|
||||
list. SchOS drives real hardware, and it has been run on a very small
|
||||
number of it.
|
||||
</p>
|
||||
<table class="support">
|
||||
<tr><td>QEMU / OVMF</td><td><span class="tag runs">boots</span></td></tr>
|
||||
<tr><td>Asus Chromebox <span class="dimtext">Guado CN62</span></td><td><span class="tag partial">under test</span></td></tr>
|
||||
<tr><td>Anything else</td><td><span class="tag planned">unknown</span></td></tr>
|
||||
</table>
|
||||
<p class="fineprint">
|
||||
If it does not boot, the kernel log is on the screen from its first line
|
||||
— that is deliberate, and it is there because of this machine. A photo of
|
||||
where it stops is a genuinely useful bug report.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<section id="write" class="reveal">
|
||||
<div class="wrap">
|
||||
<p class="eyebrow">Writing it</p>
|
||||
<h2>Two ways onto a stick</h2>
|
||||
<p class="lede">
|
||||
Ventoy first, because it is the one that does not cost you the stick. An
|
||||
ISO copied onto a Ventoy drive sits next to every other ISO on it, and the
|
||||
drive stays an ordinary drive.
|
||||
</p>
|
||||
|
||||
<div class="cards two">
|
||||
<div class="card">
|
||||
<span class="tag runs">recommended</span>
|
||||
<h3>Ventoy</h3>
|
||||
<p>
|
||||
Copy the file. That is the whole procedure — Ventoy finds it and offers
|
||||
it in its menu at boot, and the stick remains usable for everything
|
||||
else.
|
||||
</p>
|
||||
<pre class="cmd"><span class="p">$</span> cp schos.iso /run/media/<span class="v">you</span>/Ventoy/</pre>
|
||||
<p class="fineprint">
|
||||
This is how SchOS is actually tested on hardware. No optical drive has
|
||||
been involved at any point.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
<div class="card">
|
||||
<span class="tag partial">destructive</span>
|
||||
<h3><code>dd</code></h3>
|
||||
<p>
|
||||
Writes the image over the whole device. <b>Check the device name
|
||||
twice</b> — there is no confirmation and no undo, and the wrong letter
|
||||
takes a disk with it.
|
||||
</p>
|
||||
<pre class="cmd"><span class="p">$</span> lsblk
|
||||
<span class="p">$</span> sudo dd if=schos.iso of=/dev/<span class="v">sdX</span> \
|
||||
bs=4M status=progress conv=fsync</pre>
|
||||
<p class="fineprint">
|
||||
<code>of=</code> is the whole device, not a partition — <code>sdX</code>
|
||||
and never <code>sdX1</code>.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<section id="firstboot" class="reveal">
|
||||
<div class="wrap">
|
||||
<p class="eyebrow">First boot</p>
|
||||
<h2>What actually happens</h2>
|
||||
<p class="lede">
|
||||
Written out because a system you have never seen before gives you no way to
|
||||
tell "working" from "stuck", and the difference is worth knowing in advance.
|
||||
</p>
|
||||
|
||||
<div class="origin-grid">
|
||||
<div class="step">
|
||||
<span class="when">1</span>
|
||||
<h3>The loader</h3>
|
||||
<p>
|
||||
A splash, and <b>F8</b> for boot options. It is a PE/COFF loader built
|
||||
with clang and lld-link; there is no BIOS path, so the firmware has to
|
||||
be in UEFI mode.
|
||||
</p>
|
||||
</div>
|
||||
<div class="step">
|
||||
<span class="when">2</span>
|
||||
<h3>The kernel log</h3>
|
||||
<p>
|
||||
On screen, from the first line that can draw. Cores, the PCI bus, the
|
||||
network card, the filesystem. If it stops, it stops somewhere you can
|
||||
read.
|
||||
</p>
|
||||
</div>
|
||||
<div class="step">
|
||||
<span class="when">3</span>
|
||||
<h3>A shell</h3>
|
||||
<p>
|
||||
<code>schinit</code> starts one on the console and a second on
|
||||
<code>tty2</code>. <code>mksh</code> is <code>/bin/sh</code>, with
|
||||
<code>zsh</code> beside it and the real toybox userland behind both.
|
||||
</p>
|
||||
</div>
|
||||
<div class="step">
|
||||
<span class="when">4</span>
|
||||
<h3>Six terminals</h3>
|
||||
<p>
|
||||
<code>AltGr+F1</code>…<code>F6</code> switches between them — the one
|
||||
chord a Linux host does not take for itself — or <code>chvt N</code>
|
||||
from a shell.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<p class="seam-note">
|
||||
<b>Nothing is written to your disks and nothing persists.</b> The root
|
||||
filesystem is in RAM; the machine is exactly as you left it after a reboot,
|
||||
including the parts of it you were hoping to keep. There is no installer —
|
||||
<a href="docs.html?doc=plan/1.0.md">1.0</a> is where that starts.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<section id="build" class="reveal">
|
||||
<div class="wrap">
|
||||
<p class="eyebrow">Or build it</p>
|
||||
<h2>Clone it, build it, boot it</h2>
|
||||
<p class="lede">
|
||||
The toolchain is one file. On NixOS <code>shell.nix</code> brings the whole
|
||||
thing in; elsewhere it is clang, lld, GNU make and a host compiler — see
|
||||
<a href="docs.html?doc=guides/building.md">the build guide</a>.
|
||||
</p>
|
||||
|
||||
<pre class="cmd block"><span class="p">$</span> git clone <the repository> schos && cd schos
|
||||
<span class="p">$</span> nix-shell <span class="c"># NixOS only; elsewhere see the build guide</span>
|
||||
<span class="p">$</span> make iso <span class="c"># produces schos.iso</span>
|
||||
<span class="p">$</span> make qemu <span class="c"># or just run it, without a stick</span></pre>
|
||||
|
||||
<p class="seam-note">
|
||||
<code>make qemu</code> is the one to reach for first. Everything on this
|
||||
page works there, it takes seconds rather than a reboot, and a serial
|
||||
console beats a photograph of a screen.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
|
||||
<footer>
|
||||
<div class="wrap">
|
||||
<span>SchOS — kernel <b>SchIFT</b>, filesystem <b>SchFS</b>.</span>
|
||||
<span class="mono">Apache-2.0, with the xv6-derived core under MIT.</span>
|
||||
<span class="pride-note" id="pride-note">
|
||||
<img src="Assets/pride.svg" alt="">
|
||||
Built by, and for, people of every orientation and gender identity.
|
||||
The flag stays up all year.
|
||||
</span>
|
||||
<span class="note" id="ai-note">
|
||||
<b>On AI.</b>
|
||||
Parts of SchOS were written with AI assistance, and that is not the measure
|
||||
of anything. A project is good when the people building it understand what
|
||||
was built, and bad when nobody does — whoever, or whatever, typed it. Vibe
|
||||
your way through and you get something no one can fix. Stay in the loop and
|
||||
you get a system you can explain line by line. The bug writeups in
|
||||
<a href="docs.html?doc=history/kernel.md">history/</a> are where that gets
|
||||
checked, including the wrong turns.
|
||||
</span>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
<script src="app.js"></script>
|
||||
</body>
|
||||
</html>
|
||||
Loading…
Reference in a new issue