vms-b81: conversational boot — SYSBOOT> halts before executive attach - #301
Merged
Merged
Conversation
Adds a boot-flag register (substrate analogue of VMS R5) plumbed through
boot.sh/run-qemu.sh (ovmx.flags=). With the conversational bit set, PID 1
halts at a "SYSBOOT> " prompt on the console before any banner and before
executive_attach, implementing SHOW / SET / USE CURRENT|DEFAULT / CONTINUE /
WRITE against the loaded parameter set with VMS SET-vs-WRITE persistence
(SET affects this boot; only WRITE rewrites the file). Static PID 1: raw
console reads, no readline. Prompt text exactly 'SYSBOOT> '.
New: src/ovmx_init/sysboot.{c,h}, tests/qemu/test_sysboot_conversational.sh.
Wired into ovmx_init.c; early-boot output-ordering assertions added to
test_executive_integral.sh.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
baron-3dl
force-pushed
the
vms-b81-conversational-boot
branch
from
August 11, 2026 05:52
7fa51ca to
3fd5564
Compare
baron-3dl
added a commit
that referenced
this pull request
Aug 11, 2026
…in diagnostics) (#321) * vms-832: bump OVMX_PRODUCT_VERSION to V0.3-3 Third point release off tag 0.3-2, cut through the RE machinery (vms-a84). Payload: conversational boot (#301), DCL Phase 2 facade-kills (ASSIGN->real logical names #316, STOP->real sys$delprc #318, SET PASSWORD->real SYSUAF hash change #319), and rejoin isolation diagnostics (#314/#317/#320). No test hardcodes the version literal -- tests/libvms/test_identity.c and friends all compare against the OVMX_PRODUCT_VERSION macro, so no de-hardcoding was needed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * vms-832: generate V0.3-3 release notes (boot + DCL Phase 2 + rejoin diagnostics) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: alice <alice@workspace.local> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the last boot-mechanism gap in the 0.4 "boots faithfully" milestone.
A boot-flag register (substrate analogue of VMS R5) is plumbed through
boot.sh/run-qemu.sh(ovmx.flags=). With the conversational bit set, PID 1 halts at aSYSBOOT>prompt on the console before any banner and before executive_attach, implementing against the loaded parameter set:SHOW <param>(byte-shaped to the §3.1 capture),SHOW /STARTUPSET <param> <value>,USE CURRENT|DEFAULT,CONTINUE,WRITESETaffects this boot only; the parameter file is rewritten only by explicitWRITE.Static PID 1 — raw console reads, no readline. New
src/ovmx_init/sysboot.{c,h}+tests/qemu/test_sysboot_conversational.sh; early-boot output-ordering assertions added totest_executive_integral.sh.Design:
docs/design-boot-faithful.md§2.2/§3.1/§4.2. Item: vms-b81.🤖 Generated with Claude Code