THE SCOPE
Process models, filesystems, system calls, kernels, virtualization and operating-system design.
This starting dossier establishes a research remit and reference points for the section. It does not claim to be a comprehensive historical survey. Future articles will identify primary evidence, publication or artifact dates, competing accounts and the limits of verification.
Interfaces matter more than marketing eras
A syscall contract, filesystem format or scheduler design is a clearer technical claim than a broad claim that one system changed everything.
Separate kernel and userland
An operating system can refer to its kernel, its surrounding tools, its distribution or a complete deployed environment.
Reproduction can be difficult
Hardware dependencies, missing build tools and incomplete archives often constrain historical kernel experiments.
OPEN QUESTIONS / NOT ASSUMPTIONS
Questions that guide the reporting.
- 01Which release or kernel tree is being discussed?
- 02Are interfaces documented in primary manuals?
- 03Can attribution be traced to contemporary source or release notes?
PRIMARY & TECHNICAL REFERENCES
Starting sources
The references below are paths into the evidence, not a claim that every historical question is settled. Each future article will provide its own direct citations and version-specific evidence.
- 01The Linux kernel documentation docs.kernel.org
- 02The Unix Heritage Society www.tuhs.org
VERSION RECORD / 1.0
This dossier is revisable.
2026-10-08 — Initial edition. Research scope, evidence lenses, questions and reference starting points published. No external submissions have been reviewed for this initial edition. Future substantive changes should be documented with supporting evidence.
Submit source evidence or a correction →