[Bug 271134] bhyve(8), bhyvectl(8), bhyve(4), bhyve_config(5): manual pages cleanup
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 271134] bhyve(8) manual page cleanup"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 27 Feb 2025 16:03:19 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271134
--- Comment #10 from Jason Mann <jason.mann@gmail.com> ---
I've spotted another seemingly malformed section:
> -k config_file
> Set configuration variables from a simple, key-value config
> file. Each line of the config file is expected to consist of
> a config variable name, an equals sign
>
> -K layout Specify the keyboard layout. The value that can be specified
> sets the file name in /usr/share/bhyve/kbdlayout. This
> specification only works when loaded with UEFI mode for VNC.
> When using a VNC client that supports QEMU Extended Key Event
> Message (e.g. TigerVNC), this option isn't needed. When
> using a VNC client that doesn't support QEMU Extended Key
> Event Message (e.g. tightVNC), the layout defaults to the US
> keyboard unless specified otherwise. (‘=’), and a value. No
> spaces are permitted between the variable name, equals sign,
> or value. Blank lines and lines starting with ‘#’ are
> ignored. See bhyve_config(5) for more details.
It appears that the '-K layout' section has been inserted into the middle of
the '-k' section. The text beginning with "('=')" looks like it should follow
"an equals sign" at the end of the '-k config_file' section, like this:
> -k config_file
> Set configuration variables from a simple, key-value config
> file. Each line of the config file is expected to consist of
> a config variable name, an equals sign (‘=’), and a value. No
> spaces are permitted between the variable name, equals sign,
> or value. Blank lines and lines starting with ‘#’ are
> ignored. See bhyve_config(5) for more details.
>
> -K layout Specify the keyboard layout. The value that can be specified
> sets the file name in /usr/share/bhyve/kbdlayout. This
> specification only works when loaded with UEFI mode for VNC.
> When using a VNC client that supports QEMU Extended Key Event
> Message (e.g. TigerVNC), this option isn't needed. When
> using a VNC client that doesn't support QEMU Extended Key
> Event Message (e.g. tightVNC), the layout defaults to the US
> keyboard unless specified otherwise.
--
You are receiving this mail because:
You are on the CC list for the bug.