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
|
|
@ -55,7 +55,12 @@ files are.
|
|||
|
||||
**Trying to build it** → [guides/building.md](guides/building.md).
|
||||
|
||||
**Wondering what happens next** → [plan/1.0.md](plan/1.0.md), which is the finish line, then [plan/README.md](plan/README.md) for the order.
|
||||
**Wondering what happens next** → [plan/1.0.md](plan/1.0.md), which is the finish
|
||||
line *and* the register of everything half-built. Then
|
||||
[plan/README.md](plan/README.md) for the order.
|
||||
|
||||
**About to start something new** → the register, first. Nothing new starts while
|
||||
it has rows in it, and a row leaves only by being finished or deleted.
|
||||
|
||||
**Something is broken and it feels familiar** → [history/](history/). There is a
|
||||
good chance it is in there.
|
||||
|
|
@ -84,7 +89,7 @@ good chance it is in there.
|
|||
| | |
|
||||
|---|---|
|
||||
| [README](plan/README.md) | The three current decisions and the order they happen in. |
|
||||
| [1.0.md](plan/1.0.md) | **The finish line.** What 1.0 contains, and what is explicitly deferred past it. |
|
||||
| [1.0.md](plan/1.0.md) | **The finish line, and the freeze.** What 1.0 contains, what is deferred, and the register of every half-built thing in the tree. |
|
||||
| [foundations.md](plan/foundations.md) | The kernel work everything else is blocked on. |
|
||||
| [wayland.md](plan/wayland.md) | The GUI stack, and what gets deleted to make room. |
|
||||
| [hybrid.md](plan/hybrid.md) | Moving drivers out of the kernel. |
|
||||
|
|
|
|||
27
docs/Website/Assets/usb.svg
Normal file
27
docs/Website/Assets/usb.svg
Normal file
|
|
@ -0,0 +1,27 @@
|
|||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 200" width="200" height="200">
|
||||
<title>A USB stick</title>
|
||||
<desc>The only medium SchOS is meant to arrive on. There is no installer and
|
||||
no optical drive in the plan -- the stick is the machine's second disk, and on
|
||||
a Chromebox it is the only one that matters.
|
||||
|
||||
Drawn to the same rule as the other marks here: two tones, geometry only, and
|
||||
the accent spent in exactly one place. That place is the activity light,
|
||||
because it is the part of a USB stick that tells you something is happening --
|
||||
the same job the accent does everywhere else in this palette.
|
||||
|
||||
The connector's two contact windows are real holes (fill-rule evenodd) rather
|
||||
than shapes filled with the background colour, so the mark survives being put
|
||||
on a surface that is not the page background.</desc>
|
||||
|
||||
<g fill="#3C2E85">
|
||||
<path fill-rule="evenodd" d="M70 14 h60 v58 h-60 Z
|
||||
M82 30 h13 v26 h-13 Z
|
||||
M105 30 h13 v26 h-13 Z"/>
|
||||
<rect x="62" y="72" width="76" height="15" rx="3"/>
|
||||
<rect x="54" y="87" width="92" height="99" rx="12"/>
|
||||
</g>
|
||||
|
||||
<g fill="#7C5CFF">
|
||||
<circle cx="100" cy="162" r="9"/>
|
||||
</g>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 1.2 KiB |
|
|
@ -1,19 +1,42 @@
|
|||
<!-- SPDX-License-Identifier: Apache-2.0 -->
|
||||
# The website
|
||||
|
||||
Five files and a folder of marks. No build step, no dependencies, no
|
||||
Six files and a folder of marks. No build step, no dependencies, no
|
||||
framework — open `index.html` and it works, including from a `file://` URL.
|
||||
|
||||
```
|
||||
index.html the front page
|
||||
download.html get it, write it to a stick, or build it
|
||||
docs.html the documentation reader
|
||||
style.css the palette, transcribed from include/theme.h
|
||||
app.js the front page: the boot log types, sections fade in
|
||||
docs.js the Markdown renderer and the doc index
|
||||
Assets/ shift.svg (logo), uberblock.svg (SchFS), guru.svg (PSOGM),
|
||||
pride.svg
|
||||
usb.svg (downloads), pride.svg
|
||||
```
|
||||
|
||||
## The download page
|
||||
|
||||
`download.html` links to `releases/schos.iso`, a path relative to this
|
||||
directory. **Nothing puts a file there** — the ISO is 62 MB and does not belong
|
||||
in the repository — so the link is dead until a build is dropped next to the
|
||||
site:
|
||||
|
||||
```sh
|
||||
make iso
|
||||
mkdir -p docs/Website/releases && cp schos.iso docs/Website/releases/
|
||||
```
|
||||
|
||||
The page is written so that this is the only thing that needs doing, and so that
|
||||
nothing on it is a promise the tree cannot keep. In particular the support table
|
||||
says **one real machine, under test** rather than listing hardware, because one
|
||||
Chromebox is the entire bare-metal record and a compatibility list would be
|
||||
fiction. When that changes, change the table; do not soften the wording.
|
||||
|
||||
The `dd` command is split across two lines on purpose. It was one long line
|
||||
first, and 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.
|
||||
|
||||
## The docs reader
|
||||
|
||||
`docs.html` renders the Markdown in `docs/` in the site's own theme, with the
|
||||
|
|
|
|||
|
|
@ -21,6 +21,7 @@
|
|||
</a>
|
||||
<nav>
|
||||
<a href="index.html">Home</a>
|
||||
<a href="download.html">Download</a>
|
||||
<a href="docs.html" class="on">Docs</a>
|
||||
</nav>
|
||||
</div>
|
||||
|
|
|
|||
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>
|
||||
|
|
@ -25,6 +25,7 @@
|
|||
<a href="#what">What it has</a>
|
||||
<a href="#hybrid">Hybrid</a>
|
||||
<a href="#numbers">Numbers</a>
|
||||
<a href="download.html">Download</a>
|
||||
<a href="docs.html">Docs</a>
|
||||
</nav>
|
||||
</div>
|
||||
|
|
@ -42,8 +43,8 @@
|
|||
and runs unmodified <code>musl</code> and <code>toybox</code> on top.
|
||||
</p>
|
||||
<div class="cta">
|
||||
<a class="btn primary" href="#what">What it has</a>
|
||||
<a class="btn" href="#origin">Where it started</a>
|
||||
<a class="btn primary" href="download.html">Download it</a>
|
||||
<a class="btn" href="#what">What it has</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
|
@ -350,9 +351,7 @@
|
|||
<div class="figures">
|
||||
<div class="figure"><b>46,961</b><span>lines in <code>kernel/</code> and <code>include/</code></span></div>
|
||||
<div class="figure"><b>207</b><span>syscalls, Linux numbering</span></div>
|
||||
<div class="figure"><b>128</b><span>uberblock ring slots</span></div>
|
||||
<div class="figure"><b>0</b><span>patches carried against fastfetch</span></div>
|
||||
<div class="figure"><b>1</b><span>driver already running outside the kernel</span></div>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
|
|
@ -407,6 +406,24 @@
|
|||
</div>
|
||||
</section>
|
||||
|
||||
<section class="getband reveal">
|
||||
<div class="wrap">
|
||||
<img src="Assets/usb.svg" alt="">
|
||||
<div>
|
||||
<p class="eyebrow">Try it</p>
|
||||
<h2>One ISO, one stick, nothing written to your disks</h2>
|
||||
<p class="lede">
|
||||
It runs from RAM and leaves the machine as it found it. Or skip the
|
||||
stick entirely — <code>make qemu</code> is the same system in a window.
|
||||
</p>
|
||||
<p class="readerlink">
|
||||
<a class="btn primary" href="download.html">Download SchOS</a>
|
||||
<a class="btn" href="docs.html?doc=guides/building.md">Build it instead</a>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
|
||||
<footer>
|
||||
|
|
|
|||
|
|
@ -282,7 +282,7 @@ header.top {
|
|||
}
|
||||
.card h3 { font-size: 1.05rem; font-weight: 700; }
|
||||
.card p { color: var(--dim); font-size: 0.925rem; margin: 0; max-width: none; }
|
||||
.card .tag {
|
||||
.tag {
|
||||
align-self: flex-start;
|
||||
font-family: var(--mono);
|
||||
font-size: 0.68rem;
|
||||
|
|
@ -293,9 +293,9 @@ header.top {
|
|||
border: 1px solid var(--line);
|
||||
color: var(--dim);
|
||||
}
|
||||
.card .tag.runs { color: var(--ok); border-color: color-mix(in srgb, var(--ok) 35%, transparent); }
|
||||
.card .tag.partial{ color: var(--warn); border-color: color-mix(in srgb, var(--warn) 35%, transparent); }
|
||||
.card .tag.planned{ color: var(--dim); }
|
||||
.tag.runs { color: var(--ok); border-color: color-mix(in srgb, var(--ok) 35%, transparent); }
|
||||
.tag.partial{ color: var(--warn); border-color: color-mix(in srgb, var(--warn) 35%, transparent); }
|
||||
.tag.planned{ color: var(--dim); }
|
||||
|
||||
/* ---- numbers ------------------------------------------------------- */
|
||||
|
||||
|
|
@ -595,3 +595,98 @@ footer .note a { color: var(--accent); }
|
|||
|
||||
/* The two notes sit below the identity line, not beside it. */
|
||||
footer .wrap { row-gap: 1.5rem; }
|
||||
|
||||
|
||||
/* ---- the download page --------------------------------------------- */
|
||||
/*
|
||||
* Same components as the front page, arranged for a page with one job. The
|
||||
* hero here is a two-column split rather than a pitch: the action on the left,
|
||||
* and immediately beside it the thing a download page usually buries, which is
|
||||
* what this has actually been run on.
|
||||
*/
|
||||
|
||||
.getit .wrap { align-items: start; }
|
||||
.getit h1 { font-size: clamp(2rem, 1.5rem + 2.4vw, 3.1rem); }
|
||||
.getit p { color: var(--dim); }
|
||||
|
||||
h2.small {
|
||||
font-size: clamp(1.15rem, 1rem + 0.6vw, 1.4rem);
|
||||
letter-spacing: -0.01em;
|
||||
margin: 0;
|
||||
}
|
||||
|
||||
.getpanel {
|
||||
background: var(--surface);
|
||||
border: 1px solid var(--line);
|
||||
border-radius: 6px;
|
||||
padding: clamp(1.25rem, 3vw, 1.75rem);
|
||||
}
|
||||
.getpanel p { font-size: 0.92rem; margin: 0.85rem 0 0; }
|
||||
|
||||
/* Not a data table -- a two-column list of claims, where the claim on the
|
||||
right is the whole content and should line up down the page. */
|
||||
.support {
|
||||
width: 100%;
|
||||
border-collapse: collapse;
|
||||
margin-top: 1.25rem;
|
||||
font-size: 0.9rem;
|
||||
}
|
||||
.support td { padding: 0.55rem 0; border-top: 1px solid var(--line); }
|
||||
.support tr:first-child td { border-top: 0; }
|
||||
.support td:last-child { text-align: right; white-space: nowrap; }
|
||||
.dimtext { color: var(--dim); }
|
||||
|
||||
.getit .filemeta {
|
||||
margin-top: 1.25rem;
|
||||
font-family: var(--mono);
|
||||
font-size: 0.78rem;
|
||||
color: var(--dim);
|
||||
}
|
||||
.fineprint, .getpanel .fineprint, .card .fineprint {
|
||||
color: var(--dim);
|
||||
font-size: 0.82rem;
|
||||
line-height: 1.65;
|
||||
}
|
||||
|
||||
/* Two columns rather than as-many-as-fit: these two are a pair to be compared,
|
||||
and a three-up row would put the destructive one somewhere it reads as an
|
||||
equal option. */
|
||||
.cards.two { grid-template-columns: repeat(auto-fit, minmax(21rem, 1fr)); }
|
||||
|
||||
/* A command you are meant to type, as opposed to output you are meant to read
|
||||
-- which is what .console is for. The prompt is dim because it is not part
|
||||
of what you type, and the part to substitute is the accent, because that is
|
||||
the only decision in the line. */
|
||||
.cmd {
|
||||
margin: 1.1rem 0 0;
|
||||
padding: 0.8rem 0.9rem;
|
||||
background: #090B0F;
|
||||
border: 1px solid var(--line);
|
||||
border-radius: 4px;
|
||||
font-family: var(--mono);
|
||||
font-size: 0.78rem;
|
||||
line-height: 1.8;
|
||||
color: var(--fg);
|
||||
overflow-x: auto;
|
||||
}
|
||||
.cmd.block { margin-top: 2.5rem; font-size: 0.82rem; padding: 1.1rem 1.2rem; }
|
||||
.cmd .p { color: var(--dim); user-select: none; }
|
||||
.cmd .v { color: var(--accent); }
|
||||
.cmd .c { color: var(--dim); }
|
||||
|
||||
/* The closing band on the front page. Same two-column shape as the crash
|
||||
section, so the page ends the way it turns: a mark on the left, the thing to
|
||||
do on the right. */
|
||||
.getband { border-top: 1px solid var(--line); }
|
||||
.getband .wrap {
|
||||
display: grid;
|
||||
grid-template-columns: clamp(5rem, 10vw, 8rem) minmax(0, 1fr);
|
||||
gap: clamp(1.5rem, 4vw, 3rem);
|
||||
align-items: center;
|
||||
}
|
||||
.getband img { width: 100%; height: auto; display: block; }
|
||||
.getband .readerlink { display: flex; flex-wrap: wrap; gap: 0.75rem; }
|
||||
@media (max-width: 40rem) {
|
||||
.getband .wrap { grid-template-columns: 1fr; }
|
||||
.getband img { width: 5rem; }
|
||||
}
|
||||
|
|
|
|||
|
|
@ -176,24 +176,34 @@ and the reason is worth keeping:
|
|||
> constants and touches no disk. SchFS has no constant to offer — the root
|
||||
> object id comes off the uberblock — so that early `namei("/")` builds an inode
|
||||
> from an unmounted volume. Nothing complains, because absolute paths never
|
||||
> consult cwd: `exec("/bin/init")` works fine. It is the first *relative* lookup
|
||||
> consult cwd: an absolute `exec` works fine. It is the first *relative* lookup
|
||||
> that fails, and in init that is `open("console")`. No console means no fd
|
||||
> 0/1/2, so every shell it spawns exits immediately and init respawns it
|
||||
> forever. The symptom is a silent boot that reads like a hang and is not one.
|
||||
|
||||
`initcode` then execs `/bin/init`, and [init.md](init.md) takes over.
|
||||
`initcode` then execs **`/bin/schinit`**, and [init.md](init.md) takes over.
|
||||
There is no fallback path and deliberately no `/bin/init` any more: the older
|
||||
hardcoded fork-a-shell PID 1 was unreachable from the day that string changed,
|
||||
and an unreachable fallback rots rather than saves.
|
||||
|
||||
## 6. What the screen shows
|
||||
|
||||
**The display is not the kernel log.** `cons_serial_only` starts *set*: every
|
||||
boot message goes out the UART and nothing goes to the framebuffer. The loader's
|
||||
splash therefore survives the whole of boot rather than being wiped a few
|
||||
hundred milliseconds in, and `console_takeover()` clears the flag on the first
|
||||
`exec()`, when userspace genuinely starts.
|
||||
**The kernel log is on screen from the first line that can draw.** `kmain`
|
||||
attaches the loader's framebuffer and clears `cons_serial_only` before it does
|
||||
anything else, so `pci: 7 devices` and `schfs: mounted` are visible on the
|
||||
machine itself.
|
||||
|
||||
Nothing is lost — the serial line is where `bootcheck` reads from and where you
|
||||
want the messages when something is wrong — and the F8 verbose boot never sets
|
||||
the flag, so "show me everything" still works.
|
||||
This is the reverse of what the flag was added for, and the reversal was earned.
|
||||
The original argument was that a boot which prints a developer's log to the
|
||||
screen looks like a hobby project, and it is a good argument — right up until a
|
||||
Chromebox with **no serial port** froze at boot showing nothing at all. The whole
|
||||
diagnosis had to be made from a photograph of a screen that had been told to stay
|
||||
quiet. A tidy boot that cannot be debugged on the hardware it fails on is not a
|
||||
trade worth making.
|
||||
|
||||
`cons_serial_only` still exists for the case it is now the right answer to: no
|
||||
framebuffer from the loader. Then everything goes to the UART and
|
||||
`console_takeover()` clears the flag when userspace starts.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -54,6 +54,83 @@ currently either broken, missing, or unproven.
|
|||
|
||||
---
|
||||
|
||||
## The freeze, and the register of unfinished work
|
||||
|
||||
**No new capability is started until this register is empty.**
|
||||
|
||||
The failure this exists to stop is not laziness and 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 one is left in a corner:
|
||||
present in the tree, not finished, not deleted, and not visible in any list.
|
||||
Enough of those and the tree stops matching its own documentation, which is the
|
||||
state this register was written to end.
|
||||
|
||||
Two rules, and they are the same rule seen from either end:
|
||||
|
||||
> **Nothing enters the register except by being finished or being deleted.**
|
||||
>
|
||||
> **Adding a row requires closing one.** Two things in flight. Never three.
|
||||
|
||||
A row leaves this table in one of exactly two ways. Either it is **finished** —
|
||||
and finished means a description exists in [../architecture/](../architecture/),
|
||||
not that the code works — or it is **deleted**, and deleted means gone from the
|
||||
tree, not marked for deletion. A directory that has said "to be deleted" for
|
||||
months is the corner, not the cure; `projects/schwm/` and `projects/schde/`
|
||||
proved that and are now actually gone.
|
||||
|
||||
### Built, and not connected to anything
|
||||
|
||||
The galling ones. The work exists, is tested, and nothing uses it.
|
||||
|
||||
| | Where it stopped |
|
||||
|---|---|
|
||||
| **The text layer** | `kernel/dev/text.c` and `kernel/dev/ttf.c` are 850 lines that rasterise TrueType and draw at any pixel position. The console still indexes `font_data[256][16]`. The only caller is a self-test. |
|
||||
| **A font from disk** | Same layer, same reason. The console's 8×16 CP437 grid is compiled in. |
|
||||
| **Socket activation** | `schinitd` parses `[Socket name]` and remembers the path. Nothing holds the socket. **This is the entire reason for copying launchd**, and it is the half that was not built. |
|
||||
| **`display_ops.wait_vblank`** | In the vtable, implemented by the VBE driver, left null by virtio-gpu. A compositor that needs it cannot rely on it. |
|
||||
|
||||
### Started, and stopped part-way
|
||||
|
||||
| | Where it stopped |
|
||||
|---|---|
|
||||
| **`foundations.md`** | Item 1 built. Items 2 (a shareable memory object), 3 (`AF_UNIX` in the filesystem namespace), 4 and 5 open. **Wayland stops at item 2.** |
|
||||
| **`hybrid.md`** | All four mechanisms built, H1 done. **H2 — kill the driver on purpose and watch it come back — is the milestone the plan itself calls the one that proves the whole idea**, and it is not done. |
|
||||
| **Schcom v0** | 715 lines that composite, over a wire format that is superseded. Frozen: it runs, nothing more is added, and it is kept only because it is the one thing in the tree that has ever put a client's pixels on screen. |
|
||||
| **A released PCI device** | `PCIIOC_RELEASE` leaves the line masked and the in-kernel driver unbound. Nothing starts a replacement. Half a handover. |
|
||||
|
||||
### Named in a "what it does not do" and still true
|
||||
|
||||
Not corners — these were written down honestly on the day and stayed written
|
||||
down. They are here so the register is the whole picture rather than the
|
||||
flattering part of it.
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| `/proc/<pid>/exe` is a regular file | so `readlink()` fails and `ps -o comm` prints `[init]` |
|
||||
| `getrusage` | does not distinguish `RUSAGE_CHILDREN` from `RUSAGE_SELF` |
|
||||
| No slab allocator | every subsystem's fixed-size table is a consequence |
|
||||
| No `getsockname`/`getpeername` | and `accept()` does not report an AF_INET peer |
|
||||
| No routing table | first interface wins, which is a rule and not routing |
|
||||
| No descriptor garbage collector | a socket passed over itself and never received leaks the pair |
|
||||
|
||||
### Frozen — scoped, unstarted, and not to be started
|
||||
|
||||
Neither cancelled nor in progress. **Do not open these.**
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| `projects/schinst/` | the installer, the installation environment, `.sip` |
|
||||
| `projects/schfs-linux/` | SchFS as a filesystem for Linux |
|
||||
| [roadmap.md](roadmap.md) §4 | the interactive crash screen |
|
||||
| [roadmap.md](roadmap.md) §6 | SchFS beyond SchOS |
|
||||
| [schapi.md](schapi.md) | the API layering, designed and not built |
|
||||
|
||||
Each of those is well argued and none of them is on the path to the acceptance
|
||||
test above. That is the whole test for whether something belongs in this section:
|
||||
**not "is it worth doing" but "does 1.0 fail without it".**
|
||||
|
||||
---
|
||||
|
||||
## The four gates
|
||||
|
||||
In order. **Do not start a gate before the one before it closes**, and closing
|
||||
|
|
|
|||
|
|
@ -9,6 +9,11 @@ leaves — deleted from here, rewritten as a description in
|
|||
> It draws a finish line and puts most of the work below on the far side of it.
|
||||
> **Anything not named there is not being worked on**, and the documents in this
|
||||
> directory describe more than 1.0 contains.
|
||||
>
|
||||
> It also holds **[the register of unfinished work](1.0.md#the-freeze-and-the-register-of-unfinished-work)**,
|
||||
> which is the one place anything half-built is listed. No new capability starts
|
||||
> until that register is empty, and a row leaves it only by being finished or by
|
||||
> being deleted from the tree.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -18,7 +23,7 @@ Taken together, because they turn out to need the same foundation.
|
|||
|
||||
| | |
|
||||
|---|---|
|
||||
| **[wayland.md](wayland.md)** | The GUI stack becomes Wayland. SchWM and SchDE are deleted; Schcom survives and changes its wire format. |
|
||||
| **[wayland.md](wayland.md)** | The GUI stack becomes Wayland. SchWM and SchDE are **deleted** — actually gone from the tree, not marked; Schcom survives and changes its wire format. |
|
||||
| **[hybrid.md](hybrid.md)** | The kernel becomes hybrid — drivers move out into userspace processes, starting with the GPU. **Partly built**: all four mechanisms exist and the GPU driver already runs outside the kernel. |
|
||||
| ~~init.md~~ | **Built.** PID 1 is now a role the kernel refills; the description moved to [../architecture/init.md](../architecture/init.md). |
|
||||
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ So, for SchOS:
|
|||
|
||||
```
|
||||
┌──────────────────────────────────────────────┐
|
||||
│ applications, SchWM, SchDE │
|
||||
│ applications, Schcom and its clients │
|
||||
├──────────────────────────────────────────────┤
|
||||
│ SchAPI │ POSIX / Linux personality│ ← THE STABLE BOUNDARY
|
||||
├──────────────────┴───────────────────────────┤
|
||||
|
|
|
|||
|
|
@ -3,13 +3,18 @@
|
|||
Schcom survives and changes its wire format. SchWM and SchDE are deleted. What
|
||||
follows is why that is not a retreat, and what it costs.
|
||||
|
||||
Blocked on [foundations.md](foundations.md), items 1–4.
|
||||
Blocked on [foundations.md](foundations.md), items 1–4. **Item 1 is built** —
|
||||
descriptor passing, without which no Wayland client can hand over a buffer. Item
|
||||
2, a shareable memory object, is the next thing it stops at.
|
||||
|
||||
---
|
||||
|
||||
## What is deleted
|
||||
## What was deleted
|
||||
|
||||
`projects/schwm/` and `projects/schde/`. Both are README-only; no code is lost.
|
||||
`projects/schwm/` and `projects/schde/`, both README-only; no code was lost. They
|
||||
are **gone from the tree now** rather than marked for deletion — a directory that
|
||||
has said "to be deleted" for months is a corner, not a decision. The arguments
|
||||
each made are kept below, because they are the part worth keeping.
|
||||
|
||||
### SchWM is not abandoned — Wayland dissolves it
|
||||
|
||||
|
|
@ -19,7 +24,7 @@ that the compositor *is* the window manager**: there is no protocol by which a
|
|||
second process places another's windows, and every attempt to add one has been a
|
||||
private extension.
|
||||
|
||||
So the argument in `projects/schwm/README.md` —
|
||||
So SchWM's own argument —
|
||||
|
||||
> *"Compositing is mechanical and must never stall: it runs every frame and a
|
||||
> mistake there is a frozen screen. Window management is policy, full of special
|
||||
|
|
@ -31,11 +36,15 @@ Schcom**, not a process boundary: policy in its own file behind its own
|
|||
interface. Do not keep it in its own process, because the protocol to talk to it
|
||||
does not exist.
|
||||
|
||||
### SchDE is re-sited rather than deleted
|
||||
### SchDE is re-sited rather than abandoned
|
||||
|
||||
A panel, a launcher and a wallpaper are ordinary Wayland clients using
|
||||
`wlr-layer-shell` — MIT, an XML file, no dependency. They need no directory of
|
||||
their own until one of them is written.
|
||||
their own until one of them is written. SchDE's other observation stands on its
|
||||
own and is recorded here so it does not go with the directory: **a GUI terminal
|
||||
is not the kernel console with a window around it.** The console parses ANSI
|
||||
because it draws straight to the framebuffer; a terminal client parses ANSI
|
||||
itself and renders it with proportional-capable text. The two share no code.
|
||||
|
||||
### `projects/schinst/` stays
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue