vasilito
1790010483
Round 18's N22 'stale-doc removal' deleted three docs on the stated
premise that they had 'no references anywhere in the repo'. That premise
was wrong for two of them, and SUPERSEDED-DOC-LOG.md's recorded
absorption destinations for those two do not exist:
- CUB-PACKAGE-MANAGER.md was said to be absorbed into a 'redbear-cub
recipe README.md' and NETWORKING-IMPROVEMENT-PLAN.md section 8.2.
Neither exists -- there is no cub README under local/recipes/system/cub,
and that plan has no package-manager section (its 'cubic' matches are
TCP congestion control). README.md meanwhile links the doc from its
Documentation list and names cub in six places, so this left a headline
component with no documentation at all.
- BLUETOOTH-IMPLEMENTATION-PLAN.md was said to be merged into
NETWORKING-IMPROVEMENT-PLAN.md section 3.x. That file contains three
passing mentions of Bluetooth, not a 703-line plan. local/AGENTS.md,
docs/README.md and docs/07 all still list it as a first-class subsystem
plan, and AGENTS.md forbids treating Bluetooth as secondary.
Both restored from aa480f7ca3^ and their SUPERSEDED-DOC-LOG entries
retracted with the reason. USB-VALIDATION-RUNBOOK.md's supersession is
genuine -- USB-IMPLEMENTATION-PLAN.md carries the runbook as section 6.x
test procedures -- so it stays removed and its one reference now points
there.
Also de-dangled references to docs the authorised 2026-07-27
consolidation (092d1b39c3) removed but which canonical docs still cited
as openable: the driver-manager ASSESSMENT-2026-07-22 and D5-AUDIT
evidence files and the archived migration plan, across eight documents.
They now name what they were and where the supersession is recorded.
Remaining unresolved references are upstream KWin's vendored README
pointing at upstream's own CONTRIBUTING.md, which is deliberately not
touched.
77 lines
3.2 KiB
Markdown
77 lines
3.2 KiB
Markdown
# Red Bear OS Networking Validation Log
|
||
|
||
**Status:** Staged (2026-07-27). See [HARDWARE-VALIDATION-MATRIX.md](./HARDWARE-VALIDATION-MATRIX.md)
|
||
for the live cross-component matrix and [HARDWARE-NETWORKING-INVENTORY.md](./HARDWARE-NETWORKING-INVENTORY.md)
|
||
for per-driver hardware availability.
|
||
|
||
## Purpose
|
||
|
||
This document is the canonical per-run log of bare-metal networking validation activities for
|
||
Red Bear OS. Each run records:
|
||
|
||
- Hardware under test (machine, NIC model, BIOS/UEFI version)
|
||
- Software versions (kernel, relibc, netstack, drivers)
|
||
- Test commands executed
|
||
- Observed results
|
||
- New regressions or fixes
|
||
|
||
## Related Documents
|
||
|
||
This log is one of three coordinated artifacts. Read them in this order:
|
||
|
||
1. [HARDWARE-NETWORKING-INVENTORY.md](./HARDWARE-NETWORKING-INVENTORY.md) — *what* hardware
|
||
is available for validation. Tracks test bench inventory, per-driver hardware availability,
|
||
and acquisition priority list.
|
||
2. [HARDWARE-VALIDATION-MATRIX.md](./HARDWARE-VALIDATION-MATRIX.md) — *the state* of validation
|
||
per component. Tracks QEMU / bare-metal / hardware columns and gates the production-readiness
|
||
status.
|
||
3. This document — *the per-run record* of validation activities that update the matrix.
|
||
|
||
Per the project's evidence policy (per the [NETWORKING-IMPROVEMENT-PLAN.md](./NETWORKING-IMPROVEMENT-PLAN.md)
|
||
§Validation Evidence Requirements), every "validated" claim in any plan or doc must be backed
|
||
by an entry in this log.
|
||
|
||
## Format
|
||
|
||
Each run entry should follow this structure (Markdown):
|
||
|
||
```markdown
|
||
## YYYY-MM-DD — <Test bench> — <Operator>
|
||
|
||
**Hardware:** <machine> · <NIC model> · <PCI IDs>
|
||
**Software:** Red Bear OS <branch> · kernel <hash> · relibc <hash> · netstack <hash>
|
||
**Scope:** <what was tested, e.g. "e1000d on Threadripper — IPv4 DHCP+ping">
|
||
**Commands:**
|
||
\```
|
||
<exact commands run, with exit codes>
|
||
\```
|
||
**Results:** <PASS/FAIL/PARTIAL per test case>
|
||
**Regressions:** <newly discovered issues, with file:line>
|
||
**Fixes:** <fixes applied, with commit hash>
|
||
**Updated:** <links to entries updated in HARDWARE-VALIDATION-MATRIX.md>
|
||
```
|
||
|
||
## Runs
|
||
|
||
*(none yet — first run is the open task for the operator)*
|
||
|
||
## Cross-References to Other Validation Artifacts
|
||
|
||
- [FIREWALL-VALIDATION-LOG.md](./FIREWALL-VALIDATION-LOG.md) — netfilter rule validation (specific
|
||
to the `netfilter:` scheme, six scenario design documented in §Scenario A–F).
|
||
- [USB-IMPLEMENTATION-PLAN.md](./USB-IMPLEMENTATION-PLAN.md) § 6.x — USB controller validation matrix and
|
||
QEMU scripts.
|
||
- [HARDWARE-VALIDATION-MATRIX.md](./HARDWARE-VALIDATION-MATRIX.md) — cross-component validation
|
||
status (this log updates it).
|
||
- [HARDWARE-NETWORKING-INVENTORY.md](./HARDWARE-NETWORKING-INVENTORY.md) — hardware gate for
|
||
this log (records what can be tested).
|
||
|
||
## Open Tasks (as of 2026-07-27)
|
||
|
||
- **T-N1:** Acquire USB-C Ethernet dongle (~$15) for LG Gram bare-metal networking.
|
||
- **T-N2:** Collect Threadripper NIC inventory (`lspci -nn | grep -i ethernet`).
|
||
- **T-N3:** Acquire USB Bluetooth adapter (~$10) for LG Gram bare-metal Bluetooth.
|
||
- **T-N4:** First bare-metal networking run on Threadripper + onboard NIC.
|
||
|
||
These are the same tasks tracked in §15.4 of the [code audit](../docs/NETWORKING-AND-DRIVERS-CODE-ASSESSMENT-2026-07-27.md).
|