nexoniarz/SchOS
nexoniarz/SchOS
Watch
1
0
Fork
You've already forked SchOS
 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

memory: Schcom v0, and the order change that put it before the installer

Browse source 
Records that the GUI stack moved ahead of the installer, that Schcom v0
runs and how to prove it, the decisions behind the protocol shape
(Wayland-shaped, MIT so linkable, shm id rather than SCM_RIGHTS for now),
and the one-display-device trap in the screendump test.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Nexoniarz 2026-08-09 23:12:56 +02:00
commit 50e61e431b
3 changed files with 78 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

12
.claude/memory/schunix-roadmap-and-projects.md
View file

@ -48,7 +48,17 @@ size, and dedups across images. Most of it exists — `tools/mkschfs.c` and
`tools/mkfs.c` already do content dedup with an `(st_dev, st_ino)` fast path.
`mksip` should share that code.
## The installer, scoped 2026-08-09
## Order changed 2026-08-09: Schcom and SchAPI come before the installer
Nexoniarz: the GUI stack is what is actually needed, the installer can wait.
**Schcom v0 is done** — see [[schcom-v0]]. SchAPI/`libschunix` is still not
started, and is the other half of what was asked for.
`projects/` has build glue now: `make projects` builds against the sysroot libc
and stages into `sysroot/bin`. It is not a dependency of the OS build and
`make` never descends there.
## The installer, scoped 2026-08-09 (deferred, not cancelled)
**A live CD is off the list.** The ISO boots a complete system from the
ramdisk, so it already is the live environment; an installer makes a mountable