Skip to content

Commit

Permalink
bhyve.8: fix -k description
Browse files Browse the repository at this point in the history
Apparently 19eaa01 inserted -K description in the middle of -k.

Reviewed by:	markj
Sponsored by:	The FreeBSD Foundation
MFC after:	3 days
Differential revision:	https://reviews.freebsd.org/D43164
  • Loading branch information
kostikbel committed Dec 22, 2023
1 parent 59a35b7 commit 72f1e31
Showing 1 changed file with 10 additions and 10 deletions.
20 changes: 10 additions & 10 deletions usr.sbin/bhyve/bhyve.8
Original file line number Diff line number Diff line change
Expand Up @@ -196,16 +196,6 @@ Print help message and exit.
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
.It Fl K Ar layout
Specify the keyboard layout.
The value that can be specified sets the file name in
.Ar /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.
.Pq Sq = ,
and a value.
No spaces are permitted between the variable name, equals sign, or
Expand All @@ -216,6 +206,16 @@ are ignored.
See
.Xr bhyve_config 5
for more details.
.It Fl K Ar layout
Specify the keyboard layout.
The value that can be specified sets the file name in
.Ar /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.
.It Fl l Cm help
Print a list of supported LPC devices.
.It Fl l Ar lpcdev Ns Op Cm \&, Ns Ar conf
Expand Down

0 comments on commit 72f1e31

Please sign in to comment.