vasilito
7dfebab9bf
Updates six documentation files to point readers to the new input-stack observability evidence and changelog entry. No content claims are altered — only "see also" pointers and inventory updates. - CHANGELOG.md: new 2026-06-30 entry documenting the input-stack fix (commitde9d1f4in local/sources/base/), the git server docs rewrite (commit0c60adc6b), and the build-system hardening addendum (commit41045fd2f). Includes the verified end-to-end interactive login evidence from the rebuilt ISO. - local/docs/boot-logs/README.md: add the new REDBEAR-MINI-BOOT-PS2D-INPUTD-LOG-FIX.md file to the inventory table. - local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md: see-also pointer in the inputd validation deliverables section. - local/docs/REDBEAR-BOOT-EXPERIENCE-PLAN.md: see-also pointer in the bootanim handoff section, noting that step 6 (REBIND_DISPLAY drm to inputd) now has companion observability via the new inputd startup log. - local/docs/USB-IMPLEMENTATION-PLAN.md: see-also pointer in the HID producer modernization section, noting that the fix lets operators distinguish "usbhidd dead" from "usbhidd alive but not enumerated by XHCI". - local/docs/GREETER-LOGIN-IMPLEMENTATION-PLAN.md: see-also pointer in the service wiring section, noting that the greeter can rely on the new inputd/ps2d startup lines being present before inputd -A 3 runs.
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) |
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:
- The command is still correct as-written. It was the right command at the time. Leave the log alone.
- 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. - 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.mdfor current usage." Do not rewrite the original line.
Building the current redbear-full target
The canonical v6.0 build command is:
./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
make qemu CONFIG_NAME=redbear-mini # Boot the latest built image in QEMU