Skip to content
Linux Systems Field Manual

Overview

Imported from _research/manual-study-linux/README.md.

Linux Manual Study Workspace

Purpose: build source-backed Linux implementation fluency for designing a Linux-inspired Rust system and AI-native operating/runtime layers.

Authoritative source:

  • ../../repositories/reference/linux-study-clean: clean Linux source baseline.
  • Commit: 1dc18801b.
  • Existing linux and linux-full folders are retained as historical references and must not be normalized or reset as part of this workflow.

Depth standard:

  • GPUI-style exhaustive review for selected files.
  • Every reviewed source file gets a ledger row and a source note.
  • Every skipped or deferred file gets a precise reason.
  • Guidance must distinguish confirmed Linux implementation facts from Rust translation guidance and AI-native design interpretation.

Primary artifacts:

  • progress-ledger.csv: file-by-file coverage tracker.
  • coverage-map.md: subsystem grouping and review targets.
  • architecture-map.md: source-backed kernel architecture map.
  • rust-translation.md: Rust reimplementation lessons and constraints.
  • ai-native-systems.md: AI-native system ideas grounded in Linux patterns.
  • do-not-copy-register.md: licensing and source-use boundaries.
  • uncertainty-log.md: unresolved research questions.
  • final-synthesis.md: synthesized conclusions after review.
  • file-notes/: per-file evidence notes.

Priority tracks:

  1. Boot, init, and process model.
  2. Scheduler and task lifecycle.
  3. Memory management.
  4. VFS and filesystems.
  5. Networking.
  6. Drivers and device model.
  7. Synchronization, RCU, locking, atomics.
  8. Interrupts, timers, workqueues.
  9. Tracing, perf, BPF, observability.
  10. Security, capabilities, namespaces, cgroups.
  11. Build system, Kconfig, module model.
  12. In-kernel Rust support under rust/kernel/**.

Review route:

  1. Start with coverage-map.md.
  2. Pick the next pending ledger row.
  3. Read the source and relevant Documentation/** entry.
  4. Write or update a file-notes/*.md note.
  5. Update progress-ledger.csv.
  6. Promote subsystem conclusions into architecture-map.md, rust-translation.md, or ai-native-systems.md.