SchOS/lib/initcode.S
Nexoniarz a1c965da1e include: one folder per subsystem, and includes that name it
Sixty-five headers sat side by side in include/, so `#include "irq.h"`
said nothing about where irq.h was or what it belonged to, and errno.h,
stat.h and fcntl.h at the top shadowed the system's for any host tool
built with -I./include. They are in folders now -- arch/ core/ fs/
dev/ gfx/ net/ uapi/ (and ldls/ for the Linux driver layer) -- and
every include names the folder, as Linux's do: "core/proc.h".

Done mechanically and checked the hard way: the kernel built from this
tree disassembles identically to the one built from the tree before
it. The full image boots, and userland is the same set of programs.
Paths in docs and comments follow; docs/guides/layout.md has a table
of what is where, and tools/fix-includes.py rewrites old-style
includes from the folders in the tree, for code written before this.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S1giNvrHTrPMPw7V6x1kQ4
2026-10-23 15:05:12 +02:00

29 lines
No EOL
591 B
ArmAsm

#include "core/syscall.h"
#include "arch/traps.h"
.code64
.section .text
.global start
start:
lea init(%rip), %rdi
lea argv(%rip), %rsi
mov $SYS_exec, %rax
syscall
exit:
mov $SYS_exit, %rax
syscall
jmp exit
// The kernel's very first exec. There is no fallback and there deliberately
// is not one: /bin/init was the older, hardcoded fork-a-shell process 1, it was
// unreachable from the day this string changed, and an unreachable fallback is
// a thing that rots rather than a thing that saves you.
init:
.string "/bin/schinit"
.p2align 3
argv:
.quad init
.quad 0