57aff40228
docs/ was ten files where a plan, a description, a guide and a bug report all
sat next to each other. It is now architecture/ (what SchOS is), plan/ (what it
will be), guides/ (how to work on it) and history/ (why it is like this), with
an index that states the one rule holding it together: when something is
finished it moves from plan/ to architecture/ and is rewritten as a description
of the thing rather than a record of building it.
A ticked checkbox says the work happened. It does not say what the work
*produced*, and six months later the checkbox is all that is left. The network
stack proved the point: finished, verified end to end, and for a month the only
description of it anywhere was a checkbox four levels of indentation deep.
So roadmap.md went from 534 lines to 181 -- nothing deleted, the done work
graduated. Seven subsystems that were finished and undescribed now have
descriptions: boot, kernel, syscalls, filesystem, networking, graphics, usb,
init. Every one ends with "What it does not do", which is the section that pays;
a document listing only strengths is marketing, and the reader who needs it most
is the one about to trip over a limitation nobody wrote down.
schfs.md still opened with "phases 1 through 3 1/2 are done, phase 4 is next"
long after all five had landed. It is a description now, with the phase record
and the hard-won bugs moved to history/.
Three corrections found on the way, all load-bearing:
* projects/schcom/README.md claimed SCM_RIGHTS was done. There is no
sendmsg/recvmsg in the kernel at all, and an entire GUI plan rested on it.
* The root README said "No TCP/IP" months after the stack landed.
* history/kernel.md sec.7 was marked "in progress" on a problem that process
groups solved.
Also adds plan/1.0.md, which draws a finish line so the open list stops being
infinite, and marks schwm/ and schde/ superseded: in Wayland the compositor is
the window manager, so that split dissolves rather than being abandoned.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VQ7Qx8E1q1M1bbCq8QLHS2
2.4 KiB
| name | description | metadata | ||||||
|---|---|---|---|---|---|---|---|---|
| schos-linux-machine | The Fedora laptop, its project path and memory key, and the three things only it can test |
|
Nexoniarz works from two machines and moved the project to the second on 2026-08-09.
| Windows desktop | Fedora laptop | |
|---|---|---|
| path | D:\DEV\SchOS |
/home/nexoniarz/Documents/SchOS |
| memory key | D--DEV-SchOS |
-home-nexoniarz-Documents-SchOS |
Fedora 44, Ryzen 5 7000-series, RTX 4050, 16 GB DDR5. The GPU is irrelevant to the build — QEMU runs headless for tests.
tools/posix/setup-fedora.sh installs the toolchain (--check to only report).
docs/history/moving-to-linux.md is the procedure. Memory moves with
schos-memory-sync: import after arriving, export and commit after a
session that learned something.
Three things only the Linux machine can do, and they are the reason the move matters:
make portsbuilds musl, toybox and mksh from source. Windows cannot do it at all — the build skips ports and uses whatever is staged insysroot/.- The SchFS round-trip test needs symlinks and hard links, which Git Bash cannot create, so it skips on Windows.
- KVM. A Ryzen box has SVM, so QEMU runs at native speed. Deliberately not the Makefile default: the suite's timings were set under TCG.
All three ran for the first time on 2026-08-09, and the baseline is green:
make ports (the rebuilt sysroot/bin/sh no longer carries __schunix_tp),
make, make schfs-check — round-trip included, collision pass and all —
and bootcheck.ps1 at 27/27, then 108 [ok] with
-Fb -Tty -Usb -Sock -Evdev -Ps. Expect one "no prompt" on wc -c in the
extended run; the check it feeds still passes, so it is pacing, not a fault.
The move exposed two latent bugs, both fixed the same day — see schos-fedora-move-bugs. Neither was Fedora's fault; the host and the freshly built userland simply drove paths Windows never did.
PowerShell has no Fedora package, and tools/windows/bootcheck.ps1 is the
test suite. pwsh runs it on Linux fine; it comes from Microsoft's repo or the
GitHub tarball. Nothing else needs it.
Never push. There is no git remote and there should not be one until Nexoniarz says otherwise — see nexoniarz-sharing-preference. "Push to git" in this project means commit locally.