[Bug 257209] Typing ? at a loader prompt does not show the commands from loader.4th

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 15 Jul 2021 15:08:10 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257209

            Bug ID: 257209
           Summary: Typing ? at a loader prompt does not show the commands
                    from loader.4th
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs_at_FreeBSD.org
          Reporter: ceri_at_FreeBSD.org

Created attachment 226486
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=226486&action=edit
Boot menu from a virtualbox 14-CURRENT snapshot

disable-module is a very useful loader command if you are trying to get certain
things to work (in my case, loading nvidia.ko from loader.conf makes the
machine unbootable), but it does not appear if you type ? at a loader prompt.

stand/forth/loader.4th suggests that it (and other useful commands) ought to:

: .? 2 spaces 2swap 15 #type 2 spaces type cr ;

\ Execute the ? command to print all the commands defined in
\ C, then list the ones we support here. Please note that this
\ doesn't use pager_* routines that the C implementation of ?
\ does, so these will always appear, even if you stop early
\ there. And they may cause the commands to scroll off the
\ screen if the number of commands modulus LINES is close
\ to LINEs....
: ?
  ['] ? execute
  s" boot-conf" s" load kernel and modules, then autoboot" .?
  s" read-conf" s" read a configuration file" .?
  s" enable-module" s" enable loading of a module" .?
  s" disable-module" s" disable loading of a module" .?
  s" toggle-module" s" toggle loading of a module" .?
  s" show-module" s" show module load data" .?
  s" try-include" s" try to load/interpret files" .?
;

See the screenshots for evidence of it not working, but while this is a vbox
installation I have the same issue on a physical amd64 machine.

-- 
You are receiving this mail because:
You are the assignee for the bug.
Received on Thu Jul 15 2021 - 15:08:10 UTC

Original text of this message