vasilito
dc68054305
- Restore 29 recipe symlinks (libdrm, qtbase, dbus, sddm, pipewire, etc.) - Restore 33 patches (KDE, libdrm, mesa, pipewire, sddm, wireplumber) - Restore 20+ local/scripts (audit, lint, test, build helpers) - Restore src/cook/scheduler.rs, status.rs, gnu-config/ - Restore scripts/patch-inclusion-gate.sh, run_mini1.sh, validate-collision-log.sh - Recover TLC source from HEAD (was overwritten by 0.2.3 checkout) - Recover 11 local/docs plans from HEAD (were overwritten) - Recover qt6-wayland-smoke symlink from HEAD - Fix MOTD: remove garbled ASCII art, use clean text - Update version: 0.2.0 -> 0.2.4 in os-release, motd, config - Reduce filesystem_size: 1536 -> 512 MiB - Add ABSOLUTE RULE to AGENTS.md: never delete/ignore packages - Reduce pcid scheme log verbosity: info -> debug
56 lines
2.2 KiB
Markdown
56 lines
2.2 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) |
|
|
|
|
## 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 CONFIG_NAME=redbear-mini # Boot the latest built image in QEMU
|
|
```
|