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

Rename Schunix to SchOS; the kernel becomes SchIFT

Browse source 
Removes the "-unix" element and with it any trademark exposure to The
Open Group.

The split follows the ecosystem layout: SchOS is the system, and the
kernel has its own name. Kernel-identity strings are the only places
that take SchIFT -- uname(2) sysname, /proc/version, and the two licence
sentences that say "kernel" outright. That is what every Unix does here:
`uname -s` on Linux reports the kernel, not the distribution. Everything
a user reads as the product -- panic screen, boot menu, error prefixes,
docs, LICENSE, NOTICE -- is SchOS.

schunix.img is schos.img, the logo assets and the musl TLS patch are
renamed, and __SCHUNIX__ is __SCHOS__ (the define and the patch that
consumes it moved together).

Two things the rename broke, both found by the bootcheck suite:

  - shmtest wrote "SCHUNIX-MMAP-OK" with a hardcoded length of 15 and
    compared it back by hand-counted offsets (m[3]=='U', m[14]=='K').
    The shorter marker left the write running two bytes past the literal
    and the compare reading past the data, failing a file-backed mmap
    that was working correctly. Now written and compared through one
    constant with sizeof.
  - bootcheck asserted a 31-byte file after appending to
    "hello-from-schunix"; the shorter string makes it 29.

Both are the same mistake: a string literal whose length is written out
somewhere else. Full suite green -- base, Tty, Ps, Sock, Fb, Usb, Evdev.
This commit is contained in:
Nexoniarz 2026-08-09 14:09:59 +02:00
commit e04ca28812
83 changed files with 520 additions and 601 deletions
Download patch file Download diff file Expand all files Collapse all files

6
run.ps1
View file

@ -1,4 +1,4 @@
# Schunix launcher (Windows side).
# SchOS launcher (Windows side).
#
# Why this exists: without it you have to hand-type a QEMU command line, and a
# hand-typed one drifts -- notably onto a stale fs.img, which boots to
@ -35,7 +35,7 @@ $root = $PSScriptRoot
# The two images QEMU needs. These paths are the single source of truth --
# keep them in sync with the 'qemu' and 'qemu-schfs' targets in the Makefile.
$hda = Join-Path $root 'schunix.img'
$hda = Join-Path $root 'schos.img'
$hdb = if ($SchFS) { Join-Path $root 'build\schfs.img' }
else { Join-Path $root 'build\fs.img' }
@ -58,7 +58,7 @@ if (-not $NoBuild) {
# of memory, which leaves device 1 free for the SchFS volume. Booting the
# normal kernel with a SchFS disk as hdb would leave it with no root.
$target = if ($SchFS) { 'make ramroot && make build/schfs.img' } else { 'make' }
& $bash -lc "cd /d/DEV/Schunix && $target"
& $bash -lc "cd /d/DEV/SchOS && $target"
if ($LASTEXITCODE -ne 0) { throw "build failed (exit $LASTEXITCODE)" }
}