vasilito
890be982a6
Replace all non-canonical build invocations (bare 'make all/live CONFIG_NAME=', 'scripts/build-iso.sh', 'scripts/run.sh') with the canonical './local/scripts/build-redbear.sh' wrapper. Updated: AGENTS.md, local/AGENTS.md, README.md, docs/README.md, docs/06-BUILD-SYSTEM-SETUP.md, and 6 active local/docs plan files. Archived docs and frozen boot-logs left as-is (historical evidence).
58 lines
2.7 KiB
Markdown
58 lines
2.7 KiB
Markdown
# Red Bear OS QEMU Boot Logs
|
|
|
|
This directory contains frozen QEMU boot evidence captured during validation runs of
|
|
the Red Bear OS desktop target (`redbear-full`). The files here are point-in-time
|
|
records and **must not be edited** to "update" build commands or package versions —
|
|
doing so would invalidate them as historical evidence.
|
|
|
|
## What lives here
|
|
|
|
| File | What it captures |
|
|
|------|------------------|
|
|
| `REDBEAR-FULL-BOOT-RESULTS.md` | Reference QEMU boot capture (2026-06-09) |
|
|
| `REDBEAR-FULL-BOOT-EXTENDED-RESULTS.md` | Extended QEMU boot capture |
|
|
| `REDBEAR-FULL-BOOT-POST-VIRTIO-BLKD-FIX-RESULTS.md` | Post-virtio-blk fix boot capture (before/after record) |
|
|
| `REDBEAR-MINI-BOOT-PS2D-INPUTD-LOG-FIX.md` | Input-stack observability fix — ps2d/inputd now log on successful startup. Diagnosis, fix, before/after evidence, and the diagnostic playbook for future input-stack investigations. (2026-06-30) |
|
|
| `REDBEAR-MINI-BOOT-PS2D-INPUTD-LOG-FIX.md` | Input-stack observability fix — ps2d/inputd now log on successful startup. Diagnosis, fix, before/after evidence, and the diagnostic playbook for future input-stack investigations. (2026-06-30) |
|
|
|
|
## Why these are frozen
|
|
|
|
These files are the project's ground-truth evidence that a specific Red Bear build
|
|
booted, reached specific init stages, and exposed specific subsystem states at a
|
|
specific commit. They are the only place where "this is what we saw" is preserved
|
|
verbatim. Editing them retroactively — even to fix typos — would compromise the
|
|
evidentiary value.
|
|
|
|
## If a build command in here looks wrong
|
|
|
|
If a build command in one of these files looks outdated, the fix is **not** to
|
|
edit the log. The correct action is one of:
|
|
|
|
1. **The command is still correct as-written.** It was the right command at the
|
|
time. Leave the log alone.
|
|
2. **The command is outdated and the corresponding validation is being re-run.**
|
|
Write a NEW log file (e.g. `REDBEAR-FULL-BOOT-POST-QEMU-XYZ-FIX-RESULTS.md`)
|
|
with the new run's evidence. Do not edit the old one.
|
|
3. **The command is wrong and no new validation is planned.** Add a one-line
|
|
note at the bottom of the file: "Note: command X is now deprecated, see
|
|
`local/docs/BUILD-SYSTEM-IMPROVEMENTS.md` for current usage." Do not
|
|
rewrite the original line.
|
|
|
|
## Building the current redbear-full target
|
|
|
|
The canonical v6.0 build command is:
|
|
|
|
```bash
|
|
./local/scripts/build-redbear.sh redbear-full
|
|
```
|
|
|
|
This script enforces the v6.0 policies (local-over-WIP recipe priority, overlay
|
|
integrity, submodule hygiene, firmware presence warning) that bare `make all` /
|
|
`make live` invocations from older logs do not enforce.
|
|
|
|
## QEMU boot
|
|
|
|
```bash
|
|
make qemu # Boot the latest built image in QEMU
|
|
```
|