docs: 1.0 is reached; Schcom stays; Linux's r8169 set ships

1.0: the acceptance test drops its reboot clause (a live system is the finish line) and passes. Schcom is kept with a
job: the installer's GUI first, SchDE on top later (roadmap section 5). The old 'LDLS ships no Linux code' policy is
gone from ldls/devices/licensing/Makefile/.gitignore/ldlsd; NOTICE records the r8169 modules (GPL-2.0-only) and the
Realtek firmware. The download button points at the v0.1.0 release asset; the stale 64 MB ISO under docs/Website is
removed. mkaroot.sh's -dumbSched comment no longer claims SchOS has no threads.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EVRhxi9zpdW2uDUN4FVcao
This commit is contained in:
Nexoniarz 2026-10-26 08:23:20 +01:00
commit 59aff881ac
21 changed files with 175 additions and 141 deletions

View file

@ -70,22 +70,16 @@ rm -rf docs/Website/niveus && cp -r docs/niveus docs/Website/niveus
## 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:
`download.html` links to the ISO attached to the release on the project's Forgejo
(`https://pandor.pl/git/nexoniarz/SchOS/releases/download/v0.1.0/schos-v0.1.0.iso`). The ISO is
hundreds of megabytes and does not belong in the repository, so nothing is stored under
`docs/Website/`; publishing a release is `tools/posix/release.sh vX.Y.Z`, and **when the tag
changes, change the link and the version beside it** (only the newest release keeps its ISO).
```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 page is written so that nothing on it is a promise the tree cannot keep. In
particular the support table lists the three machines SchOS has booted on and nothing else,
because that 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